From 9d658893a6a139632648ec0397bceaae8f02c723 Mon Sep 17 00:00:00 2001
From: Shane McCarron <halindrome@gmail.com>
Date: Mon, 19 Sep 2016 10:04:02 +0100
Subject: [PATCH] Remove must in complete()

The complete method description indicated that the method must be called after the user has accepted the payment request.  This use of "must" was a requirement on the web page, and as an RFC 2119 term was misleading.

Also, there is a SHOULD requirement on user agents in the paragraph, but the SHOULD was not in upper case so it was not called out as an assertion.
---
 index.html | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/index.html b/index.html
index c2f829cf..97aba896 100644
--- a/index.html
+++ b/index.html
@@ -1095,9 +1095,9 @@ <h2>PaymentResponse interface</h2>
 
   <section>
     <h2>complete()</h2>
-    <p>The <code><dfn>complete</dfn></code> method must be called after the user has accepted the payment
+    <p>The <code><dfn>complete</dfn></code> method is called after the user has accepted the payment
       request and the [[\acceptPromise]] has been resolved. Calling the <code>complete</code> method tells
-      the <a>user agent</a> that the user interaction is over (and should cause any remaining user interface to be
+      the <a>user agent</a> that the user interaction is over (and SHOULD cause any remaining user interface to be
       closed).</p>
     <p>The <code>complete</code> method takes a string argument from the <code><dfn>PaymentComplete</dfn></code>
       enum (<code>result</code>). These values are used to influence the user experience provided by the <a>user agent</a>