Contents in 1999-06-04-13 of release-21-2.

[chise/xemacs-chise.git.1] / man / internals / internals.texi

diff --git a/man/internals/internals.texi b/man/internals/internals.texi
index d9043c3..2366573 100644 (file)
--- a/man/internals/internals.texi
+++ b/man/internals/internals.texi
@@ -5,6 +5,10 @@
 @c %**end of header
 
 @ifinfo
+@dircategory XEmacs Editor
+@direntry
+* Internals: (internals).      XEmacs Internals Manual.
+@end direntry
 
 Copyright @copyright{} 1992 - 1996 Ben Wing.
 Copyright @copyright{} 1996, 1997 Sun Microsystems.
@@ -1458,7 +1462,7 @@ converts to an integer whose value is 17297.
 1.983e-4
 @end example
 
-converts to a float whose value is 1983.23e-4, or .0001983.
+converts to a float whose value is 1.983e-4, or .0001983.
 
 @example
 ?b
@@ -2676,7 +2680,7 @@ Header files should @emph{not} include @code{<config.h>} and
 use it to do so.
 
 @item
-If the header uses @code{INLINE}, either directly or though
+If the header uses @code{INLINE}, either directly or through
 @code{DECLARE_LRECORD}, then it must be added to @file{inline.c}'s
 includes.
 
@@ -2968,7 +2972,7 @@ low-level macros.
 As a general rule, all typedefs should go into the typedefs section of
 @file{lisp.h} rather than into a module-specific header file even if the
 structure is defined elsewhere.  This allows function prototypes that
-use the typedef to placed into other header files.  Forward structure
+use the typedef to be placed into other header files.  Forward structure
 declarations (i.e. a simple declaration like @code{struct foo;} where
 the structure itself is defined elsewhere) should be placed into the
 typedefs section as necessary.