Name what each of the three request paths skips

2026-09-28 10:25:08 +02:00
parent 469a91b9bb
commit b4bb531200
4 changed files with 13 additions and 14 deletions
@@ -772,7 +772,7 @@ rule and an index of the titles below.
  `OutgoingRequests.canCarry()` reads it rather than `closed`. The gate is told what happened and
  never reads back into the session: a collaborator that has to ask does not own its decision, which
  is how the first cut ended up answering the same question two different ways at admit and at
-  release. The retry in `carry()` asks `gate.awaitsNextLink()` rather than `canCarry()`, which also
+  release. The retry in `requestPastDrain()` asks `gate.awaitsNextLink()` rather than `canCarry()`, which also
  reads the socket: a loop condition the gate does not gate on spins against a gate that admits it
  straight back.