Builtins are written by name: each chapter and the tutor define Look and Exec once and then say Look and Exec; the cheatsheet draws every mouse button as its icon; one-button clicks (Alt is B2, Super is B3) are in the guide and cheatsheet; building says how to send patches to the list

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

1 files changed, 4 insertions, 4 deletions

diff --git a/docs/typ/setup.typ b/docs/typ/setup.typ
index 7d2970f8..cc5b5552 100644
--- a/docs/typ/setup.typ
+++ b/docs/typ/setup.typ
@@ -20,7 +20,7 @@ virtual filesystem as files:
 #cmd("9ns --mntgen -- pardes-gui")
 
 A desktop launcher that still starts pardes without 9ns or `/dev/fuse`
-(absolute paths: `Exec` takes a `$` only escaped, and a desktop `PATH` may
+(absolute paths: the `Exec=` line takes a `$` only escaped, and a desktop `PATH` may
 lack `~/.local/bin`):
 
 ```
@@ -62,16 +62,16 @@ fi
 = A pager <pager>
 
 `pardes -` reads its standard input into the directory's one `+Pager`
-pane, colours kept, and returns. With `Pager pardes` (the default) a
+pane, colours kept, and returns. With #word("Pager") `pardes` (the default) a
 terminal's shell gets `PAGER`, `GIT_PAGER` and `SYSTEMD_PAGER` set to it,
 and `SYSTEMD_PAGERSECURE=0`, each only where your environment does not set
 it. So `git log`, `journalctl` or `man` output arrives as a pane to search
 and click in, a diff drawn as one; command panes page through `cat`. `man`
 reads `MANPAGER` first, which pardes never sets. Any pager of your own wins;
-`Pager off` in the startup file keeps them all yours, for terminals started
+#word("Pager") `off` in the startup file keeps them all yours, for terminals started
 after it. git colours what it pages by default (`color.pager`); ask other
 programs for colour outright (`ls --color=always | pardes -`), and put
-`PagerColor off` in the init file for plain text.
+#word("PagerColor") `off` in the init file for plain text.
 
 = yazi in a terminal pane <yazi>