Make the reference to pg_rewind in failover section a link.

diff --git a/doc/src/sgml/high-availability.sgml b/doc/src/sgml/high-availability.sgml
index 7c5b576b7152f2ef64880c14afb49303f07ef697..a17f55545c92842440bfe906e8149bab322c43b4 100644 (file)
--- a/doc/src/sgml/high-availability.sgml
+++ b/doc/src/sgml/high-availability.sgml
@@ -1272,7 +1272,7 @@ primary_slot_name = 'node_a_slot'
     and might stay down.  To return to normal operation, a standby server
     must be recreated,
     either on the former primary system when it comes up, or on a third,
-    possibly new, system. The <application>pg_rewind</> utility can be
+    possibly new, system. The <xref linkend="app-pgrewind"> utility can be
     used to speed up this process on large clusters.
     Once complete, the primary and standby can be
     considered to have switched roles. Some people choose to use a third