Cleanup docs/install

1 files changed, 16 insertions, 22 deletions

diff --git a/docs/install/index.md b/docs/install/index.md
index 5a4b641a..5d9ba5c3 100644
--- a/docs/install/index.md
+++ b/docs/install/index.md
@@ -4,10 +4,10 @@ title: Installation instructions
 
 This section relates to installing Libreboot on supported targets.
 
-**NOTE: if running flashrom -p internal for software based flashing, and
-you get an error related to /dev/mem access, you should reboot with
-iomem=relaxed kernel parameter before running flashrom, or use a kernel
-that has CONFIG\_STRICT\_DEVMEM not enabled.**
+**NOTE: if running flashrom -p internal for software based flashing, and you
+get an error related to `/dev/mem` access, you should reboot with
+`iomem=relaxed` kernel parameter before running flashrom, or use a kernel that
+has `CONFIG_STRICT_DEVMEM` not enabled.**
 
 Which systems are Libreboot compatible with?
 --------------------------------------------
@@ -28,14 +28,11 @@ Flashing via software methods, on system:
 -   [Apple MacBook2,1](#flashrom_macbook21)
 -   [ASUS Chromebook C201](c201.md)
 
-Setting up programmers, for external flashing via hardware method
+Setting up programmers, for external SPI flashing 
 -----------------------------------------------------------------
 
--   [How to program an SPI flash chip with the BeagleBone
-    Black](bbb_setup.md)
-
--   [How to program an SPI flash chip with the Raspberry
-    Pi](rpi_setup.md)
+-   [BeagleBone Black Setup](bbb_setup.md)
+-   [Raspberry Pi Setup](rpi_setup.md)
 
 Flashing via hardware methods, on system:
 -----------------------------------------
@@ -63,15 +60,14 @@ source code. These images are provided for user convenience, so that
 they don't have to build anything from source on their own.
 
 The ROM images in each archive use the following at the end of the file
-name, if they are built with the GRUB payload:
-**\_*keymap*\_*mode*.rom**
+name, if they are built with the GRUB payload: `*_*keymap*_*mode*.rom`
 
-Available *modes*: **vesafb** or **txtmode**. The *vesafb* ROM images
-are recommended, in most cases; *txtmode* ROM images come with
+Available `modes`: `vesafb` or `txtmode`. The `vesafb` ROM images
+are recommended, in most cases; `txtmode` ROM images come with
 MemTest86+, which requires text-mode instead of the usual framebuffer
 used by coreboot native graphics initialization.
 
-*keymap* can be one of several keymaps that keyboard supports (there are
+`keymap` can be one of several keymaps that keyboard supports (there are
 quite a few), which affects the keyboard layout configuration that is
 used in GRUB. It doesn't matter which ROM image you choose here, as far
 as the keymap in GNU+Linux is concerned.
@@ -87,12 +83,10 @@ 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\_q35\_ich9\_keymap\_mode.rom**
--   \$ **qemu-system-i386 -M pc -m 512 -bios
-    qemu\_i440fx\_piix4\_keymap\_mode.rom**
+    $ qemu-system-i386 -M q35 -m 512 -bios qemu_q35_ich9_keymap_mode.rom
+    $ 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
+You can optionally specify the `-serial stdio` argument, so that QEMU
 will emulate a serial terminal on the standard input/output (most likely
 your terminal emulator or TTY).
 
@@ -108,8 +102,8 @@ any dedicated hardware. In other words, you can do everything entirely
 in software, directly from the OS that is running on your libreboot
 system.
 
-**If you are using libreboot\_src or git, then make sure that you built
-the sources first (see [../git/\#build](../git/#build)).**
+**If you are using `libreboot_src` or git, then make sure that you built the
+sources first (see [../git/\#build](../git/#build)).**
 
 Look at the [list of ROM images](#rom) to see which image is compatible
 with your device.