diff --git a/blog/foss_is_working_against_itself.html b/blog/foss_is_working_against_itself.html
index 14a9c4c..d286a6b 100644
--- a/blog/foss_is_working_against_itself.html
+++ b/blog/foss_is_working_against_itself.html
@@ -5,7 +5,7 @@
 <!-- Copyright 2022 Jake Winters -->
 <!-- SPDX-License-Identifier: BSD-3-Clause -->
 
-<!-- Version: 5.0.1-alpha.10 -->
+<!-- Version: 5.0.2-alpha.1 -->
 
 
 <html>
@@ -31,7 +31,7 @@
 				<h1>Blog - #0</h1>
 						<h2>FOSS is Working Against Itself</h2>
 								<p class="update_date">Posted: 2022-01-27 (UTC+00:00)</p>
-								<p class="update_date">Updated: 2022-11-09 (UTC+00:00)</p>
+								<p class="update_date">Updated: 2023-10-31 (UTC+00:00)</p>
 						<section id="toc">
 								<h2 id="toc"><a href="#toc">Table of Contents<a/></h2>
 										<ul>
@@ -167,7 +167,7 @@
 										sides with any FOSS entities. The only way to win this war is to take
 										<em>whatever</em> hardware and software you can, and use it tactically.</p>
 										<p>The best solution for device security, privacy, and control, is to use a
-										Google Pixel (currently, Pixel 5a-series or newer) running
+										Google Pixel (currently, Pixel 5a or newer) running
 										<a href="https://grapheneos.org/">GrapheneOS</a>.
 										Google Pixel devices allow you complete bootloader freedom, including the
 										<a href="https://android.googlesource.com/platform/external/avb/+/master/README.md#pixel-2-and-later">ability to lock the bootloader after flashing a custom OS</a>
