From 459e6d086e5d053b1a6a5028e84d94860dfb025c Mon Sep 17 00:00:00 2001 From: Christian Grothoff Date: Sun, 25 Oct 2020 23:00:14 +0100 Subject: fix typos --- design-documents/fees.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'design-documents/fees.rst') diff --git a/design-documents/fees.rst b/design-documents/fees.rst index 96459423..3dabd0bb 100644 --- a/design-documents/fees.rst +++ b/design-documents/fees.rst @@ -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 exchanges. -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, -- cgit v1.2.3