Log Message:
-----------
Typo per Dan Langille

Modified Files:
--------------
    slony1-engine/doc/adminguide:
        intro.sgml (r1.25 -> r1.26)

-------------- next part --------------
Index: intro.sgml
===================================================================
RCS file: /usr/local/cvsroot/slony1/slony1-engine/doc/adminguide/intro.sgml,v
retrieving revision 1.25
retrieving revision 1.26
diff -Ldoc/adminguide/intro.sgml -Ldoc/adminguide/intro.sgml -u -w -r1.25 -r1.26
--- doc/adminguide/intro.sgml
+++ doc/adminguide/intro.sgml
@@ -141,9 +141,9 @@
 single common reason for these limitations, namely that &slony1;
 collects updates using triggers, and neither schema changes, large
 object operations, nor <command>TRUNCATE</command> requests are able
-to triggers suitable to inform &slony1; when those sorts of changes
-take place.  As a result, the only database objects where &slony1; can
-replicate updates are tables and sequences.  </para>
+to have triggers suitable to inform &slony1; when those sorts of
+changes take place.  As a result, the only database objects where
+&slony1; can replicate updates are tables and sequences.  </para>
 
 <para> Note that with the <emphasis>use</emphasis> of triggers comes
 some additional <emphasis>fiddling around with triggers</emphasis>.