The 9P docs find the mount through $NINE_MOUNT, and then the editor is just files

1 files changed, 4 insertions, 2 deletions

diff --git a/docs/fs.md b/docs/fs.md
index e93704a6..0b248037 100644
--- a/docs/fs.md
+++ b/docs/fs.md
@@ -62,8 +62,10 @@ private namespace:
 A `9ns --unix` mount lives in the private namespace of the command it runs,
 and nothing outside that command sees it. The mount everyone on the machine
 shares is the registry one, `9ns --mntgen` (default `/mnt/9p`): every running
-editor posts itself there, so `/mnt/9p/pardes/<pid>/` is that editor's tree
-for any process. A new pane made through `pane/new` is a scratch named
+editor posts itself there, so `$NINE_MOUNT/pardes/<pid>/` is that editor's tree
+for any process. 9ns exports `$NINE_MOUNT` to everything it starts, so a
+script checks that variable to know the mount is there, and takes `<pid>` from
+the name of `$PARDES_9P` (`pardes-9p-<pid>.sock`). A new pane made through `pane/new` is a scratch named
 `<dir>/+New` until it is given a name, and closing a column's last pane
 leaves such a `+New` in its place (`Delcol` closes the column).