Merge pull request #27 from w3c/wseltzer-patch-1
authorianbjacobs <ij@w3.org>
Sat, 18 Jul 2015 14:37:57 -0500
changeset 873 6d14cf28cb60
parent 851 4548cd65e3af (current diff)
parent 872 9b409de80a28 (diff)
child 875 ec4109dd7188
Merge pull request #27 from w3c/wseltzer-patch-1

Editorial changes and typos
--- a/latest/charters/payments-wg-charter.html	Fri Jul 17 18:31:46 2015 -0500
+++ b/latest/charters/payments-wg-charter.html	Sat Jul 18 14:37:57 2015 -0500
@@ -274,7 +274,7 @@
                 payments.
             </li>
             <li>It may enrich the payment flow by implementing business logic for loyalty, coupons, ticketing or other
-                function that is complimentary to its payment capabilities.
+                function that is complementary 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 anticipates a rich ecosystem of eCommerce and payment
@@ -294,7 +294,7 @@
 
 	  <p>In the design of these standards, the Working Group will not assume that each user has only one wallet. In this charter, the phrase "the payer's wallet" is shorthand for "the payer's wallet(s)" as the payer may have multiple wallets.</p>
 
-	   <p>The Working Group may 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
+	   <p>The Working Group may consider the use case where an aggregation service acts as a more sophisticated wallet service or provides 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>
 
         <h3 id="out_of_scope">Out of Scope</h3>
@@ -319,7 +319,7 @@
                 <strong>Payment Terms Description</strong>: used to define the terms requested by the payee in the
                 payment initiation request and the terms accepted by the payer in the payment initiation response. It
                 includes information such as amount, currency, payee account information, recurrence, transaction
-                reference and any scheme specific data that is required.
+                reference and any scheme-specific data that is required.
             </li>
             <li>
                 <strong>Proof of Payment</strong>: a verifiable payment authorization from the account provider to the
@@ -445,7 +445,7 @@
                 <a href="/Payments/IG/">Web Payments Interest Group</a>
             </dt>
             <dd>The Web Payments Interest Group acts as the overall coordinator at W3C of a vision for Web Payments, by gathering <a
-                    href="/TR/web-payments-use-cases/">Web Payments Use Cases</a>, engaging in liaisons with other payments standards bodies, and developing a high-evel architecture. The group intends to explore more eCommerce scenarios than are represented in the current Working Group charter, such as digital receipts; loyalty programs and coupons; peer-to-peer payments; and harmonization of user
+                    href="/TR/web-payments-use-cases/">Web Payments Use Cases</a>, engaging in liaisons with other payments standards bodies, and developing a high-level architecture. The group intends to explore more eCommerce scenarios than are represented in the current Working Group charter, such as digital receipts; loyalty programs and coupons; peer-to-peer payments; and harmonization of user
               experience in-browser, in-app, and in-store. From time to time, the Interest Group will seek feedback from the Working Group on its evolving vision, and share information about the evolution of the Web payments technology landscape. The Interest Group may also propose new Working Groups to cover topics such as identity, credentials and commerce (including invoicing, receipts,
         loyalty programs, coupons, discounts, and offers). The Web Payments Interest Group also expects to provide technical input to this and other
         relevant W3C Working Groups, based on a detailed analysis of the relevant <a
@@ -505,7 +505,7 @@
             </dd>
         </dl>
 
-	<p>In addition, for the Care Payments 1.0 specification, the Working Group will need to collaborate with the owners of existing global card schemes.</p>
+	<p>In addition, for the Card Payments 1.0 specification, the Working Group will need to collaborate with the owners of existing global card schemes.</p>
 
     </div>
     <div class="participation">