diff --git a/doc/administration/auth/ldap/google_secure_ldap.md b/doc/administration/auth/ldap/google_secure_ldap.md
index 01197fdacdf7a47709c2e2cce63fc09864427556..e0612099221e3e65e85d8b49143270b12d1f4e61 100644
--- a/doc/administration/auth/ldap/google_secure_ldap.md
+++ b/doc/administration/auth/ldap/google_secure_ldap.md
@@ -24,33 +24,33 @@ The steps below cover:
 
 1. Go to **Apps > LDAP > Add Client**.
 
-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'. Select the **Continue** button.
+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`. Select **Continue**.
 
    ![Add LDAP Client Step 1](img/google_secure_ldap_add_step_1.png)
 
 1. Set **Access Permission** according to your needs. You must choose either
-   'Entire domain (GitLab)' or 'Selected organizational units' for both 'Verify user
-   credentials' and 'Read user information'. Select 'Add LDAP Client'
+   `Entire domain (GitLab)` or `Selected organizational units` for both **Verify user
+   credentials** and **Read user information**. Select **Add LDAP Client**.
 
    NOTE:
    If you plan to use GitLab [LDAP Group Sync](ldap_synchronization.md#group-sync)
-   , turn on 'Read group information'.
+   , turn on `Read group information`.
 
    ![Add LDAP Client Step 2](img/google_secure_ldap_add_step_2.png)
 
 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, select the **Continue to Client Details** button.
+   for later use. After downloading, select **Continue to Client Details**.
 
-1. Expand the **Service Status** section and turn the LDAP client 'ON for everyone'.
-   After selecting 'Save', select the 'Service Status' bar again to collapse
+1. Expand the **Service Status** section and turn the LDAP client `ON for everyone`.
+   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', select
-   the 'Authentication' 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**, 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/ldap/ldap-troubleshooting.md b/doc/administration/auth/ldap/ldap-troubleshooting.md
index 21ec4b293d44bd5b4be7a52be3bbf3f9f66b3ca2..95064b296af3ae2a92b64cda4490fb82b1eaca48 100644
--- a/doc/administration/auth/ldap/ldap-troubleshooting.md
+++ b/doc/administration/auth/ldap/ldap-troubleshooting.md
@@ -373,7 +373,7 @@ things to debug the situation.
   1. Search for the user.
   1. Open the user by selecting their name. Do not select **Edit**.
   1. Select the **Identities** tab. There should be an LDAP identity with
-     an LDAP DN as the 'Identifier'. If not, this user hasn't signed in with
+     an LDAP DN as the `Identifier`. If not, this user hasn't signed in with
      LDAP yet and must do so first.
 - You've waited an hour or [the configured interval](ldap_synchronization.md#adjust-ldap-group-sync-schedule) for
   the group to sync. To speed up the process, either go to the GitLab group **Group information > Members**
@@ -523,8 +523,8 @@ LDAP group lookups. The very last occurrence of this entry should indicate
 exactly which users GitLab believes should be added to the group.
 
 NOTE:
-10 is 'Guest', 20 is 'Reporter', 30 is 'Developer', 40 is 'Maintainer'
-and 50 is 'Owner'.
+10 is `Guest`, 20 is `Reporter`, 30 is `Developer`, 40 is `Maintainer`
+and 50 is `Owner`.
 
 ```shell
 Resolved 'my_group' group member access: {"uid=john0,ou=people,dc=example,dc=com"=>30,
diff --git a/doc/administration/geo/replication/location_aware_git_url.md b/doc/administration/geo/replication/location_aware_git_url.md
index 460de5f3232c62f3875b7420f9b2ee19557188cf..4a3f9c860418c1f69099ae9134031067532845c6 100644
--- a/doc/administration/geo/replication/location_aware_git_url.md
+++ b/doc/administration/geo/replication/location_aware_git_url.md
@@ -57,7 +57,7 @@ routing configurations.
 
    ![Traffic policies](img/single_git_traffic_policies.png)
 
-1. Select the **Create traffic policy** button.
+1. Select **Create traffic policy**.
 
    ![Name policy](img/single_git_name_policy.png)
 
diff --git a/doc/administration/geo/replication/remove_geo_site.md b/doc/administration/geo/replication/remove_geo_site.md
index 4b9f31dc08c948809e2e637ddbc1898e1eb0b1a2..3826ee00bb164bf3df6a244c150760935ddff863 100644
--- a/doc/administration/geo/replication/remove_geo_site.md
+++ b/doc/administration/geo/replication/remove_geo_site.md
@@ -11,7 +11,7 @@ type: howto
 
 1. On the top bar, select **Main menu > Admin**.
 1. On the left sidebar, select **Geo > Nodes**.
-1. Select the **Remove** button for the **secondary** site you want to remove.
+1. For the **secondary** site you want to remove, select **Remove**.
 1. Confirm by selecting **Remove** when the prompt appears.
 
 After the **secondary** site is removed from the Geo administration page, you must
diff --git a/doc/administration/load_balancer.md b/doc/administration/load_balancer.md
index ad89d32183bc022f6daf753e1ca41dbc54655cd3..83b42295035a54cc2ae480083607b1e90dd6b372 100644
--- a/doc/administration/load_balancer.md
+++ b/doc/administration/load_balancer.md
@@ -36,7 +36,7 @@ for details on managing SSL certificates and configuring NGINX.
 
 ### Load Balancers terminate SSL without backend SSL
 
-Configure your load balancers to use the 'HTTP(S)' protocol rather than 'TCP'.
+Configure your load balancers to use the `HTTP(S)` protocol rather than `TCP`.
 The load balancers is be responsible for managing SSL certificates and
 terminating SSL.
 
@@ -47,7 +47,7 @@ for details.
 
 ### Load Balancers terminate SSL with backend SSL
 
-Configure your load balancers to use the 'HTTP(S)' protocol rather than 'TCP'.
+Configure your load balancers to use the `HTTP(S)` protocol rather than `TCP`.
 The load balancers is responsible for managing SSL certificates that
 end users see.
 
diff --git a/doc/administration/monitoring/performance/grafana_configuration.md b/doc/administration/monitoring/performance/grafana_configuration.md
index 92e9672cdb6fd2e02bed3f02b4f6e6becfc8836a..3dec34ebace3b07b8e8403744a35e9f823479bc7 100644
--- a/doc/administration/monitoring/performance/grafana_configuration.md
+++ b/doc/administration/monitoring/performance/grafana_configuration.md
@@ -25,9 +25,9 @@ is `admin`.
 
 1. Log in to Grafana as the administration user.
 1. Select **Data Sources** from the **Configuration** menu.
-1. Select the **Add data source** button.
+1. Select **Add data source**.
 1. Select the required data source type. For example, [Prometheus](../prometheus/index.md#prometheus-as-a-grafana-data-source).
-1. Complete the details for the data source and select the **Save & Test** button.
+1. Complete the details for the data source and select **Save & Test**.
 
 Grafana should indicate the data source is working.
 
@@ -43,8 +43,8 @@ them:
 
    1. Log in to Grafana as the administration user.
    1. Select **Manage** from the **Dashboards** menu.
-   1. Select the **Import** button, then the **Upload JSON file** button.
-   1. Locate the JSON file to import and select **Choose for Upload**. Select the **Import** button.
+   1. Select **Import**, then **Upload JSON file**.
+   1. Locate the JSON file to import and select **Choose for Upload**. Select **Import**.
    1. After the dashboard is imported, select the **Save dashboard** icon in the top bar.
 
 If you don't save the dashboard after importing it, the dashboard is removed
diff --git a/doc/ci/test_cases/index.md b/doc/ci/test_cases/index.md
index 8d2788539d851954740e2d49aa6b930a08f5bcf4..4088e5e82c6287c567f3fa379b129361be0e8727 100644
--- a/doc/ci/test_cases/index.md
+++ b/doc/ci/test_cases/index.md
@@ -25,9 +25,9 @@ Prerequisite:
 To create a test case in a GitLab project:
 
 1. Go to **CI/CD > Test Cases**.
-1. Select the **New test case** button. You are taken to the new test case form. Here you can enter
+1. Select **New test case**. You are taken to the new test case form. Here you can enter
    the new case's title, [description](../../user/markdown.md), attach a file, and assign [labels](../../user/project/labels.md).
-1. Select the **Submit test case** button. You are taken to view the new test case.
+1. Select **Submit test case**. You are taken to view the new test case.
 
 ## View a test case
 
@@ -73,7 +73,7 @@ Prerequisite:
 
 - You must have at least the Reporter role.
 
-To archive a test case, on the test case's page, select the **Archive test case** button.
+To archive a test case, on the test case's page, select **Archive test case**.
 
 To view archived test cases:
 
diff --git a/doc/integration/google.md b/doc/integration/google.md
index 3d174e56bf3d0a5146106d01b967b3a4bde17493..947bf0303be8f0110faf5a0c9bcbd68a648abd90 100644
--- a/doc/integration/google.md
+++ b/doc/integration/google.md
@@ -51,7 +51,7 @@ In Google's side:
 
    1. Go to the [Google API Console](https://console.developers.google.com/apis/dashboard).
    1. Select **ENABLE APIS AND SERVICES** at the top of the page.
-   1. Find each of the above APIs. On the page for the API, press the **ENABLE** button.
+   1. Find each of the above APIs. On the page for the API, select **ENABLE**.
       It may take a few minutes for the API to be fully functional.
 
 On your GitLab server:
diff --git a/doc/operations/metrics/embed_grafana.md b/doc/operations/metrics/embed_grafana.md
index 43a7447a97860b99938126a746e9fd1ea8646c8e..15969f0d6be2285aef66976b02d91c7f41143d10 100644
--- a/doc/operations/metrics/embed_grafana.md
+++ b/doc/operations/metrics/embed_grafana.md
@@ -25,7 +25,7 @@ To use Grafana-rendered images:
 
 1. Go to the dashboard containing the panel in Grafana.
 1. From the panel's menu, select **Share**.
-1. Select the **Direct link rendered image** button, which provides the link.
+1. Select **Direct link rendered image**, which provides the link.
 1. Copy the link and add an image tag as [inline HTML](../../user/markdown.md#inline-html) in your
    Markdown in the format `<img src="your_link"/>`. You can tweak the query parameters to meet your needs, such as removing the `&from=`
    and `&to=` parameters to display a live panel.
diff --git a/doc/user/admin_area/index.md b/doc/user/admin_area/index.md
index 49fa5342bda6ac161a4b3026309cb05f6da82dc4..559aae63da51f6b554e608daed6d0acf48221861 100644
--- a/doc/user/admin_area/index.md
+++ b/doc/user/admin_area/index.md
@@ -135,8 +135,7 @@ For each user, the following are listed:
 1. Date of account creation
 1. Date of last activity
 
-To edit a user, select the **Edit** button in that user's
-row. To delete the user, or delete the user and their contributions, select the cog dropdown list in
+To edit a user, in the user's row, select **Edit**. To delete the user, or delete the user and their contributions, select the cog dropdown list in
 that user's row, and select the desired option.
 
 To change the sort order:
@@ -256,9 +255,7 @@ To access the Groups page:
 1. On the left sidebar, select **Overview > Groups**.
 
 For each group, the page displays their name, description, size, number of projects in the group,
-number of members, and whether the group is private, internal, or public. To edit a group, select
-the **Edit** button in that group's row. To delete the group, select the **Delete** button in
-that group's row.
+number of members, and whether the group is private, internal, or public. To edit a group, in the group's row, select **Edit**. To delete the group, in the group's row, select **Delete**.
 
 To change the sort order, select the sort dropdown list and select the desired order. The default
 sort order is by **Last created**.