diff --git a/04-ISSUES/340-an-agent-can-plant-a-hook-in-every-agent-session-on-the-mesh/00-report.md b/04-ISSUES/340-an-agent-can-plant-a-hook-in-every-agent-session-on-the-mesh/00-report.md
index 89beb87e..7b0a161f 100644
--- a/04-ISSUES/340-an-agent-can-plant-a-hook-in-every-agent-session-on-the-mesh/00-report.md
+++ b/04-ISSUES/340-an-agent-can-plant-a-hook-in-every-agent-session-on-the-mesh/00-report.md
@@ -122,9 +122,9 @@ at the controller's terminal. An agent's attempt through any mesh tool is refuse
   some, of each kind, is refused through the tools and the import tool, and lands when set in the module's
   settings at the terminal. The home scope is refused for any node but the one serving the call, and there
   wherever the home is the operator's own; it is taken only where the home is an agent account's own, and a
-  home item on the bus is never placed in the operator's home. So is a new `url` on a
-  module whose mergeable runtime configuration starts empty, while a file marked `"trusted": false` stays the
-  verb's. The layer is
+  home item on the bus is never placed in the operator's home. Through the settings verb, a new `url` on a
+  module whose mergeable runtime configuration starts empty is refused too, while a file marked
+  `"trusted": false` stays the verb's. The layer is
   unchanged after every refusal. At the terminal the same is taken. These tests fail on the commit before
   the fix.
 - **Live, after both are taken:** the calls in the diagnosis's last section are each refused, and