Re: more doc. proofreading

[akim]

On Fri, Apr 13, 2001 at 01:32:25AM -0400, Steven G. Johnson wrote:
> 2001-04-13  Steven G. Johnson  <address@hidden>
> 
>       * doc/autoconf.texi: Still more minor modifications for clarity,
>       felicity, and grammar.

Great work!  Thanks _a lot_!  Please, install!

Unfortunately I have not read Pavel's proposal yet, and there might
be some conflicts between the two.  But since I believe Pavel has
completely rewritten some parts, it should be easy for him (well, I
hope Pavel!) to just paste again his part.

> @@ -3727,7 +3712,7 @@
>  @subsection Generic Header Checks
>  
>  These macros are used to find system header files not covered by the
> -particular test macros.  If you need to check the contents of a header
> +"particular" test macros.  If you need to check the contents of a header
>  as well as find out whether it is present, you have to write your own
>  test for it (@pxref{Writing Tests}).

I don't know if it's right to use the double quotes like this.  Could you
check that in DVI and info it comes out properly?  I thought we had to
use `` and ''.

>  @cindex @command{break}
> -The use of @samp{break 2} etc. is safe.
> +The use of @samp{break 2}, etcetera, is safe.

!!!  Why?  Isn't it et caetera?  At least, that's the way French spell
Latin :)

> -have been used (yes, with the parentheses).  Or better yet, using high
> -level macros such as @code{AC_EXPAND_ONCE}.
> +have been used (yes, with the parentheses)...or better yet, high-level
> +macros such as @code{AC_EXPAND_ONCE}.

Aren't there any space after ellipsis in English typography?

>  Like other @sc{gnu} @code{configure} scripts, Autoconf-generated
>  @code{configure} scripts can make decisions based on a canonical name
> -for the system type, which has the form
> +for the system type, which has the form:
>  @address@hidden@address@hidden, where @var{os} can be
>  @address@hidden or @address@hidden@var{system}}

Are you sure you meant to add a colon here?  I mean, the cpu-vendor-os
strings appears in the text body, part of the paragraph, it is not an
@example.

> -macro was run.  Any configure script may use these variables anywhere.
> -These are the variables that should be used when in interaction with
> -the user.
> address@hidden, and @samp{--target}; in particular, they are left empty

These should be @option.

Again, thanks!