From: Calvin Heim <frofroggy@gmail.com>
To: 22197@debbugs.gnu.org
Subject: bug#22197: [PATCH] Add doc fix
Date: Thu, 17 Dec 2015 13:47:42 -0800 [thread overview]
Message-ID: <56732D7E.6030505@gmail.com> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
* doc/ref/api-compound.texi: Fix grammar.
- ---
doc/ref/api-compound.texi | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/doc/ref/api-compound.texi b/doc/ref/api-compound.texi
index 8ec32d6..47f5e8a 100644
- --- a/doc/ref/api-compound.texi
+++ b/doc/ref/api-compound.texi
@@ -3718,7 +3718,7 @@ the following examples.
#f
@end lisp
-Better is to use the procedure @code{hashq-get-handle}, which makes a
+It is better to use the procedure @code{hashq-get-handle}, which makes a
distinction between the two cases. Just like @code{assq}, this
procedure returns a key/value-pair on success, and @code{#f} if the
key is not found.
- --
1.9.1
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)
iQIcBAEBAgAGBQJWcy1+AAoJEPFy53W67dRmib4P/iRA0v5tNKqv8UKwBwaeh5nv
2is04zWASy4lFW/k/2pT08hWL7HsxsK1mQTbGyM9gvS/8miGTqc8M7UQlWIjJk5P
VTbAxwBKuN4MGIEeXTOS3TRcK6CmgyBqkXqPjrH/HZF0gm/13Zh4d2/lUDSfZ6WD
k4E9uyPu+WfkSBlw4tA+xUs/qZWaBx4mMCfRCOoynZy5lDlAdmHfveYrXjBm4QnS
eajgYLjh2A81ISD5Vr+CGK+7FDs/pTz62TPDMLeexukJhOU8QCCjtij0AQu5lsFO
PaWc6dSvR0ZlGW1GunU7UrK1n1TgvoPGzWWK4QqqwFb7WVTsqs5rKZWqptiEeQOS
BvJOJLYvJks/LBQ5jxGxXgyG6QE5q8L1OQR1Cc4yAdpAol6R5OClxy3HtGcrs37a
HhFo462vWoBSkDrMJkuwJlix+UvqwoT4wR02Vu+KS2btrLiDjFi8GPC9oyTmD/GG
VjcK0nJP44rHqkRbE8lOSW22YWPWW2V3JD6rdjZNgPtzYTyAOZ98V+4aoTVeCJlb
xe7r64FliYEVgXyHhhDRWGjkHxazbfK/2uDRQaSWV5HT6t7PgqJ15Z7GEblnG1lO
7yTMQrc+DqZYeZBpBzqSv7eskqGZ/UAJmFJZHNLPk9nHPkNILZDv22JmGWUdNv/q
lV7I3fPl2JgCi57Dxeq9
=pIMi
-----END PGP SIGNATURE-----
next reply other threads:[~2015-12-17 21:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-17 21:47 Calvin Heim [this message]
2016-08-07 10:58 ` bug#22197: [PATCH] Add doc fix Andy Wingo
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=56732D7E.6030505@gmail.com \
--to=frofroggy@gmail.com \
--cc=22197@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).