typos/extra words

gpl-lgpl.tex

@@ -2142,7 +2142,7 @@ Chapters~\ref{run-and-verbatim} and~\ref{source-and-binary} presented the
 core freedom-defending provisions of GPLv2\@, which are in GPLv2~\S\S0--3.
 GPLv2\S\S~4--7 of the GPLv2 are designed to ensure that GPLv2~\S\S0--3 are
 not infringed, are enforceable, are kept to the confines of copyright law but
-also  not trumped by other copyright agreements or components of other
+also not trumped by other copyright agreements or components of other
 entirely separate legal systems.  In short, while GPLv2~\S\S0--3 are the parts
 of the license that defend the freedoms of users and programmers,
 GPLv2~\S\S4--7 are the parts of the license that keep the playing field clear
@@ -2390,7 +2390,7 @@ copyright licenses.
 \section{GPLv2~\S11: No Warranty}
 \label{GPLv2s11}
 
-Most warranty disclaimer language shout at you.  The
+Most warranty disclaimer language shouts at you.  The
 \href{http://www.law.cornell.edu/ucc/2/2-316}{Uniform Commercial
   Code~\S2-316} requires that disclaimers of warranty be ``conspicuous''.
 There is apparently general acceptance that \textsc{all caps} is the
@@ -2398,7 +2398,7 @@ preferred way to make something conspicuous, and that has over decades worked
 its way into the voodoo tradition of warranty disclaimer writing.
 
 That said, there is admittedly some authority under USA law suggesting that
-effective warranty disclaimers that conspicuousness can be established by
+conspicuousness can be established by
 capitalization and is absent when a disclaimer has the same typeface as the
 terms surrounding it (see \textit{Stevenson v.~TRW, Inc.}, 987 F.2d 288, 296
 (5th Cir.~1993)).  While GPLv3's drafters doubted that such authority would