diff options
Diffstat (limited to 'contrib/articles/ui/ui.tex')
| -rw-r--r-- | contrib/articles/ui/ui.tex | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/contrib/articles/ui/ui.tex b/contrib/articles/ui/ui.tex index 37cd8b076..4aef43bd4 100644 --- a/contrib/articles/ui/ui.tex +++ b/contrib/articles/ui/ui.tex @@ -933,7 +933,7 @@ the page. Then the wallet inspects the response as it may contain error reports about a failed payment which the wallet has to handle. By submitting the payment this way, we also ensure that this intermediate request does not require JavaScript and still does not -interfer with navigation. Once the Web shop confirms the payment, the +interfere with navigation. Once the Web shop confirms the payment, the wallet causes the fulfillment URL to be reloaded. If the contract hash does not match a payment which the user @@ -989,7 +989,7 @@ it has the following key advantages: other users has the expected behavior of asking the other user to pay for the resource. \item Asynchronously transmitting coins from injected JavaScript costs - one roundtrip, but does not interfer with navigation and allows + one roundtrip, but does not interfere with navigation and allows proper error handling. \item The different pages of the merchant have clear delineations: the shopping pages conclude by making an offer, and @@ -1189,7 +1189,7 @@ passes it to the wallet (sample code for this is shown in Figure~\ref{listing:contract}). Instead of adding any cryptographic logic to the merchant frontend, -the Taler merchant backend allows the implementor to delegate +the Taler merchant backend allows the implementer to delegate coin handling to the payment backend, which validates the coins, deposits them at the exchange, and finally validates and persists the receipt from the exchange. The merchant backend then communicates the |