Log Message:
-----------
Patch from Ian Burrell to resolve SGML tagging errors found on RHAT...

Modified Files:
--------------
    slony1-engine/doc/adminguide:
        bestpractices.sgml (r1.3 -> r1.4)
        concepts.sgml (r1.13 -> r1.14)
        faq.sgml (r1.33 -> r1.34)
        installation.sgml (r1.11 -> r1.12)
        slonik_ref.sgml (r1.23 -> r1.24)
        usingslonik.sgml (r1.10 -> r1.11)

-------------- next part --------------
Index: concepts.sgml
===================================================================
RCS file: /usr/local/cvsroot/slony1/slony1-engine/doc/adminguide/concepts.sgml,v
retrieving revision 1.13
retrieving revision 1.14
diff -Ldoc/adminguide/concepts.sgml -Ldoc/adminguide/concepts.sgml -u -w -r1.13 -r1.14
--- doc/adminguide/concepts.sgml
+++ doc/adminguide/concepts.sgml
@@ -35,7 +35,6 @@
 namespace/schema <envar>_something.</envar></para>
 </sect2>
 <sect2><title>Node</title>
-
 <indexterm>
  <primary>node</primary>
 </indexterm>
@@ -59,7 +58,6 @@
 </itemizedlist>
 </sect2>
 <sect2><title> Replication Set</title>
-
 <indexterm>
  <primary>replication set</primary>
 </indexterm>
@@ -72,11 +70,9 @@
 </sect2>
 
 <sect2><title> Origin, Providers and Subscribers</title>
-
 <indexterm>
  <primary>origin node</primary>
 </indexterm>
-
 <indexterm>
  <primary>provider node</primary>
 </indexterm>
@@ -117,7 +113,7 @@
 <listitem><para> Configuration events</para>
 
 <para> These normally occur when a <xref linkend="slonik"> script is
-run, and submit updates to the configuration of the cluster. <para>
+run, and submit updates to the configuration of the cluster. </para>
 </listitem>
 
 <listitem><para> <command>SYNC</command> events </para>
Index: installation.sgml
===================================================================
RCS file: /usr/local/cvsroot/slony1/slony1-engine/doc/adminguide/installation.sgml,v
retrieving revision 1.11
retrieving revision 1.12
diff -Ldoc/adminguide/installation.sgml -Ldoc/adminguide/installation.sgml -u -w -r1.11 -r1.12
--- doc/adminguide/installation.sgml
+++ doc/adminguide/installation.sgml
@@ -72,7 +72,7 @@
 <para>The <application>configure</application> script will run a
 number of tests to guess values for various dependent variables and
 try to detect some quirks of your system.  &slony1; is known to need a
-modified version of <application>libpq<application> on specific
+modified version of <application>libpq</application> on specific
 platforms such as Solaris2.X on SPARC.  The patch for libpq version
 7.4.2 can be found at <ulink id="threadpatch" url=
 "http://developer.postgresql.org/~wieck/slony1/download/threadsafe-libpq-742.diff.gz">
Index: slonik_ref.sgml
===================================================================
RCS file: /usr/local/cvsroot/slony1/slony1-engine/doc/adminguide/slonik_ref.sgml,v
retrieving revision 1.23
retrieving revision 1.24
diff -Ldoc/adminguide/slonik_ref.sgml -Ldoc/adminguide/slonik_ref.sgml -u -w -r1.23 -r1.24
--- doc/adminguide/slonik_ref.sgml
+++ doc/adminguide/slonik_ref.sgml
@@ -728,9 +728,7 @@
     <title>Description</title>
     
     <para> 	Remove the connection information between <quote>server</quote> and
-     <quote>client</quote>.
-     
-     
+     <quote>client</quote>.</para>
      
      <variablelist>
       <varlistentry><term><literal> SERVER  = ival </literal></term>
@@ -1986,7 +1984,7 @@
 
     <para> Note that this is a <link linkend="locking"> locking
     operation, </link> which means that it can get stuck behind other
-    database activity.
+    database activity.</para>
      
     <para> At the start of this event, all tables in the specified set
     are unlocked via the function
Index: bestpractices.sgml
===================================================================
RCS file: /usr/local/cvsroot/slony1/slony1-engine/doc/adminguide/bestpractices.sgml,v
retrieving revision 1.3
retrieving revision 1.4
diff -Ldoc/adminguide/bestpractices.sgml -Ldoc/adminguide/bestpractices.sgml -u -w -r1.3 -r1.4
--- doc/adminguide/bestpractices.sgml
+++ doc/adminguide/bestpractices.sgml
@@ -55,7 +55,7 @@
 <para> This may simply involve thinking about what the priority lists
 should be of what should fail to what, as opposed to trying to
 automate it.  But knowing what to do ahead of time cuts down on the
-number of mistakes made.
+number of mistakes made.</para>
 
 <para> At Afilias, some internal <citation>The 3AM Unhappy DBA's Guide
 to...</citation> guides have been created to provide checklists of
Index: faq.sgml
===================================================================
RCS file: /usr/local/cvsroot/slony1/slony1-engine/doc/adminguide/faq.sgml,v
retrieving revision 1.33
retrieving revision 1.34
diff -Ldoc/adminguide/faq.sgml -Ldoc/adminguide/faq.sgml -u -w -r1.33 -r1.34
--- doc/adminguide/faq.sgml
+++ doc/adminguide/faq.sgml
@@ -78,7 +78,9 @@
 against <application>slon</application>.</para> </answer>
 
 <answer><para> Note that with libpq version 7.4.2, on Solaris, a
-further patch <xref linkend="threadpatch"> was required.  </para>
+further <link linkend="threadpatch"> thread patch </link> was
+required; similar is also required for &postgres; version 8.0.
+</para>
 </answer>
 </qandaentry>
 
@@ -1078,6 +1080,7 @@
 update _app1.sl_log_1 SET log_cmddata = 'balance=''125192.00'' where pkey=''60''' where log_actionseq = '68387029';
 
 </screen>
+</listitem>
 
 </itemizedlist>
 </answer>
Index: usingslonik.sgml
===================================================================
RCS file: /usr/local/cvsroot/slony1/slony1-engine/doc/adminguide/usingslonik.sgml,v
retrieving revision 1.10
retrieving revision 1.11
diff -Ldoc/adminguide/usingslonik.sgml -Ldoc/adminguide/usingslonik.sgml -u -w -r1.10 -r1.11
--- doc/adminguide/usingslonik.sgml
+++ doc/adminguide/usingslonik.sgml
@@ -59,7 +59,7 @@
 </itemizedlist></para>
 
 <para> There are several ways to work around these issues that have
-been seen <quote>in the wild</quote>:
+been seen <quote>in the wild</quote>:</para>
 
 <itemizedlist>