diff --git a/doc/filelist.sgml b/doc/filelist.sgml
index 986eba3f..2d08b9b5 100644
--- a/doc/filelist.sgml
+++ b/doc/filelist.sgml
@@ -50,12 +50,12 @@
 <!ENTITY event-notifications  SYSTEM "event-notifications.sgml">
 <!ENTITY upgrading-repmgr  SYSTEM "upgrading-repmgr.sgml">
 
+<!ENTITY repmgrd-overview SYSTEM "repmgrd-overview.sgml">
 <!ENTITY repmgrd-automatic-failover SYSTEM "repmgrd-automatic-failover.sgml">
 <!ENTITY repmgrd-configuration SYSTEM "repmgrd-configuration.sgml">
 <!ENTITY repmgrd-demonstration SYSTEM "repmgrd-demonstration.sgml">
 <!ENTITY repmgrd-monitoring SYSTEM "repmgrd-monitoring.sgml">
 <!ENTITY repmgrd-degraded-monitoring SYSTEM "repmgrd-degraded-monitoring.sgml">
-<!ENTITY repmgrd-cascading-replication SYSTEM "repmgrd-cascading-replication.sgml">
 <!ENTITY repmgrd-network-split SYSTEM "repmgrd-network-split.sgml">
 <!ENTITY repmgrd-witness-server SYSTEM "repmgrd-witness-server.sgml">
 <!ENTITY repmgrd-pausing SYSTEM "repmgrd-pausing.sgml">
diff --git a/doc/repmgr.sgml b/doc/repmgr.sgml
index 2d97709d..beebefbd 100644
--- a/doc/repmgr.sgml
+++ b/doc/repmgr.sgml
@@ -80,10 +80,10 @@
 
  <part id="using-repmgrd">
   <title>Using repmgrd</title>
+  &repmgrd-overview;
   &repmgrd-automatic-failover;
   &repmgrd-configuration;
   &repmgrd-demonstration;
-  &repmgrd-cascading-replication;
   &repmgrd-network-split;
   &repmgrd-witness-server;
   &repmgrd-pausing;
diff --git a/doc/repmgrd-automatic-failover.sgml b/doc/repmgrd-automatic-failover.sgml
index ee3556eb..2695881a 100644
--- a/doc/repmgrd-automatic-failover.sgml
+++ b/doc/repmgrd-automatic-failover.sgml
@@ -13,5 +13,35 @@
   providing monitoring information about the state of each standby.
  </para>
 
+  <sect1 id="cascading-replication">
+ <indexterm>
+   <primary>repmgrd</primary>
+   <secondary>cascading replication</secondary>
+ </indexterm>
+
+ <indexterm>
+   <primary>cascading replication</primary>
+   <secondary>repmgrd</secondary>
+ </indexterm>
+
+ <title>repmgrd and cascading replication</title>
+ <para>
+  Cascading replication - where a standby can connect to an upstream node and not
+  the primary server itself - was introduced in PostgreSQL 9.2. &repmgr; and
+  <application>repmgrd</application> support cascading replication by keeping track of the relationship
+  between standby servers - each node record is stored with the node id of its
+  upstream ("parent") server (except of course the primary server).
+ </para>
+ <para>
+  In a failover situation where the primary node fails and a top-level standby
+  is promoted, a standby connected to another standby will not be affected
+  and continue working as normal (even if the upstream standby it's connected
+  to becomes the primary node). If however the node's direct upstream fails,
+  the &quot;cascaded standby&quot; will attempt to reconnect to that node's parent
+  (unless <varname>failover</varname> is set to <literal>manual</literal> in
+  <filename>repmgr.conf</filename>).
+ </para>
+
+  </sect1>
 
 </chapter>
diff --git a/doc/repmgrd-cascading-replication.sgml b/doc/repmgrd-cascading-replication.sgml
deleted file mode 100644
index 7d4dfbc3..00000000
--- a/doc/repmgrd-cascading-replication.sgml
+++ /dev/null
@@ -1,24 +0,0 @@
-<chapter id="repmgrd-cascading-replication">
- <indexterm>
-   <primary>repmgrd</primary>
-   <secondary>cascading replication</secondary>
- </indexterm>
-
- <title>repmgrd and cascading replication</title>
- <para>
-  Cascading replication - where a standby can connect to an upstream node and not
-  the primary server itself - was introduced in PostgreSQL 9.2. &repmgr; and
-  <application>repmgrd</application> support cascading replication by keeping track of the relationship
-  between standby servers - each node record is stored with the node id of its
-  upstream ("parent") server (except of course the primary server).
- </para>
- <para>
-  In a failover situation where the primary node fails and a top-level standby
-  is promoted, a standby connected to another standby will not be affected
-  and continue working as normal (even if the upstream standby it's connected
-  to becomes the primary node). If however the node's direct upstream fails,
-  the &quot;cascaded standby&quot; will attempt to reconnect to that node's parent
-  (unless <varname>failover</varname> is set to <literal>manual</literal> in
-  <filename>repmgr.conf</filename>).
- </para>
-</chapter>
diff --git a/doc/repmgrd-configuration.sgml b/doc/repmgrd-configuration.sgml
index 1afdc618..da692e80 100644
--- a/doc/repmgrd-configuration.sgml
+++ b/doc/repmgrd-configuration.sgml
@@ -406,9 +406,6 @@
           </listitem>
         </varlistentry>
 
-
-
-
       </variablelist>
 
       <para>
diff --git a/doc/repmgrd-overview.sgml b/doc/repmgrd-overview.sgml
new file mode 100644
index 00000000..1d2d7fae
--- /dev/null
+++ b/doc/repmgrd-overview.sgml
@@ -0,0 +1,17 @@
+
+<chapter id="repmgrd-overview" xreflabel="Overview of repmgrd">
+ <indexterm>
+   <primary>repmgrd</primary>
+   <secondary>overview</secondary>
+ </indexterm>
+
+ <title>repmgrd overview</title>
+
+ <para>
+   <application>repmgrd</application> (&quot;<literal>replication manager daemon</literal>&quot;)
+   is a management and monitoring daemon which runs
+   on each node in a replication cluster. It can automate actions such as
+   failover and updating standbys to follow the new primary, as well as
+   providing monitoring information about the state of each standby.
+ </para>
+</chapter>