diff --git a/fsfe.org/activities/android/locked_down.en.xhtml b/fsfe.org/activities/android/locked_down.en.xhtml
index ad3acbee68..4a471cc817 100644
--- a/fsfe.org/activities/android/locked_down.en.xhtml
+++ b/fsfe.org/activities/android/locked_down.en.xhtml
@@ -45,7 +45,7 @@ The default design philosophy is simple: “Here’s a machine. You decide
 what to boot.” It’s not perfect, but it’s flexible enough that different
 operating systems can coexist without begging each vendor for
 permission.</p>
-    <h3 id="standards-the-boring-miracle-behind-user-freedom">Standards: the
+    <h3 id="standards-the-boring-miracle-behind-user-freedom">Standards: The
 boring miracle behind user freedom</h3>
     <p>The same factors that required standardisation around the boot
 process, also required standardisation around other components. Over the
@@ -70,7 +70,7 @@ typically a simple, freedom-respecting workflow: download an ISO, write
 it to USB, boot, install, and you’re done. That workflow exists because
 the platform is broadly standardised and designed for user control.</p>
     <h2 id="smartphones-the-dark-corner-of-software-freedom">Smartphones:
-the dark corner of software freedom</h2>
+The dark corner of software freedom</h2>
     <p>Now let’s talk about smartphones. Technically, inside you’ll find an
 ARM System-on-Chip (SoC), a cellular modem, a GPU, an image signal
 processor, DSPs for audio and “AI” acceleration, and a constellation of