Log Message:
-----------
Added crossreference to schemadoc.html

Modified Files:
--------------
    slony1-engine/doc/howto:
        slonik_commands.html (r1.1 -> r1.2)

-------------- next part --------------
Index: slonik_commands.html
===================================================================
RCS file: /usr/local/cvsroot/slony1/slony1-engine/doc/howto/slonik_commands.html,v
retrieving revision 1.1
retrieving revision 1.2
diff -Ldoc/howto/slonik_commands.html -Ldoc/howto/slonik_commands.html -u -w -r1.1 -r1.2
--- doc/howto/slonik_commands.html
+++ doc/howto/slonik_commands.html
@@ -1436,10 +1436,14 @@
 </p>
 <p>
 	Slonik remembers the last event generated on every node during
-	script execution (events generated by earlier calls are currently
-	non checked). In certain situations it is necessary that events
-	generated on one node (like CREATE SET) are processed on another
-	node before issuing more commands (like SUBSCRIBE SET).
+	script execution (events generated by earlier calls are
+	currently not checked). In certain situations it is necessary
+	that events generated on one node (such as <tt>CREATE
+	SET</tt>) are processed on another node before issuing more
+	commands (for instance, <a
+	href="#stmt_subscribe_set">SUBSCRIBE SET</a>).  <tt>WAIT FOR
+	EVENT</tt> may be used to cause the slonik script to wait
+	until the subscriber node is ready for the next action.
 </p>
 <p>
 	WAIT FOR EVENT must be called outside of any try block to
@@ -1502,5 +1506,15 @@
 
 -->
 
+<h1> Stored Procedures </h1>
+
+<P> The commands used in Slonik invoke stored procedures in the
+namespace created for the replication instance.  Slonik provides one
+convenient way to invoke these procedures; it is just as possible to
+invoke them directly to manage the Slony-I instances. </p>
+
+<P> See the <a href= "schemadoc.html"> Schema Documentation </a> for
+more details. </p>
+
 </body>
 </html>