Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorPeter Eisentraut2019-09-08 08:26:35 +0000
committerPeter Eisentraut2019-09-08 08:27:29 +0000
commit8e929a4667a1f4f97c5447f54b8176b0ee15aa7d (patch)
treeca395028a0d737fdaae6998836e4e7d97fad34e7 /doc/src/sgml/json.sgml
parentdb438318997b75f4b40c61258da56384039fa43f (diff)
doc: Clean up title case use
Note: Following existing practice, titles of formalpara and step are not titlecased.
Diffstat (limited to 'doc/src/sgml/json.sgml')
-rw-r--r--doc/src/sgml/json.sgml4
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/src/sgml/json.sgml b/doc/src/sgml/json.sgml
index 0d8e2c6de4b..cf50410d406 100644
--- a/doc/src/sgml/json.sgml
+++ b/doc/src/sgml/json.sgml
@@ -131,7 +131,7 @@
</para>
<table id="json-type-mapping-table">
- <title>JSON primitive types and corresponding <productname>PostgreSQL</productname> types</title>
+ <title>JSON Primitive Types and Corresponding <productname>PostgreSQL</productname> Types</title>
<tgroup cols="3">
<thead>
<row>
@@ -233,7 +233,7 @@ SELECT '{"reading": 1.230e-5}'::json, '{"reading": 1.230e-5}'::jsonb;
</sect2>
<sect2 id="json-doc-design">
- <title>Designing JSON documents effectively</title>
+ <title>Designing JSON Documents Effectively</title>
<para>
Representing data as JSON can be considerably more flexible than
the traditional relational data model, which is compelling in