From a54478a045f85509bfb7f714dea0c18dfd6c5bc1 Mon Sep 17 00:00:00 2001
From: Ian Barwick <ian@2ndquadrant.com>
Date: Tue, 12 May 2015 10:16:52 +0900
Subject: [PATCH] Documentation tweaks

---
 QUICKSTART.md | 3 ++-
 README.md     | 6 ++----
 2 files changed, 4 insertions(+), 5 deletions(-)

diff --git a/QUICKSTART.md b/QUICKSTART.md
index b2dbd3c0..72c222ff 100644
--- a/QUICKSTART.md
+++ b/QUICKSTART.md
@@ -21,7 +21,8 @@ Master setup
 	CREATE DATABASE repmgr_db OWNER repmgr_usr;
 	```
 
-  - configure `postgresql.conf` for replication (see above)
+  - configure `postgresql.conf` for replication (see README.md for sample
+    settings)
 
   - update `pg_hba.conf`, e.g.:
 
diff --git a/README.md b/README.md
index 2460f75c..b1e197b7 100644
--- a/README.md
+++ b/README.md
@@ -98,8 +98,8 @@ for details.
 
 ### PostgreSQL configuration
 
-The primary server needs to be configured for replication with the
-following settings in `postgresql.conf`:
+The primary server needs to be configured for replication with settings
+like the followingin `postgresql.conf`:
 
     # Allow read-only queries on standby servers. The number of WAL
     # senders should be larger than the number of standby servers.
@@ -121,8 +121,6 @@ following settings in `postgresql.conf`:
     archive_mode = on
     archive_command = 'cd .'
 
-    # You can also set additional replication parameters here, such as
-    # hot_standby_feedback or synchronous_standby_names.
 
 PostgreSQL 9.4 makes it possible to use replication slots, which means
 the value of wal_keep_segments need no longer be set. With 9.3, `repmgr`