Log Message:
-----------
Added link to slonconf.sgml, and make sure that new documentation
is included

Modified Files:
--------------
    slony1-engine/doc/adminguide:
        slon.sgml (r1.12 -> r1.13)
        slonik.sgml (r1.12 -> r1.13)
        slonik_ref.sgml (r1.18 -> r1.19)
        slony.sgml (r1.15 -> r1.16)

-------------- next part --------------
Index: slon.sgml
===================================================================
RCS file: /usr/local/cvsroot/slony1/slony1-engine/doc/adminguide/slon.sgml,v
retrieving revision 1.12
retrieving revision 1.13
diff -Ldoc/adminguide/slon.sgml -Ldoc/adminguide/slon.sgml -u -w -r1.12 -r1.13
--- doc/adminguide/slon.sgml
+++ doc/adminguide/slon.sgml
@@ -224,6 +224,10 @@
      <para>
       File from which to read <application>slon</application> configuration.
      </para>
+
+     <para> This configuration is discussed further in <xref
+     linkend="runtime-config">.</para>
+
     </listitem>
    </varlistentry>
    <varlistentry>
Index: slonik_ref.sgml
===================================================================
RCS file: /usr/local/cvsroot/slony1/slony1-engine/doc/adminguide/slonik_ref.sgml,v
retrieving revision 1.18
retrieving revision 1.19
diff -Ldoc/adminguide/slonik_ref.sgml -Ldoc/adminguide/slonik_ref.sgml -u -w -r1.18 -r1.19
--- doc/adminguide/slonik_ref.sgml
+++ doc/adminguide/slonik_ref.sgml
@@ -2033,7 +2033,7 @@
        <listitem><para> The node to refresh.</para></listitem>
        
       </varlistentry>
-     </variablelist></para>
+     </variablelist>
 
    </refsect1>
    <refsect1><title>Example</title>
Index: slonik.sgml
===================================================================
RCS file: /usr/local/cvsroot/slony1/slony1-engine/doc/adminguide/slonik.sgml,v
retrieving revision 1.12
retrieving revision 1.13
diff -Ldoc/adminguide/slonik.sgml -Ldoc/adminguide/slonik.sgml -u -w -r1.12 -r1.13
--- doc/adminguide/slonik.sgml
+++ doc/adminguide/slonik.sgml
@@ -46,20 +46,21 @@
   script.</para>
 
   <para>Nearly all of the real configuration work is actually done by
-  calling stored procedures after loading the <productname>Slony-I</productname>
-  support base into a database.  <application>Slonik</application> was created
-  because these stored procedures have special requirements as to on
-  which particular node in the replication system they are called.
-  The absence of named parameters for stored procedures makes it
-  rather hard to do this from the <application>psql</application> prompt, and
-  <application>psql</application> lacks the ability to maintain multiple
-  connections with open transactions to multiple databases.</para>
-
-  <para>The format of the Slonik <quote>language</quote> is very similar to
-  that of SQL, and the parser is based on a similar set of formatting
-  rules for such things as numbers and strings.  Note that slonik is
-  declarative, using literal values throughout, and does
-  <emphasis>not</emphasis> have the notion of variables.  It is
+  calling stored procedures after loading the
+  <productname>Slony-I</productname> support base into a database.
+  <application>Slonik</application> was created because these stored
+  procedures have special requirements as to on which particular node
+  in the replication system they are called.  The absence of named
+  parameters for stored procedures makes it rather hard to do this
+  from the <application>psql</application> prompt, and
+  <application>psql</application> lacks the ability to maintain
+  multiple connections with open transactions to multiple
+  databases.</para>
+
+  <para>The format of the Slonik <quote>language</quote> is very
+  similar to that of SQL, and the parser is based on a similar set of
+  formatting rules for such things as numbers and strings.  Note that
+  slonik is declarative, using literal values throughout.  It is
   anticipated that Slonik scripts will typically be
   <emphasis>generated</emphasis> by scripts, such as Bash or Perl, and
   these sorts of scripting languages already have perfectly good ways
Index: slony.sgml
===================================================================
RCS file: /usr/local/cvsroot/slony1/slony1-engine/doc/adminguide/slony.sgml,v
retrieving revision 1.15
retrieving revision 1.16
diff -Ldoc/adminguide/slony.sgml -Ldoc/adminguide/slony.sgml -u -w -r1.15 -r1.16
--- doc/adminguide/slony.sgml
+++ doc/adminguide/slony.sgml
@@ -75,15 +75,16 @@
 worth documenting</emphasis>.</para>
 
  &faq;
- &schemadoc;
 
 <part id="commandreference">
     <title>Core &slony1; Programs</title>
 	&slon;
+        &slonconf;
 	&slonik;
         &slonikref;
 </part>
 
+&schemadoc;
 &bookindex;
 
 </book>