diff --git a/doc/repmgr-standby-clone.xml b/doc/repmgr-standby-clone.xml
index f87269c0..4aecc331 100644
--- a/doc/repmgr-standby-clone.xml
+++ b/doc/repmgr-standby-clone.xml
@@ -205,7 +205,7 @@
 
    <para>
      &repmgr; supports standbys cloned by another method (e.g. using <application>barman</application>'s
-     <command><ulink url="http://docs.pgbarman.org/release/2.5/#recover">barman recover</ulink></command> command).
+     <command><ulink url="https://docs.pgbarman.org/#recover">barman recover</ulink></command> command).
    </para>
    <para>
      To integrate the standby as a &repmgr; node, once the standby has been cloned,
diff --git a/doc/repmgr-standby-register.xml b/doc/repmgr-standby-register.xml
index a6df8eff..40f9f75f 100644
--- a/doc/repmgr-standby-register.xml
+++ b/doc/repmgr-standby-register.xml
@@ -108,7 +108,8 @@
     <title>Registering a node not cloned by repmgr</title>
     <para>
       If you've cloned a standby using another method (e.g. <application>barman</application>'s
-     <command>barman recover</command> command), register the node as detailed in section
+     <command><ulink url="https://docs.pgbarman.org/#recover">barman recover</ulink></command>
+     command), register the node as detailed in section
      <xref linkend="repmgr-standby-register-inactive-node"/> then execute
      <link linkend="repmgr-standby-create-recovery-conf">repmgr standby clone --recovery-conf-only</link>
      to generate the appropriate replication configuration.