From: Dmitry Polyakov <liltechdude@gmail.com>
To: guile-devel@gnu.org
Subject: tiny typo fix
Date: Fri, 14 Oct 2022 11:30:26 +0500 [thread overview]
Message-ID: <87edvakjct.fsf@gmail.com> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: 0001-api-scheduling.texi-Fix-typo.patch --]
[-- Type: text/x-patch, Size: 902 bytes --]
From 49129805f8103a4a88de6bec696ceff16420ac8a Mon Sep 17 00:00:00 2001
From: Dmitry Polyakov <liltechdude@gmail.com>
Date: Fri, 14 Oct 2022 10:31:11 +0500
Subject: [PATCH] api-scheduling.texi: Fix typo
* doc/ref/api-scheduling.texi (thread?): fix typo
---
doc/ref/api-scheduling.texi | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/doc/ref/api-scheduling.texi b/doc/ref/api-scheduling.texi
index 09e65e728..ffefbf416 100644
--- a/doc/ref/api-scheduling.texi
+++ b/doc/ref/api-scheduling.texi
@@ -80,7 +80,7 @@ Once @var{body} or @var{handler} returns, the return value is made the
@deffn {Scheme Procedure} thread? obj
@deffnx {C Function} scm_thread_p (obj)
-Return @code{#t} ff @var{obj} is a thread; otherwise, return
+Return @code{#t} if @var{obj} is a thread; otherwise, return
@code{#f}.
@end deffn
base-commit: bc3b1a4e2d19cf9fd748297bcecf4f868499fa62
--
2.38.0
[-- Attachment #2: Type: text/plain, Size: 29 bytes --]
--
sanity level in trouble
reply other threads:[~2022-10-14 6:30 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=87edvakjct.fsf@gmail.com \
--to=liltechdude@gmail.com \
--cc=guile-devel@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).