--- a/latest/charters/payments-wg-charter.html Fri Jul 17 18:16:22 2015 -0500
+++ b/latest/charters/payments-wg-charter.html Fri Jul 17 18:32:05 2015 -0500
@@ -52,7 +52,7 @@
<h1 id="title">[DRAFT] Web Payments Working Group Charter</h1>
<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.
+ Web, through incremental improvements to Web infrastructure that support and facilitate payments.</p>
<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 glossary</a>.</p>
@@ -140,7 +140,7 @@
<ul>
<li>the high level flow of a Web payment;</li>
<li>the interfaces between the
- various parties (such as between user agent and Web application);
+ various parties (such as between user agent and Web application);</li>
<li>the messages exchanged between these
parties over the Web.</li>
</ul>
@@ -532,7 +532,7 @@
dissent, after due consideration of different opinions, the Chair should put a question out for voting
within the group (allowing for remote asynchronous participation -- using, for example, email and/or
web-based survey techniques) and record a decision, along with any objections. The matter should then be
- considered resolved unless and until new information becomes available.
+ considered resolved unless and until new information becomes available.</p>
<p>Any resolution first taken in a face-to-face meeting or teleconference (i.e., that does not follow a 7 day
call for consensus on the mailing list) is to be considered provisional until 5 working days after the