ref-manual: Edits to the random build error question.

(From yocto-docs rev: ee7aa728f9a814d91de94dbc90a593958e6f295e)

Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

1 files changed, 14 insertions, 7 deletions

diff --git a/documentation/ref-manual/faq.xml b/documentation/ref-manual/faq.xml
index 8553a40081..8884dba663 100644
--- a/documentation/ref-manual/faq.xml
+++ b/documentation/ref-manual/faq.xml
@@ -351,13 +351,20 @@
         </question>
         <answer>
             <para>
-                If the same build is failing in totally different and random ways,
-                the most likely explanation is that either the hardware you're running the
-                build on has some problem, or, if you are running the build under virtualisation,
-                the virtualisation probably has bugs.
-                The OpenEmbedded build system processes a massive amount of data causing lots of network, disk and
-                CPU activity and is sensitive to even single bit failures in any of these areas.
-                True random failures have always been traced back to hardware or virtualisation issues.
+                If the same build is failing in totally different and random 
+                ways, the most likely explanation is:
+                <itemizedlist>
+                    <listitem><para>The hardware you are running the build on 
+                        has some problem.</para></listitem>
+                    <listitem><para>You are running the build under 
+                        virtualization, in which case the virtualization 
+                        probably has bugs.</para></listitem>   
+                </itemizedlist>
+                The OpenEmbedded build system processes a massive amount of 
+                data that causes lots of network, disk and CPU activity and 
+                is sensitive to even single-bit failures in any of these areas.
+                True random failures have always been traced back to hardware 
+                or virtualiZation issues.
             </para>
         </answer>
     </qandaentry>