[jboss-svn-commits] JBL Code SVN: r5946 - in labs/jbossrules/trunk/documentation/manual/en: Chapter-Rule_Engine Chapter-Rule_Language

[jboss-svn-commits at lists.jboss.org]

Author: mark.proctor at jboss.com
Date: 2006-08-19 20:06:37 -0400 (Sat, 19 Aug 2006)
New Revision: 5946

Modified:
   labs/jbossrules/trunk/documentation/manual/en/Chapter-Rule_Engine/Section-Rules.xml
   labs/jbossrules/trunk/documentation/manual/en/Chapter-Rule_Engine/Section-The_Drools_Rule_Engine.xml
   labs/jbossrules/trunk/documentation/manual/en/Chapter-Rule_Language/Section-Rule.xml
Log:
-JBRULES-383 Documentation spelling fixes

Modified: labs/jbossrules/trunk/documentation/manual/en/Chapter-Rule_Engine/Section-Rules.xml
===================================================================
--- labs/jbossrules/trunk/documentation/manual/en/Chapter-Rule_Engine/Section-Rules.xml	2006-08-19 05:27:40 UTC (rev 5945)
+++ labs/jbossrules/trunk/documentation/manual/en/Chapter-Rule_Engine/Section-Rules.xml	2006-08-20 00:06:37 UTC (rev 5946)
@@ -266,7 +266,7 @@
     ...
 }</programlisting>
 
-    <programlisting>public Class Module {
+    <programlisting>public class Module {
     private String name;
     private String studentName;
     private int score;</programlisting>
@@ -288,7 +288,7 @@
     }
 }</programlisting>
 
-    <para>Early SQL implementations where not Turing complete as they did not
+    <para>Early SQL implementations were not Turing complete as they did not
     provide quantifiers to asses the structure of data. However modern SQL
     engines allow nesting of SQL which can be combined with keywords like
     'exists' and 'in': The following query would return a set of Students who

Modified: labs/jbossrules/trunk/documentation/manual/en/Chapter-Rule_Engine/Section-The_Drools_Rule_Engine.xml
===================================================================
--- labs/jbossrules/trunk/documentation/manual/en/Chapter-Rule_Engine/Section-The_Drools_Rule_Engine.xml	2006-08-19 05:27:40 UTC (rev 5945)
+++ labs/jbossrules/trunk/documentation/manual/en/Chapter-Rule_Engine/Section-The_Drools_Rule_Engine.xml	2006-08-20 00:06:37 UTC (rev 5946)
@@ -277,7 +277,7 @@
     time (such as a conversation) - and kept updated with new facts. When you
     wish to dispose of WorkingMemory it is best pactice to use the dispose()
     method, so that it removes the reference in the parent Rule Base - however
-    this is a weak reference, so it should eventually me garbage collected
+    this is a weak reference, so it should eventually be garbage collected
     anyway. The term Working Memory Action is used to describe assertions,
     retractions and modifications with the Working Memory.</para>
 
@@ -816,4 +816,4 @@
     graphical viewer, so that the rule engine can log events for later
     viewing, and auditing.</para>
   </section>
-</section>
+</section>
\ No newline at end of file

Modified: labs/jbossrules/trunk/documentation/manual/en/Chapter-Rule_Language/Section-Rule.xml
===================================================================
--- labs/jbossrules/trunk/documentation/manual/en/Chapter-Rule_Language/Section-Rule.xml	2006-08-19 05:27:40 UTC (rev 5945)
+++ labs/jbossrules/trunk/documentation/manual/en/Chapter-Rule_Language/Section-Rule.xml	2006-08-20 00:06:37 UTC (rev 5946)
@@ -364,7 +364,7 @@
         maybe null, using == and != as you would expect, and the literal
         "null" keyword, like: Cheese(type != null). Literal Constraints,
         specifically the '==' operator, provide for very fast execution as we
-        can use hasing to improve performance.</para>
+        can use hashing to improve performance.</para>
 
         <figure>
           <title>Literal Constraints</title>
@@ -539,7 +539,7 @@
             </indexterm>Collection contains an object.</para>
 
           <example>
-            <title>Literal Cosntraints with Collections</title>
+            <title>Literal Constraints with Collections</title>
 
             <programlisting>CheeseCounter( cheeses contains "stilton" )
 CheeseCounter( cheeses excludes "chedder" )</programlisting>
@@ -555,7 +555,7 @@
             </indexterm>Collection does not contains an object.</para>
 
           <example>
-            <title>Literal Cosntraints with Collections</title>
+            <title>Literal Constraints with Collections</title>
 
             <programlisting>CheeseCounter( cheeses excludes "cheddar" )</programlisting>
           </example>
@@ -590,7 +590,7 @@
         <literal>'contains'</literal>. Valid operators are determined by the
         type of the field being constrained. Bound Variables, specifically the
         '==' and '=!' operators, provide for very fast execution as we can use
-        hasing to improve performance.</para>
+        hashing to improve performance.</para>
 
         <example>
           <title>Bound Field using '==' operator</title>