Merge branch 'patch-34' into 'master'

Add storage shards wording

See merge request gitlab-org/gitlab!18732

doc/administration/repository_storage_paths.md

@@ -2,8 +2,8 @@
 
 > [Introduced][ce-4578] in GitLab 8.10.
 
-GitLab allows you to define multiple repository storage paths to distribute the
-storage load between several mount points.
+GitLab allows you to define multiple repository storage paths (sometimes called
+storage shards) to distribute the storage load between several mount points.
 
 > **Notes:**
 >

doc/administration/repository_storage_types.md

@@ -5,8 +5,8 @@
 Two different storage layouts can be used
 to store the repositories on disk and their characteristics.
 
-GitLab can be configured to use one or multiple repository shard locations
-that can be:
+GitLab can be configured to use one or multiple repository storage paths/shard
+locations that can be:
 
 - Mounted to the local disk
 - Exposed as an NFS shared volume
@@ -34,8 +34,8 @@ easy for Administrators to find where the repository is stored.
 On the other hand this has some drawbacks:
 
 Storage location will concentrate huge amount of top-level namespaces. The
-impact can be reduced by the introduction of [multiple storage
-paths][storage-paths].
+impact can be reduced by the introduction of
+[multiple storage paths](repository_storage_paths.md).
 
 Because backups are a snapshot of the same URL mapping, if you try to recover a
 very old backup, you need to verify whether any project has taken the place of
@@ -197,5 +197,4 @@ They are also S3 compatible since **10.0** (GitLab Premium), and available in Gi
 [ce-2821]: https://gitlab.com/gitlab-com/infrastructure/issues/2821
 [ce-28283]: https://gitlab.com/gitlab-org/gitlab-foss/issues/28283
 [rake/migrate-to-hashed]: raketasks/storage.md#migrate-existing-projects-to-hashed-storage
-[storage-paths]: repository_storage_types.md
 [gitaly]: gitaly/index.md