Version 2.0release-2.0

1 files changed, 10 insertions, 9 deletions

diff --git a/README b/README
index 5ee4f46..93f6f7e 100644
--- a/README
+++ b/README
@@ -134,19 +134,20 @@ This will build the module.  Finally, do the following command as root:
   
   make install
 
 * Testing
 
 Testing the module requires access to an SQL database which will be
-populated with the test data.  Before running the test suite, you
-have to create the database, or the user (role), which is able to
-create it.  For example, for MySQL:
+populated with the test data.  You can either create that database
+yourself, or let the testsuite create it.  The easiest way is to
+create a user (role), which is able to create the database.  For
+example, in MySQL:
 
    GRANT ALL PRIVILEGES on dbrw_test.* to dbrw_test@localhost;
 
-Or, for PostgreSQL:
+Or, in PostgreSQL:
 
    CREATE ROLE dbrw_test WITH LOGIN CREATEDB
    
 Once done, supply the SQL credentials and the database name with
 extra arguments to `make check', as shown in the example below:
 
@@ -185,13 +186,13 @@ Name or IP address of SQL server.  Defaults to localhost.
 Database user.
 
 ** DBRW_TEST_PASS
 
 Password to connect to the server (if necessary).
 
-Ideally, the tests should succeed.  If they don't, that don't
+Ideally, the tests should succeed.  If they don't, that does not
 necessarily indicates a problem in the module:
 
 The tests will be skipped if the supplied credentials are insufficient
 to access the SQL server. 
 
 If the first test fails, and all subsequent ones are marked as
@@ -203,27 +204,27 @@ run `make -C tests clean' (see below) and re-run `make check'.
 If all tests are marked as "expected failure", then the testsuite
 uses the cached data from the previous run, which wasn't able to
 create or populate the test database.  In this case, act as described
 above.
 
 Finally, if some or all of the tests were marked as failed, that
-indicates a bug in the module itself, or in the test suite.  In this
-case, the file testsuite.log will contain detailed logs.  Additional
+indicates a bug either in the module itself, or in the test suite.  In
+this case, the file testsuite.log will contain detailed logs.  Additional
 information can then be found in the directory testsuite.dir.  Please
 send these data to the developer.
 
-Notice that the testsuite tries to create the database only once.
+Notice, that the testsuite tries to create the database only once.
 Subsequent invocations of `make check' will use the existing database.
 Similarly, if it failed to create the database, the failure will be
 memorized and all subsequent runs will just skip all checks.  To clear
 the state, run `make clean' in the directory tests, e.g.:
 
   make -C tests clean
   make check
 
-You can also supply the database credentials in invocation of
+You can also supply the database credentials to invocation of
 configure:
   
   ./configure --with-varnish-source=/usr/src/varnish-3.0.1\
               DBRW_TEST_DATABASE=dbrw_test\
 	      DBRW_TEST_USER=dbrw_test