|author||Christian Grothoff <email@example.com>||2020-10-25 23:00:14 +0100|
|committer||Christian Grothoff <firstname.lastname@example.org>||2020-10-25 23:00:14 +0100|
Diffstat (limited to 'design-documents/fees.rst')
1 files changed, 2 insertions, 2 deletions
diff --git a/design-documents/fees.rst b/design-documents/fees.rst
index 96459423..3dabd0bb 100644
@@ -48,7 +48,7 @@ cost for the user and and (2) restrictions on denomination/fee structures.
Thus the metrics should still allow some degree of variability between
-We make the assumption that wallet always perfer operations with better
+We make the assumption that wallet always prefer operations with better
privacy. For example, a single coin should only be used for at most one
spend operation and at most one refresh operation.
@@ -109,7 +109,7 @@ Drawbacks
* The approach does not work well in some special-purpose deployments,
- where the coin structure is taylored to the products of merchants,
+ where the coin structure is tailored to the products of merchants,
and refreshing would never even happen.
* The approach also does not consider more "creative" fee structures,