diff --git a/.gitlab/issue_templates/Feature Flag Roll Out.md b/.gitlab/issue_templates/Feature Flag Roll Out.md
index 171f55a5101..7aeecc94cec 100644
--- a/.gitlab/issue_templates/Feature Flag Roll Out.md	
+++ b/.gitlab/issue_templates/Feature Flag Roll Out.md	
@@ -101,7 +101,7 @@ To do so, follow these steps:
       If the merge request was deployed before [the monthly release was tagged](https://about.gitlab.com/handbook/engineering/releases/#self-managed-releases-1),
       the feature can be officially announced in a release blog post: `/chatops run release check <merge-request-url> <milestone>`
 - [ ] After the default-enabling MR has been deployed, clean up the feature flag from all environments by running these chatops command in the `#production` channel: `/chatops run feature delete <feature-flag-name> --dev --pre --staging --staging-ref --production`
-- [ ] Close [the feature issue][<feature-issue-link>] to indicate the feature will be released in the current milestone.
+- [ ] Close [the feature issue](<feature-issue-link>) to indicate the feature will be released in the current milestone.
 - [ ] Set the next milestone to this rollout issue for scheduling [the flag removal](#release-the-feature).
 - [ ] (Optional) You can [create a separate issue](https://gitlab.com/gitlab-org/gitlab/-/issues/new?issuable_template=Feature%20Flag%20Cleanup) for scheduling the steps below to [Release the feature](#release-the-feature).
     - [ ] Set the title to "[Feature flag] Cleanup `<feature-flag-name>`".
@@ -128,7 +128,7 @@ or use the checklist below in this same issue.
 - [ ] Ensure that the cleanup MR has been included in the release package.
       If the merge request was deployed before [the monthly release was tagged](https://about.gitlab.com/handbook/engineering/releases/#self-managed-releases-1),
       the feature can be officially announced in a release blog post: `/chatops run release check <merge-request-url> <milestone>`
-- [ ] Close [the feature issue][<feature-issue-link>] to indicate the feature will be released in the current milestone.
+- [ ] Close [the feature issue](<feature-issue-link>) to indicate the feature will be released in the current milestone.
 - [ ] Once the cleanup MR has been deployed to production, clean up the feature flag from all environments by running these chatops command in `#production` channel: `/chatops run feature delete <feature-flag-name> --dev --pre --staging --staging-ref --production`
 - [ ] Close this rollout issue.
 
diff --git a/.rubocop_todo/layout/line_end_string_concatenation_indentation.yml b/.rubocop_todo/layout/line_end_string_concatenation_indentation.yml
index e543c5fff18..baceb196313 100644
--- a/.rubocop_todo/layout/line_end_string_concatenation_indentation.yml
+++ b/.rubocop_todo/layout/line_end_string_concatenation_indentation.yml
@@ -392,7 +392,7 @@ Layout/LineEndStringConcatenationIndentation:
     - 'qa/qa/service/docker_run/product_analytics/dotnet_sdk_app.rb'
     - 'qa/qa/specs/features/ee/api/10_govern/compliance_pipeline_spec.rb'
     - 'qa/qa/specs/features/ee/browser_ui/10_govern/export_vulnerability_report_spec.rb'
-    - 'qa/qa/specs/features/ee/browser_ui/9_data_stores/elasticsearch/elasticsearch_reindexing_spec.rb'
+    - 'qa/qa/specs/features/ee/browser_ui/9_tenant_scale/elasticsearch/elasticsearch_reindexing_spec.rb'
     - 'qa/qa/support/system_logs/kibana.rb'
     - 'qa/qa/tools/revoke_user_personal_access_tokens.rb'
     - 'qa/qa/tools/test_resources_handler.rb'
diff --git a/.rubocop_todo/rspec/example_without_description.yml b/.rubocop_todo/rspec/example_without_description.yml
index 770c6ccceee..e931808fc78 100644
--- a/.rubocop_todo/rspec/example_without_description.yml
+++ b/.rubocop_todo/rspec/example_without_description.yml
@@ -218,7 +218,7 @@ RSpec/ExampleWithoutDescription:
     - 'ee/spec/workers/group_destroy_worker_spec.rb'
     - 'ee/spec/workers/security/scan_execution_policies/create_pipeline_worker_spec.rb'
     - 'ee/spec/workers/security/scan_execution_policies/rule_schedule_worker_spec.rb'
-    - 'qa/qa/specs/features/browser_ui/9_data_stores/project/dashboard_images_spec.rb'
+    - 'qa/qa/specs/features/browser_ui/9_tenant_scale/project/dashboard_images_spec.rb'
     - 'qa/spec/specs/helpers/feature_flag_spec.rb'
     - 'spec/bin/audit_event_type_spec.rb'
     - 'spec/bin/feature_flag_spec.rb'
diff --git a/.rubocop_todo/rspec/no_expectation_example.yml b/.rubocop_todo/rspec/no_expectation_example.yml
index ce96a4fd7ad..aba6b37def4 100644
--- a/.rubocop_todo/rspec/no_expectation_example.yml
+++ b/.rubocop_todo/rspec/no_expectation_example.yml
@@ -47,7 +47,7 @@ RSpec/NoExpectationExample:
     - 'qa/qa/specs/features/browser_ui/4_verify/ci_variable/ui_variable_inheritable_when_forward_pipeline_variables_true_spec.rb'
     - 'qa/qa/specs/features/browser_ui/4_verify/ci_variable/ui_variable_non_inheritable_when_forward_pipeline_variables_false_spec.rb'
     - 'qa/qa/specs/features/ee/api/2_plan/epics_to_work_items_sync_spec.rb'
-    - 'qa/qa/specs/features/ee/api/9_data_stores/elasticsearch/elasticsearch_api_spec.rb'
+    - 'qa/qa/specs/features/ee/api/9_tenant_scale/elasticsearch/elasticsearch_api_spec.rb'
     - 'qa/qa/specs/features/ee/browser_ui/10_govern/change_vulnerability_status_spec.rb'
     - 'qa/qa/specs/features/ee/browser_ui/10_govern/group/group_ldap_sync_spec.rb'
     - 'qa/qa/specs/features/ee/browser_ui/10_govern/security_reports_spec.rb'
diff --git a/app/assets/javascripts/access_tokens/components/access_token_table_app.vue b/app/assets/javascripts/access_tokens/components/access_token_table_app.vue
index e72c0909059..bb45a9c4721 100644
--- a/app/assets/javascripts/access_tokens/components/access_token_table_app.vue
+++ b/app/assets/javascripts/access_tokens/components/access_token_table_app.vue
@@ -46,7 +46,8 @@ export default {
   i18n: {
     button: {
       revoke: s__('AccessTokens|Revoke'),
-      revokeAriaLabel: (name) => sprintf(s__('AccessTokens|Revoke %{name}'), { name }).trim(),
+      revokeAriaLabel: (name) =>
+        sprintf(s__('AccessTokens|Revoke %{name}'), { name }, false).trim(),
       rotate: s__('AccessTokens|Rotate'),
     },
     emptyDateField: __('Never'),
@@ -216,10 +217,14 @@ export default {
       }
     },
     modalMessage(tokenName, action) {
-      return sprintf(this.$options.i18n.modal.message[action], {
-        accessTokenType: this.accessTokenType,
-        tokenName,
-      });
+      return sprintf(
+        this.$options.i18n.modal.message[action],
+        {
+          accessTokenType: this.accessTokenType,
+          tokenName,
+        },
+        false,
+      );
     },
     sortingChanged(aRow, bRow, key) {
       if (['createdAt', 'lastUsedAt', 'expiresAt'].includes(key)) {
diff --git a/app/assets/javascripts/achievements/components/achievements_form.vue b/app/assets/javascripts/achievements/components/achievements_form.vue
index 3a99b48e7e0..42717b19136 100644
--- a/app/assets/javascripts/achievements/components/achievements_form.vue
+++ b/app/assets/javascripts/achievements/components/achievements_form.vue
@@ -240,7 +240,7 @@ export default {
               <div class="gl-overflow-hidden">
                 <div class="gl-flex">
                   <gl-button data-testid="select-file-button" @click="$refs.fileUpload.click()">
-                    {{ __('Choose File...') }}
+                    {{ __('Choose File…') }}
                   </gl-button>
                   <gl-button
                     v-if="filename"
diff --git a/app/assets/javascripts/analytics/devops_reports/components/devops_score.vue b/app/assets/javascripts/analytics/devops_reports/components/devops_score.vue
index 6dbc31312bd..2b9b961d50c 100644
--- a/app/assets/javascripts/analytics/devops_reports/components/devops_score.vue
+++ b/app/assets/javascripts/analytics/devops_reports/components/devops_score.vue
@@ -72,7 +72,7 @@ export default {
     <devops-score-callout />
     <gl-empty-state
       v-if="isEmpty"
-      :title="__('Data is still calculating...')"
+      :title="__('Data is still calculating…')"
       :svg-path="noDataImagePath"
     >
       <template #description>
diff --git a/app/assets/javascripts/credentials/components/credentials_filter_sort_app.vue b/app/assets/javascripts/credentials/components/credentials_filter_sort_app.vue
index f4904e51209..d4e71f63339 100644
--- a/app/assets/javascripts/credentials/components/credentials_filter_sort_app.vue
+++ b/app/assets/javascripts/credentials/components/credentials_filter_sort_app.vue
@@ -58,7 +58,7 @@ export default {
     <gl-filtered-search
       class="gl-min-w-0 gl-grow"
       :value="tokens"
-      :placeholder="s__('CredentialsInventory|Search or filter credentials...')"
+      :placeholder="s__('CredentialsInventory|Search or filter credentials…')"
       :available-tokens="availableTokens"
       terms-as-tokens
       @submit="search"
diff --git a/app/assets/javascripts/environments/components/environment_actions.vue b/app/assets/javascripts/environments/components/environment_actions.vue
index 3a4a7440c66..e93e0d0bc00 100644
--- a/app/assets/javascripts/environments/components/environment_actions.vue
+++ b/app/assets/javascripts/environments/components/environment_actions.vue
@@ -25,7 +25,7 @@ export default {
   },
   computed: {
     title() {
-      return __('Deploy to...');
+      return __('Deploy to…');
     },
     actionItems() {
       return this.actions.map((actionItem) => ({
diff --git a/app/assets/javascripts/ide/components/commit_sidebar/form.vue b/app/assets/javascripts/ide/components/commit_sidebar/form.vue
index 3bcb36837d4..6eff0e317ea 100644
--- a/app/assets/javascripts/ide/components/commit_sidebar/form.vue
+++ b/app/assets/javascripts/ide/components/commit_sidebar/form.vue
@@ -162,7 +162,7 @@ export default {
             data-testid="begin-commit-button"
             @click="beginCommit"
           >
-            {{ __('Create commit...') }}
+            {{ __('Create commit…') }}
           </gl-button>
         </div>
         <p class="gl-text-center gl-font-bold">{{ overviewText }}</p>
diff --git a/app/assets/javascripts/ide/components/file_templates/bar.vue b/app/assets/javascripts/ide/components/file_templates/bar.vue
index 9389a914c23..75a04ce3750 100644
--- a/app/assets/javascripts/ide/components/file_templates/bar.vue
+++ b/app/assets/javascripts/ide/components/file_templates/bar.vue
@@ -6,8 +6,8 @@ import { mapActions, mapGetters, mapState } from 'vuex';
 import { __ } from '~/locale';
 
 const barLabel = __('File templates');
-const templateListDropdownLabel = __('Choose a template...');
-const templateTypesDropdownLabel = __('Choose a type...');
+const templateListDropdownLabel = __('Choose a template…');
+const templateTypesDropdownLabel = __('Choose a type…');
 const undoButtonText = __('Undo');
 
 export default {
diff --git a/app/assets/javascripts/profile/edit/constants.js b/app/assets/javascripts/profile/edit/constants.js
index a6e7a5eb4ef..7a1c0879d4c 100644
--- a/app/assets/javascripts/profile/edit/constants.js
+++ b/app/assets/javascripts/profile/edit/constants.js
@@ -11,7 +11,7 @@ export const avatarI18n = {
   ),
   uploadAvatar: s__('Profiles|You can upload your avatar here'),
   uploadNewAvatar: s__('Profiles|Upload new avatar'),
-  chooseFile: s__('Profiles|Choose file...'),
+  chooseFile: s__('Profiles|Choose file…'),
   noFileChosen: s__('Profiles|No file chosen.'),
   maximumFileSize: s__('Profiles|The maximum file size allowed is 200 KiB.'),
   imageDimensions: s__('Profiles|The ideal image size is 192 x 192 pixels.'),
diff --git a/app/assets/javascripts/super_sidebar/components/create_menu.vue b/app/assets/javascripts/super_sidebar/components/create_menu.vue
index c56d71773e9..5fac253f57b 100644
--- a/app/assets/javascripts/super_sidebar/components/create_menu.vue
+++ b/app/assets/javascripts/super_sidebar/components/create_menu.vue
@@ -30,7 +30,7 @@ export default {
     GlTooltip: GlTooltipDirective,
   },
   i18n: {
-    createNew: __('Create new...'),
+    createNew: __('Create new…'),
   },
   inject: ['isImpersonating'],
   props: {
diff --git a/app/assets/javascripts/vue_shared/components/mr_more_dropdown.vue b/app/assets/javascripts/vue_shared/components/mr_more_dropdown.vue
index 235fa6a5134..76cb4d7402b 100644
--- a/app/assets/javascripts/vue_shared/components/mr_more_dropdown.vue
+++ b/app/assets/javascripts/vue_shared/components/mr_more_dropdown.vue
@@ -34,9 +34,9 @@ export default {
     markAsReady: __('Mark as ready'),
     markAsDraft: __('Mark as draft'),
     close: __('Close %{issuableType}'),
-    closing: __('Closing %{issuableType}...'),
+    closing: __('Closing %{issuableType}…'),
     reopen: __('Reopen %{issuableType}'),
-    reopening: __('Reopening %{issuableType}...'),
+    reopening: __('Reopening %{issuableType}…'),
     lock: __('Lock %{issuableType}'),
     mergeRequestActions: __('Merge request actions'),
   },
diff --git a/app/assets/javascripts/work_items/components/item_title.vue b/app/assets/javascripts/work_items/components/item_title.vue
index 9887d50283f..742f57769cd 100644
--- a/app/assets/javascripts/work_items/components/item_title.vue
+++ b/app/assets/javascripts/work_items/components/item_title.vue
@@ -11,7 +11,7 @@ export default {
     placeholder: {
       type: String,
       required: false,
-      default: __('Add a title...'),
+      default: __('Add a title…'),
     },
     disabled: {
       type: Boolean,
diff --git a/app/assets/javascripts/work_items/components/work_item_development/work_item_create_branch_merge_request_modal.vue b/app/assets/javascripts/work_items/components/work_item_development/work_item_create_branch_merge_request_modal.vue
index 903d9765f35..7f48ebb02a6 100644
--- a/app/assets/javascripts/work_items/components/work_item_development/work_item_create_branch_merge_request_modal.vue
+++ b/app/assets/javascripts/work_items/components/work_item_development/work_item_create_branch_merge_request_modal.vue
@@ -283,10 +283,10 @@ export default {
 
       if (target === WORK_ITEM_CREATE_ENTITY_MODAL_TARGET_SOURCE) {
         this.checkingSourceValidity = true;
-        this.sourceDescription = __('Checking source validity...');
+        this.sourceDescription = __('Checking source validity…');
       } else {
         this.checkingBranchValidity = true;
-        this.branchDescription = __('Checking branch validity...');
+        this.branchDescription = __('Checking branch validity…');
       }
 
       this.refCancelToken = axios.CancelToken.source();
diff --git a/app/helpers/ci/jobs_helper.rb b/app/helpers/ci/jobs_helper.rb
index 2080d5264f6..ff02505af10 100644
--- a/app/helpers/ci/jobs_helper.rb
+++ b/app/helpers/ci/jobs_helper.rb
@@ -9,7 +9,7 @@ module Ci
         "test_report_summary_url" => test_report_summary(project, build),
         "page_path" => project_job_path(project, build),
         "project_path" => project.full_path,
-        "artifact_help_url" => help_page_path('user/gitlab_com/_index.md', anchor: 'gitlab-cicd'),
+        "artifact_help_url" => help_page_path('user/gitlab_com/_index.md', anchor: 'cicd'),
         "deployment_help_url" => help_page_path('user/project/clusters/deploy_to_cluster.md', anchor: 'troubleshooting'),
         "runner_settings_url" => project_runners_path(build.project, anchor: 'js-runners-settings'),
         "retry_outdated_job_docs_url" => help_page_path('ci/pipelines/settings.md', anchor: 'prevent-outdated-deployment-jobs'),
diff --git a/app/helpers/nav/new_dropdown_helper.rb b/app/helpers/nav/new_dropdown_helper.rb
index 4f499271035..a7cd71a1230 100644
--- a/app/helpers/nav/new_dropdown_helper.rb
+++ b/app/helpers/nav/new_dropdown_helper.rb
@@ -6,7 +6,7 @@ module Nav
       return unless current_user
 
       menu_sections = []
-      data = { title: _('Create new...') }
+      data = { title: _('Create new…') }
 
       if project&.persisted?
         menu_sections.push(project_menu_section(project))
diff --git a/app/views/clusters/clusters/_banner.html.haml b/app/views/clusters/clusters/_banner.html.haml
index 1f3c0ef8dff..f186d9810ee 100644
--- a/app/views/clusters/clusters/_banner.html.haml
+++ b/app/views/clusters/clusters/_banner.html.haml
@@ -11,7 +11,7 @@
   alert_options: { class: 'hidden js-cluster-creating gl-mt-5 gl-mb-5' }) do |c|
   - c.with_body do
     = render Pajamas::SpinnerComponent.new(inline: true)
-    %span.gl-ml-2= s_('ClusterIntegration|Kubernetes cluster is being created...')
+    %span.gl-ml-2= s_('ClusterIntegration|Kubernetes cluster is being created…')
 
 = render Pajamas::AlertComponent.new(variant: :warning,
   alert_options: { class: 'hidden js-cluster-api-unreachable' }) do |c|
diff --git a/app/views/devise/confirmations/almost_there.haml b/app/views/devise/confirmations/almost_there.haml
index c45854abe87..7455a35a7ec 100644
--- a/app/views/devise/confirmations/almost_there.haml
+++ b/app/views/devise/confirmations/almost_there.haml
@@ -12,7 +12,7 @@
 
 .well-confirmation.gl-text-center.gl-mb-6
   %h1.gl-mt-0
-    = _("Almost there...")
+    = _("Almost there…")
   %p{ class: 'gl-mb-6 !gl-text-lg' }
     = _('Please check your email %{email} to confirm your account') % { email: user_email }
     %br
diff --git a/app/views/devise/registrations/_signup_box_form.html.haml b/app/views/devise/registrations/_signup_box_form.html.haml
index 17000c166b8..22574981ac5 100644
--- a/app/views/devise/registrations/_signup_box_form.html.haml
+++ b/app/views/devise/registrations/_signup_box_form.html.haml
@@ -53,7 +53,7 @@
     %p.validation-success.gl-text-success.gl-field-error-ignore.gl-mt-2.field-validation.hide
       = _('Username is available.')
     %p.validation-pending.gl-field-error-ignore.gl-mt-2.field-validation.hide
-      = _('Checking username availability...')
+      = _('Checking username availability…')
   - unless @invite_email.present?
     .form-group
       = f.label :email, _('Email')
diff --git a/app/views/ide/oauth_redirect.html.haml b/app/views/ide/oauth_redirect.html.haml
index e0ce9f9768c..bbe716c8015 100644
--- a/app/views/ide/oauth_redirect.html.haml
+++ b/app/views/ide/oauth_redirect.html.haml
@@ -1,3 +1,3 @@
 - page_title _("IDE")
 
-= render partial: 'shared/ide_root', locals: { data: new_ide_oauth_data, loading_text: _('Authenticating...') }
+= render partial: 'shared/ide_root', locals: { data: new_ide_oauth_data, loading_text: _('Authenticating…') }
diff --git a/app/views/projects/deployments/_actions.haml b/app/views/projects/deployments/_actions.haml
index e1c8992a28c..fecf71b44e7 100644
--- a/app/views/projects/deployments/_actions.haml
+++ b/app/views/projects/deployments/_actions.haml
@@ -3,7 +3,7 @@
   - if actions.present?
     .btn-group
       .dropdown
-        %button.dropdown.dropdown-new.btn.gl-button.btn-default.has-tooltip{ type: 'button', 'data-toggle' => 'dropdown', title: s_('Environments|Deploy to...') }
+        %button.dropdown.dropdown-new.btn.gl-button.btn-default.has-tooltip{ type: 'button', 'data-toggle' => 'dropdown', title: s_('Environments|Deploy to…') }
           = sprite_icon('play')
           = sprite_icon('chevron-down')
         %ul.dropdown-menu.dropdown-menu-right
diff --git a/app/views/user_settings/profiles/show.html.haml b/app/views/user_settings/profiles/show.html.haml
index bb4a6c354ee..37a91bead01 100644
--- a/app/views/user_settings/profiles/show.html.haml
+++ b/app/views/user_settings/profiles/show.html.haml
@@ -30,7 +30,7 @@
         %h5.gl-mt-0= s_("Profiles|Upload new avatar")
         .gl-flex.gl-items-center.gl-my-3
           = render Pajamas::ButtonComponent.new(button_options: { class: 'js-choose-user-avatar-button' }) do
-            = s_("Profiles|Choose file...")
+            = s_("Profiles|Choose file…")
           %span.gl-ml-3.js-avatar-filename= s_("Profiles|No file chosen.")
           = f.file_field :avatar, class: 'js-user-avatar-input hidden', accept: 'image/*'
         .form-text.gl-text-subtle
diff --git a/config/gitlab_loose_foreign_keys.yml b/config/gitlab_loose_foreign_keys.yml
index a66599e1061..dc9253314ae 100644
--- a/config/gitlab_loose_foreign_keys.yml
+++ b/config/gitlab_loose_foreign_keys.yml
@@ -529,6 +529,10 @@ project_security_statistics:
   - table: projects
     column: project_id
     on_delete: async_delete
+project_states:
+  - table: projects
+    column: project_id
+    on_delete: async_delete
 projects:
   - table: users
     column: marked_for_deletion_by_user_id
diff --git a/db/post_migrate/20250320180620_remove_projects_project_states_project_id_fk.rb b/db/post_migrate/20250320180620_remove_projects_project_states_project_id_fk.rb
new file mode 100644
index 00000000000..2e64d2789ad
--- /dev/null
+++ b/db/post_migrate/20250320180620_remove_projects_project_states_project_id_fk.rb
@@ -0,0 +1,21 @@
+# frozen_string_literal: true
+
+class RemoveProjectsProjectStatesProjectIdFk < Gitlab::Database::Migration[2.2]
+  milestone '17.11'
+  disable_ddl_transaction!
+
+  FOREIGN_KEY_NAME = "fk_rails_a6e5821877"
+
+  def up
+    with_lock_retries do
+      remove_foreign_key_if_exists(:project_states, :projects,
+        name: FOREIGN_KEY_NAME, reverse_lock_order: true)
+    end
+  end
+
+  def down
+    add_concurrent_foreign_key(:project_states, :projects,
+      name: FOREIGN_KEY_NAME, column: :project_id,
+      target_column: :id, on_delete: :cascade)
+  end
+end
diff --git a/db/schema_migrations/20250320180620 b/db/schema_migrations/20250320180620
new file mode 100644
index 00000000000..00bbc55f3a1
--- /dev/null
+++ b/db/schema_migrations/20250320180620
@@ -0,0 +1 @@
+4fb80dd28bd570ee99715b8f53ddecc6bf0d0c7041b8fa444cd876eb4575438f
\ No newline at end of file
diff --git a/db/structure.sql b/db/structure.sql
index 21b6aac017a..2bee106162d 100644
--- a/db/structure.sql
+++ b/db/structure.sql
@@ -43046,9 +43046,6 @@ ALTER TABLE ONLY user_preferences
 ALTER TABLE ONLY sentry_issues
     ADD CONSTRAINT fk_rails_a6a9612965 FOREIGN KEY (issue_id) REFERENCES issues(id) ON DELETE CASCADE;
 
-ALTER TABLE ONLY project_states
-    ADD CONSTRAINT fk_rails_a6e5821877 FOREIGN KEY (project_id) REFERENCES projects(id) ON DELETE CASCADE;
-
 ALTER TABLE ONLY user_permission_export_uploads
     ADD CONSTRAINT fk_rails_a7130085e3 FOREIGN KEY (user_id) REFERENCES users(id) ON DELETE CASCADE;
 
diff --git a/doc/administration/auth/_index.md b/doc/administration/auth/_index.md
index 376e0e8553c..cf6d7732997 100644
--- a/doc/administration/auth/_index.md
+++ b/doc/administration/auth/_index.md
@@ -33,7 +33,7 @@ UltraAuth has removed their software which supports OmniAuth integration. We hav
 The external authentication and authorization providers may support the following capabilities.
 For more information, see the links shown on this page for each external provider.
 
-| Capability                                      | GitLab.com                              | Self-managed                       |
+| Capability                                      | GitLab.com                              | GitLab Self-Managed                       |
 |-------------------------------------------------|-----------------------------------------|------------------------------------|
 | **User Provisioning**                           | SCIM<br>SAML <sup>1</sup> | LDAP <sup>1</sup><br>SAML <sup>1</sup><br>[OmniAuth Providers](../../integration/omniauth.md#supported-providers) <sup>1</sup><br>SCIM  |
 | **User Detail Updating** (not group management) | Not Available                           | LDAP Sync                          |
diff --git a/doc/administration/backup_restore/backup_gitlab.md b/doc/administration/backup_restore/backup_gitlab.md
index 6c8b7d43fa9..a38706800e6 100644
--- a/doc/administration/backup_restore/backup_gitlab.md
+++ b/doc/administration/backup_restore/backup_gitlab.md
@@ -187,7 +187,7 @@ You may also want to back up any TLS keys and certificates (`/etc/gitlab/ssl`, `
 to avoid man-in-the-middle attack warnings if you have to perform a full machine restore.
 
 In the unlikely event that the secrets file is lost, see
-[When the secrets file is lost](../backup_restore/troubleshooting_backup_gitlab.md#when-the-secrets-file-is-lost).
+[When the secrets file is lost](troubleshooting_backup_gitlab.md#when-the-secrets-file-is-lost).
 
 ### Other data
 
diff --git a/doc/administration/backup_restore/restore_gitlab.md b/doc/administration/backup_restore/restore_gitlab.md
index 378d97ab78f..98698e44fae 100644
--- a/doc/administration/backup_restore/restore_gitlab.md
+++ b/doc/administration/backup_restore/restore_gitlab.md
@@ -53,7 +53,7 @@ To restore a backup, **you must also restore the GitLab secrets**.
 If you are migrating to a new GitLab instance, you must copy the GitLab secrets file from the old server.
 These include the database encryption key, [CI/CD variables](../../ci/variables/_index.md), and
 variables used for [two-factor authentication](../../user/profile/account/two_factor_authentication.md).
-Without the keys, [multiple issues occur](../backup_restore/troubleshooting_backup_gitlab.md#when-the-secrets-file-is-lost), including loss of access by users with [two-factor authentication enabled](../../user/profile/account/two_factor_authentication.md),
+Without the keys, [multiple issues occur](troubleshooting_backup_gitlab.md#when-the-secrets-file-is-lost), including loss of access by users with [two-factor authentication enabled](../../user/profile/account/two_factor_authentication.md),
 and GitLab Runners cannot sign in.
 
 Restore:
diff --git a/doc/administration/backup_restore/troubleshooting_backup_gitlab.md b/doc/administration/backup_restore/troubleshooting_backup_gitlab.md
index caa5514818f..b33acd19d76 100644
--- a/doc/administration/backup_restore/troubleshooting_backup_gitlab.md
+++ b/doc/administration/backup_restore/troubleshooting_backup_gitlab.md
@@ -9,7 +9,7 @@ When you back up GitLab, you might encounter the following issues.
 
 ## When the secrets file is lost
 
-If you didn't [back up the secrets file](../backup_restore/backup_gitlab.md#storing-configuration-files), you
+If you didn't [back up the secrets file](backup_gitlab.md#storing-configuration-files), you
 must complete several steps to get GitLab working properly again.
 
 The secrets file is responsible for storing the encryption key for the columns
@@ -266,7 +266,7 @@ Backup failed
 If this happens, examine the following:
 
 - Confirm there is sufficient disk space for the Gzip operation. It's not uncommon for backups that
-  use the [default strategy](../backup_restore/backup_gitlab.md#backup-strategy-option) to require half the instance size
+  use the [default strategy](backup_gitlab.md#backup-strategy-option) to require half the instance size
   in free disk space during backup creation.
 - If NFS is being used, check if the mount option `timeout` is set. The
   default is `600`, and changing this to smaller values results in this error.
diff --git a/doc/administration/cicd/_index.md b/doc/administration/cicd/_index.md
index f90f17e6075..087b27a675e 100644
--- a/doc/administration/cicd/_index.md
+++ b/doc/administration/cicd/_index.md
@@ -95,7 +95,7 @@ can't run more frequently than the worker.
 
 The default frequency of the pipeline schedule worker is `3-59/10 * * * *` (every ten minutes,
 starting with `0:03`, `0:13`, `0:23`, and so on). The default frequency for GitLab.com
-is listed in the [GitLab.com settings](../../user/gitlab_com/_index.md#gitlab-cicd).
+is listed in the [GitLab.com settings](../../user/gitlab_com/_index.md#cicd).
 
 To change the frequency of the pipeline schedule worker:
 
diff --git a/doc/administration/dedicated/architecture.md b/doc/administration/dedicated/architecture.md
index 73a1ae290d6..27438071ef9 100644
--- a/doc/administration/dedicated/architecture.md
+++ b/doc/administration/dedicated/architecture.md
@@ -56,7 +56,7 @@ Geo does not use an active-active failover configuration. For more information,
 
 Optionally, private connectivity is available for your GitLab Dedicated instance, using [AWS PrivateLink](https://aws.amazon.com/privatelink/) as a connection gateway.
 
-Both [inbound](../dedicated/configure_instance/network_security.md#inbound-private-link) and [outbound](../dedicated/configure_instance/network_security.md#outbound-private-link) private links are supported.
+Both [inbound](configure_instance/network_security.md#inbound-private-link) and [outbound](configure_instance/network_security.md#outbound-private-link) private links are supported.
 
 ![Diagram of a GitLab-managed AWS VPC using AWS PrivateLink to connect with a customer-managed AWS VPC.](img/privatelink_diagram_v17_1.png)
 
diff --git a/doc/administration/dedicated/configure_instance/_index.md b/doc/administration/dedicated/configure_instance/_index.md
index 2834597d9c1..d77c3cc75e5 100644
--- a/doc/administration/dedicated/configure_instance/_index.md
+++ b/doc/administration/dedicated/configure_instance/_index.md
@@ -33,15 +33,15 @@ You can use Switchboard to make limited configuration changes to your GitLab Ded
 
 The following configuration settings are available in Switchboard:
 
-- [IP allowlist](../configure_instance/network_security.md#ip-allowlist)
-- [SAML settings](../configure_instance/saml.md)
-- [Custom certificates](../configure_instance/network_security.md#custom-certificates)
-- [Outbound private links](../configure_instance/network_security.md#outbound-private-link)
-- [Private hosted zones](../configure_instance/network_security.md#private-hosted-zones)
+- [IP allowlist](network_security.md#ip-allowlist)
+- [SAML settings](saml.md)
+- [Custom certificates](network_security.md#custom-certificates)
+- [Outbound private links](network_security.md#outbound-private-link)
+- [Private hosted zones](network_security.md#private-hosted-zones)
 
 Prerequisites:
 
-- You must have the [Admin](../configure_instance/users_notifications.md#add-switchboard-users) role.
+- You must have the [Admin](users_notifications.md#add-switchboard-users) role.
 
 To make a configuration change:
 
@@ -63,7 +63,7 @@ When you apply changes immediately:
 - You can save multiple changes and apply them in one batch.
 
 After the deployment job is complete, you receive an email notification. Check your spam folder if you do not see a notification in your main inbox.
-All users with access to view or edit your tenant in Switchboard receive a notification for each change. For more information, see [Manage Switchboard notification preferences](../configure_instance/users_notifications.md#manage-notification-preferences).
+All users with access to view or edit your tenant in Switchboard receive a notification for each change. For more information, see [Manage Switchboard notification preferences](users_notifications.md#manage-notification-preferences).
 
 {{< alert type="note" >}}
 
diff --git a/doc/administration/dedicated/create_instance.md b/doc/administration/dedicated/create_instance.md
index b2e7c8ec727..c5fb15d2c91 100644
--- a/doc/administration/dedicated/create_instance.md
+++ b/doc/administration/dedicated/create_instance.md
@@ -184,7 +184,7 @@ After you sign in to Switchboard, follow these steps to create your instance:
      You can use the same option as your primary or secondary regions, or choose a different region for [increased redundancy](../../subscriptions/gitlab_dedicated/data_residency_and_high_availability.md#disaster-recovery).
 
    - **Time zone**: Select a weekly four-hour time slot when GitLab performs routine
-     maintenance and upgrades. For more information, see [maintenance windows](../dedicated/maintenance.md#maintenance-windows).
+     maintenance and upgrades. For more information, see [maintenance windows](maintenance.md#maintenance-windows).
 
 1. Optional. On the **Security** page, add your [AWS KMS keys](https://docs.aws.amazon.com/kms/latest/developerguide/overview.html) for encrypted AWS services. If you do not add keys, GitLab generates encryption keys for your instance. For more information, see [encrypting your data at rest](#encrypted-data-at-rest-byok).
 
@@ -221,17 +221,17 @@ To access and configure your GitLab Dedicated instance:
 1. Go to the tenant URL for your GitLab Dedicated instance and sign in with your temporary root credentials.
 1. [Change your temporary root password](../../user/profile/user_passwords.md#change-your-password) to a new secure password.
 1. Go to the Admin area and [add the license key](../license_file.md#add-license-in-the-admin-area) for your GitLab Dedicated subscription.
-1. Return to Switchboard and [add users](../dedicated/configure_instance/users_notifications.md#add-switchboard-users), if needed.
-1. Review the [release rollout schedule](../dedicated/maintenance.md#release-rollout-schedule) for upgrades and maintenance.
+1. Return to Switchboard and [add users](configure_instance/users_notifications.md#add-switchboard-users), if needed.
+1. Review the [release rollout schedule](maintenance.md#release-rollout-schedule) for upgrades and maintenance.
 
 Also plan ahead if you need the following GitLab Dedicated features:
 
-- [Inbound Private Link](../dedicated/configure_instance/network_security.md#inbound-private-link)
-- [Outbound Private Link](../dedicated/configure_instance/network_security.md#outbound-private-link)
-- [SAML SSO](../dedicated/configure_instance/saml.md)
-- [Bring your own domain](../dedicated/configure_instance/network_security.md#bring-your-own-domain-byod)
+- [Inbound Private Link](configure_instance/network_security.md#inbound-private-link)
+- [Outbound Private Link](configure_instance/network_security.md#outbound-private-link)
+- [SAML SSO](configure_instance/saml.md)
+- [Bring your own domain](configure_instance/network_security.md#bring-your-own-domain-byod)
 
-To view all available infrastructure configuration options, see [Configure your GitLab Dedicated instance](../dedicated/configure_instance/_index.md).
+To view all available infrastructure configuration options, see [Configure your GitLab Dedicated instance](configure_instance/_index.md).
 
 {{< alert type="note" >}}
 
diff --git a/doc/administration/dedicated/maintenance.md b/doc/administration/dedicated/maintenance.md
index 05e91e07256..59303e6b2d1 100644
--- a/doc/administration/dedicated/maintenance.md
+++ b/doc/administration/dedicated/maintenance.md
@@ -77,6 +77,6 @@ GitLab performs emergency maintenance per
 Emergency maintenance is initiated when urgent actions need to be executed by GitLab on a
 GitLab Dedicated tenant instance. For example, when a critical (S1) security vulnerability requires urgent patching, GitLab performs emergency maintenance to upgrade your tenant instance to a secure version. This maintenance can occur outside scheduled maintenance windows.
 
-GitLab provides advance emergency maintenance notice when possible and sends complete details after the issue is resolved. The GitLab Support team creates a support ticket and notifies all [Switchboard users](../dedicated/create_instance.md#step-1-get-access-to-switchboard) by email.
+GitLab provides advance emergency maintenance notice when possible and sends complete details after the issue is resolved. The GitLab Support team creates a support ticket and notifies all [Switchboard users](create_instance.md#step-1-get-access-to-switchboard) by email.
 
 You cannot postpone emergency maintenance, because the same process must be applied to all GitLab Dedicated instances to ensure their security and availability.
diff --git a/doc/administration/dedicated/monitor.md b/doc/administration/dedicated/monitor.md
index d656372565f..40d34f63e6a 100644
--- a/doc/administration/dedicated/monitor.md
+++ b/doc/administration/dedicated/monitor.md
@@ -46,7 +46,7 @@ For information about how to access S3 buckets after you have the name, see the
 
 The Amazon S3 bucket contains a combination of infrastructure logs and application logs from the GitLab [log system](../logs/_index.md).
 
-The logs in the bucket are encrypted using an AWS KMS key managed by GitLab. If you choose to enable [BYOK](../dedicated/create_instance.md#encrypted-data-at-rest-byok), the application logs are not encrypted with the key you provide.
+The logs in the bucket are encrypted using an AWS KMS key managed by GitLab. If you choose to enable [BYOK](create_instance.md#encrypted-data-at-rest-byok), the application logs are not encrypted with the key you provide.
 
 <!-- vale gitlab_base.Spelling = NO -->
 
diff --git a/doc/administration/dedicated/tenant_overview.md b/doc/administration/dedicated/tenant_overview.md
index 16b173814ed..56b3fbef5e0 100644
--- a/doc/administration/dedicated/tenant_overview.md
+++ b/doc/administration/dedicated/tenant_overview.md
@@ -52,10 +52,10 @@ The **Maintenance windows** section displays the:
 
 {{< alert type="note" >}}
 
-Each Sunday night in UTC, Switchboard updates to display the planned GitLab version upgrades for the upcoming week's maintenance windows. For more information, see [Maintenance windows](../dedicated/maintenance.md#maintenance-windows).
+Each Sunday night in UTC, Switchboard updates to display the planned GitLab version upgrades for the upcoming week's maintenance windows. For more information, see [Maintenance windows](maintenance.md#maintenance-windows).
 
 {{< /alert >}}
 
 ## Hosted runners
 
-The **Hosted runners** section shows the [hosted runners](../dedicated/hosted_runners.md) associated with your instance.
+The **Hosted runners** section shows the [hosted runners](hosted_runners.md) associated with your instance.
diff --git a/doc/administration/geo/replication/faq.md b/doc/administration/geo/replication/faq.md
index c645bb4b8c3..0cad9ce02f5 100644
--- a/doc/administration/geo/replication/faq.md
+++ b/doc/administration/geo/replication/faq.md
@@ -85,11 +85,11 @@ No, Geo sites can be based on different reference architectures. For example, yo
 
 ## Does Geo replicate archived projects?
 
-Yes, provided they are not excluded through [selective sync](../replication/selective_synchronization.md).
+Yes, provided they are not excluded through [selective sync](selective_synchronization.md).
 
 ## Does Geo replicate personal projects?
 
-Yes, provided they are not excluded through [selective sync](../replication/selective_synchronization.md).
+Yes, provided they are not excluded through [selective sync](selective_synchronization.md).
 
 ## Are delayed deletion projects replicated to secondary sites?
 
diff --git a/doc/administration/geo/replication/upgrading_the_geo_sites.md b/doc/administration/geo/replication/upgrading_the_geo_sites.md
index b881cfc77be..d6b0ae32d30 100644
--- a/doc/administration/geo/replication/upgrading_the_geo_sites.md
+++ b/doc/administration/geo/replication/upgrading_the_geo_sites.md
@@ -43,7 +43,7 @@ If you want to avoid downtime, consider using [zero-downtime upgrades](../../../
 To upgrade the Geo sites when a new GitLab version is released, upgrade **primary**
 and all **secondary** sites:
 
-1. Optional. [Pause replication on each **secondary** site](../replication/pause_resume_replication.md)
+1. Optional. [Pause replication on each **secondary** site](pause_resume_replication.md)
    to protect the disaster recovery (DR) capability of the **secondary** sites.
 1. SSH into each node of the **primary** site.
 1. [Upgrade GitLab on the **primary** site](../../../update/package/_index.md#by-using-the-official-repositories-recommended).
diff --git a/doc/administration/geo/setup/database.md b/doc/administration/geo/setup/database.md
index 47f9e5319d4..23f434b790d 100644
--- a/doc/administration/geo/setup/database.md
+++ b/doc/administration/geo/setup/database.md
@@ -27,7 +27,7 @@ the roles cannot perform all necessary configuration steps. In this case, use th
 {{< alert type="note" >}}
 
 The stages of the setup process must be completed in the documented order.
-If not, [complete all prior stages](../setup/_index.md#using-linux-package-installations) before proceeding.
+If not, [complete all prior stages](_index.md#using-linux-package-installations) before proceeding.
 {{< /alert >}}
 
 Ensure the **secondary** site is running the same version of GitLab Enterprise Edition as the **primary** site. Confirm you have added a license for a [Premium or Ultimate subscription](https://about.gitlab.com/pricing/) to your **primary** site.
diff --git a/doc/administration/get_started.md b/doc/administration/get_started.md
index a08314efddd..b44630d8f36 100644
--- a/doc/administration/get_started.md
+++ b/doc/administration/get_started.md
@@ -287,7 +287,7 @@ You can make changes to your default rate limits from the **Admin** area. For mo
 
 ### GitLab SaaS-specific block and error responses
 
-- [403 forbidden error](../user/gitlab_com/_index.md#gitlabcom-specific-rate-limits): If the error occurs for all GitLab SaaS requests, look for an automated process that could have triggered a block. For more assistance, contact GitLab support with your error details, including the affected IP address.
+- [403 forbidden error](../user/gitlab_com/_index.md#rate-limits-on-gitlabcom): If the error occurs for all GitLab SaaS requests, look for an automated process that could have triggered a block. For more assistance, contact GitLab support with your error details, including the affected IP address.
 - [HAProxy API throttle](../user/gitlab_com/_index.md#haproxy): GitLab SaaS responds with HTTP status code 429 to API requests that exceed 10 requests per second, per IP address.
 - [Protected paths throttle](../user/gitlab_com/_index.md#protected-paths-throttle): GitLab SaaS responds with HTTP status code 429 to POST requests at protected paths that exceed 10 requests per minute, per IP address.
 - [Git and container registry failed authentication ban](../user/gitlab_com/_index.md#git-and-container-registry-failed-authentication-ban): GitLab SaaS responds with HTTP status code 403 for one hour if it receives 30 failed authentication requests in three minutes from a single IP address.
diff --git a/doc/administration/gitaly/gitaly_geo_capabilities.md b/doc/administration/gitaly/gitaly_geo_capabilities.md
index 8eb84fe6df1..5b142a1c46a 100644
--- a/doc/administration/gitaly/gitaly_geo_capabilities.md
+++ b/doc/administration/gitaly/gitaly_geo_capabilities.md
@@ -14,7 +14,7 @@ The following tables are intended to guide you to choose the right combination o
 
 | Capability | Availability | Recoverability | Data Resiliency | Performance | Risks/Trade-offs|
 |------------|--------------|----------------|-----------------|-------------|-----------------|
-|Gitaly Cluster | Very high - tolerant of node failures | RTO for a single node of 10 s with no manual intervention | Data is stored on multiple nodes | Good - While writes may take slightly longer due to voting, read distribution improves read speeds | **Trade-off** - Slight decrease in write speed for redundant, strongly-consistent storage solution. **Risks** - [Does not support snapshot backups](../gitaly/_index.md#snapshot-backup-and-recovery), GitLab backup task can be slow for large data sets |
+|Gitaly Cluster | Very high - tolerant of node failures | RTO for a single node of 10 s with no manual intervention | Data is stored on multiple nodes | Good - While writes may take slightly longer due to voting, read distribution improves read speeds | **Trade-off** - Slight decrease in write speed for redundant, strongly-consistent storage solution. **Risks** - [Does not support snapshot backups](_index.md#snapshot-backup-and-recovery), GitLab backup task can be slow for large data sets |
 |Gitaly Shards | Single storage location is a single point of failure | Would need to restore only shards which failed | Single point of failure | Good - can allocate repositories to shards to spread load | **Trade-off** - Need to manually configure repositories into different shards to balance loads / storage space **Risks** - Single point of failure relies on recovery process when single-node failure occurs |
 
 ## Geo capabilities
diff --git a/doc/administration/gitlab_duo_self_hosted/_index.md b/doc/administration/gitlab_duo_self_hosted/_index.md
index 9c6adda0873..9087e033032 100644
--- a/doc/administration/gitlab_duo_self_hosted/_index.md
+++ b/doc/administration/gitlab_duo_self_hosted/_index.md
@@ -87,8 +87,8 @@ You can use the following GitLab Duo Chat features with GitLab Duo Self-Hosted:
 
 Before setting up the GitLab Duo Self-Hosted infrastructure, you must have:
 
-- A [supported model](../gitlab_duo_self_hosted/supported_models_and_hardware_requirements.md) (either cloud-based or on-premises).
-- A [supported serving platform](../gitlab_duo_self_hosted/supported_llm_serving_platforms.md) (either cloud-based or on-premises).
+- A [supported model](supported_models_and_hardware_requirements.md) (either cloud-based or on-premises).
+- A [supported serving platform](supported_llm_serving_platforms.md) (either cloud-based or on-premises).
 - A [locally hosted AI gateway](../../install/install_ai_gateway.md).
 - [Ultimate with GitLab Duo Enterprise](https://about.gitlab.com/solutions/gitlab-duo-pro/sales/?toggle=gitlab-duo-pro).
 - GitLab 17.9 or later.
@@ -105,7 +105,7 @@ The differences between these options are:
 | Feature | Self-hosted AI gateway | GitLab.com AI gateway |
 |---------|------------------------|------------------------|
 | Infrastructure requirements | Requires hosting your own AI gateway and models | No additional infrastructure needed |
-| Model options | Choose from [supported models](../gitlab_duo_self_hosted/supported_models_and_hardware_requirements.md) | Uses the default GitLab external vendor LLMs |
+| Model options | Choose from [supported models](supported_models_and_hardware_requirements.md) | Uses the default GitLab external vendor LLMs |
 | Network requirements | Can operate in fully isolated networks | Requires internet connectivity |
 | Responsibilities | You set up your infrastructure, and do your own maintenance | GitLab does the set up and maintenance |
 
@@ -153,19 +153,19 @@ To set up a fully isolated GitLab Duo Self-Hosted infrastructure:
 
 1. **Install a Large Language Model (LLM) Serving Infrastructure**
 
-   - We support various platforms for serving and hosting your LLMs, such as vLLM, AWS Bedrock, and Azure OpenAI. To help you choose the most suitable option for effectively deploying your models, see the [supported LLM platforms documentation](../gitlab_duo_self_hosted/supported_llm_serving_platforms.md) for more information on each platform's features.
+   - We support various platforms for serving and hosting your LLMs, such as vLLM, AWS Bedrock, and Azure OpenAI. To help you choose the most suitable option for effectively deploying your models, see the [supported LLM platforms documentation](supported_llm_serving_platforms.md) for more information on each platform's features.
 
-   - We provide a comprehensive matrix of supported models along with their specific features and hardware requirements. To help select models that best align with your infrastructure needs for optimal performance, see the [supported models and hardware requirements documentation](../gitlab_duo_self_hosted/supported_models_and_hardware_requirements.md).
+   - We provide a comprehensive matrix of supported models along with their specific features and hardware requirements. To help select models that best align with your infrastructure needs for optimal performance, see the [supported models and hardware requirements documentation](supported_models_and_hardware_requirements.md).
 
 1. **Install the GitLab AI gateway**
    [Install the AI gateway](../../install/install_ai_gateway.md) to efficiently configure your AI infrastructure.
 
 1. **Configure GitLab Duo features**
-   See the [Configure GitLab Duo features documentation](../gitlab_duo_self_hosted/configure_duo_features.md) for instructions on how to customize your environment to effectively meet your operational needs.
+   See the [Configure GitLab Duo features documentation](configure_duo_features.md) for instructions on how to customize your environment to effectively meet your operational needs.
 
 1. **Enable logging**
-   You can find configuration details for enabling logging in your environment. For help in using logs to track and manage your system's performance effectively, see the [logging documentation](../gitlab_duo_self_hosted/logging.md).
+   You can find configuration details for enabling logging in your environment. For help in using logs to track and manage your system's performance effectively, see the [logging documentation](logging.md).
 
 ## Related topics
 
-- [Troubleshooting](../gitlab_duo_self_hosted/troubleshooting.md)
+- [Troubleshooting](troubleshooting.md)
diff --git a/doc/administration/gitlab_duo_self_hosted/supported_llm_serving_platforms.md b/doc/administration/gitlab_duo_self_hosted/supported_llm_serving_platforms.md
index 9120ec1faf5..3d932720cba 100644
--- a/doc/administration/gitlab_duo_self_hosted/supported_llm_serving_platforms.md
+++ b/doc/administration/gitlab_duo_self_hosted/supported_llm_serving_platforms.md
@@ -78,7 +78,7 @@ For more information on:
 
 - vLLM supported models, see the [vLLM Supported Models documentation](https://docs.vllm.ai/en/latest/models/supported_models.html).
 - Available options when using vLLM to run a model, see the [vLLM documentation on engine arguments](https://docs.vllm.ai/en/stable/usage/engine_args.html).
-- The hardware needed for the models, see the [Supported models and Hardware requirements documentation](../gitlab_duo_self_hosted/supported_models_and_hardware_requirements.md).
+- The hardware needed for the models, see the [Supported models and Hardware requirements documentation](supported_models_and_hardware_requirements.md).
 
 Examples:
 
diff --git a/doc/administration/gitlab_duo_self_hosted/troubleshooting.md b/doc/administration/gitlab_duo_self_hosted/troubleshooting.md
index 035d9cade19..c6a6404b9dc 100644
--- a/doc/administration/gitlab_duo_self_hosted/troubleshooting.md
+++ b/doc/administration/gitlab_duo_self_hosted/troubleshooting.md
@@ -432,7 +432,7 @@ If problem persists, report the issue to the GitLab support team.
 You might get an error that states
 `I'm sorry, I couldn't respond in time. Please try again. Error code: A1002`.
 
-This error occurs when no events are returned from AI gateway or GitLab failed to parse the events. Check the [AI Gateway logs](../gitlab_duo_self_hosted/logging.md) for any errors.
+This error occurs when no events are returned from AI gateway or GitLab failed to parse the events. Check the [AI Gateway logs](logging.md) for any errors.
 
 ### Error A1003
 
@@ -478,7 +478,7 @@ This error typically occurs due to issues with streaming from the model to the A
 
    If streaming is working, chunked responses should be displayed. If it is not, it will likely show an empty response.
 
-1. Check the [AI gateway logs](../gitlab_duo_self_hosted/logging.md) for specific error messages, because this is usually a model deployment issue.
+1. Check the [AI gateway logs](logging.md) for specific error messages, because this is usually a model deployment issue.
 
 1. To validate the connection, disable the streaming by setting the `AIGW_CUSTOM_MODELS__DISABLE_STREAMING` environment variable in your AI gateway container:
 
diff --git a/doc/administration/instance_limits.md b/doc/administration/instance_limits.md
index ea5a38debee..642d3f205d4 100644
--- a/doc/administration/instance_limits.md
+++ b/doc/administration/instance_limits.md
@@ -197,7 +197,7 @@ This endpoint has been requested too many times. Try again later.
 
 {{< history >}}
 
-- [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/368926) in GitLab 17.10 [with a flag](../administration/feature_flags.md) named `autocomplete_users_rate_limit`. Disabled by default.
+- [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/368926) in GitLab 17.10 [with a flag](feature_flags.md) named `autocomplete_users_rate_limit`. Disabled by default.
 
 {{< /history >}}
 
@@ -465,7 +465,7 @@ If a new pipeline would cause the total number of jobs to exceed the limit, the
 fails with a `job_activity_limit_exceeded` error.
 
 - On GitLab.com, a limit is
-  [defined for each subscription tier](../user/gitlab_com/_index.md#gitlab-cicd),
+  [defined for each subscription tier](../user/gitlab_com/_index.md#cicd),
   and this limit affects all projects with that tier.
 - On GitLab Self-Managed, [Premium or Ultimate](https://about.gitlab.com/pricing/) subscriptions,
   this limit is defined under a `default` plan that affects all
@@ -525,7 +525,7 @@ If a new subscription would cause the total number of subscription to exceed the
 limit, the subscription is considered invalid.
 
 - On GitLab.com, a limit is
-  [defined for each subscription tier](../user/gitlab_com/_index.md#gitlab-cicd),
+  [defined for each subscription tier](../user/gitlab_com/_index.md#cicd),
   and this limit affects all projects with that tier.
 - On GitLab Self-Managed [Premium or Ultimate](https://about.gitlab.com/pricing/),
   this limit is defined under a `default` plan that
@@ -557,7 +557,7 @@ To set this limit to `100` on a GitLab Self-Managed instance, run the following
 Plan.default.actual_limits.update!(pipeline_triggers: 100)
 ```
 
-This limit is [enabled on GitLab.com](../user/gitlab_com/_index.md#gitlab-cicd).
+This limit is [enabled on GitLab.com](../user/gitlab_com/_index.md#cicd).
 
 ### Number of pipeline schedules
 
@@ -567,7 +567,7 @@ would cause the total number of pipeline schedules to exceed the limit, the
 pipeline schedule is not created.
 
 On GitLab.com, the limit is
-[defined for each subscription tier](../user/gitlab_com/_index.md#gitlab-cicd),
+[defined for each subscription tier](../user/gitlab_com/_index.md#cicd),
 and this limit affects all projects with that tier.
 
 On GitLab Self-Managed [Premium or Ultimate](https://about.gitlab.com/pricing/),
@@ -603,7 +603,7 @@ To set this limit to `1440` on a GitLab Self-Managed instance, run the following
 Plan.default.actual_limits.update!(ci_daily_pipeline_schedule_triggers: 1440)
 ```
 
-This limit is [enabled on GitLab.com](../user/gitlab_com/_index.md#gitlab-cicd).
+This limit is [enabled on GitLab.com](../user/gitlab_com/_index.md#cicd).
 
 ### Limit the number of schedule rules defined for security policy project
 
@@ -627,7 +627,7 @@ To set this limit for a GitLab Self-Managed instance, run the following in the
 Plan.default.actual_limits.update!(security_policy_scan_execution_schedules: 100)
 ```
 
-This limit is [enabled on GitLab.com](../user/gitlab_com/_index.md#gitlab-cicd).
+This limit is [enabled on GitLab.com](../user/gitlab_com/_index.md#cicd).
 
 ### CI/CD variable limits
 
@@ -884,7 +884,7 @@ Plan.default.actual_limits.update!(dotenv_variables: 100)
 You can also set this limit by using the [GitLab UI](settings/continuous_integration.md#set-cicd-limits) or the
 [Plan limits API](../api/plan_limits.md).
 
-This limit is [enabled on GitLab.com](../user/gitlab_com/_index.md#gitlab-cicd).
+This limit is [enabled on GitLab.com](../user/gitlab_com/_index.md#cicd).
 
 ### Limit dotenv file size
 
diff --git a/doc/administration/logs/_index.md b/doc/administration/logs/_index.md
index 202ac9abf48..48e89f0994d 100644
--- a/doc/administration/logs/_index.md
+++ b/doc/administration/logs/_index.md
@@ -30,7 +30,7 @@ The log system is similar to [audit events](../audit_event_reports.md).
 For more information, see also:
 
 - [Customizing logging on Linux package installations](https://docs.gitlab.com/omnibus/settings/logs.html)
-- [Parsing and analyzing GitLab logs in JSON format](../logs/log_parsing.md)
+- [Parsing and analyzing GitLab logs in JSON format](log_parsing.md)
 
 ## Log Levels
 
diff --git a/doc/administration/logs/log_parsing.md b/doc/administration/logs/log_parsing.md
index b256e21101b..180d7f7e0ff 100644
--- a/doc/administration/logs/log_parsing.md
+++ b/doc/administration/logs/log_parsing.md
@@ -14,7 +14,7 @@ title: Parsing GitLab logs with `jq`
 
 We recommend using log aggregation and search tools like Kibana and Splunk whenever possible,
 but if they are not available you can still quickly parse
-[GitLab logs](../logs/_index.md) in JSON format
+[GitLab logs](_index.md) in JSON format
 using [`jq`](https://stedolan.github.io/jq/).
 
 {{< alert type="note" >}}
@@ -34,7 +34,7 @@ include use cases targeted for parsing GitLab log files.
 
 The examples listed below address their respective log files by
 their relative Linux package installation paths and default filenames.
-Find the respective full paths in the [GitLab logs sections](../logs/_index.md#production_jsonlog).
+Find the respective full paths in the [GitLab logs sections](_index.md#production_jsonlog).
 
 ### Compressed logs
 
diff --git a/doc/administration/monitoring/health_check.md b/doc/administration/monitoring/health_check.md
index 0dac5ce3582..39abfadd0b3 100644
--- a/doc/administration/monitoring/health_check.md
+++ b/doc/administration/monitoring/health_check.md
@@ -42,7 +42,7 @@ Apdex measurements are used to determine uptime.
 ## IP allowlist
 
 To access monitoring resources, the requesting client IP needs to be included in the allowlist.
-For details, see [how to add IPs to the allowlist for the monitoring endpoints](../monitoring/ip_allowlist.md).
+For details, see [how to add IPs to the allowlist for the monitoring endpoints](ip_allowlist.md).
 
 ## Using the endpoints locally
 
diff --git a/doc/administration/operations/_index.md b/doc/administration/operations/_index.md
index 6f874b613a1..3665a4be093 100644
--- a/doc/administration/operations/_index.md
+++ b/doc/administration/operations/_index.md
@@ -17,15 +17,15 @@ Keep your GitLab instance up and running.
 
 - [Housekeeping](../housekeeping.md)
 - [Activate GitLab EE with license](../license_file.md)
-- [Fast SSH key lookup](../operations/fast_ssh_key_lookup.md)
-- [File system benchmarking](../operations/filesystem_benchmarking.md)
-- [`gitlab-sshd`](../operations/gitlab_sshd.md)
-- [Rails console](../operations/rails_console.md)
-- [Use SSH certificates](../operations/ssh_certificates.md)
+- [Fast SSH key lookup](fast_ssh_key_lookup.md)
+- [File system benchmarking](filesystem_benchmarking.md)
+- [`gitlab-sshd`](gitlab_sshd.md)
+- [Rails console](rails_console.md)
+- [Use SSH certificates](ssh_certificates.md)
 - [Enable encrypted configuration](../encrypted_configuration.md)
 - [Rake tasks](../../raketasks/_index.md)
 - [Backup and restore](../backup_restore/_index.md)
 - [Inactive project deletion](../inactive_project_deletion.md)
-- [Move repositories](../operations/moving_repositories.md)
+- [Move repositories](moving_repositories.md)
 - [Read-only state](../read_only_gitlab.md)
 - [Restart GitLab](../restart_gitlab.md)
diff --git a/doc/administration/operations/moving_repositories.md b/doc/administration/operations/moving_repositories.md
index 30667b982a5..8a0428be231 100644
--- a/doc/administration/operations/moving_repositories.md
+++ b/doc/administration/operations/moving_repositories.md
@@ -88,7 +88,7 @@ To move all projects by using the API:
    "https://gitlab.example.com/api/v4/projects?repository_storage=<original_storage_name>"
    ```
 
-   Alternatively use [the rails console](../operations/rails_console.md) to confirm that all
+   Alternatively use [the rails console](rails_console.md) to confirm that all
    projects have moved. Run the following in the rails console:
 
    ```ruby
@@ -116,7 +116,7 @@ To move all snippets by using the API:
    - The moves are in progress. Re-query the repository move until it completes successfully.
    - The moves have failed. Most failures are temporary and are solved by rescheduling the move.
 
-1. After the moves are complete, use [the rails console](../operations/rails_console.md) to confirm
+1. After the moves are complete, use [the rails console](rails_console.md) to confirm
    that all snippets have moved. No snippets should be returned for the original storage. Run the
    following in the rails console:
 
@@ -153,7 +153,7 @@ To move all groups by using the API:
    - The moves are in progress. Re-query the repository move until it completes successfully.
    - The moves have failed. Most failures are temporary and are solved by rescheduling the move.
 
-1. After the moves are complete, use [the rails console](../operations/rails_console.md) to confirm
+1. After the moves are complete, use [the rails console](rails_console.md) to confirm
    that all groups have moved. No groups should be returned for the original storage. Run the
    following in the rails console:
 
diff --git a/doc/administration/operations/puma.md b/doc/administration/operations/puma.md
index 238ef7f558a..fe98d327723 100644
--- a/doc/administration/operations/puma.md
+++ b/doc/administration/operations/puma.md
@@ -387,7 +387,7 @@ gitlab_rails['env'] = {
 ```
 
 For self-compiled installations, set the environment variable.
-Refer to [Puma Worker timeout](../operations/puma.md#change-the-worker-timeout).
+Refer to [Puma Worker timeout](puma.md#change-the-worker-timeout).
 
 [Reconfigure](../restart_gitlab.md#reconfigure-a-linux-package-installation) GitLab for the changes to take effect.
 
@@ -401,7 +401,7 @@ separate Rails process to debug the issue:
 1. Sign in to your GitLab account.
 1. Copy the URL that is causing problems (for example, `https://gitlab.com/ABC`).
 1. Create a personal access token for your user (User Settings -> Access tokens).
-1. Bring up the [GitLab Rails console.](../operations/rails_console.md#starting-a-rails-console-session)
+1. Bring up the [GitLab Rails console.](rails_console.md#starting-a-rails-console-session)
 1. At the Rails console, run:
 
    ```ruby
diff --git a/doc/administration/packages/container_registry.md b/doc/administration/packages/container_registry.md
index c0ca766d696..2fc9344d6e6 100644
--- a/doc/administration/packages/container_registry.md
+++ b/doc/administration/packages/container_registry.md
@@ -76,12 +76,12 @@ The contents of `gitlab.yml` are:
 ```yaml
 registry:
   enabled: true
-  host: registry.gitlab.example.com
-  port: 5005
-  api_url: http://localhost:5000/
-  key: config/registry.key
-  path: shared/registry
-  issuer: gitlab-issuer
+  host: <registry.gitlab.example.com>
+  port: <5005>
+  api_url: <http://localhost:5000/>
+  key: <config/registry.key>
+  path: <shared/registry>
+  issuer: <gitlab-issuer>
 ```
 
 Where:
@@ -107,7 +107,7 @@ as the realm:
 ```yaml
 auth:
   token:
-    realm: https://gitlab.example.com/jwt/auth
+    realm: <https://gitlab.example.com/jwt/auth>
     service: container_registry
     issuer: gitlab-issuer
     rootcertbundle: /root/certs/certbundle
@@ -164,7 +164,7 @@ under the `registry_external_url` line, rather than the port listed under
    path to the existing TLS certificate and key used by GitLab:
 
    ```ruby
-   registry_external_url 'https://gitlab.example.com:5050'
+   registry_external_url '<https://gitlab.example.com:5050>'
    ```
 
    The `registry_external_url` is listening on HTTPS under the
@@ -175,8 +175,8 @@ under the `registry_external_url` line, rather than the port listed under
    below:
 
    ```ruby
-   registry_nginx['ssl_certificate'] = "/path/to/certificate.pem"
-   registry_nginx['ssl_certificate_key'] = "/path/to/certificate.key"
+   registry_nginx['ssl_certificate'] = "</path/to/certificate.pem>"
+   registry_nginx['ssl_certificate_key'] = "</path/to/certificate.key>"
    ```
 
 1. Save the file and [reconfigure GitLab](../restart_gitlab.md#reconfigure-a-linux-package-installation)
@@ -198,7 +198,7 @@ balancer to the registry from ports `80` or `443` to the arbitrary port. This is
 rely on the `docker login` example in the container registry. Here's an example:
 
 ```ruby
-registry_external_url 'https://registry-gitlab.example.com'
+registry_external_url '<https://registry-gitlab.example.com>'
 registry_nginx['redirect_http_to_https'] = true
 registry_nginx['listen_port'] = 5678
 ```
@@ -213,7 +213,7 @@ registry_nginx['listen_port'] = 5678
    ```yaml
    registry:
      enabled: true
-     host: gitlab.example.com
+     host: <gitlab.example.com>
      port: 5050
    ```
 
@@ -228,7 +228,7 @@ Users should now be able to sign in to the container registry with their GitLab
 credentials using:
 
 ```shell
-docker login gitlab.example.com:5050
+docker login <gitlab.example.com:5050>
 ```
 
 ### Configure container registry under its own domain
@@ -250,18 +250,18 @@ Let's assume that you want the container registry to be accessible at
 {{< tab title="Linux package (Omnibus)" >}}
 
 1. Place your TLS certificate and key in
-   `/etc/gitlab/ssl/registry.gitlab.example.com.crt` and
-   `/etc/gitlab/ssl/registry.gitlab.example.com.key` and make sure they have
+   `/etc/gitlab/ssl/<registry.gitlab.example.com>.crt` and
+   `/etc/gitlab/ssl/<registry.gitlab.example.com>.key` and make sure they have
    correct permissions:
 
    ```shell
-   chmod 600 /etc/gitlab/ssl/registry.gitlab.example.com.*
+   chmod 600 /etc/gitlab/ssl/<registry.gitlab.example.com>.*
    ```
 
 1. After the TLS certificate is in place, edit `/etc/gitlab/gitlab.rb` with:
 
    ```ruby
-   registry_external_url 'https://registry.gitlab.example.com'
+   registry_external_url '<https://registry.gitlab.example.com>'
    ```
 
    The `registry_external_url` is listening on HTTPS.
@@ -287,7 +287,7 @@ registry_nginx['ssl_certificate_key'] = "/etc/gitlab/ssl/certificate.key"
    ```yaml
    registry:
      enabled: true
-     host: registry.gitlab.example.com
+     host: <registry.gitlab.example.com>
    ```
 
 1. Save the file and [restart GitLab](../restart_gitlab.md#self-compiled-installations) for the changes to take effect.
@@ -301,7 +301,7 @@ Users should now be able to sign in to the container registry using their GitLab
 credentials:
 
 ```shell
-docker login registry.gitlab.example.com
+docker login <registry.gitlab.example.com>
 ```
 
 ## Disable container registry site-wide
@@ -455,7 +455,7 @@ The default location where images are stored in Linux package installations is
 1. Edit `/etc/gitlab/gitlab.rb`:
 
    ```ruby
-   gitlab_rails['registry_path'] = "/path/to/registry/storage"
+   gitlab_rails['registry_path'] = "</path/to/registry/storage>"
    ```
 
 1. Save the file and [reconfigure GitLab](../restart_gitlab.md#reconfigure-a-linux-package-installation) for the changes to take effect.
@@ -530,22 +530,22 @@ Report any issues or feedback using [issue 525855](https://gitlab.com/gitlab-org
 # Deprecated: Will be removed in GitLab 19.0
 registry['storage'] = {
   's3' => {
-    'accesskey' => 's3-access-key',
-    'secretkey' => 's3-secret-key-for-access-key',
-    'bucket' => 'your-s3-bucket',
-    'region' => 'your-s3-region',
-    'regionendpoint' => 'your-s3-regionendpoint'
+    'accesskey' => '<s3-access-key>',
+    'secretkey' => '<s3-secret-key-for-access-key>',
+    'bucket' => '<your-s3-bucket>',
+    'region' => '<your-s3-region>',
+    'regionendpoint' => '<your-s3-regionendpoint>'
   }
 }
 
 # Beta: s3_v2 driver
 registry['storage'] = {
   's3_v2' => {
-    'accesskey' => 's3-access-key',
-    'secretkey' => 's3-secret-key-for-access-key',
-    'bucket' => 'your-s3-bucket',
-    'region' => 'your-s3-region',
-    'regionendpoint' => 'your-s3-regionendpoint'
+    'accesskey' => '<s3-access-key>',
+    'secretkey' => '<s3-secret-key-for-access-key>',
+    'bucket' => '<your-s3-bucket>',
+    'region' => '<your-s3-region>',
+    'regionendpoint' => '<your-s3-regionendpoint>'
   }
 }
 ```
@@ -559,18 +559,18 @@ For S3 VPC endpoints:
 ```ruby
 registry['storage'] = {
   's3_v2' => {  # Beta driver
-    'accesskey' => 's3-access-key',
-    'secretkey' => 's3-secret-key-for-access-key',
-    'bucket' => 'your-s3-bucket',
-    'region' => 'your-s3-region',
-    'regionendpoint' => 'your-s3-vpc-endpoint',
+    'accesskey' => '<s3-access-key>',
+    'secretkey' => '<s3-secret-key-for-access-key>',
+    'bucket' => '<your-s3-bucket>',
+    'region' => '<your-s3-region>',
+    'regionendpoint' => '<your-s3-vpc-endpoint>',
     'pathstyle' => false
   }
 }
 ```
 
 - `regionendpoint` is only required when configuring an S3 compatible service such as MinIO, or when using an AWS S3 VPC Endpoint.
-- `your-s3-bucket` should be the name of a bucket that exists, and can't include subdirectories.
+- `<your-s3-bucket>` should be the name of a bucket that exists, and can't include subdirectories.
 - `pathstyle` should be set to `true` to use host/bucket_name/object style paths instead of bucket_name.host/object. Set to `false` for AWS S3.
 
 You can set a rate limit on connections to S3 to avoid 503 errors from the S3 API:
@@ -578,11 +578,11 @@ You can set a rate limit on connections to S3 to avoid 503 errors from the S3 AP
 ```ruby
 registry['storage'] = {
   's3' => {
-    'accesskey' => 's3-access-key',
-    'secretkey' => 's3-secret-key-for-access-key',
-    'bucket' => 'your-s3-bucket',
-    'region' => 'your-s3-region',
-    'regionendpoint' => 'your-s3-regionendpoint',
+    'accesskey' => '<s3-access-key>',
+    'secretkey' => '<s3-secret-key-for-access-key>',
+    'bucket' => '<your-s3-bucket>',
+    'region' => '<your-s3-region>',
+    'regionendpoint' => '<your-s3-regionendpoint>',
     'maxrequestspersecond' => 100
   }
 }
@@ -620,7 +620,7 @@ registry['storage'] = {
 # Beta: azure_v2 driver
 registry['storage'] = {
   'azure_v2' => {
-    'credentials_type' => 'client_secret',
+    'credentials_type' => '<client_secret>',
     'tenant_id' => '<your_tenant_id>',
     'client_id' => '<your_client_id>',
     'secret' => '<your_secret>',
@@ -641,8 +641,8 @@ The GCS storage driver integrates with Google Cloud Storage.
 ```ruby
 registry['storage'] = {
   'gcs' => {
-    'bucket' => 'BUCKET_NAME',
-    'keyfile' => 'PATH/TO/KEYFILE',
+    'bucket' => '<your_bucket_name>',
+    'keyfile' => '<path/to/keyfile>',
     # If you have the bucket shared with other apps beyond the registry, uncomment the following:
     # 'rootdirectory' => '/gcs/object/name/prefix'
   }
@@ -665,18 +665,18 @@ when you deployed your Docker registry.
 ```yaml
 storage:
   s3:
-    accesskey: 's3-access-key'                # Not needed if IAM role used
-    secretkey: 's3-secret-key-for-access-key' # Not needed if IAM role used
-    bucket: 'your-s3-bucket'
-    region: 'your-s3-region'
-    regionendpoint: 'your-s3-regionendpoint'
+    accesskey: '<s3-access-key>'                # Not needed if IAM role used
+    secretkey: '<s3-secret-key-for-access-key>' # Not needed if IAM role used
+    bucket: '<your-s3-bucket>'
+    region: '<your-s3-region>'
+    regionendpoint: '<your-s3-regionendpoint>'
   cache:
     blobdescriptor: inmemory
   delete:
     enabled: true
 ```
 
-`your-s3-bucket` should be the name of a bucket that exists, and can't include subdirectories.
+`<your-s3-bucket>` should be the name of a bucket that exists, and can't include subdirectories.
 
 #### Migrate to object storage without downtime
 
@@ -703,7 +703,7 @@ you can pull from the container registry, but you cannot push.
    all buckets.
 
    ```shell
-   sudo aws --endpoint-url https://your-object-storage-backend.com s3 ls
+   sudo aws --endpoint-url <https://your-object-storage-backend.com> s3 ls
    ```
 
    If you are using AWS as your back end, you do not need the [`--endpoint-url`](https://docs.aws.amazon.com/cli/latest/reference/#options).
@@ -713,7 +713,7 @@ you can pull from the container registry, but you cannot push.
    command. Make sure to keep the `docker` folder as the top-level folder inside the bucket.
 
    ```shell
-   sudo aws --endpoint-url https://your-object-storage-backend.com s3 sync registry s3://mybucket
+   sudo aws --endpoint-url <https://your-object-storage-backend.com> s3 sync registry s3://mybucket
    ```
 
    {{< alert type="note" >}}
@@ -729,7 +729,7 @@ you can pull from the container registry, but you cannot push.
 1. Sync any changes dating from after the initial data load to your S3 bucket, and delete files that exist in the destination bucket but not in the source:
 
    ```shell
-   sudo aws --endpoint-url https://your-object-storage-backend.com s3 sync registry s3://mybucket --delete --dryrun
+   sudo aws --endpoint-url <https://your-object-storage-backend.com> s3 sync registry s3://mybucket --delete --dryrun
    ```
 
    After verifying the command performs as expected, remove the
@@ -752,7 +752,7 @@ you can pull from the container registry, but you cannot push.
    ```
 
    ```shell
-   sudo aws --endpoint-url https://your-object-storage-backend.com s3 ls s3://mybucket --recursive | wc -l
+   sudo aws --endpoint-url <https://your-object-storage-backend.com> s3 ls s3://<mybucket> --recursive | wc -l
    ```
 
    The output of these commands should match, except for the content in the
@@ -978,7 +978,7 @@ use a JSON Web Token to authenticate with GitLab. The
 ```yaml
 auth:
   token:
-    realm: https://gitlab.example.com/jwt/auth
+    realm: https://<gitlab.example.com>/jwt/auth
     service: container_registry
     issuer: gitlab-issuer
     rootcertbundle: /root/certs/certbundle
@@ -1039,7 +1039,7 @@ You can use GitLab as an auth endpoint with an external container registry.
    Registry pages, set the following configurations:
 
    ```ruby
-   gitlab_rails['registry_host'] = "registry.gitlab.example.com"
+   gitlab_rails['registry_host'] = "<registry.gitlab.example.com>"
    gitlab_rails['registry_port'] = "5005"
    ```
 
@@ -1055,11 +1055,11 @@ You can use GitLab as an auth endpoint with an external container registry.
 
    registry:
      enabled: true
-     host: "registry.gitlab.example.com"
+     host: "<registry.gitlab.example.com>"
      port: "5005"
      api_url: "https://<external_registry_host>:5000"
      path: /var/lib/registry
-     key: /path/to/keyfile
+     key: </path/to/keyfile>
      issuer: gitlab-issuer
    ```
 
@@ -1095,24 +1095,24 @@ To configure a notification endpoint for a Linux package installation:
    ```ruby
    registry['notifications'] = [
      {
-       'name' => 'test_endpoint',
-       'url' => 'https://gitlab.example.com/api/v4/container_registry_event/events',
+       'name' => '<test_endpoint>',
+       'url' => 'https://<gitlab.example.com>/api/v4/container_registry_event/events',
        'timeout' => '500ms',
        'threshold' => 5, # DEPRECATED: use `maxretries` instead.
        'maxretries' => 5,
        'backoff' => '1s',
        'headers' => {
-         "Authorization" => ["AUTHORIZATION_EXAMPLE_TOKEN"]
+         "Authorization" => ["<AUTHORIZATION_EXAMPLE_TOKEN>"]
        }
      }
    ]
 
-   gitlab_rails['registry_notification_secret'] = 'AUTHORIZATION_EXAMPLE_TOKEN' # Must match the auth token in registry['notifications']
+   gitlab_rails['registry_notification_secret'] = '<AUTHORIZATION_EXAMPLE_TOKEN>' # Must match the auth token in registry['notifications']
    ```
 
   {{< alert type="note" >}}
 
-  Replace `AUTHORIZATION_EXAMPLE_TOKEN` with a case-sensitive alphanumeric string
+  Replace `<AUTHORIZATION_EXAMPLE_TOKEN>` with a case-sensitive alphanumeric string
   that starts with a letter. You can generate one with `< /dev/urandom tr -dc _A-Z-a-z-0-9 | head -c 32 | sed "s/^[0-9]*//"; echo`
 
   {{< /alert >}}
@@ -1131,9 +1131,9 @@ Example:
 ```yaml
 notifications:
   endpoints:
-    - name: alistener
+    - name: <alistener>
       disabled: false
-      url: https://my.listener.com/event
+      url: https://<my.listener.com>/event
       headers: <http.Header>
       timeout: 500
       threshold: 5 # DEPRECATED: use `maxretries` instead.
@@ -1309,23 +1309,23 @@ Prerequisites:
 Consider the following example, where you first build the image:
 
 ```shell
-# This builds a image with content of sha256:111111
-docker build -t my.registry.com/my.group/my.project:latest .
-docker push my.registry.com/my.group/my.project:latest
+# This builds a image with content of sha256:<111111...>
+docker build -t <my.registry.com>/<my.group>/<my.project>:latest .
+docker push <my.registry.com>/<my.group>/<my.project>:latest
 ```
 
-Now, you do overwrite `:latest` with a new version:
+Now, you do overwrite `latest` with a new version:
 
 ```shell
-# This builds a image with content of sha256:222222
-docker build -t my.registry.com/my.group/my.project:latest .
-docker push my.registry.com/my.group/my.project:latest
+# This builds a image with content of sha256:<222222...>
+docker build -t <my.registry.com>/<my.group>/<my.project>:latest .
+docker push <my.registry.com>/<my.group>/<my.project>:latest
 ```
 
-Now, the `:latest` tag points to manifest of `sha256:222222`.
+Now, the `latest` tag points to manifest of `sha256:<222222...>`.
 Due to the architecture of registry, this data is still accessible when pulling the
-image `my.registry.com/my.group/my.project@sha256:111111`, though it is
-no longer directly accessible via the `:latest` tag.
+image `<my.registry.com>/<my.group>/<my.project>@sha256:<111111...>`, though it is
+no longer directly accessible via the `latest` tag.
 
 ### Remove unreferenced layers
 
@@ -1592,8 +1592,8 @@ To configure GitLab and the container registry on separate nodes:
    # Configure registry settings
    registry['enable'] = true
    registry['registry_http_addr'] = '0.0.0.0:5000'
-   registry['token_realm'] = 'https://gitlab.example.com'
-   registry['http_secret'] = '6b86b273ff34fce19d6b804eff5a3f5747ada4eaa22f1d49c01e52ddb7875b4b'
+   registry['token_realm'] = 'https://<gitlab.example.com>'
+   registry['http_secret'] = '<6b86b273ff34fce19d6b804eff5a3f5747ada4eaa22f1d49c01e52ddb7875b4b>'
 
    # Configure GitLab Rails settings
    gitlab_rails['registry_issuer'] = 'omnibus-gitlab-issuer'
@@ -1608,12 +1608,12 @@ To configure GitLab and the container registry on separate nodes:
    # - Domain: gitlab.example.com
 
    # Configure GitLab URL
-   external_url 'https://gitlab.example.com'
+   external_url 'https://<gitlab.example.com>'
 
    # Configure registry settings
    gitlab_rails['registry_enabled'] = true
-   gitlab_rails['registry_api_url'] = 'http://10.30.227.194:5000'
-   gitlab_rails['registry_host'] = 'registry.example.com'
+   gitlab_rails['registry_api_url'] = '<http://10.30.227.194:5000>'
+   gitlab_rails['registry_host'] = '<registry.example.com>'
    gitlab_rails['registry_port'] = 5000
    gitlab_rails['registry_issuer'] = 'omnibus-gitlab-issuer'
    gitlab_rails['registry_key_path'] = '/etc/gitlab/gitlab-registry.key'
diff --git a/doc/administration/packages/container_registry_metadata_database.md b/doc/administration/packages/container_registry_metadata_database.md
index 4feb9dc570c..1d334aba583 100644
--- a/doc/administration/packages/container_registry_metadata_database.md
+++ b/doc/administration/packages/container_registry_metadata_database.md
@@ -21,7 +21,7 @@ title: Container registry metadata database
 
 The metadata database enables many new registry features, including
 online garbage collection, and increases the efficiency of many registry operations.
-The work on the self-managed release of the registry metadata database feature
+The work on the GitLab Self-Managed release of the registry metadata database feature
 is tracked in [epic 5521](https://gitlab.com/groups/gitlab-org/-/epics/5521).
 
 By default, the container registry uses object storage to persist metadata
diff --git a/doc/administration/postgresql/replication_and_failover.md b/doc/administration/postgresql/replication_and_failover.md
index be4ee1d0c40..469a13be036 100644
--- a/doc/administration/postgresql/replication_and_failover.md
+++ b/doc/administration/postgresql/replication_and_failover.md
@@ -458,7 +458,7 @@ authentication mode (`patroni['tls_client_mode']`), must each have the same valu
    gitlab-ctl write-pgpass --host 127.0.0.1 --database pgbouncer --user pgbouncer --hostuser gitlab-consul
    ```
 
-1. [Enable monitoring](../postgresql/pgbouncer.md#enable-monitoring)
+1. [Enable monitoring](pgbouncer.md#enable-monitoring)
 
 #### PgBouncer Checkpoint
 
@@ -560,7 +560,7 @@ gitlab-rake gitlab:db:configure
 
 > **Note**: If you encounter a `rake aborted!` error stating that PgBouncer is failing to connect to PostgreSQL it may be that your PgBouncer node's IP address is missing from
 PostgreSQL's `trust_auth_cidr_addresses` in `gitlab.rb` on your database nodes. See
-[PgBouncer error `ERROR:  pgbouncer cannot connect to server`](../postgresql/replication_and_failover_troubleshooting.md#pgbouncer-error-error-pgbouncer-cannot-connect-to-server) before you proceed.
+[PgBouncer error `ERROR:  pgbouncer cannot connect to server`](replication_and_failover_troubleshooting.md#pgbouncer-error-error-pgbouncer-cannot-connect-to-server) before you proceed.
 
 ### Backups
 
@@ -571,7 +571,7 @@ Do not backup or restore GitLab through a PgBouncer connection: this causes a Gi
 ### Ensure GitLab is running
 
 At this point, your GitLab instance should be up and running. Verify you're able
-to sign in, and create issues and merge requests. For more information, see [Troubleshooting replication and failover](../postgresql/replication_and_failover_troubleshooting.md).
+to sign in, and create issues and merge requests. For more information, see [Troubleshooting replication and failover](replication_and_failover_troubleshooting.md).
 
 ## Example configuration
 
@@ -899,7 +899,7 @@ Stopping or restarting the Patroni service on the leader node triggers an automa
 
 In GitLab 16.5 and earlier, PgBouncer nodes do not automatically fail over alongside
 Patroni nodes. PgBouncer services
-[must be restarted manually](../postgresql/replication_and_failover_troubleshooting.md#pgbouncer-error-error-pgbouncer-cannot-connect-to-server)
+[must be restarted manually](replication_and_failover_troubleshooting.md#pgbouncer-error-error-pgbouncer-cannot-connect-to-server)
 for a successful switchover.
 
 {{< /alert >}}
@@ -1053,7 +1053,7 @@ Considering these, you should carefully plan your PostgreSQL upgrade:
    ```
 
 If issues are encountered upgrading the replicas,
-[there is a troubleshooting section](../postgresql/replication_and_failover_troubleshooting.md#postgresql-major-version-upgrade-fails-on-a-patroni-replica) that might be the solution.
+[there is a troubleshooting section](replication_and_failover_troubleshooting.md#postgresql-major-version-upgrade-fails-on-a-patroni-replica) that might be the solution.
 
 {{< alert type="note" >}}
 
diff --git a/doc/administration/postgresql/replication_and_failover_troubleshooting.md b/doc/administration/postgresql/replication_and_failover_troubleshooting.md
index d9ba429e056..a7714c6e9de 100644
--- a/doc/administration/postgresql/replication_and_failover_troubleshooting.md
+++ b/doc/administration/postgresql/replication_and_failover_troubleshooting.md
@@ -56,7 +56,7 @@ postgresql['trust_auth_cidr_addresses'] = %w(123.123.123.123/32 <other_cidrs>)
 
 Due to a [known issue](https://gitlab.com/gitlab-org/omnibus-gitlab/-/issues/8166) that
 affects versions of GitLab prior to 16.5.0, the automatic failover of PgBouncer nodes does not
-happen after a [Patroni switchover](../postgresql/replication_and_failover.md#manual-failover-procedure-for-patroni). In this
+happen after a [Patroni switchover](replication_and_failover.md#manual-failover-procedure-for-patroni). In this
 example, GitLab failed to detect a paused database, then attempted to `RESUME` a
 not-paused database:
 
@@ -66,7 +66,7 @@ ERROR -- : STDERR: Error running command: GitlabCtl::Errors::ExecutionError
 ERROR -- : STDERR: ERROR: ERROR:  database gitlabhq_production is not paused
 ```
 
-To ensure a [Patroni switchover](../postgresql/replication_and_failover.md#manual-failover-procedure-for-patroni) succeeds,
+To ensure a [Patroni switchover](replication_and_failover.md#manual-failover-procedure-for-patroni) succeeds,
 you must manually restart the PgBouncer service on all PgBouncer nodes with this command:
 
 ```shell
@@ -77,7 +77,7 @@ gitlab-ctl restart pgbouncer
 
 If a replica cannot start or rejoin the cluster, or when it lags behind and cannot catch up, it might be necessary to reinitialize the replica:
 
-1. [Check the replication status](../postgresql/replication_and_failover.md#check-replication-status) to confirm which server
+1. [Check the replication status](replication_and_failover.md#check-replication-status) to confirm which server
    needs to be reinitialized. For example:
 
    ```plaintext
@@ -196,7 +196,7 @@ To fix the problem, ensure the loopback interface is included in the CIDR addres
    ```
 
 1. [Reconfigure GitLab](../restart_gitlab.md#reconfigure-a-linux-package-installation) for the changes to take effect.
-1. Check that [all the replicas are synchronized](../postgresql/replication_and_failover.md#check-replication-status)
+1. Check that [all the replicas are synchronized](replication_and_failover.md#check-replication-status)
 
 ## Error: requested start point is ahead of the Write Ahead Log (WAL) flush position
 
@@ -357,7 +357,7 @@ An example set of symptoms is as follows:
 
 **Important**: This workaround applies when the Patroni cluster is in the following state:
 
-- The [leader has been successfully upgraded to the new major version](../postgresql/replication_and_failover.md#upgrading-postgresql-major-version-in-a-patroni-cluster).
+- The [leader has been successfully upgraded to the new major version](replication_and_failover.md#upgrading-postgresql-major-version-in-a-patroni-cluster).
 - The step to upgrade PostgreSQL on replicas is failing.
 
 This workaround completes the PostgreSQL upgrade on a Patroni replica
diff --git a/doc/administration/raketasks/cleanup.md b/doc/administration/raketasks/cleanup.md
index ba8d7edf118..0706e61a1e9 100644
--- a/doc/administration/raketasks/cleanup.md
+++ b/doc/administration/raketasks/cleanup.md
@@ -148,7 +148,7 @@ I, [2018-07-27T12:08:33.755624 #89817]  INFO -- : Did fix /opt/gitlab/embedded/s
 I, [2018-07-27T12:08:33.760257 #89817]  INFO -- : Did move to lost and found /opt/gitlab/embedded/service/gitlab-rails/public/uploads/foo/bar/1dd6f0f7eefd2acc4c2233f89a0f7b0b/image.png -> /opt/gitlab/embedded/service/gitlab-rails/public/uploads/-/project-lost-found/foo/bar/1dd6f0f7eefd2acc4c2233f89a0f7b0b/image.png
 ```
 
-If using object storage, run the [All-in-one Rake task](../raketasks/uploads/migrate.md#all-in-one-rake-task) to ensure
+If using object storage, run the [All-in-one Rake task](uploads/migrate.md#all-in-one-rake-task) to ensure
 all uploads are migrated to object storage and there are no files on disk in the uploads folder.
 
 ### Clean up project upload files from object storage
diff --git a/doc/administration/settings/account_and_limit_settings.md b/doc/administration/settings/account_and_limit_settings.md
index 45c3235f710..42b9e1a113b 100644
--- a/doc/administration/settings/account_and_limit_settings.md
+++ b/doc/administration/settings/account_and_limit_settings.md
@@ -94,6 +94,10 @@ The default prefix is `glpat-` but administrators can change it.
 [Project access tokens](../../user/project/settings/project_access_tokens.md) and
 [group access tokens](../../user/group/settings/group_access_tokens.md) also inherit this prefix.
 
+By default, [secret push protection](../../user/application_security/secret_detection/secret_push_protection/_index.md) and
+[pipeline secret detection](../../user/application_security/secret_detection/pipeline/_index.md#detected-secrets) do not detect custom prefixes.
+Custom prefixes might cause an increase in false positives.
+
 ### Set a prefix
 
 To change the default global prefix:
diff --git a/doc/administration/settings/continuous_integration.md b/doc/administration/settings/continuous_integration.md
index fec7bd1d682..c13eded5a94 100644
--- a/doc/administration/settings/continuous_integration.md
+++ b/doc/administration/settings/continuous_integration.md
@@ -179,7 +179,7 @@ You can set the maximum size of distinct [job artifacts](../cicd/job_artifacts.m
 - Groups
 
 The default maximum size for each artifact file in a job is 100 MB.
-For GitLab.com, see [Artifacts maximum size](../../user/gitlab_com/_index.md#gitlab-cicd).
+For GitLab.com, see [Artifacts maximum size](../../user/gitlab_com/_index.md#cicd).
 
 Job artifacts defined with `artifacts:reports` can have [different limits](../../administration/instance_limits.md#maximum-file-size-per-type-of-artifact).
 In this case, the smaller value is used.
@@ -296,7 +296,7 @@ After that time passes, the jobs are archived in the background and no longer ab
 retried. Make it empty to never expire jobs. It has to be no less than 1 day,
 for example: <code>15 days</code>, <code>1 month</code>, <code>2 years</code>.
 
-For the value set for GitLab.com, see [Scheduled job archiving](../../user/gitlab_com/_index.md#gitlab-cicd).
+For the value set for GitLab.com, see [Scheduled job archiving](../../user/gitlab_com/_index.md#cicd).
 
 ## Protect CI/CD variables by default
 
diff --git a/doc/administration/settings/deprecated_api_rate_limits.md b/doc/administration/settings/deprecated_api_rate_limits.md
index 6ec888bc203..993674eec65 100644
--- a/doc/administration/settings/deprecated_api_rate_limits.md
+++ b/doc/administration/settings/deprecated_api_rate_limits.md
@@ -54,4 +54,4 @@ To override the general user and IP rate limits for requests to deprecated API e
 ## Related topics
 
 - [Rate limits](../../security/rate_limits.md)
-- [User and IP rate limits](../settings/user_and_ip_rate_limits.md)
+- [User and IP rate limits](user_and_ip_rate_limits.md)
diff --git a/doc/administration/settings/git_http_rate_limits.md b/doc/administration/settings/git_http_rate_limits.md
index 2220880c16f..c6f7445cb53 100644
--- a/doc/administration/settings/git_http_rate_limits.md
+++ b/doc/administration/settings/git_http_rate_limits.md
@@ -24,7 +24,7 @@ common Git operations can generate many Git HTTP requests.
 Some of these Git HTTP requests do not contain authentication parameter and
 are considered unauthenticated. You can enforce rate limits on Git HTTP requests.
 This can improve the security and durability of your web application.
-[General user and IP rate limits](../settings/user_and_ip_rate_limits.md) aren't applied
+[General user and IP rate limits](user_and_ip_rate_limits.md) aren't applied
 to Git HTTP requests.
 
 ## Configure Git HTTP rate limits
@@ -45,4 +45,4 @@ To configure Git HTTP rate limits:
 ## Related topics
 
 - [Rate limiting](../../security/rate_limits.md)
-- [User and IP rate limits](../settings/user_and_ip_rate_limits.md)
+- [User and IP rate limits](user_and_ip_rate_limits.md)
diff --git a/doc/administration/settings/git_lfs_rate_limits.md b/doc/administration/settings/git_lfs_rate_limits.md
index 11593a10397..5b43c932c8b 100644
--- a/doc/administration/settings/git_lfs_rate_limits.md
+++ b/doc/administration/settings/git_lfs_rate_limits.md
@@ -16,14 +16,14 @@ title: Rate limits on Git LFS
 [Git LFS (Large File Storage)](../../topics/git/lfs/_index.md) is a Git extension
 for handling large files. If you use Git LFS in your repository, common Git operations
 can generate many Git LFS requests. You can enforce
-[general user and IP rate limits](../settings/user_and_ip_rate_limits.md), but you can also
+[general user and IP rate limits](user_and_ip_rate_limits.md), but you can also
 override the general setting to enforce additional limits on Git LFS requests. This
 override can improve the security and durability of your web application.
 
 ## On GitLab.com
 
 On GitLab.com, Git LFS requests are subject to
-[authenticated web request rate limits](../../user/gitlab_com/_index.md#gitlabcom-specific-rate-limits).
+[authenticated web request rate limits](../../user/gitlab_com/_index.md#rate-limits-on-gitlabcom).
 These limits are set to 1000 requests per minute per user.
 
 Each Git LFS object uploaded or downloaded generates an HTTP request that counts toward
diff --git a/doc/administration/settings/import_and_export_settings.md b/doc/administration/settings/import_and_export_settings.md
index ceea800f7bc..70902d1134d 100644
--- a/doc/administration/settings/import_and_export_settings.md
+++ b/doc/administration/settings/import_and_export_settings.md
@@ -146,7 +146,7 @@ This setting applies only to repositories
 [imported from a GitLab export file](../../user/project/settings/import_export.md#import-a-project-and-its-data).
 
 If you choose a size larger than the configured value for the web server,
-you may receive errors. See the [troubleshooting section](../settings/account_and_limit_settings.md#troubleshooting) for more
+you may receive errors. See the [troubleshooting section](account_and_limit_settings.md#troubleshooting) for more
 details.
 
 For GitLab.com repository size limits, read [accounts and limit settings](../../user/gitlab_com/_index.md#account-and-limit-settings).
diff --git a/doc/administration/settings/package_registry_rate_limits.md b/doc/administration/settings/package_registry_rate_limits.md
index b056a904e26..00bccaf67ce 100644
--- a/doc/administration/settings/package_registry_rate_limits.md
+++ b/doc/administration/settings/package_registry_rate_limits.md
@@ -18,7 +18,7 @@ publish and share packages, which others can consume as a dependency in downstre
 the [Packages API](../../api/packages.md).
 
 If downstream projects frequently download such dependencies, many requests are made through the
-Packages API. You may therefore reach enforced [user and IP rate limits](../settings/user_and_ip_rate_limits.md).
+Packages API. You may therefore reach enforced [user and IP rate limits](user_and_ip_rate_limits.md).
 To address this issue, you can define specific rate limits for the Packages API:
 
 - [Unauthenticated requests (per IP)](#enable-unauthenticated-request-rate-limit-for-packages-api).
diff --git a/doc/administration/settings/usage_statistics.md b/doc/administration/settings/usage_statistics.md
index ce82b90cbad..b905a49bf82 100644
--- a/doc/administration/settings/usage_statistics.md
+++ b/doc/administration/settings/usage_statistics.md
@@ -56,16 +56,16 @@ In the following table, you can see:
 | Feature | Available in |
 | ------ | ------ |
 | [Email from GitLab](../email_from_gitlab.md)       |   GitLab 14.1 and later     |
-| [Repository size limit](../settings/account_and_limit_settings.md#repository-size-limit) | GitLab 14.4 and later |
+| [Repository size limit](account_and_limit_settings.md#repository-size-limit) | GitLab 14.4 and later |
 | [Group access restriction by IP address](../../user/group/access_and_permissions.md#restrict-group-access-by-ip-address) | GitLab 14.4 and later |
 | [View description change history](../../user/discussions/_index.md#view-description-change-history) | GitLab 16.0 and later |
 | [Maintenance mode](../maintenance_mode/_index.md) | GitLab 16.0 and later |
 | [Configurable issue boards](../../user/project/issue_board.md#configurable-issue-boards) | GitLab 16.0 and later |
 | [Coverage-guided fuzz testing](../../user/application_security/coverage_fuzzing/_index.md) | GitLab 16.0 and later |
-| [Password complexity requirements](../settings/sign_up_restrictions.md#password-complexity-requirements) | GitLab 16.0 and later |
+| [Password complexity requirements](sign_up_restrictions.md#password-complexity-requirements) | GitLab 16.0 and later |
 | [Group wikis](../../user/project/wiki/group.md) | GitLab 16.5 and later |
 | [Issue analytics](../../user/group/issues_analytics/_index.md) | GitLab 16.5 and later |
-| [Custom Text in Emails](../settings/email.md#custom-additional-text) | GitLab 16.5 and later |
+| [Custom Text in Emails](email.md#custom-additional-text) | GitLab 16.5 and later |
 | [Contribution analytics](../../user/group/contribution_analytics/_index.md) | GitLab 16.5 and later |
 | [Group file templates](../../user/group/manage.md#group-file-templates) | GitLab 16.6 and later |
 | [Group webhooks](../../user/project/integrations/webhooks.md#group-webhooks) | GitLab 16.6 and later |
@@ -101,7 +101,7 @@ for all authenticated users, and on the **Admin** area pages. The statuses are:
 - Red: The version of GitLab you are running is vulnerable. You should install
   the latest version with security fixes as soon as possible.
 
-![Version check showing that a non-critical update is available for the GitLab instance](../settings/img/non_critical_update_available_v10_6.png)
+![Version check showing that a non-critical update is available for the GitLab instance](img/non_critical_update_available_v10_6.png)
 
 ### Enable or disable version check
 
diff --git a/doc/api/graphql/_index.md b/doc/api/graphql/_index.md
index c251d236560..6248b628916 100644
--- a/doc/api/graphql/_index.md
+++ b/doc/api/graphql/_index.md
@@ -291,7 +291,7 @@ The following limits apply to the GitLab GraphQL API.
 | Maximum page size                                     | 100 records (nodes) per page. Applies to most connections in the API. Particular connections may have different max page size limits that are higher or lower. |
 | [Maximum query complexity](#maximum-query-complexity) | 200 for unauthenticated requests and 250 for authenticated requests. |
 | Maximum query size                                    | 10,000 characters per query or mutation. If this limit is reached, use [variables](https://graphql.org/learn/queries/#variables) and [fragments](https://graphql.org/learn/queries/#fragments) to reduce the query or mutation size. Remove white spaces as last resort. |
-| Rate limits | For GitLab.com, see [GitLab.com-specific rate limits](../../user/gitlab_com/_index.md#gitlabcom-specific-rate-limits). |
+| Rate limits | For GitLab.com, see [GitLab.com-specific rate limits](../../user/gitlab_com/_index.md#rate-limits-on-gitlabcom). |
 | Request timeout                                       | 30 seconds. |
 
 ### Maximum query complexity
diff --git a/doc/api/graphql/reference/_index.md b/doc/api/graphql/reference/_index.md
index f9d5ab1b6a2..1231b98fc5f 100644
--- a/doc/api/graphql/reference/_index.md
+++ b/doc/api/graphql/reference/_index.md
@@ -20816,6 +20816,15 @@ Stores Amazon S3 configurations for audit event streaming.
 | <a id="amazons3configurationtypeid"></a>`id` | [`ID!`](#id) | ID of the configuration. |
 | <a id="amazons3configurationtypename"></a>`name` | [`String!`](#string) | Name of the external destination to send audit events to. |
 
+### `AncestorType`
+
+#### Fields
+
+| Name | Type | Description |
+| ---- | ---- | ----------- |
+| <a id="ancestortypename"></a>`name` | [`String`](#string) | Name of the ancestor. |
+| <a id="ancestortypeversion"></a>`version` | [`String`](#string) | Version of the ancestor. |
+
 ### `ApiFuzzingCiConfiguration`
 
 Data associated with configuring API fuzzing scans in GitLab CI.
@@ -29796,6 +29805,7 @@ Represents an entry from the Cloud License history.
 
 | Name | Type | Description |
 | ---- | ---- | ----------- |
+| <a id="locationancestors"></a>`ancestors` | [`[AncestorType!]`](#ancestortype) | Ancestors of the dependency. |
 | <a id="locationblobpath"></a>`blobPath` | [`String`](#string) | HTTP URI path to view the input file in GitLab. |
 | <a id="locationpath"></a>`path` | [`String`](#string) | Path, relative to the root of the repository, of the filewhich was analyzed to detect the dependency. |
 | <a id="locationtoplevel"></a>`topLevel` | [`Boolean`](#boolean) | Is top level dependency. |
diff --git a/doc/api/groups.md b/doc/api/groups.md
index cfb56fe4dde..1549889e132 100644
--- a/doc/api/groups.md
+++ b/doc/api/groups.md
@@ -375,7 +375,7 @@ When the parameter `statistics=true` is used and the authenticated user is an ad
 
 - `container_registry_size_is_estimated`: Indicates whether the size is an exact calculation based on actual data from all repositories (`false`) or estimated due to performance constraints (`true`).
 
-For self-managed instances, the [container registry metadata database](../administration/packages/container_registry_metadata_database.md) must be enabled to include the container registry size attributes.
+For GitLab Self-Managed instances, the [container registry metadata database](../administration/packages/container_registry_metadata_database.md) must be enabled to include the container registry size attributes.
 
 ```json
 [
diff --git a/doc/api/project_access_tokens.md b/doc/api/project_access_tokens.md
index 411a51e014f..f8acba9c9fc 100644
--- a/doc/api/project_access_tokens.md
+++ b/doc/api/project_access_tokens.md
@@ -129,7 +129,9 @@ curl --request GET \
 
 {{< /history >}}
 
-Creates a project access token for a specified project. You cannot create a token with an access level greater than your account. For example, a user with the Maintainer role cannot create a project access token with the Owner role.
+Creates a project access token for a specified project. You cannot create a token with an access level greater than your account. For example, a user with the Maintainer role cannot create a project access token with the Owner role. 
+
+You must use a personal access token with this endpoint. You cannot authenticate with a project access token. There is an [open feature request](https://gitlab.com/gitlab-org/gitlab/-/issues/359953) to add this functionality.
 
 ```plaintext
 POST projects/:id/access_tokens
@@ -146,7 +148,7 @@ POST projects/:id/access_tokens
 
 ```shell
 curl --request POST \
-  --header "PRIVATE-TOKEN: <your_access_token>" \
+  --header "PRIVATE-TOKEN: <your_personal_access_token>" \
   --header "Content-Type:application/json" \
   --data '{ "name":"test_token", "scopes":["api", "read_repository"], "expires_at":"2021-01-31", "access_level":30 }' \
   --url "https://gitlab.example.com/api/v4/projects/<project_id>/access_tokens"
diff --git a/doc/api/projects.md b/doc/api/projects.md
index cbc333a60e9..290b5af9e6b 100644
--- a/doc/api/projects.md
+++ b/doc/api/projects.md
@@ -78,7 +78,7 @@ Supported attributes:
 
 The responses include attributes related to container registry storage size:
 
-- `container_registry_size`: Total storage size in bytes used by all container repositories in the project. Updated whenever container images are pushed or deleted. For self-managed instances, requires the [container registry metadata database](../administration/packages/container_registry_metadata_database.md) to be enabled.
+- `container_registry_size`: Total storage size in bytes used by all container repositories in the project. Updated whenever container images are pushed or deleted. For GitLab Self-Managed instances, requires the [container registry metadata database](../administration/packages/container_registry_metadata_database.md) to be enabled.
 
 Example response:
 
diff --git a/doc/api/rest/_index.md b/doc/api/rest/_index.md
index 407eeef0722..93d175f496a 100644
--- a/doc/api/rest/_index.md
+++ b/doc/api/rest/_index.md
@@ -55,7 +55,7 @@ instance being overloaded.
 - For details, see [Rate limits](../../security/rate_limits.md).
 - For details of the rate limit settings used by
 GitLab.com, see
-  [GitLab.com-specific rate limits](../../user/gitlab_com/_index.md#gitlabcom-specific-rate-limits).
+  [GitLab.com-specific rate limits](../../user/gitlab_com/_index.md#rate-limits-on-gitlabcom).
 
 ## Response format
 
diff --git a/doc/ci/testing/unit_test_reports.md b/doc/ci/testing/unit_test_reports.md
index 19bbd48ed37..1b867428b82 100644
--- a/doc/ci/testing/unit_test_reports.md
+++ b/doc/ci/testing/unit_test_reports.md
@@ -151,7 +151,7 @@ If parsing JUnit report XML results in an error, an indicator is shown next to t
 
 ![Test Reports With Errors](img/pipelines_junit_test_report_with_errors_v13_10.png)
 
-For test case parsing limits, see [Max test cases per unit test report](../../user/gitlab_com/_index.md#gitlab-cicd).
+For test case parsing limits, see [Max test cases per unit test report](../../user/gitlab_com/_index.md#cicd).
 
 GitLab does not parse very [large nodes](https://nokogiri.org/tutorials/parsing_an_html_xml_document.html#parse-options) of JUnit reports. There is [an issue](https://gitlab.com/gitlab-org/gitlab/-/issues/268035) open to make this optional.
 
diff --git a/doc/ci/yaml/_index.md b/doc/ci/yaml/_index.md
index beb7c0f90ff..e52a5b96137 100644
--- a/doc/ci/yaml/_index.md
+++ b/doc/ci/yaml/_index.md
@@ -1319,7 +1319,7 @@ attached to the job when it [succeeds, fails, or always](#artifactswhen).
 
 The artifacts are sent to GitLab after the job finishes. They are
 available for download in the GitLab UI if the size is smaller than the
-[maximum artifact size](../../user/gitlab_com/_index.md#gitlab-cicd).
+[maximum artifact size](../../user/gitlab_com/_index.md#cicd).
 
 By default, jobs in later stages automatically download all the artifacts created
 by jobs in earlier stages. You can control artifact download behavior in jobs with
diff --git a/doc/ci/yaml/artifacts_reports.md b/doc/ci/yaml/artifacts_reports.md
index e0a014b6400..d9d7728b263 100644
--- a/doc/ci/yaml/artifacts_reports.md
+++ b/doc/ci/yaml/artifacts_reports.md
@@ -24,7 +24,7 @@ Use [`artifacts:reports`](_index.md#artifactsreports) to:
 Artifacts created for `artifacts: reports` are always uploaded, regardless of the job results (success or failure).
 You can use [`artifacts:expire_in`](_index.md#artifactsexpire_in) to set an expiration
 time for the artifacts, which overrides the instance's [default setting](../../administration/settings/continuous_integration.md#maximum-artifacts-size).
-GitLab.com might have a [different default artifacts expiry value](../../user/gitlab_com/_index.md#gitlab-cicd).
+GitLab.com might have a [different default artifacts expiry value](../../user/gitlab_com/_index.md#cicd).
 
 Some `artifacts:reports` types can be generated by multiple jobs in the same pipeline, and used by merge request or
 pipeline features from each job.
@@ -308,7 +308,7 @@ The exceptions to the [original dotenv rules](https://github.com/motdotla/dotenv
 - The variable key can contain only letters, digits, and underscores (`_`).
 - The maximum size of the `.env` file is 5 KB.
   This limit [can be changed on GitLab Self-Managed](../../administration/instance_limits.md#limit-dotenv-file-size).
-- On GitLab.com, [the maximum number of inherited variables](../../user/gitlab_com/_index.md#gitlab-cicd)
+- On GitLab.com, [the maximum number of inherited variables](../../user/gitlab_com/_index.md#cicd)
   is 50 for Free, 100 for Premium and 150 for Ultimate. The default for
   GitLab Self-Managed is 20, and can be changed by changing the
   `dotenv_variables` [application limit](../../administration/instance_limits.md#limit-dotenv-variables).
diff --git a/doc/development/ai_features/ai_development_license.md b/doc/development/ai_features/ai_development_license.md
index a66d92e9021..83f688cd72f 100644
--- a/doc/development/ai_features/ai_development_license.md
+++ b/doc/development/ai_features/ai_development_license.md
@@ -8,7 +8,14 @@ title: GitLab Duo licensing for local development
 
 This document explains the different licensing options available for GitLab Duo features in local development environments.
 
-> **Note:** When developing GitLab Duo features, it's important to test in both multi-tenant (GitLab.com) and single-tenant (Self-managed/Dedicated) environments where appropriate. There is no default or recommended approach - the setup you choose should be based on your specific testing requirements.
+{{< alert type="note" >}}
+
+When developing GitLab Duo features, it's important to test in both multi-tenant
+(GitLab.com) and single-tenant (GitLab Self-Managed/Dedicated) environments where
+appropriate. There is no default or recommended approach - the setup you choose
+should be based on your specific testing requirements.
+
+{{< /alert >}}
 
 ## Overview
 
@@ -27,7 +34,7 @@ You should choose a license setup based on your development needs. Each approach
 | Development Scenario | License Setup | Instructions |
 |----------------------|---------------------------|-------------|
 | Multi-tenant setup (GitLab.com) | Local license with Rake task | [Option A](#option-a-local-license-with-rake-task-multi-tenantgitlabcom-mode) |
-| Single-tenant setup (Self-managed/Dedicated) | Local license with Rake task in self-managed mode | [Option B](#option-b-local-license-with-rake-task-in-self-managed-mode-single-tenant-setup) |
+| Single-tenant setup (GitLab Self-Managed/Dedicated) | Local license with Rake task in self-managed mode | [Option B](#option-b-local-license-with-rake-task-in-self-managed-mode-single-tenant-setup) |
 | Full dog-fooding experience | Cloud license via CustomersDot | [Option C](#option-c-cloud-license-via-customersdot) |
 
 ## Prerequisites for all options
@@ -115,7 +122,7 @@ This approach configures your environment to behave like a self-managed or Dedic
 
 ### When to use
 
-- When you need to test in a single-tenant environment (similar to Self-managed or Dedicated)
+- When you need to test in a single-tenant environment (similar to GitLab Self-Managed or Dedicated)
 - When developing features that are specific to or need validation in self-managed or Dedicated environments
 - When testing integration points that behave differently in single-tenant mode
 
@@ -275,7 +282,7 @@ If you're having issues with your Duo license setup:
 
 ## Additional resources
 
-- [AI Features Documentation](../ai_features/_index.md)
-- [Code Suggestions Development](../ai_features/code_suggestions.md)
-- [License Management Guidelines for Code Suggestions](../ai_features/code_suggestions.md#setup-instructions-to-use-gdk-with-the-code-suggestions-add-on)
+- [AI Features Documentation](_index.md)
+- [Code Suggestions Development](code_suggestions.md)
+- [License Management Guidelines for Code Suggestions](code_suggestions.md#setup-instructions-to-use-gdk-with-the-code-suggestions-add-on)
 - [Duo Enterprise License Access Process for Staging Environment](https://gitlab.com/gitlab-com/runbooks/-/blob/master/docs/duo/duo_license.md?ref_type=heads)
diff --git a/doc/development/ai_features/code_suggestions.md b/doc/development/ai_features/code_suggestions.md
index 0cc27bf3e0f..7bf75153d5e 100644
--- a/doc/development/ai_features/code_suggestions.md
+++ b/doc/development/ai_features/code_suggestions.md
@@ -35,7 +35,7 @@ This should enable everyone to locally see how any change made in an IDE is sent
       1. In your terminal, go to your `gitlab-development-kit` > `gitlab` directory.
       1. Run `gdk rails console` or `bundle exec rails c` to start a Rails console.
       1. [Enable the Feature Flag](../../administration/feature_flags.md#enable-or-disable-the-feature) for the Code Suggestions tokens API by calling `Feature.enable(:ai_duo_code_suggestions_switch)` from the console.
-   1. [Setup AI gateway](../ai_features/_index.md#required-install-ai-gateway).
+   1. [Setup AI gateway](_index.md#required-install-ai-gateway).
    1. Run your GDK server with `gdk start` if it's not already running.
 
 ### Setup instructions to use staging AI gateway
@@ -67,7 +67,7 @@ with the deployed staging AI gateway. To do this:
 **Option 1 - Recommended**
 
 1. Ensure that you have a [GitLab Team Member License](https://handbook.gitlab.com/handbook/engineering/developer-onboarding/#working-on-gitlab-ee-developer-licenses) and that it is [activated](../../administration/license_file.md).
-1. Follow the [Setup and Run GDK](../ai_features/_index.md#set-up-and-run-gdk) guide under the AI Features doc.
+1. Follow the [Setup and Run GDK](_index.md#set-up-and-run-gdk) guide under the AI Features doc.
 
 **Option 2**
 
diff --git a/doc/development/ai_features/duo_chat.md b/doc/development/ai_features/duo_chat.md
index 63249be0c92..66ca4cc3930 100644
--- a/doc/development/ai_features/duo_chat.md
+++ b/doc/development/ai_features/duo_chat.md
@@ -299,7 +299,7 @@ We strongly recommend running the regression evaluator in at least the following
 
 | Environment                                                                 | Evaluation pipeline name                                  |
 | -----------                                                                 | ------------------------                                  |
-| Self-managed GitLab and a custom model that is widely adopted               | `duo-chat regression sm: [bedrock_mistral_8x7b_instruct]` |
+| GitLab Self-Managed and a custom model that is widely adopted               | `duo-chat regression sm: [bedrock_mistral_8x7b_instruct]` |
 | GitLab.com and GitLab Duo Enterprise add-on                                 | `duo-chat regression .com: [duo_enterprise]`              |
 | GitLab.com and GitLab Duo Pro add-on                                        | `duo-chat regression .com: [duo_pro]`                     |
 
@@ -477,7 +477,7 @@ The analysis can contain any of the attributes defined in the latest [iglu schem
 This table describes the requirements for the `access_duo_chat` policy to
 return `true` in different contexts.
 
-| | GitLab.com | Dedicated or Self-managed | All instances |
+| | GitLab.com | Dedicated or GitLab Self-Managed | All instances |
 |----------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------|
 | for user outside of project or group (`user.can?(:access_duo_chat)`)  | User need to belong to at least one group on Premium or Ultimate tier with `duo_features_enabled` group setting switched on | - Instance needs to be on Premium or Ultimate tier<br>- Instance needs to have `duo_features_enabled` setting switched on |  |
 | for user in group context (`user.can?(:access_duo_chat, group)`)     | - User needs to belong to at least one group on Premium or Ultimate tier with `experiment_and_beta_features` group setting switched on<br>- Root ancestor group of the group needs to be on Premium or Ultimate tier and the group must have `duo_features_enabled` setting switched on | - Instance needs to be on Premium or Ultimate tier<br>- Instance needs to have `duo_features_enabled` setting switched on | User must have at least _read_ permissions on the group |
diff --git a/doc/development/ai_features/embeddings.md b/doc/development/ai_features/embeddings.md
index 8e69dece68a..fd383bdb82e 100644
--- a/doc/development/ai_features/embeddings.md
+++ b/doc/development/ai_features/embeddings.md
@@ -87,7 +87,7 @@ The following process outlines the steps to get embeddings generated and stored
    Elastic::MigrationWorker.new.perform
    ```
 
-1. Make sure you can run [GitLab Duo features on your local environment](../ai_features/_index.md#instructions-for-setting-up-gitlab-duo-features-in-the-local-development-environment).
+1. Make sure you can run [GitLab Duo features on your local environment](_index.md#instructions-for-setting-up-gitlab-duo-features-in-the-local-development-environment).
 1. Ensure running the following in a rails console outputs an embedding (a vector of 768 dimensions). If not, there is a problem with the AI setup.
 
    ```ruby
diff --git a/doc/development/ai_features/model_migration.md b/doc/development/ai_features/model_migration.md
index 16051d7008b..f4aaa626c81 100644
--- a/doc/development/ai_features/model_migration.md
+++ b/doc/development/ai_features/model_migration.md
@@ -401,7 +401,7 @@ The AI Framework team should create a main migration issue following this templa
 
 ## Technical Details
 - [Any technical specifics about this migration]
-- [Impact on GitLab.com and self-managed instances]
+- [Impact on GitLab.com and GitLab Self-Managed instances]
 
 ## Implementation Steps
 - [ ] Update model configurations in each feature
diff --git a/doc/development/api_styleguide.md b/doc/development/api_styleguide.md
index 626fe94f416..3f1074d0049 100644
--- a/doc/development/api_styleguide.md
+++ b/doc/development/api_styleguide.md
@@ -116,7 +116,7 @@ The endpoints continue to respond with the same fields and accept the same
 arguments, although the underlying feature interaction is no longer operational.
 
 The intended changes must be documented ahead of time
-[following the v4 deprecation guide](../development/documentation/restful_api_styleguide.md#deprecations).
+[following the v4 deprecation guide](documentation/restful_api_styleguide.md#deprecations).
 
 For example, when we removed an application setting, we
 [kept the old API field](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/83984)
diff --git a/doc/development/application_limits.md b/doc/development/application_limits.md
index aaf3233d363..506a9f1de0a 100644
--- a/doc/development/application_limits.md
+++ b/doc/development/application_limits.md
@@ -151,7 +151,7 @@ end
 
 ### Subscription Plans
 
-Self-managed:
+GitLab Self-Managed:
 
 - `default`: Everyone.
 
@@ -187,7 +187,7 @@ The process for adding a new throttle is loosely:
    and apply it to the desired requests.
 1. Add the new settings to the **Admin** area form in `app/views/admin/application_settings/_ip_limits.html.haml`.
 1. Document the new settings in [User and IP rate limits](../administration/settings/user_and_ip_rate_limits.md) and [Application settings API](../api/settings.md).
-1. Configure the rate limit for GitLab.com and document it in [GitLab.com-specific rate limits](../user/gitlab_com/_index.md#gitlabcom-specific-rate-limits).
+1. Configure the rate limit for GitLab.com and document it in [rate limits on GitLab.com](../user/gitlab_com/_index.md#rate-limits-on-gitlabcom).
 
 Refer to these past issues for implementation details:
 
diff --git a/doc/development/code_review.md b/doc/development/code_review.md
index 10f6d9ec25a..8421237566a 100644
--- a/doc/development/code_review.md
+++ b/doc/development/code_review.md
@@ -119,11 +119,10 @@ It picks reviewers and maintainers from the list at the
 page, with these behaviors:
 
 - It doesn't pick people whose Slack or [GitLab status](../user/profile/_index.md#set-your-status):
-  - Contains the string `OOO`, `PTO`, `Parental Leave`, `Friends and Family`, `Conference` or `BUSY`.
+  - Contains the string `OOO`, `PTO`, `Parental Leave`, `Friends and Family`, or `Conference`.
   - Emoji is from one of these categories:
     - **On leave** - 🌴 `palm_tree`, 🏖️ `beach`, ⛱ `beach_umbrella`, 🏖 `beach_with_umbrella`, 🌞 `sun_with_face`, 🎡 `ferris_wheel`, 🏙 `cityscape`
     - **Out sick** - 🌡️ `thermometer`, 🤒 `face_with_thermometer`
-    - **BUSY** -  🔴 `red_circle`
   - Important: The status emojis are not detected when present on the free text input **status message**. They have to be set on your GitLab **status emoji** by clicking on the emoji selector beside the text input.
 - It doesn't pick people who are already assigned a number of reviews that is equal to
   or greater than their chosen "review limit". The review limit is the maximum number of
diff --git a/doc/development/data_retention_policies.md b/doc/development/data_retention_policies.md
index 7dd4c683cab..5f37d4fd188 100644
--- a/doc/development/data_retention_policies.md
+++ b/doc/development/data_retention_policies.md
@@ -66,4 +66,4 @@ Before submitting a merge request for a new feature:
 
 ## Related links
 
-- [Large tables limitations](../development/database/large_tables_limitations.md)
+- [Large tables limitations](database/large_tables_limitations.md)
diff --git a/doc/development/documentation/authoring_environment.md b/doc/development/documentation/authoring_environment.md
index 1d7cb1d05cb..3982a526338 100644
--- a/doc/development/documentation/authoring_environment.md
+++ b/doc/development/documentation/authoring_environment.md
@@ -13,9 +13,9 @@ Use this guidance to help ensure you have the tools you need.
 - Install a code editor, like VS Code or Sublime Text, to work with Markdown files.
 - [Install Git](../../topics/git/how_to_install_git/_index.md) and
   [add an SSH key to your GitLab profile](../../user/ssh.md#add-an-ssh-key-to-your-gitlab-account).
-- Install documentation [linters](../documentation/testing/_index.md) and configure them in your code editor:
-  - [markdownlint](../documentation/testing/markdownlint.md)
-  - [Vale](../documentation/testing/vale.md)
+- Install documentation [linters](testing/_index.md) and configure them in your code editor:
+  - [markdownlint](testing/markdownlint.md)
+  - [Vale](testing/vale.md)
 - [Set up the docs site to build locally](https://gitlab.com/gitlab-org/technical-writing/docs-gitlab-com/-/blob/main/doc/setup.md).
 - Optional. Install the [Conventional Comments](https://gitlab.com/conventionalcomments/conventional-comments-button) extension for Chrome.
   The plugin adds **Conventional Comment** buttons to GitLab comments.
diff --git a/doc/development/documentation/experiment_beta.md b/doc/development/documentation/experiment_beta.md
index 40cb0384a50..bd927058c79 100644
--- a/doc/development/documentation/experiment_beta.md
+++ b/doc/development/documentation/experiment_beta.md
@@ -17,7 +17,7 @@ When the feature changes from experiment or beta to generally available:
 
 - Remove the **Status** from the product availability details.
 - Remove any language about the feature not being ready for production.
-- Update the [history](../documentation/styleguide/availability_details.md#history).
+- Update the [history](styleguide/availability_details.md#history).
 
 ## Features that require user enrollment or feedback
 
diff --git a/doc/development/documentation/feature_flags.md b/doc/development/documentation/feature_flags.md
index bce2fe13476..e7bf237a274 100644
--- a/doc/development/documentation/feature_flags.md
+++ b/doc/development/documentation/feature_flags.md
@@ -48,7 +48,7 @@ When documenting the [offerings](styleguide/availability_details.md#offering), f
 ## Add history text
 
 When the state of a flag changes (for example, from disabled by default to enabled by default), add the change to the
-[history](../documentation/styleguide/availability_details.md#history).
+[history](styleguide/availability_details.md#history).
 
 Possible history entries are:
 
diff --git a/doc/development/documentation/restful_api_styleguide.md b/doc/development/documentation/restful_api_styleguide.md
index 057353167d0..74a7c61aa97 100644
--- a/doc/development/documentation/restful_api_styleguide.md
+++ b/doc/development/documentation/restful_api_styleguide.md
@@ -104,7 +104,7 @@ Example response:
 
 ## History
 
-Add [history](../documentation/styleguide/availability_details.md#history)
+Add [history](styleguide/availability_details.md#history)
 to describe new or updated API calls.
 
 To add history for an individual attribute, include it in the history
@@ -126,7 +126,7 @@ If the API or attribute is deployed behind a feature flag,
 ## Deprecations
 
 To document the deprecation of an API endpoint, follow the steps to
-[deprecate a page or topic](../documentation/styleguide/deprecations_and_removals.md).
+[deprecate a page or topic](styleguide/deprecations_and_removals.md).
 
 To deprecate an attribute:
 
diff --git a/doc/development/documentation/styleguide/availability_details.md b/doc/development/documentation/styleguide/availability_details.md
index 05105e99878..65d2b061f78 100644
--- a/doc/development/documentation/styleguide/availability_details.md
+++ b/doc/development/documentation/styleguide/availability_details.md
@@ -98,7 +98,7 @@ In addition:
 - Ensure that the output generates properly.
 - Ensure the version history begins with `-`.
 - If possible, include a link to the related issue. If there is no related issue, link to a merge request, or epic.
-- Do not link to [confidential issues](../styleguide/_index.md#confidential-or-restricted-access-links).
+- Do not link to [confidential issues](_index.md#confidential-or-restricted-access-links).
 - Do not link to the pricing page. Do not include the subscription tier.
 
 #### Updated features
diff --git a/doc/development/documentation/styleguide/word_list.md b/doc/development/documentation/styleguide/word_list.md
index 5a37d559968..617e23257c4 100644
--- a/doc/development/documentation/styleguide/word_list.md
+++ b/doc/development/documentation/styleguide/word_list.md
@@ -11,7 +11,7 @@ recommends these word choices. In addition:
 
 - The GitLab handbook contains a list of
   [top misused terms](https://handbook.gitlab.com/handbook/communication/top-misused-terms/).
-- The documentation [style guide](../styleguide/_index.md#language) includes details
+- The documentation [style guide](_index.md#language) includes details
   about language and capitalization.
 - 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).
 
@@ -873,7 +873,7 @@ Do not use Latin abbreviations. Use **for example**, **such as**, **for instance
 Avoid ellipses when you can. If you must include them, for example as part of a code block or other CLI response,
 use three periods with no space (`...`) instead of the `&hellip;` HTML entity or the `&#8230;` HTML code.
 
-For more information, see [code blocks](../styleguide/_index.md#code-blocks).
+For more information, see [code blocks](_index.md#code-blocks).
 
 Do not include any ellipses when documenting UI text.
 
diff --git a/doc/development/internal_analytics/_index.md b/doc/development/internal_analytics/_index.md
index be3e869b284..241665d54a9 100644
--- a/doc/development/internal_analytics/_index.md
+++ b/doc/development/internal_analytics/_index.md
@@ -180,7 +180,7 @@ The following diagram illustrates the process:
 ## Data flow
 
 On SaaS event records are directly sent to a collection system, called Snowplow, and imported into our data warehouse.
-Self-managed and GitLab Dedicated instances record event counts locally. Every week, a process called Service Ping sends the current
+GitLab Self-Managed and GitLab Dedicated instances record event counts locally. Every week, a process called Service Ping sends the current
 values for all pre-defined and active metrics to our data warehouse. For GitLab.com, metrics are calculated directly in the data warehouse.
 
 The following chart aims to illustrate this data flow:
diff --git a/doc/development/internal_analytics/metrics/metrics_instrumentation.md b/doc/development/internal_analytics/metrics/metrics_instrumentation.md
index 6deac249654..9fa39ebd215 100644
--- a/doc/development/internal_analytics/metrics/metrics_instrumentation.md
+++ b/doc/development/internal_analytics/metrics/metrics_instrumentation.md
@@ -368,7 +368,7 @@ This guide describes how to migrate a Service Ping metric from [`lib/gitlab/usag
    - Add tests for the individual metric [`spec/lib/gitlab/usage/metrics/instrumentations/`](https://gitlab.com/gitlab-org/gitlab/-/tree/master/lib/gitlab/usage/metrics/instrumentations).
    - Add tests for Service Ping.
 
-1. [Generate the metric definition file](../metrics/metrics_dictionary.md#create-a-new-metric-definition).
+1. [Generate the metric definition file](metrics_dictionary.md#create-a-new-metric-definition).
 
 1. Remove the code from [`lib/gitlab/usage_data.rb`](https://gitlab.com/gitlab-org/gitlab/-/blob/master/lib/gitlab/usage_data.rb) or [`ee/lib/ee/gitlab/usage_data.rb`](https://gitlab.com/gitlab-org/gitlab/-/blob/master/ee/lib/ee/gitlab/usage_data.rb).
 
diff --git a/doc/development/migration_style_guide.md b/doc/development/migration_style_guide.md
index e3e7c42cb1a..755124a24a7 100644
--- a/doc/development/migration_style_guide.md
+++ b/doc/development/migration_style_guide.md
@@ -1572,7 +1572,7 @@ D, [2020-07-06T00:37:12.653648 #130101] DEBUG -- :   ↳ config/initializers/con
 
 Here's a list of current [high-traffic tables](https://gitlab.com/gitlab-org/gitlab/-/blob/master/rubocop/rubocop-migrations.yml).
 
-Determining what tables are high-traffic can be difficult. Self-managed instances might use
+Determining what tables are high-traffic can be difficult. GitLab Self-Managed instances might use
 different features of GitLab with different usage patterns, thus making assumptions based
 on GitLab.com not enough.
 
diff --git a/doc/development/packages/new_format_development.md b/doc/development/packages/new_format_development.md
index 008f71feb6a..e6023c1bd40 100644
--- a/doc/development/packages/new_format_development.md
+++ b/doc/development/packages/new_format_development.md
@@ -243,7 +243,7 @@ the package format does not upload and store package files.
 #### Rate Limits on GitLab.com
 
 Package manager clients can make rapid requests that exceed the
-[GitLab.com standard API rate limits](../../user/gitlab_com/_index.md#gitlabcom-specific-rate-limits).
+[GitLab.com standard API rate limits](../../user/gitlab_com/_index.md#rate-limits-on-gitlabcom).
 This results in a `429 Too Many Requests` error.
 
 We have opened a set of paths to allow higher rate limits. Unless it is not possible,
diff --git a/doc/development/performance.md b/doc/development/performance.md
index 002d209be07..cebc9a44b90 100644
--- a/doc/development/performance.md
+++ b/doc/development/performance.md
@@ -33,7 +33,7 @@ This document describes various guidelines to ensure good and consistent perform
   - [GitLab performance monitoring](../administration/monitoring/performance/_index.md)
   - [Development department performance indicators](https://handbook.gitlab.com/handbook/engineering/development/performance-indicators/)
   - [Service measurement](service_measurement.md)
-- Self-managed administration and customer-focused:
+- GitLab Self-Managed administration and customer-focused:
   - [File system performance benchmarking](../administration/operations/filesystem_benchmarking.md)
   - [Sidekiq performance troubleshooting](../administration/sidekiq/sidekiq_troubleshooting.md)
 
diff --git a/doc/development/permissions/custom_roles.md b/doc/development/permissions/custom_roles.md
index 651206edbca..5972919b61d 100644
--- a/doc/development/permissions/custom_roles.md
+++ b/doc/development/permissions/custom_roles.md
@@ -41,7 +41,7 @@ Like default roles, custom roles are [inherited](../../user/project/members/_ind
 
 ### Finding existing abilities checks
 
-Abilities are often [checked in multiple locations](../permissions/authorizations.md#where-should-permissions-be-checked) for a single endpoint or web request. Therefore, it can be difficult to find the list of authorization checks that are run for a given endpoint.
+Abilities are often [checked in multiple locations](authorizations.md#where-should-permissions-be-checked) for a single endpoint or web request. Therefore, it can be difficult to find the list of authorization checks that are run for a given endpoint.
 
 To assist with this, you can locally set `GITLAB_DEBUG_POLICIES=true`.
 
diff --git a/doc/development/ruby_upgrade.md b/doc/development/ruby_upgrade.md
index ef0c090cfa9..d9f41ebb95c 100644
--- a/doc/development/ruby_upgrade.md
+++ b/doc/development/ruby_upgrade.md
@@ -59,7 +59,7 @@ Before any upgrade, consider all audiences and targets, ordered by how immediate
    GitLab SaaS is affected with the next deployment.
 1. **GitLab Self-Managed.** Customers installing GitLab via [Omnibus](https://gitlab.com/gitlab-org/omnibus-gitlab) use none of the above.
    Instead, their Ruby version is defined by the [Ruby software bundle](https://gitlab.com/gitlab-org/omnibus-gitlab/blob/master/config/software/ruby.rb) in Omnibus.
-   Self-managed customers are affected as soon as they upgrade to the release containing this change.
+   GitLab Self-Managed customers are affected as soon as they upgrade to the release containing this change.
 
 ## Ruby upgrade approach
 
diff --git a/doc/development/sidekiq/compatibility_across_updates.md b/doc/development/sidekiq/compatibility_across_updates.md
index 5c123f5474b..221a8565725 100644
--- a/doc/development/sidekiq/compatibility_across_updates.md
+++ b/doc/development/sidekiq/compatibility_across_updates.md
@@ -196,7 +196,7 @@ Add a migration (not a post-deployment migration) that uses `sidekiq_remove_jobs
 
 ### In the M+2 release
 
-Delete the worker class file and follow the guidance in our [Sidekiq queues documentation](../sidekiq/_index.md#sidekiq-queues) around running Rake tasks to regenerate/update related files.
+Delete the worker class file and follow the guidance in our [Sidekiq queues documentation](_index.md#sidekiq-queues) around running Rake tasks to regenerate/update related files.
 
 ## Renaming queues
 
diff --git a/doc/development/testing_guide/frontend_testing.md b/doc/development/testing_guide/frontend_testing.md
index f46606e5d6f..d4aad188df6 100644
--- a/doc/development/testing_guide/frontend_testing.md
+++ b/doc/development/testing_guide/frontend_testing.md
@@ -22,7 +22,7 @@ information on general testing practices at GitLab.
 
 If you are looking for a guide on Vue component testing, you can jump right away to this [section](../fe_guide/vue.md#testing-vue-components).
 
-Information on testing Vue 3 is contained in [this page](../testing_guide/testing_vue3.md).
+Information on testing Vue 3 is contained in [this page](testing_vue3.md).
 
 ## Jest
 
diff --git a/doc/development/testing_guide/testing_levels.md b/doc/development/testing_guide/testing_levels.md
index f59a55184f3..5db6bbcc21c 100644
--- a/doc/development/testing_guide/testing_levels.md
+++ b/doc/development/testing_guide/testing_levels.md
@@ -358,7 +358,7 @@ This also implies that database queries are executed which makes this category s
 
 See also:
 
-- The [RSpec testing guidelines](../testing_guide/best_practices.md#rspec).
+- The [RSpec testing guidelines](best_practices.md#rspec).
 - System / Feature tests in the [Testing Best Practices](best_practices.md#system--feature-tests).
 
 ```mermaid
diff --git a/doc/development/webhooks.md b/doc/development/webhooks.md
index 3995e41b4df..db995bf5a4e 100644
--- a/doc/development/webhooks.md
+++ b/doc/development/webhooks.md
@@ -83,7 +83,7 @@ or a GitLab instance.
 ## EE-only considerations
 
 Group webhooks are a Premium-licensed feature. All code related to triggering group webhooks,
-or building payloads for webhooks that are configurable only for groups, [must be in the `ee/` directory](../development/ee_features.md).
+or building payloads for webhooks that are configurable only for groups, [must be in the `ee/` directory](ee_features.md).
 
 ## Triggering a webhook
 
@@ -396,7 +396,7 @@ to feature removal, set the value to `null`, `{}`, or `[]` rather than remove th
 
 When writing a unit test for the [`DataBuilder` class](#defining-payloads), assert that:
 
-- A set number of database requests are made, using [`QueryRecorder`](../development/database/query_recorder.md),
+- A set number of database requests are made, using [`QueryRecorder`](database/query_recorder.md),
   You can do this by measuring the number of queries using `QueryRecorder` and then
   comparing against that number in the spec, to ensure that the query count does
   not change without our conscious choice. Also see [preloading](#minimizing-database-requests) of associated data.
@@ -410,6 +410,6 @@ You can configure the webhook URL to one provided by <https://webhook.site> to v
 
 ## Having changes reviewed
 
-In addition to the [usual reviewers for code review](../development/code_review.md#approval-guidelines), changes to webhooks
+In addition to the [usual reviewers for code review](code_review.md#approval-guidelines), changes to webhooks
 should be reviewed by a backend team member from
 [Import & Integrate](https://handbook.gitlab.com/handbook/product/categories/#import-and-integrate-group).
diff --git a/doc/install/docker/_index.md b/doc/install/docker/_index.md
index 56788cb1587..8797eb44e48 100644
--- a/doc/install/docker/_index.md
+++ b/doc/install/docker/_index.md
@@ -25,4 +25,4 @@ Find the GitLab official Docker images at:
 - [Configure GitLab running in a Docker container](configuration.md)
 - [Back up GitLab running in a Docker container](backup.md)
 - [Upgrade GitLab running in a Docker container](upgrade.md)
-- [Troubleshooting GitLab running in a Docker container](../docker/troubleshooting.md)
+- [Troubleshooting GitLab running in a Docker container](troubleshooting.md)
diff --git a/doc/install/docker/configuration.md b/doc/install/docker/configuration.md
index 01cdb389b00..89699755de9 100644
--- a/doc/install/docker/configuration.md
+++ b/doc/install/docker/configuration.md
@@ -66,7 +66,7 @@ The settings contained in `GITLAB_OMNIBUS_CONFIG` aren't written to the
 settings, separate them with a colon (`;`).
 
 The following example sets the external URL, enables LFS, and starts
-the container with a [minimal shm size required for Prometheus](../docker/troubleshooting.md#devshm-mount-not-having-enough-space-in-docker-container):
+the container with a [minimal shm size required for Prometheus](troubleshooting.md#devshm-mount-not-having-enough-space-in-docker-container):
 
 ```shell
 sudo docker run --detach \
diff --git a/doc/legal/licensing_policy.md b/doc/legal/licensing_policy.md
index 12c7446945c..eef502da97f 100644
--- a/doc/legal/licensing_policy.md
+++ b/doc/legal/licensing_policy.md
@@ -119,7 +119,7 @@ With this approach, GitLab makes the assumption that all other lower user count
 
 ### Visibility into latest usage data, and how to identify which of the customer's instances the data is for
 
-Self-managed usage data shared is stored in CustomersDot under `License seat links`. Data is recorded daily for customers on
+GitLab Self-Managed usage data shared is stored in CustomersDot under `License seat links`. Data is recorded daily for customers on
 Cloud Licensing and whenever customers on Offline licenses share their usage data via email (requested monthly).
 To view this data, the customer can search by `Company` name or `Subscription` name. Also recorded with this data is `Hostname` and `Instance identifier` ID,
 which can help to indicate if the data is from a production or development instance.
diff --git a/doc/operations/incident_management/integrations.md b/doc/operations/incident_management/integrations.md
index 34d9ce9b30b..5dbf6f86ccd 100644
--- a/doc/operations/incident_management/integrations.md
+++ b/doc/operations/incident_management/integrations.md
@@ -246,7 +246,7 @@ Ensure your requests are smaller than the
 
 #### Prometheus severity options
 
-Alerts from Prometheus can provide any of the case-insensitive follow values for [alert severity](../incident_management/alerts.md#alert-severity):
+Alerts from Prometheus can provide any of the case-insensitive follow values for [alert severity](alerts.md#alert-severity):
 
 - **Critical**: `critical`, `s1`, `p1`, `emergency`, `fatal`
 - **High**: `high`, `s2`, `p2`, `major`, `page`
@@ -432,7 +432,7 @@ part of the payload.
 For more information on alert properties and mappings, see
 [Customize the alert payload outside of GitLab](#customize-the-alert-payload-outside-of-gitlab).
 
-You can also configure the associated [incident to be closed automatically](../incident_management/manage_incidents.md#automatically-close-incidents-via-recovery-alerts) when the alert resolves.
+You can also configure the associated [incident to be closed automatically](manage_incidents.md#automatically-close-incidents-via-recovery-alerts) when the alert resolves.
 
 ## Link to your Opsgenie Alerts
 
diff --git a/doc/security/rate_limits.md b/doc/security/rate_limits.md
index 48071bdcb54..b5df0b8f7c6 100644
--- a/doc/security/rate_limits.md
+++ b/doc/security/rate_limits.md
@@ -15,7 +15,7 @@ title: Rate limits
 {{< alert type="note" >}}
 
 For GitLab.com, see
-[GitLab.com-specific rate limits](../user/gitlab_com/_index.md#gitlabcom-specific-rate-limits).
+[GitLab.com-specific rate limits](../user/gitlab_com/_index.md#rate-limits-on-gitlabcom).
 
 {{< /alert >}}
 
diff --git a/doc/security/tokens/token_troubleshooting.md b/doc/security/tokens/token_troubleshooting.md
index abec3c6a014..2e255946d86 100644
--- a/doc/security/tokens/token_troubleshooting.md
+++ b/doc/security/tokens/token_troubleshooting.md
@@ -181,7 +181,7 @@ on that date.
 To manage this issue, you should upgrade to GitLab 17.2 or later, because these versions
 contain a [tool that assists with analyzing, extending, or remove token expiration dates](../../administration/raketasks/tokens/_index.md).
 
-If you cannot run the tool, you can also run scripts in self-managed instances to identify
+If you cannot run the tool, you can also run scripts in GitLab Self-Managed instances to identify
 tokens that either:
 
 - Expire on a specific date.
diff --git a/doc/solutions/cloud/aws/gitlab_aws_integration.md b/doc/solutions/cloud/aws/gitlab_aws_integration.md
index 373d8cff91a..8b1d3a5227f 100644
--- a/doc/solutions/cloud/aws/gitlab_aws_integration.md
+++ b/doc/solutions/cloud/aws/gitlab_aws_integration.md
@@ -10,7 +10,7 @@ Learn how to integrate GitLab and AWS.
 
 This content is intended for GitLab team members as well as members of the wider community.
 
-Unless otherwise noted, all of this content applies to both GitLab.com and self-managed instances.
+Unless otherwise noted, all of this content applies to both GitLab.com and GitLab Self-Managed instances.
 
 This page attempts to index the ways in which GitLab can integrate with AWS. It does so whether the integration is the result of configuring general functionality, was built in to AWS or GitLab or is provided as a solution.
 
@@ -143,7 +143,7 @@ Top-level groups on GitLab.com are also known as "Namespaces" and naming one aft
 ### User authentication and authorization between GitLab and AWS
 
 - [SAML SSO for GitLab.com groups](../../../user/group/saml_sso/_index.md) `[GitLab Configuration]` - GitLab.com only
-- [Integrate LDAP with GitLab](../../../administration/auth/ldap/_index.md) `[GitLab Configuration]` - Self-managed only
+- [Integrate LDAP with GitLab](../../../administration/auth/ldap/_index.md) `[GitLab Configuration]` - GitLab Self-Managed only
 
 ### Runner workload authentication and authorization integration
 
diff --git a/doc/solutions/languages/rust/_index.md b/doc/solutions/languages/rust/_index.md
index 041666541df..4359cfb9317 100644
--- a/doc/solutions/languages/rust/_index.md
+++ b/doc/solutions/languages/rust/_index.md
@@ -7,7 +7,7 @@ title: Rust Language and Ecosystem Solutions Index
 
 This page attempts to index the ways in which GitLab supports Rust. It does so whether the integration is the result of configuring general functionality, was built in to Rust or GitLab or is provided as a solution.
 
-Unless otherwise noted, all of this content applies to both GitLab.com and self-managed instances.
+Unless otherwise noted, all of this content applies to both GitLab.com and GitLab Self-Managed instances.
 
 | Text Tag                 | Configuration / Built / Solution                             | Support/Maintenance                                          |
 | ------------------------ | ------------------------------------------------------------ | ------------------------------------------------------------ |
diff --git a/doc/subscriptions/customers_portal.md b/doc/subscriptions/customers_portal.md
index 0eb473934b5..0206e618778 100644
--- a/doc/subscriptions/customers_portal.md
+++ b/doc/subscriptions/customers_portal.md
@@ -9,7 +9,7 @@ title: The Customers Portal
 For some management tasks for your subscription and account, such as purchasing additional seats or storage and viewing invoices, you use the Customers Portal. See the following pages for specific instructions on managing your subscription:
 
 - [GitLab SaaS subscription](gitlab_com/_index.md)
-- [Self-managed subscription](self_managed/_index.md)
+- [GitLab Self-Managed subscription](self_managed/_index.md)
 
 If you made your purchase through an authorized reseller, you must contact them directly to make changes to your subscription.
 For more information, see [Customers that purchased through a reseller](#customers-that-purchased-through-a-reseller).
diff --git a/doc/subscriptions/gitlab_dedicated/_index.md b/doc/subscriptions/gitlab_dedicated/_index.md
index 1ab7245e3ef..677cc9ae9c4 100644
--- a/doc/subscriptions/gitlab_dedicated/_index.md
+++ b/doc/subscriptions/gitlab_dedicated/_index.md
@@ -256,7 +256,7 @@ Features behind flags that are disabled by default are not ready for production
 
 When a feature becomes generally available and the flag is enabled or removed, the feature becomes available in
 GitLab Dedicated in the same GitLab version. GitLab Dedicated follows its own
-[release schedule](../gitlab_dedicated/maintenance.md) for version deployments.
+[release schedule](maintenance.md) for version deployments.
 
 ## Migrate to GitLab Dedicated
 
diff --git a/doc/subscriptions/self_managed/_index.md b/doc/subscriptions/self_managed/_index.md
index 9042d98b0af..45c0c3b8417 100644
--- a/doc/subscriptions/self_managed/_index.md
+++ b/doc/subscriptions/self_managed/_index.md
@@ -629,4 +629,4 @@ After your license has expired:
 
 ## Storage
 
-The amount of storage and transfer for self-managed instances has no application limits. Administrators are responsible for the underlying infrastructure costs and can set [repository size limits](../../administration/settings/account_and_limit_settings.md#repository-size-limit).
+The amount of storage and transfer for GitLab Self-Managed instances has no application limits. Administrators are responsible for the underlying infrastructure costs and can set [repository size limits](../../administration/settings/account_and_limit_settings.md#repository-size-limit).
diff --git a/doc/subscriptions/subscription-add-ons.md b/doc/subscriptions/subscription-add-ons.md
index c36ffe9e407..81637a9cfa3 100644
--- a/doc/subscriptions/subscription-add-ons.md
+++ b/doc/subscriptions/subscription-add-ons.md
@@ -117,7 +117,7 @@ The user is sent a confirmation email.
 
 #### Configure network and proxy settings
 
-For self-managed instances, to enable GitLab Duo features,
+For GitLab Self-Managed instances, to enable GitLab Duo features,
 you must [enable network connectivity](../user/ai_features_enable.md).
 
 ## Assign and remove GitLab Duo seats in bulk
@@ -158,7 +158,7 @@ Prerequisites:
    - To remove users from seats, select **Remove seat**, then **Remove seats** to confirm.
 1. To the right of the user, turn on the toggle to assign a GitLab Duo seat.
 
-Administrators of self-managed instances can also use a [Rake task](../administration/raketasks/user_management.md#bulk-assign-users-to-gitlab-duo-pro) to assign or remove seats in bulk.
+Administrators of GitLab Self-Managed instances can also use a [Rake task](../administration/raketasks/user_management.md#bulk-assign-users-to-gitlab-duo-pro) to assign or remove seats in bulk.
 
 #### Managing GitLab Duo seats with LDAP configuration
 
diff --git a/doc/topics/autodevops/stages.md b/doc/topics/autodevops/stages.md
index 63da5b14e48..a7ff6e8f85a 100644
--- a/doc/topics/autodevops/stages.md
+++ b/doc/topics/autodevops/stages.md
@@ -574,4 +574,4 @@ for updates.
 
 This stage is enabled by default. You can disable it by adding the
 `CODE_INTELLIGENCE_DISABLED` CI/CD variable. Read more about
-[disabling Auto DevOps jobs](../autodevops/cicd_variables.md#job-skipping-variables).
+[disabling Auto DevOps jobs](cicd_variables.md#job-skipping-variables).
diff --git a/doc/topics/autodevops/upgrading_auto_deploy_dependencies.md b/doc/topics/autodevops/upgrading_auto_deploy_dependencies.md
index 23b1d5c6c03..fbbf094cfcb 100644
--- a/doc/topics/autodevops/upgrading_auto_deploy_dependencies.md
+++ b/doc/topics/autodevops/upgrading_auto_deploy_dependencies.md
@@ -31,7 +31,7 @@ This guide explains how to upgrade your deployments with newer or different majo
 The process to check the current versions differs depending on which template you
 are using. First verify which template is in use:
 
-- For self-managed instances, the [stable Auto Deploy template bundled with the GitLab package](https://gitlab.com/gitlab-org/gitlab/-/blob/master/lib/gitlab/ci/templates/Jobs/Deploy.gitlab-ci.yml)
+- For GitLab Self-Managed instances, the [stable Auto Deploy template bundled with the GitLab package](https://gitlab.com/gitlab-org/gitlab/-/blob/master/lib/gitlab/ci/templates/Jobs/Deploy.gitlab-ci.yml)
   is being used.
 - [The GitLab.com stable Auto Deploy template](https://gitlab.com/gitlab-org/gitlab/-/blob/master/lib/gitlab/ci/templates/Jobs/Deploy.gitlab-ci.yml)
   is being used if **one** of the following is true:
diff --git a/doc/topics/git/file_management.md b/doc/topics/git/file_management.md
index 7192bc45c4f..c7a73acfe29 100644
--- a/doc/topics/git/file_management.md
+++ b/doc/topics/git/file_management.md
@@ -216,7 +216,7 @@ It's a good option for:
 
 Prerequisites:
 
-- You must have [Git LFS installed](../git/lfs/_index.md).
+- You must have [Git LFS installed](lfs/_index.md).
 - You must have the Maintainer role for the project.
 
 ### Configure file locks
diff --git a/doc/tutorials/automate_runner_creation/_index.md b/doc/tutorials/automate_runner_creation/_index.md
index f2a9d322839..8f51caa0f69 100644
--- a/doc/tutorials/automate_runner_creation/_index.md
+++ b/doc/tutorials/automate_runner_creation/_index.md
@@ -106,7 +106,7 @@ To create a project access token:
    - By default, this date can be a maximum of 365 days later than the current date. In GitLab 17.6 or later, you can [extend this limit to 400 days](https://gitlab.com/gitlab-org/gitlab/-/issues/461901).
 
    - An instance-wide [maximum lifetime](../../administration/settings/account_and_limit_settings.md#limit-the-lifetime-of-access-tokens)
-     setting can limit the maximum allowable lifetime on self-managed instances.
+     setting can limit the maximum allowable lifetime on GitLab Self-Managed instances.
 1. From the **Select a role** dropdown list:
    - For the project access token, select **Maintainer**.
    - For the group access token, select **Owner**.
diff --git a/doc/user/application_security/continuous_vulnerability_scanning/_index.md b/doc/user/application_security/continuous_vulnerability_scanning/_index.md
index 8ee725f556e..e825c1bc622 100644
--- a/doc/user/application_security/continuous_vulnerability_scanning/_index.md
+++ b/doc/user/application_security/continuous_vulnerability_scanning/_index.md
@@ -106,7 +106,7 @@ Improvements to this behavior, including requiring only to have a updated SBOM u
 
 ## Security advisories
 
-Continuous Vulnerability Scanning uses the Package Metadata Database, a service managed by GitLab which aggregates license and security advisory data, and regularly publishes updates that are used by GitLab.com and self-managed instances.
+Continuous Vulnerability Scanning uses the Package Metadata Database, a service managed by GitLab which aggregates license and security advisory data, and regularly publishes updates that are used by GitLab.com and GitLab Self-Managed instances.
 
 On GitLab.com, the synchronization is managed by GitLab and is available to all projects.
 
diff --git a/doc/user/application_security/dast/browser_based_4_to_5_migration_guide.md b/doc/user/application_security/dast/browser_based_4_to_5_migration_guide.md
index a281e2eac1d..6cdb47d5567 100644
--- a/doc/user/application_security/dast/browser_based_4_to_5_migration_guide.md
+++ b/doc/user/application_security/dast/browser_based_4_to_5_migration_guide.md
@@ -147,4 +147,4 @@ See [configuration](browser/configuration/_index.md) for more information on con
 | `DAST_TARGET_AVAILABILITY_TIMEOUT`          | Rename             | To `DAST_TARGET_CHECK_TIMEOUT`                |
 | `DAST_USERNAME`                             | Rename             | To `DAST_AUTH_USERNAME`                       |
 | `DAST_USERNAME_FIELD`                       | Rename             | To `DAST_AUTH_USERNAME_FIELD`                 |
-| `DAST_WEBSITE`                              | Rename             | To `DAST_TARGET_URL`<br/>Self-managed: Upgrade your instance to version 17.0 or newer before removing `DAST_WEBSITE`. This variable is required if you use the `DAST.gitlab-ci.yml` file included with pre-17.0 versions of GitLab. |
+| `DAST_WEBSITE`                              | Rename             | To `DAST_TARGET_URL`<br/>GitLab Self-Managed: Upgrade your instance to version 17.0 or newer before removing `DAST_WEBSITE`. This variable is required if you use the `DAST.gitlab-ci.yml` file included with pre-17.0 versions of GitLab. |
diff --git a/doc/user/application_security/dast/proxy_based_to_browser_based_migration_guide.md b/doc/user/application_security/dast/proxy_based_to_browser_based_migration_guide.md
index 8c85566ec0b..ef7a9d8d2eb 100644
--- a/doc/user/application_security/dast/proxy_based_to_browser_based_migration_guide.md
+++ b/doc/user/application_security/dast/proxy_based_to_browser_based_migration_guide.md
@@ -170,7 +170,7 @@ See [configuration](browser/configuration/_index.md) for more information on con
 | `DAST_TARGET_AVAILABILITY_TIMEOUT`   | Change                   | To `DAST_TARGET_CHECK_TIMEOUT` using a duration. For example, instead of `60`, use `60s` |
 | `DAST_USE_AJAX_SPIDER`               | Remove                   | Not supported                                                                            |
 | `DAST_XML_REPORT`                    | Remove                   | Not supported                                                                            |
-| `DAST_WEBSITE`                              | Rename             | To `DAST_TARGET_URL`<br/>Self-managed: Upgrade your instance to version 17.0 or newer before removing `DAST_WEBSITE`. This variable is required if you use the `DAST.gitlab-ci.yml` file included with pre-17.0 versions of GitLab. |
+| `DAST_WEBSITE`                              | Rename             | To `DAST_TARGET_URL`<br/>GitLab Self-Managed: Upgrade your instance to version 17.0 or newer before removing `DAST_WEBSITE`. This variable is required if you use the `DAST.gitlab-ci.yml` file included with pre-17.0 versions of GitLab. |
 | `DAST_ZAP_CLI_OPTIONS`               | Remove                   | Not supported                                                                            |
 | `DAST_ZAP_LOG_CONFIGURATION`         | Remove                   | Not supported                                                                            |
 | `SECURE_ANALYZERS_PREFIX`            | None                     | Supported                                                                                |
diff --git a/doc/user/application_security/secret_detection/client/_index.md b/doc/user/application_security/secret_detection/client/_index.md
index f409db02c15..8dc3c3c3298 100644
--- a/doc/user/application_security/secret_detection/client/_index.md
+++ b/doc/user/application_security/secret_detection/client/_index.md
@@ -35,5 +35,6 @@ Client-side secret detection checks only the following for secrets:
 - Comments in issues or merge requests.
 - Descriptions of issues or merge requests.
 
-For details of which types of secrets are covered by client-side secret detection, see
+Secrets with custom prefixes are supported only for GitLab personal access tokens.
+For more information about which types of secrets are covered by client-side secret detection, see
 [Detected secrets](../detected_secrets.md).
diff --git a/doc/user/application_security/secret_detection/pipeline/_index.md b/doc/user/application_security/secret_detection/pipeline/_index.md
index b2fd8412b5b..9952839957b 100644
--- a/doc/user/application_security/secret_detection/pipeline/_index.md
+++ b/doc/user/application_security/secret_detection/pipeline/_index.md
@@ -112,9 +112,12 @@ For more information, see the confidential project `https://gitlab.com/gitlab-or
 ### Detected secrets
 
 Pipeline secret detection scans the repository's content for specific patterns. Each pattern matches
-a specific type of secret and is specified in a rule by using a TOML syntax. The default set of
-rules is maintained by GitLab. In the Ultimate tier, you can customize the default ruleset to suit
-your needs. For details, see [Customize analyzer rulesets](configure.md#customize-analyzer-rulesets). To confirm
+a specific type of secret and is specified in a rule by using a TOML syntax. GitLab maintains the default set of rules.
+
+With GitLab Ultimate you can extend these rules to suit your needs. For example, while personal access tokens that use a custom prefix are not detected by default, you can customize the rules to identify these tokens.
+For details, see [Customize analyzer rulesets](configure.md#customize-analyzer-rulesets).
+
+To confirm
 which secrets are detected by pipeline secret detection, see
 [Detected secrets](../detected_secrets.md). To provide reliable, high-confidence results, pipeline
 secret detection only looks for passwords or other unstructured secrets in specific contexts like
diff --git a/doc/user/application_security/secret_detection/secret_push_protection/_index.md b/doc/user/application_security/secret_detection/secret_push_protection/_index.md
index f69b45b0cb5..cf7197ab3da 100644
--- a/doc/user/application_security/secret_detection/secret_push_protection/_index.md
+++ b/doc/user/application_security/secret_detection/secret_push_protection/_index.md
@@ -66,12 +66,12 @@ Secret push protection scans [files or commits](#coverage) for specific patterns
 matches a specific type of secret. To confirm which secrets are detected by secret push protection,
 see [Detected secrets](../detected_secrets.md). Only high-confidence patterns were chosen for secret
 push protection, to minimize the delay when pushing your commits and minimize the number of false
-alerts. You can [exclude](../exclusions.md) selected secrets from detection by secret push
-protection.
+alerts. For example, personal access tokens that use a custom prefix are not detected by secret push protection.
+You can [exclude](../exclusions.md) selected secrets from detection by secret push protection.
 
 ## Enable secret push protection
 
-On GitLab Dedicated and Self-managed instances, you must:
+On GitLab Dedicated and GitLab Self-Managed instances, you must:
 
 1. [Allow secret push protection on the entire instance](#allow-the-use-of-secret-push-protection-in-your-gitlab-instance).
 1. [Enable secret push protection per project](#enable-secret-push-protection-in-a-project).
@@ -80,7 +80,7 @@ On GitLab.com, you must enable secret push protection per project.
 
 ### Allow the use of secret push protection in your GitLab instance
 
-On GitLab Dedicated and Self-managed instances, you must allow secret push protection before you can enable it in a project.
+On GitLab Dedicated and GitLab Self-Managed instances, you must allow secret push protection before you can enable it in a project.
 
 Prerequisites:
 
@@ -100,7 +100,7 @@ Secret push protection is allowed on the instance. To use this feature, you must
 Prerequisites:
 
 - You must have at least the Maintainer role for the project.
-- On GitLab Dedicated and Self-managed, you must allow secret push protection on the instance.
+- On GitLab Dedicated and GitLab Self-Managed, you must allow secret push protection on the instance.
 
 To enable secret push protection in a project:
 
diff --git a/doc/user/application_security/vulnerability_archival/_index.md b/doc/user/application_security/vulnerability_archival/_index.md
new file mode 100644
index 00000000000..ad4d6579edc
--- /dev/null
+++ b/doc/user/application_security/vulnerability_archival/_index.md
@@ -0,0 +1,71 @@
+---
+stage: Security Risk Management
+group: Security Insights
+info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
+title: Vulnerability archive
+---
+
+{{< details >}}
+
+- Tier: Ultimate
+- Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
+
+{{< /details >}}
+
+{{< history >}}
+
+- Introduced in GitLab 18.0 [with a flag](../../../administration/feature_flags.md) named `vulnerability_archival`. Disabled by default.
+
+{{< /history >}}
+
+{{< alert type="flag" >}}
+
+The availability of this feature is controlled by a feature flag. For more information, see the history.
+
+{{< /alert >}}
+
+To ensure the GitLab database remains performant, vulnerabilities are archived monthly from the
+database. Vulnerabilities that were last updated more than one year ago are archived. A
+vulnerability is updated every time a change is made, for example, when its status is changed.
+
+Archived vulnerabilities remain available for download for an additional 3 years, after which they are
+deleted.
+
+Vulnerability metrics, such as those in the security dashboard and value streams dashboards, include
+statistics on archived vulnerabilities.
+
+## Archival process
+
+Every month, the vulnerability archival process runs and does the following:
+
+- Archives vulnerabilities last updated more than 12 months ago.
+
+  Archived vulnerabilities are deleted from the vulnerability report. To retrieve their details,
+  download the relevant vulnerability archive.
+
+- Deletes archives created more than 3 years ago.
+
+## Vulnerability archive
+
+A vulnerability archive is a CSV file containing details of all vulnerabilities that were
+archived in a specific month or year, or within a specific date range.
+
+### Download a vulnerability archive
+
+Download a vulnerability archive to search or analyze the details it contains.
+
+Prerequisites:
+
+- You must have the Owner role for the project or the `read_vulnerability_archive` permission.
+
+To download a vulnerability archive:
+
+1. On the left sidebar, select **Search or go to** and find your project or group.
+1. Select **Secure > Security configuration**, then select **Vulnerability Management**.
+1. To download details of all vulnerabilities archived:
+   - For a specific year, in the row for that year, select **Download all**.
+   - For a specific year and month, expand the year, then in the row for that month select **Download** ({{< icon name="download" >}}).
+   - For a specific date range, in the **From** and **To** fields enter the dates and then
+      select **Download**.
+
+The selected vulnerability archive is downloaded as a CSV file.
diff --git a/doc/user/application_security/vulnerability_report/_index.md b/doc/user/application_security/vulnerability_report/_index.md
index 9f83d5d89bd..6f70354ab88 100644
--- a/doc/user/application_security/vulnerability_report/_index.md
+++ b/doc/user/application_security/vulnerability_report/_index.md
@@ -35,6 +35,13 @@ Access detailed information for each vulnerability, including Common Vulnerabili
 (CVSS) scores and file locations when available. Filter and group similar vulnerabilities to address
 them systematically.
 
+{{< alert type="note" >}}
+
+On GitLab.com, vulnerabilities are archived one year after they were last updated. For more details
+see [vulnerability archival](../vulnerability_archival/_index.md).
+
+{{< /alert >}}
+
 <i class="fa fa-youtube-play youtube" aria-hidden="true"></i>
 For an overview, see [Vulnerability Management](https://www.youtube.com/watch?v=alMRIq5UPbw).
 
@@ -114,8 +121,8 @@ You can filter by:
   Dismissed vulnerabilities can be filtered together or individually by the reason they were
   dismissed.
 - **Severity**: Critical, high, medium, low, info, unknown.
--**Report Type**: For more details, see [Report Type filter](#report-type-filter)
--**Scanner**: For more details, see [Scanner filter](#scanner-filter)
+- **Report Type**: For more details, see [Report Type filter](#report-type-filter)
+- **Scanner**: For more details, see [Scanner filter](#scanner-filter)
 - **Activity**: For more details, see [Activity filter](#activity-filter).
 - **Identifier**: Filter by the vulnerability's identifier (available only for projects, support for groups is proposed in [issue 508713](https://gitlab.com/gitlab-org/gitlab/-/issues/508713)).
 - **Project**: Filter vulnerabilities in specific projects (available only for groups).
@@ -301,7 +308,7 @@ refreshed.
 {{< history >}}
 
 - [Introduced](https://gitlab.com/groups/gitlab-org/-/epics/16157) in GitLab 17.9 [with a flag](../../../administration/feature_flags.md) named `vulnerability_severity_override`. Disabled by default.
-- [Enabled on GitLab.com, GitLab Self-Managed, and GitLab Dedicated](https://issue-link) in GitLab 17.10.
+- [Enabled on GitLab.com, GitLab Self-Managed, and GitLab Dedicated](https://gitlab.com/groups/gitlab-org/-/epics/16157) in GitLab 17.10.
 
 {{< /history >}}
 
diff --git a/doc/user/clusters/agent/user_access.md b/doc/user/clusters/agent/user_access.md
index b71189954b9..7159885edf1 100644
--- a/doc/user/clusters/agent/user_access.md
+++ b/doc/user/clusters/agent/user_access.md
@@ -27,7 +27,7 @@ of a specific project or group.
 
 Granting access also activates [the Dashboard for Kubernetes](../../../ci/environments/kubernetes_dashboard.md) for a project or group.
 
-For self-managed instances, make sure you either:
+For GitLab Self-Managed instances, make sure you either:
 
 - Host your GitLab instance and [KAS](../../../administration/clusters/kas.md) on the same domain.
 - Host KAS on a subdomain of GitLab. For example, GitLab on `gitlab.com` and KAS on `kas.gitlab.com`.
diff --git a/doc/user/free_user_limit.md b/doc/user/free_user_limit.md
index 12d5e586faa..6960d1f4259 100644
--- a/doc/user/free_user_limit.md
+++ b/doc/user/free_user_limit.md
@@ -38,7 +38,7 @@ User limits do not apply to users in the Free tier of:
     - GitLab for Open Source
     - GitLab for Education
     - GitLab for Startups
-- [Self-managed subscriptions](../subscriptions/self_managed/_index.md)
+- [GitLab Self-Managed subscriptions](../subscriptions/self_managed/_index.md)
 
 For more information, you can [talk to an expert](https://page.gitlab.com/usage_limits_help.html).
 
diff --git a/doc/user/gitlab_com/_index.md b/doc/user/gitlab_com/_index.md
index ee9cbe82bd8..e5f9bee67d3 100644
--- a/doc/user/gitlab_com/_index.md
+++ b/doc/user/gitlab_com/_index.md
@@ -65,6 +65,48 @@ Similarly, you can clone a project's wiki to back it up. All files
 [uploaded after August 22, 2020](../project/wiki/_index.md#create-a-new-wiki-page)
 are included when cloning.
 
+## CI/CD
+
+Below are the current settings regarding [GitLab CI/CD](../../ci/_index.md).
+Any settings or feature limits not listed here are using the defaults listed in
+the related documentation.
+
+| Setting                                                                          | GitLab.com                                                                                                 | Default (GitLab Self-Managed) |
+|----------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------|------------------------|
+| Artifacts maximum size (compressed)                                              | 1 GB                                                                                                       | See [Maximum artifacts size](../../administration/settings/continuous_integration.md#maximum-artifacts-size). |
+| Artifacts [expiry time](../../ci/yaml/_index.md#artifactsexpire_in)               | 30 days unless otherwise specified                                                                         | See [Default artifacts expiration](../../administration/settings/continuous_integration.md#default-artifacts-expiration). Artifacts created before June 22, 2020 have no expiry. |
+| Scheduled Pipeline Cron                                                          | `*/5 * * * *`                                                                                              | See [Pipeline schedules advanced configuration](../../administration/cicd/_index.md#change-maximum-scheduled-pipeline-frequency). |
+| Maximum jobs in active pipelines                                                 | `500` for Free tier, `1000` for all trial tiers, `20000` for Premium, and `100000` for Ultimate.           | See [Number of jobs in active pipelines](../../administration/instance_limits.md#number-of-jobs-in-active-pipelines). |
+| Maximum CI/CD subscriptions to a project                                         | `2`                                                                                                        | See [Number of CI/CD subscriptions to a project](../../administration/instance_limits.md#number-of-cicd-subscriptions-to-a-project). |
+| Maximum number of pipeline triggers in a project                                 | `25000`                                                                                                    | See [Limit the number of pipeline triggers](../../administration/instance_limits.md#limit-the-number-of-pipeline-triggers). |
+| Maximum pipeline schedules in projects                                           | `10` for Free tier, `50` for all paid tiers                                                                | See [Number of pipeline schedules](../../administration/instance_limits.md#number-of-pipeline-schedules). |
+| Maximum pipelines for each schedule                                                   | `24` for Free tier, `288` for all paid tiers                                                               | See [Limit the number of pipelines created by a pipeline schedule each day](../../administration/instance_limits.md#limit-the-number-of-pipelines-created-by-a-pipeline-schedule-each-day). |
+| Maximum number of schedule rules defined for each security policy project        | Unlimited for all paid tiers                                                                               | See [Number of schedule rules defined for each security policy project](../../administration/instance_limits.md#limit-the-number-of-schedule-rules-defined-for-security-policy-project). |
+| Scheduled job archiving                                                          | 3 months                                                                                                   | Never. Jobs created before June 22, 2020 were archived after September 22, 2020. |
+| Maximum test cases for each [unit test report](../../ci/testing/unit_test_reports.md) | `500000`                                                                                                   | Unlimited.             |
+| Maximum registered runners                                                       | Free tier: `50` for each group and `50`for each project<br/>All paid tiers: `1000` for each group and `1000` for each project | See [Number of registered runners for each scope](../../administration/instance_limits.md#number-of-registered-runners-for-each-scope). |
+| Limit of dotenv variables                                                        | Free tier: `50`<br>Premium tier: `100`<br>Ultimate tier: `150`                                             | See [Limit dotenv variables](../../administration/instance_limits.md#limit-dotenv-variables). |
+| Maximum downstream pipeline trigger rate (for a given project, user, and commit) | `350` each minute                                                                                           | See [Maximum downstream pipeline trigger rate](../../administration/settings/continuous_integration.md#maximum-downstream-pipeline-trigger-rate). |
+
+## Container registry
+
+| Setting                                | GitLab.com                       | Default (self-managed) |
+|:---------------------------------------|:---------------------------------|------------------------|
+| Domain name                            | `registry.gitlab.com`            |                        |
+| IP address                             | `35.227.35.254`                  |                        |
+| CDN domain name                        | `cdn.registry.gitlab-static.net` |                        |
+| CDN IP address                         | `34.149.22.116`                  |                        |
+| Authorization token duration (minutes) | `15`                             | See [increase container registry token duration](../../administration/packages/container_registry.md#increase-token-duration). |
+
+To use the GitLab container registry, Docker clients must have access to:
+
+- The registry endpoint and GitLab.com for authorization.
+- Google Cloud Storage or Google Cloud Content Delivery Network to download images.
+
+GitLab.com is fronted by Cloudflare.
+For incoming connections to GitLab.com, you must allow CIDR blocks of Cloudflare
+([IPv4](https://www.cloudflare.com/ips-v4/) and [IPv6](https://www.cloudflare.com/ips-v6/)).
+
 ## Email
 
 Email configuration settings, IP addressees, and aliases.
@@ -103,47 +145,11 @@ GitLab.com has a mailbox configured for Service Desk with the email address:
 [custom suffix](../project/service_desk/configure.md#configure-a-suffix-for-service-desk-alias-email) in project
 settings.
 
-## GitLab CI/CD
+## Gitaly RPC concurrency limits on GitLab.com
 
-Below are the current settings regarding [GitLab CI/CD](../../ci/_index.md).
-Any settings or feature limits not listed here are using the defaults listed in
-the related documentation.
+Per-repository Gitaly RPC concurrency and queuing limits are configured for different types of Git operations such as `git clone`. When these limits are exceeded, a `fatal: remote error: GitLab is currently unable to handle this request due to load` message is returned to the client.
 
-| Setting                                                                          | GitLab.com                                                                                                 | Default (GitLab Self-Managed) |
-|----------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------|------------------------|
-| Artifacts maximum size (compressed)                                              | 1 GB                                                                                                       | See [Maximum artifacts size](../../administration/settings/continuous_integration.md#maximum-artifacts-size). |
-| Artifacts [expiry time](../../ci/yaml/_index.md#artifactsexpire_in)               | 30 days unless otherwise specified                                                                         | See [Default artifacts expiration](../../administration/settings/continuous_integration.md#default-artifacts-expiration). Artifacts created before June 22, 2020 have no expiry. |
-| Scheduled Pipeline Cron                                                          | `*/5 * * * *`                                                                                              | See [Pipeline schedules advanced configuration](../../administration/cicd/_index.md#change-maximum-scheduled-pipeline-frequency). |
-| Maximum jobs in active pipelines                                                 | `500` for Free tier, `1000` for all trial tiers, `20000` for Premium, and `100000` for Ultimate.           | See [Number of jobs in active pipelines](../../administration/instance_limits.md#number-of-jobs-in-active-pipelines). |
-| Maximum CI/CD subscriptions to a project                                         | `2`                                                                                                        | See [Number of CI/CD subscriptions to a project](../../administration/instance_limits.md#number-of-cicd-subscriptions-to-a-project). |
-| Maximum number of pipeline triggers in a project                                 | `25000`                                                                                                    | See [Limit the number of pipeline triggers](../../administration/instance_limits.md#limit-the-number-of-pipeline-triggers). |
-| Maximum pipeline schedules in projects                                           | `10` for Free tier, `50` for all paid tiers                                                                | See [Number of pipeline schedules](../../administration/instance_limits.md#number-of-pipeline-schedules). |
-| Maximum pipelines for each schedule                                                   | `24` for Free tier, `288` for all paid tiers                                                               | See [Limit the number of pipelines created by a pipeline schedule each day](../../administration/instance_limits.md#limit-the-number-of-pipelines-created-by-a-pipeline-schedule-each-day). |
-| Maximum number of schedule rules defined for each security policy project        | Unlimited for all paid tiers                                                                               | See [Number of schedule rules defined for each security policy project](../../administration/instance_limits.md#limit-the-number-of-schedule-rules-defined-for-security-policy-project). |
-| Scheduled job archiving                                                          | 3 months                                                                                                   | Never. Jobs created before June 22, 2020 were archived after September 22, 2020. |
-| Maximum test cases for each [unit test report](../../ci/testing/unit_test_reports.md) | `500000`                                                                                                   | Unlimited.             |
-| Maximum registered runners                                                       | Free tier: `50` for each group and `50`for each project<br/>All paid tiers: `1000` for each group and `1000` for each project | See [Number of registered runners for each scope](../../administration/instance_limits.md#number-of-registered-runners-for-each-scope). |
-| Limit of dotenv variables                                                        | Free tier: `50`<br>Premium tier: `100`<br>Ultimate tier: `150`                                             | See [Limit dotenv variables](../../administration/instance_limits.md#limit-dotenv-variables). |
-| Maximum downstream pipeline trigger rate (for a given project, user, and commit) | `350` each minute                                                                                           | See [Maximum downstream pipeline trigger rate](../../administration/settings/continuous_integration.md#maximum-downstream-pipeline-trigger-rate). |
-
-## GitLab container registry
-
-| Setting                                | GitLab.com                       | Default (self-managed) |
-|:---------------------------------------|:---------------------------------|------------------------|
-| Domain name                            | `registry.gitlab.com`            |                        |
-| IP address                             | `35.227.35.254`                  |                        |
-| CDN domain name                        | `cdn.registry.gitlab-static.net` |                        |
-| CDN IP address                         | `34.149.22.116`                  |                        |
-| Authorization token duration (minutes) | `15`                             | See [increase container registry token duration](../../administration/packages/container_registry.md#increase-token-duration). |
-
-To use the GitLab container registry, Docker clients must have access to:
-
-- The registry endpoint and GitLab.com for authorization.
-- Google Cloud Storage or Google Cloud Content Delivery Network to download images.
-
-GitLab.com is fronted by Cloudflare.
-For incoming connections to GitLab.com, you must allow CIDR blocks of Cloudflare
-([IPv4](https://www.cloudflare.com/ips-v4/) and [IPv6](https://www.cloudflare.com/ips-v6/)).
+For administrator documentation, see [limit RPC concurrency](../../administration/gitaly/concurrency_limiting.md#limit-rpc-concurrency).
 
 ## GitLab Pages
 
@@ -160,9 +166,9 @@ Some settings for [GitLab Pages](../project/pages/_index.md) differ from the
 | Number of custom domains for each GitLab Pages website | 150                    |
 
 The maximum size of your Pages site depends on the maximum artifact size,
-which is part of [GitLab CI/CD](#gitlab-cicd).
+which is part of [GitLab CI/CD](#cicd).
 
-[Rate limits](#gitlabcom-specific-rate-limits) also exist for GitLab Pages.
+[Rate limits](#rate-limits-on-gitlabcom) also exist for GitLab Pages.
 
 ## GitLab.com at scale
 
@@ -214,7 +220,61 @@ Open source error tracking:
 
 - [`gitlab-cookbooks` / `gitlab-sentry` · GitLab](https://gitlab.com/gitlab-cookbooks/gitlab-sentry)
 
-## GitLab.com logging
+## GitLab-hosted runners
+
+You can use GitLab-hosted runners to run your CI/CD jobs on GitLab.com and GitLab Dedicated to seamlessly build, test, and deploy your application on different environments.
+
+For more information, see [GitLab-hosted runners](../../ci/runners/_index.md).
+
+## Hostname list
+
+Add these hostnames when you configure allow-lists in local HTTP(S) proxies,
+or other web-blocking software that governs end-user computers. Pages on
+GitLab.com load content from these hostnames:
+
+- `gitlab.com`
+- `*.gitlab.com`
+- `*.gitlab-static.net`
+- `*.gitlab.io`
+- `*.gitlab.net`
+
+Documentation and Company pages served over `docs.gitlab.com` and `about.gitlab.com`
+also load certain page content directly from common public CDN hostnames.
+
+## Imports
+
+Settings related to importing data into GitLab.
+
+### Default import sources
+
+The [import sources](../project/import/_index.md#supported-import-sources) that are available to you by default depend on
+which GitLab you use:
+
+- GitLab.com: All available import sources are enabled by default.
+- GitLab Self-Managed: No import sources are enabled by default and must be
+  [enabled](../../administration/settings/import_and_export_settings.md#configure-allowed-import-sources).
+
+### Import placeholder user limits
+
+The number of [placeholder users](../project/import/_index.md#placeholder-users) created during an import on GitLab.com is limited for each top-level namespace. The limits
+differ depending on your plan and seat count.
+For more information, see the [table of placeholder user limits for GitLab.com](../project/import/_index.md#placeholder-user-limits).
+
+## IP range
+
+GitLab.com uses the IP ranges `34.74.90.64/28` and `34.74.226.0/24` for traffic from its Web/API
+fleet. This whole range is solely allocated to GitLab. You can expect connections from webhooks or repository mirroring to come
+from those IPs and allow them.
+
+GitLab.com is fronted by Cloudflare. For incoming connections to GitLab.com, you might need to allow CIDR blocks of Cloudflare ([IPv4](https://www.cloudflare.com/ips-v4/) and [IPv6](https://www.cloudflare.com/ips-v6/)).
+
+For outgoing connections from CI/CD runners, we are not providing static IP addresses.
+Most GitLab.com instance runners are deployed into Google Cloud in `us-east1`, except _Linux GPU-enabled_ and _Linux Arm64_, hosted in `us-central1`.
+You can configure any IP-based firewall by looking up
+[IP address ranges or CIDR blocks for GCP](https://cloud.google.com/compute/docs/faq#find_ip_range).
+macOS runners are hosted on AWS in the `us-east-1` region, with runner managers hosted on Google Cloud. To configure IP-based firewall, you must allow both [AWS IP address ranges](https://docs.aws.amazon.com/vpc/latest/userguide/aws-ip-ranges.html) and [Google Cloud](https://cloud.google.com/compute/docs/faq#find_ip_range).
+
+## Logs on GitLab.com
 
 We use [Fluentd](https://gitlab.com/gitlab-com/runbooks/tree/master/logging/doc#fluentd)
 to parse our logs. Fluentd sends our logs to
@@ -236,13 +296,114 @@ and can't be configured on GitLab.com to expire. You can erase job logs
 [manually with the Jobs API](../../api/jobs.md#erase-a-job) or by
 [deleting a pipeline](../../ci/pipelines/_index.md#delete-a-pipeline)
 
-## GitLab.com-specific Gitaly RPC concurrency limits
+## Maximum number of reviewers and assignees
 
-Per-repository Gitaly RPC concurrency and queuing limits are configured for different types of Git operations such as `git clone`. When these limits are exceeded, a `fatal: remote error: GitLab is currently unable to handle this request due to load` message is returned to the client.
+{{< history >}}
 
-For administrator documentation, see [limit RPC concurrency](../../administration/gitaly/concurrency_limiting.md#limit-rpc-concurrency).
+- Maximum assignees [introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/368936) in GitLab 15.6.
+- Maximum reviewers [introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/366485) in GitLab 15.9.
 
-## GitLab.com-specific rate limits
+{{< /history >}}
+
+Merge requests enforce these maximums:
+
+- Maximum assignees: 200
+- Maximum reviewers: 200
+
+## Merge request limits
+
+{{< history >}}
+
+- [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/521970) in GitLab 17.10 [with a flag](../../administration/feature_flags.md) named `merge_requests_diffs_limit`. Disabled by default.
+- [Enabled on GitLab.com](https://gitlab.com/gitlab-org/gitlab/-/issues/521970) in GitLab 17.10.
+
+{{< /history >}}
+
+{{< alert type="flag" >}}
+
+The availability of this feature is controlled by a feature flag.
+For more information, see the history.
+
+{{< /alert >}}
+
+GitLab limits each merge request to 1000 [diff versions](../project/merge_requests/versions.md).
+Merge requests that reach this limit cannot be updated further. Instead,
+close the affected merge request and create a new merge request.
+
+## Password requirements
+
+GitLab.com has the following requirements for passwords on new accounts and password changes:
+
+- Minimum character length 8 characters.
+- Maximum character length 128 characters.
+- All characters are accepted. For example, `~`, `!`, `@`, `#`, `$`, `%`, `^`, `&`, `*`, `()`,
+  `[]`, `_`, `+`,  `=`, and `-`.
+
+## Project and group deletion
+
+Settings related to the deletion of projects and groups.
+
+### Delayed group deletion
+
+{{< details >}}
+
+- Tier: Premium, Ultimate
+- Offering: GitLab.com
+
+{{< /details >}}
+
+After May 08, 2023, all groups have delayed deletion enabled by default.
+
+Groups are permanently deleted after a seven-day delay.
+
+If you are on the Free tier, your groups are immediately deleted, and you will not be able to restore them.
+
+You can [view and restore groups marked for deletion](../group/_index.md#restore-a-group).
+
+### Delayed project deletion
+
+{{< details >}}
+
+- Tier: Premium, Ultimate
+- Offering: GitLab.com
+
+{{< /details >}}
+
+After May 08, 2023, all groups have delayed project deletion enabled by default.
+
+Projects are permanently deleted after a seven-day delay.
+
+If you are on the Free tier, your projects are immediately deleted, and you will not be able to restore them.
+
+You can [view and restore projects marked for deletion](../project/working_with_projects.md#restore-a-project).
+
+### Inactive project deletion
+
+[Inactive project deletion](../../administration/inactive_project_deletion.md) is disabled on GitLab.com.
+
+## Package registry limits
+
+The [maximum file size](../../administration/instance_limits.md#file-size-limits)
+for a package uploaded to the [GitLab package registry](../packages/package_registry/_index.md)
+varies by format:
+
+| Package type           | GitLab.com                         |
+|------------------------|------------------------------------|
+| Conan                  | 5 GB                               |
+| Generic                | 5 GB                               |
+| Helm                   | 5 MB                               |
+| Maven                  | 5 GB                               |
+| npm                    | 5 GB                               |
+| NuGet                  | 5 GB                               |
+| PyPI                   | 5 GB                               |
+| Terraform              | 1 GB                               |
+| Machine learning model | 10 GB (uploads are capped at 5 GB) |
+
+## Puma
+
+GitLab.com uses the default of 60 seconds for [Puma request timeouts](../../administration/operations/puma.md#change-the-worker-timeout).
+
+## Rate limits on GitLab.com
 
 {{< alert type="note" >}}
 
@@ -397,167 +558,6 @@ Projects, groups, and snippets have the
 [Internal visibility](../public_access.md#internal-projects-and-groups)
 setting [disabled on GitLab.com](https://gitlab.com/gitlab-org/gitlab/-/issues/12388).
 
-## GitLab-hosted runners
-
-You can use GitLab-hosted runners to run your CI/CD jobs on GitLab.com and GitLab Dedicated to seamlessly build, test, and deploy your application on different environments.
-
-For more information, see [GitLab-hosted runners](../../ci/runners/_index.md).
-
-## Hostname list
-
-Add these hostnames when you configure allow-lists in local HTTP(S) proxies,
-or other web-blocking software that governs end-user computers. Pages on
-GitLab.com load content from these hostnames:
-
-- `gitlab.com`
-- `*.gitlab.com`
-- `*.gitlab-static.net`
-- `*.gitlab.io`
-- `*.gitlab.net`
-
-Documentation and Company pages served over `docs.gitlab.com` and `about.gitlab.com`
-also load certain page content directly from common public CDN hostnames.
-
-## Imports
-
-Settings related to importing data into GitLab.
-
-### Default import sources
-
-The [import sources](../project/import/_index.md#supported-import-sources) that are available to you by default depend on
-which GitLab you use:
-
-- GitLab.com: All available import sources are enabled by default.
-- GitLab Self-Managed: No import sources are enabled by default and must be
-  [enabled](../../administration/settings/import_and_export_settings.md#configure-allowed-import-sources).
-
-### Import placeholder user limits
-
-The number of [placeholder users](../project/import/_index.md#placeholder-users) created during an import on GitLab.com is limited for each top-level namespace. The limits
-differ depending on your plan and seat count.
-For more information, see the [table of placeholder user limits for GitLab.com](../project/import/_index.md#placeholder-user-limits).
-
-## IP range
-
-GitLab.com uses the IP ranges `34.74.90.64/28` and `34.74.226.0/24` for traffic from its Web/API
-fleet. This whole range is solely allocated to GitLab. You can expect connections from webhooks or repository mirroring to come
-from those IPs and allow them.
-
-GitLab.com is fronted by Cloudflare. For incoming connections to GitLab.com, you might need to allow CIDR blocks of Cloudflare ([IPv4](https://www.cloudflare.com/ips-v4/) and [IPv6](https://www.cloudflare.com/ips-v6/)).
-
-For outgoing connections from CI/CD runners, we are not providing static IP addresses.
-Most GitLab.com instance runners are deployed into Google Cloud in `us-east1`, except _Linux GPU-enabled_ and _Linux Arm64_, hosted in `us-central1`.
-You can configure any IP-based firewall by looking up
-[IP address ranges or CIDR blocks for GCP](https://cloud.google.com/compute/docs/faq#find_ip_range).
-macOS runners are hosted on AWS in the `us-east-1` region, with runner managers hosted on Google Cloud. To configure IP-based firewall, you must allow both [AWS IP address ranges](https://docs.aws.amazon.com/vpc/latest/userguide/aws-ip-ranges.html) and [Google Cloud](https://cloud.google.com/compute/docs/faq#find_ip_range).
-
-## Maximum number of reviewers and assignees
-
-{{< history >}}
-
-- Maximum assignees [introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/368936) in GitLab 15.6.
-- Maximum reviewers [introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/366485) in GitLab 15.9.
-
-{{< /history >}}
-
-Merge requests enforce these maximums:
-
-- Maximum assignees: 200
-- Maximum reviewers: 200
-
-## Merge request limits
-
-{{< history >}}
-
-- [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/521970) in GitLab 17.10 [with a flag](../../administration/feature_flags.md) named `merge_requests_diffs_limit`. Disabled by default.
-- [Enabled on GitLab.com](https://gitlab.com/gitlab-org/gitlab/-/issues/521970) in GitLab 17.10.
-
-{{< /history >}}
-
-{{< alert type="flag" >}}
-
-The availability of this feature is controlled by a feature flag.
-For more information, see the history.
-
-{{< /alert >}}
-
-GitLab limits each merge request to 1000 [diff versions](../project/merge_requests/versions.md).
-Merge requests that reach this limit cannot be updated further. Instead,
-close the affected merge request and create a new merge request.
-
-## Password requirements
-
-GitLab.com has the following requirements for passwords on new accounts and password changes:
-
-- Minimum character length 8 characters.
-- Maximum character length 128 characters.
-- All characters are accepted. For example, `~`, `!`, `@`, `#`, `$`, `%`, `^`, `&`, `*`, `()`,
-  `[]`, `_`, `+`,  `=`, and `-`.
-
-## Project and group deletion
-
-Settings related to the deletion of projects and groups.
-
-### Delayed group deletion
-
-{{< details >}}
-
-- Tier: Premium, Ultimate
-- Offering: GitLab.com
-
-{{< /details >}}
-
-After May 08, 2023, all groups have delayed deletion enabled by default.
-
-Groups are permanently deleted after a seven-day delay.
-
-If you are on the Free tier, your groups are immediately deleted, and you will not be able to restore them.
-
-You can [view and restore groups marked for deletion](../group/_index.md#restore-a-group).
-
-### Delayed project deletion
-
-{{< details >}}
-
-- Tier: Premium, Ultimate
-- Offering: GitLab.com
-
-{{< /details >}}
-
-After May 08, 2023, all groups have delayed project deletion enabled by default.
-
-Projects are permanently deleted after a seven-day delay.
-
-If you are on the Free tier, your projects are immediately deleted, and you will not be able to restore them.
-
-You can [view and restore projects marked for deletion](../project/working_with_projects.md#restore-a-project).
-
-### Inactive project deletion
-
-[Inactive project deletion](../../administration/inactive_project_deletion.md) is disabled on GitLab.com.
-
-## Package registry limits
-
-The [maximum file size](../../administration/instance_limits.md#file-size-limits)
-for a package uploaded to the [GitLab package registry](../packages/package_registry/_index.md)
-varies by format:
-
-| Package type           | GitLab.com                         |
-|------------------------|------------------------------------|
-| Conan                  | 5 GB                               |
-| Generic                | 5 GB                               |
-| Helm                   | 5 MB                               |
-| Maven                  | 5 GB                               |
-| npm                    | 5 GB                               |
-| NuGet                  | 5 GB                               |
-| PyPI                   | 5 GB                               |
-| Terraform              | 1 GB                               |
-| Machine learning model | 10 GB (uploads are capped at 5 GB) |
-
-## Puma
-
-GitLab.com uses the default of 60 seconds for [Puma request timeouts](../../administration/operations/puma.md#change-the-worker-timeout).
-
 ## Sidekiq
 
 GitLab.com runs [Sidekiq](https://sidekiq.org) as an [external process](../../administration/sidekiq/_index.md)
diff --git a/doc/user/gitlab_duo/gateway.md b/doc/user/gitlab_duo/gateway.md
index c8754aea7f5..a04d5b612c9 100644
--- a/doc/user/gitlab_duo/gateway.md
+++ b/doc/user/gitlab_duo/gateway.md
@@ -18,7 +18,7 @@ This page describes where the AI gateway is deployed, and answers questions abou
 
 For self-managed and Dedicated customers, the ability to choose the region is planned for future implementation. Currently, the process for region selection is managed internally by GitLab.
 
-Runway, is currently not available to external customers. GitLab is working on expanding support to include self-managed instances in the future (Epic: [Expand Platform Engineering to more runtimes](https://gitlab.com/groups/gitlab-com/gl-infra/-/epics/1330)).
+Runway, is currently not available to external customers. GitLab is working on expanding support to include GitLab Self-Managed instances in the future (Epic: [Expand Platform Engineering to more runtimes](https://gitlab.com/groups/gitlab-com/gl-infra/-/epics/1330)).
 
 [View the available regions](https://gitlab-com.gitlab.io/gl-infra/platform/runway/runwayctl/manifest.schema.html#spec_regions).
 
diff --git a/doc/user/gitlab_duo_chat/examples.md b/doc/user/gitlab_duo_chat/examples.md
index 0e92e268fe3..0f19f81caca 100644
--- a/doc/user/gitlab_duo_chat/examples.md
+++ b/doc/user/gitlab_duo_chat/examples.md
@@ -55,7 +55,7 @@ GitLab Duo Chat uses the GitLab documentation from the [GitLab repository](https
 To keep Chat up to date with the documentation, its knowledge base is updated daily.
 
 - On GitLab.com, the most recent version of the documentation is used.
-- On Self-managed and GitLab Dedicated, the documentation for the version of the instance is used.
+- On GitLab Self-Managed and GitLab Dedicated, the documentation for the version of the instance is used.
 
 ## Ask about a specific issue
 
diff --git a/doc/user/group/access_and_permissions.md b/doc/user/group/access_and_permissions.md
index 2f50490e41a..88283c5a335 100644
--- a/doc/user/group/access_and_permissions.md
+++ b/doc/user/group/access_and_permissions.md
@@ -116,7 +116,7 @@ Keep in mind that restricting group access by IP address has the following impli
   push, merge, issue, or comment events.
 - IP access restrictions do not stop users from using the [reply by email feature](../../administration/reply_by_email.md) to create or edit comments on issues or merge requests.
 - IP access restrictions for Git operations through SSH are supported on GitLab SaaS.
-  IP access restrictions applied to self-managed instances are possible with [`gitlab-sshd`](../../administration/operations/gitlab_sshd.md)
+  IP access restrictions applied to GitLab Self-Managed instances are possible with [`gitlab-sshd`](../../administration/operations/gitlab_sshd.md)
   with [PROXY protocol](../../administration/operations/gitlab_sshd.md#proxy-protocol-support) enabled.
 - IP restriction is not applicable to shared resources belonging to a group. Any shared resource is accessible to a user even if that user is not able to access the group.
 - While IP restrictions apply to public projects, they aren't a complete firewall and cached files for a project may still be accessible to users not in the IP block
diff --git a/doc/user/group/epics/img/related_epic_block_v14_9.png b/doc/user/group/epics/img/related_epic_block_v14_9.png
deleted file mode 100644
index 20fdce0151d..00000000000
Binary files a/doc/user/group/epics/img/related_epic_block_v14_9.png and /dev/null differ
diff --git a/doc/user/group/epics/img/related_epics_add_v14_9.png b/doc/user/group/epics/img/related_epics_add_v14_9.png
deleted file mode 100644
index 112b900f2e3..00000000000
Binary files a/doc/user/group/epics/img/related_epics_add_v14_9.png and /dev/null differ
diff --git a/doc/user/group/epics/img/related_epics_remove_v14_9.png b/doc/user/group/epics/img/related_epics_remove_v14_9.png
deleted file mode 100644
index 2cdded5965f..00000000000
Binary files a/doc/user/group/epics/img/related_epics_remove_v14_9.png and /dev/null differ
diff --git a/doc/user/group/epics/linked_epics.md b/doc/user/group/epics/linked_epics.md
index 559fefe4ccf..cd71b05759d 100644
--- a/doc/user/group/epics/linked_epics.md
+++ b/doc/user/group/epics/linked_epics.md
@@ -130,8 +130,6 @@ To link one epic to another:
    - Enter `&`, followed by a word from the epic's title. For example, `&Deliver`.
    - Paste in the epic's full URL.
 
-   ![Adding a related epic](img/related_epics_add_v14_9.png)
-
    Epics of the same group can be specified just by the reference number.
    Epics from a different group require additional information like the
    group name. For example:
@@ -145,8 +143,6 @@ To link one epic to another:
 
 The linked epics are then displayed on the epic grouped by relationship.
 
-![Related epic block](img/related_epic_block_v14_9.png)
-
 ## Remove a linked epic
 
 {{< history >}}
@@ -165,8 +161,6 @@ To remove a linked epic:
 
 The relationship is removed from both epics.
 
-![Removing a related epic](img/related_epics_remove_v14_9.png)
-
 ## Blocking epics
 
 When you [add a linked epic](#add-a-linked-epic), you can show that it **blocks** or
diff --git a/doc/user/group/import/direct_transfer_migrations.md b/doc/user/group/import/direct_transfer_migrations.md
index 2244b800fe7..c5d84046ab1 100644
--- a/doc/user/group/import/direct_transfer_migrations.md
+++ b/doc/user/group/import/direct_transfer_migrations.md
@@ -130,7 +130,7 @@ There is a [known issue](_index.md#known-issues) affecting the mapping of shared
 
 To ensure GitLab maps users and their contributions correctly between the source and destination instances:
 
-1. Create the required users on the destination GitLab instance. You can create users with the API only on self-managed instances because it requires
+1. Create the required users on the destination GitLab instance. You can create users with the API only on GitLab Self-Managed instances because it requires
    administrator access. When migrating to GitLab.com or GitLab Self-Managed you can:
    - Create users manually.
    - Set up or use your existing [SAML SSO provider](../saml_sso/_index.md) and leverage user synchronization of SAML SSO groups supported through
diff --git a/doc/user/group/reporting/git_abuse_rate_limit.md b/doc/user/group/reporting/git_abuse_rate_limit.md
index 1589e96ea01..4f5bb5fc267 100644
--- a/doc/user/group/reporting/git_abuse_rate_limit.md
+++ b/doc/user/group/reporting/git_abuse_rate_limit.md
@@ -25,7 +25,7 @@ For more information, see the history.
 
 {{< /alert >}}
 
-This is the group-level documentation. For self-managed instances, see the [administration documentation](../../../administration/reporting/git_abuse_rate_limit.md).
+This is the group-level documentation. For GitLab Self-Managed instances, see the [administration documentation](../../../administration/reporting/git_abuse_rate_limit.md).
 
 Git abuse rate limiting is a feature to automatically ban users who download, clone, pull, fetch, or fork more than a specified number of repositories of a group in a given time frame. Banned users cannot access the top-level group or any of its non-public subgroups through HTTP or SSH. The rate limit also applies to users who authenticate with [personal](../../profile/personal_access_tokens.md) or [group access tokens](../settings/group_access_tokens.md), as well as [CI/CD job tokens](../../../ci/jobs/ci_job_token.md). Access to unrelated groups is unaffected.
 
diff --git a/doc/user/group/saml_sso/_index.md b/doc/user/group/saml_sso/_index.md
index fa9dc2f211d..4e6acf834f1 100644
--- a/doc/user/group/saml_sso/_index.md
+++ b/doc/user/group/saml_sso/_index.md
@@ -262,7 +262,7 @@ After you set up your identity provider to work with GitLab, you must configure
    1. The role to assign to
       [users who are not members of a mapped SAML group](group_sync.md#automatic-member-removal)
       when SAML Group Links is configured for the group.
-1. For groups on self-managed instances: in the **Default membership role** field,
+1. For groups on GitLab Self-Managed instances: in the **Default membership role** field,
    select the role to assign to new users.
    The default role is **Guest**. That role becomes the starting role of all users
    added to the group:
diff --git a/doc/user/group/settings/group_access_tokens.md b/doc/user/group/settings/group_access_tokens.md
index 6f6ba8e2d21..ea629e62932 100644
--- a/doc/user/group/settings/group_access_tokens.md
+++ b/doc/user/group/settings/group_access_tokens.md
@@ -28,7 +28,7 @@ You can use a group access token to authenticate:
 
 > On GitLab.com, you can use group access tokens if you have the Premium or Ultimate license tier. Group access tokens are not available with a [trial license](https://about.gitlab.com/free-trial/).
 >
-> On GitLab Dedicated and self-managed instances, you can use group access tokens with any license tier. If you have the Free tier:
+> On GitLab Dedicated and GitLab Self-Managed instances, you can use group access tokens with any license tier. If you have the Free tier:
 >
 > - Review your security and compliance policies around [user self-enrollment](../../../administration/settings/sign_up_restrictions.md#disable-new-sign-ups).
 > - Consider [restricting the creation of group access tokens](#restrict-the-creation-of-group-access-tokens) to lower potential abuse.
@@ -37,7 +37,7 @@ Group access tokens are similar to [project access tokens](../../project/setting
 and [personal access tokens](../../profile/personal_access_tokens.md), except they are
 associated with a group rather than a project or user.
 
-In self-managed instances, group access tokens are subject to the same [maximum lifetime limits](../../../administration/settings/account_and_limit_settings.md#limit-the-lifetime-of-access-tokens) as personal access tokens if the limit is set.
+In GitLab Self-Managed instances, group access tokens are subject to the same [maximum lifetime limits](../../../administration/settings/account_and_limit_settings.md#limit-the-lifetime-of-access-tokens) as personal access tokens if the limit is set.
 
 You cannot use group access tokens to create other group, project, or personal access tokens.
 
@@ -82,7 +82,7 @@ To create a group access token:
    - If you do not enter an expiry date, the expiry date is automatically set to 365 days later than the current date.
    - By default, this date can be a maximum of 365 days later than the current date. In GitLab 17.6 or later, you can [extend this limit to 400 days](https://gitlab.com/gitlab-org/gitlab/-/issues/461901).
 
-   - An instance-wide [maximum lifetime](../../../administration/settings/account_and_limit_settings.md#limit-the-lifetime-of-access-tokens) setting can limit the maximum allowable lifetime in self-managed instances.
+   - An instance-wide [maximum lifetime](../../../administration/settings/account_and_limit_settings.md#limit-the-lifetime-of-access-tokens) setting can limit the maximum allowable lifetime in GitLab Self-Managed instances.
 1. Select a role for the token.
 1. Select the [desired scopes](#scopes-for-a-group-access-token).
 1. Select **Create group access token**.
diff --git a/doc/user/infrastructure/clusters/migrate_to_gitlab_agent.md b/doc/user/infrastructure/clusters/migrate_to_gitlab_agent.md
index 66b3f5f4ea3..fae2eb99e1d 100644
--- a/doc/user/infrastructure/clusters/migrate_to_gitlab_agent.md
+++ b/doc/user/infrastructure/clusters/migrate_to_gitlab_agent.md
@@ -23,7 +23,7 @@ The certificate-based integration is
 in GitLab 14.5. The sunsetting plans are described:
 
 - for [GitLab.com customers](../../../update/deprecations.md#gitlabcom-certificate-based-integration-with-kubernetes).
-- for [Self-managed customers](../../../update/deprecations.md#gitlab-self-managed-certificate-based-integration-with-kubernetes).
+- for [GitLab Self-Managed customers](../../../update/deprecations.md#gitlab-self-managed-certificate-based-integration-with-kubernetes).
 
 If you are using the certificate-based integration, you should move to another workflow as soon as possible.
 
diff --git a/doc/user/packages/container_registry/authenticate_with_container_registry.md b/doc/user/packages/container_registry/authenticate_with_container_registry.md
index eb0075ae90f..aff2357f8d0 100644
--- a/doc/user/packages/container_registry/authenticate_with_container_registry.md
+++ b/doc/user/packages/container_registry/authenticate_with_container_registry.md
@@ -43,7 +43,7 @@ echo "$TOKEN" | docker login registry.example.com -u <username> --password-stdin
 After authentication, the client caches the credentials. Later operations make authorization
 requests that return JWT tokens, authorized to do only the specified operation.
 Tokens remain valid for [5 minutes by default](../../../administration/packages/container_registry.md#increase-token-duration),
-and [15 minutes on GitLab.com](../../gitlab_com/_index.md#gitlab-container-registry).
+and [15 minutes on GitLab.com](../../gitlab_com/_index.md#container-registry).
 
 ## Use GitLab CI/CD to authenticate
 
diff --git a/doc/user/packages/container_registry/delete_container_registry_images.md b/doc/user/packages/container_registry/delete_container_registry_images.md
index 24eeaea7da0..47aaa2f301b 100644
--- a/doc/user/packages/container_registry/delete_container_registry_images.md
+++ b/doc/user/packages/container_registry/delete_container_registry_images.md
@@ -30,7 +30,7 @@ a deleted container image, you must rebuild and re-upload it.
 
 ## Garbage collection
 
-Deleting a container image on self-managed instances doesn't free up storage space, it only marks the image
+Deleting a container image on GitLab Self-Managed instances doesn't free up storage space, it only marks the image
 as eligible for deletion. To actually delete unreferenced container images and recover storage space, GitLab Self-Managed instance administrators
 must run [garbage collection](../../../administration/packages/container_registry.md#container-registry-garbage-collection).
 
diff --git a/doc/user/packages/container_registry/protected_container_tags.md b/doc/user/packages/container_registry/protected_container_tags.md
index 01a52df364b..d67c25a6e1d 100644
--- a/doc/user/packages/container_registry/protected_container_tags.md
+++ b/doc/user/packages/container_registry/protected_container_tags.md
@@ -102,7 +102,7 @@ The protection rule is deleted and matching tags are no longer protected.
 Rule changes rely on JWT tokens to propagate between services. As a result, changes to protection rules and user access roles might take effect only after current JWT tokens expire. The delay equals the [configured token duration](../../../administration/packages/container_registry.md#increase-token-duration):
 
 - Default: 5 minutes
-- GitLab.com: [15 minutes](../../gitlab_com/_index.md#gitlab-container-registry)
+- GitLab.com: [15 minutes](../../gitlab_com/_index.md#container-registry)
 
 Most container registry clients (including Docker, the GitLab UI, and the API) request a new token for each operation, but custom clients might retain a token for its full validity period.
 
diff --git a/doc/user/packages/container_registry/reduce_container_registry_storage.md b/doc/user/packages/container_registry/reduce_container_registry_storage.md
index 7abe5039f40..a01f04bc4ca 100644
--- a/doc/user/packages/container_registry/reduce_container_registry_storage.md
+++ b/doc/user/packages/container_registry/reduce_container_registry_storage.md
@@ -41,7 +41,7 @@ View storage usage data for your container registry repositories.
 
 Prerequisites:
 
-- For self-managed instances, an administrator must [enable the container registry metadata database](../../../administration/packages/container_registry_metadata_database.md).
+- For GitLab Self-Managed instances, an administrator must [enable the container registry metadata database](../../../administration/packages/container_registry_metadata_database.md).
 - You must have at least the Maintainer role for the project or the Owner role for the namespace.
 
 To view storage usage for a project:
@@ -61,7 +61,7 @@ You can also use:
 
 Prerequisites:
 
-- For self-managed instances, an administrator must [enable the container registry metadata database](../../../administration/packages/container_registry_metadata_database.md).
+- For GitLab Self-Managed instances, an administrator must [enable the container registry metadata database](../../../administration/packages/container_registry_metadata_database.md).
 - You must have the Owner role for the group.
 
 To view storage usage for a group:
@@ -90,7 +90,7 @@ Storage data updates occur:
 
 {{< alert type="note" >}}
 
-For self-managed instances, storage data becomes available after an administrator enables the metadata database.
+For GitLab Self-Managed instances, storage data becomes available after an administrator enables the metadata database.
 On GitLab.com, the metadata database is enabled by default.
 
 {{< /alert >}}
@@ -349,7 +349,7 @@ You can use the following application settings to prevent server resource starva
   during execution of policies. Cached timestamps are stored in [Redis](../../../development/architecture.md#redis).
   Enabled by default.
 
-For self-managed instances, those settings can be updated in the [Rails console](../../../administration/operations/rails_console.md#starting-a-rails-console-session):
+For GitLab Self-Managed instances, those settings can be updated in the [Rails console](../../../administration/operations/rails_console.md#starting-a-rails-console-session):
 
 ```ruby
 ApplicationSetting.last.update(container_registry_expiration_policies_worker_capacity: 3)
diff --git a/doc/user/packages/terraform_module_registry/_index.md b/doc/user/packages/terraform_module_registry/_index.md
index f1144f9cf89..90dfb37ad79 100644
--- a/doc/user/packages/terraform_module_registry/_index.md
+++ b/doc/user/packages/terraform_module_registry/_index.md
@@ -319,7 +319,7 @@ The package is permanently deleted.
 
 The Terraform Module Registry is automatically enabled.
 
-For self-managed instances, a GitLab administrator can
+For GitLab Self-Managed instances, a GitLab administrator can
 [disable](../../../administration/packages/_index.md) **Packages and registries**,
 which removes this menu item from the sidebar.
 
diff --git a/doc/user/profile/notifications.md b/doc/user/profile/notifications.md
index 4020479a6fa..97449682647 100644
--- a/doc/user/profile/notifications.md
+++ b/doc/user/profile/notifications.md
@@ -301,7 +301,7 @@ To always receive notifications on your own issues, merge requests, and so on, t
 
 {{< alert type="note" >}}
 
-This feature is enabled by default for self-managed instances. Administrators may disable this feature
+This feature is enabled by default for GitLab Self-Managed instances. Administrators may disable this feature
 through the [Sign-in restrictions](../../administration/settings/sign_in_restrictions.md#email-notification-for-unknown-sign-ins) section of the UI.
 The feature is always enabled on GitLab.com.
 
diff --git a/doc/user/profile/service_accounts.md b/doc/user/profile/service_accounts.md
index 25977498758..91830ce01c3 100644
--- a/doc/user/profile/service_accounts.md
+++ b/doc/user/profile/service_accounts.md
@@ -35,7 +35,7 @@ token for [Git operations](personal_access_tokens.md#clone-repository-using-pers
 
 [Rate limits](../../security/rate_limits.md) apply to service accounts:
 
-- On GitLab.com, there are [GitLab.com-specific rate limits](../gitlab_com/_index.md#gitlabcom-specific-rate-limits).
+- On GitLab.com, there are [GitLab.com-specific rate limits](../gitlab_com/_index.md#rate-limits-on-gitlabcom).
 - On GitLab Self-Managed and GitLab Dedicated, there are both:
   - [Configurable rate limits](../../security/rate_limits.md#configurable-limits).
   - [Non-configurable rate limits](../../security/rate_limits.md#non-configurable-limits).
diff --git a/doc/user/profile/user_passwords.md b/doc/user/profile/user_passwords.md
index af02279ac8a..0a856db23dc 100644
--- a/doc/user/profile/user_passwords.md
+++ b/doc/user/profile/user_passwords.md
@@ -84,7 +84,7 @@ By default GitLab enforces the following password requirements:
   see [the settings for GitLab.com](../gitlab_com/_index.md#password-requirements).
 - Disallowing [weak passwords](#block-weak-passwords).
 
-Self-managed installations can configure the following additional password requirements:
+GitLab Self-Managed installations can configure the following additional password requirements:
 
 - [Password minimum and maximum length limits](../../security/password_length_limits.md).
 - [Password complexity requirements](../../administration/settings/sign_up_restrictions.md#password-complexity-requirements).
diff --git a/doc/user/project/import/_index.md b/doc/user/project/import/_index.md
index d454daa8d0c..fb62373b5d8 100644
--- a/doc/user/project/import/_index.md
+++ b/doc/user/project/import/_index.md
@@ -709,7 +709,7 @@ Check the import status:
 
 Search logs for relevant information:
 
-For self-managed instances:
+For GitLab Self-Managed instances:
 
 1. Check the [Sidekiq logs](../../../administration/logs/_index.md#sidekiqlog) and [`exceptions_json` logs](../../../administration/logs/_index.md#exceptions_jsonlog).
 1. Search for entries related to `RepositoryImportWorker` and the correlation ID from [Check import status](#check-import-status).
@@ -731,7 +731,7 @@ For GitLab.com (GitLab team members only):
    json.class: "RepositoryImportWorker" AND json.meta.project: "<project.full_path>"
    ```
 
-1. Look for the same fields as mentioned for self-managed instances.
+1. Look for the same fields as mentioned for GitLab Self-Managed instances.
 
 #### Identify common issues
 
diff --git a/doc/user/project/import/troubleshooting_github_import.md b/doc/user/project/import/troubleshooting_github_import.md
index 625b794f449..146e161f7b6 100644
--- a/doc/user/project/import/troubleshooting_github_import.md
+++ b/doc/user/project/import/troubleshooting_github_import.md
@@ -88,6 +88,6 @@ required to perform the import.
 
 ## GitLab instance cannot connect to GitHub
 
-Self-managed instances that run GitLab 15.10 or earlier, and are behind proxies, cannot resolve DNS for `github.com` or `api.github.com`.
+GitLab Self-Managed instances that run GitLab 15.10 or earlier, and are behind proxies, cannot resolve DNS for `github.com` or `api.github.com`.
 The GitLab instance fails to connect to GitHub during the import and you must add `github.com` and `api.github.com`
 entries in the [allowlist for local requests](../../../security/webhooks.md#allow-outbound-requests-to-certain-ip-addresses-and-domains).
diff --git a/doc/user/project/issues/csv_import.md b/doc/user/project/issues/csv_import.md
index 706659dbb64..c817905c69f 100644
--- a/doc/user/project/issues/csv_import.md
+++ b/doc/user/project/issues/csv_import.md
@@ -96,5 +96,5 @@ An issue with milestone,"My milestone is created",,v1.0
 
 The limit depends on how your GitLab instance is hosted:
 
-- Self-managed: Set by the configuration value of `Max Attachment Size` for the GitLab instance.
+- GitLab Self-Managed: Set by the configuration value of `Max Attachment Size` for the GitLab instance.
 - GitLab SaaS: On GitLab.com, it's set to 10 MB.
diff --git a/doc/user/project/issues/design_management.md b/doc/user/project/issues/design_management.md
index 783982b2c2f..c54a0e36ed0 100644
--- a/doc/user/project/issues/design_management.md
+++ b/doc/user/project/issues/design_management.md
@@ -27,9 +27,9 @@ For a video overview, see [Design Management](https://www.youtube.com/watch?v=CC
 
 - [Git Large File Storage (LFS)](../../../topics/git/lfs/_index.md) must be enabled:
   - On GitLab.com, LFS is already enabled.
-  - On self-managed instances, a GitLab administrator must
+  - On GitLab Self-Managed instances, a GitLab administrator must
     [enable LFS globally](../../../administration/lfs/_index.md).
-  - On both GitLab.com and self-managed instances, LFS must be
+  - On both GitLab.com and GitLab Self-Managed instances, LFS must be
     [enabled for the project itself](../settings/_index.md#configure-project-features-and-permissions).
     If enabled globally, LFS is enabled by default for all projects. If you have
     disabled it for your project, you must enable it again.
diff --git a/doc/user/project/pages/custom_domains_ssl_tls_certification/_index.md b/doc/user/project/pages/custom_domains_ssl_tls_certification/_index.md
index ed72e2dcac9..fce431a5557 100644
--- a/doc/user/project/pages/custom_domains_ssl_tls_certification/_index.md
+++ b/doc/user/project/pages/custom_domains_ssl_tls_certification/_index.md
@@ -83,7 +83,7 @@ according to the type of domain you want to use with your Pages site:
 - [For subdomains](#for-subdomains), `subdomain.example.com`.
 - [For both](#for-both-root-and-subdomains).
 
-You can [configure IPv6 on self-managed instances](../../../../administration/pages/_index.md#advanced-configuration),
+You can [configure IPv6 on GitLab Self-Managed instances](../../../../administration/pages/_index.md#advanced-configuration),
 but IPv6 is not currently configured for Pages on GitLab.com.
 Follow [this issue](https://gitlab.com/gitlab-org/gitlab/-/issues/214718) for details.
 
diff --git a/doc/user/project/pages/custom_domains_ssl_tls_certification/lets_encrypt_integration.md b/doc/user/project/pages/custom_domains_ssl_tls_certification/lets_encrypt_integration.md
index bc028e9fa6e..dca192a7a4a 100644
--- a/doc/user/project/pages/custom_domains_ssl_tls_certification/lets_encrypt_integration.md
+++ b/doc/user/project/pages/custom_domains_ssl_tls_certification/lets_encrypt_integration.md
@@ -24,7 +24,7 @@ open source Certificate Authority.
 {{< alert type="warning" >}}
 
 This feature covers only certificates for **custom domains**, not the wildcard certificate required to run
-[Pages daemon](../../../../administration/pages/_index.md) (Self-managed, Free, Premium, and Ultimate only). Wildcard
+[Pages daemon](../../../../administration/pages/_index.md) (GitLab Self-Managed, Free, Premium, and Ultimate only). Wildcard
 certificate generation is tracked in [this issue](https://gitlab.com/gitlab-org/omnibus-gitlab/-/issues/3342).
 
 {{< /alert >}}
diff --git a/doc/user/project/time_tracking.md b/doc/user/project/time_tracking.md
index c4bcc457458..b44af85aaa5 100644
--- a/doc/user/project/time_tracking.md
+++ b/doc/user/project/time_tracking.md
@@ -226,7 +226,7 @@ If you find a bug, let us know in the [feedback issue](https://gitlab.com/gitlab
 To view the global time tracking report:
 
 1. In your browser, enter the global report's URL:
-   - For self-managed, add `/-/timelogs` to your base URL. For example, `https://gitlab.example.com/-/timelogs`.
+   - For GitLab Self-Managed, add `/-/timelogs` to your base URL. For example, `https://gitlab.example.com/-/timelogs`.
    - For GitLab.com, go to <https://gitlab.com/-/timelogs>.
 1. Optional. To filter by a specific user, enter their username without the `@` symbol.
 1. Select start and end dates.
diff --git a/doc/user/project/working_with_projects.md b/doc/user/project/working_with_projects.md
index 9938cebf33d..cedfadf6e6a 100644
--- a/doc/user/project/working_with_projects.md
+++ b/doc/user/project/working_with_projects.md
@@ -300,7 +300,7 @@ Prerequisites:
 
 Projects in a group (not a personal namespace) can be deleted after a delay period.
 
-On self-managed instances, group administrators can define a deletion delay period of between 1 and 90 days.
+On GitLab Self-Managed instances, group administrators can define a deletion delay period of between 1 and 90 days.
 On SaaS, there is a non-adjustable default retention period of seven days.
 
 You can [view projects that are pending deletion](#view-projects-pending-deletion),
diff --git a/doc/user/work_items/_index.md b/doc/user/work_items/_index.md
index b9b70cc0986..2e92a7f9de5 100644
--- a/doc/user/work_items/_index.md
+++ b/doc/user/work_items/_index.md
@@ -2,6 +2,7 @@
 stage: Plan
 group: Project Management
 info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
+description: "Organize your team's work with GitLab work items. Track tasks, epics, issues, and objectives in a unified view to connect strategy with implementation and monitor progress."
 title: Work items
 ---
 
diff --git a/doc/user/work_items/linked_items.md b/doc/user/work_items/linked_items.md
new file mode 100644
index 00000000000..059730292bf
--- /dev/null
+++ b/doc/user/work_items/linked_items.md
@@ -0,0 +1,159 @@
+---
+stage: Plan
+group: Product Planning
+info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
+description: "Connect and track relationships between work items in GitLab. Manage dependencies, link strategic goals to execution, and coordinate cross-functional initiatives."
+title: Linked items
+---
+
+{{< details >}}
+
+- Tier: Free, Premium, Ultimate
+- Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
+
+{{< /details >}}
+
+Linked items create bi-directional relationships between work items, helping you visualize and manage dependencies across your entire workflow.
+
+With linked items, you can connect various work items including issues, epics, tasks, and objectives to show relationships between them.
+
+These connections help everyone understand how individual pieces of work relate to each other and to larger strategic initiatives.
+
+## Ways to use linked items
+
+You can use linked items to solve several planning and coordination challenges.
+
+The following examples show how linked items help teams work together more effectively.
+
+### Track dependencies
+
+{{< details >}}
+
+- Tier: Premium, Ultimate
+
+{{< /details >}}
+
+Clearly identify work that blocks or is blocked by other items.
+
+When you link items with a blocking relationship:
+
+- Teams can immediately see what other work they depend on.
+- Status updates flow automatically between linked items.
+- Warnings appear when closing items that have open blockers.
+- Teams can avoid delays by addressing dependencies proactively.
+
+This visibility helps coordinate work across teams and reduces bottlenecks.
+
+### Connect strategic goals with implementation details
+
+Use linked items to connect high-level planning with day-to-day execution.
+
+When you link strategic objectives to tactical tasks:
+
+- Teams understand how their work contributes to larger goals.
+- Stakeholders can trace progress from strategy to implementation.
+- Everyone gains visibility into how individual efforts support the broader vision.
+- Changes in strategy can be quickly traced to affected implementation work.
+
+This connection between levels creates alignment and purpose across the organization.
+
+### Organize cross-functional initiatives
+
+Link related work across different teams and projects to coordinate complex initiatives.
+
+When you use linked items for cross-functional work:
+
+- Each team can work in their own area while maintaining connections to related work.
+- Dependencies between specialized teams become visible.
+- Status updates flow automatically between related items.
+- Teams can coordinate their efforts without constant meetings.
+
+This coordination helps break down silos and ensures all aspects of the initiative stay in sync.
+
+## Types of linked items
+
+GitLab supports linking various types of work items:
+
+- [Issues](../project/issues/related_issues.md) help you track tasks, bugs, and features and can be
+  linked to show dependencies between discrete pieces of work.
+- [Epics](../group/epics/linked_epics.md) let you manage cross-functional initiatives, show
+  dependencies, and connect strategic planning to execution across multiple teams or projects.
+  Available in the Ultimate tier.
+- [Tasks](../tasks.md#linked-items-in-tasks) provide lightweight tracking for smaller units of work
+  and can be linked to other items to show relationships or dependencies in a project.
+- [Objectives and key results](../okrs.md#linked-items-in-okrs) help connect strategic goals with
+  execution details, ensuring that day-to-day work remains aligned with higher-level organizational
+  priorities.
+- [Incidents](../../operations/incident_management/incidents.md) represent service disruptions or
+  outages that need urgent restoration and can be linked to related work items for better tracking
+  of operational issues and their impact on planned work.
+- [Test cases](../../ci/test_cases/_index.md) integrate test planning directly into your GitLab
+  workflows, letting teams document testing scenarios and track requirements in the same platform
+  where they manage code. Available in the Ultimate tier.
+
+## Relationship types
+
+When linking items, you can specify the type of relationship:
+
+- **Relates to**: Indicates a general relationship between items.
+- **Blocks**: Shows that an item prevents progress on another item.
+- **Is blocked by**: Shows that an item cannot proceed until another item is resolved.
+
+## Common tasks with linked items
+
+Learn how to create and manage relationships between your work items with these common procedures.
+
+### Add a linked item
+
+Prerequisites:
+
+- You must have at least the Guest role for the projects or groups of both items.
+
+The general process for adding linked items is similar across all work item types:
+
+1. Go to the work item you want to modify.
+1. At the bottom of the description, find the **Linked items** section of the work item.
+1. Select **Add**.
+1. Select the relationship type: **relates to**, **blocks**, or **is blocked by**.
+1. Enter the reference for the item to link. You can:
+   - Enter `#` or `&` (depending on item type) followed by the item's number.
+   - Enter text to search for the item by title.
+   - Paste the full URL of the item.
+1. Select **Add** to confirm.
+
+Alternatively, you can add linked items using [quick actions](../project/quick_actions.md):
+
+- `/relate`
+- `/blocks`
+- `/blocked_by`
+
+For detailed instructions specific to each work item type, see the relevant documentation:
+
+- [Linked issues](../project/issues/related_issues.md#add-a-linked-issue)
+- [Linked epics](../group/epics/linked_epics.md#add-a-linked-epic)
+- [Linked tasks](../tasks.md#linked-items-in-tasks)
+- [Linked OKRs](../okrs.md#linked-items-in-okrs)
+
+### Remove a linked item
+
+Prerequisites:
+
+- You must have at least the Guest role for the projects or groups of both items.
+
+To remove a linked item:
+
+1. Go to the work item you want to modify.
+1. At the bottom of the description, find the **Linked items** section of the work item.
+1. For each linked item, select **Remove** ({{< icon name="close" >}}).
+
+The bi-directional relationship is removed from both items.
+
+Alternatively, you can remove a linked item using the `/unlink` [quick action](../project/quick_actions.md).
+
+## Related topics
+
+- [Work items](../work_items/_index.md)
+- [Issues](../project/issues/_index.md)
+- [Epics](../group/epics/_index.md)
+- [Tasks](../tasks.md)
+- [Objectives and key results](../okrs.md)
diff --git a/locale/gitlab.pot b/locale/gitlab.pot
index 49780c8919a..fd4e07cfa20 100644
--- a/locale/gitlab.pot
+++ b/locale/gitlab.pot
@@ -3143,7 +3143,7 @@ msgstr ""
 msgid "AccessTokens|Scopes set the permission levels granted to the token. %{linkStart}Learn more%{linkEnd}."
 msgstr ""
 
-msgid "AccessTokens|Search or filter access tokens..."
+msgid "AccessTokens|Search or filter access tokens…"
 msgstr ""
 
 msgid "AccessTokens|Select a role"
@@ -3485,7 +3485,7 @@ msgstr ""
 msgid "Add a timeline event to incident"
 msgstr ""
 
-msgid "Add a title..."
+msgid "Add a title…"
 msgstr ""
 
 msgid "Add a to-do item"
@@ -6218,7 +6218,7 @@ msgstr ""
 msgid "Allows projects to track errors using an Opstrace integration."
 msgstr ""
 
-msgid "Almost there..."
+msgid "Almost there…"
 msgstr ""
 
 msgid "Already blocked"
@@ -8776,7 +8776,7 @@ msgstr ""
 msgid "Authenticated web requests"
 msgstr ""
 
-msgid "Authenticating..."
+msgid "Authenticating…"
 msgstr ""
 
 msgid "Authentication"
@@ -12174,10 +12174,10 @@ msgstr ""
 msgid "Checking branch validity"
 msgstr ""
 
-msgid "Checking branch validity..."
+msgid "Checking branch validity…"
 msgstr ""
 
-msgid "Checking group path availability..."
+msgid "Checking group path availability…"
 msgstr ""
 
 msgid "Checking if merge request can be merged…"
@@ -12186,10 +12186,10 @@ msgstr ""
 msgid "Checking source validity"
 msgstr ""
 
-msgid "Checking source validity..."
+msgid "Checking source validity…"
 msgstr ""
 
-msgid "Checking username availability..."
+msgid "Checking username availability…"
 msgstr ""
 
 msgid "Checkout|Failed to load countries. Please try again."
@@ -12228,7 +12228,7 @@ msgstr ""
 msgid "Chinese language support using"
 msgstr ""
 
-msgid "Choose File..."
+msgid "Choose File…"
 msgstr ""
 
 msgid "Choose a file"
@@ -12240,10 +12240,10 @@ msgstr ""
 msgid "Choose a template"
 msgstr ""
 
-msgid "Choose a template..."
+msgid "Choose a template…"
 msgstr ""
 
-msgid "Choose a type..."
+msgid "Choose a type…"
 msgstr ""
 
 msgid "Choose an option"
@@ -13041,7 +13041,7 @@ msgstr ""
 msgid "Closes this %{work_item_type}. Marks as related to, and a duplicate of, %{duplicate_param}."
 msgstr ""
 
-msgid "Closing %{issuableType}..."
+msgid "Closing %{issuableType}…"
 msgstr ""
 
 msgid "Cloud Run"
@@ -13886,7 +13886,7 @@ msgstr ""
 msgid "ClusterIntegration|Invalid issue URL"
 msgstr ""
 
-msgid "ClusterIntegration|Kubernetes cluster is being created..."
+msgid "ClusterIntegration|Kubernetes cluster is being created…"
 msgstr ""
 
 msgid "ClusterIntegration|Kubernetes cluster name"
@@ -15906,7 +15906,7 @@ msgstr ""
 msgid "Connecting to terminal sync service"
 msgstr ""
 
-msgid "Connecting..."
+msgid "Connecting…"
 msgstr ""
 
 msgid "Connection failure"
@@ -17355,7 +17355,7 @@ msgstr ""
 msgid "Create commit"
 msgstr ""
 
-msgid "Create commit..."
+msgid "Create commit…"
 msgstr ""
 
 msgid "Create common files more quickly, and standardize their format."
@@ -17445,7 +17445,7 @@ msgstr ""
 msgid "Create new project"
 msgstr ""
 
-msgid "Create new..."
+msgid "Create new…"
 msgstr ""
 
 msgid "Create one"
@@ -17850,7 +17850,7 @@ msgstr ""
 msgid "CredentialsInventory|SSH keys"
 msgstr ""
 
-msgid "CredentialsInventory|Search or filter credentials..."
+msgid "CredentialsInventory|Search or filter credentials…"
 msgstr ""
 
 msgid "CredentialsInventory|State"
@@ -19079,7 +19079,7 @@ msgstr ""
 msgid "DastProfiles|Scanner profiles"
 msgstr ""
 
-msgid "DastProfiles|Search..."
+msgid "DastProfiles|Search…"
 msgstr ""
 
 msgid "DastProfiles|Select a scanner profile to run a DAST scan"
@@ -19400,7 +19400,7 @@ msgstr ""
 msgid "DastSiteValidation|The validation has failed. Please try again."
 msgstr ""
 
-msgid "DastSiteValidation|The validation is in progress. Please wait..."
+msgid "DastSiteValidation|The validation is in progress. Please wait…"
 msgstr ""
 
 msgid "DastSiteValidation|This will affect %d other profile targeting the same URL."
@@ -19420,7 +19420,7 @@ msgstr ""
 msgid "DastSiteValidation|Validated"
 msgstr ""
 
-msgid "DastSiteValidation|Validating..."
+msgid "DastSiteValidation|Validating…"
 msgstr ""
 
 msgid "DastSiteValidation|Validation failed"
@@ -19435,7 +19435,7 @@ msgstr ""
 msgid "DastSiteValidation|You will not be able to run active scans against %{url}."
 msgstr ""
 
-msgid "Data is still calculating..."
+msgid "Data is still calculating…"
 msgstr ""
 
 msgid "Data refresh"
@@ -20097,7 +20097,7 @@ msgstr ""
 msgid "Dependencies|Report export in progress. After the report is generated, an email will be sent with the download link."
 msgstr ""
 
-msgid "Dependencies|Search or filter dependencies..."
+msgid "Dependencies|Search or filter dependencies…"
 msgstr ""
 
 msgid "Dependencies|Software Bill of Materials (SBOM) based on the %{linkStart}latest successful%{linkEnd} scan"
@@ -20337,10 +20337,10 @@ msgstr ""
 msgid "Deploy static assets and resources to Google managed CDN"
 msgstr ""
 
-msgid "Deploy to..."
+msgid "Deploy tokens"
 msgstr ""
 
-msgid "Deploy tokens"
+msgid "Deploy to…"
 msgstr ""
 
 msgid "DeployBoards|To see deployment progress for your environments, make sure you are deploying to %{codeStart}$KUBE_NAMESPACE%{codeEnd} and annotating with %{codeStart}app.gitlab.com/app=$CI_PROJECT_PATH_SLUG%{codeEnd} and %{codeStart}app.gitlab.com/env=$CI_ENVIRONMENT_SLUG%{codeEnd}."
@@ -23319,7 +23319,7 @@ msgstr ""
 msgid "Environments|Deleting the '%{environmentName}' environment cannot be undone. Do you want to delete it anyway?"
 msgstr ""
 
-msgid "Environments|Deploy to..."
+msgid "Environments|Deploy to…"
 msgstr ""
 
 msgid "Environments|Deployment history"
@@ -25526,9 +25526,6 @@ msgstr ""
 msgid "Filter results by project"
 msgstr ""
 
-msgid "Filter results..."
-msgstr ""
-
 msgid "Filter results…"
 msgstr ""
 
@@ -45196,7 +45193,7 @@ msgstr ""
 msgid "Profiles|Changing your username can have unintended side effects."
 msgstr ""
 
-msgid "Profiles|Choose file..."
+msgid "Profiles|Choose file…"
 msgstr ""
 
 msgid "Profiles|Choose to show contributions of private projects on your public profile without any project, repository or organization information."
@@ -49090,7 +49087,7 @@ msgstr ""
 msgid "Reopened this %{quick_action_target}."
 msgstr ""
 
-msgid "Reopening %{issuableType}..."
+msgid "Reopening %{issuableType}…"
 msgstr ""
 
 msgid "Reopening…"
diff --git a/qa/qa/specs/features/api/9_data_stores/user_inherited_access_spec.rb b/qa/qa/specs/features/api/9_tenant_scale/user_inherited_access_spec.rb
similarity index 99%
rename from qa/qa/specs/features/api/9_data_stores/user_inherited_access_spec.rb
rename to qa/qa/specs/features/api/9_tenant_scale/user_inherited_access_spec.rb
index b616df123d6..4375924c8a8 100644
--- a/qa/qa/specs/features/api/9_data_stores/user_inherited_access_spec.rb
+++ b/qa/qa/specs/features/api/9_tenant_scale/user_inherited_access_spec.rb
@@ -1,7 +1,7 @@
 # frozen_string_literal: true
 
 module QA
-  RSpec.describe 'Data Stores' do
+  RSpec.describe 'Tenant Scale' do
     describe 'User', :requires_admin, product_group: :organizations do
       let!(:parent_group) { create(:group, path: "parent-group-to-test-user-access-#{SecureRandom.hex(8)}") }
 
diff --git a/qa/qa/specs/features/api/9_data_stores/users_spec.rb b/qa/qa/specs/features/api/9_tenant_scale/users_spec.rb
similarity index 97%
rename from qa/qa/specs/features/api/9_data_stores/users_spec.rb
rename to qa/qa/specs/features/api/9_tenant_scale/users_spec.rb
index b19842a142c..3aff854aada 100644
--- a/qa/qa/specs/features/api/9_data_stores/users_spec.rb
+++ b/qa/qa/specs/features/api/9_tenant_scale/users_spec.rb
@@ -1,7 +1,7 @@
 # frozen_string_literal: true
 
 module QA
-  RSpec.describe 'Data Stores' do
+  RSpec.describe 'Tenant Scale' do
     include Support::API
 
     describe 'Users API', :smoke, product_group: :organizations do
diff --git a/qa/qa/specs/features/browser_ui/9_data_stores/cells/cell_uniqueness_spec.rb b/qa/qa/specs/features/browser_ui/9_tenant_scale/cells/cell_uniqueness_spec.rb
similarity index 91%
rename from qa/qa/specs/features/browser_ui/9_data_stores/cells/cell_uniqueness_spec.rb
rename to qa/qa/specs/features/browser_ui/9_tenant_scale/cells/cell_uniqueness_spec.rb
index 6b41302cbd6..2f1a8033124 100644
--- a/qa/qa/specs/features/browser_ui/9_data_stores/cells/cell_uniqueness_spec.rb
+++ b/qa/qa/specs/features/browser_ui/9_tenant_scale/cells/cell_uniqueness_spec.rb
@@ -1,7 +1,7 @@
 # frozen_string_literal: true
 
 module QA
-  RSpec.describe 'Data Stores', :skip_live_env, :requires_admin, product_group: :cells_infrastructure do
+  RSpec.describe 'Tenant Scale', :skip_live_env, :requires_admin, product_group: :cells_infrastructure do
     describe 'Multiple Cells' do
       # set the gdk paths to where you have your gdk folders are
       let(:cell1_gdk_path) { ENV.fetch('CELL1_GDK_PATH', '~/src/gitlab-development-kit/') }
diff --git a/qa/qa/specs/features/browser_ui/9_data_stores/cells/demo2_spec.rb b/qa/qa/specs/features/browser_ui/9_tenant_scale/cells/demo2_spec.rb
similarity index 97%
rename from qa/qa/specs/features/browser_ui/9_data_stores/cells/demo2_spec.rb
rename to qa/qa/specs/features/browser_ui/9_tenant_scale/cells/demo2_spec.rb
index 2e13b63374d..5a3ddb21c22 100644
--- a/qa/qa/specs/features/browser_ui/9_data_stores/cells/demo2_spec.rb
+++ b/qa/qa/specs/features/browser_ui/9_tenant_scale/cells/demo2_spec.rb
@@ -4,7 +4,7 @@
 # implements functionality in https://gitlab.com/gitlab-org/gitlab/-/issues/415207
 
 module QA
-  RSpec.describe 'Data Stores', :skip_live_env, :requires_admin, product_group: :cells_infrastructure do
+  RSpec.describe 'Tenant Scale', :skip_live_env, :requires_admin, product_group: :cells_infrastructure do
     describe 'Demo 2' do
       let(:cell1_url) { ENV.fetch('CELL1_URL', 'http://gdk.test:3000/') }
       let(:cell2_url) { ENV.fetch('CELL2_URL', 'http://gdk.test:3001/') }
diff --git a/qa/qa/specs/features/browser_ui/9_data_stores/cells/demo3_spec.rb b/qa/qa/specs/features/browser_ui/9_tenant_scale/cells/demo3_spec.rb
similarity index 98%
rename from qa/qa/specs/features/browser_ui/9_data_stores/cells/demo3_spec.rb
rename to qa/qa/specs/features/browser_ui/9_tenant_scale/cells/demo3_spec.rb
index d2639c21bd3..4f6b78eff2b 100644
--- a/qa/qa/specs/features/browser_ui/9_data_stores/cells/demo3_spec.rb
+++ b/qa/qa/specs/features/browser_ui/9_tenant_scale/cells/demo3_spec.rb
@@ -4,7 +4,7 @@
 # implements functionality in https://gitlab.com/gitlab-org/gitlab/-/issues/420118
 
 module QA
-  RSpec.describe 'Data Stores', :skip_live_env, :requires_admin, product_group: :cells_infrastructure do
+  RSpec.describe 'Tenant Scale', :skip_live_env, :requires_admin, product_group: :cells_infrastructure do
     describe 'Demo 3' do
       let(:debug) { false }
       let(:cell1_url) { ENV.fetch('CELL1_URL', 'http://gdk.test:3000/') }
diff --git a/qa/qa/specs/features/browser_ui/9_data_stores/cells/login_across_multiple_cells_spec.rb b/qa/qa/specs/features/browser_ui/9_tenant_scale/cells/login_across_multiple_cells_spec.rb
similarity index 91%
rename from qa/qa/specs/features/browser_ui/9_data_stores/cells/login_across_multiple_cells_spec.rb
rename to qa/qa/specs/features/browser_ui/9_tenant_scale/cells/login_across_multiple_cells_spec.rb
index 31a2e058da9..4c564831939 100644
--- a/qa/qa/specs/features/browser_ui/9_data_stores/cells/login_across_multiple_cells_spec.rb
+++ b/qa/qa/specs/features/browser_ui/9_tenant_scale/cells/login_across_multiple_cells_spec.rb
@@ -1,7 +1,7 @@
 # frozen_string_literal: true
 
 module QA
-  RSpec.describe 'Data Stores', :skip_live_env, :requires_admin, product_group: :cells_infrastructure do
+  RSpec.describe 'Tenant Scale', :skip_live_env, :requires_admin, product_group: :cells_infrastructure do
     describe 'Multiple Cells' do
       let(:url) { 'gitlab-cells.bridge' }
 
diff --git a/qa/qa/specs/features/browser_ui/9_data_stores/cells/multiple_cells_gdk_spec.rb b/qa/qa/specs/features/browser_ui/9_tenant_scale/cells/multiple_cells_gdk_spec.rb
similarity index 83%
rename from qa/qa/specs/features/browser_ui/9_data_stores/cells/multiple_cells_gdk_spec.rb
rename to qa/qa/specs/features/browser_ui/9_tenant_scale/cells/multiple_cells_gdk_spec.rb
index 049689ecf16..7f47b29ae87 100644
--- a/qa/qa/specs/features/browser_ui/9_data_stores/cells/multiple_cells_gdk_spec.rb
+++ b/qa/qa/specs/features/browser_ui/9_tenant_scale/cells/multiple_cells_gdk_spec.rb
@@ -3,7 +3,7 @@
 # version of the login test that only runs against GDK
 
 module QA
-  RSpec.describe 'Data Stores', :skip_live_env, :requires_admin, product_group: :cells_infrastructure do
+  RSpec.describe 'Tenant Scale', :skip_live_env, :requires_admin, product_group: :cells_infrastructure do
     describe 'Multiple Cells' do
       it(
         'user logged into one Cell is logged into all',
diff --git a/qa/qa/specs/features/browser_ui/9_data_stores/cells/project_exists_spec.rb b/qa/qa/specs/features/browser_ui/9_tenant_scale/cells/project_exists_spec.rb
similarity index 91%
rename from qa/qa/specs/features/browser_ui/9_data_stores/cells/project_exists_spec.rb
rename to qa/qa/specs/features/browser_ui/9_tenant_scale/cells/project_exists_spec.rb
index 1df1901e89d..02baf797096 100644
--- a/qa/qa/specs/features/browser_ui/9_data_stores/cells/project_exists_spec.rb
+++ b/qa/qa/specs/features/browser_ui/9_tenant_scale/cells/project_exists_spec.rb
@@ -1,7 +1,7 @@
 # frozen_string_literal: true
 
 module QA
-  RSpec.describe 'Data Stores', :skip_live_env, :requires_admin, product_group: :cells_infrastructure do
+  RSpec.describe 'Tenant Scale', :skip_live_env, :requires_admin, product_group: :cells_infrastructure do
     describe 'Multiple Cells' do
       # default instance is Cell 1 so the user and project are created in Cell 1
       let!(:user) { create(:user) }
diff --git a/qa/qa/specs/features/browser_ui/9_data_stores/group/create_group_with_mattermost_team_spec.rb b/qa/qa/specs/features/browser_ui/9_tenant_scale/group/create_group_with_mattermost_team_spec.rb
similarity index 100%
rename from qa/qa/specs/features/browser_ui/9_data_stores/group/create_group_with_mattermost_team_spec.rb
rename to qa/qa/specs/features/browser_ui/9_tenant_scale/group/create_group_with_mattermost_team_spec.rb
diff --git a/qa/qa/specs/features/browser_ui/9_data_stores/group/group_member_access_request_spec.rb b/qa/qa/specs/features/browser_ui/9_tenant_scale/group/group_member_access_request_spec.rb
similarity index 96%
rename from qa/qa/specs/features/browser_ui/9_data_stores/group/group_member_access_request_spec.rb
rename to qa/qa/specs/features/browser_ui/9_tenant_scale/group/group_member_access_request_spec.rb
index 3cf65d7f5a5..d2c5689d2e9 100644
--- a/qa/qa/specs/features/browser_ui/9_data_stores/group/group_member_access_request_spec.rb
+++ b/qa/qa/specs/features/browser_ui/9_tenant_scale/group/group_member_access_request_spec.rb
@@ -1,7 +1,7 @@
 # frozen_string_literal: true
 
 module QA
-  RSpec.describe 'Data Stores', :requires_admin, product_group: :organizations do
+  RSpec.describe 'Tenant Scale', :requires_admin, product_group: :organizations do
     describe 'Group member access request' do
       let!(:admin_api_client) { Runtime::API::Client.as_admin }
 
diff --git a/qa/qa/specs/features/browser_ui/9_data_stores/group/transfer_group_spec.rb b/qa/qa/specs/features/browser_ui/9_tenant_scale/group/transfer_group_spec.rb
similarity index 97%
rename from qa/qa/specs/features/browser_ui/9_data_stores/group/transfer_group_spec.rb
rename to qa/qa/specs/features/browser_ui/9_tenant_scale/group/transfer_group_spec.rb
index 5d734645a3b..3f4b5bd1dd5 100644
--- a/qa/qa/specs/features/browser_ui/9_data_stores/group/transfer_group_spec.rb
+++ b/qa/qa/specs/features/browser_ui/9_tenant_scale/group/transfer_group_spec.rb
@@ -1,7 +1,7 @@
 # frozen_string_literal: true
 
 module QA
-  RSpec.describe 'Data Stores' do
+  RSpec.describe 'Tenant Scale' do
     describe 'Subgroup transfer', product_group: :organizations do
       let(:source_group) { create(:group, path: "source-group-for-transfer_#{SecureRandom.hex(8)}") }
 
diff --git a/qa/qa/specs/features/browser_ui/9_data_stores/group/transfer_project_spec.rb b/qa/qa/specs/features/browser_ui/9_tenant_scale/group/transfer_project_spec.rb
similarity index 97%
rename from qa/qa/specs/features/browser_ui/9_data_stores/group/transfer_project_spec.rb
rename to qa/qa/specs/features/browser_ui/9_tenant_scale/group/transfer_project_spec.rb
index ca5d29c8613..f6cf5556041 100644
--- a/qa/qa/specs/features/browser_ui/9_data_stores/group/transfer_project_spec.rb
+++ b/qa/qa/specs/features/browser_ui/9_tenant_scale/group/transfer_project_spec.rb
@@ -1,7 +1,7 @@
 # frozen_string_literal: true
 
 module QA
-  RSpec.describe 'Data Stores' do
+  RSpec.describe 'Tenant Scale' do
     describe 'Project transfer', product_group: :organizations do
       let(:project) { create(:project, name: 'transfer-project', group: source_group) }
       let(:source_group) { create(:group, path: "source-group-#{SecureRandom.hex(8)}") }
diff --git a/qa/qa/specs/features/browser_ui/9_data_stores/organization/create_organization_spec.rb b/qa/qa/specs/features/browser_ui/9_tenant_scale/organization/create_organization_spec.rb
similarity index 81%
rename from qa/qa/specs/features/browser_ui/9_data_stores/organization/create_organization_spec.rb
rename to qa/qa/specs/features/browser_ui/9_tenant_scale/organization/create_organization_spec.rb
index 8a8e0d1812f..3ebe4a161d2 100644
--- a/qa/qa/specs/features/browser_ui/9_data_stores/organization/create_organization_spec.rb
+++ b/qa/qa/specs/features/browser_ui/9_tenant_scale/organization/create_organization_spec.rb
@@ -1,12 +1,12 @@
 # frozen_string_literal: true
 
 module QA
-  RSpec.describe 'Data Stores',
+  RSpec.describe 'Tenant Scale',
     :skip_live_env,
     :requires_admin,
     product_group: :organizations,
     feature_flag: {
-      name: 'ui_for_organizations',
+      name: [:ui_for_organizations, :allow_organization_creation],
       scope: :global
     } do
     describe 'Organization' do
@@ -14,7 +14,9 @@ module QA
 
       around do |example|
         Runtime::Feature.enable(:ui_for_organizations)
+        Runtime::Feature.enable(:allow_organization_creation)
         example.run
+        Runtime::Feature.disable(:allow_organization_creation)
         Runtime::Feature.disable(:ui_for_organizations)
       end
 
diff --git a/qa/qa/specs/features/browser_ui/9_data_stores/project/add_project_member_spec.rb b/qa/qa/specs/features/browser_ui/9_tenant_scale/project/add_project_member_spec.rb
similarity index 89%
rename from qa/qa/specs/features/browser_ui/9_data_stores/project/add_project_member_spec.rb
rename to qa/qa/specs/features/browser_ui/9_tenant_scale/project/add_project_member_spec.rb
index d5e796e3316..2762d2f14b6 100644
--- a/qa/qa/specs/features/browser_ui/9_data_stores/project/add_project_member_spec.rb
+++ b/qa/qa/specs/features/browser_ui/9_tenant_scale/project/add_project_member_spec.rb
@@ -1,7 +1,7 @@
 # frozen_string_literal: true
 
 module QA
-  RSpec.describe 'Data Stores', :smoke, product_group: :organizations do
+  RSpec.describe 'Tenant Scale', :smoke, product_group: :organizations do
     describe 'Project Member' do
       it 'adds a project member', testcase: 'https://gitlab.com/gitlab-org/gitlab/-/quality/test_cases/347887' do
         Flow::Login.sign_in
diff --git a/qa/qa/specs/features/browser_ui/9_data_stores/project/create_project_badge_spec.rb b/qa/qa/specs/features/browser_ui/9_tenant_scale/project/create_project_badge_spec.rb
similarity index 97%
rename from qa/qa/specs/features/browser_ui/9_data_stores/project/create_project_badge_spec.rb
rename to qa/qa/specs/features/browser_ui/9_tenant_scale/project/create_project_badge_spec.rb
index b31239bbf34..5928354fbf5 100644
--- a/qa/qa/specs/features/browser_ui/9_data_stores/project/create_project_badge_spec.rb
+++ b/qa/qa/specs/features/browser_ui/9_tenant_scale/project/create_project_badge_spec.rb
@@ -1,7 +1,7 @@
 # frozen_string_literal: true
 
 module QA
-  RSpec.describe 'Data Stores' do
+  RSpec.describe 'Tenant Scale' do
     describe 'Project badge', product_group: :organizations do
       let(:badge_name) { "project-badge-#{SecureRandom.hex(8)}" }
       let(:expected_badge_link_url) { "#{Runtime::Scenario.gitlab_address}/#{project.path_with_namespace}" }
diff --git a/qa/qa/specs/features/browser_ui/9_data_stores/project/create_project_spec.rb b/qa/qa/specs/features/browser_ui/9_tenant_scale/project/create_project_spec.rb
similarity index 94%
rename from qa/qa/specs/features/browser_ui/9_data_stores/project/create_project_spec.rb
rename to qa/qa/specs/features/browser_ui/9_tenant_scale/project/create_project_spec.rb
index 2e0db582012..b716d79a9f7 100644
--- a/qa/qa/specs/features/browser_ui/9_data_stores/project/create_project_spec.rb
+++ b/qa/qa/specs/features/browser_ui/9_tenant_scale/project/create_project_spec.rb
@@ -1,7 +1,7 @@
 # frozen_string_literal: true
 
 module QA
-  RSpec.describe 'Data Stores', :smoke, product_group: :organizations, feature_flag: {
+  RSpec.describe 'Tenant Scale', :smoke, product_group: :organizations, feature_flag: {
     name: 'new_project_creation_form'
   } do
     describe 'Project' do
diff --git a/qa/qa/specs/features/browser_ui/9_data_stores/project/dashboard_images_spec.rb b/qa/qa/specs/features/browser_ui/9_tenant_scale/project/dashboard_images_spec.rb
similarity index 94%
rename from qa/qa/specs/features/browser_ui/9_data_stores/project/dashboard_images_spec.rb
rename to qa/qa/specs/features/browser_ui/9_tenant_scale/project/dashboard_images_spec.rb
index 3fc35d1d719..9c98eb79574 100644
--- a/qa/qa/specs/features/browser_ui/9_data_stores/project/dashboard_images_spec.rb
+++ b/qa/qa/specs/features/browser_ui/9_tenant_scale/project/dashboard_images_spec.rb
@@ -1,7 +1,7 @@
 # frozen_string_literal: true
 
 module QA
-  RSpec.describe 'Data Stores', product_group: :organizations do
+  RSpec.describe 'Tenant Scale', product_group: :organizations do
     shared_examples 'loads all images' do |admin|
       let(:api_client) { Runtime::API::Client.as_admin }
       let(:user) { create(:user, is_admin: admin, api_client: api_client) }
diff --git a/qa/qa/specs/features/browser_ui/9_data_stores/project/invite_group_to_project_spec.rb b/qa/qa/specs/features/browser_ui/9_tenant_scale/project/invite_group_to_project_spec.rb
similarity index 98%
rename from qa/qa/specs/features/browser_ui/9_data_stores/project/invite_group_to_project_spec.rb
rename to qa/qa/specs/features/browser_ui/9_tenant_scale/project/invite_group_to_project_spec.rb
index ba8827af1ce..06ea426567d 100644
--- a/qa/qa/specs/features/browser_ui/9_data_stores/project/invite_group_to_project_spec.rb
+++ b/qa/qa/specs/features/browser_ui/9_tenant_scale/project/invite_group_to_project_spec.rb
@@ -1,7 +1,7 @@
 # frozen_string_literal: true
 
 module QA
-  RSpec.describe 'Data Stores' do
+  RSpec.describe 'Tenant Scale' do
     describe 'Invite group', product_group: :organizations, quarantine: {
       type: :bug,
       issue: "https://gitlab.com/gitlab-org/gitlab/-/issues/436950",
diff --git a/qa/qa/specs/features/browser_ui/9_data_stores/project/project_owner_permissions_spec.rb b/qa/qa/specs/features/browser_ui/9_tenant_scale/project/project_owner_permissions_spec.rb
similarity index 98%
rename from qa/qa/specs/features/browser_ui/9_data_stores/project/project_owner_permissions_spec.rb
rename to qa/qa/specs/features/browser_ui/9_tenant_scale/project/project_owner_permissions_spec.rb
index e71ddbc9c73..2fd8e9e73c8 100644
--- a/qa/qa/specs/features/browser_ui/9_data_stores/project/project_owner_permissions_spec.rb
+++ b/qa/qa/specs/features/browser_ui/9_tenant_scale/project/project_owner_permissions_spec.rb
@@ -1,7 +1,7 @@
 # frozen_string_literal: true
 
 module QA
-  RSpec.describe 'Data Stores' do
+  RSpec.describe 'Tenant Scale' do
     describe 'Project owner permissions', :smoke, :requires_admin, product_group: :organizations do
       let!(:owner) { Runtime::User::Store.test_user }
       let!(:owner_api_client) { owner.api_client }
diff --git a/qa/qa/specs/features/browser_ui/9_data_stores/project/view_project_activity_spec.rb b/qa/qa/specs/features/browser_ui/9_tenant_scale/project/view_project_activity_spec.rb
similarity index 96%
rename from qa/qa/specs/features/browser_ui/9_data_stores/project/view_project_activity_spec.rb
rename to qa/qa/specs/features/browser_ui/9_tenant_scale/project/view_project_activity_spec.rb
index 093520a78f7..34b5b3b17d3 100644
--- a/qa/qa/specs/features/browser_ui/9_data_stores/project/view_project_activity_spec.rb
+++ b/qa/qa/specs/features/browser_ui/9_tenant_scale/project/view_project_activity_spec.rb
@@ -1,7 +1,7 @@
 # frozen_string_literal: true
 
 module QA
-  RSpec.describe 'Data Stores' do
+  RSpec.describe 'Tenant Scale' do
     describe 'Project activity', :smoke, product_group: :organizations do
       context 'with git push' do
         it 'creates an event in the activity page',
diff --git a/qa/qa/specs/features/browser_ui/9_data_stores/user/follow_user_activity_spec.rb b/qa/qa/specs/features/browser_ui/9_tenant_scale/user/follow_user_activity_spec.rb
similarity index 98%
rename from qa/qa/specs/features/browser_ui/9_data_stores/user/follow_user_activity_spec.rb
rename to qa/qa/specs/features/browser_ui/9_tenant_scale/user/follow_user_activity_spec.rb
index a0b75559add..003ad22abb3 100644
--- a/qa/qa/specs/features/browser_ui/9_data_stores/user/follow_user_activity_spec.rb
+++ b/qa/qa/specs/features/browser_ui/9_tenant_scale/user/follow_user_activity_spec.rb
@@ -1,7 +1,7 @@
 # frozen_string_literal: true
 
 module QA
-  RSpec.describe 'Data Stores' do
+  RSpec.describe 'Tenant Scale' do
     describe 'User', :requires_admin, product_group: :organizations do
       let(:admin_api_client) { Runtime::User::Store.admin_api_client }
       let(:followed_user_api_client) { followed_user.api_client }
diff --git a/qa/qa/specs/features/browser_ui/9_data_stores/user/parent_group_access_termination_spec.rb b/qa/qa/specs/features/browser_ui/9_tenant_scale/user/parent_group_access_termination_spec.rb
similarity index 97%
rename from qa/qa/specs/features/browser_ui/9_data_stores/user/parent_group_access_termination_spec.rb
rename to qa/qa/specs/features/browser_ui/9_tenant_scale/user/parent_group_access_termination_spec.rb
index ededb9fdf8d..d0897df82f2 100644
--- a/qa/qa/specs/features/browser_ui/9_data_stores/user/parent_group_access_termination_spec.rb
+++ b/qa/qa/specs/features/browser_ui/9_tenant_scale/user/parent_group_access_termination_spec.rb
@@ -1,7 +1,7 @@
 # frozen_string_literal: true
 
 module QA
-  RSpec.describe 'Data Stores' do
+  RSpec.describe 'Tenant Scale' do
     describe 'User', :requires_admin, product_group: :organizations do
       let(:admin_api_client) { Runtime::API::Client.as_admin }
 
diff --git a/qa/qa/specs/features/browser_ui/9_data_stores/user/user_inherited_access_spec.rb b/qa/qa/specs/features/browser_ui/9_tenant_scale/user/user_inherited_access_spec.rb
similarity index 98%
rename from qa/qa/specs/features/browser_ui/9_data_stores/user/user_inherited_access_spec.rb
rename to qa/qa/specs/features/browser_ui/9_tenant_scale/user/user_inherited_access_spec.rb
index 5efe1a2eab4..b3fe3f2986f 100644
--- a/qa/qa/specs/features/browser_ui/9_data_stores/user/user_inherited_access_spec.rb
+++ b/qa/qa/specs/features/browser_ui/9_tenant_scale/user/user_inherited_access_spec.rb
@@ -1,7 +1,7 @@
 # frozen_string_literal: true
 
 module QA
-  RSpec.describe 'Data Stores' do
+  RSpec.describe 'Tenant Scale' do
     describe 'User', :requires_admin, product_group: :organizations do
       let!(:parent_group) do
         create(:group, path: "parent-group-to-test-user-access-#{SecureRandom.hex(8)}")
diff --git a/spec/features/projects/environments/environment_spec.rb b/spec/features/projects/environments/environment_spec.rb
index bd6848ffb1e..211c6e2dd02 100644
--- a/spec/features/projects/environments/environment_spec.rb
+++ b/spec/features/projects/environments/environment_spec.rb
@@ -184,7 +184,7 @@ RSpec.describe 'Environment', feature_category: :environment_management do
             it 'does allow to play manual action' do
               expect(action).to be_manual
 
-              click_button('Deploy to...')
+              click_button('Deploy to…')
 
               expect { click_button(action.name) }
                 .not_to change { Ci::Pipeline.count }
diff --git a/spec/features/projects/files/project_owner_sees_link_to_create_license_file_in_empty_project_spec.rb b/spec/features/projects/files/project_owner_sees_link_to_create_license_file_in_empty_project_spec.rb
index 0b67b025d90..f73fcc774b4 100644
--- a/spec/features/projects/files/project_owner_sees_link_to_create_license_file_in_empty_project_spec.rb
+++ b/spec/features/projects/files/project_owner_sees_link_to_create_license_file_in_empty_project_spec.rb
@@ -42,7 +42,7 @@ RSpec.describe 'Projects > Files > Project owner sees a link to create a license
   end
 
   def select_template(template)
-    click_button 'Choose a template...'
+    click_button 'Choose a template…'
     click_button template
     wait_for_requests
   end
diff --git a/spec/features/projects/show/user_sees_collaboration_links_spec.rb b/spec/features/projects/show/user_sees_collaboration_links_spec.rb
index 7fb95bb0e8b..bb2a77544ff 100644
--- a/spec/features/projects/show/user_sees_collaboration_links_spec.rb
+++ b/spec/features/projects/show/user_sees_collaboration_links_spec.rb
@@ -14,7 +14,7 @@ RSpec.describe 'Projects > Show > Collaboration links', :js, feature_category: :
   end
 
   def find_new_menu_toggle
-    find_by_testid('base-dropdown-toggle', text: 'Create new...')
+    find_by_testid('base-dropdown-toggle', text: 'Create new…')
   end
 
   context 'with developer user' do
diff --git a/spec/frontend/access_tokens/components/access_token_table_app_spec.js b/spec/frontend/access_tokens/components/access_token_table_app_spec.js
index d2c545556f8..2d13b2b6215 100644
--- a/spec/frontend/access_tokens/components/access_token_table_app_spec.js
+++ b/spec/frontend/access_tokens/components/access_token_table_app_spec.js
@@ -20,10 +20,11 @@ describe('~/access_tokens/components/access_token_table_app', () => {
   const accessTokenTypePlural = 'personal access tokens';
   const noActiveTokensMessage = 'This user has no active personal access tokens.';
   const showRole = false;
+  const tokenNameWithHtmlEntities = "John's & ¥200<>";
 
   const defaultActiveAccessTokens = [
     {
-      name: 'a',
+      name: tokenNameWithHtmlEntities,
       description: 'Test description',
       scopes: ['api'],
       created_at: '2021-05-01T00:00:00.000Z',
@@ -211,7 +212,7 @@ describe('~/access_tokens/components/access_token_table_app', () => {
       expect(cells).toHaveLength(18);
 
       // First row
-      expect(cells.at(0).text()).toBe('a');
+      expect(cells.at(0).text()).toBe(tokenNameWithHtmlEntities);
       expect(cells.at(1).text()).toBe('Test description');
       expect(cells.at(2).text()).toBe('api');
       expect(cells.at(3).text()).not.toBe('Never');
@@ -222,13 +223,18 @@ describe('~/access_tokens/components/access_token_table_app', () => {
       let buttons = cells.at(8).findAllComponents(GlButton);
       expect(buttons).toHaveLength(2);
       expect(buttons.at(0).attributes()).toMatchObject({
-        'aria-label': `Revoke ${defaultActiveAccessTokens[0].name}`,
+        'aria-label': sprintf(
+          'Revoke %{tokenName}',
+          { tokenName: tokenNameWithHtmlEntities },
+          false,
+        ),
         title: 'Revoke',
         'data-testid': 'revoke-button',
         href: '/-/user_settings/personal_access_tokens/1/revoke',
         'data-confirm': sprintf(
           'Are you sure you want to revoke the %{accessTokenType} "%{tokenName}"? This action cannot be undone. Any tools that rely on this access token will stop working.',
-          { accessTokenType, tokenName: 'a' },
+          { accessTokenType, tokenName: tokenNameWithHtmlEntities },
+          false,
         ),
       });
       expect(buttons.at(0).props('category')).toBe('tertiary');
@@ -272,7 +278,7 @@ describe('~/access_tokens/components/access_token_table_app', () => {
       });
       const cells = findCells();
       expect(cells).toHaveLength(16);
-      expect(cells.at(0).text()).toBe('a');
+      expect(cells.at(0).text()).toBe(tokenNameWithHtmlEntities);
       expect(cells.at(8).text()).toBe('b');
       expect(createAlert).not.toHaveBeenCalled();
     });
@@ -370,7 +376,7 @@ describe('~/access_tokens/components/access_token_table_app', () => {
       const cells = findCells();
 
       // First and second rows
-      expect(cells.at(0).text()).toBe('a');
+      expect(cells.at(0).text()).toBe(tokenNameWithHtmlEntities);
       expect(cells.at(9).text()).toBe('b');
 
       const headers = findHeaders();
@@ -378,8 +384,8 @@ describe('~/access_tokens/components/access_token_table_app', () => {
       await headers.at(0).trigger('click');
 
       // First and second rows have swapped
-      expect(cells.at(0).text()).toBe('b');
-      expect(cells.at(9).text()).toBe('a');
+      expect(cells.at(0).text()).toBe(tokenNameWithHtmlEntities);
+      expect(cells.at(9).text()).toBe('b');
     });
 
     it('sorts rows by date', async () => {
@@ -451,7 +457,7 @@ describe('~/access_tokens/components/access_token_table_app', () => {
       const cells = findCells();
 
       // First and second rows
-      expect(cells.at(0).text()).toBe('a');
+      expect(cells.at(0).text()).toBe(tokenNameWithHtmlEntities);
       expect(cells.at(9).text()).toBe('b');
 
       const headers = findHeaders();
@@ -459,7 +465,7 @@ describe('~/access_tokens/components/access_token_table_app', () => {
       await headers.at(0).trigger('click');
 
       // First and second rows are not swapped
-      expect(cells.at(0).text()).toBe('a');
+      expect(cells.at(0).text()).toBe(tokenNameWithHtmlEntities);
       expect(cells.at(9).text()).toBe('b');
     });
 
diff --git a/spec/frontend/admin/analytics/devops_score/components/devops_score_spec.js b/spec/frontend/admin/analytics/devops_score/components/devops_score_spec.js
index 019027be6c6..bb828bec93e 100644
--- a/spec/frontend/admin/analytics/devops_score/components/devops_score_spec.js
+++ b/spec/frontend/admin/analytics/devops_score/components/devops_score_spec.js
@@ -45,7 +45,7 @@ describe('DevopsScore', () => {
 
       it('displays the correct message', () => {
         expect(findEmptyState().text().replace(/\s+/g, ' ')).toBe(
-          'Data is still calculating... It may be several days before you see feature usage data. See example DevOps Score page in our documentation.',
+          'Data is still calculating… It may be several days before you see feature usage data. See example DevOps Score page in our documentation.',
         );
       });
 
diff --git a/spec/frontend/environments/environment_actions_spec.js b/spec/frontend/environments/environment_actions_spec.js
index b7e192839da..8f94800c976 100644
--- a/spec/frontend/environments/environment_actions_spec.js
+++ b/spec/frontend/environments/environment_actions_spec.js
@@ -51,9 +51,7 @@ describe('EnvironmentActions Component', () => {
 
   it('should render a dropdown button with aria-label description', () => {
     createComponent();
-    expect(wrapper.findComponent(GlDisclosureDropdown).attributes('aria-label')).toBe(
-      'Deploy to...',
-    );
+    expect(wrapper.findComponent(GlDisclosureDropdown).attributes('aria-label')).toBe('Deploy to…');
   });
 
   describe('manual actions', () => {
diff --git a/spec/frontend/file_pickers_spec.js b/spec/frontend/file_pickers_spec.js
index c3e25b8a5b3..67389b81017 100644
--- a/spec/frontend/file_pickers_spec.js
+++ b/spec/frontend/file_pickers_spec.js
@@ -23,7 +23,7 @@ describe('initFilePickers', () => {
           <button type="button" class="js-filepicker-button">
             <span class="gl-button-text">Choose file…</span>
           </button>
-          <span class="file_name js-filepicker-filename">Choose file...</span>
+          <span class="file_name js-filepicker-filename">Choose file…</span>
           <input accept type="file" class="js-filepicker-input hidden" />
           <span class="js-filepicker-error gl-hidden gl-text-danger">The maximum file size is 200 KiB.</span
         </div>
diff --git a/spec/frontend/ide/components/commit_sidebar/form_spec.js b/spec/frontend/ide/components/commit_sidebar/form_spec.js
index 8d1a949ab09..534cb2598de 100644
--- a/spec/frontend/ide/components/commit_sidebar/form_spec.js
+++ b/spec/frontend/ide/components/commit_sidebar/form_spec.js
@@ -125,7 +125,7 @@ describe('IDE commit form', () => {
 
     it('renders commit button in compact mode', () => {
       expect(findBeginCommitButton().exists()).toBe(true);
-      expect(findBeginCommitButton().text()).toBe('Create commit...');
+      expect(findBeginCommitButton().text()).toBe('Create commit…');
     });
 
     it('does not render form', () => {
diff --git a/spec/frontend/super_sidebar/components/create_menu_spec.js b/spec/frontend/super_sidebar/components/create_menu_spec.js
index 8360f319f1a..b532354e174 100644
--- a/spec/frontend/super_sidebar/components/create_menu_spec.js
+++ b/spec/frontend/super_sidebar/components/create_menu_spec.js
@@ -62,7 +62,7 @@ describe('CreateMenu component', () => {
     });
 
     it("sets the toggle's label", () => {
-      expect(findGlDisclosureDropdown().props('toggleText')).toBe('Create new...');
+      expect(findGlDisclosureDropdown().props('toggleText')).toBe('Create new…');
     });
     it('has correct amount of dropdown groups', () => {
       const items = findGlDisclosureDropdownGroups();
@@ -131,7 +131,7 @@ describe('CreateMenu component', () => {
       await nextTick();
 
       const tooltip = getBinding(findGlDisclosureDropdown().element, 'gl-tooltip');
-      expect(tooltip.value).toBe('Create new...');
+      expect(tooltip.value).toBe('Create new…');
     });
   });
 
diff --git a/spec/frontend/super_sidebar/components/user_bar_spec.js b/spec/frontend/super_sidebar/components/user_bar_spec.js
index f77b3740e61..2e6a0d59179 100644
--- a/spec/frontend/super_sidebar/components/user_bar_spec.js
+++ b/spec/frontend/super_sidebar/components/user_bar_spec.js
@@ -86,7 +86,7 @@ describe('UserBar component', () => {
       createWrapper();
     });
 
-    describe('"Create new..." menu', () => {
+    describe('"Create new…" menu', () => {
       describe('when there are no menu items for it', () => {
         // This scenario usually happens for an "External" user.
         it('does not render it', () => {
@@ -96,7 +96,7 @@ describe('UserBar component', () => {
       });
 
       describe('when there are menu items for it', () => {
-        it('passes the "Create new..." menu groups to the create-menu component', () => {
+        it('passes the "Create new…" menu groups to the create-menu component', () => {
           expect(findCreateMenu().props('groups')).toBe(mockSidebarData.create_new_menu_groups);
         });
       });
diff --git a/spec/frontend/work_items/components/item_title_spec.js b/spec/frontend/work_items/components/item_title_spec.js
index 660ff671a80..0ded797d2d3 100644
--- a/spec/frontend/work_items/components/item_title_spec.js
+++ b/spec/frontend/work_items/components/item_title_spec.js
@@ -22,7 +22,7 @@ describe('ItemTitle', () => {
 
   it('renders title contents', () => {
     expect(findInputEl().attributes()).toMatchObject({
-      'data-placeholder': 'Add a title...',
+      'data-placeholder': 'Add a title…',
       contenteditable: 'true',
     });
     expect(findInputEl().text()).toBe('Sample title');
diff --git a/spec/helpers/ci/jobs_helper_spec.rb b/spec/helpers/ci/jobs_helper_spec.rb
index d7619ea98c6..2f82b28cdc0 100644
--- a/spec/helpers/ci/jobs_helper_spec.rb
+++ b/spec/helpers/ci/jobs_helper_spec.rb
@@ -29,7 +29,7 @@ RSpec.describe Ci::JobsHelper, feature_category: :continuous_integration do
         "test_report_summary_url" => "/#{project.full_path}/-/jobs/#{job.id}/test_report_summary.json",
         "page_path" => "/#{project.full_path}/-/jobs/#{job.id}",
         "project_path" => project.full_path,
-        "artifact_help_url" => "/help/user/gitlab_com/_index.md#gitlab-cicd",
+        "artifact_help_url" => "/help/user/gitlab_com/_index.md#cicd",
         "deployment_help_url" => "/help/user/project/clusters/deploy_to_cluster.md#troubleshooting",
         "runner_settings_url" => "/#{project.full_path}/-/runners#js-runners-settings",
         "retry_outdated_job_docs_url" => "/help/ci/pipelines/settings.md#prevent-outdated-deployment-jobs",
diff --git a/spec/helpers/nav/new_dropdown_helper_spec.rb b/spec/helpers/nav/new_dropdown_helper_spec.rb
index b1795cd2092..baefde43329 100644
--- a/spec/helpers/nav/new_dropdown_helper_spec.rb
+++ b/spec/helpers/nav/new_dropdown_helper_spec.rb
@@ -12,7 +12,7 @@ RSpec.describe Nav::NewDropdownHelper, feature_category: :navigation do
     let(:with_can_create_group) { false }
     let(:with_can_create_snippet) { false }
     let(:with_can_create_organization) { false }
-    let(:title) { 'Create new...' }
+    let(:title) { 'Create new…' }
 
     subject(:view_model) do
       helper.new_dropdown_view_model(project: current_project, group: current_group)
@@ -50,7 +50,7 @@ RSpec.describe Nav::NewDropdownHelper, feature_category: :navigation do
     end
 
     it 'has title' do
-      expect(view_model[:title]).to eq('Create new...')
+      expect(view_model[:title]).to eq('Create new…')
     end
 
     context 'when current_user is nil (anonymous)' do
diff --git a/spec/lib/gitlab/auth/o_auth/before_request_phase_oauth_login_counter_increment_spec.rb b/spec/lib/gitlab/auth/o_auth/before_request_phase_oauth_login_counter_increment_spec.rb
index a1ddfa862a1..51e7453830b 100644
--- a/spec/lib/gitlab/auth/o_auth/before_request_phase_oauth_login_counter_increment_spec.rb
+++ b/spec/lib/gitlab/auth/o_auth/before_request_phase_oauth_login_counter_increment_spec.rb
@@ -7,7 +7,8 @@ RSpec.describe Gitlab::Auth::OAuth::BeforeRequestPhaseOauthLoginCounterIncrement
     let(:env) { { 'omniauth.strategy' => omniauth_strategy } }
     let(:omniauth_strategy) { instance_double(OmniAuth::Strategies::GoogleOauth2, name: 'google_oauth2') }
 
-    it 'increments Prometheus counter for the given provider' do
+    it 'increments Prometheus counter for the given provider',
+      quarantine: 'https://gitlab.com/gitlab-org/gitlab/-/issues/524007' do
       expect { described_class.call(env) }
         .to change { gitlab_metric_omniauth_login_total_for('google_oauth2', 'initiated') }.by(1)
     end
diff --git a/spec/lib/gitlab/database/no_cross_db_foreign_keys_spec.rb b/spec/lib/gitlab/database/no_cross_db_foreign_keys_spec.rb
index ef7a7e140c6..07b1e02f81f 100644
--- a/spec/lib/gitlab/database/no_cross_db_foreign_keys_spec.rb
+++ b/spec/lib/gitlab/database/no_cross_db_foreign_keys_spec.rb
@@ -33,7 +33,6 @@ RSpec.describe 'cross-database foreign keys' do
       'pages_deployment_states.project_id',
       'pool_repositories.source_project_id',
       'project_repositories.project_id',
-      'project_states.project_id',
       'projects.pool_repository_id',
       'snippet_repositories.snippet_id',
       'snippet_repositories.snippet_organization_id',