tidy up the other.md page

Signed-off-by: Leah Rowe <leah@libreboot.org>

site/other.md

@@ -34,7 +34,6 @@ be listed. Quality over quantity.
 Canoeboot tries to support as much hardware as possible, and focuses on providing
 the easiest possible experience for non-technical users; it's also
 highly [configurable](docs/maintain/) for power users.
-
 Several other projects exist that target different kinds of users, and support
 different types of hardware; for example, Canoeboot mostly doesn't target
 Chromebooks, except for a few.
@@ -76,9 +75,6 @@ With Chultrabook's guidance, you can have a completely up to date UEFI firmware
 on your machine, and get good use out of your Chromebook for many more years,
 with regular security updates.
 
-Libreboot largely avoids supporting Chromebooks, precisely because Chultrabook
-and MrChromebox are perfectly viable options on these machines.
-
 Dasharo
 -------
 
@@ -97,8 +93,6 @@ the Dasharo project, and later upstreamed into the regular coreboot project.
 
 Dasharo has a special emphasis on commercial application, providing tailored
 coreboot images for each supported mainboard, with an emphasis on stability.
-It's a very different approach than Libreboot's approach; Libreboot provides
-a more generalised design in its build system and infrastructure.
 
 Heads
 -----
@@ -118,12 +112,6 @@ Linux distros easily.
 If you're the sort of person who needs full disk encryption and you have a
 focus on security, Heads is for you. Perfect for use with something like Qubes.
 
-Libreboot provides its own [security mechanisms](docs/linux/grub_hardening.html),
-but Heads is much more flexible and complete, in this regard. The only downside
-to Heads's Linux-based flash setup, is that it's basically a Linux-only
-coreboot distro (whereas Libreboot can boot BSD and even *Windows*, in some
-cases).
-
 Another focus of the heads project is on *reproducible builds*. Its build
 system bootstraps a toolchain that then compiles everything else, including
 the coreboot crossgcc toolchain. The purpose of this is to provide matching
@@ -131,17 +119,6 @@ ROM hashes on every build; for this purpose, it also auto-downloads vendor
 files such as Intel ME at build time, instead of requiring you to dump from
 the original boot firmware.
 
-Heads's vendorcode auto-download logic inspired Libreboot's
-own [vendorcode inject](docs/install/ivy_has_common.md) design; Libreboot
-greatly expanded on it, on more machines.
-
-We in Libreboot have an affinity for the Heads project, and have worked with
-them in the past, and they with us, helping each other back and forth. Many of
-the machines supported in Libreboot are also supported in Heads, and vice versa,
-but they target different kinds of users and use-case scenarios, with Libreboot
-targeting a more general audience (while providing security hardening options),
-whereas Heads specifically targets security-conscious users.
-
 Libreboot
 ---------
 
@@ -201,9 +178,6 @@ With MrChromebox's guidance, you can have a completely up to date UEFI firmware
 on your machine, and get good use out of your Chromebook for many more years,
 with regular security updates.
 
-Libreboot largely avoids supporting Chromebooks, precisely because Chultrabook
-and MrChromebox are perfectly viable options on these machines.
-
 Skulls
 ------
 
@@ -216,12 +190,6 @@ additional steps for installation.
 
 If you just want the simplest, most barebones setup, Skulls is a great choice.
 
-The reason Skulls is simpler is that they include certain vendor files such
-as `me.bin` pre-inserted into images; while risky indeed, this does in fact
-make installation easier for users. Libreboot takes a more conservative
-approach, excluding such files on release images and instead providing you with
-an [automated script](docs/install/ivy_has_common.md) to insert these.
-
 Libreboot *also* provides U-Boot and GRUB, and has other ambitions. Libreboot
 aims to provide ease of use while also providing great power and flexibility.
 So Libreboot is aimed specifically at power users, while also trying to