Log Message:
-----------
Cleaned up SGML tagging a bit

Modified Files:
--------------
    slony1-engine/doc/adminguide:
        reshape.sgml (r1.7 -> r1.8)

-------------- next part --------------
Index: reshape.sgml
===================================================================
RCS file: /usr/local/cvsroot/slony1/slony1-engine/doc/adminguide/reshape.sgml,v
retrieving revision 1.7
retrieving revision 1.8
diff -Ldoc/adminguide/reshape.sgml -Ldoc/adminguide/reshape.sgml -u -w -r1.7 -r1.8
--- doc/adminguide/reshape.sgml
+++ doc/adminguide/reshape.sgml
@@ -33,19 +33,20 @@
 SUBSCRIBE SET</link> </command> might change the paths as a
 side-effect.  See <link linkend="listenpaths"> Slony Listen Paths
 </link> for more information about this.  In version 1.1 and later, it
-is likely that the generation of sl_listen entries will be entirely
-automated, where they will be regenerated when changes are made to
-sl_path or sl_subscribe, thereby making it unnecessary to even think
-about <command> <link linkend="stmtstorelisten"> STORE LISTEN
+is likely that the generation of <envar>sl_listen</envar> entries will
+be entirely automated, where they will be regenerated when changes are
+made to sl_path or sl_subscribe, thereby making it unnecessary to even
+think about <command> <link linkend="stmtstorelisten"> STORE LISTEN
 </link></command>.</para></listitem>
 
 </itemizedlist>
 </para>
 <para> The <filename>altperl</filename> toolset includes a
-<application>init_cluster.pl</application> script that is quite up to the task of
+<application>regenerate-listens.pl</application> script that is up to the task of
 creating the new <command>STORE LISTEN</command> commands; it isn't,
 however, smart enough to know what listener paths should be dropped.
 </para>
+
 </sect1>
 </article>
 <!-- Keep this comment at the end of the file