correction

diff --git a/doc/todo/generic_p2p_socket_transport/comment_2_57e4608559b0873617c82d5454cab798._comment b/doc/todo/generic_p2p_socket_transport/comment_2_57e4608559b0873617c82d5454cab798._comment
index 2780e6b75bf8ae836e1f8810c4a55e3c4d3dc4a4..9367e9e3237bda33d8c7d4a1658af86ea49989df 100644 (file)
--- a/doc/todo/generic_p2p_socket_transport/comment_2_57e4608559b0873617c82d5454cab798._comment
+++ b/doc/todo/generic_p2p_socket_transport/comment_2_57e4608559b0873617c82d5454cab798._comment
@@ -20,8 +20,9 @@ the generic one could be "p2p-annex::<path-to-socket-file>". Or it could be
 `git-annex-p2p-foo <bar>` and talk to its stdin and stdout.
 
 That's for outgoing connections. For incoming connections, 
-for tor, the remotedaemon looks to see if the socket file exists and
-if so it accepts connections from it. (That tor socket is not used for
+for tor, the remotedaemon creates the socket file that tor is configured to
+use for the hidden service, and listens to it
+to accept connections from tor. (That tor socket is not used for
 outgoing connections.) It would be easy to generalize this
 to additional socket filenames. Eg, a remote with uuid U could use
 `.git/annex/p2p/U` as its socket file.