[taler-docs] branch master updated (0c64cd9 -> 246d114)

[gnunet]

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

ttn pushed a change to branch master
in repository docs.

    from 0c64cd9  add period at end of sentence (two instances)
     new e98a781  add article "a"
     new 90d84c6  fix typo: s/setup/set up/
     new b19c29a  add article "the"
     new 1c9146d  mark up ‘payto://’ and ‘?’
     new df3a1b4  mark up ‘x-taler-bank’
     new 35ecfaa  change markup of ‘x-taler-bank’ from " to ``
     new c0594fa  fix typo: s/covert/convert/
     new 246d114  mark up ‘payto://’

The 8 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails.  The revisions
listed as "add" were already present in the repository and have only
been added to this reference.


Summary of changes:
 core/wireformats.rst | 16 ++++++++--------
 1 file changed, 8 insertions(+), 8 deletions(-)

diff --git a/core/wireformats.rst b/core/wireformats.rst
index 2f1c964..d4ffe5f 100644
--- a/core/wireformats.rst
+++ b/core/wireformats.rst
@@ -8,7 +8,7 @@ account upon a successful deposit (see :ref:`deposit request 
<deposit>`).  The
 merchant has to include the necessary information for the exchange to initiate 
the
 wire transfer.
 
-The information required for wire transfer depends on the method of wire 
transfer
+The information required for a wire transfer depends on the method of wire 
transfer
 used.  Since the wire transfers differ for each region, we document here the
 ones currently supported by the exchange.
 
@@ -16,8 +16,8 @@ X-TALER-BANK
 ------------
 
 The ``x-taler-bank`` wire format is used for testing and for integration with 
Taler's
-simple "bank" system which in the future might be useful to setup a bank
-for a local / regional currency or accounting system.  Using ``x-taler-bank``
+simple "bank" system which in the future might be useful to set up a bank
+for a local / regional currency or accounting system.  Using the 
``x-taler-bank``
 wire method in combination with the Taler's bank, it is thus possible to
 fully test the Taler system without using "real" currencies.  The URL
 format for ``x-taler-bank`` is simple, in that it only specifies an account
@@ -28,16 +28,16 @@ number and the origin (domain and optionally a port) of the 
bank:
   payto://x-taler-bank/BANK_URI/ACCOUNT_IDENTIFIER
 
 The account identifier given must be a non-empty alphanumeric ASCII string.  
As with
-any payto://-URI, additional fields may be present (after a ?), but
+any ``payto://`` URI, additional fields may be present (after a ``?``), but
 are not required.  The ``BANK_URI`` may include a port number. If none is
 given, ``https`` over port 443 is assumed.  If a port number is
 given, ``http`` over the given port is to be used.  Note that this
-means that you cannot run an x-taler-bank over ``https`` on a
+means that you cannot run an ``x-taler-bank`` over ``https`` on a
 non-canonical port.
 
 Note that a particular exchange is usually only supporting one particular bank
 with the ``x-taler-bank`` wire format, so it is not possible for a merchant 
with
-an account at a different bank to use "x-taler-bank" to transfer funds across
+an account at a different bank to use ``x-taler-bank`` to transfer funds across
 banks. After all, this is for testing and not for real banking.
 
 SEPA
@@ -48,11 +48,11 @@ payments.  Since its adoption in 2012, all of the banks in 
the Eurozone and some
 banks in other countries adhere to this standard for sending and receiving
 payments.  Note that the currency of the transfer will (currently) always be 
``EUR``.  In
 case the receiving account is in a currency other than ``EUR``, the receiving 
bank
-may covert the amount into that currency; currency exchange charges may be
+may convert the amount into that currency; currency exchange charges may be
 levied by the receiving bank.
 
 For the merchant to receive deposits through SEPA, the deposit request must
-follow the payto:// specification for SEPA:
+follow the ``payto://`` specification for SEPA:
 
 .. code-block:: none
 

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