summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorAshley Hindle <ashley@smellynose.com>2015-10-16 07:36:20 +0100
committerAshley Hindle <ashley@smellynose.com>2015-10-16 07:36:20 +0100
commita317c5296e9c142cfd04168eced7d7bfd9458ffa (patch)
tree22082e965fa00099494dd5e5021c3556a210208a
parent94ec666923174ed80fab6dd7af34c35578ef0f33 (diff)
downloadgitlab-ce-a317c5296e9c142cfd04168eced7d7bfd9458ffa.tar.gz
Changed loose to lose
-rw-r--r--doc/raketasks/backup_restore.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/raketasks/backup_restore.md b/doc/raketasks/backup_restore.md
index db3f6bb40bd..06f582dcee8 100644
--- a/doc/raketasks/backup_restore.md
+++ b/doc/raketasks/backup_restore.md
@@ -16,7 +16,7 @@ You need to keep a separate copy of `/etc/gitlab/gitlab-secrets.json`
from source). This file contains the database encryption key used
for two-factor authentication. If you restore a GitLab backup without
restoring the database encryption key, users who have two-factor
-authentication enabled will loose access to your GitLab server.
+authentication enabled will lose access to your GitLab server.
If you are interested in GitLab CI backup please follow to the [CI backup documentation](https://gitlab.com/gitlab-org/gitlab-ci/blob/master/doc/raketasks/backup_restore.md)*