fixed PR comments

Author: AikoBB

articles/communication-services/concepts/identity-model.md

@@ -167,8 +167,8 @@ This architecture eliminates the need for a separate identity management service
 
 ### Limitations
 The Microsoft Entra ID integration is currently in public preview and has the following limitations:
-- [Continuous Access Evaluation](/entra/identity/conditional-access/concept-continuous-access-evaluation) is not available. To revoke access tokens immediately, follow the instructions in [Create and manage access tokens for end users](../quickstarts/identity/access-tokens.md#create-and-manage-access-tokens-for-end-users).
-- Removing an Entra ID user does not automatically remove all associated data from the Communication Services resource. To ensure all data is deleted, follow the instructions in [Create and manage access tokens for end users](../quickstarts/identity/access-tokens.md#create-and-manage-access-tokens-for-end-users).
+- [Continuous Access Evaluation](/entra/identity/conditional-access/concept-continuous-access-evaluation) is not available. To revoke access tokens immediately, follow the instructions in [Revoke access tokens](../quickstarts/identity/access-tokens.md?pivots=platform-azcli#revoke-access-tokens).
+- Removing an Entra ID user does not automatically remove all associated data from the Communication Services resource. To ensure all data is deleted, follow the instructions in [Delete an identity](../quickstarts/identity/access-tokens.md?pivots=platform-azcli#delete-an-identity).
 
 ## Next steps
 

articles/communication-services/quickstarts/identity/entra-id-authentication-integration.md

@@ -18,7 +18,7 @@ ms.custom: mode-other, devx-track-js, has-azure-ad-ps-ref
 
 [!INCLUDE [Public Preview Disclaimer](../../includes/public-preview-include.md)]
 
-This quickstart demonstrates how to use the Communication Services Common SDK along with Azure Identity SDK in a console application to authenticate a Microsoft Entra ID user, obtain an Azure Communication Services access token for Microsoft Entra ID user. The resulting Azure Communication Services access token allows you to integrate calling and chat features using the Communication Services Calling and Chat SDKs.
+This quickstart demonstrates how to use the Communication Services Common SDK along with Azure Identity SDK in a console application to authenticate a Microsoft Entra ID user and obtain an Azure Communication Services access token. The resulting Azure Communication Services access token allows you to integrate calling and chat features using the Communication Services Calling and Chat SDKs.
 
 ## Prerequisites
 - An Azure account with an active subscription. [Create an account for free](https://azure.microsoft.com/free/?WT.mc_id=A261C142F).
@@ -76,7 +76,7 @@ Users must be authenticated against Microsoft Entra applications with Azure Comm
 
 The following application settings influence the experience:
 - The *Supported account types* property defines whether the application is single tenant ("Accounts in this organizational directory only") or multitenant ("Accounts in any organizational directory"). For this scenario, you can use multitenant.
-- *Redirect URI* defines the URI where the authentication request is redirected after authentication. For this scenario, you can use **Public client/native (mobile & desktop)** and enter **`http://localhost`** as the URI.
+- *Redirect URI* defines the URI where the authentication request is redirected after authentication.
 
 For more detailed information, see [Register an application with the Microsoft identity platform](/entra/identity-platform/quickstart-register-app#register-an-application). 
 
@@ -112,6 +112,7 @@ In the Azure portal follow these steps:
 7. In the **Client ID** field, enter the client ID of Contoso application from [step 2](entra-id-authentication-integration.md#step-2-create-a-microsoft-entra-application-registration-or-select-a-microsoft-entra-application).
 8. Click **Save and exit** to apply the changes.
 
+![Providing Entra ID users with access to the Azure Communication Services resource through the Azure portal](./media/entra-id/acs-resource-access-managing.png)
 
 ### Step 5: Provide Administrator consent and group access to Azure Communication Services Clients application
 

articles/communication-services/quickstarts/identity/includes/entra-id/support-entra-id-users-js.md

@@ -15,8 +15,8 @@ ms.author: aigerimb
 
 ## Set up prerequisites
 
-- [Node.js](https://nodejs.org/) Active LTS and Maintenance LTS versions (8.11.1 and 10.14.1 recommended).
-- [Azure Identify SDK for JavaScript](https://www.npmjs.com/package/@azure/identity) to authenticate with Microsoft Entra ID.
+- [Node.js](https://nodejs.org/)
+- [Azure Identity SDK for JavaScript](https://www.npmjs.com/package/@azure/identity) to authenticate with Microsoft Entra ID.
 - [Azure Communication Services Common SDK for JavaScript](https://www.npmjs.com/package/@azure/communication-common) to obtain Azure Communication Services access tokens for Microsoft Entra ID user.
 
 ## Final code
@@ -43,24 +43,24 @@ npm init -y
 Use the `npm install` command to install the Azure Identity and Azure Communication Services Common SDKs for JavaScript.The Azure Communication Services Common SDK version should be `2.4.0` or later.
 
 ```console
-npm install @azure/communication-common@latest --save
-npm install --save @azure/identity
+npm install @azure/communication-common --save
+npm install @azure/identity --save
 npm install express --save
 npm install dotenv --save
 ```
 
 The `--save` option lists the library as a dependency in your **package.json** file.
 
-## Set up the app framework
+## Implement the credential flow
 
 From the project directory:
 
 1. Open a new text file in your code editor
-1. Create the structure for the program, including basic exception handling and importing following SDK classes:
+1. Create a basic NodeJS Express server and add the following imports:
 
     ```javascript
     const { AzureCommunicationTokenCredential } = require('@azure/communication-common');    
-    const {InteractiveBrowserCredential} = require('@azure/identity');
+    const { InteractiveBrowserCredential } = require('@azure/identity');
     const express = require("express");
 
     // You will need to set environment variables in .env
@@ -125,7 +125,7 @@ app.get('/', async (req, res) => {
     }
 });
 ```
-Providing scopes is optional. When not specified, the `https://communication.azure.com/clients/.default` scope is automatically used, requesting all API permissions for Communication Services Clients.
+Providing scopes is optional. When not specified, the `https://communication.azure.com/clients/.default` scope is automatically used, requesting all API permissions for Communication Services Clients that have been registered on the client application.
 
 <a name='step-3-obtain-acs-access-token-of-the-entra-id-user'></a>
 

articles/communication-services/quickstarts/identity/includes/entra-id/support-entra-id-users-net.md

@@ -48,7 +48,7 @@ dotnet add package Azure.Identity
 dotnet add package Azure.Communication.Common
 ```
 
-### Set up the app framework
+### Implement the credential flow
 
 From the project directory:
 
@@ -117,7 +117,7 @@ var credential = new CommunicationTokenCredential(entraTokenCredentialOptions);
 
 ```
 
-Providing scopes is optional. When not specified, the `https://communication.azure.com/clients/.default` scope is automatically used, requesting all API permissions for Communication Services Clients.
+Providing scopes is optional. When not specified, the `https://communication.azure.com/clients/.default` scope is automatically used, requesting all API permissions for Communication Services Clients that have been registered on the client application.
 
 <a name='step-3-obtain-acs-access-token-of-the-entra-id-user'></a>