diff --git a/doc/quickstart.sgml b/doc/quickstart.sgml
index b64d06f0..6d2adb4f 100644
--- a/doc/quickstart.sgml
+++ b/doc/quickstart.sgml
@@ -103,11 +103,11 @@
# ignores archiving. Use something more sensible.
archive_command = '/bin/true'
- # If you have configured `pg_basebackup_options`
- # in `repmgr.conf` to include the setting `--xlog-method=fetch` (from
- # PostgreSQL 10 `--wal-method=fetch`), *and* you have not set
- # `restore_command` in `repmgr.conf`to fetch WAL files from another
- # source such as Barman, you'll need to set `wal_keep_segments` to a
+ # If you have configured "pg_basebackup_options"
+ # in "repmgr.conf" to include the setting "--xlog-method=fetch" (from
+ # PostgreSQL 10 "--wal-method=fetch"), *and* you have not set
+ # "restore_command" in "repmgr.conf"to fetch WAL files from another
+ # source such as Barman, you'll need to set "wal_keep_segments" to a
# high enough value to ensure that all WAL files generated while
# the standby is being cloned are retained until the standby starts up.
#
@@ -121,6 +121,11 @@
include 'postgresql.replication.conf.
+
+ Additionally, if you are intending to use pg_rewind,
+ and the cluster was not initialised using data checksums, you may want to consider enabling
+ wal_log_hints; for more details see .
+
diff --git a/doc/repmgr-node-rejoin.sgml b/doc/repmgr-node-rejoin.sgml
index 084f8b44..d81531fe 100644
--- a/doc/repmgr-node-rejoin.sgml
+++ b/doc/repmgr-node-rejoin.sgml
@@ -69,7 +69,7 @@
-
+
Using pg_rewind
repmgr node rejoin can optionally use pg_rewind to re-integrate a