doc: Fix parameter name for pg_create_logical_replication_slot()

The parameter controlling if two-phase transactions can be decoded was
named "two_phase" in the documentation while its procedure defines
"twophase".

Author: Florin Irion
Discussion: https://postgr.es/m/5eeabd10-1aff-ea61-f92d-9fa0d9a7e207@gmail.com
Backpatch-through: 14

diff --git a/doc/src/sgml/func.sgml b/doc/src/sgml/func.sgml
index f63a04c66723a53ca9a4420438c6214d064c1cb3..f1a8a9a0ba5ccf4be1a6f09a712edde60ee2a266 100644 (file)
--- a/doc/src/sgml/func.sgml
+++ b/doc/src/sgml/func.sgml
@@ -25891,7 +25891,7 @@ postgres=# SELECT * FROM pg_walfile_name_offset(pg_stop_backup());
         
          pg_create_logical_replication_slot
         
-        pg_create_logical_replication_slot ( slot_name name, plugin name , temporary boolean, two_phase boolean  )
+        pg_create_logical_replication_slot ( slot_name name, plugin name , temporary boolean, twophase boolean  )
         record
         ( slot_name name,
         lsn pg_lsn )
@@ -25904,7 +25904,7 @@ postgres=# SELECT * FROM pg_walfile_name_offset(pg_stop_backup());
         the slot should not be permanently stored to disk and is only meant
         for use by the current session. Temporary slots are also
         released upon any error. The optional fourth parameter,
-        two_phase, when set to true, specifies
+        twophase, when set to true, specifies
         that the decoding of prepared transactions is enabled for this
         slot. A call to this function has the same effect as the replication
         protocol command CREATE_REPLICATION_SLOT ... LOGICAL.