Update partner-grit-iam.md

Author: Gargi-Sinha

articles/active-directory-b2c/partner-grit-iam.md

@@ -30,24 +30,22 @@ To get started, ensure the following prerequisites are met:
 
 - A Grit IAM account. You can go to [Grit IAM B2B2C solution](https://www.gritiam.com/b2b2c) to get a demo.
 - An Azure AD subscription. If you don't have one, you can create a [free Azure account](https://azure.microsoft.com/free/).
-- An Azure AD B2C tenant linked to the Azure subscription. You can learn more at [Tutorial: Create an Azure Active Directory B2C tenant](tutorial-create-tenant.md).
-
+- An Azure AD B2C tenant linked to the Azure subscription. You can learn more at [Tutorial: Create an Azure Active Directory B2C tenant](tutorial-create-tenant.md). 
+- Configure your application in the Azure portal. 
+- In the Grit Onboarding portal, create a super admin for the tenant.
 
 ## Scenario description
 
 Contoso does business with end customers and large enterprises, like Fabrikam_big1 and Fabrikam_big2. There're small enterprise customers like Fabrikam_small1 and Fabrikam_small2 and direct business is done with end customers like Smith1 and Smith2.
 
-
 *Contoso* has web and mobile applications and develops new applications. The applications rely on user shared profile data such as, first name, last name, address, and email. They want to centralize the profile data, so applications aren't collecting and storing the data. They want to store the profile information in accordance with certain compliance and regulations.
 
-
 ![Screenshot that shows the architecture diagram of how the components are connected to each other.](./media/partner-grit-iam/grit-b2b2c-architecture.png)
 
 This integration is composed of the following components:
 
 - **Azure AD B2C Identity Experience Framework (IEF)**: An engine that executes user journeys, which can include validating credentials, performing MFA, checking user access. It's aided by the Azure AD database and the API layer, which's configured using XML.
 
-
 - **Grit API layer**: This layer exposes user profile data and metadata about organizations and applications. The data is stored in Azure AD and Cosmos DB.
 
 - **Grit Onboarding portal**: Used by admins to onboard applications and organizations.
@@ -70,18 +68,17 @@ Use the guidance provided in the following sections to get started with configur
 
 ### Step 1 - Setup infrastructure 
 
-
 To get started with setup:
 
 - Contact [Grit support](mailto:[email protected]) to obtain access.
-- For evaluation, the infrastructure is deployed in the Grit Azure subscription and you'll be given admin rights.
-- After the solution is purchased, Grit engineers install the dev, test, and production version in your Azure subscription.
+- For evaluation, the Grit support team will deploy the infrastructure in the Grit Azure subscription and they'll give you admin rights.
+- After you purchase the solution, Grit engineers will install the production version in your Azure subscription.
 - The infrastructure integrates with your virtual network (VNet) setup, supports APIM (third-party API management) and the firewall.
-- Implementation engineers can provide custom recommendations based on your infrastructure.
+- Grit implementation engineers can provide custom recommendations based on your infrastructure.
 
 ### Step 2 - Create admins in the Admin Portal
 
-The Grit Admin portal is to assign administrators access to the portal where they can perform the following tasks -
+Use the Grit Admin portal to assign administrators access to the portal where they can perform the following tasks -
 
 - Add other admins such as super, organization, application admin in the hierarchy depending on their permission level.
 
@@ -95,27 +92,19 @@ To learn how to assign admin roles, check the [tutorial.](https://app.archbee.co
 
 Use the Onboarding portal for one or more of your customers and their identity provider (IdP) that supports OpenID Connect (OIDC) and SAML. Onboard customers without an IdP, for local account authentication. For B2C applications, enable social authentications.
 
-
-Make sure you've Azure portal tenant access and the application is configured in the Azure portal.
-
-
->[!NOTE]
->To provide a walk-through or demo, some applications are pre-configured in the Azure AD tenant of the Onboarding portal.
-
 The Onboarding portal defines the claims per application and per organization. Thereafter, the portal creates an endpoint URL for the sign-in and sign-up user flow.
 
-
 To learn how to onboard an organization, check this [tutorial](https://app.archbee.com/doc/G_YZFq_VwvgMlmX-_efmX/8m90WVb2M6Yi0gCe7yor2).
 
 ### Step 4 - Integrate applications using OIDC or SAML
 
-The Grit Onboarding portal provides URLs to onboard the applications after onboarding a customer.
+After you onboard the customer, the Grit Onboarding portal provides URLs to onboard the applications.
 
 Learn [how your customers can sign up, sign in, and manage their profiles](add-sign-up-and-sign-in-policy.md?pivots=b2c-custom-policy). 
 
 ## Test the scenarios
 
-Run through the authentication scenarios in the applications.  Ensure there's a super admin for the tenant. You can use the Admin portal to change roles and user properties. Provide delegated access to Admin portal by inviting users.
+Check the authentication [scenarios](## Scenario description) in your applications. Use the Grit Admin portal to change roles and user properties. Provide delegated access to Admin portal by inviting users.
 
 ## Next steps