It wasn't me, I swear!

7 files changed, 498 insertions, 249 deletions

diff --git a/docs/gnulinux/configuring_parabola.md b/docs/gnulinux/configuring_parabola.md
index 23e22d19..23ed015f 100644
--- a/docs/gnulinux/configuring_parabola.md
+++ b/docs/gnulinux/configuring_parabola.md
@@ -96,12 +96,15 @@ careful about this when reading anything on the Arch wiki.
 
 
 Some of these steps require internet access. I'll go into networking
-later but for now, I just connected my system to a switch and did:\
+later but for now, I just connected my system to a switch and did:
+
     # systemctl start dhcpcd.service
-You can stop it later by running:\
+You can stop it later by running:
+
     # systemctl stop dhcpcd.service
 For most people this should be enough, but if you don't have DHCP on
-your network then you should setup your network connection first:\
+your network then you should setup your network connection first:
+
 [Setup network connection in Parabola](#network)
 
 
@@ -128,12 +131,15 @@ Updating Parabola {#pacman_update}
 -----------------
 
 In the end, I didn't change my configuration for pacman. When you are
-updating, resync with the latest package names/versions:\
+updating, resync with the latest package names/versions:
+
     # pacman -Syy
 (according to the wiki, -Syy is better than Sy because it refreshes the
 package list even if it appears to be up to date, which can be useful
-when switching to another mirror).\
-Then, update the system:\
+when switching to another mirror).
+
+Then, update the system:
+
 # **pacman -Syu**
 
 **Before installing packages with 'pacman -S', always update first,
@@ -191,14 +197,16 @@ re-install it or install the distro on another computer, for example).
 ### Cleaning the package cache {#pacman_cacheclean}
 
 **The following is very important as you continue to use, update and
-maintain your Parabola system:\
+maintain your Parabola system:
+
 <https://wiki.archlinux.org/index.php/Pacman#Cleaning_the_package_cache>.
 Essentially, this guide talks about a directory that has to be cleaned
 once in a while, to prevent it from growing too big (it's a cache of
 old package information, updated automatically when you do anything in
 pacman).**
 
-To clean out all old packages that are cached:\
+To clean out all old packages that are cached:
+
 # **pacman -Sc**
 
 The wiki cautions that this should be used with care. For example, since
@@ -207,7 +215,8 @@ want to revert back to an older package then it's useful to have the
 caches available. Only do this if you are sure that you won't need it.
 
 The wiki also mentions this method for removing everything from the
-cache, including currently installed packages that are cached:\
+cache, including currently installed packages that are cached:
+
     # pacman -Scc
 This is inadvisable, since it means re-downloading the package again if
 you wanted to quickly re-install it. This should only be used when disk
@@ -218,7 +227,8 @@ space is at a premium.
 ### pacman command equivalents {#pacman_commandequiv}
 
 The following table lists other distro package manager commands, and
-their equivalent in pacman:\
+their equivalent in pacman:
+
 <https://wiki.archlinux.org/index.php/Pacman_Rosetta>
 
 [Back to top of page.](#pagetop)
@@ -253,9 +263,11 @@ access to the entire operating system.
 
 Read the entire document linked to above, and then continue.
 
-Add your user:\
+Add your user:
+
     # useradd -m -G wheel -s /bin/bash *yourusername*
-Set a password:\
+Set a password:
+
 # **passwd *yourusername***
 
 Use of the *diceware method* is recommended, for generating secure
@@ -281,7 +293,8 @@ sshd (openssh), dhcp, etc. There are countless others.
 the background behind the decision by Arch (Parabola's upstream
 supplier) to use systemd.
 
-The manpage should also help:\
+The manpage should also help:
+
     # man systemd
 The section on 'unit types' is especially useful.
 
@@ -292,16 +305,20 @@ implications later when the log gets too big. Based on instructions from
 the wiki, I will reduce the total size of the journal to 50MiB (the wiki
 recommends 50MiB).
 
-Open /etc/systemd/journald.conf and find the line that says:\
-*#SystemMaxUse=*\
-Change it to say:\
+Open /etc/systemd/journald.conf and find the line that says:
+
+*#SystemMaxUse=*
+
+Change it to say:
+
 *SystemMaxUse=50M*
 
 The wiki also recommended a method for forwarding journal output to TTY
 12 (accessible by pressing ctrl+alt+f12, and you use ctrl+alt+\[F1-F12\]
 to switch between terminals). I decided not to enable it.
 
-Restart journald:\
+Restart journald:
+
 # **systemctl restart systemd-journald**
 
 The wiki recommends that if the journal gets too large, you can also
@@ -312,9 +329,11 @@ delete older records when the journal size reaches it's limit
 (according to systemd developers).
 
 Finally, the wiki mentions 'temporary' files and the utility for
-managing them.\
+managing them.
+
     # man systemd-tmpfiles
-The command for 'clean' is:\
+The command for 'clean' is:
+
     # systemd-tmpfiles \--clean
 According to the manpage, this *"cleans all files and directories with
 an age parameter"*. According to the Arch wiki, this reads information
@@ -324,7 +343,8 @@ locations to get a better understanding.
 
 I looked in /etc/tmpfiles.d/ and found that it was empty on my system.
 However, /usr/lib/tmpfiles.d/ contained some files. The first one was
-etc.conf, containing information and a reference to this manpage:\
+etc.conf, containing information and a reference to this manpage:
+
     # man tmpfiles.d
 Read that manpage, and then continue studying all the files.
 
@@ -344,14 +364,18 @@ default base. It might be worth looking into what is available there,
 depending on your use case.
 
 I enabled it on my system, to see what was in it. Edit /etc/pacman.conf
-and below the 'extra' section add:\
-*\[kernels\]\
+and below the 'extra' section add:
+
+*\[kernels\]
+
 Include = /etc/pacman.d/mirrorlist*
 
-Now sync with the repository:\
+Now sync with the repository:
+
 # **pacman -Syy**
 
-List all available packages in this repository:\
+List all available packages in this repository:
+
 # **pacman -Sl kernels**
 
 In the end, I decided not to install anything from it but I kept the
@@ -372,16 +396,20 @@ Read <https://wiki.archlinux.org/index.php/Configuring_Network>.
 
 This should be the same as the hostname that you set in /etc/hostname
 when installing Parabola. You can also do it with systemd (do so now, if
-you like):\
+you like):
+
     # hostnamectl set-hostname *yourhostname*
 This writes the specified hostname to /etc/hostname. More information
-can be found in these manpages:\
+can be found in these manpages:
+
     # man hostname
     # info hostname
 # **man hostnamectl**
 
-Add the same hostname to /etc/hosts, on each line. Example:\
-*127.0.0.1 localhost.localdomain localhost myhostname\
+Add the same hostname to /etc/hosts, on each line. Example:
+
+*127.0.0.1 localhost.localdomain localhost myhostname
+
 ::1 localhost.localdomain localhost myhostname*
 
 You'll note that I set both lines; the 2nd line is for IPv6. More and
@@ -399,16 +427,20 @@ According to the Arch wiki,
 [udev](https://wiki.archlinux.org/index.php/Udev) should already detect
 the ethernet chipset and load the driver for it automatically at boot
 time. You can check this in the *"Ethernet controller"* section when
-running this command:\
+running this command:
+
 # **lspci -v**
 
 Look at the remaining sections *'Kernel driver in use'* and *'Kernel
-modules'*. In my case it was as follows:\
-*Kernel driver in use: e1000e\
+modules'*. In my case it was as follows:
+
+*Kernel driver in use: e1000e
+
 Kernel modules: e1000e*
 
 Check that the driver was loaded by issuing *dmesg | grep module\_name*.
-In my case, I did:\
+In my case, I did:
+
 # **dmesg | grep e1000e**
 
 ### Network device names {#network_devicenames}
@@ -430,10 +462,12 @@ instructions in [grub\_cbfs.html](grub_cbfs.html)).
 For background information, read [Predictable Network Interface
 Names](http://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames/)
 
-Show device names:\
+Show device names:
+
 # **ls /sys/class/net**
 
-Changing the device names is possible (I chose not to do it):\
+Changing the device names is possible (I chose not to do it):
+
 <https://wiki.archlinux.org/index.php/Configuring_Network#Change_device_name>
 
 [Back to top of page.](#pagetop)
@@ -442,7 +476,8 @@ Changing the device names is possible (I chose not to do it):\
 
 I actually chose to ignore most of Networking section on the wiki.
 Instead, I plan to set up LXDE desktop with the graphical
-network-manager client. Here is a list of network managers:\
+network-manager client. Here is a list of network managers:
+
 <https://wiki.archlinux.org/index.php/List_of_applications/Internet#Network_managers>.
 If you need to, set a static IP address (temporarily) using the
 networking guide and the Arch wiki, or start the dhcpcd service in
@@ -462,7 +497,8 @@ is important, so make sure to read them!**
 
 Install smartmontools (it can be used to check smart data. HDDs use
 non-free firmware inside, but it's transparent to you but the smart
-data comes from it. Therefore, don't rely on it too much):\
+data comes from it. Therefore, don't rely on it too much):
+
     # pacman -S smartmontools
 Read <https://wiki.archlinux.org/index.php/S.M.A.R.T.> to learn how to
 use it.
@@ -487,38 +523,49 @@ provide LXDE by default.
 
 Based on <https://wiki.archlinux.org/index.php/Xorg>.
 
-Firstly, install it!\
+Firstly, install it!
+
     # pacman -S xorg-server
 I also recommend installing this (contains lots of useful tools,
-including *xrandr*):\
+including *xrandr*):
+
 # **pacman -S xorg-server-utils**
 
 Install the driver. For me this was *xf86-video-intel* on the ThinkPad
-X60. T60 and macbook11/21 should be the same.\
+X60. T60 and macbook11/21 should be the same.
+
     # pacman -S xf86-video-intel
-For other systems you can try:\
+For other systems you can try:
+
     # pacman -Ss xf86-video- | less
 Combined with looking at your *lspci* output, you can determine which
 driver is needed. By default, Xorg will revert to xf86-video-vesa which
 is a generic driver and doesn't provide true hardware acceleration.
 
 Other drivers (not just video) can be found by looking at the
-*xorg-drivers* group:\
+*xorg-drivers* group:
+
     # pacman -Sg xorg-drivers
 
 Mostly you will rely on a display manager, but in case you ever want to
-start X without one:\
+start X without one:
+
 # **pacman -S xorg-xinit**
 
-<optional>\
-   Arch wiki recommends installing these, for testing that X works:\
+<optional>
+
+   Arch wiki recommends installing these, for testing that X works:
+
        # pacman -S xorg-twm xorg-xclock xterm
-   Refer to <https://wiki.archlinux.org/index.php/Xinitrc>. and test X:\
+   Refer to <https://wiki.archlinux.org/index.php/Xinitrc>. and test X:
+
        # startx
    When you are satisfied, type ***exit*** in xterm, inside the X
-session.\
+session.
+
    Uninstall them (clutter. eww): # **pacman -S xorg-xinit xorg-twm
-xorg-xclock xterm**\
+xorg-xclock xterm**
+
 </optional>
 
 [Back to top of page.](#pagetop)
@@ -535,7 +582,8 @@ will notice that the layout you set in /etc/vconsole.conf earlier might
 not actually be the same in X.
 
 To see what layout you currently use, try this on a terminal emulator in
-X:\
+X:
+
 # **setxkbmap -print -verbose 10**
 
 In my case, I wanted to use the Dvorak (UK) keyboard which is quite
@@ -549,20 +597,30 @@ X60, with a 105-key UK keyboard). If you use an American keyboard
 *dvorak*.
 
 The Arch wiki recommends two different methods for setting the keyboard
-layout:\
+layout:
+
 <https://wiki.archlinux.org/index.php/Keyboard_configuration_in_Xorg#Using_X_configuration_files>
-and\
+and
+
 <https://wiki.archlinux.org/index.php/Keyboard_configuration_in_Xorg#Using_localectl>.
 
-In my case, I chose to use the *configuration file* method:\
+In my case, I chose to use the *configuration file* method:
+
 Create the file /etc/X11/xorg.conf.d/10-keyboard.conf and put this
-inside:\
-*Section "InputClass"\
-        Identifier "system-keyboard"\
-        MatchIsKeyboard "on"\
-        Option "XkbLayout" "gb"\
-        Option "XkbModel" "pc105"\
-        Option "XkbVariant" "dvorak"\
+inside:
+
+*Section "InputClass"
+
+        Identifier "system-keyboard"
+
+        MatchIsKeyboard "on"
+
+        Option "XkbLayout" "gb"
+
+        Option "XkbModel" "pc105"
+
+        Option "XkbVariant" "dvorak"
+
 EndSection*
 
 For you, the steps above may differ if you have a different layout. If
@@ -582,27 +640,34 @@ would like to try something different, refer to
 
 Refer to <https://wiki.archlinux.org/index.php/LXDE>.
 
-Install it, choosing 'all' when asked for the default package list:\
+Install it, choosing 'all' when asked for the default package list:
+
 # **pacman -S lxde obconf**
 
-I didn't want the following, so I removed them:\
+I didn't want the following, so I removed them:
+
 # **pacman -R lxmusic lxtask**
 
-I also lazily installed all fonts:\
+I also lazily installed all fonts:
+
 # **pacman -S $(pacman -Ssq ttf-)**
 
-And a mail client:\
+And a mail client:
+
 # **pacman -S icedove**
 
 In IceCat, go to *Preferences :: Advanced* and disable *GNU IceCat
 Health Report*.
 
-I also like to install these:\
+I also like to install these:
+
 # **pacman -S xsensors stress htop**
 
-Enable LXDM (the default display manager, providing a graphical login):\
+Enable LXDM (the default display manager, providing a graphical login):
+
     # systemctl enable lxdm.service
-It will start when you boot up the system. To start it now, do:\
+It will start when you boot up the system. To start it now, do:
+
 # **systemctl start lxdm.service**
 
 Log in with your standard (non-root) user that you created earlier. It
@@ -610,18 +675,28 @@ is advisable to also create an xinitrc rule in case you ever want to
 start lxde without lxdm. Read
 <https://wiki.archlinux.org/index.php/Xinitrc>.
 
-Open LXterminal:\
+Open LXterminal:
+
     $ cp /etc/skel/.xinitrc \~
 Open .xinitrc and add the following plus a line break at the bottom of
-the file.\
-*# Probably not needed. The same locale info that we set before\
-# Based on advice from the LXDE wiki export LC\_ALL=en\_GB.UTF-8\
-export LANGUAGE=en\_GB.UTF-8\
-export LANG=en\_GB.UTF-8\
-\
-# Start lxde desktop\
-exec startlxde\
-* Now make sure that it is executable:\
+the file.
+
+*# Probably not needed. The same locale info that we set before
+
+# Based on advice from the LXDE wiki export LC\_ALL=en\_GB.UTF-8
+
+export LANGUAGE=en\_GB.UTF-8
+
+export LANG=en\_GB.UTF-8
+
+
+
+# Start lxde desktop
+
+exec startlxde
+
+* Now make sure that it is executable:
+
 $ **chmod +x .xinitrc**
 
 [Back to top of page.](#pagetop)
@@ -647,7 +722,8 @@ NOTE TO SELF: come back to this later.
 
 ### LXDE - screenlock {#lxde_screenlock}
 
-Arch wiki recommends to use *xscreensaver*:\
+Arch wiki recommends to use *xscreensaver*:
+
 # **pacman -S xscreensaver**
 
 Under *Preferences :: Screensaver* in the LXDE menu, I chose *Mode:
@@ -698,30 +774,38 @@ cursor over it, it'll show information about the battery.
 Refer to <https://wiki.archlinux.org/index.php/LXDE#Network_Management>.
 Then I read: <https://wiki.archlinux.org/index.php/NetworkManager>.
 
-Install Network Manager:\
+Install Network Manager:
+
 # **pacman -S networkmanager**
 
-You will also want the graphical applet:\
+You will also want the graphical applet:
+
     # pacman -S network-manager-applet
 Arch wiki says that an autostart rule will be written at
 */etc/xdg/autostart/nm-applet.desktop*
 
 I want to be able to use a VPN at some point, so the wiki tells me to
-do:\
+do:
+
 # **pacman -S networkmanager-openvpn**
 
-LXDE uses openbox, so I refer to:\
+LXDE uses openbox, so I refer to:
+
 <https://wiki.archlinux.org/index.php/NetworkManager#Openbox>.
 
-It tells me for the applet I need:\
+It tells me for the applet I need:
+
     # pacman -S xfce4-notifyd gnome-icon-theme
-Also, for storing authentication details (wifi) I need:\
+Also, for storing authentication details (wifi) I need:
+
 # **pacman -S gnome-keyring**
 
-I wanted to quickly enable networkmanager:\
+I wanted to quickly enable networkmanager:
+
     # systemctl stop dhcpcd
     # systemctl start NetworkManager
-Enable NetworkManager at boot time:\
+Enable NetworkManager at boot time:
+
 # **systemctl enable NetworkManager**
 
 Restart LXDE (log out, and then log back in).
@@ -735,7 +819,8 @@ theme, in *lxappearance*.
 
 
 
-Copyright © 2014, 2015 Leah Rowe <info@minifree.org>\
+Copyright © 2014, 2015 Leah Rowe <info@minifree.org>
+
 Permission is granted to copy, distribute and/or modify this document
 under the terms of the Creative Commons Attribution-ShareAlike 4.0
 International license or any later version published by Creative
diff --git a/docs/gnulinux/encrypted_debian.md b/docs/gnulinux/encrypted_debian.md
index dd8e44da..1cc6c095 100644
--- a/docs/gnulinux/encrypted_debian.md
+++ b/docs/gnulinux/encrypted_debian.md
@@ -22,15 +22,24 @@ tampering by someone with physical access to the system.
 
 This guide is written for Debian net installer. You can download the ISO
 from the homepage on [debian.org](https://www.debian.org/). Use this on
-the GRUB terminal to boot it from USB (for 64-bit Intel or AMD):\
-**set root='usb0'\
-linux /install.amd/vmlinuz\
-initrd /install.amd/initrd.gz\
-boot\
-** If you are on a 32-bit system (e.g. X60):\
-**set root='usb0'\
-linux /install.386/vmlinuz\
-initrd /install.386/initrd.gz\
+the GRUB terminal to boot it from USB (for 64-bit Intel or AMD):
+
+**set root='usb0'
+
+linux /install.amd/vmlinuz
+
+initrd /install.amd/initrd.gz
+
+boot
+
+** If you are on a 32-bit system (e.g. X60):
+
+**set root='usb0'
+
+linux /install.386/vmlinuz
+
+initrd /install.386/initrd.gz
+
 boot**
 
 [This guide](grub_boot_installer.html) shows how to create a boot USB
@@ -186,11 +195,13 @@ Booting your system
 At this point, you will have finished the installation. At your GRUB
 payload, press C to get to the command line.
 
-Do that:\
+Do that:
+
 grub>     cryptomount -a
 grub>     set root='lvm/matrix-rootvol'
 grub> **linux /vmlinuz root=/dev/mapper/matrix-rootvol
-cryptdevice=/dev/mapper/matrix-rootvol:root**\
+cryptdevice=/dev/mapper/matrix-rootvol:root**
+
 grub>     initrd /initrd.img
 grub> **boot**
 
@@ -202,7 +213,8 @@ ecryptfs
 If you didn't encrypt your home directory, then you can safely ignore
 this section.
 
-Immediately after logging in, do that:\
+Immediately after logging in, do that:
+
 $ **sudo ecryptfs-unwrap-passphrase**
 
 This will be needed in the future if you ever need to recover your home
@@ -225,7 +237,8 @@ Operating System' to say this inside:
     cryptomount -a
     set root='lvm/matrix-rootvol'
 **linux /vmlinuz root=/dev/mapper/matrix-rootvol
-cryptdevice=/dev/mapper/matrix-rootvol:root**\
+cryptdevice=/dev/mapper/matrix-rootvol:root**
+
 **initrd /initrd.img**
 
 Without specifying a device, the *-a* parameter tries to unlock all
@@ -328,7 +341,8 @@ problems. Removing that worked around the issue.
 
 
 
-Copyright © 2014, 2015, 2016 Leah Rowe <info@minifree.org>\
+Copyright © 2014, 2015, 2016 Leah Rowe <info@minifree.org>
+
 Permission is granted to copy, distribute and/or modify this document
 under the terms of the Creative Commons Attribution-ShareAlike 4.0
 International license or any later version published by Creative
diff --git a/docs/gnulinux/encrypted_parabola.md b/docs/gnulinux/encrypted_parabola.md
index f6c022a0..51ba0b5f 100644
--- a/docs/gnulinux/encrypted_parabola.md
+++ b/docs/gnulinux/encrypted_parabola.md
@@ -70,12 +70,14 @@ article](https://wiki.archlinux.org/index.php/Solid_State_Drives). Edit
 /etc/fstab later on when chrooted into your install. Also, read the
 whole article and keep all points in mind, adapting them for this guide.
 
-Securely wipe the drive:\
+Securely wipe the drive:
+
     # dd if=/dev/urandom of=/dev/sda; sync
 NOTE: If you have an SSD, only do this the first time. If it was already
 LUKS-encrypted before, use the info below to wipe the LUKS header. Also,
 check online for your SSD what the recommended erase block size is. For
-example if it was 2MiB:\
+example if it was 2MiB:
+
 # **dd if=/dev/urandom of=/dev/sda bs=2M; sync**
 
 If your drive was already LUKS encrypted (maybe you are re-installing
@@ -84,7 +86,8 @@ header.
 <https://www.lisenet.com/2013/luks-add-keys-backup-and-restore-volume-header/>
 showed me how to do this. It recommends doing the first 3MiB. Now, that
 guide is recommending putting zero there. I'm going to use urandom. Do
-this:\
+this:
+
     # head -c 3145728 /dev/urandom > /dev/sda; sync
 (Wiping the LUKS header is important, since it has hashed passphrases
 and so on. It's 'secure', but 'potentially' a risk).
@@ -95,7 +98,8 @@ Change keyboard layout
 ----------------------
 
 Parabola live shell assumes US Qwerty. If you have something different,
-list the available keymaps and use yours:\
+list the available keymaps and use yours:
+
     # localectl list-keymaps
     # loadkeys LAYOUT
 For me, LAYOUT would have been dvorak-uk.
@@ -124,7 +128,8 @@ dm-mod
 ------
 
 device-mapper will be used - a lot. Make sure that the kernel module is
-loaded:\
+loaded:
+
 # **modprobe dm-mod**
 
 Create LUKS partition
@@ -138,28 +143,34 @@ prepared cryptsetup command below. Note that the iteration time is for
 security purposes (mitigates brute force attacks), so anything lower
 than 5 seconds is probably not ok.
 
-I am using MBR partitioning, so I use cfdisk:\
+I am using MBR partitioning, so I use cfdisk:
+
 # **cfdisk /dev/sda**
 
 I create a single large sda1 filling the whole drive, leaving it as the
 default type 'Linux' (83).
 
 Now I refer to
-<https://wiki.archlinux.org/index.php/Dm-crypt/Drive_preparation#Partitioning>:\
+<https://wiki.archlinux.org/index.php/Dm-crypt/Drive_preparation#Partitioning>:
+
 I am then directed to
 <https://wiki.archlinux.org/index.php/Dm-crypt/Device_encryption>.
 
 Parabola forces you to RTFM. Do that.
 
-It tells me to run:\
+It tells me to run:
+
 # **cryptsetup benchmark** (for making sure the list below is
-populated)\
-Then:\
+populated)
+
+Then:
+
     # cat /proc/crypto
 This gives me crypto options that I can use. It also provides a
 representation of the best way to set up LUKS (in this case, security is
 a priority; speed, a distant second). To gain a better understanding, I
-am also reading:\
+am also reading:
+
 # **man cryptsetup**
 
 Following that page, based on my requirements, I do the following based
@@ -168,7 +179,8 @@ on
 Reading through, it seems like Serpent (encryption) and Whirlpool (hash)
 is the best option.
 
-I am initializing LUKS with the following:\
+I am initializing LUKS with the following:
+
 # **cryptsetup -v \--cipher serpent-xts-plain64 \--key-size 512 \--hash
 whirlpool \--iter-time 500 \--use-random \--verify-passphrase luksFormat
 /dev/sda1** Choose a **secure** passphrase here. Ideally lots of
@@ -186,31 +198,40 @@ Create LVM
 
 Now I refer to <https://wiki.archlinux.org/index.php/LVM>.
 
-Open the LUKS partition:\
+Open the LUKS partition:
+
     # cryptsetup luksOpen /dev/sda1 lvm
 (it will be available at /dev/mapper/lvm)
 
-Create LVM partition:\
+Create LVM partition:
+
     # pvcreate /dev/mapper/lvm
-Show that you just created it:\
+Show that you just created it:
+
 # **pvdisplay**
 
 Now I create the volume group, inside of which the logical volumes will
-be created:\
+be created:
+
     # vgcreate matrix /dev/mapper/lvm
 (volume group name is 'matrix' - choose your own name, if you like)
-Show that you created it:\
+Show that you created it:
+
 # **vgdisplay**
 
-Now create the logical volumes:\
+Now create the logical volumes:
+
 # **lvcreate -L 2G matrix -n swapvol** (2G swap partition, named
-swapvol)\
+swapvol)
+
 Again, choose your own name if you like. Also, make sure to choose a
 swap size of your own needs. It basically depends on how much RAM you
 have installed. I refer to
-<http://www.linux.com/news/software/applications/8208-all-about-linux-swap-space>.\
+<http://www.linux.com/news/software/applications/8208-all-about-linux-swap-space>.
+
 # **lvcreate -l +100%FREE matrix -n root** (single large partition in
-the rest of the space, named root)\
+the rest of the space, named root)
+
 You can also be flexible here, for example you can specify a /boot, a /,
 a /home, a /var, a /usr, etc. For example, if you will be running a
 web/mail server then you want /var in its own partition (so that if it
@@ -218,7 +239,8 @@ fills up with logs, it won't crash your system). For a home/laptop
 system (typical use case), a root and a swap will do (really).
 
 Verify that the logical volumes were created, using the following
-command:\
+command:
+
 # **lvdisplay**
 
 
@@ -226,15 +248,19 @@ command:\
 Create / and swap partitions, and mount
 ---------------------------------------
 
-For the swapvol LV I use:\
+For the swapvol LV I use:
+
     # mkswap /dev/mapper/matrix-swapvol
-Activate swap:\
+Activate swap:
+
 # **swapon /dev/matrix/swapvol**
 
-For the root LV I use:\
+For the root LV I use:
+
 # **mkfs.btrfs /dev/mapper/matrix-root**
 
-Mount the root (/) partition:\
+Mount the root (/) partition:
+
 # **mount /dev/matrix/root /mnt**
 
 
@@ -249,7 +275,8 @@ Now I am following the rest of
 <https://wiki.parabolagnulinux.org/Installation_Guide>. I also cross
 referenced <https://wiki.archlinux.org/index.php/Installation_guide>.
 
-Create /home and /boot on root mountpoint:\
+Create /home and /boot on root mountpoint:
+
     # mkdir -p /mnt/home
 # **mkdir -p /mnt/boot**
 
@@ -258,50 +285,68 @@ devices are ready to install Parabola.
 
 In **/etc/pacman.d/mirrorlist**, comment out all lines except the Server
 line closest to where you are (I chose the UK Parabola server (main
-server)) and then did:\
+server)) and then did:
+
     # pacman -Syy
     # pacman -Syu
 # **pacman -Sy pacman** (and then I did the other 2 steps above,
-again)\
+again)
+
 In my case I did the steps in the next paragraph, and followed the steps
 in this paragraph again.
 
-<troubleshooting>\
+<troubleshooting>
+
    The following is based on 'Verification of package signatures' in
-the Parabola install guide.\
-   Check there first to see if steps differ by now.\
+the Parabola install guide.
+
+   Check there first to see if steps differ by now.
+
    Now you have to update the default Parabola keyring. This is used for
-signing and verifying packages:\
+signing and verifying packages:
+
        # pacman -Sy parabola-keyring
    It says that if you get GPG errors, then it's probably an expired
-key and, therefore, you should do:\
+key and, therefore, you should do:
+
        # pacman-key \--populate parabola
        # pacman-key \--refresh-keys
        # pacman -Sy parabola-keyring
    To be honest, you should do the above anyway. Parabola has a lot of
-maintainers, and a lot of keys. Really!\
-   If you get an error mentioning dirmngr, do:\
+maintainers, and a lot of keys. Really!
+
+   If you get an error mentioning dirmngr, do:
+
        # dirmngr </dev/null
    Also, it says that if the clock is set incorrectly then you have to
-manually set the correct time\
-   (if keys are listed as expired because of it):\
+manually set the correct time
+
+   (if keys are listed as expired because of it):
+
        # date MMDDhhmm\[\[CC\]YY\]\[.ss\]
-   I also had to install:\
+   I also had to install:
+
        # pacman -S archlinux-keyring
        # pacman-key \--populate archlinux
    In my case I saw some conflicting files reported in pacman, stopping
-me from using it.\
+me from using it.
+
    I deleted the files that it mentioned and then it worked.
-Specifically, I had this error:\
-   *licenses: /usr/share/licenses/common/MPS exists in filesystem*\
+Specifically, I had this error:
+
+   *licenses: /usr/share/licenses/common/MPS exists in filesystem*
+
    I rm -Rf'd the file and then pacman worked. I'm told that the
-following would have also made it work:\
+following would have also made it work:
+
        # pacman -Sf licenses
-</troubleshooting>\
+</troubleshooting>
+
 
 I also like to install other packages (base-devel, compilers and so on)
 and wpa\_supplicant/dialog/iw/wpa\_actiond are needed for wireless after
-the install:\
+the install:
+
 # **pacstrap /mnt base base-devel wpa\_supplicant dialog iw
 wpa\_actiond**
 
@@ -312,21 +357,26 @@ Configure the system
 
 Generate an fstab - UUIDs are used because they have certain advantages
 (see <https://wiki.parabola.nu/Fstab#Identifying_filesystems>. If you
-prefer labels instead, replace the -U option with -L):\
+prefer labels instead, replace the -U option with -L):
+
     # genfstab -U -p /mnt >> /mnt/etc/fstab
-Check the created file:\
+Check the created file:
+
     # cat /mnt/etc/fstab
 (If there are any errors, edit the file. Do **NOT** run the genfstab
 command again!)
 
-Chroot into new system:\
+Chroot into new system:
+
 # **arch-chroot /mnt /bin/bash**
 
-It's a good idea to have this installed:\
+It's a good idea to have this installed:
+
 # **pacman -S linux-libre-lts**
 
 It was also suggested that you should install this kernel (read up on
-what GRSEC is):\
+what GRSEC is):
+
 # **pacman -S linux-libre-grsec**
 
 This is another kernel that sits inside /boot, which you can use. LTS
@@ -334,35 +384,43 @@ means 'long-term support'. These are so-called 'stable' kernels that
 can be used as a fallback during updates, if a bad kernel causes issues
 for you.
 
-Parabola does not have wget. This is sinister. Install it:\
+Parabola does not have wget. This is sinister. Install it:
+
 # **pacman -S wget**
 
-Locale:\
+Locale:
+
     # vi /etc/locale.gen
 Uncomment your needed localisations. For example en\_GB.UTF-8 (UTF-8 is
-highly recommended over other options).\
+highly recommended over other options).
+
     # locale-gen
     # echo LANG=en\_GB.UTF-8 > /etc/locale.conf
 # **export LANG=en\_GB.UTF-8**
 
-Console font and keymap:\
+Console font and keymap:
+
     # vi /etc/vconsole.conf
 In my case:
 
     KEYMAP=dvorak-uk
     FONT=lat9w-16
 
-Time zone:\
+Time zone:
+
     # ln -s /usr/share/zoneinfo/Europe/London /etc/localtime
 (Replace Zone and Subzone to your liking. See /usr/share/zoneinfo)
 
-Hardware clock:\
+Hardware clock:
+
 # **hwclock \--systohc \--utc**
 
 Hostname: Write your hostname to /etc/hostname. For example, if your
-hostname is parabola:\
+hostname is parabola:
+
     # echo parabola > /etc/hostname
-Add the same hostname to /etc/hosts:\
+Add the same hostname to /etc/hosts:
+
     # vi /etc/hosts
 
     #<ip-address> <hostname.domain.org> <hostname>
@@ -376,7 +434,8 @@ Mkinitcpio: Configure /etc/mkinitcpio.conf as needed (see
 <https://wiki.parabola.nu/Mkinitcpio>). Runtime modules can be found in
 /usr/lib/initcpio/hooks, and build hooks can be found in
 /usr/lib/initcpio/install. (# **mkinitcpio -H hookname** gives
-information about each hook.) Specifically, for this use case:\
+information about each hook.) Specifically, for this use case:
+
     # vi /etc/mkinitcpio.conf
 Then modify the file like so:
 
@@ -401,18 +460,23 @@ Then modify the file like so:
 
 Now using mkinitcpio, you can create the kernel and ramdisk for booting
 with (this is different from Arch, specifying linux-libre instead of
-linux):\
+linux):
+
     # mkinitcpio -p linux-libre
-Also do it for linux-libre-lts:\
+Also do it for linux-libre-lts:
+
     # mkinitcpio -p linux-libre-lts
-Also do it for linux-libre-grsec:\
+Also do it for linux-libre-grsec:
+
 # **mkinitcpio -p linux-libre-grsec**
 
 Set the root password: At the time of writing, Parabola used SHA512 by
 default for its password hashing. I referred to
-<https://wiki.archlinux.org/index.php/SHA_password_hashes>.\
+<https://wiki.archlinux.org/index.php/SHA_password_hashes>.
+
     # vi /etc/pam.d/passwd
-Add rounds=65536 at the end of the uncommented 'password' line.\
+Add rounds=65536 at the end of the uncommented 'password' line.
+
     # passwd root
 Make sure to set a secure password! Also, it must never be the same as
 your LUKS password.
@@ -427,17 +491,24 @@ Extra security tweaks
 
 Based on <https://wiki.archlinux.org/index.php/Security>.
 
-Restrict access to important directories:\
+Restrict access to important directories:
+
 # **chmod 700 /boot /etc/{iptables,arptables}**
 
-Lockout user after three failed login attempts:\
-Edit the file /etc/pam.d/system-login and comment out that line:\
-*# auth required pam\_tally.so onerr=succeed file=/var/log/faillog*\
-Or just delete it. Above it, put:\
+Lockout user after three failed login attempts:
+
+Edit the file /etc/pam.d/system-login and comment out that line:
+
+*# auth required pam\_tally.so onerr=succeed file=/var/log/faillog*
+
+Or just delete it. Above it, put:
+
 *auth required pam\_tally.so deny=2 unlock\_time=600 onerr=succeed
-file=/var/log/faillog*\
+file=/var/log/faillog*
+
 To unlock a user manually (if a password attempt is failed 3 times),
-do:\
+do:
+
 # **pam\_tally \--user *theusername* \--reset** What the above
 configuration does is lock the user out for 10 minutes, if they make 3
 failed login attempts.
@@ -451,18 +522,22 @@ don't really need sudo.
 Unmount, reboot!
 ----------------
 
-Exit from chroot:\
+Exit from chroot:
+
 # **exit**
 
-unmount:\
+unmount:
+
     # umount -R /mnt
 # **swapoff -a**
 
-deactivate the lvm lv's:\
+deactivate the lvm lv's:
+
     # lvchange -an /dev/matrix/root
     # lvchange -an /dev/matrix/swapvol
 
-Lock the encrypted partition (close it):\
+Lock the encrypted partition (close it):
+
 # **cryptsetup luksClose lvm**
 
     # shutdown -h now
@@ -480,7 +555,8 @@ underlines will boot lts kernel instead of normal).
 grub>     cryptomount -a
 grub>     set root='lvm/matrix-root'
 grub> **linux /boot/vmlinuz-linux-libre-lts root=/dev/matrix/root
-cryptdevice=/dev/sda1:root**\
+cryptdevice=/dev/sda1:root**
+
 grub>     initrd /boot/initramfs-linux-libre-lts.img
 grub>     boot
 
@@ -520,16 +596,21 @@ possibility of bricking your device!
 I will go for the re-flash option here. Firstly, cd to the
 libreboot\_util/cbfstool/{armv7l i686 x86\_64} directory. Dump the
 current firmware - where *libreboot.rom* is an example: make sure to
-adapt:\
+adapt:
+
     # flashrom -p internal -r libreboot.rom
 If flashrom complains about multiple flash chips detected, add a *-c*
-option at the end, with the name of your chosen chip is quotes.\
+option at the end, with the name of your chosen chip is quotes.
+
 You can check if everything is in there (*grub.cfg* and *grubtest.cfg*
-would be really nice):\
+would be really nice):
+
     $ ./cbfstool libreboot.rom print
-Extract grubtest.cfg:\
+Extract grubtest.cfg:
+
     $ ./cbfstool libreboot.rom extract -n grubtest.cfg -f grubtest.cfg
-And modify:\
+And modify:
+
 $ **vi grubtest.cfg**
 
 In grubtest.cfg, inside the 'Load Operating System' menu entry, change
@@ -558,18 +639,23 @@ detected LUKS volumes. You can also specify -u UUID or -a (device).
 hardening your GRUB configuration, for security purposes.
 
 Save your changes in grubtest.cfg, then delete the unmodified config
-from the ROM image:\
+from the ROM image:
+
     $ ./cbfstool libreboot.rom remove -n grubtest.cfg
-and insert the modified grubtest.cfg:\
+and insert the modified grubtest.cfg:
+
 $ **./cbfstool libreboot.rom add -n grubtest.cfg -f grubtest.cfg -t
-raw**\
+raw**
+
 
 Now refer to <http://libreboot.org/docs/install/#flashrom>. Cd (up) to
-the libreboot\_util directory and update the flash chip contents:\
+the libreboot\_util directory and update the flash chip contents:
+
     # ./flash update libreboot.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:\
+correct ROM image, then run this alternative command:
+
     # ./flash forceupdate libreboot.rom
 You should see "Verifying flash... VERIFIED." written at the end of
 the flashrom output.
@@ -596,25 +682,31 @@ the main config still links (in the menu) to grubtest.cfg, so that you
 don't have to manually switch to it, in case you ever want to follow
 this guide again in the future (modifying the already modified config).
 Inside libreboot\_util/cbfstool/{armv7l i686 x86\_64}, we can do this
-with the following command:\
+with the following command:
+
 $ **sed -e 's:(cbfsdisk)/grub.cfg:(cbfsdisk)/grubtest.cfg:g' -e
 's:Switch to grub.cfg:Switch to grubtest.cfg:g' < grubtest.cfg >
-grub.cfg**\
-Delete the grub.cfg that remained inside the ROM:\
+grub.cfg**
+
+Delete the grub.cfg that remained inside the ROM:
+
     $ ./cbfstool libreboot.rom remove -n grub.cfg
-Add the modified version that you just made:\
+Add the modified version that you just made:
+
     $ ./cbfstool libreboot.rom add -n grub.cfg -f grub.cfg -t raw
 
 Now you have a modified ROM. Once more, refer to
 <http://libreboot.org/docs/install/#flashrom>. Cd to the libreboot\_util
-directory and update the flash chip contents:\
+directory and update the flash chip contents:
+
     # ./flash update libreboot.rom
 And wait for the "Verifying flash... VERIFIED." Once you have done
 that, shut down and then boot up with your new configuration.
 
 When done, delete GRUB (remember, we only needed it for the
 *grub-mkpasswd-pbkdf2* utility; GRUB is already part of libreboot,
-flashed alongside it as a *payload*):\
+flashed alongside it as a *payload*):
+
 # **pacman -R grub**
 
 
@@ -635,23 +727,31 @@ fact that it is being loaded from an encrypted volume. Therefore, you
 will be asked to enter your passphrase a second time. A workaround is to
 put a keyfile inside initramfs, with instructions for the kernel to use
 it when booting. This is safe, because /boot/ is encrypted (otherwise,
-putting a keyfile inside initramfs would be a bad idea).\
-Boot up and login as root or your user. Then generate the key file:\
+putting a keyfile inside initramfs would be a bad idea).
+
+Boot up and login as root or your user. Then generate the key file:
+
 # **dd bs=512 count=4 if=/dev/urandom of=/etc/mykeyfile
-iflag=fullblock**\
-Insert it into the luks volume:\
+iflag=fullblock**
+
+Insert it into the luks volume:
+
     # cryptsetup luksAddKey /dev/sdX /etc/mykeyfile
 and enter your LUKS passphrase when prompted. Add the keyfile to the
-initramfs by adding it to FILES in /etc/mkinitcpio.conf. For example:\
+initramfs by adding it to FILES in /etc/mkinitcpio.conf. For example:
+
     # FILES="/etc/mykeyfile"
-Create the initramfs image from scratch:\
+Create the initramfs image from scratch:
+
     # mkinitcpio -p linux-libre
     # mkinitcpio -p linux-libre-lts
     # mkinitcpio -p linux-libre-grsec
 Add the following to your grub.cfg - you are now able to do that, see
-above! -, or add it in the kernel command line for GRUB:\
+above! -, or add it in the kernel command line for GRUB:
+
     # cryptkey=rootfs:/etc/mykeyfile
-\
+
+
 You can also place this inside the grub.cfg that exists in CBFS:
 [grub\_cbfs.html](grub_cbfs.html).
 
@@ -660,7 +760,8 @@ You can also place this inside the grub.cfg that exists in CBFS:
 Further security tips
 ---------------------
 
-<https://wiki.archlinux.org/index.php/Security>.\
+<https://wiki.archlinux.org/index.php/Security>.
+
 <https://wiki.parabolagnulinux.org/User:GNUtoo/laptop>
 
 
@@ -755,8 +856,10 @@ problems. Removing that worked around the issue.
 
 
 
-Copyright © 2014, 2015, 2016 Leah Rowe <info@minifree.org>\
-Copyright © 2015 Jeroen Quint <jezza@diplomail.ch>\
+Copyright © 2014, 2015, 2016 Leah Rowe <info@minifree.org>
+
+Copyright © 2015 Jeroen Quint <jezza@diplomail.ch>
+
 Permission is granted to copy, distribute and/or modify this document
 under the terms of the Creative Commons Attribution-ShareAlike 4.0
 International license or any later version published by Creative
diff --git a/docs/gnulinux/grub_boot_installer.md b/docs/gnulinux/grub_boot_installer.md
index 21cb1276..2669aad3 100644
--- a/docs/gnulinux/grub_boot_installer.md
+++ b/docs/gnulinux/grub_boot_installer.md
@@ -30,18 +30,22 @@ Prepare the USB drive (in GNU+Linux)
 If you downloaded your ISO on an existing GNU+Linux system, here is how
 to create the bootable GNU+Linux USB drive:
 
-Connect the USB drive. Check dmesg:\
+Connect the USB drive. Check dmesg:
+
     $ dmesg
-Check lsblk to confirm which drive it is:\
+Check lsblk to confirm which drive it is:
+
     $ lsblk
 
 Check that it wasn't automatically mounted. If it was, unmount it. For
-example:\
+example:
+
     $ sudo umount /dev/sdX*
     # umount /dev/sdX*
 
 dmesg told you what device it is. Overwrite the drive, writing your
-distro ISO to it with dd. For example:\
+distro ISO to it with dd. For example:
+
     $ sudo dd if=gnulinux.iso of=/dev/sdX bs=8M; sync
     # dd if=gnulinux.iso of=/dev/sdX bs=8M; sync
 
@@ -72,17 +76,21 @@ Prepare the USB drive (in LibertyBSD or OpenBSD)
 If you downloaded your ISO on a LibertyBSD or OpenBSD system, here is
 how to create the bootable GNU+Linux USB drive:
 
-Connect the USB drive. Check dmesg:\
+Connect the USB drive. Check dmesg:
+
     $ dmesg | tail
-Check to confirm which drive it is, for example, if you think its sd3:\
+Check to confirm which drive it is, for example, if you think its sd3:
+
     $ disklabel sd3
 
 Check that it wasn't automatically mounted. If it was, unmount it. For
-example:\
+example:
+
     $ doas umount /dev/sd3i
 
 dmesg told you what device it is. Overwrite the drive, writing the
-OpenBSD installer to it with dd. For example:\
+OpenBSD installer to it with dd. For example:
+
     $ doas dd if=gnulinux.iso of=/dev/rsdXc bs=1M; sync
 
 You should now be able to boot the installer from your USB drive.
@@ -108,16 +116,26 @@ Debian or Devuan net install?
 Download the Debian or Devuan net installer. You can download the ISO
 from the homepage on [debian.org](https://www.debian.org/), or [the
 Devuan homepage](https://www.devuan.org/) for Devuan. Use this on the
-GRUB terminal to boot it from USB (for 64-bit Intel or AMD):\
-**set root='usb0'\
-linux /install.amd/vmlinuz\
-initrd /install.amd/initrd.gz\
-boot\
-** If you are on a 32-bit system (e.g. X60):\
-**set root='usb0'\
-linux /install.386/vmlinuz\
-initrd /install.386/initrd.gz\
-boot**\
+GRUB terminal to boot it from USB (for 64-bit Intel or AMD):
+
+**set root='usb0'
+
+linux /install.amd/vmlinuz
+
+initrd /install.amd/initrd.gz
+
+boot
+
+** If you are on a 32-bit system (e.g. X60):
+
+**set root='usb0'
+
+linux /install.386/vmlinuz
+
+initrd /install.386/initrd.gz
+
+boot**
+
 We recommend using the *MATE* desktop.
 
 
@@ -142,13 +160,17 @@ distribution. You must adapt them appropriately, for whatever GNU+Linux
 distribution it is that you are trying to install.*
 
 If the ISOLINUX parser or *Search for GRUB configuration* options won't
-work, then press C in GRUB to access the command line.\
+work, then press C in GRUB to access the command line.
+
 grub>     ls
-Get the device from above output, eg (usb0). Example:\
+Get the device from above output, eg (usb0). Example:
+
 grub>     cat (usb0)/isolinux/isolinux.cfg
 Either this will show the ISOLINUX menuentries for that ISO, or link to
-other .cfg files, for example /isolinux/foo.cfg.\
-If it did that, then you do:\
+other .cfg files, for example /isolinux/foo.cfg.
+
+If it did that, then you do:
+
 grub>     cat (usb0)/isolinux/foo.cfg
 And so on, until you find the correct menuentries for ISOLINUX. **The
 file */isolinux/foo.cfg* is a fictional example. Do not actually use
@@ -165,11 +187,15 @@ options in txt.cfg. This is important if you want 64-bit booting on your
 system. Devuan versions based on Debian 8.x may also have the same
 issue.
 
-Now look at the ISOLINUX menuentry. It'll look like:\
-**kernel /path/to/kernel\
-append PARAMETERS initrd=/path/to/initrd MAYBE\_MORE\_PARAMETERS\
+Now look at the ISOLINUX menuentry. It'll look like:
+
+**kernel /path/to/kernel
+
+append PARAMETERS initrd=/path/to/initrd MAYBE\_MORE\_PARAMETERS
+
 ** GRUB works the same way, but in it's own way. Example GRUB
-commands:\
+commands:
+
 grub>     set root='usb0'
 grub>     linux /path/to/kernel PARAMETERS MAYBE\_MORE\_PARAMETERS
 grub>     initrd /path/to/initrd
@@ -207,7 +233,8 @@ When using the ROM images that use coreboot's "text mode" instead of
 the coreboot framebuffer, booting the Debian or Devuan net installer
 results in graphical corruption because it is trying to switch to a
 framebuffer which doesn't exist. Use that kernel parameter on the
-'linux' line when booting it:\
+'linux' line when booting it:
+
 **vga=normal fb=false**
 
 This forces debian-installer to start in text-mode, instead of trying to
@@ -225,8 +252,10 @@ debian-installer (text mode) net install method.
 
 
 
-Copyright © 2014, 2015, 2016 Leah Rowe <info@minifree.org>\
-Copyright © 2016 Scott Bonds <scott@ggr.com>\
+Copyright © 2014, 2015, 2016 Leah Rowe <info@minifree.org>
+
+Copyright © 2016 Scott Bonds <scott@ggr.com>
+
 Permission is granted to copy, distribute and/or modify this document
 under the terms of the Creative Commons Attribution-ShareAlike 4.0
 International license or any later version published by Creative
diff --git a/docs/gnulinux/grub_cbfs.md b/docs/gnulinux/grub_cbfs.md
index 745e47d4..58e9cc04 100644
--- a/docs/gnulinux/grub_cbfs.md
+++ b/docs/gnulinux/grub_cbfs.md
@@ -50,7 +50,8 @@ Table of Contents
 Introduction
 ------------
 
-Download the latest release from <http://libreboot.org/>\
+Download the latest release from <http://libreboot.org/>
+
 **If you downloaded from git, refer to
 [../git/#build\_meta](../git/#build_meta) before continuing.**
 
@@ -124,7 +125,8 @@ Acquire the necessary utilities {#tools}
 Use ***cbfstool*** and ***flashrom***. There are available in the
 *libreboot\_util* release archive, or they can be compiled (see
 [../git/#build\_flashrom](../git/#build_flashrom)). Flashrom is also
-available from the repositories:\
+available from the repositories:
+
 # **pacman -S flashrom**
 
 [Back to top of page.](#pagetop)
@@ -140,11 +142,13 @@ flashed. For the purpose of this tutorial it is assumed that your ROM
 image file is named *libreboot.rom*, so please make sure to adapt.
 
 ROM images are included pre-compiled in libreboot. You can also dump
-your current firmware, using flashrom:\
+your current firmware, using flashrom:
+
     $ sudo flashrom -p internal -r libreboot.rom
     # flashrom -p internal -r libreboot.rom
 If you are told to specify the chip, add the option **-c {your chip}**
-to the command, for example:\
+to the command, for example:
+
 # **flashrom -c MX25L6405 -p internal -r libreboot.rom**
 
 [Back to top of page.](#pagetop)
@@ -154,7 +158,8 @@ to the command, for example:\
 Extract grubtest.cfg from the ROM image {#extract_testconfig}
 ---------------------------------------
 
-You can check the contents of the ROM image, inside CBFS:\
+You can check the contents of the ROM image, inside CBFS:
+
     $ cd .../libreboot\_util/cbfstool** $ ./cbfstool libreboot.rom
 print**
 
@@ -163,7 +168,8 @@ loaded by default, with a menuentry for switching to grubtest.cfg. In
 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:\
+Extract grubtest.cfg from the ROM image:
+
     $ ./cbfstool libreboot.rom extract -n grubtest.cfg -f grubtest.cfg
 
 Modify the grubtest.cfg accordingly.
@@ -176,10 +182,12 @@ 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:\
+config from the ROM image:
+
     $ ./cbfstool libreboot.rom remove -n grubtest.cfg
 
-Next, insert the modified version:\
+Next, insert the modified version:
+
 **$ ./cbfstool libreboot.rom add -n grubtest.cfg -f grubtest.cfg -t
 raw**
 
@@ -192,11 +200,13 @@ Testing
 
 **Now you have a modified ROM. Refer back to
 [../install/#flashrom](../install/#flashrom) for information on how to
-flash it.\
+flash it.
+
     $ cd /libreboot\_util** # **./flash update libreboot.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:\
+correct ROM image, then run this alternative command:
+
     # ./flash forceupdate libreboot.rom
 You should see **"Verifying flash... VERIFIED."** written at the end
 of the flashrom output. Once you have done that, shut down and then boot
@@ -224,15 +234,19 @@ difference: the menuentry 'Switch to grub.cfg' will be changed to
 grubtest.cfg. This is so that the main config still links (in the menu)
 to grubtest.cfg, so that you don't have to manually switch to it, in
 case you ever want to follow this guide again in the future (modifying
-the already modified config). From /libreboot\_util/cbfstool, do:\
+the already modified config). From /libreboot\_util/cbfstool, do:
+
 $ **sed -e 's:(cbfsdisk)/grub.cfg:(cbfsdisk)/grubtest.cfg:g' -e
 's:Switch to grub.cfg:Switch to grubtest.cfg:g' < grubtest.cfg >
-grub.cfg**\
+grub.cfg**
+
+
+Delete the grub.cfg that remained inside the ROM:
 
-Delete the grub.cfg that remained inside the ROM:\
     $ ./cbfstool libreboot.rom remove -n grub.cfg
 
-Add the modified version that you just made:\
+Add the modified version that you just made:
+
     $ ./cbfstool libreboot.rom add -n grub.cfg -f grub.cfg -t raw
 
 **Now you have a modified ROM. Again, refer back to
@@ -244,8 +258,10 @@ boot up with your new configuration.**
 
 
 
-Copyright © 2014, 2015 Leah Rowe <info@minifree.org>\
-Copyright © 2015 Jeroen Quint <jezza@diplomail.ch>\
+Copyright © 2014, 2015 Leah Rowe <info@minifree.org>
+
+Copyright © 2015 Jeroen Quint <jezza@diplomail.ch>
+
 Permission is granted to copy, distribute and/or modify this document
 under the terms of the Creative Commons Attribution-ShareAlike 4.0
 International license or any later version published by Creative
diff --git a/docs/gnulinux/grub_hardening.md b/docs/gnulinux/grub_hardening.md
index ebd28645..53749d56 100644
--- a/docs/gnulinux/grub_hardening.md
+++ b/docs/gnulinux/grub_hardening.md
@@ -188,7 +188,8 @@ What remains now is to include the modifications into the image (rom):
 
 
 
-Copyright © 2017 Fedja Beader <fedja@protonmail.ch>\
+Copyright © 2017 Fedja Beader <fedja@protonmail.ch>
+
 Permission is granted to copy, distribute and/or modify this document
 under the terms of the Creative Commons Attribution-ShareAlike 4.0
 International license or any later version published by Creative
diff --git a/docs/gnulinux/index.md b/docs/gnulinux/index.md
index 00d66a1f..adf032b7 100644
--- a/docs/gnulinux/index.md
+++ b/docs/gnulinux/index.md
@@ -25,7 +25,8 @@ instructions have yet to be written.**
 
 
 
-Copyright © 2014, 2015 Leah Rowe <info@minifree.org>\
+Copyright © 2014, 2015 Leah Rowe <info@minifree.org>
+
 Permission is granted to copy, distribute and/or modify this document
 under the terms of the Creative Commons Attribution-ShareAlike 4.0
 International license or any later version published by Creative