--- a/man/lispref/keymaps.texi	Mon Aug 13 11:12:06 2007 +0200
+++ b/man/lispref/keymaps.texi	Mon Aug 13 11:13:30 2007 +0200
@@ -235,7 +235,7 @@
 @section Key Sequences
 @cindex key sequences
 
-  Contrary to popular belief, the world is not @sc{ASCII}.  When running
+  Contrary to popular belief, the world is not @sc{ascii}.  When running
 under a window manager, XEmacs can tell the difference between, for
 example, the keystrokes @kbd{control-h}, @kbd{control-shift-h}, and
 @kbd{backspace}.  You can, in fact, bind different commands to each of
@@ -246,8 +246,8 @@
 A @dfn{keysym} is what is printed on the keys on your keyboard.
 
   A keysym may be represented by a symbol, or (if and only if it is
-equivalent to an @sc{ASCII} character in the range 32 - 255) by a
-character or its equivalent @sc{ASCII} code.  The @kbd{A} key may be
+equivalent to an @sc{ascii} character in the range 32 - 255) by a
+character or its equivalent @sc{ascii} code.  The @kbd{A} key may be
 represented by the symbol @code{A}, the character @code{?A}, or by the
 number 65.  The @kbd{break} key may be represented only by the symbol
 @code{break}.
@@ -262,12 +262,12 @@
 @code{next-command-event} and @code{read-key-sequence} functions.
 
   Note that in this context, the keystroke @kbd{control-b} is @emph{not}
-represented by the number 2 (the @sc{ASCII} code for @samp{^B}) or the
+represented by the number 2 (the @sc{ascii} code for @samp{^B}) or the
 character @code{?\^B}.  See below.
 
   The @key{SHIFT} modifier is somewhat of a special case.  You should
 not (and cannot) use @code{(meta shift a)} to mean @code{(meta A)},
-since for characters that have @sc{ASCII} equivalents, the state of the
+since for characters that have @sc{ascii} equivalents, the state of the
 shift key is implicit in the keysym (@samp{a} vs. @samp{A}).  You also
 cannot say @code{(shift =)} to mean @code{+}, as that sort of thing
 varies from keyboard to keyboard.  The @key{SHIFT} modifier is for use
@@ -279,23 +279,23 @@
 That is, the @kbd{A} keystroke is represented by all of these forms:
 
 @example
-	A	?A	65	(A)	(?A)	(65)
-	[A]	[?A]	[65]	[(A)]	[(?A)]	[(65)]
+        A       ?A      65      (A)     (?A)    (65)
+        [A]     [?A]    [65]    [(A)]   [(?A)]  [(65)]
 @end example
-	   
+           
 the @kbd{control-a} keystroke is represented by these forms:
 
 @example
-	(control A)	(control ?A)	(control 65)
-	[(control A)]	[(control ?A)]	[(control 65)]
+        (control A)     (control ?A)    (control 65)
+        [(control A)]   [(control ?A)]  [(control 65)]
 @end example
 
 the key sequence @kbd{control-c control-a} is represented by these
 forms:
 
 @example
-	[(control c) (control a)]	[(control ?c) (control ?a)]
-	[(control 99) (control 65)]	etc.
+        [(control c) (control a)]       [(control ?c) (control ?a)]
+        [(control 99) (control 65)]     etc.
 @end example
 
   Mouse button clicks work just like keypresses: @code{(control
@@ -311,38 +311,38 @@
 
   For backward compatibility, a key sequence may also be represented by
 a string.  In this case, it represents the key sequence(s) that would
-produce that sequence of @sc{ASCII} characters in a purely @sc{ASCII}
-world.  For example, a string containing the @sc{ASCII} backspace
+produce that sequence of @sc{ascii} characters in a purely @sc{ascii}
+world.  For example, a string containing the @sc{ascii} backspace
 character, @code{"\^H"}, would represent two key sequences:
 @code{(control h)} and @code{backspace}.  Binding a command to this will
 actually bind both of those key sequences.  Likewise for the following
 pairs:
 
 @example
-		control h	backspace
-		control i   	tab
-		control m   	return
-		control j   	linefeed
-		control [   	escape
-		control @@	control space
+                control h       backspace
+                control i       tab
+                control m       return
+                control j       linefeed
+                control [       escape
+                control @@      control space
 @end example
 
   After binding a command to two key sequences with a form like
 
 @example
-	(define-key global-map "\^X\^I" 'command-1)
+        (define-key global-map "\^X\^I" 'command-1)
 @end example
 
 @noindent
 it is possible to redefine only one of those sequences like so:
 
 @example
-	(define-key global-map [(control x) (control i)] 'command-2)
-	(define-key global-map [(control x) tab] 'command-3)
+        (define-key global-map [(control x) (control i)] 'command-2)
+        (define-key global-map [(control x) tab] 'command-3)
 @end example
 
   Of course, all of this applies only when running under a window
-system.  If you're talking to XEmacs through a @sc{TTY} connection, you
+system.  If you're talking to XEmacs through a @sc{tty} connection, you
 don't get any of these features.
 
 @defun event-matches-key-specifier-p event key-specifier
@@ -614,22 +614,22 @@
 @result{} #<keymap lisp-interaction-mode-map 5 entries 0x558>
 (describe-bindings-internal (current-local-map))
 @result{}  ; @r{Inserted into the buffer:}
-backspace	backward-delete-char-untabify
-linefeed	eval-print-last-sexp
-delete		delete-char
-C-j		eval-print-last-sexp
-C-x		<< Prefix Command >>
-M-tab		lisp-complete-symbol
-M-;		lisp-indent-for-comment
-M-C-i		lisp-complete-symbol
-M-C-q		indent-sexp
-M-C-x		eval-defun
-Alt-backspace	backward-kill-sexp
-Alt-delete	kill-sexp
+backspace       backward-delete-char-untabify
+linefeed        eval-print-last-sexp
+delete          delete-char
+C-j             eval-print-last-sexp
+C-x             << Prefix Command >>
+M-tab           lisp-complete-symbol
+M-;             lisp-indent-for-comment
+M-C-i           lisp-complete-symbol
+M-C-q           indent-sexp
+M-C-x           eval-defun
+Alt-backspace   backward-kill-sexp
+Alt-delete      kill-sexp
 @end group
 
 @group
-C-x x		edebug-defun
+C-x x           edebug-defun
 @end group
 @end example
 @end defun
@@ -973,14 +973,14 @@
 translating a two-character sequence to a meta character so it can be
 looked up in a keymap.  For useful results, the value should be a prefix
 event (@pxref{Prefix Keys}).  The default value is @code{?\^[} (integer
-27), which is the @sc{ASCII} character usually produced by the @key{ESC}
+27), which is the @sc{ascii} character usually produced by the @key{ESC}
 key.
 
   As long as the value of @code{meta-prefix-char} remains @code{?\^[},
 key lookup translates @kbd{@key{ESC} b} into @kbd{M-b}, which is
 normally defined as the @code{backward-word} command.  However, if you
 set @code{meta-prefix-char} to @code{?\^X} (i.e. the keystroke
-@kbd{C-x}) or its equivalent @sc{ASCII} code @code{24}, then XEmacs will
+@kbd{C-x}) or its equivalent @sc{ascii} code @code{24}, then XEmacs will
 translate @kbd{C-x b} (whose standard binding is the
 @code{switch-to-buffer} command) into @kbd{M-b}.
 
@@ -1503,7 +1503,7 @@
 string representing the first key sequence found, rather than a list of
 all possible key sequences.  If @var{firstonly} is @code{t}, then the
 value is the first key sequence, except that key sequences consisting
-entirely of @sc{ASCII} characters (or meta variants of @sc{ASCII}
+entirely of @sc{ascii} characters (or meta variants of @sc{ascii}
 characters) are preferred to all other key sequences.
 @end ignore
 
@@ -1546,13 +1546,13 @@
 If @var{prefix} is non-@code{nil}, it should be a prefix key; then the
 listing includes only keys that start with @var{prefix}.
 
-When several characters with consecutive @sc{ASCII} codes have the
+When several characters with consecutive @sc{ascii} codes have the
 same definition, they are shown together, as
 @samp{@var{firstchar}..@var{lastchar}}.  In this instance, you need to
-know the @sc{ASCII} codes to understand which characters this means.
+know the @sc{ascii} codes to understand which characters this means.
 For example, in the default global map, the characters @samp{@key{SPC}
-..@: ~} are described by a single line.  @key{SPC} is @sc{ASCII} 32,
-@kbd{~} is @sc{ASCII} 126, and the characters between them include all
+..@: ~} are described by a single line.  @key{SPC} is @sc{ascii} 32,
+@kbd{~} is @sc{ascii} 126, and the characters between them include all
 the normal printing characters, (e.g., letters, digits, punctuation,
 etc.@:); all these characters are bound to @code{self-insert-command}.