taler-docs

Documentation for GNU Taler components, APIs and protocols
Log | Files | Refs | README | LICENSE

commit 13b0747160a67ac2f54e06249143f1a83f8e9c75
parent 4888588e126b1e3686d83b934600907644d7533e
Author: Thien-Thi Nguyen <ttn@gnuvola.org>
Date:   Fri, 19 Mar 2021 04:37:49 -0400

fix typo: s/from/form/

Diffstat:
Mcore/api-sync.rst | 2+-
1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/core/api-sync.rst b/core/api-sync.rst @@ -25,7 +25,7 @@ The backup and synchronization service uses an EdDSA key to identify the "account" of the user. The key is Crockford Base32-encoded in the URI to access the data and used to sign requests as well as to encrypt the contents (see below). These signatures are -provided in detached from as HTTP headers. +provided in detached form as HTTP headers. Once the user activates backup or synchronization, the client should display the key as a QR code as well as in text format together