Fixed step numbering

jpconnock · jpconnock · commit 659940233e24 · 2020-01-06T13:12:37.000-08:00
diff --git a/articles/azure-app-configuration/quickstart-aspnet-core-app.md b/articles/azure-app-configuration/quickstart-aspnet-core-app.md
@@ -43,9 +43,9 @@ In this quickstart, you will use Azure App Configuration to centralize storage a
 
 Use the [.NET Core command-line interface (CLI)](https://docs.microsoft.com/dotnet/core/tools/) to create a new ASP.NET Core MVC web app project. The [Azure Cloud Shell](https://shell.azure.com) provides these tools for you.  They are also available across the Windows, macOS, and Linux platforms.
 
-7. Create a new folder for your project. For this quickstart, name it *TestAppConfig*.
+1. Create a new folder for your project. For this quickstart, name it *TestAppConfig*.
 
-8. In the new folder, run the following command to create a new ASP.NET Core MVC web app project:
+1. In the new folder, run the following command to create a new ASP.NET Core MVC web app project:
 
 ```dotnetcli
 dotnet new mvc --no-https
@@ -96,17 +96,17 @@ The Secret Manager tool stores sensitive data for development work outside of yo
 
 ## Connect to an App Configuration store
 
-9. Add a reference to the `Microsoft.Azure.AppConfiguration.AspNetCore` NuGet package by running the following command:
+1. Add a reference to the `Microsoft.Azure.AppConfiguration.AspNetCore` NuGet package by running the following command:
 
     ```dotnetcli
     dotnet add package Microsoft.Azure.AppConfiguration.AspNetCore --version 3.0.0-preview-010560002-1165
     ```
-10. Run the following command to restore packages for your project:
+1. Run the following command to restore packages for your project:
 
     ```dotnetcli
     dotnet restore
     ```
-11. Add a secret named *ConnectionStrings:AppConfig* to Secret Manager.
+1. Add a secret named *ConnectionStrings:AppConfig* to Secret Manager.
 
     This secret contains the connection string to access your App Configuration store. Replace the value in the following command with the connection string for your App Configuration store.
 
@@ -123,13 +123,13 @@ The Secret Manager tool stores sensitive data for development work outside of yo
 
     Access this secret using the configuration API. A colon (:) works in the configuration name with the configuration API on all supported platforms. See [Configuration by environment](https://docs.microsoft.com/aspnet/core/fundamentals/configuration/index?tabs=basicconfiguration&view=aspnetcore-2.0).
 
-12. Open *Program.cs*, and add a reference to the .NET Core App Configuration provider.
+1. Open *Program.cs*, and add a reference to the .NET Core App Configuration provider.
 
     ```csharp
     using Microsoft.Extensions.Configuration.AzureAppConfiguration;
     ```
 
-13. Update the `CreateWebHostBuilder` method to use App Configuration by calling the `config.AddAzureAppConfiguration()` method.
+1. Update the `CreateWebHostBuilder` method to use App Configuration by calling the `config.AddAzureAppConfiguration()` method.
     
     > [!IMPORTANT]
     > `CreateHostBuilder` replaces `CreateWebHostBuilder` in .NET Core 3.0.  Select the correct syntax based on your environment.
@@ -162,7 +162,7 @@ The Secret Manager tool stores sensitive data for development work outside of yo
     ```
     ---
 
-14. Navigate to *<app root>/Views/Home* and open *Index.cshtml*. Replace its content with the following code:
+1. Navigate to *<app root>/Views/Home* and open *Index.cshtml*. Replace its content with the following code:
 
     ```HTML
     @using Microsoft.Extensions.Configuration
@@ -181,7 +181,7 @@ The Secret Manager tool stores sensitive data for development work outside of yo
     <h1>@Configuration["TestApp:Settings:Message"]</h1>
     ```
 
-15. Navigate to *<app root>/Views/Shared* and open *_Layout.cshtml*. Replace its content with the following code:
+1. Navigate to *<app root>/Views/Shared* and open *_Layout.cshtml*. Replace its content with the following code:
 
     ```HTML
     <!DOCTYPE html>
@@ -210,19 +210,19 @@ The Secret Manager tool stores sensitive data for development work outside of yo
 
 ## Build and run the app locally
 
-16. To build the app using the .NET Core CLI, navigate to the root directory of your application and run the following command in the command shell:
+1. To build the app using the .NET Core CLI, navigate to the root directory of your application and run the following command in the command shell:
 
     ```dotnetcli
     dotnet build
     ```
 
-17. After the build successfully completes, run the following command to run the web app locally:
+1. After the build successfully completes, run the following command to run the web app locally:
 
     ```dotnetcli
     dotnet run
     ```
 
-18. If you're working on your local machine, use a browser to navigate to `http://localhost:5000`. This is the default URL for the web app hosted locally.  
+1. If you're working on your local machine, use a browser to navigate to `http://localhost:5000`. This is the default URL for the web app hosted locally.  
 
 If you're working in the Azure Cloud Shell, select the *Web Preview* button followed by *Configure*.  
 
