[taler-docs] branch master updated (7689f72a -> cf5724ca)

[Admin]

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

dold pushed a change to branch master
in repository taler-docs.

    from 7689f72a -rst formatting
     new cb136d04 -rst formatting
     new cf5724ca -dce

The 2 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails.  The revisions
listed as "add" were already present in the repository and have only
been added to this reference.


Summary of changes:
 design-documents/064-kyc-operation-algo.rst | 35 ++++++++++++++---------------
 1 file changed, 17 insertions(+), 18 deletions(-)

diff --git a/design-documents/064-kyc-operation-algo.rst 
b/design-documents/064-kyc-operation-algo.rst
index ee7eb878..7f66b299 100644
--- a/design-documents/064-kyc-operation-algo.rst
+++ b/design-documents/064-kyc-operation-algo.rst
@@ -24,43 +24,42 @@ Requirements
 Proposed Solution
 =================
 
-Steps for processing operation of type `op` and amount `amt`:
+Steps for processing operation of type ``op`` and amount ``amt``:
 
-0. Initialize `last_check_success := null`, `last_op_attempt := null`, 
`last_rule_gen := null`
+0. Initialize ``last_op_attempt := null``, ``last_rule_gen := null``
   
-1. Check if a zero limit for `op` is applicable.
+1. Check if a zero limit for ``op`` is applicable.
 
-   * If the zero limit blocks `op`, proceed with step 3.
+   * If the zero limit blocks ``op``, proceed with step 3.
    * Proceed with step 2.
 
-2. Attempt to make a request for `op` at the exchange. Set `last_op_attempt` to
+2. Attempt to make a request for ``op`` at the exchange. Set 
``last_op_attempt`` to
    the current time.
 
    * If the request succeeds, *halt*.
-   * If `last_rule_gen` is not `null` (Note 2), proceed with step 4.
+   * If ``last_rule_gen`` is not ``null`` (Note 2), proceed with step 4.
 
    * Proceed with step 3.
 
-3. Request the `/kyc-check/...` endpoint applicable for `op` (no long-polling!)
+3. Request the ``/kyc-check/...`` endpoint applicable for ``op`` (no 
long-polling!)
 
-   * If the request returns `204 No Content`, proceed with step 2.
-   * If the request returns `200 Ok` or a `202 Accepted`:
+   * If the request returns ``204 No Content``, proceed with step 2.
+   * If the request returns ``200 Ok`` or a ``202 Accepted``:
      
-     * Set `last_rule_gen := response.rule_gen`
-     * If the exposed limits do not deny `op`, set `last_check_success := 
now()` and proceed with step 2.
+     * Set ``last_rule_gen := response.rule_gen``
+     * If the exposed limits do not deny ``op``, proceed with step 2.
 
    * Proceed with the next step 4.
 
-4. Request the `/kyc-check/...` endpoint applicable for `op`
-   with long-polling for `min_rule` set to `last_rule_gen`.
+4. Request the ``/kyc-check/...`` endpoint applicable for ``op``
+   with long-polling for ``min_rule`` set to ``last_rule_gen``.
 
-   * If the request returns `200 Ok` or a `202 Accepted`:
+   * If the request returns ``200 Ok`` or a ``202 Accepted``:
 
-     * Set `last_rule_gen := response.rule_gen`
-     * If the exposed limits
-       do not deny `op`, set `last_check_success := now()` and proceed with 
step 2.
+     * Set ``last_rule_gen := response.rule_gen``
+     * If the exposed limits do not deny ``op``, proceed with step 2.
        
-   * If if the `last_op_attempt` is `null` or is more than 10 minutes in the 
past,
+   * If if the ``last_op_attempt`` is ``null`` or is more than 10 minutes in 
the past,
      proceed with step 2. (See Note 1)
    * Proceed with step 4.
 

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