From cd4a79eaa1e745c50551bb20c08d9425885172b1 Mon Sep 17 00:00:00 2001
From: Florian Dold <florian.dold@gmail.com>
Date: Fri, 13 May 2016 14:03:24 +0200
Subject: address comment about undefined acronym

---
 articles/ui/ui.tex | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

(limited to 'articles/ui/ui.tex')

diff --git a/articles/ui/ui.tex b/articles/ui/ui.tex
index bb5466e51..9c63e2b5f 100644
--- a/articles/ui/ui.tex
+++ b/articles/ui/ui.tex
@@ -281,6 +281,7 @@ and to other currencies incurs substantial fees~\cite{BTCfees}.
 There is now an extreme diversity of Bitcoin-related payment
 technologies, but usability improvements are usually achieved by
 adding a ``trusted'' third party, and there have been many incidents
+% FIXME: citation for embezzlement
 where such parties then embezzled funds from their customers.  The
 classical Bitcoin payment workflow consisted of entering payment
 details into a peer-to-peer application.  The user would access his
@@ -445,7 +446,7 @@ that customers and merchants incur by using a particular exchange.
 \end{itemize}
 
 The specific protocol between wallet and merchant depends on the
-setting.  For a traditional store, an NFC protocol might be used
+setting.  For a traditional store, a near field communication (NFC) protocol might be used
 between a point-of-sale system and a mobile application.  In this
 paper, we focus on Web payments for an online shop.
 
-- 
cgit v1.2.3

