www/licenses gpl-faq.html

[Ineiev]

CVSROOT:        /web/www
Module name:    www
Changes by:     Ineiev <ineiev> 23/02/25 02:36:57

Modified files:
        licenses       : gpl-faq.html 

Log message:
        s,GPL3,GPLv3, for consistency.

CVSWeb URLs:
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/gpl-faq.html?cvsroot=www&r1=1.264&r2=1.265

Patches:
Index: gpl-faq.html
===================================================================
RCS file: /web/www/www/licenses/gpl-faq.html,v
retrieving revision 1.264
retrieving revision 1.265
diff -u -b -r1.264 -r1.265
--- gpl-faq.html        24 Feb 2023 21:32:17 -0000      1.264
+++ gpl-faq.html        25 Feb 2023 07:36:57 -0000      1.265
@@ -668,14 +668,14 @@
     <li><a href="#SystemLibraryException">Can I link a GPL program with
     a proprietary system library?</a></li>
 
-    <li><a href="#AGPLPL">Can I link GPL3-covered modules and
-    AGPL3-covered modules into one executable?</a></li>
+    <li><a href="#AGPLPL">Can I link GPLv3-covered modules and
+    AGPLv3-covered modules into one executable?</a></li>
 
-    <li><a href="#AGPLLibrary">Can I link a GPL3-covered program with
-    an AGPL3-covered library?</a></li>
+    <li><a href="#AGPLLibrary">Can I link a GPLv3-covered program with
+    an AGPLv3-covered library?</a></li>
 
-    <li><a href="#AGPLAndGPLLibrary">Can I link an AGPL3-covered program with
-    a GPL3-covered library?</a></li>
+    <li><a href="#AGPLAndGPLLibrary">Can I link an AGPLv3-covered program with
+    a GPLv3-covered library?</a></li>
 
     <li><a href="#GPLIncompatibleLibs">What legal issues come up if I
     use GPL-incompatible libraries with GPL software?</a></li>
@@ -1323,33 +1323,33 @@
 issue slightly differently, near the end of section 3.</p>
 </dd>
 
-<dt id="AGPLGPL">Can I link GPL3-covered modules and
-    AGPL3-covered modules into one executable?
+<dt id="AGPLGPL">Can I link GPLv3-covered modules and
+    AGPLv3-covered modules into one executable?
  <span class="anchor-reference-id">(<a
 href="#AGPLGPL">#AGPLGPL</a>)</span></dt>
 <dd><p>
-You can always link GPL3-covered modules with AGPL3-covered modules.
+You can always link GPLv3-covered modules with AGPLv3-covered modules.
 That is because each of these licenses explicitly permits linking with
 code under the other license.</p>
 </dd>
 
-<dt id="AGPLLibrary">Can I link a GPL3-covered program with
-    an AGPL3-covered library?
+<dt id="AGPLLibrary">Can I link a GPLv3-covered program with
+    an AGPLv3-covered library?
  <span class="anchor-reference-id">(<a
 href="#AGPLLibrary">#AGPLLibrary</a>)</span></dt>
 <dd><p>
-You can always <a href="#AGPLGPL">link GPL3-covered modules with
-AGPL3-covered modules</a>.  That is true regardless of whether some of
+You can always <a href="#AGPLGPL">link GPLv3-covered modules with
+AGPLv3-covered modules</a>.  That is true regardless of whether some of
 the modules are libraries.</p>
 </dd>
 
-<dt id="AGPLAndGPLLibrary">Can I link an AGPL3-covered program with
-    a GPL3-covered library?
+<dt id="AGPLAndGPLLibrary">Can I link an AGPLv3-covered program with
+    a GPLv3-covered library?
  <span class="anchor-reference-id">(<a
 href="#AGPLAndGPLLibrary">#AGPLAndGPLLibrary</a>)</span></dt>
 <dd><p>
-You can always <a href="#AGPLGPL">link GPL3-covered modules with
-AGPL3-covered modules</a>.  That is true regardless of whether some of
+You can always <a href="#AGPLGPL">link GPLv3-covered modules with
+AGPLv3-covered modules</a>.  That is true regardless of whether some of
 the modules are libraries.</p>
 </dd>
 
@@ -4044,7 +4044,7 @@
 
 <p class="unprintable">Updated:
 <!-- timestamp start -->
-$Date: 2023/02/24 21:32:17 $
+$Date: 2023/02/25 07:36:57 $
 <!-- timestamp end -->
 </p>
 </div>