Apply suggestions from code review

alexbuckgit · msmimart · web-flow · commit a3f77023a5ae · 2023-09-21T08:09:49.000-04:00
Co-authored-by: Michele Martin &lt;36167252+msmimart@users.noreply.github.com&gt;
diff --git a/articles/active-directory/external-identities/google-federation.md b/articles/active-directory/external-identities/google-federation.md
@@ -191,7 +191,7 @@ First, create a new project in the Google Developers Console to obtain a client
 
 <a name='step-2-configure-google-federation-in-azure-ad-'></a>
 
-## Step 2: Configure Google federation in Microsoft Entra ID 
+## Step 2: Configure Google federation in Microsoft Entra External ID 
 
 You'll now set the Google client ID and client secret. You can use the Microsoft Entra admin center or PowerShell to do so. Be sure to test your Google federation configuration by inviting yourself. Use a Gmail address and try to redeem the invitation with your invited Google account. 
 
diff --git a/articles/active-directory/external-identities/hybrid-cloud-to-on-premises.md b/articles/active-directory/external-identities/hybrid-cloud-to-on-premises.md
@@ -19,7 +19,7 @@ ms.collection: M365-identity-device-management
 
 # Grant B2B users in Microsoft Entra ID access to your on-premises applications
 
-As an organization that uses Microsoft Entra B2B collaboration capabilities to invite guest users from partner organizations to your Microsoft Entra ID, you can now provide these B2B users access to on-premises apps. These on-premises apps can use SAML-based authentication or integrated Windows authentication (IWA) with Kerberos constrained delegation (KCD).
+As an organization that uses Microsoft Entra B2B collaboration capabilities to invite guest users from partner organizations, you can now provide these B2B users access to on-premises apps. These on-premises apps can use SAML-based authentication or integrated Windows authentication (IWA) with Kerberos constrained delegation (KCD).
 
 ## Access to SAML apps
 
diff --git a/articles/active-directory/external-identities/hybrid-organizations.md b/articles/active-directory/external-identities/hybrid-organizations.md
@@ -32,7 +32,7 @@ For apps that use integrated Windows authentication (IWA) with Kerberos constrai
 - You can use Microsoft Identity Manager (MIM) 2016 SP1 and the MIM management agent for Microsoft Graph.
 - You can use a PowerShell script. (This solution doesn't require MIM.)
 
-For details about how to implement these solutions, see [Grant B2B users in Microsoft Entra ID access to your on-premises applications](hybrid-cloud-to-on-premises.md).
+For details about how to implement these solutions, see [Grant Microsoft Entra B2B users access to your on-premises applications](hybrid-cloud-to-on-premises.md).
 
 ## Grant locally managed partner accounts access to cloud resources
 
@@ -46,6 +46,6 @@ For implementation details, see [Grant locally managed partner accounts access t
  
 ## Next steps
 
-- [Grant B2B users in Microsoft Entra ID access to your on-premises applications](hybrid-cloud-to-on-premises.md)
+- [Grant Microsoft Entra B2B users access to your on-premises applications](hybrid-cloud-to-on-premises.md)
 - [B2B direct connect](b2b-direct-connect-overview.md)
 - [Grant locally managed partner accounts access to cloud resources using Microsoft Entra B2B collaboration](hybrid-on-premises-to-cloud.md)
diff --git a/articles/active-directory/external-identities/identity-providers.md b/articles/active-directory/external-identities/identity-providers.md
@@ -19,7 +19,7 @@ ms.collection: M365-identity-device-management
 > [!TIP]
 > This article applies to B2B collaboration identity providers. If your tenant is configured for customer identity and access management, see [Authentication methods and identity providers for customers](customers/concept-authentication-methods-customers.md).
 
-An *identity provider* creates, maintains, and manages identity information while providing authentication services to applications. When sharing your apps and resources with external users, Microsoft Entra ID is the default identity provider for sharing. This means when you invite external users who already have a Microsoft Entra ID or Microsoft account, they can automatically sign in without further configuration on your part.
+An *identity provider* creates, maintains, and manages identity information while providing authentication services to applications. When sharing your apps and resources with external users, Microsoft Entra ID is the default identity provider for sharing. This means when you invite external users who already have a Microsoft Entra account or Microsoft account, they can automatically sign in without further configuration on your part.
 
 External Identities offers a variety of identity providers.
 
diff --git a/articles/active-directory/external-identities/index.yml b/articles/active-directory/external-identities/index.yml
@@ -58,7 +58,7 @@ additionalContent:
           url: /azure/active-directory/external-identities/customers/concept-planning-your-solution
           # Card
         - title: Code samples for customer tenants
-          summary: Learn about our code samples for customer identity and access management (CIAM) in Microsoft Entra ID.
+          summary: Learn about our code samples for customer identity and access management (CIAM) in Microsoft Entra External ID.
           url: /azure/active-directory/external-identities/customers/samples-ciam-all
           # Card
         - title: Authentication methods and identity providers
@@ -83,7 +83,7 @@ additionalContent:
           summary: Learn about the Microsoft Entra B2B direct connect feature.
           url: /azure/active-directory/external-identities/b2b-direct-connect-overview   
         # Card
-        - title: External user properties in Microsoft Entra ID
+        - title: External user properties in Microsoft Entra External ID
           summary: Learn about the properties of a Microsoft Entra B2B collaboration user.
           url: /azure/active-directory/external-identities/user-properties 
         # Card
diff --git a/articles/active-directory/external-identities/invitation-email-elements.md b/articles/active-directory/external-identities/invitation-email-elements.md
@@ -17,7 +17,7 @@ ms.collection: M365-identity-device-management
 
 # The elements of the B2B collaboration invitation email
 
-Invitation emails are a critical component to bring partners on board as B2B collaboration users in Microsoft Entra ID. It’s [not required that you send an email to invite someone using B2B collaboration](redemption-experience.md#redemption-process-through-a-direct-link), but it gives the user all the information they need to decide if they accept your invite or not. It also gives them a link they can always refer to in the future when they need to return to your resources.
+Invitation emails are a critical component to bring partners on board as Microsoft Entra B2B collaboration users. It’s [not required that you send an email to invite someone using B2B collaboration](redemption-experience.md#redemption-process-through-a-direct-link), but it gives the user all the information they need to decide if they accept your invite or not. It also gives them a link they can always refer to in the future when they need to return to your resources.
 
 ![Screenshot showing the B2B invitation email](media/invitation-email-elements/invitation-email.png)
 
@@ -37,7 +37,7 @@ We use a LinkedIn-like pattern for the From address. This pattern should make it
 
 > [!NOTE]
 > For the Azure service operated by [21Vianet in China](/azure/china), the sender address is Invites@oe.21vianet.com.  
-> For the [Microsoft Entra Government](../../azure-government/index.yml), the sender address is invites@azuread.us.
+> For [Microsoft Entra ID for government](../../azure-government/index.yml), the sender address is invites@azuread.us.
 
 ### Reply To
 
diff --git a/articles/active-directory/external-identities/invite-internal-users.md b/articles/active-directory/external-identities/invite-internal-users.md
@@ -73,7 +73,7 @@ You can use the Microsoft Entra admin center, PowerShell, or the invitation API
 
 ## Use PowerShell to send a B2B invitation
 
-You'll need Azure AD PowerShell module version 2.0.2.130 or later. Use the following command to update to the latest Azure Active Directory PowerShell module and invite the internal user to B2B collaboration:
+You'll need Azure AD PowerShell module version 2.0.2.130 or later. Use the following command to update to the latest AzureAD PowerShell module and invite the internal user to B2B collaboration:
 
 ```powershell
 Uninstall-Module AzureAD
diff --git a/articles/active-directory/external-identities/microsoft-account.md b/articles/active-directory/external-identities/microsoft-account.md
@@ -1,7 +1,7 @@
 ---
 
 title: Add Microsoft account (MSA) as an identity provider
-description: Use Microsoft Entra ID to enable an external user (guest) to sign in to your Microsoft Entra apps with their Microsoft account (MSA).
+description: Use Microsoft Entra External ID to enable an external user (guest) to sign in to your Microsoft Entra apps with their Microsoft account (MSA).
 
 services: active-directory
 ms.service: active-directory
@@ -42,7 +42,7 @@ Microsoft account is an identity provider option for your self-service sign-up u
 :::image type="content" source="media/microsoft-account/microsoft-account-user-flow.png" alt-text="Screenshot of the Microsoft account in a self-service sign-up user flow.":::
 
 ## Verifying the application's publisher domain
-As of November 2020, new application registrations show up as unverified in the user consent prompt, unless [the application's publisher domain is verified](../develop/howto-configure-publisher-domain.md), ***and*** the company’s identity has been verified with the Microsoft Partner Network and associated with the application.  For Microsoft Entra user flows, the publisher’s domain appears only when using a Microsoft account or another Microsoft Entra tenant as the identity provider. To meet these new requirements, follow the steps below:
+As of November 2020, new application registrations show up as unverified in the user consent prompt, unless [the application's publisher domain is verified](../develop/howto-configure-publisher-domain.md), ***and*** the company’s identity has been verified with the Microsoft Partner Network and associated with the application.  For Microsoft Entra External ID user flows, the publisher’s domain appears only when using a Microsoft account or another Microsoft Entra tenant as the identity provider. To meet these new requirements, follow the steps below:
 
 1. [Verify your company identity using your Microsoft Partner Network (MPN) account](/partner-center/verification-responses). This process verifies information about your company and your company’s primary contact.
 1. Complete the publisher verification process to associate your MPN account with your app registration using one of the following options:
