update readmes

Author: BenBagBag

1-Authentication/0-sign-in-vanillajs/App/package.json

@@ -1,7 +1,7 @@
 {
     "name": "ciam-sign-in-javascript",
     "version": "1.0.0",
-    "description": "Vanilla JavaScript single-page application using MSAL.js to authenticate users against Azure AD Customer Identity Access Management (Azure AD for Customers)",
+    "description": "Vanilla JavaScript single-page application using MSAL.js to authenticate users against Azure AD Customer Identity Access Management (Microsoft Entra External ID)",
     "main": "server.js",
     "scripts": {
         "start": "node server.js",

1-Authentication/0-sign-in-vanillajs/AppCreationScripts/AppCreationScripts.md

@@ -33,7 +33,7 @@ This sample comes with two PowerShell scripts, which automate the creation of th
 These scripts are:
 
 - `Configure.ps1` which:
-  - creates Azure AD applications and their related objects (permissions, dependencies, secrets, app roles),
+  - creates Microsoft Entra applications and their related objects (permissions, dependencies, secrets, app roles),
   - changes the configuration files in the sample projects.
   - creates a summary file named `createdApps.html` in the folder from which you ran the script, and containing, for each Azure AD application it created:
     - the identifier of the application

1-Authentication/0-sign-in-vanillajs/AppCreationScripts/Cleanup.ps1

@@ -18,7 +18,7 @@ Function Cleanup
 
     <#
     .Description
-    This function removes the Azure AD applications for the sample. These applications were created by the Configure.ps1 script
+    This function removes the Microsoft Entra applications for the sample. These applications were created by the Configure.ps1 script
     #>
 
     # $tenantId is the Active Directory Tenant. This is a GUID which represents the "Directory ID" of the AzureAD tenant 

1-Authentication/0-sign-in-vanillajs/AppCreationScripts/Configure.ps1

@@ -9,8 +9,8 @@ param(
 )
 
 <#
- This script creates the Azure AD applications needed for this sample and updates the configuration files
- for the visual Studio projects from the data in the Azure AD applications.
+ This script creates the Microsoft Entra applications needed for this sample and updates the configuration files
+ for the visual Studio projects from the data in the Microsoft Entra applications.
 
  In case you don't have Microsoft.Graph.Applications already installed, the script will automatically install it for the current user
  
@@ -173,7 +173,7 @@ Function CreateOptionalClaim([string] $name)
 Function ConfigureApplications
 {
     <#.Description
-       This function creates the Azure AD applications for the sample in the provided Azure AD tenant and updates the
+       This function creates the Microsoft Entra applications for the sample in the provided Azure AD tenant and updates the
        configuration files in the client and service project  of the visual studio solution (App.Config and Web.Config)
        so that they are consistent with the Applications parameters
     #> 

1-Authentication/0-sign-in-vanillajs/AppCreationScripts/apps.json

@@ -1,6 +1,6 @@
 {
     "Sample": {
-        "Title": "A JavaScript single-page application using MSAL Angular to authenticate users against Azure AD for Customers",
+        "Title": "A JavaScript single-page application using MSAL Angular to authenticate users against Microsoft Entra External ID",
         "Client": "SinglePageApplication",
         "Level": 100
     },

1-Authentication/0-sign-in-vanillajs/AppCreationScripts/quickstart.md

@@ -14,7 +14,7 @@ ms.date: 04/19/2023
 ---
 # Portal quickstart for JavaScript SPA
 
-> In this quickstart, you download and run a code sample that demonstrates how a JavaScript SPA that can sign in users with Azure AD for Customers.
+> In this quickstart, you download and run a code sample that demonstrates how a JavaScript SPA that can sign in users with Microsoft Entra External ID.
 >
 > [!div renderon="portal" id="display-on-portal" class="sxs-lookup"]
 >

1-Authentication/0-sign-in-vanillajs/AppCreationScripts/sample.json

@@ -1,14 +1,14 @@
 {
     "Sample": {
-        "Title": "Vanilla JavaScript single-page application using MSAL.js to authenticate users against Customer Identity Access Management (CIAM)",
+        "Title": "Vanilla JavaScript single-page application using MSAL.js to authenticate users against Microsoft Entra External ID",
         "Level": 100,
         "Client": "Vanilla JavaScript SPA",
         "RepositoryUrl": "ms-identity-ciam-javascript-tutorial",
         "Endpoint": "AAD v2.0",
         "Languages": [
             "javascript"
         ],
-        "Description": "Vanilla JavaScript single-page application using MSAL.js to authenticate users against Customer Identity Access Management (CIAM)",
+        "Description": "Vanilla JavaScript single-page application using MSAL.js to authenticate users against Microsoft Entra External ID",
         "Products": [
             "azure-active-directory",
             "msal-js",

1-Authentication/0-sign-in-vanillajs/README.md

@@ -1,7 +1,7 @@
 ---
 page_type: sample
-name: Vanilla JavaScript single-page application using MSAL.js to authenticate users against Azure AD for Customers
-description: This sample demonstrates a Vanilla JavaScript single-page application using MSAL.js to authenticate users against Azure Active Directory Customer Identity Access Management (Azure AD for Customers)
+name: Vanilla JavaScript single-page application using MSAL.js to authenticate users against Microsoft Entra External ID
+description: This sample demonstrates a Vanilla JavaScript single-page application using MSAL.js to authenticate users against Azure Active Directory Customer Identity Access Management (Microsoft Entra External ID)
 languages:
  - javascript
 products:
@@ -21,7 +21,7 @@ extensions:
     - Vanilla JavaScript SPA
 ---
 
-# Vanilla JavaScript single-page application using MSAL.js to authenticate users against Azure AD for Customers
+# Vanilla JavaScript single-page application using MSAL.js to authenticate users against Microsoft Entra External ID
 
 * [Overview](#overview)
 * [Scenario](#scenario)
@@ -36,13 +36,13 @@ extensions:
 
 ## Overview
 
-This sample demonstrates a vanilla JavaScript single-page application (SPA) that lets users authenticate to [Azure Active Directory CIAM](https://github.com/microsoft/entra-previews/blob/PP2/docs/1-Create-a-CIAM-tenant.md) (Azure AD for Customers) using the [Microsoft Authentication Library for JavaScript](https://github.com/AzureAD/microsoft-authentication-library-for-js) (MSAL.js). 
+This sample demonstrates a vanilla JavaScript single-page application (SPA) that lets users authenticate to [Azure Active Directory CIAM](https://github.com/microsoft/entra-previews/blob/PP2/docs/1-Create-a-CIAM-tenant.md) (Microsoft Entra External ID) using the [Microsoft Authentication Library for JavaScript](https://github.com/AzureAD/microsoft-authentication-library-for-js) (MSAL.js). 
 Here you'll learn about [ID Tokens](https://docs.microsoft.com/azure/active-directory/develop/id-tokens), [OIDC scopes](https://docs.microsoft.com/azure/active-directory/develop/v2-permissions-and-consent#openid-connect-scopes), [single-sign on](https://docs.microsoft.com/azure/active-directory/develop/msal-js-sso), **silent requests** and more.
 
 ## Scenario
 
-1. The client JavaScript SPA uses the  to sign-in a user and obtain a JWT [ID Token](https://aka.ms/id-tokens) from **Azure AD for Customers**.
-1. The **ID Token** proves that the user has successfully authenticated against **Azure AD for Customers**.
+1. The client JavaScript SPA uses the  to sign-in a user and obtain a JWT [ID Token](https://aka.ms/id-tokens) from **Microsoft Entra External ID**.
+1. The **ID Token** proves that the user has successfully authenticated against **Microsoft Entra External ID**.
 
 ![Scenario Image](./ReadmeFiles/topology.png)
 
@@ -63,8 +63,8 @@ Here you'll learn about [ID Tokens](https://docs.microsoft.com/azure/active-dire
 * [Visual Studio Code](https://code.visualstudio.com/download) is recommended for running and editing this sample.
 * [VS Code Azure Tools](https://marketplace.visualstudio.com/items?itemName=ms-vscode.vscode-node-azure-pack) extension is recommended for interacting with Azure through VS Code Interface.
 * A modern web browser.
-* An **Azure AD for Customers** tenant. For more information, see: [How to get an Azure AD for Customers tenant](https://github.com/microsoft/entra-previews/blob/PP2/docs/1-Create-a-CIAM-tenant.md)
-* A user account with permissions to create applications in your **Azure AD for Customers** tenant.
+* An **Microsoft Entra External ID** tenant. For more information, see: [How to get an external tenant](https://github.com/microsoft/entra-previews/blob/PP2/docs/1-Create-a-CIAM-tenant.md)
+* A user account with permissions to create applications in your **Microsoft Entra External ID** tenant.
 
 ## Setup the sample
 
@@ -93,7 +93,7 @@ There is one project in this sample. To register it, you can:
 
 * follow the steps below for manually register your apps
 * or use PowerShell scripts that:
-  * **automatically** creates the Azure AD applications and related objects (passwords, permissions, dependencies) for you.
+  * **automatically** creates the Microsoft Entra applications and related objects (passwords, permissions, dependencies) for you.
   * modify the projects' configuration files.
 
 <details>
@@ -115,18 +115,18 @@ There is one project in this sample. To register it, you can:
 
 </details>
 
-#### Choose the Azure AD for Customers tenant where you want to create your applications
+#### Choose the Microsoft Entra External ID tenant where you want to create your applications
 
 To manually register the apps, as a first step you'll need to:
 
 1. Sign in to the [Azure portal](https://portal.azure.com).
-1. If your account is present in more than one Azure AD for Customers tenant, select your profile at the top right corner in the menu on top of the page, and then **switch directory** to change your portal session to the desired Azure AD for Customers tenant.
+1. If your account is present in more than one Microsoft Entra External ID tenant, select your profile at the top right corner in the menu on top of the page, and then **switch directory** to change your portal session to the desired Microsoft Entra External ID tenant.
 
 #### Create User Flows
 
 Please refer to: [Tutorial: Create user flow in Azure Active Directory CIAM](https://github.com/microsoft/entra-previews/blob/PP2/docs/3-Create-sign-up-and-sign-in-user-flow.md)
 
-> :information_source: To enable password reset in Customer Identity Access Management (CIAM) in Azure Active Directory (Azure AD), please refer to: [Tutorial: Enable self-service password reset](https://github.com/microsoft/entra-previews/blob/PP2/docs/4-Enable-password-reset.md)
+> :information_source: To enable password reset in Microsoft Entra External ID in Azure Active Directory (Azure AD), please refer to: [Tutorial: Enable self-service password reset](https://github.com/microsoft/entra-previews/blob/PP2/docs/4-Enable-password-reset.md)
 
 #### Add External Identity Providers
 
@@ -137,7 +137,7 @@ Please refer to:
 
 #### Register the client app (ciam-msal-javascript-spa)
 
-1. Navigate to the [Azure portal](https://portal.azure.com) and select the **Azure AD for Customers** service.
+1. Navigate to the [Azure portal](https://portal.azure.com) and select the **Microsoft Entra External ID** service.
 1. Select the **App Registrations** blade on the left, then select **New registration**.
 1. In the **Register an application page** that appears, enter your application's registration information:
     1. In the **Name** section, enter a meaningful application name that will be displayed to users of the app, for example `ciam-msal-javascript-spa`.
@@ -157,7 +157,7 @@ Please refer to:
     1. In the *Commonly used Microsoft APIs* section, select **Microsoft Graph**
     1. In the **Delegated permissions** section, select **openid**, **offline_access** in the list. Use the search box if necessary.
     1. Select the **Add permissions** button at the bottom.
-1. At this stage, the permissions are assigned correctly, but since it's a CIAM tenant, the users themselves cannot consent to these permissions. To get around this problem, we'd let the [tenant administrator consent on behalf of all users in the tenant](https://docs.microsoft.com/azure/active-directory/develop/v2-admin-consent). Select the **Grant admin consent for {tenant}** button, and then select **Yes** when you are asked if you want to grant consent for the requested permissions for all accounts in the tenant. You need to be a tenant admin to be able to carry out this operation.
+1. At this stage, the permissions are assigned correctly, but since it's an external tenant, the users themselves cannot consent to these permissions. To get around this problem, we'd let the [tenant administrator consent on behalf of all users in the tenant](https://docs.microsoft.com/azure/active-directory/develop/v2-admin-consent). Select the **Grant admin consent for {tenant}** button, and then select **Yes** when you are asked if you want to grant consent for the requested permissions for all accounts in the tenant. You need to be a tenant admin to be able to carry out this operation.
 
 ##### Configure the client app (ciam-msal-javascript-spa) to use your app registration
 

1-Authentication/1-sign-in-react/AppCreationScripts/AppCreationScripts.md

@@ -33,7 +33,7 @@ This sample comes with two PowerShell scripts, which automate the creation of th
 These scripts are:
 
 - `Configure.ps1` which:
-  - creates Azure AD applications and their related objects (permissions, dependencies, secrets, app roles),
+  - creates Microsoft Entra applications and their related objects (permissions, dependencies, secrets, app roles),
   - changes the configuration files in the sample projects.
   - creates a summary file named `createdApps.html` in the folder from which you ran the script, and containing, for each Azure AD application it created:
     - the identifier of the application

1-Authentication/1-sign-in-react/AppCreationScripts/Cleanup.ps1

@@ -18,7 +18,7 @@ Function Cleanup
 
     <#
     .Description
-    This function removes the Azure AD applications for the sample. These applications were created by the Configure.ps1 script
+    This function removes the Microsoft Entra applications for the sample. These applications were created by the Configure.ps1 script
     #>
 
     # $tenantId is the Active Directory Tenant. This is a GUID which represents the "Directory ID" of the AzureAD tenant