Cleanup and remove pivot

Author: rossgrambo

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

@@ -3,14 +3,13 @@ title: .NET feature flag management
 titleSuffix: Azure App Configuration
 description: Learn to implement feature flags in your .NET and ASP.NET Core applications using feature management and Azure App Configuration. Dynamically manage feature rollouts, conduct A/B testing, and control feature visibility without redeploying the app.
 services: azure-app-configuration
-author: zhiyuanliang-ms
-ms.author: zhiyuanliang
+author: rossgrambo
+ms.author: rossgrambo
 ms.service: azure-app-configuration
 ms.devlang: csharp
 ms.custom: devx-track-dotnet
 ms.topic: tutorial
-ms.date: 05/22/2024
-zone_pivot_groups: feature-management
+ms.date: 01/07/2024
 #Customer intent: I want to control feature availability in my app by using the Feature Management library.
 ---
 

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

@@ -138,9 +138,8 @@ In this section, you create a web application that allows users to sign in and u
     // ... ...
     ```
 
-    > [!NOTE]
-    > For Blazor applications, see [instructions](./faq.yml#how-to-enable-feature-management-in-blazor-applications-or-as-scoped-services-in--net-applications) for enabling feature management as scoped services.
-    
+    ---
+
 1. Enable configuration and feature flag refresh from Azure App Configuration with the App Configuration middleware.
 
     Update Program.cs withe the following code.
@@ -202,11 +201,11 @@ In this section, you create a web application that allows users to sign in and u
 
 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.
 
-To get targeting context for users automatically (instead of manually constructing a targeting context each time), an implementation of `ITargetingContextAccessor` is required. There's two options for adding an `ITargetingContextAccessor` to your application:
+To get targeting context for users automatically (instead of manually constructing a targeting context each time), an implementation of [ITargetingContextAccessor](./feature-management-dotnet-reference.md#itargetingcontextaccessor) is required.
 
 ### Default Targeting Accessor
 
-To add a 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 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).
 
 ``` C#
 // Existing code in Program.cs
@@ -241,11 +240,6 @@ builder.Services.AddFeatureManagement()
 
     Now sign in as `[email protected]`, using the password you set when registering the account. The **Beta** item doesn't appear on the toolbar, because `[email protected]` is specified as an excluded user.
 
-    If you used the `ExampleTargetingContextAccessor`
-    
-    * 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 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
 
 To learn more about the feature filters, continue to the following documents.

articles/zone-pivot-groups.yml

@@ -1295,15 +1295,6 @@ groups:
     title: .NET
   - id: framework-spring
     title: Spring Framework
-# Owner: zhiyuanliang
-- id: feature-management
-  title: Library version pivots
-  prompt: Choose a release
-  pivots:
-  - id: stable-version
-    title: Stable release
-  - id: preview-version
-    title: Preview release
 # Owner: avanigupta
 - id: appconfig-data-plane-api-version
   title: API version pivots