PR review team comments

Author: kengaderdus

articles/active-directory-b2c/TOC.yml

@@ -43,6 +43,8 @@
     - name: Manage emergency access
       href: tenant-management-emergency-access-account.md
       displayName: break glass account, emergence account
+    - name: Check tenant creation permission 
+      href: tenant-management-check-tenant-creation-permission.md
     - name: Find tenant name and ID  
       href: tenant-management-read-tenant-name.md
       displayName: tenant name, tenant ID, tenant details    

articles/active-directory-b2c/custom-policies-series-branch-user-journey.md

@@ -183,7 +183,7 @@ You now need two new self-asserted technical profiles, one to collect the accoun
     1. Remove the `accountType` output claim, `<OutputClaim ClaimTypeReferenceId="accountType"/>`, from the `OutputClaims` collection. 
 
 
-## Step 4 - Update the User Journey Orchestration Steps
+## Step 4 - Update the User journey orchestration steps
 
 Now that you've set up your technical profiles, you need to update your user journey orchestration steps:
 
@@ -220,7 +220,7 @@ Now that you've set up your technical profiles, you need to update your user jou
 
 Follow the steps in [Upload custom policy file](custom-policies-series-hello-world.md#step-3---upload-custom-policy-file) to upload your policy file. If you're uploading a file with same name as the one already in the portal, make sure you select **Overwrite the custom policy if it already exists**.
 
-## Step 5 - Test the custom policy
+## Step 6 - Test the custom policy
 
 Follow the steps in [Test the custom policy](custom-policies-series-validate-user-input.md#step-6---test-the-custom-policy) to test your custom policy:
 

articles/active-directory-b2c/custom-policies-series-install-xml-extensions.md

@@ -57,7 +57,7 @@ Azure AD B2C extension  allows you to understand the organization of your policy
 > [!NOTE] 
 > The community has developed the VS Code extension for Azure AD B2C to help identity developers. The extension is not supported by Microsoft and is made available strictly as-is.
 
-## Next step
+## Next steps
 
 Next, learn:
 

articles/active-directory-b2c/custom-policies-series-overview.md

@@ -37,7 +37,7 @@ This how-to guide series consists of multiple articles. We recommend that you st
 |[Write your first Azure Active Directory B2C custom policy - Hello World!](custom-policies-series-hello-world.md) | Write your first Azure AD B2C custom policy. You'll return the message *Hello World!* in the JWT token. |
 |[Collect and manipulate user inputs by using Azure AD B2C custom policy](custom-policies-series-collect-user-input.md) | Learn how to collect inputs from users, and how to manipulate them.|
 |[Validate user inputs by using Azure Active Directory B2C custom policy](custom-policies-series-validate-user-input.md) | Learn how to validate user inputs by using techniques such as limiting user input options, regular expressions, predicates, and validation technical profiles|
-|[Create branching in user journey by using Azure Active Directory B2C custom policy](custom-policies-series-branch-in-user-journey.md) | Learn how to create different user experiences for different users based on the value of a claim.|
+|[Create branching in user journey by using Azure Active Directory B2C custom policy](custom-policies-series-branch-user-journey.md) | Learn how to create different user experiences for different users based on the value of a claim.|
 |[Validate custom policy files by using TrustFrameworkPolicy schema](custom-policies-series-install-xml-extensions.md)| Learn how to validate your custom files against a custom policy schema. You also learn how to easily navigate your policy files by using Azure AD B2C Visual Studio Code (VS Code) extension.|
 |[Call a REST API by using Azure Active Directory B2C custom policy](custom-policies-series-call-rest-api.md)| Learn how to write a custom policy that integrates with your own RESTful service.|
 |[Create and read a user account by using Azure Active Directory B2C custom policy](custom-policies-series-store-user.md)| Learn how to store into and read user details from Azure AD storage by using Azure AD B2C custom policy. You use the Azure Active Directory technical profile.|

articles/active-directory-b2c/custom-policies-series-sign-up-or-sign-in-federation.md

@@ -215,7 +215,7 @@ Replace:
 
 Notice the claims transformations we defined in [step 3.2](#step-32---define-claims-transformations) in the *OutputClaimsTransformations* collection.   
 
-### Step 3.4 - Create Azure AD Technical Profiles
+### Step 3.4 - Create Azure AD technical profiles
 
 Just like in sign-in with a local account, you need to configure the [Azure AD Technical Profiles](active-directory-technical-profile.md), which you use to connect to Azure AD storage, to store or read a user social account. 
 
@@ -292,7 +292,7 @@ Just like in sign-in with a local account, you need to configure the [Azure AD T
 
 1. Replace *B2C_1A_TokenSigningKeyContainer* with the token signing key you created in [Configure the signing](custom-policies-series-hello-world.md#step-1---configure-the-signing-and-encryption-keys).
 
-### Step 3.5 - Configure Content Definition 
+### Step 3.5 - Configure content definition 
 
 After a user signs in, you can collect some information from them by using a self-asserted technical profile. So, you need to configure content definition for the self-asserted technical profile.  
 
@@ -376,7 +376,7 @@ The claims provider we've added contains a self-asserted technical profile, *Sel
 
 Also, notice that we've added the content definition, *socialAccountsignupContentDefinition*, that we configured in [step 3.5](#step-35---configure-content-definition) in the metadata section.  
 
-## Step 4 - Update the User Journey Orchestration Steps
+## Step 4 - Update the User journey orchestration steps
 
 In the `ContosoCustomPolicy.XML` file, locate the `HelloWorldJourney` user journey and replace all the orchestration steps with the steps shown in the following code: 
 

articles/active-directory-b2c/custom-policies-series-sign-up-or-sign-in.md

@@ -162,7 +162,7 @@ When your policy runs, the user needs to see a user interface that allows them t
 - Configure a self-asserted technical profile, which displays the sign-in form to the user.  
 - Configure content definition for the sign-in user interface.
 
-### Step 2.1 - Configure a sign-in user interface Technical Profile 
+### Step 2.1 - Configure a sign-in user interface technical profile 
 
 In the `ContosoCustomPolicy.XML` file, locate the `SignInUser` technical profile and add a SelfAsserted Technical Profile after it by using the following code:   
 
@@ -197,7 +197,7 @@ Also, we've added the *SignInUser* OpenID Connect Technical Profile as a *Valida
 
 In the next step ([step 2.2](#step-22---configure-sign-in-interface-content-definition)), we configure a content definition that we'll use in this SelfAsserted Technical Profile.    
 
-### Step 2.2 - Configure sign-in interface Content Definition
+### Step 2.2 - Configure sign-in interface content definition
 
 In the `ContosoCustomPolicy.XML` file, locate the *ContentDefinitions* section, and then sign-in [Content Definition](contentdefinitions.md) by using the following code: 
 
@@ -217,7 +217,7 @@ In the `ContosoCustomPolicy.XML` file, locate the *ContentDefinitions* section,
 We've configured a content definition for our self-asserted technical profile, `SignupOrSigninContentDefinition`. We can specify it in the technical profile using the metadata element or specify it when we reference the technical profile in the orchestration steps. Previously, we learnt how to specify a content definition directly in the self-asserted technical profile, so in this article, we'll learn how to specify it when we reference the technical profile in the orchestration steps, [step 3](#step-3---update-the-user-journey-orchestration-steps).
 
 
-## Step 3 - Update the User Journey Orchestration Steps
+## Step 3 - Update the User journey orchestration steps
 
 In the `ContosoCustomPolicy.XML` file, locate the *HelloWorldJourney* user journey and replace all its orchestration steps collection with the following code: 
 

articles/active-directory-b2c/custom-policies-series-validate-user-input.md

@@ -1,7 +1,7 @@
 ---
 title: Validate user inputs by using Azure AD B2C custom policy 
 titleSuffix: Azure AD B2C
-description: Learn how to validate user inputs by using Azure Active Directory B2C custom policy. Learn how to validate user input by providing user input options. Learn how to validate user input by using Predicates. Learn how t validate user input by using Regular Expressions. Learn how to validate user input by using validation technical profiles    
+description: Learn how to validate user inputs by using Azure Active Directory B2C custom policy. Learn how to validate user input by limiting user input options. Learn how to validate user input by using Predicates. Learn how to validate user input by using Regular Expressions. Learn how to validate user input by using validation technical profiles    
 services: active-directory-b2c
 author: kengaderdus
 manager: CelesteDG
@@ -85,7 +85,7 @@ If you know all the possible values that a user can enter for a given input, you
         <OutputClaim ClaimTypeReferenceId="accountType" />
     ```
 
-## Step 2 - Validate user input by using Regular Expressions
+## Step 2 - Validate user input by using regular expressions
 
 When it's not possible to know all possible user input values in advance, you allow the user to input the data themselves. In this case, you can use *regular expressions (regex)* or [pattern](claimsschema.md#pattern) to dictate how a user input need to be formatted. For instance, an email must have the *at (@)* symbol and a *period (.)* somewhere in its text. 
 
@@ -126,7 +126,7 @@ When you declare a claim, custom policy allows you to define a regex, which the
         <OutputClaim ClaimTypeReferenceId="email" />
     ```
 
-## Step 3 - Validate user input by using Predicates
+## Step 3 - Validate user input by using predicates
 
 You've used regex to validate user inputs. However, regex have one weakness, that's, the error message displays until you correct input without showing you the specific requirement the input is missing. 
 
@@ -482,9 +482,9 @@ Use the following steps to learn how to validate user input by using validation
 
     :::image type="content" source="media/custom-policies-series-validate-user-input/screenshot-of-error-due-to-invalid-email-address.png" alt-text="screenshot of error due to invalid email address.":::
 
-## Next Steps
+## Next steps
 
 - Learn about [validation technical profile](validation-technical-profile.md).
 
--  Learn how to [Conditionally enable or disable Technical Profiles in Azure AD B2C custom policies](custom-policies-series-branch-in-user-journey.md)
+-  Learn how to [Conditionally enable or disable Technical Profiles in Azure AD B2C custom policies](custom-policies-series-branch-user-journey.md)
 

articles/active-directory-b2c/tenant-management-check-tenant-creation-permision.md renamed to articles/active-directory-b2c/tenant-management-check-tenant-creation-permission.md

@@ -59,4 +59,7 @@ Before you create an Azure AD B2C tenant, make sure that you've the permission t
 1. Review your **Tenant Creation** setting. If the settings is set to **No**, then contact your administrator to assign the tenant creator role to you. The setting is greyed out if you're not an administrator in the tenant.
 
 
-## Next steps 
+## Next steps 
+
+- [Read tenant name and ID](tenant-management-read-tenant-name.md)
+- [Clean up resources and delete tenant](tutorial-delete-tenant.md)