summaryrefslogtreecommitdiff
path: root/doc/system/taler
diff options
context:
space:
mode:
authorChristian Grothoff <christian@grothoff.org>2021-04-23 23:53:52 +0200
committerChristian Grothoff <christian@grothoff.org>2021-04-23 23:53:52 +0200
commit5106a09c9fff809ff502a267759f5f72401c1065 (patch)
tree9caa2afa69427a15ae0119958228716aee08cd0e /doc/system/taler
parenta140c114d3b3109d7f288be3c21164f490348d44 (diff)
downloadexchange-5106a09c9fff809ff502a267759f5f72401c1065.tar.gz
exchange-5106a09c9fff809ff502a267759f5f72401c1065.tar.bz2
exchange-5106a09c9fff809ff502a267759f5f72401c1065.zip
fix more typos
Diffstat (limited to 'doc/system/taler')
-rw-r--r--doc/system/taler/implementation.tex2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/system/taler/implementation.tex b/doc/system/taler/implementation.tex
index b49763c65..9d7cb9a9e 100644
--- a/doc/system/taler/implementation.tex
+++ b/doc/system/taler/implementation.tex
@@ -2267,7 +2267,7 @@ exchange. The highest rate of spends was $780$ per second. Thus, the
theoretically achievable transaction rate on our single test machine (and a
dedicated machine for the database) would be $780 \cdot 3 / 10 = 234$ transactions
per second under the relatively pessimistic assumptions we made about what
-consitutes a transaction.
+constitutes a transaction.
If a GNU Taler deployment was used to pay for items of fixed price (e.g., online
news articles), the overhead of multiple coins and refresh operations (which