ryan77627/guix
1
0
Fork 0
mirror of https://git.in.rschanz.org/ryan77627/guix.git synced 2025-01-11 13:49:23 -05:00
Code Issues Projects Releases Packages Wiki Activity Actions

doc: Use @command instead of @code.

Browse source 
* doc/guix.texi: Use @command to refer to Guix commands.
This commit is contained in:
Ricardo Wurmus 2022-10-06 12:14:33 +02:00
parent 40a42c4348
commit 32ba74ab48
No known key found for this signature in database
GPG key ID: 197A5888235FACAC
1 changed files with 3 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

6
doc/guix.texi
View file

@ -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