Make changes to meet the minimum Acrolinx socre requirement.

Author: zhenlan

articles/azure-app-configuration/enable-dynamic-configuration-azure-kubernetes-service.md

@@ -14,7 +14,7 @@ ms.author: linglingye
 
 # Tutorial: Use dynamic configuration in Azure Kubernetes Service
 
-If you use Azure Kubernetes Service (AKS), this tutorial will show you how to enable dynamic configuration for your workloads in AKS by leveraging Azure App Configuration and its Kubernetes Provider. The tutorial assumes that you have already worked through the quickstart and have an App Configuration Kubernetes Provider set up, so before proceeding, make sure you have completed the [Use Azure App Configuration in Azure Kubernetes Service](./quickstart-azure-kubernetes-service.md) quickstart.
+If you use Azure Kubernetes Service (AKS), this tutorial shows you how to enable dynamic configuration for your workloads in AKS by leveraging Azure App Configuration and its Kubernetes Provider. The tutorial assumes that you work through the quickstart and have an App Configuration Kubernetes Provider set up, so before proceeding, make sure you complete the [Use Azure App Configuration in Azure Kubernetes Service](./quickstart-azure-kubernetes-service.md) quickstart.
 
 > [!TIP]
 > See [options](./howto-best-practices.md#azure-kubernetes-service-access-to-app-configuration) for workloads hosted in Kubernetes to access Azure App Configuration.
@@ -38,7 +38,7 @@ Add the following key-value to your App Configuration store. For more informatio
 
 ## Reload data from App Configuration
 
-1. Open the *appConfigurationProvider.yaml* file located in the *Deployment* directory. Then, add the `refresh` section under the `configuration` property as shown below. It enables configuration refresh by monitoring the sentinel key.
+1. Open the *appConfigurationProvider.yaml* file located in the *Deployment* directory. Then, add the `refresh` section under the `configuration` property. It enables configuration refresh by monitoring the sentinel key.
 
     ```yaml
     apiVersion: azconfig.io/v1
@@ -66,15 +66,15 @@ Add the following key-value to your App Configuration store. For more informatio
     > [!TIP]
     > By default, the Kubernetes provider polls the monitoring key-values every 30 seconds for change detection. However, you can change this behavior by setting the `interval` property of the `refresh`. If you want to reduce the number of requests to your App Configuration store, you can adjust it to a higher value.
 
-1. Open the *deployment.yaml* file in the *Deployment* directory and add the following content to the `spec.containers` section. Your application will load configuration from a volume-mounted file the App Configuration Kubernetes provider generates. By setting this environment variable, your application can [ use polling to monitor changes in mounted files](/dotnet/api/microsoft.extensions.fileproviders.physicalfileprovider.usepollingfilewatcher).
+1. Open the *deployment.yaml* file in the *Deployment* directory and add the following content to the `spec.containers` section. Your application loads configuration from a volume-mounted file the App Configuration Kubernetes provider generates. By setting this environment variable, your application can [ use polling to monitor changes in mounted files](/dotnet/api/microsoft.extensions.fileproviders.physicalfileprovider.usepollingfilewatcher).
 
     ```yaml
     env:
     - name: DOTNET_USE_POLLING_FILE_WATCHER
       value: "true"
     ```
 
-1. Run the following command to deploy the change. Replace the namespace if you are using your existing AKS application.
+1. Run the following command to deploy the change. Replace the namespace if you're using your existing AKS application.
 
    ```console
    kubectl apply -f ./Deployment -n appconfig-demo
@@ -92,7 +92,7 @@ Add the following key-value to your App Configuration store. For more informatio
     | Settings:Message | Hello from Azure App Configuration - now with live updates! |
     | Settings:Sentinel | 2 |
 
-1. After refreshing the browser a few times, you will see the updated content once the ConfigMap is updated in 30 seconds.
+1. After refreshing the browser a few times, you'll see the updated content once the ConfigMap is updated in 30 seconds.
 
     ![Screenshot of the web app with updated values.](./media/quickstarts/kubernetes-provider-app-launch-dynamic-after.png)
 

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

@@ -1,7 +1,7 @@
 ---
 title: Enable staged rollout of features for targeted audiences
 titleSuffix: Azure App Configuration
-description: Learn how to enable staged rollout of features for targeted audiences
+description: Learn how to enable staged rollout of features for targeted audiences.
 ms.service: azure-app-configuration
 ms.devlang: csharp
 author: maud-lv
@@ -12,9 +12,9 @@ ms.date: 02/16/2024
 
 # Enable staged rollout of features for targeted audiences
 
-Feature flags allow you to dynamically activate or deactivate functionality in your application. Feature filters determine the state of a feature flag each time it's evaluated. The `Microsoft.FeatureManagement` library includes `TargetingFilter`, which enables a feature flag for a specified list of users and groups, or for a specified percentage of users. `TargetingFilter` is "sticky." This means that once an individual user receives a feature, they'll continue to see that feature on all future requests. You can use `TargetingFilter` to enable a feature for a specific account during a demo, to progressively roll out new features to users in different groups or "rings," and much more.
+Feature flags allow you to dynamically activate or deactivate functionality in your application. Feature filters determine the state of a feature flag each time it's evaluated. The `Microsoft.FeatureManagement` library includes `TargetingFilter`, which enables a feature flag for a specified list of users and groups, or for a specified percentage of users. `TargetingFilter` is "sticky." This means that once an individual user receives a feature, they'll continue to see that feature on all future requests. You can use `TargetingFilter` to enable a feature for a specific account during a demo, to progressively rollout new features to users in different groups or "rings," and much more.
 
-In this article, you'll learn how to roll out a new feature in an ASP.NET Core web application to specified users and groups, using `TargetingFilter` with Azure App Configuration.
+In this article, you learn how to roll out a new feature in an ASP.NET Core web application to specified users and groups, using `TargetingFilter` with Azure App Configuration.
 
 ## Prerequisites
 
@@ -23,31 +23,31 @@ In this article, you'll learn how to roll out a new feature in an ASP.NET Core w
 
 ## Create a web application with feature flags and authentication
 
-To roll out features based on users and groups, you'll need a web application that allows users to sign in.
+To roll out features based on users and groups, you need a web application that allows users to sign in.
 
-1. Create a web application that authenticates against a local database using the following command:
+1. Create a web application that authenticates against a local database using the following command.
 
    ```dotnetcli
    dotnet new mvc --auth Individual -o TestFeatureFlags
    ```
 
-1. Build and run, then select the **Register** link in the upper right corner to create a new user account. Use an email address of `[email protected]`. On the **Register Confirmation** screen, select **Click here to confirm your account**.
+1. Build and run. Then select the **Register** link in the upper right corner to create a new user account. Use an email address of `[email protected]`. On the **Register Confirmation** screen, select **Click here to confirm your account**.
 
-1. Follow the instructions in [Quickstart: Add feature flags to an ASP.NET Core app](./quickstart-feature-flag-aspnet-core.md) to add a feature flag to your new web application.
+1. Follow the instructions in the [Quickstart](./quickstart-feature-flag-aspnet-core.md) to add a feature flag to your new web application.
 
 1. Toggle the feature flag in App Configuration. Validate that this action controls the visibility of the **Beta** item on the navigation bar.
 
 ## Update the web application code to use TargetingFilter
 
-At this point, you can use the feature flag to enable or disable the `Beta` feature for all users. To enable the feature flag for some users while disabling it for others, update your code to use `TargetingFilter`. In this example, you'll use the signed-in user's email address as the user ID, and the domain name portion of the email address as the group. You'll add the user and group to the `TargetingContext`. The `TargetingFilter` uses this context to determine the state of the feature flag for each request.
+At this point, you can use the feature flag to enable or disable the `Beta` feature for all users. To enable the feature flag for some users while disabling it for others, update your code to use `TargetingFilter`. In this example, you use the signed-in user's email address as the user ID, and the domain name portion of the email address as the group. You add the user and group to the `TargetingContext`. The `TargetingFilter` uses this context to determine the state of the feature flag for each request.
 
 1. Update to the latest version of the `Microsoft.FeatureManagement.AspNetCore` package.
 
    ```dotnetcli
    dotnet add package Microsoft.FeatureManagement.AspNetCore
    ```
 
-1. Add a *TestTargetingContextAccessor.cs* file:
+1. Add a *TestTargetingContextAccessor.cs* file.
 
     ```csharp
     using Microsoft.AspNetCore.Http;
@@ -92,13 +92,13 @@ At this point, you can use the feature flag to enable or disable the `Beta` feat
     }
     ```
 
-1. In *Startup.cs*, add a reference to the *Microsoft.FeatureManagement.FeatureFilters* namespace:
+1. In *Startup.cs*, add a reference to the *Microsoft.FeatureManagement.FeatureFilters* namespace.
 
     ```csharp
     using Microsoft.FeatureManagement.FeatureFilters;
     ```
 
-1. Update the *ConfigureServices* method to register `TargetingFilter`, following the call to `AddFeatureManagement()`:
+1. Update the *ConfigureServices* method to register `TargetingFilter`, following the call to `AddFeatureManagement()`.
 
     ```csharp
     services.AddFeatureManagement()
@@ -114,7 +114,7 @@ At this point, you can use the feature flag to enable or disable the `Beta` feat
       services.AddSingleton<ITargetingContextAccessor, TestTargetingContextAccessor>();
     ```
 
-    The entire *ConfigureServices* method will look like this:
+    The entire *ConfigureServices* method looks like this.
 
     ```csharp
     public void ConfigureServices(IServiceCollection services)
@@ -151,20 +151,20 @@ At this point, you can use the feature flag to enable or disable the `Beta` feat
 
 1. Select the **Override by Groups** and **Override by Users** checkbox.
 
-1. Select the following options:
+1. Select the following options.
 
     - **Default percentage**: 0
     - **Include Groups**: Enter a **Name** of _contoso.com_ and a **Percentage** of _50_
     - **Exclude Groups**: `contoso-xyz.com`
     - **Include Users**: `test@contoso.com`
     - **Exclude Users**: `testuser@contoso.com`
 
-    The feature filter screen will look like this:
+    The feature filter screen will look like this.
 
     > [!div class="mx-imgBorder"]
     > ![Conditional feature flag](./media/feature-flag-filter-enabled.png)
 
-    These settings result in the following behavior:
+    These settings result in the following behavior.
 
     - The feature flag is always disabled for user `testuser@contoso.com`, because `testuser@contoso.com` is listed in the _Exclude Users_ section.
     - The feature flag is always disabled for users in the `contoso-xyz.com`, because `contoso-xyz.com` is listed in the _Exclude Groups_ section.
@@ -176,7 +176,7 @@ At this point, you can use the feature flag to enable or disable the `Beta` feat
 
 1. Select **Apply** to save these settings and return to the **Feature manager** screen.
 
-1. The **Feature filter** for the feature flag now appears as *Targeting*. This state indicates that the feature flag will be enabled or disabled on a per-request basis, based on the criteria enforced by the *Targeting* feature filter.
+1. The **Feature filter** for the feature flag now appears as *Targeting*. This state indicates that the feature flag is enabled or disabled on a per-request basis, based on the criteria enforced by the *Targeting* feature filter.
 
 ## TargetingFilter in action
 
@@ -191,9 +191,9 @@ The following video shows this behavior in action.
 > [!div class="mx-imgBorder"]
 > ![TargetingFilter in action](./media/feature-flags-targetingfilter.gif)
 
-You can create additional users with `@contoso.com` and `@contoso-xyz.com` email addresses to see the behavior of the group settings.
+You can create more users with `@contoso.com` and `@contoso-xyz.com` email addresses to see the behavior of the group settings.
 
-Users with `contoso-xyz.com` email addresses will not see the *Beta* item. While 50% of users with `@contoso.com` email addresses will see the *Beta* item, the other 50% won't see the *Beta* item.
+Users with `contoso-xyz.com` email addresses won't see the *Beta* item. While 50% of users with `@contoso.com` email addresses will see the *Beta* item, the other 50% won't see the *Beta* item.
 
 ## Next steps