From b691a1bd1063c083c205f344a028ea4c41fc146d Mon Sep 17 00:00:00 2001
From: Ian Barwick <ian@2ndquadrant.com>
Date: Fri, 20 Mar 2020 17:24:41 +0900
Subject: [PATCH] doc: minor fixes to pg_upgrade notes

---
 doc/upgrading-repmgr.xml | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/doc/upgrading-repmgr.xml b/doc/upgrading-repmgr.xml
index 0e07a07b..c8da814f 100644
--- a/doc/upgrading-repmgr.xml
+++ b/doc/upgrading-repmgr.xml
@@ -269,7 +269,7 @@ ALTER EXTENSION repmgr UPDATE</programlisting>
 	</para>
   </tip>
 
-  <sect2 id="upgrading-pg-upgrade-standby" xreflabel="pg_upgrade and repmgr">
+  <sect2 id="upgrading-pg-upgrade-standby" xreflabel="pg_upgrade and upgrading standbys">
     <title>Upgrading standbys with pg_upgrade and rsync</title>
     <para>
       If you are intending to upgrade a standby using the <command>rsync</command> method described
@@ -278,7 +278,7 @@ ALTER EXTENSION repmgr UPDATE</programlisting>
       before starting the standby.
     </para>
     <para>
-      Use <link linkend="repmgr-standby-clone">repmgr standby clone --recovery-conf-only</link> to generate
+      Use <link linkend="repmgr-standby-clone">repmgr standby clone --replication-conf-only</link> to generate
       the correct replication configuration.
     </para>