2 files changed, 2 insertions, 4 deletions

diff --git a/docs/MESHBAY_DESIGN.md b/docs/MESHBAY_DESIGN.md
index e145ed4..49bd99b 100644
--- a/docs/MESHBAY_DESIGN.md
+++ b/docs/MESHBAY_DESIGN.md
@@ -1544,8 +1544,7 @@ Several roots may be writable and none need be — a fully read-only group is va
 
 **What widens the sharing is decided on the node's own machine.** Adding a root,
 hosting a group over a directory, and switching `writable` or `removable` go through
-the loopback API (in the desktop application, behind a native dialog for anything
-that shares a folder or opens one to writes) or the CLI — never over MNP, since 6.0.
+the loopback API (the desktop application) or the CLI — never over MNP, since 6.0.
 A signed op proves that the operator's key signed, not that they meant it: in a
 browser that key is driven by code the hub serves (T3), and in the desktop
 application by a renderer that parses content from nodes. Either could otherwise
diff --git a/docs/MESHBAY_NODE_PROTOCOL.md b/docs/MESHBAY_NODE_PROTOCOL.md
index d03b7eb..cdcc2c0 100644
--- a/docs/MESHBAY_NODE_PROTOCOL.md
+++ b/docs/MESHBAY_NODE_PROTOCOL.md
@@ -1183,8 +1183,7 @@ drop box", which is the ordinary arrangement.
 **Nothing in this table widens what the node shares**, and that is the design too.
 Adding a directory to a group, hosting a new group over a directory, and switching
 a root's `writable` or `removable` flag are done on the node's own machine — the
-desktop application over the loopback API, which asks in a native dialog before it
-shares a folder or opens one to writes, or the CLI — and never over MNP. Until 6.0
+desktop application over the loopback API, or the CLI — and never over MNP. Until 6.0
 they were the signed ops `root_add`, `group_attach` and `root_update`. A signature
 proves that the operator's key signed, not that the operator meant it: in a browser
 that key is driven by code the hub serves (T3), and in the desktop application by a