Update partner-bindid.md

Author: Gargi-Sinha

articles/active-directory-b2c/partner-bindid.md

@@ -59,7 +59,7 @@ To get started, you'll need:
 
 ::: zone-end
 
-### Part 1 - Create an application registration in BindID
+### Step 1 - Create an application registration in BindID
 
 From [Applications](https://admin.bindid-sandbox.io/console/#/applications) to configure your tenant application in BindID, the following information is needed
 
@@ -75,7 +75,7 @@ From [Applications](https://admin.bindid-sandbox.io/console/#/applications) to c
 
 ::: zone pivot="b2c-user-flow"
 
-### Part 2 - Add a new Identity provider in Azure AD B2C
+### Step 2 - Add a new Identity provider in Azure AD B2C
 
 1. Sign-in to the [Azure portal](https://portal.azure.com/#home) as the global administrator of your Azure AD B2C tenant.
 
@@ -91,7 +91,7 @@ From [Applications](https://admin.bindid-sandbox.io/console/#/applications) to c
 
 7. Select **Add**.
 
-### Part 3 - Configure an Identity provider
+### Step 3 - Configure an Identity provider
 
 1. Select **Identity provider type > OpenID Connect**
 
@@ -101,8 +101,8 @@ From [Applications](https://admin.bindid-sandbox.io/console/#/applications) to c
   |:---------|:---------|
   |Name     |Enter BindID – Passwordless or a name of your choice|
   |Metadata URL| `https://signin.bindid-sandbox.io/.well-known/openid-configuration` |
-  |Client ID|The application ID from the BindID admin UI captured in **Part 1**|
-  |Client Secret|The application Secret from the BindID admin UI captured in **Part 1**|
+  |Client ID|The application ID from the BindID admin UI captured in **Step 1**|
+  |Client Secret|The application Secret from the BindID admin UI captured in **Step 1**|
   |Scope|OpenID email|
   |Response type|Code|
   |Response mode|form_post|
@@ -112,7 +112,7 @@ From [Applications](https://admin.bindid-sandbox.io/console/#/applications) to c
 
 3. Select **Save** to complete the setup for your new OIDC Identity provider.  
 
-### Part 4 - Create a user flow policy
+### Step 4 - Create a user flow policy
 
 You should now see BindID as a new OIDC Identity provider listed within your B2C identity providers.  
 
@@ -146,7 +146,7 @@ You should now see BindID as a new OIDC Identity provider listed within your B2C
 
 ::: zone pivot="b2c-custom-policy"
 
-### Part 2 - Create a BindID policy key
+### Step 2 - Create a BindID policy key
 
 Store the client secret that you previously recorded in your Azure AD B2C tenant.
 
@@ -175,7 +175,7 @@ Store the client secret that you previously recorded in your Azure AD B2C tenant
 >[!NOTE]
 >In Azure Active Directory B2C, [**custom policies**](./user-flow-overview.md) are designed primarily to address complex scenarios. For most scenarios, we recommend that you use built-in [**user flows**](./user-flow-overview.md).
 
-### Part 3- Configure BindID as an Identity provider
+### Step 3- Configure BindID as an Identity provider
 
 To enable users to sign in using BindID, you need to define BindID as a claims provider that Azure AD B2C can communicate with through an endpoint. The endpoint provides a set of claims that are used by Azure AD B2C to verify a specific user has authenticated using digital identity available on their device, proving the user’s identity.
 
@@ -232,7 +232,7 @@ You can define BindID as a claims provider by adding it to the **ClaimsProvider*
 
 5. Save the file.
 
-### Part 4 - Add a user journey
+### Step 4 - Add a user journey
 
 At this point, the identity provider has been set up, but it's not yet available in any of the sign-in pages. If you don't have your own custom user journey, create a duplicate of an existing template user journey, otherwise continue to the next step.
 
@@ -246,7 +246,7 @@ At this point, the identity provider has been set up, but it's not yet available
 
 5. Rename the ID of the user journey. For example, `ID=CustomSignUpSignIn`
 
-### Part 5 - Add the identity provider to a user journey
+### Step 5 - Add the identity provider to a user journey
 
 Now that you have a user journey, add the new identity provider to the user journey.
 
@@ -274,7 +274,7 @@ The following XML demonstrates orchestration steps of a user journey with the id
 </OrchestrationStep>
 ```
 
-### Part 6 - Configure the relying party policy
+### Step 6 - Configure the relying party policy
 
 The relying party policy, for example [SignUpSignIn.xml](https://github.com/Azure-Samples/active-directory-b2c-custom-policy-starterpack/blob/master/SocialAccounts/SignUpOrSignin.xml), specifies the user journey which Azure AD B2C will execute. You can also control what claims are passed to your application by adjusting the **OutputClaims** element of the **PolicyProfile** TechnicalProfile element.  In this sample, the application will receive the user attributes such as display name, given name, surname, email, objectId, identity provider, and tenantId.  
 
@@ -298,7 +298,7 @@ The relying party policy, for example [SignUpSignIn.xml](https://github.com/Azur
   </RelyingParty>
 ```
 
-### Part 7 - Upload the custom policy
+### Step 7 - Upload the custom policy
 
 1. Sign in to the [Azure portal](https://portal.azure.com/#home).
 
@@ -313,7 +313,7 @@ The relying party policy, for example [SignUpSignIn.xml](https://github.com/Azur
 6. Select **Upload Custom Policy**, and then upload the two policy files that you changed, in the following order: the extension policy, for example `TrustFrameworkExtensions.xml`, then the relying party policy, such as `SignUpSignIn.xml`.
 
 
-### Part 8 - Test your custom policy
+### Step 8 - Test your custom policy
 
 1. Open the Azure AD B2C tenant and under Policies select **Identity Experience Framework**.