Clarifications to README file

Clarify the instructions for recording test results and tidy formatting.
Signed-off-by: Grant Likely <grant.likely@arm.com>

README.md

+# Template Structure for SystemReady Compliance Reports
+
+This repo structure is the template for collecting compliance evidence for a
+SystemReady certification.
+
+## General Instructions
+
 General instructions for collecting SystemReady compliance logs:
 
 ./report.txt
     Fill in with information about the system being certified
 
+./acs
+    If using serial console, capture a full console log from first power on
+    until completion of ACS tests. Must include all output from firmware.
+    Should end at a Linux busybox shell prompt after running FWTS tests.
 
 ./acs/acs-results
-    Place an entire copy of the 'LUV-Results' or 'acs-results' partitions, as  follows:
+    Place an entire copy of the 'LUV-Results' or 'acs-results' partitions, as
+    follows:
+
         For Enterprise ACS, under the 'LUV-Results' partition:
             /luv-results-<date>
             /sbsa_results
@@ -22,7 +35,6 @@ General instructions for collecting SystemReady compliance logs:
             /uefi
             /uefi_dump
 
-
 ./acs/bsa-linux
 
     Place any BSA or SBSA results collected manually, from UEFI or Linux.
@@ -31,7 +43,8 @@ General instructions for collecting SystemReady compliance logs:
 
     Enterprise-ACS:
 
-        SBSA Linux results can be collected by running the following commands after booting LUVOS
+        SBSA Linux results can be collected by running the following commands
+        after booting LUVOS:
             insmod /lib/modules/4.18.0-luv/extra/sbsa_acs.ko
             sbsa -l 3
 
@@ -41,9 +54,6 @@ General instructions for collecting SystemReady compliance logs:
         To skip a specific problematic test, use -skip <testnum>. For example:
             sbsa -l 3 -v 2 -skip 20,36
 
-
-
-
 ./acs/bsa-uefi
 
     Place any BSA or SBSA results collected manually from UEFI Shell
@@ -52,8 +62,9 @@ General instructions for collecting SystemReady compliance logs:
 
     Enterprise-ACS
 
-        SBSA UEFI results can be collected by running the following commands after booting LUVOS:
-        sbsa.efi -l 3
+        SBSA UEFI results can be collected by running the following commands
+        after booting LUVOS:
+            sbsa.efi -l 3
 
         You can include verbose output (-v):
             sbsa.efi -l 3 -v 2
@@ -61,13 +72,10 @@ General instructions for collecting SystemReady compliance logs:
         To skip a specific problematic test, use -skip <testnum>
             sbsa.efi -l 3 -v 2 -skip 407
 
-
-
 ./acs/fwts
     Place any additional FWTS results collected manually by running:
         fwts -r stdout -q –sbbr
 
-
 ./acs/sct
     Place any additional SCT results collected manually
         FS2:\SCT>SCT.efi -a –v
@@ -83,9 +91,10 @@ General instructions for collecting SystemReady compliance logs:
 ./fw
     ./fw/screenshots
 
-        Place some screenshots showing the FW menus (such as UEFI Setup, BMC web console, uboot shell)
+        Place some screenshots showing the FW menus (such as UEFI Setup, BMC
+        web console, uboot shell)
 
-    ./fw/uboot
+    ./fw/u-boot
 
         Run the following commands at U-Boot prompt and attach the logs:
             u-boot=> help
@@ -112,7 +121,10 @@ General instructions for collecting SystemReady compliance logs:
 
 
     ./fw/uefi_shell
-        Run the following commands in UEFI Shell and attach the logs (if not already done by ACS):
+        Run the following commands in UEFI Shell and attach the logs (if not
+        already done by ACS). The UEFI Shell can be run from the ACS image by
+        pressing a key at the UEFI timeout prompt before tests begin to
+        execute.
             Shell> pci
             Shell> drivers
             Shell> devices
@@ -129,15 +141,21 @@ General instructions for collecting SystemReady compliance logs:
             Shell> CapsuleApp.efi -P
             Shell> CapsuleApp.efi -E
 
-
 ./os_logs
 
-    ./os_logs/linux_distro_1
-    ./os_logs/linux_distro_2
+    ./os_logs/linux_[distroname]_[distroversion]
+
+        Create a directory for each Linux distro used for testing.
 
         Install the OS to a disk, and boot it.
-        Collect the installation and OS boot logs and save in a text file.
-        Run the following commands and attach the logs:
+        Collect the installation and OS boot logs and save in single text file.
+        The install log must begin when the platform is released from reset and
+        must include:
+        - all firmware output
+        - output from Linux installer
+        - reboot into installed OS.
+        - Output of following commands from Linux shell:
+
             dmesg
             lspci -vvv
             lscpu
@@ -147,7 +165,6 @@ General instructions for collecting SystemReady compliance logs:
             efibootmgr
             copy the entire content of /sys/firmware and attach zipped/archive file
 
-
     ./os_logs/esxi
 
         Install VMWare ESXi to a disk, and boot it
@@ -171,6 +188,3 @@ General instructions for collecting SystemReady compliance logs:
             pnputil/enum-drivers
             Systeminfo
             ver
-
-
-