Browse Source

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

Rob Landley 18 years ago
parent
commit
69c54f8038
1 changed files with 3 additions and 3 deletions
  1. 3 3
      docs/uclibc.org/FAQ.html

+ 3 - 3
docs/uclibc.org/FAQ.html

@@ -173,9 +173,9 @@ How could it be smaller and not suck?</a></h2>
 
 
     No, you do not need to give away your application source code just because
     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
     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
     Using shared libraries makes complying with the license easy.  You can
     distribute a closed source application which is linked with an unmodified
     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
     uClibc shared library.  In this case, you do not need to give away any