diff --git a/compliance-guide.tex b/compliance-guide.tex
index a9f2fac..d764104 100644
--- a/compliance-guide.tex
+++ b/compliance-guide.tex
@@ -718,6 +718,10 @@ under the GPL\@.  This section outlines a typical enforcement case and
 provides some guidelines for response.  These discussions are
 generalizations and do not all apply to every alleged violation.
 
+\section{Understanding Who's Enforcing}
+\label{compliance-understanding-whos-enforcing}
+% FIXME
+
 \section{Communication Is Key}
 
 GPL violations are typically only escalated when a company ignores the
diff --git a/gpl-lgpl.tex b/gpl-lgpl.tex
index 2db26b3..44c9015 100644
--- a/gpl-lgpl.tex
+++ b/gpl-lgpl.tex
@@ -1951,7 +1951,10 @@ from all copying, modification and distribution of the GPL'd software.
 At that point, violating licensees must gain the forgiveness of the copyright
 holders to have their rights restored.  Alternatively, the violators could
 negotiate another agreement, separate from GPL, with the copyright
-holder.  Both are common practice.
+holder.  Both are common practice, although
+\tutorialpartsplit{as discussed in \textit{A Practical Guide to GPL
+    Compliance}, there are }{Chapter~\ref{compliance-understanding-whos-enforcing}
+  explains further } key differences between these two very different uses of GPL.
 
 At FSF, it is part of the mission to spread software freedom. When FSF
 enforces GPL, the goal is to bring the violator back into compliance as