use ‘.. note::’ syntax (two instances)

1 files changed, 13 insertions, 9 deletions

diff --git a/libeufin/int-deployment-gv.rst b/libeufin/int-deployment-gv.rst
index dc6f21ef..b3a12935 100644
--- a/libeufin/int-deployment-gv.rst
+++ b/libeufin/int-deployment-gv.rst
@@ -27,14 +27,16 @@ At this point, the services can be launched, and will be
 served at ``$hostname/$service``.  The following command
 will launch all the services and show what ``$service``
 can be:
-   
+
 .. code-block:: console
 
    $ python3 deployment/bin/WIP/taler-local launch
 
-Note: in this context, one reverse proxy gets launched
-along all the Taler services and will dispatch any request
-to ``$service`` to the respective Unix domain socket.
+.. note::
+
+   In this context, one reverse proxy gets launched
+   along all the Taler services and will dispatch any request
+   to ``$service`` to the respective Unix domain socket.
 
 Withdraw with Taler
 -------------------
@@ -43,17 +45,19 @@ The following command withdraws a fixed amount of 5 units of currency
 to the CLI wallet:
 
 .. code-block:: console
-   
+
    $ python3 deployment/bin/WIP/taler-local withdraw
 
 The requests will be addressed to the default Sandbox, unless
 ``--bank-host`` (and ``--bank-proto``) were given; see ``--help``
 for more information.
 
-Note: to test phone wallets, the option ``--with-qr-code``
-can be specified.  That will print a QR code on screen, and
-wait for the user's input before confirming the payment to
-the Exchange.
+.. note::
+
+   To test phone wallets, the option ``--with-qr-code``
+   can be specified.  That will print a QR code on screen, and
+   wait for the user's input before confirming the payment to
+   the Exchange.
 
 Taler Internal deployment
 -------------------------