[Jboss-svn-commits] JBL Code SVN: r4601 - labs/jbossrules/trunk/documentation/manual/en/Chapter-Rule_Engine

[<jbo...@li...>]

Author: mic...@jb...
Date: 2006-06-04 20:57:35 -0400 (Sun, 04 Jun 2006)
New Revision: 4601

Modified:
   labs/jbossrules/trunk/documentation/manual/en/Chapter-Rule_Engine/Section-Why_use_a_Rule_Engine.xml
Log:
removed bad para tag

Modified: labs/jbossrules/trunk/documentation/manual/en/Chapter-Rule_Engine/Section-Why_use_a_Rule_Engine.xml
===================================================================
--- labs/jbossrules/trunk/documentation/manual/en/Chapter-Rule_Engine/Section-Why_use_a_Rule_Engine.xml	2006-06-04 19:00:33 UTC (rev 4600)
+++ labs/jbossrules/trunk/documentation/manual/en/Chapter-Rule_Engine/Section-Why_use_a_Rule_Engine.xml	2006-06-05 00:57:35 UTC (rev 4601)
@@ -213,9 +213,9 @@
     to use a rule engine.</para>
 
     <para>Alternatives are script-based engines that provide the dynamicness
-    for "changes on the fly" (there are many solutions here) or</para>
+    for "changes on the fly" (there are many solutions here). </para>
 
-    <para>Process engines (also capable of workflow) such as jBPM allow you to
+	<para>Alternatively Process engines (also capable of workflow) such as jBPM allow you to
     graphically (or programmatically) describe steps in a process - those
     steps can also involve decision point which are in themselves a simple
     rule. Process engines and rules often can work nicely together, so its not