diff options
author | Rob Landley <rob@landley.net> | 2007-03-13 18:34:52 +0000 |
---|---|---|
committer | Rob Landley <rob@landley.net> | 2007-03-13 18:34:52 +0000 |
commit | 69c54f803864cee503801f7e45b6c22e28db2df1 (patch) | |
tree | 8df332539044efc6c22084a8d0fb7c502b40aeaf | |
parent | 11b4fd555c8a016d02af89afadd6964fb23aa054 (diff) |
Be consistent about spelling. LGPL says "License" not "Licence", so go
with that. (Spotted by Xride on irc.)
-rw-r--r-- | docs/uclibc.org/FAQ.html | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/docs/uclibc.org/FAQ.html b/docs/uclibc.org/FAQ.html index 631944fd9..8cc1be20e 100644 --- a/docs/uclibc.org/FAQ.html +++ b/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 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 |