More node renaming in the manual.

* doc/automake.texi (Top): Adjust menu to ...
(API Versioning): ... this node being renamed from ...
(API versioning): ... this, and ...
(Wildcards): ... this being renamed from ...
(wildcards): ... this.
Report by Karl Berry.

Signed-off-by: Ralf Wildenhues <Ralf.Wildenhues@gmx.de>

diff --git a/ChangeLog b/ChangeLog
index ff1cc4a..5626424 100644 (file)
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,13 @@
+2009-04-04  Ralf Wildenhues  <Ralf.Wildenhues@gmx.de>
+
+       More node renaming in the manual.
+       * doc/automake.texi (Top): Adjust menu to ...
+       (API Versioning): ... this node being renamed from ...
+       (API versioning): ... this, and ...
+       (Wildcards): ... this being renamed from ...
+       (wildcards): ... this.
+       Report by Karl Berry.
+
 2009-04-03  Andreas Schwab  <schwab@linux-m68k.org>
 
        * tests/instdir-java.test: Don't require gcj.  Skip if javac is

diff --git a/doc/automake.texi b/doc/automake.texi
index 14552cf..0f61f05 100644 (file)
--- a/doc/automake.texi
+++ b/doc/automake.texi
@@ -117,7 +117,7 @@ section entitled ``@acronym{GNU} Free Documentation License.''
 * Cygnus::                      The effect of @option{--cygnus}
 * Not Enough::                  When Automake is not Enough
 * Distributing::                Distributing the Makefile.in
-* API versioning::              About compatibility between Automake versions
+* API Versioning::              About compatibility between Automake versions
 * Upgrading::                   Upgrading to a Newer Automake Version
 * FAQ::                         Frequently Asked Questions
 * History::                     Notes about the history of Automake
@@ -329,7 +329,7 @@ Frequently Asked Questions about Automake
 
 * CVS::                         CVS and generated files
 * maintainer-mode::             missing and AM_MAINTAINER_MODE
-* wildcards::                   Why doesn't Automake support wildcards?
+* Wildcards::                   Why doesn't Automake support wildcards?
 * Limitations on File Names::   Limitations on source and installed file names
 * distcleancheck::              Files left in build directory after distclean
 * Flag Variables Ordering::     CFLAGS vs.@: AM_CFLAGS vs.@: mumble_CFLAGS
@@ -10036,8 +10036,8 @@ have a special exception allowing you to distribute them with your
 package, regardless of the licensing you choose.
 
 
-@node API versioning
-@chapter Automake API versioning
+@node API Versioning
+@chapter Automake API Versioning
 
 New Automake releases usually include bug fixes and new features.
 Unfortunately they may also introduce new bugs and incompatibilities.
@@ -10166,7 +10166,7 @@ lists.
 @menu
 * CVS::                         CVS and generated files
 * maintainer-mode::             missing and AM_MAINTAINER_MODE
-* wildcards::                   Why doesn't Automake support wildcards?
+* Wildcards::                   Why doesn't Automake support wildcards?
 * Limitations on File Names::   Limitations on source and installed file names
 * distcleancheck::              Files left in build directory after distclean
 * Flag Variables Ordering::     CFLAGS vs.@: AM_CFLAGS vs.@: mumble_CFLAGS
@@ -10420,7 +10420,7 @@ and because @command{missing} isn't enough if you have the wrong
 version of the tools.
 
 
-@node wildcards
+@node Wildcards
 @section Why doesn't Automake support wildcards?
 @cindex wildcards
 
@@ -12080,7 +12080,7 @@ facing similar troubles, for similar reasons.
 @item 2002-03-05 Automake 1.6
 
 This release introduced versioned installation (@pxref{API
-versioning}).  This was mainly pushed by Havoc Pennington, taking the
+Versioning}).  This was mainly pushed by Havoc Pennington, taking the
 GNOME source tree as motive: due to incompatibilities between the
 autotools it's impossible for the GNOME packages to switch to Autoconf
 2.53 and Automake 1.5 all at once, so they are currently stuck with