From a944bf3076f5adac7da615cbb42ca145c72aeadf Mon Sep 17 00:00:00 2001
From: Shane McCarron <halindrome@gmail.com>
Date: Tue, 15 Mar 2016 09:26:20 -0500
Subject: [PATCH 1/3] Some friendly editorial changes

A couple of typos and suggested wording changes.  Use at your discretion.
---
 specs/architecture.html | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/specs/architecture.html b/specs/architecture.html
index 4c4d4c89..abfe880c 100644
--- a/specs/architecture.html
+++ b/specs/architecture.html
@@ -223,7 +223,7 @@ <h2>Specifications</h2>
 
       <p>The Payment Request Architecture organizes the above concepts into several component specifications
 	      so that they can be discussed and moved forward independently. The
-        <a href="#payment-method-identifiers">Payment Method Identifiers</a> specification the only
+        <a href="#payment-method-identifiers">Payment Method Identifiers</a> specification is the only
         common dependency. The following diagram shows the references between different specifications that describe
         the Payment Request Architecture. The arrows show normative references pointing from the referring
         document to the referenced document.
@@ -327,7 +327,7 @@ <h2>Relationship to Previous Concepts</h2>
         <ul>
         	<li>
         	  In the physical world it is not practical for users to have multiple wallets. On the Web this is
-            possible and for there to be a copies of the same payment method data in more than one wallet.</li>
+            possible and for there to be copies of the same payment method data in more than one wallet.</li>
         	<li> In the physical world the process of deciding how to pay is not done by the wallet, it is done by
            the user. On the Web the process of selection can be facilitated by digital algorithms that are capable
             of processing complex data and relationships to assist the user in deciding how to pay.</li>
@@ -348,7 +348,7 @@ <h2>Relationship to Previous Concepts</h2>
       	  <tr>
       	    <td>Payment App</td>
       	    <td>Digital Wallet, Payment Instrument </td>
-      	    <td>A piece of software to pay</td>
+      	    <td>A piece of software to manage payment methods</td>
       	  </tr>
       	  <tr>
       	    <td>Payment Method</td>
@@ -358,7 +358,7 @@ <h2>Relationship to Previous Concepts</h2>
       	  <tr>
       	    <td>Payment Mediator</td>
       	    <td>Digital Wallet, Payment Instrument</td>
-      	    <td>A piece of software that coordinates messages between Web apps and Payment apps</td>
+      	    <td>A piece of software that coordinates messages between sellers and Payment apps</td>
       	  </tr>
       	</table>
       </section>

From c57304427a822353d799ebb77e055b270e7f299c Mon Sep 17 00:00:00 2001
From: Shane McCarron <halindrome@gmail.com>
Date: Thu, 17 Mar 2016 07:47:54 -0500
Subject: [PATCH 2/3] Updated definition to make it more precise.

---
 specs/architecture.html | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/specs/architecture.html b/specs/architecture.html
index abfe880c..bfdd328f 100644
--- a/specs/architecture.html
+++ b/specs/architecture.html
@@ -348,7 +348,7 @@ <h2>Relationship to Previous Concepts</h2>
       	  <tr>
       	    <td>Payment App</td>
       	    <td>Digital Wallet, Payment Instrument </td>
-      	    <td>A piece of software to manage payment methods</td>
+      	    <td>A piece of software to manage payment methods and coordinate the issuance of payments.</td>
       	  </tr>
       	  <tr>
       	    <td>Payment Method</td>

From 417f86be6024f1a3556fadb3dc697f198fe89a5c Mon Sep 17 00:00:00 2001
From: Shane McCarron <halindrome@gmail.com>
Date: Thu, 24 Mar 2016 05:22:36 -0500
Subject: [PATCH 3/3] Update architecture.html

Updated to reflect agreed upon wording.
---
 specs/architecture.html | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/specs/architecture.html b/specs/architecture.html
index bfdd328f..8f60e10a 100644
--- a/specs/architecture.html
+++ b/specs/architecture.html
@@ -348,7 +348,8 @@ <h2>Relationship to Previous Concepts</h2>
       	  <tr>
       	    <td>Payment App</td>
       	    <td>Digital Wallet, Payment Instrument </td>
-      	    <td>A piece of software to manage payment methods and coordinate the issuance of payments.</td>
+      	    <td>An application, registered by the payer, that supports processing payment 
+      	    requests and returning payment responses for one or more payment methods.</td>
       	  </tr>
       	  <tr>
       	    <td>Payment Method</td>
@@ -358,7 +359,7 @@ <h2>Relationship to Previous Concepts</h2>
       	  <tr>
       	    <td>Payment Mediator</td>
       	    <td>Digital Wallet, Payment Instrument</td>
-      	    <td>A piece of software that coordinates messages between sellers and Payment apps</td>
+      	    <td>A piece of software that coordinates messages between sellers and Payment apps.</td>
       	  </tr>
       	</table>
       </section>