diff --git a/aspnetcore/security/authentication/social/google-logins.md b/aspnetcore/security/authentication/social/google-logins.md
index 0eec27b636..85b89319f1 100644
--- a/aspnetcore/security/authentication/social/google-logins.md
+++ b/aspnetcore/security/authentication/social/google-logins.md
@@ -81,7 +81,7 @@ This tutorial shows you how to enable your users to sign in with their Google+ a
 
 ## Storing Google ClientID and ClientSecret
 
-Link sensitive settings like Google `ClientID` and `ClientSecret` to your application configuration by using the [Secret Manager tool](../../app-secrets.md) instead of storing them in your configuration file directly, as described in the [social login overview page](index.md).
+Link sensitive settings like Google `ClientID` and `ClientSecret` to your application configuration by using the [Secret Manager tool](../../app-secrets.md) instead of storing them in your configuration file directly, as described in the [social authentication overview page](index.md).
 
 * Open the JSON file downloaded in the last step. Note the `client_id` and `client_secret` values present in the JSON structure.
 
@@ -115,6 +115,9 @@ app.UseGoogleAuthentication(new GoogleOptions()
 });
 ```
 
+> [!NOTE]
+> Call `UseIdentity` before you call `UseGoogleAuthentication`. See the [social authentication overview page](index.md).
+
 ## Sign in with Google
 
 Run your application and click **Log in**. An option to sign in with Google appears:
diff --git a/aspnetcore/security/authentication/social/index.md b/aspnetcore/security/authentication/social/index.md
index 61a53e0e15..1c9b4726e4 100644
--- a/aspnetcore/security/authentication/social/index.md
+++ b/aspnetcore/security/authentication/social/index.md
@@ -81,7 +81,7 @@ As a best practice, it is not recommended to store the secrets in a configuratio
 
 The **SecretManager** tool stores sensitive application settings in the user profile folder on the local machine. These settings are then seamlessly merged with settings from all other sources during application startup.
 
-> [NOTE!]
+> [!NOTE]
 > Most login providers assign **Application Id** and **Application Secret** during the registration process. These values are effectively the *user name* and *password* your application uses to access their API, and constitute the "secrets" linked to your application configuration with the help of **Secret Manager** instead of storing them in configuration files directly.
 
 Install the [Secret Manager tool](../../app-secrets.md) so that you can use it to store tokens assigned by each login provider below.
@@ -96,7 +96,7 @@ Use the following pages to configure your application to use the respective prov
 * [Microsoft](microsoft-logins.md) instructions
 * [Other provider](other-logins.md) instructions
 
-> [NOTE!]
+> [!NOTE]
 > Call `app.UseIdentity` (in `Configure`) before any other external providers.
 
 ## Optionally set password