From: Robert Haas <rhaas@postgresql.org>
Date: Tue, 5 Apr 2011 16:40:17 +0000 (-0400)
Subject: Typo fixes.
X-Git-Tag: REL9_1_BETA1~156
X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=ad275473a5ea75f4aa010791884004f75f3c7a65;p=postgresql

Typo fixes.

Erik Rijkers
---

diff --git a/doc/src/sgml/high-availability.sgml b/doc/src/sgml/high-availability.sgml
index 6dbc6bcd72..5972a45555 100644
--- a/doc/src/sgml/high-availability.sgml
+++ b/doc/src/sgml/high-availability.sgml
@@ -486,7 +486,7 @@ protocol to make nodes agree on a serializable transactional order.
   <para>
    Directly moving WAL records from one database server to another
    is typically described as log shipping. <productname>PostgreSQL</>
-   implements file-based log shipping by transfering WAL records
+   implements file-based log shipping by transferring WAL records
    one file (WAL segment) at a time. WAL files (16MB) can be
    shipped easily and cheaply over any distance, whether it be to an
    adjacent system, another system at the same site, or another system on
@@ -944,7 +944,7 @@ primary_conninfo = 'host=192.168.1.50 port=5432 user=foo password=foopass'
    </para>
 
    <para>
-    After a commit record has been written to disk on the primary the
+    After a commit record has been written to disk on the primary, the
     WAL record is then sent to the standby. The standby sends reply
     messages each time a new batch of WAL data is written to disk, unless
     <varname>wal_receiver_status_interval</> is set to zero on the standby.