Fix some typos and a grammar nit.

diff --git a/automake.texi b/automake.texi
index 9a164b45a30511b9ab3846d324b04e0f363de0f7..de2fec9491b2f8c06d331d2c5d972f597d7bb077 100644 (file)
--- a/automake.texi
+++ b/automake.texi
@@ -560,7 +560,7 @@ Such compilers are rare.
 @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 @@ is substituted.  Because we have not listed the source of
 @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 @@ and generate the corresponding @file{Makefile.in}.  Note that
 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
-@file{configure.in}.  (Alteratively, you may rely on Autoconf's
+@file{configure.in}.  (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 @@ nobase_include_HEADERS = sys/types.h
 @cindex dist_ and nobase_
 @cindex nodist_ and nobase_
 
-@samp{nobase_} should be specified first when used in conjonction with
+@samp{nobase_} should be specified first when used in conjunction with
 either @samp{dist_} or @samp{nodist_} (@pxref{Dist}).  For instance:
 
 @example
@@ -2184,7 +2184,7 @@ You can't put a configure substitution (e.g., @samp{@@FOO@@}) into a
 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.
 
@@ -4190,7 +4190,7 @@ distribution is self-contained.
 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
-@file{Makefile.am}, or on the commande line when invoking @code{make}.
+@file{Makefile.am}, or on the command line when invoking @code{make}.
 @vindex DISTCHECK_CONFIGURE_FLAGS
 
 If the target @code{distcheck-hook} is defined in your
@@ -4648,7 +4648,7 @@ suffixes in the @code{SUFFIXES} variable @strong{before} you define your
 implicit rule.
 
 For instance the following definition prevents Automake to misinterpret
-@samp{.idlC.cpp:} as an attemp to transform @samp{.idlC} into
+@samp{.idlC.cpp:} as an attempt to transform @samp{.idlC} into
 @samp{.cpp}.
 
 @example
@@ -5040,7 +5040,7 @@ means you can install several versions of Automake in the same
 @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
@@ -5069,9 +5069,9 @@ older than the requested version.
 
 @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{}