From 42cfdfb453c30f9500f058994a249647713d6006 Mon Sep 17 00:00:00 2001
From: Neil Conway <neilc@samurai.com>
Date: Fri, 17 Nov 2006 09:00:03 +0000
Subject: [PATCH] Fix a typo.
---
doc/src/sgml/failover.sgml | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/doc/src/sgml/failover.sgml b/doc/src/sgml/failover.sgml
index 19b9740be0..3957d3ef45 100644
--- a/doc/src/sgml/failover.sgml
+++ b/doc/src/sgml/failover.sgml
@@ -1,4 +1,4 @@
-<!-- $PostgreSQL: pgsql/doc/src/sgml/failover.sgml,v 1.11 2006/11/17 08:46:53 meskes Exp $ -->
+<!-- $PostgreSQL: pgsql/doc/src/sgml/failover.sgml,v 1.12 2006/11/17 09:00:03 neilc Exp $ -->
<chapter id="failover">
<title>Failover, Replication, Load Balancing, and Clustering Options</title>
@@ -121,7 +121,7 @@
<para>
A master/slave replication setup sends all data modification
- queries to the master server. The master server asynchonously
+ queries to the master server. The master server asynchronously
sends data changes to the slave server. The slave can answer
read-only queries while the master server is running. The
slave server is ideal for data warehouse queries.