[latex3-commits] [latex2e-public] r1333 - wording from Chris

[noreply at latex-project.org]

Author: carlisle
Date: 2017-01-11 10:58:44 +0100 (Wed, 11 Jan 2017)
New Revision: 1333

Modified:
   trunk/doc/ltnews26.tex
Log:
wording from Chris

Modified: trunk/doc/ltnews26.tex
===================================================================
--- trunk/doc/ltnews26.tex	2017-01-11 00:39:40 UTC (rev 1332)
+++ trunk/doc/ltnews26.tex	2017-01-11 09:58:44 UTC (rev 1333)
@@ -197,8 +197,8 @@
 
 In 2015 we announced the introduction of the roll-back\slash
 roll-forward concept to manage bug fixes and additions to core
-\LaTeX{} in a manageable way for the user base. We also announced back
-then that we now incorporate all fixes from \textsf{fixltx2e} into the
+\LaTeX{} in a manageable way. We also announced at that time
+that we now incorporate all fixes from \textsf{fixltx2e} into the
 kernel (as the old mechanism produced problems instead of improving
 the situation). Refer to
 \href{https://www.latex-project.org/news/latex2e-news/ltnews22.pdf}{\texttt{ltnews22.pdf}}
@@ -213,11 +213,12 @@
 when typesetting in two-column mode).
 
 Starting with release 2015/01/01 this is now finally corrected already
-in the kernel and not only in \textsf{fixltx2e}. In nearly all
-circumstances this will either not make any difference to existing
-documents or if it does locally improve the visual appearance of that
-document. It is, however, by the nature of the change also possible
-that there are changes to the page breaks due to the different break
+in the kernel and not only in \textsf{fixltx2e}.  In nearly all
+circumstances this will either make no difference to existing
+documents or, it will locally impove the visual appearence of that
+document without changing anything on other pages.  However, by the
+nature of the change it is also possible that there are further
+non-local changes to the page breaks due to the different break
 positions introduced by the fix.
 
 Thus, for documents that have been written before 2015 and that should