diff --git a/compliance-guide.tex b/compliance-guide.tex
index 7a35558..f2dc345 100644
--- a/compliance-guide.tex
+++ b/compliance-guide.tex
@@ -162,23 +162,32 @@ situations admittedly do require a highly
 fact-dependent analysis and cannot be addressed in a general-purpose
 document, anyway.
 
-Most companies accused of violations, however, lack a basic understanding
-of how to comply even in the straightforward scenario.  This document
-provides that fundamental and generally applicable prerequisite knowledge.
+\medskip
+
+Most companies accused of violations lack a basic understanding
+of how to comply even in the former straightforward scenario.  This document
+provides those companies with the fundamental and generally applicable prerequisite knowledge.
 For answers to rarer and more complicated legal questions, such as whether
-your software is a derivative work of some copylefted software, consult
+your software is a derivative or combined work of some copylefted software, consult
 with an attorney.\footnote{If you would like more information on the
   application of derivative works doctrine to software, a detailed legal
   discussion is presented in our colleague Dan Ravicher's article,
-  \textit{Software Derivative Work: A Circuit Dependent Determination}.}
+  \textit{Software Derivative Work: A Circuit Dependent Determination} and in
+  \tutorialpartsplit{\texit{Detailed Analysis of the GNU GPL and Related
+      Licenses}'s Section on derivative works}{\S~\ref{derivative-works} of
+    this tutorial}.}
 
-For this discussion, we will assume that you have already identified the
+This discussion thus assumes that you have already identified the
 ``work'' covered by the license, and that any components not under the GPL
 (e.g., applications written entirely by your developers that merely happen
 to run on a Linux-based operating system) distributed in conjunction with
-those works are separate works within the meaning of copyright law.  In
-such a case, the GPL requires you to provide complete and corresponding
-source for the GPL'd components and your modifications thereto, but not
+those works are separate works within the meaning of copyright law and the GPL\@.  In
+such a case, the GPL requires you to provide complete corresponding
+source (CCS)\footnote{For more on CCS,  see
+\tutorialpartsplit{\texit{Detailed Analysis of the GNU GPL and Related
+      Licenses}'s Section on GPLv2~\S2 and GPLv3~\S1.}{\S~\ref{GPLv2s2} and \S~\ref{GPLv3s1} of
+    this tutorial}.
+for the GPL'd components and your modifications thereto, but not
 for independent proprietary applications.  The procedures described in
 this document address this typical scenario.
 
diff --git a/gpl-lgpl.tex b/gpl-lgpl.tex
index 041ce94..96b461e 100644
--- a/gpl-lgpl.tex
+++ b/gpl-lgpl.tex
@@ -2406,6 +2406,7 @@ defined terms are discussed in the section where they are defined and/or
 used.
 
 \section{GPLv3~\S1: Understanding CCS}
+\label{GPLv3s1}
 
 Ensuring that users have the source code to the software they receive and the
 freedom to modify remains the paramount right embodied in the Free Software