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, 1 insertions, 2 deletions

diff --git a/src/swarm/dissemination.rs b/src/swarm/dissemination.rs
index 9763449..4c15d0f 100644
--- a/src/swarm/dissemination.rs
+++ b/src/swarm/dissemination.rs
@@ -1,8 +1,7 @@
 //! How a change reaches every member: whom a node sends a writer's changes to at once,
 //! and whom it leaves to the announcement rounds (`swarm::relay`, which repair what it
 //! misses: announcements, pulls, the slow round). Writers' trees (`swarm::tree`) are
-//! one way; others can be tried against them in the benchmark (`docs/future-work.md`,
-//! Swappable topology and dissemination). One per swarm: a node's part in passing a
+//! one way; others can be tried against them in the benchmark. One per swarm: a node's part in passing a
 //! change on is worked out by itself and by its neighbours, and must agree.
 //!
 //! What every way keeps: the base underneath, pairs of neighbours syncing with