More code blocks

3 files changed, 12 insertions, 12 deletions

diff --git a/docs/gnulinux/configuring_parabola.md b/docs/gnulinux/configuring_parabola.md
index 0739038e..ba54dde1 100644
--- a/docs/gnulinux/configuring_parabola.md
+++ b/docs/gnulinux/configuring_parabola.md
@@ -94,8 +94,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**\
+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**\
 For most people this should be enough, but if you don't have DHCP on
@@ -610,8 +610,8 @@ 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:\
-\$ **cp /etc/skel/.xinitrc \~**\
+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\
diff --git a/docs/gnulinux/encrypted_parabola.md b/docs/gnulinux/encrypted_parabola.md
index afa4d137..f7faf575 100644
--- a/docs/gnulinux/encrypted_parabola.md
+++ b/docs/gnulinux/encrypted_parabola.md
@@ -68,8 +68,8 @@ 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:\
-\# **dd if=/dev/urandom of=/dev/sda; sync**\
+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
@@ -523,8 +523,8 @@ adapt:\
 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**\
+would be really nice):
+    $ ./cbfstool libreboot.rom print
 Extract grubtest.cfg:\
 \$ **./cbfstool libreboot.rom extract -n grubtest.cfg -f grubtest.cfg**\
 And modify:\
diff --git a/docs/gnulinux/grub_cbfs.md b/docs/gnulinux/grub_cbfs.md
index 538a04fd..d15e70d5 100644
--- a/docs/gnulinux/grub_cbfs.md
+++ b/docs/gnulinux/grub_cbfs.md
@@ -138,8 +138,8 @@ 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:\
-\$ **sudo flashrom -p internal -r libreboot.rom**\
+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:\
@@ -194,8 +194,8 @@ 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:\
-\# **./flash forceupdate libreboot.rom**\
+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
 up with your new test configuration.**