[Bug-gnupress] [DOCPATCH] Review of GCC Manual, Section 18

[Simon Law]

On Mon, Apr 28, 2003 at 10:22:22PM -0400, D F wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> I've attached a file with my suggested edits for section 18. Most of 
> these edits are an effort to avoid the second person voice in 
> favour of the (often more stilted) passive voice, as per the email 
> from Lisa earlier today.
> 
> Note that, when I sent along the edits for section 11 a couple of 
> days ago, I did not review for voice other than to ensure that the 
> voice of the section was broadly consistent.
> 
> - -- 
> Dave Fluri
> PGP Public Key-ID 3F64B9AC
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.0.7 (GNU/Linux)
> 
> iD8DBQE+reHeo1mPmT9kuawRAr8hAJ4oCNKWvVFIolsl4uiNUrRQh4e+rgCeOFGx
> VFz/SXCMJH61UKJW7nGa6e4=
> =cx1u
> -----END PGP SIGNATURE-----

        Thanks for your reading.  I have prepared a patch according to
your instructions with some minor changes.  However, I cannot make
changes to page 333.

Index: vms.texi
===================================================================
RCS file: /cvsroot/gcc/gcc/gcc/doc/vms.texi,v
retrieving revision 1.2
diff -u -r1.2 vms.texi
--- vms.texi    2 Oct 2002 19:17:30 -0000       1.2
+++ vms.texi    4 May 2003 18:39:53 -0000
@@ -160,7 +160,7 @@
 A caveat for use of @code{const} global variables: the @code{const}
 modifier must be specified in every external declaration of the variable
 in all of the source files that use that variable.  Otherwise the linker
-will issue warnings about conflicting attributes for the variable.  Your
+will issue warnings about conflicting attributes for the variable.  The
 program will still work despite the warnings, but the variable will be
 placed in writable storage.
 
@@ -181,8 +181,8 @@
 upper case without augmentation.
 
 Name augmentation yields bad results for programs that use precompiled
-libraries (such as Xlib) which were generated by another compiler.  You
-can use the compiler option @samp{/NOCASE_HACK} to inhibit augmentation;
+libraries (such as Xlib) which were generated by another compiler.  Using
+the compiler option @samp{/NOCASE_HACK} will inhibit augmentation;
 it makes external C functions and variables case-independent as is usual
 on address@hidden  Alternatively, you could write all references to the 
functions
 and variables in such libraries using lower case; this will work on VMS,
@@ -206,15 +206,15 @@
 @samp{/VERBOSE} compiler option is used, the assembler will print both
 the full and truncated names of each symbol that is truncated.
 
-The @samp{/NOCASE_HACK} compiler option should not be used when you are
+The @samp{/NOCASE_HACK} compiler option should not be used when
 compiling programs that use libg++.  libg++ has several instances of
 objects (i.e.  @code{Filebuf} and @code{filebuf}) which become
 indistinguishable in a case-insensitive environment.  This leads to
-cases where you need to inhibit augmentation selectively (if you were
+cases where augmentation needs to be inhibited selectively (if you were
 using libg++ and Xlib in the same program, for example).  There is no
-special feature for doing this, but you can get the result by defining a
-macro for each mixed case symbol for which you wish to inhibit
-augmentation.  The macro should expand into the lower case equivalent of
+special feature for doing this, but one way to achieve it is to define a
+macro for each mixed case symbol that should not be augmented.
+The macro should expand into the lower case equivalent of
 itself.  For example:
 
 @example
Index: gnu.texi
===================================================================
RCS file: /cvsroot/gcc/gcc/gcc/doc/gnu.texi,v
retrieving revision 1.1
diff -u -r1.1 gnu.texi
--- gnu.texi    16 Nov 2001 18:56:14 -0000      1.1
+++ gnu.texi    4 May 2003 18:39:53 -0000
@@ -9,7 +9,7 @@
 operating system which is free software: the GNU system.  (GNU is a
 recursive acronym for ``GNU's Not Unix''; it is pronounced
 ``guh-NEW''@.)  Variants of the GNU operating system, which use the
-kernel Linux, are now widely used; though these systems are often
+Linux kernel, are now widely used; though these systems are often
 referred to as ``Linux'', they are more accurately called GNU/Linux
 systems.