From 4ebbd92c291573c1ae5a1cf7c004caeefa09dd86 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Ludovic=20Court=C3=A8s?= <ludo@gnu.org>
Date: Tue, 23 Jun 2020 08:57:58 +0200
Subject: [PATCH] doc: cookbook: Fix typos.

* doc/guix-cookbook.texi (Extended example): Fix typos.
---
 doc/guix-cookbook.texi | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/doc/guix-cookbook.texi b/doc/guix-cookbook.texi
index e4d685c7478..ec6217c69c0 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/
-- 
GitLab