diff --git a/doc/src/sgml/ref/pg_rewind.sgml b/doc/src/sgml/ref/pg_rewind.sgml
index 94517d607d8..e6a5279215e 100644
--- a/doc/src/sgml/ref/pg_rewind.sgml
+++ b/doc/src/sgml/ref/pg_rewind.sgml
@@ -68,11 +68,10 @@ PostgreSQL documentation
    shut down soon after the divergence, this is not a problem, but if the
    target cluster ran for a long time after the divergence, the old WAL
    files might no longer be present. In that case, they can be manually
-   copied from the WAL archive to the <filename>pg_wal</> directory, or
-   fetched on startup by configuring <filename>recovery.conf</>.  The use of
-   <application>pg_rewind</> is not limited to failover, e.g.,  a standby
-   server can be promoted, run some write transactions, and then rewound
-   to become a standby again.
+   copied from the WAL archive to the <filename>pg_wal</> directory.
+   The use of <application>pg_rewind</> is not limited to
+   failover, e.g., a standby server can be promoted, run some write
+   transactions, and then rewound to become a standby again.
   </para>
 
   <para>