From d33fc4bc23057bde35b94ae7e7fa3fb435466ab5 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Marcos=20C=C3=A1ceres?= <marcos@marcosc.com>
Date: Mon, 9 Jul 2018 23:15:49 -0400
Subject: [PATCH] Define payerAddress more like shippingAddress

---
 index.html | 9 ++++-----
 1 file changed, 4 insertions(+), 5 deletions(-)

diff --git a/index.html b/index.html
index b4f15ccb..05c2a652 100644
--- a/index.html
+++ b/index.html
@@ -1283,11 +1283,10 @@ <h2>
           <dfn>payerAddress</dfn> attribute
         </h2>
         <p>
-          If the <a data-lt=
-          "PaymentOptions.requestPayerAddress">requestPayerAddress</a> member
-          was set to true in the <a>PaymentOptions</a> passed to the
-          <a>PaymentRequest</a> constructor, then <a>payerAddress</a> will be
-          the payer's address chosen by the user.
+          A <a>PaymentRequest</a>'s <a>payerAddress</a> attribute is populated
+          when the user provides a payer address (commonly referred to as a
+          billing address). It is null by default. When a user provides a
+          payer address, the <a>payer address changed algorithm</a> runs.
         </p>
         <p class="note">
           On some user agents, some attributes of <a>payerAddress</a> might be