[taler-docs] 27/94: change markup of ‘304’ from " to ``

[gnunet]

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

ttn pushed a commit to branch master
in repository docs.

commit 95af36b957800dd50e6e587711dcf9347ad9976d
Author: Thien-Thi Nguyen <ttn@gnuvola.org>
AuthorDate: Wed Apr 7 03:47:34 2021 -0400

    change markup of ‘304’ from " to ``
---
 anastasis.rst | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/anastasis.rst b/anastasis.rst
index 71bbaa6..f1efa2e 100644
--- a/anastasis.rst
+++ b/anastasis.rst
@@ -566,7 +566,7 @@ In the following, UUID is always defined and used according 
to `RFC 4122`_.
   The client SHOULD also set the ``Expect: 100-Continue`` header and wait for 
``100 continue``
   before uploading the body.  The server MUST
   use the Etag to check whether it already knows the encrypted recovery 
document that is about to be uploaded.
-  The server MUST refuse the upload with a "304" status code if the Etag 
matches
+  The server MUST refuse the upload with a ``304`` status code if the Etag 
matches
   the latest version already known to the server.
 
   *Anastasis-Policy-Signature*: The client must provide Base-32 encoded EdDSA 
signature over hash of body with ``$ACCOUNT_PRIV``, affirming desire to upload 
an encrypted recovery document.

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