reach set for the session

2 files changed, 5 insertions, 3 deletions

diff --git a/docs/openapi.yaml b/docs/openapi.yaml
index b7cd3ab..03f75d9 100644
--- a/docs/openapi.yaml
+++ b/docs/openapi.yaml
@@ -1638,7 +1638,7 @@ components:
           type: [array, 'null']
           items:
             type: string
-          description: The members it said it reaches, by node ID (those in our member list); null before it said so, or once that is stale.
+          description: The members it said it reaches, by node ID (those in our member list); null before it said so since its session began (handshake, or back from dormant).
         traffic:
           $ref: '#/components/schemas/Traffic'
         incidents:
diff --git a/docs/peers.md b/docs/peers.md
index 939f318..377d8aa 100644
--- a/docs/peers.md
+++ b/docs/peers.md
@@ -302,8 +302,10 @@ has an active session with (handshake done, neither dormant nor unreachable), ea
 an 8-byte key (the hash its pair scores come from), in its keepalive STATUSes and
 their replies, and within 5 s when it changed; not in announcements of heads, which go
 often. So every node knows its 2-hop neighbourhood as measured, not as the member list
-says, for as long as it is fresh (two STATUS refreshes and a keepalive: 7 minutes with
-the default keepalive), and nothing goes into the document. `GET /peers` shows it
+says, for as long as each neighbour's session lasts (one that goes dormant or starts
+anew says it again), and nothing goes into the document. Not for a set time: while a
+pair exchanges changes it sends no keepalives, and so no STATUS, however long the
+writes go on. `GET /peers` shows it
 (`localReaches`, and `reaches` per peer).
 
 A writer's changes pass on along its tree ([`swarm/tree.rs`](../src/swarm/tree.rs)), the same on every node: