Editorial tweaks
authorIan Jacobs <ij@w3.org>
Thu, 16 Jul 2015 17:09:49 -0500
changeset 821 a3d97f176f87
parent 820 7b1ddf62c31a
child 822 9513c48dbc09
Editorial tweaks

From Timeless
latest/charters/payments-wg-charter.html
--- a/latest/charters/payments-wg-charter.html	Thu Jul 16 16:18:54 2015 -0500
+++ b/latest/charters/payments-wg-charter.html	Thu Jul 16 17:09:49 2015 -0500
@@ -54,7 +54,7 @@
     <p class="mission">The mission of the Web Payments Working Group is to make payments easier and more secure on the
         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 (payer, payee, etc.),
+    <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>
 
@@ -125,7 +125,7 @@
     <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,
-        loyalty programs, coupons, discounts, offers etc.).</p>
+        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
         relevant W3C Working Groups, based on a detailed analysis of the relevant <a
@@ -139,7 +139,7 @@
         <h2 id="scope">Scope</h2>
 
         <p>A payment, on the Web today, ordinarily starts on a payment page where the <strong>payer</strong> must
-            manually select a payment scheme, manually select their own <strong>payment instrument</strong> for that
+            manually select a <strong>payment scheme</strong>, manually select their own <strong>payment instrument</strong> for that
             payment scheme, manually capture the details of that instrument into the page (along with any other
             essential data such as a shipping address) and then submit this data back to the <strong>payee.</strong> The
             payment data briefly passes through the Web (from the payer's user agent to the payee's Website) on its way
@@ -200,7 +200,7 @@
                     <li>
                         <strong>Payment Initiation Request</strong>, by the payee to the payer providing the terms of
                         the payment including elements such as the accepted payment schemes, price, currency,
-                        recurrence, transaction type (purchase, refund etc.), timeout and requests for any additional
+                        recurrence, transaction type (purchase, refund, etc.), timeout and requests for any additional
                         data that is required from the payee.
                     </li>
                 </ul>
@@ -276,7 +276,7 @@
         <h2 id="wallets">Wallets</h2>
 
         <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
+            native applications, within applications in the Cloud, within user agents such as Web browsers or in the
             form of user agent extensions or plug-ins. Some of the capabilities provided by the standards from this
             group can be found in various Web services today, as well as in digital wallets. Because the "digital
             wallet" concept is useful as a shorthand, but means different things to different audiences, this charter
@@ -379,7 +379,7 @@
                 be proxied between a Web application and the payer's wallet service via a WebIDL API hosted by
                 the User Agent.
             </li>
-            <li><strong>Web services API</strong>: Where request messages may be passed to a cloud-based wallet service
+            <li><strong>Web services API</strong>: Where request messages may be passed to a Cloud-based wallet service
                 via that service's REST API endpoint(s) and where HTTP callbacks may be used to pass responses to other
                 Web services.
             </li>
@@ -495,7 +495,7 @@
                 <a href="/International/core/">Internationalization Core
                     Working Group</a>
             </dt>
-            <dd>Internationalization and localization review</dd>
+            <dd>Internationalization and localization review.</dd>
             <dt>
                 <a href="/2012/webcrypto/">Web Cryptography Working Group</a>
             </dt>