Minor docs fixes for new json functions.

Thom Brown.

Author: adunstan

doc/src/sgml/func.sgml

@@ -10309,7 +10309,7 @@ table2-mapping
        </entry>
        <entry><type>json</type></entry>
        <entry>
-         Builds a heterogeneously typed json array out of a variadic argument list.
+         Builds a heterogeneously-typed json array out of a variadic argument list.
        </entry>
        <entry><literal>SELECT json_build_array(1,2,'3',4,5);</literal></entry>
        <entry>
@@ -10329,7 +10329,8 @@ table2-mapping
        </entry>
        <entry><type>json</type></entry>
        <entry>
-         Builds a JSON array out of a variadic agument list.  By convention, the object is 
+         Builds a JSON array out of a variadic argument list.
+         By convention, the object is 
          constructed out of alternating name/value arguments.
        </entry>
        <entry><literal>SELECT json_build_object('foo',1,'bar',2);</literal></entry>
@@ -10371,8 +10372,8 @@ table2-mapping
        </entry>
        <entry><type>json</type></entry>
        <entry>
-         The two argument form of JSON object takes keys and values pairwise from two separate
-         arrays. In all other respects it is identical to the one argument form.
+         The two-argument form of JSON object takes keys and values pairwise from two separate
+         arrays. In all other respects it is identical to the one-argument form.
        </entry>
        <entry><literal>select * from json_object('{a, b}', '{1,2}');</literal></entry>
        <entry>
@@ -10457,7 +10458,7 @@ table2-mapping
 
   <note>
     <para>
-       In json_to_record and json_to_recordset, type coercion from the JSON is
+       In json_to_record and json_to_recordset, type-coercion from the JSON is
        "best effort" and may not result in desired values for some types.  JSON
        elements are matched to identical field names in the record definition,
        and elements which do not exist in the JSON will simply be NULL.  JSON