2005-08-08 Ralf Wildenhues <Ralf.Wildenhues@gmx.de> (tiny change)

	* README: Typos.

diff --git a/ChangeLog b/ChangeLog
index 5bac178..3e59f76 100644 (file)
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,7 @@
+2005-08-08  Ralf Wildenhues <Ralf.Wildenhues@gmx.de>  (tiny change)
+
+       * README: Typos.
+
 2005-08-02  Simon Josefsson  <jas@extundo.com>
 
        * modules/getdelim: New file.

diff --git a/README b/README
index 5c57d70..c3c593a 100644 (file)
--- 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.