Return-Path: 
 <commits-return-40366-apmail-commons-commits-archive=commons.apache.org@commons.apache.org>
X-Original-To: apmail-commons-commits-archive@minotaur.apache.org
Delivered-To: apmail-commons-commits-archive@minotaur.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id 0E8231021D
	for <apmail-commons-commits-archive@minotaur.apache.org>;
 Mon, 10 Mar 2014 22:59:54 +0000 (UTC)
Received: (qmail 80843 invoked by uid 500); 10 Mar 2014 22:59:52 -0000
Delivered-To: apmail-commons-commits-archive@commons.apache.org
Received: (qmail 80782 invoked by uid 500); 10 Mar 2014 22:59:52 -0000
Mailing-List: contact commits-help@commons.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:commits-help@commons.apache.org>
List-Unsubscribe: <mailto:commits-unsubscribe@commons.apache.org>
List-Post: <mailto:commits@commons.apache.org>
List-Id: <commits.commons.apache.org>
Reply-To: dev@commons.apache.org
Delivered-To: mailing list commits@commons.apache.org
Received: (qmail 80775 invoked by uid 99); 10 Mar 2014 22:59:51 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 10 Mar 2014 22:59:51 +0000
X-ASF-Spam-Status: No, hits=-2000.0 required=5.0
	tests=ALL_TRUSTED
X-Spam-Check-By: apache.org
Received: from [140.211.11.4] (HELO eris.apache.org) (140.211.11.4)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 10 Mar 2014 22:59:50 +0000
Received: from eris.apache.org (localhost [127.0.0.1])
	by eris.apache.org (Postfix) with ESMTP id ABC38238890D;
	Mon, 10 Mar 2014 22:59:30 +0000 (UTC)
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Subject: svn commit: r1576120 -
 /commons/proper/scxml/trunk/src/site/xdoc/roadmap.xml
Date: Mon, 10 Mar 2014 22:59:30 -0000
To: commits@commons.apache.org
From: ate@apache.org
X-Mailer: svnmailer-1.0.9
Message-Id: <20140310225930.ABC38238890D@eris.apache.org>
X-Virus-Checked: Checked by ClamAV on apache.org

Author: ate
Date: Mon Mar 10 22:59:30 2014
New Revision: 1576120

URL: http://svn.apache.org/r1576120
Log:
some corrections

Modified:
    commons/proper/scxml/trunk/src/site/xdoc/roadmap.xml

Modified: commons/proper/scxml/trunk/src/site/xdoc/roadmap.xml
URL: http://svn.apache.org/viewvc/commons/proper/scxml/trunk/src/site/xdoc/roadmap.xml?rev=1576120&r1=1576119&r2=1576120&view=diff
==============================================================================
--- commons/proper/scxml/trunk/src/site/xdoc/roadmap.xml (original)
+++ commons/proper/scxml/trunk/src/site/xdoc/roadmap.xml Mon Mar 10 22:59:30 2014
@@ -29,12 +29,12 @@
       </p>
       <p>
         The goal for Commons SCXML 2.0 is to get alignment (back) and be compliant with the W3C SCXML specification,
-        but for this a lot of major changes are needed, both to the 'public' API and, even more so, to the internal
+        but for this a lot of major changes are needed, both to the public API and, even more so, to the internal
         model and processing logic.
       </p>
       <p>
         To be able to make such major changes in an effective way, we already cleaned out a lot of the old but no
-        longer relevant, working or otherwise compatible features from the previous SCXML (0.9) version, see
+        longer relevant, working or otherwise incompatible features from the previous SCXML (0.9) version, see
         <a href="#Milestone_0:_Cleanup_(done)">Milestone 0</a> below.
       </p>
       <p>
@@ -175,8 +175,8 @@
           will be used to test against.
         </p>
         <p>
-          Even if the IRP is not intended to be used for conformance testing of implementations, it is very much used as
-          a functional benchmark, also by other SCXML implementations.
+          Even though the IRP is not intended to be used for conformance testing of implementations, it is very much
+          used as a functional benchmark, also by other SCXML implementations.
         </p>
       </subsection>
       <subsection name="Commons SCXML 2.0+: Optional SCXML features">
@@ -186,7 +186,7 @@
         </p>
         <p>
           Also, adding extensions outside the specification, or bringing back some of the features dropped for
-          milestone 0, like integration with other frameworks or expression languages (Servlet, EL, etc.) will be
+          milestone 0, like integration with other frameworks or expression languages (Servlet, EL, etc.), will be
           considered again.
         </p>
       </subsection>
@@ -196,7 +196,7 @@
           For the above milestones specific VCS milestone tags will be set, like <b>commons-scxml-2.0-M0</b>.
         </p>
         <p>
-          These milestones tag however do <b><em>not</em></b> represent a formal release and they are
+          These milestones tags however do <b><em>not</em></b> represent a formal release and they are
           <b><em>only</em></b> intended and targeted to be used by the Commons SCXML developers, not end users.
         </p>
         <p>