Fix another class of code bug

4 files changed, 14 insertions, 14 deletions

diff --git a/docs/gnulinux/configuring_parabola.md b/docs/gnulinux/configuring_parabola.md
index ba54dde1..12c05109 100644
--- a/docs/gnulinux/configuring_parabola.md
+++ b/docs/gnulinux/configuring_parabola.md
@@ -96,8 +96,8 @@ 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
-You can stop it later by running:\
-\# **systemctl stop dhcpcd.service**\
+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:\
 [Setup network connection in Parabola](#network)
@@ -621,8 +621,8 @@ export LANG=en\_GB.UTF-8\
 \
 \# Start lxde desktop\
 exec startlxde\
-* Now make sure that it is executable:\
-\$ **chmod +x .xinitrc**
+* Now make sure that it is executable:
+    $ chmod +x .xinitrc
 
 [Back to top of page.](#pagetop)
 
diff --git a/docs/gnulinux/encrypted_debian.md b/docs/gnulinux/encrypted_debian.md
index b0f0b586..6dfb1435 100644
--- a/docs/gnulinux/encrypted_debian.md
+++ b/docs/gnulinux/encrypted_debian.md
@@ -200,8 +200,8 @@ ecryptfs
 If you didn't encrypt your home directory, then you can safely ignore
 this section.
 
-Immediately after logging in, do that:\
-\$ **sudo ecryptfs-unwrap-passphrase**
+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
 directory from another system, so write it down and keep the note
diff --git a/docs/gnulinux/encrypted_parabola.md b/docs/gnulinux/encrypted_parabola.md
index f7faf575..f17fa10e 100644
--- a/docs/gnulinux/encrypted_parabola.md
+++ b/docs/gnulinux/encrypted_parabola.md
@@ -73,8 +73,8 @@ Securely wipe the drive:
 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**
+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
 your distro) then it is already 'wiped'. You should just wipe the LUKS
@@ -525,8 +525,8 @@ 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
-Extract grubtest.cfg:\
-\$ **./cbfstool libreboot.rom extract -n grubtest.cfg -f grubtest.cfg**\
+Extract grubtest.cfg:
+    $ ./cbfstool libreboot.rom extract -n grubtest.cfg -f grubtest.cfg\
 And modify:\
 \$ **vi grubtest.cfg**
 
diff --git a/docs/gnulinux/grub_cbfs.md b/docs/gnulinux/grub_cbfs.md
index d15e70d5..24fd2108 100644
--- a/docs/gnulinux/grub_cbfs.md
+++ b/docs/gnulinux/grub_cbfs.md
@@ -122,8 +122,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:\
-\# **pacman -S flashrom**
+available from the repositories:
+    # pacman -S flashrom
 
 [Back to top of page.](#pagetop)
 
@@ -190,8 +190,8 @@ Testing
 
 **Now you have a modified ROM. Refer back to
 [../install/\#flashrom](../install/#flashrom) for information on how to
-flash it.\
-\$ **cd /libreboot\_util** \# **./flash update libreboot.rom**\
+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: