Re: Fixing trivial grammaros (was: [SCM] GNU Autoconf source repository branch, master, updated. v2.63b-26-ge7c7a47)

[Eric Blake]

Ralf Wildenhues <Ralf.Wildenhues <at> gmx.de> writes:

> I used these vim regexes to search for possible issues:
> 
> /\<a\>[ \n] *\(@[^{]*{\)\?[aeiouAEIOU]
> /\<a\>[ \n] *\(@[^{]*{\)\?[A-Z][^a-z]
> /\<an\>[ \n] *\(@[^{]*{\)\?[bcdfghjklmnpqrstvwxyzu][a-z]
> /\<an\>[ \n] *\(@[^{]*{\)\?[BCDFGHJKLMNPQRSTVWXYZU][a-zA-Z]

Thanks for the hints.

> @@ -12811,7 +12811,7 @@ Initialization Macros
>  parent script has @code{AS_MESSAGE_FD} redirected somewhere besides
>  @samp{1}, then the child script already has code that copies stdout to
>  that descriptor.  Currently, the suggested
> -idiom for writing a M4sh shell script from within another script is:
> +idiom for writing an M4sh shell script from within another script is:

Hmm.  The manual itself says that this is pronounced 'mash', not 'em-four-ess-
aitch' [1].  In which case, this hunk is a step backwards.

[1] http://www.gnu.org/software/autoconf/manual/html_node/Programming-in-
M4sh.html

> @@ -20053,7 +20053,7 @@ config.status Invocation
> 
>  It configures each @var{tag}; if none are specified, all the templates
>  are instantiated.  A @var{tag} refers to a file or other tag associated
> -with a configuration action, as specified by a @code{AC_CONFIG_FOOS}
> +with a configuration action, as specified by an @code{AC_CONFIG_FOOS}

At least we're consistent in using the term 'AC_CONFIG_FOOS' throughout the 
manual.  But on rereading this, I think I'd like:

@address@hidden

better, since it emphasizes that FOOS is a meta-syntactic placeholder for one 
of the four config actions.  It won't help info text (since FOOS is already in 
capitals), but will make html and pdf renderings nicer.

-- 
Eric Blake