From e316ba1fc48bfb4d2b8013a2bcdc54d63e8e6e0e Mon Sep 17 00:00:00 2001
From: John Ericson <John.Ericson@Obsidian.Systems>
Date: Thu, 25 Jan 2018 18:32:18 -0500
Subject: [PATCH] doc: chap cross: Make example command stick out more

It should be in a <programlisting>, not <command>, tag.
---
 doc/cross-compilation.xml | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/doc/cross-compilation.xml b/doc/cross-compilation.xml
index 028fd6744910..3e67944e58f7 100644
--- a/doc/cross-compilation.xml
+++ b/doc/cross-compilation.xml
@@ -253,7 +253,8 @@
     or also with <varname>crossSystem</varname>, in which case packages run on the latter, but all building happens on the former.
     Both parameters take the same schema as the 3 (build, host, and target) platforms defined in the previous section.
     As mentioned above, <literal>lib.systems.examples</literal> has some platforms which are used as arguments for these parameters in practice.
-    You can use them programmatically, or on the command line like <command>nix-build &lt;nixpkgs&gt; --arg crossSystem '(import &lt;nixpkgs/lib&gt;).systems.examples.fooBarBaz'</command>.
+    You can use them programmatically, or on the command line: <programlisting>
+nix-build &lt;nixpkgs&gt; --arg crossSystem '(import &lt;nixpkgs/lib&gt;).systems.examples.fooBarBaz' -A whatever</programlisting>
   </para>
   <para>
     While one is free to pass both parameters in full, there's a lot of logic to fill in missing fields.