gnunet-svn
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[taler-docs] branch master updated (5efd154 -> 00c31d1)


From: gnunet
Subject: [taler-docs] branch master updated (5efd154 -> 00c31d1)
Date: Thu, 27 May 2021 09:18:08 +0200

This is an automated email from the git hooks/post-receive script.

ttn pushed a change to branch master
in repository docs.

    from 5efd154  add details for unfunded
     new c27578b  fix typo: s/thats/that's/
     new 00c31d1  s/advertised/advertized/

The 2 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails.  The revisions
listed as "add" were already present in the repository and have only
been added to this reference.


Summary of changes:
 design-documents/021-exchange-key-continuity.rst | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/design-documents/021-exchange-key-continuity.rst 
b/design-documents/021-exchange-key-continuity.rst
index 05d438b..e09b6fe 100644
--- a/design-documents/021-exchange-key-continuity.rst
+++ b/design-documents/021-exchange-key-continuity.rst
@@ -25,7 +25,7 @@ an exchange, the trust record must always explicitly mention
 a base URL and a master public key.
 
 An exchange **should** have a single, canonical base URL.
-However, an exchange thats reachable over different base URLs
+However, an exchange that's reachable over different base URLs
 should still be handled gracefully.
 
 Wallet
@@ -36,7 +36,7 @@ Wallets do not support changing the base URL of an exchange.
 
 A ``/keys`` response with an unknown exchange master public key is only
 accepted if the exchange is audited by a trusted auditor or the wallet
-has an exchange trust record with the advertised master public key.
+has an exchange trust record with the advertized master public key.
 
 Denomination records explicitly store which master public key
 signed them.

-- 
To stop receiving notification emails like this one, please contact
gnunet@gnunet.org.



reply via email to

[Prev in Thread] Current Thread [Next in Thread]