diff --git a/enforcement-case-studies.tex b/enforcement-case-studies.tex
index cec9431..3274bf4 100644
--- a/enforcement-case-studies.tex
+++ b/enforcement-case-studies.tex
@@ -250,12 +250,15 @@ begin, we offer a study in how copyleft compliance done correctly.
 This example is, in fact, more than ten years in the making.  Since almost
 the inception of for-profit corporate adoption of Free Software, companies
 have requested a clear example of a model citizen to emulate.  Sadly, while
-community-oriented enforcers have vetted uncounted thousands of CCS
-candidates from hundreds of companies, the CCS release describes the first
-one CCS experts have declared a  ``pristine example''.
+community-oriented enforcers have vetted uncounted thousands of ``Complete,
+Corresponding Source'' CCS candidates from hundreds of companies, the CCS
+release describes the first one CCS experts have declared a ``pristine
+example''.
 
-% FIXME: link to a ``CCS iteration'' discussion in compliance-guide.tex when
-% one exists.  (the ``iteration process'' is discussed in~\ref{} of this guide)
+% FIXME (above): link to a further discussion of CCS in the compliance guide
+% when a good spot exists, then (below) link to a ``CCS iteration''
+% discussion in compliance-guide.tex when one exists.  (the ``iteration
+% process'' is discussed in~\ref{} of this guide)
 
 Of course, most CCS examined for the last decade has (eventually) complied
 with the GPL, perhaps after many iterations of review by the enforcer.