diff --git a/doc/bugs/fsck_tells___39__ok__39___also_if_no_file_present.mdwn b/doc/bugs/fsck_tells___39__ok__39___also_if_no_file_present.mdwn
index bd552daa51..860a94f3d1 100644
--- a/doc/bugs/fsck_tells___39__ok__39___also_if_no_file_present.mdwn
+++ b/doc/bugs/fsck_tells___39__ok__39___also_if_no_file_present.mdwn
@@ -74,3 +74,4 @@ sc@section9 ~> cat /etc/issue
 ### Have you had any luck using git-annex before? (Sometimes we get tired of reading bug reports all day and a lil' positive end note does wonders)
 
 
+> [[notabug|done]] (I did add some more detail to the man page tho) --[[Joey]]
diff --git a/doc/bugs/fsck_tells___39__ok__39___also_if_no_file_present/comment_1_ddde7370b75814987b5dd1bc7d416cf7._comment b/doc/bugs/fsck_tells___39__ok__39___also_if_no_file_present/comment_1_ddde7370b75814987b5dd1bc7d416cf7._comment
new file mode 100644
index 0000000000..22ce7a4c23
--- /dev/null
+++ b/doc/bugs/fsck_tells___39__ok__39___also_if_no_file_present/comment_1_ddde7370b75814987b5dd1bc7d416cf7._comment
@@ -0,0 +1,18 @@
+[[!comment format=mdwn
+ username="joey"
+ subject="""comment 1"""
+ date="2020-04-27T16:02:29Z"
+ content="""
+fsck finds problems with the repository.
+
+A file not being present in the local repository is not a problem, if the
+file is known to be present in some other repository.
+
+The ability to have some files not present in the local repository, but
+retreivable by `git annex get` when you need them, is one of the main
+features of git-annex, since it lets you manage quantities of data larger
+than you have space for on your computer.
+
+If you want to know what files are not present in your local repository,
+there is a way to do that: `git annex find --not --in here`
+"""]]
diff --git a/doc/git-annex-fsck.mdwn b/doc/git-annex-fsck.mdwn
index 369a583ca0..472c5a70af 100644
--- a/doc/git-annex-fsck.mdwn
+++ b/doc/git-annex-fsck.mdwn
@@ -8,11 +8,16 @@ git annex fsck `[path ...]`
 
 # DESCRIPTION
 
-With no parameters, this command checks the whole annex for consistency,
-and warns about or fixes any problems found. This is a good complement to
-`git fsck`.
+This command checks annexed files for consistency, and warns about or
+fixes any problems found. This is a good complement to `git fsck`.
 
-With parameters, only the specified files are checked.
+The default is to check all annexed files in the current directory and
+subdirectories. With parameters, only the specified files are checked.
+
+The problems fsck finds include files that have gotten corrupted,
+files whose content has somehow become lost, files that do not have the
+configured number of copies yet made, and keys that can be upgraded to a
+better format.
 
 # OPTIONS