doc: effective -> efficient

diff --git a/doc/src/sgml/json.sgml b/doc/src/sgml/json.sgml
index cf50410d406e1fd20aefac01696f1be75cff3599..2d2f404b73e13faa8afe74481c457e3ec2f5da8b 100644 (file)
--- a/doc/src/sgml/json.sgml
+++ b/doc/src/sgml/json.sgml
@@ -23,7 +23,7 @@
 
  
   PostgreSQL offers two types for storing JSON
-  data: json and jsonb. To implement effective query
+  data: json and jsonb. To implement efficient query
   mechanisms for these data types, PostgreSQL
   also provides the jsonpath data type described in
   .
@@ -233,7 +233,7 @@ SELECT '{"reading": 1.230e-5}'::json, '{"reading": 1.230e-5}'::jsonb;
  
 
  
-  Designing JSON Documents<span class="marked"> Effectively</span>
+  Designing JSON Documents
   
    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->'guid', jdoc->'name' FROM api WHERE jdoc @> '{"tags": ["qu
 
   
    The jsonpath type implements support for the SQL/JSON path language
-   in PostgreSQL to effectively query JSON data.
+   in PostgreSQL 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