summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorPeter Leitzen <pleitzen@gitlab.com>2019-08-28 10:58:29 +0000
committerPeter Leitzen <pleitzen@gitlab.com>2019-08-28 10:58:29 +0000
commitddcf45dd5893a85d4c62ecf63173d1e99656ab90 (patch)
tree919adcd5cd172a8e5e0ac9298f8b4d683a65290f
parent7e2bdf58ba55c8b8cec9ff642475721c31ec1788 (diff)
downloadgitlab-ce-pl-migrations-new-instances-docs.tar.gz
Apply suggestion to doc/development/post_deployment_migrations.mdpl-migrations-new-instances-docs
-rw-r--r--doc/development/post_deployment_migrations.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/development/post_deployment_migrations.md b/doc/development/post_deployment_migrations.md
index 24719f1800b..adc9b4e4737 100644
--- a/doc/development/post_deployment_migrations.md
+++ b/doc/development/post_deployment_migrations.md
@@ -76,7 +76,7 @@ Some other examples where these migrations are useful:
### When not to use post deployment migrations
-As described above, post migrations might be useful, however, they are not
+As described above, post deployment migrations might be useful, however, they are not
run during setup of a new GitLab instance.
Some examples where these migration are NOT useful: