diff --git a/doc/git-annex-fix/comment_1_0d8c0a803be4576a3048b231b19a4a6a._comment b/doc/git-annex-fix/comment_1_0d8c0a803be4576a3048b231b19a4a6a._comment
new file mode 100644
index 0000000000..7cbbbb1e0d
--- /dev/null
+++ b/doc/git-annex-fix/comment_1_0d8c0a803be4576a3048b231b19a4a6a._comment
@@ -0,0 +1,9 @@
+[[!comment format=mdwn
+ username="eric.w@eee65cd362d995ced72640c7cfae388ae93a4234"
+ nickname="eric.w"
+ avatar="http://cdn.libravatar.org/avatar/8d9808c12db3a3f93ff7f9e74c0870fc"
+ subject="comment 1"
+ date="2020-11-20T22:16:34Z"
+ content="""
+If I move a symlink up one directory (thus breaking it), git-annex fix \"symlink-name\" doesn't do anything. the only way I could find to fix it was to do a git annex add $symlink-name. what am I doing wrong?
+"""]]
diff --git a/doc/special_remotes/git.mdwn b/doc/special_remotes/git.mdwn
index 080fecdbf8..0f729ae4cf 100644
--- a/doc/special_remotes/git.mdwn
+++ b/doc/special_remotes/git.mdwn
@@ -4,7 +4,7 @@ remote of the normal kind. Two exceptions to that are [[git-lfs]] and
 
 But it is possible to register a git repository as a special remote.
 git-annex and git will use the remote the same as any normal git remote,
-but its url will be recorded in the repisitory. One benefit of doing this
+but its url will be recorded in the repository. One benefit of doing this
 is it allows [[git-annex init|git-annex-init]] to autoenable the remote.
 
 First you need a regular git remote with the url that you want to use for