diff options
| author | tv <tv@krebsco.de> | 2026-11-18 12:48:29 +0000 |
|---|---|---|
| committer | tv <tv@krebsco.de> | 2026-11-18 13:59:42 +0100 |
| commit | d130c0612b4c63f2d30da65ebcc231018c1f2606 (patch) | |
| tree | 8700f2d53351cbbecbe772ea7701bf6240d5210c /docs/guides/federation/checkpoints.md | |
| parent | 0bfe07af92a775b0e896e0fc5a989a1d9b65f7b3 (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/guides/federation/checkpoints.md')
| -rw-r--r-- | docs/guides/federation/checkpoints.md | 17 |
1 files changed, 9 insertions, 8 deletions
diff --git a/docs/guides/federation/checkpoints.md b/docs/guides/federation/checkpoints.md index 23f0e9c..66f79e9 100644 --- a/docs/guides/federation/checkpoints.md +++ b/docs/guides/federation/checkpoints.md @@ -2,8 +2,8 @@ A checkpoint writes down what counts at some heads, so that nodes forget the rest and hold what is relevant. The parties pass it as any version. The rules are the design's -([`federation.md`](../../federation.md), Checkpoints; [`store.md`](../../store.md), -Checkpoints). +([`federation.md`](../../federation.md), [Checkpoints](../../federation.md#checkpoints); +[`store.md`](../../store.md), [Checkpoints](../../store.md#checkpoints)). ## What one does @@ -23,12 +23,13 @@ isn't above the heads, which its party signs again ([After a move](#after-a-move A version that only moves the store on is the current one with the next `number`, the current version's hash as `changes`, and the heads as `checkpoint` -([`proposing-and-voting.md`](proposing-and-voting.md), Writing a version). The heads are -events after the current checkpoint, at which the current version is current too, none in +([`proposing-and-voting.md`](proposing-and-voting.md), +[Writing a version](proposing-and-voting.md#writing-a-version)). The heads are events +after the current checkpoint, at which the current version is current too, none in another's history, their IDs ascending: heads a node showed (`heads` in `GET /events`) -once the version was written, and that it has held for a while since, so that every -node holds them. Propose it afterwards: the client signs the proposal on the heads its -node shows then, above the ones it names, as it must be. +once the version was written, and that it has held for a while since, so that every node +holds them. Propose it afterwards: the client signs the proposal on the heads its node +shows then, above the ones it names, as it must be. Like any version, it lapses the proposals on the version before: propose one where nothing that can still pass is proposed on the current version. @@ -75,4 +76,4 @@ leaves out what a checkpoint forgot, the document holds what came before, and a that was away builds the checkpoint from it as any. After such a remake, a node away across it, or joining, takes the checkpoint only where its operator pins it: ask a node you trust for it (`checkpoint` in `GET /events`) -([`running-a-node.md`](running-a-node.md), Joining). +([`running-a-node.md`](running-a-node.md), [Joining](running-a-node.md#joining)). |
