taler-docs

commit db395bbcd5c0f36c3ff2e9693b1c8c8f2708dac5
parent b8dc72bff1f1fb1a6ef3c7533ae7d21942e5a7eb
Author: Thien-Thi Nguyen <ttn@gnuvola.org>
Date:   Thu, 11 Feb 2021 19:29:36 -0500

mark up field names ‘refund’, ‘reason’

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

1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/taler-merchant-api-tutorial.rst b/taler-merchant-api-tutorial.rst
@@ -328,12 +328,12 @@ The frontend can instruct the merchant backend to authorize a refund by
 
 The refund request JSON object has only two fields:
 
--  refund: Amount to be refunded. If a previous refund was authorized
+-  ``refund``: Amount to be refunded. If a previous refund was authorized
    for the same order, the new amount must be higher, otherwise the
    operation has no effect. The value indicates the total amount to be
    refunded, *not* an increase in the refund.
 
--  reason: Human-readable justification for the refund. The reason is
+-  ``reason``: Human-readable justification for the refund. The reason is
    only used by the Back Office and is not exposed to the customer.
 
 If the request is successful (indicated by HTTP status code 200), the