Update according to feedback from @lynneoconnor and @Jak-MS

Author: mlourie

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

@@ -12,54 +12,54 @@ ms.date: 06/21/2024
 ms.author: gasinh
 ms.subservice: b2c
 
-# Customer intent: I'm a developer integrating Azure Active Directory B2C with a third-party authentication provider. I want to learn how to configure Nok Nok S3 Authentication Suite as an identity provider (IdP) in Azure AD B2C. My goal is to implement FIDO Passkey authentication for my users.
+# Customer intent: I'm a developer integrating Azure AD B2C with a third-party authentication provider. I want to learn how to configure Nok Nok S3 Authentication Suite as an identity provider (IdP) in Azure AD B2C. My goal is to implement FIDO Passkey authentication for my users.
 ---
-# Tutorial: Configure Nok Nok S3 Authentication Suite with Azure Active Directory B2C for FIDO Passkey Authentication
+# Tutorial: Configure Nok Nok S3 Authentication Suite with Azure AD B2C for FIDO Passkey Authentication
 
-Learn to integrate the Nok Nok S3 Authentication Suite into your Azure Active Directory B2C (Azure AD B2C) tenant. The Nok Nok solution enables FIDO-certified multifactor authentication such as FIDO UAF, FIDO U2F, WebAuthn, and FIDO2 for mobile and web applications. The Nok Nok solution strengthens your security while maintaining an optimal with user experience.
+Learn to integrate the Nok Nok S3 Authentication Suite into your Azure Active Directory (AD) B2C tenant. The Nok Nok solution enables FIDO-certified multifactor authentication such as FIDO UAF, FIDO U2F, WebAuthn, and FIDO2 for mobile and web applications. The Nok Nok solution strengthens your security while maintaining an optimal user experience.
 
-Go to noknok.com to learn more: [Nok Nok Labs, Inc.](https://noknok.com/)
+Learn more at [Nok Nok](https://noknok.com/)
 
 ## Prerequisites
 
 To get started, you need:
 
-* An Azure subscription. If you don't have one, get an [Azure free account](https://azure.microsoft.com/free/)
-* An Azure AD B2C tenant linked to the Azure subscription [Tutorial: Create an Azure Active Directory B2C tenant](tutorial-create-tenant.md)
-* Nok Nok Cloud evaluation tenant to be used for registration and authentication
+* An Azure subscription. If you don't have one, get an [Azure free account](https://azure.microsoft.com/free/).
+* An Azure AD B2C tenant linked to the Azure subscription [Tutorial: Create an Azure AD B2C tenant](tutorial-create-tenant.md).
+* A Nok Nok Cloud evaluation tenant for FIDO registration and authentication.
 
 ## Scenario description
 
-To enable Passkey authentication for your users, enable Nok Nok as an identity provider (IdP) in your Azure AD B2C (AAD B2C) tenant. The Nok Nok integration includes the following components:
+To enable Passkey authentication for your users, enable Nok Nok as an identity provider (IdP) in your Azure AD B2C tenant. The Nok Nok integration includes the following components:
 
-* **Azure AD B2C** – authorization server that verifies user credentials
-* **Web and mobile applications** – mobile or web apps to protect with Nok Nok solutions and AAD B2C
-* **Nok Nok Tutorial Web App** – application used to register the passkey on your device
-* **Nok Nok Sign in App** – application used for authenticating AAD B2C applications using passkey.
+* **Azure AD B2C** – authorization server that verifies user credentials.
+* **Web and mobile applications** – mobile or web apps to protect with Nok Nok solutions and Azure AD B2C.
+* **Nok Nok Tutorial Web App** – application to register the passkey on your device.
+* **Nok Nok Sign in App** – application for authenticating Azure AD B2C applications using passkey.
 
 
-The following diagram illustrates the Nok Nok solution as an IdP for AAD B2C by using OpenID Connect (OIDC) for Passkey authentication.
+The following diagram illustrates the Nok Nok solution as an IdP for Azure AD B2C by using OpenID Connect (OIDC) for Passkey authentication.
 
-![Diagram of Nok Nok as IdP for AAD B2C using OpenID Connect (OIDC) for Passkey authentication.](./media/partner-nok-nok/nok-nok-architecture-diagram.png)
+![Diagram of Nok Nok as IdP for Azure AD B2C using OpenID Connect (OIDC) for Passkey authentication.](./media/partner-nok-nok/nok-nok-architecture-diagram.png)
 
 ### Scenario 1: Passkey Registration
 1. The user navigates to the Nok Nok Tutorial Web App using the link provided by Nok Nok.
-2. They enter their AAD B2C username and default tutorial app password.
-3. They are prompted to register the passkey.
-4. The Nok Nok server validates the passkey credential and confirms successful registration to the user.
-5. The passkey is now registered on the user's device and is ready to authenticate.
+2. The user enters their Azure AD B2C username and default tutorial app password.
+3. The user receives a prompt to register the passkey.
+4. The Nok Nok server validates the passkey credential and confirms successful passkey registration to the user.
+5. The passkey on the user's device is ready for authentication.
 
 ### Scenario 2: Passkey Authentication
-1. The user clicks on the Sign in with Nok Nok Cloud button on the AAD B2C Sign in page.
-2. AAD B2C redirects the user to the Nok Nok Signin App.
+1. The user selects the Sign in with Nok Nok Cloud button on the Azure AD B2C Sign in page.
+2. Azure AD B2C redirects the user to the Nok Nok Signin App.
 3. User authenticates with their passkey.
-4. The Nok Nok server validates the passkey assertion and sends an OIDC authentication response to AAD B2C.
-5. Based on the authentication result, AAD B2C either grants or denies access to the target application.
+4. The Nok Nok server validates the passkey assertion and sends an OIDC authentication response to Azure AD B2C.
+5. Based on the authentication result, Azure AD B2C either grants or denies access to the target application.
 
 
 ## Get started with Nok Nok
 
-1. Go to noknok.com [Contact](https://noknok.com/contact/).
+1. [Contact](https://noknok.com/contact/) Nok Nok.
 2. Fill out the form for a Nok Nok tenant.
 3. An email arrives with tenant access information and links to documentation.
 4. Use the Nok Nok integration documentation to complete the tenant OIDC configuration.
@@ -70,10 +70,10 @@ Use the following instructions to add and configure an IdP, and then configure a
 
 ### Add a new Identity provider
 
-For the following instructions, use the directory with the AAD B2C tenant. To add a new IdP:
+For the following instructions, use the directory with the Azure AD B2C tenant. To add a new IdP:
 
-1. Sign in to the [Azure portal](https://portal.azure.com/#home) as at least as the B2C IEF Policy Administrator of the AAD B2C tenant.
-2. In the portal toolbar, select the **Directories + subscriptions**.
+1. Sign in to the [Azure portal](https://portal.azure.com/#home) as at least as the B2C IEF Policy Administrator of the Azure AD B2C tenant.
+2. In the portal toolbar, select **Directories + subscriptions**.
 3. On **Portal settings, Directories + subscriptions**, in the **Directory name** list, locate the Azure AD B2C directory.
 4. Select **Switch**.
 5. In the top-left corner of the Azure portal, select **All services**.
@@ -88,7 +88,7 @@ To configure an IdP:
 
 1. Select **Identity provider type** > **OpenID Connect (Preview)**.
 2. For **Name**, enter the Nok Nok Authentication Provider, or another name.
-3. For **Metadata URL**, enter the following url after replacing the placeholder with the tenant id provided by Nok Nok: `https://cloud.noknok.com/<tenant_id>/webapps/nnlfed/realms/<tenant_id>/.well-known/openid-configuration`.
+3. For **Metadata URL**, enter the following URL after replacing the placeholder with the tenant ID provided by Nok Nok: `https://cloud.noknok.com/<tenant_id>/webapps/nnlfed/realms/<tenant_id>/.well-known/openid-configuration`.
 4. For **Client Secret**, use the Client Secret from Nok Nok.
 5. For **Client ID**, use the Client ID provided by Nok Nok.
 6. For **Scope**, use **openid**.
@@ -102,27 +102,27 @@ To configure an IdP:
 
 For the following instructions, Nok Nok is a new OIDC IdP in the B2C identity providers list.
 
-1. In your AAD B2C tenant, under **Policies**, select **User flows**.
+1. In your Azure AD B2C tenant, under **Policies**, select **User flows**.
 2. Select **New**.
 3. Select **Sign up and sign in**.
 4. Select a **Version**.
 5. Select **Create**.
 6. Enter a policy **Name**.
 7. In **Identity providers**, select the created Nok Nok IdP.
-8. Check **Email signup** under Local accounts to display an intermediate AAD B2C signin/signup page with a button that redirects the user to the Nok Nok Signin App.
+8. Check **Email signup** under **Local accounts** to display an intermediate Azure AD B2C signin/signup page with a button that redirects the user to the Nok Nok Signin App.
 9. Leave the **Multi-factor Authentication** field.
-10. Click on **Create** to save.
+10. Click **Create** to save.
 
 ## Test the user flow
 
-1. Open the AAD B2C tenant. Under **Policies** select **Identity Experience Framework**.
+1. Open the Azure AD B2C tenant. Under **Policies**, select **Identity Experience Framework**.
 2. Select the created **SignUpSignIn**.
 3. Select **Run user flow**.
 4. For **Application**, select the registered app. The example is JWT.
-5. For **Reply URL**, select the redirect URL of the application selected at the previous step.
+5. For **Reply URL**, select the redirect URL of the application that you previously selected at the previous step.
 6. Select **Run user flow**.
-7. Perform signin using the AAD B2C username and the previously registered passkey for the same user.
-8. Verify the token received after authentication.
+7. Perform signin using the Azure AD B2C username and the passkey that you previously registered for the same user.
+8. Verify that you received the token after authentication.
 
 If the flow is incomplete, confirm the user is or isn't saved in the directory.