summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorThien-Thi Nguyen <ttn@gnuvola.org>2020-11-24 20:23:42 -0500
committerThien-Thi Nguyen <ttn@gnuvola.org>2020-11-24 20:23:42 -0500
commit483b8bf659ec8bc714446fea448fa774909a327b (patch)
tree8821ad0d8299d911755ca35468939eeca4bf7573
parent39bc96b0bac4cc3291bda81d78a2a5f437b5c2da (diff)
downloaddocs-483b8bf659ec8bc714446fea448fa774909a327b.tar.gz
docs-483b8bf659ec8bc714446fea448fa774909a327b.tar.bz2
docs-483b8bf659ec8bc714446fea448fa774909a327b.zip
delete unfinished sentence fragment
-rw-r--r--taler-merchant-api-tutorial.rst3
1 files changed, 1 insertions, 2 deletions
diff --git a/taler-merchant-api-tutorial.rst b/taler-merchant-api-tutorial.rst
index 208144b..c016508 100644
--- a/taler-merchant-api-tutorial.rst
+++ b/taler-merchant-api-tutorial.rst
@@ -271,8 +271,7 @@ Given the order ID, the status of a payment can be checked with the
by the customer, ``/private/orders/$ORDER_ID`` will give the frontend a URL
(under the name ``payment_redirect_url``) that will trigger the customer’s
wallet to execute the payment. This is basically the
-``https://example.com/orders/$ORDER_ID/`` URL we discussed above. Note
-that
+``https://example.com/orders/$ORDER_ID/`` URL we discussed above.
Note that the best way to obtain the ``payment_redirect_url`` is to check the
status of the payment, even if you know that the user did not pay yet. There