diff --git a/FAQ.md b/FAQ.md
index e2130d5d..1512d4e7 100644
--- a/FAQ.md
+++ b/FAQ.md
@@ -8,11 +8,11 @@ General
 
 - What's the difference between the repmgr versions?
 
-  repmgr v3 builds on the improved replication facilities added
+  repmgr 3.x builds on the improved replication facilities added
   in PostgreSQL 9.3, as well as improved automated failover support
   via `repmgrd`, and is not compatible with PostgreSQL 9.2 and earlier.
 
-  repmgr v2 supports PostgreSQL 9.0 onwards. While it is compatible
+  repmgr 2.x supports PostgreSQL 9.0 onwards. While it is compatible
   with  PostgreSQL 9.3 and later, we recommend repmgr v3.
 
 - What's the advantage of using replication slots?
@@ -29,7 +29,7 @@ General
 - How many replication slots should I define in `max_replication_slots`?
 
   Normally at least same number as the number of standbys which will connect
-  to the node. Note that changes to  `max_replication_slots` require a server
+  to the node. Note that changes to `max_replication_slots` require a server
   restart to take effect, and as there is no particular penalty for unused
   replication slots, setting a higher figure will make adding new nodes
   easier.
diff --git a/README.md b/README.md
index d88f9b38..2460f75c 100644
--- a/README.md
+++ b/README.md
@@ -48,20 +48,21 @@ automatic failover.
 Requirements
 ------------
 
-`repmgr` is developed and tested on Linux, but it should work on any
-UNIX-like system which PostgreSQL itself supports.
+`repmgr` is developed and tested on Linux and OS X, but it should work
+on any UNIX-like system which PostgreSQL itself supports.
 
 All nodes must be running the same major version of PostgreSQL, and we
 recommend that they also run the same minor version. This version of
 `repmgr` (v3) supports PostgreSQL 9.3 and 9.4.
 
-Earlier versions of `repmgr` required password-less SSH access between
+Earlier versions of `repmgr` needed password-less SSH access between
 nodes in order to clone standby servers using `rsync`. `repmgr 3` can
-use `pg_basebackup` instead in most circumstances; ssh is not needed.
+use `pg_basebackup` instead in most circumstances; ssh is not required.
 
 You will need to use rsync only if your PostgreSQL configuration files
-are outside your data directory (as on Debian). See the `SSH-RSYNC.md`
-file for details on configuring password-less SSH between your nodes.
+are outside your data directory (as on Debian) and you wish these to
+be copied by `repmgr`. See the `SSH-RSYNC.md` file for details on
+configuring password-less SSH between your nodes.
 
 Installation
 ------------
@@ -110,7 +111,7 @@ following settings in `postgresql.conf`:
     # How much WAL to retain on the primary to allow a temporarily
     # disconnected standby to catch up again. The larger this is, the
     # longer the standby can be disconnected. This is needed only in
-    # 9.3; in 9.4, use replication slots instead (see below).
+    # 9.3; in 9.4, replication slots can be used instead (see below).
 
     wal_keep_segments = 5000