diff --git a/doc/administration/auth/ldap/ldap-troubleshooting.md b/doc/administration/auth/ldap/ldap-troubleshooting.md
index 7e21d3c66557133eab690431734ea194e6fc3dc7..9c925e0a40e1d5c5c0ed971d33fb2442e22d3a9a 100644
--- a/doc/administration/auth/ldap/ldap-troubleshooting.md
+++ b/doc/administration/auth/ldap/ldap-troubleshooting.md
@@ -170,10 +170,10 @@ We have a workaround, based on toggling the access level of affected users:
 1. As an administrator, on the top bar, select **Main menu > Admin**.
 1. On the left sidebar, select **Overview > Users**.
 1. Select the name of the affected user.
-1. In the upper right, select **Edit**.
+1. In the upper-right corner, select **Edit**.
 1. Change the user's access level from `Regular` to `Administrator` (or vice versa).
 1. At the bottom of the page, select **Save changes**.
-1. In the upper right, select **Edit** again.
+1. In the upper-right corner, select **Edit** again.
 1. Restore the user's original access level (`Regular` or `Administrator`)
    and select **Save changes** again.
 
diff --git a/doc/ci/caching/index.md b/doc/ci/caching/index.md
index 1aa579b842a286d54e7a4285e1ddc678a8f01608..c0e0a1cbff3fba1d8f5c944d58a42d68929db918 100644
--- a/doc/ci/caching/index.md
+++ b/doc/ci/caching/index.md
@@ -570,7 +570,7 @@ You can clear the cache in the GitLab UI:
 
 1. On the top bar, select **Main menu > Projects** and find your project.
 1. On the left sidebar, select **CI/CD > Pipelines**.
-1. In the upper right, select **Clear runner caches**.
+1. In the upper-right corner, select **Clear runner caches**.
 
 On the next commit, your CI/CD jobs use a new cache.
 
diff --git a/doc/ci/environments/index.md b/doc/ci/environments/index.md
index 6045069279486bcde46b5821f892c511dbf648f6..77c4ae31f0bc36307b8963f2a7210b2530b194bc 100644
--- a/doc/ci/environments/index.md
+++ b/doc/ci/environments/index.md
@@ -708,7 +708,7 @@ You can view a deployment's expiration date in the GitLab UI.
 1. On the left sidebar, select **Deployments > Environments**.
 1. Select the name of the deployment.
 
-In the upper left, next to the environment name, the expiration date is displayed.
+In the upper-left corner, next to the environment name, the expiration date is displayed.
 
 #### Override a deployment's scheduled stop time
 
@@ -717,7 +717,7 @@ You can manually override a deployment's expiration date.
 1. On the top bar, select **Main menu > Projects** and find your project.
 1. On the left sidebar, select **Deployments > Environments**.
 1. Select the deployment name.
-1. in the upper right, select the thumbtack (**{thumbtack}**).
+1. in the upper-right corner, select the thumbtack (**{thumbtack}**).
 
 ![Environment auto stop](img/environment_auto_stop_v13_10.png)
 
diff --git a/doc/ci/examples/semantic-release.md b/doc/ci/examples/semantic-release.md
index 9f299448d520b9cf5a6166b8807879cb65674fa9..0b4b20546100e004c8e3ce38a7fbb806736fa8f7 100644
--- a/doc/ci/examples/semantic-release.md
+++ b/doc/ci/examples/semantic-release.md
@@ -90,7 +90,7 @@ As part of publishing a package, semantic-release increases the version number i
 
 <!-- markdownlint-disable MD044 -->
 
-1. On the top bar, in the upper right, select your avatar.
+1. On the top bar, in the upper-right corner, select your avatar.
 1. On the left sidebar, select **Access Tokens**.
 1. In the **Token name** box, enter a token name.
 1. Under **select scopes**, select the **api** checkbox.
diff --git a/doc/ci/jobs/index.md b/doc/ci/jobs/index.md
index 5e69ecff7b8e736bd419817dd8cc193d8be0fe1e..4aa12d12bdbe86b0711c794614b88e76e14252e0 100644
--- a/doc/ci/jobs/index.md
+++ b/doc/ci/jobs/index.md
@@ -339,8 +339,8 @@ In the example above:
 - `date +%s`: The Unix timestamp (for example `1560896352`).
 - `my_first_section`: The name given to the section.
 - `\r\e[0K`: Prevents the section markers from displaying in the rendered (colored)
-  job log, but they are displayed in the raw job log. To see them, in the upper right
-  of the job log, select **{doc-text}** (**Show complete raw**).
+  job log, but they are displayed in the raw job log. To see them, in the upper-right corner
+  of the job log, select **Show complete raw** (**{doc-text}**).
   - `\r`: carriage return.
   - `\e[0K`: clear line ANSI escape code.
 
diff --git a/doc/ci/lint.md b/doc/ci/lint.md
index 74e0f0cd5ef4b0a0203257bc9ad60a23ac289b20..119a0e5853e03cae7d86b39666dffc713ee070c3 100644
--- a/doc/ci/lint.md
+++ b/doc/ci/lint.md
@@ -26,7 +26,7 @@ To check CI/CD configuration with the CI lint tool:
 
 1. On the top bar, select **Main menu > Projects** and find your project.
 1. On the left sidebar, select **CI/CD > Pipelines**.
-1. In the upper right, select **CI lint**.
+1. In the upper-right corner, select **CI lint**.
 1. Paste a copy of the CI/CD configuration you want to check into the text box.
 1. Select **Validate**.
 
@@ -47,7 +47,7 @@ To simulate a pipeline:
 
 1. On the top bar, select **Main menu > Projects** and find your project.
 1. On the left sidebar, select **CI/CD > Pipelines**.
-1. In the upper right, select **CI lint**.
+1. In the upper-right corner, select **CI lint**.
 1. Paste a copy of the CI/CD configuration you want to check into the text box.
 1. Select **Simulate pipeline creation for the default branch**.
 1. Select **Validate**.
diff --git a/doc/ci/pipeline_editor/index.md b/doc/ci/pipeline_editor/index.md
index 727977b3bc86d8664397ce83b1de0ca2414d7dbc..1a7155c8195b34c1a1f106878e7f7ef1a23acf37 100644
--- a/doc/ci/pipeline_editor/index.md
+++ b/doc/ci/pipeline_editor/index.md
@@ -70,7 +70,7 @@ simulations in the [CI Lint tool](../lint.md#simulate-a-pipeline).
 > - [Feature flag removed](https://gitlab.com/gitlab-org/gitlab/-/issues/357219) in GitLab 15.1.
 
 You can review configuration added with the [`include`](../yaml/index.md#include)
-keyword in the pipeline editor. In the upper right, select the file tree (**{file-tree}**)
+keyword in the pipeline editor. In the upper-right corner, select the file tree (**{file-tree}**)
 to see a list of all included configuration files. Selected files open in a new tab
 for review.
 
diff --git a/doc/ci/pipelines/job_artifacts.md b/doc/ci/pipelines/job_artifacts.md
index 75c9852d3d0284085a2a2d3b0f52ef5c6f63f302..32b9923e811d1a4aee1e04b0f7e4036824a97d2e 100644
--- a/doc/ci/pipelines/job_artifacts.md
+++ b/doc/ci/pipelines/job_artifacts.md
@@ -264,7 +264,7 @@ artifacts and log. You must be:
 To delete a job:
 
 1. Go to a job's detail page.
-1. In the upper right of the job's log, select **Erase job log** (**{remove}**).
+1. In the upper-right corner of the job's log, select **Erase job log** (**{remove}**).
 1. On the confirmation dialog, select **OK**.
 
 ## Expose job artifacts in the merge request UI
diff --git a/doc/development/documentation/versions.md b/doc/development/documentation/versions.md
index 30a0d4d4cf48c40c93b3d0e58542c507f3819ffd..0c21e7cd76621ed235a5fcf32ca1193e4363e2ad 100644
--- a/doc/development/documentation/versions.md
+++ b/doc/development/documentation/versions.md
@@ -13,7 +13,7 @@ including when features were introduced and when they were updated or removed.
 ## View older documentation versions
 
 Previous versions of the documentation are available on `docs.gitlab.com`.
-To view a previous version, select the **Versions** button in the upper right.
+To view a previous version, in the upper-right corner, select **Versions**.
 
 To view versions that are not available on `docs.gitlab.com`:
 
diff --git a/doc/development/documentation/workflow.md b/doc/development/documentation/workflow.md
index fe5453a4a5819e316aa34ce8d25f04b6027b6d79..63612861e4defa4166819635a00d5e1eb31da5a9 100644
--- a/doc/development/documentation/workflow.md
+++ b/doc/development/documentation/workflow.md
@@ -40,11 +40,11 @@ If you are not a GitLab team member, or do not have the Developer role for the G
    - If you're not taking part in a Hackathon, you don't need an issue to open a merge request.
      If you are looking for issues to work on and don't see any that suit you, you can always fix [Vale](testing.md#vale) issues.
 1. Go to the [GitLab repository](https://gitlab.com/gitlab-org/gitlab).
-1. In the upper right, select **Fork**. Forking makes a copy of the repository on GitLab.com.
+1. In the upper-right corner, select **Fork**. Forking makes a copy of the repository on GitLab.com.
 1. In your fork, find the documentation page in the `\doc` directory.
 1. If you know Git, make your changes and open a merge request.
    If not, follow these steps:
-   1. In the upper right, select **Edit** if it is visible. If it is not, select the down arrow (**{chevron-lg-down}**) next to **Open in Web IDE** or **Gitpod**, and select **Edit**.
+   1. In the upper-right corner, select **Edit** if it is visible. If it is not, select the down arrow (**{chevron-lg-down}**) next to **Open in Web IDE** or **Gitpod**, and select **Edit**.
    1. In the **Commit message** text box, enter a commit message. Use 3-5 words, start with a capital letter, and do not end with a period.
    1. Select **Commit changes**.
    1. On the left sidebar, select **Merge requests**.
diff --git a/doc/development/fe_guide/frontend_faq.md b/doc/development/fe_guide/frontend_faq.md
index 3b349d880c011a2c4a32ed568e5b047588769eb9..ba28eea92651acb864f25d504a8458f07f490db3 100644
--- a/doc/development/fe_guide/frontend_faq.md
+++ b/doc/development/fe_guide/frontend_faq.md
@@ -192,7 +192,7 @@ To see what polyfills are being used:
 1. Select the [`compile-production-assets`](https://gitlab.com/gitlab-org/gitlab/-/jobs/641770154) job.
 1. In the right-hand sidebar, scroll to **Job Artifacts**, and select **Browse**.
 1. Select the **webpack-report** folder to open it, and select **index.html**.
-1. In the upper left corner of the page, select the right arrow **{chevron-lg-right}**
+1. In the upper-left corner of the page, select the right arrow (**{chevron-lg-right}**)
    to display the explorer.
 1. In the **Search modules** field, enter `gitlab/node_modules/core-js` to see
    which polyfills are being loaded and where:
diff --git a/doc/development/fe_guide/graphql.md b/doc/development/fe_guide/graphql.md
index 8ae0458e47ca4b43c78439219c27f3c5bfeedbf0..71a19b500015caa105a5fe4f9d7a3e7e09f415f3 100644
--- a/doc/development/fe_guide/graphql.md
+++ b/doc/development/fe_guide/graphql.md
@@ -84,10 +84,8 @@ Our GraphQL API can be explored via GraphiQL at your instance's
 [GitLab GraphQL API Reference documentation](../../api/graphql/reference)
 where needed.
 
-You can check all existing queries and mutations on the right side
-of GraphiQL in its **Documentation explorer**. You can also
-write queries and mutations directly on the left tab and check
-their execution by selecting **Execute query** in the upper left:
+To check all existing queries and mutations, on the right side of GraphiQL, select **Documentation explorer**.
+To check the execution of the queries and mutations you've written, in the upper-left corner, select **Execute query**.
 
 ![GraphiQL interface](img/graphiql_explorer_v12_4.png)
 
diff --git a/doc/gitlab-basics/start-using-git.md b/doc/gitlab-basics/start-using-git.md
index 224d1fabb14ed86d04e7d1f857ad38c0c6842198..194647259b8f7894c135628a9e0dffa0c893fb42 100644
--- a/doc/gitlab-basics/start-using-git.md
+++ b/doc/gitlab-basics/start-using-git.md
@@ -98,7 +98,7 @@ access on GitLab.com or any other GitLab instance.
 To use the repository in the examples on this page:
 
 1. Go to [https://gitlab.com/gitlab-tests/sample-project/](https://gitlab.com/gitlab-tests/sample-project/).
-1. In the upper right, select **Fork**.
+1. In the upper-right corner, select **Fork**.
 1. Choose a namespace for your fork.
 
 The project becomes available at `https://gitlab.com/<your-namespace>/sample-project/`.
diff --git a/doc/install/aws/index.md b/doc/install/aws/index.md
index 99ba05925a5f1400c9a74a188ff1966ead7f3a90..8f540691a45fbe60dbbfb8a4b699a118834afe72 100644
--- a/doc/install/aws/index.md
+++ b/doc/install/aws/index.md
@@ -87,7 +87,7 @@ Because any given GitLab upgrade might involve data disk updates or database sch
    - [GitLab Community Edition](https://console.aws.amazon.com/ec2/v2/home?region=us-east-1#Images:visibility=public-images;ownerAlias=782774275127;search=GitLab%20CE;sort=desc:name): The open source version of GitLab.
    - [GitLab Premium or Ultimate Marketplace (pre-licensed)](https://console.aws.amazon.com/ec2/v2/home?region=us-east-1#Images:visibility=public-images;source=Marketplace;search=GitLab%20EE;sort=desc:name): 5 user license built into per-minute billing.
 
-1. AMI IDs are unique per region, so after you've loaded one of the above, select the desired target region in the upper right of the console to see the appropriate AMIs.
+1. AMI IDs are unique per region. After you've loaded any of these editions, in the upper-right corner, select the desired target region of the console to see the appropriate AMIs.
 1. After the console is loaded, you can add additional search criteria to narrow further. For instance, type `13.` to find only 13.x versions.
 1. To launch an EC2 Machine with one of the listed AMIs, check the box at the start of the relevant row, and select **Launch** near the top of left of the page.
 
diff --git a/doc/integration/facebook.md b/doc/integration/facebook.md
index 8b7bdeaa177e2c4b642c1ffcd52c96e957d949b6..b35e3c585e0cf2709c5dcc09c7b6c0fce1abd3f8 100644
--- a/doc/integration/facebook.md
+++ b/doc/integration/facebook.md
@@ -31,7 +31,7 @@ Facebook. Facebook generates an app ID and secret key for you to use.
 
 1. Choose "Next"
 
-1. Choose "Skip Quick Start" in the upper right corner
+1. In the upper-right corner, select **Skip Quick Start**.
 
 1. Choose "Settings" in the menu on the left
 
diff --git a/doc/integration/gitpod.md b/doc/integration/gitpod.md
index ee8f46e73dfd1069e43bcbbbb411b2e54d94355a..6df36cff6386cd2c53493a969f6bf4eb6a897257 100644
--- a/doc/integration/gitpod.md
+++ b/doc/integration/gitpod.md
@@ -69,6 +69,6 @@ You can launch Gitpod directly from GitLab in one of these ways:
   1. Select **Open in Gitpod**.
 - *From a merge request:*
   1. Go to your merge request.
-  1. In the upper right corner, select **Code**, then select **Open in Gitpod**.
+  1. In the upper-right corner, select **Code**, then select **Open in Gitpod**.
 
 Gitpod builds your development environment for your branch.
diff --git a/doc/integration/google.md b/doc/integration/google.md
index 5eac639f11967ac2b60a8161546b41f0b4701e3c..bb76d7c8ff194ad6345ed9dacfca737b0960014d 100644
--- a/doc/integration/google.md
+++ b/doc/integration/google.md
@@ -22,7 +22,7 @@ In Google's side:
      the randomly generated ID or choose a new one.
 1. Refresh the page and you should see your new project in the list
 1. Go to the [Google API Console](https://console.developers.google.com/apis/dashboard)
-1. Select the previously created project in the upper left corner
+1. In the upper-left corner, select the previously created project
 1. Select **Credentials** from the sidebar
 1. Select **OAuth consent screen** and fill the form with the required information
 1. In the **Credentials** tab, select **Create credentials > OAuth client ID**
diff --git a/doc/integration/jira/jira_server_configuration.md b/doc/integration/jira/jira_server_configuration.md
index 7dee99b024e772c7fdb5e2b4dcfcd19983c02bbc..5bac108b457dabcf0632b0d67958bd889509eeb6 100644
--- a/doc/integration/jira/jira_server_configuration.md
+++ b/doc/integration/jira/jira_server_configuration.md
@@ -20,7 +20,7 @@ credentials, you must:
 This process creates a user named `gitlab`:
 
 1. Sign in to your Jira instance as a Jira administrator.
-1. In the upper right corner of the top menu, go to the gear icon and
+1. On the top bar, in the upper-right corner, select the gear icon, then
    select **User Management**.
 1. Create a new user account (`gitlab`) with write access to
    projects in Jira.
@@ -43,9 +43,9 @@ group to assign permissions to the user.
 This process adds the `gitlab` user you created to a new group named `gitlab-developers`:
 
 1. Sign in to your Jira instance as a Jira administrator.
-1. In the upper right corner of the top menu, go to the gear icon and
+1. On the top bar, in the upper-right corner, select the gear icon, then
    select **User Management**.
-1. On the sidebar, select **Groups**.
+1. On the left sidebar, select **Groups**.
 
    ![Jira create new user](img/jira_create_new_group.png)
 
@@ -70,9 +70,9 @@ Next, create a permission scheme for your group.
 After creating the group in Jira, grant permissions to the group by creating a permission scheme:
 
 1. Sign in to your Jira instance as a Jira administrator.
-1. In the upper right corner of the top menu, go to the gear icon and
+1. On the top bar, in the upper-right corner, select the gear icon, then
    select **Issues**.
-1. On the sidebar, select **Permission Schemes**.
+1. On the left sidebar, select **Permission Schemes**.
 1. Select **Add Permission Scheme**, enter a **Name** and (optionally) a
    **Description**, and then select **Add**.
 1. In the permissions scheme list, locate your new permissions scheme, and
diff --git a/doc/operations/incident_management/manage_incidents.md b/doc/operations/incident_management/manage_incidents.md
index ad4de8641e58fb55ea29af4eacd1af563eec5818..338dacda16618d21495ea7fff4ea1bde3924a10a 100644
--- a/doc/operations/incident_management/manage_incidents.md
+++ b/doc/operations/incident_management/manage_incidents.md
@@ -220,7 +220,7 @@ Prerequisites:
 
 - You must have at least the Reporter role for the project.
 
-To close an incident, in the upper right, select **Close incident**.
+To close an incident, in the upper-right corner, select **Close incident**.
 
 When you close an incident that is linked to an [alert](alerts.md),
 the linked alert's status changes to **Resolved**.
diff --git a/doc/operations/metrics/dashboards/index.md b/doc/operations/metrics/dashboards/index.md
index 09bb8cedbf6933638022b38903436a7c4b55f55f..b2c17ce7730f291c813907234887a5168fc95f75 100644
--- a/doc/operations/metrics/dashboards/index.md
+++ b/doc/operations/metrics/dashboards/index.md
@@ -124,9 +124,9 @@ can manage [the settings](settings.md) for your metrics dashboard.
 
 ## Chart Context Menu
 
-You can take action related to a chart's data by selecting the
-**{ellipsis_v}** **More actions** dropdown list above the upper right corner of
-any chart on a dashboard:
+To take action related to a chart's data:
+
+- In the upper-right corner of the chart, select **More actions** (**{ellipsis_v}**).
 
 ![Context Menu](img/panel_context_menu_v14_0.png)
 
diff --git a/doc/operations/metrics/embed.md b/doc/operations/metrics/embed.md
index f622780530a061b3441ae244d7092b110dfec649..987f1dc019dd35153e065074a0c7b8eef5fbfc7d 100644
--- a/doc/operations/metrics/embed.md
+++ b/doc/operations/metrics/embed.md
@@ -48,9 +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, select
-**{ellipsis_v}** **More actions** in the upper right corner of the chart,
-and select **Copy link to chart**, as shown in this example:
+You can also embed a single chart. To get a link to a chart, in the upper-right corner of the chart,
+select **More actions** (**{ellipsis_v}**), then 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/quickstart-guide.md b/doc/operations/quickstart-guide.md
index 91c5f25405cf2f0611dd0d675f91745e525c983c..b661243b3e0c5bc6a81df71aaaff88cf7e5b0b68 100644
--- a/doc/operations/quickstart-guide.md
+++ b/doc/operations/quickstart-guide.md
@@ -166,7 +166,7 @@ After the previous command exits, the cluster is ready.
 Go to a namespace you own in the connected GitLab instance and copy the Group ID below the group name.
 
 GOP can only be enabled for groups you own.
-To list all the groups that your user owns, go to the menu in upper left corner and select `Groups`->`View all Groups`. You then see the **Your groups** tab.
+To list all the groups that your user owns, in the upper-left corner, select **Groups > View all Groups**. You then see the **Your groups** tab.
 
 In your browser, go to `http://localhost/-/{GroupID}`. For example, `http://localhost/-/14485840`.
 
diff --git a/doc/subscriptions/self_managed/index.md b/doc/subscriptions/self_managed/index.md
index b5436b6cb72b0236c9014e048feabaab96c4800f..52a39fb3f49741f8dff52f4937d90461ecea3e37 100644
--- a/doc/subscriptions/self_managed/index.md
+++ b/doc/subscriptions/self_managed/index.md
@@ -280,7 +280,7 @@ If you are an administrator, you can export your license usage into a CSV:
 
 1. On the top bar, select **Main menu > Admin**.
 1. On the left sidebar, select **Subscription**.
-1. In the upper right, select **Export license usage file**.
+1. In the upper-right corner, select **Export license usage file**.
 
 This file contains the information GitLab uses to manually process quarterly reconciliations or renewals. If your instance is firewalled or an offline environment, you must provide GitLab with this information.
 
diff --git a/doc/topics/autodevops/cloud_deployments/auto_devops_with_gke.md b/doc/topics/autodevops/cloud_deployments/auto_devops_with_gke.md
index 9bd1d30e1b1d356304bb93de6170a8273e6ac517..06b772cc455b7972c9071d016adb3c14b8e3b908 100644
--- a/doc/topics/autodevops/cloud_deployments/auto_devops_with_gke.md
+++ b/doc/topics/autodevops/cloud_deployments/auto_devops_with_gke.md
@@ -274,7 +274,7 @@ bin/rails test test/controllers/welcome_controller_test.rb:4
 To fix the broken test:
 
 1. Return to your merge request.
-1. In the upper right corner, select **Code**, then select **Open in Gitpod**.
+1. In the upper-right corner, select **Code**, then select **Open in Gitpod**.
 1. In the left-hand directory of files, find the `test/controllers/welcome_controller_test.rb`
    file, and select it to open it.
 1. Change line 7 to say `You're on Rails! Powered by GitLab Auto DevOps.`
diff --git a/doc/update/package/index.md b/doc/update/package/index.md
index 34c7c096a8d6277ce315da1bc857dbeb0c2aee06..d3bd89975d2b64e2466aec4af3667bdc7d98fd20 100644
--- a/doc/update/package/index.md
+++ b/doc/update/package/index.md
@@ -169,7 +169,7 @@ To download and install GitLab:
    and architecture. Next to the filename is a label indicating the distribution,
    as the filenames may be the same.
 1. Find the package version you wish to install, and select the filename from the list.
-1. Select **Download** in the upper right corner to download the package.
+1. In the upper-right corner, select **Download**.
 1. After the package is downloaded, install it by using one of the
    following commands and replacing `<package_name>` with the package name
    you downloaded:
diff --git a/doc/user/admin_area/settings/continuous_integration.md b/doc/user/admin_area/settings/continuous_integration.md
index aa171fe4536885dbfa547c1ce668f6403c9dda0f..7b496bf364464256d88871f7c10dba00030b3291 100644
--- a/doc/user/admin_area/settings/continuous_integration.md
+++ b/doc/user/admin_area/settings/continuous_integration.md
@@ -54,7 +54,7 @@ To enable a project runner for more than one project:
 1. On the top bar, select **Main menu > Admin**.
 1. From the left sidebar, select **CI/CD > Runners**.
 1. Select the runner you want to edit.
-1. In the upper right, select **Edit** (**{pencil}**).
+1. In the upper-right corner, select **Edit** (**{pencil}**).
 1. Under **Restrict projects for this runner**, search for a project.
 1. To the left of the project, select **Enable**.
 1. Repeat this process for each additional project.
diff --git a/doc/user/admin_area/settings/external_authorization.md b/doc/user/admin_area/settings/external_authorization.md
index ab6c5ee409668bc76de93db6be1d5e51433ed2bf..32a5b0a606f975e50055e8807d08a8f6c657cc39 100644
--- a/doc/user/admin_area/settings/external_authorization.md
+++ b/doc/user/admin_area/settings/external_authorization.md
@@ -123,7 +123,7 @@ You can use your own classification label in the project's
 label" box. When no classification label is specified on a project, the default
 label defined in the [global settings](#configuration) is used.
 
-The label is shown on all project pages in the upper right corner.
+On all project pages, in the upper-right corner, the label appears.
 
 ![classification label on project page](img/classification_label_on_project_page_v14_8.png)
 
diff --git a/doc/user/application_security/vulnerability_report/index.md b/doc/user/application_security/vulnerability_report/index.md
index e6353264f394312ea20f1a6b73e82da4fe91e4c8..6b2f7f0655d979332bf1647acab4f90f1e544051 100644
--- a/doc/user/application_security/vulnerability_report/index.md
+++ b/doc/user/application_security/vulnerability_report/index.md
@@ -242,7 +242,7 @@ Vulnerability records cannot be deleted, so a permanent record always remains.
 You can dismiss a vulnerability in projects and groups:
 
 1. Select the vulnerability in the Security Dashboard.
-1. In the upper right, from the **Status** selector menu, select **Dismissed**.
+1. In the upper-right corner, from the **Status** dropdown list, select **Dismissed**.
 1. Optional. Add a reason for the dismissal and select **Save comment**.
 
 To undo this action, select a different status from the same menu.
diff --git a/doc/user/award_emojis.md b/doc/user/award_emojis.md
index e145971724164ba242f905d403d16b1f2cb9ce2f..919b76e930feb9726fc337b51caecbcbca20f0ca 100644
--- a/doc/user/award_emojis.md
+++ b/doc/user/award_emojis.md
@@ -36,7 +36,7 @@ celebrate an accomplishment or agree with an opinion.
 
 To add an award emoji:
 
-1. In the upper right of the comment, select the smile (**{slight-smile}**).
+1. In the upper-right corner of the comment, select the smile (**{slight-smile}**).
 1. Select an emoji from the dropdown list.
 
 To remove an award emoji, select the emoji again.
diff --git a/doc/user/discussions/index.md b/doc/user/discussions/index.md
index 9c9b5301460455a3028757b48ec34253bf889360..e168a140a21d3ca0e981e5b9d3a86273afcb9a88 100644
--- a/doc/user/discussions/index.md
+++ b/doc/user/discussions/index.md
@@ -260,7 +260,7 @@ Prerequisites:
 
 To create a thread by replying to a comment:
 
-1. In the upper right of the comment, select **Reply to comment** (**{comment}**).
+1. In the upper-right corner of the comment, select **Reply to comment** (**{comment}**).
 
    ![Reply to comment button](img/reply_to_comment_button.png)
 
@@ -308,7 +308,7 @@ To resolve a thread:
 
 1. Go to the thread.
 1. Do one of the following:
-   - In the upper right of the original comment, select **Resolve thread** (**{check-circle}**).
+   - In the upper-right corner of the original comment, select **Resolve thread** (**{check-circle}**).
    - Below the last reply, in the **Reply** field, select **Resolve thread**.
    - Below the last reply, in the **Reply** field, enter text, select the **Resolve thread** checkbox, and select **Add comment now**.
 
diff --git a/doc/user/group/epics/epic_boards.md b/doc/user/group/epics/epic_boards.md
index 64addd524adbfad74c3d04ac402d618253542418..e712eb8fbe9a6b5b9a21c493a116bb3a9ce0dd54 100644
--- a/doc/user/group/epics/epic_boards.md
+++ b/doc/user/group/epics/epic_boards.md
@@ -30,7 +30,7 @@ To create a new epic board:
 
 1. On the top bar, select **Main menu > Groups** and find your group.
 1. On the left sidebar, select **Epics > Boards**.
-1. In the upper left corner, select the dropdown list with the current board name.
+1. In the upper-left corner, select the dropdown list with the current board name.
 1. Select **Create new board**.
 1. Enter the new board's title.
 1. Optional. To hide the Open or Closed lists, clear the **Show the Open list** and
@@ -54,7 +54,7 @@ Prerequisites:
 
 To delete the active epic board:
 
-1. Select the dropdown list with the current board name in the upper left corner of the epic boards page.
+1. In the upper-left corner of the epic board page, select the dropdown list.
 1. Select **Delete board**.
 1. Select **Delete**.
 
diff --git a/doc/user/group/import/index.md b/doc/user/group/import/index.md
index 7f8bb95f4d5dc376b3a70d9c063d0c7f696f0fe1..d10f6526e967c8b0dbe0b71fbfeb0024bfb6b00e 100644
--- a/doc/user/group/import/index.md
+++ b/doc/user/group/import/index.md
@@ -151,7 +151,7 @@ To view group import history:
 1. On the top bar, select **Create new…** (**{plus-square}**).
 1. Select **New group**.
 1. Select **Import group**.
-1. Select **History** in the upper right corner.
+1. In the upper-right corner, select **History**.
 1. If there are any errors for a particular import, you can see them by selecting **Details**.
 
 ### Migrated group items
diff --git a/doc/user/group/manage.md b/doc/user/group/manage.md
index fc72b81d74c4e4c7fc2e65235ecc77b1f38fdb44..4679df1da8b8f9697f859c68192a3b6c86bfec62 100644
--- a/doc/user/group/manage.md
+++ b/doc/user/group/manage.md
@@ -155,7 +155,7 @@ You can sort members by **Account**, **Access granted**, **Max role**, or **Last
 
 1. On the top bar, select **Main menu > Groups** and find your group.
 1. On the left sidebar, select **Group information > Members**.
-1. Above the list of members, in the upper right, from the **Account** list, select
+1. Above the list of members, in the upper-right corner, from the **Account** list, select
    the criteria to filter by.
 1. To switch the sort between ascending and descending, to the right of the **Account** list, select the
    arrow (**{sort-lowest}** or **{sort-highest}**).
diff --git a/doc/user/group/saml_sso/scim_setup.md b/doc/user/group/saml_sso/scim_setup.md
index c6ff5dc63c3ef79208033499ae91b768ea6ccaa1..3751f2153ff3a46c097ad1585e9ea0046a025279 100644
--- a/doc/user/group/saml_sso/scim_setup.md
+++ b/doc/user/group/saml_sso/scim_setup.md
@@ -139,7 +139,7 @@ Prerequisites:
 To configure Okta for SCIM:
 
 1. Sign in to Okta.
-1. Ensure you are in the Admin Area by selecting the **Admin** button located in the upper right. The button is not visible from the Admin Area.
+1. In the upper-right corner, select **Admin**. 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 the **GitLab** application.
 1. On the GitLab application overview page, select **Add**.
diff --git a/doc/user/group/subgroups/index.md b/doc/user/group/subgroups/index.md
index 6c7baa848e76aa8a1402a3f0adaf325c46fd8bf3..976b8d6fa5db6d44eeece1bd2ce2be98228863a3 100644
--- a/doc/user/group/subgroups/index.md
+++ b/doc/user/group/subgroups/index.md
@@ -85,7 +85,7 @@ You cannot host a GitLab Pages subgroup website with a top-level domain name. Fo
 To create a subgroup:
 
 1. On the top bar, select **Main menu > Groups** and find and select the parent group to add a subgroup to.
-1. On the parent group's overview page, in the upper right, select **New subgroup**.
+1. On the parent group's overview page, in the upper-right corner, select **New subgroup**.
 1. Select **Create group**.
 1. Fill in the fields. View a list of [reserved names](../../reserved_names.md) that cannot be used as group names.
 1. Select **Create group**.
diff --git a/doc/user/group/value_stream_analytics/index.md b/doc/user/group/value_stream_analytics/index.md
index c5a95779087316ea4b193610b3fd7e55078a9095..3546922b00ce1d86e669b3ac79c1a2bb33a8fb8e 100644
--- a/doc/user/group/value_stream_analytics/index.md
+++ b/doc/user/group/value_stream_analytics/index.md
@@ -305,7 +305,7 @@ After you create a value stream, you can customize it to suit your purposes. To
 
 1. On the top bar, select **Main menu > Groups** and find your group.
 1. On the left sidebar, select **Analytics > Value Stream**.
-1. In the upper right, select the dropdown list, and select a value stream.
+1. In the upper-right corner, select the dropdown list, then select a value stream.
 1. Next to the value stream dropdown list, select **Edit**.
 1. Optional:
     - Rename the value stream.
@@ -324,7 +324,7 @@ To delete a custom value stream:
 
 1. On the top bar, select **Main menu > Groups** and find your group.
 1. On the left sidebar, select **Analytics > Value Stream**.
-1. In the upper right, select the dropdown list and then select the value stream you would like to delete.
+1. In the upper-right corner, select the dropdown list, then select the value stream you would like to delete.
 1. Select **Delete (name of value stream)**.
 1. To confirm, select **Delete**.
 
diff --git a/doc/user/packages/harbor_container_registry/index.md b/doc/user/packages/harbor_container_registry/index.md
index 1ad5e2c2f05e599301b38abe1726381130eb40f6..6cea541a55dd3fc332409ab41bd02a7eaee5c5f8 100644
--- a/doc/user/packages/harbor_container_registry/index.md
+++ b/doc/user/packages/harbor_container_registry/index.md
@@ -18,7 +18,7 @@ You can view the Harbor Registry for a project or group.
 
 You can search, sort, and filter images on this page. You can share a filtered view by copying the URL from your browser.
 
-At the project level, you can see **CLI Commands** in the upper right corner, where you can copy
+At the project level, in the upper-right corner, you can see **CLI Commands** where you can copy
 corresponding commands to sign in, build images, and push images. **CLI Commands** is not shown at
 the group level.
 
diff --git a/doc/user/profile/contributions_calendar.md b/doc/user/profile/contributions_calendar.md
index e9802cccef6f788c848cc3a506cf8f1d244e8718..ea47fed02b5653eabc940d2458632ac663bc6f65 100644
--- a/doc/user/profile/contributions_calendar.md
+++ b/doc/user/profile/contributions_calendar.md
@@ -83,7 +83,7 @@ GitLab provides RSS feeds of user activity. To subscribe to the
 RSS feed of a user's activity:
 
 1. Go to the [user's profile](index.md#access-your-user-profile).
-1. In the upper right, select the feed symbol **{rss}** to display the results as an RSS feed in Atom format.
+1. In the upper-right corner, select the feed symbol (**{rss}**) to display the results as an RSS feed in Atom format.
 
 The URL of the result contains both a feed token, and
 the user's activity that you're authorized to view.
diff --git a/doc/user/project/file_lock.md b/doc/user/project/file_lock.md
index 8d3446994e8dcade08c14b846a6070f2e19aa748..d6351483b60e4a7b2b90f32299e5013b38da0f9b 100644
--- a/doc/user/project/file_lock.md
+++ b/doc/user/project/file_lock.md
@@ -209,7 +209,7 @@ requests that modify locked files. Unlock the file to allow changes.
 To lock a file:
 
 1. Open the file or directory in GitLab.
-1. In the upper right, above the file, select **Lock**.
+1. In the upper-right corner, above the file, select **Lock**.
 1. On the confirmation dialog box, select **OK**.
 
 If you do not have permission to lock the file, the button is not enabled.
diff --git a/doc/user/project/import/gitea.md b/doc/user/project/import/gitea.md
index 404bb4c8600a79ed8b59bf6f22c74233c86ecdcc..29fe9db8887e6c0a9333b851d317b99ae408c8d1 100644
--- a/doc/user/project/import/gitea.md
+++ b/doc/user/project/import/gitea.md
@@ -75,10 +75,9 @@ From there, you can view the import statuses of your Gitea repositories:
 
 You also can:
 
-- Import all of your Gitea projects in one go by selecting **Import all projects**
-  in the upper left corner.
-- Filter projects by name. If filter is applied, selecting **Import all projects**
-  imports only matched projects.
+- In the upper-left corner, select **Import all projects** to import all of your Gitea projects at once.
+- Filter projects by name. If a filter is applied, **Import all projects**
+  imports only selected projects.
 
 ![Gitea importer page](img/import_projects_from_gitea_importer_v12_3.png)
 
diff --git a/doc/user/project/import/index.md b/doc/user/project/import/index.md
index 24748b2e89ce52359451e76b417afc370131f55a..8c95e68e1f25c2bec7320ee4d307a5ee8589b1e1 100644
--- a/doc/user/project/import/index.md
+++ b/doc/user/project/import/index.md
@@ -109,7 +109,7 @@ To view project import history:
 1. On the top bar, select **Create new...** (**{plus-square}**).
 1. Select **New project/repository**.
 1. Select **Import project**.
-1. Select **History** in the upper right corner.
+1. In the upper-right corner, select **History**.
 1. If there are any errors for a particular import, you can see them by selecting **Details**.
 
 The history also includes projects created from [built-in](../index.md#create-a-project-from-a-built-in-template)
diff --git a/doc/user/project/index.md b/doc/user/project/index.md
index decf3b071e79d1b8a7be15c7eebccda6b3ece56b..4f3fff1b38da8e2ac768cd522eb17f46a7902771 100644
--- a/doc/user/project/index.md
+++ b/doc/user/project/index.md
@@ -139,9 +139,8 @@ Prerequisites:
 - You must have permission to add new projects to a namespace. To check if you have permission:
 
   1. On the top bar, select **Main menu > Groups** and find your group.
-  1. Confirm that **New project** is visible in the upper right
-     corner. Contact your GitLab
-     administrator if you require permission.
+  1. In the upper-right corner, confirm that **New project** is visible.
+     Contact your GitLab administrator if you require permission.
 
 To push your repository and create a project:
 
diff --git a/doc/user/project/integrations/hangouts_chat.md b/doc/user/project/integrations/hangouts_chat.md
index 9aee2684ed4c131e5d97db48678ad02db9c259c4..c9ba5b1b3aa8e94a409e6c5de6f8b87bc8553e95 100644
--- a/doc/user/project/integrations/hangouts_chat.md
+++ b/doc/user/project/integrations/hangouts_chat.md
@@ -28,7 +28,7 @@ notifications to Google Chat:
 To enable the integration in Google Chat:
 
 1. Enter the room where you want to receive notifications from GitLab.
-1. Open the room dropdown list in the upper left and select **Manage webhooks**.
+1. In the upper-left corner, from the room dropdown list, select **Manage webhooks**.
 1. Enter the name for your webhook, for example "GitLab integration".
 1. Optional. Add an avatar for your bot.
 1. Select **Save**.
diff --git a/doc/user/project/issue_board.md b/doc/user/project/issue_board.md
index 234faa893ebbe5f5178181e99d5434221037069b..2ab808d2b0d93a5d1159b98fe8203d27e0766156 100644
--- a/doc/user/project/issue_board.md
+++ b/doc/user/project/issue_board.md
@@ -74,7 +74,7 @@ Prerequisites:
 
 To create a new issue board:
 
-1. Select the dropdown list with the current board name in the upper left corner of the issue boards page.
+1. In the upper-left corner of the issue board page, select the dropdown list with the current board name.
 1. Select **Create new board**.
 1. Enter the new board's name and select its scope: milestone, labels, assignee, or weight.
 
@@ -86,7 +86,7 @@ Prerequisites:
 
 To delete the currently active issue board:
 
-1. Select the dropdown list with the current board name in the upper left corner of the issue boards page.
+1. In the upper-left corner of the issue board page, select the dropdown list with the current board name.
 1. Select **Delete board**.
 1. Select **Delete** to confirm.
 
@@ -475,7 +475,7 @@ Additionally, you can also see the time tracking value.
 
 ### Create a new list
 
-Create a new list by selecting the **Create** button in the upper right corner of the issue board.
+To create a new list, in the upper-right corner of the issue board, select **Create**.
 
 ![creating a new list in an issue board](img/issue_board_add_list_v14_1.png)
 
diff --git a/doc/user/project/issues/csv_import.md b/doc/user/project/issues/csv_import.md
index 8a6683a55b5529ddadd71caed48e7595836c7743..ac7d8c99fa8648d899ca95b6ec18624b48cdcef9 100644
--- a/doc/user/project/issues/csv_import.md
+++ b/doc/user/project/issues/csv_import.md
@@ -36,8 +36,8 @@ To import issues:
 
 1. Go to your project's Issues list page.
 1. Open the import feature, depending if the project has issues:
-   - Existing issues are present: Select the import icon in the upper right, next to **Edit issues**.
-   - Project has no issues: Select **Import CSV** in the middle of the page.
+   - The project has existing issues: in the upper-right corner, next to **Edit issues**, select the import icon (**{import}**).
+   - The project has no issues: in the middle of the page, select **Import CSV**.
 1. Select the file you want to import, and then select **Import issues**.
 
 The file is processed in the background, and a notification email is sent
diff --git a/doc/user/project/issues/managing_issues.md b/doc/user/project/issues/managing_issues.md
index c16074ea1d84f45c60fe88c19ec98311fd6e44ce..e0966909b1e4b8ca0483097eaa5668ea0462dc5f 100644
--- a/doc/user/project/issues/managing_issues.md
+++ b/doc/user/project/issues/managing_issues.md
@@ -400,7 +400,7 @@ To view all issues assigned to you:
 Or:
 
 - To use a [keyboard shortcut](../../shortcuts.md), press <kbd>Shift</kbd> + <kbd>i</kbd>.
-- On the top bar, in the upper right, select **{issues}** **Issues**.
+- On the top bar, in the upper-right corner, select **Issues** (**{issues}**).
 
 ## Filter the list of issues
 
diff --git a/doc/user/project/merge_requests/allow_collaboration.md b/doc/user/project/merge_requests/allow_collaboration.md
index 0729e024df40efaada92a1350f1c20ed18964e76..4a22cc71349c50c9f7926f7b9e276e127b2c8d7e 100644
--- a/doc/user/project/merge_requests/allow_collaboration.md
+++ b/doc/user/project/merge_requests/allow_collaboration.md
@@ -61,7 +61,7 @@ In the following example:
 To change or add a commit to the contributor's merge request:
 
 1. Go to the merge request.
-1. In the upper right corner, select **Code**, then select **Check out branch**.
+1. In the upper-right corner, select **Code**, then select **Check out branch**.
 1. In the modal window, select **Copy** (**{copy-to-clipboard}**).
 1. In your terminal, go to your cloned version of the repository, and
    paste the commands. For example:
diff --git a/doc/user/project/merge_requests/cherry_pick_changes.md b/doc/user/project/merge_requests/cherry_pick_changes.md
index 9fac872ac4b37aaa16e7b7ac07657d466e779283..1dab6bf31cf3295fa89a16527c07cc8f130d81eb 100644
--- a/doc/user/project/merge_requests/cherry_pick_changes.md
+++ b/doc/user/project/merge_requests/cherry_pick_changes.md
@@ -55,7 +55,7 @@ by the merge request:
 1. On the top bar, select **Main menu > Projects** and find your project.
 1. On the left sidebar, select **Merge requests**, and find your merge request.
 1. Scroll to the merge request reports section, and find the **Merged by** report.
-1. In the upper right, select **Cherry-pick**:
+1. In the upper-right corner, select **Cherry-pick**:
 
    ![Cherry-pick merge request](img/cherry_pick_v15_4.png)
 1. In the modal window, select the project and branch to cherry-pick into.
diff --git a/doc/user/project/merge_requests/creating_merge_requests.md b/doc/user/project/merge_requests/creating_merge_requests.md
index 875312bbb7c7cf27511ddb1add763a583b377757..d704e9fa5d1edd169855254d8b102e7e22e71b95 100644
--- a/doc/user/project/merge_requests/creating_merge_requests.md
+++ b/doc/user/project/merge_requests/creating_merge_requests.md
@@ -19,7 +19,7 @@ You can create a merge request from the list of merge requests.
 
 1. On the top bar, select **Main menu > Projects** and find your project.
 1. On the left menu, select **Merge requests**.
-1. In the upper right, select **New merge request**.
+1. In the upper-right corner, select **New merge request**.
 1. Select a source and target branch and then **Compare branches and continue**.
 1. Fill out the fields and select **Create merge request**.
 
@@ -171,7 +171,7 @@ To create a merge request by sending an email:
 
 1. On the top bar, select **Main menu > Projects** and find your project.
 1. On the left menu, select **Merge requests**.
-1. In the upper right, select **Email a new merge request to this project**.
+1. In the upper-right corner, select **Email a new merge request to this project**.
    An email address is displayed. Copy this address.
    Ensure you keep this address private.
 1. Open an email and compose a message with the following information:
diff --git a/doc/user/project/merge_requests/index.md b/doc/user/project/merge_requests/index.md
index a633366cc62670e4d420d77d289f82acbfa58785..9e19b3a69ff60d0046bdc82950cb479426e0d7d4 100644
--- a/doc/user/project/merge_requests/index.md
+++ b/doc/user/project/merge_requests/index.md
@@ -65,7 +65,7 @@ or:
 
 or:
 
-1. On the top bar, in the upper right, select **{merge-request-open}** **Merge requests**.
+1. On the top bar, in the upper-right corner, select **Merge requests** (**{merge-request-open}**).
 1. From the dropdown list, select **Assigned to you**.
 
 ## Filter the list of merge requests
@@ -257,8 +257,8 @@ FLAG:
 On self-managed GitLab, by default this feature is not available. To make it available per project or for your entire instance, ask an administrator to [enable the feature flag](../../../administration/feature_flags.md) named `moved_mr_sidebar`.
 On GitLab.com, this feature is enabled in the following projects: `gitlab-org/gitlab`, `gitlab-com/www-gitlab-com`, and `gitlab-org/customers-gitlab-com`.
 
-When this feature flag is enabled, you can find the following actions in
-**Merge request actions** (**{ellipsis_v}**) in the upper right:
+When this feature flag is enabled, in the upper-right corner,
+**Merge request actions** (**{ellipsis_v}**) contains the following actions:
 
 - The [notifications](../../profile/notifications.md#edit-notification-settings-for-issues-merge-requests-and-epics) toggle
 - Mark merge request as ready or [draft](../merge_requests/drafts.md)
diff --git a/doc/user/project/merge_requests/reviews/index.md b/doc/user/project/merge_requests/reviews/index.md
index 5291a84543741cc2dfba1703f1553c8139d4f8b8..262d36d9db08ddde2f1014839e1307babb8f9d1d 100644
--- a/doc/user/project/merge_requests/reviews/index.md
+++ b/doc/user/project/merge_requests/reviews/index.md
@@ -84,7 +84,7 @@ To download the changes included in a merge request as a diff:
 1. On the top bar, select **Main menu > Projects** and find your project.
 1. On the left sidebar, select **Merge requests**.
 1. Select your merge request.
-1. In the upper right, select **Code > Plain diff**.
+1. In the upper-right corner, select **Code > Plain diff**.
 
 If you know the URL of the merge request, you can also download the diff from
 the command line by appending `.diff` to the URL. This example downloads the diff
@@ -107,7 +107,7 @@ To download the changes included in a merge request as a patch file:
 1. On the top bar, select **Main menu > Projects** and find your project.
 1. On the left sidebar, select **Merge requests**.
 1. Select your merge request.
-1. In the upper right, select **Code > Email patches**.
+1. In the upper-right corner, select **Code > Email patches**.
 
 If you know the URL of the merge request, you can also download the patch from
 the command line by appending `.patch` to the URL. This example downloads the patch
diff --git a/doc/user/project/pages/getting_started/pages_forked_sample_project.md b/doc/user/project/pages/getting_started/pages_forked_sample_project.md
index 509609e9b89b921d8f5ee05ebdc267710046a4b6..ec195f0f0e4ba78e4b13bfe07fa3f82553fe5e37 100644
--- a/doc/user/project/pages/getting_started/pages_forked_sample_project.md
+++ b/doc/user/project/pages/getting_started/pages_forked_sample_project.md
@@ -19,7 +19,7 @@ To fork a sample project and create a Pages website:
 
 1. View the sample projects by navigating to the [GitLab Pages examples](https://gitlab.com/pages) group.
 1. Select the name of the project you want to [fork](../../repository/forking_workflow.md#creating-a-fork).
-1. In the upper right, select **Fork** and then choose a namespace to fork to.
+1. In the upper-right corner, select **Fork**, then choose a namespace to fork to.
 1. For your project, on the left sidebar, select **CI/CD > Pipelines** and then **Run pipeline**.
    GitLab CI/CD builds and deploys your site.
 
diff --git a/doc/user/project/repository/file_finder.md b/doc/user/project/repository/file_finder.md
index f9a5d4e3aa7fcebd606c9b801e747fc3674b15b3..3fcc19db344e9268a3601f9d751566ef53afdbe3 100644
--- a/doc/user/project/repository/file_finder.md
+++ b/doc/user/project/repository/file_finder.md
@@ -11,7 +11,7 @@ The file finder feature allows you to search for a file in a repository using th
 GitLab UI. To use it:
 
 1. Go to your project's **Repository > Files**.
-1. In the upper right corner, select **Find File**.
+1. In the upper-right corner, select **Find File**.
 
 If you prefer to keep your fingers on the keyboard, use the
 [shortcut button](../../shortcuts.md), which you can invoke from anywhere
diff --git a/doc/user/project/repository/forking_workflow.md b/doc/user/project/repository/forking_workflow.md
index 929751b72476e72f9779c94876bc7ebcbb8f9577..ea45de4efc4bcd42d52dcd454562beb13d2f84d2 100644
--- a/doc/user/project/repository/forking_workflow.md
+++ b/doc/user/project/repository/forking_workflow.md
@@ -23,7 +23,7 @@ submit them through a merge request to the repository you don't have access to.
 
 To fork an existing project in GitLab:
 
-1. On the project's home page, in the upper right, select **{fork}** **Fork**:
+1. On the project's homepage, in the upper-right corner, select **Fork** (**{fork}**):
    ![Fork this project](img/forking_workflow_fork_button_v13_10.png)
 1. Optional. Edit the **Project name**.
 1. For **Project URL**, select the [namespace](../../namespace/index.md)
diff --git a/doc/user/project/repository/git_blame.md b/doc/user/project/repository/git_blame.md
index 78fcdec2a0b0333285905b71e21c6b738159605b..fbf29bddd46a16440243d90f816ac2a9952893a7 100644
--- a/doc/user/project/repository/git_blame.md
+++ b/doc/user/project/repository/git_blame.md
@@ -14,7 +14,7 @@ commit hash. To view it for a file:
 
 1. Go to your project's **Repository > Files**.
 1. Select the file you want to review.
-1. In the upper right corner, select **Blame**.
+1. In the upper-right corner, select **Blame**.
 
 When you select **Blame**, this information is displayed:
 
diff --git a/doc/user/project/repository/git_history.md b/doc/user/project/repository/git_history.md
index 321b9a5eb53462c51cec43a1b86061a4857527ad..a9228b8cabdb23507670ba2cdafff0b23d69107b 100644
--- a/doc/user/project/repository/git_history.md
+++ b/doc/user/project/repository/git_history.md
@@ -12,7 +12,7 @@ Git file History provides information about the commit history associated
 with a file. To use it:
 
 1. Go to your project's **Repository > Files**.
-1. In the upper right corner, select **History**.
+1. In the upper-right corner, select **History**.
 
 When you select **History**, this information is displayed:
 
diff --git a/doc/user/project/repository/gpg_signed_commits/index.md b/doc/user/project/repository/gpg_signed_commits/index.md
index 64f19d1a92c01432a0054b5a69f96877a6394bc7..a2dd24889611e8ab56141efac3499460bd4942c0 100644
--- a/doc/user/project/repository/gpg_signed_commits/index.md
+++ b/doc/user/project/repository/gpg_signed_commits/index.md
@@ -43,7 +43,7 @@ To view a user's public GPG key, you can either:
 
 - Go to `https://gitlab.example.com/<USERNAME>.gpg`. GitLab displays the GPG key,
   if the user has configured one, or a blank page for users without a configured GPG key.
-- Go to the user's profile (such as `https://gitlab.example.com/<USERNAME>`). In the upper right
+- Go to the user's profile (such as `https://gitlab.example.com/<USERNAME>`). In the upper-right corner
   of the user's profile, select **View public GPG keys** (**{key}**).
 
 ## Configure commit signing
diff --git a/doc/user/project/requirements/index.md b/doc/user/project/requirements/index.md
index b04905e6b34a23b290310808f84c7a7ee24847e4..4b5a9dcececc6a5d6e513eee28d2de6d0ca0be11 100644
--- a/doc/user/project/requirements/index.md
+++ b/doc/user/project/requirements/index.md
@@ -235,9 +235,9 @@ Before you import your file:
 To import requirements:
 
 1. In a project, go to **Issues > Requirements**.
-   - If the project already has existing requirements, select the import icon (**{import}**) in the
-     upper right.
-   - For a project without any requirements, select **Import CSV** in the middle of the page.
+   - For a project with requirements, in the
+     upper-right corner, select the import icon (**{import}**).
+   - For a project without requirements, in the middle of the page, select **Import CSV**.
 1. Select the file and select **Import requirements**.
 
 The file is processed in the background and a notification email is sent
@@ -296,7 +296,7 @@ Prerequisite:
 To export requirements:
 
 1. In a project, go to **Issues > Requirements**.
-1. In the upper right, select the **Export as CSV** icon (**{export}**).
+1. In the upper-right corner, select **Export as CSV** (**{export}**).
 
    A confirmation modal appears.
 
diff --git a/doc/user/project/web_ide/index.md b/doc/user/project/web_ide/index.md
index 5e9f648daba5729407cc11f68264ec55fb904b98..e2a74f0200810f69529630f279eda45c9730af26 100644
--- a/doc/user/project/web_ide/index.md
+++ b/doc/user/project/web_ide/index.md
@@ -22,7 +22,7 @@ and from merge requests:
 
 ### When viewing a file or the repository file list
 
-  1. In the upper right corner of the page, select **Open in Web IDE** if it is visible.
+  1. In the upper-right corner of the page, select **Open in Web IDE** if it is visible.
   1. If **Open in Web IDE** is not visible:
      1. Select the (**{chevron-lg-down}**) next to **Edit** or **Gitpod**, depending on your configuration.
      1. Select **Open in Web IDE** from the list to display it as the editing option.
@@ -31,7 +31,7 @@ and from merge requests:
 ### When viewing a merge request
 
   1. Go to your merge request.
-  1. In the upper right corner, select **Code > Open in Web IDE**.
+  1. In the upper-right corner, select **Code > Open in Web IDE**.
 
 ## File finder
 
diff --git a/doc/user/project/web_ide_beta/index.md b/doc/user/project/web_ide_beta/index.md
index fe110baf578bd61ed65f9f2547d9107890781b28..a52a9d579b282fe836f798d1de7c83041dc629fd 100644
--- a/doc/user/project/web_ide_beta/index.md
+++ b/doc/user/project/web_ide_beta/index.md
@@ -40,7 +40,7 @@ or a merge request.
 
 To open the Web IDE Beta from a file or the repository file list:
 
-- In the upper right of the page, select **Open in Web IDE**.
+- In the upper-right corner of the page, select **Open in Web IDE**.
 
 If **Open in Web IDE** is not visible:
 
@@ -53,7 +53,7 @@ If **Open in Web IDE** is not visible:
 To open the Web IDE Beta from a merge request:
 
 1. Go to your merge request.
-1. In the upper right corner, select **Code > Open in Web IDE**.
+1. In the upper-right corner, select **Code > Open in Web IDE**.
 
 ## Open a file in the Web IDE Beta
 
diff --git a/doc/user/project/working_with_projects.md b/doc/user/project/working_with_projects.md
index a0e6a78dfe2e1caad63d86b93f3df1755dbeebf2..dc005cf88a5da693706e4b93ec400c3aebf6a586 100644
--- a/doc/user/project/working_with_projects.md
+++ b/doc/user/project/working_with_projects.md
@@ -63,7 +63,7 @@ You can add a star to projects you use frequently to make them easier to find.
 To add a star to a project:
 
 1. On the top bar, select **Main menu > Projects** and find your project.
-1. In the upper right corner of the page, select **Star**.
+1. In the upper-right corner of the page, select **Star**.
 
 ## View starred projects
 
diff --git a/doc/user/search/index.md b/doc/user/search/index.md
index dc07b4c9215e49e8025ad58db8a567e6d0b3c85e..60d428850acf3360e3cdc9a8c303def0f4b6f586 100644
--- a/doc/user/search/index.md
+++ b/doc/user/search/index.md
@@ -50,7 +50,7 @@ Global search only flags with an error any search that includes more than:
 
 ## Perform a search
 
-To start a search, type your search query in the search bar in the upper right of the screen.
+To start a search, in the upper-right corner of the screen, in the search bar, type your search query.
 You must type at least two characters.
 
 ![search navbar](img/search_navbar_v15_7.png)
diff --git a/doc/user/shortcuts.md b/doc/user/shortcuts.md
index d67c595512a7259f95ac62c39bdf05aba141dc83..9c2925ec647c0d3ecf5f907ba45b84600d3ae410 100644
--- a/doc/user/shortcuts.md
+++ b/doc/user/shortcuts.md
@@ -15,7 +15,7 @@ To display a window in GitLab that lists its keyboard shortcuts, use one of the
 following methods:
 
 - Press <kbd>?</kbd>.
-- In the Help menu in the upper right of the application, select **Keyboard shortcuts**.
+- In the Help menu, in the upper-right corner of the application, select **Keyboard shortcuts**.
 
 Although [global shortcuts](#global-shortcuts) work from any area of GitLab,
 you must be in specific pages for the other shortcuts to be available, as
diff --git a/doc/user/todos.md b/doc/user/todos.md
index 50b60dc5b4b48eab64e441d1288e0195a345a0db..4951ba024afef008ed3ca74cb9249fe7826fdbc1 100644
--- a/doc/user/todos.md
+++ b/doc/user/todos.md
@@ -21,7 +21,7 @@ You can use the To-Do List to track [actions](#actions-that-create-to-do-items)
 
 To access your To-Do List:
 
-On the top bar, in the upper right, select To-Do List (**{task-done}**).
+On the top bar, in the upper-right corner, select the To-Do List (**{task-done}**).
 
 ## Search the To-Do List
 
@@ -158,7 +158,7 @@ There are two ways to do this:
 
 You can mark all your to-do items as done at the same time.
 
-In the To-Do List, in the upper right, select **Mark all as done**.
+In the To-Do List, in the upper-right corner, select **Mark all as done**.
 
 ## How a user's To-Do List is affected when their access changes