summaryrefslogtreecommitdiff
path: root/doc/lispref/loading.texi
diff options
context:
space:
mode:
authorStefan Kangas <stefan@marxist.se>2021-12-21 11:19:04 +0100
committerStefan Kangas <stefan@marxist.se>2021-12-21 11:19:04 +0100
commitcf6dc1838af4b3d0604d0848e1ac0d4fbd9c3dbc (patch)
tree49d76ec7b8201a96b5d12e6f5db09d8b93bdf155 /doc/lispref/loading.texi
parente56dd354c751ee67d0012a0209b769246207d74c (diff)
downloademacs-cf6dc1838af4b3d0604d0848e1ac0d4fbd9c3dbc.tar.gz
; Fix spelling; be consistent with "key binding" (Bug#52674)
Diffstat (limited to 'doc/lispref/loading.texi')
-rw-r--r--doc/lispref/loading.texi2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/lispref/loading.texi b/doc/lispref/loading.texi
index ee119445e56..e4cd940ab2e 100644
--- a/doc/lispref/loading.texi
+++ b/doc/lispref/loading.texi
@@ -482,7 +482,7 @@ automatically. However, if this does make a difference, you can force
a particular Lisp file to be interpreted as unibyte by writing
@samp{coding: raw-text} in a local variables section. With
that designator, the file will unconditionally be interpreted as
-unibyte. This can matter when making keybindings to
+unibyte. This can matter when making key bindings to
non-@acronym{ASCII} characters written as @code{?v@var{literal}}.
@node Autoload