keep naming consistent

1 files changed, 3 insertions, 3 deletions

diff --git a/taler-exchange-manual.rst b/taler-exchange-manual.rst
index 5c314aee..2d476711 100644
--- a/taler-exchange-manual.rst
+++ b/taler-exchange-manual.rst
@@ -85,7 +85,7 @@ Note that, given the technical burden (XML-based communications,
 additional cryptography, and a vast variety of standards) due to
 interact with banks, the exchange uses a intermediary system to talk
 to its bank.  Such intermediary system abstracts the native banking
-protocol by exposing the *Wire Gateway API*; this way, the exchange
+protocol by exposing the *Taler Wire Gateway API*; this way, the exchange
 can conduct its banking operations in a simplified and JSON-based style.
 
 When customers wire money to the escrow account, the bank notifies the
@@ -143,7 +143,7 @@ components:
    The ``taler-exchange-transfer`` tool is responsible for actually
    executing the aggregated wire transfers. It is the only process
    that needs to have the credentials to execute outgoing wire
-   transfers.  The tool uses the Taler Wire REST API to execute
+   transfers.  The tool uses the Taler Wire Gateway API to execute
    wire transfers.  This API is provided by the Taler Python Bank
    for stand-alone deployments (like those with ``KUDOS``) and
    by LibEuFin.  LibEuFin is an adapter which maps the Taler Wire
@@ -153,7 +153,7 @@ components:
    The ``taler-exchange-wirewatch`` tool is responsible for observing
    incoming wire transfers to the exchange. It needs to have the
    credentials to obtain a list of incoming wire transfers.
-   The tool also uses the Taler Wire REST API to observe such
+   The tool also uses the Taler Wire Gateway API to observe such
    incoming transfers.  It is possible that observing incoming and
    making outgoing wire transfers is done via different bank accounts
    and/or credentials.