aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorLudovic Courtès <ludo@gnu.org>2020-06-23 08:57:58 +0200
committerLudovic Courtès <ludo@gnu.org>2020-06-23 23:39:42 +0200
commit4ebbd92c291573c1ae5a1cf7c004caeefa09dd86 (patch)
tree9e0a42ab854413902ce010134557bdbf7a0c9a69
parent501d89d707a64335731f54e0e28dbf252b31afc7 (diff)
downloadguix-4ebbd92c291573c1ae5a1cf7c004caeefa09dd86.tar
guix-4ebbd92c291573c1ae5a1cf7c004caeefa09dd86.tar.gz
doc: cookbook: Fix typos.
* doc/guix-cookbook.texi (Extended example): Fix typos.
-rw-r--r--doc/guix-cookbook.texi4
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/guix-cookbook.texi b/doc/guix-cookbook.texi
index e4d685c747..ec6217c69c 100644
--- a/doc/guix-cookbook.texi
+++ b/doc/guix-cookbook.texi
@@ -847,14 +847,14 @@ To ensure that the source code from the Git repository is stored in a
directory with a descriptive name, we use @code{(file-name (git-file-name name
version))}.
-The @code{git-version} procedure that can be used to derive the
+The @code{git-version} procedure can be used to derive the
version when packaging programs for a specific commit, following the
Guix contributor guidelines (@pxref{Version Numbers,,, guix, GNU Guix
Reference Manual}).
How does one obtain the @code{sha256} hash that's in there, you ask? By
invoking @command{guix hash} on a checkout of the desired commit, along
-the lines:
+these lines:
@example
git clone https://github.com/libgit2/libgit2/