[w3c/webpayments-payment-apps-api] Small fixes (#114)

* Small fixes
* Also clarified that paymentResponse is not necessarily for successful
completion of "payment" in the sense of exchange of funds. For example,
it might involve merely returning card credentials. So reframed in terms
of successful user interaction.

Question: can/should we reuse PaymentResponse rather than create a new PaymentAppResponse?
You can view, comment on, or merge this pull request online at:

  https://github.com/w3c/webpayments-payment-apps-api/pull/114

-- Commit Summary --

  * * Small fixes

-- File Changes --

    M index.html (10)

-- Patch Links --

https://github.com/w3c/webpayments-payment-apps-api/pull/114.patch
https://github.com/w3c/webpayments-payment-apps-api/pull/114.diff

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/webpayments-payment-apps-api/pull/114