Use input-decode-map in the manuals

* doc/misc/edt.texi (Changes):
* doc/emacs/custom.texi (Terminal Init): Use input-decode-map
instead of local-function-key-map, according to Stefan Monnier.

2 files changed, 2 insertions, 3 deletions

diff --git a/doc/emacs/custom.texi b/doc/emacs/custom.texi
index aba96442767..adea9351ea9 100644
--- a/doc/emacs/custom.texi
+++ b/doc/emacs/custom.texi
@@ -2616,8 +2616,7 @@ kept.
 
   The usual purpose of the terminal-specific library is to map the
 escape sequences used by the terminal's function keys onto more
-meaningful names, using @code{input-decode-map} (or
-@code{local-function-key-map} before it).  See the file
+meaningful names, using @code{input-decode-map}.  See the file
 @file{term/lk201.el} for an example of how this is done.  Many function
 keys are mapped automatically according to the information in the
 Termcap data base; the terminal-specific library needs to map only the
diff --git a/doc/misc/edt.texi b/doc/misc/edt.texi
index 73ec47d144a..c34efb6937a 100644
--- a/doc/misc/edt.texi
+++ b/doc/misc/edt.texi
@@ -190,7 +190,7 @@ key sequence, providing the @acronym{ASCII} key sequence prefix is
 already known by Emacs to be a prefix.  As a result of providing this
 support, some terminal/keyboard/window system configurations, which
 don't have a complete set of sensible function key bindings built into
-Emacs in @code{local-function-key-map}, can still be configured for use with
+Emacs in @code{input-decode-map}, can still be configured for use with
 EDT Emulation.  (Note: In a few rare circumstances this does not work
 properly.  In particular, it does not work if a subset of the leading
 @acronym{ASCII} characters in a key sequence are recognized by Emacs as