The docs match what Save to a directory not ours and an image's tag say

A Save refused by the disk reads as EACCES through a mount (its words say denied), not EIO; an image's tag starts palette:commodore ascii:on by default.

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

1 files changed, 3 insertions, 2 deletions

diff --git a/docs/fs.md b/docs/fs.md
index b7d1d27e..ca24034d 100644
--- a/docs/fs.md
+++ b/docs/fs.md
@@ -303,7 +303,8 @@ lines before a failing one have taken effect and those after it never run,
 which is what acme's ctl loop does (editors/acme/xfid.c:600-790). An error
 that only happens as the editor performs what a line asked for -- a `Save`
 whose disk write fails -- fails the write too, once the editor has tried
-(`Save /root/x.txt: access denied`, EIO), and changes nothing: a scratch
+(`Save /root/x.txt: access denied`, which 9ns reads as EACCES, a shell's
+`Permission denied`), and changes nothing: a scratch
 keeps its name and stays a scratch, a clean file stays clean, a dirty one
 dirty. Like any write, a ctl write answers once the editor has
 performed what it asked for (a save written, a shell started). A click on
@@ -793,7 +794,7 @@ a command pane ends in its own time, told by its `exit` record.
 `tag` reads the whole tag as the pane shows it: the computed path or PDF
 page (no mark for unsaved text: the grip shows that, and `dirty` says it),
 then the text you may edit. An image's tag begins with its mode words, not
-its path: `img petscii:off palette:terminal ascii:off <path>`, the modes
+its path: `img petscii:off palette:commodore ascii:on <path>` by default, the modes
 it is drawn in, then the file. A write appends to that text,
 newlines included, and a tag with more than one line takes a row per line on
 screen; truncating `tag` clears it, as acme's `cleartag` does -- the default