FYI: merge automake.texi changes from HEAD

[Alexandre Duret-Lutz]

I'm installing this on branch-1-7.  (It's already on HEAD.)

2002-11-29  Jim Meyering  <address@hidden>

        * automake.texi: Fix some typos and a grammar nit.

Index: automake.texi
===================================================================
RCS file: /cvs/automake/automake/automake.texi,v
retrieving revision 1.305.2.3
diff -u -r1.305.2.3 automake.texi
--- automake.texi       13 Nov 2002 21:05:53 -0000      1.305.2.3
+++ automake.texi       29 Nov 2002 22:05:45 -0000
@@ -560,7 +560,7 @@
 @item config.guess
 @itemx config.sub
 These programs compute the canonical triplets for the given build, host,
-or target architecture.  These programs are updated regulary to support
+or target architecture.  These programs are updated regularly to support
 new architectures and fix probes broken by changes in new kernel
 versions.  You are encouraged to fetch the latest versions of these
 files from @url{ftp://ftp.gnu.org/gnu/config/} before making a release.
@@ -829,7 +829,7 @@
 @file{false}, we have to tell Automake how to link the program.  This is
 the purpose of the @code{false_LDADD} line.  A @code{false_DEPENDENCIES}
 variable, holding the dependencies of the @file{false} target will be
-automatically generated by Automake from the contant of
+automatically generated by Automake from the content of
 @code{false_LDADD}.
 
 The above rules won't work if your compiler doesn't accept both
@@ -895,7 +895,7 @@
 package; it assumes that a package has only one @file{configure.in}, at
 the top.  If your package has multiple @file{configure.in}s, then you
 must run @code{automake} in each directory holding a
address@hidden  (Alteratively, you may rely on Autoconf's
address@hidden  (Alternatively, you may rely on Autoconf's
 @code{autoreconf}, which is able to recurse your package tree and run
 @code{automake} where appropriate.)
 
@@ -1972,7 +1972,7 @@
 @cindex dist_ and nobase_
 @cindex nodist_ and nobase_
 
address@hidden should be specified first when used in conjonction with
address@hidden should be specified first when used in conjunction with
 either @samp{dist_} or @samp{nodist_} (@pxref{Dist}).  For instance:
 
 @example
@@ -2184,7 +2184,7 @@
 but suffice to say that it simply won't work.  Automake will give an
 error if you try to do this.
 
-Fortunatly there are two other ways to achieve the same result.  One is
+Fortunately there are two other ways to achieve the same result.  One is
 to use configure substitutions in @code{_LDADD} variables, the other is
 to use an Automake conditional.
 
@@ -4188,7 +4188,7 @@
 Building the package involves running @code{./configure}.  If you need
 to supply additional flags to @code{configure}, define them in the
 @code{DISTCHECK_CONFIGURE_FLAGS} variable, either in your top-level
address@hidden, or on the commande line when invoking @code{make}.
address@hidden, or on the command line when invoking @code{make}.
 @vindex DISTCHECK_CONFIGURE_FLAGS
 
 If the target @code{distcheck-hook} is defined in your
@@ -4646,7 +4646,7 @@
 implicit rule.
 
 For instance the following definition prevents Automake to misinterpret
address@hidden:} as an attemp to transform @samp{.idlC} into
address@hidden:} as an attempt to transform @samp{.idlC} into
 @samp{.cpp}.
 
 @example
@@ -5038,7 +5038,7 @@
 @samp{$prefix}, and can select an arbitrary Automake version by running
 @samp{automake-1.6} or @samp{automake-1.7} without juggling with
 @samp{$PATH}.  Furthermore, @file{Makefile}'s generated by Automake 1.6
-will use @samp{automake-1.6} explicitely in their rebuild rules.
+will use @samp{automake-1.6} explicitly in their rebuild rules.
 
 Note that @samp{1.6} in @samp{automake-1.6} is Automake's API version,
 not Automake's version.  If a bug fix release is made, for instance
@@ -5067,9 +5067,9 @@
 
 @heading What is in the API
 
-Automake's programing interface is not easy to define.  Basically it
+Automake's programming interface is not easy to define.  Basically it
 should include at least all @strong{documented} variables and targets
-that a @samp{Makefile.am} authors can use, the behaviours associated to
+that a @samp{Makefile.am} author can use, any behavior associated with
 them (e.g. the places where @samp{-hook}'s are run), the command line
 interface of @samp{automake} and @samp{aclocal}, @dots{}
 
-- 
Alexandre Duret-Lutz