www/licenses gpl-faq.html old-licenses/gpl-2.0-...

[Therese Godefroy]

CVSROOT:        /webcvs/www
Module name:    www
Changes by:     Therese Godefroy <th_g> 17/03/10 16:22:40

Modified files:
        licenses       : gpl-faq.html 
        licenses/old-licenses: gpl-2.0-faq.html 

Log message:
        Fix typos.

CVSWeb URLs:
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/gpl-faq.html?cvsroot=www&r1=1.229&r2=1.230
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/old-licenses/gpl-2.0-faq.html?cvsroot=www&r1=1.36&r2=1.37

Patches:
Index: gpl-faq.html
===================================================================
RCS file: /webcvs/www/www/licenses/gpl-faq.html,v
retrieving revision 1.229
retrieving revision 1.230
diff -u -b -r1.229 -r1.230
--- gpl-faq.html        10 Mar 2017 15:33:50 -0000      1.229
+++ gpl-faq.html        10 Mar 2017 21:22:38 -0000      1.230
@@ -1787,12 +1787,12 @@
 <dd><p>
 Please see this question <a href="#GPLPlugins">for determining when
 plug-ins and a main program are considered a single combined program
-and when they considered are separate works</a>.</p>
+and when they are considered separate works</a>.</p>
 
 <p> If the main program and the plugins are a single combined program then 
this means
 you must license the plug-in under the GPL or a GPL-compatible free
 software license and distribute it with source code in a GPL-compliant
-way. A main program that is a seperate from its plug-ins makes no
+way. A main program that is separate from its plug-ins makes no
 requirements for the plug-ins. </p></dd>
 
 
@@ -1827,7 +1827,7 @@
 <p>
 If they form a single combined program then the
 main program must be released under the GPL or a GPL-compatible free
-software license, and that the terms of the GPL must be followed when
+software license, and the terms of the GPL must be followed when
 the main program is distributed for use with these plug-ins.</p>
     
 <p>However, if they are separate works then the license of the plug-in
@@ -3896,7 +3896,7 @@
 
 <p class="unprintable">Updated:
 <!-- timestamp start -->
-$Date: 2017/03/10 15:33:50 $
+$Date: 2017/03/10 21:22:38 $
 <!-- timestamp end -->
 </p>
 </div>

Index: old-licenses/gpl-2.0-faq.html
===================================================================
RCS file: /webcvs/www/www/licenses/old-licenses/gpl-2.0-faq.html,v
retrieving revision 1.36
retrieving revision 1.37
diff -u -b -r1.36 -r1.37
--- old-licenses/gpl-2.0-faq.html       10 Mar 2017 19:12:08 -0000      1.36
+++ old-licenses/gpl-2.0-faq.html       10 Mar 2017 21:22:40 -0000      1.37
@@ -1336,12 +1336,12 @@
 <dd>
 Please see this question <a href="#GPLPlugins">for determining when
 plug-ins and a main program are considered a single combined program
-and when they considered are separate works</a>.
+and when they are considered separate works</a>.
 
 <p> If the main program and the plugins are a single combined program then 
this means
 you must license the plug-in under the GPL or a GPL-compatible free
 software license and distribute it with source code in a GPL-compliant
-way. A main program that is a seperate from its plug-ins makes no
+way. A main program that is separate from its plug-ins makes no
 requirements for the plug-ins. </p></dd>
 
 
@@ -1374,7 +1374,7 @@
 <p>
 If they form a single combined program then the
 main program must be released under the GPL or a GPL-compatible free
-software license, and that the terms of the GPL must be followed when
+software license, and the terms of the GPL must be followed when
 the main program is distributed for use with these plug-ins.</p>
     
 <p>However, if they are separate works then the license of the plug-in
@@ -2482,7 +2482,7 @@
 
 <p class="unprintable">Updated:
 <!-- timestamp start -->
-$Date: 2017/03/10 19:12:08 $
+$Date: 2017/03/10 21:22:40 $
 <!-- timestamp end -->
 </p>
 </div>