diff --git a/compliance-guide.tex b/compliance-guide.tex
index 82b02978cd86a0b9fdd903d16d71427e81c7228c..110b71b089a81a90d24bbc441f170f974aaa8fc6 100644
--- a/compliance-guide.tex
+++ b/compliance-guide.tex
@@ -157,13 +157,18 @@ the GPL'd components.\footnote{However, these programs do often combine
   with LGPL'd libraries. This is discussed in detail in \S~\ref{lgpl}.}
 In the latter case, where the work is unquestionably a separate work of
 creative expression, no copyleft provisions are invoked.
+The core compliance issue faced, thus, in such a situation, is not an discussion of what is or is not a
+combined or derivative work, but rather, issues related to distribution and
+conveyance of binary works based on GPL'd source, but without Complete,
+Corresponding Source.  This tutorial therefore focuses primarily on that issue.
 
 Admittedly, a tiny
-minority of situations lie outside these two categories, and thus
-do involve close questions about derivative and combined works.  Those
-situations admittedly do require a highly
+minority of compliance situations relate to question of derivative and
+combined words.  Those
+situations are so rare, and the details from situation to situation differ
+greatly.  Thus, such situations require a highly
 fact-dependent analysis and cannot be addressed in a general-purpose
-document, anyway.
+document such as this one.
 
 \medskip
 
