Add latest changes from gitlab-org/gitlab@master

8 files changed, 112 insertions, 111 deletions

diff --git a/doc/administration/audit_events.md b/doc/administration/audit_events.md
index a600a4d7501..f590229f79e 100644
--- a/doc/administration/audit_events.md
+++ b/doc/administration/audit_events.md
@@ -316,12 +316,9 @@ The following actions on projects generate project audit events:
 
 ### GitLab agent for Kubernetes events
 
-The following actions on projects generate agent audit events:
+> [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/382133) in GitLab 15.10.
 
-- A cluster agent token is created.
-  Introduced in GitLab 15.9
-- A cluster agent token is revoked.
-  Introduced in GitLab 15.9
+GitLab generates audit events when a cluster agent token is created or revoked.
 
 ### Instance events **(PREMIUM SELF)**
 
@@ -364,23 +361,18 @@ Instance events can also be accessed using the [Instance Audit Events API](../ap
 
 ### GitLab Runner events
 
-The following GitLab Runner actions generate instance audit events:
-
-- [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/335509) in GitLab 14.8:
-  - Registered instance runner.
-  - Registered group runner.
-  - Registered project runner.
-- [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/355637) in GitLab 15.0. and [deprecated](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/102579) in GitLab 15.6:
-  - Reset instance runner registration token.
-  - Reset group runner registration token.
-  - Reset project runner registration token.
-- [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/349542) in GitLab 14.9.
-  - Assigned runner to project.
-  - Unassigned runner from project.
-- [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/349540) in GitLab 14.9.
-  - Unregistered instance runner.
-  - Unregistered group runner.
-  - Unregistered project runner.
+> - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/335509) in GitLab 14.8, audit events for when a runner is registered.
+> - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/349540) in GitLab 14.9, audit events for when a runner is unregistered.
+> - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/349542) in GitLab 14.9, audit events for when a runner is assigned to or unassigned from a project.
+> - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/355637) in GitLab 15.0, audit events for when a runner registration token is reset.
+
+GitLab generates audit events for the following GitLab Runner actions:
+
+- Instance, group, or project runner is registered.
+- Instance, group, or project runner is unregistered.
+- Runner is assigned to or unassigned from a project.
+- Instance, group, or project runner registration token is reset.
+  [Deprecated](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/102579) in GitLab 15.6.
 
 ## "Deleted User" events
 
diff --git a/doc/api/keys.md b/doc/api/keys.md
index 90144310238..337758e6c33 100644
--- a/doc/api/keys.md
+++ b/doc/api/keys.md
@@ -11,15 +11,15 @@ If using a SHA256 fingerprint in an API call, you should URL-encode the fingerpr
 
 ## Get SSH key with user by ID of an SSH key
 
-Get SSH key with user by ID of an SSH key. Note only administrators can lookup SSH key with user by ID of an SSH key.
+Get SSH key with user by ID of an SSH key. Only available to administrators.
 
 ```plaintext
 GET /keys/:id
 ```
 
-| Attribute | Type    | Required | Description          |
-|:----------|:--------|:---------|:---------------------|
-| `id`      | integer | yes      | The ID of an SSH key |
+| Attribute | Type    | Required | Description           |
+|:----------|:--------|:---------|:----------------------|
+| `id`      | integer | yes      | The ID of an SSH key. |
 
 Example request:
 
@@ -78,9 +78,9 @@ You can search for a user that owns a specific SSH key. Note only administrators
 GET /keys
 ```
 
-| Attribute     | Type   | Required | Description                   |
-|:--------------|:-------|:---------|:------------------------------|
-| `fingerprint` | string | yes      | The fingerprint of an SSH key |
+| Attribute     | Type   | Required | Description                    |
+|:--------------|:-------|:---------|:-------------------------------|
+| `fingerprint` | string | yes      | The fingerprint of an SSH key. |
 
 Example request:
 
diff --git a/doc/api/project_import_export.md b/doc/api/project_import_export.md
index f09e4d2785a..9728332f8f8 100644
--- a/doc/api/project_import_export.md
+++ b/doc/api/project_import_export.md
@@ -46,14 +46,15 @@ POST /projects/:id/export
 
 | Attribute | Type           | Required | Description                              |
 | --------- | -------------- | -------- | ---------------------------------------- |
-| `id`      | integer/string | yes      | The ID or [URL-encoded path of the project](rest/index.md#namespaced-path-encoding) owned by the authenticated user |
-| `description`      | string | no | Overrides the project description |
-| `upload`      | hash | no | Hash that contains the information to upload the exported project to a web server |
-| `upload[url]`      | string | yes      | The URL to upload the project |
-| `upload[http_method]`      | string | no      | The HTTP method to upload the exported project. Only `PUT` and `POST` methods allowed. Default is `PUT` |
+| `id`                  | integer or string | yes      | The ID or [URL-encoded path of the project](rest/index.md#namespaced-path-encoding) owned by the authenticated user.
+| `upload[url]`         | string | yes      | The URL to upload the project.
+| `description`         | string | no | Overrides the project description.
+| `upload`              | hash | no | Hash that contains the information to upload the exported project to a web server.
+| `upload[http_method]` | string | no      | The HTTP method to upload the exported project. Only `PUT` and `POST` methods allowed. Default is `PUT`.
 
 ```shell
-curl --request POST --header "PRIVATE-TOKEN: <your_access_token>" "https://gitlab.example.com/api/v4/projects/1/export" \
+curl --request POST --header "PRIVATE-TOKEN: <your_access_token>" \
+    "https://gitlab.example.com/api/v4/projects/1/export" \
     --data "upload[http_method]=PUT" \
     --data-urlencode "upload[url]=https://example-bucket.s3.eu-west-3.amazonaws.com/backup?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAIMBJHN2O62W8IELQ%2F20180312%2Feu-west-3%2Fs3%2Faws4_request&X-Amz-Date=20180312T110328Z&X-Amz-Expires=900&X-Amz-SignedHeaders=host&X-Amz-Signature=8413facb20ff33a49a147a0b4abcff4c8487cc33ee1f7e450c46e8f695569dbd"
 ```
@@ -74,10 +75,11 @@ GET /projects/:id/export
 
 | Attribute | Type           | Required | Description                              |
 | --------- | -------------- | -------- | ---------------------------------------- |
-| `id`      | integer/string | yes      | The ID or [URL-encoded path of the project](rest/index.md#namespaced-path-encoding) owned by the authenticated user |
+| `id`      | integer or string | yes      | The ID or [URL-encoded path of the project](rest/index.md#namespaced-path-encoding) owned by the authenticated user.
 
 ```shell
-curl --header "PRIVATE-TOKEN: <your_access_token>" "https://gitlab.example.com/api/v4/projects/1/export"
+curl --header "PRIVATE-TOKEN: <your_access_token>" \
+  "https://gitlab.example.com/api/v4/projects/1/export"
 ```
 
 Status can be one of:
@@ -120,9 +122,9 @@ Download the finished export.
 GET /projects/:id/export/download
 ```
 
-| Attribute | Type           | Required | Description                              |
-| --------- | -------------- | -------- | ---------------------------------------- |
-| `id`      | integer/string | yes      | The ID or [URL-encoded path of the project](rest/index.md#namespaced-path-encoding) owned by the authenticated user |
+| Attribute | Type              | Required | Description                              |
+| --------- | ----------------- | -------- | ---------------------------------------- |
+| `id`      | integer or string | yes      | The ID or [URL-encoded path of the project](rest/index.md#namespaced-path-encoding) owned by the authenticated user.
 
 ```shell
 curl --header "PRIVATE-TOKEN: <your_access_token>" --remote-header-name \
@@ -140,14 +142,14 @@ ls *export.tar.gz
 POST /projects/import
 ```
 
-| Attribute | Type           | Required | Description                              |
-| --------- | -------------- | -------- | ---------------------------------------- |
-| `namespace` | integer/string | no | The ID or path of the namespace to import the project to. Defaults to the current user's namespace.<br/><br/> Requires at least the Maintainer role on the destination group to import to. Using the Developer role for this purpose was [deprecated](https://gitlab.com/gitlab-org/gitlab/-/issues/387891) in GitLab 15.8 and will be removed in GitLab 16.0. |
-| `name` | string | no | The name of the project to be imported. Defaults to the path of the project if not provided |
-| `file` | string | yes | The file to be uploaded |
-| `path` | string | yes | Name and path for new project |
-| `overwrite` | boolean | no | If there is a project with the same path the import overwrites it. Default to false |
-| `override_params` | Hash | no | Supports all fields defined in the [Project API](projects.md) |
+| Attribute   | Type           | Required | Description                              |
+| ----------- | -------------- | -------- | ---------------------------------------- |
+| `file`      | string | yes | The file to be uploaded.
+| `path`      | string | yes | Name and path for new project.
+| `name`      | string | no | The name of the project to be imported. Defaults to the path of the project if not provided.
+| `namespace` | integer or string | no | The ID or path of the namespace to import the project to. Defaults to the current user's namespace.<br/><br/> Requires at least the Maintainer role on the destination group to import to. Using the Developer role for this purpose was [deprecated](https://gitlab.com/gitlab-org/gitlab/-/issues/387891) in GitLab 15.8 and is scheduled for removal in GitLab 16.0.
+| `override_params` | Hash | no | Supports all fields defined in the [Project API](projects.md).
+| `overwrite` | boolean | no | If there is a project with the same path the import overwrites it. Defaults to `false`.
 
 The override parameters passed take precedence over all values defined inside the export file.
 
@@ -196,39 +198,29 @@ requests.post(url, headers=headers, data=data, files=files)
 ```
 
 NOTE:
-The maximum import file size can be set by the Administrator, default is `0` (unlimited)..
+The maximum import file size can be set by the Administrator. It defaults to `0` (unlimited).
 As an administrator, you can modify the maximum import file size. To do so, use the `max_import_size` option in the [Application settings API](settings.md#change-application-settings) or the [Admin Area](../user/admin_area/settings/account_and_limit_settings.md). Default [modified](https://gitlab.com/gitlab-org/gitlab/-/issues/251106) from 50 MB to 0 in GitLab 13.8.
 
-## Import a file from a remote object storage
-
-> [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/282503) in GitLab 13.12 in [Beta](../policy/alpha-beta-support.md#beta-features).
-
-This endpoint is behind a feature flag that is enabled by default.
+## Import a file from a remote object storage (Beta)
 
-To enable this endpoint:
+> [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/282503) in GitLab 13.12 in [Beta](../policy/alpha-beta-support.md#beta-features) [with a flag](../administration/feature_flags.md) named `import_project_from_remote_file`. Enabled by default.
 
-```ruby
-Feature.enable(:import_project_from_remote_file)
-```
-
-To disable this endpoint:
-
-```ruby
-Feature.disable(:import_project_from_remote_file)
-```
+FLAG:
+On self-managed GitLab, by default this feature is available. To hide the feature, ask an administrator to [disable the feature flag](../administration/feature_flags.md) named `import_project_from_remote_file`.
+On GitLab.com, this feature is available.
 
 ```plaintext
 POST /projects/remote-import
 ```
 
-| Attribute         | Type           | Required | Description                              |
-| ----------------- | -------------- | -------- | ---------------------------------------- |
-| `namespace`       | integer/string | no       | The ID or path of the namespace to import the project to. Defaults to the current user's namespace. |
-| `name`            | string         | no       | The name of the project to import. If not provided, defaults to the path of the project. |
-| `url`             | string         | yes      | URL for the file to import. |
-| `path`            | string         | yes      | Name and path for the new project. |
-| `overwrite`       | boolean        | no       | Whether to overwrite a project with the same path when importing. Defaults to `false`. |
-| `override_params` | Hash           | no       | Supports all fields defined in the [Project API](projects.md). |
+| Attribute         | Type              | Required | Description                              |
+| ----------------- | ----------------- | -------- | ---------------------------------------- |
+| `path`            | string            | yes      | Name and path for the new project.
+| `url`             | string            | yes      | URL for the file to import.
+| `name`            | string            | no       | The name of the project to import. If not provided, defaults to the path of the project.
+| `namespace`       | integer or string | no       | The ID or path of the namespace to import the project to. Defaults to the current user's namespace.
+| `overwrite`       | boolean           | no       | Whether to overwrite a project with the same path when importing. Defaults to `false`.
+| `override_params` | Hash              | no       | Supports all fields defined in the [Project API](projects.md).
 
 The passed override parameters take precedence over all values defined in the export file.
 
@@ -256,7 +248,7 @@ curl --request POST \
 }
 ```
 
-The `Content-Length` header must return a valid number. The maximum file size is 10 gigabytes.
+The `Content-Length` header must return a valid number. The maximum file size is 10 GB.
 The `Content-Type` header must be `application/gzip`.
 
 ## Import a file from AWS S3
@@ -273,14 +265,14 @@ POST /projects/remote-import-s3
 
 | Attribute           | Type           | Required | Description                              |
 | ------------------- | -------------- | -------- | ---------------------------------------- |
-| `namespace`         | integer/string | no       | The ID or path of the namespace to import the project to. Defaults to the current user's namespace. |
-| `name`              | string         | no       | The name of the project to import. If not provided, defaults to the path of the project. |
-| `path`              | string         | yes      | The full path of the new project. |
-| `region`            | string         | yes      | [AWS S3 region name where the file is stored.](https://docs.aws.amazon.com/AmazonS3/latest/userguide/Welcome.html#Regions) |
-| `bucket_name`       | string         | yes      | [AWS S3 bucket name where the file is stored.](https://docs.aws.amazon.com/AmazonS3/latest/userguide/bucketnamingrules.html) |
-| `file_key`          | string         | yes      | [AWS S3 file key to identify the file.](https://docs.aws.amazon.com/AmazonS3/latest/userguide/UsingObjects.html) |
-| `access_key_id`     | string         | yes      | [AWS S3 access key ID.](https://docs.aws.amazon.com/general/latest/gr/aws-sec-cred-types.html#access-keys-and-secret-access-keys). |
-| `secret_access_key` | string         | yes      | [AWS S3 secret access key.](https://docs.aws.amazon.com/general/latest/gr/aws-sec-cred-types.html#access-keys-and-secret-access-keys) |
+| `access_key_id`     | string         | yes      | [AWS S3 access key ID](https://docs.aws.amazon.com/general/latest/gr/aws-sec-cred-types.html#access-keys-and-secret-access-keys).
+| `bucket_name`       | string         | yes      | [AWS S3 bucket name](https://docs.aws.amazon.com/AmazonS3/latest/userguide/bucketnamingrules.html) where the file is stored.
+| `file_key`          | string         | yes      | [AWS S3 file key](https://docs.aws.amazon.com/AmazonS3/latest/userguide/UsingObjects.html) to identify the file.
+| `path`              | string         | yes      | The full path of the new project.
+| `region`            | string         | yes      | [AWS S3 region name](https://docs.aws.amazon.com/AmazonS3/latest/userguide/Welcome.html#Regions) where the file is stored.
+| `secret_access_key` | string         | yes      | [AWS S3 secret access key](https://docs.aws.amazon.com/general/latest/gr/aws-sec-cred-types.html#access-keys-and-secret-access-keys).
+| `name`              | string         | no       | The name of the project to import. If not provided, defaults to the path of the project.
+| `namespace`         | integer or string | no       | The ID or path of the namespace to import the project to. Defaults to the current user's namespace.
 
 The passed override parameters take precedence over all values defined in the export file.
 
@@ -347,10 +339,11 @@ GET /projects/:id/import
 
 | Attribute | Type           | Required | Description                              |
 | --------- | -------------- | -------- | ---------------------------------------- |
-| `id`      | integer/string | yes      | The ID or [URL-encoded path of the project](rest/index.md#namespaced-path-encoding) owned by the authenticated user |
+| `id`      | integer or string | yes      | The ID or [URL-encoded path of the project](rest/index.md#namespaced-path-encoding) owned by the authenticated user.
 
 ```shell
-curl --header "PRIVATE-TOKEN: <your_access_token>" "https://gitlab.example.com/api/v4/projects/1/import"
+curl --header "PRIVATE-TOKEN: <your_access_token>" \
+  "https://gitlab.example.com/api/v4/projects/1/import"
 ```
 
 Status can be one of:
@@ -363,8 +356,10 @@ Status can be one of:
 
 If the status is `failed`, it includes the import error message under `import_error`.
 If the status is `failed`, `started` or `finished`, the `failed_relations` array might
-be populated with any occurrences of relations that failed to import either due to
-unrecoverable errors or because retries were exhausted (a typical example are query timeouts.)
+be populated with any occurrences of relations that failed to import due to either:
+
+- Unrecoverable errors.
+- Retries were exhausted. A typical example: query timeouts.
 
 NOTE:
 An element's `id` field in `failed_relations` references the failure record, not the relation.
diff --git a/doc/api/repositories.md b/doc/api/repositories.md
index d56a855b745..d3bee8de2c5 100644
--- a/doc/api/repositories.md
+++ b/doc/api/repositories.md
@@ -164,7 +164,8 @@ Supported attributes:
 Example request:
 
 ```shell
-curl --header "PRIVATE-TOKEN: <your_access_token>" "https://gitlab.com/api/v4/projects/<project_id>/repository/archive?sha=<commit_sha>&path=<path>"
+curl --header "PRIVATE-TOKEN: <your_access_token>" \
+  "https://gitlab.com/api/v4/projects/<project_id>/repository/archive?sha=<commit_sha>&path=<path>"
 ```
 
 ## Compare branches, tags or commits
@@ -278,10 +279,11 @@ GET /projects/:id/repository/merge_base
 | `id`      | integer or string | yes      | The ID or [URL-encoded path of the project](rest/index.md#namespaced-path-encoding). |
 | `refs`    | array          | yes      | The refs to find the common ancestor of. Accepts multiple refs.                    |
 
-Example request:
+Example request, with the refs truncated for readability:
 
 ```shell
-curl --header "PRIVATE-TOKEN: <your_access_token>" "https://gitlab.example.com/api/v4/projects/5/repository/merge_base?refs[]=304d257dcb821665ab5110318fc58a007bd104ed&refs[]=0031876facac3f2b2702a0e53a26e89939a42209"
+curl --header "PRIVATE-TOKEN: <your_access_token>" \
+  "https://gitlab.example.com/api/v4/projects/5/repository/merge_base?refs[]=304d257d&refs[]=0031876f"
 ```
 
 Example response:
@@ -385,26 +387,30 @@ If the last tag is `v0.9.0` and the default branch is `main`, the range of commi
 included in this example is `v0.9.0..main`:
 
 ```shell
-curl --request POST --header "PRIVATE-TOKEN: token" --data "version=1.0.0" "https://gitlab.com/api/v4/projects/42/repository/changelog"
+curl --request POST --header "PRIVATE-TOKEN: token" \
+  --data "version=1.0.0" "https://gitlab.com/api/v4/projects/42/repository/changelog"
 ```
 
 To generate the data on a different branch, specify the `branch` parameter. This
 command generates data from the `foo` branch:
 
 ```shell
-curl --request POST --header "PRIVATE-TOKEN: token" --data "version=1.0.0&branch=foo" "https://gitlab.com/api/v4/projects/42/repository/changelog"
+curl --request POST --header "PRIVATE-TOKEN: token" \
+  --data "version=1.0.0&branch=foo" "https://gitlab.com/api/v4/projects/42/repository/changelog"
 ```
 
 To use a different trailer, use the `trailer` parameter:
 
 ```shell
-curl --request POST --header "PRIVATE-TOKEN: token" --data "version=1.0.0&trailer=Type" "https://gitlab.com/api/v4/projects/42/repository/changelog"
+curl --request POST --header "PRIVATE-TOKEN: token" \
+  --data "version=1.0.0&trailer=Type" "https://gitlab.com/api/v4/projects/42/repository/changelog"
 ```
 
 To store the results in a different file, use the `file` parameter:
 
 ```shell
-curl --request POST --header "PRIVATE-TOKEN: token" --data "version=1.0.0&file=NEWS" "https://gitlab.com/api/v4/projects/42/repository/changelog"
+curl --request POST --header "PRIVATE-TOKEN: token" \
+  --data "version=1.0.0&file=NEWS" "https://gitlab.com/api/v4/projects/42/repository/changelog"
 ```
 
 ## Generate changelog data
@@ -426,21 +432,26 @@ Supported attributes:
 | Attribute | Type     | Required   | Description |
 | :-------- | :------- | :--------- | :---------- |
 | `version` | string   | yes | The version to generate the changelog for. The format must follow [semantic versioning](https://semver.org/). |
-| `config_file` | string   | no | The path of changelog configuration file in the project's Git repository, defaults to `.gitlab/changelog_config.yml`. |
-| `date`    | datetime | no | The date and time of the release, ISO 8601 formatted. Example: `2016-03-11T03:45:40Z`. Defaults to the current time. |
+| `config_file` | string   | no | The path of changelog configuration file in the project's Git repository. Defaults to `.gitlab/changelog_config.yml`. |
+| `date`    | datetime | no | The date and time of the release. Uses ISO 8601 format. Example: `2016-03-11T03:45:40Z`. Defaults to the current time. |
 | `from`    | string   | no | The start of the range of commits (as a SHA) to use for generating the changelog. This commit itself isn't included in the list. |
 | `to`      | string   | no | The end of the range of commits (as a SHA) to use for the changelog. This commit _is_ included in the list. Defaults to the HEAD of the default project branch. |
-| `trailer` | string   | no | The Git trailer to use for including commits, defaults to `Changelog`. |
+| `trailer` | string   | no | The Git trailer to use for including commits. Defaults to `Changelog`. |
 
 ```shell
-curl --header "PRIVATE-TOKEN: token" "https://gitlab.com/api/v4/projects/42/repository/changelog?version=1.0.0"
+curl --header "PRIVATE-TOKEN: token" \
+  "https://gitlab.com/api/v4/projects/42/repository/changelog?version=1.0.0"
 ```
 
-Example Response:
+Example response, with line breaks added for readability:
 
 ```json
 {
-  "notes": "## 1.0.0 (2021-11-17)\n\n### feature (2 changes)\n\n- [Title 2](namespace13/project13@ad608eb642124f5b3944ac0ac772fecaf570a6bf) ([merge request](namespace13/project13!2))\n- [Title 1](namespace13/project13@3c6b80ff7034fa0d585314e1571cc780596ce3c8) ([merge request](namespace13/project13!1))\n"
+  "notes": "## 1.0.0 (2021-11-17)\n\n### feature (2 changes)\n\n-
+    [Title 2](namespace13/project13@ad608eb642124f5b3944ac0ac772fecaf570a6bf)
+    ([merge request](namespace13/project13!2))\n-
+    [Title 1](namespace13/project13@3c6b80ff7034fa0d585314e1571cc780596ce3c8)
+    ([merge request](namespace13/project13!1))\n"
 }
 ```
 
diff --git a/doc/ci/environments/external_deployment_tools.md b/doc/ci/environments/external_deployment_tools.md
index 58d2705b490..37c4cf05f13 100644
--- a/doc/ci/environments/external_deployment_tools.md
+++ b/doc/ci/environments/external_deployment_tools.md
@@ -14,7 +14,7 @@ GitLab can receive deployment events from these external tools and allows you to
 For example, the following features are available by setting up tracking:
 
 - [See when an merge request has been deployed, and to which environment](../../user/project/merge_requests/widgets.md#post-merge-pipeline-status).
-- [Filter merge requests by environment or deployment date](../../user/project/merge_requests/index.md#filter-merge-requests-by-environment-or-deployment-date).
+- [Filter merge requests by environment or deployment date](../../user/project/merge_requests/index.md#by-environment-or-deployment-date).
 - [DevOps Research and Assessment (DORA) metrics](../../user/analytics/dora_metrics.md).
 - [View environments and deployments](index.md#view-environments-and-deployments).
 - [Track newly included merge requests per deployment](index.md#track-newly-included-merge-requests-per-deployment).
diff --git a/doc/development/graphql_guide/reviewing.md b/doc/development/graphql_guide/reviewing.md
index eee2e285957..c98158a43be 100644
--- a/doc/development/graphql_guide/reviewing.md
+++ b/doc/development/graphql_guide/reviewing.md
@@ -37,7 +37,7 @@ For more information, see [deprecation and removal process](../../api/graphql/in
 Ensure that multi-version compatibility is guaranteed.
 This generally means frontend and backend code for the same GraphQL feature can't be shipped in the same release.
 
-For details, see [multiple version compatibility](../multi_version_compatibility.md).[multiple version compatibility](../multi_version_compatibility.md).
+For details, see [multiple version compatibility](../multi_version_compatibility.md).
 
 ### Technical writing review
 
diff --git a/doc/user/group/saml_sso/index.md b/doc/user/group/saml_sso/index.md
index 345330827b9..e5e83384e3a 100644
--- a/doc/user/group/saml_sso/index.md
+++ b/doc/user/group/saml_sso/index.md
@@ -469,11 +469,11 @@ than 24 hours ago, GitLab prompts the user to sign in again through SSO.
 SSO is enforced as follows:
 
 | Project/Group visibility | Enforce SSO setting | Member with identity | Member without identity | Non-member or not signed in |
-|--------------------------|---------------------|--------------------| ------ |------------------------------|
-| Private                  | Off                 | Enforced           | Not enforced | No access                    |
-| Private                  | On            | Enforced           | Enforced | No access                    |
-| Public                   | Off                 | Enforced           | Not enforced | Not enforced                 |
-| Public                   | On            | Enforced           | Enforced | Not enforced                 |
+|--------------------------|---------------------|----------------------|-------------------------|-----------------------------|
+| Private                  | Off                 | Enforced             | Not enforced            | Not enforced                |
+| Private                  | On                  | Enforced             | Enforced                | Enforced                    |
+| Public                   | Off                 | Enforced             | Not enforced            | Not enforced                |
+| Public                   | On                  | Enforced             | Enforced                | Not enforced                |
 
 An [issue exists](https://gitlab.com/gitlab-org/gitlab/-/issues/297389) to add a similar SSO requirement for API activity.
 
@@ -481,7 +481,7 @@ An [issue exists](https://gitlab.com/gitlab-org/gitlab/-/issues/297389) to add a
 
 When the **Enforce SSO-only authentication for web activity for this group** option is enabled:
 
-- All users must access GitLab by using their GitLab group's single sign-on URL
+- All members must access GitLab by using their GitLab group's single sign-on URL
   to access group resources, regardless of whether they have an existing SAML
   identity.
 - SSO is enforced when users access groups and projects in the organization's
@@ -489,6 +489,9 @@ When the **Enforce SSO-only authentication for web activity for this group** opt
 - Users cannot be added as new members manually.
 - Users with the Owner role can use the standard sign in process to make
   necessary changes to top-level group settings.
+- For non-members or users who are not signed in:
+  - SSO is not enforced when they access public group resources.
+  - SSO is enforced when they access private group resources.
 
 SSO enforcement for web activity has the following effects when enabled:
 
diff --git a/doc/user/project/merge_requests/index.md b/doc/user/project/merge_requests/index.md
index 0a526e1d268..ee7f4e5dfed 100644
--- a/doc/user/project/merge_requests/index.md
+++ b/doc/user/project/merge_requests/index.md
@@ -30,7 +30,7 @@ Learn the various ways to [create a merge request](creating_merge_requests.md).
 
 You can view merge requests for your project, group, or yourself.
 
-### View merge requests for a project
+### For a project
 
 To view all merge requests for a project:
 
@@ -39,7 +39,7 @@ To view all merge requests for a project:
 
 Or, to use a [keyboard shortcut](../../shortcuts.md), press <kbd>g</kbd> + <kbd>m</kbd>.
 
-### View merge requests for all projects in a group
+### For all projects in a group
 
 To view merge requests for all projects in a group:
 
@@ -48,7 +48,7 @@ To view merge requests for all projects in a group:
 
 If your group contains subgroups, this view also displays merge requests from the subgroup projects.
 
-### View all merge requests assigned to you
+### Assigned to you
 
 To view all merge requests assigned to you:
 
@@ -79,7 +79,7 @@ To filter the list of merge requests:
 
 1. Above the list of merge requests, select **Search or filter results...**.
 1. From the dropdown list, select the attribute you wish to filter by. Some examples:
-   - [**By environment or deployment date**](#filter-merge-requests-by-environment-or-deployment-date).
+   - [**By environment or deployment date**](#by-environment-or-deployment-date).
    - **ID**: Enter filter `#30` to return only merge request 30.
    - User filters: Type (or select from the dropdown list) any of these filters to display a list of users:
      - **Approved-By**, for merge requests already approved by a user. **(PREMIUM)**.
@@ -100,7 +100,7 @@ To filter the list of merge requests:
 GitLab displays the results on-screen, but you can also
 [retrieve them as an RSS feed](../../search/index.md#retrieve-search-results-as-feed).
 
-### Filter merge requests by environment or deployment date
+### By environment or deployment date
 
 > [Introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/44041) in GitLab 13.6.