Commit to fix typo in the documentaiton.

Author: koichi-szk

doc-xc/src/sgml/advanced.sgmlin

@@ -155,7 +155,7 @@ DETAIL:  Key (city)=(Berkeley) is not present in table "cities".
 &xconly;
    <para>
     In the current <productname>Postgres-XC</> release, you can
-    specify columns of a replciated table or the distribution column
+    specify columns of a replicated table or the distribution column
     of a distributed column as referred column.
    </para>
 <!## end>
@@ -232,7 +232,7 @@ UPDATE branches SET balance = balance + 100.00
     related to the notion of atomic updates: when multiple transactions
     are running concurrently, each one should not be able to see the
     incomplete changes made by others.  For example, if one transaction
-    is busy totalling all the branch balances, it would not do for it
+    is busy totaling all the branch balances, it would not do for it
     to include the debit from Alice's branch but not the credit to
     Bob's branch, nor vice versa.  So transactions must be all-or-nothing
     not only in terms of their permanent effect on the database, but
@@ -317,7 +317,7 @@ COMMIT;
 
 <!## PG>
 <!-- NOTE:
-     Again, XC does not supoprt savepoint yet.
+     Again, XC does not support savepoint yet.
 -->
 
    <para>

doc-xc/src/sgml/catalogs.sgmlin

@@ -3322,7 +3322,7 @@
 <!## XC>
   <para>
    This catalog exists in each coordinator and datanode in 
-   <productname>Postgres-XC</productname> as inheritted from <productname>PostgreSQL</productname>.
+   <productname>Postgres-XC</productname> as inherited from <productname>PostgreSQL</productname>.
    Please note that current release of <productname>Postgres-XC</productname> does not support
    foreign data wrapper.
   </para>
@@ -3430,7 +3430,7 @@
 <!## XC>
   <para>
    This catalog exists in each coordinator and datanode in 
-   <productname>Postgres-XC</productname> as inheritted from <productname>PostgreSQL</productname>.
+   <productname>Postgres-XC</productname> as inherited from <productname>PostgreSQL</productname>.
    Please note that current release of <productname>Postgres-XC</productname> does not support
    foreign data wrapper.
   </para>
@@ -3535,7 +3535,7 @@
 <!## XC>
   <para>
    This catalog exists in each coordinator and datanode in 
-   <productname>Postgres-XC</productname> as inheritted from <productname>PostgreSQL</productname>.
+   <productname>Postgres-XC</productname> as inherited from <productname>PostgreSQL</productname>.
    Please note that current release of <productname>Postgres-XC</productname> does not support
    foreign data wrapper.
   </para>
@@ -4004,7 +4004,7 @@
 <!## XC>
   <para>
    This catalog exists in each coordinator and datanode in 
-   <productname>Postgres-XC</productname> as inheritted from <productname>PostgreSQL</productname>.
+   <productname>Postgres-XC</productname> as inherited from <productname>PostgreSQL</productname>.
    Please note that current release of <productname>Postgres-XC</productname> does not support
    large object.
   </para>
@@ -4093,7 +4093,7 @@
 <!## XC>
   <para>
    This catalog exists in each coordinator and datanode in 
-   <productname>Postgres-XC</productname> as inheritted from <productname>PostgreSQL</productname>.
+   <productname>Postgres-XC</productname> as inherited from <productname>PostgreSQL</productname>.
    Please note that current release of <productname>Postgres-XC</productname> does not support
    large object.
   </para>
@@ -6963,7 +6963,7 @@
 <!## XC>
   <para>
    This catalog exists in each coordinator and datanode in 
-   <productname>Postgres-XC</productname> as inheritted from <productname>PostgreSQL</productname>.
+   <productname>Postgres-XC</productname> as inherited from <productname>PostgreSQL</productname>.
    Please note that current release of <productname>Postgres-XC</productname> does not support
    foreign data wrapper.
   </para>
@@ -9500,7 +9500,7 @@
 <!## XC>
   <para>
    This catalog exists in each coordinator and datanode in 
-   <productname>Postgres-XC</productname> as inheritted from <productname>PostgreSQL</productname>.
+   <productname>Postgres-XC</productname> as inherited from <productname>PostgreSQL</productname>.
    Please note that current release of <productname>Postgres-XC</productname> does not support
    foreign data wrapper.
   </para>

doc-xc/src/sgml/config.sgmlin

@@ -1372,7 +1372,7 @@ include 'filename'
       <para>
        Current release of <emphasis>Postgres-XC only:</emphasis> <productname>Postgres-XC</productname>
        does not support Windows.
-       The following description applies onlyh to <productname>PostgreSQL</productname>.
+       The following description applies only to <productname>PostgreSQL</productname>.
       </para>
 <!## end>
 
@@ -2482,7 +2482,7 @@ include 'filename'
      <para>
       Current release of <productname>Postgres-XC</productname> does not
       provide consistent view of standby servers.
-      Staandby server of a coordinator does not provide global view of
+      Standby server of a coordinator does not provide global view of
       datanode standbys.
       Each standby server provides only local view of the database.
       Please also note that the view is not governed by MVCC.
@@ -7068,7 +7068,7 @@ LOG:  CleanUpLock: deleting: lock(0xb7acd844) id(24688,24696,0,0,0,1)
       </indexterm>
       <listitem>
        <para>
-        Minumum number of the connection from the Coordinator to
+        Minimum number of the connection from the Coordinator to
         Datanodes.
        </para>
       </listitem>

doc-xc/src/sgml/func.sgmlin

@@ -14716,7 +14716,7 @@ SELECT collation for ('foo' COLLATE "de_DE");
 &xconly;
    <para>
     In <productname>Postgres-XC</>, OID is maintained locally in each Coordinator and Datanode.
-    If you specify specific OID value, you should do it in SQL statements targeted to specif
+    If you specify specific OID value, you should do it in SQL statements targeted to specific
     Coordinator or Datanode by <type>EXECUTE DIRECT</> statement.
    </para>
 <!## end>
@@ -16345,8 +16345,8 @@ SELECT (pg_stat_file('filename')).modification;
    </indexterm>
    <para>
     <function>pgxc_lock_for_backup</> locks the cluster for taking backup using <application>pg_dump/pg_dumpall</application>.
-    Locking means that we disallow the statemets that change the portions of the catalog which are
-    backed up by <application>pg_dump/pg_dumpall</application>. When locked only the following utility statemets are allowed.
+    Locking means that we disallow the statements that change the portions of the catalog which are
+    backed up by <application>pg_dump/pg_dumpall</application>. When locked only the following utility statements are allowed.
     Please note that this function does not impact SELECTs or DMLs.
    </para>
 <!## end>

doc-xc/src/sgml/high-availability.sgmlin

@@ -93,7 +93,7 @@
 <!## XC>
 &xconly;
  <para>
-  At failover, you should be careful to synchronize restration point of
+  At failover, you should be careful to synchronize restoration point of
   all the coordinators and datanodes.
   Barrier will help this synchronization.
   See <xref linkend="SQL-CREATEBARRIER"> for details.
@@ -1524,7 +1524,7 @@ if (!triggered)
     of <productname>Postgres-XC</productname>.
     Please note that <productname>Postgres-XC</productname> does not provide integrated database view
     to applications.
-    Please note that you cannot connect to hot standby node of datanodes through coordiantors.
+    Please note that you cannot connect to hot standby node of datanodes through coordinators.
     You can connect directly to hot-standby nodes using conventional manners and
     read only their local database.
    </para>