From: Arun Isaac <arunisaac@systemreboot.net>
To: 34008@debbugs.gnu.org
Subject: bug#34008: [PATCH] doc: Fix minor typo in the HTTP headers documentation.
Date: Mon, 7 Jan 2019 17:42:31 +0530 [thread overview]
Message-ID: <20190107121232.13444-1-arunisaac@systemreboot.net> (raw)
* doc/ref/web.texi (HTTP Headers): Fix minor typo.
---
doc/ref/web.texi | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/doc/ref/web.texi b/doc/ref/web.texi
index c8fc488b7..c11ed32fa 100644
--- a/doc/ref/web.texi
+++ b/doc/ref/web.texi
@@ -791,7 +791,7 @@ The MIME type of a resource, as a symbol, along with any parameters.
(parse-header 'content-type "text/plain;charset=utf-8")
@result{} (text/plain (charset . "utf-8"))
@end example
-Note that the @code{charset} parameter is something is a misnomer, and
+Note that the @code{charset} parameter is something of a misnomer, and
the HTTP specification admits this. It specifies the @emph{encoding} of
the characters, not the character set.
@end deftypevr
--
2.19.2
next reply other threads:[~2019-01-07 12:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-07 12:12 Arun Isaac [this message]
2019-06-24 13:19 ` bug#34008: [PATCH] doc: Fix minor typo in the HTTP headers documentation Ludovic Courtès
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190107121232.13444-1-arunisaac@systemreboot.net \
--to=arunisaac@systemreboot.net \
--cc=34008@debbugs.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).