summaryrefslogtreecommitdiff
path: root/doc/walkthrough/fsck:_verifying_your_data.mdwn
diff options
context:
space:
mode:
Diffstat (limited to 'doc/walkthrough/fsck:_verifying_your_data.mdwn')
-rw-r--r--doc/walkthrough/fsck:_verifying_your_data.mdwn2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/walkthrough/fsck:_verifying_your_data.mdwn b/doc/walkthrough/fsck:_verifying_your_data.mdwn
index d036332fb..62e15b6fa 100644
--- a/doc/walkthrough/fsck:_verifying_your_data.mdwn
+++ b/doc/walkthrough/fsck:_verifying_your_data.mdwn
@@ -2,7 +2,7 @@ You can use the fsck subcommand to check for problems in your data. What
can be checked depends on the key-value [[backend|backends]] you've used
for the data. For example, when you use the SHA1 backend, fsck will verify
that the checksums of your files are good. Fsck also checks that the
-annex.numcopies setting is satisfied for all files.
+[[numcopies|copies]] setting is satisfied for all files.
# git annex fsck
fsck some_file (checksum...) ok