summaryrefslogtreecommitdiff
path: root/doc/update/restore_after_failure.md
diff options
context:
space:
mode:
Diffstat (limited to 'doc/update/restore_after_failure.md')
-rw-r--r--doc/update/restore_after_failure.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/update/restore_after_failure.md b/doc/update/restore_after_failure.md
index 0847fc82f19..e9c2c69ecb9 100644
--- a/doc/update/restore_after_failure.md
+++ b/doc/update/restore_after_failure.md
@@ -12,7 +12,7 @@ However, it's important to know how to recover when problems do arise.
## Roll back to an earlier version and restore a backup
In some cases after a failed upgrade, the fastest solution is to roll back to
-the previous version you were using. We recommend this path because the failed
+the previous version you were using. We recommend this path because the failed
upgrade will likely have made database changes that can not be readily reverted.
First, roll back the code or package. For source installations this involves