diff --git a/aspnetcore/security/authentication/facebook-logins.md b/aspnetcore/security/authentication/facebook-logins.md
index a8e090f959..6d724dca6f 100644
--- a/aspnetcore/security/authentication/facebook-logins.md
+++ b/aspnetcore/security/authentication/facebook-logins.md
@@ -37,7 +37,7 @@ This tutorial shows you how to enable your users to log in with their Facebook a
 
 ![image](sociallogins/_static/FBOAuthSetup.png)
 
-* Enter your base URI with *signin-facebook* appended into the **Valid OAuth Redirect URIs** field. For example, https://localhost:44320/**signin-facebook**.
+* Enter your base URI with *signin-facebook* appended into the **Valid OAuth Redirect URIs** field. For example, `https://localhost:44320/signin-facebook`.
 
 > [!NOTE]
 > You don't need to configure **signin-facebook** as a route in your app. The ASP.NET Core team's implementation of the OAuth flow will create a temporary socket (called a *backchannel*) that listens at this route just for the duration of the OAuth flow.
diff --git a/aspnetcore/security/authentication/google-logins.md b/aspnetcore/security/authentication/google-logins.md
index 14c8939f2f..8ed109b5b0 100644
--- a/aspnetcore/security/authentication/google-logins.md
+++ b/aspnetcore/security/authentication/google-logins.md
@@ -54,7 +54,7 @@ This tutorial shows you how to enable your users to login with their Google+ acc
 
 * Because we are creating a Google+ project with just one feature (logins), we can enter the same **Name** for the OAuth 2.0 client ID as the one we used for the project.
 
-* Enter your current site URL with *signin-google* appended into the **Authorized redirect URIs** field. For example, https://localhost:44320/**signin-google**.
+* Enter your current site URL with *signin-google* appended into the **Authorized redirect URIs** field. For example, `https://localhost:44320/signin-google`.
 
 > [!NOTE]
 > You don't need to configure **signin-google** as a route in your app. The ASP.NET Core team's implementation of the OAuth flow will create a temporary socket (called a *backchannel*) that listens at this route just for the duration of the OAuth flow.
diff --git a/aspnetcore/security/authentication/microsoft-logins.md b/aspnetcore/security/authentication/microsoft-logins.md
index 325d3376bf..ab0915e2e1 100644
--- a/aspnetcore/security/authentication/microsoft-logins.md
+++ b/aspnetcore/security/authentication/microsoft-logins.md
@@ -41,15 +41,15 @@ If you don't already have a Microsoft account, tap *[Create one!](https://signup
 
 ![image](sociallogins/_static/MicrosoftDevAppPlatform.png)
 
-* In the new *Web* platform section, enter your current site URL with *signin-microsoft* appended into the **Redirect URIs** field.
-
-* Don't forget to tap **Add Url** to ensure the Url was added:
+* In the new *Web* platform section, enter your current site URL with *signin-microsoft* appended into the **Redirect URIs** field. For example, `https://localhost:44320/signin-microsoft`:
 
 ![image](sociallogins/_static/MicrosoftRedirectUri.png)
 
 > [!NOTE]
 > You don't need to configure **signin-microsoft** as a route in your app. The ASP.NET Core team's implementation of the OAuth flow will create a temporary socket (called a *backchannel*) that listens at this route just for the duration of the OAuth flow.
 
+* Don't forget to tap **Add Url** to ensure the Url was added.
+
 * Tap **Save** to save changes.
 
 ## Storing Microsoft ApplicationId and Secret
diff --git a/aspnetcore/security/authentication/twitter-logins.md b/aspnetcore/security/authentication/twitter-logins.md
index 55ca10e1e0..5d4f20da61 100644
--- a/aspnetcore/security/authentication/twitter-logins.md
+++ b/aspnetcore/security/authentication/twitter-logins.md
@@ -25,7 +25,7 @@ This tutorial shows you how to enable your users to [log in with their Twitter a
 
 ![image](sociallogins/_static/TwitterCreate.png)
 
-* Enter your current site URL with *signin-twitter* appended into the **Callback URL** field. For example, https://localhost:44320/**signin-twitter**.
+* Enter your current site URL with *signin-twitter* appended into the **Callback URL** field. For example, `https://localhost:44320/signin-twitter`.
 
 > [!NOTE]
 > You don't need to configure **signin-twitter** as a route in your app. The ASP.NET Core team's implementation of the OAuth flow will create a temporary socket (called a *backchannel*) that listens at this route just for the duration of the OAuth flow.