* loading.texi (Loading Non-ASCII): Multibyte sessions no longer exist.

diff --git a/doc/lispref/ChangeLog b/doc/lispref/ChangeLog
index a64c4386e331bfdc13d3c6efdd45d8dafb997d2e..b56164669f8ebf032c41a68c6ed961463a0aa1f0 100644 (file)
--- a/doc/lispref/ChangeLog
+++ b/doc/lispref/ChangeLog
@@ -2,6 +2,7 @@
 
        * loading.texi (Loading Non-ASCII): Replace the obsolete "unibyte: t"
        with "coding: raw-text".
+       Concept of multibyte sessions no longer exists.
 
        * files.texi (File Locks): Mention create-lockfiles option.
 

diff --git a/doc/lispref/loading.texi b/doc/lispref/loading.texi
index b012091d4a82ac8bbe1c161402622d520a2c6d13..c585bafbdeba6d1aaaa188f23edac13fe63f4a79 100644 (file)
--- a/doc/lispref/loading.texi
+++ b/doc/lispref/loading.texi
@@ -376,9 +376,8 @@ 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, even in an ordinary multibyte Emacs session.  This can matter
-when making keybindings to non-@acronym{ASCII} characters written as
-@code{?v@var{literal}}.
+unibyte.  This can matter when making keybindings to
+non-@acronym{ASCII} characters written as @code{?v@var{literal}}.
 
 @node Autoload
 @section Autoload