summaryrefslogtreecommitdiff
path: root/taler-merchant-api-tutorial.rst
diff options
context:
space:
mode:
authorThien-Thi Nguyen <ttn@gnuvola.org>2020-11-24 20:30:33 -0500
committerThien-Thi Nguyen <ttn@gnuvola.org>2020-11-24 20:30:33 -0500
commitca225f997ce68401c33a074609ee03f0c149187f (patch)
treefcc0c07ccff86516b64765177cf46561fd0b5bcf /taler-merchant-api-tutorial.rst
parent483b8bf659ec8bc714446fea448fa774909a327b (diff)
downloaddocs-ca225f997ce68401c33a074609ee03f0c149187f.tar.gz
docs-ca225f997ce68401c33a074609ee03f0c149187f.tar.bz2
docs-ca225f997ce68401c33a074609ee03f0c149187f.zip
mark up ‘taler://’
Diffstat (limited to 'taler-merchant-api-tutorial.rst')
-rw-r--r--taler-merchant-api-tutorial.rst2
1 files changed, 1 insertions, 1 deletions
diff --git a/taler-merchant-api-tutorial.rst b/taler-merchant-api-tutorial.rst
index c016508..adf3f02 100644
--- a/taler-merchant-api-tutorial.rst
+++ b/taler-merchant-api-tutorial.rst
@@ -380,7 +380,7 @@ may then want to read it on a different device, possibly one that
does not even have a Taler wallet installed.
Naturally, at this point the customer would at first still be prompted to pay
-for the article again. If the customer then opens the taler://-link in the
+for the article again. If the customer then opens the ``taler://`` link in the
wallet that did previously pay for the article (for example by scanning the QR
code on the desktop with the Android App), the wallet will claim the contract,
detect that the fulfillment URL is identical to one that it already has made a