From 38ea35a06998bed6f63cc9e2dbdc6c4a8602224a Mon Sep 17 00:00:00 2001
From: "Alessandro (Ale) Segala" <43508+ItalyPaleAle@users.noreply.github.com>
Date: Thu, 9 Sep 2021 19:37:08 -0700
Subject: [PATCH] Updated per Christos' comments

---
 .../integrations/cloud-providers/authenticating-azure.md        | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/daprdocs/content/en/developing-applications/integrations/cloud-providers/authenticating-azure.md b/daprdocs/content/en/developing-applications/integrations/cloud-providers/authenticating-azure.md
index f938ba523..912b0d7b6 100644
--- a/daprdocs/content/en/developing-applications/integrations/cloud-providers/authenticating-azure.md
+++ b/daprdocs/content/en/developing-applications/integrations/cloud-providers/authenticating-azure.md
@@ -20,7 +20,7 @@ Some Azure components offer alternative authentication methods, such as systems
 
 Azure AD is Azure's identity and access management (IAM) solution, which is used to authenticate and authorize users and services.
 
-Azure AD is based on the OAuth 2.0 standard, which allows services (applications) to obtain access tokens to make requests to Azure services, including Azure Storage, Azure Key Vault, Cosmos DB, etc. In the Azure terminology, an application is also called a "Service Principal".
+Azure AD is built on top of open standards such OAuth 2.0, which allows services (applications) to obtain access tokens to make requests to Azure services, including Azure Storage, Azure Key Vault, Cosmos DB, etc. In the Azure terminology, an application is also called a "Service Principal".
 
 Many of the services listed above also support authentication using other systems, such as "master keys" or "shared keys". Although those are always valid methods to authenticate your application (and Dapr continues to support them, as explained in each component's reference page), using Azure AD when possible offers various benefits, including: