taler-docs

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

commit 9aefe16af8607332779cd4dd257585c27bdd57d6
parent c652f968968a6040f400f9e8e34f65d745bff6ea
Author: Thien-Thi Nguyen <ttn@gnuvola.org>
Date:   Sat, 28 Nov 2020 00:20:30 -0500

diction: s/N bytes/N-byte/ (two instances)

The hypen and singular noun is used when the composed term is used as an
adjective (as in this case).

Diffstat:
Manastasis.rst | 4++--
1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/anastasis.rst b/anastasis.rst @@ -510,8 +510,8 @@ In the following, UUID is always defined and used according to `RFC 4122`_. Upload a new version of the customer's encrypted recovery document. While the document's structure is described in JSON below, the upload - should just be the bytestream of the raw data (i.e. 32 bytes nonce followed - by 16 bytes tag followed by the encrypted document). + should just be the bytestream of the raw data (i.e. 32-byte nonce followed + by 16-byte tag followed by the encrypted document). If request has been seen before, the server should do nothing, and otherwise store the new version. The body must begin with a nonce, an AES-GCM tag and continue with the ciphertext. The format is the same as specified for the response of the GET method. The