Begin descent from weird command line syntax

7 files changed, 24 insertions, 24 deletions

diff --git a/docs/install/bbb_setup.md b/docs/install/bbb_setup.md
index aa03b85d..244bd8e0 100644
--- a/docs/install/bbb_setup.md
+++ b/docs/install/bbb_setup.md
@@ -158,7 +158,7 @@ Alternatives to SSH (in case SSH fails)
 
 You can also use a serial FTDI debug board with GNU Screen, to access
 the serial console.\
-\# **screen /dev/ttyUSB0 115200**\
+\#     screen /dev/ttyUSB0 115200
 Here are some example photos:\
 ![](images/x200/ftdi.jpg) ![](images/x200/ftdi_port.jpg)\
 
@@ -211,14 +211,14 @@ contents of this file with:
 Run **apt-get update** and **apt-get upgrade** then reboot the BBB,
 before continuing.
 Check that the firmware exists:\
-\# **ls /lib/firmware/BB-SPI0-01-00A0.***\
+\#     ls /lib/firmware/BB-SPI0-01-00A0.*
 Output:
 
     /lib/firmware/BB-SPI0-01-00A0.dtbo
 
 Then:\
-\# **echo BB-SPI0-01 > /sys/devices/bone\_capemgr.*/slots**\
-\# **cat /sys/devices/bone\_capemgr.*/slots**\
+\#     echo BB-SPI0-01 > /sys/devices/bone\_capemgr.*/slots
+\#     cat /sys/devices/bone\_capemgr.*/slots
 Output:
 
      0: 54:PF--- 
@@ -230,7 +230,7 @@ Output:
      7: ff:P-O-L Override Board Name,00A0,Override Manuf,BB-SPI0-01
 
 Verify that the spidev device now exists:\
-\# **ls -al /dev/spid***\
+\#     ls -al /dev/spid*
 Output:
 
     crw-rw---T 1 root spi 153, 0 Nov 19 21:07 /dev/spidev1.0
@@ -253,7 +253,7 @@ Finally, get the ROM image that you would like to flash and put that on
 your BBB.
 
 Now test flashrom:\
-\# **./flashrom -p linux\_spi:dev=/dev/spidev1.0,spispeed=512**\
+\#     ./flashrom -p linux\_spi:dev=/dev/spidev1.0,spispeed=512
 Output:
 
     Calibrating delay loop... OK.
diff --git a/docs/install/c201.md b/docs/install/c201.md
index d04ba2b0..da6e3499 100644
--- a/docs/install/c201.md
+++ b/docs/install/c201.md
@@ -148,20 +148,20 @@ transferred to the device.
 The following operations have to be executed with root privileges on the
 device (e.g. using the *root* account). In addition, the
 **cros-flash-replace** script has to be made executable:\
-\# **chmod a+x cros-flash-replace**\
+\#     chmod a+x cros-flash-replace
 
 The SPI flash has to be read first:\
-\# **flashrom -p host -r flash.img**\
+\#     flashrom -p host -r flash.img
 **Note: it might be a good idea to copy the produced flash.img file at
 this point and store it outside of the device for backup purposes.**
 
 Then, the **cros-flash-replace** script has to be executed as such:\
-\# **./cros-flash-replace flash.img coreboot ro-frid**\
+\#     ./cros-flash-replace flash.img coreboot ro-frid
 If any error is shown, it is definitely a bad idea to go further than
 this point.
 
 The resulting flash image can then be flashed back:\
-\# **flashrom -p host -w flash.img**\
+\#     flashrom -p host -w flash.img
 
 You should also see within the output the following:\
 **"Verifying flash\... VERIFIED."**
@@ -195,21 +195,21 @@ transferred to the host.
 The following operations have to be executed with root privileges on the
 host (e.g. using the *root* account). In addition, the
 **cros-flash-replace** script has to be made executable:\
-\# **chmod a+x cros-flash-replace**\
+\#     chmod a+x cros-flash-replace
 
 The SPI flash has to be read first (using the right spi programmer):\
-\# **flashrom -p *programmer* -r flash.img**\
+\#     flashrom -p *programmer* -r flash.img
 **Note: it might be a good idea to copy the produced flash.img file at
 this point and store it outside of the device for backup purposes.**
 
 Then, the **cros-flash-replace** script has to be executed as such:\
-\# **./cros-flash-replace flash.img coreboot ro-frid**\
+\#     ./cros-flash-replace flash.img coreboot ro-frid
 If any error is shown, it is definitely a bad idea to go further than
 this point.
 
 The resulting flash image can then be flashed back (using the right spi
 programmer):\
-\# **flashrom -p *programmer* -w flash.img**\
+\#     flashrom -p *programmer* -w flash.img
 
 You should also see within the output the following:\
 **"Verifying flash\... VERIFIED."**
diff --git a/docs/install/index.md b/docs/install/index.md
index fd988dfa..ac59f60d 100644
--- a/docs/install/index.md
+++ b/docs/install/index.md
@@ -330,7 +330,7 @@ are swapped"**.
 
 You should also see within the output the following:\
 **"Your flash chip is in an unknown state"**, **"FAILED"** and
-**"DO NOT REBOOT OR POWEROFF"**\
+    "DO NOT REBOOT OR POWEROFF"
 Seeing this means that the operation was a **resounding** success!
 **DON'T PANIC**.
 
diff --git a/docs/install/r400_external.md b/docs/install/r400_external.md
index 21303e01..19f3a5fd 100644
--- a/docs/install/r400_external.md
+++ b/docs/install/r400_external.md
@@ -73,7 +73,7 @@ Flash chip size {#flashchips}
 ===============
 
 Use this to find out:\
-\# **flashrom -p internal -V**\
+\#     flashrom -p internal -V
 
 [Back to top of page.](#pagetop)
 
@@ -231,7 +231,7 @@ Log in as root on your BBB, using the instructions in
 [bbb\_setup.html\#bbb\_access](bbb_setup.html#bbb_access).
 
 Test that flashrom works:\
-\# **./flashrom -p linux\_spi:dev=/dev/spidev1.0,spispeed=512**\
+\#     ./flashrom -p linux\_spi:dev=/dev/spidev1.0,spispeed=512
 In this case, the output was:
 
     flashrom v0.9.7-r1854 on Linux 3.8.13-bone47 (armv7l)
@@ -255,7 +255,7 @@ Note: the **-c** option is not required in libreboot's patched
 flashrom, because the redundant flash chip definitions in *flashchips.c*
 have been removed.\
 Now compare the 3 images:\
-\# **sha512sum factory*.rom**\
+\#     sha512sum factory*.rom
 If the hashes match, then just copy one of them (the factory.rom) to a
 safe place (on a drive connected to another system, not the BBB). This
 is useful for reverse engineering work, if there is a desirable
diff --git a/docs/install/t400_external.md b/docs/install/t400_external.md
index 014ace48..1d9ea3ed 100644
--- a/docs/install/t400_external.md
+++ b/docs/install/t400_external.md
@@ -237,7 +237,7 @@ Log in as root on your BBB, using the instructions in
 [bbb\_setup.html\#bbb\_access](bbb_setup.html#bbb_access).
 
 Test that flashrom works:\
-\# **./flashrom -p linux\_spi:dev=/dev/spidev1.0,spispeed=512**\
+\#     ./flashrom -p linux\_spi:dev=/dev/spidev1.0,spispeed=512
 In this case, the output was:
 
     flashrom v0.9.7-r1854 on Linux 3.8.13-bone47 (armv7l)
@@ -261,7 +261,7 @@ Note: the **-c** option is not required in libreboot's patched
 flashrom, because the redundant flash chip definitions in *flashchips.c*
 have been removed.\
 Now compare the 3 images:\
-\# **sha512sum factory*.rom**\
+\#     sha512sum factory*.rom
 If the hashes match, then just copy one of them (the factory.rom) to a
 safe place (on a drive connected to another system, not the BBB). This
 is useful for reverse engineering work, if there is a desirable
diff --git a/docs/install/t500_external.md b/docs/install/t500_external.md
index 83524252..e49886ec 100644
--- a/docs/install/t500_external.md
+++ b/docs/install/t500_external.md
@@ -242,7 +242,7 @@ Log in as root on your BBB, using the instructions in
 [bbb\_setup.html\#bbb\_access](bbb_setup.html#bbb_access).
 
 Test that flashrom works:\
-\# **./flashrom -p linux\_spi:dev=/dev/spidev1.0,spispeed=512**\
+\#     ./flashrom -p linux\_spi:dev=/dev/spidev1.0,spispeed=512
 In this case, the output was:
 
     flashrom v0.9.7-r1854 on Linux 3.8.13-bone47 (armv7l)
@@ -266,7 +266,7 @@ Note: the **-c** option is not required in libreboot's patched
 flashrom, because the redundant flash chip definitions in *flashchips.c*
 have been removed.\
 Now compare the 3 images:\
-\# **sha512sum factory*.rom**\
+\#     sha512sum factory*.rom
 If the hashes match, then just copy one of them (the factory.rom) to a
 safe place (on a drive connected to another system, not the BBB). This
 is useful for reverse engineering work, if there is a desirable
diff --git a/docs/install/x200_external.md b/docs/install/x200_external.md
index 3146c2e7..128f80af 100644
--- a/docs/install/x200_external.md
+++ b/docs/install/x200_external.md
@@ -171,7 +171,7 @@ Log in as root on your BBB, using the instructions in
 [bbb\_setup.html\#bbb\_access](bbb_setup.html#bbb_access).
 
 Test that flashrom works:\
-\# **./flashrom -p linux\_spi:dev=/dev/spidev1.0,spispeed=512**\
+\#     ./flashrom -p linux\_spi:dev=/dev/spidev1.0,spispeed=512
 In this case, the output was:
 
     flashrom v0.9.7-r1854 on Linux 3.8.13-bone47 (armv7l)
@@ -195,7 +195,7 @@ Note: the **-c** option is not required in libreboot's patched
 flashrom, because the redundant flash chip definitions in *flashchips.c*
 have been removed.\
 Now compare the 3 images:\
-\# **sha512sum factory*.rom**\
+\#     sha512sum factory*.rom
 If the hashes match, then just copy one of them (the factory.rom) to a
 safe place (on a drive connected to another system, not the BBB). This
 is useful for reverse engineering work, if there is a desirable