Correct all labels and references to use GPL version number in them.

gpl-lgpl.tex

@@ -477,7 +477,7 @@ available to subjugate users.  For example:
   computational ideas), they still ultimately exist.  As such, a software
   program might otherwise be seemly unrestricted, but a patent might read on
   the software and ruin everything for its users.\footnote{See
-  \S\S~\ref{gpl-implied-patent-grant},~\ref{GPLs7},~\ref{GPLv3s11} for more
+  \S\S~\ref{gpl-implied-patent-grant},~\ref{GPLv2s7},~\ref{GPLv3s11} for more
   discussion on how the patent system interacts with copyleft, and read
   Richard M.~Stallman's essay,
   \href{http://www.wired.com/opinion/2012/11/richard-stallman-software-patents/}{\textit{Let’s
@@ -765,6 +765,7 @@ shows how the text of the GPL we know has evolved to address more of the
 issues discussed earlier in \S~\ref{software-and-non-copyright}.
 
 \section{The GNU General Public License, Version 1}
+\label{GPLv1}
 
 In January 1989, the FSF announced that the GPL had been converted into a
 ``subroutine'' that could be reused not just for all FSF-copyrighted
@@ -968,7 +969,7 @@ GPLv2\@. In this chapter, we consider the first two sections: GPLv2 \S\S
 simplest rights that the user receives.
 
 \section{GPLv2 \S 0: Freedom to Run}
-\label{GPLs0}
+\label{GPLv2s0}
 
 \S 0, the opening section of GPLv2, sets forth that the work is governed by
 copyright law. It specifically points out that it is the ``copyright
@@ -983,7 +984,7 @@ covered by this License; they are outside its scope.
 \end{quote}
 In essence, the license governs \emph{only} those activities, and all other
 activities are unrestricted, provided that no other agreements trump GPLv2
-(which they cannot; see Sections~\ref{GPLs6} and~\ref{GPLs7}). This is
+(which they cannot; see Sections~\ref{GPLv2s6} and~\ref{GPLv2s7}). This is
 very important, because the Free Software community heavily supports
 users' rights to ``fair use'' and ``unregulated use'' of copyrighted
 material. GPLv2 asserts through this clause that it supports users' rights
@@ -1034,7 +1035,7 @@ even the GNU GPL --- can be blamed for this. Legislators and court
 opinions must give us guidance to decide the border cases.
 
 \section{GPLv2 \S 1: Verbatim Copying}
-\label{GPLs1}
+\label{GPLv2s1}
 
 GPLv2 \S 1 covers the matter of redistributing the source code of a program
 exactly as it was received. This section is quite straightforward.
@@ -1064,7 +1065,7 @@ proposed state-level UCITA bills (which have never obtained widespread
 adoption), there are few or no implied warranties with software.
 However, just to be on the safe side, GPL clearly disclaims them, and the
 GPL requires redistributors to keep the disclaimer very visible. (See
-Sections~\ref{GPLs11} and~\ref{GPLs12} of this tutorial for more on GPL's
+Sections~\ref{GPLv2s11} and~\ref{GPLv2s12} of this tutorial for more on GPL's
 warranty disclaimers.)
 
 Note finally that \S 1 begins to set forth the important defense of
@@ -1556,7 +1557,7 @@ receive this no-charge license. Namely, they receive it ``under the terms
 of this License,'' the GPL. When an entity \emph{chooses} to redistribute
 a derivative work of GPL'd software, the license of that whole derivative
 work must be GPL and only GPL\@. In this manner, \S 2(b) dovetails nicely
-with \S 6 (as discussed in Section~\ref{GPLs6} of this tutorial).
+with \S 6 (as discussed in Section~\ref{GPLv2s6} of this tutorial).
 
 \medskip
 
@@ -1908,7 +1909,7 @@ the parts of the license that keep the playing field clear so that \S\S
 0--3 can do their jobs.
 
 \section{GPLv2 \S 4: Termination on Violation}
-\label{GPLs4}
+\label{GPLv2s4}
 
 \S 4 is GPLv2's termination clause. Upon first examination, it seems
 strange that a license with the goal of defending users' and programmers'
@@ -1966,7 +1967,7 @@ would ever consider undertaking or even endorsing, it is a legal way for
 copyright holders to proceed.
 
 \section{GPLv2 \S 5: Acceptance, Copyright Style}
-\label{GPLs5}
+\label{GPLv2s5}
 
 \S 5 brings us to perhaps the most fundamental misconception and common
 confusion about GPLv2\@. Because of the prevalence of proprietary software,
@@ -2002,9 +2003,9 @@ freedom.
 \section{Using GPL Both as a Contract and Copyright License}
 
 \section{GPLv2 \S 6: GPL, My One and Only}
-\label{GPLs6}
+\label{GPLv2s6}
 
-A point that was glossed over in Section~\ref{GPLs4}'s discussion of \S 4
+A point that was glossed over in Section~\ref{GPLv2s4}'s discussion of \S 4
 was the irrevocable nature of the GPL\@. The GPLv2 is indeed irrevocable,
 and it is made so formally by \S 6.
 
@@ -2032,7 +2033,7 @@ only copyright license allowing you to copy, modify and distribute the
 software.
 
 \section{GPLv2 \S 7: ``Give Software Liberty or Give It Death!''}
-\label{GPLs7}
+\label{GPLv2s7}
 
 In essence, \S 7 is a verbosely worded way of saying for non-copyright
 systems what \S 6 says for copyright. If there exists any reason that a
@@ -2054,7 +2055,7 @@ Instead, it is inspiring patent holders to share their patents in the same
 freedom-defending way that they share their copyrighted works.
 
 \section{GPLv2 \S 8: Excluding Problematic Jurisdictions}
-\label{GPLs8}
+\label{GPLv2s8}
 
 \S 8 is rarely used by copyright holders. Its intention is that if a
 particular country, say Unfreedonia, grants particular patents or allows
@@ -2079,7 +2080,7 @@ of the GPLv2 handles administrivia and issues concerning warranties and
 liability.
 
 \section{GPLv2 \S 9: FSF as Stewards of GPL}
-\label{GPLs9}
+\label{GPLv2s9}
 
 FSF reserves the exclusive right to publish future versions of the GPL\@;
 \S 9 expresses this. While the stewardship of the copyrights on the body
@@ -2095,7 +2096,7 @@ a gigantic community depends on that freedom now. FSF hopes to take all
 stakeholders' opinions under advisement.
 
 \section{GPLv2 \S 10: Relicensing Permitted}
-\label{GPLs10}
+\label{GPLv2s10}
 
 \S 10 reminds the licensee of what is already implied by the nature of
 copyright law. Namely, the copyright holder of a particular software
@@ -2103,7 +2104,7 @@ program has the prerogative to grant alternative agreements under separate
 copyright licenses.
 
 \section{GPLv2 \S 11: No Warranty}
-\label{GPLs11}
+\label{GPLv2s11}
 
 All warranty disclaimer language tends to be shouted in all capital
 letters. Apparently, there was once a case where the disclaimer language
@@ -2124,7 +2125,7 @@ Finally, one important point to remember when reading \S 11 is that \S 1
 permits the sale of warranty as an additional service, which \S 11 affirms.
 
 \section{GPLv2 \S 12: Limitation of Liability}
-\label{GPLs12}
+\label{GPLv2s12}
 
 There are many types of warranties, and in some jurisdictions some of them
 cannot be disclaimed. Therefore, usually agreements will have both a
@@ -2672,7 +2673,7 @@ business and how to build business models around GPL'd software.
 
 \section{Using GPL'd Software In-House}
 
-As discussed in Sections~\ref{GPLs0} and~\ref{GPLs5} of this tutorial,
+As discussed in Sections~\ref{GPLv2s0} and~\ref{GPLv2s5} of this tutorial,
 the GPL only governs the activities of copying, modifying and
 distributing software programs that are not governed by the license.
 Thus, in FSF's view, simply installing the software on a machine and