gnunet-svn
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[taler-docs] branch master updated: make AML setup section more prominen


From: gnunet
Subject: [taler-docs] branch master updated: make AML setup section more prominent in exchange manual
Date: Fri, 17 Nov 2023 10:07:13 +0100

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

grothoff pushed a commit to branch master
in repository docs.

The following commit(s) were added to refs/heads/master by this push:
     new 28619609 make AML setup section more prominent in exchange manual
28619609 is described below

commit 28619609a0b46f0729c31f7fdeef14289e0fb0d6
Author: Christian Grothoff <christian@grothoff.org>
AuthorDate: Fri Nov 17 10:07:09 2023 +0100

    make AML setup section more prominent in exchange manual
---
 taler-exchange-manual.rst | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/taler-exchange-manual.rst b/taler-exchange-manual.rst
index d2ff8931..9033f94d 100644
--- a/taler-exchange-manual.rst
+++ b/taler-exchange-manual.rst
@@ -1930,7 +1930,7 @@ of ``taler-exchange-offline``.
    operation.
 
 AML Configuration
------------------
+=================
 
 The AML configuration steps are used to add or remove keys of exchange
 operator staff that are responsible for anti-money laundering (AML)
@@ -1941,7 +1941,7 @@ request additional KYC data from the consumer and can 
change the threshold
 amount above which a further AML review is triggered.
 
 AML Officer Setup
-^^^^^^^^^^^^^^^^^
+-----------------
 
 To begin the AML setup, AML staff should launch the GNU Taler
 exchange AML SPA Web interface. (FIXME-Sebastian: how?). The
@@ -1976,7 +1976,7 @@ Access rights can be revoked at any time using:
 
 
 AML Triggers
-^^^^^^^^^^^^
+------------
 
 AML decision processes are automatically triggered under certain configurable
 conditions.  The primary condition that *must* be configured is the

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



reply via email to

[Prev in Thread] Current Thread [Next in Thread]