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, 1 insertions, 1 deletions

diff --git a/docs/config.md b/docs/config.md
index b5ec1aa5..1af696be 100644
--- a/docs/config.md
+++ b/docs/config.md
@@ -49,7 +49,7 @@ opens the file. Shell follows the same requested/effective/pending model as
 Font. `Default shell` is the one used while no `Shell` is set: `$SHELL`, the
 user's login shell, else `/bin/sh` (also when `$SHELL` names nothing
 executable); an explicit `Shell` overrides it. `Shell <name or path>` is
-refused unless it names an executable file (`Shell: no shell "x" (...)`, or
+refused unless it names an executable file (`Shell: shell "x" not found (...)`, or
 `Shell: not a shell: /etc is a directory`; a bare name is looked for in the
 usual bin directories), as `Tty <shell>` is, and a
 bare `Shell` goes back to the default. The root ctl reads `Shell <the one the