diff --git a/doc/administration/settings/usage_statistics.md b/doc/administration/settings/usage_statistics.md
index cf26c78d9a17a76cdbd7262d0e616c556550d943..b8a54de4edd4ce5db82e092948a6b6050ec75cc5 100644
--- a/doc/administration/settings/usage_statistics.md
+++ b/doc/administration/settings/usage_statistics.md
@@ -14,7 +14,7 @@ GitLab Inc. periodically collects information about your instance in order
to perform various actions.
For free self-managed instances, all usage statistics are [opt-out](#enable-or-disable-service-ping).
-For information about other tiers, see [Customer Product Usage Information](https://about.gitlab.com/handbook/legal/privacy/customer-product-usage-information/#service-ping-formerly-known-as-usage-ping).
+For information about other tiers, see [Customer Product Usage Information](https://handbook.gitlab.com/handbook/legal/privacy/customer-product-usage-information/#service-ping-formerly-known-as-usage-ping).
## Service Ping
@@ -146,7 +146,7 @@ To enable or disable Service Ping:
1. Select **Save changes**.
NOTE:
-The effect of disabling Service Ping depends on the instance's tier. For more information, see [Customer Product Usage Information](https://about.gitlab.com/handbook/legal/privacy/customer-product-usage-information/#service-ping-formerly-known-as-usage-ping).
+The effect of disabling Service Ping depends on the instance's tier. For more information, see [Customer Product Usage Information](https://handbook.gitlab.com/handbook/legal/privacy/customer-product-usage-information/#service-ping-formerly-known-as-usage-ping).
Service Ping settings only control whether the data is being shared with GitLab, or limited to only internal use by the instance.
Even if you disable Service Ping, the `gitlab_service_ping_worker` background job still periodically generates a Service Ping payload for your instance.
The payload is available in the [Metrics and profiling](#manually-upload-service-ping-payload) admin section.
diff --git a/doc/development/activitypub/index.md b/doc/development/activitypub/index.md
index 7714541dd88378e30c9e7f38b45b6097475c0e75..31cde3f55498f9648257f03073de27796e805b79 100644
--- a/doc/development/activitypub/index.md
+++ b/doc/development/activitypub/index.md
@@ -19,7 +19,7 @@ On GitLab.com, this feature is not available.
The feature is not ready for production use.
Usage of ActivityPub in GitLab is governed by the
-[GitLab Testing Agreement](https://about.gitlab.com/handbook/legal/testing-agreement/).
+[GitLab Testing Agreement](https://handbook.gitlab.com/handbook/legal/testing-agreement/).
The goal of those documents is to provide an implementation path for adding
Fediverse capabilities to GitLab.
diff --git a/doc/development/code_review.md b/doc/development/code_review.md
index 9722ad3b2297ccf4ba0d530a5717e5a0df512364..230d9a87e8a67cbecdc73dd8e00f4a81721a4bcc 100644
--- a/doc/development/code_review.md
+++ b/doc/development/code_review.md
@@ -177,7 +177,7 @@ by a reviewer before passing it to a maintainer as described in the
| `~workhorse` changes | [Workhorse maintainer](https://handbook.gitlab.com/handbook/engineering/projects/#gitlab_maintainers_workhorse). |
| `~frontend` changes <sup>1</sup> | [Frontend maintainer](https://handbook.gitlab.com/handbook/engineering/projects/#gitlab_maintainers_frontend). |
| `~UX` user-facing changes <sup>3</sup> | [Product Designer](https://handbook.gitlab.com/handbook/engineering/projects/#gitlab_reviewers_UX). Refer to the [design and user interface guidelines](contributing/design.md) for details. |
-| Adding a new JavaScript library <sup>1</sup> | - [Frontend foundations member](https://about.gitlab.com/direction/manage/foundations/) if the library significantly increases the [bundle size](https://gitlab.com/gitlab-org/frontend/playground/webpack-memory-metrics/-/blob/master/doc/report.md).<br/>- A [legal department member](https://about.gitlab.com/handbook/legal/) if the license used by the new library hasn't been approved for use in GitLab.<br/><br/>More information about license compatibility can be found in our [GitLab Licensing and Compatibility documentation](licensing.md). |
+| Adding a new JavaScript library <sup>1</sup> | - [Frontend foundations member](https://about.gitlab.com/direction/manage/foundations/) if the library significantly increases the [bundle size](https://gitlab.com/gitlab-org/frontend/playground/webpack-memory-metrics/-/blob/master/doc/report.md).<br/>- A [legal department member](https://handbook.gitlab.com/handbook/legal/) if the license used by the new library hasn't been approved for use in GitLab.<br/><br/>More information about license compatibility can be found in our [GitLab Licensing and Compatibility documentation](licensing.md). |
| A new dependency or a file system change | - [Distribution team member](https://about.gitlab.com/company/team/). See how to work with the [Distribution team](https://handbook.gitlab.com/handbook/engineering/infrastructure/core-platform/systems/distribution/#how-to-work-with-distribution) for more details.<br/>- For RubyGems, request an [AppSec review](gemfile.md#request-an-appsec-review). |
| `~documentation` or `~UI text` changes | [Technical writer](https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments) based on assignments in the appropriate [DevOps stage group](https://about.gitlab.com/handbook/product/categories/#devops-stages). |
| Changes to development guidelines | Follow the [review process](development_processes.md#development-guidelines-review) and get the approvals accordingly. |
diff --git a/doc/development/documentation/styleguide/word_list.md b/doc/development/documentation/styleguide/word_list.md
index a42f6280709b7bcb63c1bc9063ad65b75490c86a..201659e45b9c0369428c67e1f7f348457ed77713 100644
--- a/doc/development/documentation/styleguide/word_list.md
+++ b/doc/development/documentation/styleguide/word_list.md
@@ -14,7 +14,7 @@ recommends these word choices. In addition:
[top misused terms](https://about.gitlab.com/handbook/communication/top-misused-terms/).
- The documentation [style guide](../styleguide#language) includes details
about language and capitalization.
-- The GitLab handbook provides guidance on the [use of third-party trademarks](https://about.gitlab.com/handbook/legal/policies/product-third-party-trademarks-guidelines/#process-for-adding-third-party-trademarks-to-gitlab).
+- The GitLab handbook provides guidance on the [use of third-party trademarks](https://handbook.gitlab.com/handbook/legal/policies/product-third-party-trademarks-guidelines/#process-for-adding-third-party-trademarks-to-gitlab).
For guidance not on this page, we defer to these style guides:
diff --git a/doc/development/internal_analytics/index.md b/doc/development/internal_analytics/index.md
index bd45f7fe207ed4b4dc475406cf6a049db81c89c6..465d4dec14c1720a70fa7b2c651ee756f42a3ddb 100644
--- a/doc/development/internal_analytics/index.md
+++ b/doc/development/internal_analytics/index.md
@@ -138,4 +138,4 @@ flowchart LR;
## Data Privacy
GitLab only receives event counts or similarly aggregated information from self-managed instances. User identifiers for individual events on the SaaS version of GitLab are [pseudonymized](https://metrics.gitlab.com/identifiers).
-An exact description on what kind of data is being collected through the Internal Analytics system is given in our [handbook](https://about.gitlab.com/handbook/legal/privacy/customer-product-usage-information/).
+An exact description on what kind of data is being collected through the Internal Analytics system is given in our [handbook](https://handbook.gitlab.com/handbook/legal/privacy/customer-product-usage-information/).
diff --git a/doc/development/licensing.md b/doc/development/licensing.md
index 3c8f8d34a02a1a0efa409805d8388a3a2c1e46b8..9f7975b91a6219d72fa76b33293f92b463bd0c6f 100644
--- a/doc/development/licensing.md
+++ b/doc/development/licensing.md
@@ -52,7 +52,7 @@ More detailed information on how the gem and its commands work is available in t
We sometimes need to use third-party software whose license is not part of the Blue Oak Council
license list, or is marked as Lead-rated in the list. In this case, the use-case needs to be
-legal-approved before the software can be installed. More on this can be [found in the Handbook](https://about.gitlab.com/handbook/legal/product/#using-open-source-software).
+legal-approved before the software can be installed. More on this can be [found in the Handbook](https://handbook.gitlab.com/handbook/legal/product/#using-open-source-software).
To get legal approval, follow these steps:
diff --git a/doc/policy/experiment-beta-support.md b/doc/policy/experiment-beta-support.md
index 7b9530caf0b18dc6084a23e17d962ba12a441779..57a67f5d964b70a2cd926a8d6b581c432b9e823a 100644
--- a/doc/policy/experiment-beta-support.md
+++ b/doc/policy/experiment-beta-support.md
@@ -38,8 +38,8 @@ Experimental features are:
- Data loss may occur.
- Documentation may not exist or just be in a blog format.
- Offer a way to opt-in with minimal friction. For example, needing to flip a feature flag is too much friction, but a group or project-level setting in the UI is not.
-- Link out to the [GitLab Testing Agreement](https://about.gitlab.com/handbook/legal/testing-agreement/) in the opt-in.
-- Documentation reflects that the feature is subject to the [GitLab Testing Agreement](https://about.gitlab.com/handbook/legal/testing-agreement/).
+- Link out to the [GitLab Testing Agreement](https://handbook.gitlab.com/handbook/legal/testing-agreement/) in the opt-in.
+- Documentation reflects that the feature is subject to the [GitLab Testing Agreement](https://handbook.gitlab.com/handbook/legal/testing-agreement/).
- [UI reflects experiment status](https://design.gitlab.com/usability/feature-management#highlighting-feature-versions).
- Feedback issue to engage with team.
- UX not finalized, might be just quick action access.
diff --git a/doc/user/ai_features.md b/doc/user/ai_features.md
index 09c6a72a9bbf6c4cc86581f490847fbb7fe7f290..a9165237bcf6d87f525ee5f1913ff51ccb709750 100644
--- a/doc/user/ai_features.md
+++ b/doc/user/ai_features.md
@@ -44,7 +44,7 @@ Some features are still in development. View details about [support for each sta
(besides Code Suggestions) require that this setting is enabled at the group
level.
- Their usage is subject to the
- [Testing Terms of Use](https://about.gitlab.com/handbook/legal/testing-agreement/).
+ [Testing Terms of Use](https://handbook.gitlab.com/handbook/legal/testing-agreement/).
- Experiment and Beta features are disabled by default.
- This setting is available to Ultimate groups on SaaS and can be set by a user
who has the Owner role in the group.
diff --git a/doc/user/application_security/secret_detection/pre_receive.md b/doc/user/application_security/secret_detection/pre_receive.md
index 8d53c5376c40d2c63fdc8f1ec815de1d1768801e..82628ae8524c4204388f874d6797c1d497593113 100644
--- a/doc/user/application_security/secret_detection/pre_receive.md
+++ b/doc/user/application_security/secret_detection/pre_receive.md
@@ -12,7 +12,7 @@ DETAILS:
> - [Introduced](https://gitlab.com/groups/gitlab-org/-/epics/11439) in GitLab 16.7 as an [Experiment](../../../policy/experiment-beta-support.md) for GitLab Dedicated customers.
NOTE:
-This feature is an [Experiment](../../../policy/experiment-beta-support.md), available only on GitLab Dedicated, and is subject to the [GitLab Testing Agreement](https://about.gitlab.com/handbook/legal/testing-agreement/).
+This feature is an [Experiment](../../../policy/experiment-beta-support.md), available only on GitLab Dedicated, and is subject to the [GitLab Testing Agreement](https://handbook.gitlab.com/handbook/legal/testing-agreement/).
Pre-receive secret detection scans the contents of committed files when they are pushed to a remote repository to prevent the accidental exposure of secrets like keys or API tokens to your repositories. If any secrets are detected, the push is blocked, ensuring that the secrets do not reach your instance.
diff --git a/doc/user/gitlab_duo_chat.md b/doc/user/gitlab_duo_chat.md
index de3c6199ed7b72f53be3710303802bd5282459be..ebb0aebb640856ae9bf2e3815e0740656f9d13be 100644
--- a/doc/user/gitlab_duo_chat.md
+++ b/doc/user/gitlab_duo_chat.md
@@ -168,7 +168,7 @@ have the [experiment and beta features setting](group/manage.md#enable-experimen
### For self-managed users
NOTE:
-Usage of GitLab Duo Chat is governed by the [GitLab Testing Agreement](https://about.gitlab.com/handbook/legal/testing-agreement/).
+Usage of GitLab Duo Chat is governed by the [GitLab Testing Agreement](https://handbook.gitlab.com/handbook/legal/testing-agreement/).
Learn about [data usage when using GitLab Duo Chat](ai_features.md#data-usage).
Prerequisites:
diff --git a/doc/user/project/repository/code_suggestions/index.md b/doc/user/project/repository/code_suggestions/index.md
index 6d6cc79b0c5c41ee71e3071f8c90e9e7fad3dae4..19948c841adb73007a0c835ed1460eae643c8b57 100644
--- a/doc/user/project/repository/code_suggestions/index.md
+++ b/doc/user/project/repository/code_suggestions/index.md
@@ -49,9 +49,9 @@ GitLab Duo Code Suggestions are available:
Code Suggestions is available and free to use until February 15, 2024:
- Before February 15, 2024, usage of Code Suggestions is governed by the
- [GitLab Testing Agreement](https://about.gitlab.com/handbook/legal/testing-agreement/).
+ [GitLab Testing Agreement](https://handbook.gitlab.com/handbook/legal/testing-agreement/).
- On February 15, 2024, Code Suggestions becomes a paid add-on and will be governed by our
- [AI Functionality Terms](https://about.gitlab.com/handbook/legal/ai-functionality-terms/).
+ [AI Functionality Terms](https://handbook.gitlab.com/handbook/legal/ai-functionality-terms/).
## Supported languages
diff --git a/doc/user/project/repository/code_suggestions/saas.md b/doc/user/project/repository/code_suggestions/saas.md
index cc821b8b5492a4c59d03c78a35bf3b9228744a0b..a9f1da8b5df84d149eea5b43c0ca501cddad1a0d 100644
--- a/doc/user/project/repository/code_suggestions/saas.md
+++ b/doc/user/project/repository/code_suggestions/saas.md
@@ -24,7 +24,7 @@ available to Premium and Ultimate users for purchase now.
Write code more efficiently by using generative AI to suggest code while you're developing.
-Usage of GitLab Duo Code Suggestions is governed by the [GitLab Testing Agreement](https://about.gitlab.com/handbook/legal/testing-agreement/).
+Usage of GitLab Duo Code Suggestions is governed by the [GitLab Testing Agreement](https://handbook.gitlab.com/handbook/legal/testing-agreement/).
Learn about [data usage when using Code Suggestions](index.md#code-suggestions-data-usage).
## Enable Code Suggestions
diff --git a/doc/user/project/repository/code_suggestions/self_managed.md b/doc/user/project/repository/code_suggestions/self_managed.md
index 1297e98807ba820e5b57dd44557732932abbe14a..a56d5ae7e9ef9278d24be38740f7233f42540091 100644
--- a/doc/user/project/repository/code_suggestions/self_managed.md
+++ b/doc/user/project/repository/code_suggestions/self_managed.md
@@ -32,7 +32,7 @@ In GitLab 16.3 and later, to participate in the free trial of Code Suggestions o
- Be a Premium or Ultimate customer.
- Have activated cloud licensing.
-Usage of Code Suggestions is governed by the [GitLab Testing Agreement](https://about.gitlab.com/handbook/legal/testing-agreement/).
+Usage of Code Suggestions is governed by the [GitLab Testing Agreement](https://handbook.gitlab.com/handbook/legal/testing-agreement/).
Learn about [data usage when using Code Suggestions](index.md#code-suggestions-data-usage).
## Enable Code Suggestions on self-managed GitLab
@@ -42,7 +42,7 @@ Learn about [data usage when using Code Suggestions](index.md#code-suggestions-d
When you enable Code Suggestions for your self-managed instance, you:
-- Agree to the [GitLab testing agreement](https://about.gitlab.com/handbook/legal/testing-agreement/).
+- Agree to the [GitLab testing agreement](https://handbook.gitlab.com/handbook/legal/testing-agreement/).
- Acknowledge that GitLab sends data from the instance, including personal data, to GitLab.com infrastructure.
How you enable Code Suggestions for your instance differs depending on your