--- a/man/ChangeLog	Sun Jan 05 05:13:45 2003 +0000
+++ b/man/ChangeLog	Sun Jan 05 10:54:04 2003 +0000
@@ -2,6 +2,11 @@
 
 	* XEmacs 21.5.10 "burdock" is released.
 
+2003-01-04  Steve Youngs  <youngs@xemacs.org>
+
+	* lispref/mule.texi (Charset Unification): Menu item "Internals"
+	should be "Unification Internals".
+
 2003-01-03  Stephen J. Turnbull  <stephen@xemacs.org>
 
 	* xemacs/startup.texi (Startup Paths): Hierarchy, not package, layout.

--- a/man/lispref/mule.texi	Sun Jan 05 05:13:45 2003 +0000
+++ b/man/lispref/mule.texi	Sun Jan 05 10:54:04 2003 +0000
@@ -2214,7 +2214,7 @@
 * Theory of Operation::         How Unification works.
 * What Unification Cannot Do for You::  Inherent problems of 8-bit charsets.
 * Charsets and Coding Systems:: Reference lists with annotations.
-* Internals::                   Utilities and implementation details.
+* Unification Internals::       Utilities and implementation details.
 @end menu
 
 @node Overview, Usage, Charset Unification, Charset Unification
@@ -2695,10 +2695,10 @@
 different coded character sets into a single buffer.
 
 There are two problems stemming from this design.  First, Mule
-represents the same character in different ways.  Abstractly, ',As(B'
+represents the same character in different ways.  Abstractly, 'ó'
 (LATIN SMALL LETTER O WITH ACUTE) can get represented as
 [latin-iso8859-1 #x73] or as [latin-iso8859-2 #x73].  So what looks like
-',Ass(B' in the display might actually be represented [latin-iso8859-1
+'óó' in the display might actually be represented [latin-iso8859-1
 #x73][latin-iso8859-2 #x73] in the buffer, and saved as [#xF3 ESC - B
 #xF3 ESC - A] in the file.  In some cases this treatment would be
 appropriate (consider HYPHEN, MINUS SIGN, EN DASH, EM DASH, and U+4E00
@@ -2746,7 +2746,7 @@
 The primary purpose of Unification is to fix the problem by giving the
 user the choice to change the representation of all characters to one
 character set and give sensible recommendations based on context.  In
-the ',As(B' example, either ISO 8859/1 or ISO 8859/2 is satisfactory, and
+the 'ó' example, either ISO 8859/1 or ISO 8859/2 is satisfactory, and
 both will be suggested.  In the EURO SIGN example, only ISO 8859/15
 makes sense, and that is what will be recommended.  In both cases, the
 user will be reminded that there are universal encodings available.
@@ -2757,7 +2757,7 @@
 but there are many examples of Latin characters that have different code
 points in different Latin-X sets.)
 
-Note that, in the ',As(B' example, that treating the buffer in this way will
+Note that, in the 'ó' example, that treating the buffer in this way will
 result in a representation such as [latin-iso8859-2
 #x73][latin-iso8859-2 #x73], and the file will be saved as [#xF3 #xF3].
 This is guaranteed to occasionally result in the second problem you