From cd758e4cd677e51d4591c8ed0bdf355f35b52132 Mon Sep 17 00:00:00 2001
From: Ade Bateman <bateman@acm.org>
Date: Fri, 16 Sep 2016 15:40:19 -0700
Subject: [PATCH] Remove explanation using "parties"

Fixes #121.
---
 index.html | 12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)

diff --git a/index.html b/index.html
index 005aedb0..692e2732 100644
--- a/index.html
+++ b/index.html
@@ -109,12 +109,12 @@ <h2>Introduction</h2>
     checkout flows that support various payment schemes.</p>
 
   <p>This specification describes an API that allows <a>user agents</a> (e.g., browsers) to act
-    as an intermediary between the three key parties in every transaction: the merchant (e.g., an
-    online web store), the buyer (e.g., the user buying from the online web store), and the
-    <dfn data-lt="payment method|payment methods">Payment Method</dfn> (e.g., credit card). Information
-    necessary to process and confirm a transaction is passed between the <a>Payment Method</a> and the
-    merchant via the <a>user agent</a>  with the buyer confirming and authorizing as necessary across
-    the flow.</p>
+    as an intermediary between three systems in every transaction: the merchant (e.g., an
+    online web store), the buyer represented by the <a>user agent</a> (e.g., the user buying from the
+    online web store), and the <dfn data-lt="payment method|payment methods">Payment Method</dfn>
+    (e.g., credit card). Information necessary to process and confirm a transaction is passed between
+    the <a>Payment Method</a> and the  merchant via the <a>user agent</a> with the buyer confirming
+    and authorizing as necessary across the flow.</p>
 
   <p>In addition to better, more consistent user experiences, this also enables web sites to take
     advantage of more secure payment schemes (e.g., tokenization and system-level authentication)