aboutsummaryrefslogtreecommitdiffstats
path: root/docs/guides/federation/voting-by-itself.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/guides/federation/voting-by-itself.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/guides/federation/voting-by-itself.md')
-rw-r--r--docs/guides/federation/voting-by-itself.md18
1 files changed, 9 insertions, 9 deletions
diff --git a/docs/guides/federation/voting-by-itself.md b/docs/guides/federation/voting-by-itself.md
index bf7a01e..300f60c 100644
--- a/docs/guides/federation/voting-by-itself.md
+++ b/docs/guides/federation/voting-by-itself.md
@@ -2,8 +2,8 @@
A party may have one of its nodes vote and propose for it, by rules its operator sets,
written nowhere in the swarm: every node judges what such a node signs as any vote or
-proposal. The rules are the design's ([`federation.md`](../../federation.md), Votes a
-node casts by itself).
+proposal. The rules are the design's ([`federation.md`](../../federation.md),
+[Votes a node casts by itself](../../federation.md#votes-a-node-casts-by-itself)).
## Setting it up
@@ -56,13 +56,13 @@ or `POST /admin/events/vote` with `{"proposal": "8d02…", "yes": true}`.
## What it keeps to
What a party's client keeps to: one `true` at a time, never `true` and `false` on one
-proposal, nothing on the version its record began on, and no `true` for a proposal that
-is no version ([`proposing-and-voting.md`](proposing-and-voting.md), Voting). And, for a
-version naming a checkpoint, the voters' rule: it backs one only where it changes nothing
-of the current version but its number, what it changes and its checkpoint, and its heads
-leave out nothing it held for a while before it was proposed
-([`checkpoints.md`](checkpoints.md), Backing one). A vote by hand through it keeps to the
-same.
+proposal, nothing on the version its record began on, and no `true` for a proposal that is
+no version ([`proposing-and-voting.md`](proposing-and-voting.md),
+[Voting](proposing-and-voting.md#voting)). And, for a version naming a checkpoint, the
+voters' rule: it backs one only where it changes nothing of the current version but its
+number, what it changes and its checkpoint, and its heads leave out nothing it held for a
+while before it was proposed ([`checkpoints.md`](checkpoints.md),
+[Backing one](checkpoints.md#backing-one)). A vote by hand through it keeps to the same.
It signs its votes on the events proposing what it votes on, and its checkpoint
proposals on its heads, so that a version event may be written on them.