From 32ba74ab483e0e2fb92c01a4110f741ad88497a6 Mon Sep 17 00:00:00 2001 From: Ricardo Wurmus Date: Thu, 6 Oct 2022 12:14:33 +0200 Subject: doc: Use @command instead of @code. * doc/guix.texi: Use @command to refer to Guix commands. --- doc/guix.texi | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/doc/guix.texi b/doc/guix.texi index 6691ae5844..3079d49b1d 100644 --- a/doc/guix.texi +++ b/doc/guix.texi @@ -37809,7 +37809,7 @@ like @end lisp @node Invoking guix system -@section Invoking @code{guix system} +@section Invoking @command{guix system} Once you have written an operating system declaration as seen in the previous section, it can be @dfn{instantiated} using the @command{guix @@ -38455,7 +38455,7 @@ Again, the default output format is Dot/Graphviz, but you can pass @end table @node Invoking guix deploy -@section Invoking @code{guix deploy} +@section Invoking @command{guix deploy} We've already seen @code{operating-system} declarations used to manage a machine's configuration locally. Suppose you need to configure multiple @@ -41027,7 +41027,7 @@ A typical extension for adding a channel might look like this: @end defvr @node Invoking guix home -@section Invoking @code{guix home} +@section Invoking @command{guix home} Once you have written a home environment declaration (@pxref{Declaring the Home Environment,,,,}, it can be @dfn{instantiated} using the -- cgit 1.4.1