From 50f479a11262572e305ac74e25ccd41ed093f47d Mon Sep 17 00:00:00 2001
From: Bruce Momjian <bruce@momjian.us>
Date: Thu, 26 Oct 2006 17:07:03 +0000
Subject: [PATCH] Fix spelling mistake in docs.

---
 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 3a5b0dd4d6..f0a1b257a3 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.1 2006/10/26 15:32:45 momjian Exp $ -->
+<!-- $PostgreSQL: pgsql/doc/src/sgml/failover.sgml,v 1.2 2006/10/26 17:07:03 momjian Exp $ -->
 
 <chapter id="failover">
  <title>Failover, Replication, Load Balancing, and Clustering Options</title>
@@ -109,7 +109,7 @@
 
   <para>
    Slony is an example of this type of replication, with per-table
-   granularity.  It updates the backup server in batches, so the repliation
+   granularity.  It updates the backup server in batches, so the replication
    is asynchronous and might lose data during a fail over.
   </para>
  </sect1>