diff --git a/compliance-guide.tex b/compliance-guide.tex
index 05b1c8f2427ae679728d6a8850bc791141a1a452..9b220134b9d85f8732afd8606a5cb66004f1dd96 100644
--- a/compliance-guide.tex
+++ b/compliance-guide.tex
@@ -148,7 +148,7 @@ systems most often encountered typically consist of a full operating system
 including components under the GPL (e.g., Linux, BusyBox) and components
 under the LGPL (e.g., the GNU C Library).  Sometimes, these programs have
 been patched or slightly improved by direct modification of their sources,
-and thus the result is unequivocally a derivative work.  Alongside these programs,
+and thus the result is unequivocally a modified version.  Alongside these programs,
 companies often distribute fully independent, proprietary programs,
 developed from scratch, which are designed to run on the Free Software operating
 system but do not combine with, link to, modify, derive from, or otherwise
@@ -158,13 +158,13 @@ the GPL'd components.\footnote{However, these programs do often combine
 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
+combined, derivative, and/or modified version of the 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 compliance situations relate to question of derivative and
-combined words.  Those
+minority of compliance situations relate to question of derivative,
+combined, or modified versions of the work.  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
