[gnurl] 391/411: docs: fix typos and markup in ETag manpage sections

[gnunet]

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

nikita pushed a commit to branch master
in repository gnurl.

commit 41b3b830f118197a4b4988f425902493f4f85de8
Author: Daniel Gustafsson <daniel@yesql.se>
AuthorDate: Thu Dec 3 13:25:42 2020 +0100

    docs: fix typos and markup in ETag manpage sections
    
    Reported-by: emanruse on github
    Fixes #6273
---
 docs/cmdline-opts/etag-compare.d | 2 +-
 docs/cmdline-opts/etag-save.d    | 4 ++--
 2 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/docs/cmdline-opts/etag-compare.d b/docs/cmdline-opts/etag-compare.d
index cbf48ac5e..cd8fe4a33 100644
--- a/docs/cmdline-opts/etag-compare.d
+++ b/docs/cmdline-opts/etag-compare.d
@@ -15,5 +15,5 @@ line with a desired ETag. An empty file is parsed as an empty 
ETag.
 Use the option --etag-save to first save the ETag from a response, and
 then use this option to compare using the saved ETag in a subsequent request.
 
-\fCOMPARISON\fP: There are 2 types of comparison or ETags, Weak and Strong.
+\fBCOMPARISON\fP: There are 2 types of comparison or ETags: Weak and Strong.
 This option expects, and uses a strong comparison.
diff --git a/docs/cmdline-opts/etag-save.d b/docs/cmdline-opts/etag-save.d
index 82e6dfa84..95d1615ae 100644
--- a/docs/cmdline-opts/etag-save.d
+++ b/docs/cmdline-opts/etag-save.d
@@ -10,8 +10,8 @@ usually part of headers returned by a request. When server 
sends an
 ETag, it must be enveloped by a double quote. This option extracts the
 ETag without the double quotes and saves it into the <file>.
 
-A server can send a week ETag which is prefixed by "W/". This identifier
+A server can send a weak ETag which is prefixed by "W/". This identifier
 is not considered, and only relevant ETag between quotation marks is parsed.
 
-It an ETag wasn't send by the server or it cannot be parsed, and empty
+It an ETag wasn't sent by the server or it cannot be parsed, an empty
 file is created.

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