doc: clarify behavior of pg_upgrade's clone mode

Be more precise about the benefits of using clone mode.

diff --git a/doc/src/sgml/ref/pgupgrade.sgml b/doc/src/sgml/ref/pgupgrade.sgml
index 0c4b16d32ce1efa4ee7331e3e1f652056ce2b247..26e3f9ea2b9d06e5a24e5a11021ce100712d7d86 100644 (file)
--- a/doc/src/sgml/ref/pgupgrade.sgml
+++ b/doc/src/sgml/ref/pgupgrade.sgml
@@ -382,11 +382,11 @@ NET STOP postgresql-&majorversion;
      requires that the old and new cluster data directories be in the
      same file system.  (Tablespaces and <filename>pg_wal</filename> can be on
      different file systems.)
-     The clone mode provides the same speed and disk space advantages but will
-     not leave the old cluster unusable after the upgrade.  The clone mode
-     also requires that the old and new data directories be in the same file
-     system.  The clone mode is only available on certain operating systems
-     and file systems.
+     Clone mode provides the same speed and disk space advantages but
+     does not cause the old cluster to be unusable once the new cluster
+     is started.  Clone mode also requires that the old and new data
+     directories be in the same file system.  This mode is only available
+     on certain operating systems and file systems.
     </para>
 
     <para>