Fix another class of command

9 files changed, 30 insertions, 30 deletions

diff --git a/docs/bsd/freebsd.md b/docs/bsd/freebsd.md
index bf364dcb..c0eae1dd 100644
--- a/docs/bsd/freebsd.md
+++ b/docs/bsd/freebsd.md
@@ -64,7 +64,7 @@ how to create the bootable FreeBSD USB drive:
 Connect the USB drive. Check dmesg:\
     $ dmesg | tail
 Check to confirm which drive it is, for example, if you think its sd3:\
-**$ disklabel sd3**
+    $ disklabel sd3
 
 Check that it wasn't automatically mounted. If it was, unmount it. For
 example:\
@@ -87,7 +87,7 @@ the bootable FreeBSD USB drive:
 Connect the USB drive. Check dmesg:\
     $ dmesg
 Check lsblk to confirm which drive it is:\
-**$ lsblk**
+    $ lsblk
 
 Check that it wasn't automatically mounted. If it was, unmount it. For
 example:\
diff --git a/docs/bsd/netbsd.md b/docs/bsd/netbsd.md
index 7d107c44..b6700641 100644
--- a/docs/bsd/netbsd.md
+++ b/docs/bsd/netbsd.md
@@ -60,7 +60,7 @@ to create the bootable NetBSD USB drive:
 Connect the USB drive. Check dmesg:\
     $ dmesg | tail
 Check to confirm which drive it is, for example, if you think its sd3:\
-**$ disklabel sd3**
+    $ disklabel sd3
 
 Check that it wasn't automatically mounted. If it was, unmount it. For
 example:\
@@ -83,7 +83,7 @@ the bootable NetBSD USB drive:
 Connect the USB drive. Check dmesg:\
     $ dmesg
 Check lsblk to confirm which drive it is:\
-**$ lsblk**
+    $ lsblk
 
 Check that it wasn't automatically mounted. If it was, unmount it. For
 example:\
diff --git a/docs/bsd/openbsd.md b/docs/bsd/openbsd.md
index 93ed01e7..7cf22ac4 100644
--- a/docs/bsd/openbsd.md
+++ b/docs/bsd/openbsd.md
@@ -42,7 +42,7 @@ how to create the bootable LibertyBSD/OpenBSD USB drive:
 Connect the USB drive. Check dmesg:\
     $ dmesg | tail
 Check to confirm which drive it is, for example, if you think its sd3:\
-**$ disklabel sd3**
+    $ disklabel sd3
 
 Check that it wasn't automatically mounted. If it was, unmount it. For
 example:\
@@ -82,7 +82,7 @@ the bootable OpenBSD USB drive:
 Connect the USB drive. Check dmesg:\
     $ dmesg
 Check lsblk to confirm which drive it is:\
-**$ lsblk**
+    $ lsblk
 
 Check that it wasn't automatically mounted. If it was, unmount it. For
 example:\
diff --git a/docs/future/index.md b/docs/future/index.md
index 94453e55..fd9aaeaa 100644
--- a/docs/future/index.md
+++ b/docs/future/index.md
@@ -326,7 +326,7 @@ Get intelvbttool here: <http://review.coreboot.org/#/c/5842>
 Now dump a copy of the running VGA BIOS: **$ sudo dd if=/dev/mem bs=64k
 of=runningvga.bin skip=12 count=1**\
 Then do (and record the output):\
-**$ ./intelvbttool runningvga.bin > intelvbttool\_out**
+    $ ./intelvbttool runningvga.bin > intelvbttool\_out
 
 Backup both files (runningvga.bin and intelvbttool\_out), renaming them
 to match the system and LCD panel used.
diff --git a/docs/gnulinux/grub_boot_installer.md b/docs/gnulinux/grub_boot_installer.md
index 8fa8dcb6..f0ad1de4 100644
--- a/docs/gnulinux/grub_boot_installer.md
+++ b/docs/gnulinux/grub_boot_installer.md
@@ -33,7 +33,7 @@ to create the bootable GNU+Linux USB drive:
 Connect the USB drive. Check dmesg:\
     $ dmesg
 Check lsblk to confirm which drive it is:\
-**$ lsblk**
+    $ lsblk
 
 Check that it wasn't automatically mounted. If it was, unmount it. For
 example:\
@@ -75,7 +75,7 @@ how to create the bootable GNU+Linux USB drive:
 Connect the USB drive. Check dmesg:\
     $ dmesg | tail
 Check to confirm which drive it is, for example, if you think its sd3:\
-**$ disklabel sd3**
+    $ disklabel sd3
 
 Check that it wasn't automatically mounted. If it was, unmount it. For
 example:\
diff --git a/docs/gnulinux/grub_cbfs.md b/docs/gnulinux/grub_cbfs.md
index 7b7c4cf3..7bba7730 100644
--- a/docs/gnulinux/grub_cbfs.md
+++ b/docs/gnulinux/grub_cbfs.md
@@ -155,7 +155,7 @@ Extract grubtest.cfg from the ROM image {#extract_testconfig}
 ---------------------------------------
 
 You can check the contents of the ROM image, inside CBFS:\
-**$ cd \.../libreboot\_util/cbfstool** **$ ./cbfstool libreboot.rom
+    $ cd \.../libreboot\_util/cbfstool** $ ./cbfstool libreboot.rom
 print**
 
 The files *grub.cfg* and *grubtest.cfg* should be present. grub.cfg is
@@ -164,7 +164,7 @@ this tutorial, you will first modify and test *grubtest.cfg*. This is to
 reduce the possibility of bricking your device, so DO NOT SKIP THIS!
 
 Extract grubtest.cfg from the ROM image:\
-**$ ./cbfstool libreboot.rom extract -n grubtest.cfg -f grubtest.cfg**
+    $ ./cbfstool libreboot.rom extract -n grubtest.cfg -f grubtest.cfg
 
 Modify the grubtest.cfg accordingly.
 
@@ -177,7 +177,7 @@ Re-insert the modified grubtest.cfg into the ROM image {#reinsert_modified_testc
 
 Once your grubtest.cfg is modified and saved, delete the unmodified
 config from the ROM image:\
-**$ ./cbfstool libreboot.rom remove -n grubtest.cfg**
+    $ ./cbfstool libreboot.rom remove -n grubtest.cfg
 
 Next, insert the modified version:\
 **$ ./cbfstool libreboot.rom add -n grubtest.cfg -f grubtest.cfg -t
@@ -230,10 +230,10 @@ $ **sed -e 's:(cbfsdisk)/grub.cfg:(cbfsdisk)/grubtest.cfg:g' -e
 grub.cfg**\
 
 Delete the grub.cfg that remained inside the ROM:\
-**$ ./cbfstool libreboot.rom remove -n grub.cfg**
+    $ ./cbfstool libreboot.rom remove -n grub.cfg
 
 Add the modified version that you just made:\
-**$ ./cbfstool libreboot.rom add -n grub.cfg -f grub.cfg -t raw**
+    $ ./cbfstool libreboot.rom add -n grub.cfg -f grub.cfg -t raw
 
 **Now you have a modified ROM. Again, refer back to
 [../install/#flashrom](../install/#flashrom) for information on how to
diff --git a/docs/grub/index.md b/docs/grub/index.md
index 3f509179..6b1eb7f8 100644
--- a/docs/grub/index.md
+++ b/docs/grub/index.md
@@ -50,7 +50,7 @@ like Debian, Devuan or Parabola.
     $ cd libreboot\_src/grub
 compile grub (the build scripts info on how to do this)\
 come back out into libreboot\_src/resources/grub:\
-**$ cd ../libreboot\_src/resources/grub/font**
+    $ cd ../libreboot\_src/resources/grub/font
 
 I took Dejavu Sans Mono from dejavu (included in this version of
 libreboot) and did:\
@@ -104,7 +104,7 @@ ukdvorak had to be created manually, based on usdvorak. diff them (under
 resources/utilities/grub-assemble/keymap/original) to see how ukdvorak
 file was created
 
-**$ cat ukdvorak | ./grub/grub-mklayout -o ukdvorak.gkb**
+    $ cat ukdvorak | ./grub/grub-mklayout -o ukdvorak.gkb
 
 
 
diff --git a/docs/misc/index.md b/docs/misc/index.md
index c012ce99..232a9b98 100644
--- a/docs/misc/index.md
+++ b/docs/misc/index.md
@@ -59,7 +59,7 @@ when idle. So far we have use processor.max\_cstate=2 or idle=halt in
 GRUB. These consume power. Stop using them!
 
 Be root\
-**$ su -**
+    $ su -
 
 Installed powertop:\
 **# pacman -S powertop**
@@ -108,7 +108,7 @@ port on the dock and connect the other end to a 2nd system using your
 USB Serial adapter.
 
 On the 2nd system, you can try this (using GNU Screen):\
-**$ sudo screen /dev/ttyUSB0 115200**
+    $ sudo screen /dev/ttyUSB0 115200
 
 How to quit GNU Screen: Ctrl+A then release and press K, and then press
 Y.
diff --git a/docs/misc/patch.md b/docs/misc/patch.md
index 00454a79..43c35382 100644
--- a/docs/misc/patch.md
+++ b/docs/misc/patch.md
@@ -12,11 +12,11 @@ Apply a patch
 =============
 
 To apply a patch to a single file, do that in it's directory:\
-**$ patch < foo.patch**
+    $ patch < foo.patch
 
 Assuming that the patch is distributed in unified format identifying the
 file the patch should be applied to, the above will work. Otherwise:\
-**$ patch foo.txt < bar.patch**
+    $ patch foo.txt < bar.patch
 
 You can apply a patch to an entire directory, but note the "p level".
 What this means is that inside patch files will be the files that you
@@ -25,7 +25,7 @@ the files ane located on your own computer instead of on the computer
 where the patch was created. 'p' level instructs the 'patch' utility
 to ignore parts of the path name to identify the files correctly.
 Usually a p level of 1 will work, so you would use:\
-**$ patch -p1 < baz.patch**
+    $ patch -p1 < baz.patch
 
 Change to the top level directory before running this. If a patch level
 of 1 cannot identify the files to patch, then inspect the patch file for
@@ -33,14 +33,14 @@ file names. For example:\
 **/home/user/do/not/panic/yet.c**
 
 and you are working in a directory that contains panic/yet.c, use:\
-**$ patch -p5 < baz.patch**
+    $ patch -p5 < baz.patch
 
 You usually count one up for each path separator (forward slash) removed
 from the beginning of the path, until you are left with a path that
 exists in the current working directory. The count is the p level.
 
 Removing a patch using the -R flag\
-**$ patch -p5 -R < baz.patch**
+    $ patch -p5 -R < baz.patch
 
 [Back to top of page.](#pagetop)
 
@@ -50,13 +50,13 @@ Create a patch with diff
 ========================
 
 Diff can create a patch for a single file:\
-**$ diff -u original.c new.c > original.patch**
+    $ diff -u original.c new.c > original.patch
 
 For diff'ing a source tree:\
-**$ cp -R original new**
+    $ cp -R original new
 
 Do whatever you want in new/ and then diff it:\
-**$ diff -rupN original/ new/ > original.patch**
+    $ diff -rupN original/ new/ > original.patch
 
 [Back to top of page.](#pagetop)
 
@@ -70,10 +70,10 @@ git is something special.
 Note: this won't show new files created.
 
 Just make whatever changes you want to a git clone and then:\
-**$ git diff > patch.git**
+    $ git diff > patch.git
 
 Note the git revision that you did this with:\
-**$ git log**
+    $ git log
 
 Alternatively (better yet), commit your changes and then use:\
     $ git format-patch -N
@@ -90,10 +90,10 @@ it really is.
 
 Now to apply that patch in the future, just git clone it again and do
 with the git revision you found from above:\
-**$ git reset \--hard REVISIONNUMBER**
+    $ git reset \--hard REVISIONNUMBER
 
 Now put patch.git in the git clone directory and do:\
-**$ git apply patch.git**
+    $ git apply patch.git
 
 If you use a patch from git format-patch, then use **git am patch.git**
 instead of **git apply patch.git**. git-am will re-create the commits