From 513a944573dd523c739a08df95f50d4b5029c99e Mon Sep 17 00:00:00 2001
From: James Garbutt <43081j@users.noreply.github.com>
Date: Sun, 28 Jun 2026 17:23:20 +0100
Subject: [PATCH] chore: tweak readme wording

---
 README.md | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/README.md b/README.md
index 9f3ada0..f4a331c 100644
--- a/README.md
+++ b/README.md
@@ -12,13 +12,13 @@ You can learn a lot about these optimizations on the [v8 website](https://v8.dev
 
 ## Use with care :boom:
 
-If you resolve all of the diagnostics, you'll generally end up with incredibly performant code **for v8** and **this version of v8**.
+If you resolve all of the diagnostics, you'll generally end up with incredibly performant code **for this version of v8**.
 
 However, there are a few things to note:
 
 - v8 changes over time, and so do the optimizations
-- we should raise bugs in v8 for notable slow syntax rather than working around it
-- other engines (non-v8) will have different optimizations, and it is unlikely you can write code that is optimal for all of them
+- we should raise bugs in v8 for notably slow syntax rather than working around it
+- other engines (non-v8) will have different optimizations, and it is unlikely you can write code that is (super) optimal for all of them
 - different versions of v8 (and thus Node.js) may optimize code differently
 
 Many of the more common optimizations (e.g. consistent shapes of objects) seem unlikely to ever stop being optimized. These are the ones worth focusing on rather than the more niche ones.