From 032228dd80f3052ef97eaf752873f728f95d20a4 Mon Sep 17 00:00:00 2001
From: yokoffing <11689349+yokoffing@users.noreply.github.com>
Date: Tue, 21 Apr 2026 12:20:06 -0400
Subject: [PATCH] Updated Optional Hardening (markdown)

---
 Optional-Hardening.md | 9 ++++++---
 1 file changed, 6 insertions(+), 3 deletions(-)

diff --git a/Optional-Hardening.md b/Optional-Hardening.md
index ac89439..a591458 100644
--- a/Optional-Hardening.md
+++ b/Optional-Hardening.md
@@ -246,14 +246,17 @@ The optimizing compiler is like driving a 500-horsepower (HP) sports car to work
 
 ```javascript
 // PREF: disable JIT optimization
-// This removes most of the attack surface
-// while keeping JIT functionality.
+// This removes most of the attack surface while keeping JIT compilation.
 user_pref("javascript.options.ion", false);
 user_pref("javascript.options.wasm_optimizingjit", false);
 ```
 
 #### Option 2: Disable JIT
-The prefs below are the equivalent to running Chrome with the `--jitless` flag. Expect more site issues when choosing this option.
+The prefs below are the equivalent to running Chrome with the `--jitless` flag and using [Enhanced Security](https://support.microsoft.com/microsoft-edge/enhance-your-security-on-the-web-with-microsoft-edge-b8199f13-b21b-4a08-a806-daed31a1929d) in Edge.
+
+However, unlike Edge and Chrome, there are no per-site exceptions. It's all or nothing.
+
+This option is the most secure of the two, but you should expect more site issues when choosing this option.
 
 ```javascript
 // PREF: disable JIT compliation