path: root/taler-merchant-api-tutorial.rst
diff options
authorThien-Thi Nguyen <>2020-11-24 20:35:50 -0500
committerThien-Thi Nguyen <>2020-11-24 20:35:50 -0500
commit7bb54b26f81074704f2637e6909e9b5fd88e7276 (patch)
treeb88d90a6c6f902e10de2950605ae9b7a0530bcd9 /taler-merchant-api-tutorial.rst
parentca225f997ce68401c33a074609ee03f0c149187f (diff)
add comma
Diffstat (limited to 'taler-merchant-api-tutorial.rst')
1 files changed, 1 insertions, 1 deletions
diff --git a/taler-merchant-api-tutorial.rst b/taler-merchant-api-tutorial.rst
index adf3f02..a721a5e 100644
--- a/taler-merchant-api-tutorial.rst
+++ b/taler-merchant-api-tutorial.rst
@@ -494,7 +494,7 @@ be paid for exactly the same product by each customer. Taler supports
this model by allowing the mechant to check whether the “payment
receipt” is available on the user’s current device. This prevents users
from easily sharing media access by transmitting a link to the
-fulfillment page. Of course sophisticated users could share payment
+fulfillment page. Of course, sophisticated users could share payment
receipts as well, but this is not as easy as sharing a link, and in this
case they are more likely to just share the media directly.