diff --git a/doc/administration/operations/extra_sidekiq_routing.md b/doc/administration/operations/extra_sidekiq_routing.md
index bb8eb18430226cc6ea4429a3a5ef1a9958a44ea6..cd3a53b7c6311f019d9ec7128a69077036747059 100644
--- a/doc/administration/operations/extra_sidekiq_routing.md
+++ b/doc/administration/operations/extra_sidekiq_routing.md
@@ -88,8 +88,8 @@ components:
 
 > [Introduced](https://gitlab.com/gitlab-com/gl-infra/scalability/-/issues/261) in GitLab 13.1 (`tags`).
 
-Queue matching query works upon the worker attributes, described in [Sidekiq
-style guide](../../development/sidekiq_style_guide.md). We support querying
+Queue matching query works upon the worker attributes, described in
+[Sidekiq style guide](../../development/sidekiq/index.md). We support querying
 based on a subset of worker attributes:
 
 - `feature_category` - the [GitLab feature
diff --git a/doc/development/kubernetes.md b/doc/development/kubernetes.md
index a6d9c75483890fc0e956f1fc73c1a21a85c04eeb..ee261769d82655c994f1029dd7228afc80b213ae 100644
--- a/doc/development/kubernetes.md
+++ b/doc/development/kubernetes.md
@@ -54,7 +54,7 @@ webserver, and can lead to a denial-of-service (DoS) attack in GitLab as
 the Kubernetes cluster response times are outside of our control.
 
 The easiest way to ensure your calls happen a background process is to
-delegate any such work to happen in a [Sidekiq worker](sidekiq_style_guide.md).
+delegate any such work to happen in a [Sidekiq worker](sidekiq/index.md).
 
 You may want to make calls to Kubernetes and return the response, but a background
 worker isn't a good fit. Consider using
diff --git a/doc/development/redis.md b/doc/development/redis.md
index 75170b8c7460f0a39bb7e3a0b7988e8c60137357..f01dc005b49c567d2b1aa41a18c438d778890283 100644
--- a/doc/development/redis.md
+++ b/doc/development/redis.md
@@ -11,7 +11,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w
 GitLab uses [Redis](https://redis.io) for the following distinct purposes:
 
 - Caching (mostly via `Rails.cache`).
-- As a job processing queue with [Sidekiq](sidekiq_style_guide.md).
+- As a job processing queue with [Sidekiq](sidekiq/index.md).
 - To manage the shared application state.
 - To store CI trace chunks.
 - As a Pub/Sub queue backend for ActionCable.
diff --git a/doc/user/project/import/github.md b/doc/user/project/import/github.md
index 329d91916e8d3bcc6225a5b6d51c599ba020a397..f6abb31db0bb3b1c37906fb2086081538e91aedc 100644
--- a/doc/user/project/import/github.md
+++ b/doc/user/project/import/github.md
@@ -52,7 +52,7 @@ self-managed GitLab instance.
   pull requests) with matching GitLab users.
 - If you're importing to a self-managed GitLab instance, you can alternatively use the
   [GitHub Rake task](../../../administration/raketasks/github_import.md) to import
-  projects without the constraints of a [Sidekiq](../../../development/sidekiq_style_guide.md) worker.
+  projects without the constraints of a [Sidekiq](../../../development/sidekiq/index.md) worker.
 - If you're importing from GitHub Enterprise to your self-managed GitLab instance:
   - You must first enable [GitHub integration](../../../integration/github.md).
   - To import projects from GitHub Enterprise to GitLab.com, use the [Import API](../../../api/import.md).