[bug#72439] [PATCH v2] doc: Setting Up the Daemon: Give guidance to whom this section is useful.

[Florian Pelz]

* doc/guix.texi (Setting Up the Daemon): Specify intended audience.

Change-Id: I784c5f720aa87bddb6455e42181a1e9de5d7ec9a
---
Changes since v1:
* better commit message
* give command to test daemon
* shortened WSL

 doc/guix.texi | 21 ++++++++++++++++++++-
 1 file changed, 20 insertions(+), 1 deletion(-)

diff --git a/doc/guix.texi b/doc/guix.texi
index b7eb8fd346..201573b5b1 100644
--- a/doc/guix.texi
+++ b/doc/guix.texi
@@ -860,8 +860,27 @@ Setting Up the Daemon
 @section Setting Up the Daemon
 
 @cindex daemon
+During the installation, the @dfn{build daemon} that must be running
+to use Guix has already been set up and you can run @command{guix}
+commands in your terminal program, @pxref{Getting Started}:
+
+@example
+guix build hello
+@end example
+
+If this works, feel free to skip this section.  You should continue
+with the following section, @ref{Application Setup}.
+
+However, some of us have reason to replace outdated daemon versions,
+tweak it, perform builds on other machines (@pxref{Daemon Offload
+Setup}) or start it manually in special environments like Chroots
+(@pxref{Chrooting into an existing system}) or WSL (not needed for WSL
+images created with Guix, @pxref{System Images,
+@code{wsl2-image-type}}).  If you want to know more or optimize your
+system, this section is worth reading.
+
 Operations such as building a package or running the garbage collector
-are all performed by a specialized process, the @dfn{build daemon}, on
+are all performed by a specialized process, the build daemon, on
 behalf of clients.  Only the daemon may access the store and its
 associated database.  Thus, any operation that manipulates the store
 goes through the daemon.  For instance, command-line tools such as

base-commit: 3c309a7b7020a9645bfe775d9f53f43f05d076bf
-- 
2.45.2