A tag write past the limit says tag: no space: over 4096 bytes, which 9ns maps to ENOSPC as the docs say

The tree answers ENOSPC, but through a mount 9ns maps the words, and tag: over 4096 bytes carried none it knows, so a shell saw EIO. The words now hold no space; docs/fs.md says ENOSPC again.

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

1 files changed, 3 insertions, 3 deletions

diff --git a/docs/fs.md b/docs/fs.md
index 2e2f1453..06fa1406 100644
--- a/docs/fs.md
+++ b/docs/fs.md
@@ -134,8 +134,8 @@ never a C library string. Through 9ns the kernel sees an errno 9ns reads
 from those words (cloud9 `9ns/src/nine.zig`, `enameToErrno`): `control
 message`, `invalid` or `bad ` is EINVAL (malformed input); `no such`, `not
 found` ENOENT; `in use` EBUSY; `no space` ENOSPC; `denied` EACCES; anything
-else, such as `no match for regexp`, `address out of range`, `Modified` or
-`tag: over 4096 bytes`, EIO. The `err` record has the words; a shell sees
+else, such as `no match for regexp`, `address out of range` or `Modified`,
+EIO. The `err` record has the words; a shell sees
 only the errno, most often `Invalid argument` or `Input/output error`.
 
 Not failures: a look that finds nothing (it answers nothing and logs one
@@ -320,7 +320,7 @@ blank matters; `echo` would start a second line). A pane tag may hold
 several lines; a column or workspace tag is one, a newline written into it
 becoming a space. Control characters other than tab, DEL, C1 controls and
 non-UTF-8 bytes are refused (`invalid tag text`). The editable text is at
-most 4096 bytes (`tag: over 4096 bytes`, EIO). A clear is an ordinary edit
+most 4096 bytes (`tag: no space: over 4096 bytes`, ENOSPC). A clear is an ordinary edit
 and `u` in the tag undoes it. [tags.md](tags.md) covers tags on screen.
 
 ## Panes