From e483e4ec42738f86c72e7b4aa5d3659c97c4393c Mon Sep 17 00:00:00 2001
From: Justin Pryzby <pryzbyj@telsasoft.com>
Date: Wed, 29 Dec 2021 16:02:16 -0600
Subject: [PATCH 19/33] v15 doc review: Add option -N/--no-sync to pg_upgrade
 3d5ffccb6df323f528cf870c26d0d0517ffe3eaa

Or is it intended to say 'unsynchronized' ?
---
 doc/src/sgml/ref/pgupgrade.sgml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/doc/src/sgml/ref/pgupgrade.sgml b/doc/src/sgml/ref/pgupgrade.sgml
index c5ce732ee98..a1745a2642c 100644
--- a/doc/src/sgml/ref/pgupgrade.sgml
+++ b/doc/src/sgml/ref/pgupgrade.sgml
@@ -139,7 +139,7 @@ PostgreSQL documentation
         of the upgraded cluster to be written safely to disk.  This option
         causes <command>pg_upgrade</command> to return without waiting, which
         is faster, but means that a subsequent operating system crash can leave
-        the synchronized data directory corrupt.  Generally, this option is
+        the data directory corrupt.  Generally, this option is
         useful for testing but should not be used on a production
         installation.
        </para>
-- 
2.17.1

