[taler-marketing] branch master updated: typos

[gnunet]

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

grothoff pushed a commit to branch master
in repository marketing.

The following commit(s) were added to refs/heads/master by this push:
     new f31da65  typos
f31da65 is described below

commit f31da65233046be2c61a6730937f6a314c20d421
Author: Christian Grothoff <christian@grothoff.org>
AuthorDate: Mon Dec 28 10:37:54 2020 +0100

    typos
---
 presentations/bank/bank.tex | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/presentations/bank/bank.tex b/presentations/bank/bank.tex
index 9fb8be0..7966a18 100644
--- a/presentations/bank/bank.tex
+++ b/presentations/bank/bank.tex
@@ -365,7 +365,7 @@ Both exchange and auditor use offline keys.
 \begin{frame}{Online keys}
 The exchange needs RSA and EdDSA keys to be available for online signing.
 \begin{itemize}
-\item Knowledge of these private keys will allow and adversary to
+\item Knowledge of these private keys will allow an adversary to
       mint digital cash, possibly resulting in huge financial losses
       (eventually, this will be detected by the auditor, but only
        after some financial losses have been irrevocably incurred).
@@ -418,7 +418,7 @@ The exchange needs the database to detect double spending.
 
 \begin{frame}{taler-exchange-wirewatch}
 {\tt taler-exchange-wirewatch} needs credentials to access data about
-incoming via transfers from the Nexus.
+incoming wire transfers from the Nexus.
 \begin{itemize}
 \item This tool should run as a separate UID and GID (from
       {\tt taler-exchange-httpd}).
@@ -560,7 +560,7 @@ Technical tasks in Beta phase:
   \item Develop customer support procedures
   \item Security audit of operational security
   \item Integrate system monitoring (load, disk capacity, etc.)
-  \item Verify deployment is {\bf reproducably deterministic}
+  \item Verify deployment is {\bf reproducibly deterministic}
   \item Experiment with scale-out options:
   \begin{itemize}
   \item multiple Postgres backends (sharding)

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