A couple of wording fixes suggested by Bruce

docs/dev_install.rst

@@ -10,8 +10,8 @@ with. Here's a quick step-by-step on how to do that:
    and *markdown* (these are python libraries, so prefix python- for Debian
    packages, for example).
 #. Make sure you have downloaded and installed PostgreSQL (tested only
-   with *version 8.4* and later, but doesn't use any functionality that
-   didn't exist for quite a while by then).
+   with *version 8.4* and later, but doesn't use any advanced
+   functionality so it should work with other versions)
 
 #. Create a database in your PostgreSQL installation called pgweb
    (other names are of course possible, but that's the standard one)

docs/django.rst

@@ -17,9 +17,9 @@ Database access
 ---------------
 In all places where database access is simple, the django ORM is used
 to access the data. In the few places where more advanced queries are
-necessary, direct queries to the database are used. There exists no
+necessary, direct queries to the database are used. There is no
 intention to keep the database structure independent of database
-used - it's all designed to use PostgreSQL. Therefor, using PostgreSQL
+used - it's all designed to use PostgreSQL. Therefore, using PostgreSQL
 specific syntax in these direct queries is not a problem.
 
 Module split

docs/frontend.rst

@@ -40,7 +40,7 @@ django project can override this default, by specifying the
 "Cache-control: s-maxage=xxx" http header on the response. This is
 done by using the @cache() decorator on the view method. Caching
 should be kept lower for pages that have frequently updating data,
-such as the front page or the result of surveys page.
+such as the front page or the survey results page.
 
 Finally, there is a form on the admin web interface that lets the
 administrator manually expire specific pages using a varnish process