Editorial fixes to g77 docs

From-SVN: r25790

gcc/f/ChangeLog

+Mon Mar 15 17:12:07 1999  Craig Burley  <craig@jcb-sc.com>
+
+	* bugs.texi, g77.texi, news.texi: Editorial fixes.
+
 Sat Mar 13 17:51:55 1999  Craig Burley  <craig@jcb-sc.com>
 
 	Fix 19990313-0.f, 19990313-1.f, 19990313-2.f, 19990313-3.f:

gcc/f/bugs.texi

@@ -9,7 +9,7 @@
 @c in the standalone derivations of this file (e.g. BUGS).
 @set copyrights-bugs 1995-1999
 
-@set last-update-bugs 1999-03-13
+@set last-update-bugs 1999-03-15
 
 @include root.texi
 
@@ -47,15 +47,15 @@ so it isn't worth separating them out.
 
 @ifset DOC-G77
 For information on bugs in @emph{other} versions of @code{g77},
-@ref{News,,News About GNU Fortran}.
-There, lists of bugs fixed in various versions of @code{g77},
+see @ref{News,,News About GNU Fortran}.
+There, lists of bugs fixed in various versions of @code{g77}
 can help determine what bugs existed in prior versions.
 @end ifset
 
 @ifset DOC-BUGS
 For information on bugs in @emph{other} versions of @code{g77},
 see @file{@value{path-g77}/NEWS}.
-There, lists of bugs fixed in various versions of @code{g77},
+There, lists of bugs fixed in various versions of @code{g77}
 can help determine what bugs existed in prior versions.
 @end ifset
 
@@ -85,7 +85,7 @@ Follow the ``Known Bugs'' link.
 @ifset DOC-G77
 For information on bugs that might afflict people who
 configure, port, build, and install @code{g77},
-@ref{Problems Installing}.
+see @ref{Problems Installing}.
 @end ifset
 
 @ifset DOC-BUGS

gcc/f/g77.texi

@@ -2,7 +2,7 @@
 @c %**start of header
 @setfilename g77.info
 
-@set last-update 1999-03-13
+@set last-update 1999-03-15
 @set copyrights-g77 1995-1999
 
 @include root.texi
@@ -1527,7 +1527,8 @@ Such source code cannot contain any preprocessor directives, such
 as @code{#include}, @code{#define}, @code{#if}, and so on.
 
 You can force @samp{.f} files to be preprocessed by @samp{cpp} by using
-@samp{-x f77-cpp-input}, @ref{LEX}.
+@samp{-x f77-cpp-input}.
+@xref{LEX}.
 
 @cindex preprocessor
 @cindex C preprocessor
@@ -2735,8 +2736,8 @@ but not in code like:
       d = (b + c) * e
 @end smallexample
 
-For another, potentially better, way of controlling the precision
-@ref{Floating-point precision}.
+For another, potentially better, way of controlling the precision,
+see @ref{Floating-point precision}.
 
 @cindex -fforce-mem option
 @cindex options, -fforce-mem
@@ -5989,14 +5990,15 @@ they are documented elsewhere.
 @ifinfo
 @xref{Characters Lines Sequence},
 @end ifinfo
-for information on additional fixed source form lexical issues.  In
-addition, the free source form is supported through the
+for information on additional fixed source form lexical issues.
 @cindex @samp{-ffree-form}
-@samp{-ffree-form} option.  Other Fortran 90 features can be turned on
-by the
+Further, the free source form is supported through the
+@samp{-ffree-form} option.
 @cindex @samp{-ff90}
-@samp{-ff90} option, @ref{Fortran 90}.  For information on the Fortran
-90 intrinsics available @ref{Table of Intrinsic Functions}.
+Other Fortran 90 features can be turned on by the @samp{-ff90} option;
+see @ref{Fortran 90}.
+For information on the Fortran 90 intrinsics available,
+see @ref{Table of Intrinsic Functions}.
 
 @table @asis
 @item Automatic arrays in procedures
@@ -12198,7 +12200,7 @@ written.
 Thus for exchanging a sequential or direct access unformatted file
 between big- and little-endian 32-bit systems using IEEE 754 floating
 point it would be sufficient to reverse the bytes in consecutive words
-in the file @emph{iff} only @code{REAL*4}, @code{COMPLEX},
+in the file if, and @emph{only} if, only @code{REAL*4}, @code{COMPLEX},
 @code{INTEGER*4} and/or @code{LOGICAL*4} data have been written to it by
 @code{g77}.
 

gcc/f/news.texi

@@ -107,7 +107,7 @@ somewhat more difficult.
 
 @ifset DOC-G77
 For information on bugs in the @value{which-g77} version of @code{g77},
-@ref{Known Bugs,,Known Bugs In GNU Fortran}.
+see @ref{Known Bugs,,Known Bugs In GNU Fortran}.
 @end ifset
 
 @ifset DOC-BUGS