From b5e0d90ea5625c5a4f43ac2b3d4c1fcf2e933441 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Ludovic=20Court=C3=A8s?= Date: Fri, 17 Oct 2025 11:53:14 +0200 Subject: [PATCH] =?UTF-8?q?doc:=20cookbook:=20Fix=20typos=20under=20?= =?UTF-8?q?=E2=80=9CReproducible=20Research=E2=80=9D.?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit * doc/guix-cookbook.texi (Setting Up the Environment): Remove extra word; add missing word. Change-Id: I41ba29bd81fd6e8262d4112e57e1ff0cce439967 --- 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 53d72a4b4d2..96acdb7a289 100644 --- a/doc/guix-cookbook.texi +++ b/doc/guix-cookbook.texi @@ -5730,14 +5730,14 @@ If you fail to guess the name of the package (this one was easy!), try @code{guix search}. Environments for Python, R, and similar high-level languages are -relatively easy to set up. For C/C++ code, you may find need many more +relatively easy to set up. For C/C++ code, you may need more packages: @example guix shell -C gcc-toolchain cmake coreutils grep sed make -- @dots{} @end example -Or perhaps you'll find that you could just as well provide a +Or perhaps you'll find that you could just as well provide a definition for your package---@pxref{Defining Packages,,, guix, GNU Guix Reference Manual}, to learn more on how to do that.