Re: [Patch, wwwdocs] Update Fortran part of the GCC 4.8 release notes

[Gerald Pfeifer <gerald at pfeifer dot com>]

On Thu, 20 Dec 2012, Tobias Burnus wrote:
> The following patch updates the Fortran part of the GCC 4.8 release 
> notes at http://gcc.gnu.org/gcc-4.8/changes.html#fortran

Nice!  I had a look and made a couple of editorial changes which
should not change any of the statements.  If you'd like to see
some adjusted (or clarified) or have further suggestions, let me
know and I'll take care.

Gerald

Index: changes.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/gcc-4.8/changes.html,v
retrieving revision 1.77
retrieving revision 1.78
diff -u -3 -p -r1.77 -r1.78
--- changes.html	3 Jan 2013 05:11:30 -0000	1.77
+++ changes.html	7 Jan 2013 22:31:45 -0000	1.78
@@ -246,20 +246,21 @@ B b(42); // OK
   <ul>
     <li>Compatibility notice:
     <ul>
-      <li>Module files: The version of the module files (<code>.mod</code>)
+      <li>Module files: The version of module files (<code>.mod</code>)
         has been incremented. Fortran <code>MODULE</code>s compiled by earlier
         GCC versions have to be recompiled, when they are <code>USE</code>d by
-        files compiled with GCC 4.8, because GCC 4.8 is not able to read
-        <code>.mod</code> file of earlier GCC versions; attempting to do so
-        gives an error message. Note: The ABI of the produced assembler data
-        itself has not changed; object files and libraries are fully compatible
-        to older versions. (Except as noted below.)</li>
-      <li>ABI: Some internal names (name in the assembler/object file) have
+        files compiled with GCC 4.8.  GCC 4.8 is not able to read
+        <code>.mod</code> files created by earlier versions; attempting to do so
+	gives an error message.<br/ >
+	Note: The ABI of the produced assembler data itself has not changed;
+	object files and libraries are fully compatible
+        with older versions except as noted below.</li>
+      <li>ABI: Some internal names (used in the assembler/object file) have
         changed for symbols declared in the specification part of a module.
-        If the module &ndash; or a file using such a symbol via use
-        association &ndash; is recompiled, the module and all files which
-        directly use such symbols have to be recompiled. The change only
-        affects the following kind of module symbols:
+	If an affected module &ndash; or a file using it via use
+	association &ndash; is recompiled, the module and all files which
+	directly use such symbols have to be recompiled as well. This change
+	only affects the following kind of module symbols:
         <ul>
           <li>Procedure pointers. Note: C-interoperable function pointers
             (<code>type(c_funptr)</code>) are not affected nor are
@@ -276,12 +277,12 @@ B b(42); // OK
     <li>The <code><a
     href="http://gcc.gnu.org/onlinedocs/gfortran/Error-and-Warning-Options.html";>
     -Wc-binding-type</a></code> warning option has been added (disabled
-    by default), which warns if the a variable might not be C interoperable. In
+    by default).  It warns if the a variable might not be C interoperable; in
     particular, if the variable has been declared using an intrinsic type with
     default kind instead of using a kind parameter defined for C
-    interoperability in the intrinsic <code>ISO_C_Binding</code> module. Before,
-    the warning was always printed. The <code>-Wc-binding-type</code> option
-    is enabled by <code>-Wall</code>.</li>
+    interoperability in the intrinsic <code>ISO_C_Binding</code> module.
+    Before, this warning was always printed. The <code>-Wc-binding-type</code>
+    option is enabled by <code>-Wall</code>.</li>
 
     <li>The <a
     href="http://gcc.gnu.org/onlinedocs/gfortran/Error-and-Warning-Options.html";>
@@ -334,7 +335,7 @@ B b(42); // OK
     <li><a href="http://gcc.gnu.org/wiki/Fortran2003Status";>Fortran 2003</a>:
     <ul>
       <li>Support for unlimited polymorphic variables (<code>CLASS(*)</code>)
-      has been added. Note that nonconstant character lengths are not yet
+      has been added. Nonconstant character lengths are not yet
       supported.</li>
     </ul></li>