GNU bug report logs - #64690
[PATCH] doc: Fix typos.

Previous Next

Full log

View this message in rfc822 format

From: help-debbugs <at> gnu.org (GNU bug Tracking System)
To: Florian Pelz <pelzflorian <at> pelzflorian.de>
Subject: bug#64690: closed (Re: bug#64690: [PATCH] doc: Fix typos.)
Date: Tue, 18 Jul 2023 00:17:02 +0000

[Message part 1 (text/plain, inline)]

Your bug report

#64690: [PATCH] doc: Fix typos.

which was filed against the guix-patches package, has been closed.

The explanation is attached below, along with your original report.
If you require more details, please reply to 64690 <at> debbugs.gnu.org.

-- 
64690: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=64690
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems

[Message part 2 (message/rfc822, inline)]

From: "pelzflorian (Florian Pelz)" <pelzflorian <at> pelzflorian.de>
To: 64690-done <at> debbugs.gnu.org
Cc: Ludovic Courtès <ludo <at> gnu.org>
Subject: Re: bug#64690: [PATCH] doc: Fix typos.
Date: Tue, 18 Jul 2023 02:16:48 +0200

Thanks!  Pushed as 3a3752400d7a70a295a27b66f29457aeeaa2cf27.

Regards,
Florian

[Message part 3 (message/rfc822, inline)]

From: Florian Pelz <pelzflorian <at> pelzflorian.de>
To: guix-patches <at> gnu.org
Cc: Florian Pelz <pelzflorian <at> pelzflorian.de>
Subject: [PATCH] doc: Fix typos.
Date: Mon, 17 Jul 2023 21:06:12 +0200

* doc/guix.texi (Creating a Channel): Fix typos.
---
Not confident about the commas, but still.

 doc/guix.texi | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/doc/guix.texi b/doc/guix.texi
index 9af1b4417b..ee03de04dc 100644
--- a/doc/guix.texi
+++ b/doc/guix.texi
@@ -5776,7 +5776,7 @@ a package collection.  This involves the following steps:
 
 @enumerate
 @item
-Channels live in a Git repository so the first step, when creating a
+A channel lives in a Git repository so the first step, when creating a
 channel, is to create its repository:
 
 @example
@@ -5790,7 +5790,7 @@ The next step is to create files containing package modules
 (@pxref{Package Modules}), each of which will contain one or more
 package definitions (@pxref{Defining Packages}).  A channel can provide
 things other than packages, such as build systems or services; we're
-using packages as most common use case.
+using packages as it's the most common use case.
 
 For example, Alice might want to provide a module called @code{(alice
 packages greetings)} that will provide her favorite ``hello world''
@@ -5815,7 +5815,7 @@ that.
 @item
 With this first module in place, the next step is to test the packages
 it provides.  This can be done with @command{guix build}, which needs to
-be fold to look for modules in the Git checkout.  For example, assuming
+be told to look for modules in the Git checkout.  For example, assuming
 @code{(alice packages greetings)} provides a package called
 @code{hi-from-alice}, Alice will run this command from the Git checkout:
 
@@ -5856,7 +5856,7 @@ example, @code{(alice packages greetings)} will automatically be found
 by the @command{guix} command.
 @end enumerate
 
-Voilà!  
+Voilà!
 
 @c What follows stems from discussions at
 @c <https://debbugs.gnu.org/cgi/bugreport.cgi?bug=22629#134> as well as

base-commit: 3755941f038ec66fba568fa88d6b2d295e196723
-- 
2.41.0

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.