Refresh article

Author: JKirsch1

docs/service-hooks/authorize.md

@@ -15,13 +15,14 @@ ms.date: 07/27/2020
 
 [!INCLUDE [version-lt-eq-azure-devops](../includes/version-lt-eq-azure-devops.md)]
 
-When you use a service that's integrated with Azure DevOps, the industry-standard OAuth 2.0 authorization framework provides safe and secure access to your resources by those other services.
-With OAuth, you grant a service the authorization to access your Azure DevOps resources, such as work items, source code, and build results.
+When you use a service that's integrated with Azure DevOps, you can grant the service access your Azure DevOps resources, such as work items, source code, and build results.
 
-- Authorizations are bound to your credentials, so the service can use the authorization to access your resources in Azure DevOps.
-- Use your Microsoft account or your work account to authorize the service.
-- The service that you authorize never has access to your Azure DevOps credentials.
-- Revoke any authorizations that you've granted to other services.
+Azure DevOps uses the industry-standard OAuth 2.0 authorization framework to grant the service access to your resources.
+
+- Authorizations are bound to your credentials, so the service can use an authorization to access your resources in Azure DevOps.
+- You use your Microsoft account or your work account to authorize the service.
+- The service that you authorize doesn't have access to your Azure DevOps credentials.
+- You can revoke any authorizations that you grant to other services.
 
 ## Prerequisites
 
@@ -33,29 +34,30 @@ With OAuth, you grant a service the authorization to access your Azure DevOps re
 
 ## Authorize a service
 
-A typical authorization flow might go like this:
+A typical authorization flow might include the following steps:
 
 1. You're using a service that uses Azure DevOps resources, so the service requests authorization.
+
 1. If you're not already signed in, Azure DevOps prompts you for your credentials.
 
    ![Screenshot of Azure DevOps sign in page.](./media/authorize/vso-sign-in.png) 
 
-2. After you sign in, you get the authorization approval page.
+1. After you sign in, you get the authorization approval page.
 
    ![Screenshot of Azure DevOps authorization page](./media/authorize/vso-authorize.png)
 
-   Services can only request full access to all of the resources that are available to you through the REST APIs, so the authorization request might not be specific.
+   Services can only request full access to all the resources that are available to you through the REST APIs, so the authorization request might not be specific.
 
-3. Review the request and approve the authorization.
+1. You review the request and approve the authorization.
 
-   The authorized service uses that authorization to access resources in your Visual Studio account.
+1. The authorized service uses that authorization to access resources in your Visual Studio account.
 
-   To ensure an authorization request is legitimate:
+To ensure an authorization request is legitimate, take the following steps:
 
 - Look for the Azure DevOps branding across the upper portion of the authorization approval page.
-- Ensure the authorization approval page URL begins with ```https://app.vssps.visualstudio.com/```.
+- Ensure the authorization approval page URL begins with `https://app.vssps.visualstudio.com/`.
 - Pay attention to any HTTPS-related security warnings in your browser.
-- Remember that other services don't ask for your credentials directly. They let you provide them to Azure DevOps through the authorization approval page.
+- Don't give your credentials to other services directly. Enter your credentials only through the authorization approval page in Azure DevOps.
 
 ## Manage authorizations