Addressing comments

Author: rossgrambo

articles/azure-app-configuration/feature-management-dotnet-reference.md

@@ -43,7 +43,7 @@ Here are some of the benefits of using .NET feature management library:
   The .NET feature management library is open source. For more information, visit the [GitHub repo](https://github.com/microsoft/FeatureManagement-Dotnet).
 
 ## Feature Flags
-Feature flags have a name and can be either enabled or disabled. The state of a flag can be made conditional through the use of feature filters.
+Feature flags can be either enabled or disabled. The state of a flag can be made conditional through the use of feature filters.
 
 ### Feature Filters
 Feature filters define a scenario for when a feature should be enabled. When a feature is evaluated as on or off, its list of feature filters are traversed until one of the filters determines the feature is enabled. At this point, traversal through the feature filters stops. If no feature filter indicates that the feature should be enabled, it is considered disabled.

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

@@ -199,13 +199,11 @@ In this section, you create a web application that allows users to sign in and u
 
 ## Enable targeting for the web application
 
-The targeting filter evaluates a user's feature state based on the user's targeting context, which comprises the user ID and the groups the user belongs to. In this example, you can use the signed-in user's email address as the user ID and the domain name of the email address as the group.
+A targeting context is required for feature evaluation with targeting. You can provide it as a parameter to the `featureManager.IsEnabledAsync` API explicitly. In ASP.NET Core, the targeting context can also be provided through the service collection as an ambient context by implementing the [ITargetingContextAccessor](./feature-management-dotnet-reference.md#itargetingcontextaccessor) interface.
 
-To evaluate features that use targeting without the need to manually pass a targeting context, an [ITargetingContextAccessor](./feature-management-dotnet-reference.md#itargetingcontextaccessor) can be used.
+### Targeting Context Accessor
 
-### Default Targeting Accessor
-
-To add the default implementation of `ITargetingContextAccessor` use the `WithTargeting()` extension on the feature management builder as seen below. The default uses `HttpContext.User.Identity.Name` as `UserId` and uses `HttpContext.User.Claims` of type `Role` for `Groups`. You can see how the accessor works by looking at the [DefaultHttpTargetingContextAccessor](https://github.com/microsoft/FeatureManagement-Dotnet/blob/main/src/Microsoft.FeatureManagement.AspNetCore/DefaultHttpTargetingContextAccessor.cs).
+To provide the targeting context, pass your implementation type of the `ITargetingContextAccessor` to the `WithTargeting<T>` method. If no type is provided, a default implementation is used, as shown in the following code snippet. The default targeting context accessor utilizes `HttpContext.User.Identity.Name` as `UserId` and uses `HttpContext.User.Claims` of type [`Role`](https://learn.microsoft.com/dotnet/api/system.security.claims.claimtypes.role?view=net-9.0#system-security-claims-claimtypes-role) for `Groups`. You can reference the [DefaultHttpTargetingContextAccessor](https://github.com/microsoft/FeatureManagement-Dotnet/blob/main/src/Microsoft.FeatureManagement.AspNetCore/DefaultHttpTargetingContextAccessor.cs) to implement your own if customization is needed. To learn more about implementing the [ITargetingContextAccessor](./feature-management-dotnet-reference.md#itargetingcontextaccessor), see the feature reference for targeting.
 
 ``` C#
 // Existing code in Program.cs
@@ -219,9 +217,6 @@ builder.Services.AddFeatureManagement()
 // ... ...
 ```
 
-> [!NOTE]
-> For more control over how username and groups are extracted for targeting, see the [feature reference for targeting](./feature-management-dotnet-reference.md#itargetingcontextaccessor).
-
 ## Targeting filter in action
 
 1. Build and run the application. Initially, the **Beta** item doesn't appear on the toolbar, because the _Default percentage_ option is set to 0.