From: jgart via "Bug reports for GUILE, GNU's Ubiquitous Extension Language" <bug-guile@gnu.org>
To: 59647@debbugs.gnu.org
Cc: jgart <jgart@dismail.de>
Subject: bug#59647: [PATCH] Fix typos in docstrings.
Date: Sun, 27 Nov 2022 20:20:21 -0600 [thread overview]
Message-ID: <20221128022021.30225-1-jgart@dismail.de> (raw)
* libguile/boolean.c
(scm_not): Fix typo.
(scm_boolean_p): Fix typo.
---
libguile/boolean.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/libguile/boolean.c b/libguile/boolean.c
index e8370331f..930001a89 100644
--- a/libguile/boolean.c
+++ b/libguile/boolean.c
@@ -56,7 +56,7 @@ verify (SCM_BITS_DIFFER_IN_EXACTLY_TWO_BIT_POSITIONS \
SCM_DEFINE (scm_not, "not", 1, 0, 0,
(SCM x),
- "Return @code{#t} iff @var{x} is false, else return @code{#f}.")
+ "Return @code{#t} if @var{x} is false, else return @code{#f}.")
#define FUNC_NAME s_scm_not
{
return scm_from_bool (scm_is_false (x));
@@ -82,7 +82,7 @@ SCM_DEFINE (scm_nil_p, "nil?", 1, 0, 0,
SCM_DEFINE (scm_boolean_p, "boolean?", 1, 0, 0,
(SCM obj),
- "Return @code{#t} iff @var{obj} is @code{#t} or false.")
+ "Return @code{#t} if @var{obj} is @code{#t} or false.")
#define FUNC_NAME s_scm_boolean_p
{
return scm_from_bool (scm_is_bool (obj));
--
2.38.1
next reply other threads:[~2022-11-28 2:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-28 2:20 jgart via Bug reports for GUILE, GNU's Ubiquitous Extension Language [this message]
2023-01-16 22:20 ` bug#59647: [PATCH] Fix typos in docstrings Ludovic Courtès
2023-01-16 23:17 ` jgart via Bug reports for GUILE, GNU's Ubiquitous Extension Language
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=20221128022021.30225-1-jgart@dismail.de \
--to=bug-guile@gnu.org \
--cc=59647@debbugs.gnu.org \
--cc=jgart@dismail.de \
/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).