diff --git a/doc/administration/auth/cognito.md b/doc/administration/auth/cognito.md
index 66f8407894caef4a13ee495400db9dec3b818095..db8cdd3e7bb148cdc4b18c57afc7a4da642239b0 100644
--- a/doc/administration/auth/cognito.md
+++ b/doc/administration/auth/cognito.md
@@ -18,13 +18,13 @@ The following steps enable AWS Cognito as an authentication provider:
 
 1. Sign in to the [AWS console](https://console.aws.amazon.com/console/home).
 1. Select **Cognito** from the **Services** menu.
-1. Select **Manage User Pools**, and click the **Create a user pool** button in the top right corner.
-1. Enter the pool name and then click the **Step through settings** button.
+1. Select **Manage User Pools**, and select the **Create a user pool** button in the top right corner.
+1. Enter the pool name and then select the **Step through settings** button.
 1. Under **How do you want your end users to sign in?**, select **Email address or phone number** and **Allow email addresses**.
 1. Under **Which standard attributes do you want to require?**, select **email**.
 1. Go to the next steps of configuration and set the rest of the settings to suit your needs - in the basic setup they are not related to GitLab configuration.
-1. In the **App clients** settings, click **Add an app client**, add **App client name** and select the **Enable username password based authentication** checkbox.
-1. Click **Create app client**.
+1. In the **App clients** settings, select **Add an app client**, add **App client name** and select the **Enable username password based authentication** checkbox.
+1. Select **Create app client**.
 1. In the next step, you can set up AWS Lambda functions for sending emails. You can then finish creating the pool.
 1. After creating the user pool, go to **App client settings** and provide the required information:
 
@@ -85,7 +85,7 @@ Include the code block in the `/etc/gitlab/gitlab.rb` file:
 1. Save the file and [reconfigure](../restart_gitlab.md#omnibus-gitlab-reconfigure) GitLab for the changes to take effect.
 
 Your sign-in page should now display a Cognito button below the regular sign-in form.
-To begin the authentication process, click the icon, and AWS Cognito asks the user to sign in and authorize the GitLab application.
+To begin the authentication process, select the icon, and AWS Cognito asks the user to sign in and authorize the GitLab application.
 If successful, the user is redirected and signed in to your GitLab instance.
 
 For more information, see [Configure initial settings](../../integration/omniauth.md#configure-initial-settings).
diff --git a/doc/administration/auth/jwt.md b/doc/administration/auth/jwt.md
index 98f928fd7eec19de96b13a66dc3b30a02fc65709..99cba3f220d0596a1ce2b31808a68ad7eac5cc30 100644
--- a/doc/administration/auth/jwt.md
+++ b/doc/administration/auth/jwt.md
@@ -74,7 +74,7 @@ JWT provides you with a secret key for you to use.
    installed GitLab via Omnibus or from source respectively.
 
 On the sign in page there should now be a JWT icon below the regular sign in form.
-Click the icon to begin the authentication process. JWT asks the user to
+Select the icon to begin the authentication process. JWT asks the user to
 sign in and authorize the GitLab application. If everything goes well, the user
 is redirected to GitLab and signed in.
 
diff --git a/doc/administration/auth/ldap/google_secure_ldap.md b/doc/administration/auth/ldap/google_secure_ldap.md
index 10745c5e2bfdd86874e1cd0507bfed9f5f7ad4da..7f399f7e7301fd5be036c094bba61fcb2c618ad9 100644
--- a/doc/administration/auth/ldap/google_secure_ldap.md
+++ b/doc/administration/auth/ldap/google_secure_ldap.md
@@ -26,7 +26,7 @@ The steps below cover:
 
 1. Provide an `LDAP client name` and an optional `Description`. Any descriptive
    values are acceptable. For example, the name could be 'GitLab' and the
-   description could be 'GitLab LDAP Client'. Click the **Continue** button.
+   description could be 'GitLab LDAP Client'. Select the **Continue** button.
 
    ![Add LDAP Client Step 1](img/google_secure_ldap_add_step_1.png)
 
@@ -42,15 +42,15 @@ The steps below cover:
 
 1. Download the generated certificate. This is required for GitLab to
    communicate with the Google Secure LDAP service. Save the downloaded certificates
-   for later use. After downloading, click the **Continue to Client Details** button.
+   for later use. After downloading, select the **Continue to Client Details** button.
 
 1. Expand the **Service Status** section and turn the LDAP client 'ON for everyone'.
-   After selecting 'Save', click on the 'Service Status' bar again to collapse
+   After selecting 'Save', select the 'Service Status' bar again to collapse
    and return to the rest of the settings.
 
 1. Expand the **Authentication** section and choose 'Generate New Credentials'.
-   Copy/note these credentials for later use. After selecting 'Close', click
-   on the 'Authentication' bar again to collapse and return to the rest of the settings.
+   Copy/note these credentials for later use. After selecting 'Close', select
+   the 'Authentication' bar again to collapse and return to the rest of the settings.
 
 Now the Google Secure LDAP Client configuration is finished. The screenshot below
 shows an example of the final settings. Continue on to configure GitLab.
diff --git a/doc/administration/auth/oidc.md b/doc/administration/auth/oidc.md
index 561cbd1b3ae5831b2b6aabaf01c5884193b2f457..deb47160d98236a0ecedb4be34d2b1955faffd63 100644
--- a/doc/administration/auth/oidc.md
+++ b/doc/administration/auth/oidc.md
@@ -120,7 +120,7 @@ The OpenID Connect provides you with a client's details and secret for you to us
    for the changes to take effect if you installed GitLab via Omnibus or from source respectively.
 
 On the sign in page, there should now be an OpenID Connect icon below the regular sign in form.
-Click the icon to begin the authentication process. The OpenID Connect provider asks the user to
+Select the icon to begin the authentication process. The OpenID Connect provider asks the user to
 sign in and authorize the GitLab application (if confirmation required by the client). If everything goes well, the user
 is redirected to GitLab and signed in.
 
diff --git a/doc/administration/geo/replication/location_aware_git_url.md b/doc/administration/geo/replication/location_aware_git_url.md
index 8689fac987fd193524dbba8124192beb54c20287..27deafeba819d797c67a1783b09425de078c4db1 100644
--- a/doc/administration/geo/replication/location_aware_git_url.md
+++ b/doc/administration/geo/replication/location_aware_git_url.md
@@ -57,34 +57,34 @@ routing configurations.
 
    ![Traffic policies](img/single_git_traffic_policies.png)
 
-1. Click the **Create traffic policy** button.
+1. Select the **Create traffic policy** button.
 
    ![Name policy](img/single_git_name_policy.png)
 
-1. Fill in the **Policy Name** field with `Single Git Host` and click **Next**.
+1. Fill in the **Policy Name** field with `Single Git Host` and select **Next**.
 
    ![Policy diagram](img/single_git_policy_diagram.png)
 
 1. Leave **DNS type** as `A: IP Address in IPv4 format`.
-1. Click **Connect to...** and select **Geolocation rule**.
+1. Select **Connect to...** and select **Geolocation rule**.
 
    ![Add geolocation rule](img/single_git_add_geolocation_rule.png)
 
 1. For the first **Location**, leave it as `Default`.
-1. Click **Connect to...** and select **New endpoint**.
+1. Select **Connect to...** and select **New endpoint**.
 1. Choose **Type** `value` and fill it in with `<your **primary** IP address>`.
 1. For the second **Location**, choose `Europe`.
-1. Click **Connect to...** and select **New endpoint**.
+1. Select **Connect to...** and select **New endpoint**.
 1. Choose **Type** `value` and fill it in with `<your **secondary** IP address>`.
 
    ![Add traffic policy endpoints](img/single_git_add_traffic_policy_endpoints.png)
 
-1. Click **Create traffic policy**.
+1. Select **Create traffic policy**.
 
    ![Create policy records with traffic policy](img/single_git_create_policy_records_with_traffic_policy.png)
 
 1. Fill in **Policy record DNS name** with `git`.
-1. Click **Create policy records**.
+1. Select **Create policy records**.
 
    ![Created policy record](img/single_git_created_policy_record.png)
 
diff --git a/doc/topics/autodevops/customize.md b/doc/topics/autodevops/customize.md
index e278e95378ced9a6816edd0b18947bd668e5e899..43731176e3f396849d2f6e1643faa3124f637809 100644
--- a/doc/topics/autodevops/customize.md
+++ b/doc/topics/autodevops/customize.md
@@ -670,7 +670,7 @@ The percentage is based on the `REPLICAS` CI/CD variable, and defines the number
 pods you want to have for your deployment. If the value is `10`, and you run the
 `10%` rollout job, there is `1` new pod and `9` old ones.
 
-To start a job, click the play icon (**{play}**) next to the job's name. You're not
+To start a job, select the play icon (**{play}**) next to the job's name. You're not
 required to go from `10%` to `100%`, you can jump to whatever job you want.
 You can also scale down by running a lower percentage job, just before hitting
 `100%`. Once you get to `100%`, you can't scale down, and you'd have to roll
diff --git a/doc/topics/git/feature_branch_development.md b/doc/topics/git/feature_branch_development.md
index ae1485741a5c9d9729d538ef32f8ab1459eb6585..771aa8c7a950e4396dd3caa3dc4f61b46767b000 100644
--- a/doc/topics/git/feature_branch_development.md
+++ b/doc/topics/git/feature_branch_development.md
@@ -83,7 +83,7 @@ we have selected `test-branch` as the source, and `release-13-0` as the target.
 
    ![Modify branches](img/modify_branches_v13_1.png)
 
-1. Once you've selected the Source and Target branches, click **Compare branches and continue**.
+1. Once you've selected the Source and Target branches, select **Compare branches and continue**.
    You should see an entry similar to:
 
    ```plaintext
@@ -94,7 +94,7 @@ we have selected `test-branch` as the source, and `release-13-0` as the target.
 
    An entry like this confirms your merge request's destination.
 
-1. Make any additional changes in the **New Merge Request** screen, and click **Submit merge request**.
+1. Make any additional changes in the **New Merge Request** screen, and select **Submit merge request**.
 1. In the new merge request, look for **Request to merge**. An entry similar to this displays:
 
    ```plaintext
diff --git a/doc/topics/git/lfs/migrate_to_git_lfs.md b/doc/topics/git/lfs/migrate_to_git_lfs.md
index 32e3b6e2f729d6598631d946f6264d0be672e9e4..864615e7264d1dc2a2fc653db7c2af5493c91281 100644
--- a/doc/topics/git/lfs/migrate_to_git_lfs.md
+++ b/doc/topics/git/lfs/migrate_to_git_lfs.md
@@ -121,7 +121,7 @@ Consider an example upstream project, `git@gitlab.com:gitlab-tests/test-git-lfs-
 
    1. Navigate to your project's **Settings > Repository** and
    expand **Protected branches**.
-   1. Scroll down to locate the protected branches and click
+   1. Scroll down to locate the protected branches and select
    **Unprotect** the default branch.
 
 1. Force-push to GitLab:
@@ -162,7 +162,7 @@ Consider an example upstream project, `git@gitlab.com:gitlab-tests/test-git-lfs-
    1. Select the default branch from the **Branch** dropdown menu,
    and set up the
    **Allowed to push** and **Allowed to merge** rules.
-   1. Click **Protect**.
+   1. Select **Protect**.
 
 <!-- ## Troubleshooting
 
diff --git a/doc/topics/offline/quick_start_guide.md b/doc/topics/offline/quick_start_guide.md
index 4426f955cb7435e75cc3e1a45e511f642cc570bb..2426fc8f87d775be465356e7c1f95ff3eaa38c80 100644
--- a/doc/topics/offline/quick_start_guide.md
+++ b/doc/topics/offline/quick_start_guide.md
@@ -202,7 +202,7 @@ done.
 ### Disable Version Check and Service Ping
 
 The Version Check and Service Ping services improve the GitLab user experience and ensure that
-users are on the most up-to-date instances of GitLab. These two services can be turned off for air-gapped
+users are on the most up-to-date instances of GitLab. These two services can be turned off for offline
 environments so that they do not attempt and fail to reach out to GitLab services.
 
 Learn more about [disabling usage statistics](../../user/admin_area/settings/usage_statistics.md#enable-or-disable-usage-statistics).
diff --git a/doc/user/application_security/api_fuzzing/index.md b/doc/user/application_security/api_fuzzing/index.md
index 3582572e480fe008302a63eb38c95fbae65288d2..7b9655f0b6e68fa355db6df3eb5c1f1a5567065e 100644
--- a/doc/user/application_security/api_fuzzing/index.md
+++ b/doc/user/application_security/api_fuzzing/index.md
@@ -883,7 +883,7 @@ Adding some basic logging to your overrides script is useful in case the script
 Following our example, we provided `renew_token.py` in the environmental variable `FUZZAPI_OVERRIDES_CMD`. Please notice two things in the script:
 
 - Log file is saved in the location indicated by the environment variable `CI_PROJECT_DIR`.
-- Log file name should match `gl-*.log`.
+- Log filename should match `gl-*.log`.
 
 ```python
 #!/usr/bin/env python
@@ -1476,9 +1476,9 @@ Follow these steps to view details of a fuzzing fault:
 
    - In a project, go to the project's **{shield}** **Security & Compliance > Vulnerability Report**
      page. This page shows all vulnerabilities from the default branch only.
-   - In a merge request, go the merge request's **Security** section and click the **Expand**
+   - In a merge request, go the merge request's **Security** section and select the **Expand**
      button. API Fuzzing faults are available in a section labeled
-     **API Fuzzing detected N potential vulnerabilities**. Click the title to display the fault
+     **API Fuzzing detected N potential vulnerabilities**. Select the title to display the fault
      details.
 
 1. Select the fault's title to display the fault's details. The table below describes these details.
diff --git a/doc/user/application_security/dast/index.md b/doc/user/application_security/dast/index.md
index 1389db657138e5c4eaebbf72b616d1dd424968d6..f3dfbbb4d5f430b28dd921fbae575f4af3357f76 100644
--- a/doc/user/application_security/dast/index.md
+++ b/doc/user/application_security/dast/index.md
@@ -493,7 +493,7 @@ To perform a [full scan](#full-scan) on the listed paths, use the `DAST_FULL_SCA
 ### List URLs scanned
 
 When DAST completes scanning, the merge request page states the number of URLs scanned.
-Click **View details** to view the web console output which includes the list of scanned URLs.
+Select **View details** to view the web console output which includes the list of scanned URLs.
 
 ![DAST Widget](img/dast_urls_scanned_v12_10.png)
 
@@ -846,7 +846,7 @@ Many web applications show the user the login form in a pop-up (modal) window.
 For these applications, navigating to the form requires both:
 
 - A starting URL.
-- A list of elements to click to display the modal window.
+- A list of elements to select to display the modal window.
 
 When `DAST_BROWSER_PATH_TO_LOGIN_FORM` is present, like in this example:
 
diff --git a/doc/user/application_security/dast_api/index.md b/doc/user/application_security/dast_api/index.md
index d4e5e9dbab31bd0b46e27905ecf4987eaf0d5e62..72e495924fa8009702bb017a3069221c6978044a 100644
--- a/doc/user/application_security/dast_api/index.md
+++ b/doc/user/application_security/dast_api/index.md
@@ -837,7 +837,7 @@ Adding some basic logging to your overrides script is useful in case the script
 Following our example, we provided `renew_token.py` in the environment variable `DAST_API_OVERRIDES_CMD`. Please notice two things in the script:
 
 - Log file is saved in the location indicated by the environmental variable `CI_PROJECT_DIR`.
-- Log file name should match `gl-*.log`.
+- Log filename should match `gl-*.log`.
 
 ```python
 #!/usr/bin/env python
@@ -1332,12 +1332,12 @@ Follow these steps to view details of a vulnerability:
 
    - In a project, go to the project's **{shield}** **Security & Compliance > Vulnerability Report**
      page. This page shows all vulnerabilities from the default branch only.
-   - In a merge request, go the merge request's **Security** section and click the **Expand**
+   - In a merge request, go the merge request's **Security** section and select the **Expand**
      button. DAST API vulnerabilities are available in a section labeled
-     **DAST detected N potential vulnerabilities**. Click the title to display the vulnerability
+     **DAST detected N potential vulnerabilities**. Select the title to display the vulnerability
      details.
 
-1. Click the vulnerabilities title to display the details. The table below describes these details.
+1. Select the vulnerabilities title to display the details. The table below describes these details.
 
    | Field               | Description                                                                             |
    |:--------------------|:----------------------------------------------------------------------------------------|
diff --git a/doc/user/application_security/vulnerability_report/index.md b/doc/user/application_security/vulnerability_report/index.md
index e499ddbbd6bf97c9d577e8461d93ee08ab775faa..7c1ea6a4e3c84a717f9b86d2300395ef4e6193cd 100644
--- a/doc/user/application_security/vulnerability_report/index.md
+++ b/doc/user/application_security/vulnerability_report/index.md
@@ -249,7 +249,7 @@ To add a new vulnerability finding from your project level Vulnerability Report
 
 1. On the top bar, select **Menu > Projects** and find your project.
 1. On the left sidebar, select **Security & Compliance > Vulnerability Report**.
-1. Click on **Submit Vulnerability**.
+1. Select **Submit Vulnerability**.
 1. Complete the fields and submit the form.
 
 You will be brought to the newly created vulnerability's detail page. Manually created records appear in the
diff --git a/doc/user/group/saml_sso/scim_setup.md b/doc/user/group/saml_sso/scim_setup.md
index bc1799c2e54be9d9937692db90c44acd8867edab..42cf442ea94d3c055d68b5a2ce1a9bc3e0278fe3 100644
--- a/doc/user/group/saml_sso/scim_setup.md
+++ b/doc/user/group/saml_sso/scim_setup.md
@@ -112,7 +112,7 @@ After the above steps are complete:
 1. Sign in to Okta.
 1. Ensure you are in the Admin Area by selecting the **Admin** button located in the top right. The button is not visible from the Admin Area.
 1. In the **Application** tab, select **Browse App Catalog**.
-1. Search for **GitLab**, find and select on the 'GitLab' application.
+1. Search for **GitLab**, find and select the 'GitLab' application.
 1. On the GitLab application overview page, select **Add**.
 1. Under **Application Visibility** select both checkboxes. Currently the GitLab application does not support SAML authentication so the icon should not be shown to users.
 1. Select **Done** to finish adding the application.
diff --git a/doc/user/profile/account/two_factor_authentication.md b/doc/user/profile/account/two_factor_authentication.md
index a820cf150e9eee25996ff87b0074f53c1f9f409b..f19d14fa035a1ab41af577f3dc99c0b0fe552a5e 100644
--- a/doc/user/profile/account/two_factor_authentication.md
+++ b/doc/user/profile/account/two_factor_authentication.md
@@ -206,7 +206,7 @@ To set up 2FA with a U2F device:
 1. Select **Account**.
 1. Select **Enable Two-Factor Authentication**.
 1. Connect your U2F device.
-1. Select on **Set up New U2F Device**.
+1. Select **Set up New U2F Device**.
 1. A light begins blinking on your device. Activate it by pressing its button.
 
 A message displays indicating that your device was successfully set up. Select **Register U2F Device** to complete the
diff --git a/doc/user/project/clusters/add_eks_clusters.md b/doc/user/project/clusters/add_eks_clusters.md
index 935bc01bae79b876af101e2fe93fbcf8c342dc79..49671cd67aa105bd23c3ad4eafae07f993a00879 100644
--- a/doc/user/project/clusters/add_eks_clusters.md
+++ b/doc/user/project/clusters/add_eks_clusters.md
@@ -58,7 +58,7 @@ cluster certificates:
    - Group's **Kubernetes** page, for a group-level cluster.
    - **Menu > Admin > Kubernetes**, for an instance-level cluster.
 1. Select **Integrate with a cluster certificate**.
-1. Under the **Create new cluster** tab, click **Amazon EKS** to display an
+1. Under the **Create new cluster** tab, select **Amazon EKS** to display an
    `Account ID` and `External ID` needed for later steps.
 1. In the [IAM Management Console](https://console.aws.amazon.com/iam/home), create an IAM policy:
    1. From the left panel, select **Policies**.
@@ -116,8 +116,8 @@ cluster certificates:
       If you get an error during this process, GitLab does not roll back the changes. You must remove resources manually. You can do this by deleting
       the relevant [CloudFormation stack](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/cfn-console-delete-stack.html).
 
-   1. Click **Review policy**.
-   1. Enter a suitable name for this policy, and click **Create Policy**. You can now close this window.
+   1. Select **Review policy**.
+   1. Enter a suitable name for this policy, and select **Create Policy**. You can now close this window.
 
 ### Prepare the cluster in Amazon
 
@@ -145,11 +145,11 @@ create another IAM role (**role B**) for GitLab authentication with AWS:
 1. Enter the Account ID from GitLab into the **Account ID** field.
 1. Check **Require external ID**.
 1. Enter the External ID from GitLab into the **External ID** field.
-1. Click **Next: Permissions**, and select the policy you just created.
-1. Click **Next: Tags**, and optionally enter any tags you wish to associate with this role.
-1. Click **Next: Review**.
+1. Select **Next: Permissions**, and select the policy you just created.
+1. Select **Next: Tags**, and optionally enter any tags you wish to associate with this role.
+1. Select **Next: Review**.
 1. Enter a role name and optional description into the fields provided.
-1. Click **Create role**. The new role name displays at the top. Click on its name and copy the
+1. Select **Create role**. The new role name displays at the top. Select its name and copy the
    `Role ARN` from the newly created role.
 
 ### Configure your cluster's data in GitLab
@@ -213,7 +213,7 @@ Otherwise, the deployed app isn't externally available outside of the cluster.
 GitLab creates a new pipeline, which begins to build, test, and deploy the app.
 
 After the pipeline has finished, your app runs in EKS, and is available
-to users. Click on **CI/CD > Environments**.
+to users. Select **CI/CD > Environments**.
 
 ![Deployed Environment](img/environment.png)
 
@@ -252,7 +252,7 @@ IAM user in the Amazon AWS console, and follow these steps:
 1. Check **Enable Amazon EKS integration**.
 1. Enter your **Account ID**.
 1. Enter your [access key and ID](#eks-access-key-and-id).
-1. Click **Save changes**.
+1. Select **Save changes**.
 
 #### EKS access key and ID
 
diff --git a/doc/user/project/deploy_boards.md b/doc/user/project/deploy_boards.md
index 42c1b8b0a62ed4a65c17786559ea4d2922a7a0a5..a90ffbe579676042232c595e614fa705538338b9 100644
--- a/doc/user/project/deploy_boards.md
+++ b/doc/user/project/deploy_boards.md
@@ -69,7 +69,7 @@ specific environment, there are a lot of use cases. To name a few:
 
 - You want to promote what's running in staging, to production. You go to the
   environments list, verify that what's running in staging is what you think is
-  running, then click on the [manual job](../../ci/jobs/job_control.md#create-a-job-that-must-be-run-manually) to deploy to production.
+  running, then select the [manual job](../../ci/jobs/job_control.md#create-a-job-that-must-be-run-manually) to deploy to production.
 - You trigger a deploy, and you have many containers to upgrade so you know
   this takes a while (you've also throttled your deploy to only take down X
   containers at a time). But you need to tell someone when it's deployed, so you
@@ -80,7 +80,7 @@ specific environment, there are a lot of use cases. To name a few:
   stuck or failed.
 - You've got an MR that looks good, but you want to run it on staging because
   staging is set up in some way closer to production. You go to the environment
-  list, find the [Review App](../../ci/review_apps/index.md) you're interested in, and click the
+  list, find the [Review App](../../ci/review_apps/index.md) you're interested in, and select the
   manual action to deploy it to staging.
 
 ## Enabling deploy boards
@@ -129,7 +129,7 @@ To display the deploy boards for a specific [environment](../../ci/environments/
 Once all of the above are set up and the pipeline has run at least once,
 navigate to the environments page under **Deployments > Environments**.
 
-Deploy boards are visible by default. You can explicitly click
+Deploy boards are visible by default. You can explicitly select
 the triangle next to their respective environment name in order to hide them.
 
 ### Example manifest file
diff --git a/doc/user/project/integrations/discord_notifications.md b/doc/user/project/integrations/discord_notifications.md
index b7e25b815fcdfd926eb45c23f9c6a54958f57725..3780ea37c0be9a81b6d37e100ae081a389b82264 100644
--- a/doc/user/project/integrations/discord_notifications.md
+++ b/doc/user/project/integrations/discord_notifications.md
@@ -32,6 +32,6 @@ With the webhook URL created in the Discord channel, you can set up the Discord
 1. Ensure that the **Active** toggle is enabled.
 1. Check the checkboxes corresponding to the GitLab events for which you want to send notifications to Discord.
 1. Paste the webhook URL that you copied from the create Discord webhook step.
-1. Configure the remaining options and click the **Save changes** button.
+1. Configure the remaining options and select the **Save changes** button.
 
 The Discord channel you created the webhook for now receives notification of the GitLab events that were configured.
diff --git a/doc/user/project/issues/multiple_assignees_for_issues.md b/doc/user/project/issues/multiple_assignees_for_issues.md
index 279f297d01686986e3a8b476fb1fa8b775954f1d..105dcd529c81622a90a404a0a7db0293bb6efb6a 100644
--- a/doc/user/project/issues/multiple_assignees_for_issues.md
+++ b/doc/user/project/issues/multiple_assignees_for_issues.md
@@ -34,7 +34,7 @@ it clear that their role is complete.
 ## How it works
 
 From an opened issue, expand the right sidebar, locate the assignees entry,
-and click on **Edit**. From the dropdown menu, select as many users as you want
+and select **Edit**. From the dropdown menu, select as many users as you want
 to assign the issue to.
 
 ![adding multiple assignees](img/multiple_assignees.gif)
diff --git a/doc/user/project/merge_requests/cherry_pick_changes.md b/doc/user/project/merge_requests/cherry_pick_changes.md
index fb41ec3eff67ad70ea11c1d613517d685beaf017..14f3979cf34da4a26c0972e8fa049f0e694544c5 100644
--- a/doc/user/project/merge_requests/cherry_pick_changes.md
+++ b/doc/user/project/merge_requests/cherry_pick_changes.md
@@ -18,7 +18,7 @@ to cherry-pick the changes introduced by that merge request.
 
 ![Cherry-pick merge request](img/cherry_pick_changes_mr.png)
 
-After you click that button, a modal displays a
+After you select that button, a modal displays a
 [branch filter search box](../repository/branches/index.md#branch-filter-search-box)
 where you can choose to either:
 
@@ -69,12 +69,12 @@ git cherry-pick -m 2 7a39eb0
 You can cherry-pick merge requests from the same project, or forks of the same
 project, from the GitLab user interface:
 
-1. In the merge request's secondary menu, click **Commits** to display the commit details page.
-1. Click on the **Options** dropdown and select **Cherry-pick** to show the cherry-pick modal.
+1. In the merge request's secondary menu, select **Commits** to display the commit details page.
+1. Select the **Options** dropdown and select **Cherry-pick** to show the cherry-pick modal.
 1. In **Pick into project** and **Pick into branch**, select the destination project and branch:
    ![Cherry-pick commit](img/cherry_pick_into_project_v13_11.png)
 1. Optional. Select **Start a new merge request** if you're ready to create a merge request.
-1. Click **Cherry-pick**.
+1. Select **Cherry-pick**.
 
 ## Related topics
 
diff --git a/doc/user/project/merge_requests/code_quality.md b/doc/user/project/merge_requests/code_quality.md
index a57f1940977986674b938d1be7be9471eabdbfdd..623af914692f7154edfac1b7fde1b868c15d9ec6 100644
--- a/doc/user/project/merge_requests/code_quality.md
+++ b/doc/user/project/merge_requests/code_quality.md
@@ -256,7 +256,7 @@ This can be done:
 - For a single pipeline run:
 
   1. Go to **CI/CD > Pipelines**
-  1. Click **Run pipeline**
+  1. Select **Run pipeline**
   1. Add `CODE_QUALITY_DISABLED` as the variable key, with any value.
 
 ### Using with merge request pipelines
diff --git a/doc/user/project/merge_requests/csv_export.md b/doc/user/project/merge_requests/csv_export.md
index df527ec6ebffe05c410433fa28eb39ed8df63b2a..aaa9bec945f0390c3df3c8fc438301be28765dc4 100644
--- a/doc/user/project/merge_requests/csv_export.md
+++ b/doc/user/project/merge_requests/csv_export.md
@@ -10,7 +10,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w
 
 Exporting merge requests CSV enables you and your team to export all the data collected from merge requests into a comma-separated values (CSV) file, which stores tabular data in plain text.
 
-To export merge requests to CSV, navigate to your **Merge requests** from the sidebar of a project and click **Export to CSV**.
+To export merge requests to CSV, navigate to your **Merge requests** from the sidebar of a project and select **Export to CSV**.
 
 ## CSV Output
 
diff --git a/doc/user/project/merge_requests/drafts.md b/doc/user/project/merge_requests/drafts.md
index 637b682d6038b782b3f2cba6896d79ac216894e3..8e193fb84d0072408bc1c7f9820fb0dbcf39395f 100644
--- a/doc/user/project/merge_requests/drafts.md
+++ b/doc/user/project/merge_requests/drafts.md
@@ -23,9 +23,9 @@ the **Merge** button until you remove the **Draft** flag:
 
 There are several ways to flag a merge request as a draft:
 
-- **Viewing a merge request**: In the top right corner of the merge request, click **Mark as draft**.
+- **Viewing a merge request**: In the top right corner of the merge request, select **Mark as draft**.
 - **Creating or editing a merge request**: Add `[Draft]`, `Draft:` or `(Draft)` to
-  the beginning of the merge request's title, or click **Start the title with Draft:**
+  the beginning of the merge request's title, or select **Start the title with Draft:**
   below the **Title** field.
 - **Commenting in an existing merge request**: Add the `/draft`
   [quick action](../quick_actions.md#issues-merge-requests-and-epics)
@@ -40,14 +40,14 @@ There are several ways to flag a merge request as a draft:
 
 When a merge request is ready to be merged, you can remove the `Draft` flag in several ways:
 
-- **Viewing a merge request**: In the top right corner of the merge request, click **Mark as ready**.
+- **Viewing a merge request**: In the top right corner of the merge request, select **Mark as ready**.
   Users with at least the Developer role
-  can also scroll to the bottom of the merge request description and click **Mark as ready**:
+  can also scroll to the bottom of the merge request description and select **Mark as ready**:
 
   ![Mark as ready](img/draft_blocked_merge_button_v13_10.png)
 
 - **Editing an existing merge request**: Remove `[Draft]`, `Draft:` or `(Draft)`
-  from the beginning of the title, or click **Remove the Draft: prefix from the title**
+  from the beginning of the title, or select **Remove the Draft: prefix from the title**
   below the **Title** field.
 - **Commenting in an existing merge request**: Add the `/draft`
   [quick action](../quick_actions.md#issues-merge-requests-and-epics)
@@ -64,9 +64,9 @@ When viewing or searching in your project's merge requests list, you can include
 draft merge requests:
 
 1. Go to your project and select **Merge requests**.
-1. In the navigation bar, click **Open**, **Merged**, **Closed**, or **All** to
+1. In the navigation bar, select **Open**, **Merged**, **Closed**, or **All** to
    filter by merge request status.
-1. Click the search box to display a list of filters and select **Draft**, or
+1. Select the search box to display a list of filters and select **Draft**, or
    enter the word `draft`.
 1. Select `=`.
 1. Select **Yes** to include drafts, or **No** to exclude, and press **Return**
diff --git a/doc/user/project/merge_requests/merge_when_pipeline_succeeds.md b/doc/user/project/merge_requests/merge_when_pipeline_succeeds.md
index ac1c61f2e7274287070761acd169c886f7cb544a..104fb5ca900a29dc56342fa6d5f566bcf2f4e69e 100644
--- a/doc/user/project/merge_requests/merge_when_pipeline_succeeds.md
+++ b/doc/user/project/merge_requests/merge_when_pipeline_succeeds.md
@@ -16,7 +16,7 @@ finish and remember to merge the request manually.
 
 ## How it works
 
-When you click "Merge When Pipeline Succeeds", the status of the merge
+When you select "Merge When Pipeline Succeeds", the status of the merge
 request is updated to show the impending merge. If you can't wait
 for the pipeline to succeed, you can choose **Merge immediately**
 in the dropdown menu on the right of the main button.
diff --git a/doc/user/project/merge_requests/revert_changes.md b/doc/user/project/merge_requests/revert_changes.md
index 7b4a41f93390e79f06572f3592906d34f301eb90..8f433c138875769086968befd33d5fc095e1178a 100644
--- a/doc/user/project/merge_requests/revert_changes.md
+++ b/doc/user/project/merge_requests/revert_changes.md
@@ -22,7 +22,7 @@ to revert the changes introduced by that merge request.
 
 ![Revert merge request](img/cherry_pick_changes_mr.png)
 
-After you click that button, a modal appears where you can choose to
+After you select that button, a modal appears where you can choose to
 revert the changes directly into the selected branch or you can opt to
 create a new merge request with the revert changes.
 
diff --git a/doc/user/project/merge_requests/reviews/index.md b/doc/user/project/merge_requests/reviews/index.md
index eb5a54e611925776bb33bd6bf9a77dc5ebd75cf4..c222795e8a09aeba60800795bd81c6bc013a9daa 100644
--- a/doc/user/project/merge_requests/reviews/index.md
+++ b/doc/user/project/merge_requests/reviews/index.md
@@ -123,9 +123,9 @@ Use [attention requests](../index.md#request-attention-to-a-merge-request) inste
 After a reviewer completes their [merge request reviews](../../../discussions/index.md),
 the author of the merge request can request a new review from the reviewer:
 
-1. If the right sidebar in the merge request is collapsed, click the
+1. If the right sidebar in the merge request is collapsed, select the
    **{chevron-double-lg-left}** **Expand Sidebar** icon to expand it.
-1. In the **Reviewers** section, click the **Re-request a review** icon (**{redo}**)
+1. In the **Reviewers** section, select the **Re-request a review** icon (**{redo}**)
    next to the reviewer's name.
 
 GitLab creates a new [to-do item](../../../todos.md) for the reviewer, and sends
@@ -168,11 +168,11 @@ When bulk-editing merge requests in a project, you can edit the following attrib
 To update multiple project merge requests at the same time:
 
 1. In a project, go to **Merge requests**.
-1. Click **Edit merge requests**. A sidebar on the right-hand side of your screen appears with
+1. Select **Edit merge requests**. A sidebar on the right-hand side of your screen appears with
    editable fields.
 1. Select the checkboxes next to each merge request you want to edit.
 1. Select the appropriate fields and their values from the sidebar.
-1. Click **Update all**.
+1. Select **Update all**.
 
 ## Bulk edit merge requests at the group level **(PREMIUM)**
 
@@ -188,11 +188,11 @@ When bulk editing merge requests in a group, you can edit the following attribut
 To update multiple group merge requests at the same time:
 
 1. In a group, go to **Merge requests**.
-1. Click **Edit merge requests**. A sidebar on the right-hand side of your screen appears with
+1. Select **Edit merge requests**. A sidebar on the right-hand side of your screen appears with
    editable fields.
 1. Select the checkboxes next to each merge request you want to edit.
 1. Select the appropriate fields and their values from the sidebar.
-1. Click **Update all**.
+1. Select **Update all**.
 
 ## Associated features
 
diff --git a/doc/user/project/pages/custom_domains_ssl_tls_certification/index.md b/doc/user/project/pages/custom_domains_ssl_tls_certification/index.md
index d970c0f9ef4c2d39190673cfe3d4cfc9805ab9d8..ce35f8c3ebe6577f9c1fdb7dd775583bc27bef48 100644
--- a/doc/user/project/pages/custom_domains_ssl_tls_certification/index.md
+++ b/doc/user/project/pages/custom_domains_ssl_tls_certification/index.md
@@ -47,13 +47,13 @@ this document for an [overview on DNS records](dns_concepts.md).
 
 #### 1. Add a custom domain to Pages
 
-Navigate to your project's **Setting > Pages** and click **+ New domain**
+Navigate to your project's **Setting > Pages** and select **+ New domain**
 to add your custom domain to GitLab Pages. You can choose whether to:
 
 - Add an [SSL/TLS certificate](#adding-an-ssltls-certificate-to-pages).
 - Leave it blank (it can be added later).
 
-Click **Create New Domain**.
+Select **Create New Domain**.
 
 ![Add new domain](img/add_certificate_to_pages.png)
 
@@ -162,8 +162,8 @@ If you're using Cloudflare, check
 Once you have added all the DNS records:
 
 1. Go back at your project's **Settings > Pages**.
-1. Locate your domain name and click **Details**.
-1. Click the **Retry verification** button to activate your new domain.
+1. Locate your domain name and select **Details**.
+1. Select the **Retry verification** button to activate your new domain.
 
 ![Verify your domain](img/retry_domain_verification_v12_0.png)
 
@@ -241,10 +241,10 @@ can use the following setup:
 1. In GitLab, verify your domain.
 1. In Cloudflare, create a DNS `CNAME` record pointing `www` to `domain.com`.
 1. In Cloudflare, add a Page Rule pointing `www.domain.com` to `domain.com`:
-   - Navigate to your domain's dashboard and click **Page Rules**
+   - Navigate to your domain's dashboard and select **Page Rules**
      on the top nav.
-   - Click **Create Page Rule**.
-   - Enter the domain `www.domain.com` and click **+ Add a Setting**.
+   - Select **Create Page Rule**.
+   - Enter the domain `www.domain.com` and select **+ Add a Setting**.
    - From the dropdown menu, choose **Forwarding URL**, then select the
      status code **301 - Permanent Redirect**.
    - Enter the destination URL `https://domain.com`.
@@ -285,7 +285,7 @@ meet these requirements.
 - To add the certificate at the time you add a new domain, go to your
   project's **Settings > Pages > New Domain**, add the domain name and the certificate.
 - To add the certificate to a domain previously added, go to your
-  project's **Settings > Pages**, locate your domain name, click **Details** and **Edit** to add the certificate.
+  project's **Settings > Pages**, locate your domain name, select **Details** and **Edit** to add the certificate.
 
 ![Pages project - adding certificates](img/add_certificate_to_pages.png)
 
diff --git a/doc/user/project/pages/custom_domains_ssl_tls_certification/lets_encrypt_integration.md b/doc/user/project/pages/custom_domains_ssl_tls_certification/lets_encrypt_integration.md
index cb22a200514ed2f2e2aa95a029275d3988875fd8..184e4f345c1d7f17c729b96a0c1f68e7b6a66224 100644
--- a/doc/user/project/pages/custom_domains_ssl_tls_certification/lets_encrypt_integration.md
+++ b/doc/user/project/pages/custom_domains_ssl_tls_certification/lets_encrypt_integration.md
@@ -43,13 +43,13 @@ For **self-managed** GitLab instances, make sure your administrator has
 Once you've met the requirements, enable Let's Encrypt integration:
 
 1. Navigate to your project's **Settings > Pages**.
-1. Find your domain and click **Details**.
-1. Click **Edit** in the top-right corner.
+1. Find your domain and select **Details**.
+1. Select **Edit** in the top-right corner.
 1. Enable Let's Encrypt integration by switching **Automatic certificate management using Let's Encrypt**:
 
    ![Enable Let's Encrypt](img/lets_encrypt_integration_v12_1.png)
 
-1. Click **Save changes**.
+1. Select **Save changes**.
 
 Once enabled, GitLab obtains a LE certificate and add it to the
 associated Pages domain. GitLab also renews it automatically.
@@ -70,8 +70,8 @@ associated Pages domain. GitLab also renews it automatically.
 If you get an error **Something went wrong while obtaining the Let's Encrypt certificate**, first, make sure that your pages site is set to "Everyone" in your project's **Settings > General > Visibility**. This allows the Let's Encrypt Servers reach your pages site. Once this is confirmed, you can try obtaining the certificate again by following these steps:
 
 1. Go to your project's **Settings > Pages**.
-1. Click **Edit** on your domain.
-1. Click **Retry**.
+1. Select **Edit** on your domain.
+1. Select **Retry**.
 1. If you're still seeing the same error:
     1. Make sure you have properly set only one `CNAME` or `A` DNS record for your domain.
     1. Make sure your domain **doesn't have** an `AAAA` DNS record.
@@ -86,7 +86,7 @@ Another possible cause of this error is the `_redirects` file because the curren
 If you've enabled Let's Encrypt integration, but a certificate is absent after an hour and you see the message, "GitLab is obtaining a Let's Encrypt SSL certificate for this domain. This process can take some time. Please try again later.", try to remove and add the domain for GitLab Pages again by following these steps:
 
 1. Go to your project's **Settings > Pages**.
-1. Click **Remove** on your domain.
+1. Select **Remove** on your domain.
 1. [Add the domain again and verify it](index.md#1-add-a-custom-domain-to-pages).
 1. [Enable Let's Encrypt integration for your domain](#enabling-lets-encrypt-integration-for-your-custom-domain).
 1. If you still see the same message after some time:
diff --git a/doc/user/project/pages/getting_started/pages_new_project_template.md b/doc/user/project/pages/getting_started/pages_new_project_template.md
index b32d71a48871edb0af4aff9b7a8816958588417a..92baba6b9c6897348132417bd453c9394126f367 100644
--- a/doc/user/project/pages/getting_started/pages_new_project_template.md
+++ b/doc/user/project/pages/getting_started/pages_new_project_template.md
@@ -12,15 +12,15 @@ You can create a new project from a template and run the CI/CD pipeline to gener
 Use a template when you want to test GitLab Pages or start a new project that's already
 configured to generate a Pages site.
 
-1. From the top navigation, click the **+** button and select **New project**.
+1. From the top navigation, select the **+** button and select **New project**.
 1. Select **Create from Template**.
-1. Next to one of the templates starting with **Pages**, click **Use template**.
+1. Next to one of the templates starting with **Pages**, select **Use template**.
 
    ![Project templates for Pages](../img/pages_project_templates_v13_1.png)
 
-1. Complete the form and click **Create project**.
+1. Complete the form and select **Create project**.
 1. From the left sidebar, navigate to your project's **CI/CD > Pipelines**
-   and click **Run pipeline** to trigger GitLab CI/CD to build and deploy your
+   and select **Run pipeline** to trigger GitLab CI/CD to build and deploy your
    site.
 
 When the pipeline is finished, go to **Settings > Pages** to find the link to
diff --git a/doc/user/project/pages/introduction.md b/doc/user/project/pages/introduction.md
index 5846ceeb1b6c9be705bf79aea4c0f5e13ec88ffa..23cb62e479f59ecd93c885ad2ac1b1f1809c2cbc 100644
--- a/doc/user/project/pages/introduction.md
+++ b/doc/user/project/pages/introduction.md
@@ -71,7 +71,7 @@ To restrict access to your website, enable [GitLab Pages Access Control](pages_a
 
 If you ever feel the need to purge your Pages content, you can do so by going
 to your project's settings through the gear icon in the top right, and then
-navigating to **Pages**. Click the **Remove pages** button to delete your Pages
+navigating to **Pages**. Select the **Remove pages** button to delete your Pages
 website.
 
 ![Remove pages](img/remove_pages.png)
diff --git a/doc/user/project/pages/pages_access_control.md b/doc/user/project/pages/pages_access_control.md
index 9b747e0497377d21b85aa72a24f5406e1e264015..a3fe41936ccfa5fea1fd30689718dd74d520b63d 100644
--- a/doc/user/project/pages/pages_access_control.md
+++ b/doc/user/project/pages/pages_access_control.md
@@ -36,7 +36,7 @@ For a demonstration, see [Pages access controls](https://www.youtube.com/watch?v
      - **Only project members**: Only project members are able to browse the website.
      - **Everyone with access**: Everyone, both logged into and logged out of GitLab, is able to browse the website, no matter their project membership.
 
-1. Click **Save changes**. Note that your changes may not take effect immediately. GitLab Pages uses
+1. Select **Save changes**. Note that your changes may not take effect immediately. GitLab Pages uses
    a caching mechanism for efficiency. Your changes may not take effect until that cache is
    invalidated, which usually takes less than a minute.
 
diff --git a/doc/user/project/repository/web_editor.md b/doc/user/project/repository/web_editor.md
index 747bd690911d07971a43796b7b42b6e9a3f4e0bb..370a349b982941e4359677ade431998ee5acfdcc 100644
--- a/doc/user/project/repository/web_editor.md
+++ b/doc/user/project/repository/web_editor.md
@@ -14,7 +14,7 @@ dropdown menu.
 
 ## Create a file
 
-From a project's files page, click the '+' button to the right of the branch selector.
+From a project's files page, select the '+' button to the right of the branch selector.
 Choose **New file** from the dropdown.
 ![New file dropdown menu](img/web_editor_new_file_dropdown_v14_1.png)
 
@@ -24,7 +24,7 @@ defaults to the branch you were viewing in the file browser. If you enter
 a new branch name, a checkbox displays, allowing you to start a new merge
 request after you commit the changes.
 
-When you are satisfied with your new file, click **Commit Changes** at the bottom.
+When you are satisfied with your new file, select **Commit Changes** at the bottom.
 
 ![Create file editor](img/web_editor_new_file_editor_v14_1.png)
 
@@ -72,7 +72,7 @@ You don't need to construct these lines manually. Instead, you can:
 
 1. Hover over the number of a line you want to be highlighted when sharing.
 1. Right-click the number with your mouse.
-1. Click **Copy Link Address** in the context menu.
+1. Select **Copy Link Address** in the context menu.
 
    ![Link to a line](img/web_editor_line_link_v13_10.png)
 
@@ -82,7 +82,7 @@ The ability to create a file is great when the content is text. However, this
 doesn't work well for binary data such as images, PDFs, or other binary file types. In
 this case, you need to upload a file.
 
-From a project's files page, click the '+' button to the right of the branch
+From a project's files page, select the '+' button to the right of the branch
 selector. Choose **Upload file** from the dropdown:
 
 ![Upload file dropdown menu](img/web_editor_upload_file_dropdown_v14_1.png)
@@ -91,7 +91,7 @@ After the upload dialog pops up, there are two ways to upload your file. Either
 drag and drop a file on the popup or use the **click to upload** link. After you
 select a file to upload, a file preview displays.
 
-Enter a commit message, choose a branch, and click **Upload file** when you are
+Enter a commit message, choose a branch, and select **Upload file** when you are
 ready.
 
 ![Upload file dialog](img/web_editor_upload_file_dialog_v14_1.png)
@@ -101,13 +101,13 @@ ready.
 To keep files in the repository organized it is often helpful to create a new
 directory.
 
-From a project's files page, click the plus button (`+`) to the right of the branch selector.
+From a project's files page, select the plus button (`+`) to the right of the branch selector.
 Choose **New directory** from the dropdown.
 
 ![New directory dropdown](img/web_editor_new_directory_dropdown_v14_1.png)
 
 In the new directory dialog, enter a directory name, a commit message, and choose
-the target branch. Click **Create directory** to finish.
+the target branch. Select **Create directory** to finish.
 
 ![New directory dialog](img/web_editor_new_directory_dialog_v14_1.png)
 
@@ -153,7 +153,7 @@ The branch name is based on an internal ID, and the issue title. The example
 screenshot above creates a branch named
 `2-make-static-site-auto-deploy-and-serve`.
 
-When you click the **Create branch** button in an empty
+When you select the **Create branch** button in an empty
 repository project, GitLab performs these actions:
 
 - Creates a default branch.
diff --git a/doc/user/project/web_ide/index.md b/doc/user/project/web_ide/index.md
index 9db30ee2ab620ec6c5237f6ebf9c4aa597409738..5569c69fcc692ab753a8f98d432a41c614c64802 100644
--- a/doc/user/project/web_ide/index.md
+++ b/doc/user/project/web_ide/index.md
@@ -198,13 +198,13 @@ left.
 
 ## Switching merge requests
 
-To switch between your authored and assigned merge requests, click the
+To switch between your authored and assigned merge requests, select the
 dropdown in the top of the sidebar to open a list of merge requests. You must commit or discard all your changes before switching to a different merge
 request.
 
 ## Switching branches
 
-To switch between branches of the current project repository, click the dropdown
+To switch between branches of the current project repository, select the dropdown
 in the top of the sidebar to open a list of branches.
 You must commit or discard all your changes before switching to a
 different branch.
@@ -361,7 +361,7 @@ If there is no configuration file in a branch, an error message is shown.
 
 ### Running interactive terminals in the Web IDE
 
-If Interactive Terminals are available for the current user, the **Terminal** button is visible in the right sidebar of the Web IDE. Click this button to open
+If Interactive Terminals are available for the current user, the **Terminal** button is visible in the right sidebar of the Web IDE. Select this button to open
 or close the terminal tab.
 
 After opening, the tab shows the **Start Web Terminal** button. This button may
@@ -383,7 +383,7 @@ to running commands in a local terminal or through SSH.
 
 While the terminal is running, it can be stopped by clicking **Stop Terminal**.
 This disconnects the terminal and stops the runner's terminal job. From here,
-click **Restart Terminal** to start a new terminal session.
+select **Restart Terminal** to start a new terminal session.
 
 ### File syncing to web terminal