Fix some typos in jsonpath documentation
authorAlexander Korotkov <akorotkov@postgresql.org>
Wed, 7 Aug 2019 13:06:45 +0000 (16:06 +0300)
committerAlexander Korotkov <akorotkov@postgresql.org>
Wed, 7 Aug 2019 13:08:03 +0000 (16:08 +0300)
Discussion: https://postgr.es/m/8B7FA3B4-328D-43D7-95A8-37B8891B8C78%40winand.at
Author: Markus Winand
Backpatch-through: 12

doc/src/sgml/func.sgml

index 8ccb3a5a999ee1a135fd7b1b99332a6e8ceb88cc..4bb546148431310d71bc1a2132e9946a6fe2eb5b 100644 (file)
@@ -11733,7 +11733,7 @@ table2-mapping
      A path expression can be a Boolean predicate, although the SQL/JSON
      standard allows predicates only in filters.  This is necessary for
      implementation of the <literal>@@</literal> operator. For example,
-     the following<type>jsonpath</type> expression is valid in
+     the following <type>jsonpath</type> expression is valid in
      <productname>PostgreSQL</productname>:
 <programlisting>
 '$.track.segments[*].HR &lt; 70'
@@ -12995,7 +12995,7 @@ table2-mapping
         </entry>
         <entry>
          <para><literal>
-           select * jsonb_path_query('{"a":[1,2,3,4,5]}', '$.a[*] ? (@ >= $min &amp;&amp; @ &lt;= $max)', '{"min":2,"max":4}');
+           select * from jsonb_path_query('{"a":[1,2,3,4,5]}', '$.a[*] ? (@ >= $min &amp;&amp; @ &lt;= $max)', '{"min":2,"max":4}');
          </literal></para>
         </entry>
         <entry>