Include more about CCS as a defined term,

including a footnote explaining why it's still called CCS.

gpl-lgpl.tex

@@ -2257,12 +2257,23 @@ 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: More about CCS here.
+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
+  Corresponding Source'', abbreviated to ``CCS''.  Admittedly, the word
+  ``complete'' no longer appears in GPLv3 (which uses the word ``all''
+  instead).  However, both GPLv2 and the early drafts of GPLv3 itself used
+  the word complete, and early GPLv3 drafts even included the phrase
+  ``Complete Corresponding Source''.  Meanwhile, use of the acronym ``CCS''
+  (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
 
-The definition of ``Complete Corresponding Source Code'' given in the
-second paragraph of section 1 is as broad as necessary to protect users'
+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