fuck

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

1 files changed, 1 insertions, 1 deletions

diff --git a/lume/src/shitposts/no-way-to-prevent-this/CVE-2024-2511.md b/lume/src/shitposts/no-way-to-prevent-this/CVE-2024-2511.md
index 5787bf1..7bbb701 100644
--- a/lume/src/shitposts/no-way-to-prevent-this/CVE-2024-2511.md
+++ b/lume/src/shitposts/no-way-to-prevent-this/CVE-2024-2511.md
@@ -10,7 +10,7 @@ hero:
 ---
 
 In the hours following the release of [CVE-2024-2511](https://www.openssl.org/news/secadv/20240408.txt) for the project [OpenSSL](https://www.openssl.org/), site reliability workers
-and systems administrators scrambled to desperately rebuild and patch all their systems to fix a memory leak that allows for unbound growth when using a non-default TLSv1.3 configuration. This is due to the affected components being
+and systems administrators scrambled to desperately rebuild and patch all their systems to fix a memory leak that allows for unbounded growth when using a non-default TLSv1.3 configuration. 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
 these things just happen and there's nothing anyone can do to stop them," said programmer Lady Shanel Streich, echoing statements
 expressed by hundreds of thousands of programmers who use the only language where 90% of the world's memory safety vulnerabilities have