Log Message:
-----------
More discussion in docs of merits of mkslonconf.sh

Modified Files:
--------------
    slony1-engine/doc/adminguide:
        adminscripts.sgml (r1.31 -> r1.32)

-------------- next part --------------
Index: adminscripts.sgml
===================================================================
RCS file: /usr/local/cvsroot/slony1/slony1-engine/doc/adminguide/adminscripts.sgml,v
retrieving revision 1.31
retrieving revision 1.32
diff -Ldoc/adminguide/adminscripts.sgml -Ldoc/adminguide/adminscripts.sgml -u -w -r1.31 -r1.32
--- doc/adminguide/adminscripts.sgml
+++ doc/adminguide/adminscripts.sgml
@@ -236,7 +236,7 @@
 from one version of &slony1; to another.</para>
 </sect2>
 
-<sect2><title>mkslonconf.sh</title>
+<sect2 id="mkslonconf"><title>mkslonconf.sh</title>
 
 <para> This is a shell script designed to rummage through a &slony1;
 cluster and generate a set of <filename>slon.conf</filename> files
@@ -309,7 +309,7 @@
 &lslon;s.  </para>
 
 <para> This would usually only cause some minor inconvenience due to,
-for instance, a &slon; running at a non-preferred site, and either
+for instance, a &lslon; running at a non-preferred site, and either
 failing due to lack of network connectivity (in which no damage is
 done!) or running a bit less efficiently than it might have due to
 living at the wrong end of the network <quote>pipe.</quote> </para>
@@ -330,7 +330,7 @@
 
 </sect2>
 
-<sect2><title> launch_clusters.sh </title>
+<sect2 id="launchclusters"><title> launch_clusters.sh </title>
 
 <para> This is another shell script which uses the configuration as
 set up by <filename>mkslonconf.sh</filename> and is intended to be run