feat: rewrite docs

spec/06-anchors.md

@@ -30,7 +30,7 @@ On the web the node ID is the fragment: `…/smithlab/cornell1995second#k3m9q2a`
 ## 6.2 The anchor
 
 An anchor, `scienting-anchor/1`, is the stored form of a pinned address, with enough context to survive change.
-It is what Lode extracts, annotations, dataset values and draft citations use.
+It is what extracts, annotations, dataset values and draft citations use.
 
 | Property | Required | Holds |
 | --- | --- | --- |
@@ -101,7 +101,7 @@ This finds a value again even in a table with multi-level headers or row labels
 The result is `{result, node, node_hash?, span?, drift?, via?, reason?}`: the outcome, the live node and its `node_hash`, the new span, the drift of a `changed-below` result, the IDs followed, and a reason for `stale` and relabel results.
 A `moved` or `reattached` anchor is re-pinned to the live node, and the move is recorded.
 
-Checks are stricter than readers: a Lode extract is a span or leaf anchor and never accepts `changed-below`, because a check is about exact words.
+Checks are stricter than readers: an extract is a span or leaf anchor and never accepts `changed-below`, because a check is about exact words.
 `resolve.jsonl` resolves seventeen anchors made at revision 0 against `fixtures/packages/hale2026harmonic` at revision 12, with every outcome.
 
 ## 6.6 Drift