Update content/blog/2025-04-09-2024-recap.md

Co-authored-by: Jonathan Wright <jonathan@almalinux.org>

content/blog/2025-04-09-2024-recap.md

@@ -45,7 +45,7 @@ When we were surprised by [Red Hat's change in 2023](https://almalinux.org/blog/
 
 To fix that, we established the [AlmaLinux Engineering Steering Committee](https://almalinux.org/blog/2024-05-21-introducing-alesco/), or ALESCo! In short, ALESCo is a group of engineers heavily involved in using and developing AlmaLinux, formed into a committee that has been generally guiding the technical progression and growth of AlmaLinux as an operating system. It acts as a central collaboration point for the AlmaLinux SIGs and community in general, and is the driving force behind any deviations that AlmaLinux takes from our upstreams while ensuring we maintain full compatibility with RHEL.
 
-For example, when made aware of CVEs like [CVE-2024-6387 (regreSSHion)](https://almalinux.org/blog/2024-07-01-almalinux-9-cve-2024-6387/) and [CVE-2024-6409](https://almalinux.org/blog/2024-07-09-cve-2024-6409/), ALESCo made the decision to build the update and push the package to production on our own, without waiting for  a CentOS Stream/RHEL update.
+For example, when made aware of CVEs like [CVE-2024-6387 (regreSSHion)](https://almalinux.org/blog/2024-07-01-almalinux-9-cve-2024-6387/) and [CVE-2024-6409](https://almalinux.org/blog/2024-07-09-cve-2024-6409/), ALESCo made the decision to build the update and push the package to production on our own, without waiting for a CentOS Stream/RHEL update.
 
 We're looking forward to ALESCo continuing to guide the OS in a very public way, furthering our goal of providing full transparency regarding the technical decisions surrounding AlmaLinux.