DOC: fix typos specific for EE

Author: Liudmila Mantrova

doc/src/sgml/aqo.sgml

@@ -137,7 +137,7 @@ where <replaceable>mode</> is the name of the optimization mode to use.
         </note>
       <para>
         Since the <literal>intelligent</literal> mode tries to learn separately for
-        different query types, <filename>aqo</filename> may fail to provide peformance improvements if the types of the queries in the workload are constantly changing. For such dynamic workloads, reset the <filename>aqo</filename> extension to
+        different query types, <filename>aqo</filename> may fail to provide performance improvements if the types of the queries in the workload are constantly changing. For such dynamic workloads, reset the <filename>aqo</filename> extension to
         the <literal>controlled</literal> mode, or try using the <literal>forced</literal> mode.
       </para>
       <para>

doc/src/sgml/cfs.sgml

@@ -98,7 +98,7 @@
     most frequently used pages. Each page is fixed size (8kb by default). But if we compress page, then
     its size will depend on its content. So updated page can require more (or less) space than original page.
     So we may not always perform in-place update of the page. Instead of it we have to locate new space for the page and somehow release
-    old space. There are two main apporaches of solving this problem:
+    old space. There are two main approaches to solving this problem:
   </para>
 
   <variablelist>

doc/src/sgml/multimaster.sgml

@@ -72,7 +72,7 @@
 
   <sect2 id="multimaster-limitations">
     <title>Limitations</title>
-    <para>The <filename>multimaster</filename> extension takes care of the database replication in a fully automated way. You can perform write transactions on any node and work with temporary tables on each cluster node simultaneosly. However, make sure to take the following replication restrictions into account:</para>
+    <para>The <filename>multimaster</filename> extension takes care of the database replication in a fully automated way. You can perform write transactions on any node and work with temporary tables on each cluster node simultaneously. However, make sure to take the following replication restrictions into account:</para>
     <itemizedlist>
       <listitem>
         <para>
@@ -832,7 +832,7 @@ pg_ctl -D <replaceable>datadir</replaceable> -l <replaceable>pg.log</replaceable
   <varlistentry><term><varname>multimaster.max_recovery_lag</varname><indexterm><primary><varname>multimaster.max_recovery_lag</varname></primary></indexterm></term><listitem><para>
     Maximal WAL lag
     size, in bytes. When a node is disconnected from the cluster, other
-    nodes copy WALs for all new trasactions into the replication slot of
+    nodes copy WALs for all new transactions into the replication slot of
     this node. Upon reaching the
     <varname>multimaster.max_recovery_lag</varname> value, the
     replication slot for the disconnected node is dropped to avoid

doc/src/sgml/pghintplan.sgml

@@ -11,7 +11,7 @@
     <title>Synopsis</title>
     <para>
       &productname; uses cost-based optimizer, which utilizes data
-      statistics, not static rules. The planner (optimizer) esitimates
+      statistics, not static rules. The planner (optimizer) estimates
       costs of each possible execution plans for a SQL statement then
       the execution plan with the lowest cost finally be executed. The
       planner does its best to select the best execution plan, but
@@ -284,7 +284,7 @@ postgres=# /*+ Leading((t1 (t2 t3))) */ SELECT...
         condition. This hint can corrects the number by several methods,
         which are absolute value, addition/subtraction and
         multiplication. The parameters are the list of objects compose
-        the targetted join then operation. The following example shows
+        the targeted join then operation. The following example shows
         notations to correct the number of the join on a and b by the
         four correction methods.
       </para>
@@ -299,7 +299,7 @@ postgres=# /*+ Rows(a b *10) */ SELECT... ; Makes the number 10 times larger.
       <title>GUC temporarily setting</title>
       <para>
         <quote>Set</quote> hint sets GUC parameter values during the
-        target statement is under plannning. In the following example,
+        target statement is under planning. In the following example,
         planning for the query is done with random_page_cost is 2.0.
       </para>
       <programlisting>
@@ -407,10 +407,10 @@ postgres=#
       <title>Limitations on multiple VALUES lists in FROM
       clauses</title>
       <para>
-        All occurences of VALUES lists in FROM clauses in a query has
+        All occurrences of VALUES lists in FROM clauses in a query has
         the same name <quote>*VALUES*</quote> irrespective of aliases
         syntactically given to them or shown in explain descriptions. So
-        it cannot be hinted at all if appeares twice or more in a target
+        it cannot be hinted at all if appears twice or more in a target
         query.
       </para>
     </sect3>
@@ -453,7 +453,7 @@ postgres=#
         Hints are effective on any objects with the target name even if
         they aren't apparent in the query, specifically objects in views.
         For that reason, you should create different views in which
-        targetted objects have distinct aliases if you want to hint them
+        targeted objects have distinct aliases if you want to hint them
         differently from the first view.
       </para>
       <para>
@@ -580,9 +580,9 @@ postgres=#   WHERE aid IN (SELECT bid FROM pgbench_accounts a2 LIMIT 10);
     <sect3>
       <title>Object misspecifications</title>
       <para>
-        Object misspecifications results silent ingorance of the hints.
+        Object misspecifications results silent ignorance of the hints.
         This kind of error is reported as <quote>not used hints</quote>
-        in the server log by the same condtion to syntax errors.
+        in the server log by the same condition to syntax errors.
       </para>
     </sect3>
     <sect3>
@@ -643,7 +643,7 @@ postgres=#   WHERE aid IN (SELECT bid FROM pgbench_accounts a2 LIMIT 10);
       <para>
         ECPG removes comments in queries written as embedded SQLs so
         hints cannot be passed form those queries. The only exception is
-        that EXECUTE command passes given string unmodifed. Please
+        that EXECUTE command passes given string unmodified. Please
         consider hint tables for this case.
       </para>
     </sect3>

doc/src/sgml/pgpro-scheduler.sgml

@@ -131,7 +131,7 @@ Make sure to create the <filename>pgpro_scheduler</filename> extension for each
       <programlisting>
 <varname>schedule.max_parallel_workers</varname> = 3
 </programlisting>
-<para>By default, two backgound workers for one-time jobs are available. These workers are not included into the <varname>schedule.max_workers</> number. Thus, one-time jobs can run in parallel with the scheduled jobs even if all the <varname>schedule.max_workers</> workers are busy.</para>
+<para>By default, two background workers for one-time jobs are available. These workers are not included into the <varname>schedule.max_workers</> number. Thus, one-time jobs can run in parallel with the scheduled jobs even if all the <varname>schedule.max_workers</> workers are busy.</para>
       </listitem>
       <listitem>
         <para>

doc/src/sgml/pgrepack.sgml

@@ -525,7 +525,7 @@ CREATE EXTENSION pg_repack
     <para>
      For previous versions load the script
      <filename>$SHAREDIR/contrib/uninstall_pg_repack.sql</filename> into the database
-     where the error occured and then load <filename>$SHAREDIR/contrib/pg_repack.sql</filename>
+     where the error occurred and then load <filename>$SHAREDIR/contrib/pg_repack.sql</filename>
      again.
     </para>
 

doc/src/sgml/release-proee-9.6.sgml

@@ -107,7 +107,7 @@
         use of <xref linkend="pgupgrade">, is required for those
           wishing to migrate data from any previous major release.</para>
 
-    <para>Dump/restore is neccessary when migrating from <productname>PostgreSQL</productname>
+    <para>Dump/restore is necessary when migrating from <productname>PostgreSQL</productname>
       or <productname>Postgres Pro Standard</productname> edition.</para>
 
     <para>For upgrades from previous releases of <productname>Postgres Pro Standard</productname> or
@@ -193,7 +193,7 @@
         use of <xref linkend="pgupgrade">, is required for those
           wishing to migrate data from any previous major release.</para>
 
-    <para>Dump/restore is neccessary when migrating from <productname>PostgreSQL</productname>
+    <para>Dump/restore is necessary when migrating from <productname>PostgreSQL</productname>
       or <productname>Postgres Pro Standard</productname> edition.</para>
 
     <para>For upgrades from previous releases of <productname>Postgres Pro Standard</productname> or from

doc/src/sgml/rum.sgml

@@ -20,7 +20,7 @@
        <para>
         Slow ranking. The positional information is needed for ranking.
         <literal>GIN</literal> index doesn't store positions of lexems.
-        So after index scan we need an additional heap scan to retreive
+        So after index scan we need an additional heap scan to retrieve
         lexems positions.
        </para>
       </listitem>

doc/src/sgml/spgist.sgml

@@ -159,7 +159,7 @@
  </para>
  <para>
   By supporting the ordering &lt;-&gt; operator the quad_point_ops and kd_point_ops provide 
-  a user with the ability to perform a K-nearest-neighbour search over the indexed point dataset.
+  a user with the ability to perform a K-nearest-neighbor search over the indexed point dataset.
  </para>
 
 </sect1>

doc/src/sgml/storage.sgml

@@ -777,7 +777,7 @@ data. Empty in ordinary tables.</entry>
   from the page start to the start of unallocated space, to the end of
   unallocated space, and to the start of the special space.
   Next are two 8-byte fields containing epoch, i. e. an offset, for
-  short (4-byte) transacion IDs in this page. The next 2
+  short (4-byte) transaction IDs in this page. The next 2
   bytes of the page header, <structfield>pd_pagesize_version</structfield>,
   store both the page size and a version indicator.  Beginning with
   <productname>PostgreSQL</productname> 8.3 the version number is 4;