[jbpm-commits] JBoss JBPM SVN: r5815 - jbpm4/trunk/modules/userguide/src/main/docbook/en/modules.

[do-not-reply at jboss.org]

Author: jbarrez
Date: 2009-10-27 11:22:03 -0400 (Tue, 27 Oct 2009)
New Revision: 5815

Modified:
   jbpm4/trunk/modules/userguide/src/main/docbook/en/modules/ch01-Introduction.xml
Log:
Fixed some typos and linkes in introduction chapter

Modified: jbpm4/trunk/modules/userguide/src/main/docbook/en/modules/ch01-Introduction.xml
===================================================================
--- jbpm4/trunk/modules/userguide/src/main/docbook/en/modules/ch01-Introduction.xml	2009-10-27 14:44:56 UTC (rev 5814)
+++ jbpm4/trunk/modules/userguide/src/main/docbook/en/modules/ch01-Introduction.xml	2009-10-27 15:22:03 UTC (rev 5815)
@@ -9,7 +9,7 @@
     <title>License and EULA</title>
     <para>jBPM is distributed under the terms of the 
     GNU Lesser General Public License (LGPL) and the JBoss End User License Agreement (EULA).  
-    See <ulink url="../../../lgpl.html">the full LGPL license text</ulink> and <ulink url="../../../JBossORG-EULA.txt">the 
+    See <ulink url="../../../license.txt">the full LGPL license text</ulink> and <ulink url="../../../jboss.eula.txt">the 
     full End User License Agreement</ulink>. 
     </para>
   </section>
@@ -18,7 +18,7 @@
     <title>Downloads</title>
     <para>The distribution packages can be downloaded from sourceforge
     </para>
-    <ulink url="http://sourceforge.net/project/showfiles.php?group_id=70542&amp;package_id=268068">http://sourceforge.net/project/showfiles.php?group_id=70542&amp;package_id=268068</ulink>
+    <ulink url="http://sourceforge.net/projects/jbpm/files/">http://sourceforge.net/projects/jbpm/files/</ulink>
   </section>
 
   <section>
@@ -41,7 +41,7 @@
     process language in persistent execution mode.  Persistent 
     execution mode means that process definitions, process executions 
     and process history is stored in a relational DB.  This is the common way 
-    of how jBPM is used. 
+    of how jBPM is used in practice. 
     </para>
     <para>This user guide explains the supported way on how to use jBPM.
     The developers guide explains more advanced customization options that 
@@ -51,8 +51,8 @@
 
   <section>
     <title>Migration from jBPM 3</title>
-    <para>Migration from jBPM 3 to jBPM 4 is not supported. Check out the developers 
-    guide for more information about migration.
+    <para>Migration from jBPM 3 to jBPM 4 is not supported. 
+    Check out the developers guide for hints on how to perform the migration.
     </para>
   </section>
 
@@ -65,23 +65,23 @@
 - <emphasis role="bold">jBPM Version</emphasis> : which version of jBPM are you using?
 - <emphasis role="bold">Database</emphasis> : which database and which version of that database
 - <emphasis role="bold">JDK</emphasis> : which Java version are you using? use 'java -version' to find out
-- <emphasis role="bold">Container</emphasis> : which Java version are you using? use 'java -version' to find out
-- <emphasis role="bold">Configuration</emphasis> : is your jbpm.cfg.xml only importing files from the jbpm.jar
+- <emphasis role="bold">Container</emphasis> : which container are you using? (JBoss, Tomcat, etc.)
+- <emphasis role="bold">Configuration</emphasis> : is your jbpm.cfg.xml only using imports from the jbpm.jar
    lib itself? or did you create a custom config file?
 - <emphasis role="bold">Libraries</emphasis> : are you using the exact versions of the libs from inside the jbpm
    distribution of the version that you're using? or did you change some of the libs?
 
 <emphasis role="bold">=== Process ==================================</emphasis>
-past jPDL process here
+paste jPDL process here
 
 <emphasis role="bold">=== API ===================================</emphasis>
-past the relevant code snippet that you use to invoke jBPM
+paste the relevant code snippet that you use to invoke jBPM
 
 <emphasis role="bold">=== Stacktrace ==============================</emphasis>
-past full stack trace here
+paste full stack trace here
 
 <emphasis role="bold">=== Debug logs ==============================</emphasis>
-past debug logs here
+paste debug logs here
 
 <emphasis role="bold">=== Problem description =========================</emphasis>
 Keep this part short and to the point. E.g. API doesn't work as expected.