taler-docs

commit 2c6ecca28a6ee3139f858f3f3f6966b76f25d6ac
parent 3173ec90f4a491302e324a6851fb4f36f4a11366
Author: Christian Grothoff <grothoff@gnunet.org>
Date:   Mon, 29 Nov 2021 18:03:16 +0100

-fix typos

Diffstat:
M
design-documents/024-age-restriction.rst
 | 
6
+++---
M
design-documents/025-withdraw-from-wallet.rst
 | 
2
+-

2 files changed, 4 insertions(+), 4 deletions(-)
diff --git 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.
    
 
 
diff --git a/design-documents/025-withdraw-from-wallet.rst b/design-documents/025-withdraw-from-wallet.rst
@@ -62,7 +62,7 @@ Alternatives
 
 * exchange field first has been discussed, but the exchange list its only showing the 
   current currency exchanges, the user need to switch the currency first. Adding a 
-  new exchange sould be done in a different context that can be accessed using the
+  new exchange should be done in a different context that can be accessed using the
   ``add exchange`` link