docs after trees

1 files changed, 5 insertions, 4 deletions

diff --git a/src/simtest/relay.rs b/src/simtest/relay.rs
index da1ce0a..0b7c739 100644
--- a/src/simtest/relay.rs
+++ b/src/simtest/relay.rs
@@ -15,10 +15,11 @@ const SOON: Duration = Duration::from_secs(30);
 
 /// a on `sim` alone, c on `sim2` alone, b on both; a full mesh at each (every member
 /// it reaches is its neighbour), so a pushes its write to b alone, and b, which only
-/// received it, must announce it to c. With a long keepalive, the regular STATUS (every
-/// third keepalive, 15 s) can't be what brings it: c has it within a second (an
-/// announcement waits 200 ms, then c pulls). Without the announcement, a STATUS that
-/// happens to fall into that second would pass it too, once in about 15 runs.
+/// received it, must pass it on to c: along a's tree at once (b is c's parent), else by
+/// announcement 200 to 400 ms later and a pull. With a long keepalive, the regular
+/// STATUS (every third keepalive, 15 s) can't be what brings it: c has it within a
+/// second. Without either, a STATUS that happens to fall into that second would pass it
+/// too, once in about 15 runs.
 #[tokio::test(flavor = "multi_thread", worker_threads = 4)]
 async fn changes_reach_members_the_writer_cant_reach_at_once() {
     let keepalive = Duration::from_secs(5);