s/parenthesis/parentheses/ where appropriate.

* doc/autoconf.texi: Fix typos.
* lib/m4sugar/m4sugar.m4: Likewise.
Reported by Ralf Wildenhues.

Signed-off-by: Eric Blake <ebb9@byu.net>

diff --git a/ChangeLog b/ChangeLog
index 9cd6b9ff4a63efa647e338ffcd529d6f3d9eb82b..9603e3290be3883013aacb39cb74b0590c516bf8 100644 (file)
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,5 +1,10 @@
 2007-10-19  Eric Blake  <ebb9@byu.net>
 
+       s/parenthesis/parentheses/ where appropriate.
+       * doc/autoconf.texi: Fix typos.
+       * lib/m4sugar/m4sugar.m4: Likewise.
+       Reported by Ralf Wildenhues.
+
        Document m4_expand limitation.
        * lib/m4sugar/m4sugar.m4 (m4_expand): Mention problem with
        unbalanced parse.

diff --git a/doc/autoconf.texi b/doc/autoconf.texi
index cd04092366927a3efe1a2e1da38f45f05610e5c6..5c09d3e15ceec93491bdcf8a4b115717ab0b8558 100644 (file)
--- a/doc/autoconf.texi
+++ b/doc/autoconf.texi
@@ -9484,7 +9484,7 @@ what syntactic forms are comments (it is common to see
 @samp{changecom(<!--, -->)} when M4 is used to produce HTML pages),
 @code{changeword} and @code{changesyntax} to change other syntactic
 details (such as the character to denote the @var{n}th argument, @samp{$} by
-default, the parenthesis around arguments, etc.).
+default, the parentheses around arguments, etc.).
 
 These primitives are really meant to make M4 more useful for specific
 domains: they should be considered like command line options:
@@ -10770,7 +10770,7 @@ expansion of macros contained in @var{arg}.
 
 Note that @code{m4_expand} cannot parse everything.  The expansion of
 @var{arg} must not contain unbalanced quotes (although quadrigraphs can
-get around this), nor unbalanced parenthesis (portable shell @code{case}
+get around this), nor unbalanced parentheses (portable shell @code{case}
 statements are a major culprit here, but creative shell comments can get
 around this).
 
@@ -17376,7 +17376,7 @@ Since it is not expanded, it should not be double quoted.
 The @code{AS_HELP_STRING} macro is particularly helpful when the
 @var{left-hand-side} and/or @var{right-hand-side} are composed of macro
 arguments, as shown in the following example.  Be aware that
-@var{left-hand-side} may not contain unbalanced quotes or parenthesis.
+@var{left-hand-side} may not contain unbalanced quotes or parentheses.
 
 @example
 AC_DEFUN([MY_ARG_WITH],
@@ -19946,7 +19946,7 @@ This macro starts a group of related tests, all to be executed in the
 same subshell.  It accepts a single argument, which holds a few words
 (no more than about 30 or 40 characters) quickly describing the purpose
 of the test group being started.  @var{test-group-name} must not contain
-unbalanced quotes or parenthesis.
+unbalanced quotes or parentheses.
 @end defmac
 
 @defmac AT_KEYWORDS (@var{keywords})

diff --git a/lib/m4sugar/m4sugar.m4 b/lib/m4sugar/m4sugar.m4
index 70b9a84a889dffe395b3aec309e404c5539cdb50..7ac53d54d445b398da5efde1d6debae7c6c40aea 100644 (file)
--- a/lib/m4sugar/m4sugar.m4
+++ b/lib/m4sugar/m4sugar.m4
@@ -676,7 +676,7 @@ m4_define([m4_echo], [$@])
 #   => ACT,IVE, ACT, IVE
 #
 # Unfortunately, due to limitations in m4, ARG must contain balanced quotes
-# (use quadrigraphs) and balanced parenthesis (use creative shell comments
+# (use quadrigraphs) and balanced parentheses (use creative shell comments
 # when writing shell case statements).
 #
 # Splitting a quoted ARG on `,' preserves space, but produces a quoted list.
@@ -866,7 +866,7 @@ m4_if(m4_defn([$1]), [$2], [],
 #
 # Now, just replace the `$2' with `m4_quote($2)' in the outer `m4_if'
 # to improve robustness, and you come up with a nice implementation
-# that doesn't require extra parenthesis in the user's LIST.
+# that doesn't require extra parentheses in the user's LIST.
 #
 # But wait -  now the algorithm is quadratic, because every recursion of
 # the algorithm keeps the entire LIST and merely adds another m4_shift to