gnunet-svn
[Top][All Lists]
Advanced

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

[taler-marketing] branch master updated: improve wording


From: gnunet
Subject: [taler-marketing] branch master updated: improve wording
Date: Mon, 22 Mar 2021 14:22:08 +0100

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

dold pushed a commit to branch master
in repository marketing.

The following commit(s) were added to refs/heads/master by this push:
     new 84d397b  improve wording
84d397b is described below

commit 84d397b31f9888c10c5b28addf863f0da4c0eb19
Author: Florian Dold <florian@dold.me>
AuthorDate: Mon Mar 22 14:22:05 2021 +0100

    improve wording
---
 2021-offline/offline.tex | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/2021-offline/offline.tex b/2021-offline/offline.tex
index 6dc4ee1..65989cd 100644
--- a/2021-offline/offline.tex
+++ b/2021-offline/offline.tex
@@ -189,7 +189,7 @@ is online-only.
 \section{Conclusion}
 
 While in some situations, offline payments might be a desireable requirement,
-adding offline capabilities to a payment system comes with substantial risks.
+adding offline payment systems have inherent and severe risks.
 The exposure to these risks should be limited by only resorting to an offline
 fallback mode of the payment system when actually required.
 
@@ -199,7 +199,7 @@ exposing the payee to counterparty risk.  In a system based 
on restricted
 hardware elements, the payee would bear the risk in case of a compromised
 hardware system.  In a system based on identifying offline double spenders /
 cheaters, the payee would bear the risk in case the offline double spender /
-cheater can't be found and held accountable.
+cheater cannot be found and held accountable.
 
 Preliminary results from a survey done by the ECB have shown that privacy is
 regarded as one of the the most important feature by participants among

-- 
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]