From 23e9fe039172ea751223c44a2732a75979ed018b Mon Sep 17 00:00:00 2001
From: Heikki Linnakangas <heikki.linnakangas@iki.fi>
Date: Sat, 29 May 2010 09:01:10 +0000
Subject: [PATCH] Fix typos in recent doc patch. Fujii Masao

---
 doc/src/sgml/high-availability.sgml | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/doc/src/sgml/high-availability.sgml b/doc/src/sgml/high-availability.sgml
index e771edf9c4..6f2125f2a5 100644
--- a/doc/src/sgml/high-availability.sgml
+++ b/doc/src/sgml/high-availability.sgml
@@ -1,4 +1,4 @@
-<!-- $PostgreSQL: pgsql/doc/src/sgml/high-availability.sgml,v 1.69 2010/05/28 14:03:31 heikki Exp $ -->
+<!-- $PostgreSQL: pgsql/doc/src/sgml/high-availability.sgml,v 1.70 2010/05/29 09:01:10 heikki Exp $ -->
 
 <chapter id="high-availability">
  <title>High Availability, Load Balancing, and Replication</title>
@@ -714,7 +714,7 @@ trigger_file = '/path/to/trigger_file'
 
    <para>
     If you're using a WAL archive, its size can be minimized using
-    the <varname>restartpoint_command</> option to remove files that are no
+    the <varname>restartpoint_command</> option to remove files that are
     no longer required by the standby server. Note however, that if you're
     using the archive for backup purposes, you need to retain files needed
     to recover from at least the latest base backup, even if they're no
@@ -1089,7 +1089,7 @@ if (!triggered)
    <para>
     It is also possible to implement record-based log shipping using this
     alternative method, though this requires custom development, and changes
-    will still only becomes visible to hot standby queries after a full WAL
+    will still only become visible to hot standby queries after a full WAL
     file has been shipped.
    </para>
 
-- 
2.40.0