database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-07-28 23:42:10 +03:00
Code Activity

doc: Clean up title case use

Browse Source
This commit is contained in:
Peter Eisentraut
2025-06-16 11:43:52 +02:00
parent f24fdf9855
commit ee685c9baf
3 changed files with 9 additions and 9 deletions
Download Patch File Download Diff File Expand all files Collapse all files

12
doc/src/sgml/logical-replication.sgml
View File

@ -2413,7 +2413,7 @@ CONTEXT: processing remote data for replication origin "pg_16395" during "INSER
</para>
<sect2 id="prepare-publisher-upgrades">
<title>Prepare for publisher upgrades</title>
<title>Prepare for Publisher Upgrades</title>
<para>
<application>pg_upgrade</application> attempts to migrate logical
@ -2485,7 +2485,7 @@ CONTEXT: processing remote data for replication origin "pg_16395" during "INSER
</sect2>
<sect2 id="prepare-subscriber-upgrades">
<title>Prepare for subscriber upgrades</title>
<title>Prepare for Subscriber Upgrades</title>
<para>
Setup the <link linkend="logical-replication-config-subscriber">
@ -2535,7 +2535,7 @@ CONTEXT: processing remote data for replication origin "pg_16395" during "INSER
</sect2>
<sect2 id="upgrading-logical-replication-clusters">
<title>Upgrading logical replication clusters</title>
<title>Upgrading Logical Replication Clusters</title>
<para>
While upgrading a subscriber, write operations can be performed in the
@ -2599,7 +2599,7 @@ CONTEXT: processing remote data for replication origin "pg_16395" during "INSER
</para>
<sect3 id="steps-two-node-logical-replication-cluster">
<title>Steps to upgrade a two-node logical replication cluster</title>
<title>Steps to Upgrade a Two-node Logical Replication Cluster</title>
<para>
Let's say publisher is in <literal>node1</literal> and subscriber is
in <literal>node2</literal>. The subscriber <literal>node2</literal> has
@ -2743,7 +2743,7 @@ pg_ctl -D /opt/PostgreSQL/data2_upgraded start -l logfile
</sect3>
<sect3 id="steps-cascaded-logical-replication-cluster">
<title>Steps to upgrade a cascaded logical replication cluster</title>
<title>Steps to Upgrade a Cascaded Logical Replication Cluster</title>
<para>
Let's say we have a cascaded logical replication setup
<literal>node1</literal>-><literal>node2</literal>-><literal>node3</literal>.
@ -2972,7 +2972,7 @@ pg_ctl -D /opt/PostgreSQL/data3_upgraded start -l logfile
</sect3>
<sect3 id="steps-two-node-circular-logical-replication-cluster">
<title>Steps to upgrade a two-node circular logical replication cluster</title>
<title>Steps to Upgrade a Two-node Circular Logical Replication Cluster</title>
<para>
Let's say we have a circular logical replication setup
<literal>node1</literal>-><literal>node2</literal> and

4
doc/src/sgml/protocol.sgml
View File

@ -189,7 +189,7 @@
</sect2>
<sect2 id="protocol-versions">
<title>Protocol versions</title>
<title>Protocol Versions</title>
<para>
The current, latest version of the protocol is version 3.2. However, for
@ -226,7 +226,7 @@
</para>
<table id="protocol-versions-table">
<title>Protocol versions</title>
<title>Protocol Versions</title>
<tgroup cols="3">
<thead>

2
doc/src/sgml/textsearch.sgml
View File

@ -1355,7 +1355,7 @@ ts_headline(<optional> <replaceable class="parameter">config</replaceable> <type
</itemizedlist>
<warning>
<title>Warning: Cross-site scripting (XSS) safety</title>
<title>Warning: Cross-site Scripting (XSS) Safety</title>
<para>
The output from <function>ts_headline</function> is not guaranteed to
be safe for direct inclusion in web pages. When