Fix broken anchors in docs (#9406)

Author: melindafekete

README.md

@@ -137,7 +137,7 @@ Check out [the CONTRIBUTING.md file](./CONTRIBUTING.md) for contribution guideli
 
 - Get an overview of all feature flags across all your environments, applications and services
 - Targeted releases using [activation strategies](https://docs.getunleash.io/reference/activation-strategies) to enable and disable features for certain users or segments without having to redeploy your application.
-- [Canary releases / gradual rollouts](https://docs.getunleash.io/reference/activation-strategies#gradual-rollout)
+- [Canary releases / gradual rollouts](https://docs.getunleash.io/reference/activation-strategies)
 - [Kill switches](https://docs.getunleash.io/reference/feature-toggles#feature-flag-types)
 - [A/B testing](https://docs.getunleash.io/feature-flag-tutorials/use-cases/a-b-testing)
 - 2 [environments](https://docs.getunleash.io/reference/environments)

frontend/src/component/admin/serviceAccounts/ServiceAccountsTable/ServiceAccountModal/ServiceAccountModal.tsx

@@ -271,7 +271,7 @@ export const ServiceAccountModal = ({
                 modal
                 title={editing ? 'Edit service account' : 'New service account'}
                 description='A service account is a special type of account that can only be used to authenticate with the Unleash API. Service accounts can be used to automate tasks.'
-                documentationLink='https://docs.getunleash.io'
+                documentationLink='https://docs.getunleash.io/reference/service-accounts'
                 documentationLinkLabel='Service accounts documentation'
                 formatApiCode={formatApiCode}
             >

frontend/src/component/demo/demo-topics.tsx

@@ -315,7 +315,7 @@ export const TOPICS: ITutorialTopic[] = [
                     <>
                         <Description>
                             <a
-                                href='https://docs.getunleash.io/reference/activation-strategies#gradual-rollout'
+                                href='https://docs.getunleash.io/reference/activation-strategies'
                                 target='_blank'
                                 rel='noreferrer'
                             >

frontend/src/component/insights/componentsStat/HealthStats/HealthStats.tsx

@@ -99,7 +99,7 @@ export const HealthStats: FC<IHealthStatsProps> = ({
             </StyledStatsRow>
             <ExplanationRow>
                 <Link
-                    href='https://docs.getunleash.io/reference/technical-debt'
+                    href='https://docs.getunleash.io/reference/insights#health'
                     target='_blank'
                     rel='noreferrer'
                 >

frontend/src/component/user/Profile/PersonalAPITokensTab/CreatePersonalAPIToken/CreatePersonalAPIToken.tsx

@@ -119,8 +119,8 @@ export const CreatePersonalAPIToken: FC<ICreatePersonalAPITokenProps> = ({
                 description='Use personal API tokens to authenticate to the Unleash API as
                 yourself. A personal API token has the same access privileges as
                 your user.'
-                documentationLink='https://docs.getunleash.io/reference/api-tokens-and-client-keys'
-                documentationLinkLabel='Tokens documentation'
+                documentationLink='https://docs.getunleash.io/reference/api-tokens-and-client-keys#personal-access-tokens'
+                documentationLinkLabel='Personal access tokens documentation'
                 formatApiCode={formatApiCode}
             >
                 <StyledForm onSubmit={handleSubmit}>

src/lib/addons/new-relic-definition.ts

@@ -21,7 +21,7 @@ const newRelicDefinition: IAddonDefinition = {
     name: 'new-relic',
     displayName: 'New Relic',
     description: 'Allows Unleash to post updates to New Relic Event API.',
-    documentationUrl: 'https://docs.getunleash.io/docs/addons/new-relic',
+    documentationUrl: 'https://docs.getunleash.io/reference/integrations',
     howTo: 'The New Relic integration allows Unleash to post Updates to New Relic Event API when a feature flag is updated.',
     parameters: [
         {

src/lib/openapi/spec/edge-token-schema.ts

@@ -7,7 +7,7 @@ export const edgeTokenSchema = {
     additionalProperties: false,
     required: ['token', 'projects', 'type'],
     description:
-        'A representation of a client token, limiting access to [CLIENT](https://docs.getunleash.io/reference/api-tokens-and-client-keys#client-tokens) (used by serverside SDKs) or [FRONTEND](https://docs.getunleash.io/reference/api-tokens-and-client-keys#front-end-tokens) (used by proxy SDKs)',
+        'A representation of a client token, limiting access to [CLIENT](https://docs.getunleash.io/reference/api-tokens-and-client-keys#client-tokens) (used by serverside SDKs) or [FRONTEND](https://docs.getunleash.io/reference/api-tokens-and-client-keys#frontend-tokens) (used by proxy SDKs)',
     properties: {
         projects: {
             description:
@@ -19,7 +19,7 @@ export const edgeTokenSchema = {
             example: ['developerexperience', 'enterprisegrowth'],
         },
         type: {
-            description: `The [API token](https://docs.getunleash.io/reference/api-tokens-and-client-keys#api-tokens)'s **type**. Unleash supports three different types of API tokens ([ADMIN](https://docs.getunleash.io/reference/api-tokens-and-client-keys#admin-tokens), [CLIENT](https://docs.getunleash.io/reference/api-tokens-and-client-keys#client-tokens), [FRONTEND](https://docs.getunleash.io/reference/api-tokens-and-client-keys#front-end-tokens)). They all have varying access, so when validating a token it's important to know what kind you're dealing with`,
+            description: `The [API token](https://docs.getunleash.io/reference/api-tokens-and-client-keys)'s **type**. Unleash supports three different types of API tokens ([ADMIN](https://docs.getunleash.io/reference/api-tokens-and-client-keys#admin-tokens), [CLIENT](https://docs.getunleash.io/reference/api-tokens-and-client-keys#client-tokens), [FRONTEND](https://docs.getunleash.io/reference/api-tokens-and-client-keys#frontend-tokens)). They all have varying access, so when validating a token it's important to know what kind you're dealing with`,
             type: 'string',
             enum: Object.values(ApiTokenType),
             example: 'client',

website/docs/feature-flag-tutorials/django/django-examples.md

@@ -94,7 +94,7 @@ Often, canary deployments are managed at the load balancer level while feature f
 
 Unleash has a few ways to help manage canary deployments for Django apps at scale:
 
--   Using a [gradual rollout](/reference/activation-strategies#gradual-rollout) (which we [implemented in a previous section](#gradual-rollouts-for-python-apps)) would be a simple use case but would reduce the amount of control you have over who gets the new feature.
+-   Using a [gradual rollout](/reference/activation-strategies) (which we [implemented in a previous section](#gradual-rollouts-for-django-apps)) would be a simple use case but would reduce the amount of control you have over who gets the new feature.
 
 -   Using either [constraints](/reference/activation-strategies#constraints) or [segments](/reference/segments) (which are a collection of constraints) for a subset of your users to get the new feature vs. the old feature, for _more_ control than a gradual rollout
 

website/docs/feature-flag-tutorials/dotnet/dotnet-examples.md

@@ -89,7 +89,7 @@ Often, canary deployments are managed at the load balancer level while feature f
 
 Unleash has a few ways to help manage canary deployments for .NET apps at scale:
 
--   Using a [gradual rollout](/reference/activation-strategies#gradual-rollout) (which we [implemented in a previous section](#gradual-rollouts-for-net-apps)) would be a simple use case but would reduce the amount of control you have over who gets the new feature.
+-   Using a [gradual rollout](/reference/activation-strategies) (which we [implemented in a previous section](#gradual-rollouts-for-net-apps)) would be a simple use case but would reduce the amount of control you have over who gets the new feature.
 
 -   Using either [constraints](/reference/activation-strategies#constraints) or [segments](/reference/segments) (which are a collection of constraints) for a subset of your users to get the new feature vs. the old feature, for _more_ control than a gradual rollout
 

website/docs/feature-flag-tutorials/ios/examples.md

@@ -81,7 +81,7 @@ Often, canary deployments are managed at the load balancer level while feature f
 
 Unleash has a few ways to help manage canary deployments for iOS apps at scale:
 
--   Using a [gradual rollout](/reference/activation-strategies#gradual-rollout) (which we [implemented in a previous section](#gradual-rollouts-for-ios-apps)) would be a simple use case but would reduce the amount of control you have over who gets the new feature.
+-   Using a [gradual rollout](/reference/activation-strategies) (which we [implemented in a previous section](#gradual-rollouts-for-ios-apps)) would be a simple use case but would reduce the amount of control you have over who gets the new feature.
 
 -   Using either [constraints](/reference/activation-strategies#constraints) or [segments](/reference/segments) (which are a collection of constraints) for a subset of your users to get the new feature vs. the old feature, for _more_ control than a gradual rollout
 

website/docs/feature-flag-tutorials/java/spring-boot-examples.md

@@ -77,7 +77,7 @@ Often, canary deployments are managed at the load balancer level while feature f
 
 Unleash has a few ways to help manage canary deployments for Java apps at scale:
 
--   Using a [gradual rollout](/reference/activation-strategies#gradual-rollout) (which we [implemented in a previous section](#gradual-rollouts-for-java-spring-boot-apps)) would be a simple use case but would reduce the amount of control you have over who gets the new feature.
+-   Using a [gradual rollout](/reference/activation-strategies) (which we [implemented in a previous section](#gradual-rollouts-for-java-spring-boot-apps)) would be a simple use case but would reduce the amount of control you have over who gets the new feature.
 
 -   Using either [constraints](/reference/activation-strategies#constraints) or [segments](/reference/segments) (which are a collection of constraints) for a subset of your users to get the new feature vs. the old feature, for _more_ control than a gradual rollout
 

website/docs/feature-flag-tutorials/python/examples.md

@@ -93,7 +93,7 @@ Often, canary deployments are managed at the load balancer level while feature f
 
 Unleash has a few ways to help manage canary deployments for Python apps at scale:
 
--   Using a [gradual rollout](/reference/activation-strategies#gradual-rollout) (which we [implemented in a previous section](#gradual-rollouts-for-python-apps)) would be a simple use case but would reduce the amount of control you have over who gets the new feature.
+-   Using a [gradual rollout](/reference/activation-strategies) (which we [implemented in a previous section](#gradual-rollouts-for-python-apps)) would be a simple use case but would reduce the amount of control you have over who gets the new feature.
 
 -   Using either [constraints](/reference/activation-strategies#constraints) or [segments](/reference/segments) (which are a collection of constraints) for a subset of your users to get the new feature vs. the old feature, for _more_ control than a gradual rollout
 

website/docs/feature-flag-tutorials/python/implementing-feature-flags.mdx

@@ -23,9 +23,8 @@ Here are the steps we will cover in this tutorial:
 2. [Spin up a local flag provider](#2-install-a-local-feature-flag-provider)
 3. [Configure a feature flag](#3-create-and-configure-the-feature-flag)
 4. [Add Unleash to a Python Flask app](#4-add-unleash-to-a-python-app)
-5. [Toggle the database deletion route](#5-use-a-feature-flag-to-roll-out-a-delete-method)
+5. [Toggle the database deletion route](#5-use-a-feature-flag-to-release-a-delete-method)
 6. [Verify the feature flag experience](#6-verify-the-toggle-experience)
-7. [Improve feature flag error handling](#7-improve-a-feature-flag-implementation-with-error-handling)
 
 Watch the video tutorial and follow along with the code from this documentation.
 

website/docs/feature-flag-tutorials/rails/rails-examples.md

@@ -93,7 +93,7 @@ Often, canary deployments are managed at the load balancer level while feature f
 
 Unleash has a few ways to help manage canary deployments for Ruby apps at scale:
 
--   Using a [gradual rollout](/reference/activation-strategies#gradual-rollout) (which we [implemented in a previous section](#gradual-rollouts-for-ruby-apps)) would be a simple use case but would reduce the amount of control you have over who gets the new feature.
+-   Using a [gradual rollout](/reference/activation-strategies) (which we [implemented in a previous section](#gradual-rollouts-for-rails-apps)) would be a simple use case but would reduce the amount of control you have over who gets the new feature.
 
 -   Using either [constraints](/reference/activation-strategies#constraints) or [segments](/reference/segments) (which are a collection of constraints) for a subset of your users to get the new feature vs. the old feature, for _more_ control than a gradual rollout
 

website/docs/feature-flag-tutorials/react/examples.md

@@ -96,7 +96,7 @@ Often, canary deployments are managed at the load balancer level while feature f
 
 Unleash has a few ways to help manage canary deployments for React apps at scale:
 
--   Using a [gradual rollout](/reference/activation-strategies#gradual-rollout) (which we [implemented in a previous section](#gradual-rollouts-for-react-apps)) would be a simple use case but would reduce the amount of control you have over who gets the new feature.
+-   Using a [gradual rollout](/reference/activation-strategies) (which we [implemented in a previous section](#gradual-rollouts-for-react-apps)) would be a simple use case but would reduce the amount of control you have over who gets the new feature.
 
 -   Using either [constraints](/reference/activation-strategies#constraints) or [segments](/reference/segments) (which are a collection of constraints) for a subset of your users to get the new feature vs. the old feature, for _more_ control than a gradual rollout
 

website/docs/feature-flag-tutorials/ruby/ruby-examples.md

@@ -92,7 +92,7 @@ Often, canary deployments are managed at the load balancer level while feature f
 
 Unleash has a few ways to help manage canary deployments for Ruby apps at scale:
 
--   Using a [gradual rollout](/reference/activation-strategies#gradual-rollout) (which we [implemented in a previous section](#gradual-rollouts-for-ruby-apps)) would be a simple use case but would reduce the amount of control you have over who gets the new feature.
+-   Using a [gradual rollout](/reference/activation-strategies) (which we [implemented in a previous section](#gradual-rollouts-for-ruby-apps)) would be a simple use case but would reduce the amount of control you have over who gets the new feature.
 
 -   Using either [constraints](/reference/activation-strategies#constraints) or [segments](/reference/segments) (which are a collection of constraints) for a subset of your users to get the new feature vs. the old feature, for _more_ control than a gradual rollout
 

website/docs/feature-flag-tutorials/rust/rust-examples.md

@@ -113,7 +113,7 @@ Often, canary deployments are managed at the load balancer level while feature f
 
 Unleash has a few ways to help manage canary deployments for Rust apps:
 
--   Using a [gradual rollout](/reference/activation-strategies#gradual-rollout) (which we [implemented in a previous section](#gradual-rollouts-for-rust-apps)) would be a simple use case but would reduce the amount of control you have over who gets the new feature.
+-   Using a [gradual rollout](/reference/activation-strategies) (which we [implemented in a previous section](#gradual-rollouts-for-rust-apps)) would be a simple use case but would reduce the amount of control you have over who gets the new feature.
 
 -   Using either [constraints](/reference/activation-strategies#constraints) or [segments](/reference/segments) (which are a collection of constraints) for a subset of your users to get the new feature vs. the old feature, for _more_ control than a gradual rollout
 

website/docs/feature-flag-tutorials/use-cases/a-b-testing.md

@@ -17,7 +17,7 @@ In this tutorial, you will learn how to set up and run an A/B test using feature
 2. [Target specific users for each test variant](#target-users-for-ab-testing)
 3. [Manage cross-session visibility of test variants](#manage-user-session-behavior)
 4. [Connect feature flag impression data to conversion outcomes](#track-ab-testing-for-your-key-performance-metrics)
-5. [Roll out the winning variant to all users](#rollout-the-winning-variant-to-all-users)
+5. [Roll out the winning variant to all users](#roll-out-the-winning-variant-to-all-users)
 
 You will also learn about how to [automate advanced A/B testing strategies](#multi-arm-bandit-tests-to-find-the-winning-variant) such as multi-arm bandit testing using feature flags.
 

website/docs/feature-flag-tutorials/use-cases/gradual-rollout.md

@@ -162,7 +162,7 @@ Unleash provides the data to log any change that has happened over time, at the
 
 ![Events for a feature flag. The Event log tab is highlighted and the UI shows the most recent changes, including a JSON diff and the change details.](/img/unleash-toggle-history.png)
 
-Learn more about [Event Log](/reference/events#event-log/) in our documentation.
+Learn more about [Event Log](/reference/events#event-log) in our documentation.
 
 ### Managing Change Requests
 

website/docs/how-to/how-to-create-feature-toggles.md

@@ -97,7 +97,7 @@ Constraints aren't fixed and can be changed later to further narrow your audienc
 
 :::tip API: Add constraints
 
-You can either [add constraints when you add the strategy](/reference/api/legacy/unleash/admin/features-v2#add-strategy) or [PUT](/reference/api/legacy/unleash/admin/features-v2#update-strategy 'PUT an activation strategy') or [PATCH the strategy afterwards](/reference/api/legacy/unleash/admin/features-v2#put-strategy)
+You can either [add constraints when you add the strategy](/reference/api/unleash/add-feature-strategy) or [PUT](/reference/api/unleash/update-feature-strategy) or [PATCH](/reference/api/unleash/patch-feature-strategy) the strategy later.
 
 :::
 
@@ -115,7 +115,7 @@ This can be done after you have created a strategy.
 
 :::tip API: add segments
 
-Use the [API for adding segments to a strategy](/reference/api/legacy/unleash/admin/segments#replace-activation-strategy-segments) to add segments to your strategy.
+Use the [API for adding segments to a strategy](/reference/api/unleash/update-feature-strategy-segments) to add segments to your strategy.
 
 :::
 
@@ -133,7 +133,7 @@ This can be done at any point after you've created your flag.
 
 :::tip API: add variants
 
-Use the [update variants endpoint](/reference/api/legacy/unleash/admin/features-v2#update-variants). The payload should be your desired variant configuration.
+Use the [create variants endpoint](/reference/api/unleash/overwrite-feature-variants) to create or overwrite existing variants in all environments. The payload should be your desired variant configuration.
 
 :::
 

website/docs/how-to/how-to-run-the-unleash-proxy.mdx

@@ -10,7 +10,7 @@ Placeholders in the code samples below are delimited by angle brackets (i.e. `<p
 
 :::
 
-The [Unleash Proxy](../reference/unleash-proxy) provides a way for you to consume feature flags in [front-end clients](../reference/sdks#front-end-sdks), such as the [JavaScript Proxy client](../reference/sdks/javascript-browser) and [React Proxy client](../reference/sdks/react).
+The [Unleash Proxy](../reference/unleash-proxy) provides a way for you to consume feature flags in [front-end clients](../reference/sdks#client-side-sdks), such as the [JavaScript Proxy client](../reference/sdks/javascript-browser) and [React Proxy client](../reference/sdks/react).
 
 Depending on your setup, the Proxy is most easily run in one of two ways, depending on your situation:
 

website/docs/quickstart.mdx

@@ -6,7 +6,7 @@ import Tabs from '@theme/Tabs';
 
 import TabItem from '@theme/TabItem';
 
-This guide helps you set up Unleash in just a few minutes. The fastest way to get started is by using [Docker](#set-up-unleash-with-docker). If Docker doesn't work for you, see [other ways to try Unleash](#additional-ways-to-try-unleash).
+This guide helps you set up Unleash in just a few minutes. The fastest way to get started is by using [Docker](#set-up-unleash-with-docker). If Docker doesn't work for you, see [other ways to try Unleash](#other-ways-to-try-unleash).
 
 ## Set up Unleash with Docker
 
@@ -43,7 +43,7 @@ For more details on creating feature flags, see [How to create a feature flag](/
 Next, use one of the client or server-side [SDKs](/reference/sdks) to connect Unleash with your application.
 
 1. Create an API token:
-    - For client-side SDKs, use a [frontend token](/reference/api-tokens-and-client-keys#front-end-tokens). 
+    - For client-side SDKs, use a [frontend token](/reference/api-tokens-and-client-keys#frontend-tokens). 
     - For server-side SDKs, use a [client token](/reference/api-tokens-and-client-keys#client-tokens).
 2. Determine your Unleash URL:
     - For client-side SDKs, use `<your-unleash-instance>/api/frontend`.