From: jsynacek@redhat.com
To: 41355@debbugs.gnu.org
Subject: bug#41355: [PATCH] Fix typos in the manual
Date: Sun, 17 May 2020 13:03:44 +0200 [thread overview]
Message-ID: <20200517110344.53777-1-jsynacek@redhat.com> (raw)
From: Jan Synacek <jsynacek@redhat.com>
* doc/ref/api-control.texi:
* doc/ref/r6rs.texi:
* doc/ref/sxml.texi: Fix typos.
---
doc/ref/api-control.texi | 4 ++--
doc/ref/r6rs.texi | 2 +-
doc/ref/sxml.texi | 2 +-
3 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/doc/ref/api-control.texi b/doc/ref/api-control.texi
index b62c0d6fe..5df5344c5 100644
--- a/doc/ref/api-control.texi
+++ b/doc/ref/api-control.texi
@@ -678,8 +678,8 @@ Evaluate @var{expr} in a prompt, optionally specifying a tag and a
handler. If no tag is given, the default prompt tag is used.
If no handler is given, a default handler is installed. The default
-handler accepts a procedure of one argument, which will called on the
-captured continuation, within a prompt.
+handler accepts a procedure of one argument, which will be called on
+the captured continuation, within a prompt.
Sometimes it's easier just to show code, as in this case:
diff --git a/doc/ref/r6rs.texi b/doc/ref/r6rs.texi
index c47eef7d1..e430708d0 100644
--- a/doc/ref/r6rs.texi
+++ b/doc/ref/r6rs.texi
@@ -1173,7 +1173,7 @@ evaluates to @code{baz}.
@deffn {Scheme Procedure} raise obj
Equivalent to core Guile @code{(raise-exception @var{obj})}.
-@xref{Raising and Handling Exceptions}. p(Unfortunately, @code{raise}
+@xref{Raising and Handling Exceptions}. (Unfortunately, @code{raise}
is already bound to a different function in core Guile.
@xref{Signals}.)
@end deffn
diff --git a/doc/ref/sxml.texi b/doc/ref/sxml.texi
index 19125091c..5f827916e 100644
--- a/doc/ref/sxml.texi
+++ b/doc/ref/sxml.texi
@@ -230,7 +230,7 @@ SAX parsers were created to give the programmer more control on the
parsing process. A programmer gives the SAX parser a number of
``callbacks'': functions that will be called on various features of the
XML stream as they are encountered. SAX parsers are more efficient, but
-much harder to user, as users typically have to manually maintain a
+much harder to use, as users typically have to manually maintain a
stack of open elements.
Kiselyov realized that the SAX programming model could be made much
--
2.26.2
next reply other threads:[~2020-05-17 11:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-17 11:03 jsynacek [this message]
2020-05-27 20:40 ` bug#41355: [PATCH] Fix typos in the manual 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=20200517110344.53777-1-jsynacek@redhat.com \
--to=jsynacek@redhat.com \
--cc=41355@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).