some fixes

Author: JimacoMS3

articles/iot-dps/how-to-use-custom-allocation-policies.md

@@ -97,7 +97,7 @@ In this section, you create an Azure function that implements your custom alloca
 
 2. In the *Search the Marketplace* search box, type "Function App". From the drop-down list select **Function App**, and then select **Create**.
 
-3. On **Function App** create page, under the **Basics** tab, enter the following settings for your new function app and click **Review + create**:
+3. On **Function App** create page, under the **Basics** tab, enter the following settings for your new function app and select **Review + create**:
 
     **Resource Group**: Select the **contoso-us-resource-group** to keep all resources created in this article together.
 
@@ -110,7 +110,7 @@ In this section, you create an Azure function that implements your custom alloca
     **Region**: Select the same region as your resource group. This example uses **West US**.
 
     > [!NOTE]
-    > By default, **Application Insights** is enabled. Application Insights is not necessary for this article, but it might help you understand If you want to, you can disable it by selecting the **Monitoring** tab and selecting **No** for **Enable Application Insights**.
+    > By default, Application Insights is enabled. Application Insights is not necessary for this article, but it might help you understand and investigate any issues you encounter with the custom allocation. If you prefer, you can disable Application Insights by selecting the **Monitoring** tab and then selecting **No** for **Enable Application Insights**.
 
     ![Create an Azure Function App to host the custom allocation function](./media/how-to-use-custom-allocation-policies/create-function-app.png)
 
@@ -235,7 +235,7 @@ In this section, you create an Azure function that implements your custom alloca
                 // This is a Contoso Heat pump Model 008
                 else if (regId.Contains("-contoso-hpsd-088"))
                 {
-                    //Find the "-heatpumps-" IoT hub configured on the enrollment 
+                    //Find the "-heatpumps-" IoT hub configured on the enrollment
                     foreach(string hubString in hubs)
                     {
                         if (hubString.Contains("-heatpumps-"))
@@ -295,9 +295,9 @@ In this section, you'll create a new enrollment group that uses the custom alloc
 
 1. Still on the [Azure portal](https://portal.azure.com), open your provisioning service.
 
-2. Select **Manage enrollments** on the left pane, and then click the **Add enrollment group** button at the top of the page.
+2. Select **Manage enrollments** on the left pane, and then select the **Add enrollment group** button at the top of the page.
 
-3. On **Add Enrollment Group**, enter the following information, and click the **Save** button.
+3. On **Add Enrollment Group**, enter the following information, and select the **Save** button.
 
     **Group name**: Enter **contoso-custom-allocated-devices**.
 
@@ -309,7 +309,7 @@ In this section, you'll create a new enrollment group that uses the custom alloc
 
     ![Add custom allocation enrollment group for symmetric key attestation](./media/how-to-use-custom-allocation-policies/create-custom-allocation-enrollment.png)
 
-4. On **Add Enrollment Group**, click **Link a new IoT hub** to link both of your new divisional IoT hubs.
+4. On **Add Enrollment Group**, select **Link a new IoT hub** to link both of your new divisional IoT hubs.
 
     Execute this step for both of your divisional IoT hubs.
 
@@ -458,7 +458,7 @@ This sample code simulates a device boot sequence that sends the provisioning re
 2. In Visual Studio, open the **azure_iot_sdks.sln** solution file that was generated by running CMake earlier. The solution file should be in the following location:
 
     ```
-    \azure-iot-sdk-c\cmake\azure_iot_sdks.sln
+    azure-iot-sdk-c\cmake\azure_iot_sdks.sln
     ```
 
 3. In Visual Studio's *Solution Explorer* window, navigate to the **Provision\_Samples** folder. Expand the sample project named **prov\_dev\_client\_sample**. Expand **Source Files**, and open **prov\_dev\_client\_sample.c**.
@@ -478,7 +478,7 @@ This sample code simulates a device boot sequence that sends the provisioning re
     hsm_type = SECURE_DEVICE_TYPE_SYMMETRIC_KEY;
     ```
 
-6. Right-click the **prov\_dev\_client\_sample** project and select **Set as Startup Project**. 
+6. Right-click the **prov\_dev\_client\_sample** project and select **Set as Startup Project**.
 
 ### Simulate the Contoso toaster device
 
@@ -498,7 +498,7 @@ This sample code simulates a device boot sequence that sends the provisioning re
 
     Save the file.
 
-2. On the Visual Studio menu, select **Debug** > **Start without debugging** to run the solution. In the prompt to rebuild the project, click **Yes**, to rebuild the project before running.
+2. On the Visual Studio menu, select **Debug** > **Start without debugging** to run the solution. In the prompt to rebuild the project, select **Yes**, to rebuild the project before running.
 
     The following output is an example of the simulated toaster device successfully booting up and connecting to the provisioning service instance to be assigned to the toasters IoT hub by the custom allocation policy:
 
@@ -527,7 +527,7 @@ This sample code simulates a device boot sequence that sends the provisioning re
 
     Save the file.
 
-2. On the Visual Studio menu, select **Debug** > **Start without debugging** to run the solution. In the prompt to rebuild the project, click **Yes** to rebuild the project before running.
+2. On the Visual Studio menu, select **Debug** > **Start without debugging** to run the solution. In the prompt to rebuild the project, select **Yes** to rebuild the project before running.
 
     The following output is an example of the simulated heat pump device successfully booting up and connecting to the provisioning service instance to be assigned to the Contoso heat pumps IoT hub by the custom allocation policy:
 
@@ -570,13 +570,13 @@ The steps here assume you created all resources in this article as instructed in
 
 To delete the resource group by name:
 
-1. Sign in to the [Azure portal](https://portal.azure.com) and click **Resource groups**.
+1. Sign in to the [Azure portal](https://portal.azure.com) and select **Resource groups**.
 
 2. In the **Filter by name...** textbox, type the name of the resource group containing your resources, **contoso-us-resource-group**. 
 
-3. To the right of your resource group in the result list, click **...** then **Delete resource group**.
+3. To the right of your resource group in the result list, select **...** then **Delete resource group**.
 
-4. You'll be asked to confirm the deletion of the resource group. Type the name of your resource group again to confirm, and then click **Delete**. After a few moments, the resource group and all of its contained resources are deleted.
+4. You'll be asked to confirm the deletion of the resource group. Type the name of your resource group again to confirm, and then select **Delete**. After a few moments, the resource group and all of its contained resources are deleted.
 
 ## Next steps