diff --git a/compliance-guide.tex b/compliance-guide.tex
index e60d189..33d6c8f 100644
--- a/compliance-guide.tex
+++ b/compliance-guide.tex
@@ -111,11 +111,11 @@ licenses, by comparison, its terms are in fact clear and quite favorable to
 licensees.  Indeed, the GPL's terms actually simplify compliance when
 violations occur.
 
-GPL violations are often caused or compounded by a failure to adopt sound
-practices for the incorporation of GPL'd components into a company's
-internal development environment.  In this section, we introduce some best
+GPL violations occur (or, are compounded) most often when companies lack sound
+practices for the incorporation of GPL'd components into their
+internal development environment.  This section introduces some best
 practices for software tool selection, integration and distribution,
-inspired by and congruent with software freedom methodologies.  We suggest companies
+inspired by and congruent with software freedom methodologies.  Companies should
 establish such practices before building a product based on GPL'd
 software.\footnote{This document addresses compliance with GPLv2,
   GPLv3, LGPLv2, and LGPLv3.  Advice on avoiding the most common