Merge pull request #177611 from alexbuckgit/alexbuckgit/docutune-autopr-20211026-153714-6894254

DocuTune: Initial cleanup of (a, an, the) terms

Author: denrea

articles/active-directory/app-provisioning/on-premises-application-provisioning-architecture.md

@@ -57,11 +57,11 @@ The following information is provided to better explain the anchor attributes an
 
 The anchor attribute is a unique attribute of an object type that does not change and represents that object in the ECMA Connector Host in-memory cache.
 
-The distinguished name (DN) is a name that uniquely identifies an object by indicating its current location in the directory hierarchy.  Or in the case of SQL, in the partition. The name is formed by concatenating the anchor attribute a the root of the directory partition. 
+The distinguished name (DN) is a name that uniquely identifies an object by indicating its current location in the directory hierarchy.  Or in the case of SQL, in the partition. The name is formed by concatenating the anchor attribute at the root of the directory partition. 
 
 When we think of traditional DNs in a traditional format, for say, Active Directory or LDAP, we think of something similar to:
 
-  CN=Lola Jacobson,CN=Users,DC=contoso,DC=com
+  `CN=Lola Jacobson,CN=Users,DC=contoso,DC=com`
 
 However, for a data source such as SQL, which is flat, not hierarchical, the DN needs to be either already present in one of the table or created from the information we provide to the ECMA Connector Host.  
 

articles/active-directory/app-provisioning/plan-auto-user-provisioning.md

@@ -94,7 +94,7 @@ In this example, users and or groups are created in an HR database connected to
 
 In this example, user creation occurs in Azure AD and the  Azure AD provisioning service manages automatic user provisioning to the target (SaaS) applications.
 
-![Diagram that shows the user/group creation process from an on-premises H R application through the Azure A D Provisioning Service to the target S a a S applications.](./media/plan-auto-user-provisioning/cloudprovisioning.png)
+![Diagram that shows the user/group creation process from an on-premises H R application through the Azure A D Provisioning Service to the target S A A S applications.](./media/plan-auto-user-provisioning/cloudprovisioning.png)
 
 **Description of workflow:**
 

articles/active-directory/conditional-access/concept-conditional-access-grant.md

@@ -157,7 +157,7 @@ The following client apps have been confirmed to support this setting:
 - Nine Mail - Email & Calendar
 
 > [!NOTE]
-> Microsoft Kaizala, Microsoft Skype for Business and Microsoft Visio do not support the **Require app protection policy** grant. If you require these apps to work, please use the **Require approved apps** grant exclusively. The use of the or clause between the two grants will not work for these three applications.
+> Microsoft Kaizala, Microsoft Skype for Business and Microsoft Visio do not support the **Require app protection policy** grant. If you require these apps to work, please use the **Require approved apps** grant exclusively. The use of the `or` clause between the two grants will not work for these three applications.
 
 **Remarks**
 

articles/active-directory/develop/msal-net-migration-public-client.md

@@ -221,7 +221,7 @@ result = await context.AcquireTokenAsync(resource, clientId,
       // AcquireTokenByIntegratedWindowsAuth form that takes in the username
 
       // Error Code: integrated_windows_auth_not_supported_managed_user
-      // Explanation: This method relies on an a protocol exposed by Active Directory (AD). If a user was created in Azure
+      // Explanation: This method relies on a protocol exposed by Active Directory (AD). If a user was created in Azure
       // Active Directory without AD backing ("managed" user), this method will fail. Users created in AD and backed by
       // AAD ("federated" users) can benefit from this non-interactive method of authentication.
       // Mitigation: Use interactive authentication

articles/active-directory/develop/scenario-desktop-acquire-token-integrated-windows-authentication.md

@@ -124,7 +124,7 @@ static async Task GetATokenForGraph()
       // AcquireTokenByIntegratedWindowsAuth form that takes in the username
 
       // Error Code: integrated_windows_auth_not_supported_managed_user
-      // Explanation: This method relies on an a protocol exposed by Active Directory (AD). If a user was created in Azure
+      // Explanation: This method relies on a protocol exposed by Active Directory (AD). If a user was created in Azure
       // Active Directory without AD backing ("managed" user), this method will fail. Users created in AD and backed by
       // AAD ("federated" users) can benefit from this non-interactive method of authentication.
       // Mitigation: Use interactive authentication

articles/app-service/troubleshoot-dotnet-visual-studio.md

@@ -73,9 +73,9 @@ You typically deploy a web project with the `customErrors` flag in the Web.confi
 
 **The website cannot display the page**
 
-:::image type="content" source="./media/web-sites-dotnet-troubleshoot-visual-studio/genericerror2.png" alt-text="Screenshot showing a The website cannot display the page error in a web browser.":::
+:::image type="content" source="./media/web-sites-dotnet-troubleshoot-visual-studio/genericerror2.png" alt-text="Screenshot showing a message that reads **The website cannot display the page error in a web browser**.":::
 
-Frequently the easiest way to find the cause of the error is to enable detailed error messages, which the first of the preceding screenshots explains how to do. That requires a change in the deployed Web.config file. You could edit the *Web.config* file in the project and redeploy the project, or create a [Web.config transform](https://www.asp.net/mvc/tutorials/deployment/visual-studio-web-deployment/web-config-transformations) and deploy a debug build, but there's a quicker way: in **Solution Explorer**, you can directly view and edit files in the remote app by using the *remote view* feature.
+Frequently the easiest way to find the cause of the error is to enable detailed error messages, which the first of the preceding screenshots explains how to do. That requires a change in the deployed Web.config file. You could edit the *Web.config* file in the project and redeploy the project, or create a [`Web.config` transform](https://www.asp.net/mvc/tutorials/deployment/visual-studio-web-deployment/web-config-transformations) and deploy a debug build, but there's a quicker way: in **Solution Explorer**, you can directly view and edit files in the remote app by using the *remote view* feature.
 
 1. In **Server Explorer**, expand **Azure**, expand **App Service**, expand the resource group that your app is located in, and then expand the node for your app.
 

articles/automation/automation-webhooks.md

@@ -134,7 +134,7 @@ Then save and publish the revised runbook. The examples below show to create a w
 
 1. Enter in the **Name** for the webhook. The expiration date for the field **Expires** defaults to one year from the current date.
 
-1. Click the copy icon or press <kbd>Ctrl+C to</kbd> copy the URL of the webhook. Then save the URL to a secure location.
+1. Click the copy icon or press <kbd>Ctrl + C</kbd> copy the URL of the webhook. Then save the URL to a secure location.
 
     :::image type="content" source="media/automation-webhooks/create-new-webhook.png" alt-text="Creaye webhook page with URL highlighted.":::
 

articles/azure-app-configuration/enable-dynamic-configuration-java-spring-push-refresh.md

@@ -34,7 +34,7 @@ In this tutorial, you learn how to:
 
 > [!div class="checklist"]
 > * Set up a subscription to send configuration change events from App Configuration to a Web Hook
-> * Deploy an a Spring Boot application to App Service
+> * Deploy a Spring Boot application to App Service
 > * Set up your Java Spring app to update its configuration in response to changes in App Configuration.
 > * Consume the latest configuration in your application.
 

articles/azure-monitor/logs/create-pipeline-datacollector-api.md

@@ -32,7 +32,7 @@ This article will not cover how to create data or [upload it to an Azure Blob St
 
 1. A process will detect that new data has been uploaded.  Our example uses an [Azure Logic App](../../logic-apps/logic-apps-overview.md), which has available a trigger to detect new data being uploaded to a blob.
 
-2. A processor reads this new data and converts it to JSON, the format required by Azure Monitor  In this example, we use an [Azure Function](../../azure-functions/functions-overview.md) as a lightweight, cost-efficient way of executing our processing code. The function is kicked off by the same Logic App that we used to detect a the new data.
+2. A processor reads this new data and converts it to JSON, the format required by Azure Monitor  In this example, we use an [Azure Function](../../azure-functions/functions-overview.md) as a lightweight, cost-efficient way of executing our processing code. The function is kicked off by the same Logic App that we used to detect the new data.
 
 3. Finally, once the JSON object is available, it is sent to Azure Monitor. The same Logic App sends the data to Azure Monitor using the built in Log Analytics Data Collector activity.
 

articles/azure-monitor/visualize/workbooks-bring-your-own-storage.md

@@ -23,11 +23,11 @@ There are times when you may have a query or some business logic that you want t
 3. Select the **Save** button to save the workbook.
 4. There's an option to `Save content to an Azure Storage Account`, select the checkbox to save to an Azure Storage Account.
 
-    ![Screenshot showing a the saved dialog](./media/workbooks-bring-your-own-storage/saved-dialog-default.png)
+    ![Screenshot showing the **Save** dialog.](./media/workbooks-bring-your-own-storage/saved-dialog-default.png)
 
 5. Select the desire Storage account and Container. The Storage account list is from the Subscription selected above.
 
-    ![Screenshot showing a save dialog with storage option](./media/workbooks-bring-your-own-storage/save-dialog-with-storage.png)
+    ![Screenshot showing the **Save** dialog with storage option.](./media/workbooks-bring-your-own-storage/save-dialog-with-storage.png)
 
 6. Then select **Change** to select a managed identity previously created.