X-Git-Url: http://git.chise.org/gitweb/?a=blobdiff_plain;f=info%2Flispref.info-3;h=837bb6019ef0c1cccaad6904351ae94787daeac4;hb=2800b582091b18fec928d76fc36c0b4201c55a19;hp=bb82c59c40bc1b5a99367b00328d7a09671c2cb2;hpb=afa9772e3fcbb4e80e3e4cfd1a40b4fccc6d08b8;p=chise%2Fxemacs-chise.git

diff --git a/info/lispref.info-3 b/info/lispref.info-3
index bb82c59..837bb60 100644
--- a/info/lispref.info-3
+++ b/info/lispref.info-3
@@ -71,7 +71,7 @@ confoundance disease".  In particular, many functions such as `eq',
 `old-memq', etc.) that pretend like characters are integers are the
 same.  Byte code compiled under any version 19 Emacs will have all such
 functions mapped to their `old-' equivalents when the byte code is read
-into XEmacs 20.  This is to preserve compatibility - Emacs 19 converts
+into XEmacs 20.  This is to preserve compatibility--Emacs 19 converts
 all constant characters to the equivalent integer during
 byte-compilation, and thus there is no other way to preserve byte-code
 compatibility even if the code has specifically been written with the
@@ -81,7 +81,7 @@ distinction between characters and integers in mind.
 code".  For example, the character `A' is represented as the
 integer 65, following the standard ASCII representation of characters.
 If XEmacs was not compiled with MULE support, the range of this integer
-will always be 0 to 255 - eight bits, or one byte. (Integers outside
+will always be 0 to 255--eight bits, or one byte. (Integers outside
 this range are accepted but silently truncated; however, you should
 most decidedly _not_ rely on this, because it will not work under
 XEmacs with MULE support.)  When MULE support is present, the range of