taler-docs

commit 483b8bf659ec8bc714446fea448fa774909a327b
parent 39bc96b0bac4cc3291bda81d78a2a5f437b5c2da
Author: Thien-Thi Nguyen <ttn@gnuvola.org>
Date:   Tue, 24 Nov 2020 20:23:42 -0500

delete unfinished sentence fragment

Diffstat:
M
taler-merchant-api-tutorial.rst
 | 
3
+--

1 file changed, 1 insertion(+), 2 deletions(-)
diff --git 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