Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into edit-net-features-downtime

Author: b-ahibbard

articles/azure-netapp-files/use-availability-zones.md

@@ -1,19 +1,19 @@
 ---
-title: Use availability zones zonal placement for application high availability with Azure NetApp Files
+title: Use availability zone placement for application high availability with Azure NetApp Files
 description: Azure availability zones are highly available, fault tolerant, and more scalable than traditional single or multiple data center infrastructures.
 services: azure-netapp-files
 author: b-hchen
 ms.service: azure-netapp-files
 ms.topic: conceptual
-ms.date: 05/22/2024
+ms.date: 10/22/2024
 ms.author: anfdocs
 ---
-# Use availability zones zonal placement for application high availability with Azure NetApp Files
+# Use availability zone placement for application high availability with Azure NetApp Files
 
 Azure [availability zones](../availability-zones/az-overview.md#availability-zones) are physically separate locations within each supporting Azure region that are tolerant to local failures. Failures can range from software and hardware failures to events such as earthquakes, floods, and fires. Tolerance to failures is achieved because of redundancy and logical isolation of Azure services. To ensure resiliency, a minimum of three separate availability zones are present in all [availability zone-enabled regions](../availability-zones/az-overview.md#azure-regions-with-availability-zones). 
 
 >[!IMPORTANT]
-> Availability zones are referred to as _logical zones_. Each data center is assigned to a physical zone. Physical zones are mapped to logical zones in your Azure subscription, and the mapping is different with different subscriptions. Azure subscriptions are automatically assigned this mapping when a subscription is created. Azure NetApp Files aligns with the generic logical-to-physical availability zone mapping for all Azure services for the subscription. 
+> Availability zones are referred to as _logical zones_. Each data center is assigned to a physical zone. [Physical zones are mapped to logical zones in your Azure subscription](/azure/reliability/availability-zones-overview#physical-and-logical-availability-zones), and the mapping is different with different subscriptions. Azure subscriptions are automatically assigned this mapping when a subscription is created. Azure NetApp Files aligns with the generic logical-to-physical availability zone mapping for all Azure services for the subscription. 
 
 Azure availability zones are highly available, fault tolerant, and more scalable than traditional single or multiple data center infrastructures. Azure availability zones let you design and operate applications and databases that automatically transition between zones without interruption. You can design resilient solutions by using Azure services that use availability zones.  
 

articles/iot-central/core/concepts-private-endpoints.md

@@ -3,7 +3,7 @@ title: Network security using private endpoints in IoT Central
 description: Use private endpoints to limit and secure device connectivity to your IoT Central application instead of using public URLs.
 author: dominicbetts
 ms.author: dobett
-ms.date: 05/22/2023
+ms.date: 10/22/2024
 ms.topic: conceptual
 ms.service: azure-iot-central
 services: iot-central
@@ -51,7 +51,7 @@ IoT Central creates multiple customer visible FQDNs as part of a private endpoin
 
 :::image type="content" source="media/concepts-private-endpoints/visible-fqdns.png" alt-text="Screenshot from the Azure portal that shows the customer visible FQDNs.":::
 
-The IoT Central private endpoint uses multiple IP addresses from your virtual network and subnet. Also, based on application's load profile, IoT Central [autoscales its underlying IoT Hubs](/azure/iot-central/core/concepts-scalability-availability) so the number of IP addresses used by a private endpoint may increase. Plan for this possible increase when you determine the size for the subnet.
+The IoT Central private endpoint uses multiple IP addresses from your virtual network and subnet. Also, based on application's load profile, IoT Central [autoscales its underlying IoT Hubs](/azure/iot-central/core/concepts-scalability-availability) so the number of IP addresses used by a private endpoint might increase. Plan for this possible increase when you determine the size for the subnet.
 
 Use the following information to help determine the total number of IP addresses required in your subnet:
 

articles/iot-central/core/howto-create-organizations.md

@@ -5,7 +5,7 @@ services: iot-central
 ms.service: azure-iot-central
 author: dominicbetts
 ms.author: dobett
-ms.date: 06/14/2023
+ms.date: 10/22/2024
 ms.topic: how-to
 ---
 
@@ -99,7 +99,7 @@ Then select the permissions for the role.
 
 ## Invite users
 
-After you've created your organization hierarchy and assigned devices to organizations, invite users to your application and assign them to organizations.
+After you create your organization hierarchy and assigned devices to organizations, invite users to your application and assign them to organizations.
 
 To invite a user, navigate to **Permissions > Users**. Enter their email address, the organization they're assigned to, and the role or roles they're a member of. The organization you select filters the list of available roles to make sure you assign the user to a valid role:
 
@@ -112,13 +112,13 @@ You can assign the same user to multiple organizations. The user can have a diff
 | [email protected] | Org Administrator | Custom app |
 | [email protected] | Org Viewer | Custom app |
 
-When you invite a new user, you need to share the application URL with them and ask them to sign in. After the user has signed in for the first time, the application appears on the user's [My apps](https://apps.azureiotcentral.com/myapps) page.
+When you invite a new user, you need to share the application URL with them and ask them to sign in. After the user signs in for the first time, the application appears on the user's [My apps](https://apps.azureiotcentral.com/myapps) page.
 
 To access the application for the first time, an invited user must first navigate to the application using the link they receive from the administrator. The application isn't visible on the [My apps](https://apps.azureiotcentral.com/myapps) page on the Azure IoT Central site until then.
 
 ## Use organizations
 
-After you've created your organization hierarchy, you can use organizations in areas of your application such as:
+After you create your organization hierarchy, you can use organizations in areas of your application such as:
 
 - [Organization dashboards](howto-manage-dashboards.md) that show information to users about devices in their organization.
 - [Device groups](tutorial-use-device-groups.md) for devices in specific organizations.
@@ -139,7 +139,7 @@ To set the default organization, select **Settings** on the top menu bar:
 
 ## Add organizations to an existing application
 
-An application may contain devices, users, and experiences such as dashboards, device groups, and jobs before you add an organization hierarchy.
+An application might contain devices, users, and experiences such as dashboards, device groups, and jobs before you add an organization hierarchy.
 
 When you start adding organizations, all existing devices, users, and experiences remain associated with the root organization in the application:
 

articles/iot-central/core/howto-create-private-endpoint.md

@@ -3,7 +3,7 @@ title: Create a private endpoint for Azure IoT Central
 description: Learn how to create and configure a private endpoint to securely connect your devices to IoT Central over a private virtual network.
 author: dominicbetts
 ms.author: dobett
-ms.date: 05/19/2023
+ms.date: 10/22/2024
 ms.topic: how-to
 ms.service: azure-iot-central
 services: iot-central
@@ -73,7 +73,7 @@ To see all the private endpoints created for your application:
 
 ### Use a custom DNS server
 
-In some situations, you may not be able to integrate with the private DNS zone of the virtual network. For example, you may use your own DNS server or create DNS records using the host files on your virtual machines. This section describes how to get to the DNS zones.
+In some situations, you might not be able to integrate with the private DNS zone of the virtual network. For example, you might use your own DNS server or create DNS records using the host files on your virtual machines. This section describes how to get to the DNS zones.
 
 1. Install [chocolatey](https://chocolatey.org/install).
 1. Install ARMClient:
@@ -160,9 +160,9 @@ Update your device code to use the direct DPS endpoint.
 
 - Don't use private link subdomain URLs to connect your devices to IoT Central. Always use the DPS URL shown in your IoT Central application after you create the private endpoint.
 
-- Using Azure provided private DNS zones for DNS management. Avoid using your own DNS server because you would need to constantly update your DNS configuration to keep up as IoT Central autoscales its resources.
+- Use Azure provided private DNS zones for DNS management. Avoid using your own DNS server because you would need to constantly update your DNS configuration to keep up as IoT Central autoscales its resources.
 
-- If you create multiple private endpoints for same IoT Central resource, the DNS Zone may overwrite the FQDNs so you should add them again.
+- If you create multiple private endpoints for same IoT Central resource, the DNS Zone might overwrite the FQDNs so you should add them again.
 
 ## Limitations
 
@@ -226,9 +226,9 @@ If you find an FQDN that doesn't match its corresponding IP address, fix your cu
 DNS configuration can be overwritten if you create or delete multiple private endpoints for a single IoT Central application:
 
 - In the Azure portal, navigate to the private endpoint resource.
-- In the DNS section, make sure there are entries for all required resources:  IoT Hubs, Event Hubs, DPS and IoT Central FQDNs.
+- In the DNS section, make sure there are entries for all required resources:  IoT Hubs, Event Hubs, DPS, and IoT Central FQDNs.
 - Verify that the IPs (and IPs for other private endpoints using this DNS zone) are reflected in the A record of the DNS.
-- Remove any A records for IPs from older private endpoints that have already been deleted.
+- Remove any A records for IPs from older private endpoints that were previously deleted.
 
 ### Other troubleshooting tips
 

articles/iot-central/core/howto-customize-ui.md

@@ -3,7 +3,7 @@ title: Customize the Azure IoT Central UI
 description: How to customize the theme, text, and help links for your Azure IoT Central application to apply your branding to the application.
 author: dominicbetts
 ms.author: dobett
-ms.date: 05/22/2023
+ms.date: 10/22/2024
 ms.topic: how-to
 ms.service: azure-iot-central
 services: iot-central
@@ -37,7 +37,7 @@ On this page, you can customize the following aspects of your application:
 
 ### Application logo
 
-A PNG image, no larger than 1 MB, with a transparent background. This logo displays to the left on the IoT Central application title bar.
+A PNG image, no larger than 1 MB, with a transparent background. This logo displays on the IoT Central application title bar.
 
 If your logo image includes the name of your application, you can hide the application name text. For more information, see [Manage your application](howto-administer.md#change-application-name-and-url).
 
@@ -81,7 +81,7 @@ Following example shows how to change the word `Device` to `Asset` when you view
 
 1. Select **Add application text** and select the English language in the dropdown.
 1. Download the default text file. The file contains a JSON definition of the text strings you can change.
-1. Open the file in a text editor and edit the right-hand side strings to replace the word `device` with `asset` as shown in the following example:
+1. To replace the word `device` with `asset`, open the file in a text editor and edit the value strings as shown in the following example:
 
       ```json
       {

articles/iot-central/core/howto-manage-data-export-with-rest-api.md

@@ -1,9 +1,9 @@
 ---
 title: Use the REST API to manage data export in Azure IoT Central
-description: How to use the IoT Central REST API to manage data export in an application. Export data to desinations such as blob storage, event hubs, and service bus.
+description: How to use the IoT Central REST API to manage data export in an application. Export data to destinations such as blob storage, event hubs, and service bus.
 author: dominicbetts
 ms.author: dobett
-ms.date: 06/13/2023
+ms.date: 10/22/2024
 ms.topic: how-to
 ms.service: azure-iot-central
 services: iot-central
@@ -208,7 +208,7 @@ The request body has some required fields:
 
 There are some optional fields you can use to add more details to the export.
 
-* `enrichments`: Extra pieces of information to include with each sent message. Data is represented as a set of key/value pairs, where the key is the name of the enrichment that will appear in the output message and the value identifies the data to send.
+* `enrichments`: Extra pieces of information to include with each sent message. Data is represented as a set of key/value pairs, where the key is the name of the enrichment to appear in the output message and the value identifies the data to send.
 * `filter`: Query defining which events from the source should be exported.
 
 The response to this request looks like the following example:

articles/iot-central/core/howto-manage-devices-in-bulk.md

@@ -5,7 +5,7 @@ ms.service: azure-iot-central
 services: iot-central
 author: dominicbetts
 ms.author: dobett
-ms.date: 07/24/2023
+ms.date: 10/22/2024
 ms.topic: how-to
 ms.custom: engagement-fy23
 ---
@@ -88,7 +88,7 @@ The following example shows you how to create and run a job to set the light thr
 
 ## Manage jobs
 
-To stop a running job, open it and select **Stop**. The job status changes to reflect that the job is stopped. The **Summary** section shows which devices have completed, have failed, or are still pending.
+To stop a running job, open it and select **Stop**. The job status changes to reflect that the job is stopped. The **Summary** section shows which devices completed, failed, or are still pending.
 
 When a job is in a stopped state, you can select **Continue** to resume running the job. The job status changes to reflect that the job is now running again. The **Summary** section continues to update with the latest progress.
 
@@ -106,15 +106,15 @@ After a job is created, the **Status** column updates with the latest job status
 | Failed               | This job failed and didn't fully run on devices.  |
 | Pending              | This job hasn't yet begun running on devices.         |
 | Running              | This job is currently running on devices.             |
-| Stopped              | A user has manually stopped this job.           |
+| Stopped              | A user manually stopped this job.           |
 | Canceled             | This job was canceled because the threshold set on the **Delivery options** page was exceeded. |
 
 The status message is followed by an overview of the devices in the job. The following table lists the possible *device status* values:
 
 | Status message       | Status meaning                                                     |
 | -------------------- | ------------------------------------------------------------------ |
 | Succeeded            | The number of devices that the job successfully ran on.       |
-| Failed               | The number of devices that the job has failed to run on.       |
+| Failed               | The number of devices that the job failed to run on.       |
 
 To view the status of the job and all the affected devices, open the job. Next to each device name, you see one of the following status messages:
 
@@ -159,8 +159,8 @@ To register a large number of devices to your application, you can bulk import d
 
 | Column | Description |
 | - | - |
-| IOTC_DEVICEID | The device ID is a unique identified this device will use to connect. The device ID can contain letters, numbers, and the `-` character without any spaces. The maximum length is 128 characters. |
-| IOTC_DEVICENAME | Optional. The device name is a friendly name that will be displayed throughout the application. If not specified, the device name is the same as the device ID. The maximum length is 148 characters. |
+| IOTC_DEVICEID | The device ID is a unique identified this device uses to connect. The device ID can contain letters, numbers, and the `-` character without any spaces. The maximum length is 128 characters. |
+| IOTC_DEVICENAME | Optional. The device name is a friendly name that's displayed throughout the application. If not specified, the device name is the same as the device ID. The maximum length is 148 characters. |
 
 To bulk-register devices in your application:
 
@@ -177,7 +177,7 @@ To bulk-register devices in your application:
 
 1. Select the CSV file that has the list of device IDs to be imported.
 
-1. Device import starts once the file has been uploaded. You can track the import status in the **Device Operations** panel. This panel appears automatically after the import starts or you can access it through the bell icon in the top right-hand corner.
+1. Device import starts after the file uploads. You can track the import status in the **Device Operations** panel. This panel appears automatically after the import starts or you can access it through the bell icon in the top right-hand corner.
 
 1. Once the import completes, a success message is shown in the **Device Operations** panel.
 

articles/iot-central/core/howto-manage-jobs-with-rest-api.md

@@ -3,7 +3,7 @@ title: Use the REST API to manage jobs in Azure IoT Central
 description: How to use the IoT Central REST API to create and manage jobs in an application to bulk manage your devices
 author: dominicbetts
 ms.author: dobett
-ms.date: 06/14/2023
+ms.date: 10/22/2024
 ms.topic: how-to
 ms.service: azure-iot-central
 services: iot-central