slightly more diplomatic bridge burning

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

site/about.md

@@ -104,8 +104,8 @@ made to show them precisely how the Libreboot project is run, so as to provide
 them with inspiration.
 
 GNU FSDG policy is [heavily
-misguided](https://libreboot.org/news/policy.html#problems-with-fsdg). Canoeboot
-is vastly inferior to Libreboot, but it can at least be developed to a high
+misguided](https://libreboot.org/news/policy.html#problems-with-fsdg). Libreboot
+is vastly superior to Canoeboot, but it can at least be developed to a high
 standard (within the FSF and GNU dogma); as of 26 October 2023, GNU Boot's build
 system and revisions were still largely based on Libreboot 20220710, with very
 few meaningful changes; Canoeboot was released on that day (26 Oct 2023), based
@@ -138,16 +138,17 @@ It was decided then that Canoeboot would be created, as an official project in
 direct competition with GNU Boot, for fun - the GNU Boot project started in June
 2023, in opposition to Libreboot's change of policy. Canoeboot started, with
 the desire to provide FSDG-compliant releases based on Libreboot, exactly in
-line with GNU Boot policy (adhering to GNU FSDG), while being superior to it.
+line with the GNU Free System Distribution Guidelines, as a proof of concept
+to show what *Libreboot* would otherwise be.
 
 Libreboot is on the forefront, bringing coreboot to ordinary people, and Canoeboot
 follows the same pattern, providing high quality releases in parallel to it.
 
 Canoeboot exists purely *for fun*, to see what is technically possible under GNU
-policy. It is a fun technical challenge, nothing more. Every effort is made to
-ensure perfect compliance with GNU FSDG criteria. Fun fun!
+policy. It is a fun technical challenge. Every effort is made to ensure perfect
+compliance with GNU FSDG criteria.
 
-Libreboot's Binary Blob Reduction Policy is superior, because it allows
+Libreboot's Binary Blob Reduction Policy is more ideal, because it allows
 more people to use coreboot, thus increasing software freedom overall for more
 people, but there is no harm in Canoeboot so long as it does not stifle Libreboot
 development; so Canoeboot is only updated after each Libreboot release,

site/gnuboot.md

@@ -8,9 +8,9 @@ read the [about page](about.md), the [Libreboot Binary Blob Reduction
 Policy](https://libreboot.org/news/policy.html) and the [GNU Boot article
 on libreboot.org](https://libreboot.org/news/gnuboot.html) - all of that energy
 has fuelled the creation of this page, and in fact the entire Canoeboot project.
-The purpose of Canoeboot is to be superior to GNU Boot, while complying with
-all of its policies by providing ROM images and source tarballs adhering to
-the GNU Free System Distribution Guidelines, [even though GNU FSDG is
+The main purpose of Canoeboot is to be technically superior to GNU Boot, while
+complying with all of its policies by providing ROM images and source tarballs
+adhering to the GNU Free System Distribution Guidelines, [even though GNU FSDG is
 deeply flawed](https://libreboot.org/news/policy.html#problems-with-fsdg); this
 page describes precisely how that has been achieved, and it will be updated
 over time as Canoeboot continues to develop.
@@ -553,18 +553,15 @@ Build system / performance improvements in Canoeboot:
 Summary
 =======
 
-Now, does this mean Canoeboot is *good*? The answer is an emphatic no. It only
-means that Canoeboot is far superior to GNU Boot, on a technical level.
-
-Canoeboot is still *inferior* to Libreboot, for all of the reasons laid out in
+So, in conclusion: this page is not trying to tell you why you should use
+Canoeboot; rather, it's just telling you that someone worse exists. Canoeboot
+and GNU Boot are *both* inherently flawed in their designs; *both* projects are
+completely *inferior* to the Libreboot project, for all the reasons laid out in
 the [Binary Blob Reduction Policy](https://libreboot.org/news/policy.html) - the
 Canoeboot project is provided, specifically, to prove the merits of that policy,
 by showing what Libreboot would have been by now if it continued adhering to
 GNU policy, instead of changing to its current Blob Reduction Policy.
 
-So, in conclusion: this page is not trying to tell you why you should use
-Canoeboot; rather, it's just telling you that someone worse exists.
-
 Libreboot provides all of the same blob-free configurations as Canoeboot, when
 possible on any given mainboard, and that is the preference, but the FSF/GNU
 dogma states that the user must never run any proprietary software. This dogma
@@ -583,9 +580,9 @@ we can, meeting people where they're at right now.
 
 And that is why Libreboot exists in the way that it does. Canoeboot serves as an
 example of what would happen in the best-case scenario if Libreboot never changed
-its policy. That best case scenario is still inferior to Libreboot. Canoeboot
-is missing a ton of boards and features from Libreboot. you can see that
-by reading the Canoeboot 20231026 and nonGeNUine Boot 20230717 change logs.
+its policy. The best possible release of Canoeboot will still be missing a ton
+of boards and features from Libreboot. Indeed, the Canoeboot 20231026 and
+nonGeNUine Boot 20230717 both illustrate that quite nicely.
 
 Actual summary
 ==============

site/news/canoeboot20231026.md

@@ -755,7 +755,10 @@ I make these Canoeboot releases, specifically so that I have something to crap
 all over. I could criticise GNU Boot more heavily, but GNU Boot is even more
 inferior; I make Canoeboot as good as it can feasibly be at any point in time,
 and criticise *that* result. My arguments are stronger when an *example* exists,
-especially a strong example such as Canoeboot.
+especially a strong example such as Canoeboot. If the best possible solution is
+still inferior, then that will further invalidate the even lesser solutions,
+and that is the entire purpose of Canoeboot; I make Canoeboot releases,
+specifically that I can crap all over them. I'm allowed to do that if it's mine.
 
 [Download Libreboot 20231021 instead](https://libreboot.org/news/libreboot20231021.html).