mint->exchange renaming

1 files changed, 13 insertions, 13 deletions

diff --git a/api-merchant.rst b/api-merchant.rst
index 72b7592e..bcaf38eb 100644
--- a/api-merchant.rst
+++ b/api-merchant.rst
@@ -57,7 +57,7 @@ The contract must have the following structure:
 
     interface Contract {
       // Total price for the transaction.
-      // The mint will subtract deposit fees from that amount
+      // The exchange will subtract deposit fees from that amount
       // before transfering it to the merchant.
       amount: Amount;
 
@@ -104,18 +104,18 @@ The contract must have the following structure:
       // The hash of the merchant's wire details.
       H_wire: HashCode;
 
-      // Any mints audited by these auditors are accepted by the merchant.
+      // Any exchanges audited by these auditors are accepted by the merchant.
       auditors: Auditor[];
 
-      // Mints that the merchant accepts even if it does not accept any auditors that audit them.
-      mints: Mint[];
+      // Exchanges that the merchant accepts even if it does not accept any auditors that audit them.
+      exchanges: Exchange[];
 
       // Map from label to a `Location`_.
       // The label strings must not contain a colon (`:`).
       locations: { [label: string]: Location>;
     }
 
-  The wallet must select a mint that either the mechant accepts directly by listing it in the mints arry, or for which the merchant accepts an auditor that audits that mint by listing it in the auditors array.
+  The wallet must select a exchange that either the mechant accepts directly by listing it in the exchanges arry, or for which the merchant accepts an auditor that audits that exchange by listing it in the auditors array.
 
   The `product` object describes the product being purchased from the merchant. It has the following structure:
 
@@ -193,11 +193,11 @@ The contract must have the following structure:
 
   .. code-block:: ts
 
-    interface Mint {
-      // the mint's base URL
+    interface Exchange {
+      // the exchange's base URL
       url: string;
 
-      // master public key of the mint
+      // master public key of the exchange
       master_pub: EddsaPublicKey;
     }
 
@@ -207,7 +207,7 @@ The contract must have the following structure:
 When the contract is signed by the merchant or the wallet, the
 signature is made over the hash of the JSON text, as the contract may
 be confidential between merchant and customer and should not be
-exposed to the mint.  The hashcode is generated by hashing the
+exposed to the exchange.  The hashcode is generated by hashing the
 encoding of the contract's JSON obtained by using the flags
 ``JSON_COMPACT | JSON_PRESERVE_ORDER``, as described in the `libjansson
 documentation
@@ -264,7 +264,7 @@ merchant's offer.
   :<json base32 merchant_sig: signature by the merchant over the contract, must match signed data of purpose TALER_SIGNATURE_MERCHANT_CONTRACT
   :<json date timestamp: a timestamp of this deposit permission. It equals just the contract's timestamp
   :<json date refund_deadline: same value held in the contract's `refund` field
-  :<json string mint: the chosen mint's base URL
+  :<json string exchange: the chosen exchange's base URL
   :<json array coins: the coins used to sign the contract
 
   For each coin, the array contains the following information:
@@ -272,8 +272,8 @@ merchant's offer.
   :<json amount f: the :ref:`amount <Amount>` this coin is paying, including this coin's deposit fee
   :<json base32 coin_pub: the coin's public key
   :<json base32 denom_pub: the denomination's (RSA public) key
-  :<json base32 ub_sig: the mint's signature over this coin's public key
-  :<json base32 coin_sig: the signature made by the coin's private key on a `struct TALER_DepositRequestPS`. See the :ref:`dedicated section <Signatures>` on the mint's specifications.
+  :<json base32 ub_sig: the exchange's signature over this coin's public key
+  :<json base32 coin_sig: the signature made by the coin's private key on a `struct TALER_DepositRequestPS`. See the :ref:`dedicated section <Signatures>` on the exchange's specifications.
 
   **Success Response:**
 
@@ -281,7 +281,7 @@ merchant's offer.
 
   **Failure Responses:**
 
-  The error codes and data sent to the wallet are a mere copy of those gotten from the mint when attempting to pay. The section about :ref:`deposit <deposit>` explains them in detail.
+  The error codes and data sent to the wallet are a mere copy of those gotten from the exchange when attempting to pay. The section about :ref:`deposit <deposit>` explains them in detail.
 
 
 .. http:post:: $exec_url