fix correctness in direct signin

Author: kengaderdus

articles/active-directory-b2c/direct-signin.md

@@ -1,37 +1,37 @@
 ---
-title: Set up direct sign-in using Azure Active Directory B2C  
-description: Learn how to prepopulate the sign-in name or redirect straight to a social identity provider.
+title: Set up direct sign in using Azure Active Directory B2C  
+description: Learn how to prepopulate the sign in name or redirect straight to a social identity provider.
 services: active-directory-b2c
 author: kengaderdus
 manager: CelesteDG
 
 ms.service: active-directory
 ms.workload: identity
 ms.topic: how-to
-ms.date: 12/14/2020
+ms.date: 03/31/2022
 ms.custom: project-no-code
 ms.author: kengaderdus
 ms.subservice: B2C
 zone_pivot_groups: b2c-policy-type
 ---
 
-# Set up direct sign-in using Azure Active Directory B2C
+# Set up direct sign in using Azure Active Directory B2C
 
 [!INCLUDE [active-directory-b2c-choose-user-flow-or-custom-policy](../../includes/active-directory-b2c-choose-user-flow-or-custom-policy.md)]
 
-When setting up sign in for your application using Azure Active Directory B2C (Azure AD B2C), you can prepopulate the sign in name or directly sign in to a specific social identity provider, such as Facebook, LinkedIn, or a Microsoft account.
+When you set up sign-in for your application using Azure Active Directory B2C (Azure AD B2C), you can prepopulate the sign-in name or directly sign in to a specific social identity provider, such as Facebook, LinkedIn, or a Microsoft account.
 
-## Prepopulate the sign-in name
+## Prepopulate the sign in name
 
-During a sign in user journey, a relying party application may target a specific user or domain name. When targeting a user, an application can specify, in the authorization request, the `login_hint` query parameter with the user sign in name. Azure AD B2C automatically populates the sign in name, while the user only needs to provide the password.
+During a sign-in user journey, a relying party application may target a specific user or domain name. When targeting a user, an application can specify, in the authorization request, the `login_hint` query parameter with the user sign-in name. Azure AD B2C automatically populates the sign-in name, while the user only needs to provide the password.
 
 ![Sign up sign in page with login_hint query param highlighted in URL](./media/direct-signin/login-hint.png)
 
-The user is able to change the value in the sign in textbox.
+The user is able to change the value in the sign-in textbox.
 
 ::: zone pivot="b2c-custom-policy"
 
-To support login hint parameter, override the `SelfAsserted-LocalAccountSignin-Email` technical profile. In the `<InputClaims>` section, set the DefaultValue of the signInName claim to `{OIDC:LoginHint}`. The `{OIDC:LoginHint}` variable contains the value of the `login_hint` parameter. Azure AD B2C reads the value of the signInName claim and pre-populates the signInName textbox.
+To support sign in hint parameter, override the `SelfAsserted-LocalAccountSignin-Email` technical profile. In the `<InputClaims>` section, set the DefaultValue of the signInName claim to `{OIDC:LoginHint}`. The `{OIDC:LoginHint}` variable contains the value of the `login_hint` parameter. Azure AD B2C reads the value of the signInName claim and pre-populates the signInName textbox.
 
 ```xml
 <ClaimsProvider>
@@ -51,7 +51,7 @@ To support login hint parameter, override the `SelfAsserted-LocalAccountSignin-E
 
 ## Redirect sign in to a social provider
 
-If you configured the sign in journey for your application to include social accounts, such as Facebook, LinkedIn, or Google, you can specify the `domain_hint` parameter. This query parameter provides a hint to Azure AD B2C about the social identity provider that should be used for sign in. For example, if the application specifies `domain_hint=facebook.com`, sign in goes directly to the Facebook sign in page.
+If you configured the sign-in journey for your application to include social accounts, such as Facebook, LinkedIn, or Google, you can specify the `domain_hint` parameter. This query parameter provides a hint to Azure AD B2C about the social identity provider that should be used for sign-in. For example, if the application specifies `domain_hint=facebook.com`, sign in goes directly to the Facebook sign in page.
 
 ![Sign up sign in page with domain_hint query param highlighted in URL](./media/direct-signin/domain-hint.png)