www/licenses gpl-howto.html

[Ineiev]

CVSROOT:        /web/www
Module name:    www
Changes by:     Ineiev <ineiev> 17/08/17 14:21:04

Modified files:
        licenses       : gpl-howto.html 

Log message:
        Fix typos.

CVSWeb URLs:
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/gpl-howto.html?cvsroot=www&r1=1.48&r2=1.49

Patches:
Index: gpl-howto.html
===================================================================
RCS file: /web/www/www/licenses/gpl-howto.html,v
retrieving revision 1.48
retrieving revision 1.49
diff -u -b -r1.48 -r1.49
--- gpl-howto.html      17 Aug 2017 18:08:47 -0000      1.48
+++ gpl-howto.html      17 Aug 2017 18:21:03 -0000      1.49
@@ -28,7 +28,7 @@
 
 <ul>
 <li>Get a copyright disclaimer from your employer or school.</li>
-<li>Give each file the proper copyright notices(s).</li>
+<li>Give each file the proper copyright notices.</li>
 <li>Add a COPYING file with a copy of the GNU GPL or GNU AGPL.</li>
 <li>Also add a COPYING.LESSER file with a copy of the GNU LGPL, if you
 use that.</li>
@@ -69,7 +69,7 @@
 writing the program</a> to reduce resistance.</p>
 
 <p>If you work, the best time to negotiate permission to release free
-software is <em>when negotiating your employment agreement.</em></p>
+software is <em>when negotiating your employment agreement</em>.</p>
 
 <h3>The copyright notice</h3>
 
@@ -99,7 +99,7 @@
 license, copy their copyright notices too.  Put all the copyright
 notices for a file together, right near the top of the file.</p>
 
-<h3>The license file(s)</h3>
+<h3>The license files</h3>
 
 <p>You should also include a copy of the license itself somewhere in the
 distribution of your program.  All programs, whether they are released
@@ -296,7 +296,7 @@
 
 <p class="unprintable">Updated:
 <!-- timestamp start -->
-$Date: 2017/08/17 18:08:47 $
+$Date: 2017/08/17 18:21:03 $
 <!-- timestamp end -->
 </p>
 </div>