diff options
Diffstat (limited to 'design-documents/024-age-restriction.rst')
| -rw-r--r-- | design-documents/024-age-restriction.rst | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/design-documents/024-age-restriction.rst b/design-documents/024-age-restriction.rst index 7c6c251c..884ab275 100644 --- a/design-documents/024-age-restriction.rst +++ b/design-documents/024-age-restriction.rst @@ -339,7 +339,7 @@ Refresh - reveal phase During the reveal phase -- that is upon POST to ``/refreshes/$RCH/reveal`` -- the client has to provide the original age commitment of the old coin (i.e. the vector of public keys), iff the corresponding denomination had support for age -restriction. The size of the vector ist defined by the Exchange implicetly as +restriction. The size of the vector is defined by the Exchange implicetly as the amount of age groups defined in the field ``.age_groups`` of the ``ExtensionAgeRestriction``. @@ -351,7 +351,7 @@ the amount of age groups defined in the field ``.age_groups`` of the // Iff the corresponding denomination has support for age restriction, // the client MUST provide the original age commitment, i.e. the vector // of public keys. - // The size of the vector ist defined by the Exchange implicetly as the + // The size of the vector is defined by the Exchange implicetly as the // amount of age groups defined in the field ``.age_groups`` of the // ``ExtensionAgeRestriction``. old_age_commitment?: EddsaPublicKey[]; @@ -498,7 +498,7 @@ The merchant can now verify **Note**: This applies only to coins for denominations that have support for age restriction. Denominations *without* support for age restriction *always* -fullfill any minimum age requirement. +satisfy any minimum age requirement. |