gnunet-svn
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[taler-docs] branch master updated: diction: s/N bytes/N-byte/ (two inst


From: gnunet
Subject: [taler-docs] branch master updated: diction: s/N bytes/N-byte/ (two instances)
Date: Sat, 28 Nov 2020 06:21:36 +0100

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

ttn pushed a commit to branch master
in repository docs.

The following commit(s) were added to refs/heads/master by this push:
     new 9aefe16  diction: s/N bytes/N-byte/ (two instances)
9aefe16 is described below

commit 9aefe16af8607332779cd4dd257585c27bdd57d6
Author: Thien-Thi Nguyen <ttn@gnuvola.org>
AuthorDate: Sat Nov 28 00:20:30 2020 -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).
---
 anastasis.rst | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/anastasis.rst b/anastasis.rst
index e3203e4..6824738 100644
--- 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

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



reply via email to

[Prev in Thread] Current Thread [Next in Thread]