[taler-docs] branch master updated: convert from table @item to @cindex: ‘frontend’, ‘backend’

[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 eea3461  convert from table @item to @cindex: ‘frontend’, ‘backend’
eea3461 is described below

commit eea346162b9ba78c9f4b0f48b9c2b2bcda425ecd
Author: Thien-Thi Nguyen <ttn@gnuvola.org>
AuthorDate: Wed Nov 25 12:21:39 2020 -0500

    convert from table @item to @cindex: ‘frontend’, ‘backend’
---
 taler-merchant-api-tutorial.rst | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/taler-merchant-api-tutorial.rst b/taler-merchant-api-tutorial.rst
index 39f5ae5..33e0f8e 100644
--- a/taler-merchant-api-tutorial.rst
+++ b/taler-merchant-api-tutorial.rst
@@ -78,18 +78,18 @@ Architecture overview
 The Taler software stack for a merchant consists of the following main
 components:
 
--  frontend
+.. index:: frontend
 
-   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. This tutorial describes how to
    develop a Taler frontend.
 
--  backend
+.. index:: 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. For this tutorial, you
    will use a public sandbox backend. For production use, you must
    either set up your own backend or ask another person to do so for

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