[taler-docs] 25/94: change markup of ‘Expect: 100-Continue’ 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 336995e5714c27b45ea6f9289de305a4dead92d3
Author: Thien-Thi Nguyen <ttn@gnuvola.org>
AuthorDate: Wed Apr 7 03:46:57 2021 -0400

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

diff --git a/anastasis.rst b/anastasis.rst
index 41ff3be..22361ea 100644
--- a/anastasis.rst
+++ b/anastasis.rst
@@ -563,7 +563,7 @@ In the following, UUID is always defined and used according 
to `RFC 4122`_.
     backend may return a response immediately.
 
   *If-None-Match*: This header MUST be present and set to the SHA512 hash 
(Etag) of the body by the client.
-  The client SHOULD also set the "Expect: 100-Continue" header and wait for 
"100 continue"
+  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

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