Grammar updates (increased Acrolinx score from 78 to 100).

Author: stevemunk

articles/azure-maps/how-to-secure-device-code.md

@@ -1,7 +1,7 @@
 ---
 title: How to secure an input constrained device using  Azure AD and Azure Maps REST API
 titleSuffix: Azure Maps
-description: How to configure a browser-less application which supports sign-in to Azure AD and calls Azure Maps REST API.
+description: How to configure a browser-less application that supports sign-in to Azure AD and calls Azure Maps REST API.
 author: eriklindeman
 ms.author: eriklind
 ms.date: 06/12/2020
@@ -12,7 +12,7 @@ services: azure-maps
 
 # Secure an input constrained device using Azure active directory (Azure AD) and Azure Maps REST APIs
 
-This guide discusses how to secure public applications or devices that cannot securely store secrets or accept browser input. These types of applications fall under the internet of things (IoT) category. Examples include Smart TVs and sensor data emitting applications.
+This guide discusses how to secure public applications or devices that can't securely store secrets or accept browser input. These types of applications fall under the internet of things (IoT) category. Examples include Smart TVs and sensor data emitting applications.
 
 [!INCLUDE [authentication details](./includes/view-authentication-details.md)]
 
@@ -23,31 +23,31 @@ This guide discusses how to secure public applications or devices that cannot se
 > * **Prerequisite Reading:** [Scenario: Desktop app that calls web APIs]
 > * The following scenario uses the device code flow, which does not involve a web browser to acquire a token.
 
-Create the device based application in Azure AD to enable Azure AD sign in. This application will be granted access to Azure Maps REST APIs.
+Create the device based application in Azure AD to enable Azure AD sign in, which is granted access to Azure Maps REST APIs.
 
 1. In the Azure portal, in the list of Azure services, select **Azure Active Directory** > **App registrations** > **New registration**.  
 
     :::image type="content" source="./media/how-to-manage-authentication/app-registration.png" alt-text="A screenshot showing application registration in Azure AD":::
 
-2. Enter a **Name**, choose **Accounts in this organizational directory only** as the **Supported account type**. In **Redirect URIs**, specify **Public client / native (mobile & desktop)** then add `https://login.microsoftonline.com/common/oauth2/nativeclient` to the value. For more details please see Azure AD [Desktop app that calls web APIs: App registration]. Then **Register** the application.
+2. Enter a **Name**, choose **Accounts in this organizational directory only** as the **Supported account type**. In **Redirect URIs**, specify **Public client / native (mobile & desktop)** then add `https://login.microsoftonline.com/common/oauth2/nativeclient` to the value. For more information, see Azure AD [Desktop app that calls web APIs: App registration]. Then **Register** the application.
 
-    :::image type="content" source="./media/how-to-manage-authentication/devicecode-app-registration.png" alt-text="A screenshot showing the register an application settings.":::
+    :::image type="content" source="./media/how-to-manage-authentication/devicecode-app-registration.png" alt-text="A screenshot showing the settings used to register an application.":::
 
-3. Navigate to **Authentication** and enable **Treat application as a public client**. This will enable device code authentication with Azure AD.
+3. Navigate to **Authentication** and enable **Treat application as a public client** to enable device code authentication with Azure AD.
 
-    :::image type="content" source="./media/azure-maps-authentication/devicecode-public-client.png" alt-text="A screen shot showing the advanced settings used to specify treating the application as a public client.":::
+    :::image type="content" source="./media/azure-maps-authentication/devicecode-public-client.png" alt-text="A screenshot showing the advanced settings used to specify treating the application as a public client.":::
 
 4. To assign delegated API permissions to Azure Maps, go to the application. Then select **API permissions** > **Add a permission**. Under **APIs my organization uses**, search for and select **Azure Maps**.
 
-    :::image type="content" source="./media/how-to-manage-authentication/app-permissions.png" alt-text="A screen shot showing where you request API permissions.":::
+    :::image type="content" source="./media/how-to-manage-authentication/app-permissions.png" alt-text="A screenshot showing where you request API permissions.":::
 
 5. Select the check box next to **Access Azure Maps**, and then select **Add permissions**.
 
-    :::image type="content" source="./media/how-to-manage-authentication/select-app-permissions.png" alt-text="A screen shot showing where you specify the app permissions you require.":::
+    :::image type="content" source="./media/how-to-manage-authentication/select-app-permissions.png" alt-text="A screenshot showing where you specify the app permissions you require.":::
 
-6. Configure Azure role-based access control (Azure RBAC) for users or groups. See [Grant role-based access for users to Azure Maps].
+6. Configure Azure role-based access control (Azure RBAC) for users or groups. For more information, see [Grant role-based access for users to Azure Maps].
 
-7. Add code for acquiring token flow in the application, for implementation details see [Device code flow]. When acquiring tokens, reference the scope: `user_impersonation` which was selected on earlier steps.
+7. Add code for acquiring token flow in the application, for implementation details see [Device code flow]. When acquiring tokens, reference the scope: `user_impersonation` that was selected on earlier steps.
 
     > [!Tip]
     > Use Microsoft Authentication Library (MSAL) to acquire access tokens.
@@ -101,9 +101,9 @@ Find the API usage metrics for your Azure Maps account:
 > [!div class="nextstepaction"]
 > [View usage metrics]
 
-[Scenario: Desktop app that calls web APIs]: ../active-directory/develop/scenario-desktop-overview.md
 [Desktop app that calls web APIs: App registration]: ../active-directory/develop/scenario-desktop-app-registration.md
-[Grant role-based access for users to Azure Maps]: #grant-role-based-access-for-users-to-azure-maps
-[Device code flow]: ../active-directory/develop/scenario-desktop-acquire-token-device-code-flow.md
 [Desktop app that calls web APIs: Code configuration]: ../active-directory/develop/scenario-desktop-app-configuration.md
+[Device code flow]: ../active-directory/develop/scenario-desktop-acquire-token-device-code-flow.md
+[Grant role-based access for users to Azure Maps]: #grant-role-based-access-for-users-to-azure-maps
+[Scenario: Desktop app that calls web APIs]: ../active-directory/develop/scenario-desktop-overview.md
 [View usage metrics]: how-to-view-api-usage.md