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.mdwn10
1 files changed, 5 insertions, 5 deletions
diff --git a/doc/walkthrough/fsck:_verifying_your_data.mdwn b/doc/walkthrough/fsck:_verifying_your_data.mdwn
index 7e05469a1..d036332fb 100644
--- a/doc/walkthrough/fsck:_verifying_your_data.mdwn
+++ b/doc/walkthrough/fsck:_verifying_your_data.mdwn
@@ -1,8 +1,8 @@
-You can use the fsck subcommand to check for problems in your data.
-What can be checked depends on the [[backend|backends]] you've used to store
-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.
+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.
# git annex fsck
fsck some_file (checksum...) ok