Review and acrolinx

Author: kgremban

articles/iot-dps/how-to-manage-enrollments.md

@@ -1,7 +1,7 @@
 ---
 title: Manage device enrollments in the Azure portal
 titleSuffix: Azure IoT Hub Device Provisioning Service
-description: How to manage group and individual device enrollments for your Device Provisioning Service (DPS) in the Azure portal
+description: How to manage group and individual device enrollments for your Device Provisioning Service (DPS) in the Azure portal.
 author: kgremban
 ms.author: kgremban
 ms.date: 03/09/2023

articles/iot-dps/how-to-provision-multitenant.md

@@ -105,15 +105,15 @@ For simplicity, this tutorial uses [Symmetric key attestation](concepts-symmetri
 
 1. On the **Review + create** tab, verify all of your values then select **Create**.
 
-1. Once your enrollment group is creted, select its name *contoso-us-devices* from the enrollment groups list.
+1. Once your enrollment group is created, select its name *contoso-us-devices* from the enrollment groups list.
 
 1. Copy the *Primary key*. This key will be used later to generate unique device keys for both simulated devices.
 
 ## Create regional Linux VMs
 
-In this section, you'll create two regional Linux virtual machines (VMs). These VMs will run a device simulation sample from each region to demonstrate device provisioning for devices from both regions.
+In this section, you create two regional Linux virtual machines (VMs), one in **West US 2** and one in **East US 2**. These VMs run a device simulation sample from each region to demonstrate device provisioning for devices from both regions.
 
-To make clean-up easier, these VMs will be added to the same resource group that contains the IoT hubs that were created, *contoso-us-resource-group*. However, the VMs will run in separate regions (**West US 2** and **East US**).
+To make clean-up easier, add these VMs to the same resource group that contains the IoT hubs that were created, *contoso-us-resource-group*.
 
 1. In the Azure Cloud Shell, run the following command to create an **East US** region VM after making the following parameter changes in the command:
 
@@ -135,7 +135,7 @@ To make clean-up easier, these VMs will be added to the same resource group that
     --public-ip-sku Standard
     ```
 
-    This command will take a few minutes to complete. 
+    This command will take a few minutes to complete.
 
 2. Once the command has completed, copy the **publicIpAddress** value for your East US region VM.
 

articles/iot-dps/how-to-roll-certificates.md

@@ -98,13 +98,13 @@ If you are rolling certificates to handle certificate expirations, you should us
 
    :::image type="content" source="./media/how-to-roll-certificates/manage-certificates.png" alt-text="Screenshot that shows the certificates page.":::
 
-1. Select the compromised or expired certificate from the list, and then select **Delete**. Confirm the delete by entering the certificate name and click **OK**.
+1. Select the compromised or expired certificate from the list, and then select **Delete**. Confirm the delete by entering the certificate name and select **OK**.
 
 1. Follow steps outlined in [Configure verified CA certificates](how-to-verify-certificates.md) to add and verify new root CA certificates.
 
 1. Select **Manage enrollments** from the **Settings** section of the navigation menu for your Device Provisioning Service instance, and select the **Enrollment groups** tab.
 
-1. Click your enrollment group name from the list.
+1. Select your enrollment group name from the list.
 
 1. In the **X.509 certificate settings** section, and select your new root CA certificate to either replace the compromised or expired certificate, or to add as a secondary certificate.
 
@@ -122,7 +122,7 @@ If you are rolling certificates to handle certificate expirations, you should us
 
 1. Select **Manage enrollments** from the **Settings** section of the navigation menu for your Device Provisioning Service instance, and select the **Enrollment groups** tab.
 
-1. Select the group name grom the list.
+1. Select the group name from the list.
 
 1. Check the **Remove or replace primary/secondary certificate** checkboxes if you want to delete an existing certificate. Select the file folder icon to browse for and upload the new certificates.
 
@@ -146,9 +146,9 @@ Once the certificate is rolled on both the device and the Device Provisioning Se
 
 One easy way of programming devices to reprovision is to program the device to contact the provisioning service to go through the provisioning flow if the device receives an “unauthorized” error from attempting to connect to the IoT hub.
 
-Another way is for both the old and the new certificates to be valid for a short overlap, and use the IoT hub to send a command to devices to have them re-register via the provisioning service to update their IoT Hub connection information. Because each device can process commands differently, you will have to program your device to know what to do when the command is invoked. There are several ways you can command your device via IoT Hub, and we recommend using [direct methods](../iot-hub/iot-hub-devguide-direct-methods.md) or [jobs](../iot-hub/iot-hub-devguide-jobs.md) to initiate the process.
+Another way is for both the old and the new certificates to be valid for a short overlap, and use the IoT hub to send a command to devices to have them re-register via the provisioning service to update their IoT Hub connection information. Because each device can process commands differently, you have to program your device to know what to do when the command is invoked. There are several ways you can command your device via IoT Hub, and we recommend using [direct methods](../iot-hub/iot-hub-devguide-direct-methods.md) or [jobs](../iot-hub/iot-hub-devguide-jobs.md) to initiate the process.
 
-Once reprovisioning is complete, devices will be able to connect to IoT Hub using their new certificates.
+Once reprovisioning is complete, devices are able to connect to IoT Hub using their new certificates.
 
 ## Disallow certificates
 

articles/iot-dps/media/how-to-manage-enrollments/add-enrollment-group-symm-key.png renamed to articles/iot-dps/media/how-to-manage-enrollments/add-enrollment-group-symmetric-key.png

@@ -120,7 +120,7 @@ In this section, you'll prepare a development environment that's used to build t
 
 6. The code sample uses an X.509 certificate to provide attestation via X.509 authentication. Run the following command to build a version of the SDK specific to your development platform that includes the device provisioning client. A Visual Studio solution for the simulated device is generated in the `cmake` directory.
 
-    When specifying the path used with `-Dhsm_custom_lib` in the command below, make sure to use the absolute path to the library in the `cmake` directory you previously created. The path shown below assumes that you cloned the C SDK in the root directory of the C drive. If you used another directory, adjust the path accordingly.
+    When specifying the path used with `-Dhsm_custom_lib` in the following command, make sure to use the absolute path to the library in the `cmake` directory you previously created. The path shown assumes that you cloned the C SDK in the root directory of the C drive. If you used another directory, adjust the path accordingly.
 
     ```cmd
     cmake -Duse_prov_client:BOOL=ON -Dhsm_custom_lib=c:/azure-iot-sdk-c/cmake/provisioning_client/samples/custom_hsm_example/Debug/custom_hsm_example.lib ..
@@ -377,7 +377,7 @@ You won't need the Git Bash prompt for the rest of this quickstart. However, you
 
 7. When asked to **Enter pass phrase for device-key.pem:**, use the same pass phrase you did previously, `1234`.
 
-8. Copy the device certificate and unencrytped private key to the project directory for the X.509 device provisioning sample. The path given is relative to the location where you downloaded the SDK.
+8. Copy the device certificate and unencrypted private key to the project directory for the X.509 device provisioning sample. The path given is relative to the location where you downloaded the SDK.
 
     ```bash
     cp device-cert.pem ./azure-iot-sdk-node/provisioning/device/samples
@@ -438,11 +438,11 @@ This article demonstrates an individual enrollment for a single device to be pro
 
 ## Prepare and run the device provisioning code
 
-In this section, you'll update the sample code to send the device's boot sequence to your Device Provisioning Service instance. This boot sequence will cause the device to be recognized and assigned to an IoT hub linked to the DPS instance.
+In this section, you update the sample code to send the device's boot sequence to your Device Provisioning Service instance. This boot sequence causes the device to be recognized and assigned to an IoT hub linked to the DPS instance.
 
 ::: zone pivot="programming-language-ansi-c"
 
-In this section, you'll use your Git Bash prompt and the Visual Studio IDE.
+In this section, you use your Git Bash prompt and the Visual Studio IDE.
 
 ### Configure the provisioning device code
 
@@ -464,7 +464,7 @@ In this section, you update the sample code with your Device Provisioning Servic
     static const char* id_scope = "0ne00000A0A";
     ```
 
-1. Find the definition for the `main()` function in the same file. Make sure the `hsm_type` variable is set to `SECURE_DEVICE_TYPE_X509` as shown below.
+1. Find the definition for the `main()` function in the same file. Make sure the `hsm_type` variable is set to `SECURE_DEVICE_TYPE_X509`.
 
     ```c
     SECURE_DEVICE_TYPE hsm_type;
@@ -493,7 +493,7 @@ To update the custom HSM stub code to simulate the identity of the device with I
 
 1. Update the string value of the `CERTIFICATE` constant string using the device certificate, *device-cert.pem*, that you generated previously.
 
-    The syntax of certificate text in the sample must follow the pattern below with no extra spaces or parsing done by Visual Studio.
+    The syntax of certificate text in the sample must follow the following pattern with no extra spaces or parsing done by Visual Studio.
 
     ```c
     static const char* const CERTIFICATE = "-----BEGIN CERTIFICATE-----\n"
@@ -513,7 +513,7 @@ To update the custom HSM stub code to simulate the identity of the device with I
 
 1. Update the string value of the `PRIVATE_KEY` constant with the unencrypted private key for your device certificate, *unencrypted-device-key.pem*.
 
-    The syntax of the private key text must follow the pattern below with no extra spaces or parsing done by Visual Studio.
+    The syntax of the private key text must follow the following pattern with no extra spaces or parsing done by Visual Studio.
 
     ```c
     static const char* const PRIVATE_KEY = "-----BEGIN RSA PRIVATE KEY-----\n"
@@ -580,13 +580,12 @@ In this section, you'll use your Windows command prompt.
 
    >[!NOTE]
    >Additional parameters can be passed along while running the application to change the TransportType (-t) and the GlobalDeviceEndpoint (-g).
-    
 
     ```cmd
     dotnet run -- -s 0ne00000A0A -c certificate.pfx -p 1234
     ```
 
-5. The device will connect to DPS and be assigned to an IoT hub. Then, the device will send a telemetry message to the IoT hub.
+5. The device connects to DPS and is assigned to an IoT hub. Then, the device will send a telemetry message to the IoT hub.
 
     ```output
     Loading the certificate...
@@ -660,7 +659,7 @@ In this section, you'll use your Windows command prompt.
     node register_x509.js
     ```
 
-    You should see output similar to the following:
+    You should see output similar to the following example:
 
     ```output
     registration succeeded
@@ -722,7 +721,7 @@ In this section, you'll use your Windows command prompt.
 
 1. Review the code for [provision_x509.py](https://github.com/Azure/azure-iot-sdk-python/blob/main/samples/async-hub-scenarios/provision_x509.py). If you're not using **Python version 3.7** or later, make the [code change mentioned here](https://github.com/Azure/azure-iot-sdk-python/tree/main/samples/async-hub-scenarios#advanced-iot-hub-scenario-samples-for-the-azure-iot-hub-device-sdk) to replace `asyncio.run(main())` and save your changes.
 
-1. Run the sample. The sample will connect to DPS, which will provision the device to an IoT hub. After the device is provisioned, the sample will send some test messages to the IoT hub.
+1. Run the sample. The sample connects to DPS, which will provision the device to an IoT hub. After the device is provisioned, the sample will send some test messages to the IoT hub.
 
     ```cmd
     $ python azure-iot-sdk-python/samples/async-hub-scenarios/provision_x509.py
@@ -759,7 +758,7 @@ In this section, you'll use your Windows command prompt.
 
 ::: zone pivot="programming-language-java"
 
-In this section, you'll use both your Windows command prompt and your Git Bash prompt.
+In this section, you use both your Windows command prompt and your Git Bash prompt.
 
 1. In the Azure portal, select the **Overview** tab for your Device Provisioning Service.
 
@@ -773,7 +772,7 @@ In this section, you'll use both your Windows command prompt and your Git Bash p
     cd .\azure-iot-sdk-java\provisioning\provisioning-samples\provisioning-X509-sample
     ```
 
-1. Enter the provisioning service and X.509 identity information in the sample code. This is used during provisioning, for attestation of the simulated device, prior to device registration.
+1. Enter the provisioning service and X.509 identity information in the sample code. This information is used during provisioning, for attestation of the simulated device, prior to device registration.
 
     1. Open the file `.\src\main\java\samples\com/microsoft\azure\sdk\iot\ProvisioningX509Sample.java` in your favorite editor.
 
@@ -786,7 +785,7 @@ In this section, you'll use both your Windows command prompt and your Git Bash p
 
     1. Update the value of the `leafPublicPem` constant string with the value of your certificate, *device-cert.pem*.
 
-        The syntax of certificate text must follow the pattern below with no extra spaces or characters.
+        The syntax of certificate text must follow the following pattern with no extra spaces or characters.
 
         ```java
         private static final String leafPublicPem = "-----BEGIN CERTIFICATE-----\n" +
@@ -806,7 +805,7 @@ In this section, you'll use both your Windows command prompt and your Git Bash p
 
     1. Update the string value of the `leafPrivateKey` constant with the unencrypted private key for your device certificate, *unencrypted-device-key.pem*.
 
-        The syntax of the private key text must follow the pattern below with no extra spaces or characters.
+        The syntax of the private key text must follow the following pattern with no extra spaces or characters.
 
         ```java
         private static final String leafPrivateKey = "-----BEGIN PRIVATE KEY-----\n" +
@@ -833,13 +832,13 @@ In this section, you'll use both your Windows command prompt and your Git Bash p
     cd target
     ```
 
-1. The build outputs .jar file in the `target` folder with the following file format: `provisioning-x509-sample-{version}-with-deps.jar`; for example: `provisioning-x509-sample-1.8.1-with-deps.jar`. Execute the .jar file. You may need to replace the version in the command below.
+1. The build outputs .jar file in the `target` folder with the following file format: `provisioning-x509-sample-{version}-with-deps.jar`; for example: `provisioning-x509-sample-1.8.1-with-deps.jar`. Execute the .jar file. You may need to replace the version in the following command.
 
     ```cmd
     java -jar ./provisioning-x509-sample-1.8.1-with-deps.jar
     ```
 
-    The sample will connect to DPS, which will provision the device to an IoT hub. After the device is provisioned, the sample will send some test messages to the IoT hub.
+    The sample connects to DPS, which will provision the device to an IoT hub. After the device is provisioned, the sample will send some test messages to the IoT hub.
 
     ```output
     Starting...