Author: smukhina Date: 2007-12-03 11:58:10 -0500 (Mon, 03 Dec 2007) New Revision: 5204 Modified: trunk/jbpm/docs/reference/en/modules/Introduction.xml trunk/jbpm/docs/reference/en/modules/Test_Drive_Proc.xml trunk/jbpm/docs/reference/en/modules/The_JBoss_jBPM_Int_Mech.xml trunk/jbpm/docs/reference/en/modules/guided_tour_jboss_jbpmgpd.xml Log: spelling is corrected Modified: trunk/jbpm/docs/reference/en/modules/Introduction.xml =================================================================== --- trunk/jbpm/docs/reference/en/modules/Introduction.xml 2007-12-03 16:27:58 UTC (rev 5203) +++ trunk/jbpm/docs/reference/en/modules/Introduction.xml 2007-12-03 16:58:10 UTC (rev 5204) @@ -10,7 +10,7 @@ </keywordset> </chapterinfo> <title>Introduction</title> - <para>All developers and process analists who are beginning to use JBoss jBPM should read this Getting Started guide. It will give them a jumpstart showing how to create a process definition.</para> + <para>All developers and process analysts who are beginning to use JBoss jBPM should read this Getting Started guide. It will give them a jumpstart showing how to create a process definition.</para> <section id="Preface"> <?dbhtml filename="Preface.html"?> <title>Preface</title> Modified: trunk/jbpm/docs/reference/en/modules/Test_Drive_Proc.xml =================================================================== --- trunk/jbpm/docs/reference/en/modules/Test_Drive_Proc.xml 2007-12-03 16:27:58 UTC (rev 5203) +++ trunk/jbpm/docs/reference/en/modules/Test_Drive_Proc.xml 2007-12-03 16:58:10 UTC (rev 5204) @@ -14,9 +14,9 @@ <para> One of the most important advantages of JBoss jBPM&apos;s lightweight approach to BPM and workflow management is that developers can easily leverage their usual programming - skills and techiques. One of these well-known techniques is unit testing and test driven + skills and techniques. One of these well-known techniques is unit testing and test driven development. In this chapter we will show how developers, making use of the JBoss jBPM GPD - can use a technique we have baptised <property>Test Driven Process Development</property> to + can use a technique we have baptized <property>Test Driven Process Development</property> to create process definitions and test their correctness. </para> <para> When creating the <emphasis> @@ -79,7 +79,7 @@ <para>In the first line of the method, a jBPM process archive object is created. We use a constructor accepting the filename of the archive. In our case it is the <emphasis> - <property>hello</property></emphasis> file we created earlier and wich lives in the + <property>hello</property></emphasis> file we created earlier and which lives in the <emphasis> <property>src/main/jpdl</property></emphasis> folder of our project. After asserting that this object is really created, we extract a process definition object from it. This object is fed to the Modified: trunk/jbpm/docs/reference/en/modules/The_JBoss_jBPM_Int_Mech.xml =================================================================== --- trunk/jbpm/docs/reference/en/modules/The_JBoss_jBPM_Int_Mech.xml 2007-12-03 16:27:58 UTC (rev 5203) +++ trunk/jbpm/docs/reference/en/modules/The_JBoss_jBPM_Int_Mech.xml 2007-12-03 16:58:10 UTC (rev 5204) @@ -27,7 +27,7 @@ implementation of the <emphasis> <property>ActionHandler</property> </emphasis> interface, and attach this piece of code to a particular event. These events - are amongst others, going over a transition, leaving or enterning nodes, after and + are amongst others, going over a transition, leaving or entering nodes, after and before signalling. </para> <figure> Modified: trunk/jbpm/docs/reference/en/modules/guided_tour_jboss_jbpmgpd.xml =================================================================== --- trunk/jbpm/docs/reference/en/modules/guided_tour_jboss_jbpmgpd.xml 2007-12-03 16:27:58 UTC (rev 5203) +++ trunk/jbpm/docs/reference/en/modules/guided_tour_jboss_jbpmgpd.xml 2007-12-03 16:58:10 UTC (rev 5204) @@ -200,7 +200,7 @@ <property>Window &gt; Show view &gt; Outline</property> </emphasis>). It is presented as the classical tree view. Also you can use <emphasis> <property>Overview</property> - </emphasis> that comes as as a scrollable thumbnail.</para> + </emphasis> that comes as a scrollable thumbnail.</para> <figure> <title>The Outline and Overview Views</title> <mediaobject> @@ -251,7 +251,7 @@ <para>Some properties can be directly edited in the graphical editor. One example of this is the <emphasis> <property>Name</property> - </emphasis> property of nodes. You can edit this directly by selecting the node of wich + </emphasis> property of nodes. You can edit this directly by selecting the node of which you want to change the name and then click once inside this node. This enables an editor in the node. We change the name of the node to <emphasis> <property>auction</property>