Add latest changes from gitlab-org/gitlab@master

51 files changed, 244 insertions, 225 deletions

diff --git a/doc/administration/geo/setup/external_database.md b/doc/administration/geo/setup/external_database.md
index 0fefc11f078..f93ef5f5d5e 100644
--- a/doc/administration/geo/setup/external_database.md
+++ b/doc/administration/geo/setup/external_database.md
@@ -217,14 +217,14 @@ the tracking database on port 5432.
    `pg_hba.conf` that is associated with your tracking database.
    Remember to restart PostgreSQL afterwards for the changes to take effect:
 
-    ```plaintext
-    ##
-    ## Geo Tracking Database Role
-    ## - pg_hba.conf
-    ##
-    host    all         all               <trusted tracking IP>/32      md5
-    host    all         all               <trusted secondary IP>/32     md5
-    ```
+   ```plaintext
+   ##
+   ## Geo Tracking Database Role
+   ## - pg_hba.conf
+   ##
+   host    all         all               <trusted tracking IP>/32      md5
+   host    all         all               <trusted secondary IP>/32     md5
+   ```
 
 1. SSH into a GitLab **secondary** server and login as root:
 
diff --git a/doc/administration/instance_limits.md b/doc/administration/instance_limits.md
index 2ba2930c6f7..1a5e5134e9b 100644
--- a/doc/administration/instance_limits.md
+++ b/doc/administration/instance_limits.md
@@ -723,22 +723,23 @@ GitLab checks these limits against runners that have been active in the last 3 m
 A runner's registration fails if it exceeds the limit for the scope determined by the runner registration token.
 If the limit value is set to zero, the limit is disabled.
 
-- GitLab SaaS subscribers have different limits defined per plan, affecting all projects using that plan.
-- Self-managed GitLab Premium and Ultimate limits are defined by a default plan that affects all projects:
-
-    | Runner scope                                | Default value |
-    |---------------------------------------------|---------------|
-    | `ci_registered_group_runners`               | 1000          |
-    | `ci_registered_project_runners`             | 1000          |
-
-    To update these limits, run the following in the
-    [GitLab Rails console](operations/rails_console.md#starting-a-rails-console-session):
-
-    ```ruby
-    # Use ci_registered_group_runners or ci_registered_project_runners
-    # depending on desired scope
-    Plan.default.actual_limits.update!(ci_registered_project_runners: 100)
-    ```
+GitLab SaaS subscribers have different limits defined per plan, affecting all projects using that plan.
+
+Self-managed GitLab Premium and Ultimate limits are defined by a default plan that affects all projects:
+
+| Runner scope                                | Default value |
+|---------------------------------------------|---------------|
+| `ci_registered_group_runners`               | 1000          |
+| `ci_registered_project_runners`             | 1000          |
+
+To update these limits, run the following in the
+[GitLab Rails console](operations/rails_console.md#starting-a-rails-console-session):
+
+```ruby
+# Use ci_registered_group_runners or ci_registered_project_runners
+# depending on desired scope
+Plan.default.actual_limits.update!(ci_registered_project_runners: 100)
+```
 
 ### Maximum file size for job logs
 
diff --git a/doc/administration/object_storage.md b/doc/administration/object_storage.md
index aaa5f7b90b0..3da7ee3d692 100644
--- a/doc/administration/object_storage.md
+++ b/doc/administration/object_storage.md
@@ -116,42 +116,42 @@ The following example uses AWS S3 to enable object storage for all supported ser
 1. Edit `/etc/gitlab/gitlab.rb` and add the following lines, substituting
    the values you want:
 
-    ```ruby
-    # Consolidated object storage configuration
-    gitlab_rails['object_store']['enabled'] = true
-    gitlab_rails['object_store']['proxy_download'] = true
-    gitlab_rails['object_store']['connection'] = {
-      'provider' => 'AWS',
-      'region' => 'eu-central-1',
-      'aws_access_key_id' => '<AWS_ACCESS_KEY_ID>',
-      'aws_secret_access_key' => '<AWS_SECRET_ACCESS_KEY>'
-    }
-    # OPTIONAL: The following lines are only needed if server side encryption is required
-    gitlab_rails['object_store']['storage_options'] = {
-      'server_side_encryption' => '<AES256 or aws:kms>',
-      'server_side_encryption_kms_key_id' => '<arn:aws:kms:xxx>'
-    }
-    gitlab_rails['object_store']['objects']['artifacts']['bucket'] = 'gitlab-artifacts'
-    gitlab_rails['object_store']['objects']['external_diffs']['bucket'] = 'gitlab-mr-diffs'
-    gitlab_rails['object_store']['objects']['lfs']['bucket'] = 'gitlab-lfs'
-    gitlab_rails['object_store']['objects']['uploads']['bucket'] = 'gitlab-uploads'
-    gitlab_rails['object_store']['objects']['packages']['bucket'] = 'gitlab-packages'
-    gitlab_rails['object_store']['objects']['dependency_proxy']['bucket'] = 'gitlab-dependency-proxy'
-    gitlab_rails['object_store']['objects']['terraform_state']['bucket'] = 'gitlab-terraform-state'
-    gitlab_rails['object_store']['objects']['ci_secure_files']['bucket'] = 'gitlab-ci-secure-files'
-    gitlab_rails['object_store']['objects']['pages']['bucket'] = 'gitlab-pages'
-    ```
-
-    If you’re using [AWS IAM profiles](#using-amazon-instance-profiles), omit
-    the AWS access key and secret access key/value pairs. For example:
-
-    ```ruby
-    gitlab_rails['object_store']['connection'] = {
-      'provider' => 'AWS',
-      'region' => 'eu-central-1',
-      'use_iam_profile' => true
-    }
-    ```
+   ```ruby
+   # Consolidated object storage configuration
+   gitlab_rails['object_store']['enabled'] = true
+   gitlab_rails['object_store']['proxy_download'] = true
+   gitlab_rails['object_store']['connection'] = {
+     'provider' => 'AWS',
+     'region' => 'eu-central-1',
+     'aws_access_key_id' => '<AWS_ACCESS_KEY_ID>',
+     'aws_secret_access_key' => '<AWS_SECRET_ACCESS_KEY>'
+   }
+   # OPTIONAL: The following lines are only needed if server side encryption is required
+   gitlab_rails['object_store']['storage_options'] = {
+     'server_side_encryption' => '<AES256 or aws:kms>',
+     'server_side_encryption_kms_key_id' => '<arn:aws:kms:xxx>'
+   }
+   gitlab_rails['object_store']['objects']['artifacts']['bucket'] = 'gitlab-artifacts'
+   gitlab_rails['object_store']['objects']['external_diffs']['bucket'] = 'gitlab-mr-diffs'
+   gitlab_rails['object_store']['objects']['lfs']['bucket'] = 'gitlab-lfs'
+   gitlab_rails['object_store']['objects']['uploads']['bucket'] = 'gitlab-uploads'
+   gitlab_rails['object_store']['objects']['packages']['bucket'] = 'gitlab-packages'
+   gitlab_rails['object_store']['objects']['dependency_proxy']['bucket'] = 'gitlab-dependency-proxy'
+   gitlab_rails['object_store']['objects']['terraform_state']['bucket'] = 'gitlab-terraform-state'
+   gitlab_rails['object_store']['objects']['ci_secure_files']['bucket'] = 'gitlab-ci-secure-files'
+   gitlab_rails['object_store']['objects']['pages']['bucket'] = 'gitlab-pages'
+   ```
+
+   If you're using [AWS IAM profiles](#using-amazon-instance-profiles), omit
+   the AWS access key and secret access key/value pairs. For example:
+
+   ```ruby
+   gitlab_rails['object_store']['connection'] = {
+     'provider' => 'AWS',
+     'region' => 'eu-central-1',
+     'use_iam_profile' => true
+   }
+   ```
 
 1. Save the file and reconfigure GitLab:
 
@@ -171,7 +171,7 @@ The following example uses AWS S3 to enable object storage for all supported ser
    aws_secret_access_key: <AWS_SECRET_ACCESS_KEY>
    ```
 
-   If you’re using [AWS IAM profiles](#using-amazon-instance-profiles), omit
+   If you're using [AWS IAM profiles](#using-amazon-instance-profiles), omit
    the AWS access key and secret access key/value pairs. For example:
 
    ```yaml
@@ -293,7 +293,7 @@ The following example uses AWS S3 to enable object storage for all supported ser
            gitlab_rails['object_store']['objects']['pages']['bucket'] = 'gitlab-pages'
    ```
 
-   If you’re using [AWS IAM profiles](#using-amazon-instance-profiles), omit
+   If you're using [AWS IAM profiles](#using-amazon-instance-profiles), omit
    the AWS access key and secret access key/value pairs. For example:
 
    ```ruby
@@ -348,7 +348,7 @@ The following example uses AWS S3 to enable object storage for all supported ser
            bucket: gitlab-pages
    ```
 
-   If you’re using [AWS IAM profiles](#using-amazon-instance-profiles), omit
+   If you're using [AWS IAM profiles](#using-amazon-instance-profiles), omit
    the AWS access key and secret access key/value pairs. For example:
 
    ```yaml
@@ -369,7 +369,7 @@ The following example uses AWS S3 to enable object storage for all supported ser
      aws_secret_access_key = "<AWS_SECRET_ACCESS_KEY>"
    ```
 
-   If you’re using [AWS IAM profiles](#using-amazon-instance-profiles), omit
+   If you're using [AWS IAM profiles](#using-amazon-instance-profiles), omit
    the AWS access key and secret access key/value pairs. For example:
 
    ```yaml
diff --git a/doc/administration/operations/gitlab_sshd.md b/doc/administration/operations/gitlab_sshd.md
index 7b61631fe3a..1153321267d 100644
--- a/doc/administration/operations/gitlab_sshd.md
+++ b/doc/administration/operations/gitlab_sshd.md
@@ -110,11 +110,11 @@ To enable the PROXY protocol:
 
 1. Edit `/etc/gitlab/gitlab.rb`:
 
-    ```ruby
-    gitlab_sshd['proxy_protocol'] = true
-    # # Proxy protocol policy ("use", "require", "reject", "ignore"), "use" is the default value
-    gitlab_sshd['proxy_policy'] = "use"
-    ```
+   ```ruby
+   gitlab_sshd['proxy_protocol'] = true
+   # # Proxy protocol policy ("use", "require", "reject", "ignore"), "use" is the default value
+   gitlab_sshd['proxy_policy'] = "use"
+   ```
 
 1. Save the file and reconfigure GitLab:
 
diff --git a/doc/administration/operations/moving_repositories.md b/doc/administration/operations/moving_repositories.md
index aa0477be788..e9d829f3f08 100644
--- a/doc/administration/operations/moving_repositories.md
+++ b/doc/administration/operations/moving_repositories.md
@@ -139,14 +139,14 @@ To move all snippets by using the API:
 To move all groups by using the API:
 
 1. [Schedule repository storage moves for all groups on a storage shard](../../api/group_repository_storage_moves.md#schedule-repository-storage-moves-for-all-groups-on-a-storage-shard).
-    For example:
-
-    ```shell
-    curl --request POST --header "PRIVATE-TOKEN: <your_access_token>" \
-         --header "Content-Type: application/json" \
-         --data '{"source_storage_name":"<original_storage_name>","destination_storage_name":"<cluster_storage_name>"}' \
-         "https://gitlab.example.com/api/v4/group_repository_storage_moves"
-    ```
+   For example:
+
+   ```shell
+   curl --request POST --header "PRIVATE-TOKEN: <your_access_token>" \
+        --header "Content-Type: application/json" \
+        --data '{"source_storage_name":"<original_storage_name>","destination_storage_name":"<cluster_storage_name>"}' \
+        "https://gitlab.example.com/api/v4/group_repository_storage_moves"
+   ```
 
 1. [Query the most recent repository moves](../../api/group_repository_storage_moves.md#retrieve-all-group-repository-storage-moves).
    The response indicates either:
diff --git a/doc/administration/packages/container_registry.md b/doc/administration/packages/container_registry.md
index 576917a40d5..619ec2490a7 100644
--- a/doc/administration/packages/container_registry.md
+++ b/doc/administration/packages/container_registry.md
@@ -639,20 +639,20 @@ However, this behavior is undesirable for registries used by internal hosts that
 
 1. Edit `/etc/gitlab/gitlab.rb`:
 
-    ```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'
-      },
-      'redirect' => {
-        'disable' => true
-      }
-    }
-    ```
+   ```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'
+     },
+     'redirect' => {
+       'disable' => true
+     }
+   }
+   ```
 
 1. Save the file and [reconfigure GitLab](../restart_gitlab.md#omnibus-gitlab-reconfigure) for the changes to take effect.
 
@@ -660,21 +660,21 @@ However, this behavior is undesirable for registries used by internal hosts that
 
 1. Add the `redirect` flag to your registry configuration YAML file:
 
-    ```yaml
-    storage:
-      s3:
-        accesskey: 'AKIAKIAKI'
-        secretkey: 'secret123'
-        bucket: 'gitlab-registry-bucket-AKIAKIAKI'
-        region: 'your-s3-region'
-        regionendpoint: 'your-s3-regionendpoint'
-      redirect:
-        disable: true
-      cache:
-        blobdescriptor: inmemory
-      delete:
-        enabled: true
-    ```
+   ```yaml
+   storage:
+     s3:
+       accesskey: 'AKIAKIAKI'
+       secretkey: 'secret123'
+       bucket: 'gitlab-registry-bucket-AKIAKIAKI'
+       region: 'your-s3-region'
+       regionendpoint: 'your-s3-regionendpoint'
+     redirect:
+       disable: true
+     cache:
+       blobdescriptor: inmemory
+     delete:
+       enabled: true
+   ```
 
 1. Save the file and [restart GitLab](../restart_gitlab.md#installations-from-source) for the changes to take effect.
 
@@ -692,18 +692,18 @@ For Omnibus GitLab installations:
 
 1. Edit `/etc/gitlab/gitlab.rb`:
 
-    ```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',
-        'encrypt' => true
-      }
-    }
-    ```
+   ```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',
+       'encrypt' => true
+     }
+   }
+   ```
 
 1. Save the file and [reconfigure GitLab](../restart_gitlab.md#omnibus-gitlab-reconfigure)
    for the changes to take effect.
@@ -712,16 +712,16 @@ For installations from source:
 
 1. Edit your registry configuration YAML file:
 
-    ```yaml
-    storage:
-      s3:
-        accesskey: 'AKIAKIAKI'
-        secretkey: 'secret123'
-        bucket: 'gitlab-registry-bucket-AKIAKIAKI'
-        region: 'your-s3-region'
-        regionendpoint: 'your-s3-regionendpoint'
-        encrypt: true
-    ```
+   ```yaml
+   storage:
+     s3:
+       accesskey: 'AKIAKIAKI'
+       secretkey: 'secret123'
+       bucket: 'gitlab-registry-bucket-AKIAKIAKI'
+       region: 'your-s3-region'
+       regionendpoint: 'your-s3-regionendpoint'
+       encrypt: true
+   ```
 
 1. Save the file and [restart GitLab](../restart_gitlab.md#installations-from-source)
    for the changes to take effect.
diff --git a/doc/administration/postgresql/external.md b/doc/administration/postgresql/external.md
index 8605ee94255..24548f690ff 100644
--- a/doc/administration/postgresql/external.md
+++ b/doc/administration/postgresql/external.md
@@ -30,18 +30,18 @@ If you use a cloud-managed service, or provide your own PostgreSQL instance:
 1. Configure the GitLab application servers with the appropriate connection details
    for your external PostgreSQL service in your `/etc/gitlab/gitlab.rb` file:
 
-    ```ruby
-    # Disable the bundled Omnibus provided PostgreSQL
-    postgresql['enable'] = false
-
-    # PostgreSQL connection details
-    gitlab_rails['db_adapter'] = 'postgresql'
-    gitlab_rails['db_encoding'] = 'unicode'
-    gitlab_rails['db_host'] = '10.1.0.5' # IP/hostname of database server
-    gitlab_rails['db_password'] = 'DB password'
-    ```
-
-    For more information on GitLab multi-node setups, refer to the [reference architectures](../reference_architectures/index.md).
+   ```ruby
+   # Disable the bundled Omnibus provided PostgreSQL
+   postgresql['enable'] = false
+
+   # PostgreSQL connection details
+   gitlab_rails['db_adapter'] = 'postgresql'
+   gitlab_rails['db_encoding'] = 'unicode'
+   gitlab_rails['db_host'] = '10.1.0.5' # IP/hostname of database server
+   gitlab_rails['db_password'] = 'DB password'
+   ```
+
+   For more information on GitLab multi-node setups, refer to the [reference architectures](../reference_architectures/index.md).
 
 1. Reconfigure for the changes to take effect:
 
diff --git a/doc/administration/read_only_gitlab.md b/doc/administration/read_only_gitlab.md
index 3718741e2e9..3842cf0846b 100644
--- a/doc/administration/read_only_gitlab.md
+++ b/doc/administration/read_only_gitlab.md
@@ -70,28 +70,28 @@ the database is read-only:
    in case things don't go as expected.
 1. Enter PostgreSQL on the console as an administrator user:
 
-    ```shell
-    sudo \
-        -u gitlab-psql /opt/gitlab/embedded/bin/psql \
-        -h /var/opt/gitlab/postgresql gitlabhq_production
-    ```
+   ```shell
+   sudo \
+       -u gitlab-psql /opt/gitlab/embedded/bin/psql \
+       -h /var/opt/gitlab/postgresql gitlabhq_production
+   ```
 
 1. Create the `gitlab_read_only` user. The password is set to `mypassword`,
    change that to your liking:
 
-    ```sql
-    -- NOTE: Use the password defined earlier
-    CREATE USER gitlab_read_only WITH password 'mypassword';
-    GRANT CONNECT ON DATABASE gitlabhq_production to gitlab_read_only;
-    GRANT USAGE ON SCHEMA public TO gitlab_read_only;
-    GRANT SELECT ON ALL TABLES IN SCHEMA public TO gitlab_read_only;
-    GRANT SELECT ON ALL SEQUENCES IN SCHEMA public TO gitlab_read_only;
-
-    -- Tables created by "gitlab" should be made read-only for "gitlab_read_only"
-    -- automatically.
-    ALTER DEFAULT PRIVILEGES FOR USER gitlab IN SCHEMA public GRANT SELECT ON TABLES TO gitlab_read_only;
-    ALTER DEFAULT PRIVILEGES FOR USER gitlab IN SCHEMA public GRANT SELECT ON SEQUENCES TO gitlab_read_only;
-    ```
+   ```sql
+   -- NOTE: Use the password defined earlier
+   CREATE USER gitlab_read_only WITH password 'mypassword';
+   GRANT CONNECT ON DATABASE gitlabhq_production to gitlab_read_only;
+   GRANT USAGE ON SCHEMA public TO gitlab_read_only;
+   GRANT SELECT ON ALL TABLES IN SCHEMA public TO gitlab_read_only;
+   GRANT SELECT ON ALL SEQUENCES IN SCHEMA public TO gitlab_read_only;
+
+   -- Tables created by "gitlab" should be made read-only for "gitlab_read_only"
+   -- automatically.
+   ALTER DEFAULT PRIVILEGES FOR USER gitlab IN SCHEMA public GRANT SELECT ON TABLES TO gitlab_read_only;
+   ALTER DEFAULT PRIVILEGES FOR USER gitlab IN SCHEMA public GRANT SELECT ON SEQUENCES TO gitlab_read_only;
+   ```
 
 1. Get the hashed password of the `gitlab_read_only` user and copy the result:
 
@@ -101,10 +101,10 @@ the database is read-only:
 
 1. Edit `/etc/gitlab/gitlab.rb` and add the password from the previous step:
 
-    ```ruby
-    postgresql['sql_user_password'] = 'a2e20f823772650f039284619ab6f239'
-    postgresql['sql_user'] = "gitlab_read_only"
-    ```
+   ```ruby
+   postgresql['sql_user_password'] = 'a2e20f823772650f039284619ab6f239'
+   postgresql['sql_user'] = "gitlab_read_only"
+   ```
 
 1. Reconfigure GitLab and restart PostgreSQL:
 
diff --git a/doc/administration/redis/replication_and_failover_external.md b/doc/administration/redis/replication_and_failover_external.md
index 23c9ce33c2d..16383db6c2a 100644
--- a/doc/administration/redis/replication_and_failover_external.md
+++ b/doc/administration/redis/replication_and_failover_external.md
@@ -32,15 +32,15 @@ Note the Redis node's IP address or hostname, port, and password (if required).
 1. Configure the GitLab application servers with the appropriate connection details
    for your external Redis service in your `/etc/gitlab/gitlab.rb` file:
 
-    ```ruby
-    redis['enable'] = false
+   ```ruby
+   redis['enable'] = false
 
-    gitlab_rails['redis_host'] = 'redis.example.com'
-    gitlab_rails['redis_port'] = 6379
+   gitlab_rails['redis_host'] = 'redis.example.com'
+   gitlab_rails['redis_port'] = 6379
 
-    # Required if Redis authentication is configured on the Redis node
-    gitlab_rails['redis_password'] = 'Redis Password'
-    ```
+   # Required if Redis authentication is configured on the Redis node
+   gitlab_rails['redis_password'] = 'Redis Password'
+   ```
 
 1. Reconfigure for the changes to take effect:
 
diff --git a/doc/administration/sidekiq/index.md b/doc/administration/sidekiq/index.md
index 3e6708024f6..388596532d4 100644
--- a/doc/administration/sidekiq/index.md
+++ b/doc/administration/sidekiq/index.md
@@ -325,7 +325,7 @@ To enable LDAP with the synchronization worker for Sidekiq:
 
 1. Edit `/etc/gitlab/gitlab.rb`:
 
-    ```ruby
+   ```ruby
    gitlab_rails['ldap_enabled'] = true
    gitlab_rails['prevent_ldap_sign_in'] = false
    gitlab_rails['ldap_servers'] = {
diff --git a/doc/api/graphql/reference/index.md b/doc/api/graphql/reference/index.md
index f6ac330f645..57d92512e8a 100644
--- a/doc/api/graphql/reference/index.md
+++ b/doc/api/graphql/reference/index.md
@@ -14760,6 +14760,7 @@ four standard [pagination arguments](#connection-pagination-arguments):
 
 | Name | Type | Description |
 | ---- | ---- | ----------- |
+| <a id="groupprojectscomplianceframeworkfilters"></a>`complianceFrameworkFilters` | [`ComplianceFrameworkFilters`](#complianceframeworkfilters) | Filters applied when selecting a compliance framework. |
 | <a id="groupprojectshascodecoverage"></a>`hasCodeCoverage` | [`Boolean`](#boolean) | Returns only the projects which have code coverage. |
 | <a id="groupprojectshasvulnerabilities"></a>`hasVulnerabilities` | [`Boolean`](#boolean) | Returns only the projects which have vulnerabilities. |
 | <a id="groupprojectsids"></a>`ids` | [`[ID!]`](#id) | Filter projects by IDs. |
@@ -17080,6 +17081,7 @@ four standard [pagination arguments](#connection-pagination-arguments):
 
 | Name | Type | Description |
 | ---- | ---- | ----------- |
+| <a id="namespaceprojectscomplianceframeworkfilters"></a>`complianceFrameworkFilters` | [`ComplianceFrameworkFilters`](#complianceframeworkfilters) | Filters applied when selecting a compliance framework. |
 | <a id="namespaceprojectshascodecoverage"></a>`hasCodeCoverage` | [`Boolean`](#boolean) | Returns only the projects which have code coverage. |
 | <a id="namespaceprojectshasvulnerabilities"></a>`hasVulnerabilities` | [`Boolean`](#boolean) | Returns only the projects which have vulnerabilities. |
 | <a id="namespaceprojectsids"></a>`ids` | [`[ID!]`](#id) | Filter projects by IDs. |
@@ -25742,6 +25744,14 @@ Attributes for defining a CI/CD variable.
 | <a id="commitactionlastcommitid"></a>`lastCommitId` | [`String`](#string) | Last known file commit ID. |
 | <a id="commitactionpreviouspath"></a>`previousPath` | [`String`](#string) | Original full path to the file being moved. |
 
+### `ComplianceFrameworkFilters`
+
+#### Arguments
+
+| Name | Type | Description |
+| ---- | ---- | ----------- |
+| <a id="complianceframeworkfiltersid"></a>`id` | [`ComplianceManagementFrameworkID`](#compliancemanagementframeworkid) | ID of the compliance framework. |
+
 ### `ComplianceFrameworkInput`
 
 #### Arguments
diff --git a/doc/architecture/blueprints/runner_tokens/index.md b/doc/architecture/blueprints/runner_tokens/index.md
index 789869cdc16..8c9c8f63dae 100644
--- a/doc/architecture/blueprints/runner_tokens/index.md
+++ b/doc/architecture/blueprints/runner_tokens/index.md
@@ -379,35 +379,37 @@ scope.
 | GitLab Rails app | `%15.9` | Implement the `create_runner_workflow`  [feature flag](../../../administration/feature_flags.md). |
 | GitLab Rails app | `%15.9` | Implement `create_{instance|group|project}_runner` permissions. |
 | GitLab Rails app | `%15.9` | Rename `ci_runner_machines.machine_xid` column to `system_xid` to be consistent with `system_id` passed in APIs. |
-| GitLab Rails app | `%15.10` | Drop `ci_runner_machines.machine_xid` column. |
-| GitLab Rails app | `%15.11` | Remove the ignore rule for `ci_runner_machines.machine_xid` column. |
+| GitLab Rails app | `%15.10` | Remove the ignore rule for `ci_runner_machines.machine_xid` column. |
 | GitLab Rails app | `%15.10` | Replace `ci_builds_metadata.runner_machine_id` with a new join table. |
-| GitLab Rails app | %15.11 | Drop `ci_builds_metadata.runner_machine_id` column. |
-| GitLab Rails app | %16.0 | Remove the ignore rule for `ci_builds_metadata.runner_machine_id` column. |
+| GitLab Rails app | `%15.11` | Drop `ci_builds_metadata.runner_machine_id` column. |
+| GitLab Rails app | `%16.0` | Remove the ignore rule for `ci_builds_metadata.runner_machine_id` column. |
 
 ### Stage 4 - Create runners from the UI
 
 | Component        | Milestone | Changes |
 |------------------|----------:|---------|
-| GitLab Rails app | `%15.9` | Implement new GraphQL user-authenticated API to create a new runner. |
 | GitLab Rails app | `%15.9` | [Add prefix to newly generated runner authentication tokens](https://gitlab.com/gitlab-org/gitlab/-/issues/383198). |
+| GitLab Rails app | `%15.9` | Add new runner field for with token that is used in registration |
+| GitLab Rails app | `%15.9` | Implement new GraphQL user-authenticated API to create a new runner. |
 | GitLab Rails app | `%15.10` | Return token and runner ID information from `/runners/verify` REST endpoint. |
 | GitLab Runner    | `%15.10` | [Modify register command to allow new flow with glrt- prefixed authentication tokens](https://gitlab.com/gitlab-org/gitlab-runner/-/issues/29613). |
-| GitLab Rails app | `%15.10` | Implement UI to create new runner. |
-| GitLab Rails app | `%15.10` | GraphQL changes to `CiRunner` type. |
-| GitLab Rails app | `%15.10` | UI changes to runner details view (listing of platform, architecture, IP address, etc.) (?) |
-| GitLab Rails app | `%15.11` | Adapt `POST /api/v4/runners` REST endpoint to accept a request from an authorized user with a scope instead of a registration token. |
+| GitLab Rails app | `%15.11` | Define feature flag and policies for "New Runner creation workflow" for groups and projects. |
+| GitLab Rails app | `%15.11` | Update service and mutation to accept groups and projects. |
+| GitLab Rails app | `%15.11` | Implement UI to create new runner. |
+| GitLab Rails app | `%15.11` | GraphQL changes to `CiRunner` type. (?) |
+| GitLab Rails app | `%15.11` | UI changes to runner details view (listing of platform, architecture, IP address, etc.) (?) |
+| GitLab Rails app | `%15.11` | Adapt `POST /api/v4/runners` REST endpoint to accept a request from an authorized user with a scope instead of a registration token. || GitLab Rails app | `%15.9` | Implement new GraphQL user-authenticated API to create a new runner. |
 
 ### Stage 5 - Optional disabling of registration token
 
 | Component        | Milestone | Changes |
 |------------------|----------:|---------|
-| GitLab Rails app | `%15.11` | Adapt `register_{group|project}_runner` permissions to take [application setting](https://gitlab.com/gitlab-org/gitlab/-/issues/386712) in consideration. |
-| GitLab Rails app | `%15.11` | Add UI to allow disabling use of registration tokens at project or group level. |
-| GitLab Rails app | `%15.11` | Introduce `:enforce_create_runner_workflow` feature flag (disabled by default) to control whether use of registration tokens is allowed. |
-| GitLab Rails app | `%15.11` | Make [`POST /api/v4/runners` endpoint](../../../api/runners.md#register-a-new-runner) permanently return `HTTP 410 Gone` if either `allow_runner_registration_token` setting or `:enforce_create_runner_workflow` feature flag disables registration tokens.<br/>A future v5 version of the API should return `HTTP 404 Not Found`. |
-| GitLab Rails app | `%15.11` | Start refusing job requests that don't include a unique ID, if either `allow_runner_registration_token` setting or `:enforce_create_runner_workflow` feature flag disables registration tokens. |
-| GitLab Rails app | `%15.11` | Hide legacy UI showing registration with a registration token, if `:enforce_create_runner_workflow` feature flag disables registration tokens. |
+| GitLab Rails app | | Adapt `register_{group|project}_runner` permissions to take [application setting](https://gitlab.com/gitlab-org/gitlab/-/issues/386712) in consideration. |
+| GitLab Rails app | | Add UI to allow disabling use of registration tokens at project or group level. |
+| GitLab Rails app | | Introduce `:enforce_create_runner_workflow` feature flag (disabled by default) to control whether use of registration tokens is allowed. |
+| GitLab Rails app | | Make [`POST /api/v4/runners` endpoint](../../../api/runners.md#register-a-new-runner) permanently return `HTTP 410 Gone` if either `allow_runner_registration_token` setting or `:enforce_create_runner_workflow` feature flag disables registration tokens.<br/>A future v5 version of the API should return `HTTP 404 Not Found`. |
+| GitLab Rails app | | Start refusing job requests that don't include a unique ID, if either `allow_runner_registration_token` setting or `:enforce_create_runner_workflow` feature flag disables registration tokens. |
+| GitLab Rails app | | Hide legacy UI showing registration with a registration token, if `:enforce_create_runner_workflow` feature flag disables registration tokens. |
 
 ### Stage 6 - Enforcement
 
diff --git a/doc/development/advanced_search.md b/doc/development/advanced_search.md
index d326f1fdb99..4e61098b17d 100644
--- a/doc/development/advanced_search.md
+++ b/doc/development/advanced_search.md
@@ -4,7 +4,7 @@ group: Global Search
 info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments
 ---
 
-# Advanced search development
+# Advanced search development guidelines
 
 This page includes information about developing and working with Elasticsearch.
 
diff --git a/doc/development/audit_event_guide/index.md b/doc/development/audit_event_guide/index.md
index 8df5121a2f7..c7c723d1686 100644
--- a/doc/development/audit_event_guide/index.md
+++ b/doc/development/audit_event_guide/index.md
@@ -4,7 +4,7 @@ group: Compliance
 info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments
 ---
 
-# Audit Event Guide
+# Audit event development guidelines
 
 This guide provides an overview of how Audit Events work, and how to instrument
 new audit events.
diff --git a/doc/development/auto_devops.md b/doc/development/auto_devops.md
index 53033cd19ff..b2281f9c032 100644
--- a/doc/development/auto_devops.md
+++ b/doc/development/auto_devops.md
@@ -4,7 +4,7 @@ group: Configure
 info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments
 ---
 
-# Auto DevOps development guide
+# Auto DevOps development guidelines
 
 This document provides a development guide for contributors to
 [Auto DevOps](../topics/autodevops/index.md).
diff --git a/doc/development/backend/create_source_code_be/index.md b/doc/development/backend/create_source_code_be/index.md
index 77c98982210..ba0ed2a2867 100644
--- a/doc/development/backend/create_source_code_be/index.md
+++ b/doc/development/backend/create_source_code_be/index.md
@@ -4,16 +4,16 @@ group: Source Code
 info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments
 ---
 
-# Create: Source Code Backend
+# Create: Source Code backend
 
-The Create:Source Code BE team focuses on the GitLab suite of Source Code Management
+The Create: Source Code backend (BE) team focuses on the GitLab suite of Source Code Management
 (SCM) tools. It is responsible for all backend aspects of the product categories
 that fall under the [Source Code group](https://about.gitlab.com/handbook/product/categories/#source-code-group)
 of the [Create stage](https://about.gitlab.com/handbook/product/categories/#create-stage)
 of the [DevOps lifecycle](https://about.gitlab.com/handbook/product/categories/#devops-stages).
 
 We interface with the Gitaly and Code Review teams, and work closely with the
-[Create:Source Code Frontend team](https://about.gitlab.com/handbook/engineering/development/dev/create/create-source-code-fe/). The features
+[Create: Source Code frontend team](https://about.gitlab.com/handbook/engineering/development/dev/create/create-source-code-fe/). The features
 we work with are listed on the
 [Features by Group Page](https://about.gitlab.com/handbook/product/categories/features/#createsource-code-group).
 
diff --git a/doc/development/cicd/index.md b/doc/development/cicd/index.md
index 641d0ea4f6f..2e2907feae1 100644
--- a/doc/development/cicd/index.md
+++ b/doc/development/cicd/index.md
@@ -5,7 +5,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w
 type: index, concepts, howto
 ---
 
-# CI/CD development documentation
+# CI/CD development guidelines
 
 Development guides that are specific to CI/CD are listed here:
 
diff --git a/doc/development/code_intelligence/index.md b/doc/development/code_intelligence/index.md
index 107a1588e18..2034f57d995 100644
--- a/doc/development/code_intelligence/index.md
+++ b/doc/development/code_intelligence/index.md
@@ -4,7 +4,7 @@ group: Code Review
 info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments
 ---
 
-# Code Intelligence
+# Code intelligence development guidelines
 
 > [Introduced](https://gitlab.com/groups/gitlab-org/-/epics/1576) in GitLab 13.1.
 
diff --git a/doc/development/contributing/style_guides.md b/doc/development/contributing/style_guides.md
index 28ce8e6ff4b..36b38e2e16b 100644
--- a/doc/development/contributing/style_guides.md
+++ b/doc/development/contributing/style_guides.md
@@ -5,7 +5,7 @@ group: Development
 info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments
 ---
 
-# Style guides
+# Development style guides
 
 ## Editor/IDE styling standardization
 
diff --git a/doc/development/database/index.md b/doc/development/database/index.md
index eaf37cd7699..2cb8509e203 100644
--- a/doc/development/database/index.md
+++ b/doc/development/database/index.md
@@ -4,7 +4,7 @@ group: Database
 info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments
 ---
 
-# Database guides
+# Database development guidelines
 
 ## Database Reviews
 
diff --git a/doc/development/distributed_tracing.md b/doc/development/distributed_tracing.md
index 79d0ff84713..bd9e7035290 100644
--- a/doc/development/distributed_tracing.md
+++ b/doc/development/distributed_tracing.md
@@ -4,7 +4,7 @@ group: Respond
 info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments
 ---
 
-# Distributed Tracing - development guidelines
+# Distributed tracing development guidelines
 
 GitLab is instrumented for distributed tracing. Distributed Tracing in GitLab is currently considered **experimental**, as it has not yet been tested at scale on GitLab.com.
 
diff --git a/doc/development/fe_guide/style/index.md b/doc/development/fe_guide/style/index.md
index 94ed9544cf5..552b769d6f6 100644
--- a/doc/development/fe_guide/style/index.md
+++ b/doc/development/fe_guide/style/index.md
@@ -4,7 +4,7 @@ group: unassigned
 info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments
 ---
 
-# GitLab development style guides
+# Frontend style guides
 
 See below for the relevant style guides, guidelines, linting, and other information for developing GitLab.
 
diff --git a/doc/development/gemfile.md b/doc/development/gemfile.md
index 36ef1bcd834..bfe8b7c5205 100644
--- a/doc/development/gemfile.md
+++ b/doc/development/gemfile.md
@@ -4,7 +4,7 @@ group: unassigned
 info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments
 ---
 
-# Gemfile guidelines
+# Gemfile development guidelines
 
 When adding a new entry to `Gemfile`, or upgrading an existing dependency pay
 attention to the following rules.
diff --git a/doc/development/gitaly.md b/doc/development/gitaly.md
index b4f5501ccac..5b481661e7d 100644
--- a/doc/development/gitaly.md
+++ b/doc/development/gitaly.md
@@ -4,7 +4,7 @@ group: Gitaly
 info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments
 ---
 
-# Gitaly developers guide
+# Gitaly development guidelines
 
 [Gitaly](https://gitlab.com/gitlab-org/gitaly) is a high-level Git RPC service used by GitLab Rails,
 Workhorse and GitLab Shell.
diff --git a/doc/development/gitlab_flavored_markdown/index.md b/doc/development/gitlab_flavored_markdown/index.md
index f115ae9a11c..064a7ecbfa9 100644
--- a/doc/development/gitlab_flavored_markdown/index.md
+++ b/doc/development/gitlab_flavored_markdown/index.md
@@ -6,7 +6,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w
 
 <!-- vale gitlab.GitLabFlavoredMarkdown = NO -->
 
-# GitLab Flavored Markdown (GLFM) developer documentation
+# GitLab Flavored Markdown (GLFM) development guidelines
 
 This page contains the MVC for the developer documentation for GitLab Flavored Markdown (GLFM).
 For the user documentation about Markdown in GitLab, refer to
diff --git a/doc/development/gitlab_shell/index.md b/doc/development/gitlab_shell/index.md
index 7097fd48cea..9dc8d8e01c5 100644
--- a/doc/development/gitlab_shell/index.md
+++ b/doc/development/gitlab_shell/index.md
@@ -4,7 +4,7 @@ group: Source Code
 info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/engineering/ux/technical-writing/#assignments
 ---
 
-# GitLab Shell
+# GitLab Shell development guidelines
 
 [![pipeline status](https://gitlab.com/gitlab-org/gitlab-shell/badges/main/pipeline.svg)](https://gitlab.com/gitlab-org/gitlab-shell/-/pipelines?ref=main) [![coverage report](https://gitlab.com/gitlab-org/gitlab-shell/badges/main/coverage.svg)](https://gitlab.com/gitlab-org/gitlab-shell/-/pipelines?ref=main) [![Code Climate](https://codeclimate.com/github/gitlabhq/gitlab-shell.svg)](https://codeclimate.com/github/gitlabhq/gitlab-shell)
 
diff --git a/doc/development/integrations/index.md b/doc/development/integrations/index.md
index b9c05429bd3..6f42cb4d4fe 100644
--- a/doc/development/integrations/index.md
+++ b/doc/development/integrations/index.md
@@ -5,7 +5,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w
 description: "GitLab's development guidelines for Integrations"
 ---
 
-# Integrations development guide
+# Integrations development guidelines
 
 This page provides development guidelines for implementing [GitLab integrations](../../user/project/integrations/index.md),
 which are part of our [main Rails project](https://gitlab.com/gitlab-org/gitlab).
diff --git a/doc/development/integrations/jira_connect.md b/doc/development/integrations/jira_connect.md
index 0b1fc8c6124..4789280c09d 100644
--- a/doc/development/integrations/jira_connect.md
+++ b/doc/development/integrations/jira_connect.md
@@ -4,7 +4,7 @@ group: Integrations
 info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments
 ---
 
-# Set up a development environment
+# Set up a Jira development environment
 
 The following are required to install and test the app:
 
diff --git a/doc/development/json.md b/doc/development/json.md
index 8a2575401fb..bdb7f73ab62 100644
--- a/doc/development/json.md
+++ b/doc/development/json.md
@@ -4,7 +4,7 @@ group: unassigned
 info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments
 ---
 
-# JSON Guidelines
+# JSON development guidelines
 
 At GitLab we handle a lot of JSON data. To best ensure we remain performant
 when handling large JSON encodes or decodes, we use our own JSON class
diff --git a/doc/development/kubernetes.md b/doc/development/kubernetes.md
index e44e2af4371..99737e71b22 100644
--- a/doc/development/kubernetes.md
+++ b/doc/development/kubernetes.md
@@ -4,7 +4,7 @@ group: Configure
 info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments
 ---
 
-# Kubernetes integration - development guidelines
+# Kubernetes integration development guidelines
 
 This document provides various guidelines when developing for the GitLab
 [Kubernetes integration](../user/infrastructure/clusters/index.md).
diff --git a/doc/development/lfs.md b/doc/development/lfs.md
index ec91f9f3c8b..7f44d12ed95 100644
--- a/doc/development/lfs.md
+++ b/doc/development/lfs.md
@@ -4,7 +4,7 @@ group: Source Code
 info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments
 ---
 
-# Git LFS developer information
+# Git LFS development guidelines
 
 This page contains developer-centric information for GitLab team members. For the
 user documentation, see [Git Large File Storage](../topics/git/lfs/index.md).
diff --git a/doc/development/logging.md b/doc/development/logging.md
index 538fc7ccfe1..5b9a311c704 100644
--- a/doc/development/logging.md
+++ b/doc/development/logging.md
@@ -4,7 +4,7 @@ group: Respond
 info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments
 ---
 
-# GitLab Developers Guide to Logging
+# Logging development guidelines
 
 [GitLab Logs](../administration/logs/index.md) play a critical role for both
 administrators and GitLab team members to diagnose problems in the field.
diff --git a/doc/development/merge_request_concepts/approval_rules.md b/doc/development/merge_request_concepts/approval_rules.md
index d119644cd7c..d6000d48706 100644
--- a/doc/development/merge_request_concepts/approval_rules.md
+++ b/doc/development/merge_request_concepts/approval_rules.md
@@ -4,7 +4,7 @@ group: Code Review
 info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments
 ---
 
-# Approval Rules development guide
+# Approval rules development guidelines
 
 This document explains the backend design and flow of all related functionality
 about [merge request approval rules](../../user/project/merge_requests/approvals/index.md).
diff --git a/doc/development/packages/index.md b/doc/development/packages/index.md
index fa0e9f5d926..4f027825422 100644
--- a/doc/development/packages/index.md
+++ b/doc/development/packages/index.md
@@ -4,7 +4,7 @@ group: Package Registry
 info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments
 ---
 
-# Package and container registry documentation
+# Package and container registry development guidelines
 
 The documentation for package and container registry development is split into two groups.
 
diff --git a/doc/development/permissions.md b/doc/development/permissions.md
index 6ce2b855e64..b4c8614a9fa 100644
--- a/doc/development/permissions.md
+++ b/doc/development/permissions.md
@@ -4,7 +4,7 @@ group: Authentication and Authorization
 info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments
 ---
 
-# Implementing permissions
+# Permission development guidelines
 
 There are multiple types of permissions across GitLab, and when implementing
 anything that deals with permissions, all of them should be considered.
diff --git a/doc/development/product_qualified_lead_guide/index.md b/doc/development/product_qualified_lead_guide/index.md
index c72110bc253..41237dcdff4 100644
--- a/doc/development/product_qualified_lead_guide/index.md
+++ b/doc/development/product_qualified_lead_guide/index.md
@@ -4,7 +4,7 @@ group: Acquisition
 info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments
 ---
 
-# Product Qualified Lead (PQL) development guide
+# Product Qualified Lead (PQL) development guidelines
 
 The Product Qualified Lead (PQL) funnel connects our users with our team members. Read more about [PQL product principles](https://about.gitlab.com/handbook/product/product-principles/#product-qualified-leads-pqls).
 
diff --git a/doc/development/prometheus_metrics.md b/doc/development/prometheus_metrics.md
index 834a20239fc..590ac547c2d 100644
--- a/doc/development/prometheus_metrics.md
+++ b/doc/development/prometheus_metrics.md
@@ -4,7 +4,7 @@ group: Respond
 info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments
 ---
 
-# Working with Prometheus Metrics
+# Prometheus metrics development guidelines
 
 ## Adding to the library
 
diff --git a/doc/development/python_guide/index.md b/doc/development/python_guide/index.md
index 08d2f46c1cd..e9b52b81c0e 100644
--- a/doc/development/python_guide/index.md
+++ b/doc/development/python_guide/index.md
@@ -4,7 +4,7 @@ group: unassigned
 info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments
 ---
 
-# Python Development Guidelines
+# Python development guidelines
 
 GitLab requires Python as a dependency for [reStructuredText](https://docutils.sourceforge.io/rst.html)
 markup rendering.
diff --git a/doc/development/real_time.md b/doc/development/real_time.md
index 2aa48fed8eb..99d09170646 100644
--- a/doc/development/real_time.md
+++ b/doc/development/real_time.md
@@ -4,7 +4,7 @@ group: Project Management
 info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments
 ---
 
-# Real-Time Features
+# Real-time features
 
 This guide contains instructions on how to safely roll out new real-time
 features.
diff --git a/doc/development/redis.md b/doc/development/redis.md
index 68cab9ac38d..e8c781c40be 100644
--- a/doc/development/redis.md
+++ b/doc/development/redis.md
@@ -4,7 +4,7 @@ group: unassigned
 info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments
 ---
 
-# Redis guidelines
+# Redis development guidelines
 
 ## Redis instances
 
diff --git a/doc/development/rubocop_development_guide.md b/doc/development/rubocop_development_guide.md
index 10c129abaaa..fe09bfbce2c 100644
--- a/doc/development/rubocop_development_guide.md
+++ b/doc/development/rubocop_development_guide.md
@@ -5,7 +5,7 @@ group: Development
 info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments
 ---
 
-# RuboCop rule development guide
+# RuboCop rule development guidelines
 
 Our codebase style is defined and enforced by [RuboCop](https://github.com/rubocop-hq/rubocop).
 
diff --git a/doc/development/sec/index.md b/doc/development/sec/index.md
index 9d9a4752cc2..f74d31a1fb3 100644
--- a/doc/development/sec/index.md
+++ b/doc/development/sec/index.md
@@ -5,7 +5,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w
 type: index, concepts, howto
 ---
 
-# Sec section development
+# Sec section development guidelines
 
 The Sec section is responsible for GitLab application security features, the "Sec" part of
 DevSecOps. Development guides that are specific to the Sec section are listed here.
diff --git a/doc/development/secure_coding_guidelines.md b/doc/development/secure_coding_guidelines.md
index 12665acacff..259d4bf969d 100644
--- a/doc/development/secure_coding_guidelines.md
+++ b/doc/development/secure_coding_guidelines.md
@@ -5,7 +5,7 @@ group: Development
 info: "See the Technical Writers assigned to Development Guidelines: https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments-to-development-guidelines"
 ---
 
-# Secure Coding Guidelines
+# Secure coding development guidelines
 
 This document contains descriptions and guidelines for addressing security
 vulnerabilities commonly identified in the GitLab codebase. They are intended
diff --git a/doc/development/service_ping/index.md b/doc/development/service_ping/index.md
index a5fc28b8d19..e938de9e253 100644
--- a/doc/development/service_ping/index.md
+++ b/doc/development/service_ping/index.md
@@ -4,7 +4,7 @@ group: Product Intelligence
 info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments
 ---
 
-# Service Ping Guide
+# Service Ping development guidelines
 
 > - Introduced in GitLab Ultimate 11.2, more statistics.
 > - In GitLab 14.1, [renamed from Usage Ping to Service Ping](https://gitlab.com/groups/gitlab-org/-/epics/5990). In 14.0 and earlier, use the Usage Ping documentation for the Rails commands appropriate to your version.
diff --git a/doc/development/shell_commands.md b/doc/development/shell_commands.md
index d78a005d76b..25f62fbcc98 100644
--- a/doc/development/shell_commands.md
+++ b/doc/development/shell_commands.md
@@ -4,7 +4,7 @@ group: unassigned
 info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments
 ---
 
-# Guidelines for shell commands in the GitLab codebase
+# Shell command development guidelines
 
 This document contains guidelines for working with processes and files in the GitLab codebase.
 These guidelines are meant to make your code more reliable _and_ secure.
diff --git a/doc/development/sidekiq/index.md b/doc/development/sidekiq/index.md
index 355f5a3b753..2010a21130d 100644
--- a/doc/development/sidekiq/index.md
+++ b/doc/development/sidekiq/index.md
@@ -4,7 +4,7 @@ group: unassigned
 info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments
 ---
 
-# Sidekiq guides
+# Sidekiq development guidelines
 
 We use [Sidekiq](https://github.com/mperham/sidekiq) as our background
 job processor. These guides are for writing jobs that works well on
diff --git a/doc/development/snowplow/index.md b/doc/development/snowplow/index.md
index 6acbd72175e..276b5913890 100644
--- a/doc/development/snowplow/index.md
+++ b/doc/development/snowplow/index.md
@@ -4,7 +4,7 @@ group: Product Intelligence
 info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments
 ---
 
-# Snowplow
+# Snowplow development guidelines
 
 Snowplow is an enterprise-grade marketing and Product Intelligence platform that tracks how users engage with our website and application.
 
diff --git a/doc/development/uploads/index.md b/doc/development/uploads/index.md
index b5509f5934e..a62e8ea2d58 100644
--- a/doc/development/uploads/index.md
+++ b/doc/development/uploads/index.md
@@ -4,7 +4,7 @@ group: unassigned
 info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments
 ---
 
-# Uploads development guide
+# Uploads development guidelines
 
 Uploads are an integral part of many GitLab features. To understand how GitLab handles uploads, this page
 provides an overview of the key mechanisms for transferring files to a storage destination.
diff --git a/doc/development/value_stream_analytics.md b/doc/development/value_stream_analytics.md
index 77a32b62e32..aec8dbfc2fb 100644
--- a/doc/development/value_stream_analytics.md
+++ b/doc/development/value_stream_analytics.md
@@ -4,7 +4,7 @@ group: Optimize
 info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments
 ---
 
-# Value stream analytics development guide
+# Value stream analytics development guidelines
 
 For information on how to configure value stream analytics (VSA) in GitLab, see our [analytics documentation](../user/analytics/value_stream_analytics.md).
 
diff --git a/doc/development/wikis.md b/doc/development/wikis.md
index acb7ed335d3..2f97931f924 100644
--- a/doc/development/wikis.md
+++ b/doc/development/wikis.md
@@ -5,7 +5,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w
 description: "GitLab's development guidelines for Wikis"
 ---
 
-# Wikis development guide
+# Wikis development guidelines
 
 > [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/227027) in GitLab 13.5.
 
diff --git a/doc/user/packages/debian_repository/index.md b/doc/user/packages/debian_repository/index.md
index 3e04e105c39..5cfecc22ac5 100644
--- a/doc/user/packages/debian_repository/index.md
+++ b/doc/user/packages/debian_repository/index.md
@@ -23,6 +23,12 @@ Project and Group packages are supported.
 For documentation of the specific API endpoints that Debian package manager
 clients use, see the [Debian API documentation](../../../api/packages/debian.md).
 
+Prerequisites:
+
+- The `dpkg-deb` binary must be installed on the GitLab instance.
+  This binary is usually provided by the [`dpkg` package](https://wiki.debian.org/Teams/Dpkg/Downstream),
+  installed by default on Debian and derivatives.
+
 ## Enable the Debian API **(FREE SELF)**
 
 Debian repository support is still a work in progress. It's gated behind a feature flag that's