Reworking intro per Zhenlan's feedback

Author: lisaguthrie

articles/azure-app-configuration/howto-feature-filters-aspnet-core.md

@@ -13,13 +13,13 @@ ms.author: lcozzens
 ---
 # Use feature filters to enable a feature for a subset of users
 
-Feature flags allow you to show or hide functionality in your application. A simple feature flag is either on or off. The application always behaves the same way. For example, you could roll out a new feature behind a feature flag. When the feature flag is enabled, all users see the new feature. Disabling the feature flag hides the new feature.
+Feature flags allow you to activate or deactivate functionality in your application. A simple feature flag is either on or off. The application always behaves the same way. For example, you could roll out a new feature behind a feature flag. When the feature flag is enabled, all users see the new feature. Disabling the feature flag hides the new feature.
 
 In contrast, a _conditional feature flag_ allows the feature flag to be enabled or disabled dynamically. The application may behave differently, depending on the feature flag criteria. Suppose you want to show your new feature to a small subset of users at first. A conditional feature flag allows you to enable the feature flag for some users while disabling it for others. _Feature filters_ determine the state of the feature flag each time it's evaluated.
 
 The `Microsoft.FeatureManagement` library includes two feature filters:
 
-- `PercentageFilter` enables the feature flag for a specified percentage of requests.
+- `PercentageFilter` enables the feature flag based on a percentage.
 - `TimeWindowFilter` enables the feature flag during a specified window of time.
 
 You can also create your own feature filter that implements the [Microsoft.FeatureManagement.IFeatureFilter interface](/dotnet/api/microsoft.featuremanagement.ifeaturefilter).
@@ -38,9 +38,9 @@ public void ConfigureServices(IServiceCollection services)
 
 ## Configuring a feature filter in Azure App Configuration
 
-Some feature filters have additional settings. For example, `PercentageFilter` has a setting specifying the percentage of requests for which the feature is enabled.
+Some feature filters have additional settings. For example, `PercentageFilter` activates a feature based on a percentage. It has a setting defining the percentage to use.
 
-You can configure these settings for feature flags defined in Azure App Configuration. For example, follow these steps to use `PercentageFilter` to enable the feature flag for 50% of requests:
+You can configure these settings for feature flags defined in Azure App Configuration. For example, follow these steps to use `PercentageFilter` to enable the feature flag for 50% of requests to a web app:
 
 1. Follow the instructions in [Quickstart: Add feature flags to an ASP.NET Core app](./quickstart-feature-flag-aspnet-core.md) to create a web app with a feature flag.
 
@@ -77,7 +77,7 @@ You can configure these settings for feature flags defined in Azure App Configur
 
 ## Feature filters in action
 
-To see the effects of this feature flag, launch the application and hit the **Refresh** button in your browser multiple times. You'll see that the *Beta* item appears on the toolbar about 50% of the time. It's hidden the rest of the time, because the `PercentageFilter` dynamically enables the *Beta* feature for a subset of requests. The following video shows this behavior in action.
+To see the effects of this feature flag, launch the application and hit the **Refresh** button in your browser multiple times. You'll see that the *Beta* item appears on the toolbar about 50% of the time. It's hidden the rest of the time, because the `PercentageFilter` deactivates the *Beta* feature for a subset of requests. The following video shows this behavior in action.
 
 > [!div class="mx-imgBorder"]
 > ![PercentageFilter in action](./media/feature-flags-percentagefilter.gif)