summary refs log tree commit diff
path: root/doc
diff options
context:
space:
mode:
authorLudovic Courtès <ludo@gnu.org>2022-06-01 23:26:33 +0200
committerLudovic Courtès <ludo@gnu.org>2022-06-01 23:28:20 +0200
commit582b4bb4ce8239b321af8b75e866992aff16b8a9 (patch)
tree42b5d3a05b9be8f5ae628c0a8a5e20d5ca4fda46 /doc
parentfe7856b6ed8f197fae0e989927783bd010bc482d (diff)
downloadguix-582b4bb4ce8239b321af8b75e866992aff16b8a9.tar.gz
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.
Diffstat (limited to 'doc')
-rw-r--r--doc/guix-cookbook.texi9
1 files 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: