diff --git a/compliance-guide.tex b/compliance-guide.tex
index 256e5dd7e92fc1ffd7f32ff53aad2d8f86bdf735..4f6a580113f022d115249706fc9fee45c8418b15 100644
--- a/compliance-guide.tex
+++ b/compliance-guide.tex
@@ -1209,15 +1209,15 @@ particular interest.
 
 GPL compliance and LGPL compliance mostly involve the same issues.  As we
 discussed in \S~\ref{derivative-works}, questions of modified versions of
-software are highly fact-dependant and cannot be easily addressed in any
+software are highly fact-dependent and cannot be easily addressed in any
 overview document.  The LGPL adds some additional complexity to the
 analysis.  Namely, the various LGPL versions permit proprietary licensing
-of certain types of modified versions.  These issues are well beyond the
-scope of this document, but as a rule of thumb, once you have determined
+of certain types of modified versions.  These issues are discussed in greater
+detail in Chapter~\ref{LGPLv2} and~\ref{LGPLv3}.  However, as a rule of thumb, once you have determined
 (in accordance with LGPLv3) what part of the work is the ``Application''
 and what portions of the source are ``Minimal Corresponding Source'', then
-you can usually proceed to follow the GPL compliance rules that we
-discussed, replacing our discussion of ``Corresponding Source'' with
+you can usually proceed to follow the GPL compliance rules that
+discussed above, replacing our discussion of ``Corresponding Source'' with
 ``Minimal Corresponding Source''.
 
 LGPL also requires that you provide a mechanism to combine the Application