From: Blake Shaw via "Bug reports for GUILE, GNU's Ubiquitous Extension Language" <bug-guile@gnu.org>
To: 52482@debbugs.gnu.org
Cc: Blake Shaw <blake@nonconstructivism.com>
Subject: bug#52482: [PATCH] doc/ref/texinfo.texi: corrected typo generare->generate
Date: Tue, 14 Dec 2021 22:40:32 +0700 [thread overview]
Message-ID: <caaa20e7a4072061916cc111fea64c2b31f136b3.1639496432.git.blake@nonconstructivism.com> (raw)
Signed-off-by: Blake Shaw <blake@nonconstructivism.com>
---
doc/ref/texinfo.texi | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/doc/ref/texinfo.texi b/doc/ref/texinfo.texi
index 64a866b23..59df7f8e7 100644
--- a/doc/ref/texinfo.texi
+++ b/doc/ref/texinfo.texi
@@ -472,7 +472,7 @@ Serialize the stexi @var{tree} into plain texinfo.
@node texinfo reflection
@subsection (texinfo reflection)
@subsubsection Overview
-Routines to generare @code{stexi} documentation for objects and modules.
+Routines to generate @code{stexi} documentation for objects and modules.
Note that in this context, an @dfn{object} is just a value associated
with a location. It has nothing to do with GOOPS.
--
2.33.1
reply other threads:[~2021-12-14 15:40 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=caaa20e7a4072061916cc111fea64c2b31f136b3.1639496432.git.blake@nonconstructivism.com \
--to=bug-guile@gnu.org \
--cc=52482@debbugs.gnu.org \
--cc=blake@nonconstructivism.com \
/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).