summaryrefslogtreecommitdiff
path: root/doc/development/file_storage.md
diff options
context:
space:
mode:
authorGitLab Bot <gitlab-bot@gitlab.com>2020-03-31 12:08:09 +0000
committerGitLab Bot <gitlab-bot@gitlab.com>2020-03-31 12:08:09 +0000
commit0d0cddc9ce20c5a7d8a2723d0aa620ca184a711a (patch)
tree64f91b4d4ca74aa09d2a62ac5910820d087ed7cb /doc/development/file_storage.md
parent6044caed20964a70c1ac6c5a3365d567ed96dfde (diff)
downloadgitlab-ce-0d0cddc9ce20c5a7d8a2723d0aa620ca184a711a.tar.gz
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'doc/development/file_storage.md')
-rw-r--r--doc/development/file_storage.md4
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/development/file_storage.md b/doc/development/file_storage.md
index adfb92acc54..e16fe7eba5b 100644
--- a/doc/development/file_storage.md
+++ b/doc/development/file_storage.md
@@ -50,9 +50,9 @@ In the case of Issues/MR/Notes Markdown attachments, there is a different approa
instead of basing the path into a mutable variable `:project_path_with_namespace`, it's possible to use the
hash of the project ID instead, if project migrates to the new approach (introduced in 10.2).
-> Note: We provide an [all-in-one rake task] to migrate all uploads to object
+> Note: We provide an [all-in-one Rake task] to migrate all uploads to object
> storage in one go. If a new Uploader class or model type is introduced, make
-> sure you add a rake task invocation corresponding to it to the [category
+> sure you add a Rake task invocation corresponding to it to the [category
> list].
### Path segments