Removing preview from variant docs

Author: rossgrambo

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

@@ -1207,7 +1207,7 @@ builder.services
 > [!NOTE]
 > To ensure Application Insights telemetry works as expected, the `TargetingHttpContextMiddleware` should be used.
 
-To enable persistance of targeting context in the current activity, you can use the [`TargetingHttpContextMiddleware`](https://github.com/microsoft/FeatureManagement-Dotnet/blob/preview/src/Microsoft.FeatureManagement.AspNetCore/TargetingHttpContextMiddleware.cs).
+To enable persistance of targeting context in the current activity, you can use the [`TargetingHttpContextMiddleware`](https://github.com/microsoft/FeatureManagement-Dotnet/blob/main/src/Microsoft.FeatureManagement.AspNetCore/TargetingHttpContextMiddleware.cs).
 
 ``` C#
 app.UseMiddleware<TargetingHttpContextMiddleware>();
@@ -1217,7 +1217,7 @@ An example of its usage can be found in the [VariantAndTelemetryDemo](https://gi
 
 #### Prerequisite
 
-This telemetry publisher depends on Application Insights already being setup registered as an application service. For example, that is done [here](https://github.com/microsoft/FeatureManagement-Dotnet/blob/preview/examples/VariantAndTelemetryDemo/Program.cs#L22-L32) in the example application.
+This telemetry publisher depends on Application Insights already being setup registered as an application service. For example, that is done [here](https://github.com/microsoft/FeatureManagement-Dotnet/blob/main/examples/VariantAndTelemetryDemo/Program.cs#L22-L32) in the example application.
 
 This telemetry publisher depends on Application Insights already being [setup](/azure/azure-monitor/app/asp-net-core#enable-application-insights-server-side-telemetry-no-visual-studio) and registered as an application service.
 

Diff for: 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.":::
 

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

@@ -26,7 +26,7 @@ In this tutorial, you:
 
 ## Create a variant feature flag
 
-Create a variant feature flag called *Greeting* with no label and three variants, *None*, *Simple*, and *Long*. Creating variant flags is described in the [Feature Flag quickstart](./manage-feature-flags.md#create-a-variant-feature-flag-preview).
+Create a variant feature flag called *Greeting* with no label and three variants, *None*, *Simple*, and *Long*. Creating variant flags is described in the [Feature Flag quickstart](./manage-feature-flags.md#create-a-variant-feature-flag).
 
 | Variant Name | Variant Configuration Value | Allocation| 
 |---|---|---|