From 45bd11d30d67b7b4d2854c51660fcff0bc3a3d14 Mon Sep 17 00:00:00 2001
From: Peter Smith <peter.b.smith@fujitsu.com>
Date: Tue, 30 Mar 2021 18:30:18 +1100
Subject: [PATCH v1] Use consistent terminology for tablesync slots.

Some pages called these tablesync slots.
Some pages called there table synchronization slots.

For consistency try make them all the same as "tablesync slots"
---
 doc/src/sgml/logical-replication.sgml   | 6 +++---
 doc/src/sgml/ref/drop_subscription.sgml | 4 ++--
 2 files changed, 5 insertions(+), 5 deletions(-)

diff --git a/doc/src/sgml/logical-replication.sgml b/doc/src/sgml/logical-replication.sgml
index e95d446..ea94daf 100644
--- a/doc/src/sgml/logical-replication.sgml
+++ b/doc/src/sgml/logical-replication.sgml
@@ -252,9 +252,9 @@
     replication slot on the remote (publishing) side.
    </para>
    <para>
-    Additional table synchronization slots are normally transient, created
+    Additional tablesync slots are normally transient, created
     internally to perform initial table synchronization and dropped
-    automatically when they are no longer needed. These table synchronization
+    automatically when they are no longer needed. These tablesync
     slots have generated names: <quote><literal>pg_%u_sync_%u_%llu</literal></quote>
     (parameters: Subscription <parameter>oid</parameter>,
     Table <parameter>relid</parameter>, system identifier <parameter>sysid</parameter>)
@@ -306,7 +306,7 @@
        the subscription.  If the remote database instance no longer exists, no
        further action is then necessary.  If, however, the remote database
        instance is just unreachable, the replication slot (and any still 
-       remaining table synchronization slots) should then be
+       remaining tablesync slots) should then be
        dropped manually; otherwise it/they would continue to reserve WAL and might
        eventually cause the disk to fill up.  Such cases should be carefully
        investigated.
diff --git a/doc/src/sgml/ref/drop_subscription.sgml b/doc/src/sgml/ref/drop_subscription.sgml
index aee9615..98f0d39 100644
--- a/doc/src/sgml/ref/drop_subscription.sgml
+++ b/doc/src/sgml/ref/drop_subscription.sgml
@@ -80,7 +80,7 @@ DROP SUBSCRIPTION [ IF EXISTS ] <replaceable class="parameter">name</replaceable
    When dropping a subscription that is associated with a replication slot on
    the remote host (the normal state), <command>DROP SUBSCRIPTION</command>
    will connect to the remote host and try to drop the replication slot (and
-   any remaining table synchronization slots) as
+   any remaining tablesync slots) as
    part of its operation.  This is necessary so that the resources allocated
    for the subscription on the remote host are released.  If this fails,
    either because the remote host is not reachable or because the remote
@@ -90,7 +90,7 @@ DROP SUBSCRIPTION [ IF EXISTS ] <replaceable class="parameter">name</replaceable
    executing <literal>ALTER SUBSCRIPTION ... SET (slot_name = NONE)</literal>.
    After that, <command>DROP SUBSCRIPTION</command> will no longer attempt any
    actions on a remote host.  Note that if the remote replication slot still
-   exists, it (and any related table synchronization slots) should then be
+   exists, it (and any related tablesync slots) should then be
    dropped manually; otherwise it/they will continue to
    reserve WAL and might eventually cause the disk to fill up.  See
    also <xref linkend="logical-replication-subscription-slot"/>.
-- 
1.8.3.1