From: <jbo...@li...> - 2006-05-18 00:53:45
|
Author: mic...@jb... Date: 2006-05-17 20:53:39 -0400 (Wed, 17 May 2006) New Revision: 4307 Modified: labs/jbossrules/trunk/documentation/manual/en/Chapter-Rule_Engine/Section-Why_use_a_Rule_Engine.xml Log: typo fix 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-05-18 00:34:24 UTC (rev 4306) +++ labs/jbossrules/trunk/documentation/manual/en/Chapter-Rule_Engine/Section-Why_use_a_Rule_Engine.xml 2006-05-18 00:53:39 UTC (rev 4307) @@ -227,7 +227,7 @@ rules, you are effectively calling rules directly) and this may cause more difficulty in future maintenance, as they tend to grow in complexity over time. The upside of scripting engines is they can be easier to implement - at first, and you can get quite results (and conceptually simpler for + at first, and you can get quick results (and conceptually simpler for imperative programmers !).</para> <para>Many people have also implemented data-driven systems successfully |