Update britive-tutorial.md as per the new Britive UI

docs/identity/saas-apps/britive-provisioning-tutorial.md

@@ -43,26 +43,26 @@ The scenario outlined in this article assumes that you already have the followin
 
 ## Step 2: Configure Britive to support provisioning with Microsoft Entra ID
 
-The application has to be manually configured using the steps provided in the this section:
-1. Login to Britive application with administrator privileges
-1. Select **Admin->User Administration->Identity Providers**
-1. Select **Add Identity Provider**. Enter the name and description. Select Add Identity Provider button.
+The application has to be manually configured using the steps provided in this section:
+1. Login to the Britive application with administrator privileges
+1. Select **Admin->Identity Management->Identity Providers**
+1. Select **Add Identity Provider**. Enter the name and description. Select the **Add** button.
 
 	![Identity Provider](media/britive-provisioning-tutorial/identity.png)
 
-1. A configuration page similar to one displayed below is shown.
+1. A configuration page similar to the one displayed below is shown.
 
 	![Configuration Page](media/britive-provisioning-tutorial/configuration.png)
 
-1. Select **SCIM** tab. Change the SCIM provider from Generic to Azure and save the changes. Copy the SCIM URL and note it down. These values are entered in the **Tenant URL** boxes on the Provisioning tab of your Britive application.
+1. Select **SCIM** tab. Change the SCIM provider from Generic to Azure and save the changes. Copy the **SCIM URL** and note it down. These values are entered in the **Tenant URL** boxes on the Provisioning tab of your Britive application.
 
 	![SCIM Page](media/britive-provisioning-tutorial/scim.png)
 
-1. Select **Create Token**. Select the validity of the token as required and select Create Token button.
+1. Select **Create Token**. Select the validity of the token as required and select the **Create Token** button.
 
 	![Create Token](media/britive-provisioning-tutorial/create-token.png)
 
-1. Copy the token generated and note it down. Select OK. Note that the user isn't able to see the token again. Select Re-Create button to generate a new token if needed. These values are entered in the **Secret Token** and Tenant URL boxes on the Provisioning tab of your getAbstract application.
+1. Copy the token generated and note it down. Select OK. Note that the user isn't able to see the token again. Select **Recreate token** button to generate a new token if needed. These values are entered in the **Secret Token** and Tenant URL boxes on the Provisioning tab of your getAbstract application.
 
 	![Copy Token](media/britive-provisioning-tutorial/copy-token.png) 
 
@@ -71,7 +71,7 @@ The application has to be manually configured using the steps provided in the th
 
 ## Step 3: Add Britive from the Microsoft Entra application gallery
 
-Add Britive from the Microsoft Entra application gallery to start managing provisioning to Britive. If you have previously setup Britive for SSO, you can use the same application. However, we recommend that you create a separate app when testing out the integration initially. Learn more about adding an application from the gallery [here](~/identity/enterprise-apps/add-application-portal.md). 
+Add Britive from the Microsoft Entra application gallery to start managing provisioning to Britive. If you have previously set up Britive for SSO, you can use the same application. However, we recommend that you create a separate app when testing out the integration initially. Learn more about adding an application from the gallery [here](~/identity/enterprise-apps/add-application-portal.md). 
 
 ## Step 4: Define who is in scope for provisioning 
 

docs/identity/saas-apps/britive-tutorial.md

@@ -42,7 +42,7 @@ To configure the integration of Britive into Microsoft Entra ID, you need to add
 1. Sign in to the [Microsoft Entra admin center](https://entra.microsoft.com) as at least a [Cloud Application Administrator](~/identity/role-based-access-control/permissions-reference.md#cloud-application-administrator).
 1. Browse to **Entra ID** > **Enterprise apps** > **New application**.
 1. In the **Add from the gallery** section, type **Britive** in the search box.
-1. Select **Britive** from results panel and then add the app. Wait a few seconds while the app is added to your tenant.
+1. Select **Britive** from the results panel and then add the app. Wait a few seconds while the app is added to your tenant.
 
  [!INCLUDE [sso-wizard.md](~/identity/saas-apps/includes/sso-wizard.md)]
 
@@ -103,45 +103,43 @@ Follow these steps to enable Microsoft Entra SSO.
 
 1. Select **Admin->Identity Management->Identity Providers** from the navigation menu.
 
-1. Select **ADD IDENTITY PROVIDER**. Enter the name and description. Select the **Add** button.
+1. Select **Add Identity Provider**. Enter the name and description. Select the **Add** button.
 
     ![Screenshot of Add Identity Provider.](./media/britive-tutorial/security.png)
 
 1. Select **Manage** for the Azure identity provider and select **SSO Configuration**.
 
    ![Screenshot of SSO Configuration Settings.](./media/britive-tutorial/configuration.png)
 
-   1. Copy **Audience/Entity ID** value and paste it into the **Identifier (Entity ID)** text box in the **Basic SAML Configuration** section.
-   1. Copy **Initiate SSO URL** value and paste it into the **Sign on URL** text box in the **Basic SAML Configuration** section.
    1. Change the **SSO Provider** from **Generic** to **Azure**.
-   1. Copy the **Audience/Entity ID** value and paste it into the Identifier (Entity ID) text box in the Basic SAML Configuration section in the Azure portal.
-   1. Copy the **Initiate SSO URL** value and paste it into the Sign on URL text box in the Basic SAML Configuration section in the Azure portal.
-   1. Select **UPLOAD SAML METADATA** to upload the downloaded **metadata XML** file from the Azure portal. After uploading the metadata file the above values are auto- populated and save changes.
+   2. Copy the **Audience/Entity ID** value and paste it into the **Identifier (Entity ID)** text box in the **Basic SAML Configuration** section.
+   3. Copy **Initiate SSO URL** value and paste it into the **Sign on URL** text box in the **Basic SAML Configuration** section.
+   4. Select **Upload SAML Metadata** to upload the downloaded **metadata XML** file from the Azure portal. After uploading the metadata file the above values are auto-populated and save changes.
 
 
 ### Create Britive test user
 
-1. Log in to the Britive with administrator privileges in a different web browser window.
+1. Log in to Britive with administrator privileges in a different web browser window.
 
 2. Select **Admin** Settings Icon and select **Identity Management**.
 
-3. Select **ADD USER** from the **Users** tab.
+3. Select **Add User** from the **Users** tab.
 
 4. Fill in all the necessary details of the user according to your organization's requirements and select **Add**. Make sure to select Azure from the **Identity Providers** list.
 
 > [!NOTE]
->Britive also supports automatic user provisioning, you can find more details [here](./britive-provisioning-tutorial.md) on how to configure automatic user provisioning.
+>Britive also supports automatic user provisioning; you can find more details [here](./britive-provisioning-tutorial.md) on how to configure automatic user provisioning.
 
 ## Test SSO
 
-In this section, you test your Microsoft Entra single sign-on configuration with following options. 
+In this section, you test your Microsoft Entra single sign-on configuration with the following options. 
 
-* Select **Test this application**, this option redirects to Britive Sign-on URL where you can initiate the login flow. 
+* Select **Test this application**, this option redirects to the Britive Sign-on URL, where you can initiate the login flow. 
 
 * Go to Britive Sign-on URL directly and initiate the login flow from there.
 
-* You can use Microsoft My Apps. When you select the Britive tile in the My Apps, this option redirects to Britive Sign-on URL. For more information, see [Microsoft Entra My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps).
+* You can use Microsoft My Apps. When you select the Britive tile in the My Apps, this option redirects to the Britive Sign-on URL. For more information, see [Microsoft Entra My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps).
 
 ## Related content
 
-Once you configure Britive you can enforce session control, which protects exfiltration and infiltration of your organization’s sensitive data in real time. Session control extends from Conditional Access. [Learn how to enforce session control with Microsoft Defender for Cloud Apps](/cloud-app-security/proxy-deployment-aad).
+Once you configure Britive, you can enforce session control, which protects exfiltration and infiltration of your organization’s sensitive data in real time. Session control extends from Conditional Access. [Learn how to enforce session control with Microsoft Defender for Cloud Apps](/cloud-app-security/proxy-deployment-aad).