summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorEli Zaretskii <eliz@gnu.org>2023-03-18 15:54:35 +0200
committerEli Zaretskii <eliz@gnu.org>2023-03-18 15:54:35 +0200
commite388a77cf0b1ccae51c27303d2ab640cbc552015 (patch)
tree69d9e139787510308583b777940ebc7ba2c8f87b
parent33a26703689298819528bae689cd9a031c90b253 (diff)
downloademacs-e388a77cf0b1ccae51c27303d2ab640cbc552015.tar.gz
; Minor copyedits of recent changes in ELisp reference manual
* doc/lispref/keymaps.texi (Changing Key Bindings): Fix wording and markup.
-rw-r--r--doc/lispref/keymaps.texi6
1 files changed, 3 insertions, 3 deletions
diff --git a/doc/lispref/keymaps.texi b/doc/lispref/keymaps.texi
index aab2fe58255..c17c8a2dc3f 100644
--- a/doc/lispref/keymaps.texi
+++ b/doc/lispref/keymaps.texi
@@ -1445,10 +1445,10 @@ does matter for menu keymaps (@pxref{Menu Keymaps}).
This function is the inverse of @code{keymap-set}, it unsets the
binding for @var{key} in @var{keymap}, which is the same as setting
the binding to @code{nil}. In order to instead remove the binding
-completely, specify @var{remove} as non-nil. This only makes a
-difference if @var{keymap} has a parent keymap. When unsetting a key
+completely, specify @var{remove} as non-@code{nil}. This only makes a
+difference if @var{keymap} has a parent keymap: if you just unset a key
in a child map, it will still shadow the same key in the parent
-keymap. Removing the binding will allow the key in the parent keymap
+keymap; using @var{remove} instead will allow the key in the parent keymap
to be used.
@end defun