taler-docs

commit 52ae3b276b6527ab4e5d8a19982c5cd3fa5784e5
parent be0ccfe748731518508a4e2d890382f7b68e5a8d
Author: Christian Grothoff <christian@grothoff.org>
Date:   Mon, 30 Oct 2023 15:54:34 +0100

add links

Diffstat:
M
taler-user-guide.rst
 | 
11
++++++-----

1 file changed, 6 insertions(+), 5 deletions(-)
diff --git a/taler-user-guide.rst b/taler-user-guide.rst
@@ -294,9 +294,10 @@ you can specify which URL, which HTTP headers, which HTTP method and what HTTP
 body to send to the Webhook.  Webhooks are automatically retried (with
 increasing delays) when the target server returns a temporary error.
 
-Mustach templates are used when defining the contents of Webhooks.  Depending
-on the triggering event, the templates will be expanded with event-specific
-data.
+`Mustach templates <https://mustache.github.io/mustache.5.html>__` are used
+when defining the contents of Webhooks.  Depending on the triggering event,
+the templates will be expanded with event-specific data.
+
 
 Pay events
 ----------
@@ -304,7 +305,7 @@ Pay events
 For "pay" events, the backend will provide the following
 information to the Mustach templating engine:
 
-  * contract_terms: the contract terms of the paid order
+  * :ref:`contract_terms <contract-terms>`: the contract terms of the paid order
   * order_id: the ID of the order that received the refund
 
 
@@ -316,7 +317,7 @@ Mustach templating engine:
 
   * timestamp: time of the refund (in nanoseconds since 1970)
   * order_id: the ID of the order that received the refund
-  * contract_terms: the full JSON of the contract terms of the refunded order
+  * :ref:`contract_terms <contract-terms>`: the full JSON of the contract terms of the refunded order
   * refund_amout: the amount that was being refunded
   * reason: the reason entered by the merchant staff for granting the refund;
     be careful, you probably want to inform your staff if a webhook may expose