README Updates.

Author: Frank Li (Wicresoft North America Ltd)

README.md

@@ -104,12 +104,12 @@ This command shows the secret information including the URI. After completing th
     Open Program.cs file and update the placeholder <YourKeyVaultName> with the name of your Key Vault that you created in Step 3
 
 
-#### 8) Run the app
+#### 7) Run the app
     From the main menu of Visual Studio 2017, choose 
     Debug > Start without Debugging. 
     When the browser appears, navigate to the About page. The value for the AppSecret is displayed.
 
-#### 9) Publish the web application to Azure
+#### 8) Publish the web application to Azure
 
 1. In Visual Studio, select **key-vault-dotnet-core-quickstart** Project.
 2. Select **Publish** then **Start**.
@@ -118,7 +118,7 @@ This command shows the secret information including the URI. After completing th
 5. Select **Create**.
 ![Publish](./media/PublishToAzure.gif)
 
-#### 10) Enable Managed Service Identity
+#### 9) Enable Managed Service Identity
 Azure Key Vault provides a way to securely store credentials and other keys and secrets, but your code needs to authenticate to Key Vault to retrieve them. Managed Service Identity (MSI) makes solving this problem simpler by giving Azure services an automatically managed identity in Azure Active Directory (Azure AD). You can use this identity to authenticate to any service that supports Azure AD authentication, including Key Vault, without having any credentials in your code.
 
 1. Return to the Azure CLI
@@ -131,7 +131,7 @@ az webapp identity assign --name "keyvaultdotnetcorequickstart" --resource-group
 >[!NOTE]
 >This command is the equivalent of going to the portal and switching **Managed service identity** to **On** in the web application properties.
 
-#### 11) Assign permissions to your application to read secrets from Key Vault
+#### 10) Assign permissions to your application to read secrets from Key Vault
 1. Return to the Azure CLI
 2. Run the following commands by replacing the placeholders
    ```