Fix minor issues spotted by Shane McCarron.
authorManu Sporny <msporny@digitalbazaar.com>
Mon, 30 Mar 2015 00:50:14 -0400
changeset 108 c0466f717f4a
parent 107 ad521ad885b4
child 109 eed0efa464af
Fix minor issues spotted by Shane McCarron.
latest/use-cases/index.html
--- a/latest/use-cases/index.html	Mon Mar 30 00:09:19 2015 -0400
+++ b/latest/use-cases/index.html	Mon Mar 30 00:50:14 2015 -0400
@@ -157,7 +157,7 @@
     <p>
 ECommerce is thriving and continues to expand. However
 fragmentation of payment systems is limiting the growth potential
-as are problems —both real and perceived— such as
+as are problems &mdash; both real and perceived &mdash; such as
 fraud and usability.
     </p>
 
@@ -174,15 +174,14 @@
     </p>
 
     <p>
-To achieve greater interoperability among merchants and their
-customers, payment providers, software vendors, mobile operators,
-and payment networks, the W3C Web Payments Interest Group is
-developing a roadmap for standards to improve the interoperability
-of payments on the Web, including
-<a title="payment scheme">payment schemes</a> in use today
-(such as electronic cheques, credit cards, direct debit, and
-cryptocurrencies) and those of the future. The roadmap will be derived
-from the use cases listed below.
+The W3C Web Payments Interest Group is developing a roadmap for standards to
+improve the interoperability of payments on the Web. This will help achieve
+greater interoperability among merchants and their customers,
+payment providers, software vendors, mobile operators, and payment networks.
+The roadmap will include <a title="payment scheme">payment schemes</a> in use
+today (such as electronic cheques, credit cards, direct debit, and
+cryptocurrencies) and those of the future. The roadmap will be derived from
+the use cases listed below.
     </p>
 
     <section>
@@ -238,7 +237,7 @@
 of how the payment phases apply.
         </li>
         <li>
-Section 6 lists the use cases, short scenarios that cover
+Section 6 lists the use cases - short scenarios that cover
 diverse aspects of each payment step.
         </li>
       </ul>
@@ -352,7 +351,7 @@
       </dd>
       <dt><dfn>payment processor</dfn></dt>
       <dd>
-Submits and processes payments using a particular
+An <a>entity</a> that submits and processes payments using a particular
 <a>payment instrument</a> to a payment network. Examples: Stripe, PayPal,
 Authorize.net, Atos, FedACH</li>
       </dd>
@@ -472,9 +471,7 @@
         <li>
 <strong>Discovery of Accepted Schemes</strong>. The <a>payer</a>
 discovers the <a title="payment instrument">payment instruments</a> that
-are accepted by the <a>payee</a>. These will vary depending on the types
-of <a title="payment instrument">payment instruments</a> that the
-<a>payee</a> accepts.
+are accepted by the <a>payee</a>.
         </li>
         <li>
 <strong>Selection of Payment Instruments</strong>. The <a>payee</a>
@@ -600,7 +597,7 @@
       <p>
 <strong>Discovery of Accepted Schemes</strong>: Given where Jill lives,
 PayToParty offers her payment by credit card, debit card, the PayToParty
-loyalty card and PayPal, but not Jill's favorite cryptocurrency (which she
+loyalty card, and PayPal, but not Jill's favorite cryptocurrency (which she
 uses on other sites).
       </p>
 
@@ -646,8 +643,7 @@
 <strong>Completion of Transfer</strong>. Since Jill's PayToParty loyalty card
 operates as a credit card, the PayToParty site is immediately credited with
 the <a>purchase</a> amount and the funds will be swept into their bank account
-at the end of the week. Jill will pay off the credit line at the end of the
-month.
+at the end of the week.
         </p>
     </section>