Fix markup errors.
authorIan Jacobs <>
Mon, 30 Mar 2015 17:05:14 -0500
changeset 117 15797901d99d
parent 116 acabcc29e003
child 118 81612f49856a
Fix markup errors.
--- a/latest/use-cases/index.html	Mon Mar 30 17:02:16 2015 -0500
+++ b/latest/use-cases/index.html	Mon Mar 30 17:05:14 2015 -0500
@@ -353,7 +353,7 @@
 An <a>entity</a> that submits and processes payments using a particular
 <a>payment instrument</a> to a payment network. Examples: Stripe, PayPal,, Atos, FedACH</li>, Atos, FedACH.
@@ -419,14 +419,14 @@
 It is also important to note that these phases and steps may be interrupted
 at various times (e.g., one party drops out, or exceptions occur like
-insufficient funds, refunds, or a regulatory block). While these phases are an
+insufficient funds or a regulatory block). While these phases are an
 approximation of the general flow of all payments, they are helpful in
 structuring the use cases such that it is easy to figure out to which part of
 the payment process a particular use case belongs.
  <p>While these four phases may apply more or less well to a variety
-of other payment scenarios such as refunds or person-to-person
+of other payment scenarios such as person-to-person
 payments, those topics are not the current focus of the group.  We
 plan to address them directly in <a href="#future-work">future
@@ -537,7 +537,7 @@
 <strong>Delivery of Receipt</strong>. Depending on the
-<a title="payment scheme">payment scheme(s)</a></a> chosen, there are
+<a title="payment scheme">payment scheme(s)</a> chosen, there are
 various ways and times that a receipt may be delivered (e.g., credit card
 receipt, digital proof of <a>purchase</a>, encrypted line-item receipt, etc.).
@@ -1960,8 +1960,6 @@
         <h4>Delivery of Receipt</h4>
-        <p>
-        </p>
         <dl class="dl-horizontal">
           <dt>Electronic Receipts</dt>
@@ -2024,6 +2022,11 @@
+      </section>
+      <section>
+        <h4>Delivery of Receipt</h4>
         <dl class="dl-horizontal">