[taler-docs] branch master updated: -fix typos

[gnunet]

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

grothoff pushed a commit to branch master
in repository docs.

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

commit 95409b94e83e5e7a72a28d9e150490497d196c84
Author: Christian Grothoff <christian@grothoff.org>
AuthorDate: Sat Jun 25 21:44:06 2022 +0200

    -fix typos
---
 design-documents/026-refund-fees.rst     |  4 ++--
 design-documents/028-proof-of-escrow.rst | 12 ++++++------
 design-documents/_svgs/escrow-flow.svg   |  2 +-
 libeufin/nexus-tutorial.rst              |  6 +++---
 manpages/libeufin-nexus.1.rst            |  2 +-
 taler-developer-manual.rst               |  2 +-
 6 files changed, 14 insertions(+), 14 deletions(-)

diff --git a/design-documents/026-refund-fees.rst 
b/design-documents/026-refund-fees.rst
index f65da4a..b460b43 100644
--- a/design-documents/026-refund-fees.rst
+++ b/design-documents/026-refund-fees.rst
@@ -15,7 +15,7 @@ When a user receives a refund, we have to decide what happens 
to the deposit
 fee that was originally paid on the associated deposit.  Originally, we said
 that the deposit fee is waived when any refund happens.  However, if the
 refund fee is zero and the deposit fee is non-zero, this results in a
-problematic scenario where merchants issue miniscule refunds that primarily
+problematic scenario where merchants issue minuscule refunds that primarily
 enable customers to effectively obtain the deposit fee.
 
 
@@ -25,7 +25,7 @@ Requirements
   * If the refund and refresh fees are zero, it should be possible for
     consumers to get 100% of their digital cash back on refunds.
   * This should not result in a problematic situation where merchants
-    conspire with consumers and issue miniscule refunds to allow consumers
+    conspire with consumers and issue minuscule refunds to allow consumers
     to work around deposit fees.
 
 Proposed Solution
diff --git a/design-documents/028-proof-of-escrow.rst 
b/design-documents/028-proof-of-escrow.rst
index 113d274..103b3a9 100644
--- a/design-documents/028-proof-of-escrow.rst
+++ b/design-documents/028-proof-of-escrow.rst
@@ -41,7 +41,7 @@ and until a valid order of release is provided.
 
 However, in the context of auctions, we want the parties to be able to verify
 the fairness of the participants.  For example, a seller of goods during an
-auction shall only be able to relase the money for the winning bidder and not
+auction shall only be able to release the money for the winning bidder and not
 for the others.  On the other hand, both, sellers and bidders should be able
 provide evidence to the exchange and auditor if the other party wasn't honest,
 f.e. if the winning bidder hasn't released the money.
@@ -74,11 +74,11 @@ We propose a the following endpoints
     ``$DEPOSIT_ID`` and the ``$ESCROW_ID``.
 
   The ``$DEPOSIT_ID`` is the SHA512 hash over all the coins.
-  
+
 
 - ``POST /escrows/$ESCROW_ID/claim/$DEPOSIT_ID``:  The owner of the private 
key for
-  ``$ESCROW_ID`` can claim the deposited coins.  It has to provide 
-  
+  ``$ESCROW_ID`` can claim the deposited coins.  It has to provide
+
   - the particular amount ``a'`` to be claimed
   - the list of coins to be claimed from the deposit
   - signatures over the SHA512 hash of the amount ``a'``, ``$ESCROW_ID`` and
@@ -91,10 +91,10 @@ The following diagram gives an overview of the flow:
 
 When the ``endtime`` of an escrow has arrived on the exchange, an amount ``a``
 of a deposit of amount ``b ≥ a`` can be claimed by the originator of the escrow
-account.  Only *one* succesfull claim can be made for a particular escrow
+account.  Only *one* successful claim can be made for a particular escrow
 account.  After a claim has been made, the remaining coins in the remaining
 deposits are released by the exchange.  If no claim is made within a specific
-time inverval after ``endtime``, all coins of *all* deposits are released.
+time interval after ``endtime``, all coins of *all* deposits are released.
 
 The ``GET /escrows/$ESCROWS_ID`` allows to depositors and auditors to confirm
 their deposit.  It also allows depositors to compare the list with their
diff --git a/design-documents/_svgs/escrow-flow.svg 
b/design-documents/_svgs/escrow-flow.svg
index cd0b2c9..6fc0a51 100644
--- a/design-documents/_svgs/escrow-flow.svg
+++ b/design-documents/_svgs/escrow-flow.svg
@@ -1 +1 @@
-<svg aria-labelledby="chart-title-graph-div chart-desc-graph-div" role="img" 
viewBox="-111 -10 1273 1070" style="max-width: 1273px;" height="1070" 
xmlns="http://www.w3.org/2000/svg"; width="100%" id="graph-div"><title 
id="chart-title-graph-div"></title><desc 
id="chart-desc-graph-div"></desc><style>#graph-div {font-family:"trebuchet 
ms",verdana,arial,sans-serif;font-size:16px;fill:#333;}#graph-div 
.error-icon{fill:#552222;}#graph-div 
.error-text{fill:#552222;stroke:#552222;}#graph-div .edg [...]
+<svg aria-labelledby="chart-title-graph-div chart-desc-graph-div" role="img" 
viewBox="-111 -10 1273 1070" style="max-width: 1273px;" height="1070" 
xmlns="http://www.w3.org/2000/svg"; width="100%" id="graph-div"><title 
id="chart-title-graph-div"></title><desc 
id="chart-desc-graph-div"></desc><style>#graph-div {font-family:"trebuchet 
ms",verdana,arial,sans-serif;font-size:16px;fill:#333;}#graph-div 
.error-icon{fill:#552222;}#graph-div 
.error-text{fill:#552222;stroke:#552222;}#graph-div .edg [...]
diff --git a/libeufin/nexus-tutorial.rst b/libeufin/nexus-tutorial.rst
index 1877e92..df2809f 100644
--- a/libeufin/nexus-tutorial.rst
+++ b/libeufin/nexus-tutorial.rst
@@ -190,13 +190,13 @@ The instructions below hook Nginx to the Sandbox:
 .. code-block:: console
 
   redirect / to /demobanks/default;
-  rewrite ^/$ https://$host/demobanks/default; 
+  rewrite ^/$ https://$host/demobanks/default;
   location / {
     proxy_set_header Host $host;
     proxy_set_header X-Forwarded-Host $host;
     proxy_set_header X-Forwarded-Proto "https";
     proxy_set_header X-Forwarded-Prefix "/";
-    proxy_pass http://localhost:5016/; 
+    proxy_pass http://localhost:5016/;
   }
 
 To reset the state of the sandbox, delete the database.
@@ -261,7 +261,7 @@ Check the balance of the user just created:
 
 With a user registered, we can now create an EBICS subscriber (identified by
 the partner ID and user ID) for the host.  This command requires admin
-priveleges, so ``LIBEUFIN_SANDBOX_USERNAME`` and ``LIBEUFIN_SANDBOX_PASSWORD``
+privileges, so ``LIBEUFIN_SANDBOX_USERNAME`` and ``LIBEUFIN_SANDBOX_PASSWORD``
 are reset back to ``admin`` and ``secret``, respectively.
 
 .. The plan is to replace the ‘sandbox ebicssubscriber list’ command
diff --git a/manpages/libeufin-nexus.1.rst b/manpages/libeufin-nexus.1.rst
index d1a0698..792c1de 100644
--- a/manpages/libeufin-nexus.1.rst
+++ b/manpages/libeufin-nexus.1.rst
@@ -6,7 +6,7 @@ libeufin-nexus(1)
    Name
    ====
 
-   **libeufin-nexus** - Sevice to interface to various bank access APIs
+   **libeufin-nexus** - Service to interface to various bank access APIs
 
 
 Synopsis
diff --git a/taler-developer-manual.rst b/taler-developer-manual.rst
index 5981bfe..c95d080 100644
--- a/taler-developer-manual.rst
+++ b/taler-developer-manual.rst
@@ -187,7 +187,7 @@ Thus, to update that file, you need to:
 
 - Commit the submodule change, and push it to the Taler exchange Git repo.
 
-A similiar procedure is required for other databases in GANA.
+A similar procedure is required for other databases in GANA.
 See file ``README`` in the various directories for specific instructions.
 
 

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