Editorial
authorIan Jacobs <ij@w3.org>
Thu, 16 Jul 2015 20:35:13 -0500
changeset 326 8a667badfad0
parent 325 64c81659d93d
child 327 e8a65f2a6fb2
Editorial

- Moved wallets section
- typo fix
latest/charters/payments-wg-charter.html
--- a/latest/charters/payments-wg-charter.html	Thu Jul 16 20:30:17 2015 -0500
+++ b/latest/charters/payments-wg-charter.html	Thu Jul 16 20:35:13 2015 -0500
@@ -157,7 +157,7 @@
 	    <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
+	      <p>The result is that users are led 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
@@ -271,14 +271,7 @@
             it is important to ensure the standards put forward by the group are considerate of how these hardware
             integrations may fit into the payment flow.</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
-            schemes. The standards from this group will provide a channel for protocols and messages defined by payment
-            schemes.</p>
-    </div>
-    <div>
-        <h2 id="wallets">Wallets</h2>
+        <h3 id="wallets">Relation to Wallets</h3>
 
         <p>The standards from this group may be implemented in a variety of ways, including within stand-alone Web or
             native applications, within applications in the Cloud, within user agents such as Web browsers or in the
@@ -330,6 +323,11 @@
             additions, and so on. Some of this functionality may be provided by a digital wallet, or by other services
             available to the user. 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
+            schemes. The standards from this group will provide a channel for protocols and messages defined by payment
+            schemes.</p>
     </div>
     <div>
         <h2 id="deliverables">Deliverables</h2>