svn commit: trunk/uClibc/docs/uclibc.org

[landley at uclibc.org]

Author: landley
Date: 2007-03-13 11:34:52 -0700 (Tue, 13 Mar 2007)
New Revision: 18086

Log:
Be consistent about spelling.  LGPL says "License" not "Licence", so go 
with that.  (Spotted by Xride on irc.)


Modified:
   trunk/uClibc/docs/uclibc.org/FAQ.html


Changeset:
Modified: trunk/uClibc/docs/uclibc.org/FAQ.html
===================================================================
--- trunk/uClibc/docs/uclibc.org/FAQ.html	2007-03-13 13:01:14 UTC (rev 18085)
+++ trunk/uClibc/docs/uclibc.org/FAQ.html	2007-03-13 18:34:52 UTC (rev 18086)
@@ -173,9 +173,9 @@
 
     No, you do not need to give away your application source code just because
     you use uClibc and/or run on Linux.  uClibc is licensed under the <a
-    href="http://www.gnu.org/copyleft/lesser.html">Lesser GPL</a> licence, just
-    like the GNU C library (glibc).  Please read this licence, or have a lawyer
-    read this licence if you have any questions.  Here is my brief summary...
+    href="http://www.gnu.org/copyleft/lesser.html">Lesser GPL</a> license, just
+    like the GNU C library (glibc).  Please read this license, or have a lawyer
+    read this license if you have any questions.  Here is my brief summary...
     Using shared libraries makes complying with the license easy.  You can
     distribute a closed source application which is linked with an unmodified
     uClibc shared library.  In this case, you do not need to give away any