aboutsummaryrefslogtreecommitdiffstats
path: root/docs/guides/federation/remakes.md
diff options
context:
space:
mode:
Diffstat (limited to 'docs/guides/federation/remakes.md')
-rw-r--r--docs/guides/federation/remakes.md7
1 files changed, 4 insertions, 3 deletions
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