aboutsummaryrefslogtreecommitdiffstats
path: root/docs/remakes.md
diff options
context:
space:
mode:
authortv <tv@krebsco.de>2026-11-18 12:41:10 +0000
committertv <tv@krebsco.de>2026-11-18 13:42:58 +0100
commit0bfe07af92a775b0e896e0fc5a989a1d9b65f7b3 (patch)
treecd8d576ac13160163a2cee508cf985ef183b3a01 /docs/remakes.md
parentb0f0e1a9edb08b324df2ec5e97d15e7089349fdb (diff)
docs: references to a section of the same document linked to it
Where a document names one of its own sections in parentheses ("(What counts, 5)", "(Joining, below)"), the name links to the section by its GitHub-style ID; paragraphs that grew past the width are wrapped anew, links and code kept on one line each. References to another document's sections stay as they are.
Diffstat (limited to 'docs/remakes.md')
-rw-r--r--docs/remakes.md6
1 files changed, 3 insertions, 3 deletions
diff --git a/docs/remakes.md b/docs/remakes.md
index 5a12873..94d50dc 100644
--- a/docs/remakes.md
+++ b/docs/remakes.md
@@ -395,8 +395,8 @@ remake report's `local.quarantine` on that node names the entry.
own`, error), but it follows peers that did: the epoch most of them are on. Nodes on
the other epoch of that generation rejoin it sideways once they see themselves
outnumbered (`More peers are on another epoch of this generation than on ours`,
- warn), and what was written there goes to quarantine ([`lifecycle.md`](lifecycle.md), Rejoining).
- Look at those quarantines; report how it came about (Limits).
+ warn), and what was written there goes to quarantine ([`lifecycle.md`](lifecycle.md),
+ Rejoining). Look at those quarantines; report how it came about ([Limits](#limits)).
* **Repairing records by hand.** Remake records live in the document under
`_continuum/remakes/<id>`. Old ones need no cleaning up: an epoch's document holds
the remakes proposed in it and the record of the remake that made it, and earlier
@@ -434,7 +434,7 @@ remake report's `local.quarantine` on that node names the entry.
in its electorate (with three members and one cut off, two joining on its side make
it 3 of 5 there, while the other side has 2 of 3). Two epochs of
the next generation result; the swarm follows the one more nodes are on, and the
- others' writes there are quarantined (Troubleshooting).
+ others' writes there are quarantined ([Troubleshooting](#troubleshooting)).
* **Same Automerge version.** Every node must build byte-identical snapshots, so all
nodes need the same Automerge version. A node whose build differs rejoins instead.
* **Lost votes.** Votes aren't stored outside the document. A node that voted, then