aboutsummaryrefslogtreecommitdiff
path: root/doc/src
diff options
context:
space:
mode:
authorPeter Eisentraut <peter@eisentraut.org>2019-09-08 11:10:49 +0200
committerPeter Eisentraut <peter@eisentraut.org>2019-09-08 11:10:49 +0200
commit0e777462121bd5b892c1621903d1953a49437290 (patch)
tree049974e10734f2677afb9618c37bde83d9dd166b /doc/src
parent8e929a4667a1f4f97c5447f54b8176b0ee15aa7d (diff)
downloadpostgresql-0e777462121bd5b892c1621903d1953a49437290.tar.gz
postgresql-0e777462121bd5b892c1621903d1953a49437290.zip
doc: effective -> efficient
Diffstat (limited to 'doc/src')
-rw-r--r--doc/src/sgml/json.sgml6
1 files changed, 3 insertions, 3 deletions
diff --git a/doc/src/sgml/json.sgml b/doc/src/sgml/json.sgml
index cf50410d406..2d2f404b73e 100644
--- a/doc/src/sgml/json.sgml
+++ b/doc/src/sgml/json.sgml
@@ -23,7 +23,7 @@
<para>
<productname>PostgreSQL</productname> offers two types for storing JSON
- data: <type>json</type> and <type>jsonb</type>. To implement effective query
+ data: <type>json</type> and <type>jsonb</type>. To implement efficient query
mechanisms for these data types, <productname>PostgreSQL</productname>
also provides the <type>jsonpath</type> data type described in
<xref linkend="datatype-jsonpath"/>.
@@ -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</title>
<para>
Representing data as JSON can be considerably more flexible than
the traditional relational data model, which is compelling in
@@ -633,7 +633,7 @@ SELECT jdoc-&gt;'guid', jdoc-&gt;'name' FROM api WHERE jdoc @&gt; '{"tags": ["qu
<para>
The <type>jsonpath</type> type implements support for the SQL/JSON path language
- in <productname>PostgreSQL</productname> to effectively query JSON data.
+ in <productname>PostgreSQL</productname> to efficiently query JSON data.
It provides a binary representation of the parsed SQL/JSON path
expression that specifies the items to be retrieved by the path
engine from the JSON data for further processing with the