@msmimart feadback

Author: yoelhor

articles/active-directory-b2c/configure-tokens-custom-policy.md

@@ -9,7 +9,7 @@ manager: celestedg
 ms.service: active-directory
 ms.workload: identity
 ms.topic: conceptual
-ms.date: 05/04/2020
+ms.date: 05/07/2020
 ms.author: mimart
 ms.subservice: B2C
 ---
@@ -87,5 +87,5 @@ The following values are set in the previous example:
 ## Next steps
 
 - Learn more about [Azure AD B2C session](session-overview.md).
-- Learn how to [configure session behavior in custom policy](session-behavior-custom-policy.md).
+- Learn how to [configure session behavior in custom policies](session-behavior-custom-policy.md).
 - Reference: [JwtIssuer](jwt-issuer-technical-profile.md).

articles/active-directory-b2c/configure-tokens.md

@@ -8,7 +8,7 @@ manager: celestedg
 ms.service: active-directory
 ms.workload: identity
 ms.topic: conceptual
-ms.date: 05/04/2020
+ms.date: 05/07/2020
 ms.author: mimart
 ms.subservice: B2C
 ---

articles/active-directory-b2c/custom-policy-reference-sso.md

@@ -9,7 +9,7 @@ manager: celestedg
 ms.service: active-directory
 ms.workload: identity
 ms.topic: reference
-ms.date: 05/04/2020
+ms.date: 05/07/2020
 ms.author: mimart
 ms.subservice: B2C
 ---
@@ -18,7 +18,7 @@ ms.subservice: B2C
 
 [!INCLUDE [active-directory-b2c-advanced-audience-warning](../../includes/active-directory-b2c-advanced-audience-warning.md)]
 
-The [Single sign-on (SSO) session](session-overview.md) management uses the same semantics as any other technical profile in custom policies. When an orchestration step is executed, the technical profile associated with the step is queried for a `UseTechnicalProfileForSessionManagement` reference. If one exists, the referenced SSO session provider is then checked to see if the user is a session participant. If so, the SSO session provider is used to repopulate the session. Similarly, when the execution of an orchestration step is complete, the provider is used to store information in the session if an SSO session provider has been specified.
+[Single sign-on (SSO) session](session-overview.md) management uses the same semantics as any other technical profile in custom policies. When an orchestration step is executed, the technical profile associated with the step is queried for a `UseTechnicalProfileForSessionManagement` reference. If one exists, the referenced SSO session provider is then checked to see if the user is a session participant. If so, the SSO session provider is used to repopulate the session. Similarly, when the execution of an orchestration step is complete, the provider is used to store information in the session if an SSO session provider has been specified.
 
 Azure AD B2C has defined a number of SSO session providers that can be used:
 
@@ -168,4 +168,4 @@ The following `SM-Saml-issuer` technical profile is used by [SAML issuer technic
 ## Next steps
 
 - Learn more about [Azure AD B2C session](session-overview.md).
-- Learn how to [configure session behavior in custom policy](session-behavior-custom-policy.md).
+- Learn how to [configure session behavior in custom policies](session-behavior-custom-policy.md).

articles/active-directory-b2c/jwt-issuer-technical-profile.md

@@ -9,7 +9,7 @@ manager: celestedg
 ms.service: active-directory
 ms.workload: identity
 ms.topic: reference
-ms.date: 04/28/2020
+ms.date: 05/07/2020
 ms.author: mimart
 ms.subservice: B2C
 ---

articles/active-directory-b2c/session-behavior-custom-policy.md

@@ -8,7 +8,7 @@ manager: celestedg
 ms.service: active-directory
 ms.workload: identity
 ms.topic: conceptual
-ms.date: 05/04/2020
+ms.date: 05/07/2020
 ms.author: mimart
 ms.subservice: B2C
 ---
@@ -30,7 +30,7 @@ You can use the following properties to manage web application sessions:
 
 ## Configure the properties
 
-To change your session behavior and SSO configurations, you add a **UserJourneyBehaviors** element inside of the [RelyingParty](relyingparty.md) element.  The **UserJourneyBehaviors** element must immediately follow the **DefaultUserJourney**. The inside of your **UserJourneyBehavors** element should look like this example:
+To change your session behavior and SSO configurations, you add a **UserJourneyBehaviors** element inside of the [RelyingParty](relyingparty.md) element.  The **UserJourneyBehaviors** element must immediately follow the **DefaultUserJourney**. Your **UserJourneyBehavors** element should look like this example:
 
 ```XML
 <UserJourneyBehaviors>
@@ -47,18 +47,18 @@ To change your session behavior and SSO configurations, you add a **UserJourneyB
 When you redirect the user to the Azure AD B2C sign-out endpoint (for both OAuth2 and SAML protocols), Azure AD B2C clears the user's session from the browser.  To allow [Single sign-out](session-overview.md#single-sign-out), set the `LogoutUrl` of the application from the Azure portal:
 
 1. Navigate to the [Azure portal](https://portal.azure.com).
-1. Choose your Active B2C directory by clicking your account in the top right corner of the page.
-1. From the left hand navigation panel, choose **Azure AD B2C**, select **App registrations**, and then select your application.
+1. Choose your Azure AD B2C directory by clicking your account in the top right corner of the page.
+1. In the left menu, choose **Azure AD B2C**, select **App registrations**, and then select your application.
 1. Select **Settings**, select **Properties**, and then find the **Logout URL** text box. 
 
 ### Configure the token issuer 
 
-To support sing-sign out, the token issuer technical profiles, for both JWT and SAML must specify:
+To support single sign-out, the token issuer technical profiles for both JWT and SAML must specify:
 
-1. The protocol name, such as `<Protocol Name="OpenIdConnect" />`
-1. Reference to the session technical profile, such as `UseTechnicalProfileForSessionManagement ReferenceId="SM-jwt-issuer" />`.
+- The protocol name, such as `<Protocol Name="OpenIdConnect" />`
+- The reference  to the session technical profile, such as `UseTechnicalProfileForSessionManagement ReferenceId="SM-jwt-issuer" />`.
 
-The following example illustrates the JWT and SMAL token issuers with single sign-out:
+The following example illustrates the JWT and SAML token issuers with single sign-out:
 
 ```xml
 <ClaimsProvider>

articles/active-directory-b2c/session-behavior.md

@@ -8,7 +8,7 @@ manager: celestedg
 ms.service: active-directory
 ms.workload: identity
 ms.topic: conceptual
-ms.date: 05/04/2020
+ms.date: 05/07/2020
 ms.author: mimart
 ms.subservice: B2C
 ---

articles/active-directory-b2c/session-overview.md

@@ -8,7 +8,7 @@ manager: celestedg
 ms.service: active-directory
 ms.workload: identity
 ms.topic: conceptual
-ms.date: 05/04/2020
+ms.date: 05/07/2020
 ms.author: mimart
 ms.subservice: B2C
 ---
@@ -101,7 +101,7 @@ The sign-out clears the user's single sign-on state with Azure AD B2C, but it mi
 
 
 > [!NOTE]
-> This feature is limited to [custom policy](custom-policy-overview.md).
+> This feature is limited to [custom policies](custom-policy-overview.md).
 
 When you redirect the user to the Azure AD B2C sign-out endpoint (for both OAuth2 and SAML protocols), Azure AD B2C clears the user's session from the browser. However, the user might still be signed in to other applications that use Azure AD B2C for authentication. To enable those applications to sign the user out simultaneously, Azure AD B2C sends an HTTP GET request to the registered `LogoutUrl` of all the applications that the user is currently signed in to.
 
@@ -111,4 +111,4 @@ Applications must respond to this request by clearing any session that identifie
 ## Next steps
 
 - Learn how to [configure session behavior in user flow](session-behavior.md).
-- Learn how to [configure session behavior in custom policy](session-behavior-custom-policy.md).
+- Learn how to [configure session behavior in custom policies](session-behavior-custom-policy.md).