minor edits and acrolinx improvements

wesmc7777 · wesmc7777 · commit bf03a5e75e94 · 2018-07-19T04:10:20.000-04:00
diff --git a/articles/iot-dps/tutorial-set-up-cloud.md b/articles/iot-dps/tutorial-set-up-cloud.md
@@ -23,9 +23,9 @@ This tutorial shows how to set up the cloud for automatic device provisioning us
 
 If you don't have an Azure subscription, create a [free account](https://azure.microsoft.com/free/) before you begin.
 
-## Log in to the Azure portal
+## Sign in to the Azure portal
 
-Log in to the [Azure portal](https://portal.azure.com/).
+Sign in to the [Azure portal](https://portal.azure.com/).
 
 ## Create a Device Provisioning Service instance and get the ID scope
 
@@ -45,9 +45,9 @@ Follow these steps to create a new Device Provisioning Service instance.
 
    ![Enter basic information about your DPS in the portal](./media/tutorial-set-up-cloud/create-iot-dps-portal.png)
 
-5. Click **Create**. After a few moments the Device Provisioning Service instance is created and the **Overview** tab is displayed.
-6. On the **Overview** tab for the new service instance, copy the value for the **ID scope** for use later. That value is used to identify registration IDs, and provides a guarantee that the registration ID is unique.
-7. Also copy the **Service endpoint** value for later use. 
+5. Click **Create**. After a few moments, the Device Provisioning Service instance is created and the **Overview** page is displayed.
+6. On the **Overview** page for the new service instance, copy the value for the **ID scope** for use later. That value is used to identify registration IDs, and provides a guarantee that the registration ID is unique.
+7. Also, copy the **Service endpoint** value for later use. 
 
 [!INCLUDE [iot-hub-get-started-create-hub](../../includes/iot-hub-get-started-create-hub.md)]
 
@@ -60,11 +60,11 @@ The next step is to link the Device Provisioning Service and IoT hub so that the
 1. In the **All resources** page, click the Device Provisioning Service instance you created previously.
 2. In the Device Provisioning Service page, click **Linked IoT hubs**.
 3. Click **Add**.
-4. In the **Add link to IoT hub** page, provide the following information and click **Save**:
+4. In the **Add link to IoT hub** page, provide the following information, and click **Save**:
 
-    * **Subscription** : Make sure the subscription that contains the IoT hub is selected. You can link to IoT hub that resides in a different subscription.
-    * **IoT hub** : Choose the name of the IoT hub that you want to link with this Device Provisioning Service instance.
-    * **Access Policy** : Select **iothubowner** to use those credientals for the IoT hub.
+    * **Subscription:** Make sure the subscription that contains the IoT hub is selected. You can link to IoT hub that resides in a different subscription.
+    * **IoT hub:** Choose the name of the IoT hub that you want to link with this Device Provisioning Service instance.
+    * **Access Policy:** Select **iothubowner** as the credentials to use for establishing the link to the IoT hub.
 
    ![Link the hub name to link to the DPS in the portal](./media/tutorial-set-up-cloud/link-iot-hub-to-dps-portal.png)
 
@@ -73,7 +73,7 @@ The next step is to link the Device Provisioning Service and IoT hub so that the
 The allocation policy is a IoT Hub Device Provisioning Service setting that determines how devices are assigned to an IoT hub. There are three supported allocation policies: 
 
 1. **Lowest latency**: Devices are provisioned to an IoT hub based on the hub with the lowest latency to the device.
-2. **Evenly weighted distribution** (default): Linked IoT hubs are equally likely to have devices provisioned to them. This is the default setting. If you are provisioning devices to only one IoT hub, you can keep this setting. 
+2. **Evenly weighted distribution** (default): Linked IoT hubs are equally likely to have devices provisioned to them. This setting is the default. If you are provisioning devices to only one IoT hub, you can keep this setting. 
 3. **Static configuration via the enrollment list**: Specification of the desired IoT hub in the enrollment list takes priority over the Device Provisioning Service-level allocation policy.
 
 To set the allocation policy, in the Device Provisioning Service page click **Manage allocation policy**. Make sure the allocation policy is set to **Evenly weighted distribution** (the default). If you make any changes, click **Save** when you are done.
diff --git a/articles/iot-dps/tutorial-set-up-device.md b/articles/iot-dps/tutorial-set-up-device.md
@@ -20,7 +20,7 @@ In the previous tutorial, you learned how to set up the Azure IoT Hub Device Pro
 > * Extract the security artifacts
 > * Create the device registration software
 
-This tutorial expect that you have already created your Device Provisioning Service instance and an IoT hub, using the instructions in the previous [1 - Set up cloud resources](./tutorial-set-up-cloud.md) tutorial.
+This tutorial expects that you have already created your Device Provisioning Service instance and an IoT hub, using the instructions in the previous [Set up cloud resources](tutorial-set-up-cloud.md) tutorial.
 
 This tutorial uses the [Azure IoT SDKs and libraries for C repository](https://github.com/Azure/azure-iot-sdk-c), which contains the Device Provisioning Service Client SDK for C. The SDK currently provides TPM and X.509 support for devices running on Windows or Ubuntu implementations. This tutorial is based on use of a Windows development client, which also assumes basic proficiency with Visual Studio 2017. 
 
@@ -80,7 +80,8 @@ The Device Provisioning Service Client SDK helps you implement your device regis
         cmake -Duse_prov_client:BOOL=ON ..
         ```
 
-    Now you're ready to use the SDK to build your device registration code. 
+
+Now you're ready to use the SDK to build your device registration code. 
  
 <a id="extractsecurity"></a> 
 
@@ -90,18 +91,18 @@ The next step is to extract the security artifacts for the attestation mechanism
 
 ### Physical devices 
 
-Depending on whether you built the SDK to use attestation from a physical TPM/HSM or using X.509 certificates, gathering the security artifacts differ as follows:
+Depending on whether you built the SDK to use attestation for a physical TPM/HSM or using X.509 certificates, gathering the security artifacts is as follows:
 
 - For a TPM device, you need to determine the **Endorsement Key** associated with it from the TPM chip manufacturer. You can derive a unique **Registration ID** for your TPM device by hashing the endorsement key.  
 
-- For an X.509 device, you need to obtain the certificates issued to your device(s). The provisioning service exposes two types enrollment entries that control access for devices using the X.509 attestation mechanism. The certificates needed depend on the enrollment types you will be using.
+- For an X.509 device, you need to obtain the certificates issued to your device(s). The provisioning service exposes two types of enrollment entries that control access for devices using the X.509 attestation mechanism. The certificates needed depend on the enrollment types you will be using.
 
-    1. Individual enrollments : Enrollment for a specific single device. This type of enrollment entry requires [end-entity, "leaf", certificates](concepts-security.md#end-entity-leaf-certificate).
-    2. Enrollment groups : This type of enrollment entry requires intermediate or root certificates. For more information, see [Controlling device access to the provisioning service with X.509 certificates](concepts-security.md#controlling-device-access-to-the-provisioning-service-with-x509-certificates).
+    1. Individual enrollments: Enrollment for a specific single device. This type of enrollment entry requires [end-entity, "leaf", certificates](concepts-security.md#end-entity-leaf-certificate).
+    2. Enrollment groups: This type of enrollment entry requires intermediate or root certificates. For more information, see [Controlling device access to the provisioning service with X.509 certificates](concepts-security.md#controlling-device-access-to-the-provisioning-service-with-x509-certificates).
 
 ### Simulated devices
 
-Depending on whether you built the SDK to use attestation from a simulated device using TPM or X.509 certificates, gathering the security artifacts differ as follows:
+Depending on whether you built the SDK to use attestation for a simulated device using TPM or X.509 certificates, gathering the security artifacts is as follows:
 
 - For a simulated TPM device:
 
@@ -120,15 +121,15 @@ Depending on whether you built the SDK to use attestation from a simulated devic
 
    3. In the *Solution Explorer* pane in Visual Studio, navigate to the folder **Provision\_Tools**. Right-click the **tpm_device_provision** project and select **Set as Startup Project**. 
 
-   4. Run the solution using either of the "Start" commands on the "Debug" menu. The output window displays the TPM simulator's **_Registration ID_** and the **_Endorsement Key_**, needed for device enrollment and registration. Copy these values for use later. You can close this window (with Registration Id and Endorsement Key), but leave the TPM simulator window running that you started in step #1.
+   4. Run the solution using either of the "Start" commands on the "Debug" menu. The output window displays the TPM simulator's **_Registration ID_** and the **_Endorsement Key_**, needed for device enrollment and registration. Copy these values for use later. You can close this window (with Registration ID and Endorsement Key), but leave the TPM simulator window running that you started in step #1.
 
 - For a simulated X.509 device:
 
   1. Using Visual Studio, open the solution generated in the *cmake* folder named `azure_iot_sdks.sln`, and build it using the "Build solution" command on the "Build" menu.
 
   2. In the *Solution Explorer* pane in Visual Studio, navigate to the folder **Provision\_Tools**. Right-click the **dice\_device\_enrollment** project and select **Set as Startup Project**. 
   
-  3. Run the solution using either of the "Start" commands on the "Debug" menu. In the output window, enter **i** for individual enrollment when prompted. The output window displays a locally generated X.509 certificate for your simulated device. Copy to clipboard the output starting from *-----BEGIN CERTIFICATE-----* and ending at the first *-----END CERTIFICATE-----*, making sure to include both of these lines as well. Note that you need only the first certificate from the output window.
+  3. Run the solution using either of the "Start" commands on the "Debug" menu. In the output window, enter **i** for individual enrollment when prompted. The output window displays a locally generated X.509 certificate for your simulated device. Copy to clipboard the output starting from *-----BEGIN CERTIFICATE-----* and ending at the first *-----END CERTIFICATE-----*, making sure to include both of these lines as well. You only need the first certificate from the output window.
  
   4. Create a file named **_X509testcert.pem_**, open it in a text editor of your choice, and copy the clipboard contents to this file. Save the file as you will use it later for device enrollment. When your registration software runs, it uses the same certificate during auto-provisioning.    
 
