Add latest changes from gitlab-org/gitlab@master

6 files changed, 14 insertions, 14 deletions

diff --git a/doc/ci/environments/environments_dashboard.md b/doc/ci/environments/environments_dashboard.md
index 8ff31827ae7..c3c1e7868fd 100644
--- a/doc/ci/environments/environments_dashboard.md
+++ b/doc/ci/environments/environments_dashboard.md
@@ -36,9 +36,9 @@ environments are not displayed.
 
 To add a project to the dashboard:
 
-1. Click the **Add projects** button in the home screen of the dashboard.
+1. Select **Add projects** in the home screen of the dashboard.
 1. Search and add one or more projects using the **Search your projects** field.
-1. Click the **Add projects** button.
+1. Select **Add projects**.
 
 Once added, you can see a summary of each project's environment operational
 health, including the latest commit, pipeline status, and deployment time.
diff --git a/doc/ci/environments/incremental_rollouts.md b/doc/ci/environments/incremental_rollouts.md
index d359ed078ff..ee2e708f822 100644
--- a/doc/ci/environments/incremental_rollouts.md
+++ b/doc/ci/environments/incremental_rollouts.md
@@ -63,7 +63,7 @@ rollout 10%:
     ROLLOUT_PERCENTAGE: 10
 ```
 
-When the jobs are built, a **play** button appears next to the job's name. Click the **play** button
+When the jobs are built, a **play** button appears next to the job's name. Select **play**
 to release each stage of pods. You can also rollback by running a lower percentage job. Once 100%
 is reached, you cannot roll back using this method. It is still possible to roll back by redeploying
 the old version using the **Rollback** button on the environment page.
diff --git a/doc/ci/pipelines/settings.md b/doc/ci/pipelines/settings.md
index 2a95a4e1421..379f002753e 100644
--- a/doc/ci/pipelines/settings.md
+++ b/doc/ci/pipelines/settings.md
@@ -92,7 +92,7 @@ For more information, see [Deployment safety](../environments/deployment_safety.
 > [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/211339) in GitLab 13.6.
 
 A deployment job can fail because a newer one has run. If you retry the failed deployment job, the
-environment could be overwritten with older source code. If you click **Retry**, a modal warns you
+environment could be overwritten with older source code. If you select **Retry**, a modal warns you
 about this and asks for confirmation.
 
 For more information, see [Deployment safety](../environments/deployment_safety.md).
diff --git a/doc/ci/runners/configure_runners.md b/doc/ci/runners/configure_runners.md
index a5e567ad461..221060f89c5 100644
--- a/doc/ci/runners/configure_runners.md
+++ b/doc/ci/runners/configure_runners.md
@@ -85,9 +85,9 @@ To protect or unprotect a runner:
 
 1. Go to the project's **Settings > CI/CD** and expand the **Runners** section.
 1. Find the runner you want to protect or unprotect. Make sure it's enabled.
-1. Click the pencil button.
+1. Select the pencil button.
 1. Check the **Protected** option.
-1. Click **Save changes**.
+1. Select **Save changes**.
 
 ![specific runners edit icon](img/protected_runners_check_box_v14_1.png)
 
@@ -113,7 +113,7 @@ To reset the registration token:
 
 1. Go to the project's **Settings > CI/CD**.
 1. Expand the **General pipelines settings** section.
-1. Find the **Runner token** form field and click the **Reveal value** button.
+1. Find the **Runner token** form field and select **Reveal value**.
 1. Delete the value and save the form.
 1. After the page is refreshed, expand the **Runners settings** section
    and check the registration token - it should be changed.
@@ -193,9 +193,9 @@ To make a runner pick untagged jobs:
 
 1. Go to the project's **Settings > CI/CD** and expand the **Runners** section.
 1. Find the runner you want to pick untagged jobs and make sure it's enabled.
-1. Click the pencil button.
+1. Select the pencil button.
 1. Check the **Run untagged jobs** option.
-1. Click the **Save changes** button for the changes to take effect.
+1. Select **Save changes** for the changes to take effect.
 
 NOTE:
 The runner tags list can not be empty when it's not allowed to pick untagged jobs.
diff --git a/doc/ci/runners/runners_scope.md b/doc/ci/runners/runners_scope.md
index 01032c116df..8b2753d26f1 100644
--- a/doc/ci/runners/runners_scope.md
+++ b/doc/ci/runners/runners_scope.md
@@ -84,7 +84,7 @@ To disable shared runners for a group:
 1. Go to the group's **Settings > CI/CD** and expand the **Runners** section.
 1. In the **Shared runners** area, turn off the **Enable shared runners for this group** toggle.
 1. Optionally, to allow shared runners to be enabled for individual projects or subgroups,
-   click **Allow projects and subgroups to override the group setting**.
+   select **Allow projects and subgroups to override the group setting**.
 
 NOTE:
 To re-enable the shared runners for a group, turn on the
@@ -200,11 +200,11 @@ You must have the Owner role for the group.
 
 1. Go to the group you want to remove or pause the runner for.
 1. On the left sidebar, select **CI/CD > Runners**.
-1. Click **Pause** or **Remove runner**.
+1. Select **Pause** or **Remove runner**.
    - If you pause a group runner that is used by multiple projects, the runner pauses for all projects.
    - From the group view, you cannot remove a runner that is assigned to more than one project.
      You must remove it from each project first.
-1. On the confirmation dialog, click **OK**.
+1. On the confirmation dialog, select **OK**.
 
 ## Specific runners
 
diff --git a/doc/ci/secure_files/index.md b/doc/ci/secure_files/index.md
index 673dca65335..fb421ab8944 100644
--- a/doc/ci/secure_files/index.md
+++ b/doc/ci/secure_files/index.md
@@ -34,8 +34,8 @@ Additional features and capabilities are planned.
 
 To add a secure file to a project:
 
-1. On the top bar, select **Menu > Projects** and find your project. 
-1. On the left sidebar, select **Settings > CI/CD**. 
+1. On the top bar, select **Menu > Projects** and find your project.
+1. On the left sidebar, select **Settings > CI/CD**.
 1. In the **Secure Files** section, select **Manage**.
 1. Select **Upload File**.
 1. Find the file to upload, select **Open**, and the file upload begins immediately.