unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Colin Woodbury <colin_woodbury@caddi.jp>
To: guile-devel@gnu.org
Subject: [PATCH] Fix minor typos
Date: Wed, 30 Nov 2022 09:39:35 +0900	[thread overview]
Message-ID: <448cb126-3a40-fd85-e27b-43806030860b@caddi.jp> (raw)

[-- Attachment #1: Type: text/plain, Size: 258 bytes --]

Hi all, this is my first patch to Guile. I have a few more planned, but 
figured I'd throw this in first to get my feet wet with the development 
process here.

Detailed comments regarding the typo fixes are included in the patch's 
commit message.

Cheers!

[-- Attachment #2: 0001-doc-Fix-minor-typos.patch --]
[-- Type: text/x-patch, Size: 1949 bytes --]

From 5ba770e685aefc26e8554ccb327bce9fbb39acce Mon Sep 17 00:00:00 2001
From: Colin Woodbury <colin@fosskers.ca>
Date: Wed, 30 Nov 2022 09:24:06 +0900
Subject: [PATCH] doc: Fix minor typos

The spelling mistake is a clear fix, but the Arrays fix might not be as
obvious. Previously, with the "arrays" alias, the @ref macro would
render a superfluous period after the word "arrays", rendering (at least
within Emacs) as:

  you may wish to use see arrays. instead.

Notice also the superflous "see" also somehow added by @ref. That fix
should generally be included elsewhere, since it affects many more
locations, some of which expect the word "see" to appear magically, and
some which don't.
---
 doc/ref/api-data.texi     | 2 +-
 doc/ref/srfi-modules.texi | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/doc/ref/api-data.texi b/doc/ref/api-data.texi
index 8658b9785..30190f315 100644
--- a/doc/ref/api-data.texi
+++ b/doc/ref/api-data.texi
@@ -6136,7 +6136,7 @@ accessed element in the list.
 
 Vectors can contain any kind of Scheme object; it is even possible to
 have different types of objects in the same vector.  For vectors
-containing vectors, you may wish to use @ref{Arrays,arrays} instead.
+containing vectors, you may wish to use @ref{Arrays} instead.
 Note, too, that vectors are a special case of one dimensional
 non-uniform arrays and that array procedures operate happily on vectors.
 
diff --git a/doc/ref/srfi-modules.texi b/doc/ref/srfi-modules.texi
index bce5b4eac..0ef136215 100644
--- a/doc/ref/srfi-modules.texi
+++ b/doc/ref/srfi-modules.texi
@@ -6077,7 +6077,7 @@ be used to generalize something like @code{tsegment}:
 @deffnx {Scheme Procedure} tfold reducer seed
 
 A folding transducer that yields the result of @code{(reducer seed
-value)}, saving it's result between iterations.
+value)}, saving its result between iterations.
 
 @example
 (list-transduce (tfold +) rcons (iota 10))
-- 
2.38.1


             reply	other threads:[~2022-11-30  0:39 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-30  0:39 Colin Woodbury [this message]
2022-12-01  0:17 ` [PATCH] Fix minor typos Aleix Conchillo Flaqué
2022-12-01  1:03   ` Colin Woodbury
2022-12-02  5:45     ` Aleix Conchillo Flaqué
2022-12-02  6:09       ` Colin Woodbury
2022-12-02 17:43         ` Aleix Conchillo Flaqué
2022-12-09 12:31           ` Mikael Djurfeldt

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=448cb126-3a40-fd85-e27b-43806030860b@caddi.jp \
    --to=colin_woodbury@caddi.jp \
    --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).