-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
According to Ralf Wildenhues on 4/18/2009 2:51 PM:
> Still, you do have a point in that the documentation could be a bit more
> consistent. Here's my try at it. What do you think about this?
Looks good - fix these nits, then apply:
> +It configures the @var{tag}s; if none are specified, all the templates
In info, this renders as "`tag's", which looks awkward. How about
It configures each @var{tag}; if none...
> +are instantiated. A @var{tag} specifies a file, or tag associated with
> +some other configuration action by a @code{AC_CONFIG_FOOS} macro
That comma seems awkward, since it is only a list of two alternatives.
How about:
A @var{tag} refers to a file or other tag associated with a configuration
action, as specified by a @code{AC_CONFIG_FOOS} macro
> +(@pxref{Configuration Actions}). The files must be specified without
> +their dependencies, as in
>
- --
Don't work too hard, make some time for fun as well!
Eric Blake [email protected]
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Public key at home.comcast.net/~ericblake/eblake.gpg
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAknqWFEACgkQ84KuGfSFAYCcMwCgq7K6hjK4zjHFC9CoYC+F+3On
bkEAn1nKK7yh09TQydtnCmORrwsHymEy
=ySYb
-----END PGP SIGNATURE-----
