Merge branch 'docs/harmonise-geo-sections' into 'master'

Remove unnecessary warning and add other minor improvements

See merge request gitlab-org/gitlab-ee!8722

doc/administration/geo/replication/configuration.md

@@ -205,21 +205,14 @@ that the secondary can act on those notifications immediately.
 Make sure the secondary instance is running and accessible.
 You can login to the secondary node with the same credentials as used in the primary.
 
-### Step 4. Enabling hashed storage (from GitLab 10.0)
+### Step 4. Enabling Hashed Storage
 
-CAUTION: **Warning**:
-Hashed storage is in **Beta**. It is not considered production-ready. See
-[Hashed Storage] for more detail, and for the latest updates, check
-infrastructure issue [gitlab-com/infrastructure#2821].
-
-Using hashed storage significantly improves Geo replication - project and group
+Using Hashed Storage significantly improves Geo replication. Project and group
 renames no longer require synchronization between nodes.
 
-1. Visit the **primary** node's **Admin Area > Settings**
-   (`/admin/application_settings`) in your browser
-1. In the `Repository Storages` section, check `Create new projects using hashed storage paths`:
-
-    ![](img/hashed_storage.png)
+1. Visit the **primary** node's **Admin Area > Settings > Repository**
+   (`/admin/application_settings/repository`) in your browser.
+1. In the **Repository storage** section, check **Use hashed storage paths for newly created and renamed projects**.
 
 ### Step 5. (Optional) Configuring the secondary to trust the primary
 

doc/administration/geo/replication/configuration_source.md

@@ -126,9 +126,9 @@ that the secondary can act on those notifications immediately.
 Make sure the secondary instance is running and accessible.
 You can login to the secondary node with the same credentials as used in the primary.
 
-### Step 4. Enabling hashed storage (from GitLab 10.0)
+### Step 4. Enabling Hashed Storage
 
-Read [Enabling Hashed Storage][configuration-hashed-storage]
+Read [Enabling Hashed Storage](configuration.md##step-4-enabling-hashed-storage).
 
 ### Step 5. (Optional) Configuring the secondary to trust the primary
 
@@ -157,7 +157,6 @@ method to be enabled. Navigate to **Admin Area > Settings**
 
 Read [Verify proper functioning of the secondary node][configuration-verify-node].
 
-
 ## Selective synchronization
 
 Read [Selective synchronization][configuration-selective-replication].
@@ -169,7 +168,6 @@ Read the [troubleshooting document][troubleshooting].
 [setup-geo-source]: index.md#using-gitlab-installed-from-source
 [gitlab-org/gitlab-ee#3789]: https://gitlab.com/gitlab-org/gitlab-ee/issues/3789
 [configuration]: configuration.md
-[configuration-hashed-storage]: configuration.md#step-4-optional-enabling-hashed-storage-from-gitlab-10-0
 [configuration-replicate-ssh]: configuration.md#step-2-manually-replicate-primary-ssh-host-keys
 [configuration-selective-replication]: configuration.md#selective-synchronization
 [configuration-verify-node]: configuration.md#step-7-verify-proper-functioning-of-the-secondary-node