Manu's wording changes to wallet section
authorAdrian Hope-Bailie <adrian@hopebailie.com>
Sun, 12 Jul 2015 07:12:10 -0700
changeset 437 7b5f6e354683
parent 436 73318158c957
child 438 720e4a9a21b0
Manu's wording changes to wallet section
latest/charters/payments-wg-charter.html
--- a/latest/charters/payments-wg-charter.html	Sun Jul 12 00:35:24 2015 +0200
+++ b/latest/charters/payments-wg-charter.html	Sun Jul 12 07:12:10 2015 -0700
@@ -266,11 +266,11 @@
 
         <p>The group intends to create a standard interface from the Web to a user's wallet so that a user with any
             conforming wallet can seamlessly make payments with any conforming Web application running in a conforming
-            user agent. Though not a requirement for this charter, the group may define APIs that may also be used
-            outside of a browser context (such as from within a native application, where the browser is not the proxy
-            between wallet and payee application).</p>
+            user agent. The group may define APIs that will also be used outside of a browser context (such as between
+            Web services, or from within a native application, where the browser is not the proxy between wallet and
+            payee application).</p>
 
-        <p>The group will also consider the use case where an aggregation service stands in place of a wallet service
+        <p>The group may also consider the use case where an aggregation service stands in place of a wallet service
             and offers the user a wider choice of payment solutions by combining the functionality of multiple wallet
             services or performing a complex payment instrument discovery process to collect the set of payment
             instruments the user has available.</p>