2005-03-31  Stepan Kasal  <address@hidden>

	* doc/automake.texi: Fix a few typos.

Index: doc/automake.texi
===================================================================
RCS file: /cvsroot/automake/automake/doc/automake.texi,v
retrieving revision 1.111
diff -u -r1.111 automake.texi
--- doc/automake.texi	30 Mar 2005 19:50:52 -0000	1.111
+++ doc/automake.texi	31 Mar 2005 08:12:25 -0000
@@ -775,7 +775,7 @@
 @url{http://www.gnu.org/software/texinfo/}.
 
 @item ylwrap
-This program wraps @command{lex} and @command{yacc} and ensures that,
+This program wraps @command{lex} and @command{yacc} and ensures that;
 for instance, multiple @command{yacc} instances can be invoked in a
 single directory in parallel.
 
@@ -2926,7 +2926,7 @@
 Finally, note that a variable using the @samp{nobase_} prefix can
 always be replaced by several variables, one for each destination
 directory (@pxref{Uniform}).  For instance the last example could be
-rewritten as follows.
+rewritten as follows:
 
 @example
 imagesdir = $(pkgdatadir)/images
@@ -8676,7 +8676,7 @@
 
 There are other variables in Automake that follow similar principles
 to allow user options.  For instance Texinfo rules (@pxref{Texinfo})
-uses @code{MAKEINFOFLAGS} and @code{AM_MAKEINFOFLAGS}.  Similarly,
+use @code{MAKEINFOFLAGS} and @code{AM_MAKEINFOFLAGS}.  Similarly,
 DejaGnu tests (@pxref{Tests}) use @code{RUNTESTDEFAULTFLAGS} and
 @code{AM_RUNTESTDEFAULTFLAGS}.  The tags and ctags rules
 (@pxref{Tags}) use @code{ETAGSFLAGS}, @code{AM_ETAGSFLAGS},
@@ -9025,7 +9025,7 @@
 with parallel makes, so you may decide that the recover rule is solely
 to help non-parallel make users and leave things as-is.  Fixing this
 requires some locking mechanism to ensure only one instance of the
-recover rule rebuilds @code{data.stamp}.  One could imagine something
+recover rule rebuilds @file{data.stamp}.  One could imagine something
 along the following lines.
 
 @example
@@ -9048,9 +9048,9 @@
         fi
 @end example
 
-Using a dedicated witness like this is very handy when the list of
-output files is not known beforehand.  As an illustration, consider
-the following rules to compile many @file{*.el} files into
+Using a dedicated witness, like @file{data.stamp}, is very handy when
+the list of output files is not known beforehand.  As an illustration,
+consider the following rules to compile many @file{*.el} files into
 @file{*.elc} files in a single command.  It does not matter how
 @code{ELFILES} is defined (as long as it is not empty: empty targets
 are not accepted by POSIX).
@@ -9599,7 +9599,7 @@
 file from a repository of third-party macros.  Because Autoconf has
 stalled, Automake also becomes a kind of repository for such
 third-party macros, even macros completely unrelated to Automake (for
-instance macros that fixes broken Autoconf macros).
+instance macros that fix broken Autoconf macros).
 
 The 1.2 release contains 20 macros, among which the
 @code{AM_INIT_AUTOMAKE} macro that simplifies the creation of