Cleanup some escaped symbols

10 files changed, 42 insertions, 42 deletions

diff --git a/docs/install/bbb_setup.md b/docs/install/bbb_setup.md
index 03882956..aa03b85d 100644
--- a/docs/install/bbb_setup.md
+++ b/docs/install/bbb_setup.md
@@ -119,10 +119,10 @@ Short PS\_ON\# / Power on (green wire; pin 16 on 24-pin ATX PSU, or pin
 it) using a wire/paperclip/jumper, then power on the PSU by grounding
 PS\_ON\# (this is also how an ATX motherboard turns on a PSU).
 
-**DO \*\*NOT\*\* use pin 4, 6, do \*\*NOT\*\* use pin 19 or 20 (on a
-20-pin ATX PSU), and DO \*\*NOT\*\* use pin 21, 22 or 23 (on a 24-pin
-ATX PSU). Those wires (the red ones) are 5V, and they \*\*WILL\*\* kill
-your flash chip. \*\*\*NEVER\*\*\* supply more than 3.3V to your flash
+**DO **NOT** use pin 4, 6, do **NOT** use pin 19 or 20 (on a
+20-pin ATX PSU), and DO **NOT** use pin 21, 22 or 23 (on a 24-pin
+ATX PSU). Those wires (the red ones) are 5V, and they **WILL** kill
+your flash chip. ***NEVER*** supply more than 3.3V to your flash
 chip (that is, if it's a 3.3V flash chip; 5V and 1.8V SPI flash chips
 do exist, but they are rare. Always check what voltage your chip takes.
 Most of them take 3.3V).**
@@ -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
diff --git a/docs/install/index.md b/docs/install/index.md
index 0e8b7ea9..d6d37b3d 100644
--- a/docs/install/index.md
+++ b/docs/install/index.md
@@ -86,9 +86,9 @@ Libreboot comes with ROM images built for QEMU, by default:
 
 Examples of how to use libreboot ROM images in QEMU:
 
--   \$ **qemu-system-i386 -M q35 -m 512 -bios
+-   $ **qemu-system-i386 -M q35 -m 512 -bios
     qemu\_q35\_ich9\_keymap\_mode.rom**
--   \$ **qemu-system-i386 -M pc -m 512 -bios
+-   $ **qemu-system-i386 -M pc -m 512 -bios
     qemu\_i440fx\_piix4\_keymap\_mode.rom**
 
 You can optionally specify the **-serial stdio** argument, so that QEMU
@@ -274,14 +274,14 @@ executables from the libreboot source code archives.
 
 
 How to update the flash chip contents:\
-\$ **sudo ./flash update [yourrom.rom](#rom)**
+$ **sudo ./flash update [yourrom.rom](#rom)**
 
 
 
 Ocassionally, coreboot changes the name of a given board. If flashrom
 complains about a board mismatch, but you are sure that you chose the
 correct ROM image, then run this alternative command:\
-\$ **sudo ./flash forceupdate [yourrom.rom](#rom)**
+$ **sudo ./flash forceupdate [yourrom.rom](#rom)**
 
 
 
@@ -321,7 +321,7 @@ https://notabug.org/vimuser/libreboot/raw/9d850543ad90b72e0e333c98075530b31e5d23
 && chmod +x flash***
 
 The first half of the procedure is as follows:\
-\$ **sudo ./flash i945lenovo\_firstflash [yourrom.rom](#rom).**
+$ **sudo ./flash i945lenovo\_firstflash [yourrom.rom](#rom).**
 
 
 
@@ -340,15 +340,15 @@ See this link for more details:
 
 If the above is what you see, then **SHUT DOWN**. Wait a few seconds,
 and then boot; libreboot is running, but there is a 2nd procedure
-**\*needed\*** (see below).
+***needed*** (see below).
 
 
 
 When you have booted up again, you must also do this:\
-\$ **sudo ./flash i945lenovo\_secondflash [yourrom.rom](#rom)**
+$ **sudo ./flash i945lenovo\_secondflash [yourrom.rom](#rom)**
 
 If flashing fails at this stage, try the following:\
-\$ **sudo ./flashrom/i686/flashrom -p
+$ **sudo ./flashrom/i686/flashrom -p
 internal:laptop=force\_I\_want\_a\_brick -w [yourrom.rom](#rom)**
 
 
@@ -394,7 +394,7 @@ with your device.
 
 
 Use this flashing script, to install libreboot:\
-\$ **sudo ./flash i945apple\_firstflash [yourrom.rom](#rom)**
+$ **sudo ./flash i945apple\_firstflash [yourrom.rom](#rom)**
 
 
 
diff --git a/docs/install/r400_external.md b/docs/install/r400_external.md
index 1c8e9c83..21303e01 100644
--- a/docs/install/r400_external.md
+++ b/docs/install/r400_external.md
@@ -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/rpi_setup.md b/docs/install/rpi_setup.md
index 21c8a4fc..f3cbcb5a 100644
--- a/docs/install/rpi_setup.md
+++ b/docs/install/rpi_setup.md
@@ -18,7 +18,7 @@ SOIC-16).
 [](#raspberry-pi-thinkpad-x60t60-and-macbook-21){#user-content-raspberry-pi-thinkpad-x60t60-and-macbook-21 .anchor}Raspberry Pi (ThinkPad X60/T60 and Macbook 2,1)
 ------------------------------------------------------------------------------------------------------------------------------------------------------------------
 
-The Raspberry Pi (a multipurpose \$25 GNU+Linux computer) can be used as
+The Raspberry Pi (a multipurpose $25 GNU+Linux computer) can be used as
 a BIOS flashing tool, thanks to its GPIO pins and SPI support.
 
 > **Note:** The Raspberry Pi Model A is not supported, since it has no
@@ -351,13 +351,13 @@ for great good!
 [](#raspberry-pi-c720-chromebook){#user-content-raspberry-pi-c720-chromebook .anchor}Raspberry Pi (C720 Chromebook)
 -------------------------------------------------------------------------------------------------------------------
 
-The Raspberry Pi (a multipurpose \$25 GNU+Linux computer) can be used as
+The Raspberry Pi (a multipurpose $25 GNU+Linux computer) can be used as
 a BIOS flashing tool, thanks to its GPIO pins and SPI support.
 
 ### [](#what-you-need){#user-content-what-you-need .anchor}What you need
 
--   \$25 - Raspberry Pi Model B (Rev.2 or higher)
--   \$10-20 - SOIC-8 Pomona Clip
+-   $25 - Raspberry Pi Model B (Rev.2 or higher)
+-   $10-20 - SOIC-8 Pomona Clip
     -   Usually comes bundled with nice, color-colored *female to
         female* wires
 
@@ -367,8 +367,8 @@ GPIO Pinouts:
 
 ![](images/rpi/0009.png) ![](images/rpi/0010.png)
 
-> \*Diagram made by ["Pacman" from Win-Raid
-> Forums\*](http://www.win-raid.com/t58f16-Guide-Recover-from-failed-BIOS-flash-using-Raspberry-PI.html)
+> *Diagram made by ["Pacman" from Win-Raid
+> Forums*](http://www.win-raid.com/t58f16-Guide-Recover-from-failed-BIOS-flash-using-Raspberry-PI.html)
 
 SOIC Pinouts:
 
diff --git a/docs/install/t400_external.md b/docs/install/t400_external.md
index e8576284..014ace48 100644
--- a/docs/install/t400_external.md
+++ b/docs/install/t400_external.md
@@ -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 accaac32..83524252 100644
--- a/docs/install/t500_external.md
+++ b/docs/install/t500_external.md
@@ -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/t60_unbrick.md b/docs/install/t60_unbrick.md
index 47bc3d06..5ca8076a 100644
--- a/docs/install/t60_unbrick.md
+++ b/docs/install/t60_unbrick.md
@@ -23,7 +23,7 @@ Brick type 1: bucts not reset. {#bucts_brick}
 ==============================
 
 You still have Lenovo BIOS, or you had libreboot running and you flashed
-another ROM; and you had bucts 1 set and the ROM wasn't dd'd.\* or if
+another ROM; and you had bucts 1 set and the ROM wasn't dd'd.* or if
 Lenovo BIOS was present and libreboot wasn't flashed.\
 \
 In this case, unbricking is easy: reset BUC.TS to 0 by removing that
@@ -31,14 +31,14 @@ yellow cmos coin (it's a battery) and putting it back after a minute or
 two:\
 ![](../images/t60_dev/0006.JPG)\
 \
-\*Those dd commands should be applied to all newly compiled T60 ROM
+*Those dd commands should be applied to all newly compiled T60 ROM
 images (the ROM images in libreboot binary archives already have this
 applied!):\
-dd if=coreboot.rom of=top64k.bin bs=1 skip=\$\[\$(stat -c %s
+dd if=coreboot.rom of=top64k.bin bs=1 skip=$\[$(stat -c %s
 coreboot.rom) - 0x10000\] count=64k\
-dd if=coreboot.rom bs=1 skip=\$\[\$(stat -c %s coreboot.rom) - 0x20000\]
+dd if=coreboot.rom bs=1 skip=$\[$(stat -c %s coreboot.rom) - 0x20000\]
 count=64k | hexdump\
-dd if=top64k.bin of=coreboot.rom bs=1 seek=\$\[\$(stat -c %s
+dd if=top64k.bin of=coreboot.rom bs=1 seek=$\[$(stat -c %s
 coreboot.rom) - 0x20000\] count=64k conv=notrunc\
 (doing this makes the ROM suitable for use when flashing a system that
 still has Lenovo BIOS running, using those instructions:
diff --git a/docs/install/x200_external.md b/docs/install/x200_external.md
index ccfab1ae..3146c2e7 100644
--- a/docs/install/x200_external.md
+++ b/docs/install/x200_external.md
@@ -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
diff --git a/docs/install/x60_unbrick.md b/docs/install/x60_unbrick.md
index 19b1abb8..c291c584 100644
--- a/docs/install/x60_unbrick.md
+++ b/docs/install/x60_unbrick.md
@@ -23,7 +23,7 @@ Brick type 1: bucts not reset. {#bucts_brick}
 ==============================
 
 You still have Lenovo BIOS, or you had libreboot running and you flashed
-another ROM; and you had bucts 1 set and the ROM wasn't dd'd.\* or if
+another ROM; and you had bucts 1 set and the ROM wasn't dd'd.* or if
 Lenovo BIOS was present and libreboot wasn't flashed.\
 \
 In this case, unbricking is easy: reset BUC.TS to 0 by removing that
@@ -31,14 +31,14 @@ yellow cmos coin (it's a battery) and putting it back after a minute or
 two:\
 ![](../images/x60_unbrick/0004.jpg)\
 \
-\*Those dd commands should be applied to all newly compiled X60 ROM
+*Those dd commands should be applied to all newly compiled X60 ROM
 images (the ROM images in libreboot binary archives already have this
 applied!):\
-dd if=coreboot.rom of=top64k.bin bs=1 skip=\$\[\$(stat -c %s
+dd if=coreboot.rom of=top64k.bin bs=1 skip=$\[$(stat -c %s
 coreboot.rom) - 0x10000\] count=64k\
-dd if=coreboot.rom bs=1 skip=\$\[\$(stat -c %s coreboot.rom) - 0x20000\]
+dd if=coreboot.rom bs=1 skip=$\[$(stat -c %s coreboot.rom) - 0x20000\]
 count=64k | hexdump\
-dd if=top64k.bin of=coreboot.rom bs=1 seek=\$\[\$(stat -c %s
+dd if=top64k.bin of=coreboot.rom bs=1 seek=$\[$(stat -c %s
 coreboot.rom) - 0x20000\] count=64k conv=notrunc\
 (doing this makes the ROM suitable for use when flashing a system that
 still has Lenovo BIOS running, using those instructions:
diff --git a/docs/install/x60tablet_unbrick.md b/docs/install/x60tablet_unbrick.md
index b91438a1..3fd64c2b 100644
--- a/docs/install/x60tablet_unbrick.md
+++ b/docs/install/x60tablet_unbrick.md
@@ -23,7 +23,7 @@ Brick type 1: bucts not reset. {#bucts_brick}
 ==============================
 
 You still have Lenovo BIOS, or you had libreboot running and you flashed
-another ROM; and you had bucts 1 set and the ROM wasn't dd'd.\* or if
+another ROM; and you had bucts 1 set and the ROM wasn't dd'd.* or if
 Lenovo BIOS was present and libreboot wasn't flashed.\
 \
 In this case, unbricking is easy: reset BUC.TS to 0 by removing that
@@ -31,14 +31,14 @@ yellow cmos coin (it's a battery) and putting it back after a minute or
 two:\
 ![](../images/x60t_unbrick/0008.JPG)\
 \
-\*Those dd commands should be applied to all newly compiled X60 ROM
+*Those dd commands should be applied to all newly compiled X60 ROM
 images (the ROM images in libreboot binary archives already have this
 applied!):\
-dd if=coreboot.rom of=top64k.bin bs=1 skip=\$\[\$(stat -c %s
+dd if=coreboot.rom of=top64k.bin bs=1 skip=$\[$(stat -c %s
 coreboot.rom) - 0x10000\] count=64k\
-dd if=coreboot.rom bs=1 skip=\$\[\$(stat -c %s coreboot.rom) - 0x20000\]
+dd if=coreboot.rom bs=1 skip=$\[$(stat -c %s coreboot.rom) - 0x20000\]
 count=64k | hexdump\
-dd if=top64k.bin of=coreboot.rom bs=1 seek=\$\[\$(stat -c %s
+dd if=top64k.bin of=coreboot.rom bs=1 seek=$\[$(stat -c %s
 coreboot.rom) - 0x20000\] count=64k conv=notrunc\
 (doing this makes the ROM suitable for use when flashing a system that
 still has Lenovo BIOS running, using those instructions: