Log Message:
-----------

Fix sgml errors

Modified Files:
--------------
    slony1-engine/doc/adminguide:
        bestpractices.sgml (r1.10 -> r1.11)

-------------- next part --------------
Index: bestpractices.sgml
===================================================================
RCS file: /usr/local/cvsroot/slony1/slony1-engine/doc/adminguide/bestpractices.sgml,v
retrieving revision 1.10
retrieving revision 1.11
diff -Ldoc/adminguide/bestpractices.sgml -Ldoc/adminguide/bestpractices.sgml -u -w -r1.10 -r1.11
--- doc/adminguide/bestpractices.sgml
+++ doc/adminguide/bestpractices.sgml
@@ -313,7 +313,9 @@
 <quote>strain</quote> on the system, in particular where it may take
 several days for the <command>COPY_SET</command> event to complete.
 Here are some principles that have been observed for dealing with
-these sorts of situtations.</para>
+these sorts of situtations.</para></listitem>
+
+</itemizedlist>
 
 <itemizedlist>
 
@@ -349,10 +351,12 @@
 number of those 90,000 <command>SYNC</command> events, it still reads
 through the entire table.  In such a case, you may never see
 replication catch up.
-</para> </listitem>
+</para> 
 
-<listitem><para> Several things can be done that will help, involving
+<para> Several things can be done that will help, involving
 careful selection of <xref linkend="slon"> parameters:</para>
+</listitem>
+</itemizedlist>
 
 <itemizedlist>
 
@@ -384,7 +388,6 @@
 the data is copied and the subscriber starts to catch up. </para>
 </listitem>
 </itemizedlist>
-</itemizedlist>
 
 </sect1>
 <!-- Keep this comment at the end of the file