aboutsummaryrefslogtreecommitdiffstats
path: root/docs/lifecycle.md
diff options
context:
space:
mode:
authortv <tv@krebsco.de>2026-11-18 12:48:29 +0000
committertv <tv@krebsco.de>2026-11-18 13:59:42 +0100
commitd130c0612b4c63f2d30da65ebcc231018c1f2606 (patch)
tree8700f2d53351cbbecbe772ea7701bf6240d5210c /docs/lifecycle.md
parent0bfe07af92a775b0e896e0fc5a989a1d9b65f7b3 (diff)
docs: references to another document's section linked to it
Where a document names a section of another after linking to it ("([`store.md`](store.md), Pinned checkpoints)"), the name links to that section too, by the id both GitHub and cgit's about filter give its heading; paragraphs that grew past the width are wrapped anew, links and code kept on one line each.
Diffstat (limited to 'docs/lifecycle.md')
-rw-r--r--docs/lifecycle.md13
1 files changed, 7 insertions, 6 deletions
diff --git a/docs/lifecycle.md b/docs/lifecycle.md
index 3140fa8..47cf051 100644
--- a/docs/lifecycle.md
+++ b/docs/lifecycle.md
@@ -164,12 +164,13 @@ The normal phase. The node:
Entered when enough active, ready members (two if this node was ready, one if it
never was) advertise the same newer epoch, at most 1000 generations ahead: the node
-missed a switch (it was away, or its own build didn't match). With several epochs of
-the newest generation advertised (two remakes committed for one epoch; [`remakes.md`](remakes.md),
-Limits), it follows the one most of them are on (of those, the lowest ID). A ready node
-also rejoins **sideways**, to another epoch of its own generation, when more ready
-members are on it than on its own (counting itself; two at least; on a tie, the lower
-ID): its own writes on the epoch it leaves all go to quarantine (step 5). What happens:
+missed a switch (it was away, or its own build didn't match). With several epochs of the
+newest generation advertised (two remakes committed for one epoch;
+[`remakes.md`](remakes.md), [Limits](remakes.md#limits)), it follows the one most of them
+are on (of those, the lowest ID). A ready node also rejoins **sideways**, to another epoch
+of its own generation, when more ready members are on it than on its own (counting itself;
+two at least; on a tie, the lower ID): its own writes on the epoch it leaves all go to
+quarantine (step 5). What happens:
1. at once (under the document's lock), the node swaps in an empty document labelled
with the target epoch, which takes no writes; sync with every peer resets; and a