From d130c0612b4c63f2d30da65ebcc231018c1f2606 Mon Sep 17 00:00:00 2001 From: tv Date: Wed, 18 Nov 2026 12:48:29 +0000 Subject: 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. --- docs/guides/federation/remakes.md | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) (limited to 'docs/guides/federation/remakes.md') diff --git a/docs/guides/federation/remakes.md b/docs/guides/federation/remakes.md index ef60266..05c27ab 100644 --- a/docs/guides/federation/remakes.md +++ b/docs/guides/federation/remakes.md @@ -3,7 +3,8 @@ A remake moves a swarm to a new document, for Automerge's sake only: the store needs none, and its events stay what they are. A federated swarm takes compactions only. How a remake runs is as in any swarm ([`remakes.md`](../../remakes.md)); this guide says what is -otherwise. The rules are the store's ([`store.md`](../../store.md), Remakes). +otherwise. The rules are the store's ([`store.md`](../../store.md), +[Remakes](../../store.md#remakes)). ## Proposing one @@ -53,8 +54,8 @@ document, one its operator pins (`--store-checkpoint`), or, to an empty document root; and only one with its swarm's policy. A made-up epoch can withhold events from a node and keep it apart from the others, but make it take nothing it wouldn't. A node that can't follow the others' epoch, as its snapshot holds a checkpoint it can't build, -follows it once its operator pins that checkpoint -([`checkpoints.md`](checkpoints.md), Nodes that weren't there). +follows it once its operator pins that checkpoint ([`checkpoints.md`](checkpoints.md), +[Nodes that weren't there](checkpoints.md#nodes-that-werent-there)). ## Without remakes -- cgit v1.3.1