Log Message:
-----------
Fixing tagging of documentation

Modified Files:
--------------
    slony1-engine/doc/adminguide:
        faq.sgml (r1.29 -> r1.30)
        slonik_ref.sgml (r1.21 -> r1.22)
        slony.sgml (r1.16 -> r1.17)
        usingslonik.sgml (r1.9 -> r1.10)

-------------- next part --------------
Index: slonik_ref.sgml
===================================================================
RCS file: /usr/local/cvsroot/slony1/slony1-engine/doc/adminguide/slonik_ref.sgml,v
retrieving revision 1.21
retrieving revision 1.22
diff -Ldoc/adminguide/slonik_ref.sgml -Ldoc/adminguide/slonik_ref.sgml -u -w -r1.21 -r1.22
--- doc/adminguide/slonik_ref.sgml
+++ doc/adminguide/slonik_ref.sgml
@@ -747,7 +747,6 @@
 	</para></listitem>
       </varlistentry>
      </variablelist>
-    <para> This uses <xref linkend= "function.droppath-integer-integer">. </para>
    </refsect1>
    <refsect1><title>Example</title>
     <programlisting>
Index: faq.sgml
===================================================================
RCS file: /usr/local/cvsroot/slony1/slony1-engine/doc/adminguide/faq.sgml,v
retrieving revision 1.29
retrieving revision 1.30
diff -Ldoc/adminguide/faq.sgml -Ldoc/adminguide/faq.sgml -u -w -r1.29 -r1.30
--- doc/adminguide/faq.sgml
+++ doc/adminguide/faq.sgml
@@ -823,7 +823,7 @@
 key</quote> index on the table rather than to the table
 itself.</para></listitem>
 
-</itemizedlist></para>
+</itemizedlist>
 
 <para> A somewhat unfortunate side-effect is that this handling of the
 rules and triggers somewhat <quote>tramples</quote> on them.  The
@@ -1103,7 +1103,7 @@
 DEBUG2 remoteListenThread_1: queue event 1,4897523 SYNC
 </screen>
 
-</para></question>
+</question>
 
 <answer><para> If you see a <xref linkend="slon"> shutting down with
 <emphasis>ignore new events due to shutdown</emphasis> log entries,
@@ -1246,8 +1246,8 @@
 <answer><para> There are two notable areas of
 <productname>PostgreSQL</productname> that cache query plans and OIDs:</para>
 <itemizedlist>
-<listitem><para> Prepared statements
-<listitem><para> pl/pgSQL functions
+<listitem><para> Prepared statements</para></listitem>
+<listitem><para> pl/pgSQL functions</para></listitem>
 </itemizedlist>
 
 <para> The problem isn't particularly a &slony1; one; it would occur
Index: usingslonik.sgml
===================================================================
RCS file: /usr/local/cvsroot/slony1/slony1-engine/doc/adminguide/usingslonik.sgml,v
retrieving revision 1.9
retrieving revision 1.10
diff -Ldoc/adminguide/usingslonik.sgml -Ldoc/adminguide/usingslonik.sgml -u -w -r1.9 -r1.10
--- doc/adminguide/usingslonik.sgml
+++ doc/adminguide/usingslonik.sgml
@@ -77,6 +77,7 @@
 supposed to do.  </para></listitem>
 
 </itemizedlist>
+</sect1>
 
 <sect1 id="slonikshell"><title> Embedding Slonik in Shell Scripts </title>
 
@@ -252,6 +253,8 @@
 <para> At that point, it makes sense to start looking at other
 scripting languages, of which Perl is the most ubiquitous, being
 widely available on Linux, <trademark>UNIX</trademark>, and BSD.
+</para>
+</sect1>
 
 <sect1 id="noslonik"><title> Not Using Slonik - Bare Metal &slony1;
 Functions </title>
@@ -320,8 +323,8 @@
 In other cases, the function needs to be called on some particular
 node because that is the only place where data may be reasonably
 validated.  For instance, <xref
-	  linkend="function.subscribeset-integer-integer-integer-boolean"> must be
-called on the receivernode.</para></listitem>
+linkend="function.subscribeset-integer-integer-integer-boolean"> must
+be called on the receivernode.</para></listitem>
 
 <listitem><para> If that <quote>main</quote> function succeeds, then
 the configuration change is performed on the local node, and an event
Index: slony.sgml
===================================================================
RCS file: /usr/local/cvsroot/slony1/slony1-engine/doc/adminguide/slony.sgml,v
retrieving revision 1.16
retrieving revision 1.17
diff -Ldoc/adminguide/slony.sgml -Ldoc/adminguide/slony.sgml -u -w -r1.16 -r1.17
--- doc/adminguide/slony.sgml
+++ doc/adminguide/slony.sgml
@@ -75,7 +75,7 @@
 worth documenting</emphasis>.</para>
 
  &faq;
-
+</article>
 <part id="commandreference">
     <title>Core &slony1; Programs</title>
 	&slon;