[taler-docs] branch master updated: mark up ‘frontend’, ‘back-office’, ‘backend’, ‘DBMS’

[gnunet]

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 f47e509  mark up ‘frontend’, ‘back-office’, ‘backend’, ‘DBMS’
f47e509 is described below

commit f47e5097ff43fe87ee34b117239dce77302585bd
Author: Thien-Thi Nguyen <ttn@gnuvola.org>
AuthorDate: Tue Feb 23 23:21:07 2021 -0500

    mark up ‘frontend’, ‘back-office’, ‘backend’, ‘DBMS’
---
 taler-merchant-manual.rst | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/taler-merchant-manual.rst b/taler-merchant-manual.rst
index e27c656..fdaf138 100644
--- a/taler-merchant-manual.rst
+++ b/taler-merchant-manual.rst
@@ -71,24 +71,24 @@ special currency “KUDOS” and includes its own special bank.
 The Taler software stack for a merchant consists of four main
 components:
 
--  A frontend which interacts with the customer’s browser. The 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
    the order. This component is not included with Taler, but rather
    assumed to exist at the merchant.
    The :ref:`Merchant API Tutorial <merchant-api-tutorial>` gives an
    introduction for how to integrate Taler with Web shop frontends.
--  A back-office application that enables the shop operators to view
+-  A *back-office* application that enables the shop operators to view
    customer orders, match them to financial transfers, and possibly
    approve refunds if an order cannot be satisfied. This component is
    not included with Taler, but rather assumed to exist at the
    merchant. The :ref:`Merchant Backend API <merchant-api>` provides
    the API specification that should be reviewed to integrate such a
    back-office with the Taler backend.
--  A Taler-specific payment backend which makes it easy for the frontend
+-  A Taler-specific payment *backend* which makes it easy for the frontend
    to process financial transactions with Taler. This manual primarily
    describes how to install and configure this backend.
--  A DBMS which stores the transaction history for the Taler backend.
+-  A *DBMS* which stores the transaction history for the Taler backend.
    For now, the GNU Taler reference implementation only supports
    Postgres, but the code could be easily extended to support another
    DBMS.  Please review the Postgres documentation for details on

-- 
To stop receiving notification emails like this one, please contact
gnunet@gnunet.org.