Revert to "configure.in" in the history, since

"configure.ac" wasn't used in the past, and in any case it is
probably a good idea to preserve this section verbatim.

diff --git a/doc/autoconf.texi b/doc/autoconf.texi
index ee70fc9faa67c3723aa8a01883a472676792fb5d..6dc410bb3f3da2b1e9ffcb762daa5b8381d1c743 100644 (file)
--- a/doc/autoconf.texi
+++ b/doc/autoconf.texi
@@ -10253,10 +10253,10 @@ locally or that have patches from vendors installed.
 
 I considered using an architecture similar to that of Cygnus
 @code{configure}, where there is a single @code{configure} script that
-reads pieces of @file{configure.ac} when run.  But I didn't want to have
+reads pieces of @file{configure.in} when run.  But I didn't want to have
 to distribute all of the feature tests with every package, so I settled
 on having a different @code{configure} made from each
-@file{configure.ac} by a preprocessor.  That approach also offered more
+@file{configure.in} by a preprocessor.  That approach also offered more
 control and flexibility.
 
 I looked briefly into using the Metaconfig package, by Larry Wall,