Log Message:
-----------
More comments...

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

-------------- next part --------------
Index: ddlchanges.sgml
===================================================================
RCS file: /usr/local/cvsroot/slony1/slony1-engine/doc/adminguide/ddlchanges.sgml,v
retrieving revision 1.11
retrieving revision 1.12
diff -Ldoc/adminguide/ddlchanges.sgml -Ldoc/adminguide/ddlchanges.sgml -u -w -r1.11 -r1.12
--- doc/adminguide/ddlchanges.sgml
+++ doc/adminguide/ddlchanges.sgml
@@ -18,12 +18,12 @@
 transactions are still winding their way through your systems, this is
 necessary.  </para>
 
-<para>It is also necessary to use <command> EXECUTE SCRIPT</command>
-if you alter tables so as to change their schemas.  If you do not,
-then you may run into the problems <link linkend="neededexecddl">
-described here </link> where triggers on modified tables do not take
-account of the schema change.  This has the potential to corrupt data
-on subscriber nodes.  </para>
+<para>It is also necessary to use <command>EXECUTE SCRIPT</command> if
+you alter tables so as to change their schemas.  If you do not, then
+you may run into the problems <link linkend="neededexecddl"> described
+here </link> where triggers on modified tables do not take account of
+the schema change.  This has the potential to corrupt data on
+subscriber nodes.  </para>
 
 <para>It's worth making a couple of comments on <quote>special
 things</quote> about <command><link linkend="stmtddlscript">EXECUTE
@@ -176,7 +176,8 @@
 implicitly stop replication, while the index builds, but shouldn't
 cause any particular problems.  If you add an index on a table that
 takes 20 minutes to build, replication will block for 20 minutes, but
-should catch up quickly once the index is created.</para></listitem>
+should catch up quickly enough once the index is
+created.</para></listitem>
 
 </itemizedlist></para></sect2>