diff --git a/compliance-guide.tex b/compliance-guide.tex
index 33d6c8f78226984fe2903f19d96e5319755927af..14d783a5a1bcff89fa1b5ae3622cf4cf382bb13e 100644
--- a/compliance-guide.tex
+++ b/compliance-guide.tex
@@ -128,12 +128,15 @@ software.\footnote{This document addresses compliance with GPLv2,
 Political discussion about the GPL often centers around the ``copyleft''
 requirements of the license.  Indeed, the license was designed primarily
 to embody this licensing feature.  Most companies adding non-trivial
-features (beyond mere porting and bug-fixing) to GPL'd software, and
-thereby implicating these requirements, are already well aware of their
-more complex obligations under the license.\footnote{There has been much legal
+features (beyond mere porting and bug-fixing) to GPL'd software (and
+thereby invoking these requirements) are already well aware of their
+more complex obligations under the license.\footnote{While, there has been much legal
   discussion regarding copyleft and derivative works.  In practical
   reality, this issue is not relevant to the vast majority of companies
-  distributing GPL'd software.}
+  distributing GPL'd software.  Those interested in this issue should study
+  \tutorialpartsplit{\texit{Detailed Analysis of the GNU GPL and Related
+      Licenses}'s Section on derivative works}{\S~\ref{derivative-works} of
+    this tutorial}.}
 
 However, in our experience with GPL enforcement, few redistributors'
 compliance challenges relate directly to the copyleft provisions; this is