Improving acrolinx score

Author: rossgrambo

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

@@ -15,7 +15,7 @@ ms.custom: "devx-track-csharp, mvc"
 
 # Quickstart: Manage feature flags in Azure App Configuration
 
-Azure App Configuration includes feature flags, which you can use to enable or disable a functionality, and variant feature flags (preview), which allow multiple variations of a feature flag.
+Azure App Configuration includes feature flags, which you can use to enable or disable a functionality, and variant feature flags, which allow multiple variations of a feature flag.
 
 The Feature manager in the Azure portal provides a UI for creating and managing the feature flags and the variant feature flags that you use in your applications.
 
@@ -59,9 +59,9 @@ az appconfig feature set --name <name> --feature Beta
 
 ---
 
-## Create a variant feature flag (preview)
+## Create a variant feature flag
 
-Add a new variant feature flag (preview) by opening your Azure App Configuration store in the Azure portal and from the **Operations** menu, select **Feature manager** > **Create**. Then select **Variant feature flag (Preview)**.
+Add a new variant feature flag by opening your Azure App Configuration store in the Azure portal and from the **Operations** menu, select **Feature manager** > **Create**. Then select **Variant feature flag**.
 
 :::image type="content" source="media\manage-feature-flags\variant-feature-flags-menu.png" alt-text="Screenshot of the Azure platform. Create a variant feature flag.":::
 

articles/azure-app-configuration/use-variant-feature-flags-aspnet-core.md

@@ -13,7 +13,7 @@ ms.date: 10/10/2024
 
 # Tutorial: Use variant feature flags from Azure App Configuration in an ASP.NET application
 
-In this tutorial, you'll use a variant feature flag to manage experiences for different user segments in an example application, *Quote of the Day*. You'll utilize the variant feature flag created in [Use variant feature flags](./use-variant-feature-flags.md). Before proceeding, ensure you create the variant feature flag named *Greeting* in your App Configuration store.
+In this tutorial, you use a variant feature flag to manage experiences for different user segments in an example application, *Quote of the Day*. You utilize the variant feature flag created in [Use variant feature flags](./use-variant-feature-flags.md). Before proceeding, ensure you create the variant feature flag named *Greeting* in your App Configuration store.
 
 > [!div class="checklist"]
 > * Set up an ASP.NET app to consume variant feature flags
@@ -26,19 +26,19 @@ In this tutorial, you'll use a variant feature flag to manage experiences for di
 
 ## Create an ASP.NET Core web app
 
-1. Open a command prompt and run the following code. This creates a new Razor Pages application in ASP.NET Core, using Individual account auth, and places it in an output folder named *QuoteOfTheDay*.
+1. Run the following code in a command prompt. This command creates a new Razor Pages application in ASP.NET Core, using Individual account auth, and places it in an output folder named *QuoteOfTheDay*.
 
     ```dotnetcli
     dotnet new razor --auth Individual -o QuoteOfTheDay
     ```
 
-1. In the command prompt, navigate to the *QuoteOfTheDay* folder and run the following command to create a [user secret](/aspnet/core/security/app-secrets) for the application. This secret holds the endpoint for App Configuration.
+1. Navigate to the *QuoteOfTheDay* folder and run the following command to create a [user secret](/aspnet/core/security/app-secrets) for the application. This secret holds the endpoint for App Configuration.
 
     ```dotnetcli
     dotnet user-secrets set Endpoints:AppConfiguration "<App Configuration Endpoint>"
     ```
 
-1. Add the latest versions of the required libraries.
+1. Add the latest versions of the required packages.
 
     ```dotnetcli
     dotnet add package Azure.Identity
@@ -58,7 +58,7 @@ In this tutorial, you'll use a variant feature flag to manage experiences for di
 
 1. In *Program.cs*, under the line `var builder = WebApplication.CreateBuilder(args);`, add the App Configuration provider, which pulls down the configuration from Azure App Configuration when the application starts. By default, the `UseFeatureFlags` method pulls down all feature flags with no label.
 
-    You use the `DefaultAzureCredential` to authenticate to your App Configuration store. Follow the [instructions](./concept-enable-rbac#authentication-with-token-credentials) to assign your credential the **App Configuration Data Reader** role. Be sure to allow sufficient time for the permission to propagate before running your application.
+    You use the `DefaultAzureCredential` to authenticate to your App Configuration store. Follow the [instructions](./concept-enable-rbac.md#authentication-with-token-credentials) to assign your credential the **App Configuration Data Reader** role. Be sure to allow sufficient time for the permission to propagate before running your application.
 
     ```csharp
     builder.Configuration

articles/azure-app-configuration/use-variant-feature-flags.md

@@ -13,15 +13,15 @@ ms.date: 10/10/2024
 
 # Use variant feature flags
 
-Variant feature flags enable your application to support multiple variants of a feature. The variants of your feature can be assigned to specific users, groups, or percentile buckets. These can be particularly useful for feature rollouts, configuration rollouts, and feature experimentation (also known as A/B testing).
+Variant feature flags enable your application to support multiple variants of a feature. The variants of your feature can be assigned to specific users, groups, or percentile buckets. These flags can be useful for feature rollouts, configuration rollouts, and feature experimentation (also known as A/B testing).
 
 ## What is a variant feature flag?
 
 A variant feature flag uses variants and allocation to assign values to users. Variants are defined with a **Name** and a **Configuration Value**. Name is simply an identifier to help tell variants apart. The configuration value on a variant can be any valid JSON or JSON value. Using JSON allows variants to contain as much or as little data as needed to control a feature.
 
 ### Variants
 
-The following is an example of two variants using JSON objects for the configuration value.
+The following example shows two variants using JSON objects for the configuration value.
 
 | Variant Name | Variant Configuration Value |
 |---|---|
@@ -30,11 +30,11 @@ The following is an example of two variants using JSON objects for the configura
 
 ### Allocation
 
-Allocation controls which segment of users will get each variant. The following example allocates 10% of users to get the *Minimal* variant and 90% to get the *Standard* variant.
+Allocation controls which segment of users get each variant. The following example allocates 10% of users to get the *Minimal* variant and 90% to get the *Standard* variant.
 
 | Variant | Allocation | Remarks |
 |---|---|---|
-| Minimal | 10% | Assign the variant to users in the 0 to 10th percentile. |
+| Minimal | 10% | Assign the variant to users in the 0th to 10th percentile. |
 | Standard | 90% | Assign the variant to users in the 10th to 100th percentile. |
 
 ### Overrides
@@ -48,14 +48,14 @@ You can assign variants to specific groups or users irrespective of the percenta
 ### Default variants and kill switch
 
 Variant feature flags have two variant defaults, **DefaultWhenEnabled** and **DefaultWhenDisabled**. 
-1. The **DefaultWhenEnabled** variant will take effect if the flag is enabled but the allocation does assign all percentiles. Any user placed in an unassigned percentile will receive the **DefaultWhenEnabled** variant.
-1. The **DefaultWhenDisabled** variant will take effect if the flag is disabled, usually done by setting the **Enabled** field to false, also known as using the "kill switch". 
+1. The **DefaultWhenEnabled** variant takes effect if the flag is enabled but the allocation does assign all percentiles. Any user placed in an unassigned percentile receives the **DefaultWhenEnabled** variant.
+1. The **DefaultWhenDisabled** variant takes effect if the flag is disabled, done by setting the **Enabled** field to false, also known as using the "kill switch". 
 
-The **kill switch** is used to stop users from allocating. Usually it is used when one or more of the variants have a problem- whether it's a bug, regression, or bad performance. To use the kill switch, set the **Enabled** field of the variant flag to false. Regardless of which percentiles users were a part of, all users will now be given the **DefaultWhenDisabled** variant.
+The **kill switch** is used to stop users from allocating. Usually it's used when one or more of the variants have a problem- whether it's a bug, regression, or bad performance. To use the kill switch, set the **Enabled** field of the variant flag to false. Regardless which percentiles users were a part of, all users now are given the **DefaultWhenDisabled** variant.
 
 ## Build an app with a variant feature flag
 
-In this tutorial, you will create a web app named _Quote of the Day_. When the app is loaded, it displays a quote. Users can interact with the heart button to like it. To improve user engagement, you want to explore whether a personalized greeting message will increase the number of users who like the quote. Users who receive the _None_ variant will see no greeting. Users who receive the _Simple_ variant will get a simple greeting message. Users who receive the _Long_ variant will get a slightly longer greeting. 
+In this tutorial, you create a web app named _Quote of the Day_. When the app is loaded, it displays a quote. Users can interact with the heart button to like it. To improve user engagement, you want to explore whether a personalized greeting message increases the number of users who like the quote. Users who receive the _None_ variant see no greeting. Users who receive the _Simple_ variant get a simple greeting message. Users who receive the _Long_ variant get a slightly longer greeting. 
 
 1. Create a variant feature flag called *Greeting* with no label in your App Configuration store. It includes three variants: *None*, *Simple*, and *Long*, each corresponding to different greeting messages. Refer to the following table for their configuration values and allocation settings. For more information on how to add a variant feature flag, see [Create a variant feature flag](./manage-feature-flags.md#create-a-variant-feature-flag).
 
@@ -65,7 +65,7 @@ In this tutorial, you will create a web app named _Quote of the Day_. When the a
 | Simple | "Hello!" | 25% |
 | Long | "I hope this makes your day!" | 25% | 
 
-2. Continue to the following instructions to use the variant feature flag in your application for the language or platform you are using.
+2. Continue to the following instructions to use the variant feature flag in your application for the language or platform you're using.
     * > [ASP.NET Core](./use-variant-feature-flags-aspnet-core.md)
 
 ## Next steps