marketing

commit b0f7b807e8cd2b7cc5798069ddefcd8ab81a85ee
parent 0cdad531b12644a302188d85e92bbed5382eb2eb
Author: Florian Dold <florian.dold@gmail.com>
Date:   Sun, 26 May 2019 12:07:00 +0200

KB is upper-case

Diffstat:
M
sa/sa.tex
 | 
4
++--

1 file changed, 2 insertions(+), 2 deletions(-)
diff --git 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: