[Azure AD B2C] Content freshness and customer intent Dec 2023

Author: kengaderdus

articles/active-directory-b2c/add-ropc-policy.md

@@ -40,9 +40,9 @@ The following flows aren't supported:
 - **Server-to-server**: The identity protection system needs a reliable IP address gathered from the caller (the native client) as part of the interaction. In a server-side API call, only the server’s IP address is used. If a dynamic threshold of failed authentications is exceeded, the identity protection system may identify a repeated IP address as an attacker.
 - **Confidential client flow**: The application client ID is validated, but the application secret isn't validated.
 
-When using the ROPC flow, consider the following:
+When using the ROPC flow, consider the following limitations:
 
-- ROPC doesn’t work when there's any interruption to the authentication flow that needs user interaction. For example, when a password has expired or needs to be changed, [multifactor authentication](multi-factor-authentication.md) is required, or when more information needs to be collected during sign-in (for example, user consent).
+- ROPC doesn’t work when there's any interruption to the authentication flow that needs user interaction. For example, when a password expires or needs to be changed, [multifactor authentication](multi-factor-authentication.md) is required, or when more information needs to be collected during sign-in (for example, user consent).
 - ROPC supports local accounts only. Users can’t sign in with [federated identity providers](add-identity-provider.md) like Microsoft, Google+, Twitter, AD-FS, or Facebook.
 - [Session Management](session-behavior.md), including [keep me signed-in (KMSI)](session-behavior.md#enable-keep-me-signed-in-kmsi), isn't applicable.
 
@@ -70,7 +70,7 @@ When using the ROPC flow, consider the following:
 
 ::: zone pivot="b2c-custom-policy"
 
-## Pre-requisite 
+## Prerequisite 
 If you've not done so, learn how to use the custom policy starter pack in [Get started with custom policies in Active Directory B2C](tutorial-create-user-flows.md).
 
 ##  Create a resource owner policy
@@ -375,12 +375,8 @@ A successful response looks like the following example:
 
 * **Symptom** - You run the ROPC flow, and get the following message: *AADB2C90057: The provided application isn't configured to allow the 'OAuth' Implicit flow*.
 * **Possible causes** - The implicit flow isn't allowed for your application.
-* **Resolution**: When creating your [app registration](#register-an-application) in Azure AD B2C, you need to manually edit the application manifest and set the value of the `oauth2AllowImplicitFlow` property to `true`. After you configure the `oauth2AllowImplicitFlow` property, it can take a few minutes (typically no more than five) for the change to take affect. 
+* **Resolution**: When creating your [app registration](#register-an-application) in Azure AD B2C, you need to manually edit the application manifest and set the value of the `oauth2AllowImplicitFlow` property to `true`. After you configure the `oauth2AllowImplicitFlow` property, it can take a few minutes (typically no more than five) for the change to take effect. 
 
 ## Use a native SDK or App-Auth
 
-Azure AD B2C meets OAuth 2.0 standards for public client resource owner password credentials and should be compatible with most client SDKs. For the latest information, see [Native App SDK for OAuth 2.0 and OpenID Connect implementing modern best practices](https://appauth.io/).
-
-## Next steps
-
-Download working samples that have been configured for use with Azure AD B2C from GitHub, [for Android](https://aka.ms/aadb2cappauthropc) and [for iOS](https://aka.ms/aadb2ciosappauthropc).
+Azure AD B2C meets OAuth 2.0 standards for public client resource owner password credentials and should be compatible with most client SDKs. For the latest information, see [Native App SDK for OAuth 2.0 and OpenID Connect implementing modern best practices](https://appauth.io/).

articles/active-directory-b2c/api-connectors-overview.md

@@ -29,7 +29,7 @@ As a developer or IT administrator, you can use API connectors to integrate your
 - **Validate user input data**. Validate against malformed or invalid user data. For example, you can validate user-provided data against existing data in an external data store or list of permitted values. If invalid, you can ask a user to provide valid data or block the user from continuing the sign-up flow.
 - **Verify user identity**. Use an identity verification service or external identity data sources to add an extra level of security to account creation decisions.
 - **Integrate with a custom approval workflow**. Connect to a custom approval system for managing and limiting account creation.
-- **Augment tokens with attributes from external sources**. Enrich tokens with attributes about the user from sources that are external to Azure AD B2C such as cloud systems, custom user stores, custom permission systems, legacy identity services, and more.
+- **Augment tokens with attributes from external sources**. Enrich tokens with user attributes from sources that are external to Azure AD B2C such as cloud systems, custom user stores, custom permission systems, legacy identity services, and more.
 - **Overwrite user attributes**. Reformat or assign a value to an attribute collected from the user. For example, if a user enters the first name in all lowercase or all uppercase letters, you can format the name with only the first letter capitalized. 
 - **Run custom business logic**. You can trigger downstream events in your cloud systems to send push notifications, update corporate databases, manage permissions, audit databases, and perform other custom actions.
 

articles/active-directory-b2c/configure-user-input.md

@@ -75,10 +75,10 @@ To provide a set list of values for the city attribute:
 1. Select your policy (for example, "B2C_1_SignupSignin") to open it.
 1. On the **Languages** page for the user flow, select the language that you want to customize.
 1. Under **Page-level resources files**, select **Local account sign up page**.
-1. Select **Download defaults** (or **Download overrides** if you have previously edited this language).
+1. Select **Download defaults** (or **Download overrides** if you previously edited this language).
 1. Create a `LocalizedCollections` attribute.
 
-The `LocalizedCollections` is an array of `Name` and `Value` pairs. The order for the items will be the order they are displayed. 
+The `LocalizedCollections` is an array of `Name` and `Value` pairs. The order for the items is the order they are displayed. 
 
 * `ElementId` is the user attribute that this `LocalizedCollections` attribute is a response to.
 * `Name` is the value that's shown to the user.
@@ -134,7 +134,7 @@ The `LocalizedCollections` is an array of `Name` and `Value` pairs. The order fo
 
 ## Overview
 
-You can gather initial data from your users by using the sign-up or sign-in user journey. Additional claims can be gathered later by using a profile edit user journey. Anytime Azure AD B2C gathers information directly from the user interactively, it uses the [self-asserted technical profile](self-asserted-technical-profile.md). In this sample, you:
+You can gather initial data from your users by using the sign-up or sign-in user journey. You can gather more claims later by using a profile edit user journey. Anytime Azure AD B2C gathers information directly from the user interactively, it uses the [self-asserted technical profile](self-asserted-technical-profile.md). In this sample, you:
 
 1. Define a "city" claim. 
 1. Ask the user for their city.

articles/active-directory-b2c/customize-ui.md

@@ -40,27 +40,27 @@ Azure AD B2C provide several built-in templates you can choose from to give your
 
 ### Ocean Blue
 
-Example of the Ocean Blue template rendered on sign up and sign in page:
+Example of the Ocean Blue template rendered on sign-up and sign-in page:
 
 ![Ocean Blue template screenshot](media/customize-ui/template-ocean-blue.png)
 
 ### Slate Gray
 
-Example of the Slate Gray template rendered on sign up sign in page:
+Example of the Slate Gray template rendered on sign-up sign-in page:
 
 ![Slate Gray template screenshot](media/customize-ui/template-slate-gray.png)
 
 ### Classic
 
-Example of the Classic template rendered on sign up sign in page:
+Example of the Classic template rendered on sign-up sign-in page:
 
 ![Classic template screenshot](media/customize-ui/template-classic.png)
 
 ### Company branding
 
 You can customize your Azure AD B2C pages with a banner logo, background image, and background color by using Microsoft Entra ID [Company branding](../active-directory/fundamentals/how-to-customize-branding.md). The company branding includes signing up, signing in, profile editing, and password resetting. 
 
-The following example shows a *Sign up and sign in* page with a custom logo, background image, using Ocean Blue template:
+The following example shows a *Sign-up and sign-in* page with a custom logo, background image, using Ocean Blue template:
 
 ![Branded sign-up/sign-in page served by Azure AD B2C](media/customize-ui/template-ocean-blue-branded.png)