aboutsummaryrefslogtreecommitdiff
path: root/articles
diff options
context:
space:
mode:
authorChristian Grothoff <christian@grothoff.org>2016-08-26 15:50:17 +0200
committerChristian Grothoff <christian@grothoff.org>2016-08-26 15:50:17 +0200
commitacfc24ff3c3c7804415588d73d849dd1110acfb2 (patch)
treed3be421900c09e7624b4e00c28adde337af3ef92 /articles
parentf85f75b7db615662d80dd89e39b2f99fa1e8e2f8 (diff)
downloadwallet-core-acfc24ff3c3c7804415588d73d849dd1110acfb2.tar.gz
wallet-core-acfc24ff3c3c7804415588d73d849dd1110acfb2.tar.bz2
wallet-core-acfc24ff3c3c7804415588d73d849dd1110acfb2.zip
do not be so POST-specific
Diffstat (limited to 'articles')
-rw-r--r--articles/ui/ui.tex4
1 files changed, 2 insertions, 2 deletions
diff --git a/articles/ui/ui.tex b/articles/ui/ui.tex
index ba5941643..a45eb051c 100644
--- a/articles/ui/ui.tex
+++ b/articles/ui/ui.tex
@@ -981,11 +981,11 @@ it has the following key advantages:
\item Sending deep links to fullfilment or offer pages to
other users has the expected behavior
of asking the other user to pay for the resource.
- \item Asynchronously POSTing coins from injected JavaScript costs
+ \item Asynchronously transmitting coins from injected JavaScript costs
one roundtrip, but does not interfer with navigation and allows
proper error handling.
\item The different pages of the merchant have clear
- delineations: the shopping pages conclude by proposing a contract, and
+ delineations: the shopping pages conclude by making an offer, and
the fulfillment page begins with processing an accepted contract. It is thus
possible for these pages to be managed by separate parties. The
control of the fulfillment page over the transmission of the payment