Add latest changes from gitlab-org/gitlab@master

8 files changed, 15 insertions, 15 deletions

diff --git a/doc/integration/advanced_search/elasticsearch.md b/doc/integration/advanced_search/elasticsearch.md
index 9c926add8c2..0a456e6c73e 100644
--- a/doc/integration/advanced_search/elasticsearch.md
+++ b/doc/integration/advanced_search/elasticsearch.md
@@ -168,7 +168,7 @@ Prerequisites:
 To enable advanced search:
 
 1. On the left sidebar, at the bottom, select **Admin Area**.
-1. On the left sidebar, select **Settings > Advanced Search**.
+1. Select **Settings > Advanced Search**.
 
    NOTE:
    To see the **Advanced Search** section, you need an active GitLab Premium
@@ -211,7 +211,7 @@ initial indexing, not to re-create an index from scratch.
 To enable advanced search with **Index all projects**:
 
 1. On the left sidebar, at the bottom, select **Admin Area**.
-1. On the left sidebar, select **Settings > Advanced Search**.
+1. Select **Settings > Advanced Search**.
 1. Select the **Elasticsearch indexing** checkbox, then select **Save changes**.
 1. Select **Index all projects**.
 1. Optional. Select **Check progress** to see the status of background jobs.
@@ -402,7 +402,7 @@ To enable languages support:
 
 1. Install the desired plugins, refer to [Elasticsearch documentation](https://www.elastic.co/guide/en/elasticsearch/plugins/7.9/installation.html) for plugins installation instructions. The plugins must be installed on every node in the cluster, and each node must be restarted after installation. For a list of plugins, see the table later in this section.
 1. On the left sidebar, at the bottom, select **Admin Area**.
-1. On the left sidebar, select **Settings > Advanced Search**.
+1. Select **Settings > Advanced Search**.
 1. Locate **Custom analyzers: language support**.
 1. Enable plugins support for **Indexing**.
 1. Select **Save changes** for the changes to take effect.
@@ -423,7 +423,7 @@ For guidance on what to install, see the following Elasticsearch language plugin
 To disable the Elasticsearch integration:
 
 1. On the left sidebar, at the bottom, select **Admin Area**.
-1. On the left sidebar, select **Settings > Advanced Search**.
+1. Select **Settings > Advanced Search**.
 1. Clear the **Elasticsearch indexing** and **Search with Elasticsearch enabled** checkboxes.
 1. Select **Save changes**.
 1. Optional. For Elasticsearch instances that are still online, delete existing indices:
@@ -439,7 +439,7 @@ To disable the Elasticsearch integration:
 ## Unpause Indexing
 
 1. On the left sidebar, at the bottom, select **Admin Area**.
-1. On the left sidebar, select **Settings > Advanced Search**.
+1. Select **Settings > Advanced Search**.
 1. Expand **Advanced Search**.
 1. Clear the **Pause Elasticsearch indexing** checkbox.
 
@@ -462,7 +462,7 @@ To trigger the reindexing process:
 
 1. Sign in to your GitLab instance as an administrator.
 1. On the left sidebar, at the bottom, select **Admin Area**.
-1. On the left sidebar, select **Settings > Advanced Search**.
+1. Select **Settings > Advanced Search**.
 1. Expand **Elasticsearch zero-downtime reindexing**.
 1. Select **Trigger cluster reindexing**.
 
@@ -477,7 +477,7 @@ While the reindexing is running, you can follow its progress under that same sec
 #### Elasticsearch zero-downtime reindexing
 
 1. On the left sidebar, at the bottom, select **Admin Area**.
-1. On the left sidebar, select **Settings > Advanced Search**.
+1. Select **Settings > Advanced Search**.
 1. Expand **Elasticsearch zero-downtime reindexing**, and you'll
    find the following options:
 
@@ -525,7 +525,7 @@ Sometimes, you might want to abandon the unfinished reindex job and resume the i
    ```
 
 1. On the left sidebar, at the bottom, select **Admin Area**.
-1. On the left sidebar, select **Settings > Advanced Search**.
+1. Select **Settings > Advanced Search**.
 1. Expand **Advanced Search**.
 1. Clear the **Pause Elasticsearch indexing** checkbox.
 
diff --git a/doc/integration/akismet.md b/doc/integration/akismet.md
index c4af7deccb9..b8b871d83f2 100644
--- a/doc/integration/akismet.md
+++ b/doc/integration/akismet.md
@@ -31,7 +31,7 @@ To use Akismet:
 1. Select **Show** to reveal the API key, and copy the API key's value.
 1. Sign in to GitLab as an administrator.
 1. On the left sidebar, at the bottom, select **Admin Area**.
-1. On the left sidebar, select **Settings > Reporting**.
+1. Select **Settings > Reporting**.
 1. Expand **Spam and Anti-bot Protection**.
 1. Select the **Enable Akismet** checkbox.
 1. Fill in the API key from step 3.
diff --git a/doc/integration/datadog.md b/doc/integration/datadog.md
index b5ea06cde57..c5fe2bc5f0f 100644
--- a/doc/integration/datadog.md
+++ b/doc/integration/datadog.md
@@ -28,7 +28,7 @@ project, group, or instance level:
 1. *For instance-level integrations:*
    1. Sign in to GitLab as a user with administrator access.
    1. On the left sidebar, at the bottom, select **Admin Area**.
-1. On the left sidebar, select **Settings > Integrations**.
+1. Select **Settings > Integrations**.
 1. Scroll to **Add an integration**, and select **Datadog**.
 1. Select **Active** to enable the integration.
 1. Specify the [**Datadog site**](https://docs.datadoghq.com/getting_started/site/) to send data to.
diff --git a/doc/integration/kerberos.md b/doc/integration/kerberos.md
index 63589ffec33..b5515a730d3 100644
--- a/doc/integration/kerberos.md
+++ b/doc/integration/kerberos.md
@@ -107,7 +107,7 @@ If you're an administrator, you can link a Kerberos account to an
 existing GitLab account. To do so:
 
 1. On the left sidebar, at the bottom, select **Admin Area**.
-1. On the left sidebar, select **Overview > Users**.
+1. Select **Overview > Users**.
 1. Select a user, then select the **Identities** tab.
 1. From the **Provider** dropdown list, select **Kerberos**.
 1. Make sure the **Identifier** corresponds to the Kerberos username.
diff --git a/doc/integration/oauth_provider.md b/doc/integration/oauth_provider.md
index 63a2a4fabf7..30e14e95d3b 100644
--- a/doc/integration/oauth_provider.md
+++ b/doc/integration/oauth_provider.md
@@ -76,7 +76,7 @@ To create a new application for a group:
 To create an application for your GitLab instance:
 
 1. On the left sidebar, at the bottom, select **Admin Area**.
-1. On the left sidebar, select **Applications**.
+1. Select **Applications**.
 1. Select **New application**.
 
 When creating application in the **Admin Area** , mark it as **trusted**.
diff --git a/doc/integration/omniauth.md b/doc/integration/omniauth.md
index de335b68fdd..ab43a14d169 100644
--- a/doc/integration/omniauth.md
+++ b/doc/integration/omniauth.md
@@ -258,7 +258,7 @@ By default, sign-in is enabled for all the OAuth providers configured in `config
 To enable or disable an OmniAuth provider:
 
 1. On the left sidebar, at the bottom, select **Admin Area**.
-1. On the left sidebar, select **Settings > General**.
+1. Select **Settings > General**.
 1. Expand **Sign-in restrictions**.
 1. In the **Enabled OAuth authentication sources** section, select or clear the checkbox for each provider you want to enable or disable.
 
diff --git a/doc/integration/recaptcha.md b/doc/integration/recaptcha.md
index 52d72e56e5b..bee6381a078 100644
--- a/doc/integration/recaptcha.md
+++ b/doc/integration/recaptcha.md
@@ -18,7 +18,7 @@ To use reCAPTCHA, first create a site and private key.
 1. To get reCAPTCHA v2 keys, fill in the form and select **Submit**.
 1. Sign in to your GitLab server as an administrator.
 1. On the left sidebar, at the bottom, select **Admin Area**.
-1. On the left sidebar, select **Settings > Reporting**.
+1. Select **Settings > Reporting**.
 1. Expand **Spam and Anti-bot Protection**.
 1. In the reCAPTCHA fields, enter the keys you obtained in the previous steps.
 1. Select the **Enable reCAPTCHA** checkbox.
diff --git a/doc/integration/sourcegraph.md b/doc/integration/sourcegraph.md
index b8cf4895542..f6fb387f016 100644
--- a/doc/integration/sourcegraph.md
+++ b/doc/integration/sourcegraph.md
@@ -49,7 +49,7 @@ You can skip this step if you already have your GitLab repositories searchable i
 ### Configure your GitLab instance with Sourcegraph
 
 1. On the left sidebar, at the bottom, select **Admin Area**.
-1. On the left sidebar, select **Settings > General**.
+1. Select **Settings > General**.
 1. Expand the **Sourcegraph** configuration section.
 1. Check **Enable Sourcegraph**.
 1. Set the Sourcegraph URL to your Sourcegraph instance, such as `https://sourcegraph.example.com`.