doc: Clean up title case use

Note: Following existing practice, titles of formalpara and step are
not titlecased.

Author: petere

doc/src/sgml/amcheck.sgml

@@ -169,7 +169,7 @@ ORDER BY c.relpages DESC LIMIT 10;
  </sect2>
 
  <sect2>
-  <title>Optional <parameter>heapallindexed</parameter> verification</title>
+  <title>Optional <parameter>heapallindexed</parameter> Verification</title>
  <para>
   When the <parameter>heapallindexed</parameter> argument to
   verification functions is <literal>true</literal>, an additional
@@ -210,7 +210,7 @@ ORDER BY c.relpages DESC LIMIT 10;
  </sect2>
 
  <sect2>
-  <title>Using <filename>amcheck</filename> effectively</title>
+  <title>Using <filename>amcheck</filename> Effectively</title>
 
  <para>
   <filename>amcheck</filename> can be effective at detecting various types of
@@ -319,7 +319,7 @@ ORDER BY c.relpages DESC LIMIT 10;
 
  </sect2>
  <sect2>
-  <title>Repairing corruption</title>
+  <title>Repairing Corruption</title>
  <para>
   No error concerning corruption raised by <filename>amcheck</filename> should
   ever be a false positive.  <filename>amcheck</filename> raises

doc/src/sgml/arch-dev.sgml

@@ -114,7 +114,7 @@
   </sect1>
 
   <sect1 id="connect-estab">
-   <title>How Connections are Established</title>
+   <title>How Connections Are Established</title>
 
    <para>
     <productname>PostgreSQL</productname> is implemented using a

doc/src/sgml/backup.sgml

@@ -824,8 +824,9 @@ test ! -f /mnt/server/archivedir/00000001000000A900000065 && cp pg_wal/0
     way. The non-exclusive method is recommended and the exclusive one is
     deprecated and will eventually be removed.
    </para>
+
    <sect3 id="backup-lowlevel-base-backup-nonexclusive">
-    <title>Making a non-exclusive low level backup</title>
+    <title>Making a Non-Exclusive Low-Level Backup</title>
     <para>
      A non-exclusive low level backup is one that allows other
      concurrent backups to be running (both those started using
@@ -947,7 +948,7 @@ SELECT * FROM pg_stop_backup(false, true);
     </para>
    </sect3>
    <sect3 id="backup-lowlevel-base-backup-exclusive">
-    <title>Making an exclusive low level backup</title>
+    <title>Making an Exclusive Low-Level Backup</title>
 
     <note>
      <para>
@@ -1082,7 +1083,7 @@ SELECT pg_stop_backup();
     </para>
    </sect3>
    <sect3 id="backup-lowlevel-base-backup-data">
-   <title>Backing up the data directory</title>
+   <title>Backing Up the Data Directory</title>
    <para>
     Some file system backup tools emit warnings or errors
     if the files they are trying to copy change while the copy proceeds.

doc/src/sgml/charset.sgml

@@ -580,7 +580,7 @@ SELECT * FROM test1 ORDER BY a || b COLLATE "fr_FR";
    </para>
 
   <sect4>
-   <title>libc collations</title>
+   <title>libc Collations</title>
 
    <para>
     For example, the operating system might
@@ -637,7 +637,7 @@ SELECT a COLLATE "C" &lt; b COLLATE "POSIX" FROM test1;
   </sect4>
 
   <sect4>
-   <title>ICU collations</title>
+   <title>ICU Collations</title>
 
    <para>
     With ICU, it is not sensible to enumerate all possible locale names.  ICU
@@ -713,7 +713,7 @@ SELECT a COLLATE "C" &lt; b COLLATE "POSIX" FROM test1;
    </para>
 
    <sect4>
-    <title>libc collations</title>
+    <title>libc Collations</title>
 
     <para>
      New libc collations can be created like this:
@@ -737,7 +737,7 @@ CREATE COLLATION german (provider = libc, locale = 'de_DE');
    </sect4>
 
    <sect4>
-    <title>ICU collations</title>
+    <title>ICU Collations</title>
 
    <para>
     ICU allows collations to be customized beyond the basic language+country

doc/src/sgml/config.sgml

@@ -5351,7 +5351,7 @@ SELECT * FROM parent WHERE key = 2400;
     </indexterm>
 
     <sect2 id="runtime-config-logging-where">
-     <title>Where To Log</title>
+     <title>Where to Log</title>
 
      <indexterm zone="runtime-config-logging-where">
       <primary>where to log</primary>
@@ -5795,7 +5795,7 @@ local0.*    /var/log/postgresql
       </variablelist>
     </sect2>
      <sect2 id="runtime-config-logging-when">
-     <title>When To Log</title>
+     <title>When to Log</title>
 
      <variablelist>
 
@@ -6011,7 +6011,7 @@ local0.*    /var/log/postgresql
 
     </sect2>
      <sect2 id="runtime-config-logging-what">
-     <title>What To Log</title>
+     <title>What to Log</title>
 
      <variablelist>
 

doc/src/sgml/custom-scan.sgml

@@ -1,7 +1,7 @@
 <!-- doc/src/sgml/custom-scan.sgml -->
 
 <chapter id="custom-scan">
- <title>Writing A Custom Scan Provider</title>
+ <title>Writing a Custom Scan Provider</title>
 
  <indexterm zone="custom-scan">
   <primary>custom scan provider</primary>

doc/src/sgml/dfunc.sgml

@@ -1,7 +1,7 @@
 <!-- doc/src/sgml/dfunc.sgml -->
 
 <sect2 id="dfunc">
- <title>Compiling and Linking Dynamically-loaded Functions</title>
+ <title>Compiling and Linking Dynamically-Loaded Functions</title>
 
  <para>
   Before you are able to use your

doc/src/sgml/docguide.sgml

@@ -247,7 +247,7 @@ checking for fop... fop
  </sect1>
 
  <sect1 id="docguide-build">
-  <title>Building The Documentation</title>
+  <title>Building the Documentation</title>
 
   <para>
    Once you have everything set up, change to the directory

doc/src/sgml/earthdistance.sgml

@@ -24,7 +24,7 @@
  </para>
 
  <sect2>
-  <title>Cube-based Earth Distances</title>
+  <title>Cube-Based Earth Distances</title>
 
   <para>
    Data is stored in cubes that are points (both corners are the same) using 3
@@ -60,7 +60,7 @@
   </para>
 
   <table id="earthdistance-cube-functions">
-   <title>Cube-based Earthdistance Functions</title>
+   <title>Cube-Based Earthdistance Functions</title>
    <tgroup cols="3">
     <thead>
      <row>
@@ -137,7 +137,7 @@
  </sect2>
 
  <sect2>
-  <title>Point-based Earth Distances</title>
+  <title>Point-Based Earth Distances</title>
 
   <para>
    The second part of the module relies on representing Earth locations as
@@ -154,7 +154,7 @@
   </para>
 
   <table id="earthdistance-point-operators">
-   <title>Point-based Earthdistance Operators</title>
+   <title>Point-Based Earthdistance Operators</title>
    <tgroup cols="3">
     <thead>
      <row>

doc/src/sgml/ecpg.sgml

@@ -1720,7 +1720,7 @@ while (1)
    </sect3>
 
    <sect3>
-    <title>User-defined Base Types</title>
+    <title>User-Defined Base Types</title>
 
     <para>
      New user-defined base types are not directly supported by ECPG.

doc/src/sgml/extend.sgml

@@ -953,7 +953,7 @@ SELECT * FROM pg_extension_update_paths('<replaceable>extension_name</replaceabl
    </sect2>
 
    <sect2>
-    <title>Installing Extensions using Update Scripts</title>
+    <title>Installing Extensions Using Update Scripts</title>
 
     <para>
      An extension that has been around for awhile will probably exist in

doc/src/sgml/fdwhandler.sgml

@@ -1,7 +1,7 @@
 <!-- doc/src/sgml/fdwhandler.sgml -->
 
  <chapter id="fdwhandler">
-   <title>Writing A Foreign Data Wrapper</title>
+   <title>Writing a Foreign Data Wrapper</title>
 
    <indexterm zone="fdwhandler">
     <primary>foreign data wrapper</primary>
@@ -96,7 +96,7 @@
     </para>
 
    <sect2 id="fdw-callbacks-scan">
-    <title>FDW Routines For Scanning Foreign Tables</title>
+    <title>FDW Routines for Scanning Foreign Tables</title>
 
     <para>
 <programlisting>
@@ -286,7 +286,7 @@ EndForeignScan(ForeignScanState *node);
    </sect2>
 
    <sect2 id="fdw-callbacks-join-scan">
-    <title>FDW Routines For Scanning Foreign Joins</title>
+    <title>FDW Routines for Scanning Foreign Joins</title>
 
     <para>
      If an FDW supports performing foreign joins remotely (rather than
@@ -348,7 +348,7 @@ GetForeignJoinPaths(PlannerInfo *root,
    </sect2>
 
    <sect2 id="fdw-callbacks-upper-planning">
-    <title>FDW Routines For Planning Post-Scan/Join Processing</title>
+    <title>FDW Routines for Planning Post-Scan/Join Processing</title>
 
     <para>
      If an FDW supports performing remote post-scan/join processing, such as
@@ -404,7 +404,7 @@ GetForeignUpperPaths(PlannerInfo *root,
    </sect2>
 
    <sect2 id="fdw-callbacks-update">
-    <title>FDW Routines For Updating Foreign Tables</title>
+    <title>FDW Routines for Updating Foreign Tables</title>
 
     <para>
      If an FDW supports writable foreign tables, it should provide
@@ -967,7 +967,7 @@ EndDirectModify(ForeignScanState *node);
    </sect2>
 
    <sect2 id="fdw-callbacks-row-locking">
-    <title>FDW Routines For Row Locking</title>
+    <title>FDW Routines for Row Locking</title>
 
     <para>
      If an FDW wishes to support <firstterm>late row locking</firstterm> (as described
@@ -1231,7 +1231,7 @@ AcquireSampleRowsFunc(Relation relation,
    </sect2>
 
    <sect2 id="fdw-callbacks-import">
-    <title>FDW Routines For <command>IMPORT FOREIGN SCHEMA</command></title>
+    <title>FDW Routines for <command>IMPORT FOREIGN SCHEMA</command></title>
 
     <para>
 <programlisting>
@@ -1394,7 +1394,7 @@ ShutdownForeignScan(ForeignScanState *node);
    </sect2>
 
    <sect2 id="fdw-callbacks-reparameterize-paths">
-    <title>FDW Routines For reparameterization of paths</title>
+    <title>FDW Routines for Reparameterization of Paths</title>
 
     <para>
 <programlisting>

doc/src/sgml/features.sgml

@@ -200,7 +200,7 @@
    </para>
 
    <sect2 id="functions-xml-limits-xpath1">
-    <title>Queries are restricted to XPath 1.0</title>
+    <title>Queries Are Restricted to XPath 1.0</title>
 
     <para>
      The <productname>PostgreSQL</productname>-specific functions
@@ -383,7 +383,7 @@
     </sect3>
 
     <sect3 id="functions-xml-limits-casts">
-     <title>Mappings between SQL and XML data types and values</title>
+     <title>Mappings between SQL and XML Data Types and Values</title>
 
      <para>
       In SQL:2006 and later, both directions of conversion between standard SQL
@@ -424,7 +424,7 @@
     </para>
 
     <sect3>
-     <title>Only <literal>BY VALUE</literal> passing mechanism is supported</title>
+     <title>Only <literal>BY VALUE</literal> Passing Mechanism Is Supported</title>
 
      <para>
       The SQL standard defines two <firstterm>passing mechanisms</firstterm>
@@ -460,7 +460,7 @@ SELECT XMLQUERY('$a is $b' PASSING BY VALUE <replaceable>x</replaceable> AS a, <
     </sect3>
 
     <sect3>
-     <title>Cannot pass named parameters to queries</title>
+     <title>Cannot Pass Named Parameters to Queries</title>
 
      <para>
       The XPath-based functions support passing one parameter to serve as the
@@ -470,7 +470,7 @@ SELECT XMLQUERY('$a is $b' PASSING BY VALUE <replaceable>x</replaceable> AS a, <
     </sect3>
 
     <sect3>
-     <title>No <type>XML(SEQUENCE)</type> type</title>
+     <title>No <type>XML(SEQUENCE)</type> Type</title>
 
      <para>
       The <productname>PostgreSQL</productname> <type>xml</type> data type

doc/src/sgml/func.sgml

@@ -5206,7 +5206,7 @@ SELECT foo FROM regexp_split_to_table('the quick brown fox', '\s*') AS foo;
    </para>
 
    <table id="posix-character-entry-escapes-table">
-    <title>Regular Expression Character-entry Escapes</title>
+    <title>Regular Expression Character-Entry Escapes</title>
 
     <tgroup cols="2">
      <thead>
@@ -5347,7 +5347,7 @@ SELECT foo FROM regexp_split_to_table('the quick brown fox', '\s*') AS foo;
    </para>
 
    <table id="posix-class-shorthand-escapes-table">
-    <title>Regular Expression Class-shorthand Escapes</title>
+    <title>Regular Expression Class-Shorthand Escapes</title>
 
     <tgroup cols="2">
      <thead>
@@ -5541,7 +5541,7 @@ SELECT foo FROM regexp_split_to_table('the quick brown fox', '\s*') AS foo;
    </para>
 
    <table id="posix-embedded-options-table">
-    <title>ARE Embedded-option Letters</title>
+    <title>ARE Embedded-Option Letters</title>
 
     <tgroup cols="2">
      <thead>
@@ -16425,7 +16425,7 @@ WHERE EXISTS (SELECT 1 FROM tab2 WHERE col2 = tab1.col2);
   </sect2>
 
   <sect2>
-   <title>Single-row Comparison</title>
+   <title>Single-Row Comparison</title>
 
    <indexterm zone="functions-subquery">
     <primary>comparison</primary>
@@ -19336,7 +19336,7 @@ SELECT collation for ('foo' COLLATE "de_DE");
    </para>
 
    <table id="functions-commit-timestamp">
-    <title>Committed transaction information</title>
+    <title>Committed Transaction Information</title>
     <tgroup cols="3">
      <thead>
       <row><entry>Name</entry> <entry>Return Type</entry> <entry>Description</entry></row>
@@ -22351,7 +22351,7 @@ CREATE EVENT TRIGGER test_event_trigger_for_drops
    </para>
 
    <table id="functions-event-trigger-table-rewrite">
-    <title>Table Rewrite information</title>
+    <title>Table Rewrite Information</title>
     <tgroup cols="3">
      <thead>
       <row><entry>Name</entry> <entry>Return Type</entry> <entry>Description</entry></row>
@@ -22419,7 +22419,7 @@ CREATE EVENT TRIGGER test_table_rewrite_oid
    </para>
 
   <sect2 id="functions-statistics-mcv">
-   <title>Inspecting MCV lists</title>
+   <title>Inspecting MCV Lists</title>
 
    <indexterm>
      <primary>pg_mcv_list_items</primary>

doc/src/sgml/gist.sgml

@@ -961,7 +961,7 @@ my_fetch(PG_FUNCTION_ARGS)
  <title>Implementation</title>
 
  <sect2 id="gist-buffering-build">
-  <title>GiST buffering build</title>
+  <title>GiST Buffering Build</title>
   <para>
    Building large GiST indexes by simply inserting all the tuples tends to be
    slow, because if the index tuples are scattered across the index and the