diff --git a/gpl-lgpl.tex b/gpl-lgpl.tex
index bf08bb34c1fa20358611caa91af0c86f65326c8c..63a7283d86ff8cc4094d184a6da873be741008ac 100644
--- a/gpl-lgpl.tex
+++ b/gpl-lgpl.tex
@@ -2802,7 +2802,7 @@ in \S~\ref{GPLv2s3} of this tutorial), the distribution of object code may
 either be accompanied by the machine-readable source code, or it may be
 accompanied by a valid written offer to provide the machine-readable source
 code.  However, unlike in GPLv2, that offer cannot be exercised by any third
-party; rather, only those ``who possesses the object code'' it can exercised
+party; rather, only those ``who possesses the object code'' can exercise
 the offer.  (Note that this is a substantial narrowing of requirements of
 offer fulfillment, and is a wonderful counterexample to dispute claims that
 the GPLv3 has more requirements than GPLv2.)
@@ -2947,7 +2947,7 @@ GPLv3 drafting process.  However, companies and governments that use
 specialized or enterprise-level computer facilities reported that they
 actually \textit{want} their systems not to be under their own control.
 Rather than agreeing to this as a concession, or bowing to pressure, they ask
-for this as a \textit{preference}.  It is not clear that GPL should interfere
+for this as a \textit{preference}.  It is not clear that the GPL should interfere
 here, since the main problem lies elsewhere.
 
 While imposing technical barriers to modification is wrong regardless of