Review comments

Author: kengaderdus

articles/active-directory/external-identities/customers/how-to-register-ciam-app.md

@@ -24,7 +24,7 @@ During app registration, you specify the redirect URI. The redirect URI is the e
 
 Azure AD for customers supports authentication for various modern application architectures, for example web app or single-page app. The interaction of each application type with the customer tenant is different, therefore, you must specify the type of application you want to register.
 
-In this article, you’ll learn how to register an application in your customer tenant.
+In this article, you learn how to register an application in your customer tenant.
 
 ## Prerequisites
 
@@ -56,7 +56,7 @@ The following steps show you how to register your SPA in the Microsoft Entra adm
 
 1. In the **Register an application page** that appears, enter your application's registration information:
 
-    1. In the **Name** section, enter a meaningful application name that will be displayed to users of the app, for example *ciam-client-app*.
+    1. In the **Name** section, enter a meaningful application name that is displayed to users of the app, for example *ciam-client-app*.
 
     1. Under **Supported account types**, select **Accounts in this organizational directory only**.
 
@@ -75,7 +75,7 @@ This app signs in users. You can add delegated permissions to it, by following t
 
 ### Grant API permissions (optional):
 
-If your SPA needs to call an API, you must grant your SPA API permissions so it can to call the API. You must also [register the web API](how-to-register-ciam-app.md?tabs=webapi) that you need to call. 
+If your SPA needs to call an API, you must grant your SPA API permissions so it can call the API. You must also [register the web API](how-to-register-ciam-app.md?tabs=webapi) that you need to call. 
 
 [!INCLUDE [grant permisions for calling an API](../customers/includes/register-app/grant-api-permission-call-api.md)] 
 
@@ -109,7 +109,7 @@ The following steps show you how to register your web app in the Microsoft Entra
 
 1. In the **Register an application page** that appears, enter your application's registration information:
 
-    1. In the **Name** section, enter a meaningful application name that will be displayed to users of the app, for example *ciam-client-app*.
+    1. In the **Name** section, enter a meaningful application name that is displayed to users of the app, for example *ciam-client-app*.
 
     1. Under **Supported account types**, select **Accounts in this organizational directory only**.
 
@@ -131,7 +131,7 @@ This app signs in users. You can add delegated permissions to it, by following t
 
 ### Grant API permissions (optional)
 
-If your web app needs to call an API, you must grant your web app API permissions so it can to call the API. You must also [register the web API](how-to-register-ciam-app.md?tabs=webapi) that you need to call.
+If your web app needs to call an API, you must grant your web app API permissions so it can call the API. You must also [register the web API](how-to-register-ciam-app.md?tabs=webapi) that you need to call.
 
 [!INCLUDE [grant permissions for calling an API](../customers/includes/register-app/grant-api-permission-call-api.md)] 
 
@@ -179,7 +179,7 @@ The following steps show you how to register your app in the Microsoft Entra adm
 
 1. In the **Register an application page** that appears, enter your application's registration information:
 
-    1. In the **Name** section, enter a meaningful application name that will be displayed to users of the app, for example *ciam-client-app*.
+    1. In the **Name** section, enter a meaningful application name that is displayed to users of the app, for example *ciam-client-app*.
 
     1. Under **Supported account types**, select **Accounts in this organizational directory only**.
 
@@ -194,7 +194,7 @@ The following steps show you how to register your app in the Microsoft Entra adm
 
 ### Grant API permissions (optional)
 
-If your mobile app needs to call an API, you must grant your mobile app API permissions so it can to call the API. You must also [register the web API](how-to-register-ciam-app.md?tabs=webapi) that you need to call.
+If your mobile app needs to call an API, you must grant your mobile app API permissions so it can call the API. You must also [register the web API](how-to-register-ciam-app.md?tabs=webapi) that you need to call.
 [!INCLUDE [grant permissions for calling an API](../customers/includes/register-app/grant-api-permission-call-api.md)] 
 
 ## Next steps

articles/active-directory/external-identities/customers/how-to-web-app-node-sign-in-call-api-sign-in-acquire-access-token.md

@@ -119,7 +119,7 @@ The `/` route is the entry point to the application. It renders the `views/index
 
 1. In your code editor, open *auth/AuthProvider.js* file, then add the code from [AuthProvider.js](https://github.com/Azure-Samples/ms-identity-ciam-javascript-tutorial/blob/main/2-Authorization/4-call-api-express/App/auth/AuthProvider.js) to it.
 
-The `/signin`, `/signout` and `/redirect` routes are defined in the *routes/auth.js* file, but their logic live in *auth/AuthProvider.js* file.
+The `/signin`, `/signout` and `/redirect` routes are defined in the *routes/auth.js* file, but you implement their logic in *auth/AuthProvider.js* file.
 
 - The `login` method handles`/signin` route:
     

articles/active-directory/external-identities/customers/includes/register-app/add-api-scopes.md

@@ -16,7 +16,7 @@ An API needs to publish a minimum of one scope, also called [Delegated Permissio
 
 1. Under **Scopes defined by this API**, select **Add a scope**.
 
-1. Enter the following values that defines a read access to the API, then select **Add scope** to save your changes:
+1. Enter the following values that define a read access to the API, then select **Add scope** to save your changes:
 
 
     | Property | Value |
@@ -27,7 +27,7 @@ An API needs to publish a minimum of one scope, also called [Delegated Permissio
     | Admin consent description | *Allow the app to read the user's ToDo list using the 'TodoListApi'*. |
     | State | **Enabled** |
 
-1. Select **Add a scope** again, and enter the following values for the second scope that defines a read and write access to the API. Select **Add scope** to save your changes:
+1. Select **Add a scope** again, and enter the following values that define a read and write access scope to the API. Select **Add scope** to save your changes:
 
     | Property | Value |
     |----------|-------|

articles/active-directory/external-identities/customers/includes/register-app/register-client-app-common.md

@@ -23,8 +23,8 @@ The following steps show you how to register your app in the Microsoft Entra adm
 1. Select **+ New registration**.
 1. In the **Register an application** page that appears;
 
-    1. Enter a meaningful application **Name** that will be displayed to users of the app, for example *ciam-client-app*.
+    1. Enter a meaningful application **Name** that is displayed to users of the app, for example *ciam-client-app*.
     1. Under **Supported account types**, select **Accounts in this organizational directory only**.
 
 1. Select **Register**.
-1. The application's **Overview** pane will displays upon successful registration. Record the **Application (client) ID** to be used in your application source code.
+1. The application's **Overview** pane displays upon successful registration. Record the **Application (client) ID** to be used in your application source code.

articles/active-directory/external-identities/customers/tutorial-web-app-node-sign-in-sign-out.md

@@ -130,7 +130,7 @@ The `/` route is the entry point to the application. It renders the *views/index
 
 1. In your code editor, open *auth/AuthProvider.js* file, then add the code from [AuthProvider.js](https://github.com/Azure-Samples/ms-identity-ciam-javascript-tutorial/blob/main/1-Authentication/5-sign-in-express/App/auth/AuthProvider.js) to it.
 
-    The `/signin`, `/signout` and `/redirect` routes are defined in the *routes/auth.js* file, but their logic live in the *auth/AuthProvider.js* class.
+    The `/signin`, `/signout` and `/redirect` routes are defined in the *routes/auth.js* file, but you implement their logic in the *auth/AuthProvider.js* class.
 
 - The `login` method handles `/signin` route: