[Doc]: fix typos patch

dmpgpro · dmpgpro · commit 9e3ae05c510f · 2017-02-02T17:30:11.000+03:00
diff --git a/doc/src/sgml/intro.sgml b/doc/src/sgml/intro.sgml
@@ -214,7 +214,7 @@
      <simpara><application>fulleq</application> module provides additional equivalence operator to compatibility with Microsoft SQL Server.</simpara>
     </listitem>
     <listitem>
-     <simpara><application>fasttrun</application> module provides transaction unsafe function to truncate tempory tables without growing pg_class size.</simpara>
+     <simpara><application>fasttrun</application> module provides transaction unsafe function to truncate temporary tables without growing pg_class size.</simpara>
     </listitem>
     <listitem>
      <simpara><application>online_analyze</application> module provides set of
diff --git a/doc/src/sgml/mchar.sgml b/doc/src/sgml/mchar.sgml
@@ -38,7 +38,7 @@
     </listitem>
     <listitem>
     <para>
-    These types are always stored as two-byte unicode value regradless
+    These types are always stored as two-byte unicode value regardless
     of database encoding.
     </para>
     </listitem>
diff --git a/doc/src/sgml/pgquerystate.sgml b/doc/src/sgml/pgquerystate.sgml
@@ -11,7 +11,7 @@
       optimization/planning stage is translated into plan tree wich is kind of
       imperative representation of declarative SQL query. EXPLAIN ANALYZE
       request allows to demonstrate execution statistics gathered from each
-      node of plan tree (full time of execution, number rows emitted to upper
+      node of plan tree (full time of execution, number of rows emitted to upper
       nodes, etc). But this statistics is collected after execution of query.
       This module allows to show actual statistics of query running on external
       backend. At that, format of resulting output is almost identical to
@@ -182,7 +182,7 @@
       </listitem>
     </itemizedlist>
     <para>
-      This parameters is set on called side before running any queries whose
+      These parameters are set on called side before running any queries whose
       states are attempted to extract. <literal>WARNING</literal>: if
       pg_query_state.enable_timing is turned off the calling side cannot get
       time statistics, similarly for pg_query_state.enable_buffers parameter.
