Typographically correct quotes

3 files changed, 34 insertions, 34 deletions

diff --git a/docs/bsd/freebsd.md b/docs/bsd/freebsd.md
index eb0a1236..085b989c 100644
--- a/docs/bsd/freebsd.md
+++ b/docs/bsd/freebsd.md
@@ -4,11 +4,11 @@ How to install FreeBSD on a libreboot system
 
 This section relates to preparing, booting and installing FreeBSD on
 your libreboot system, using nothing more than a USB flash drive (and
-*dd*). They\'ve only been tested on a Lenovo ThinkPad x200.
+*dd*). They've only been tested on a Lenovo ThinkPad x200.
 
 It is expected that you use text mode in libreboot (txtmode images), for
 the early boot process in FreeBSD. **Booting the installer results in a
-red flickering text display, and doesn\'t boot.**
+red flickering text display, and doesn't boot.**
 
 Thanks go to ioxcide in [this Reddit
 post](https://www.reddit.com/r/BSD/comments/53jt70/libreboot_and_bsds/)
@@ -16,7 +16,7 @@ for the initial instructions.
 
 TODO: test FreeBSD more extensively, and make sure it works (and fix it
 if it does not). Instructions are provided here, to boot and install
-FreeBSD but we\'re not sure whether it is currently fully compatible
+FreeBSD but we're not sure whether it is currently fully compatible
 with libreboot.
 
 -   [Prepare the USB drive (in FreeBSD)](#prepare)
@@ -66,7 +66,7 @@ Connect the USB drive. Check dmesg:\
 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
+Check that it wasn't automatically mounted. If it was, unmount it. For
 example:\
 **\$ doas umount /dev/sd3i**\
 
@@ -90,7 +90,7 @@ Connect the USB drive. Check dmesg:\
 Check lsblk to confirm which drive it is:\
 **\$ lsblk**
 
-Check that it wasn\'t automatically mounted. If it was, unmount it. For
+Check that it wasn't automatically mounted. If it was, unmount it. For
 example:\
 **\$ sudo umount /dev/sdX\***\
 **\# umount /dev/sdX\***
@@ -153,16 +153,16 @@ TODO
 Troubleshooting
 ===============
 
-Most of these issues occur when using libreboot with coreboot\'s \'text
-mode\' instead of the coreboot framebuffer. This mode is useful for
+Most of these issues occur when using libreboot with coreboot's 'text
+mode' instead of the coreboot framebuffer. This mode is useful for
 booting payloads like memtest86+ which expect text-mode, but for FreeBSD
 it can be problematic when they are trying to switch to a framebuffer
-because it doesn\'t exist.
+because it doesn't exist.
 
 In most cases, you should use the vesafb ROM images. Example filename:
 libreboot\_ukdvorak\_vesafb.rom.
 
-won\'t boot\...something about file not found
+won't boot\...something about file not found
 ---------------------------------------------
 
 Your device names (i.e. usb0, usb1, sd0, sd1, wd0, ahci0, hd0, etc) and
diff --git a/docs/bsd/netbsd.md b/docs/bsd/netbsd.md
index b3bb722a..70845469 100644
--- a/docs/bsd/netbsd.md
+++ b/docs/bsd/netbsd.md
@@ -4,7 +4,7 @@ How to install NetBSD on a libreboot system
 
 This section relates to preparing, booting and installing NetBSD on your
 libreboot system, using nothing more than a USB flash drive (and *dd*).
-They\'ve only been tested on a librebooted ThinkPad X60.
+They've only been tested on a librebooted ThinkPad X60.
 
 It is expected that you use text mode in libreboot (txtmode images), for
 the early boot process in NetBSD. **Suspend/hibernate is broken,
@@ -62,7 +62,7 @@ Connect the USB drive. Check dmesg:\
 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
+Check that it wasn't automatically mounted. If it was, unmount it. For
 example:\
 **\$ doas umount /dev/sd3i**\
 
@@ -86,7 +86,7 @@ Connect the USB drive. Check dmesg:\
 Check lsblk to confirm which drive it is:\
 **\$ lsblk**
 
-Check that it wasn\'t automatically mounted. If it was, unmount it. For
+Check that it wasn't automatically mounted. If it was, unmount it. For
 example:\
 **\$ sudo umount /dev/sdX\***\
 **\# umount /dev/sdX\***
@@ -145,22 +145,22 @@ NetBSD will start booting. Yay!
 Configuring Grub
 ----------------
 
-If you don\'t want to drop to the GRUB command line and type in a
+If you don't want to drop to the GRUB command line and type in a
 command to boot NetBSD every time, you can create a GRUB configuration
-that\'s aware of your NetBSD installation and that will automatically be
+that's aware of your NetBSD installation and that will automatically be
 used by libreboot.
 
 On your NetBSD root partition, create the **/grub** directory and add
 the file **libreboot\_grub.cfg** to it. Inside the
 **libreboot\_grub.cfg** add these lines:
 
-**default=0 timeout=3 menuentry \"NetBSD\" {\
+**default=0 timeout=3 menuentry "NetBSD" {\
     knetbsd -r wd0a (ahci0,netbsd1)/netbsd\
 }\
 **
 
-The next time you boot, you\'ll see the old Grub menu for a few seconds,
-then you\'ll see the a new menu with only NetBSD on the list. After 3
+The next time you boot, you'll see the old Grub menu for a few seconds,
+then you'll see the a new menu with only NetBSD on the list. After 3
 seconds NetBSD will boot, or you can hit enter to boot.
 
 [Back to top of page](#pagetop).
@@ -170,16 +170,16 @@ seconds NetBSD will boot, or you can hit enter to boot.
 Troubleshooting
 ===============
 
-Most of these issues occur when using libreboot with coreboot\'s \'text
-mode\' instead of the coreboot framebuffer. This mode is useful for
+Most of these issues occur when using libreboot with coreboot's 'text
+mode' instead of the coreboot framebuffer. This mode is useful for
 booting payloads like memtest86+ which expect text-mode, but for NetBSD
 it can be problematic when they are trying to switch to a framebuffer
-because it doesn\'t exist.
+because it doesn't exist.
 
 In most cases, you should use the vesafb ROM images. Example filename:
 libreboot\_ukdvorak\_vesafb.rom.
 
-won\'t boot\...something about file not found
+won't boot\...something about file not found
 ---------------------------------------------
 
 Your device names (i.e. usb0, usb1, sd0, sd1, wd0, ahci0, hd0, etc) and
diff --git a/docs/bsd/openbsd.md b/docs/bsd/openbsd.md
index 284f0468..783bd7bb 100644
--- a/docs/bsd/openbsd.md
+++ b/docs/bsd/openbsd.md
@@ -11,7 +11,7 @@ LibertyBSD and prioritise that in this guide.
 
 This section relates to preparing, booting and installing OpenBSD on
 your libreboot system, using nothing more than a USB flash drive (and
-*dd*). They\'ve only been tested on a Lenovo ThinkPad x200.
+*dd*). They've only been tested on a Lenovo ThinkPad x200.
 
 -   [Prepare the USB drive (in OpenBSD)](#prepare)
 -   [Installing OpenBSD without full disk encryption](#noencryption)
@@ -44,7 +44,7 @@ Connect the USB drive. Check dmesg:\
 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
+Check that it wasn't automatically mounted. If it was, unmount it. For
 example:\
 **\$ doas umount /dev/sd3i**\
 
@@ -85,7 +85,7 @@ Connect the USB drive. Check dmesg:\
 Check lsblk to confirm which drive it is:\
 **\$ lsblk**
 
-Check that it wasn\'t automatically mounted. If it was, unmount it. For
+Check that it wasn't automatically mounted. If it was, unmount it. For
 example:\
 **\$ sudo umount /dev/sdX\***\
 **\# umount /dev/sdX\***
@@ -141,7 +141,7 @@ to boot a truly fully encrypted OpenBSD or LibertyBSD installation, by
 putting everything in the flash chip.**
 
 Alternatively, modifying GRUB to support booting fully encrypted OpenBSD
-installations would be possible, but probably not feasible; it\'s an
+installations would be possible, but probably not feasible; it's an
 alien codebase to the OpenBSD project, not tightly integrated and the
 OpenBSD bootloader already works.
 
@@ -166,22 +166,22 @@ OpenBSD will start booting. Yay!
 Configuring Grub
 ----------------
 
-If you don\'t want to drop to the GRUB command line and type in a
+If you don't want to drop to the GRUB command line and type in a
 command to boot OpenBSD every time, you can create a GRUB configuration
-that\'s aware of your OpenBSD installation and that will automatically
+that's aware of your OpenBSD installation and that will automatically
 be used by libreboot.
 
 On your OpenBSD root partition, create the **/grub** directory and add
 the file **libreboot\_grub.cfg** to it. Inside the
 **libreboot\_grub.cfg** add these lines:
 
-**default=0 timeout=3 menuentry \"OpenBSD\" {\
+**default=0 timeout=3 menuentry "OpenBSD" {\
     kopenbsd -r sd0a (ahci0,openbsd1)/bsd\
 }\
 **
 
-The next time you boot, you\'ll see the old Grub menu for a few seconds,
-then you\'ll see the a new menu with only OpenBSD on the list. After 3
+The next time you boot, you'll see the old Grub menu for a few seconds,
+then you'll see the a new menu with only OpenBSD on the list. After 3
 seconds OpenBSD will boot, or you can hit enter to boot.
 
 [Back to top of page](#pagetop).
@@ -191,16 +191,16 @@ seconds OpenBSD will boot, or you can hit enter to boot.
 Troubleshooting
 ===============
 
-Most of these issues occur when using libreboot with coreboot\'s \'text
-mode\' instead of the coreboot framebuffer. This mode is useful for
+Most of these issues occur when using libreboot with coreboot's 'text
+mode' instead of the coreboot framebuffer. This mode is useful for
 booting payloads like memtest86+ which expect text-mode, but for OpenBSD
 it can be problematic when they are trying to switch to a framebuffer
-because it doesn\'t exist.
+because it doesn't exist.
 
 In most cases, you should use the vesafb ROM images. Example filename:
 libreboot\_ukdvorak\_vesafb.rom.
 
-won\'t boot\...something about file not found
+won't boot\...something about file not found
 ---------------------------------------------
 
 Your device names (i.e. usb0, usb1, sd0, sd1, wd0, ahci0, hd0, etc) and