Changes based on Content standards report

Author: v-lakast

articles/iot-dps/about-iot-dps.md

@@ -11,7 +11,7 @@ manager: eliotgra
 ms.custom:  [amqp, mqtt]
 ---
 
-# Provisioning devices with Azure IoT Hub Device Provisioning Service
+# What is Azure IoT Hub Device Provisioning Service?
 Microsoft Azure provides a rich set of integrated public cloud services for all your IoT solution needs. The IoT Hub Device Provisioning Service (DPS) is a helper service for IoT Hub that enables zero-touch, just-in-time provisioning to the right IoT hub without requiring human intervention. DPS enables the provisioning of millions of devices in a secure and scalable manner.
 
 ## When to use Device Provisioning Service

articles/iot-dps/how-to-legacy-device-symm-key.md

@@ -25,26 +25,26 @@ This article is oriented toward a Windows-based workstation. However, you can pe
 > [!NOTE]
 > The sample used in this article is written in C. There is also a [C# device provisioning symmetric key sample](https://github.com/Azure-Samples/azure-iot-samples-csharp/tree/master/provisioning/Samples/device/SymmetricKeySample) available. To use this sample, download or clone the [azure-iot-samples-csharp](https://github.com/Azure-Samples/azure-iot-samples-csharp) repository and follow the in-line instructions in the sample code. You can follow the instructions in this article to create a symmetric key enrollment group using the portal and to find the ID Scope and enrollment group primary and secondary keys needed to run the sample. You can also create individual enrollments using the sample.
 
-## Overview
+## Prerequisites
 
-A unique registration ID will be defined for each device based on information that identifies that device. For example, the MAC address or a serial number.
+* Completion of the [Set up IoT Hub Device Provisioning Service with the Azure portal](./quick-setup-auto-provision.md) quickstart.
 
-An enrollment group that uses [symmetric key attestation](concepts-symmetric-key-attestation.md) will be created with the Device Provisioning Service. The enrollment group will include a group master key. That master key will be used to hash each unique registration ID to produce a unique device key for each device. The device will use that derived device key with its unique registration ID to attest with the Device Provisioning Service and be assigned to an IoT hub.
+The following prerequisites are for a Windows development environment. For Linux or macOS, see the appropriate section in [Prepare your development environment](https://github.com/Azure/azure-iot-sdk-c/blob/master/doc/devbox_setup.md) in the SDK documentation.
 
-The device code demonstrated in this article will follow the same pattern as the [Quickstart: Provision a simulated device with symmetric keys](quick-create-simulated-device-symm-key.md). The code will simulate a device using a sample from the [Azure IoT C SDK](https://github.com/Azure/azure-iot-sdk-c). The simulated device will attest with an enrollment group instead of an individual enrollment as demonstrated in the quickstart.
+* [Visual Studio](https://visualstudio.microsoft.com/vs/) 2019 with the ['Desktop development with C++'](/cpp/ide/using-the-visual-studio-ide-for-cpp-desktop-development) workload enabled. Visual Studio 2015 and Visual Studio 2017 are also supported.
 
-[!INCLUDE [quickstarts-free-trial-note](../../includes/quickstarts-free-trial-note.md)]
+* Latest version of [Git](https://git-scm.com/download/) installed.
 
+## Overview
 
-## Prerequisites
+A unique registration ID will be defined for each device based on information that identifies that device. For example, the MAC address or a serial number.
 
-* Completion of the [Set up IoT Hub Device Provisioning Service with the Azure portal](./quick-setup-auto-provision.md) quickstart.
+An enrollment group that uses [symmetric key attestation](concepts-symmetric-key-attestation.md) will be created with the Device Provisioning Service. The enrollment group will include a group master key. That master key will be used to hash each unique registration ID to produce a unique device key for each device. The device will use that derived device key with its unique registration ID to attest with the Device Provisioning Service and be assigned to an IoT hub.
 
-The following prerequisites are for a Windows development environment. For Linux or macOS, see the appropriate section in [Prepare your development environment](https://github.com/Azure/azure-iot-sdk-c/blob/master/doc/devbox_setup.md) in the SDK documentation.
+The device code demonstrated in this article will follow the same pattern as the [Quickstart: Provision a simulated device with symmetric keys](quick-create-simulated-device-symm-key.md). The code will simulate a device using a sample from the [Azure IoT C SDK](https://github.com/Azure/azure-iot-sdk-c). The simulated device will attest with an enrollment group instead of an individual enrollment as demonstrated in the quickstart.
 
-* [Visual Studio](https://visualstudio.microsoft.com/vs/) 2019 with the ['Desktop development with C++'](/cpp/ide/using-the-visual-studio-ide-for-cpp-desktop-development) workload enabled. Visual Studio 2015 and Visual Studio 2017 are also supported.
+[!INCLUDE [quickstarts-free-trial-note](../../includes/quickstarts-free-trial-note.md)]
 
-* Latest version of [Git](https://git-scm.com/download/) installed.
 
 ## Prepare an Azure IoT C SDK development environment
 
@@ -280,6 +280,15 @@ Be aware that this leaves the derived device key included as part of the image f
 
 ## Next steps
 
-* To learn more Reprovisioning, see [IoT Hub Device reprovisioning concepts](concepts-device-reprovision.md) 
-* [Quickstart: Provision a simulated device with symmetric keys](quick-create-simulated-device-symm-key.md)
-* To learn more Deprovisioning, see [How to deprovision devices that were previously auto-provisioned](how-to-unprovision-devices.md)
+* To learn more about Reprovisioning, see
+
+> [!div class="nextstepaction"]
+> [IoT Hub Device reprovisioning concepts](concepts-device-reprovision.md)
+
+> [!div class="nextstepaction"]
+> [Quickstart: Provision a simulated device with symmetric keys](quick-create-simulated-device-symm-key.md)
+
+* To learn more about Deprovisioning, see
+
+> [!div class="nextstepaction"]
+> [How to deprovision devices that were previously auto-provisioned](how-to-unprovision-devices.md)

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

@@ -22,11 +22,12 @@ It is common to combine these two scenarios. For example, a multitenant IoT solu
 
 This article uses a simulated device sample from the [Azure IoT C SDK](https://github.com/Azure/azure-iot-sdk-c) to demonstrate how to provision devices in a multitenant scenario across regions. You will perform the following steps in this article:
 
-* Use the Azure CLI to create two regional IoT hubs (**West US** and **East US**)
-* Create a multitenant enrollment
-* Use the Azure CLI to create two regional Linux VMs to act as devices in the same regions (**West US** and **East US**)
-* Set up the development environment for the Azure IoT C SDK on both Linux VMs
-* Simulate the devices to see that they are provisioned for the same tenant in the closest region.
+> [!div class="checklist"]
+> * Use the Azure CLI to create two regional IoT hubs (**West US** and **East US**)
+> * Create a multitenant enrollment
+> * Use the Azure CLI to create two regional Linux VMs to act as devices in the same regions (**West US** and **East US**)
+> * Set up the development environment for the Azure IoT C SDK on both Linux VMs
+> * Simulate the devices to see that they are provisioned for the same tenant in the closest region.
 
 
 [!INCLUDE [quickstarts-free-trial-note](../../includes/quickstarts-free-trial-note.md)]
@@ -413,8 +414,11 @@ To delete the resource group by name:
 
 ## Next steps
 
+* To learn more about reprovisioning, see
+
 > [!div class="nextstepaction"]
-> To learn more about reprovisioning, see [IoT Hub Device reprovisioning concepts](concepts-device-reprovision.md)
+> [IoT Hub Device reprovisioning concepts](concepts-device-reprovision.md)
 
+* To learn more about deprovisioning, see
 > [!div class="nextstepaction"]
-> To learn more about deprovisioning, see [How to deprovision devices that were previously auto-provisioned](how-to-unprovision-devices.md)
+> [How to deprovision devices that were previously auto-provisioned](how-to-unprovision-devices.md)

articles/iot-dps/tutorial-custom-allocation-policies.md

@@ -479,6 +479,17 @@ To delete the resource group by name:
 
 ## Next steps
 
-* For a more in-depth custom allocation policy example, see [How to use custom allocation policies](how-to-use-custom-allocation-policies.md).
-* To learn more Reprovisioning, see [IoT Hub Device reprovisioning concepts](concepts-device-reprovision.md).
-* To learn more Deprovisioning, see [How to deprovision devices that were previously autoprovisioned](how-to-unprovision-devices.md).
+For a more in-depth custom allocation policy example, see 
+
+> [!div class="nextstepaction"]
+> [How to use custom allocation policies](how-to-use-custom-allocation-policies.md)
+
+* To learn more Reprovisioning, see
+
+> [!div class="nextstepaction"]
+> [IoT Hub Device reprovisioning concepts](concepts-device-reprovision.md)
+
+* To learn more Deprovisioning, see
+
+> [!div class="nextstepaction"]
+> [How to deprovision devices that were previously autoprovisioned](how-to-unprovision-devices.md)

articles/iot-dps/tutorial-provision-device-to-hub.md

@@ -95,7 +95,7 @@ In this tutorial, you learned how to:
 > * Start the device
 > * Verify the device is registered
 
-Advance to the next tutorial to learn how to provision multiple devices across load-balanced hubs. 
+Advance to the next tutorial to learn how to provision multiple devices across load-balanced hubs
 
 > [!div class="nextstepaction"]
 > [Provision devices across load-balanced IoT hubs](./tutorial-provision-multiple-hubs.md)

articles/iot-dps/tutorial-set-up-cloud.md

@@ -115,7 +115,7 @@ In this tutorial, you learned how to:
 > * Link the IoT hub to the Device Provisioning Service
 > * Set the allocation policy on the Device Provisioning Service
 
-Advance to the next tutorial to learn how to set up your device for provisioning.
+Advance to the next tutorial to learn how to set up your device for provisioning
 
 > [!div class="nextstepaction"]
 > [Set up device for provisioning](tutorial-set-up-device.md)