doc: Clean up title case use

diff --git a/doc/src/sgml/logical-replication.sgml b/doc/src/sgml/logical-replication.sgml
index 686dd441d02236e11ec08fdad47c03a795b5099b..c32e6bc000d4d2bb373288658f2750ab9b4970da 100644 (file)
--- a/doc/src/sgml/logical-replication.sgml
+++ b/doc/src/sgml/logical-replication.sgml
@@ -2413,7 +2413,7 @@ CONTEXT:  processing remote data for replication origin "pg_16395" during "INSER
   
 
   
-   Prepare for <span class="marked">publisher u</span>pgrades
+   Prepare for <span class="marked">Publisher U</span>pgrades
 
    
     pg_upgrade attempts to migrate logical
@@ -2485,7 +2485,7 @@ CONTEXT:  processing remote data for replication origin "pg_16395" during "INSER
   
 
   
-   Prepare for <span class="marked">subscriber u</span>pgrades
+   Prepare for <span class="marked">Subscriber U</span>pgrades
 
    
     Setup the 
@@ -2535,7 +2535,7 @@ CONTEXT:  processing remote data for replication origin "pg_16395" during "INSER
   
 
   
-   Upgrading <span class="marked">logical replication c</span>lusters
+   Upgrading <span class="marked">Logical Replication C</span>lusters
 
    
     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
    
 
    
-    Steps to <span class="marked">upgrade a two-node logical replication c</span>luster
+    Steps to <span class="marked">Upgrade a Two-node Logical Replication C</span>luster
      
       Let's say publisher is in node1 and subscriber is
       in node2. The subscriber node2 has
@@ -2743,7 +2743,7 @@ pg_ctl -D /opt/PostgreSQL/data2_upgraded start -l logfile
     
 
     
-     Steps to <span class="marked">upgrade a cascaded logical replication c</span>luster
+     Steps to <span class="marked">Upgrade a Cascaded Logical Replication C</span>luster
      
       Let's say we have a cascaded logical replication setup
       node1->node2->node3.
@@ -2972,7 +2972,7 @@ pg_ctl -D /opt/PostgreSQL/data3_upgraded start -l logfile
     
 
     
-     Steps to <span class="marked">upgrade a two-node circular logical replication c</span>luster
+     Steps to <span class="marked">Upgrade a Two-node Circular Logical Replication C</span>luster
      
       Let's say we have a circular logical replication setup
       node1->node2 and

diff --git a/doc/src/sgml/protocol.sgml b/doc/src/sgml/protocol.sgml
index c4d3853cbf2c2ddee4348e6066c5ca0ffb48e03b..137ffc8d0b7eb8a248d46bcd1fb374a263dcfb0d 100644 (file)
--- a/doc/src/sgml/protocol.sgml
+++ b/doc/src/sgml/protocol.sgml
@@ -189,7 +189,7 @@
   
 
   
-   Protocol <span class="marked">v</span>ersions
+   Protocol <span class="marked">V</span>ersions
 
    
     The current, latest version of the protocol is version 3.2. However, for
@@ -226,7 +226,7 @@
    
 
    
-    Protocol <span class="marked">v</span>ersions
+    Protocol <span class="marked">V</span>ersions
 
     
      

diff --git a/doc/src/sgml/textsearch.sgml b/doc/src/sgml/textsearch.sgml
index 908857a54af5f5bf2d4858797225d0a761562b0e..89928ed182913730c8050421d104bd621898ed10 100644 (file)
--- a/doc/src/sgml/textsearch.sgml
+++ b/doc/src/sgml/textsearch.sgml
@@ -1355,7 +1355,7 @@ ts_headline( config 
     
 
     
-     Warning: Cross-site <span class="marked">scripting (XSS) s</span>afety
+     Warning: Cross-site <span class="marked">Scripting (XSS) S</span>afety
      
       The output from ts_headline is not guaranteed to
       be safe for direct inclusion in web pages. When