[GNUnet-SVN] r16804 - gnunet-update

[gnunet]

Author: grothoff
Date: 2011-09-13 14:17:47 +0200 (Tue, 13 Sep 2011)
New Revision: 16804

Modified:
   gnunet-update/README
Log:
english

Modified: gnunet-update/README
===================================================================
--- gnunet-update/README        2011-09-13 12:04:42 UTC (rev 16803)
+++ gnunet-update/README        2011-09-13 12:17:47 UTC (rev 16804)
@@ -24,11 +24,11 @@
 as architecture, OS, etc. as meta-data. Meta-data also includes the
 version information of the dependencies.
 
-When a peer wants to update its installation. It searches in the
+When a peer wants to update its installation, it searches in the
 network for a suitable update package and downloads the package's
 meta-data. From the meta-data, it determines which dependencies are
 not satisfied locally. It then downloads those dependencies from peers
-and installs them. It then proceeds to in the new GNUnet
+and installs them. It then proceeds to the actual new GNUnet
 installation.
 
 
@@ -38,14 +38,14 @@
 There could be some problems in the way the dependencies are
 handled. The dependencies are tracked using their version
 information. Although most of the libraries follow the version
-numbering descibed by libtool. Some, e.g: libc, may not have the
-version numbers as specified. Such libraries must be explicitly
+numbering descibed by libtool. Some, e.g. libc, may not include
+version numbers as recommended by libtool. Such libraries must be explicitly
 handled. In case of libc only one number is present in its version. We 
 deem a libc library dependency compatible only if there is a libc with
 the same version number installed on the system.  
 
 Another issue may be present with certain shared object files which
-may not have any version information, e.g: plugins in GNUnet. Again,
+may not have any version information, e.g. plugins in GNUnet. Again,
 these objects have to be explicitly defined for the software to
 consider them in the updates.