always announce new heads

1 files changed, 4 insertions, 5 deletions

diff --git a/docs/peers.md b/docs/peers.md
index c63cec1..3b107bf 100644
--- a/docs/peers.md
+++ b/docs/peers.md
@@ -283,11 +283,10 @@ that announce heads it lacks meanwhile wait their turn and are pulled from as so
 the current pull is answered, if they still have something it lacks. The regular
 STATUS (every third keepalive) triggers the same pull, so gaps close within a few
 keepalive intervals. A node
-that just caught up announces its heads once. In a full mesh nothing is announced: the
-writer reaches everyone (while a node doesn't know its neighbours yet, it announces);
-but to the neighbours the writer can't reach, those on none of its transports (by the
-member list, the writer's neighbours as this node computes them): a node on Tor and
-libp2p announces to one on Tor alone what came from one on libp2p alone.
+that just caught up announces its heads once. In a full mesh too: the member list makes
+every member the writer's neighbour, but the writer may reach fewer of them (one behind
+NAT may reach a single one, one on libp2p alone none on Tor alone), and no node can tell
+which from where it is. A neighbour that has the changes already only answers.
 
 ## Keepalive and self-healing