Log Message:
-----------
Reshaped sections a bit to improve flow of web pages

Modified Files:
--------------
    slony1-engine/doc/adminguide:
        usingslonik.sgml (r1.1 -> r1.2)

-------------- next part --------------
Index: usingslonik.sgml
===================================================================
RCS file: /usr/local/cvsroot/slony1/slony1-engine/doc/adminguide/usingslonik.sgml,v
retrieving revision 1.1
retrieving revision 1.2
diff -Ldoc/adminguide/usingslonik.sgml -Ldoc/adminguide/usingslonik.sgml -u -w -r1.1 -r1.2
--- doc/adminguide/usingslonik.sgml
+++ doc/adminguide/usingslonik.sgml
@@ -84,7 +84,7 @@
 
 </itemizedlist>
 
-<sect2><title> Using m4 to rewrite slonik scripts </title>
+<sect1 id="slonikm4"><title> Using m4 to rewrite slonik scripts </title>
 
 <para> This needs to be prefaced with something of a warning, from the
 GNU M4 documentation:
@@ -135,7 +135,7 @@
 practices.</quote>
 </itemizedlist>
 
-<sect3><title> An m4 example </title>
+<sect2><title> An m4 example </title>
 
 <para> Without further ado, here is an example where you set up a
 central file, <filename> cluster.m4 </filename> containing some M4
@@ -189,7 +189,7 @@
 highly preferable to do this by using a scripting language like the
 Bourne Shell or Perl.
 
-<sect2><title> Embedding Slonik in Shell Scripts </title>
+<sect1 id="slonikshell"><title> Embedding Slonik in Shell Scripts </title>
 
 <para> As mentioned earlier, there are numerous
 <productname>Slony-I</productname> test scripts in
@@ -355,7 +355,6 @@
 scripting languages, of which Perl is the most ubiquitous, being
 widely available on Linux, <trademark/UNIX/, and BSD.
 
-</sect1>
 <!-- Keep this comment at the end of the file
 Local variables:
 mode:sgml