staged review

Author: cephalin

articles/app-service/configure-authentication-provider-aad.md

@@ -35,15 +35,12 @@ It's recommended that you configure each App Service app with its own registrati
 1. In the [Azure portal], navigate to your App Service app. In the left navigation, select **Authentication / Authorization**.
 2. If **Authentication / Authorization** is not enabled, select **On**.
 3. Select **Azure Active Directory**, and then select **Express** under **Management Mode**.
-4. Select **OK** to register the App Service app in Azure Active Directory. This creates a new app registration. If you want to choose an existing
-   app registration instead, click **Select an existing app** and then search for the name of a previously created app registration within your tenant.
-   Click the app registration to select it and click **OK**. Then click **OK** on the Azure Active Directory settings page.
-   By default, App Service provides authentication but does not restrict authorized access to your site content and APIs. You must authorize users in your app code.
+4. Select **OK** to register the App Service app in Azure Active Directory. This creates a new app registration. If you want to choose an existing app registration instead, click **Select an existing app** and then search for the name of a previously created app registration within your tenant. Click the app registration to select it and click **OK**. Then click **OK** on the Azure Active Directory settings page.
+By default, App Service provides authentication but does not restrict authorized access to your site content and APIs. You must authorize users in your app code.
 5. (Optional) To restrict access to your app to only users authenticated by Azure Active Directory, set **Action to take when request is not authenticated** to **Log in with Azure Active Directory**. This requires that all requests be authenticated, and all unauthenticated requests are redirected to Azure Active Directory for authentication.
 
-> [!CAUTION]
-> Restricting access in this way applies to all calls to your app, which may not be desirable for apps wanting a publicly available home page, as in many single-page applications. For such applications, **Allow anonymous requests (no action)** may be preferred, with the app manually starting login itself, as described [here](overview-authentication-authorization.md#authentication-flow).
-
+    > [!NOTE]
+    > Restricting access in this way applies to all calls to your app, which may not be desirable for apps wanting a publicly available home page, as in many single-page applications. For such applications, **Allow anonymous requests (no action)** may be preferred, with the app manually starting login itself, as described [here](overview-authentication-authorization.md#authentication-flow).
 6. Click **Save**.
 
 ## <a name="advanced"> </a>Configure with advanced settings

articles/app-service/configure-authentication-provider-google.md

@@ -26,7 +26,7 @@ This topic shows you how to configure Azure App Service to use Google as an auth
 To complete the procedure in this topic, you must have a Google account that has a verified email address. To create a new Google account, go to [accounts.google.com](https://go.microsoft.com/fwlink/p/?LinkId=268302).
 
 ## <a name="register"> </a>Register your application with Google
-2. Follow the Google documentation at [Google Sign-In for server-side apps](https://developers.google.com/identity/sign-in/web/server-side-flow) to create a client ID and client secret, with the following information (no need to make any code changes):
+1. Follow the Google documentation at [Google Sign-In for server-side apps](https://developers.google.com/identity/sign-in/web/server-side-flow) to create a client ID and client secret, with the following information (no need to make any code changes):
     - For **Authorized JavaScript Origins**, use `https://<app-name>.azurewebsites.net` with the name of your app in *\<app-name>*.
     - For **Authorized Redirect URI**, use `https://<app-name>.azurewebsites.net/.auth/login/google/callback`.
 1. Once the client ID and client secrets are created, copy their values.
@@ -43,9 +43,9 @@ To complete the procedure in this topic, you must have a Google account that has
    App Service provides authentication but does not restrict authorized access to your site content and APIs. For more information, see [Authorize or deny users](app-service-authentication-how-to.md#authorize-or-deny-users).
 4. (Optional) To restrict access to your site to only users authenticated by Google, set **Action to take when request is not authenticated** to **Google**. This requires that all requests be authenticated, and all unauthenticated requests are redirected to Google for authentication.
 
-> [!CAUTION]
-> Restricting access in this way applies to all calls to your app, which may not be desirable for apps wanting a publicly available home page, as in many single-page applications. For such applications, **Allow anonymous requests (no action)** may be preferred, with the app manually starting login itself, as described [here](overview-authentication-authorization.md#authentication-flow).
-
+    > [!NOTE]
+    > Restricting access in this way applies to all calls to your app, which may not be desirable for apps wanting a publicly available home page, as in many single-page applications. For such applications, **Allow anonymous requests (no action)** may be preferred, with the app manually starting login itself, as described [here](overview-authentication-authorization.md#authentication-flow).
+    
 5. Click **Save**.
 
 You are now ready to use Google for authentication in your app.

articles/app-service/configure-authentication-provider-microsoft.md

@@ -58,7 +58,7 @@ This topic shows you how to configure Azure App Service to use Microsoft Account
 
 4. (Optional) To restrict access to Microsoft account users, set **Action to take when request is not authenticated** to **Log in with Microsoft Account**. This requires that all requests be authenticated, and all unauthenticated requests are redirected to Microsoft account for authentication.
 
-> [!CAUTION]
+> [!NOTE]
 > Restricting access in this way applies to all calls to your app, which may not be desirable for apps wanting a publicly available home page, as in many single-page applications. For such applications, **Allow anonymous requests (no action)** may be preferred, with the app manually starting login itself, as described [here](overview-authentication-authorization.md#authentication-flow).
 
 5. Click **Save**.

articles/app-service/configure-authentication-provider-twitter.md

@@ -48,7 +48,7 @@ To complete the procedure in this topic, you must have a Twitter account that ha
    By default, App Service provides authentication but does not restrict authorized access to your site content and APIs. You must authorize users in your app code.
 4. (Optional) To restrict access to your site to only users authenticated by Twitter, set **Action to take when request is not authenticated** to **Twitter**. This requires that all requests be authenticated, and all unauthenticated requests are redirected to Twitter for authentication.
 
-> [!CAUTION]
+> [!NOTE]
 > Restricting access in this way applies to all calls to your app, which may not be desirable for apps wanting a publicly available home page, as in many single-page applications. For such applications, **Allow anonymous requests (no action)** may be preferred, with the app manually starting login itself, as described [here](overview-authentication-authorization.md#authentication-flow).
 
 5. Click **Save**.