From: Paul Eggert <eggert@cs.ucla.edu>
Date: Thu, 7 Aug 2003 05:13:09 +0000 (+0000)
Subject: Fix minor doc typos.  Problem reported by Ralf Wildenhues.
X-Git-Tag: AUTOCONF-2.57b~29
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=27dc41d1bc0e3a6b43802b74b56c0885e7fe98b0;p=thirdparty%2Fautoconf.git

Fix minor doc typos.  Problem reported by Ralf Wildenhues.
---

diff --git a/doc/autoconf.texi b/doc/autoconf.texi
index d765656b..186918e5 100644
--- a/doc/autoconf.texi
+++ b/doc/autoconf.texi
@@ -7587,8 +7587,8 @@ Yet another great name from Lars J. Aas.
 @c
 }.
 
-@command{autom4te} should basically considered as a replacement of
-@command{m4} itself.
+@command{autom4te} is a preprocessor that is like @command{m4}.
+It supports M4 extensions designed for use in tools like Autoconf.
 
 @menu
 * autom4te Invocation::         A @acronym{GNU} M4 wrapper
@@ -11448,7 +11448,8 @@ OpenBSD and FreeBSD @command{make}s, however, will never perform a
 This is extremely annoying.
 
 When attempting a @code{VPATH} build for an autoconfiscated package
-(e.g, @code{mkdir build; ../configure}), this means the @acronym{GNU}
+(e.g,, @code{mkdir build && cd build && ../configure}), this means the
+@acronym{GNU}
 @command{make} will build everything locally in the @file{build}
 directory, while BSD @command{make} will build new files locally and
 update existing files in the source directory.