[taler-docs] 01/10: add hyphen to ‘back-office’ (three instances)

[gnunet]

This is an automated email from the git hooks/post-receive script.

ttn pushed a commit to branch master
in repository docs.

commit 7282c11df233221011b40f72765c3e2ec2b46527
Author: Thien-Thi Nguyen <ttn@gnuvola.org>
AuthorDate: Mon Feb 8 02:49:43 2021 -0500

    add hyphen to ‘back-office’ (three instances)
---
 taler-merchant-manual.rst | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/taler-merchant-manual.rst b/taler-merchant-manual.rst
index 8e2c7fa..62c60f4 100644
--- a/taler-merchant-manual.rst
+++ b/taler-merchant-manual.rst
@@ -63,7 +63,7 @@ currencies such as USD or EUR. For testing purposes, Taler 
uses a
 special currency “KUDOS” and includes its own special bank.
 
 .. index:: frontend
-.. index:: back office
+.. index:: back-office
 .. index:: backend
 .. index:: DBMS
 .. index:: Postgres
@@ -78,13 +78,13 @@ components:
    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.
+   back-office with the Taler backend.
 -  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.

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