guile-commits
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Guile-commits] branch main updated: Fix typo in srfi-69 doc


From: Daniel Llorens
Subject: [Guile-commits] branch main updated: Fix typo in srfi-69 doc
Date: Tue, 14 Sep 2021 10:55:29 -0400

This is an automated email from the git hooks/post-receive script.

lloda pushed a commit to branch main
in repository guile.

The following commit(s) were added to refs/heads/main by this push:
     new af741e5  Fix typo in srfi-69 doc
af741e5 is described below

commit af741e50e912790b3756a9e64a0cffca9b14899b
Author: Daniel Llorens <lloda@sarc.name>
AuthorDate: Tue Sep 14 16:55:15 2021 +0200

    Fix typo in srfi-69 doc
---
 doc/ref/srfi-modules.texi | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/doc/ref/srfi-modules.texi b/doc/ref/srfi-modules.texi
index cf7a4b4..d32560a 100644
--- a/doc/ref/srfi-modules.texi
+++ b/doc/ref/srfi-modules.texi
@@ -5280,7 +5280,7 @@ By default, @var{equal-proc} is @code{equal?}.  It can be 
any
 two-argument procedure, and should answer whether two keys are the
 same for this table's purposes.
 
-My default @var{hash-proc} assumes that @code{equal-proc} is no
+By default @var{hash-proc} assumes that @code{equal-proc} is no
 coarser than @code{equal?}  unless it is literally @code{string-ci=?}.
 If provided, @var{hash-proc} should be a two-argument procedure that
 takes a key and the current table size, and answers a reasonably good



reply via email to

[Prev in Thread] Current Thread [Next in Thread]