1.9b: some minor nits

[Ralf Wildenhues]

Hello Alexandre, all,

Thanks for the beta release.  OK to apply this patch for some minor
nits?

Cheers,
Ralf

        * doc/automake.texi, lib/Automake/Rule.pm: Fix some typos.
        * NEWS: Likewise.  Clarify that only one LIBOBJDIR is supported.

Index: NEWS
===================================================================
RCS file: /cvs/automake/automake/NEWS,v
retrieving revision 1.313
diff -u -r1.313 NEWS
--- NEWS        22 Aug 2006 10:04:52 -0000      1.313
+++ NEWS        24 Aug 2006 17:34:04 -0000
@@ -13,7 +13,7 @@
   - `dirlist' entries (for the aclocal search path) may use shell
     wildcards such as `*', `?', or `[...]'.
 
-  - aclocal supports an --install option, that will cause system-wide
+  - aclocal supports an --install option that will cause system-wide
     third-party macros to be installed in the local directory
     specified with the first -I flag.  This option also uses #serial
     lines in M4 files to upgrade local macros.
@@ -41,7 +41,8 @@
 
   - If `subdir-objects' is set, and AC_CONFIG_LIBOBJ_DIR is specified,
     $(LIBOBJS), $(LTLIBOBJS), $(ALLOCA), and $(LTALLOCA) can be used
-    in different directories.
+    in different directories.  However, only one instance of such a
+    library objects directory is supported.
 
 * Change to Libtool support:
 
@@ -55,11 +56,11 @@
     is not enabled.
 
   - ylwrap is now always used for lex and yacc source files,
-    regardless of whether there is more than one source per-directory.
+    regardless of whether there is more than one source per directory.
 
 * Languages changes:
 
-  - Preprocessed assembler (*.S) compilation now honnors CPPFLAGS,
+  - Preprocessed assembler (*.S) compilation now honors CPPFLAGS,
     AM_CPPFLAGS and per-target _CPPFLAGS, and supports dependency
     tracking, unlike non-preprocessed assembler (*.s).
 
@@ -128,7 +129,7 @@
 
   - clean, distribution, or rebuild rules are normally disabled for
     inputs and outputs of AC_CONFIG_FILES, AC_CONFIG_HEADERS, and
-    AC_CONFIG_LINK specified using shell variable.  However if these
+    AC_CONFIG_LINK specified using shell variables.  However, if these
     variables are used as ${VAR}, and AC_SUBSTed, then Automake will
     be able to output rules anyway.
     (See the Automake documentation for AC_CONFIG_FILES.)
@@ -138,7 +139,7 @@
     This is mostly useful when some check_PROGRAMS are listed in TESTS.
 
   - `-Wportability' has finally been turned on by default for `gnu' and
-    `gnits' strictness.  This means automake will complain about %-rules
+    `gnits' strictness.  This means, automake will complain about %-rules
     or $(GNU Make functions) unless you switch to `foreign' strictness or
     use `-Wno-portability'.
 
Index: doc/automake.texi
===================================================================
RCS file: /cvs/automake/automake/doc/automake.texi,v
retrieving revision 1.149
diff -u -r1.149 automake.texi
--- doc/automake.texi   22 Aug 2006 10:04:52 -0000      1.149
+++ doc/automake.texi   24 Aug 2006 17:34:05 -0000
@@ -3896,7 +3896,7 @@
 @vindex mkdir_p
 
 From Automake 1.8 to 1.9.6 this macro used to define the output
-variable @code{mkdir_p} to one of @code{mkdir -p}, @code{install.sh
+variable @code{mkdir_p} to one of @code{mkdir -p}, @code{install-sh
 -d}, or @code{mkinstalldirs}.
 
 Nowadays Autoconf provides a similar functionality with
Index: lib/Automake/Rule.pm
===================================================================
RCS file: /cvs/automake/automake/lib/Automake/Rule.pm,v
retrieving revision 1.10
diff -u -r1.10 Rule.pm
--- lib/Automake/Rule.pm        14 May 2005 20:28:51 -0000      1.10
+++ lib/Automake/Rule.pm        24 Aug 2006 17:37:58 -0000
@@ -1,4 +1,4 @@
-# Copyright (C) 2003, 2004  Free Software Foundation, Inc.
+# Copyright (C) 2003, 2004, 2006  Free Software Foundation, Inc.
 
 # This program is free software; you can redistribute it and/or modify
 # it under the terms of the GNU General Public License as published by
@@ -631,7 +631,7 @@
              if ($target !~ /^[^%]*%[^%]*$/)
                {
                  ## FIXME: Presently we can't diagnose duplicate user rules
-                 ## because we doesn't distinguish rules with commands
+                 ## because we don't distinguish rules with commands
                  ## from rules that only add dependencies.  E.g.,
                  ##   .PHONY: foo
                  ##   .PHONY: bar