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/002-wallet-exchange-management.rst | 2 +- design-documents/003-tos-rendering.rst | 2 +- design-documents/fees.rst | 4 ++-- 3 files changed, 4 insertions(+), 4 deletions(-) diff --git a/design-documents/002-wallet-exchange-management.rst b/design-documents/002-wallet-exchange-management.rst index d70a799c..9d10045a 100644 --- a/design-documents/002-wallet-exchange-management.rst +++ b/design-documents/002-wallet-exchange-management.rst @@ -154,7 +154,7 @@ Response: // The "reasonable-ness" of the exchange's fees. feeStructureSummary: FeeStructureSummary | undefined; - // Detailled info for each individual denomination + // Detailed info for each individual denomination denominations: ExchangeDenomination[]; // Currency of the exchange. diff --git a/design-documents/003-tos-rendering.rst b/design-documents/003-tos-rendering.rst index 52d293c3..3011775c 100644 --- a/design-documents/003-tos-rendering.rst +++ b/design-documents/003-tos-rendering.rst @@ -34,7 +34,7 @@ Legal documents with mime type ``text/markdown`` **should** confirm to the When wallets render ``text/markdown`` legal documents, they **must** disable embedded HTML rendering. Wallets **may** style the markdown rendering to improve -usability. For example, they can make sections collabsible or add a nagivation side-bar +usability. For example, they can make sections collabsible or add a navigation side-bar on bigger screens. It is recommended that the ``text/markdown`` document is used as the "master 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