Remove nonsensical jargon from april-2024-security-releases.md

Signed-off-by: getsnoopy <getsnoopy@users.noreply.github.com>

apps/site/pages/en/blog/vulnerability/april-2024-security-releases.md

@@ -22,7 +22,7 @@ This security release includes the following dependency updates to address publi
 
 An attacker can make the Node.js HTTP/2 server completely unavailable by sending a small amount of HTTP/2 frames packets with a few HTTP/2 frames inside. It is possible to leave some data in nghttp2 memory after reset when headers with HTTP/2 CONTINUATION frame are sent to the server and then a TCP connection is abruptly closed by the client triggering the Http2Session destructor while header frames are still being processed (and stored in memory) causing a race condition.
 
-Impacts:
+Affects:
 
 - This vulnerability affects all users in all active release lines: 18.x, 20.x and, 21.x.
 
@@ -32,7 +32,7 @@ Thank you, to bart for reporting this vulnerability and [Anna Henningsen](https:
 
 The team has identified a vulnerability in the http server of the most recent version of Node, where malformed headers can lead to HTTP request smuggling. Specifically, if a space is placed before a content-length header, it is not interpreted correctly, enabling attackers to smuggle in a second request within the body of the first.
 
-Impacts:
+Affects:
 
 - This vulnerability affects all users in all active release lines: 18.x, 20.x and, 21.x.
 
@@ -48,7 +48,7 @@ releases lines on or shortly after, Wednesday, April 3, 2024 in order to address
 - 1 medium severity issue.
 - 1 high severity issue.
 
-## Impact
+## Consequences
 
 The 18.x release line of Node.js is vulnerable to 1 medium severity issue, 1 high severity issue.
 The 20.x release line of Node.js is vulnerable to 1 medium severity issue, 1 high severity issue.