unofficial mirror of bug-guile@gnu.org 
 help / color / mirror / Atom feed
From: Alex Kost <alezost@gmail.com>
To: 20797@debbugs.gnu.org
Subject: bug#20797: [PATCH] Fix typo in manual.
Date: Fri, 12 Jun 2015 19:43:17 +0300	[thread overview]
Message-ID: <87fv5wev2y.fsf@gmail.com> (raw)

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

Hello, I've noticed a typo.  Please let me know if the attached patch is
not appropriate.


[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: 0001-Fix-typo-in-manual.patch --]
[-- Type: text/x-diff, Size: 1010 bytes --]

From f7aabb38c24b40bec4be6af13ad387d4ed0c20ca Mon Sep 17 00:00:00 2001
From: Alex Kost <alezost@gmail.com>
Date: Fri, 12 Jun 2015 19:30:17 +0300
Subject: [PATCH] Fix typo in manual.

* doc/ref/api-modules.texi (Using Guile Modules): Remove extra "yet".
---
 doc/ref/api-modules.texi | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/doc/ref/api-modules.texi b/doc/ref/api-modules.texi
index 4c46f29..8f18b1e 100644
--- a/doc/ref/api-modules.texi
+++ b/doc/ref/api-modules.texi
@@ -171,8 +171,8 @@ of @code{@@} and should only be used as a last resort or for
 debugging, for example.
 
 Note that just as with a @code{use-modules} statement, any module that
-has not yet been loaded yet will be loaded when referenced by a
-@code{@@} or @code{@@@@} form.
+has not yet been loaded will be loaded when referenced by a @code{@@} or
+@code{@@@@} form.
 
 You can also use the @code{@@} and @code{@@@@} syntaxes as the target
 of a @code{set!} when the binding refers to a variable.
-- 
2.4.2


             reply	other threads:[~2015-06-12 16:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-12 16:43 Alex Kost [this message]
2015-06-19 19:46 ` bug#20797: [PATCH] Fix typo in manual Mark H Weaver

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=87fv5wev2y.fsf@gmail.com \
    --to=alezost@gmail.com \
    --cc=20797@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).