edit pass 2: howto-labels-aspnet-core

Author: denrea

articles/azure-app-configuration/howto-labels-aspnet-core.md

@@ -11,28 +11,28 @@ ms.author: lcozzens
 ---
 # Use labels to enable configurations for different environments
 
-Many applications need to use different configurations for different environments. For example, suppose that an application has a configuration value that defines the connection string to use for its back-end database. The application developers use a different database from the one used in production. The database connection string used by the application must change as the application moves from development to production.
+Many applications need to use different configurations for different environments. Suppose that an application has a configuration value that defines the connection string to use for its back-end database. The application developers use a different database from the one used in production. The database connection string that the application uses must change as the application moves from development to production.
 
-In Azure App Configuration, you can use *labels* to define different values for the same key. For example, you can define a single key with different values for *Development* and *Production*. You can specify which label to load when connecting to App Configuration.
+In Azure App Configuration, you can use *labels* to define different values for the same key. For example, you can define a single key with different values for development and production. You can specify which label to load when connecting to App Configuration.
 
-To demonstrate this functionality, you'll modify the web app created in [Quickstart: Create an ASP.NET Core app with Azure App Configuration](./quickstart-aspnet-core-app.md) to use different configuration settings for development versus production. Complete the Quickstart before proceeding.
+To demonstrate this functionality, you'll modify the web app created in [Quickstart: Create an ASP.NET Core app with Azure App Configuration](./quickstart-aspnet-core-app.md) to use different configuration settings for development versus production. Complete the quickstart before proceeding.
 
 ## Specify a label when adding a configuration value
 
-1. In the Azure portal, go to **Configuration Explorer** and locate the *TestApp:Settings:FontColor* key that you created in the Quickstart. Select its context menu and then click **Add Value**.
+In the Azure portal, go to **Configuration Explorer** and find the *TestApp:Settings:FontColor* key that you created in the quickstart. Select its context menu and then click **Add Value**.
 
     > [!div class="mx-imgBorder"]
     > ![Add Value menu item](media/labels-add-value.png)
 
-1. On the **Add Value** screen, enter a **Value** of **red** and a **Label** of **Development**. Leave **Content type** empty. Select **Apply**.
+On the **Add Value** screen, enter a **Value** of **red** and a **Label** of **Development**. Leave **Content type** empty. Select **Apply**.
 
 ## Load configuration values with a specified label
 
-By default, App Configuration only loads configuration values with no label. If you've defined labels for your configuration values, you'll want to specify the label(s) to use when connecting to App Configuration.
+By default, Azure App Configuration only loads configuration values with no label. If you've defined labels for your configuration values, you'll want to specify the labels to use when connecting to App Configuration.
 
-In the previous section, you created a different configuration value for the *Development* environment. You use the `HostingEnvironment.EnvironmentName` variable to dynamically determine which environment the app currently runs in. To learn more, see [Use multiple environments in ASP.NET Core](/aspnet/core/fundamentals/environments).
+In the previous section, you created a different configuration value for the development environment. You use the `HostingEnvironment.EnvironmentName` variable to dynamically determine which environment the app currently runs in. To learn more, see [Use multiple environments in ASP.NET Core](/aspnet/core/fundamentals/environments).
 
-- Load configuration values with the label corresponding to the current environment by passing the environment name into the `Select` method:
+Load configuration values with the label corresponding to the current environment by passing the environment name into the `Select` method:
 
     ```csharp
             public static IHostBuilder CreateHostBuilder(string[] args) =>
@@ -53,29 +53,27 @@ In the previous section, you created a different configuration value for the *De
                 .UseStartup<Startup>());
     ```
 
-    > [!IMPORTANT]
-    > The preceding code snippet loads the App Configuration connection string from an environment variable called `AppConfigConnectionString`. Be sure that this environment variable is set properly.
+> [!IMPORTANT]
+    > The preceding code snippet loads the App Configuration connection string from an environment variable named `AppConfigConnectionString`. Be sure that this environment variable is set properly.
 
-    This calls the `Select` method twice. The first time, it loads configuration values with no label. Then, it loads configuration values with the label corresponding to the current environment. These environment-specific values override any corresponding values with no label. You don't need to define environment-specific values for every key. If a key doesn't have a value with a label corresponding to the current environment, it uses the value with no label.
+The `Select` method is called twice. The first time, it loads configuration values with no label. Then, it loads configuration values with the label corresponding to the current environment. These environment-specific values override any corresponding values with no label. You don't need to define environment-specific values for every key. If a key doesn't have a value with a label corresponding to the current environment, it uses the value with no label.
 
 ## Test in different environments
 
-Follow these steps to test the different configuration values:
+Open the `launchSettings.json` file under the `Properties` directory. Find the `config` entry under `profiles`. In the `environmentVariables` section, set the `ASPNETCORE_ENVIRONMENT` variable to `Production`.
 
-1. Open the `launchSettings.json` file under the `Properties` directory. Locate the `config` entry under `profiles`. In the `environmentVariables` section, set the `ASPNETCORE_ENVIRONMENT` variable to `Production`.
-
-1. With the new values set, build and run your application.
+With the new values set, build and run your application.
 
     ```dotnetcli
     dotnet build
     dotnet run
     ```
 
-1. Use a web browser to go to `http://localhost:5000`. You'll notice that the font color is black.
+Use a web browser to go to `http://localhost:5000`. You'll notice that the font color is black.
 
     ![Web application running with production configuration](media/labels-website-prod.png)
 
-1. Update `launchSettings.json` to set the `ASPNETCORE_ENVIRONMENT` variable to `Development`. Run `dotnet run` again. 
+Update `launchSettings.json` to set the `ASPNETCORE_ENVIRONMENT` variable to `Development`. Run `dotnet run` again. 
 
     You'll notice that the font color is now red. This is because the application now uses the value of `TestApp:Settings:FontColor` that has the `Development` label. All other configuration values remain the same as their production values.