[taler-docs] 01/02: token instead of login

[gnunet]

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

sebasjm pushed a commit to branch master
in repository docs.

commit e9268f18c02a634d4dd564cff33ea6fccd676a03
Author: Sebastian <sebasjm@gmail.com>
AuthorDate: Fri Sep 8 11:10:43 2023 -0300

    token instead of login
---
 core/api-merchant.rst | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/core/api-merchant.rst b/core/api-merchant.rst
index 732a35b1..3239db23 100644
--- a/core/api-merchant.rst
+++ b/core/api-merchant.rst
@@ -107,7 +107,7 @@ Currently, the API supports two main authentication methods:
   header, where ``$TOKEN`` is a secret authentication token configured for the 
instance which must begin with the RFC 8959 prefix.
 
 Additionally, clients can send a **login token** which they may obtain from
-the ``/private/login`` endpoint.  Such a login token is valid only for a
+the ``/private/token`` endpoint.  Such a login token is valid only for a
 limited period of time and can be used by clients to avoid storing the
 long-term login secrets from an authentication method.
 

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