chore: oops FreeBSD is C, not C++

Signed-off-by: Xe Iaso <me@xeiaso.net>

Author: Xe

lume/src/shitposts/no-way-to-prevent-this/CVE-2026-45250.md

@@ -11,7 +11,7 @@ hero:
 
 In the hours following the release of [CVE-2026-45250](https://www.freebsd.org/security/advisories/FreeBSD-SA-26:18.setcred.asc) for the project [FreeBSD](https://www.freebsd.org/), site reliability workers
 and systems administrators scrambled to desperately rebuild and patch all their systems to fix a kernel stack overflow when validating permissions of the setcred(2) system call, allowing arbitrary code execution in the context of the kernel. This is due to the affected components being
-written in C++, the only programming language where these vulnerabilities regularly happen. "This was a terrible tragedy, but sometimes
+written in C, the only programming language where these vulnerabilities regularly happen. "This was a terrible tragedy, but sometimes
 these things just happen and there's nothing anyone can do to stop them," said programmer Mrs. Gregoria Doyle, echoing statements
 expressed by hundreds of thousands of programmers who use the only language where 90% of the world's memory safety vulnerabilities have
 occurred in the last 50 years, and whose projects are 20 times more likely to have security vulnerabilities. "It's a shame, but what can