Acrolynx fixes

Author: niklarin

articles/cosmos-db/postgresql/concepts-authentication.md

@@ -50,7 +50,7 @@ Permissions for the `citus` role:
   superusers.
 * Read all pg\_stat\_\* views and use various statistics-related
   extensions--even views or extensions normally visible only to superusers.
-* Execute monitoring functions that may take ACCESS SHARE locks on tables,
+* Execute monitoring functions that might take ACCESS SHARE locks on tables,
   potentially for a long time.
 * [Create PostgreSQL extensions](reference-extensions.md).
 
@@ -105,7 +105,7 @@ Once you've authenticated against the Active Directory, you then retrieve a toke
 > [!NOTE]  
 > Login with the deleted Microsoft Entra ID user can still be done till the token expires (up to 90 minutes from token issuing).  If you also remove the user from Azure Cosmos DB for PostgreSQL cluster this access will be revoked immediately.
 
-- Azure Cosmos DB for PostgreSQL matches access tokens to the database role using the user’s unique Microsoft Entra ID user ID, as opposed to using the username. If a Microsoft Entra ID user is deleted and a new user is created with the same name, Azure Cosmos DB for PostgreSQL considers that a different user. Therefore, if a user is deleted from Microsoft Entra ID identificator and a new user is added with the same name the new user would be unable to connect with the existing role.
+- Azure Cosmos DB for PostgreSQL matches access tokens to the database role using the user’s unique Microsoft Entra ID user ID, as opposed to using the username. If a Microsoft Entra ID user is deleted and a new user is created with the same name, Azure Cosmos DB for PostgreSQL considers that a different user. Therefore, if a user is deleted from Microsoft Entra ID and a new user is added with the same name the new user would be unable to connect with the existing role.
 
 ## Next steps
 

articles/cosmos-db/postgresql/how-to-configure-authentication.md

@@ -52,7 +52,7 @@ Users need to be allowed to sign in to Azure Cosmos DB for PostgreSQL in the Mic
 
 1. Search for 'Microsoft Entra ID' in Azure portal.
 1. Open 'Microsoft Entra ID' service.
-1. In the **Overview** section on the **Overview** page of Microsoft Entra ID service search for 'b4fa09d8-5da5-4352-83d9-05c2a44cf431' application ID.
+1. In the **Overview** section on the **Overview** page of Microsoft Entra ID service, search for 'b4fa09d8-5da5-4352-83d9-05c2a44cf431' application ID.
 1. Choose 'Azure Cosmos DB for PostgreSQL AAD Authentication' enterprise application in the search results.
 1. In the Azure Cosmos DB for PostgreSQL AAD Authentication enterprise application, choose 'Properties' page.
 1. Set **Enabled for users to sign-in?** to **Yes** and save the change.
@@ -89,7 +89,7 @@ The native PostgreSQL user is created on the coordinator node of the cluster, an
 
 Microsoft Entra ID integration works with standard PostgreSQL client tools like **psql**, which aren't Microsoft Entra ID aware and support only specifying the username and password when you're connecting to PostgreSQL. In such cases, the Microsoft Entra ID token is passed as the password.
 
-We've tested the following clients:
+We tested the following clients:
 
 - **psql command line**: Use the `PGPASSWORD` variable to pass the token.
 - **Other libpq-based clients**: Examples include common application frameworks and object-relational mappers (ORMs).