Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Skip to content

Commit 5d5678d

Browse files
committed
Properly capitalize documentation headings; some only had initial-word
capitalization.
1 parent 6f489dc commit 5d5678d

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

65 files changed

+447
-447
lines changed

doc/src/sgml/adminpack.sgml

+1-1
Original file line numberDiff line numberDiff line change
@@ -15,7 +15,7 @@
1515
</para>
1616

1717
<sect2>
18-
<title>Functions implemented</title>
18+
<title>Functions Implemented</title>
1919

2020
<para>
2121
The functions implemented by <filename>adminpack</> can only be run by a

doc/src/sgml/auth-delay.sgml

+1-1
Original file line numberDiff line numberDiff line change
@@ -22,7 +22,7 @@
2222
</para>
2323

2424
<sect2>
25-
<title>Configuration parameters</title>
25+
<title>Configuration Parameters</title>
2626

2727
<variablelist>
2828
<varlistentry>

doc/src/sgml/auto-explain.sgml

+1-1
Original file line numberDiff line numberDiff line change
@@ -32,7 +32,7 @@ LOAD 'auto_explain';
3232
</para>
3333

3434
<sect2>
35-
<title>Configuration parameters</title>
35+
<title>Configuration Parameters</title>
3636

3737
<para>
3838
There are several configuration parameters that control the behavior of

doc/src/sgml/backup.sgml

+8-8
Original file line numberDiff line numberDiff line change
@@ -103,7 +103,7 @@ pg_dump <replaceable class="parameter">dbname</replaceable> &gt; <replaceable cl
103103
</important>
104104

105105
<sect2 id="backup-dump-restore">
106-
<title>Restoring the dump</title>
106+
<title>Restoring the Dump</title>
107107

108108
<para>
109109
The text files created by <application>pg_dump</> are intended to
@@ -225,7 +225,7 @@ psql -f <replaceable class="parameter">infile</replaceable> postgres
225225
</sect2>
226226

227227
<sect2 id="backup-dump-large">
228-
<title>Handling large databases</title>
228+
<title>Handling Large Databases</title>
229229

230230
<para>
231231
Some operating systems have maximum file size limits that cause
@@ -527,7 +527,7 @@ tar -cf backup.tar /usr/local/pgsql/data
527527
</para>
528528

529529
<sect2 id="backup-archiving-wal">
530-
<title>Setting up WAL archiving</title>
530+
<title>Setting Up WAL Archiving</title>
531531

532532
<para>
533533
In an abstract sense, a running <productname>PostgreSQL</> system
@@ -934,7 +934,7 @@ SELECT pg_stop_backup();
934934
</sect2>
935935

936936
<sect2 id="backup-pitr-recovery">
937-
<title>Recovering using a Continuous Archive Backup</title>
937+
<title>Recovering Using a Continuous Archive Backup</title>
938938

939939
<para>
940940
Okay, the worst has happened and you need to recover from your backup.
@@ -1193,7 +1193,7 @@ restore_command = 'cp /mnt/server/archivedir/%f %p'
11931193
</para>
11941194

11951195
<sect3 id="backup-standalone">
1196-
<title>Standalone hot backups</title>
1196+
<title>Standalone Hot Backups</title>
11971197

11981198
<para>
11991199
It is possible to use <productname>PostgreSQL</>'s backup facilities to
@@ -1256,7 +1256,7 @@ restore_command = 'gunzip &lt; /mnt/server/archivedir/%f | pg_decompresslog - %p
12561256
</sect3>
12571257

12581258
<sect3 id="backup-scripts">
1259-
<title><varname>archive_command</varname> scripts</title>
1259+
<title><varname>archive_command</varname> Scripts</title>
12601260

12611261
<para>
12621262
Many people choose to use scripts to define their
@@ -1482,7 +1482,7 @@ archive_command = 'local_backup_script.sh'
14821482
</variablelist>
14831483

14841484
<sect2 id="migration-methods-pgdump">
1485-
<title>Migrating data via <application>pg_dump</></title>
1485+
<title>Migrating Data via <application>pg_dump</></title>
14861486

14871487
<para>
14881488
To dump data from one major version of <productname>PostgreSQL</> and
@@ -1562,7 +1562,7 @@ psql -f backup postgres
15621562
</sect2>
15631563

15641564
<sect2 id="migration-methods-other">
1565-
<title>Other data migration methods</title>
1565+
<title>Other Data Migration Methods</title>
15661566

15671567
<para>
15681568
The <filename>contrib</> program

doc/src/sgml/btree-gin.sgml

+1-1
Original file line numberDiff line numberDiff line change
@@ -31,7 +31,7 @@
3131
</para>
3232

3333
<sect2>
34-
<title>Example usage</title>
34+
<title>Example Usage</title>
3535

3636
<programlisting>
3737
CREATE TABLE test (a int4);

doc/src/sgml/btree-gist.sgml

+1-1
Original file line numberDiff line numberDiff line change
@@ -36,7 +36,7 @@
3636
</para>
3737

3838
<sect2>
39-
<title>Example usage</title>
39+
<title>Example Usage</title>
4040

4141
<para>
4242
Simple example using btree_gist instead of btree:

doc/src/sgml/charset.sgml

+4-4
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
<!-- doc/src/sgml/charset.sgml -->
22

33
<chapter id="charset">
4-
<title>Localization</>
4+
<title>Localization</title>
55

66
<para>
77
This chapter describes the available localization features from the
@@ -44,7 +44,7 @@
4444
</para>
4545

4646
<sect2>
47-
<title>Overview</>
47+
<title>Overview</title>
4848

4949
<para>
5050
Locale support is automatically initialized when a database
@@ -198,7 +198,7 @@ initdb --locale=sv_SE
198198
</sect2>
199199

200200
<sect2>
201-
<title>Behavior</>
201+
<title>Behavior</title>
202202

203203
<para>
204204
The locale settings influence the following SQL features:
@@ -256,7 +256,7 @@ initdb --locale=sv_SE
256256
</sect2>
257257

258258
<sect2>
259-
<title>Problems</>
259+
<title>Problems</title>
260260

261261
<para>
262262
If locale support doesn't work according to the explanation above,

doc/src/sgml/client-auth.sgml

+18-18
Original file line numberDiff line numberDiff line change
@@ -54,7 +54,7 @@
5454
</para>
5555

5656
<sect1 id="auth-pg-hba-conf">
57-
<title>The <filename>pg_hba.conf</filename> file</title>
57+
<title>The <filename>pg_hba.conf</filename> File</title>
5858

5959
<indexterm zone="auth-pg-hba-conf">
6060
<primary>pg_hba.conf</primary>
@@ -577,7 +577,7 @@ hostnossl <replaceable>database</replaceable> <replaceable>user</replaceable>
577577
</para>
578578

579579
<example id="example-pg-hba.conf">
580-
<title>Example <filename>pg_hba.conf</filename> entries</title>
580+
<title>Example <filename>pg_hba.conf</filename> Entries</title>
581581
<programlisting>
582582
# Allow any user on the local system to connect to any database with
583583
# any database user name using Unix-domain sockets (the default for local
@@ -666,7 +666,7 @@ local db1,db2,@demodbs all md5
666666
</sect1>
667667

668668
<sect1 id="auth-username-maps">
669-
<title>User name maps</title>
669+
<title>User Name Maps</title>
670670

671671
<indexterm zone="auth-username-maps">
672672
<primary>User name maps</primary>
@@ -771,7 +771,7 @@ mymap /^(.*)@otherdomain\.com$ guest
771771
</para>
772772

773773
<example id="example-pg-ident.conf">
774-
<title>An example <filename>pg_ident.conf</> file</title>
774+
<title>An Example <filename>pg_ident.conf</> File</title>
775775
<programlisting>
776776
# MAPNAME SYSTEM-USERNAME PG-USERNAME
777777

@@ -786,13 +786,13 @@ omicron bryanh guest1
786786
</sect1>
787787

788788
<sect1 id="auth-methods">
789-
<title>Authentication methods</title>
789+
<title>Authentication Methods</title>
790790
<para>
791791
The following subsections describe the authentication methods in more detail.
792792
</para>
793793

794794
<sect2 id="auth-trust">
795-
<title>Trust authentication</title>
795+
<title>Trust Authentication</title>
796796

797797
<para>
798798
When <literal>trust</> authentication is specified,
@@ -840,7 +840,7 @@ omicron bryanh guest1
840840
</sect2>
841841

842842
<sect2 id="auth-password">
843-
<title>Password authentication</title>
843+
<title>Password Authentication</title>
844844

845845
<indexterm>
846846
<primary>MD5</>
@@ -883,7 +883,7 @@ omicron bryanh guest1
883883
</sect2>
884884

885885
<sect2 id="gssapi-auth">
886-
<title>GSSAPI authentication</title>
886+
<title>GSSAPI Authentication</title>
887887

888888
<indexterm zone="gssapi-auth">
889889
<primary>GSSAPI</primary>
@@ -960,7 +960,7 @@ omicron bryanh guest1
960960
</sect2>
961961

962962
<sect2 id="sspi-auth">
963-
<title>SSPI authentication</title>
963+
<title>SSPI Authentication</title>
964964

965965
<indexterm zone="sspi-auth">
966966
<primary>SSPI</primary>
@@ -1026,7 +1026,7 @@ omicron bryanh guest1
10261026
</sect2>
10271027

10281028
<sect2 id="kerberos-auth">
1029-
<title>Kerberos authentication</title>
1029+
<title>Kerberos Authentication</title>
10301030

10311031
<indexterm zone="kerberos-auth">
10321032
<primary>Kerberos</primary>
@@ -1198,7 +1198,7 @@ omicron bryanh guest1
11981198
</sect2>
11991199

12001200
<sect2 id="auth-ident">
1201-
<title>Ident-based authentication</title>
1201+
<title>Ident-Based Authentication</title>
12021202

12031203
<indexterm>
12041204
<primary>ident</primary>
@@ -1229,7 +1229,7 @@ omicron bryanh guest1
12291229
</para>
12301230

12311231
<sect3>
1232-
<title>Ident Authentication over TCP/IP</title>
1232+
<title>Ident Authentication Over TCP/IP</title>
12331233

12341234
<para>
12351235
The <quote>Identification Protocol</quote> is described in
@@ -1276,7 +1276,7 @@ omicron bryanh guest1
12761276
</sect3>
12771277

12781278
<sect3>
1279-
<title>Ident Authentication over Local Sockets</title>
1279+
<title>Ident Authentication Over Local Sockets</title>
12801280

12811281
<para>
12821282
On systems supporting <symbol>SO_PEERCRED</symbol> requests for
@@ -1306,7 +1306,7 @@ omicron bryanh guest1
13061306
</sect2>
13071307

13081308
<sect2 id="auth-ldap">
1309-
<title>LDAP authentication</title>
1309+
<title>LDAP Authentication</title>
13101310

13111311
<indexterm zone="auth-ldap">
13121312
<primary>LDAP</primary>
@@ -1450,7 +1450,7 @@ ldapserver=ldap.example.net ldapprefix="cn=" ldapsuffix=", dc=example, dc=net"
14501450
</sect2>
14511451

14521452
<sect2 id="auth-radius">
1453-
<title>RADIUS authentication</title>
1453+
<title>RADIUS Authentication</title>
14541454

14551455
<indexterm zone="auth-radius">
14561456
<primary>RADIUS</primary>
@@ -1539,7 +1539,7 @@ ldapserver=ldap.example.net ldapprefix="cn=" ldapsuffix=", dc=example, dc=net"
15391539
</sect2>
15401540

15411541
<sect2 id="auth-cert">
1542-
<title>Certificate authentication</title>
1542+
<title>Certificate Authentication</title>
15431543

15441544
<indexterm zone="auth-cert">
15451545
<primary>Certificate</primary>
@@ -1575,7 +1575,7 @@ ldapserver=ldap.example.net ldapprefix="cn=" ldapsuffix=", dc=example, dc=net"
15751575
</sect2>
15761576

15771577
<sect2 id="auth-pam">
1578-
<title>PAM authentication</title>
1578+
<title>PAM Authentication</title>
15791579

15801580
<indexterm zone="auth-pam">
15811581
<primary>PAM</primary>
@@ -1621,7 +1621,7 @@ ldapserver=ldap.example.net ldapprefix="cn=" ldapsuffix=", dc=example, dc=net"
16211621
</sect1>
16221622

16231623
<sect1 id="client-authentication-problems">
1624-
<title>Authentication problems</title>
1624+
<title>Authentication Problems</title>
16251625

16261626
<para>
16271627
Authentication failures and related problems generally

doc/src/sgml/config.sgml

+3-3
Original file line numberDiff line numberDiff line change
@@ -3204,7 +3204,7 @@ local0.* /var/log/postgresql
32043204
</para>
32053205

32063206
<table id="runtime-config-severity-levels">
3207-
<title>Message severity levels</title>
3207+
<title>Message Severity Levels</title>
32083208
<tgroup cols="4">
32093209
<thead>
32103210
<row>
@@ -6084,11 +6084,11 @@ LOG: CleanUpLock: deleting: lock(0xb7acd844) id(24688,24696,0,0,0,1)
60846084
</para>
60856085

60866086
<table id="runtime-config-short-table">
6087-
<title>Short option key</title>
6087+
<title>Short Option Key</title>
60886088
<tgroup cols="2">
60896089
<thead>
60906090
<row>
6091-
<entry>Short option</entry>
6091+
<entry>Short Option</entry>
60926092
<entry>Equivalent</entry>
60936093
</row>
60946094
</thead>

doc/src/sgml/contrib-spi.sgml

+5-5
Original file line numberDiff line numberDiff line change
@@ -18,7 +18,7 @@
1818
</para>
1919

2020
<sect2>
21-
<title>refint.c &mdash; functions for implementing referential integrity</title>
21+
<title>refint.c &mdash; Functions for Implementing Referential Integrity</title>
2222

2323
<para>
2424
<function>check_primary_key()</> and
@@ -59,7 +59,7 @@
5959
</sect2>
6060

6161
<sect2>
62-
<title>timetravel.c &mdash; functions for implementing time travel</title>
62+
<title>timetravel.c &mdash; Functions for Implementing Time Travel</title>
6363

6464
<para>
6565
Long ago, <productname>PostgreSQL</> had a built-in time travel feature
@@ -152,7 +152,7 @@ CREATE TABLE mytab (
152152
</sect2>
153153

154154
<sect2>
155-
<title>autoinc.c &mdash; functions for autoincrementing fields</title>
155+
<title>autoinc.c &mdash; Functions for Autoincrementing Fields</title>
156156

157157
<para>
158158
<function>autoinc()</> is a trigger that stores the next value of
@@ -179,7 +179,7 @@ CREATE TABLE mytab (
179179
</sect2>
180180

181181
<sect2>
182-
<title>insert_username.c &mdash; functions for tracking who changed a table</title>
182+
<title>insert_username.c &mdash; Functions for Tracking Who Changed a Table</title>
183183

184184
<para>
185185
<function>insert_username()</> is a trigger that stores the current
@@ -200,7 +200,7 @@ CREATE TABLE mytab (
200200
</sect2>
201201

202202
<sect2>
203-
<title>moddatetime.c &mdash; functions for tracking last modification time</title>
203+
<title>moddatetime.c &mdash; Functions for Tracking Last Modification Time</title>
204204

205205
<para>
206206
<function>moddatetime()</> is a trigger that stores the current

0 commit comments

Comments
 (0)