[jboss-svn-commits] JBL Code SVN: r26290 - labs/jbossrules/trunk/drools-docs/drools-docs-flow/src/main/docbook/en-US/Chapter-Introduction.

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

Author: laune
Date: 2009-04-28 07:40:05 -0400 (Tue, 28 Apr 2009)
New Revision: 26290

Modified:
   labs/jbossrules/trunk/drools-docs/drools-docs-flow/src/main/docbook/en-US/Chapter-Introduction/Chapter-Introduction.xml
Log:
improvements

Modified: labs/jbossrules/trunk/drools-docs/drools-docs-flow/src/main/docbook/en-US/Chapter-Introduction/Chapter-Introduction.xml
===================================================================
--- labs/jbossrules/trunk/drools-docs/drools-docs-flow/src/main/docbook/en-US/Chapter-Introduction/Chapter-Introduction.xml	2009-04-28 11:03:48 UTC (rev 26289)
+++ labs/jbossrules/trunk/drools-docs/drools-docs-flow/src/main/docbook/en-US/Chapter-Introduction/Chapter-Introduction.xml	2009-04-28 11:40:05 UTC (rev 26290)
@@ -1,13 +1,13 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<chapter version="5.0" xmlns="http://docbook.org/ns/docbook"
-                    xmlns:xlink="http://www.w3.org/1999/xlink"
-                    xmlns:xi="http://www.w3.org/2001/XInclude"
-                    xmlns:svg="http://www.w3.org/2000/svg"
-                    xmlns:m="http://www.w3.org/1998/Math/MathML"
-                    xmlns:html="http://www.w3.org/1999/xhtml"
-                    xmlns:db="http://docbook.org/ns/docbook" xml:base="./">
-  <title>Introduction</title>
-  <para>Drools Flow is a workflow or process engine that allows
+<?xml version="1.0" encoding="UTF-8"?>
+<chapter version="5.0" xmlns="http://docbook.org/ns/docbook"
+                    xmlns:xlink="http://www.w3.org/1999/xlink"
+                    xmlns:xi="http://www.w3.org/2001/XInclude"
+                    xmlns:svg="http://www.w3.org/2000/svg"
+                    xmlns:m="http://www.w3.org/1998/Math/MathML"
+                    xmlns:html="http://www.w3.org/1999/xhtml"
+                    xmlns:db="http://docbook.org/ns/docbook" xml:base="./">
+  <title>Introduction</title>
+  <para>Drools Flow is a workflow or process engine that allows
   advanced integration of processes and rules.  A process or a
   workflow describes the order in which a series of steps need
   to be executed, using a flow chart.  For example, the following
@@ -15,17 +15,17 @@
   executed in parallel.  After completion of both, Task3 needs to
   be executed.</para>
 
-    <mediaobject>
-      <imageobject>
-        <imagedata align="center" format="BMP" role="" 
-                   fileref="images/Chapter-Introduction/process.bmp"/>
-      </imageobject>
+    <mediaobject>
+      <imageobject>
+        <imagedata align="center" format="BMP" role="" 
+                   fileref="images/Chapter-Introduction/process.bmp"/>
+      </imageobject>
     </mediaobject>
 
-  <para>The following chapters will learn you everything you need
-  to know about Drools Flow.  It's distinguishing characteristics
+  <para>The following chapters will teach you everything you need
+  to know about Drools Flow.  Its distinguishing characteristics
   are:
-    <orderedlist>
+    <orderedlist>
       <listitem><emphasis role="strong">Advanced integration of processes
       and rules:</emphasis> Processes and rules are usually considered as
       two different paradigms when it comes to defining business logic.
@@ -38,21 +38,21 @@
       rules:</emphasis> We consider rules, processes and event processing
       all as different types of knowledge.  Not only do we allow the advanced
       integration of these three types, we also offer a unified API and
-      unified tooling so that users should not learn three different products
+      unified tooling so that users should not have to learn three different products
       but can easily combine these three types using our knowledge-based API.
       The tooling also allows seamless integration of these different kinds of
       knowledge, including things like a unified knowledge repository, audit
       logs, debugging, etc.</listitem>
       <listitem><emphasis role="strong">Declarative modelling:</emphasis>
-      Drools Flow tries to keep processes as declarative as possible, i.e.
+      Drools Flow tries to keep processes as declarative as possible, i.e.,
       focussing on what should happen instead of how.  As a result, we try
       to avoid having to hardcode details into your process but offer ways
-      to describe your work in an abstract way (e.g. using pluggable work
-      items, a business scripting language, etc.). We also allows users
-      to easily create domain-specific extension, making it much easier to
+      to describe your work in an abstract way (e.g., by using pluggable work
+      items, a business scripting language, etc.). We also allow users
+      to easily create domain-specific extensions, making it much simpler to
       read, update or create these processes as they are using
-      domain-specific concepts that are closely related to the problem you
-      are trying to solve and can be understood by domain experts.</listitem>
+      domain-specific concepts that are closely related to the problem at
+      hand and can be understood by domain experts.</listitem>
       <listitem><emphasis role="strong">Generic process engine supporting
       multiple process languages:</emphasis> We do not believe that there
       is one process language that fits all purposes.  Therefore, the Drools
@@ -67,5 +67,5 @@
     </orderedlist>
   All these features (and many more) will be explained in the following
   chapters.
-  </para>
-</chapter>
+  </para>
+</chapter>