--- a/latest/charters/payments-wg-charter.html	Fri Jul 17 17:11:34 2015 -0500
+++ b/latest/charters/payments-wg-charter.html	Fri Jul 17 17:23:30 2015 -0500
@@ -290,9 +290,11 @@
                 function that is complimentary to its payment capabilities.
             </li>
         </ul>
-          <p>This group is not developing standards for all digital wallet capabilities: this charter's scope is limited to payment flow capabilities. At the same time, this definition of wallet is not intended to constrain W3C's future activities. Indeed, W3C expects to expand its activities to standardize additional
-	    functions of physical wallets
-            such as holding digital receipts and digital credentials. The wallet metaphor appropriate to this charter may change in future charters or may be dropped if no longer relevant.</p>
+          <p>This group is not developing standards for all digital wallet capabilities: this charter's scope is limited to payment flow capabilities. At the same time, this definition of wallet is not intended to constrain W3C's future activities. Indeed, W3C anticipates a rich ecosystem of eCommerce and payment
+            functionality on the Web, including loyalty schemes and coupons, digital receipts, digital credentials, location services, marketing
+            additions, and more. Some of this functionality may be provided by a digital wallet, or by other services
+            available to the payer. This charter does not seek to preclude those additional services, and in the future
+            W3C may look for opportunities increase the interoperability of such services. The wallet metaphor appropriate to this charter may change in future charters or may be dropped if no longer relevant.</p>
 
         <p>This Working Group intends to create a standard interface from the Web to a payer's wallet so that someone with any
             conforming wallet can seamlessly make payments with any conforming application running in a conforming
@@ -304,12 +306,6 @@
           <p>The group may also consider the use case where an aggregation service acts as a more sophisticated wallet service or providing a wider choice of payment solutions to the payer. For example, the aggregator service might combine the functionality of multiple wallet services, or apply more complex algorithms to discover and collect the set of payment
             instruments available to the payer.</p>
 
-        <p>
-            <strong>Note:</strong> The Working Group anticipates a rich ecosystem of eCommerce and payment
-            functionality, including loyalty schemes and coupons, digital receipts, location services, marketing
-            additions, and so on. Some of this functionality may be provided by a digital wallet, or by other services
-            available to the payer. This charter does not seek to preclude those additional services, and in the future
-            W3C may look for opportunities to standardize and increase interoperability of such services.</p>
         <h3 id="out_of_scope">Out of Scope</h3>
 
         <p>This group will not define a new payment scheme, or redefine that which is already addressed today by payment