Typographically correct quotes

13 files changed, 111 insertions, 111 deletions

diff --git a/docs/install/bbb_setup.md b/docs/install/bbb_setup.md
index f0cd36a3..c8f72f75 100644
--- a/docs/install/bbb_setup.md
+++ b/docs/install/bbb_setup.md
@@ -40,13 +40,13 @@ Hardware requirements
 Shopping list (pictures of this hardware is shown later):
 
 -   A [Flashrom](http://flashrom.org)-compatible external SPI
-    programmer: **BeagleBone Black**, sometimes referred to as \'BBB\',
+    programmer: **BeagleBone Black**, sometimes referred to as 'BBB',
     (rev. C) is highly recommended. You can buy one from
     [Adafruit](https://www.adafruit.com) (USA),
     [ElectroKit](http://electrokit.com) (Sweden) or any of the
     distributors listed [here](http://beagleboard.org/black) (look below
-    \'Purchase\'). We recommend this product because we know that it
-    works well for our purposes and doesn\'t require any non-free
+    'Purchase'). We recommend this product because we know that it
+    works well for our purposes and doesn't require any non-free
     software.
 -   Electrical/insulative tape: cover the entire bottom surface of the
     BBB (the part that rests on a surface). This is important, when
@@ -63,14 +63,14 @@ Shopping list (pictures of this hardware is shown later):
     ships to many countries. Some people find these clips difficult to
     get hold of, especially in South America. If you know of any good
     suppliers, please contact the libreboot project with the relevant
-    information. **If you can\'t get hold of a pomona clip, some other
+    information. **If you can't get hold of a pomona clip, some other
     clips might work, e.g. 3M, but they are not always reliable. You can
     also directly solder the wires to the chip, if that suits you; the
     clip is just for convenience, really.**
 -   **External 3.3V DC power supply**, for powering the flash chip: an
     ATX power supply / PSU (common on Intel/AMD desktop computers) will
     work for this. A lab PSU (DC) will also work (adjusted to 3.3V).
-    -   Getting a multimeter might be worthwhile, to verify that it\'s
+    -   Getting a multimeter might be worthwhile, to verify that it's
         supplying 3.3V.
 -   **External 5V DC power supply** (barrel connector), for powering the
     BBB: the latter can have power supplied via USB, but a dedicated
@@ -78,7 +78,7 @@ Shopping list (pictures of this hardware is shown later):
     places that sell electronics. **OPTIONAL. Only needed if not
     powering with the USB cable, or if you want to use [EHCI
     debug](../misc/bbb_ehci.html)**.
--   **Pin header / jumper cables** (2.54mm / 0.1\" headers): you should
+-   **Pin header / jumper cables** (2.54mm / 0.1" headers): you should
     get male\--male, male\--female and female\--female cables in 10cm
     size. Just get a load of them. Other possible names for these
     cables/wires/leads are as follows:
@@ -123,14 +123,14 @@ PS\_ON\# (this is also how an ATX motherboard turns on a PSU).
 20-pin ATX PSU), and DO \*\*NOT\*\* use pin 21, 22 or 23 (on a 24-pin
 ATX PSU). Those wires (the red ones) are 5V, and they \*\*WILL\*\* kill
 your flash chip. \*\*\*NEVER\*\*\* supply more than 3.3V to your flash
-chip (that is, if it\'s a 3.3V flash chip; 5V and 1.8V SPI flash chips
+chip (that is, if it's a 3.3V flash chip; 5V and 1.8V SPI flash chips
 do exist, but they are rare. Always check what voltage your chip takes.
 Most of them take 3.3V).**
 
 You only need one 3.3V supply and one ground for the flash chip, after
 grounding PS\_ON\#.
 
-The male end of a 0.1\" or 2.54mm header cable is not thick enough to
+The male end of a 0.1" or 2.54mm header cable is not thick enough to
 remain permanently connected to the ATX PSU on its own. When connecting
 header cables to the connector on the ATX PSU, use a female end attached
 to a thicker piece of wire (you could use a paper clip), or wedge the
@@ -188,7 +188,7 @@ element14 brand BBB (sold by Premier Farnell plc. stores like Farnell
 element14, Newark element14, and Embest), you may need to [work around a
 bug](https://groups.google.com/forum/?_escaped_fragment_=msg/beagleboard/LPjCn4LEY2I/alozBGsbTJMJ#!msg/beagleboard/LPjCn4LEY2I/alozBGsbTJMJ)
 in the LED aging init script before you can update your software. If you
-don\'t have a file named /etc/init.d/led\_aging.sh, you can skip this
+don't have a file named /etc/init.d/led\_aging.sh, you can skip this
 step and update your software as described below. Otherwise, replace the
 contents of this file with:
 
@@ -260,7 +260,7 @@ Output:
     No EEPROM/flash device found.
     Note: flashrom can never write if the flash chip isn't found automatically.
 
-This means that it\'s working (the clip isn\'t connected to any flash
+This means that it's working (the clip isn't connected to any flash
 chip, so the error is fine).
 
 
@@ -351,7 +351,7 @@ use higher speeds while maintaining stability.
 tty0\_ in \#libreboot was able to get better flashing speeds with the
 following configuration:
 
--   \"coax\" with 0.1 mm core and aluminum foley (from my kitchen), add
+-   "coax" with 0.1 mm core and aluminum foley (from my kitchen), add
     100 Ohm resistors (serial)
 -   put heatshrink above the foley, for: CS, CLK, D0, D1
 -   Twisted pair used as core (in case more capacitors are needed)
@@ -361,7 +361,7 @@ following configuration:
 
 
 Copyright © 2014, 2015 Leah Rowe <info@minifree.org>\
-Copyright © 2015 Patrick \"P. J.\" McDermott <pj@pehjota.net>\
+Copyright © 2015 Patrick "P. J." McDermott <pj@pehjota.net>\
 Copyright © 2015 Albin Söderqvist\
 Permission is granted to copy, distribute and/or modify this document
 under the terms of the Creative Commons Attribution-ShareAlike 4.0
diff --git a/docs/install/c201.md b/docs/install/c201.md
index d231ff1c..efe50f64 100644
--- a/docs/install/c201.md
+++ b/docs/install/c201.md
@@ -16,12 +16,12 @@ Look at the [list of ROM images](#rom) to see which image is compatible
 with your device.
 
 Libreboot can be installed internally from the device, with sufficient
-privileges. The installation process requires using **Google\'s modified
-version of flashrom**, that has support for reflashing the Chromebook\'s
+privileges. The installation process requires using **Google's modified
+version of flashrom**, that has support for reflashing the Chromebook's
 SPI flash. Otherwise, flashing externally will work with the upstream
 flashrom version.
 
-**Google\'s modified version of flashrom** is free software and its
+**Google's modified version of flashrom** is free software and its
 source code is made available by Google:
 [flashrom](https://chromium.googlesource.com/chromiumos/third_party/flashrom/).\
 It is not distributed along with Libreboot yet. However, it is
@@ -83,7 +83,7 @@ A tty prompt can be obtained by pressing **Ctrl + Alt + Next**. The
 Preparing the device for the installation
 Before installing Libreboot on the device, both its software and
 hardware has to be prepared to allow the installation procedure and to
-ensure that security features don\'t get in the way.
+ensure that security features don't get in the way.
 
 
 Configuring verified boot parameters {#configuring_verified_boot_parameters}
@@ -164,7 +164,7 @@ The resulting flash image can then be flashed back:\
 \# **flashrom -p host -w flash.img**\
 
 You should also see within the output the following:\
-**\"Verifying flash\... VERIFIED.\"**
+**"Verifying flash\... VERIFIED."**
 
 Shut down. The device will now boot to Libreboot.
 
@@ -212,7 +212,7 @@ programmer):\
 \# **flashrom -p *programmer* -w flash.img**\
 
 You should also see within the output the following:\
-**\"Verifying flash\... VERIFIED.\"**
+**"Verifying flash\... VERIFIED."**
 
 The device will now boot to Libreboot.
 
diff --git a/docs/install/ga-g41m-es2l.md b/docs/install/ga-g41m-es2l.md
index 67b7dd7c..c032f613 100644
--- a/docs/install/ga-g41m-es2l.md
+++ b/docs/install/ga-g41m-es2l.md
@@ -23,9 +23,9 @@ Flashing instructions {#clip}
 
 Refer to [bbb\_setup.html](bbb_setup.html) for how to set up the BBB for
 external flashing. **You can only externally reprogram one of the chips
-at a time, and you need to disable the chip that you\'re not flashing,
+at a time, and you need to disable the chip that you're not flashing,
 by connecting 3v3 to /CS of that chip, so you will actually need 2 test
-clips (you also need to connect GND on the chip that you\'re
+clips (you also need to connect GND on the chip that you're
 disabling).**
 
 Here is an image of the flash chip:\
diff --git a/docs/install/index.md b/docs/install/index.md
index b37a5d6c..3b05a3ef 100644
--- a/docs/install/index.md
+++ b/docs/install/index.md
@@ -59,7 +59,7 @@ Information about libreboot ROM images {#rom}
 
 Libreboot distributes pre-compiled ROM images, built from the libreboot
 source code. These images are provided for user convenience, so that
-they don\'t have to build anything from source on their own.
+they don't have to build anything from source on their own.
 
 The ROM images in each archive use the following at the end of the file
 name, if they are built with the GRUB payload:
@@ -72,7 +72,7 @@ used by coreboot native graphics initialization.
 
 *keymap* can be one of several keymaps that keyboard supports (there are
 quite a few), which affects the keyboard layout configuration that is
-used in GRUB. It doesn\'t matter which ROM image you choose here, as far
+used in GRUB. It doesn't matter which ROM image you choose here, as far
 as the keymap in GNU+Linux is concerned.
 
 Keymaps are named appropriately according to each keyboard layout
@@ -195,7 +195,7 @@ Do check the HCL entry: [../hcl/kcma-d8.html](../hcl/kcma-d8.html)
 Intel D945GCLF?
 ---------------
 
-If you\'re running the original Intel factory BIOS, then you will need
+If you're running the original Intel factory BIOS, then you will need
 to flash externally. For instructions on how to do that, refer to
 [d945gclf.html](d945gclf.html).
 
@@ -210,7 +210,7 @@ flash chip, please refer to [x60\_unbrick.html](x60_unbrick.html),
 [x60tablet\_unbrick.html](x60tablet_unbrick.html) or
 [t60\_unbrick.html](t60_unbrick.html). *This probably does not apply to
 you. Most people do not write-protect the flash chip, so you probably
-didn\'t either.*
+didn't either.*
 
 Similarly, it is possible to write-protect the flash chip in coreboot or
 libreboot on GM45 laptops (X200/R400/T400/T500). If you did this, then
@@ -246,7 +246,7 @@ Apple iMac 5,2?
 Internal flashing works, even when flashing from Apple EFI to libreboot.
 Continue reading the instructions below.
 
-**NOTE: If you\'re flashing an older version of Libreboot, the iMac5,2
+**NOTE: If you're flashing an older version of Libreboot, the iMac5,2
 motherboard is compatible with the MacBook2,1. Simply flash a MacBook2,1
 ROM image, and it should work.**
 
@@ -285,7 +285,7 @@ correct ROM image, then run this alternative command:\
 
 
 
-You should see **\"Verifying flash\... VERIFIED.\"** written at the end
+You should see **"Verifying flash\... VERIFIED."** written at the end
 of the flashrom output. **Shut down** after you see this, and then boot
 up again after a few seconds.
 
@@ -315,7 +315,7 @@ and will not work on any other. For that, please refer to
 <http://www.coreboot.org/Board:lenovo/x60/Installation>.**
 
 
-**If you\'re using libreboot 20150518, note that there is a mistake in
+**If you're using libreboot 20150518, note that there is a mistake in
 the flashing script. do this: *rm -f patch && wget -O flash
 https://notabug.org/vimuser/libreboot/raw/9d850543ad90b72e0e333c98075530b31e5d23f1/flash
 && chmod +x flash***
@@ -326,14 +326,14 @@ The first half of the procedure is as follows:\
 
 
 You should see within the output the following:\
-**\"Updated BUC.TS=1 - 64kb address ranges at 0xFFFE0000 and 0xFFFF0000
-are swapped\"**.
+**"Updated BUC.TS=1 - 64kb address ranges at 0xFFFE0000 and 0xFFFF0000
+are swapped"**.
 
 You should also see within the output the following:\
-**\"Your flash chip is in an unknown state\"**, **\"FAILED\"** and
-**\"DO NOT REBOOT OR POWEROFF\"**\
+**"Your flash chip is in an unknown state"**, **"FAILED"** and
+**"DO NOT REBOOT OR POWEROFF"**\
 Seeing this means that the operation was a **resounding** success!
-**DON\'T PANIC**.
+**DON'T PANIC**.
 
 See this link for more details:
 <http://thread.gmane.org/gmane.linux.bios.flashrom/575>.
@@ -354,11 +354,11 @@ internal:laptop=force\_I\_want\_a\_brick -w [yourrom.rom](#rom)**
 
 
 You should see within the output the following:\
-**\"Updated BUC.TS=0 - 128kb address range 0xFFFE0000-0xFFFFFFFF is
-untranslated\"**
+**"Updated BUC.TS=0 - 128kb address range 0xFFFE0000-0xFFFFFFFF is
+untranslated"**
 
 You should also see within the output the following:\
-**\"Verifying flash\... VERIFIED.\"**
+**"Verifying flash\... VERIFIED."**
 
 
 [Back to top of page.](#pagetop)
@@ -399,7 +399,7 @@ Use this flashing script, to install libreboot:\
 
 
 You should also see within the output the following:\
-**\"Verifying flash\... VERIFIED.\"**
+**"Verifying flash\... VERIFIED."**
 
 Shut down.
 
diff --git a/docs/install/kgpe-d16.md b/docs/install/kgpe-d16.md
index 5cae7d45..522c013e 100644
--- a/docs/install/kgpe-d16.md
+++ b/docs/install/kgpe-d16.md
@@ -27,7 +27,7 @@ TODO: show photos here, and other info.
 KGPE-D16 boards (and full systems) with libreboot preinstalled {#preinstall}
 ==============================================================
 
-If you don\'t want to install libreboot yourself, companies exist that
+If you don't want to install libreboot yourself, companies exist that
 sell these boards with libreboot pre-installed, along with a free
 GNU+Linux distribution.
 
diff --git a/docs/install/r400_external.md b/docs/install/r400_external.md
index 498733e8..0ee3488f 100644
--- a/docs/install/r400_external.md
+++ b/docs/install/r400_external.md
@@ -53,7 +53,7 @@ A note about GPUs
 =================
 
 Some models have an Intel GPU, while others have both an ATI and an
-Intel GPU; this is referred to as \"switchable graphics\". In the *BIOS
+Intel GPU; this is referred to as "switchable graphics". In the *BIOS
 setup* program for lenovobios, you can specify that the system will use
 one or the other (but not both).
 
@@ -144,7 +144,7 @@ Remove the palm rest and keyboard:\
 Remove these screws, and then remove the bezel:\
 ![](images/r400/0006.jpg) ![](images/r400/0007.jpg)
 
-Remove the speaker screws, but don\'t remove the speakers yet (just set
+Remove the speaker screws, but don't remove the speakers yet (just set
 them loose):\
 ![](images/r400/0008.jpg) ![](images/r400/0009.jpg)
 ![](images/r400/0010.jpg)
@@ -251,7 +251,7 @@ factory.rom**\
 factory1.rom**\
 \# **./flashrom -p linux\_spi:dev=/dev/spidev1.0,spispeed=512 -r
 factory2.rom**\
-Note: the **-c** option is not required in libreboot\'s patched
+Note: the **-c** option is not required in libreboot's patched
 flashrom, because the redundant flash chip definitions in *flashchips.c*
 have been removed.\
 Now compare the 3 images:\
@@ -276,7 +276,7 @@ path/to/libreboot/rom/image.rom -V**
 ![](images/x200/disassembly/0015.jpg)
 
 You might see errors, but if it says **Verifying flash\... VERIFIED** at
-the end, then it\'s flashed and should boot. If you see errors, try
+the end, then it's flashed and should boot. If you see errors, try
 again (and again, and again); the message **Chip content is identical to
 the requested image** is also an indication of a successful
 installation.
@@ -331,7 +331,7 @@ Some R400 laptops might come with an Atheros chipset, but this is
 It is recommended that you install a new wifi chipset. This can only be
 done after installing libreboot, because the original firmware has a
 whitelist of approved chips, and it will refuse to boot if you use an
-\'unauthorized\' wifi card.
+'unauthorized' wifi card.
 
 The following photos show an Atheros AR5B95 being installed, to replace
 the Intel chip that this R400 came with:\
@@ -355,7 +355,7 @@ Memory
 ======
 
 You need DDR3 SODIMM PC3-8500 RAM installed, in matching pairs
-(speed/size). Non-matching pairs won\'t work. You can also install a
+(speed/size). Non-matching pairs won't work. You can also install a
 single module (meaning, one of the slots will be empty) in slot 0.
 
 Make sure that the RAM you buy is the 2Rx8 density.
diff --git a/docs/install/rpi_setup.md b/docs/install/rpi_setup.md
index c4008933..c130327e 100644
--- a/docs/install/rpi_setup.md
+++ b/docs/install/rpi_setup.md
@@ -69,7 +69,7 @@ B+ with 40 pins, start counting from the right and leave 14 pins):
   8        3.3V           *red*        White         [3.3V PSU RED](http://libreboot.org/docs/install/bbb_setup.html)      17
 
 Make sure the pinouts are correct; otherwise, Flashrom will fail to
-detect a chip, or it will \"detect\" a `0x0` chip. Finally, make sure
+detect a chip, or it will "detect" a `0x0` chip. Finally, make sure
 that the Pomona clip makes contact with the metal wires of the chip. It
 can be a challenge, but keep trying.
 
@@ -148,7 +148,7 @@ successfully. If not, just flash again.
 -   [Scruss - Simple ADC with the Raspberry
     Pi](http://scruss.com/blog/2013/02/02/simple-adc-with-the-raspberry-pi/)
 -   [Flashing coreboot on a T60 with a Raspberry Pi -
-    the\_unconventional\'s
+    the\_unconventional's
     blog](https://blogs.fsfe.org/the_unconventional/2015/05/08/flashing-coreboot-on-a-t60-with-a-raspberry-pi/)
 -   **Pomona SOIC Clip flashing**
     -   [Arch Linux Wiki - Installing Arch Linux on
@@ -201,7 +201,7 @@ Download NOOBS from [The Raspberry Pi
 Foundation.](https://www.raspberrypi.org/downloads/) Torrent download
 recommended, and remember to seed. :)
 
-If you\'re running Raspian, you can do **sudo raspi-config**, enable SPI
+If you're running Raspian, you can do **sudo raspi-config**, enable SPI
 under Advanced and then spidev will be enabled. Simple, eh?
 
 [Download Libreboot from their releases
@@ -227,7 +227,7 @@ Install Noobs to your fat32 formatted SD card
 ### [](#set-up-noobs-on-raspberry-pi){#user-content-set-up-noobs-on-raspberry-pi .anchor}Set up NOOBS on Raspberry Pi
 
 Plug in the NOOBs SDCard to your Raspberry Pi, and enable the following
-under \'Advanced Options\':
+under 'Advanced Options':
 
 SSH server
 
@@ -318,9 +318,9 @@ At this point connect your SOIC clip to the rom chip before powering on
 your PI.
 
 Power on your Pi, and run the following. Ensure you swap out
-\"your\_chip\_name\" with the proper name/model of your chip. Check that
+"your\_chip\_name" with the proper name/model of your chip. Check that
 it can be read successfully. If you cannot read the chip and receive an
-error similar to \"no EEPROM Detected\" or \"0x0 Chip detected\" then
+error similar to "no EEPROM Detected" or "0x0 Chip detected" then
 you may want to try powering off your PI, and switching the two pins
 which are connected to the IO ports. I.E. Connect pins (clip)8 to (pi)19
 and pins (clip)15 to (pi)21
@@ -336,13 +336,13 @@ and pins (clip)15 to (pi)21
     pi# sha512sum romread*.rom
 
 If they are identical sha512 hashes then you can generally assume that
-it\'s safe to flash your rom.
+it's safe to flash your rom.
 
     pi# ./flashrom -p linux_spi:dev=/dev/spidev0.0,spispeed=512 --chip <your_chip_name> -w libreboot.rom
 
 It may fail a couple times, but keep at it and when you get the message
 `Verifying flash... Verified` or
-`Warning: Chip content is identical to the requested image` then you\'re
+`Warning: Chip content is identical to the requested image` then you're
 done.
 
 Shut down your pi, put your box back together, and install a libre OS
@@ -367,7 +367,7 @@ GPIO Pinouts:
 
 ![](images/rpi/0009.png) ![](images/rpi/0010.png)
 
-> \*Diagram made by [\"Pacman\" from Win-Raid
+> \*Diagram made by ["Pacman" from Win-Raid
 > Forums\*](http://www.win-raid.com/t58f16-Guide-Recover-from-failed-BIOS-flash-using-Raspberry-PI.html)
 
 SOIC Pinouts:
@@ -382,7 +382,7 @@ clip).
 
 ![SOIC Pinouts for C720 Chromebook](images/rpi/0003.png)
 
-(C720 Only?) The diagram depicts a \"bridged\" connection. You will need
+(C720 Only?) The diagram depicts a "bridged" connection. You will need
 to fashion one with some copper wire:
 
 ![Bridged wires](images/rpi/0004.jpg)
@@ -395,7 +395,7 @@ Plug in the other end of the wires to the Raspberry Pi as shown below:
 
 ![Raspberry Pi connections](images/rpi/0006.jpg)
 
-(C720 only?) Plug in the \"bridged\" wires as shown below:
+(C720 only?) Plug in the "bridged" wires as shown below:
 
 ![Bridged wires connected](images/rpi/0007.jpg)
 
@@ -405,7 +405,7 @@ Finally, put the Pomona SOIC clip on the chip:
 
 ### [](#flashrom){#user-content-flashrom .anchor}Flashrom
 
-[Once it\'s all set up, flashrom works out of the
+[Once it's all set up, flashrom works out of the
 box.](http://www.flashrom.org/RaspberryPi)
 
 ### [](#sources-1){#user-content-sources-1 .anchor}Sources
diff --git a/docs/install/t400_external.md b/docs/install/t400_external.md
index 74765d62..bcba837c 100644
--- a/docs/install/t400_external.md
+++ b/docs/install/t400_external.md
@@ -9,10 +9,10 @@ they still have the original Lenovo BIOS present. This guide can also be
 followed (adapted) if you brick your T400, to know how to recover.
 
 An
-[\"HMM\"](https://download.lenovo.com/ibmdl/pub/pc/pccbbs/mobiles_pdf/43y6629_05.pdf#page=386)
+["HMM"](https://download.lenovo.com/ibmdl/pub/pc/pccbbs/mobiles_pdf/43y6629_05.pdf#page=386)
 (Hardware Maintenance Manual) detailing the process of \[dis\]assembly
 is available for this model. Be careful when reassembling the laptop as
-the screws on page 144 (with title \"1130 Keyboard bezel\") are swapped
+the screws on page 144 (with title "1130 Keyboard bezel") are swapped
 and if you follow the HMM you will punch a hole through the bezel in the
 upper right corner.
 
@@ -22,7 +22,7 @@ upper right corner.
 T400 laptops with libreboot pre-installed {#preinstall}
 =========================================
 
-If you don\'t want to install libreboot yourself, companies exist that
+If you don't want to install libreboot yourself, companies exist that
 sell these laptops with libreboot pre-installed, along with a free
 GNU+Linux distribution.
 
@@ -58,7 +58,7 @@ A note about GPUs
 =================
 
 Some models have an Intel GPU, while others have both an ATI and an
-Intel GPU; this is referred to as \"switchable graphics\". In the *BIOS
+Intel GPU; this is referred to as "switchable graphics". In the *BIOS
 setup* program for lenovobios, you can specify that the system will use
 one or the other (but not both).
 
@@ -257,7 +257,7 @@ factory.rom**\
 factory1.rom**\
 \# **./flashrom -p linux\_spi:dev=/dev/spidev1.0,spispeed=512 -r
 factory2.rom**\
-Note: the **-c** option is not required in libreboot\'s patched
+Note: the **-c** option is not required in libreboot's patched
 flashrom, because the redundant flash chip definitions in *flashchips.c*
 have been removed.\
 Now compare the 3 images:\
@@ -282,7 +282,7 @@ path/to/libreboot/rom/image.rom -V**
 ![](images/x200/disassembly/0015.jpg)
 
 You might see errors, but if it says **Verifying flash\... VERIFIED** at
-the end, then it\'s flashed and should boot. If you see errors, try
+the end, then it's flashed and should boot. If you see errors, try
 again (and again, and again); the message **Chip content is identical to
 the requested image** is also an indication of a successful
 installation.
@@ -337,7 +337,7 @@ Some T400 laptops might come with an Atheros chipset, but this is
 It is recommended that you install a new wifi chipset. This can only be
 done after installing libreboot, because the original firmware has a
 whitelist of approved chips, and it will refuse to boot if you use an
-\'unauthorized\' wifi card.
+'unauthorized' wifi card.
 
 The following photos show an Atheros AR5B95 being installed, to replace
 the Intel chip that this T400 came with:\
@@ -361,7 +361,7 @@ Memory
 ======
 
 You need DDR3 SODIMM PC3-8500 RAM installed, in matching pairs
-(speed/size). Non-matching pairs won\'t work. You can also install a
+(speed/size). Non-matching pairs won't work. You can also install a
 single module (meaning, one of the slots will be empty) in slot 0.
 
 Make sure that the RAM you buy is the 2Rx8 density.
diff --git a/docs/install/t500_external.md b/docs/install/t500_external.md
index 4bd9bb44..ba272d03 100644
--- a/docs/install/t500_external.md
+++ b/docs/install/t500_external.md
@@ -48,7 +48,7 @@ A note about GPUs
 =================
 
 Some models have an Intel GPU, while others have both an ATI and an
-Intel GPU; this is referred to as \"switchable graphics\". In the *BIOS
+Intel GPU; this is referred to as "switchable graphics". In the *BIOS
 setup* program for lenovobios, you can specify that the system will use
 one or the other (but not both).
 
@@ -166,7 +166,7 @@ Remove the NVRAM battery (already removed in this photo):\
 ![](images/t500/0026.jpg)
 
 When you re-assemble, you will be replacing the wifi chip with another.
-These two screws don\'t hold anything together, but they are included in
+These two screws don't hold anything together, but they are included in
 your system because the screw holes for half-height cards are a
 different size, so use these if you will be installing a half-height
 card:\
@@ -262,7 +262,7 @@ factory.rom**\
 factory1.rom**\
 \# **./flashrom -p linux\_spi:dev=/dev/spidev1.0,spispeed=512 -r
 factory2.rom**\
-Note: the **-c** option is not required in libreboot\'s patched
+Note: the **-c** option is not required in libreboot's patched
 flashrom, because the redundant flash chip definitions in *flashchips.c*
 have been removed.\
 Now compare the 3 images:\
@@ -287,7 +287,7 @@ path/to/libreboot/rom/image.rom -V**
 ![](images/x200/disassembly/0015.jpg)
 
 You might see errors, but if it says **Verifying flash\... VERIFIED** at
-the end, then it\'s flashed and should boot. If you see errors, try
+the end, then it's flashed and should boot. If you see errors, try
 again (and again, and again); the message **Chip content is identical to
 the requested image** is also an indication of a successful
 installation.
@@ -342,7 +342,7 @@ Some T500 laptops might come with an Atheros chipset, but this is
 It is recommended that you install a new wifi chipset. This can only be
 done after installing libreboot, because the original firmware has a
 whitelist of approved chips, and it will refuse to boot if you use an
-\'unauthorized\' wifi card.
+'unauthorized' wifi card.
 
 The following photos show an Atheros AR5B95 being installed, to replace
 the Intel chip that this T500 came with:\
@@ -366,7 +366,7 @@ Memory
 ======
 
 You need DDR3 SODIMM PC3-8500 RAM installed, in matching pairs
-(speed/size). Non-matching pairs won\'t work. You can also install a
+(speed/size). Non-matching pairs won't work. You can also install a
 single module (meaning, one of the slots will be empty) in slot 0.
 
 Make sure that the RAM you buy is the 2Rx8 density.
diff --git a/docs/install/t60_unbrick.md b/docs/install/t60_unbrick.md
index aab55241..7a0d4e7f 100644
--- a/docs/install/t60_unbrick.md
+++ b/docs/install/t60_unbrick.md
@@ -14,7 +14,7 @@ Table of Contents
 
 -   Types of brick:
     -   [Brick type 1: bucts not reset](#bucts_brick)
-    -   [Brick type 2: bad rom (or user error), system won\'t
+    -   [Brick type 2: bad rom (or user error), system won't
         boot](#recovery)
 
 
@@ -23,11 +23,11 @@ Brick type 1: bucts not reset. {#bucts_brick}
 ==============================
 
 You still have Lenovo BIOS, or you had libreboot running and you flashed
-another ROM; and you had bucts 1 set and the ROM wasn\'t dd\'d.\* or if
-Lenovo BIOS was present and libreboot wasn\'t flashed.\
+another ROM; and you had bucts 1 set and the ROM wasn't dd'd.\* or if
+Lenovo BIOS was present and libreboot wasn't flashed.\
 \
 In this case, unbricking is easy: reset BUC.TS to 0 by removing that
-yellow cmos coin (it\'s a battery) and putting it back after a minute or
+yellow cmos coin (it's a battery) and putting it back after a minute or
 two:\
 ![](../images/t60_dev/0006.JPG)\
 \
@@ -47,7 +47,7 @@ but instructions for t60 are identical)
 
 
 
-bad rom (or user error), system won\'t boot {#recovery}
+bad rom (or user error), system won't boot {#recovery}
 ===========================================
 
 In this scenario, you compiled a ROM that had an incorrect
@@ -56,8 +56,8 @@ booting. Or, maybe, you set BUC.TS to 0 and shut down after first flash
 while Lenovo BIOS was running. In any case, your system is bricked and
 will not boot at all.
 
-\"Unbricking\" means flashing a known-good (working) ROM. The problem:
-you can\'t boot the system, making this difficult. In this situation,
+"Unbricking" means flashing a known-good (working) ROM. The problem:
+you can't boot the system, making this difficult. In this situation,
 external hardware (see hardware requirements above) is needed which can
 flash the SPI chip (where libreboot resides).
 
@@ -132,11 +132,11 @@ system:\
 Now wire up the BBB and the Pomona with your PSU.\
 Refer to [bbb\_setup.html](bbb_setup.html) for how to setup the BBB for
 flashing.\
-**Note, the guide mentions a 3.3v DC PSU but you don\'t need this on the
-T60: if you don\'t have or don\'t want to use an external PSU, then make
+**Note, the guide mentions a 3.3v DC PSU but you don't need this on the
+T60: if you don't have or don't want to use an external PSU, then make
 sure not to connect the 3.3v leads mentioned in the guide; instead,
 connect the AC adapter (the one that normally charges your battery) so
-that the board has power (but don\'t boot it up)**\
+that the board has power (but don't boot it up)**\
 ![](../images/t60_dev/0030.JPG)\
 Correlate the following with the BBB guide linked above:
 
@@ -156,7 +156,7 @@ Flashrom binaries for ARM (tested on a BBB) are distributed in
 libreboot\_util. Alternatively, libreboot also distributes flashrom
 source code which can be built.
 
-SSH\'d into the BBB:\
+SSH'd into the BBB:\
 \# **./flashrom -p linux\_spi:dev=/dev/spidev1.0,spispeed=512 -w
 yourrom.rom**
 
@@ -207,7 +207,7 @@ It lives!\
 ![](../images/t60_dev/0071.JPG) ![](../images/t60_dev/0072.JPG)
 ![](../images/t60_dev/0073.JPG)
 
-Always stress test (\'stress -c 2\' and xsensors. below 90C is ok) when
+Always stress test ('stress -c 2' and xsensors. below 90C is ok) when
 replacing cpu paste/heatsink:\
 ![](../images/t60_dev/0074.JPG)
 
diff --git a/docs/install/x200_external.md b/docs/install/x200_external.md
index 1a76f839..81f7b3ea 100644
--- a/docs/install/x200_external.md
+++ b/docs/install/x200_external.md
@@ -24,7 +24,7 @@ followed (adapted) if you brick your X200, to know how to recover.
 X200 laptops with libreboot pre-installed {#preinstall}
 =========================================
 
-If you don\'t want to install libreboot yourself, companies exist that
+If you don't want to install libreboot yourself, companies exist that
 sell these laptops with libreboot pre-installed, along with a free
 GNU+Linux distribution.
 
@@ -191,7 +191,7 @@ factory.rom**\
 factory1.rom**\
 \# **./flashrom -p linux\_spi:dev=/dev/spidev1.0,spispeed=512 -r
 factory2.rom**\
-Note: the **-c** option is not required in libreboot\'s patched
+Note: the **-c** option is not required in libreboot's patched
 flashrom, because the redundant flash chip definitions in *flashchips.c*
 have been removed.\
 Now compare the 3 images:\
@@ -216,7 +216,7 @@ path/to/libreboot/rom/image.rom -V**
 ![](images/x200/disassembly/0015.jpg)
 
 You might see errors, but if it says **Verifying flash\... VERIFIED** at
-the end, then it\'s flashed and should boot. If you see errors, try
+the end, then it's flashed and should boot. If you see errors, try
 again (and again, and again); the message **Chip content is identical to
 the requested image** is also an indication of a successful
 installation.
@@ -252,7 +252,7 @@ only.
 It is recommended that you install a new wifi chipset. This can only be
 done after installing libreboot, because the original firmware has a
 whitelist of approved chips, and it will refuse to boot if you use an
-\'unauthorized\' wifi card.
+'unauthorized' wifi card.
 
 The following photos show an Atheros AR5B95 being installed, to replace
 the Intel chip that this X200 came with:\
@@ -277,7 +277,7 @@ Memory
 ======
 
 You need DDR3 SODIMM PC3-8500 RAM installed, in matching pairs
-(speed/size). Non-matching pairs won\'t work. You can also install a
+(speed/size). Non-matching pairs won't work. You can also install a
 single module (meaning, one of the slots will be empty) in slot 0.
 
 NOTE: according to users repors, non matching pairs (e.g. 1+2 GiB) might
@@ -309,7 +309,7 @@ disable the flashing protections by the descriptor and stop the ME from
 starting (which itself interferes with flashing attempts). The theory
 was proven correct; however, it is still useless in practise.
 
-Look just above the 7 in TP37 (that\'s GPIO33):\
+Look just above the 7 in TP37 (that's GPIO33):\
 ![](../hcl/images/x200/gpio33_location.jpg)
 
 By default we would see this in lenovobios, when trying flashrom -p
@@ -334,7 +334,7 @@ The part in bold is what got us. This was still observed:
 It is actually possible to disable these protections. Lenovobios does,
 when updating the BIOS (proprietary one). One possible way to go about
 this would be to debug the BIOS update utility from Lenovo, to find out
-how it\'s disabling these protections. Some more research is available
+how it's disabling these protections. Some more research is available
 here:
 <http://www.coreboot.org/Board:lenovo/x200/internal_flashing_research>
 
diff --git a/docs/install/x60_unbrick.md b/docs/install/x60_unbrick.md
index 123dce40..810cad60 100644
--- a/docs/install/x60_unbrick.md
+++ b/docs/install/x60_unbrick.md
@@ -14,7 +14,7 @@ Table of Contents
 
 -   Types of brick:
     -   [Brick type 1: bucts not reset](#bucts_brick)
-    -   [Brick type 2: bad rom (or user error), system won\'t
+    -   [Brick type 2: bad rom (or user error), system won't
         boot](#recovery)
 
 
@@ -23,11 +23,11 @@ Brick type 1: bucts not reset. {#bucts_brick}
 ==============================
 
 You still have Lenovo BIOS, or you had libreboot running and you flashed
-another ROM; and you had bucts 1 set and the ROM wasn\'t dd\'d.\* or if
-Lenovo BIOS was present and libreboot wasn\'t flashed.\
+another ROM; and you had bucts 1 set and the ROM wasn't dd'd.\* or if
+Lenovo BIOS was present and libreboot wasn't flashed.\
 \
 In this case, unbricking is easy: reset BUC.TS to 0 by removing that
-yellow cmos coin (it\'s a battery) and putting it back after a minute or
+yellow cmos coin (it's a battery) and putting it back after a minute or
 two:\
 ![](../images/x60_unbrick/0004.jpg)\
 \
@@ -46,7 +46,7 @@ still has Lenovo BIOS running, using those instructions:
 
 
 
-bad rom (or user error), system won\'t boot {#recovery}
+bad rom (or user error), system won't boot {#recovery}
 ===========================================
 
 In this scenario, you compiled a ROM that had an incorrect
@@ -55,8 +55,8 @@ booting. Or, maybe, you set BUC.TS to 0 and shut down after first flash
 while Lenovo BIOS was running. In any case, your system is bricked and
 will not boot at all.
 
-\"Unbricking\" means flashing a known-good (working) ROM. The problem:
-you can\'t boot the system, making this difficult. In this situation,
+"Unbricking" means flashing a known-good (working) ROM. The problem:
+you can't boot the system, making this difficult. In this situation,
 external hardware (see hardware requirements above) is needed which can
 flash the SPI chip (where libreboot resides).
 
@@ -116,11 +116,11 @@ flash chip:\
 Now wire up the BBB and the Pomona with your PSU.\
 Refer to [bbb\_setup.html](bbb_setup.html) for how to setup the BBB for
 flashing.\
-**Note, the guide mentions a 3.3v DC PSU but you don\'t need this on the
-X60: if you don\'t have or don\'t want to use an external PSU, then make
+**Note, the guide mentions a 3.3v DC PSU but you don't need this on the
+X60: if you don't have or don't want to use an external PSU, then make
 sure not to connect the 3.3v leads mentioned in the guide; instead,
 connect the AC adapter (the one that normally charges your battery) so
-that the board has power (but don\'t boot it up)**
+that the board has power (but don't boot it up)**
 ![](../images/x60_unbrick/0017.jpg)\
 Correlate the following with the BBB guide linked above:
 
@@ -141,7 +141,7 @@ Flashrom binaries for ARM (tested on a BBB) are distributed in
 libreboot\_util. Alternatively, libreboot also distributes flashrom
 source code which can be built.
 
-SSH\'d into the BBB:\
+SSH'd into the BBB:\
 \# **./flashrom -p linux\_spi:dev=/dev/spidev1.0,spispeed=512 -w
 yourrom.rom**
 
@@ -195,7 +195,7 @@ Route the antenna and modem cables neatly like so:\
 ![](../images/x60_unbrick/0039.jpg)
 
 Connect the wifi antenna cables. At the start of the tutorial, this
-system had an Intel wifi chip. Here you see I\'ve replaced it with an
+system had an Intel wifi chip. Here you see I've replaced it with an
 Atheros AR5B95 (supports 802.11n and can be used without blobs):\
 ![](../images/x60_unbrick/0040.jpg)
 
diff --git a/docs/install/x60tablet_unbrick.md b/docs/install/x60tablet_unbrick.md
index 8481cac9..064cbbca 100644
--- a/docs/install/x60tablet_unbrick.md
+++ b/docs/install/x60tablet_unbrick.md
@@ -14,7 +14,7 @@ Table of Contents
 
 -   Types of brick:
     -   [Brick type 1: bucts not reset](#bucts_brick)
-    -   [Brick type 2: bad rom (or user error), system won\'t
+    -   [Brick type 2: bad rom (or user error), system won't
         boot](#recovery)
 
 
@@ -23,11 +23,11 @@ Brick type 1: bucts not reset. {#bucts_brick}
 ==============================
 
 You still have Lenovo BIOS, or you had libreboot running and you flashed
-another ROM; and you had bucts 1 set and the ROM wasn\'t dd\'d.\* or if
-Lenovo BIOS was present and libreboot wasn\'t flashed.\
+another ROM; and you had bucts 1 set and the ROM wasn't dd'd.\* or if
+Lenovo BIOS was present and libreboot wasn't flashed.\
 \
 In this case, unbricking is easy: reset BUC.TS to 0 by removing that
-yellow cmos coin (it\'s a battery) and putting it back after a minute or
+yellow cmos coin (it's a battery) and putting it back after a minute or
 two:\
 ![](../images/x60t_unbrick/0008.JPG)\
 \
@@ -46,7 +46,7 @@ still has Lenovo BIOS running, using those instructions:
 
 
 
-bad rom (or user error), system won\'t boot {#recovery}
+bad rom (or user error), system won't boot {#recovery}
 ===========================================
 
 In this scenario, you compiled a ROM that had an incorrect
@@ -55,8 +55,8 @@ booting. Or, maybe, you set BUC.TS to 0 and shut down after first flash
 while Lenovo BIOS was running. In any case, your system is bricked and
 will not boot at all.
 
-\"Unbricking\" means flashing a known-good (working) ROM. The problem:
-you can\'t boot the system, making this difficult. In this situation,
+"Unbricking" means flashing a known-good (working) ROM. The problem:
+you can't boot the system, making this difficult. In this situation,
 external hardware (see hardware requirements above) is needed which can
 flash the SPI chip (where libreboot resides).
 
@@ -95,11 +95,11 @@ Remove that screw and then remove the board:\
 Now wire up the BBB and the Pomona with your PSU.\
 Refer to [bbb\_setup.html](bbb_setup.html) for how to setup the BBB for
 flashing.\
-**Note, the guide mentions a 3.3v DC PSU but you don\'t need this on the
-X60 Tablet: if you don\'t have or don\'t want to use an external PSU,
+**Note, the guide mentions a 3.3v DC PSU but you don't need this on the
+X60 Tablet: if you don't have or don't want to use an external PSU,
 then make sure not to connect the 3.3v leads mentioned in the guide;
 instead, connect the AC adapter (the one that normally charges your
-battery) so that the board has power (but don\'t boot it up)**
+battery) so that the board has power (but don't boot it up)**
 ![](../images/x60t_unbrick/0011.JPG)\
 Correlate the following with the BBB guide linked above:
 
@@ -120,7 +120,7 @@ Flashrom binaries for ARM (tested on a BBB) are distributed in
 libreboot\_util. Alternatively, libreboot also distributes flashrom
 source code which can be built.
 
-SSH\'d into the BBB:\
+SSH'd into the BBB:\
 \# **./flashrom -p linux\_spi:dev=/dev/spidev1.0,spispeed=512 -w
 yourrom.rom**