2003-05-09  J. Otto Tennant  <jotto@pobox.com>

	* doc/bugreport.texi: Fixes to spelling, grammar, and diction.
	* doc/trouble.texi: Fix linebreaking across variables.

--- bugreport.texi.orig	2003-05-13 13:01:12.000000000 -0400
+++ bugreport.texi	2003-05-13 13:01:30.000000000 -0400
@@ -233,7 +233,7 @@
 
 Even if the problem you experience is a fatal signal, you should still
 say so explicitly.  Suppose something strange is going on, such as, your
-copy of the compiler is out of synch, or you have encountered a bug in
+copy of the compiler is out of sync, or you have encountered a bug in
 the C library on your system.  (This has happened!)  Your copy might
 crash and the copy here would not.  If you @i{said} to expect a crash,
 then when the compiler here fails to crash, we would know that the bug
--- trouble.texi.orig	2003-05-13 12:52:40.000000000 -0400
+++ trouble.texi	2003-05-13 12:59:48.000000000 -0400
@@ -1226,7 +1226,7 @@
 for pragmatic reasons, not as a requirement.
 
 GCC normally defines @code{__STDC__} to be 1, and in addition
-defines @code{__STRICT_ANSI__} if you specify the @option{-ansi} option,
+defines @w{@code{__STRICT_ANSI__}} if you specify the @option{-ansi} option,
 or a @option{-std} option for strict conformance to some version of ISO C@.
 On some hosts, system include files use a different convention, where
 @code{__STDC__} is normally 0, but is 1 if the user specifies strict
@@ -1238,7 +1238,7 @@
 Undefining @code{__STDC__} in C++.
 
 Programs written to compile with C++-to-C translators get the
-value of @code{__STDC__} that goes with the C compiler that is
+value of @w{@code{__STDC__}} that goes with the C compiler that is
 subsequently used.  These programs must test @code{__STDC__}
 to determine what kind of C preprocessor that compiler uses:
 whether they should concatenate tokens in the ISO C fashion