offer answers

1 files changed, 2 insertions, 1 deletions

diff --git a/docs/peers.md b/docs/peers.md
index 991bb40..5f5cfc9 100644
--- a/docs/peers.md
+++ b/docs/peers.md
@@ -178,7 +178,8 @@ as it knows them; of those, the ones it holds, and for any it lacks, the heads t
 share). The peer fetches them as a blob, in chunks (each deflated where that makes it
 at least a tenth smaller), from the sender and any other peer holding both sets of
 heads (every such peer produces the same bytes), loads them,
-and syncs on; the rest goes in ordinary messages. Until the peer answers, the sender
+and syncs on; the rest goes in ordinary messages. The offer is the sender's answer to
+what the peer sent: the peer waits for no other while it downloads. Until the peer answers, the sender
 sends it nothing; if the answer is overdue, it offers again (the same offer, without
 generating the message again, while neither side's heads moved). This is how a join without a
 recent remake, or a return after much was written, gets the bulk of its changes. A node