Add latest changes from gitlab-org/gitlab@master

5 files changed, 6 insertions, 6 deletions

diff --git a/doc/integration/gitpod.md b/doc/integration/gitpod.md
index 7d53af89ca5..9df85e61798 100644
--- a/doc/integration/gitpod.md
+++ b/doc/integration/gitpod.md
@@ -47,7 +47,7 @@ For GitLab self-managed instances, a GitLab administrator needs to:
 1. Set up a Gitpod instance to integrate with GitLab. Refer to the [Gitpod documentation](https://www.gitpod.io/docs/self-hosted/latest)
    to get your instance up and running.
 1. Enable it in GitLab:
-   1. On the top bar, select **Menu >** **{admin}** **Admin**.
+   1. On the top bar, select **Menu > Admin**.
    1. In the left sidebar, select **Settings > General**.
    1. Expand the **Gitpod** configuration section.
    1. Check the **Enable Gitpod integration** checkbox.
diff --git a/doc/integration/kerberos.md b/doc/integration/kerberos.md
index ba3f246f5f5..de71b88666a 100644
--- a/doc/integration/kerberos.md
+++ b/doc/integration/kerberos.md
@@ -107,7 +107,7 @@ set up GitLab to create a new account when a Kerberos user tries to sign in.
 If you're an administrator, you can link a Kerberos account to an
 existing GitLab account. To do so:
 
-1. On the top bar, select **Menu >** **{admin}** **Admin**.
+1. On the top bar, select **Menu > Admin**.
 1. On the left sidebar, select **Overview > Users**.
 1. Select a user, then select the **Identities** tab.
 1. Select 'Kerberos SPNEGO' in the 'Provider' dropdown box.
@@ -147,7 +147,7 @@ With that information at hand:
       ```
 
       1. As an administrator, you can confirm the new, blocked account:
-         1. On the top bar, select **Menu >** **{admin}** **Admin**.
+         1. On the top bar, select **Menu > Admin**.
          1. On the left sidebar, select **Overview > Users** and review the **Blocked** tab.
       1. You can enable the user.
    1. If `block_auto_created_users` is false, the Kerberos user is
diff --git a/doc/integration/oauth_provider.md b/doc/integration/oauth_provider.md
index 0b1c9ca75da..b7578a452ea 100644
--- a/doc/integration/oauth_provider.md
+++ b/doc/integration/oauth_provider.md
@@ -81,7 +81,7 @@ To add a new application for a group:
 
 To create an application for your GitLab instance:
 
-1. On the top bar, select **Menu >** **{admin}** **Admin**.
+1. On the top bar, select **Menu > Admin**.
 1. On the left sidebar, select **Applications**.
 1. Select **New application**.
 
diff --git a/doc/integration/omniauth.md b/doc/integration/omniauth.md
index 99cdb42adfd..2ed7218cabb 100644
--- a/doc/integration/omniauth.md
+++ b/doc/integration/omniauth.md
@@ -269,7 +269,7 @@ By default, **Sign In** is enabled by using all the OAuth Providers that have be
 
 To enable/disable an OmniAuth provider:
 
-1. On the top bar, select **Menu >** **{admin}** **Admin**.
+1. On the top bar, select **Menu > Admin**.
 1. In the left sidebar, go to **Settings**.
 1. Scroll to the **Sign-in Restrictions** section, and click **Expand**.
 1. Below **Enabled OAuth Sign-In sources**, select the checkbox for each provider you want to enable or disable.
diff --git a/doc/integration/sourcegraph.md b/doc/integration/sourcegraph.md
index 86ca389e9b2..42c1722b69b 100644
--- a/doc/integration/sourcegraph.md
+++ b/doc/integration/sourcegraph.md
@@ -76,7 +76,7 @@ You can skip this step if you already have your GitLab repositories searchable i
 
 ### Configure your GitLab instance with Sourcegraph
 
-1. On the top bar, select **Menu >** **{admin}** **Admin**.
+1. On the top bar, select **Menu > Admin**.
 1. In the left sidebar, select **Settings > General**.
 1. Expand the **Sourcegraph** configuration section.
 1. Check **Enable Sourcegraph**.