Enable syntax highlighting

doc/manual/src/installation/multi-user.md

@@ -28,10 +28,12 @@ group should have no other members. The build users should not be
 members of any other group. On Linux, you can create the group and users
 as follows:
 
-    $ groupadd -r nixbld
-    $ for n in $(seq 1 10); do useradd -c "Nix build user $n" \
-        -d /var/empty -g nixbld -G nixbld -M -N -r -s "$(which nologin)" \
-        nixbld$n; done
+```console
+$ groupadd -r nixbld
+$ for n in $(seq 1 10); do useradd -c "Nix build user $n" \
+    -d /var/empty -g nixbld -G nixbld -M -N -r -s "$(which nologin)" \
+    nixbld$n; done
+```
 
 This creates 10 build users. There can never be more concurrent builds
 than the number of build users, so you may want to increase this if you
@@ -42,7 +44,9 @@ expect to do many builds at the same time.
 The [Nix daemon](../command-ref/nix-daemon.md) should be started as
 follows (as `root`):
 
-    $ nix-daemon
+```console
+$ nix-daemon
+```
 
 You’ll want to put that line somewhere in your system’s boot scripts.
 
@@ -50,7 +54,9 @@ To let unprivileged users use the daemon, they should set the
 [`NIX_REMOTE` environment variable](../command-ref/env-common.md) to
 `daemon`. So you should put a line like
 
-    export NIX_REMOTE=daemon
+```console
+export NIX_REMOTE=daemon
+```
 
 into the users’ login scripts.
 
@@ -61,8 +67,10 @@ permissions on the directory `/nix/var/nix/daemon-socket`. For instance,
 if you want to restrict the use of Nix to the members of a group called
 `nix-users`, do
 
-    $ chgrp nix-users /nix/var/nix/daemon-socket
-    $ chmod ug=rwx,o= /nix/var/nix/daemon-socket
+```console
+$ chgrp nix-users /nix/var/nix/daemon-socket
+$ chmod ug=rwx,o= /nix/var/nix/daemon-socket
+```
 
 This way, users who are not in the `nix-users` group cannot connect to
 the Unix domain socket `/nix/var/nix/daemon-socket/socket`, so they