Unbork some things

5 files changed, 157 insertions, 157 deletions

diff --git a/docs/gnulinux/configuring_parabola.md b/docs/gnulinux/configuring_parabola.md
index 76870bda..23e22d19 100644
--- a/docs/gnulinux/configuring_parabola.md
+++ b/docs/gnulinux/configuring_parabola.md
@@ -97,9 +97,9 @@ 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:\
-\#     systemctl start dhcpcd.service
+    # systemctl start dhcpcd.service
 You can stop it later by running:\
-\#     systemctl stop dhcpcd.service
+    # 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:\
 [Setup network connection in Parabola](#network)
@@ -129,12 +129,12 @@ 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:\
-\#     pacman -Syy
+    # 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:\
-\# **pacman -Syu**
+# **pacman -Syu**
 
 **Before installing packages with 'pacman -S', always update first,
 using the notes above.**
@@ -156,7 +156,7 @@ work.
 
 The Arch forum can also be useful, if others have the same issue as you
 (if you encounter issues, that is). The *Parabola* IRC channel
-(\#parabola on freenode) can also help you.
+(#parabola on freenode) can also help you.
 
 Due to this and the volatile nature of Parabola/Arch, you should only
 update when you have at least a couple hours of spare time in case of
@@ -199,7 +199,7 @@ old package information, updated automatically when you do anything in
 pacman).**
 
 To clean out all old packages that are cached:\
-\# **pacman -Sc**
+# **pacman -Sc**
 
 The wiki cautions that this should be used with care. For example, since
 older packages are deleted from the repo, if you encounter issues and
@@ -208,7 +208,7 @@ 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:\
-\#     pacman -Scc
+    # 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
 space is at a premium.
@@ -254,9 +254,9 @@ access to the entire operating system.
 Read the entire document linked to above, and then continue.
 
 Add your user:\
-\#     useradd -m -G wheel -s /bin/bash *yourusername*
+    # useradd -m -G wheel -s /bin/bash *yourusername*
 Set a password:\
-\# **passwd *yourusername***
+# **passwd *yourusername***
 
 Use of the *diceware method* is recommended, for generating secure
 passphrases (instead of passwords).
@@ -282,7 +282,7 @@ the background behind the decision by Arch (Parabola's upstream
 supplier) to use systemd.
 
 The manpage should also help:\
-\#     man systemd
+    # man systemd
 The section on 'unit types' is especially useful.
 
 According to the wiki, systemd 'journal' keeps logs of a size up to
@@ -293,7 +293,7 @@ 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=*\
+*#SystemMaxUse=*\
 Change it to say:\
 *SystemMaxUse=50M*
 
@@ -302,7 +302,7 @@ The wiki also recommended a method for forwarding journal output to TTY
 to switch between terminals). I decided not to enable it.
 
 Restart journald:\
-\# **systemctl restart systemd-journald**
+# **systemctl restart systemd-journald**
 
 The wiki recommends that if the journal gets too large, you can also
 simply delete (rm -Rf) everything inside /var/log/journald/* but
@@ -313,9 +313,9 @@ delete older records when the journal size reaches it's limit
 
 Finally, the wiki mentions 'temporary' files and the utility for
 managing them.\
-\#     man systemd-tmpfiles
+    # man systemd-tmpfiles
 The command for 'clean' is:\
-\#     systemd-tmpfiles \--clean
+    # 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
 in /etc/tmpfiles.d/ and /usr/lib/tmpfiles.d/ to know what actions to
@@ -325,7 +325,7 @@ 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:\
-\#     man tmpfiles.d
+    # man tmpfiles.d
 Read that manpage, and then continue studying all the files.
 
 The systemd developers tell me that it isn't usually necessary to touch
@@ -349,10 +349,10 @@ and below the 'extra' section add:\
 Include = /etc/pacman.d/mirrorlist*
 
 Now sync with the repository:\
-\# **pacman -Syy**
+# **pacman -Syy**
 
 List all available packages in this repository:\
-\# **pacman -Sl kernels**
+# **pacman -Sl kernels**
 
 In the end, I decided not to install anything from it but I kept the
 repository enabled regardless.
@@ -373,12 +373,12 @@ 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):\
-\#     hostnamectl set-hostname *yourhostname*
+    # hostnamectl set-hostname *yourhostname*
 This writes the specified hostname to /etc/hostname. More information
 can be found in these manpages:\
-\#     man hostname
-\#     info hostname
-\# **man hostnamectl**
+    # 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\
@@ -400,7 +400,7 @@ According to the Arch wiki,
 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:\
-\# **lspci -v**
+# **lspci -v**
 
 Look at the remaining sections *'Kernel driver in use'* and *'Kernel
 modules'*. In my case it was as follows:\
@@ -409,7 +409,7 @@ Kernel modules: e1000e*
 
 Check that the driver was loaded by issuing *dmesg | grep module\_name*.
 In my case, I did:\
-\# **dmesg | grep e1000e**
+# **dmesg | grep e1000e**
 
 ### Network device names {#network_devicenames}
 
@@ -431,7 +431,7 @@ For background information, read [Predictable Network Interface
 Names](http://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames/)
 
 Show device names:\
-\# **ls /sys/class/net**
+# **ls /sys/class/net**
 
 Changing the device names is possible (I chose not to do it):\
 <https://wiki.archlinux.org/index.php/Configuring_Network#Change_device_name>
@@ -463,7 +463,7 @@ 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):\
-\#     pacman -S smartmontools
+    # pacman -S smartmontools
 Read <https://wiki.archlinux.org/index.php/S.M.A.R.T.> to learn how to
 use it.
 
@@ -488,36 +488,36 @@ provide LXDE by default.
 Based on <https://wiki.archlinux.org/index.php/Xorg>.
 
 Firstly, install it!\
-\#     pacman -S xorg-server
+    # pacman -S xorg-server
 I also recommend installing this (contains lots of useful tools,
 including *xrandr*):\
-\# **pacman -S xorg-server-utils**
+# **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.\
-\#     pacman -S xf86-video-intel
+    # pacman -S xf86-video-intel
 For other systems you can try:\
-\#     pacman -Ss xf86-video- | less
+    # 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:\
-\#     pacman -Sg xorg-drivers
+    # pacman -Sg xorg-drivers
 
 Mostly you will rely on a display manager, but in case you ever want to
 start X without one:\
-\# **pacman -S xorg-xinit**
+# **pacman -S xorg-xinit**
 
 <optional>\
    Arch wiki recommends installing these, for testing that X works:\
-   \#     pacman -S xorg-twm xorg-xclock xterm
+       # pacman -S xorg-twm xorg-xclock xterm
    Refer to <https://wiki.archlinux.org/index.php/Xinitrc>. and test X:\
-   \#     startx
+       # startx
    When you are satisfied, type ***exit*** in xterm, inside the X
 session.\
-   Uninstall them (clutter. eww): \# **pacman -S xorg-xinit xorg-twm
+   Uninstall them (clutter. eww): # **pacman -S xorg-xinit xorg-twm
 xorg-xclock xterm**\
 </optional>
 
@@ -536,7 +536,7 @@ not actually be the same in X.
 
 To see what layout you currently use, try this on a terminal emulator in
 X:\
-\# **setxkbmap -print -verbose 10**
+# **setxkbmap -print -verbose 10**
 
 In my case, I wanted to use the Dvorak (UK) keyboard which is quite
 different from Xorg's default Qwerty (US) layout.
@@ -583,27 +583,27 @@ 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:\
-\# **pacman -S lxde obconf**
+# **pacman -S lxde obconf**
 
 I didn't want the following, so I removed them:\
-\# **pacman -R lxmusic lxtask**
+# **pacman -R lxmusic lxtask**
 
 I also lazily installed all fonts:\
-\# **pacman -S $(pacman -Ssq ttf-)**
+# **pacman -S $(pacman -Ssq ttf-)**
 
 And a mail client:\
-\# **pacman -S icedove**
+# **pacman -S icedove**
 
 In IceCat, go to *Preferences :: Advanced* and disable *GNU IceCat
 Health Report*.
 
 I also like to install these:\
-\# **pacman -S xsensors stress htop**
+# **pacman -S xsensors stress htop**
 
 Enable LXDM (the default display manager, providing a graphical login):\
-\#     systemctl enable lxdm.service
+    # systemctl enable lxdm.service
 It will start when you boot up the system. To start it now, do:\
-\# **systemctl start lxdm.service**
+# **systemctl start lxdm.service**
 
 Log in with your standard (non-root) user that you created earlier. It
 is advisable to also create an xinitrc rule in case you ever want to
@@ -611,15 +611,15 @@ start lxde without lxdm. Read
 <https://wiki.archlinux.org/index.php/Xinitrc>.
 
 Open LXterminal:\
-$     cp /etc/skel/.xinitrc \~
+    $ 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\
+*# 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\
+# Start lxde desktop\
 exec startlxde\
 * Now make sure that it is executable:\
 $ **chmod +x .xinitrc**
@@ -648,7 +648,7 @@ NOTE TO SELF: come back to this later.
 ### LXDE - screenlock {#lxde_screenlock}
 
 Arch wiki recommends to use *xscreensaver*:\
-\# **pacman -S xscreensaver**
+# **pacman -S xscreensaver**
 
 Under *Preferences :: Screensaver* in the LXDE menu, I chose *Mode:
 Blank Screen Only*, setting *Blank After*, *Cycle After* and *Lock
@@ -699,30 +699,30 @@ Refer to <https://wiki.archlinux.org/index.php/LXDE#Network_Management>.
 Then I read: <https://wiki.archlinux.org/index.php/NetworkManager>.
 
 Install Network Manager:\
-\# **pacman -S networkmanager**
+# **pacman -S networkmanager**
 
 You will also want the graphical applet:\
-\#     pacman -S network-manager-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:\
-\# **pacman -S networkmanager-openvpn**
+# **pacman -S networkmanager-openvpn**
 
 LXDE uses openbox, so I refer to:\
 <https://wiki.archlinux.org/index.php/NetworkManager#Openbox>.
 
 It tells me for the applet I need:\
-\#     pacman -S xfce4-notifyd gnome-icon-theme
+    # pacman -S xfce4-notifyd gnome-icon-theme
 Also, for storing authentication details (wifi) I need:\
-\# **pacman -S gnome-keyring**
+# **pacman -S gnome-keyring**
 
 I wanted to quickly enable networkmanager:\
-\#     systemctl stop dhcpcd
-\#     systemctl start NetworkManager
+    # systemctl stop dhcpcd
+    # systemctl start NetworkManager
 Enable NetworkManager at boot time:\
-\# **systemctl enable NetworkManager**
+# **systemctl enable NetworkManager**
 
 Restart LXDE (log out, and then log back in).
 
diff --git a/docs/gnulinux/encrypted_parabola.md b/docs/gnulinux/encrypted_parabola.md
index f04b969a..36a60c61 100644
--- a/docs/gnulinux/encrypted_parabola.md
+++ b/docs/gnulinux/encrypted_parabola.md
@@ -71,12 +71,12 @@ article](https://wiki.archlinux.org/index.php/Solid_State_Drives). Edit
 whole article and keep all points in mind, adapting them for this guide.
 
 Securely wipe the drive:\
-\#     dd if=/dev/urandom of=/dev/sda; sync
+    # 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:\
-\# **dd if=/dev/urandom of=/dev/sda bs=2M; sync**
+# **dd if=/dev/urandom of=/dev/sda bs=2M; sync**
 
 If your drive was already LUKS encrypted (maybe you are re-installing
 your distro) then it is already 'wiped'. You should just wipe the LUKS
@@ -85,7 +85,7 @@ 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:\
-\#     head -c 3145728 /dev/urandom > /dev/sda; sync
+    # 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).
 
@@ -96,8 +96,8 @@ Change keyboard layout
 
 Parabola live shell assumes US Qwerty. If you have something different,
 list the available keymaps and use yours:\
-\#     localectl list-keymaps
-\#     loadkeys LAYOUT
+    # localectl list-keymaps
+    # loadkeys LAYOUT
 For me, LAYOUT would have been dvorak-uk.
 
 
@@ -125,7 +125,7 @@ dm-mod
 
 device-mapper will be used - a lot. Make sure that the kernel module is
 loaded:\
-\# **modprobe dm-mod**
+# **modprobe dm-mod**
 
 Create LUKS partition
 ---------------------
@@ -139,7 +139,7 @@ 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:\
-\# **cfdisk /dev/sda**
+# **cfdisk /dev/sda**
 
 I create a single large sda1 filling the whole drive, leaving it as the
 default type 'Linux' (83).
@@ -152,15 +152,15 @@ I am then directed to
 Parabola forces you to RTFM. Do that.
 
 It tells me to run:\
-\# **cryptsetup benchmark** (for making sure the list below is
+# **cryptsetup benchmark** (for making sure the list below is
 populated)\
 Then:\
-\#     cat /proc/crypto
+    # 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:\
-\# **man cryptsetup**
+# **man cryptsetup**
 
 Following that page, based on my requirements, I do the following based
 on
@@ -169,7 +169,7 @@ Reading through, it seems like Serpent (encryption) and Whirlpool (hash)
 is the best option.
 
 I am initializing LUKS with the following:\
-\# **cryptsetup -v \--cipher serpent-xts-plain64 \--key-size 512 \--hash
+# **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
 lowercase/uppercase numbers, letters, symbols etc all in a random
@@ -187,29 +187,29 @@ Create LVM
 Now I refer to <https://wiki.archlinux.org/index.php/LVM>.
 
 Open the LUKS partition:\
-\#     cryptsetup luksOpen /dev/sda1 lvm
+    # cryptsetup luksOpen /dev/sda1 lvm
 (it will be available at /dev/mapper/lvm)
 
 Create LVM partition:\
-\#     pvcreate /dev/mapper/lvm
+    # pvcreate /dev/mapper/lvm
 Show that you just created it:\
-\# **pvdisplay**
+# **pvdisplay**
 
 Now I create the volume group, inside of which the logical volumes will
 be created:\
-\#     vgcreate matrix /dev/mapper/lvm
+    # vgcreate matrix /dev/mapper/lvm
 (volume group name is 'matrix' - choose your own name, if you like)
 Show that you created it:\
-\# **vgdisplay**
+# **vgdisplay**
 
 Now create the logical volumes:\
-\# **lvcreate -L 2G matrix -n swapvol** (2G swap partition, named
+# **lvcreate -L 2G matrix -n swapvol** (2G swap partition, named
 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>.\
-\# **lvcreate -l +100%FREE matrix -n root** (single large partition in
+# **lvcreate -l +100%FREE matrix -n root** (single large partition in
 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
@@ -219,7 +219,7 @@ system (typical use case), a root and a swap will do (really).
 
 Verify that the logical volumes were created, using the following
 command:\
-\# **lvdisplay**
+# **lvdisplay**
 
 
 
@@ -227,15 +227,15 @@ Create / and swap partitions, and mount
 ---------------------------------------
 
 For the swapvol LV I use:\
-\#     mkswap /dev/mapper/matrix-swapvol
+    # mkswap /dev/mapper/matrix-swapvol
 Activate swap:\
-\# **swapon /dev/matrix/swapvol**
+# **swapon /dev/matrix/swapvol**
 
 For the root LV I use:\
-\# **mkfs.btrfs /dev/mapper/matrix-root**
+# **mkfs.btrfs /dev/mapper/matrix-root**
 
 Mount the root (/) partition:\
-\# **mount /dev/matrix/root /mnt**
+# **mount /dev/matrix/root /mnt**
 
 
 
@@ -250,8 +250,8 @@ Now I am following the rest of
 referenced <https://wiki.archlinux.org/index.php/Installation_guide>.
 
 Create /home and /boot on root mountpoint:\
-\#     mkdir -p /mnt/home
-\# **mkdir -p /mnt/boot**
+    # mkdir -p /mnt/home
+# **mkdir -p /mnt/boot**
 
 Once all the remaining partitions, if any, have been mounted, the
 devices are ready to install Parabola.
@@ -259,9 +259,9 @@ 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:\
-\#     pacman -Syy
-\#     pacman -Syu
-\# **pacman -Sy pacman** (and then I did the other 2 steps above,
+    # pacman -Syy
+    # pacman -Syu
+# **pacman -Sy pacman** (and then I did the other 2 steps above,
 again)\
 In my case I did the steps in the next paragraph, and followed the steps
 in this paragraph again.
@@ -272,23 +272,23 @@ 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:\
-   \#     pacman -Sy parabola-keyring
+       # pacman -Sy parabola-keyring
    It says that if you get GPG errors, then it's probably an expired
 key and, therefore, you should do:\
-   \#     pacman-key \--populate parabola
-   \#     pacman-key \--refresh-keys
-   \#     pacman -Sy parabola-keyring
+       # 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:\
-   \#     dirmngr </dev/null
+       # 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):\
-   \#     date MMDDhhmm\[\[CC\]YY\]\[.ss\]
+       # date MMDDhhmm\[\[CC\]YY\]\[.ss\]
    I also had to install:\
-   \#     pacman -S archlinux-keyring
-   \#     pacman-key \--populate archlinux
+       # pacman -S archlinux-keyring
+       # pacman-key \--populate archlinux
    In my case I saw some conflicting files reported in pacman, stopping
 me from using it.\
    I deleted the files that it mentioned and then it worked.
@@ -296,13 +296,13 @@ 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:\
-   \#     pacman -Sf licenses
+       # pacman -Sf licenses
 </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:\
-\# **pacstrap /mnt base base-devel wpa\_supplicant dialog iw
+# **pacstrap /mnt base base-devel wpa\_supplicant dialog iw
 wpa\_actiond**
 
 
@@ -313,21 +313,21 @@ 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):\
-\#     genfstab -U -p /mnt >> /mnt/etc/fstab
+    # genfstab -U -p /mnt >> /mnt/etc/fstab
 Check the created file:\
-\#     cat /mnt/etc/fstab
+    # cat /mnt/etc/fstab
 (If there are any errors, edit the file. Do **NOT** run the genfstab
 command again!)
 
 Chroot into new system:\
-\# **arch-chroot /mnt /bin/bash**
+# **arch-chroot /mnt /bin/bash**
 
 It's a good idea to have this installed:\
-\# **pacman -S linux-libre-lts**
+# **pacman -S linux-libre-lts**
 
 It was also suggested that you should install this kernel (read up on
 what GRSEC is):\
-\# **pacman -S linux-libre-grsec**
+# **pacman -S linux-libre-grsec**
 
 This is another kernel that sits inside /boot, which you can use. LTS
 means 'long-term support'. These are so-called 'stable' kernels that
@@ -335,35 +335,35 @@ 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:\
-\# **pacman -S wget**
+# **pacman -S wget**
 
 Locale:\
-\#     vi /etc/locale.gen
+    # vi /etc/locale.gen
 Uncomment your needed localisations. For example en\_GB.UTF-8 (UTF-8 is
 highly recommended over other options).\
-\#     locale-gen
-\#     echo LANG=en\_GB.UTF-8 > /etc/locale.conf
-\# **export LANG=en\_GB.UTF-8**
+    # locale-gen
+    # echo LANG=en\_GB.UTF-8 > /etc/locale.conf
+# **export LANG=en\_GB.UTF-8**
 
 Console font and keymap:\
-\#     vi /etc/vconsole.conf
+    # vi /etc/vconsole.conf
 In my case:
 
     KEYMAP=dvorak-uk
     FONT=lat9w-16
 
 Time zone:\
-\#     ln -s /usr/share/zoneinfo/Europe/London /etc/localtime
+    # ln -s /usr/share/zoneinfo/Europe/London /etc/localtime
 (Replace Zone and Subzone to your liking. See /usr/share/zoneinfo)
 
 Hardware clock:\
-\# **hwclock \--systohc \--utc**
+# **hwclock \--systohc \--utc**
 
 Hostname: Write your hostname to /etc/hostname. For example, if your
 hostname is parabola:\
-\#     echo parabola > /etc/hostname
+    # echo parabola > /etc/hostname
 Add the same hostname to /etc/hosts:\
-\#     vi /etc/hosts
+    # vi /etc/hosts
 
     #<ip-address> <hostname.domain.org> <hostname>
     127.0.0.1   localhost.localdomain   localhost   parabola
@@ -375,9 +375,9 @@ Configure the network: Refer to
 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
+/usr/lib/initcpio/install. (# **mkinitcpio -H hookname** gives
 information about each hook.) Specifically, for this use case:\
-\#     vi /etc/mkinitcpio.conf
+    # vi /etc/mkinitcpio.conf
 Then modify the file like so:
 
 -   MODULES="i915"
@@ -402,18 +402,18 @@ 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):\
-\#     mkinitcpio -p linux-libre
+    # mkinitcpio -p linux-libre
 Also do it for linux-libre-lts:\
-\#     mkinitcpio -p linux-libre-lts
+    # mkinitcpio -p linux-libre-lts
 Also do it for linux-libre-grsec:\
-\# **mkinitcpio -p 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>.\
-\#     vi /etc/pam.d/passwd
+    # vi /etc/pam.d/passwd
 Add rounds=65536 at the end of the uncommented 'password' line.\
-\#     passwd root
+    # passwd root
 Make sure to set a secure password! Also, it must never be the same as
 your LUKS password.
 
@@ -428,17 +428,17 @@ Extra security tweaks
 Based on <https://wiki.archlinux.org/index.php/Security>.
 
 Restrict access to important directories:\
-\# **chmod 700 /boot /etc/{iptables,arptables}**
+# **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*\
+*# 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*\
 To unlock a user manually (if a password attempt is failed 3 times),
 do:\
-\# **pam\_tally \--user *theusername* \--reset** What the above
+# **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.
 
@@ -452,20 +452,20 @@ Unmount, reboot!
 ----------------
 
 Exit from chroot:\
-\# **exit**
+# **exit**
 
 unmount:\
-\#     umount -R /mnt
-\# **swapoff -a**
+    # umount -R /mnt
+# **swapoff -a**
 
 deactivate the lvm lv's:\
-\#     lvchange -an /dev/matrix/root
-\#     lvchange -an /dev/matrix/swapvol
+    # lvchange -an /dev/matrix/root
+    # lvchange -an /dev/matrix/swapvol
 
 Lock the encrypted partition (close it):\
-\# **cryptsetup luksClose lvm**
+# **cryptsetup luksClose lvm**
 
-\#     shutdown -h now
+    # shutdown -h now
 Remove the installation media, then boot up again.
 
 
@@ -521,14 +521,14 @@ 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:\
-\#     flashrom -p internal -r libreboot.rom
+    # 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.\
 You can check if everything is in there (*grub.cfg* and *grubtest.cfg*
 would be really nice):\
-$     ./cbfstool libreboot.rom print
+    $ ./cbfstool libreboot.rom print
 Extract grubtest.cfg:\
-$     ./cbfstool libreboot.rom extract -n grubtest.cfg -f grubtest.cfg
+    $ ./cbfstool libreboot.rom extract -n grubtest.cfg -f grubtest.cfg
 And modify:\
 $ **vi grubtest.cfg**
 
@@ -559,18 +559,18 @@ hardening your GRUB configuration, for security purposes.
 
 Save your changes in grubtest.cfg, then delete the unmodified config
 from the ROM image:\
-$     ./cbfstool libreboot.rom remove -n grubtest.cfg
+    $ ./cbfstool libreboot.rom remove -n grubtest.cfg
 and insert the modified grubtest.cfg:\
 $ **./cbfstool libreboot.rom add -n grubtest.cfg -f grubtest.cfg -t
 raw**\
 
 Now refer to <http://libreboot.org/docs/install/#flashrom>. Cd (up) to
 the libreboot\_util directory and update the flash chip contents:\
-\#     ./flash update libreboot.rom
+    # ./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:\
-\#     ./flash forceupdate libreboot.rom
+    # ./flash forceupdate libreboot.rom
 You should see "Verifying flash\... VERIFIED." written at the end of
 the flashrom output.
 
@@ -601,21 +601,21 @@ $ **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:\
-$     ./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. Once more, refer to
 <http://libreboot.org/docs/install/#flashrom>. Cd to the libreboot\_util
 directory and update the flash chip contents:\
-\#     ./flash update libreboot.rom
+    # ./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*):\
-\# **pacman -R grub**
+# **pacman -R grub**
 
 
 
@@ -637,20 +637,20 @@ 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:\
-\# **dd bs=512 count=4 if=/dev/urandom of=/etc/mykeyfile
+# **dd bs=512 count=4 if=/dev/urandom of=/etc/mykeyfile
 iflag=fullblock**\
 Insert it into the luks volume:\
-\#     cryptsetup luksAddKey /dev/sdX /etc/mykeyfile
+    # 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:\
-\#     FILES="/etc/mykeyfile"
+    # FILES="/etc/mykeyfile"
 Create the initramfs image from scratch:\
-\#     mkinitcpio -p linux-libre
-\#     mkinitcpio -p linux-libre-lts
-\#     mkinitcpio -p linux-libre-grsec
+    # 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:\
-\#     cryptkey=rootfs:/etc/mykeyfile
+    # cryptkey=rootfs:/etc/mykeyfile
 \
 You can also place this inside the grub.cfg that exists in CBFS:
 [grub\_cbfs.html](grub_cbfs.html).
diff --git a/docs/gnulinux/grub_boot_installer.md b/docs/gnulinux/grub_boot_installer.md
index 592b20f7..8fa8dcb6 100644
--- a/docs/gnulinux/grub_boot_installer.md
+++ b/docs/gnulinux/grub_boot_installer.md
@@ -38,12 +38,12 @@ Check lsblk to confirm which drive it is:\
 Check that it wasn't automatically mounted. If it was, unmount it. For
 example:\
     $ sudo umount /dev/sdX*
-**\# 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:\
     $ sudo dd if=gnulinux.iso of=/dev/sdX bs=8M; sync
-**\# dd if=gnulinux.iso of=/dev/sdX bs=8M; sync**
+**# dd if=gnulinux.iso of=/dev/sdX bs=8M; sync**
 
 You should now be able to boot the installer from your USB drive.
 Continue reading, for information about how to do that.
diff --git a/docs/gnulinux/grub_cbfs.md b/docs/gnulinux/grub_cbfs.md
index 9eb55c27..7b7c4cf3 100644
--- a/docs/gnulinux/grub_cbfs.md
+++ b/docs/gnulinux/grub_cbfs.md
@@ -52,7 +52,7 @@ Introduction
 
 Download the latest release from <http://libreboot.org/>\
 **If you downloaded from git, refer to
-[../git/\#build\_meta](../git/#build_meta) before continuing.**
+[../git/#build\_meta](../git/#build_meta) before continuing.**
 
 [Back to top of page.](#pagetop)
 
@@ -94,8 +94,8 @@ coreboot payload) that is located in a partition on the main storage.
 
 If you want to adapt a copy of the existing *libreboot* GRUB
 configuration and use that for the libreboot\_grub.cfg file, then follow
-[\#tools](#tools), [\#rom](#rom) and
-[\#extract\_testconfig](#extract_testconfig) to get the
+[#tools](#tools), [\#rom](#rom) and
+[#extract\_testconfig](#extract_testconfig) to get the
 ***grubtest.cfg***. Rename ***grubtest.cfg*** to
 ***libreboot\_grub.cfg*** and save it to ***/boot/grub/*** on the
 running system where it is intended to be used. Modify the file at that
@@ -123,9 +123,9 @@ 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
+[../git/#build\_flashrom](../git/#build_flashrom)). Flashrom is also
 available from the repositories:\
-\# **pacman -S flashrom**
+# **pacman -S flashrom**
 
 [Back to top of page.](#pagetop)
 
@@ -141,11 +141,11 @@ 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:\
-$     sudo flashrom -p internal -r libreboot.rom
-\#     flashrom -p internal -r libreboot.rom
+    $ 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:\
-\# **flashrom -c MX25L6405 -p internal -r libreboot.rom**
+# **flashrom -c MX25L6405 -p internal -r libreboot.rom**
 
 [Back to top of page.](#pagetop)
 
@@ -191,13 +191,13 @@ Testing
 -------
 
 **Now you have a modified ROM. Refer back to
-[../install/\#flashrom](../install/#flashrom) for information on how to
+[../install/#flashrom](../install/#flashrom) for information on how to
 flash it.\
-$     cd /libreboot\_util** \# **./flash update libreboot.rom
+    $ 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:\
-\#     ./flash forceupdate libreboot.rom
+    # ./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
 up with your new test configuration.**
@@ -236,7 +236,7 @@ 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
-[../install/\#flashrom](../install/#flashrom) for information on how to
+[../install/#flashrom](../install/#flashrom) for information on how to
 flash it. It's the same method as you used before. Shut down and then
 boot up with your new configuration.**
 
diff --git a/docs/gnulinux/grub_hardening.md b/docs/gnulinux/grub_hardening.md
index 26de1399..cad4ca40 100644
--- a/docs/gnulinux/grub_hardening.md
+++ b/docs/gnulinux/grub_hardening.md
@@ -36,7 +36,7 @@ image:
 Helpful links:
 
 -   [GRUB manual
-    \#security](https://www.gnu.org/software/grub/manual/html_node/Security.html#Security)
+    #security](https://www.gnu.org/software/grub/manual/html_node/Security.html#Security)
 -   [GRUB info
     pages](http://git.savannah.gnu.org/cgit/grub.git/tree/docs/grub.texi)
 -   [SATA connected storage considered dangerous until proven