From b03ca7f6d5eb871da0d4287aa1fab5ea77b703d5 Mon Sep 17 00:00:00 2001 From: "Bradley M. Kuhn" Date: Thu, 20 Mar 2014 21:08:50 -0400 Subject: [PATCH] Wordsmith paragraph --- compliance-guide.tex | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/compliance-guide.tex b/compliance-guide.tex index e9ca2f4..e60d189 100644 --- a/compliance-guide.tex +++ b/compliance-guide.tex @@ -102,13 +102,13 @@ when a violation occurs. \label{best-practices} Unlike highly permissive licenses (such as the ISC license), which -typically only require preservation of copyright notices, the GPL places a -number of important requirements upon licensees. These requirements are +typically only require preservation of copyright notices, licensees face many +important requirements from the GPL. These requirements are carefully designed to uphold certain values and standards of the software freedom community. While the GPL's requirements may appear initially counter-intuitive to those more familiar with proprietary software -licenses, by comparison its terms are in fact clear and favorable to -licensees. The terms of the GPL actually simplify compliance when +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