Add latest changes from gitlab-org/gitlab@15-1-stable-eev15.1.0-rc42

13 files changed, 53 insertions, 105 deletions

diff --git a/doc/operations/feature_flags.md b/doc/operations/feature_flags.md
index 4b503af2cf7..71248adc777 100644
--- a/doc/operations/feature_flags.md
+++ b/doc/operations/feature_flags.md
@@ -403,7 +403,7 @@ docker run \
 > - Showing related feature flags in issues [introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/220333) in GitLab 14.1.
 
 You can link related issues to a feature flag. In the Feature Flag **Linked issues** section,
-click the `+` button and input the issue reference number or the full URL of the issue.
+select the `+` button and input the issue reference number or the full URL of the issue.
 The issues then appear in the related feature flag and the other way round.
 
 This feature is similar to the [linked issues](../user/project/issues/related_issues.md) feature.
diff --git a/doc/operations/incident_management/alerts.md b/doc/operations/incident_management/alerts.md
index 008e41f5d64..af42571f82f 100644
--- a/doc/operations/incident_management/alerts.md
+++ b/doc/operations/incident_management/alerts.md
@@ -205,7 +205,7 @@ To assign an alert:
    ![Alert Details View Assignees](img/alert_details_assignees_v13_1.png)
 
 1. If the right sidebar is not expanded, select
-   **Expand sidebar** (**{angle-double-right}**) to expand it.
+   **Expand sidebar** (**{chevron-double-lg-right}**) to expand it.
 
 1. On the right sidebar, locate the **Assignee**, and then select **Edit**.
    From the list, select each user you want to assign to the alert.
diff --git a/doc/operations/incident_management/incidents.md b/doc/operations/incident_management/incidents.md
index 66d04fce14c..e48127b3415 100644
--- a/doc/operations/incident_management/incidents.md
+++ b/doc/operations/incident_management/incidents.md
@@ -58,7 +58,7 @@ GitLab to create incident automatically whenever an alert is triggered:
    with the Developer role, select
    **Send a separate email notification to Developers**. Email notifications are
    also sent to users with the **Maintainer** and **Owner** roles.
-1. Click **Save changes**.
+1. Select **Save changes**.
 
 ### Create incidents via the PagerDuty webhook
 
@@ -149,7 +149,7 @@ displays it in the Incident Details view:
 
 For live examples of GitLab incidents, visit the `tanuki-inc` project's
 [incident list page](https://gitlab.com/gitlab-examples/ops/incident-setup/everyone/tanuki-inc/-/incidents).
-Click any incident in the list to display its incident details page.
+Select any incident in the list to display its incident details page.
 
 ### Summary
 
@@ -180,7 +180,7 @@ charts in the **Metrics** tab:
 
 ![Incident Metrics tab](img/incident_metrics_tab_v13_8.png)
 
-When you upload an image, you can associate the image with text or a link to the original graph.  
+When you upload an image, you can associate the image with text or a link to the original graph.
 
 ![Text link modal](img/incident_metrics_tab_text_link_modal_v14_9.png)
 
@@ -199,7 +199,7 @@ field populated.
 
 > [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/227836) in GitLab 13.5.
 
-To quickly see the latest updates on an incident, click
+To quickly see the latest updates on an incident, select
 **{history}** **Turn recent updates view on** in the comment bar to display comments
 un-threaded and ordered chronologically, newest to oldest:
 
@@ -217,11 +217,11 @@ every 15 minutes so you do not have to refresh the page to see the time remainin
 To configure the timer:
 
 1. Navigate to **Settings > Monitor**.
-1. Scroll to **Incidents** and click **Expand**, then select the
+1. Scroll to **Incidents** and select **Expand**, then select the
    **Incident settings** tab.
 1. Select **Activate "time to SLA" countdown timer**.
 1. Set a time limit in increments of 15 minutes.
-1. Click **Save changes**.
+1. Select **Save changes**.
 
 After you enable the SLA countdown timer, the **Time to SLA** attribute is displayed
 as a column in the Incidents List, and as a field on newly created Incidents. If
@@ -250,18 +250,14 @@ You can also change the severity using the [`/severity` quick action](../../user
 
 ### Add a to-do item
 
-Add a to-do for incidents that you want to track in your to-do list. Click the
-**Add a to do** button at the top of the right-hand side bar to add a to-do item.
+Add a to-do for incidents that you want to track in your to-do list. Select
+**Add a to do** at the top of the right-hand side bar to add a to-do item.
 
 ### Change incident status
 
 > - [Introduced](https://gitlab.com/groups/gitlab-org/-/epics/5716) in GitLab 14.9 [with a flag](../../administration/feature_flags.md) named `incident_escalations`. Disabled by default.
 > - [Enabled on GitLab.com and self-managed](https://gitlab.com/gitlab-org/gitlab/-/issues/345769) in GitLab 14.10.
-
-FLAG:
-This feature is available by default. To disable it per project or for your entire
-instance, ask an administrator to [disable the feature flag](../../administration/feature_flags.md)
-named `incident_escalations`.
+> - [Feature flag `incident_escalations`](https://gitlab.com/gitlab-org/gitlab/-/issues/345769) removed in GitLab 15.1.
 
 For users with the Developer role or higher, select **Edit** in the **Status** section of the
 right-hand side bar of an incident, then select a status. **Triggered** is the default status for
@@ -281,11 +277,7 @@ updating the incident status also updates the alert status.
 
 > - [Introduced](https://gitlab.com/groups/gitlab-org/-/epics/5716) in GitLab 14.9 [with a flag](../../administration/feature_flags.md) named `incident_escalations`. Disabled by default.
 > - [Enabled on GitLab.com and self-managed](https://gitlab.com/gitlab-org/gitlab/-/issues/345769) in GitLab 14.10.
-
-FLAG:
-This feature is available by default. To disable it per project or for your entire
-instance, ask an administrator to [disable the feature flag](../../administration/feature_flags.md)
-named `incident_escalations`.
+> - [Feature flag `incident_escalations`](https://gitlab.com/gitlab-org/gitlab/-/issues/345769) removed in GitLab 15.1.
 
 For users with the Developer role or higher, select **Edit** in the **Escalation policy** section of
 the right-hand side bar of an incident, then select a policy. By default, new incidents do not have
@@ -336,7 +328,7 @@ With at least the Maintainer role, you can enable
 
 1. Navigate to **Settings > Monitor > Incidents** and expand **Incidents**.
 1. Check the **Automatically close associated Incident** checkbox.
-1. Click **Save changes**.
+1. Select **Save changes**.
 
 When GitLab receives a **Recovery Alert**, it closes the associated incident.
 This action is recorded as a system message on the incident indicating that it
diff --git a/doc/operations/incident_management/integrations.md b/doc/operations/incident_management/integrations.md
index fe05cb9fda0..6e65fe875c5 100644
--- a/doc/operations/incident_management/integrations.md
+++ b/doc/operations/incident_management/integrations.md
@@ -10,9 +10,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w
 > - [Moved](https://gitlab.com/gitlab-org/gitlab/-/issues/42640) from GitLab Ultimate to GitLab Free in 12.8.
 
 GitLab can accept alerts from any source via a webhook receiver. This can be configured
-generically or, in GitLab versions 13.1 and greater, you can configure
-[External Prometheus instances](../metrics/alerts.md#external-prometheus-instances)
-to use this endpoint.
+generically.
 
 ## Integrations list
 
@@ -27,8 +25,7 @@ the integration name, type, and status (enabled or disabled):
 
 ## Configuration
 
-GitLab can receive alerts via a HTTP endpoint that you configure,
-or the [Prometheus integration](#external-prometheus-integration).
+GitLab can receive alerts via a HTTP endpoint that you configure.
 
 ### Single HTTP Endpoint
 
@@ -59,19 +56,19 @@ and you can [customize the payload](#customize-the-alert-payload-outside-of-gitl
 1. Expand the **Alerts** section.
 1. For each endpoint you want to create:
 
-   1. Click the **Add new integration** button.
+   1. Select **Add new integration**.
    1. In the **Select integration type** dropdown menu, select **HTTP Endpoint**.
    1. Name the integration.
    1. Toggle the **Active** alert setting. The **URL** and **Authorization Key** for the webhook
       configuration 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.
    1. Optional. To map fields from your monitoring tool's alert to GitLab fields, enter a sample
-      payload and click **Parse payload for custom mapping**. Valid JSON is required. If you update
+      payload and select **Parse payload for custom mapping**. Valid JSON is required. If you update
       a sample payload, you must also remap the fields.
 
    1. Optional. If you provided a valid sample payload, select each value in
       **Payload alert key** to [map to a **GitLab alert key**](#map-fields-in-custom-alerts).
-   1. To save your integration, click **Save Integration**. If desired, you can send a test alert
+   1. To save your integration, select **Save Integration**. If desired, you can send a test alert
       from your integration's **Send test alert** tab after the integration is created.
 
 The new HTTP Endpoint displays in the [integrations list](#integrations-list).
@@ -89,12 +86,6 @@ GitLab fields when you [create an HTTP endpoint](#http-endpoints):
 
 ![Alert Management List](img/custom_alert_mapping_v13_11.png)
 
-### External Prometheus integration
-
-For GitLab versions 13.1 and greater, read
-[External Prometheus Instances](../metrics/alerts.md#external-prometheus-instances)
-to configure alerts for this integration.
-
 ## Customize the alert payload outside of GitLab
 
 For HTTP Endpoints without [custom mappings](#map-fields-in-custom-alerts), you can customize the payload by sending the following
@@ -227,11 +218,11 @@ alert to confirm your integration works properly.
 
 1. Sign in as a user with at least the Developer role.
 1. Navigate to **Settings > Monitor** in your project.
-1. Click **Alerts** to expand the section.
-1. Click the **{settings}** settings icon on the right side of the integration in [the list](#integrations-list).
+1. Select **Alerts** to expand the section.
+1. Select the **{settings}** settings icon on the right side of the integration in [the list](#integrations-list).
 1. Select the **Send test alert** tab to open it.
 1. Enter a test payload in the payload field (valid JSON is required).
-1. Click **Send**.
+1. Select **Send**.
 
 GitLab displays an error or success message, depending on the outcome of your test.
 
diff --git a/doc/operations/incident_management/paging.md b/doc/operations/incident_management/paging.md
index 420454d8d8a..936c297e555 100644
--- a/doc/operations/incident_management/paging.md
+++ b/doc/operations/incident_management/paging.md
@@ -52,11 +52,7 @@ or stop alert escalations by [updating the alert's status](alerts.md#update-an-a
 
 > - [Introduced](https://gitlab.com/groups/gitlab-org/-/epics/5716) in GitLab 14.9 [with a flag](../../administration/feature_flags.md) named `incident_escalations`. Disabled by default.
 > - [Enabled on GitLab.com and self-managed](https://gitlab.com/gitlab-org/gitlab/-/issues/345769) in GitLab 14.10.
-
-FLAG:
-This feature is available by default. To disable it per project or for your entire
-instance, ask an administrator to [disable the feature flag](../../administration/feature_flags.md)
-named `incident_escalations`.
+> - [Feature flag `incident_escalations`](https://gitlab.com/gitlab-org/gitlab/-/issues/345769) removed in GitLab 15.1.
 
 For incidents, paging on-call responders is optional for each individual incident.
 To begin escalating the incident, [set the incident's escalation policy](incidents.md#change-escalation-policy).
diff --git a/doc/operations/metrics/alerts.md b/doc/operations/metrics/alerts.md
index 0e446f04b9b..12bd975db5d 100644
--- a/doc/operations/metrics/alerts.md
+++ b/doc/operations/metrics/alerts.md
@@ -17,46 +17,15 @@ your team when environment performance falls outside of the boundaries you set.
 
 Alerts are not currently supported for [Prometheus cluster integrations](../../user/clusters/integrations.md).
 
-## External Prometheus instances
+<!--- start_remove The following content will be removed on remove_date: '2022-09-22' -->
 
-> [Moved](https://gitlab.com/gitlab-org/gitlab/-/issues/42640) to GitLab Free in 12.10.
+## External Prometheus instances (removed)
+
+This feature was [deprecated](https://gitlab.com/gitlab-org/gitlab/-/issues/219142) in GitLab 13.2 and [removed](https://gitlab.com/gitlab-org/gitlab/-/issues/338834) in 15.0.
+To manually configure a Prometheus server, we recommend
+you use the [generic alerts integration](../incident_management/integrations.md).
 
-For manually configured Prometheus servers, GitLab provides a notify endpoint for
-use with Prometheus webhooks. If you have manual configuration enabled, an
-**Alerts** section is added to **Settings > Integrations > Prometheus**.
-This section contains the needed **URL** and **Authorization Key**. The
-**Reset Key** button invalidates the key and generates a new one.
-
-![Prometheus integration configuration of Alerts](img/prometheus_integration_alerts.png)
-
-To send GitLab alert notifications, copy the **URL** and **Authorization Key** into the
-[`webhook_configs`](https://prometheus.io/docs/alerting/latest/configuration/#webhook_config)
-section of your Prometheus Alertmanager configuration:
-
-```yaml
-receivers:
-  - name: gitlab
-    webhook_configs:
-      - http_config:
-          authorization:
-            type: Bearer
-            credentials: 9e1cbfcd546896a9ea8be557caf13a76
-        send_resolved: true
-        url: http://192.168.178.31:3001/root/manual_prometheus/prometheus/alerts/notify.json
-        # Rest of configuration omitted
-        # ...
-```
-
-For GitLab to associate your alerts with an [environment](../../ci/environments/index.md),
-you must configure a `gitlab_environment_name` label on the alerts you set up in
-Prometheus. The value of this should match the name of your environment in GitLab.
-
-You can display alerts with a `gitlab_environment_name` of `production`
-[on a dashboard](../../user/operations_dashboard/index.md#adding-a-project-to-the-dashboard).
-
-In GitLab versions 13.1 and greater, you can configure your manually configured
-Prometheus server to use the
-[Generic alerts integration](../incident_management/integrations.md).
+<!--- end_remove -->
 
 ## Trigger actions from alerts **(ULTIMATE)**
 
@@ -67,7 +36,7 @@ Alerts can be used to trigger actions, like opening an issue automatically
 1. Enable the option to create issues.
 1. Choose the [issue template](../../user/project/description_templates.md) to create the issue from.
 1. Optionally, select whether to send an email notification to the developers of the project.
-1. Click **Save changes**.
+1. Select **Save changes**.
 
 After enabling, GitLab automatically opens an issue when an alert is triggered containing
 values extracted from the [`alerts` field in webhook payload](https://prometheus.io/docs/alerting/latest/configuration/#webhook_config):
diff --git a/doc/operations/metrics/dashboards/develop.md b/doc/operations/metrics/dashboards/develop.md
index 513e5532bee..e09f56e27cf 100644
--- a/doc/operations/metrics/dashboards/develop.md
+++ b/doc/operations/metrics/dashboards/develop.md
@@ -23,14 +23,14 @@ Navigate to the browser-based editor of your choice:
 - In the **Repository view**:
 
   1. Navigate to **{doc-text}** **Repository > Files**.
-  1. Click **{plus}** **Add to tree** and select **New file**,
-     then click **Select a template type** to see a list of available templates:
+  1. Select **{plus}** **Add to tree** and select **New file**,
+     then select **Select a template type** to see a list of available templates:
      ![Metrics dashboard template selection](img/metrics_dashboard_template_selection_v13_3.png)
 
 - In the **[Web IDE](../../../user/project/web_ide/index.md)**:
 
-  1. Click **Web IDE** when viewing your repository.
-  1. Click **{doc-new}** **New file**, then click **Choose a template** to see a list of available templates:
+  1. Select **Web IDE** when viewing your repository.
+  1. Select **{doc-new}** **New file**, then select **Choose a template** to see a list of available templates:
      ![Metrics dashboard template selection WebIDE](img/metrics_dashboard_template_selection_web_ide_v13_3.png)
 
 ## Custom dashboard templates **(PREMIUM SELF)**
diff --git a/doc/operations/metrics/dashboards/index.md b/doc/operations/metrics/dashboards/index.md
index 052f678f1b7..152e3dca27d 100644
--- a/doc/operations/metrics/dashboards/index.md
+++ b/doc/operations/metrics/dashboards/index.md
@@ -33,10 +33,10 @@ To create a new dashboard from the GitLab user interface:
 1. Sign in to GitLab as a user with Maintainer or Owner
    [permissions](../../../user/permissions.md#project-members-permissions).
 1. Navigate to your dashboard at **Monitor > Metrics**.
-1. In the top-right corner of your dashboard, click the **{ellipsis_v}** **More actions** menu,
+1. In the top-right corner of your dashboard, select the **{ellipsis_v}** **More actions** menu,
    and select **Create new**:
    ![Monitoring Dashboard actions menu with create new item](img/actions_menu_create_new_dashboard_v13_3.png)
-1. In the modal window, click **Open Repository**, then follow the instructions
+1. In the modal window, select **Open Repository**, then follow the instructions
    for creating a new dashboard from the command line.
 
 To create a new dashboard from the command line:
@@ -84,7 +84,7 @@ with the **Add Panel** page:
 
 1. Sign in to GitLab as a user with Maintainer or Owner
    [permissions](../../../user/permissions.md#project-members-permissions).
-1. Click **Add panel** in the **{ellipsis_v}** **More actions** menu.
+1. Select **Add panel** in the **{ellipsis_v}** **More actions** menu.
 
    NOTE:
    You can only add panels to custom dashboards.
@@ -92,7 +92,7 @@ with the **Add Panel** page:
    ![Monitoring Dashboard actions menu with add panel item](img/actions_menu_create_add_panel_v13_3.png)
 1. In the **Define and preview panel** section, paste in the YAML you want to
    preview in the **Panel YAML** field.
-1. Click **Preview panel**, and GitLab displays a preview of the chart below the
+1. Select **Preview panel**, and GitLab displays a preview of the chart below the
    `Define and preview panel` section:
    ![Monitoring Dashboard Add Panel page](img/metrics_dashboard_panel_preview_v13_3.png)
 
@@ -106,8 +106,8 @@ The resulting `.yml` file can be customized and adapted to your project.
 You can decide to save the dashboard `.yml` file in the project's **default** branch or in a
 new branch. To duplicate a GitLab-defined dashboard:
 
-1. Click **Duplicate current dashboard** in the **{ellipsis_v}** **More actions** menu.
-1. Enter the filename and other information, such as the new commit's message, and click **Duplicate**.
+1. Select **Duplicate current dashboard** in the **{ellipsis_v}** **More actions** menu.
+1. Enter the filename and other information, such as the new commit's message, and select **Duplicate**.
 1. Select a branch to add your dashboard to:
    - *If you select your **default** branch,* the new dashboard becomes immediately available.
    - *If you select another branch,* this branch should be merged to your **default** branch first.
@@ -133,7 +133,7 @@ any chart on a dashboard:
 The options are:
 
 - **Expand panel** - Displays a larger version of a visualization. To return to
-  the dashboard, click the **Back** button in your browser, or press the <kbd>Escape</kbd> key.
+  the dashboard, select the **Back** button in your browser, or press the <kbd>Escape</kbd> key.
   ([Introduced](https://gitlab.com/groups/gitlab-org/-/epics/3100) in GitLab 13.0.)
 - **View logs** **(ULTIMATE)** - Displays [Logs](../../../user/project/clusters/kubernetes_pod_logs.md),
   if they are enabled. If used in conjunction with the [timeline zoom](#timeline-zoom-and-url-sharing)
@@ -146,7 +146,7 @@ The options are:
 > [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/198910) in GitLab 12.8.
 
 You can use the **Timeline zoom** function at the bottom of a chart to zoom in
-on a date and time of your choice. When you click and drag the sliders to select
+on a date and time of your choice. When you select and drag the sliders to select
 a different beginning or end date of data to display, GitLab adds your selected start
 and end times to the URL, enabling you to share specific time frames more easily.
 
diff --git a/doc/operations/metrics/dashboards/settings.md b/doc/operations/metrics/dashboards/settings.md
index aae5a623420..45f0e906e9c 100644
--- a/doc/operations/metrics/dashboards/settings.md
+++ b/doc/operations/metrics/dashboards/settings.md
@@ -28,12 +28,12 @@ time zone:
 
 1. Sign in as a user with Manage Project Operations [permissions](../../../user/permissions.md).
 1. Navigate to **Settings > Monitor**.
-1. Scroll to **Metrics Dashboard** and click **Expand**.
+1. Scroll to **Metrics Dashboard** and select **Expand**.
 1. In the **Dashboard timezone** select box, select *User's local timezone*
    or *UTC*:
 
    ![Dashboard timezone setting](img/dashboard_local_timezone_v13_1.png)
-1. Click **Save changes**.
+1. Select **Save changes**.
 
 ## Link to an external dashboard
 
@@ -44,12 +44,12 @@ existing external dashboards:
 
 1. Sign in as a user with Manage Project Operations [permissions](../../../user/permissions.md).
 1. Navigate to **Settings > Monitor**.
-1. Scroll to **Metrics Dashboard** and click **Expand**.
+1. Scroll to **Metrics Dashboard** and select **Expand**.
 1. In **External dashboard URL**, provide the URL to your external dashboard:
 
    ![External Dashboard Setting](img/dashboard_external_link_v13_1.png)
 
-1. Click **Save changes**.
+1. Select **Save changes**.
 
 GitLab displays a **View full dashboard** button in the top right corner of your
 [monitoring dashboard](../../../ci/environments/index.md#monitor-environments)
diff --git a/doc/operations/metrics/embed.md b/doc/operations/metrics/embed.md
index 44b998dc3ee..3fd5daba4fb 100644
--- a/doc/operations/metrics/embed.md
+++ b/doc/operations/metrics/embed.md
@@ -48,8 +48,8 @@ GitLab unfurls the link as an embedded metrics panel:
 
 ![Embedded Metrics Rendered](img/embedded_metrics_rendered_v13_4.png)
 
-You can also embed a single chart. To get a link to a chart, click the
-**{ellipsis_v}** **More actions** menu in the upper right corner of the chart,
+You can also embed a single chart. To get a link to a chart, select
+**{ellipsis_v}** **More actions** in the upper right corner of the chart,
 and select **Copy link to chart**, as shown in this example:
 
 ![Copy Link To Chart](img/copy_link_to_chart_v12_10.png)
diff --git a/doc/operations/metrics/embed_grafana.md b/doc/operations/metrics/embed_grafana.md
index 5bfb097619d..700bf821a49 100644
--- a/doc/operations/metrics/embed_grafana.md
+++ b/doc/operations/metrics/embed_grafana.md
@@ -52,7 +52,7 @@ To set up the Grafana API in Grafana:
 1. To enable the integration, check the **Active** checkbox.
 1. For **Grafana URL**, enter the base URL of the Grafana instance.
 1. For **API Token**, enter the Administrator API token you just generated.
-1. Click **Save Changes**.
+1. Select **Save Changes**.
 
 ### Generate a link to a panel
 
@@ -61,10 +61,10 @@ To generate a link to a panel:
 1. In Grafana, go to the dashboard you wish to embed a panel from.
 1. In the upper-left corner of the page, select a specific value for each variable required for the
    queries in the dashboard.
-1. In Grafana click on a panel's title, then click **Share** to open the panel's sharing dialog to
+1. In Grafana select a panel's title, then select **Share** to open the panel's sharing dialog to
    the **Link** tab.
 
-   If you click the dashboard's share button instead, GitLab attempts to embed the first supported
+   If you select the dashboard's share button instead, GitLab attempts to embed the first supported
    panel on the dashboard (if available).
 1. If your Prometheus queries use Grafana's custom template variables, ensure the
    **Template variables** option is set to on. Only the Grafana global template variables
diff --git a/doc/operations/metrics/index.md b/doc/operations/metrics/index.md
index 937bd329570..916fe6b0ea9 100644
--- a/doc/operations/metrics/index.md
+++ b/doc/operations/metrics/index.md
@@ -87,7 +87,7 @@ navigation bar contains:
   [custom dashboards](dashboards/index.md).
   ([Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/34779) in GitLab 12.5.)
   - **Duplicate current dashboard** - Save a [complete copy of a dashboard](dashboards/index.md#duplicate-a-gitlab-defined-dashboard). Only available on GitLab-defined dashboards.
-  - **Star dashboard** **{star-o}** - Click to mark a dashboard as a favorite.
+  - **Star dashboard** **{star-o}** - Mark a dashboard as a favorite.
   Starred dashboards display a solid star **{star}** button, and display first
   in the **Dashboard** dropdown list.
   ([Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/214582) in GitLab 13.0.)
diff --git a/doc/operations/tracing.md b/doc/operations/tracing.md
index e68d7077328..45f2febd73e 100644
--- a/doc/operations/tracing.md
+++ b/doc/operations/tracing.md
@@ -46,6 +46,6 @@ GitLab provides an easy way to open the Jaeger UI from within your project:
 1. [Set up Jaeger](https://www.jaegertracing.io) and configure your application using one of the
    [client libraries](https://www.jaegertracing.io/docs/latest/client-libraries/).
 1. Navigate to your project's **Settings > Monitor** and provide the Jaeger URL.
-1. Click **Save changes** for the changes to take effect.
+1. Select **Save changes** for the changes to take effect.
 1. You can now visit **Monitor > Tracing** in your project's sidebar and GitLab redirects you to
    the configured Jaeger URL.