Address comments

Author: karinazhou

docs/connect/ado-net/sql/azure-active-directory-authentication.md

@@ -1,5 +1,5 @@
 ---
-title: "Using Azure Active Directory Authentication with SqlClient"
+title: "Using Azure Active Directory authentication with SqlClient"
 description: "Describes how to use supported Azure Active Directory Authentication modes to connect to Azure SQL data sources with SqlClient"
 ms.date: "11/10/2020"
 dev_langs: 
@@ -130,7 +130,7 @@ using (SqlConnection conn = new SqlConnection(ConnectionString)) {
 
 ## Connecting with Active Directory Managed Identity authentication
 
-**Managed Identities** for Azure resources is the new name for the service formerly known as **Managed Service Identity (MSI)**. When a client application uses an Azure resources to access an Azure service that support Azure AD authentication, **Managed Identities** can be used to authenticate by providing an identity for the Azure resource in Azure AD and use it to obtain access tokens. This can eliminate the need for developers having to manage credentials and secrets. There are two types of **Managed Identities: _System-assigned Managed Identity_ and _User-assigned Managed Identity_. The _System-assigned Managed Identity_ is an identity created on a service instance in Azure AD. It is tied to the lifecycle of that service instance. _User-assigned Managed Identity_ is created as a standalone Azure resource. It can be assigned to one or more instances of an Azure service. For more information about **Managed Identities**, see [About managed identities for Azure resources](/azure/active-directory/managed-identities-azure-resources/overview).
+**Managed Identities** for Azure resources is the new name for the service formerly known as **Managed Service Identity (MSI)**. When a client application uses an Azure resources to access an Azure service that support Azure AD authentication, **Managed Identities** can be used to authenticate by providing an identity for the Azure resource in Azure AD and use it to obtain access tokens. This can eliminate the need for developers having to manage credentials and secrets. There are two types of **Managed Identities**: _System-assigned Managed Identity_ and _User-assigned Managed Identity_. The _System-assigned Managed Identity_ is an identity created on a service instance in Azure AD. It is tied to the lifecycle of that service instance. _User-assigned Managed Identity_ is created as a standalone Azure resource. It can be assigned to one or more instances of an Azure service. For more information about **Managed Identities**, see [About managed identities for Azure resources](/azure/active-directory/managed-identities-azure-resources/overview).
 
 Since **Microsoft.Data.SqlClient** 2.1.0, the driver now supports authentication to Azure SQL Database, Azure Synapse, and Azure SQL Managed Instance by acquiring access tokens via Managed Identity. To use this authentication, specify either `Active Directory Managed Identity` or `Active Directory MSI` in the connection string and no password is required. The Credential property of SqlConnection cannot be set in this mode either. For _User-assigned Managed Identity_, username must be provided. The following example shows how to use `Active Directory Managed Identity` authentication with _System-assigned Managed Identity_.
 

docs/connect/ado-net/sql/azure-key-vault-enclave-example.md

@@ -24,9 +24,9 @@ This example demonstrates use of Azure Key Vault Provider when accessing encrypt
 [!code-csharp [Azure Key Vault Provider with Enclave Example#1](~/../sqlclient/doc/samples/AzureKeyVaultProviderWithEnclaveProviderExample.cs#1)]
 
 > [!NOTE]
-> 1. To use Always Encrypted with secure enclaves for .NET Standard application, **Microsoft.Data.SqlClient** version 2.1.0 or higher is required. The supported .NET Standard version is 2.1 or higher. 
+> - To use Always Encrypted with secure enclaves for .NET Standard application, **Microsoft.Data.SqlClient** version 2.1.0 or higher is required. The supported .NET Standard version is 2.1 or higher. 
 >
-> 2. To use Always Encrypted with secure enclaves on Linux and macOS, **Microsoft.Data.SqlClient** version 2.1.0 or higher is required.
+> - To use Always Encrypted with secure enclaves on Linux and macOS, **Microsoft.Data.SqlClient** version 2.1.0 or higher is required.
 
 ## See Also
 

docs/connect/ado-net/sql/azure-key-vault-example.md

@@ -24,9 +24,9 @@ This example demonstrates use of Azure Key Vault Provider when accessing encrypt
 [!code-csharp [AKVProvider Example#1](~/../sqlclient/doc/samples/AzureKeyVaultProviderExample.cs#1)]
 
 > [!NOTE]
-> 1. To use Always Encrypted feature without secure enclaves for .NET Standard application, **Microsoft.Data.SqlClient** version 2.1.0 or higher is required. The supported .NET Standard version is 2.0 or higher. 
+> - To use Always Encrypted feature without secure enclaves for .NET Standard application, **Microsoft.Data.SqlClient** version 2.1.0 or higher is required. The supported .NET Standard version is 2.0 or higher. 
 >
-> 2. To use Always Encrypted feature on Linux and macOS, **Microsoft.Data.SqlClient** version 2.1.0 or higher is required.
+> - To use Always Encrypted feature on Linux and macOS, **Microsoft.Data.SqlClient** version 2.1.0 or higher is required.
 
 ## See Also
 

docs/connect/toc.yml

@@ -53,7 +53,7 @@
       items:
       - name: Authentication
         href: ../connect/ado-net/sql/authentication-sql-server.md
-      - name: Azure Active Directory Authentication
+      - name: Azure Active Directory authentication
         href: ../connect/ado-net/sql/azure-active-directory-authentication.md
       - name: Application security scenarios
         href: ../connect/ado-net/sql/application-security-scenarios-sql-server.md