unofficial mirror of bug-guile@gnu.org 
 help / color / mirror / Atom feed
From: Luri Bert <luribert331@zoho.com>
To: 23333@debbugs.gnu.org
Subject: bug#23333: typo in documentation
Date: Thu, 21 Apr 2016 19:05:42 +0200	[thread overview]
Message-ID: <87k2jqlwnt.fsf@zoho.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 84 bytes --]

Hello!

There is a little typo in the documentation. Here is the patch.

Bye,
Luri


[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: typofix.patch --]
[-- Type: text/x-diff, Size: 972 bytes --]

From 3aa250f58e01463fe172fd4de80f34df403f554b Mon Sep 17 00:00:00 2001
From: Luribert <luribert331@zoho.com>
Date: Thu, 21 Apr 2016 18:56:58 +0200
Subject: [PATCH] Fixed typo in documentation.

* doc/ref/web.texi (Http Headers): Fixed typo.
---
 doc/ref/web.texi | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/doc/ref/web.texi b/doc/ref/web.texi
index 2311b82..b078929 100644
--- a/doc/ref/web.texi
+++ b/doc/ref/web.texi
@@ -747,9 +747,9 @@ a resource.
 @deftypevr {HTTP Header} List content-type
 The MIME type of a resource, as a symbol, along with any parameters.
 @example
-(parse-header 'content-length "text/plain")
+(parse-header 'content-type "text/plain")
 @result{} (text/plain)
-(parse-header 'content-length "text/plain;charset=utf-8")
+(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
-- 
2.5.0


             reply	other threads:[~2016-04-21 17:05 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-21 17:05 Luri Bert [this message]
2016-05-08 19:59 ` bug#23333: typo in 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=87k2jqlwnt.fsf@zoho.com \
    --to=luribert331@zoho.com \
    --cc=23333@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).