relational databases. PostgreSQL implements SQL/PGQ<footnote><para>Here, PGQ
stands for <quote>property graph query</quote>. In the jargon of graph
databases, <quote>property graph</quote> is normally abbreviated as PG, which
- is clearly confusing for practioners of PostgreSQL, also usually abbreviated
+ is clearly confusing for practitioners of PostgreSQL, also usually abbreviated
as PG.</para></footnote>, which is part of the SQL standard, where a property
graph is defined as a kind of read-only view over relational tables. So the
actual data is still in tables or table-like objects, but is exposed as a
</para>
<para>
-This is controled with the <literal>EXCEPT</literal> clause, and is useful when specifying <literal>ALL TABLES</literal>.
+This is controlled with the <literal>EXCEPT</literal> clause, and is useful when specifying <literal>ALL TABLES</literal>.
</para>
</listitem>
<listitem>
<para>
-Allow <link linkend="app-psql"><application>psql</application></link> to more accurately determine if the <link linkend="app-psql-meta-command-pset-pager">pager</link>l is needed (Erik Wienhold)
+Allow <link linkend="app-psql"><application>psql</application></link> to more accurately determine if the <link linkend="app-psql-meta-command-pset-pager">pager</link> is needed (Erik Wienhold)
<ulink url="&commit_baseurl;27da1a796">§</ulink>
</para>
</listitem>