resolve comments

Author: zhiyuanliang-ms

articles/azure-app-configuration/cli-samples.md

@@ -18,9 +18,9 @@ The following table includes links to Azure CLI scripts for Azure App Configurat
 |**Create**||
 | [Create an App Configuration store](./scripts/cli-create-service.md) | Creates a resource group and an App Configuration store instance.  |
 |**Use**||
-| [Work with key values](./scripts/cli-work-with-keys.md) | Creates, views, updates, and deletes key values. |
-| [Import key values](./scripts/cli-import.md) | Imports key values from other sources. |
-| [Export key values](./scripts/cli-export.md) | Exports key values to other targets. |
+| [Work with key-values](./scripts/cli-work-with-keys.md) | Creates, views, updates, and deletes key-values. |
+| [Import key-values](./scripts/cli-import.md) | Imports key-values from other sources. |
+| [Export key-values](./scripts/cli-export.md) | Exports key-values to other targets. |
 |**Delete**||
 | [Delete an App Configuration store](./scripts/cli-delete-service.md) | Deletes an App Configuration store instance.  |
 | | |

articles/azure-app-configuration/concept-customer-managed-keys.md

@@ -38,16 +38,11 @@ After these resources are configured, use the following steps so that the Azure
 1. Assign a managed identity to the Azure App Configuration instance.
 1. Grant the identity `GET`, `WRAP`, and `UNWRAP` permissions in the target Key Vault's access policy.
 
-## Enable customer-managed key encryption for your Azure App Configuration instance
+## Enable customer-managed key encryption for your App Configuration store
 
-To begin, you'll need a properly configured Azure App Configuration instance. If you don't yet have an App Configuration instance available, follow one of these quickstarts to set one up:
+1. [Create an App Configuration store](quickstart-azure-app-configuration-create) if you don't have one.
+1. Create an Azure Key Vault by using the Azure CLI.
 
-- [Create an ASP.NET Core app with Azure App Configuration](quickstart-aspnet-core-app.md)
-- [Create a .NET app with Azure App Configuration](quickstart-dotnet-core-app.md)
-- [Create a .NET Framework app with Azure App Configuration](quickstart-dotnet-app.md)
-- [Create a Java Spring app with Azure App Configuration](quickstart-java-spring-app.md)
-- [Create a JavaScript app with Azure App Configuration](quickstart-javascript.md)
-- [Create a Python app with Azure App Configuration](quickstart-python.md)
 
 > [!TIP]
 > The Azure Cloud Shell is a free interactive shell that you can use to run the command line instructions in this article. It has common Azure tools preinstalled, including the .NET Core SDK. If you are logged in to your Azure subscription, launch your [Azure Cloud Shell](https://shell.azure.com) from shell.azure.com. You can learn more about Azure Cloud Shell by [reading our documentation](../cloud-shell/overview.md).

articles/azure-app-configuration/concept-feature-management.md

@@ -74,7 +74,7 @@ To use feature flags effectively, you need to externalize all the feature flags
 
 Azure App Configuration provides a centralized repository for feature flags. You can use it to define different kinds of feature flags and manipulate their states quickly and confidently. You can then use the App Configuration libraries for various programming language frameworks to easily access these feature flags from your application.
 
-[The feature flags in an ASP.NET Core app](./use-feature-flags-dotnet-core.md) shows how the .NET App Configuration provider and Feature Management libraries are used together to implement feature flags for your ASP.NET web application. For more information on feature flags in Azure App Configuration, see the following articles:
+[The feature flags in an ASP.NET Core app](./use-feature-flags-dotnet-core.md) shows how the App Configuration .NET provider and Feature Management libraries are used together to implement feature flags for your ASP.NET web application. For more information on feature flags in Azure App Configuration, see the following articles:
 
 * [Manage feature flags](./manage-feature-flags.md)
 * [Use conditional feature flags](./howto-feature-filters-aspnet-core.md)

articles/azure-app-configuration/concept-point-time-snapshot.md

@@ -28,7 +28,7 @@ You can use the Azure portal or the Azure CLI to retrieve past key-values.
    :::image type="content" source="media/restore-key-value-portal.png" alt-text="Screenshot of the Azure portal, selecting restore":::
 
 3. Select **Date: Select date** to select a date and time you want to revert to.
-4. Click outside of the date and time fields or press **Tab** to validate your choice. You can now see which key values have changed between your selected date and time and the current time. This step helps you understand what keys and values you're preparing to revert to. 
+4. Click outside of the date and time fields or press **Tab** to validate your choice. You can now see which key-values have changed between your selected date and time and the current time. This step helps you understand what keys and values you're preparing to revert to. 
 
    :::image type="content" source="media/restore-key-value-past-values.png" alt-text="Screenshot of the Azure portal with saved key-values":::
 

articles/azure-app-configuration/enable-dynamic-configuration-dotnet-core.md

@@ -33,7 +33,7 @@ Finish the quickstart [Create a .NET app with App Configuration](./quickstart-do
 
 ## Activity-driven configuration refresh
 
-Open the `Program.cs` file and update the code configurations to match the following:
+Open *Program.cs* and update the file with the following code.
 
 ```csharp
 using Microsoft.Extensions.Configuration;

articles/azure-app-configuration/howto-best-practices.md

@@ -27,15 +27,15 @@ You can use either one or both options to group your keys.
 
 An important thing to keep in mind is that keys are what your application code references to retrieve the values of the corresponding settings. Keys shouldn't change, or else you'll have to modify your code each time that happens.
 
-*Labels* are an attribute on keys. They're used to create variants of a key. For example, you can assign labels to multiple versions of a key. A version might be an iteration, an environment, or some other contextual information. Your application can request an entirely different set of key values by specifying another label. As a result, all key references remain unchanged in your code.
+*Labels* are an attribute on keys. They're used to create variants of a key. For example, you can assign labels to multiple versions of a key. A version might be an iteration, an environment, or some other contextual information. Your application can request an entirely different set of key-values by specifying another label. As a result, all key references remain unchanged in your code.
 
 ## Key-value compositions
 
-App Configuration treats all keys stored with it as independent entities. App Configuration doesn't attempt to infer any relationship between keys or to inherit key values based on their hierarchy. You can aggregate multiple sets of keys, however, by using labels coupled with proper configuration stacking in your application code.
+App Configuration treats all keys stored with it as independent entities. App Configuration doesn't attempt to infer any relationship between keys or to inherit key-values based on their hierarchy. You can aggregate multiple sets of keys, however, by using labels coupled with proper configuration stacking in your application code.
 
 Let's look at an example. Suppose you have a setting named **Asset1**, whose value might vary based on the development environment. You create a key named "Asset1" with an empty label and a label named "Development". In the first label, you put the default value for **Asset1**, and you put a specific value for "Development" in the latter.
 
-In your code, you first retrieve the key values without any labels, and then you retrieve the same set of key values a second time with the "Development" label. When you retrieve the values the second time, the previous values of the keys are overwritten. The .NET configuration system allows you to "stack" multiple sets of configuration data on top of each other. If a key exists in more than one set, the last set that contains it is used. With a modern programming framework, such as .NET, you get this stacking capability for free if you use a native configuration provider to access App Configuration. The following code snippet shows how you can implement stacking in a .NET application:
+In your code, you first retrieve the key-values without any labels, and then you retrieve the same set of key-values a second time with the "Development" label. When you retrieve the values the second time, the previous values of the keys are overwritten. The .NET configuration system allows you to "stack" multiple sets of configuration data on top of each other. If a key exists in more than one set, the last set that contains it is used. With a modern programming framework, such as .NET, you get this stacking capability for free if you use a native configuration provider to access App Configuration. The following code snippet shows how you can implement stacking in a .NET application:
 
 ```csharp
 // Augment the ConfigurationBuilder with Azure App Configuration

articles/azure-app-configuration/howto-integrate-azure-managed-service-identity.md

@@ -45,14 +45,16 @@ To complete this tutorial, you must have:
 
 :::zone target="docs" pivot="framework-dotnet"
 
+* An Azure account with an active subscription. [Create one for free](https://azure.microsoft.com/en-us/free/).
+* An Azure App Configuration store. [Create a store](./quickstart-azure-app-configuration-create.md).
 * [.NET SDK 6.0 or later](https://dotnet.microsoft.com/download).
-* [Azure Cloud Shell configured](../cloud-shell/quickstart.md).
 
 :::zone-end
 
 :::zone target="docs" pivot="framework-spring"
 
-* Azure subscription - [create one for free](https://azure.microsoft.com/free/)
+* An Azure account with an active subscription. [Create one for free](https://azure.microsoft.com/en-us/free/).
+* An Azure App Configuration store. [Create a store](./quickstart-azure-app-configuration-create.md).
 * A supported [Java Development Kit (JDK)](/java/azure/jdk) with version 11.
 * [Apache Maven](https://maven.apache.org/download.cgi) version 3.0 or above.
 
@@ -78,7 +80,7 @@ To set up a managed identity in the portal, you first create an application and
 
 The following steps describe how to assign the App Configuration Data Reader role to App Service. For detailed steps, see [Assign Azure roles using the Azure portal](../role-based-access-control/role-assignments-portal.md).
 
-1. In the [Azure portal](https://portal.azure.com), select the App Configuration store that you created in the [quickstart](../azure-app-configuration/quickstart-azure-functions-csharp.md).
+1. In the [Azure portal](https://portal.azure.com), select your App Configuration store.
 
 1. Select **Access control (IAM)**.
 

articles/azure-app-configuration/howto-move-resource-between-regions.md

@@ -54,7 +54,7 @@ Follow these steps to export your configuration to the target store using the Az
     az appconfig kv export -n SourceConfigurationStore -d appconfig --dest-name TargetConfigurationStore --key * --label * --preserve-labels
     ```
 
-1. To verify that your configurations have been successfully transferred from your source to your target store, list all of the key values in your target store.
+1. To verify that your configurations have been successfully transferred from your source to your target store, list all of the key-values in your target store.
 
     ```azurecli
     az appconfig kv list -n TargetAppConfiguration --all

articles/azure-app-configuration/integrate-kubernetes-deployment-helm.md

@@ -208,7 +208,7 @@ Use helm upgrade's **-f** argument to pass in the two configuration files you've
 helm upgrade --install -f myConfig.yaml -f mySecrets.yaml "example" ./mychart
 ```
 
-You can also use the **--set** argument for helm upgrade to pass literal key values. Using the **--set** argument is a good way to avoid persisting sensitive data to disk.
+You can also use the **--set** argument for helm upgrade to pass literal key-values. Using the **--set** argument is a good way to avoid persisting sensitive data to disk.
 
 ```powershell
 $secrets = az appconfig kv list -n myAppConfiguration --key "secrets.*" --resolve-keyvault --query "[*].{name:key, value:value}" | ConvertFrom-Json

articles/azure-app-configuration/manage-feature-flags.md

@@ -15,13 +15,12 @@ ms.custom: "devx-track-csharp, mvc"
 
 # Tutorial: Manage feature flags in Azure App Configuration
 
-You can store all feature flags in Azure App Configuration and administer them from a single place. App Configuration has a portal UI named **Feature Manager** that's designed specifically for feature flags. App Configuration also natively supports the .NET feature-flag data schema.
+You can create feature flags in Azure App Configuration and manage them from the **Feature Manager** in the Azure portal.
 
 In this tutorial, you learn how to:
 
 > [!div class="checklist"]
 > * Define and manage feature flags in App Configuration.
-> * Access feature flags from your application.
 
 ## Create feature flags