summaryrefslogtreecommitdiff
path: root/core/api-exchange.rst
diff options
context:
space:
mode:
authorChristian Grothoff <christian@grothoff.org>2020-10-25 22:57:27 +0100
committerChristian Grothoff <christian@grothoff.org>2020-10-25 22:57:27 +0100
commit919b293070ac5ce443f68a25eacefeb3663aec0e (patch)
tree68a41d17b693f09374b62ccfc394cf0b12c7c092 /core/api-exchange.rst
parent6570cab515e073fad4b7bf8f5ada4bb4cff12788 (diff)
downloaddocs-919b293070ac5ce443f68a25eacefeb3663aec0e.tar.gz
docs-919b293070ac5ce443f68a25eacefeb3663aec0e.tar.bz2
docs-919b293070ac5ce443f68a25eacefeb3663aec0e.zip
fix typos
Diffstat (limited to 'core/api-exchange.rst')
-rw-r--r--core/api-exchange.rst12
1 files changed, 6 insertions, 6 deletions
diff --git a/core/api-exchange.rst b/core/api-exchange.rst
index 15547ed..af1c509 100644
--- a/core/api-exchange.rst
+++ b/core/api-exchange.rst
@@ -355,7 +355,7 @@ Withdrawal
This API is used by the wallet to obtain digital coins.
-When transfering money to the exchange such as via SEPA transfers, the exchange creates
+When transferring money to the exchange such as via SEPA transfers, the exchange creates
a *reserve*, which keeps the money from the customer. The customer must
specify an EdDSA reserve public key as part of the transfer, and can then
withdraw digital coins using the corresponding private key. All incoming and
@@ -524,7 +524,7 @@ exchange.
**Response:**
:status 200 OK:
- The request was succesful, and the response is a `WithdrawResponse`. Note that repeating exactly the same request
+ The request was successful, and the response is a `WithdrawResponse`. Note that repeating exactly the same request
will again yield the same response, so if the network goes down during the
transaction or before the client can commit the coin signature to disk, the
coin is not lost.
@@ -860,7 +860,7 @@ the API during normal operation.
:status 401 Unauthorized:
One of the signatures is invalid.
:status 200 OK:
- The request was succesful. The response body is `MeltResponse` in this case.
+ The request was successful. The response body is `MeltResponse` in this case.
:status 404:
the exchange does not recognize the denomination key as belonging to the exchange,
or it has expired
@@ -967,7 +967,7 @@ the API during normal operation.
.. http:post:: /refreshes/$RCH/reveal
- Reveal previously commited values to the exchange, except for the values
+ Reveal previously committed values to the exchange, except for the values
corresponding to the ``noreveal_index`` returned by the /coins/-melt step.
The $RCH is the hash over the refresh commitment from the /coins/-melt step
@@ -993,7 +993,7 @@ the API during normal operation.
The response body is a `RevealResponse`
:status 409 Conflict:
There is a problem between the original commitment and the revealed private
- keys. The returned information is proof of the missmatch, and therefore
+ keys. The returned information is proof of the mismatch, and therefore
rather verbose, as it includes most of the original /refresh/melt request,
but of course expected to be primarily used for diagnostics.
The response body is a `RevealConflictResponse`.
@@ -1132,7 +1132,7 @@ in using this API.
**Response:**
:status 200 OK:
- The request was succesful, and the response is a `RecoupConfirmation`.
+ The request was successful, and the response is a `RecoupConfirmation`.
Note that repeating exactly the same request
will again yield the same response, so if the network goes down during the
transaction or before the client can commit the coin signature to disk, the