diff --git a/doc/src/sgml/advanced.sgml b/doc/src/sgml/advanced.sgml
index 1bbc16e..35c3b0b 100644
--- a/doc/src/sgml/advanced.sgml
+++ b/doc/src/sgml/advanced.sgml
@@ -9,14 +9,14 @@
   <para>
    <firstterm>Watchdog</firstterm> is a sub process of <productname>Pgpool-II</productname>
    to add high availability. Watchdog is used to resolve the single
-   point of failure by coordinating multiple <productname>pgpool-II</productname>
-   nodes. The watchdog was first introduced in <productname>pgpool-II</productname>
+   point of failure by coordinating multiple <productname>Pgpool-II</productname>
+   nodes. The watchdog was first introduced in <productname>Pgpool-II</productname>
    <emphasis>V3.2</emphasis> and is significantly enhanced in
-   <productname>pgpool-II</productname> <emphasis>V3.5</emphasis>, to ensure the presence of a
+   <productname>Pgpool-II</productname> <emphasis>V3.5</emphasis>, to ensure the presence of a
    quorum at all time. This new addition to watchdog makes it more fault tolerant
    and robust in handling and guarding against the split-brain syndrome
    and network partitioning. However to ensure the quorum mechanism properly
-   works, the number of pgpool-II nodes must be odd in number and greater than or
+   works, the number of Pgpool-II nodes must be odd in number and greater than or
    equal to 3.
   </para>
 
@@ -410,7 +410,7 @@
        the "NODES LIST DATA" result packet.
     </para>
     <para>
-     The result packet returnd by watchdog for the "GET NODES LIST"
+     The result packet returned by watchdog for the "GET NODES LIST"
      will contains the list of all configured watchdog nodes to do
      health check on in the <acronym>JSON</acronym> format.
      The <acronym>JSON</acronym> of the watchdog nodes contains the
@@ -516,7 +516,7 @@
     status and brings the virtual IP assigned to watchdog down.
     Thus clients of <productname>Pgpool-II</productname> cannot
     connect to <productname>Pgpool-II</productname> using the
-    virtual IP any more. This is neccessary to avoid split-brain,
+    virtual IP any more. This is necessary to avoid split-brain,
     that is, situations where there are multiple active
     <productname>Pgpool-II</productname>.
    </para>
diff --git a/doc/src/sgml/client-auth.sgml b/doc/src/sgml/client-auth.sgml
index 0d30821..8d633b1 100644
--- a/doc/src/sgml/client-auth.sgml
+++ b/doc/src/sgml/client-auth.sgml
@@ -13,8 +13,8 @@
   a <productname>PostgreSQL</productname> database client, so when a
   client application connects to
   the <productname>Pgpool-II</productname>, <productname>Pgpool-II</productname>
-  inturn connects to the <productname>PostgreSQL</productname> servers
-  using the same credentials to serve the incomming client
+  in turn connects to the <productname>PostgreSQL</productname> servers
+  using the same credentials to serve the incoming client
   connection. Thus, all the access privileges and restrictions defined
   for the user in <productname>PostgreSQL</productname> gets
   automatically applied to all <productname>Pgpool-II</productname>
@@ -28,7 +28,7 @@
   <productname>Pgpool-II</productname> server and not that of the actual client.
   Therefore, for the client host based authentications <productname>Pgpool-II</productname> has the
   <literal>pool_hba</literal> mechanism similar to the <literal>pg_hba</literal> mechanism for
-  authenticating the incomming client connections.
+  authenticating the incoming client connections.
  </para>
 
  <sect1 id="auth-pool-hba-conf">
diff --git a/doc/src/sgml/connection-pooling.sgml b/doc/src/sgml/connection-pooling.sgml
index eccb9dc..4233ac2 100644
--- a/doc/src/sgml/connection-pooling.sgml
+++ b/doc/src/sgml/connection-pooling.sgml
@@ -121,7 +121,7 @@
      </para>
 
      <para>
-      But serialization has its own overheads, and it is recomended
+      But serialization has its own overheads, and it is recommended
       to be used only with the larger values of <xref linkend="guc-num-init-children">.
        For the small number of <xref linkend="guc-num-init-children">,
 	the serialize accept can degrade the performance because of
@@ -130,8 +130,8 @@
 
      <note>
       <para>
-       It is recomended to do a benchmark before deciding wether to use
-       <varname>serialize_accept</varname> or not, because the corelation
+       It is recommended to do a benchmark before deciding whether to use
+       <varname>serialize_accept</varname> or not, because the correlation
        of <xref linkend="guc-num-init-children"> and <varname>serialize_accept</varname>
 	can be different on different environments.
       </para>
diff --git a/doc/src/sgml/connection-settings.sgml b/doc/src/sgml/connection-settings.sgml
index 7699700..6f2f411 100644
--- a/doc/src/sgml/connection-settings.sgml
+++ b/doc/src/sgml/connection-settings.sgml
@@ -710,7 +710,7 @@
       <productname>Pgpool-II</productname> <emphasis>V2.2</emphasis>
       or later, automatically detects whether the table has a
       SERIAL columns or not, so it never locks the table if it
-      desn't have the SERIAL columns.
+      doesn't have the SERIAL columns.
      </para>
 
      <para>
diff --git a/doc/src/sgml/examples.sgml b/doc/src/sgml/examples.sgml
index e4c1cd7..0da47d2 100644
--- a/doc/src/sgml/examples.sgml
+++ b/doc/src/sgml/examples.sgml
@@ -83,7 +83,7 @@
        $ cp /usr/local/etc/pgpool.conf.sample /usr/local/etc/pgpool.conf
       </programlisting>
       <productname>Pgpool-II</productname> only accepts connections from the localhost
-      using port 9999. If you wish to receive conenctions from other hosts,
+      using port 9999. If you wish to receive connections from other hosts,
       set <xref linkend="guc-listen-addresses"> to <literal>'*'</literal>.
        <programlisting>
 	listen_addresses = 'localhost'
@@ -523,7 +523,7 @@
        [root@osspc20]# {installed_dir}/bin/pgpool -n -f {installed_dir}/etc/pgpool.conf > pgpool.log 2>&1
       </programlisting>
       Log messages will show that <productname>Pgpool-II</productname>
-      has joind the watchdog cluster as standby watchdog.
+      has joined the watchdog cluster as standby watchdog.
       <programlisting>
        LOG:  watchdog cluster configured with 1 remote nodes
        LOG:  watchdog remote node:0 on Linux_osspc16_9000:9000
@@ -653,8 +653,8 @@
       There are the parameters about watchdog's monitoring.
       Specify the interval to check <xref linkend="guc-wd-interval">,
        the count to retry <xref linkend="guc-wd-life-point">,
-	the qyery to check <xref linkend="guc-wd-lifecheck-query"> and
-	 finaly the type of lifecheck <xref linkend="guc-wd-lifecheck-method">.
+	the query to check <xref linkend="guc-wd-lifecheck-query"> and
+	 finally the type of lifecheck <xref linkend="guc-wd-lifecheck-method">.
 	  <programlisting>
 	   wd_lifecheck_method = 'query'
 	   # Method of watchdog lifecheck ('heartbeat' or 'query' or 'external')
@@ -982,7 +982,7 @@
         <thead>
 	 <row>
 	  <entry>User Name</entry>
-	  <entry>Passowrd</entry>
+	  <entry>Password</entry>
 	  <entry>Detail</entry>
 	 </row>
         </thead>
@@ -1046,7 +1046,7 @@
       <para>
        To allow <literal>repl</literal> user without specifying password for streaming 
        replication and online recovery, we create the <filename>.pgpass</filename> file 
-       in <literal>postgres</literal> user's home directory and change the permisson  to 
+       in <literal>postgres</literal> user's home directory and change the permission  to
        <literal>600</literal> on each <productname>PostgreSQL</productname> server.
       </para>
       <programlisting>
@@ -1071,7 +1071,7 @@
      <para>
       When installing <productname>Pgpool-II</productname> from RPM,  all the 
       <productname>Pgpool-II</productname> configuration files are in <filename>/etc/pgpool-II</filename>. 
-      In this example, we copy the sample configuration file for streaming replicaton mode.
+      In this example, we copy the sample configuration file for streaming replication mode.
      </para>
      <programlisting>
       # cp /etc/pgpool-II/pgpool.conf.sample-stream /etc/pgpool-II/pgpool.conf
@@ -1113,7 +1113,7 @@
       health_check_max_retries = 3
      </programlisting>
      <para>
-      Specify the <productname>PostgreSQL</productname> backend informations.
+      Specify the <productname>PostgreSQL</productname> backend information.
       Multiple backends can be specified by adding a number at the end of the parameter name.
      </para>
      <programlisting>
@@ -1573,7 +1573,7 @@ exit 0
        </programlisting>
      </para>
      <para>
-      Execute command <command>pg_enc -m -k /path/to/.pgpoolkey -u username -p</command> to regist user 
+      Execute command <command>pg_enc -m -k /path/to/.pgpoolkey -u username -p</command> to register user
       name and <literal>AES</literal> encrypted password in file <filename>pool_passwd</filename>. 
       If <filename>pool_passwd</filename> doesn't exist yet, it will be created in the same directory as
       <filename>pgpool.conf</filename>.
@@ -1912,7 +1912,7 @@ exit 0
      </programlisting>
      <para>
       After executing <command>pcp_recovery_node</command> command, 
-      vertify that <literal>server2</literal> and <literal>server3</literal> 
+      verify that <literal>server2</literal> and <literal>server3</literal>
       are started as <productname>PostgreSQL</productname> standby server.
      </para>
      <programlisting>
@@ -1957,7 +1957,7 @@ exit 0
       server3:9999 Linux server3 server3 9999 9000 7 STANDBY    #server3 runs as STANDBY
      </programlisting>
      <para>
-      Start <productname>Pgpool-II</productname> (<literal>server1</literal>) which we have stopped again, and vertify that <literal>server1</literal> runs as a standby.
+      Start <productname>Pgpool-II</productname> (<literal>server1</literal>) which we have stopped again, and verify that <literal>server1</literal> runs as a standby.
      </para>
      <programlisting>
       [server1]# systemctl start pgpool.service
@@ -1975,7 +1975,7 @@ exit 0
     <sect3 id="example-cluster-try-failover">
      <title>Failover</title>
      <para>
-      First, use <command>psql</command> to connect to <productname>PostgreSQL</productname> via virtual IP, and verify the backend informations.
+      First, use <command>psql</command> to connect to <productname>PostgreSQL</productname> via virtual IP, and verify the backend information.
      </para>
      <programlisting>
       # psql -h 192.168.137.150 -p 9999 -U pgpool postgres -c "show pool_nodes"
@@ -2141,7 +2141,7 @@ exit 0
       <xref linkend="guc-delegate-ip"> which we will not set in this example instead
        we will use <xref linkend="guc-wd-escalation-command"> and
 	<xref linkend="guc-wd-de-escalation-command"> to switch the
-	 Elastic IP address to the maste/Active <productname>Pgpool-II</productname> node.
+	 Elastic IP address to the master/Active <productname>Pgpool-II</productname> node.
     </para>
 
     <sect3 id="example-AWS-pgpool-config-instance-1">
@@ -2407,7 +2407,7 @@ exit 0
 	Set <xref linkend="guc-sr-check-period"> to 0 to
 	 disable streaming replication delay checking.  This
 	 is because <productname>Aurora</productname> does
-	 not provide neccessary functions to check the
+	 not provide necessary functions to check the
 	 replication delay.
        </para>
       </listitem>
@@ -2431,7 +2431,7 @@ exit 0
 	 Aurora writer node.  Set
 	 other <xref linkend="guc-backend-hostname"> for the
 	  Aurora reader node.  Set
-	  appropreate <xref linkend="guc-backend-weight"> as
+	  appropriate <xref linkend="guc-backend-weight"> as
 	   usual. You don't need to
 	   set <xref linkend="guc-backend-data-directory">
        </para>
diff --git a/doc/src/sgml/failover.sgml b/doc/src/sgml/failover.sgml
index 6765bcf..c95a067 100644
--- a/doc/src/sgml/failover.sgml
+++ b/doc/src/sgml/failover.sgml
@@ -141,7 +141,7 @@
 	</row>
 	<row>
 	 <entry>%m</entry>
-	 <entry>	New master node ID</entry>
+	 <entry>New master node ID</entry>
 	</row>
 	<row>
 	 <entry>%H</entry>
@@ -149,7 +149,7 @@
 	</row>
 	<row>
 	 <entry>%P</entry>
-	 <entry>	Old primary node ID</entry>
+	 <entry>Old primary node ID</entry>
 	</row>
 	<row>
 	 <entry>%r</entry>
@@ -241,7 +241,7 @@
       Specifies a user command to run when a <productname>PostgreSQL</> backend node gets attached to
       <productname>Pgpool-II</productname>. <productname>Pgpool-II</productname>
       replaces the following special characters with the backend specific information.
-      before excuting the command.
+      before executing the command.
      </para>
 
      <table id="ffailback-command-table">
@@ -433,7 +433,7 @@
       <para>
        If <varname>follow_master_command</varname> is not empty, then after failover
        on the primary node gets completed in Master Slave mode with streaming replication,
-       <productname>Pgpool-II</productname> degenerates all nodes excepted the new primary
+       <productname>Pgpool-II</productname> degenerates all nodes except the new primary
        and starts new child processes to be ready again to accept connections from the clients.
        After this, <productname>Pgpool-II</productname> executes the command configured
        in the <varname>follow_master_command</varname> for each degenerated backend nodes.
diff --git a/doc/src/sgml/installation-rpm.sgml b/doc/src/sgml/installation-rpm.sgml
index 8d6fbd6..e82afb8 100644
--- a/doc/src/sgml/installation-rpm.sgml
+++ b/doc/src/sgml/installation-rpm.sgml
@@ -4,7 +4,7 @@
  <title>Installation from RPM</title>
  <para>
   This chapter describes the installation
-  of <productname>Pgpool-II</productname> from PRM.  If you are
+  of <productname>Pgpool-II</productname> from RPM.  If you are
   going to install from the source code, please
   check <xref linkend="install-source">.
  </para>
diff --git a/doc/src/sgml/loadbalance.sgml b/doc/src/sgml/loadbalance.sgml
index d59f336..5b6871a 100644
--- a/doc/src/sgml/loadbalance.sgml
+++ b/doc/src/sgml/loadbalance.sgml
@@ -180,7 +180,7 @@
 
     <listitem>
      <para>
-      COPY TO STODUT
+      COPY TO STDOUT
      </para>
     </listitem>
 
@@ -206,7 +206,7 @@
   </para>
 
   <para>
-   If writing queires appear, succeeding read queries may not be
+   If writing queries appear, succeeding read queries may not be
    load balanced. i.e. sent to primary node (in streaming
    replication mode) or master node (in other mode) depending on the
    setting of <xref linkend="guc-disable-load-balance-on-write">.
@@ -656,7 +656,7 @@
 	 </listitem>
 	 <listitem>
 	  <para>
-	   SQL including table_nama3
+	   SQL including table_name3
 	  </para>
 	 </listitem>
 	</itemizedlist>
@@ -863,13 +863,13 @@
 
      <caution>
       <para>
-       <acronym>JDBC</acronym> driver postgreSQL-9.3 and earlier versions
+       <acronym>JDBC</acronym> driver PostgreSQL-9.3 and earlier versions
        does not send the application name in the startup packet even if
        the application name is specified using the <acronym>JDBC</acronym>
        driver option <literal>"ApplicationName"</literal> and
        <literal>"assumeMinServerVersion=9.0"</literal>.
        So if you want to use the <xref linkend="guc-app-name-redirect-preference-list">
-	feature through <acronym>JDBC</acronym>, Use postgreSQL-9.4 or later version of the driver.
+	feature through <acronym>JDBC</acronym>, Use PostgreSQL-9.4 or later version of the driver.
       </para>
      </caution>
 
diff --git a/doc/src/sgml/memcache.sgml b/doc/src/sgml/memcache.sgml
index 01fbdd2..ac9ebcc 100644
--- a/doc/src/sgml/memcache.sgml
+++ b/doc/src/sgml/memcache.sgml
@@ -412,7 +412,7 @@
      </para>
 
      <para>
-      <varname>memqcache_cache_block_size</varname> must be set to atleast 512.
+      <varname>memqcache_cache_block_size</varname> must be set to at least 512.
      </para>
 
      <para>
diff --git a/doc/src/sgml/misc-config.sgml b/doc/src/sgml/misc-config.sgml
index 488f2a8..3c242d4 100644
--- a/doc/src/sgml/misc-config.sgml
+++ b/doc/src/sgml/misc-config.sgml
@@ -17,7 +17,7 @@
      Specifies the relation cache expiration time in seconds.
      The relation cache is used for caching the query result of
      <productname>PostgreSQL</> system catalogs that is used by <productname>Pgpool-II
-     </productname> to get various informations including the table
+     </productname> to get various information including the table
      structures and to check table types(e.g. To check if the referred
      table is a temporary table or not). The cache is maintained in
      the local memory space of <productname>Pgpool-II</productname>
diff --git a/doc/src/sgml/online-recovery.sgml b/doc/src/sgml/online-recovery.sgml
index 74f9011..4ccb26f 100644
--- a/doc/src/sgml/online-recovery.sgml
+++ b/doc/src/sgml/online-recovery.sgml
@@ -62,7 +62,7 @@
     safely leave it as an empty string.
  </para>
  <para>
-  Connections from cliens are not allowed only in the second stage
+  Connections from clients are not allowed only in the second stage
   while the data can be updated or retrieved during the first stage.
  </para>
  <para>
@@ -278,14 +278,14 @@
 
     <para>
      Specifies a command to be run by master node at the second
-     stage of online recovery. This parameter only neccessary for
+     stage of online recovery. This parameter only necessary for
      <xref linkend="guc-replication-mode">. The command file must
       be placed in the database cluster directory for security
       reasons.  For example,
       if <varname>recovery_2nd_stage_command</varname> = <literal>
        'sync-command'</literal>,
       then <productname>Pgpool-II</productname> will look for the
-      command scrit in <literal>$PGDATA</literal> directory and
+      command script in <literal>$PGDATA</literal> directory and
       will try to execute <command>$PGDATA/sync-command</command>.
     </para>
     <para>
diff --git a/doc/src/sgml/ref/pcp_detach_node.sgml b/doc/src/sgml/ref/pcp_detach_node.sgml
index e67563e..cf269db 100644
--- a/doc/src/sgml/ref/pcp_detach_node.sgml
+++ b/doc/src/sgml/ref/pcp_detach_node.sgml
@@ -17,7 +17,7 @@ Pgpool-II documentation
  <refnamediv>
   <refname>pcp_detach_node</refname>
   <refpurpose>
-   detaches the given node from Pgpool-II. Exisiting connections to Pgpool-II are forced to be disconnected.</refpurpose>
+   detaches the given node from Pgpool-II. Existing connections to Pgpool-II are forced to be disconnected.</refpurpose>
  </refnamediv>
 
  <refsynopsisdiv>
@@ -33,7 +33,7 @@ Pgpool-II documentation
   <title>Description</title>
   <para>
    <command>pcp_detach_node</command>
-   detaches the given node from Pgpool-II. Exisiting connections to Pgpool-II are forced to be disconnected.
+   detaches the given node from Pgpool-II. Existing connections to Pgpool-II are forced to be disconnected.
   </para>
  </refsect1>
 
diff --git a/doc/src/sgml/ref/pcp_watchdog_info.sgml b/doc/src/sgml/ref/pcp_watchdog_info.sgml
index b4d42e5..088a9df 100644
--- a/doc/src/sgml/ref/pcp_watchdog_info.sgml
+++ b/doc/src/sgml/ref/pcp_watchdog_info.sgml
@@ -52,7 +52,7 @@ Pgpool-II documentation
        Index 0 gets one's self watchdog information.
       </para>
       <para>
-       If ommitted then gets information of all watchdog nodes.
+       If omitted then gets information of all watchdog nodes.
       </para>
      </listitem>
     </varlistentry>
diff --git a/doc/src/sgml/ref/pgpool.sgml b/doc/src/sgml/ref/pgpool.sgml
index 978dab8..1665303 100644
--- a/doc/src/sgml/ref/pgpool.sgml
+++ b/doc/src/sgml/ref/pgpool.sgml
@@ -100,7 +100,7 @@ Pgpool-II documentation
      <listitem>
       <para>
        Set the path to the <filename>.pgpoolkey</filename> file.
-       Mandatory if you use AES256 encrypted password and the file is placed other than the standard locatiaon and used.
+       Mandatory if you use AES256 encrypted password and the file is placed other than the standard location and used.
       </para>
      </listitem>
     </varlistentry>
@@ -229,7 +229,7 @@ Pgpool-II documentation
   <para>
    Reload configuration file
    of <productname>Pgpool-II</productname>. No specific options
-   exist for realod mode. Common options are applicable.
+   exist for reload mode. Common options are applicable.
   </para>
  </refsect1>
 
diff --git a/doc/src/sgml/ref/show_pool_nodes.sgml b/doc/src/sgml/ref/show_pool_nodes.sgml
index 1bbacb1..cf2c428 100644
--- a/doc/src/sgml/ref/show_pool_nodes.sgml
+++ b/doc/src/sgml/ref/show_pool_nodes.sgml
@@ -35,7 +35,7 @@
    hostname, the port, the status, the weight (only meaningful if
    you use the load balancing mode), the role, the SELECT query
    counts issued to each backend, whether each node is the load
-   bakance node or not, the replication delay (only if in streaming
+   balance node or not, the replication delay (only if in streaming
    replication mode) and last status change time. The possible
    values in the status column are explained in
    the <xref linkend="pcp-node-info"> reference. If the hostname is
diff --git a/doc/src/sgml/reference.sgml b/doc/src/sgml/reference.sgml
index c8b4be2..0ceaec1 100644
--- a/doc/src/sgml/reference.sgml
+++ b/doc/src/sgml/reference.sgml
@@ -189,7 +189,7 @@
     to <productname>PostgreSQL</productname> with the result
     (3). <productname>PostgreSQL</productname> returns the result
     to <productname>Pgpool-II</productname> (5)
-    and <productname>Pgpool-II</productname> fowards the data to
+    and <productname>Pgpool-II</productname> forwards the data to
     the user (6).
    </para>
    <para>
@@ -214,7 +214,7 @@
     of <productname>PostgreSQL</productname>.  The pcp port number
     is hard coded as 9898, the pcp user name is assumes to be same
     as caller's <productname>PostgreSQL</productname> user name.
-    password is extraced from $HOME/.pcppass.
+    password is extracted from $HOME/.pcppass.
    </para>
 
    <sect1 id="installing-pgpool-adm">
diff --git a/doc/src/sgml/release-3.2.sgml b/doc/src/sgml/release-3.2.sgml
index ecb5816..4b446f3 100644
--- a/doc/src/sgml/release-3.2.sgml
+++ b/doc/src/sgml/release-3.2.sgml
@@ -216,7 +216,7 @@
     </para>
 
     <para>
-     This status mismatch should be fixe by pcp_promote_node, but when the node
+     This status mismatch should be fixed by pcp_promote_node, but when the node
      is the master node (the first alive node), it fails as mentioned above.
     </para>
 
@@ -299,7 +299,7 @@
     2016-12-28 [afebadf]
     -->
     <para>
-     Fix authentication timeout that can occur right after client connecttions. (Yugo Nagata)
+     Fix authentication timeout that can occur right after client connections. (Yugo Nagata)
     </para>
    </listitem>
 
diff --git a/doc/src/sgml/release-3.3.sgml b/doc/src/sgml/release-3.3.sgml
index cb3342c..38a376a 100644
--- a/doc/src/sgml/release-3.3.sgml
+++ b/doc/src/sgml/release-3.3.sgml
@@ -133,7 +133,7 @@
      Change the <filename>pgpool.service</filename> and sysconfig files to output <productname>Pgpool-II</productname> log. (Bo Peng)
     </para>
     <para>
-     Removeing "Type=forking" and add OPTS=" -n" to
+     Removing "Type=forking" and add OPTS=" -n" to
      run <productname>Pgpool-II</productname> with non-daemon mode, because we need to redirect logs.
      Using <command>"journalctl"</command> command to see <productname>Pgpool-II</productname> systemd log.
     </para>
@@ -167,7 +167,7 @@
      frontend. In most cases this is good. However if other than primary
      node or master node returns an error state (this could happen if load
      balance node is other than primary or master node and the query is an
-     errornous SELECT), this should be returned to frontend, because the
+     erroneous SELECT), this should be returned to frontend, because the
      frontend already received an error.
     </para>
    </listitem>
@@ -208,7 +208,7 @@
      Fix bug mistakenly overriding global backend status right after failover. (Tatsuo Ishii)
     </para>
     <para>
-     See <ulink url="http://www.sraoss.jp/pipermail/pgpool-general/2017-September/005786.html">[pgpool-general: 5728]</ulink> for mor details.
+     See <ulink url="http://www.sraoss.jp/pipermail/pgpool-general/2017-September/005786.html">[pgpool-general: 5728]</ulink> for more details.
     </para>
    </listitem>
 
@@ -416,7 +416,7 @@
     2017-03-24 [dab2ff0]
     -->
     <para>
-     Fix for 0000296: PGPool v3.6.2 terminated by systemd because the service Type has been set to 'forking'.
+     Fix for 0000296: Pgpool v3.6.2 terminated by systemd because the service Type has been set to 'forking'.
      <ulink url="http://www.pgpool.net/mantisbt/view.php?id=296">(Bug 296)</ulink> (Muhammad Usama)
     </para>
    </listitem>
@@ -476,7 +476,7 @@
     </para>
 
     <para>
-     This status mismatch should be fixe by pcp_promote_node, but when the node
+     This status mismatch should be fixed by pcp_promote_node, but when the node
      is the master node (the first alive node), it fails as mentioned above.
     </para>
 
@@ -589,7 +589,7 @@
     2016-12-28 [afebadf]
     -->
     <para>
-     Fix authentication timeout that can occur right after client connecttions. (Yugo Nagata)
+     Fix authentication timeout that can occur right after client connections. (Yugo Nagata)
     </para>
    </listitem>
 
diff --git a/doc/src/sgml/release-3.4.sgml b/doc/src/sgml/release-3.4.sgml
index 99f78d9..de7f643 100644
--- a/doc/src/sgml/release-3.4.sgml
+++ b/doc/src/sgml/release-3.4.sgml
@@ -239,7 +239,7 @@
      (<ulink url="http://www.pgpool.net/mantisbt/view.php?id=487">bug 487</>) (Bo Peng)
     </para>
     <para>
-     When all backend nodes are down, <productname>Pgpool-II</> throws an uncorrect
+     When all backend nodes are down, <productname>Pgpool-II</> throws an incorrect
      error message "ERROR: connection cache is full". Change the error
      message to "all backend nodes are down, pgpool requires at least one valid node".
     </para>
@@ -474,7 +474,7 @@
     </para>
     <para>
      If order of startup packet's parameters differ between cached connection
-     pools and connection request, did't use connection pool ,and created new
+     pools and connection request, didn't use connection pool ,and created new
      connection pool.
     </para>
    </listitem>
@@ -635,7 +635,7 @@
     </para>
     <para>
      In a explicit transaction, the <literal>SELECT</literal> results are cached in temporary buffer.
-     If a write <acronym>SQL</acronym> is sent which modifies the table, the temporary buffe should be reset.
+     If a write <acronym>SQL</acronym> is sent which modifies the table, the temporary buffer should be reset.
     </para>
    </listitem>
 
@@ -979,7 +979,7 @@
      Change the <filename>pgpool.service</filename> and sysconfig files to output <productname>Pgpool-II</productname> log. (Bo Peng)
     </para>
     <para>
-     Removeing "Type=forking" and add OPTS=" -n" to
+     Removing "Type=forking" and add OPTS=" -n" to
      run <productname>Pgpool-II</productname> with non-daemon mode, because we need to redirect logs.
      Using <command>"journalctl"</command> command to see <productname>Pgpool-II</productname> systemd log.
     </para>
@@ -1013,7 +1013,7 @@
      frontend. In most cases this is good. However if other than primary
      node or master node returns an error state (this could happen if load
      balance node is other than primary or master node and the query is an
-     errornous SELECT), this should be returned to frontend, because the
+     erroneous SELECT), this should be returned to frontend, because the
      frontend already received an error.
     </para>
    </listitem>
@@ -1072,7 +1072,7 @@
      Fix bug mistakenly overriding global backend status right after failover. (Tatsuo Ishii)
     </para>
     <para>
-     See <ulink url="http://www.sraoss.jp/pipermail/pgpool-general/2017-September/005786.html">[pgpool-general: 5728]</ulink> for mor details.
+     See <ulink url="http://www.sraoss.jp/pipermail/pgpool-general/2017-September/005786.html">[pgpool-general: 5728]</ulink> for more details.
     </para>
    </listitem>
 
@@ -1326,7 +1326,7 @@
     2017-03-24 [1172e6c]
     -->
     <para>
-     Fix for 0000296: PGPool v3.6.2 terminated by systemd because the service Type has been set to 'forking'.
+     Fix for 0000296: Pgpool v3.6.2 terminated by systemd because the service Type has been set to 'forking'.
      <ulink url="http://www.pgpool.net/mantisbt/view.php?id=296">(Bug 296)</ulink> (Muhammad Usama)
     </para>
    </listitem>
@@ -1385,7 +1385,7 @@
     </para>
 
     <para>
-     This status mismatch should be fixe by pcp_promote_node, but when the node
+     This status mismatch should be fixed by pcp_promote_node, but when the node
      is the master node (the first alive node), it fails as mentioned above.
     </para>
 
@@ -1572,7 +1572,7 @@
     2016-12-28 [afebadf]
     -->
     <para>
-     Fix authentication timeout that can occur right after client connecttions. (Yugo Nagata)
+     Fix authentication timeout that can occur right after client connections. (Yugo Nagata)
     </para>
    </listitem>
 
diff --git a/doc/src/sgml/release-3.5.sgml b/doc/src/sgml/release-3.5.sgml
index 7557bd8..f1a7144 100644
--- a/doc/src/sgml/release-3.5.sgml
+++ b/doc/src/sgml/release-3.5.sgml
@@ -16,7 +16,7 @@
     2020-01-28 [d60e6b7]
     -->
     <para>
-     Check if socket file exists at startup and remove them if PID file doesn't exist to avoid bind() failire. (Bo Peng)
+     Check if socket file exists at startup and remove them if PID file doesn't exist to avoid bind() failure. (Bo Peng)
     </para>
    </listitem>
   </itemizedlist>
@@ -262,7 +262,7 @@
     2019-07-03 [380d8a5]
     -->
     <para>
-     Fix sefault when query cache is enabled. (<ulink url="https://www.pgpool.net/mantisbt/view.php?id=525">bug 525</ulink>) (Tatsuo Ishii)
+     Fix segfault when query cache is enabled. (<ulink url="https://www.pgpool.net/mantisbt/view.php?id=525">bug 525</ulink>) (Tatsuo Ishii)
     </para>
    </listitem>
 
@@ -376,7 +376,7 @@
      (<ulink url="http://www.pgpool.net/mantisbt/view.php?id=487">bug 487</>) (Bo Peng)
     </para>
     <para>
-     When all backend nodes are down, <productname>Pgpool-II</> throws an uncorrect
+     When all backend nodes are down, <productname>Pgpool-II</> throws an incorrect
      error message "ERROR: connection cache is full". Change the error
      message to "all backend nodes are down, pgpool requires at least one valid node".
     </para>
@@ -654,7 +654,7 @@
     </para>
     <para>
      If order of startup packet's  parameters differ between cached connection
-     pools and connection request, did't use connection pool ,and created new
+     pools and connection request, didn't use connection pool ,and created new
      connection pool.
     </para>
    </listitem>
@@ -859,7 +859,7 @@
     </para>
     <para>
      In a explicit transaction, the <literal>SELECT</literal> results are cached in temporary buffer.
-     If a write <acronym>SQL</acronym> is sent which modifies the table, the temporary buffe should be reset.
+     If a write <acronym>SQL</acronym> is sent which modifies the table, the temporary buffer should be reset.
     </para>
    </listitem>
 
@@ -1298,7 +1298,7 @@
      Change the <filename>pgpool.service</filename> and sysconfig files to output <productname>Pgpool-II</productname> log. (Bo Peng)
     </para>
     <para>
-     Removeing "Type=forking" and add OPTS=" -n" to
+     Removing "Type=forking" and add OPTS=" -n" to
      run <productname>Pgpool-II</productname> with non-daemon mode, because we need to redirect logs.
      Using <command>"journalctl"</command> command to see <productname>Pgpool-II</productname> systemd log.
     </para>
@@ -1384,7 +1384,7 @@
      frontend. In most cases this is good. However if other than primary
      node or master node returns an error state (this could happen if load
      balance node is other than primary or master node and the query is an
-     errornous SELECT), this should be returned to frontend, because the
+     erroneous SELECT), this should be returned to frontend, because the
      frontend already received an error.
     </para>
    </listitem>
@@ -1497,7 +1497,7 @@
      Fix bug mistakenly overriding global backend status right after failover. (Tatsuo Ishii)
     </para>
     <para>
-     See <ulink url="http://www.sraoss.jp/pipermail/pgpool-general/2017-September/005786.html">[pgpool-general: 5728]</ulink> for mor details.
+     See <ulink url="http://www.sraoss.jp/pipermail/pgpool-general/2017-September/005786.html">[pgpool-general: 5728]</ulink> for more details.
     </para>
    </listitem>
 
@@ -1558,7 +1558,7 @@
     2017-09-01 [ad90886]
     -->
     <para>
-     Fix <varname>wd_authkey</varname> bug in that a request to add new node to the clusetr is rejected by master. (Yugo Nagata)
+     Fix <varname>wd_authkey</varname> bug in that a request to add new node to the cluster is rejected by master. (Yugo Nagata)
     </para>
     <para>
      This is a bug due to the implementation of 3.5.6 and 3.6.3.
@@ -1850,10 +1850,10 @@
     2017-06-09 [b86e7b7]
     -->
     <para>
-     Fix a posible hang with streaming replication and extended protocol (Yugo Nagata)
+     Fix a possible hang with streaming replication and extended protocol (Yugo Nagata)
     </para>
     <para>
-     This hang occured under a certain condition. The following is an example.
+     This hang occurred under a certain condition. The following is an example.
     </para>
 
     <programlisting>
@@ -1864,7 +1864,7 @@
     </programlisting>
 
     <para>
-     Without using <productname>JDBC</productname>, we can reproduce the problem by <productname>pgproto</productname> with the followeing messages.
+     Without using <productname>JDBC</productname>, we can reproduce the problem by <productname>pgproto</productname> with the following messages.
     </para>
 
     <programlisting>
@@ -2271,7 +2271,7 @@
     2017-03-24 [d726c3a]
     -->
     <para>
-     Fix for 0000296: PGPool v3.6.2 terminated by systemd because the service Type has been set to 'forking'.
+     Fix for 0000296: Pgpool v3.6.2 terminated by systemd because the service Type has been set to 'forking'.
      <ulink url="http://www.pgpool.net/mantisbt/view.php?id=296">(Bug 296)</ulink> (Muhammad Usama)
     </para>
    </listitem>
@@ -2330,7 +2330,7 @@
     </para>
 
     <para>
-     This status mismatch should be fixe by pcp_promote_node, but when the node
+     This status mismatch should be fixed by pcp_promote_node, but when the node
      is the master node (the first alive node), it fails as mentioned above.
     </para>
 
@@ -2584,7 +2584,7 @@
     2016-12-28 [afebadf]
     -->
     <para>
-     Fix authentication timeout that can occur right after client connecttions. (Yugo Nagata)
+     Fix authentication timeout that can occur right after client connections. (Yugo Nagata)
     </para>
    </listitem>
 
@@ -2689,7 +2689,7 @@
       </listitem>
       <listitem>
        <para>
-	Pgool-II forward it to backend 1
+	Pgpool-II forward it to backend 1
        </para>
       </listitem>
       <listitem>
@@ -2699,7 +2699,7 @@
       </listitem>
       <listitem>
        <para>
-	Pgool-II forward it to backend 0 & 1
+	Pgpool-II forward it to backend 0 & 1
        </para>
       </listitem>
       <listitem>
@@ -2709,7 +2709,7 @@
       </listitem>
       <listitem>
        <para>
-	Pgool-II forward it to backend 0 & 1
+	Pgpool-II forward it to backend 0 & 1
        </para>
       </listitem>
       <listitem>
diff --git a/doc/src/sgml/release-3.6.sgml b/doc/src/sgml/release-3.6.sgml
index 32bbad6..7c4e1a1 100644
--- a/doc/src/sgml/release-3.6.sgml
+++ b/doc/src/sgml/release-3.6.sgml
@@ -16,7 +16,7 @@
     2020-01-28 [d60e6b7]
     -->
     <para>
-     Check if socket file exists at startup and remove them if PID file doesn't exist to avoid bind() failire. (Bo Peng)
+     Check if socket file exists at startup and remove them if PID file doesn't exist to avoid bind() failure. (Bo Peng)
     </para>
    </listitem>
   </itemizedlist>
@@ -337,7 +337,7 @@
     2019-07-03 [380d8a5]
     -->
     <para>
-     Fix sefault when query cache is enabled. (<ulink url="https://www.pgpool.net/mantisbt/view.php?id=525">bug 525</ulink>) (Tatsuo Ishii)
+     Fix segfault when query cache is enabled. (<ulink url="https://www.pgpool.net/mantisbt/view.php?id=525">bug 525</ulink>) (Tatsuo Ishii)
     </para>
    </listitem>
 
@@ -490,7 +490,7 @@
      (<ulink url="http://www.pgpool.net/mantisbt/view.php?id=487">bug 487</>) (Bo Peng)
     </para>
     <para>
-     When all backend nodes are down, <productname>Pgpool-II</> throws an uncorrect
+     When all backend nodes are down, <productname>Pgpool-II</> throws an incorrect
      error message "ERROR: connection cache is full". Change the error
      message to "all backend nodes are down, pgpool requires at least one valid node".
     </para>
@@ -828,7 +828,7 @@
     </para>
     <para>
      If order of startup packet's  parameters differ between cached connection
-     pools and connection request, did't use connection pool ,and created new
+     pools and connection request, didn't use connection pool ,and created new
      connection pool.
     </para>
    </listitem>
@@ -1070,7 +1070,7 @@
     </para>
     <para>
      In a explicit transaction, the <literal>SELECT</literal> results are cached in temporary buffer.
-     If a write <acronym>SQL</acronym> is sent which modifies the table, the temporary buffe should be reset.
+     If a write <acronym>SQL</acronym> is sent which modifies the table, the temporary buffer should be reset.
     </para>
    </listitem>
 
@@ -1675,7 +1675,7 @@
      Change the <filename>pgpool.service</filename> and sysconfig files to output <productname>Pgpool-II</productname> log. (Bo Peng)
     </para>
     <para>
-     Removeing "Type=forking" and add OPTS=" -n" to
+     Removing "Type=forking" and add OPTS=" -n" to
      run <productname>Pgpool-II</productname> with non-daemon mode, because we need to redirect logs.
      Using <command>"journalctl"</command> command to see <productname>Pgpool-II</productname> systemd log.
     </para>
@@ -1785,7 +1785,7 @@
      frontend. In most cases this is good. However if other than primary
      node or master node returns an error state (this could happen if load
      balance node is other than primary or master node and the query is an
-     errornous SELECT), this should be returned to frontend, because the
+     erroneous SELECT), this should be returned to frontend, because the
      frontend already received an error.
     </para>
    </listitem>
@@ -1907,7 +1907,7 @@
      Fix bug mistakenly overriding global backend status right after failover. (Tatsuo Ishii)
     </para>
     <para>
-     See <ulink url="http://www.sraoss.jp/pipermail/pgpool-general/2017-September/005786.html">[pgpool-general: 5728]</ulink> for mor details.
+     See <ulink url="http://www.sraoss.jp/pipermail/pgpool-general/2017-September/005786.html">[pgpool-general: 5728]</ulink> for more details.
     </para>
    </listitem>
 
@@ -1977,7 +1977,7 @@
     2017-09-01 [b661a8b]
     -->
     <para>
-     Fix <varname>wd_authkey</varname> bug in that a request to add new node to the clusetr is rejected by master. (Yugo Nagata)
+     Fix <varname>wd_authkey</varname> bug in that a request to add new node to the cluster is rejected by master. (Yugo Nagata)
     </para>
     <para>
      This is a bug due to the implementation of 3.5.6 and 3.6.3.
@@ -2203,7 +2203,7 @@
     2017-08-21 [1812a84]
     -->
     <para>
-     Doc: Add new English and Japanese documents of <link linkend="example-cluster">Pgpoo-II + Watchdog Setup Example</link>. (Bo Peng)
+     Doc: Add new English and Japanese documents of <link linkend="example-cluster">Pgpool-II + Watchdog Setup Example</link>. (Bo Peng)
     </para>
    </listitem>
 
@@ -2289,11 +2289,11 @@
     2017-06-09 [d9b0b83]
     -->
     <para>
-     Fix a posible hang with streaming replication and extended protocol. (Yugo Nagata)
+     Fix a possible hang with streaming replication and extended protocol. (Yugo Nagata)
     </para>
 
     <para>
-     This hang occured under a certain condition. The following is an example.
+     This hang occurred under a certain condition. The following is an example.
     </para>
 
     <programlisting>
@@ -2304,7 +2304,7 @@
     </programlisting>
 
     <para>
-     Without using <productname>JDBC</productname>, we can reproduce the problem by <productname>pgproto</productname> with the followeing messages.
+     Without using <productname>JDBC</productname>, we can reproduce the problem by <productname>pgproto</productname> with the following messages.
     </para>
 
     <programlisting>
@@ -2587,7 +2587,7 @@
     2017-04-14 [50fb9a4]
     -->
     <para>
-     Removing the function defined but not used warnings from pool_config_vatiable.c (Muhammad Usama)
+     Removing the function defined but not used warnings from pool_config_variable.c (Muhammad Usama)
     </para>
    </listitem>
 
@@ -2843,7 +2843,7 @@
     2017-03-24 [c2a0cc5]
     -->
     <para>
-     Fix for 0000296: PGPool v3.6.2 terminated by systemd because the service Type has been set to 'forking'.
+     Fix for 0000296: Pgpool v3.6.2 terminated by systemd because the service Type has been set to 'forking'.
      <ulink url="http://www.pgpool.net/mantisbt/view.php?id=296">(Bug 296)</ulink> (Muhammad Usama)
     </para>
    </listitem>
@@ -2903,7 +2903,7 @@
     </para>
 
     <para>
-     This status mismatch should be fixe by pcp_promote_node, but when the node
+     This status mismatch should be fixed by pcp_promote_node, but when the node
      is the master node (the first alive node), it fails as mentioned above.
     </para>
 
@@ -3158,7 +3158,7 @@
     2016-12-28 [afebadf]
     -->
     <para>
-     Fix authentication timeout that can occur right after client connecttions. (Yugo Nagata)
+     Fix authentication timeout that can occur right after client connections. (Yugo Nagata)
     </para>
    </listitem>
 
@@ -3261,7 +3261,7 @@
       </listitem>
       <listitem>
        <para>
-	Pgool-II forward it to backend 1
+	Pgpool-II forward it to backend 1
        </para>
       </listitem>
       <listitem>
@@ -3271,7 +3271,7 @@
       </listitem>
       <listitem>
        <para>
-	Pgool-II forward it to backend 0 & 1
+	Pgpool-II forward it to backend 0 & 1
        </para>
       </listitem>
       <listitem>
@@ -3281,7 +3281,7 @@
       </listitem>
       <listitem>
        <para>
-	Pgool-II forward it to backend 0 & 1
+	Pgpool-II forward it to backend 0 & 1
        </para>
       </listitem>
       <listitem>
@@ -3557,7 +3557,7 @@
     restart. Watchdog not syncing status.
     -->
     <para>
-     Sync inconsitent status
+     Sync inconsistent status
      of <productname>PostgreSQL</productname> nodes
      in <productname>Pgpool-II</productname> instances after
      restart. (bug 218) (Muhammad Usama)
@@ -3691,7 +3691,7 @@
     2016-08-18 [d3211dc] Let watchdog_setup to be installed.
     -->
     <para>
-     Add new script called "watchdog_setup". (Tatstuo Ishii)
+     Add new script called "watchdog_setup". (Tatsuo Ishii)
     </para>
     <para>
      <xref linkend="WATCHDOG-SETUP"> is a command to create a
@@ -3742,7 +3742,7 @@
      Do not update status file if all backend nodes are in down status. (Chris Pacejo, Tatsuo Ishii)
     </para>
     <para>
-     This commit tries to remove the data inconsitency in
+     This commit tries to remove the data inconsistency in
      replication mode found
      in <ulink url="http://www.pgpool.net/pipermail/pgpool-general/2015-August/003974.html">[pgpool-general:
       3918]</ulink> by not recording the status file when all
@@ -3839,7 +3839,7 @@
     -->
     <para>
      Change the default value of
-     <xref linkend="guc-search-primary-node-timeout"> from 10 to 300. (Tatstuo Ishii)
+     <xref linkend="guc-search-primary-node-timeout"> from 10 to 300. (Tatsuo Ishii)
     </para>
     <para>
      Prior default value 10 seconds is sometimes too short for a standby to
@@ -4081,10 +4081,10 @@
    </listitem>
    <listitem>
     <!--
-    2016-08-01 [024eaea]  Fix for 215: pgpool doesnt escalate ip in case of another node inavailability
+    2016-08-01 [024eaea]  Fix for 215: pgpool doesnt escalate ip in case of another node unavailability
     -->
     <para>
-     Fix <productname>Pgpool-II</productname> doesn't escalate ip in case of another node inavailability. (bug 215) (Muhammad Usama)
+     Fix <productname>Pgpool-II</productname> doesn't escalate ip in case of another node unavailability. (bug 215) (Muhammad Usama)
     </para>
     <para>
      The heartbeat receiver fails to identify the heartbeat sender watchdog node when
@@ -4260,16 +4260,16 @@
    </listitem>
    <listitem>
     <!--
-    2016-06-08 [294cf4a]  Fix a posible hang during health checking
+    2016-06-08 [294cf4a]  Fix a possible hang during health checking
     -->
     <para>
-     Fix a posible hang during health checking. (bug 204) (Yugo Nagata)
+     Fix a possible hang during health checking. (bug 204) (Yugo Nagata)
     </para>
     <para>
-     Helath checking was hang when any data wasn't sent
+     Health checking was hang when any data wasn't sent
      from backend after <function>connect(2)</function> succeeded. To fix this,
      <function>pool_check_fd()</function> returns 1 when <function>select(2)</function> exits with
-     EINTR due to SIGALRM while health checkking is performed.
+     EINTR due to SIGALRM while health checking is performed.
     </para>
    </listitem>
    <listitem>
@@ -4348,13 +4348,13 @@
    </listitem>
    <listitem>
     <!--
-    2016-05-11 [de905f6]  Fix documetation bug about raw mode
+    2016-05-11 [de905f6]  Fix documentation bug about raw mode
     -->
     <para>
-     Fix  Japanese and Chinese documetation bug about raw mode. (Yugo Nagata, Bo Peng)
+     Fix  Japanese and Chinese documentation bug about raw mode. (Yugo Nagata, Bo Peng)
     </para>
     <para>
-     Connection pool is avalilable in raw mode.
+     Connection pool is available in raw mode.
     </para>
    </listitem>
    <listitem>
@@ -4464,7 +4464,7 @@
      Fix pgpool hung after receiving error state from backend. (bug #169) (Tatsuo Ishii)
     </para>
     <para>
-     This could happend if we execute an extended protocol query and it
+     This could happen if we execute an extended protocol query and it
      fails.
     </para>
    </listitem>
@@ -4473,7 +4473,7 @@
     2016-03-03 [bb295a2]  Fix query stack problems in extended protocol case.
     -->
     <para>
-     Fix query stack problems in extended protocol case. (bug 167, 168) (Tatstuo Ishii)
+     Fix query stack problems in extended protocol case. (bug 167, 168) (Tatsuo Ishii)
     </para>
     <para>
     </para>
@@ -4520,10 +4520,10 @@
    </listitem>
    <listitem>
     <!--
-    2016-02-03 [48e9d4b]  Fix for [pgpool-II 0000166]: compile issue on freebsd
+    2016-02-03 [48e9d4b]  Fix for [pgpool-II 0000166]: compile issue on FreeBSD
     -->
     <para>
-     Fix compile issue on freebsd. (Muhammad Usama)
+     Fix compile issue on FreeBSD. (Muhammad Usama)
     </para>
     <para>
      Add missing include files. The patch is contributed by
@@ -4547,7 +4547,7 @@
     </para>
     <para>
      Sometimes <xref linkend="guc-wd-authkey"> calculation fails for some reason other than
-      authkey mismatch. The additional messages make these distingushable
+      authkey mismatch. The additional messages make these distinguishable
       for each other.
     </para>
    </listitem>
diff --git a/doc/src/sgml/release-3.7.sgml b/doc/src/sgml/release-3.7.sgml
index 2c653d2..fbd4e26 100644
--- a/doc/src/sgml/release-3.7.sgml
+++ b/doc/src/sgml/release-3.7.sgml
@@ -35,7 +35,7 @@
     2020-01-28 [abbba81]
     -->
     <para>
-     Check if socket file exists at startup and remove them if PID file doesn't exist to avoid bind() failire. (Bo Peng)
+     Check if socket file exists at startup and remove them if PID file doesn't exist to avoid bind() failure. (Bo Peng)
     </para>
    </listitem>
   </itemizedlist>
@@ -262,7 +262,7 @@
     2019-09-04 [3ba4e73]
     -->
     <para>
-     Doc: mention that VIP will not be brougt up if quorum does not exist. (Tatsuo Ishii)
+     Doc: mention that VIP will not be brought up if quorum does not exist. (Tatsuo Ishii)
     </para>
     <para>
      
@@ -467,7 +467,7 @@
     2019-07-03 [380d8a5]
     -->
     <para>
-     Fix sefault when query cache is enabled. (<ulink url="https://www.pgpool.net/mantisbt/view.php?id=525">bug 525</ulink>) (Tatsuo Ishii)
+     Fix segfault when query cache is enabled. (<ulink url="https://www.pgpool.net/mantisbt/view.php?id=525">bug 525</ulink>) (Tatsuo Ishii)
     </para>
    </listitem>
 
@@ -631,7 +631,7 @@
      (<ulink url="http://www.pgpool.net/mantisbt/view.php?id=487">bug 487</>) (Bo Peng)
     </para>
     <para>
-     When all backend nodes are down, <productname>Pgpool-II</> throws an uncorrect
+     When all backend nodes are down, <productname>Pgpool-II</> throws an incorrect
      error message "ERROR: connection cache is full". Change the error
      message to "all backend nodes are down, pgpool requires at least one valid node".
     </para>
@@ -996,7 +996,7 @@
     </para>
     <para>
      If order of startup packet's  parameters differ between cached connection
-     pools and connection request, did't use connection pool ,and created new
+     pools and connection request, didn't use connection pool ,and created new
      connection pool.
     </para>
    </listitem>
@@ -1237,7 +1237,7 @@
     </para>
     <para>
      In a explicit transaction, the <literal>SELECT</literal> results are cached in temporary buffer.
-     If a write <acronym>SQL</acronym> is sent which modifies the table, the temporary buffe should be reset.
+     If a write <acronym>SQL</acronym> is sent which modifies the table, the temporary buffer should be reset.
     </para>
    </listitem>
 
@@ -2085,7 +2085,7 @@
      Change the <filename>pgpool.service</filename> and sysconfig files to output <productname>Pgpool-II</productname> log. (Bo Peng)
     </para>
     <para>
-     Removeing "Type=forking" and add OPTS=" -n" to
+     Removing "Type=forking" and add OPTS=" -n" to
      run <productname>Pgpool-II</productname> with non-daemon mode, because we need to redirect logs.
      Using <command>"journalctl"</command> command to see <productname>Pgpool-II</productname> systemd log.
     </para>
@@ -2225,7 +2225,7 @@
      frontend. In most cases this is good. However if other than primary
      node or master node returns an error state (this could happen if load
      balance node is other than primary or master node and the query is an
-     errornous SELECT), this should be returned to frontend, because the
+     erroneous SELECT), this should be returned to frontend, because the
      frontend already received an error.
     </para>
    </listitem>
@@ -2587,7 +2587,7 @@
     2017-09-19 [34922b5]
     -->
     <para>
-     Test: Add new test 011.watchdoc_quorum_failover. (Tatsuo Ishii)
+     Test: Add new test 011.watchdog_quorum_failover. (Tatsuo Ishii)
     </para>
    </listitem>
 
diff --git a/doc/src/sgml/release-4.0.sgml b/doc/src/sgml/release-4.0.sgml
index 408e966..6b75f7c 100644
--- a/doc/src/sgml/release-4.0.sgml
+++ b/doc/src/sgml/release-4.0.sgml
@@ -35,7 +35,7 @@
     2020-01-28 [304e091]
     -->
     <para>
-     Check if socket file exists at startup and remove them if PID file doesn't exist to avoid bind() failire. (Bo Peng)
+     Check if socket file exists at startup and remove them if PID file doesn't exist to avoid bind() failure. (Bo Peng)
     </para>
    </listitem>
   </itemizedlist>
@@ -93,7 +93,7 @@
     2020-01-28 [f8bbd91]
     -->
     <para>
-     Doc: Change the sample follow_master_command script %M %H paramater's order. (Bo Peng)
+     Doc: Change the sample follow_master_command script %M %H parameter's order. (Bo Peng)
     </para>
     <para>
      
@@ -303,7 +303,7 @@
     2019-09-04 [3ba4e73]
     -->
     <para>
-     Doc: mention that VIP will not be brougt up if quorum does not exist. (Tatsuo Ishii)
+     Doc: mention that VIP will not be brought up if quorum does not exist. (Tatsuo Ishii)
     </para>
     <para>
      
@@ -550,7 +550,7 @@
     2019-07-03 [5d042e4]
     -->
     <para>
-     Fix sefault when query cache is enabled. (<ulink url="https://www.pgpool.net/mantisbt/view.php?id=525">bug 525</ulink>) (Tatsuo Ishii)
+     Fix segfault when query cache is enabled. (<ulink url="https://www.pgpool.net/mantisbt/view.php?id=525">bug 525</ulink>) (Tatsuo Ishii)
     </para>
    </listitem>
 
@@ -1337,7 +1337,7 @@
  <sect2>
   <title>Overview</title>
   <para>
-   This version addes support for SCRAM and CERT authentication,
+   This version adds support for SCRAM and CERT authentication,
    improves load balancing control and import PostgreSQL 11 
    new SQL parser. 
   </para>
diff --git a/doc/src/sgml/runtime.sgml b/doc/src/sgml/runtime.sgml
index 70f3509..dc2fd39 100644
--- a/doc/src/sgml/runtime.sgml
+++ b/doc/src/sgml/runtime.sgml
@@ -134,7 +134,7 @@
     replication mode and raw mode. In any
     mode, <productname>Pgpool-II</> provides connection pooling,
     automatic fail over and online recovery. The sample
-    configuration files for each mode are provied. They are located
+    configuration files for each mode are provided. They are located
     under <filename>$prefix/etc</filename>. You can copy one of them
     to <filename>$prefix/etc/pgpool.conf</filename>.
    </para>
diff --git a/doc/src/sgml/ssl.sgml b/doc/src/sgml/ssl.sgml
index f106009..5b95140 100644
--- a/doc/src/sgml/ssl.sgml
+++ b/doc/src/sgml/ssl.sgml
@@ -1,7 +1,7 @@
 <!-- doc/src/sgml/config.sgml -->
 
 <sect1 id="runtime-ssl">
- <title>Secure Sockect Layer (SSL)</title>
+ <title>Secure Socket Layer (SSL)</title>
 
  <sect2 id="runtime-config-ssl-settings">
 
diff --git a/doc/src/sgml/start.sgml b/doc/src/sgml/start.sgml
index 8f321ad..ca1415a 100644
--- a/doc/src/sgml/start.sgml
+++ b/doc/src/sgml/start.sgml
@@ -422,7 +422,7 @@
   </para>
   <para>
    <figure>
-    <title>Process architecure of <productname>Pgpool-II</productname></title>
+    <title>Process architecture of <productname>Pgpool-II</productname></title>
     <mediaobject>
      <imageobject>
       <imagedata fileref="process-diagram.gif">
diff --git a/doc/src/sgml/stream-check.sgml b/doc/src/sgml/stream-check.sgml
index 2750a7e..86a98d4 100644
--- a/doc/src/sgml/stream-check.sgml
+++ b/doc/src/sgml/stream-check.sgml
@@ -158,7 +158,7 @@
     </para>
 
     <para>
-     This parameter can be changed by reloading the <productname>Pgpool-II conf</>igurations.
+     This parameter can be changed by reloading the <productname>Pgpool-II</>configurations.
     </para>
 
    </listitem>
diff --git a/doc/src/sgml/watchdog.sgml b/doc/src/sgml/watchdog.sgml
index 61ba814..b037b58 100644
--- a/doc/src/sgml/watchdog.sgml
+++ b/doc/src/sgml/watchdog.sgml
@@ -288,7 +288,7 @@
  </sect2>
 
  <sect2 id="config-watchdog-escalation-de-escalation">
-  <title>Behaivor on escalation and de-escalation</title>
+  <title>Behaviour on escalation and de-escalation</title>
 
   <para>
    Configuration about behavior when <productname>Pgpool-II</productname>
@@ -306,8 +306,8 @@
     <listitem>
      <para>
       When set to on, watchdog clears all the query cache in the shared memory
-      when pgpool-II escaltes to active. This prevents the new active <productname>Pgpool-II</productname>
-      from using old query caches inconsistence to the old active.
+      when pgpool-II escalates to active. This prevents the new active <productname>Pgpool-II</productname>
+      from using old query caches inconsistent to the old active.
      </para>
      <para>
       Default is on.
@@ -410,7 +410,7 @@
        and silently detaches the problematic node, So in the case when the master backend node is quarantined, the
        <productname>Pgpool-II</productname> will not promote the standby to take over the master responsibilities
        and until the master node is quarantined the <productname>Pgpool-II</productname> will not have
-       any useable master backend node.
+       any usable master backend node.
      </para>
      <para>
       Default is on.