taler-docs

commit 17bbb841d54fbcf2cfcb0d8b2abc0e7790a99983
parent b9684ec1de0d1af5bda91e7c074e63187a1ba0dc
Author: Martin Schanzenbach <schanzen@gnunet.org>
Date:   Mon, 16 Jun 2025 12:33:49 +0200

minor fix

Diffstat:
M
core/api-merchant.rst
 | 
2
+-

1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/core/api-merchant.rst b/core/api-merchant.rst
@@ -105,7 +105,7 @@ Currently, the API supports two main authentication methods:
 * ``token``: With this method, the client must provide a ``Authorization: Bearer $TOKEN``
   header, where ``$TOKEN`` is a secret authentication token configured for the instance.
   The format of ``$TOKEN`` is ``secret-token: $INSTANCE_PASSWORD``.
-  If the ``$INSTANCE_PASSWORD`` is lost, the administrator can set a token (including the ``secret-token: `` prefix!)
+  If the ``$INSTANCE_PASSWORD`` is lost, the administrator can set a token (including the ``secret-token:`` prefix!)
   for the default instance using the ``--auth`` command line option of the service,
   or by restarting the service by providing an environment variable called ``TALER_MERCHANT_TOKEN``.
   Alternatively, the ``taler-merchant-passwd`` command-line tool may be used to set or reset the password for any instance