18/18: doc: cookbook: Refer to the "Writing Manifests" manual node.

[guix-commits]

civodul pushed a commit to branch master
in repository guix.

commit 582b4bb4ce8239b321af8b75e866992aff16b8a9
Author: Ludovic Courtès <ludo@gnu.org>
AuthorDate: Wed Jun 1 23:26:33 2022 +0200

    doc: cookbook: Refer to the "Writing Manifests" manual node.
    
    * doc/guix-cookbook.texi (Basic setup with manifests): Tweak
    introductory paragraph.  Refer to the new "Writing Manifests" node of
    the manual.
---
 doc/guix-cookbook.texi | 9 +++++----
 1 file changed, 5 insertions(+), 4 deletions(-)

diff --git a/doc/guix-cookbook.texi b/doc/guix-cookbook.texi
index b4dc9f864c..06fb872177 100644
--- a/doc/guix-cookbook.texi
+++ b/doc/guix-cookbook.texi
@@ -2533,8 +2533,9 @@ Let's dive in the set up!
 @node Basic setup with manifests
 @subsection Basic setup with manifests
 
-A Guix profile can be set up @emph{via} a so-called @emph{manifest 
specification} that looks like
-this:
+A Guix profile can be set up @i{via} a @dfn{manifest}.  A manifest is a
+snippet of Scheme code that specifies the set of packages you want to
+have in your profile; it looks like this:
 
 @lisp
 (specifications->manifest
@@ -2547,8 +2548,8 @@ this:
     "package-N"))
 @end lisp
 
-@pxref{Invoking guix package,,, guix, GNU Guix Reference Manual}, for
-the syntax details.
+@xref{Writing Manifests,,, guix, GNU Guix Reference Manual}, for
+more information about the syntax.
 
 We can create a manifest specification per profile and install them this way: