summaryrefslogtreecommitdiff
path: root/README
diff options
context:
space:
mode:
authorSimon Josefsson <simon@josefsson.org>2005-08-08 13:58:29 +0000
committerSimon Josefsson <simon@josefsson.org>2005-08-08 13:58:29 +0000
commit18437eed37fb12272d954b7f28e51ad5e391e63a (patch)
treeb32eda8dfced2c99c34b34772f5cb2af2a2772a5 /README
parent2575e06437b633b04865b8caace118c23d480b6e (diff)
downloadgnulib-18437eed37fb12272d954b7f28e51ad5e391e63a.tar.gz
2005-08-08 Ralf Wildenhues <Ralf.Wildenhues@gmx.de> (tiny change)
* README: Typos.
Diffstat (limited to 'README')
-rw-r--r--README6
1 files changed, 3 insertions, 3 deletions
diff --git a/README b/README
index 5c57d7071a..c3c593abf5 100644
--- a/README
+++ b/README
@@ -41,14 +41,14 @@ you should probably consider packaging it as a separate library.
License
-------
-GNULib contain code both under GPL and LGPL. Because several packages
+GNULib contains code both under GPL and LGPL. Because several packages
that use GNULib are GPL, the files state they are licensed under GPL.
However, to support LGPL projects as well, you may use some of the
files under LGPL. The "License:" information in the files under
-modules/ clarify the real license that apply to source.
+modules/ clarifies the real license that applies to the module source.
Keep in mind that if you submit patches to files in GNULib, you should
-license them under a compatible license. Which means that sometimes
+license them under a compatible license, which means that sometimes
the contribution will have to be LGPL, if the original file is
available under LGPL via a "License: LGPL" information in the
projects' modules/ file.