summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorThien-Thi Nguyen <ttn@gnuvola.org>2020-11-24 20:13:12 -0500
committerThien-Thi Nguyen <ttn@gnuvola.org>2020-11-24 20:13:12 -0500
commitacead6d4316a1937b44865c5617145b4be1516db (patch)
tree0000d659ecc1d1e9d402e8b623a4e59c44f79ea6
parent9202c59f1dc5aead6bdc4ade01ce1ad08af250d8 (diff)
downloaddocs-acead6d4316a1937b44865c5617145b4be1516db.tar.gz
docs-acead6d4316a1937b44865c5617145b4be1516db.tar.bz2
docs-acead6d4316a1937b44865c5617145b4be1516db.zip
add blank line between term and explanation for ‘frontend’, ‘backend’
-rw-r--r--taler-merchant-api-tutorial.rst2
1 files changed, 2 insertions, 0 deletions
diff --git a/taler-merchant-api-tutorial.rst b/taler-merchant-api-tutorial.rst
index 1449c9f..fccac51 100644
--- a/taler-merchant-api-tutorial.rst
+++ b/taler-merchant-api-tutorial.rst
@@ -79,6 +79,7 @@ The Taler software stack for a merchant consists of the following main
components:
- frontend
+
A frontend which interacts with the customer’s browser. The frontend
enables the customer to build a shopping cart and place an order.
Upon payment, it triggers the respective business logic to satisfy
@@ -87,6 +88,7 @@ components:
develop a Taler frontend.
- backend
+
A Taler-specific payment backend which makes it easy for the frontend
to process financial transactions with Taler. For this tutorial, you
will use a public sandbox backend. For production use, you must