@@ -122,7 +122,7 @@ gives them permission to engage in these activities governed by copyright law.
\section{Ongoing Violations}
In conjunction with \S 4's termination of violators' rights, there is
one final industry fact added to the mix: rarely, does one engage in a
one final industry fact added to the mix: rarely does one engage in a
single, solitary act of copying, distributing or modifying software.
Almost always, a violator will have legitimately acquired a copy of a
GPL'd program, either making modifications or not, and then begun
@@ -337,7 +337,7 @@ This case introduces a number of concepts regarding GPL enforcement.
\begin{enumerate}
\item {\bf Enforcement should not begin until the evidence is confirmed.}
Most companies who distribute GPL'd software do so in compliance, and at
Most companies that distribute GPL'd software do so in compliance, and at
times, violation reports are mistaken. Even with extensive efforts in
GPL education, many users do not fully understand their rights and the
obligations that companies have. By working through the investigation
@@ -636,7 +636,7 @@ did so, and the violation was resolved.
the GPL are ignored. If companies do not want to release source code
for some reason, then they should not base the work on GPL'd software.
No external argument for noncompliance can hold weight if the work as
whole is indeed a derivative work of a GPL'd program.
a whole is indeed a derivative work of a GPL'd program.
The ``security concerns'' argument is often floated as a reason to keep
software proprietary, but the computer security community has on