--- gforth/Attic/gforth.ds	1995/01/24 17:31:22	1.7
+++ gforth/Attic/gforth.ds	1995/02/22 18:40:15	1.11
@@ -428,7 +428,7 @@ unwary (e.g., floating point addition is
 for the wary. You should not use them unless you know what you are doing
 or you don't care that the results you get are totally bogus. If you
 want to learn about the problems of floating point numbers (and how to
-avoid them), you might start with @cite{David (?) Goldberg, What Every
+avoid them), you might start with @cite{David Goldberg, What Every
 Computer Scientist Should Know About Floating-Point Arithmetic, ACM
 Computing Surveys 23(1):5@minus{}48, March 1991}.
 
@@ -607,6 +607,9 @@ The standard guarantees that addresses r
 are cell-aligned; in addition, gforth guarantees that these addresses
 are aligned for all purposes.
 
+Note that the standard defines a word @code{char}, which has nothing to
+do with address arithmetic.
+
 doc-chars
 doc-char+
 doc-cells
@@ -625,6 +628,10 @@ doc-dfloats
 doc-dfloat+
 doc-dfalign
 doc-dfaligned
+doc-maxalign
+doc-maxaligned
+doc-cfalign
+doc-cfaligned
 doc-address-unit-bits
 
 @node Memory block access,  , Address arithmetic, Memory access
@@ -878,7 +885,7 @@ doc-next
 doc-leave
 doc-?leave
 doc-unloop
-doc-undo
+doc-done
 
 The standard does not allow using @code{cs-pick} and @code{cs-roll} on
 @i{do-sys}. Our system allows it, but it's your job to ensure that for
@@ -1625,10 +1632,11 @@ GForth comes with @file{gforth.el}, an i
 @file{forth.el} by Goran Rydqvist (icluded in the TILE package). The
 improvements are a better (but still not perfect) handling of
 indentation. I have also added comment paragraph filling (@kbd{M-q}),
-commenting (@kbd{C-x \}) and uncommenting (@kbd{C-x |}) regions and
-removing debugging tracers (@kbd{C-x ~}). I left the stuff I do not use
-alone, even though some of it only makes sense for TILE. To get a
-description of these features, enter Forth mode and type @kbd{C-h m}.
+commenting (@kbd{C-x \}) and uncommenting (@kbd{C-u C-x \}) regions and
+removing debugging tracers (@kbd{C-x ~}, @pxref{Debugging}). I left the
+stuff I do not use alone, even though some of it only makes sense for
+TILE. To get a description of these features, enter Forth mode and type
+@kbd{C-h m}.
 
 In addition, GForth supports Emacs quite well: The source code locations
 given in error messages, debugging output (from @code{~~}) and failed