From: jc zulian <jeanchristophe.zulian@gmail.com>
To: 10302@debbugs.gnu.org
Subject: bug#10302: Some typos in web.texi documenation
Date: Wed, 14 Dec 2011 22:20:38 +0100 [thread overview]
Message-ID: <CA+3nJJd9btQogrFy7EgGAFz4ccDpV88LiFtYz3W-Cqxu4+DBew@mail.gmail.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 189 bytes --]
Hello,
While reading the documentation I came across some typos. Please find
attached a patch to correct those (I hope the patch format is alright).
Thanks for your work,
Jean-christophe
[-- Attachment #1.2: Type: text/html, Size: 248 bytes --]
[-- Attachment #2: typos-web-doc.patch --]
[-- Type: text/x-patch, Size: 789 bytes --]
diff --git a/doc/ref/web.texi b/doc/ref/web.texi
index d98f1bb..795e2c9 100644
--- a/doc/ref/web.texi
+++ b/doc/ref/web.texi
@@ -349,7 +349,7 @@ parsing and serialization procedures. If a header is unknown, its
string name is simply its symbol name in title-case.
@deffn {Scheme Procedure} known-header? sym
-Return @code{#t} iff @var{sym} is a known header, with associated
+Return @code{#t} if @var{sym} is a known header, with associated
parsers and serialization procedures.
@end deffn
@@ -398,7 +398,7 @@ HTTP stack like this:
@end example
@deffn {Scheme Procedure} valid-header? sym val
-Return a true value iff @var{val} is a valid Scheme value for the header
+Return a true value if @var{val} is a valid Scheme value for the header
with name @var{sym}.
@end deffn
next reply other threads:[~2011-12-14 21:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-14 21:20 jc zulian [this message]
2011-12-15 4:27 ` bug#10302: Some typos in web.texi documenation Mark H Weaver
2011-12-15 7:45 ` jc zulian
2011-12-15 14:19 ` Andy Wingo
2011-12-15 21:08 ` jc zulian
2011-12-16 7:46 ` Marijn
2013-03-10 21:29 ` Andy Wingo
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=CA+3nJJd9btQogrFy7EgGAFz4ccDpV88LiFtYz3W-Cqxu4+DBew@mail.gmail.com \
--to=jeanchristophe.zulian@gmail.com \
--cc=10302@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).