[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[GNUnet-SVN] [taler-marketing] branch master updated: KB is upper-case
From: |
gnunet |
Subject: |
[GNUnet-SVN] [taler-marketing] branch master updated: KB is upper-case |
Date: |
Sun, 26 May 2019 12:07:06 +0200 |
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 b0f7b80 KB is upper-case
b0f7b80 is described below
commit b0f7b807e8cd2b7cc5798069ddefcd8ab81a85ee
Author: Florian Dold <address@hidden>
AuthorDate: Sun May 26 12:07:00 2019 +0200
KB is upper-case
---
sa/sa.tex | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/sa/sa.tex b/sa/sa.tex
index 2e728bd..7a41522 100644
--- a/sa/sa.tex
+++ b/sa/sa.tex
@@ -51,8 +51,8 @@ money-laundering (AML) and know-your-customer (KYC) auditing
requirements.
Transactions with Taler execute in one network round-trip time. Taler is
economically viable for micro-payments (payments of 1 cent) as its design
minimizes requirements in terms of CPU time (typically less than 1 M cycles
-per transaction), bandwidth (typically 1-10 kb/transaction), and storage
-(again a few kb/transaction, with the ability to delete old data once legal
+per transaction), bandwidth (typically 1-10 KB/transaction), and storage
+(again a few KB/transaction, with the ability to delete old data once legal
data retention periods have expired).
The USPs of Taler are:
--
To stop receiving notification emails like this one, please contact
address@hidden
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [GNUnet-SVN] [taler-marketing] branch master updated: KB is upper-case,
gnunet <=