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/topology/mod.rs b/src/swarm/topology/mod.rs
index 2d812e5..8fae0ed 100644
--- a/src/swarm/topology/mod.rs
+++ b/src/swarm/topology/mod.rs
@@ -41,8 +41,7 @@ use graph::*;
 pub(crate) use graph::{RingAndPairs, pair_key, pair_score};
 
 /// How members' neighbours are chosen: the graph above (`RingAndPairs`) is one way;
-/// others can be tried against it in the benchmark (`docs/future-work.md`, Swappable
-/// topology and dissemination). One per swarm: a node's neighbours must count it as
+/// others can be tried against it in the benchmark. One per swarm: a node's neighbours must count it as
 /// theirs.
 ///
 /// A topology either computes a graph every node shares (`graph`: the same inputs give