From c57a7cafc172e399d1122883f9c61a46ba376abe Mon Sep 17 00:00:00 2001 From: Michael Kozono Date: Wed, 1 Nov 2017 17:04:08 +0000 Subject: Fix typo --- doc/administration/repository_storage_types.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'doc') diff --git a/doc/administration/repository_storage_types.md b/doc/administration/repository_storage_types.md index 0cb2648cc1e..bc9b6253f1a 100644 --- a/doc/administration/repository_storage_types.md +++ b/doc/administration/repository_storage_types.md @@ -76,7 +76,7 @@ To migrate your existing projects to the new storage type, check the specific [r We are incrementally moving every storable object in GitLab to the Hashed Storage pattern. You can check the current coverage status below. -Not that things stored in S3 compatible endpoint, will not have the downsides mentioned earlier, if they are not +Note that things stored in an S3 compatible endpoint will not have the downsides mentioned earlier, if they are not prefixed with `#{namespace}/#{project_name}`, which is true for CI Cache and LFS Objects. | Storable Object | Legacy Storage | Hashed Storage | S3 Compatible | GitLab Version | -- cgit v1.2.1