--- a/latest/charters/payments-wg-charter.html	Thu Jul 16 17:22:05 2015 -0500
+++ b/latest/charters/payments-wg-charter.html	Thu Jul 16 20:30:17 2015 -0500
@@ -55,8 +55,7 @@
         Web, through incremental improvements to Web infrastructure that support and facilitate payments.
 
     <p><strong>Note</strong>: For more information about roles involved in this payment flow (e.g., payer, payee) and some terms used in the payments industry (e.g., payment scheme),
-        please see the <a href="http://www.w3.org/TR/2015/WD-web-payments-use-cases-20150416/#terminology">Web Payments
-            Interest Group's glossary</a>.</p>
+        please see the <a href="http://www.w3.org/TR/2015/WD-web-payments-use-cases-20150416/#terminology">Web Payments glossary</a>.</p>
 
     <div class="noprint">
         <p class="join">@@Join the Web Payments Working Group.</p>
@@ -124,7 +123,7 @@
     </ul>
     <p>
         The Web Payments Interest Group will continue to guide the W3C in the Web Payments activity and may propose new
-        working groups to cover topics such as identity, credentials and commerce (including invoicing, receipts,
+        Working Groups to cover topics such as identity, credentials and commerce (including invoicing, receipts,
         loyalty programs, coupons, discounts, and offers).</p>
 
     <p>As part of this work the Web Payments Interest Group expects to provide technical input to this and other
@@ -149,10 +148,16 @@
         <p>In an effort to improve upon this process, various parties have innovated ways to make the payment flow
             easier, for example by caching payment instrument information in browsers, registering users on eCommerce
             websites to facilitate re-use of customer data and/or payment credentials (increasingly through the use of
-            tokenization), and even developing new payment schemes. Unfortunately, these efforts all suffer from a lack
-            of standardization. Standardization of the high level flow of a Web payment, of the interfaces between the
-            various parties (example: the user agent and the Web application) or of the messages exchanged between these
-            parties over the Web. The result is that users are lead through entirely different flows and verification
+            tokenization), and even developing new payment schemes. Unfortunately, these efforts suffer from a lack
+          of standardization in areas such as:</p>
+	<ul>
+	  <li>the high level flow of a Web payment;</li>
+	    <li>the interfaces between the
+            various parties (such as between user agent and Web application);
+	    <li>the messages exchanged between these
+              parties over the Web.</li>
+	    </ul>
+	      <p>The result is that users are lead through entirely different flows and verification
             routines every time they make a payment on the Web.</p>
 
         <p>This group will create open Web standards for the <em>interfaces</em> in and out of the Web context to
@@ -167,7 +172,7 @@
             confirmation and completion of a payment. By focusing on the message format and flow the group leaves open
             the standardisation of the delivery mechanism for these messages as this will vary depending on the use case
             and technology stack. To support use cases where messages are proxied between payer and payee using
-            different technologies, the group will aim to standardize delivery mechanisms for common scenarios. This
+            different technologies, the group will standardize delivery mechanisms for common scenarios. This
             will include WebIDL APIs for the use cases where the messages are proxied between payer and payee via a Web
             browser or Web APIs where the messages are exchanged directly over the Web between two online entities in
             the classic REST pattern.</p>
@@ -411,8 +416,7 @@
 
         <h4>Test Suites</h4>
 
-        <p>The Web Payments Working Group will allocate the necessary resources to build Test Suites for each
-            specification.</p>
+        <p>The Web Payments Working Group anticipates developing test suites for Recommendation-track specifications it develops.</p>
 
         <h4>Milestones</h4>
         <table width="80%" class="roadmap">
@@ -455,9 +459,10 @@
             </tr>
             </tbody>
         </table>
-        <h3 id="other_deliverables">Other deliverables</h3>
 
-        <p>The Working Group will document best practices and recommended algorithms for the discovery of payer payment
+        <h3 id="best_practices">Instrument Discovery Best Practices</h3>
+
+	<p>The Working Group may document best practices and recommended algorithms for the discovery of payer payment
             instruments by wallet services. This involves best practice approaches for discovering the supported payer
             payment instruments given the payer's configured payment instruments and those acceptable to a payee as
             listed in a payment initiation request.</p>
@@ -497,7 +502,7 @@
             </dt>
             <dd>Consultation on encryption of messages that are part of these APIs.</dd>
             <dt>
-                <a href="/WAI/PF/">Protocols and Formats Working Group</a>(and successor)
+                <a href="/WAI/PF/">Protocols and Formats Working Group</a> (and successor)
             </dt>
             <dd>To help ensure the protocols support accessibility.</dd>
         </dl>
@@ -530,8 +535,7 @@
 
         <p>To be successful, the Web Payments Working Group is expected to have active participants for its duration.
             Effective participation in Web Payments Working Group may consume .1FTE for each participant; for editors
-            this commitment may be higher. The Web Payments Working Group will allocate also the necessary resources for
-            building Test Suites for each specification.</p>
+          this commitment may be higher.</p>
     </div>
     <div class="communication">
         <h2 id="communication">Communication</h2>