diff --git a/03-DESIGN/01-to-be/27-a-module-requires-the-mesh-resolves.md b/03-DESIGN/01-to-be/27-a-module-requires-the-mesh-resolves.md
index 42dff768..3c7fc3e8 100644
--- a/03-DESIGN/01-to-be/27-a-module-requires-the-mesh-resolves.md
+++ b/03-DESIGN/01-to-be/27-a-module-requires-the-mesh-resolves.md
@@ -228,8 +228,8 @@ both `settings` listings name the shared name as a value's source beside the def
 node. **A shared value reaches no trusted setting** (ADR 0319): a trusted setting may not declare a
 shared name, and registration refuses one that does, so a shared value is never trusted and needs no
 warrant; a trusted setting is set in its own module's layer, on the operator's warrant (ADR 0277) or at
-the terminal, as before. Where a stored manifest still has a trusted reader, the write of that shared
-value is refused naming it, and the trusted setting never reads the value. Whether a shared value is a
+the terminal, as before. A trusted setting that a stored manifest still declares with a shared name
+never reads the shared value, and both listings say why beside it. Whether a shared value is a
 number, a colour or a string waits for the typed-settings work (issues 346 and 410). *How it is
 checked:* the tables in ADR 0309 and ADR 0319.