docs: what is postponed or rejected stays in its own two files

Docs and comments outside future-work.md and review-rejections.md say what the code
does, and point nowhere else for what it doesn't: the architecture page's map, the
transports' forwarders, keys with `/`, a strict swarm's registry, trust.md's "Not yet"
(now saying what isn't protected, in a sentence), the topology bench, and the comments
of the change benchmarks, capabilities' grantor, tokens, dissemination, refusals and
topology.

1 files changed, 2 insertions, 2 deletions

diff --git a/src/document/bench.rs b/src/document/bench.rs
index 39a8dc7..db76ccc 100644
--- a/src/document/bench.rs
+++ b/src/document/bench.rs
@@ -8,7 +8,7 @@
 //! ways on the same input.
 //!
 //! `change_signatures`: what signing every change by its committer's node key would
-//! cost (`future-work.md`, Write protection by checking changes): an Ed25519 signature
+//! cost: an Ed25519 signature
 //! over a change's hash, made on every commit, checked on every change received.
 //! Against what the node does anyway on the same input: a local write, a sync message
 //! of many changes received (catching up), and a document of many changes loaded
@@ -20,7 +20,7 @@
 //! same input (`changes::misplaced_author`).
 //!
 //! `change_paths`: what knowing every received change's paths would cost, to judge it by
-//! rules by path (`future-work.md`, Write protection by checking changes): each
+//! rules by path: each
 //! change's operations decoded, and each object they name followed up to the root as
 //! the change left it (`store::changed_by`, so every node finds the same paths). Against
 //! receiving a sync message of many changes and loading a document of many changes, as