taler-docs

commit 9983421472ca332e9a689ae53692c31e45e561dc
parent 7da757b4ef3b30989913bac97072bb07aa77e4b2
Author: Florian Dold <florian@dold.me>
Date:   Mon, 25 Apr 2022 23:55:20 +0200

age restriction: fix minimum age field name

Diffstat:
M
design-documents/024-age-restriction.rst
 | 
8
++++----

1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/design-documents/024-age-restriction.rst b/design-documents/024-age-restriction.rst
@@ -418,7 +418,7 @@ minimum age in response to order claim by the wallet, that is, a POST to
 ``[/instances/$INSTANCE]/orders/$ORDER_ID/claim``.
 
 The object ``ContractTerms`` is extended by an optional field
-``required_minimum_age`` that can be any integer greater than 0.  In reality
+``minimum_age`` that can be any integer greater than 0.  In reality
 this value will not be smaller than, say, 8, and not larger than, say, 21.
 
 .. ts:def:: ContractTerms
@@ -429,12 +429,12 @@ this value will not be smaller than, say, 8, and not larger than, say, 21.
    // If the order requires a minimum age greater than 0, this field is set
    // to the integer value of that age.  In reality this value will not be
    // smaller than, say, 8, and not larger than, say, 21.
-   required_minimum_age?: Integer;
+   minimum_age?: Integer;
 
    ...
    }
 
-By sending the contract term with the field ``required_minimum_age`` set to an
+By sending the contract term with the field ``minimum_age`` set to an
 non-zero integer value, the merchant implicetly signals that it understands the
 extension ``age_restriction`` for age restriction from the exchange.
 
@@ -443,7 +443,7 @@ Making the payment
 ------------------
 
 If the ``ContractTerms`` had a non-zero value in field
-``required_minimum_age``, the wallet has to provide evidence of that minimum
+``minimum_age``, the wallet has to provide evidence of that minimum
 age by
 
 #. *either* using coins which are of denominations that had *no* age support