diff --git a/doc/git-annex-unlock/comment_8_d10c8b6e2dd8800cbfc11a7fa8536065._comment b/doc/git-annex-unlock/comment_8_d10c8b6e2dd8800cbfc11a7fa8536065._comment
new file mode 100644
index 0000000000..b8ec3bb67a
--- /dev/null
+++ b/doc/git-annex-unlock/comment_8_d10c8b6e2dd8800cbfc11a7fa8536065._comment
@@ -0,0 +1,10 @@
+[[!comment format=mdwn
+ username="pat"
+ avatar="http://cdn.libravatar.org/avatar/6b552550673a6a6df3b33364076f8ea8"
+ subject="Are my unlocked, annexed files still safe?"
+ date="2021-04-21T15:47:48Z"
+ content="""
+I want to double-check something: if I've annexed and committed files, I believe they are safely stored in git-annex even if I unlock them (as long as I don't use `--thin`). If I annex copies of the the same file, annex will only store it once, and use a symlink for the two original files. But if I unlock them, I can edit them independently.
+
+Basically, unlock gives me an editable copy of the file - but I always have the original version, and can revert or check it out if I need to. Is that correct?
+"""]]
diff --git a/doc/git-annex-unlock/comment_9_31c72f60ddf029f09c1850223d5a8a55._comment b/doc/git-annex-unlock/comment_9_31c72f60ddf029f09c1850223d5a8a55._comment
new file mode 100644
index 0000000000..0a61a8954a
--- /dev/null
+++ b/doc/git-annex-unlock/comment_9_31c72f60ddf029f09c1850223d5a8a55._comment
@@ -0,0 +1,8 @@
+[[!comment format=mdwn
+ username="Ilya_Shlyakhter"
+ avatar="http://cdn.libravatar.org/avatar/1647044369aa7747829c38b9dcc84df0"
+ subject="clarifying unlocked files"
+ date="2021-04-21T16:08:05Z"
+ content="""
+Does the locked/unlocked state apply to one particular path within the repo, or to a particular key?  Can the same key be used by both a locked and an unlocked file?
+"""]]
diff --git a/doc/todo/hiding_a_repository/comment_3_64ba3f1d5099e066d554566ca818bdd6._comment b/doc/todo/hiding_a_repository/comment_3_64ba3f1d5099e066d554566ca818bdd6._comment
new file mode 100644
index 0000000000..fcc0579327
--- /dev/null
+++ b/doc/todo/hiding_a_repository/comment_3_64ba3f1d5099e066d554566ca818bdd6._comment
@@ -0,0 +1,8 @@
+[[!comment format=mdwn
+ username="Ilya_Shlyakhter"
+ avatar="http://cdn.libravatar.org/avatar/1647044369aa7747829c38b9dcc84df0"
+ subject="auto-expire temp repos"
+ date="2021-04-21T15:37:37Z"
+ content="""
+As a possible simpler alternative, maybe add an option to [[git-annex-dead]] to mark a repo dead from a future time onwards?  I often have temp repos created on temp cloud instances.   I mark them untrusted right after cloning, and then manually mark them dead after the cloud instance is gone.  If the latter part were automated, would that cover most of what hidden repos do?
+"""]]