[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[taler-docs] branch master updated: add blank line between term and expl
From: |
gnunet |
Subject: |
[taler-docs] branch master updated: add blank line between term and explanation for ‘frontend’, ‘backend’ |
Date: |
Wed, 25 Nov 2020 02:14:36 +0100 |
This is an automated email from the git hooks/post-receive script.
ttn pushed a commit to branch master
in repository docs.
The following commit(s) were added to refs/heads/master by this push:
new acead6d add blank line between term and explanation for ‘frontend’,
‘backend’
acead6d is described below
commit acead6d4316a1937b44865c5617145b4be1516db
Author: Thien-Thi Nguyen <ttn@gnuvola.org>
AuthorDate: Tue Nov 24 20:13:12 2020 -0500
add blank line between term and explanation for ‘frontend’, ‘backend’
---
taler-merchant-api-tutorial.rst | 2 ++
1 file changed, 2 insertions(+)
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
--
To stop receiving notification emails like this one, please contact
gnunet@gnunet.org.
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [taler-docs] branch master updated: add blank line between term and explanation for ‘frontend’, ‘backend’,
gnunet <=