Not-found failures say it once, in plain words: grep: pattern not found, callers not found

The ENOENT that 9ns reads from a failure's words came from a tacked-on suffix, grep: no match, not found, definition: nothing found, not found, no shell "x", not found. They now say it once: grep: pattern not found, find: name not found, Callers: callers not found, definition: not found, shell "x" not found (...).

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

1 files changed, 2 insertions, 2 deletions

diff --git a/docs/fs.md b/docs/fs.md
index 4b772c18..b7d1d27e 100644
--- a/docs/fs.md
+++ b/docs/fs.md
@@ -258,7 +258,7 @@ back changes nothing; a setting the frontend cannot show (`Lift`,
 (EINVAL: a request this build cannot take), and so is a builtin only the
 GUI has (`Fonts`), written to an `exec` too, where it would otherwise run as
 a shell command; a `Shell` or `Tty` naming no
-shell says `no shell "x", not found` (ENOENT); a `DumpDir` whose last
+shell says `shell "x" not found` (ENOENT); a `DumpDir` whose last
 directory is missing has it made at the Dump, and one further up missing
 says `Dump <path>: no such directory` (ENOENT), one that is no directory
 (`/dev/null`) `Dump /dev/null/pardes-<time>.zon: /dev/null is not a
@@ -773,7 +773,7 @@ name (ENOENT for a pane, file or directory gone -- `look .` from a pane
 whose directory is gone says `look: <dir>: no such directory`, and a
 `./zz.txt` or `../x` that is not there `look: ./zz.txt: no such file`, while a
 plain `zz.txt` is looked for as text, a miss logged as any look's -- and for a
-Find or Grep that finds nothing, `grep: no match, not found`; Grep walks
+Find or Grep that finds nothing, `grep: pattern not found`; Grep walks
 every pane's directory on this host, passing over panes of the served
 tree (`/virtual/`, a peer's `/n/<name>/`) and directories not there,
 so none of them spoils the rest; Find, Grep and a language server's lists