The docs call pardes's scripting interface a virtual filesystem, served over 9P, and the guide opens on look and execute as the core idea

Co-Authored-By: Claude Opus 5.5 <[email protected]>

1 files changed, 3 insertions, 3 deletions

diff --git a/docs/typ/reference.typ b/docs/typ/reference.typ
index 5ef871a3..afbbd899 100644
--- a/docs/typ/reference.typ
+++ b/docs/typ/reference.typ
@@ -1,11 +1,11 @@
-// The reference: every file the 9P control filesystem serves, what it
+// The reference: every file the virtual filesystem serves over 9P, what it
 // does, how it fails, and the limits. How pardes behaves on screen is the
 // guide's; recipes and traps are scripting's; how a mount cuts writes and
 // the listeners are building's.
 #import "style.typ": key, keys, btn, chord, word, tag, addr, file, cmd, doc, pairs
 
-Every native session serves 9P2000 (not .u, not .L) as a control
-filesystem, in acme's manner: panes, columns, tags and the session are
+Every native session is a virtual filesystem, served as 9P2000 (not .u,
+not .L), in acme's manner: panes, columns, tags and the session are
 files. Paths here are the served ones (#file("/pane/2/body")); through a
 mount they sit under the session's directory (`$m`; #doc("scripting", section: "find-the-session")
 says how to find it). The served #file("/README") is a