From: Paul Eggert <eggert@cs.ucla.edu>
Date: Sun, 1 Sep 2002 08:36:52 +0000 (+0000)
Subject: Fix English-language typo in previous change.
X-Git-Tag: AUTOCONF-2.53c~17
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=7274977e149f9df08bbfb0c80f871fb40bae0ca8;p=thirdparty%2Fautoconf.git

Fix English-language typo in previous change.
---

diff --git a/doc/autoconf.texi b/doc/autoconf.texi
index 6e578e909..7f0d158a9 100644
--- a/doc/autoconf.texi
+++ b/doc/autoconf.texi
@@ -9133,11 +9133,11 @@ your script might be suspended waiting for data on its standard input.
 @evindex PS2
 @evindex PS4
 These variables should not matter for shell scripts, since they are
-supposed affect only interactive shells.  However, at least one shell
-(the pre-3.0 UWIN @command{ksh}) gets confused about whether it is
-interactive, which means that (for example) a @env{PS1} with a side
-effect can unexpectedly modify @samp{$?}.  To work around this bug,
-Autoconf-generated scripts do something like this:
+supposed to affect only interactive shells.  However, at least one
+shell (the pre-3.0 @sc{uwin} @command{ksh}) gets confused about
+whether it is interactive, which means that (for example) a @env{PS1}
+with a side effect can unexpectedly modify @samp{$?}.  To work around
+this bug, Autoconf-generated scripts do something like this:
 
 @example
 (unset ENV) >/dev/null 2>&1 && unset ENV MAIL MAILPATH