Add latest changes from gitlab-org/gitlab@16-3-stable-eev16.3.0-rc42

27 files changed, 50 insertions, 56 deletions

diff --git a/doc/operations/error_tracking.md b/doc/operations/error_tracking.md
index c3902a560c0..36c5ed03197 100644
--- a/doc/operations/error_tracking.md
+++ b/doc/operations/error_tracking.md
@@ -4,7 +4,7 @@ group: Observability
 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
 ---
 
-# Error Tracking **(FREE)**
+# Error Tracking **(FREE ALL)**
 
 Error Tracking allows developers to discover and view errors generated by their application. Because error information is surfaced where the code is developed, this increases efficiency and awareness. Users can choose between [GitLab Integrated error tracking](#integrated-error-tracking) and [Sentry based](#sentry-error-tracking) backends.
 
@@ -82,7 +82,7 @@ You can also review the stack trace.
 
 ### Supported language SDKs & Sentry types
 
-In the following table, you can see a list of all event types available through Sentry SDK, and whether they are supported by GitLab Error Tracking.
+The following table lists all event types available through Sentry SDK, and whether they are supported by GitLab Error Tracking.
 
 | Language | Tested SDK client and version   | Endpoint   | Supported item types              |
 | -------- | ------------------------------- | ---------- | --------------------------------- |
@@ -173,7 +173,7 @@ To enable the Sentry integration:
    `event:write` (for resolving events).
 1. In GitLab, enable and configure Error Tracking:
    1. On the left sidebar, at the top, select **Search GitLab** (**{search}**) to find your project.
-   1. Select **Monitor > Error Tracking**.
+   1. Select **Settings > Monitor > Error Tracking**.
    1. Under **Enable error tracking**, select the **Active** checkbox.
    1. Under **Error tracking backend**, select **Sentry**.
    1. Under **Sentry API URL**, enter your Sentry hostname. For example,
@@ -201,9 +201,7 @@ to your runner's `config.toml` configuration file, as referenced in
 
 If you're asked for the project type while setting up Sentry, select **Go**.
 
-If you see the following error in your GitLab Runner logs, then you should
-specify the deprecated
-DSN in **Sentry.io > Project Settings > Client Keys (DSN) > Show deprecated DSN**.
+To rectify the following error, specify the deprecated DSN in **Sentry.io > Project Settings > Client Keys (DSN) > Show deprecated DSN**.
 
 ```plaintext
 ERROR: Sentry failure builds=0 error=raven: dsn missing private key
diff --git a/doc/operations/feature_flags.md b/doc/operations/feature_flags.md
index 142bd9d898d..21470f66750 100644
--- a/doc/operations/feature_flags.md
+++ b/doc/operations/feature_flags.md
@@ -4,7 +4,7 @@ group: Environments
 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
 ---
 
-# Feature flags **(FREE)**
+# Feature flags **(FREE ALL)**
 
 > [Moved](https://gitlab.com/gitlab-org/gitlab/-/issues/212318) from GitLab Premium to GitLab Free in 13.5.
 
@@ -167,8 +167,7 @@ target users. See the [Ruby example](#ruby-application-example) below.
 Enables the feature for lists of users created [in the feature flags UI](#create-a-user-list), or with the [feature flag user list API](../api/feature_flag_user_lists.md).
 Similar to [User IDs](#user-ids), it uses the Unleash UsersIDs (`userWithId`) activation [strategy](https://docs.getunleash.io/reference/activation-strategies#userids).
 
-It's not possible to *disable* a feature for members of a user list, but you can achieve the same
-effect by enabling a feature for a user list that doesn't contain the excluded users.
+You can't disable a specific feature for a user, but you can achieve similar results by enabling it for a user list.
 
 For example:
 
@@ -217,12 +216,11 @@ To remove users from a user list:
 1. Select **Edit** (**{pencil}**) next to the list you want to change.
 1. Select **Remove** (**{remove}**) next to the ID you want to remove.
 
-## Search for Code References **(PREMIUM)**
+## Search for Code References **(PREMIUM ALL)**
 
 > [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/300299) in GitLab 14.4.
 
-Search your project and find any references of a feature flag in your
-code so that you can clean it up when it's time to remove the feature flag.
+To remove the feature flag from the code during cleanup, find any project references to it.
 
 To search for code references of a feature flag:
 
@@ -399,7 +397,7 @@ docker run \
 There is a limitation when using the Unleash Proxy where each proxy instance can request flags only for the environment named in `UNLEASH_APP_NAME`. The Proxy sends
 this to GitLab on behalf of the client, which means the client can't override it.
 
-## Feature flag related issues **(PREMIUM)**
+## Feature flag related issues **(PREMIUM ALL)**
 
 > - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/36617) in GitLab 13.2.
 > - [Feature flag removed](https://gitlab.com/gitlab-org/gitlab/-/issues/251234) in GitLab 13.5.
@@ -413,8 +411,7 @@ This feature is similar to the [linked issues](../user/project/issues/related_is
 
 ## Performance factors
 
-In general, GitLab feature flags can be used in any applications,
-however, if it's a large application, it could require an additional configuration in advance.
+GitLab feature flags can be used in any application. Large applications might require advance configuration.
 This section explains the performance factors to help your organization to identify
 what's needed to be done before using the feature.
 Read [How it works](#how-it-works) section before diving into the details.
@@ -431,7 +428,7 @@ The polling rate is configurable in SDKs. Provided that all clients are requesti
 - Request once per minute ... 500 clients can be supported.
 - Request once per 15 sec ... 125 clients can be supported.
 
-For applications looking for more scalable solution, we recommend to use [Unleash Proxy](#unleash-proxy-example).
+For applications looking for more scalable solution, you should use [Unleash Proxy](#unleash-proxy-example).
 This proxy server sits between the server and clients. It requests to the server as a behalf of the client groups,
 so the number of outbound requests can be greatly reduced.
 
@@ -452,7 +449,6 @@ Read the documentation in a SDK project for more information.
 Functionality-wise, there are no differences. Both SaaS and self-managed behave the same.
 
 In terms of scalability, it's up to the spec of the GitLab instance.
-For example, GitLab.com runs on HA architecture so that it can handle a lot of requests concurrently,
-however, a self-managed instance runs on a low spec machine can't expect the same result.
+For example, GitLab.com uses HA architecture so it can handle many concurrent requests. However, self-managed instances on underpowered machines won't deliver comparable performance.
 See [Reference architectures](../administration/reference_architectures/index.md)
 for more information.
diff --git a/doc/operations/incident_management/alerts.md b/doc/operations/incident_management/alerts.md
index e701fb2e5fb..e558462cad7 100644
--- a/doc/operations/incident_management/alerts.md
+++ b/doc/operations/incident_management/alerts.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
 ---
 
-# Alerts **(FREE)**
+# Alerts **(FREE ALL)**
 
 Alerts are a critical entity in your incident management workflow. They represent a notable event that might indicate a service outage or disruption. GitLab provides a list view for triage and detail view for deeper investigation of what happened.
 
@@ -153,7 +153,7 @@ When you [close an incident](manage_incidents.md#close-an-incident) that is link
 GitLab [changes the alert's status](#change-an-alerts-status) to **Resolved**.
 You are then credited with the alert's status change.
 
-#### As an on-call responder **(PREMIUM)**
+#### As an on-call responder **(PREMIUM ALL)**
 
 On-call responders can respond to [alert pages](paging.md#escalating-an-alert)
 by changing the alert status.
@@ -206,7 +206,7 @@ from an alert, and view it later on your **To-Do List**.
 
 To add a to-do item, on the right sidebar, select **Add a to do**.
 
-### Trigger actions from alerts **(ULTIMATE)**
+### Trigger actions from alerts **(ULTIMATE ALL)**
 
 > - Introduced in GitLab 13.1: incidents are not created automatically by default.
 > - Mapping common severity values from the alert payload [introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/50871) in GitLab 13.9.
diff --git a/doc/operations/incident_management/escalation_policies.md b/doc/operations/incident_management/escalation_policies.md
index 4360fe6243d..0cbbf42372e 100644
--- a/doc/operations/incident_management/escalation_policies.md
+++ b/doc/operations/incident_management/escalation_policies.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
 ---
 
-# Escalation Policies **(PREMIUM)**
+# Escalation Policies **(PREMIUM ALL)**
 
 > [Introduced](https://gitlab.com/groups/gitlab-org/-/epics/4638) in GitLab 14.1.
 
diff --git a/doc/operations/incident_management/incidents.md b/doc/operations/incident_management/incidents.md
index 4e2be27e424..4aae8809620 100644
--- a/doc/operations/incident_management/incidents.md
+++ b/doc/operations/incident_management/incidents.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
 ---
 
-# Incidents **(FREE)**
+# Incidents **(FREE ALL)**
 
 An incident is a service disruption or outage that needs to be restored urgently.
 Incidents are critical in incident management workflows.
@@ -97,7 +97,7 @@ Comments are displayed in threads, but can be displayed chronologically
 When you make changes to an incident, GitLab creates [system notes](../../user/project/system_notes.md) and
 displays them below the summary.
 
-### Metrics **(PREMIUM)**
+### Metrics **(PREMIUM ALL)**
 
 > [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/235994) in GitLab 13.8.
 
@@ -130,7 +130,7 @@ during an incident, and the steps that were taken for it to be resolved.
 
 Read more about [timeline events](incident_timeline_events.md) and how to enable this feature.
 
-### Recent updates view **(PREMIUM)**
+### Recent updates view **(PREMIUM ALL)**
 
 > [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/227836) in GitLab 13.5.
 
@@ -138,7 +138,7 @@ To see the latest updates on an incident, select
 **Turn recent updates view on** (**{history}**) on the comment bar. Comments display
 un-threaded and chronologically, newest to oldest.
 
-### Service Level Agreement countdown timer **(PREMIUM)**
+### Service Level Agreement countdown timer **(PREMIUM ALL)**
 
 > [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/241663) in GitLab 13.5.
 
diff --git a/doc/operations/incident_management/index.md b/doc/operations/incident_management/index.md
index 9e66ab46692..1cae066ce32 100644
--- a/doc/operations/incident_management/index.md
+++ b/doc/operations/incident_management/index.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
 ---
 
-# Incident management **(FREE)**
+# Incident management **(FREE ALL)**
 
 > [Introduced](https://gitlab.com/groups/gitlab-org/-/epics/2877) in GitLab 13.0.
 
diff --git a/doc/operations/incident_management/integrations.md b/doc/operations/incident_management/integrations.md
index 5fe7db71fd8..5eed1921168 100644
--- a/doc/operations/incident_management/integrations.md
+++ b/doc/operations/incident_management/integrations.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
 ---
 
-# Integrations **(FREE)**
+# Integrations **(FREE ALL)**
 
 > - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/13203) in GitLab 12.4.
 > - [Moved](https://gitlab.com/gitlab-org/gitlab/-/issues/42640) from GitLab Ultimate to GitLab Free in 12.8.
@@ -42,7 +42,7 @@ receive alert payloads in JSON format. You can always
    are available in the **View credentials** tab after you save the integration. You must also input
    the URL and Authorization Key in your external service.
 
-### HTTP Endpoints **(PREMIUM)**
+### HTTP Endpoints **(PREMIUM ALL)**
 
 > [Introduced](https://gitlab.com/groups/gitlab-org/-/epics/4442) in GitLab 13.6.
 
@@ -395,7 +395,7 @@ alert to confirm your integration works properly.
 
 GitLab displays an error or success message, depending on the outcome of your test.
 
-## Automatic grouping of identical alerts **(PREMIUM)**
+## Automatic grouping of identical alerts **(PREMIUM ALL)**
 
 > [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/214557) in GitLab 13.2.
 
@@ -420,7 +420,7 @@ field is `end_time`. With custom mappings, you can select the expected field.
 
 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.
 
-## Link to your Opsgenie Alerts **(PREMIUM)**
+## Link to your Opsgenie Alerts **(PREMIUM ALL)**
 
 > [Introduced](https://gitlab.com/groups/gitlab-org/-/epics/3066) in GitLab 13.2.
 
diff --git a/doc/operations/incident_management/linked_resources.md b/doc/operations/incident_management/linked_resources.md
index e43b08dfd78..15317f61057 100644
--- a/doc/operations/incident_management/linked_resources.md
+++ b/doc/operations/incident_management/linked_resources.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
 ---
 
-# Linked resources in incidents **(PREMIUM)**
+# Linked resources in incidents **(PREMIUM ALL)**
 
 > - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/230852) in GitLab 15.3 [with a flag](../../administration/feature_flags.md) named `incident_resource_links_widget`. Disabled by default.
 > - [Enabled on GitLab.com](https://gitlab.com/gitlab-org/gitlab/-/issues/364755) in GitLab 15.3.
diff --git a/doc/operations/incident_management/manage_incidents.md b/doc/operations/incident_management/manage_incidents.md
index bb9dde4b416..f88d9b51891 100644
--- a/doc/operations/incident_management/manage_incidents.md
+++ b/doc/operations/incident_management/manage_incidents.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
 ---
 
-# Manage incidents **(FREE)**
+# Manage incidents **(FREE ALL)**
 
 This page collects instructions for all the things you can do with [incidents](incidents.md) or in relation to them.
 
@@ -68,7 +68,7 @@ When you [close an incident](#close-an-incident) linked to an alert, GitLab
 [changes the alert's status](alerts.md#change-an-alerts-status) to **Resolved**.
 You are then credited with the alert's status change.
 
-### Automatically, when an alert is triggered **(ULTIMATE)**
+### Automatically, when an alert is triggered **(ULTIMATE ALL)**
 
 In the project settings, you can turn on [creating an incident automatically](alerts.md#trigger-actions-from-alerts)
 whenever an alert is triggered.
@@ -166,7 +166,7 @@ To change the status of an incident:
 
 **Triggered** is the default status for new incidents.
 
-### As an on-call responder **(PREMIUM)**
+### As an on-call responder **(PREMIUM ALL)**
 
 On-call responders can respond to [incident pages](paging.md#escalating-an-incident)
 by changing the status.
@@ -181,7 +181,7 @@ In GitLab 15.1 and earlier, changing the status of an [incident created from an
 also changes the alert status. In [GitLab 15.2 and later](https://gitlab.com/gitlab-org/gitlab/-/issues/356057),
 the alert status is independent and does not change when the incident status changes.
 
-## Change escalation policy **(PREMIUM)**
+## Change escalation policy **(PREMIUM ALL)**
 
 Prerequisites:
 
@@ -245,7 +245,7 @@ To configure the setting:
 1. Select the **Automatically close associated incident** checkbox.
 1. Select **Save changes**.
 
-When GitLab receives a recovery alert, it closes the associated incident.
+When GitLab receives a [recovery alert](integrations.md#recovery-alerts), it closes the associated incident.
 This action is recorded as a system note on the incident indicating that it
 was closed automatically by the GitLab Alert bot.
 
diff --git a/doc/operations/incident_management/oncall_schedules.md b/doc/operations/incident_management/oncall_schedules.md
index 8e3318766b4..808dc30581d 100644
--- a/doc/operations/incident_management/oncall_schedules.md
+++ b/doc/operations/incident_management/oncall_schedules.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
 ---
 
-# On-call Schedule Management **(PREMIUM)**
+# On-call Schedule Management **(PREMIUM ALL)**
 
 > [Introduced](https://gitlab.com/groups/gitlab-org/-/epics/4544) in GitLab 13.11.
 
diff --git a/doc/operations/incident_management/paging.md b/doc/operations/incident_management/paging.md
index be28e94c148..05cc8c8e221 100644
--- a/doc/operations/incident_management/paging.md
+++ b/doc/operations/incident_management/paging.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
 ---
 
-# Paging and notifications **(FREE)**
+# Paging and notifications **(FREE ALL)**
 
 When there is a new alert or incident, it is important for a responder to be notified
 immediately so they can triage and respond to the problem. Responders can receive
@@ -35,7 +35,7 @@ a single email notification for new alerts.
 
 [Update the alert's status](alerts.md#change-an-alerts-status) to manage email notifications for an alert.
 
-## Paging **(PREMIUM)**
+## Paging **(PREMIUM ALL)**
 
 In projects that have an [escalation policy](escalation_policies.md) configured, on-call responders
 can be automatically paged about critical problems through email.
diff --git a/doc/operations/incident_management/slack.md b/doc/operations/incident_management/slack.md
index aa0d057bfd8..82d5d8b3150 100644
--- a/doc/operations/incident_management/slack.md
+++ b/doc/operations/incident_management/slack.md
@@ -32,7 +32,7 @@ Prerequisites:
 
 1. Install the [GitLab for Slack app](../../user/project/integrations/gitlab_slack_application.md).
    This way, you can use slash commands in Slack to create and update GitLab incidents.
-1. Enable [Slack notifications](../../user/project/integrations/slack.md). Be sure to enable
+1. Enable [Slack notifications](../../user/project/integrations/gitlab_slack_application.md#slack-notifications). Be sure to enable
    notifications for `Incident` events, and to define a Slack channel to receive the relevant notifications.
 1. Authorize GitLab to take actions on behalf of your Slack user.
    Each user must do this before they can use any of the incident slash commands.
diff --git a/doc/operations/incident_management/status_page.md b/doc/operations/incident_management/status_page.md
index a52790b7f70..374571d225e 100644
--- a/doc/operations/incident_management/status_page.md
+++ b/doc/operations/incident_management/status_page.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
 ---
 
-# Status Page **(ULTIMATE)**
+# Status Page **(ULTIMATE ALL)**
 
 > [Introduced](https://gitlab.com/groups/gitlab-org/-/epics/2479) in GitLab 12.10.
 
diff --git a/doc/operations/index.md b/doc/operations/index.md
index 922ec557c4c..73925afb2d8 100644
--- a/doc/operations/index.md
+++ b/doc/operations/index.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
 ---
 
-# Monitor application performance **(FREE)**
+# Monitor application performance **(FREE ALL)**
 
 GitLab provides a variety of tools to help operate and maintain
 your applications.
diff --git a/doc/operations/metrics/alerts.md b/doc/operations/metrics/alerts.md
index 44a257f532b..a5f580ac503 100644
--- a/doc/operations/metrics/alerts.md
+++ b/doc/operations/metrics/alerts.md
@@ -6,7 +6,7 @@ remove_date: '2023-08-22'
 redirect_to: '../index.md'
 ---
 
-# Set up alerts for Prometheus metrics (removed) **(FREE)**
+# Set up alerts for Prometheus metrics (removed) **(FREE ALL)**
 
 This feature was [deprecated](https://gitlab.com/gitlab-org/gitlab/-/issues/346541) in GitLab 14.7
 and [removed](https://gitlab.com/gitlab-org/gitlab/-/issues/399231) in 16.0.
diff --git a/doc/operations/metrics/dashboards/default.md b/doc/operations/metrics/dashboards/default.md
index 28a3adc5051..3eec1272307 100644
--- a/doc/operations/metrics/dashboards/default.md
+++ b/doc/operations/metrics/dashboards/default.md
@@ -6,7 +6,7 @@ remove_date: '2023-08-22'
 redirect_to: '../../index.md'
 ---
 
-# GitLab-defined metrics dashboards (removed) **(FREE)**
+# GitLab-defined metrics dashboards (removed) **(FREE ALL)**
 
 This feature was [deprecated](https://gitlab.com/gitlab-org/gitlab/-/issues/346541) in GitLab 14.7
 and [removed](https://gitlab.com/gitlab-org/gitlab/-/issues/399231) in 16.0.
diff --git a/doc/operations/metrics/dashboards/develop.md b/doc/operations/metrics/dashboards/develop.md
index b7912e164d7..c6d4721863a 100644
--- a/doc/operations/metrics/dashboards/develop.md
+++ b/doc/operations/metrics/dashboards/develop.md
@@ -6,7 +6,7 @@ remove_date: '2023-08-22'
 redirect_to: '../../index.md'
 ---
 
-# Developing templates for custom dashboards (removed) **(FREE)**
+# Developing templates for custom dashboards (removed) **(FREE ALL)**
 
 This feature was [deprecated](https://gitlab.com/gitlab-org/gitlab/-/issues/346541) in GitLab 14.7
 and [removed](https://gitlab.com/gitlab-org/gitlab/-/issues/399231) in 16.0.
diff --git a/doc/operations/metrics/dashboards/index.md b/doc/operations/metrics/dashboards/index.md
index a4cf12cc64a..df94f979f5f 100644
--- a/doc/operations/metrics/dashboards/index.md
+++ b/doc/operations/metrics/dashboards/index.md
@@ -6,7 +6,7 @@ remove_date: '2023-08-22'
 redirect_to: '../../index.md'
 ---
 
-# Custom dashboards (removed) **(FREE)**
+# Custom dashboards (removed) **(FREE ALL)**
 
 This feature was [deprecated](https://gitlab.com/gitlab-org/gitlab/-/issues/346541) in GitLab 14.7
 and [removed](https://gitlab.com/gitlab-org/gitlab/-/issues/399231) in 16.0.
diff --git a/doc/operations/metrics/dashboards/panel_types.md b/doc/operations/metrics/dashboards/panel_types.md
index c789e99052c..8dcf4e6ad28 100644
--- a/doc/operations/metrics/dashboards/panel_types.md
+++ b/doc/operations/metrics/dashboards/panel_types.md
@@ -6,7 +6,7 @@ remove_date: '2023-08-22'
 redirect_to: '../../index.md'
 ---
 
-# Panel types for dashboards (removed) **(FREE)**
+# Panel types for dashboards (removed) **(FREE ALL)**
 
 This feature was [deprecated](https://gitlab.com/gitlab-org/gitlab/-/issues/346541) in GitLab 14.7
 and [removed](https://gitlab.com/gitlab-org/gitlab/-/issues/399231) in 16.0.
diff --git a/doc/operations/metrics/dashboards/settings.md b/doc/operations/metrics/dashboards/settings.md
index 5572dfa360f..7abcbf88d59 100644
--- a/doc/operations/metrics/dashboards/settings.md
+++ b/doc/operations/metrics/dashboards/settings.md
@@ -6,7 +6,7 @@ remove_date: '2023-08-22'
 redirect_to: '../../index.md'
 ---
 
-# Dashboard settings (removed) **(FREE)**
+# Dashboard settings (removed) **(FREE ALL)**
 
 This feature was [deprecated](https://gitlab.com/gitlab-org/gitlab/-/issues/346541) in GitLab 14.7
 and [removed](https://gitlab.com/gitlab-org/gitlab/-/issues/399231) in 16.0.
diff --git a/doc/operations/metrics/dashboards/templating_variables.md b/doc/operations/metrics/dashboards/templating_variables.md
index a93c559c98c..ceeeb229a81 100644
--- a/doc/operations/metrics/dashboards/templating_variables.md
+++ b/doc/operations/metrics/dashboards/templating_variables.md
@@ -6,7 +6,7 @@ remove_date: '2023-08-22'
 redirect_to: '../../index.md'
 ---
 
-# Templating variables for metrics dashboards (removed) **(FREE)**
+# Templating variables for metrics dashboards (removed) **(FREE ALL)**
 
 This feature was [deprecated](https://gitlab.com/gitlab-org/gitlab/-/issues/346541) in GitLab 14.7
 and [removed](https://gitlab.com/gitlab-org/gitlab/-/issues/399231) in 16.0.
diff --git a/doc/operations/metrics/dashboards/variables.md b/doc/operations/metrics/dashboards/variables.md
index 45e13aa731a..b4ea05a0cea 100644
--- a/doc/operations/metrics/dashboards/variables.md
+++ b/doc/operations/metrics/dashboards/variables.md
@@ -6,7 +6,7 @@ remove_date: '2023-08-22'
 redirect_to: '../../index.md'
 ---
 
-# Using variables (removed) **(FREE)**
+# Using variables (removed) **(FREE ALL)**
 
 This feature was [deprecated](https://gitlab.com/gitlab-org/gitlab/-/issues/346541) in GitLab 14.7
 and [removed](https://gitlab.com/gitlab-org/gitlab/-/issues/399231) in 16.0.
diff --git a/doc/operations/metrics/dashboards/yaml.md b/doc/operations/metrics/dashboards/yaml.md
index 7807f713773..95c02319b19 100644
--- a/doc/operations/metrics/dashboards/yaml.md
+++ b/doc/operations/metrics/dashboards/yaml.md
@@ -6,7 +6,7 @@ remove_date: '2023-08-22'
 redirect_to: '../../index.md'
 ---
 
-# Dashboard YAML properties (removed) **(FREE)**
+# Dashboard YAML properties (removed) **(FREE ALL)**
 
 This feature was [deprecated](https://gitlab.com/gitlab-org/gitlab/-/issues/346541) in GitLab 14.7
 and [removed](https://gitlab.com/gitlab-org/gitlab/-/issues/399231) in 16.0.
diff --git a/doc/operations/metrics/dashboards/yaml_number_format.md b/doc/operations/metrics/dashboards/yaml_number_format.md
index 90e7f67b153..e75beadfab9 100644
--- a/doc/operations/metrics/dashboards/yaml_number_format.md
+++ b/doc/operations/metrics/dashboards/yaml_number_format.md
@@ -6,7 +6,7 @@ remove_date: '2023-08-22'
 redirect_to: '../../index.md'
 ---
 
-# Unit formats reference (removed) **(FREE)**
+# Unit formats reference (removed) **(FREE ALL)**
 
 This feature was [deprecated](https://gitlab.com/gitlab-org/gitlab/-/issues/346541) in GitLab 14.7
 and [removed](https://gitlab.com/gitlab-org/gitlab/-/issues/399231) in 16.0.
diff --git a/doc/operations/metrics/embed.md b/doc/operations/metrics/embed.md
index 00c145adee3..68f115b66db 100644
--- a/doc/operations/metrics/embed.md
+++ b/doc/operations/metrics/embed.md
@@ -6,7 +6,7 @@ remove_date: '2023-08-22'
 redirect_to: '../index.md'
 ---
 
-# Embedding metric charts within GitLab Flavored Markdown (removed) **(FREE)**
+# Embedding metric charts within GitLab Flavored Markdown (removed) **(FREE ALL)**
 
 This feature was [deprecated](https://gitlab.com/gitlab-org/gitlab/-/issues/346541) in GitLab 14.7
 and [removed](https://gitlab.com/gitlab-org/gitlab/-/issues/399231) in 16.0.
diff --git a/doc/operations/metrics/embed_grafana.md b/doc/operations/metrics/embed_grafana.md
index e14b4b5a893..82967aa663f 100644
--- a/doc/operations/metrics/embed_grafana.md
+++ b/doc/operations/metrics/embed_grafana.md
@@ -5,7 +5,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w
 remove_date: '2023-08-22'
 redirect_to: '../index.md'
 ---
-# Embed Grafana panels in Markdown (removed) **(FREE)**
+# Embed Grafana panels in Markdown (removed) **(FREE ALL)**
 
 This feature was [deprecated](https://gitlab.com/gitlab-org/gitlab/-/issues/346541) in GitLab 14.7
 and [removed](https://gitlab.com/gitlab-org/gitlab/-/issues/399231) in 16.0.
diff --git a/doc/operations/metrics/index.md b/doc/operations/metrics/index.md
index 98ed9aba0da..65f84c9c825 100644
--- a/doc/operations/metrics/index.md
+++ b/doc/operations/metrics/index.md
@@ -6,7 +6,7 @@ remove_date: '2023-08-22'
 redirect_to: '../index.md'
 ---
 
-# Monitor your environment's metrics (removed) **(FREE)**
+# Monitor your environment's metrics (removed) **(FREE ALL)**
 
 This feature was [deprecated](https://gitlab.com/gitlab-org/gitlab/-/issues/346541) in GitLab 14.7
 and [removed](https://gitlab.com/gitlab-org/gitlab/-/issues/399231) in 16.0.