summaryrefslogtreecommitdiff
path: root/doc/update/restore_after_failure.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/update/restore_after_failure.md
parent6044caed20964a70c1ac6c5a3365d567ed96dfde (diff)
downloadgitlab-ce-0d0cddc9ce20c5a7d8a2723d0aa620ca184a711a.tar.gz
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'doc/update/restore_after_failure.md')
-rw-r--r--doc/update/restore_after_failure.md6
1 files changed, 3 insertions, 3 deletions
diff --git a/doc/update/restore_after_failure.md b/doc/update/restore_after_failure.md
index 99329fdceb3..e01ae409bb3 100644
--- a/doc/update/restore_after_failure.md
+++ b/doc/update/restore_after_failure.md
@@ -45,7 +45,7 @@ need to do.
### GitLab 8.6+
-Pass the version to a database rake task to manually mark the migration as
+Pass the version to a database Rake task to manually mark the migration as
complete.
```shell
@@ -56,7 +56,7 @@ sudo -u git -H bundle exec rake gitlab:db:mark_migration_complete[20151103134857
sudo gitlab-rake gitlab:db:mark_migration_complete[20151103134857]
```
-Once the migration is successfully marked, run the rake `db:migrate` task again.
+Once the migration is successfully marked, run the Rake `db:migrate` task again.
You will likely have to repeat this process several times until all failed
migrations are marked complete.
@@ -77,6 +77,6 @@ ActiveRecord::Base.connection.execute("INSERT INTO schema_migrations (version) V
exit
```
-Once the migration is successfully marked, run the rake `db:migrate` task again.
+Once the migration is successfully marked, run the Rake `db:migrate` task again.
You will likely have to repeat this process several times until all failed
migrations are marked complete.