FYI: HEAD: some typos

[Ralf Wildenhues]

Applied to HEAD.

Rationale for not waiting for approval: triviality. :)

Cheers,
Ralf

        * README, README.alpha, libtoolize.m4sh: Typos.
        * tests/am-subdir.at, tests/duplicate_members.at: Make all
        banners end with a dot, for symmetry.

Index: README
===================================================================
RCS file: /cvsroot/libtool/libtool/README,v
retrieving revision 1.21
diff -u -r1.21 README
--- README      22 Apr 2005 10:10:29 -0000      1.21
+++ README      4 Dec 2005 12:48:10 -0000
@@ -62,7 +62,7 @@
 If you wish to report a test group failure to the libtool list, you
 need to send the verbose output of the FAILing group, along with the
 information from the end of `$(top_builddir)/libtool --help' to the
-bug report mailing list, <address@hidden>.  From a bourne
+bug report mailing list, <address@hidden>.  From a Bourne
 compatible shell, you can generate verbose test output like this:
 
   VERBOSE=yes make check \
Index: README.alpha
===================================================================
RCS file: /cvsroot/libtool/libtool/README.alpha,v
retrieving revision 1.4
diff -u -r1.4 README.alpha
--- README.alpha        22 Apr 2005 10:10:29 -0000      1.4
+++ README.alpha        4 Dec 2005 13:01:30 -0000
@@ -66,7 +66,7 @@
 to send the verbose output of the FAILing group, along with the
 information from the end of `$(top_builddir)/libtool --help' to the bug
 report mailing list, <address@hidden> with a subject line that
-includes the string `[TEST FAILURE]'.  From a bourne compatible shell,
+includes the string `[TEST FAILURE]'.  From a Bourne compatible shell,
 you can generate verbose test output like this:
 
   VERBOSE=yes make check \
Index: libtoolize.m4sh
===================================================================
RCS file: /cvsroot/libtool/libtool/libtoolize.m4sh,v
retrieving revision 1.48
diff -u -r1.48 libtoolize.m4sh
--- libtoolize.m4sh     3 Dec 2005 08:49:48 -0000       1.48
+++ libtoolize.m4sh     4 Dec 2005 12:48:10 -0000
@@ -1131,9 +1118,9 @@
       func_ltmain_update ltmain.sh "$pkgdatadir/config" "$auxdir"
     fi
   else
-    func_verbose "AC_CONFIG_AUX_DIR not defined, not copying libtool 
auxilliary files."
+    func_verbose "AC_CONFIG_AUX_DIR not defined, not copying libtool auxiliary 
files."
   fi
 
   # Copy libtool's m4 macros to the macro directory, if they are newer.
   if test -n "$m4dir"; then
     $opt_quiet || func_echo "putting macros in AC_CONFIG_MACRO_DIR, \`$m4dir'."
Index: tests/am-subdir.at
===================================================================
RCS file: /cvsroot/libtool/libtool/tests/am-subdir.at,v
retrieving revision 1.10
diff -u -r1.10 am-subdir.at
--- tests/am-subdir.at  14 Nov 2005 22:19:40 -0000      1.10
+++ tests/am-subdir.at  4 Dec 2005 12:48:11 -0000
@@ -17,7 +17,7 @@
 # 02110-1301, USA.
 
 
-AT_BANNER([Libtool's subdir-objects support.])
+AT_BANNER([Libtool subdir-objects support.])
 
 
 ## ----------- ##
Index: tests/duplicate_members.at
===================================================================
RCS file: /cvsroot/libtool/libtool/tests/duplicate_members.at,v
retrieving revision 1.3
diff -u -r1.3 duplicate_members.at
--- tests/duplicate_members.at  27 Apr 2005 18:18:10 -0000      1.3
+++ tests/duplicate_members.at  4 Dec 2005 12:48:11 -0000
@@ -16,7 +16,7 @@
 # Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA
 # 02110-1301, USA.
 
-AT_BANNER([Testing libtool functions])
+AT_BANNER([Testing libtool functions.])
 AT_SETUP([duplicate members in archive tests])
 
 # we don't want to use whole_archive_flag_spec, even if available