diff --git a/gpl-lgpl.tex b/gpl-lgpl.tex
index 940c2e88a281bb7eee3f97acf34e24687ee969cf..c55b5c88b69fd022d77f8d723e73a6c01c1b372d 100644
--- a/gpl-lgpl.tex
+++ b/gpl-lgpl.tex
@@ -2257,6 +2257,8 @@ as bytecode.  The definition of object code also ensures that licensees
 cannot escape their obligations under the GPL by resorting to shrouded
 source or obfuscated programming.
 
+% FIXME: CCS Coresponding Source updated to newer definition in later drafts
+
 Keeping with the desire to ``round up'' definitions that were spread
 throughout the text of GPLv2, the definition of CCS\footnote{Note that the
   preferred term by those who work with both GPLv2 and GPLv3 is ``Complete
@@ -2268,18 +2270,13 @@ throughout the text of GPLv2, the definition of CCS\footnote{Note that the
   (sometimes, ``C&CS'') was so widespread among GPL enforcers that its use
   continues even though GPLv3-focused experts tend to say just the defined
   term of ``Corresponding Source''.}, or, as GPLv3 officially calls it,
-``Corresponding Source'', is given in GPLv3~\S1\P4
-
-% FIXME: CCS Coresponding Source updated to newer definition in later drafts
-
-This definition of ``Corresponding Source''
-is as broad as necessary to protect users'
-exercise of their rights under the GPL. We follow the definition with
-particular examples to remove any doubt that they are to be considered
-Complete Corresponding Source Code. We wish to make completely clear
-that a licensee cannot avoid complying with the requirements of the GPL
-by dynamically linking an add-on component to the original version of a
-program.
+``Corresponding Source'', is given in GPLv3~\S1\P4.  This definition is as
+broad as necessary to protect users' exercise of their rights under the
+GPL. We follow the definition with particular examples to remove any doubt
+that they are to be considered Complete Corresponding Source Code. We wish to
+make completely clear that a licensee cannot avoid complying with the
+requirements of the GPL by dynamically linking an add-on component to the
+original version of a program.
 
 Though the definition of Complete Corresponding Source Code in the
 second paragraph of section 1 is expansive, it is not sufficient to