diff --git a/doc/administration/auth/oidc.md b/doc/administration/auth/oidc.md
index 8ef95872ad46742a39c6fdbb59dedb43b5907720..1f76818a510a2574a3db248875572f5bb54beac2 100644
--- a/doc/administration/auth/oidc.md
+++ b/doc/administration/auth/oidc.md
@@ -554,7 +554,7 @@ For your app, complete the following steps on Casdoor:
    ensure the Casdoor app has the following
    `Redirect URI`: `https://gitlab.example.com/users/auth/openid_connect/callback`.
 
-See the [Casdoor documentation](https://casdoor.org/docs/integration/ruby/gitlab) for more details.
+See the [Casdoor documentation](https://casdoor.org/docs/integration/ruby/gitlab/) for more details.
 
 Example configuration for Linux package installations (file path: `/etc/gitlab/gitlab.rb`):
 
diff --git a/doc/administration/geo/glossary.md b/doc/administration/geo/glossary.md
index 2e9a637eb5cb86ba329ff00274ffcf62936f2d13..d0f94ba39f5c499308cca567547510a62cdbb3cd 100644
--- a/doc/administration/geo/glossary.md
+++ b/doc/administration/geo/glossary.md
@@ -14,8 +14,8 @@ these definitions yet.
 
  These are the defined terms to describe all aspects of Geo. Using a set of clearly
  defined terms helps us to communicate efficiently and avoids confusion. The language
- on this page aims to be [ubiquitous](https://about.gitlab.com/handbook/communication/#ubiquitous-language)
- and [as simple as possible](https://about.gitlab.com/handbook/communication/#simple-language).
+ on this page aims to be [ubiquitous](https://handbook.gitlab.com/handbook/communication/#ubiquitous-language)
+ and [as simple as possible](https://handbook.gitlab.com/handbook/communication/#simple-language).
 
  We provide example diagrams and statements to demonstrate correct usage of terms.
 
diff --git a/doc/administration/gitaly/index.md b/doc/administration/gitaly/index.md
index db11ac8c769c390c09eaea0373c9c9d39cc3cdcd..dc0b7a4a6c27a5587e7b5e9978bbea008607cc8e 100644
--- a/doc/administration/gitaly/index.md
+++ b/doc/administration/gitaly/index.md
@@ -57,7 +57,7 @@ If you have not yet migrated to Gitaly Cluster, you have two options:
 - A sharded Gitaly instance.
 - Gitaly Cluster.
 
-Contact your [Customer Success Manager](https://about.gitlab.com/job-families/sales/customer-success-management/) or customer support if you have any questions.
+Contact your [Customer Success Manager](https://handbook.gitlab.com/job-families/sales/customer-success-management/) or customer support if you have any questions.
 
 ### Known issues
 
diff --git a/doc/administration/instance_limits.md b/doc/administration/instance_limits.md
index db0178ec0eddc05034880511b4bcd5452aefb395..05aeffdd1aea42144d3e34cdd251a12e7447deb7 100644
--- a/doc/administration/instance_limits.md
+++ b/doc/administration/instance_limits.md
@@ -1079,7 +1079,7 @@ Issues and merge requests enforce these maximums:
 
 ## CDN-based limits on GitLab.com
 
-In addition to application-based limits, GitLab.com is configured to use Cloudflare's standard DDoS protection and Spectrum to protect Git over SSH. Cloudflare terminates client TLS connections but is not application aware and cannot be used for limits tied to users or groups. Cloudflare page rules and rate limits are configured with Terraform. These configurations are [not public](https://about.gitlab.com/handbook/communication/#not-public) because they include security and abuse implementations that detect malicious activities and making them public would undermine those operations.
+In addition to application-based limits, GitLab.com is configured to use Cloudflare's standard DDoS protection and Spectrum to protect Git over SSH. Cloudflare terminates client TLS connections but is not application aware and cannot be used for limits tied to users or groups. Cloudflare page rules and rate limits are configured with Terraform. These configurations are [not public](https://handbook.gitlab.com/handbook/communication/confidentiality-levels/#not-public) because they include security and abuse implementations that detect malicious activities and making them public would undermine those operations.
 
 ## Container Repository tag deletion limit
 
diff --git a/doc/administration/integration/kroki.md b/doc/administration/integration/kroki.md
index 0356212d6ddc4c9044667479a341743cb54fcdf4..d3b381195cc5c6e86a7ad29231685ac00ca6ae34 100644
--- a/doc/administration/integration/kroki.md
+++ b/doc/administration/integration/kroki.md
@@ -36,9 +36,9 @@ Supported libraries include:
 
 <!-- vale gitlab.Spelling = NO -->
 
-- [Bytefield](https://bytefield-svg.deepsymmetry.org/)
+- [Bytefield](https://bytefield-svg.deepsymmetry.org/bytefield-svg/intro.html)
 - [D2](https://d2lang.com/tour/intro/)
-- [DBML](https://www.dbml.org/home/)
+- [DBML](https://dbml.dbdiagram.io/home/)
 - [Ditaa](https://ditaa.sourceforge.net)
 - [Erd](https://github.com/BurntSushi/erd)
 - [GraphViz](https://www.graphviz.org/)
diff --git a/doc/administration/lfs/index.md b/doc/administration/lfs/index.md
index 4659917cf8b23db91eaa84806590a8e747b3f0b7..26034ce1d01766169d23433f30243910fc40afdd 100644
--- a/doc/administration/lfs/index.md
+++ b/doc/administration/lfs/index.md
@@ -453,7 +453,7 @@ settings to allow the GitLab domain. See the following documentation
 for more details:
 
 1. [AWS S3](https://repost.aws/knowledge-center/s3-configure-cors)
-1. [Google Cloud Storage](https://cloud.google.com/storage/docs/configuring-cors)
+1. [Google Cloud Storage](https://cloud.google.com/storage/docs/using-cors)
 1. [Azure Storage](https://learn.microsoft.com/en-us/rest/api/storageservices/cross-origin-resource-sharing--cors--support-for-the-azure-storage-services).
 
 ## Known limitations
diff --git a/doc/administration/logs/tracing_correlation_id.md b/doc/administration/logs/tracing_correlation_id.md
index 45c0ce371026ecd1e652c703aecbae417e6b7032..79c8dcf4d817cfb0acfc0a89573b982d052f9df2 100644
--- a/doc/administration/logs/tracing_correlation_id.md
+++ b/doc/administration/logs/tracing_correlation_id.md
@@ -25,7 +25,7 @@ You can use your browser's developer tools to monitor and inspect network
 activity with the site that you're visiting. See the links below for network monitoring
 documentation for some popular browsers.
 
-- [Network Monitor - Firefox Developer Tools](https://developer.mozilla.org/en-US/docs/Tools/Network_Monitor)
+- [Network Monitor - Firefox Developer Tools](https://firefox-source-docs.mozilla.org/devtools-user/network_monitor/index.html)
 - [Inspect Network Activity In Chrome DevTools](https://developer.chrome.com/docs/devtools/network/)
 - [Safari Web Development Tools](https://developer.apple.com/safari/tools/)
 - [Microsoft Edge Network panel](https://learn.microsoft.com/en-us/microsoft-edge/devtools-guide-chromium/network/)
diff --git a/doc/administration/object_storage.md b/doc/administration/object_storage.md
index aa17452f2604d83a688f9b845ed38379d0644823..07cb815796079e0db44dd258613eb204f86a41cd 100644
--- a/doc/administration/object_storage.md
+++ b/doc/administration/object_storage.md
@@ -237,7 +237,7 @@ To set up an instance profile:
    }
    ```
 
-1. [Attach this role](https://aws.amazon.com/premiumsupport/knowledge-center/attach-replace-ec2-instance-profile/)
+1. [Attach this role](https://repost.aws/knowledge-center/attach-replace-ec2-instance-profile)
    to the EC2 instance hosting your GitLab instance.
 1. Set the `use_iam_profile` GitLab configuration option to `true`.
 
diff --git a/doc/administration/packages/container_registry.md b/doc/administration/packages/container_registry.md
index 7d9e6a4b9ada9bd044877c6d1b8b1a8cdeb548ce..13aa3bb829b10f25ef19d8724540356501bff2e1 100644
--- a/doc/administration/packages/container_registry.md
+++ b/doc/administration/packages/container_registry.md
@@ -500,7 +500,7 @@ To configure the `s3` storage driver for a Linux package installation:
      `bucket_name.host/object`. [Set to false for AWS S3](https://aws.amazon.com/blogs/aws/amazon-s3-path-deprecation-plan-the-rest-of-the-story/).
 
    You can set a rate limit on connections to S3 to avoid 503 errors from the S3 API. To do this,
-   set `maxrequestspersecond` to a number within the [S3 request rate threshold](https://repost.aws/knowledge-center/s3-503-within-request-rate-prefix):
+   set `maxrequestspersecond` to a number within the [S3 request rate threshold](https://repost.aws/knowledge-center/http-5xx-errors-s3):
 
    ```ruby
       registry['storage'] = {
diff --git a/doc/administration/pages/troubleshooting.md b/doc/administration/pages/troubleshooting.md
index a103c793763016df65a8c317053947190d1090cc..9f335dc7d9c20abd5e417dd1b9766904a5adecc7 100644
--- a/doc/administration/pages/troubleshooting.md
+++ b/doc/administration/pages/troubleshooting.md
@@ -152,7 +152,7 @@ This can happen to GitLab instances with multiple servers
 running both the core GitLab application and GitLab Pages. This can also happen when a single
 container is running both the core GitLab application and GitLab Pages.
 
-AWS [recommends using an IP target type](https://aws.amazon.com/premiumsupport/knowledge-center/target-connection-fails-load-balancer/)
+AWS [recommends using an IP target type](https://repost.aws/knowledge-center/target-connection-fails-load-balancer)
 to resolve this issue.
 
 Turning off [client IP preservation](https://docs.aws.amazon.com/elasticloadbalancing/latest/network/load-balancer-target-groups.html#client-ip-preservation)