9 files changed, 26 insertions, 29 deletions
diff --git a/docs/gnulinux/configuring_parabola.md b/docs/gnulinux/configuring_parabola.md
index 1e525f59..935ff099 100644
--- a/docs/gnulinux/configuring_parabola.md
+++ b/docs/gnulinux/configuring_parabola.md
@@ -63,7 +63,7 @@ For more information related to `pacman`, review the following articles on the A
 
 *    [Configuring pacman](https://wiki.parabolagnulinux.org/Installation_Guide#Configure_pacman)
 *    [Using pacman](https://wiki.archlinux.org/index.php/Pacman)
-*    [Additional Repositories](https://wiki.parabolagnulinux.org/Official_Repositories>)
+*    [Additional Repositories](https://wiki.parabolagnulinux.org/Official_Repositories)
 
 ## Updating Parabola
 Parabola is kept up-to-date, using `pacman`. When you are updating Parabola,
diff --git a/docs/gnulinux/encrypted_parabola.md b/docs/gnulinux/encrypted_parabola.md
index 74c74fce..5ff070a6 100644
--- a/docs/gnulinux/encrypted_parabola.md
+++ b/docs/gnulinux/encrypted_parabola.md
@@ -102,7 +102,7 @@ You can either fill the header with zeroes, or with random data; again, I chose
 Also, if you're using an SSD, there are a two things you should keep in mind:
 
 -    There are issues with TRIM; it's not enabled by default through LUKS,
-and there are security issues, if you do enable it. See [this page](https://wiki.archlinux.org/index.php/Dm-cryptSpecialties#Discard.2FTRIM_support_for_solid_state_drives_.28SSD.29) for more info.
+and there are security issues, if you do enable it. See [this page](https://wiki.archlinux.org/index.php/Dm-crypt#Specialties) for more info.
 -    Make sure to read [this article](https://wiki.archlinux.org/index.php/Solid_State_Drives),
 for information on managing SSD's in Arch Linux (the information applies to Parabola, as well).
 
@@ -381,7 +381,7 @@ for the LUKS passphrase, apply here as well. You will set this password with the
 
 ### Extra Security Tweaks
 There are some final changes that we can make to the installation, to make it
-significantly more secure; these are based on the [Security](https://wiki.archlinux.org/index.php/Securit) section of the Arch wiki.
+significantly more secure; these are based on the [Security](https://wiki.archlinux.org/index.php/Security) section of the Arch wiki.
 
 #### Key Strengthening
 We will want to open the configuration file for password settings, and increase
@@ -422,7 +422,7 @@ Edit configuration in `/etc/default/grub`, remembering to use UUID when poitning
 Use `blkid` to get list of devices with their respective UUIDs.
 Next generate grub.cfg with
 
-    # grub-mkconfig /boot/grub/grub.cfg
+    # grub-mkconfig -o /boot/grub/grub.cfg
     
 If you have separate `/boot` partition, don't forget to add `boot` symlink inside that points to current directory
 
diff --git a/docs/gnulinux/grub_boot_installer.md b/docs/gnulinux/grub_boot_installer.md
index 7086b71d..7d4375e6 100644
--- a/docs/gnulinux/grub_boot_installer.md
+++ b/docs/gnulinux/grub_boot_installer.md
@@ -25,7 +25,7 @@ Overwrite the drive, writing your distro ISO to it with `dd`. For example, if we
 That's it! You should now be able to boot the installer from your USB drive (the instructions for doing so will be given later).
 
 ## Prepare the USB drive in NetBSD
-[This page](https://wiki.netbsd.org/tutorials how_to_install_netbsd_from_an_usb_memory_stick/) on the NetBSD website shows how to create a NetBSD bootable USB drive, from within NetBSD itself. You should the `dd` method documented there. This will work with any GNU+Linux ISO image.
+[This page](https://wiki.netbsd.org/tutorials/how_to_install_netbsd_from_an_usb_memory_stick/) on the NetBSD website shows how to create a NetBSD bootable USB drive, from within NetBSD itself. You should the `dd` method documented there. This will work with any GNU+Linux ISO image.
 
 ## Prepare the USB drive in FreeBSD
 [This page](https://www.freebsd.org/doc/handbook/bsdinstall-pre.html) on the FreeBSD website shows how to create a bootable USB drive for installing FreeBSD. Use the `dd` method documented. This will work with any GNU+Linux ISO image.
diff --git a/docs/gnulinux/grub_hardening.md b/docs/gnulinux/grub_hardening.md
index 9eb7237e..e1329f21 100644
--- a/docs/gnulinux/grub_hardening.md
+++ b/docs/gnulinux/grub_hardening.md
@@ -33,7 +33,7 @@ Helpful links:
 
 -   [GRUB manual](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.](../../faq.md#firmware-hddssd)
+-   [SATA connected storage considered dangerous.](../../faq.md#hddssd-firmware)
 -   [Coreboot GRUB security howto](https://www.coreboot.org/GRUB2#Security)
 
 GRUB Password
diff --git a/docs/hardware/gm45_remove_me.md b/docs/hardware/gm45_remove_me.md
index 0ac2f49b..26e5f9f6 100644
--- a/docs/hardware/gm45_remove_me.md
+++ b/docs/hardware/gm45_remove_me.md
@@ -418,7 +418,7 @@ region.
 
 According to the datasheet, it's supposed to add up to 0xBABA but can
 actually be others on the X200.
-<https://communities.intel.com/community/wired/blog/2010/10/14/how-to-basic-eeprom-checksums>
+<https://web.archive.org/web/20150912070329/https://communities.intel.com/community/wired/blog/2010/10/14/how-to-basic-eeprom-checksums>
 
 *"One of those engineers loves classic rock music, so they selected
 0xBABA"*
diff --git a/docs/hardware/x200.md b/docs/hardware/x200.md
index 10f5f621..fdf992d1 100644
--- a/docs/hardware/x200.md
+++ b/docs/hardware/x200.md
@@ -132,12 +132,6 @@ comparing it with X200 (factory BIOS) and X200 (gm45 raminit code in
 coreboot), to see what the differences are. Then tweak raminit code
 based on that.
 
-Trouble undocking (button doesn't work)
-----------------------------------------
-
-This person seems to have a workaround:
-<https://github.com/the-unconventional/libreboot-undock>
-
 LCD compatibility list {#lcd_supported_list}
 ----------------------
 
diff --git a/docs/install/index.md b/docs/install/index.md
index d4ac2f13..b54dca15 100644
--- a/docs/install/index.md
+++ b/docs/install/index.md
@@ -62,10 +62,12 @@ 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: `*_*keymap*_*mode*.rom`
 
-Available `modes`: `vesafb` or `txtmode`. The `vesafb` ROM images
-are recommended, in most cases; `txtmode` ROM images come with
-MemTest86+, which requires text-mode instead of the usual framebuffer
-used by coreboot native graphics initialization.
+Available modes: vesafb or txtmode. The vesafb ROM images are recommended
+for regular use, but when flashing for the first time use txtmode version,
+as it comes with Memtest86+, which requires text-mode instead of the usual
+framebuffer used by coreboot native graphics initialization.
+Machine should be tested with Memtest86+ after each reassembly or changing
+from vendor bios to libreboot due to differences in raminit code.
 
 `keymap` can be one of several keymaps that keyboard supports (there are
 quite a few), which affects the keyboard layout configuration that is
@@ -169,7 +171,7 @@ ASUS KCMA-D8?
 -------------
 
 If you have the proprietary BIOS, you need to flash libreboot
-externally. See [kcma-d8.md](kgpe-d8.md).
+externally. See [kcma-d8.md](kcma-d8.md).
 
 If you already have coreboot or libreboot installed, without write
 protection on the flash chip, then you can do it in software (otherwise,
@@ -244,7 +246,7 @@ Flash chip size
 
 Use this to find out:
 
-    # flashrom -p internal -V
+    # flashrom -p internal
 
 All good?
 ---------
@@ -264,13 +266,13 @@ executables from the libreboot source code archives.
 
 How to update the flash chip contents:
 
-`$ sudo ./flash update `[`yourrom.rom`](#rom)
+`$ sudo ./flash update `[`yourrom.rom`](#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:
 
- `$ sudo ./flash forceupdate `[`yourrom.rom`](#rom)
+ `$ sudo ./flash forceupdate `[`yourrom.rom`](#rom)
 
 You should see `Verifying flash... VERIFIED.` written at the end
 of the flashrom output. *Shut down* after you see this, and then boot
@@ -305,7 +307,7 @@ the flashing script. do this: *
 
 The first half of the procedure is as follows:
 
-`$ sudo ./flash i945lenovo_firstflash `[`yourrom.rom`](#rom)
+`$ sudo ./flash i945lenovo_firstflash `[`yourrom.rom`](#rom)
 
 You should see within the output the following:
 
@@ -332,11 +334,11 @@ needed (see below).
 
 When you have booted up again, you must also do this:
 
-`$ sudo ./flash i945lenovo_secondflash `[`yourrom.rom`](#rom)
+`$ sudo ./flash i945lenovo_secondflash `[`yourrom.rom`](#rom)
 
 If flashing fails at this stage, try the following:
 
-`$ sudo ./flashrom/i686/flashrom -p internal:laptop=force_I_want_a_brick -w `[`yourrom.rom`](#rom)
+`$ sudo ./flashrom/i686/flashrom -p internal:laptop=force_I_want_a_brick -w `[`yourrom.rom`](#rom)
 
 You should see within the output the following:
 
@@ -372,7 +374,7 @@ with your device.
 
 Use this flashing script, to install libreboot:
 
-`$ sudo ./flash i945apple_firstflash `[`yourrom.rom`](#rom)
+`$ sudo ./flash i945apple_firstflash `[`yourrom.rom`](#rom)
 
 You should also see within the output the following:
 
diff --git a/docs/install/rpi_setup.md b/docs/install/rpi_setup.md
index e46191e7..b083aac9 100644
--- a/docs/install/rpi_setup.md
+++ b/docs/install/rpi_setup.md
@@ -150,7 +150,7 @@ successfully. If not, just flash again.
     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
-    blog](https://blogs.fsfe.org/the_unconventional/2015/05/08/flashing-coreboot-on-a-t60-with-a-raspberry-pi/)
+    blog](https://web.archive.org/web/20150709043222/http://blogs.fsfe.org:80/the_unconventional/2015/05/08/coreboot-t60-raspberry-pi/)
 -   *Pomona SOIC Clip flashing*
     -   [Arch Linux Wiki - Installing Arch Linux on
         Chromebook](https://wiki.archlinux.org/index.php/Chromebook)
diff --git a/docs/install/t500_external.md b/docs/install/t500_external.md
index c9b85a5d..9e114bca 100644
--- a/docs/install/t500_external.md
+++ b/docs/install/t500_external.md
@@ -362,11 +362,12 @@ Not to be confused with wifi (wifi is fine).
 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
+DDR3 SO-DIMM sticks will work at PC3-8500 clock and voltage, so make sure that
+timings of sticks are matched while they operate at its frequency.
+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.
+Make sure that the RAM you buy has 2Rx8 arrangement when buying 4GiB modules.
 
 [This page](http://www.forum.thinkpads.com/viewtopic.php?p=760721) might
 be useful for RAM compatibility info (note: coreboot raminit is