Log Message:
-----------
Add closing tags and remove some warnings.

Modified Files:
--------------
    slony1-engine/doc/adminguide:
        ddlchanges.sgml (r1.23 -> r1.24)

-------------- next part --------------
Index: ddlchanges.sgml
===================================================================
RCS file: /usr/local/cvsroot/slony1/slony1-engine/doc/adminguide/ddlchanges.sgml,v
retrieving revision 1.23
retrieving revision 1.24
diff -Ldoc/adminguide/ddlchanges.sgml -Ldoc/adminguide/ddlchanges.sgml -u -w -r1.23 -r1.24
--- doc/adminguide/ddlchanges.sgml
+++ doc/adminguide/ddlchanges.sgml
@@ -99,15 +99,14 @@
 that <command>SYNC</command>, &slony1; has been replicating tuples
 based on the <emphasis>old</emphasis>
 schema; <emphasis>after</emphasis> the <command>DDL_SCRIPT</command>,
-tuples are being replicated based on the <emphasis>new<emphasis>
-schema. </para></listitem>
+tuples are being replicated based on the <emphasis>new</emphasis>
+schema. </para>
 
 <para> On a system which is busily taking updates, it may be
 troublesome to <quote>get in edgewise</quote> to actually successfully
 engage all the required locks.  The locks may run into deadlocks.
 This points to two ways to address this:
-
-<itemizedlist>
+</para></listitem>
 
 <listitem><para> You may be able to <link linkend="definesets"> define
 replication sets </link> that consist of smaller sets of tables so
@@ -123,8 +122,6 @@
 will conflict with the ones you need to take in order to update the
 database schema.</para></listitem>
 
-</itemizedlist></para></listitem>
-
 <listitem><para> In &slony1; versions 1.0 thru 1.1.5, the script is
 processed as a single query request, which can cause problems if you
 are making complex changes.  In version 1.2, the script is parsed into