An event record never carries flag 2, as no expansion record follows; flag 1 reads the first word

In acme flag 2 promises a second record with the expanded range, and
acme's libraries read one. F records set it always and a click with no
range known set it, with none following: a library then took the next
event for it. Records here carry the word already, so 2 is never set.
Flag 1 now reads the first word as acme's lookup does, so `Msg hi` is 1.

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

1 files changed, 5 insertions, 3 deletions

diff --git a/docs/fs.md b/docs/fs.md
index 23c87216..5a4ece78 100644
--- a/docs/fs.md
+++ b/docs/fs.md
@@ -771,9 +771,11 @@ files, the editor's own lines), `K` (the keyboard) or `M` (the mouse); the
 action's case says where: `x`/`l` a click executed or looked at in the tag
 (its offsets count the tag's whole text, path included, as `tag` reads),
 `X`/`L` in the body, `I`/`D` text put in or taken out of the body, `i`/`d`
-of the tag. The flag is acme's: 1 the text is a builtin's word, 2 the range
-was expanded from a click (a second record gives the original range), 4 (a
-look) the text is a file name or address, 8 (an exec) chorded: two records
+of the tag. The flag is acme's: 1 the text's first word is a builtin's, 2
+an expansion record follows (acme's look.c:42-43, exec.c:154-157; pardes
+never sends one: a click's record already carries the word it took, its
+range and text, so 2 is never set, whatever the origin), 4 (a look) the
+text is a file name or address, 8 (an exec) chorded: two records
 follow, the argument's text and where it came from, `<file>:#q0,#q1`, each
 with no place of its own: offsets `0 0` and flag 0, `Mx0 0 0 5 hello` (as
 acme's exec.c:182 writes them).