diff --git a/doc/forum/Cannot_get_unlocked_file_contents/comment_3_57ee489f24b26b73b28f64566e2b8ff5._comment b/doc/forum/Cannot_get_unlocked_file_contents/comment_3_57ee489f24b26b73b28f64566e2b8ff5._comment
new file mode 100644
index 0000000000..b48377726d
--- /dev/null
+++ b/doc/forum/Cannot_get_unlocked_file_contents/comment_3_57ee489f24b26b73b28f64566e2b8ff5._comment
@@ -0,0 +1,10 @@
+[[!comment format=mdwn
+ username="Maximilian"
+ avatar="http://cdn.libravatar.org/avatar/e7add028a8da87278c36a3d7b9f1cd60"
+ subject="comment 3"
+ date="2020-10-12T19:53:27Z"
+ content="""
+@Lukey: thanks for the tip. Will try this at some point with a new repo. For now I just copied the most recent version of the file from /annex/objects/ of my central repo. 
+
+@joey: I am afraid I committed the hash-link contents: 'git annex get' didn't change anything. Still I have no idea how this could happen; I'll dig through the history and report back :) 
+"""]]
diff --git a/doc/todo/memory_use_increase/comment_4_774d540ce6f5c3ffda924159e146721e._comment b/doc/todo/memory_use_increase/comment_4_774d540ce6f5c3ffda924159e146721e._comment
index 5d94c1cedc..f877c89000 100644
--- a/doc/todo/memory_use_increase/comment_4_774d540ce6f5c3ffda924159e146721e._comment
+++ b/doc/todo/memory_use_increase/comment_4_774d540ce6f5c3ffda924159e146721e._comment
@@ -28,5 +28,5 @@ is in use.
 
 Hmm, this doesn't explain the memory leak (throwing in a S.copy didn't fix
 it either) or why profiling doesn't show the full memory use, but it does
-explain the PINNED memory use, probably.
+start to explain the PINNED memory use.
 """]]