deploy: f63d4a3a65e95d3845c43a9dd2893605b06f164a

1 files changed, 2 insertions, 4 deletions

diff --git a/dev-docs/develop/modules/federation_sender.html b/dev-docs/develop/modules/federation_sender.html

index 7d1e3fea15..55406e828f 100644
--- a/dev-docs/develop/modules/federation_sender.html
+++ b/dev-docs/develop/modules/federation_sender.html
@@ -268,10 +268,8 @@ was enabled</em>, Catch-Up Mode is exited and we return to <code class="docutils
 <h4 class="rubric" id="a-note-on-failures-and-back-offs">A note on failures and back-offs</h4>
 <p>If a remote server is unreachable over federation, we back off from that server,
 with an exponentially-increasing retry interval.
-Whilst we don’t automatically retry after the interval, we prevent making new attempts
-until such time as the back-off has cleared.
-Once the back-off is cleared and a new PDU or EDU arrives for transmission, the transmission
-loop resumes and empties the queue by making federation requests.</p>
+We automatically retry after the retry interval expires (roughly, the logic to do so
+being triggered every minute).</p>
 <p>If the backoff grows too large (&gt; 1 hour), the in-memory queue is emptied (to prevent
 unbounded growth) and Catch-Up Mode is entered.</p>
 <p>It is worth noting that the back-off for a remote server is cleared once an inbound