Update 'README.md'

README.md

@@ -1,6 +1,7 @@
 # ⚔️ Exclusion Enforcer ⚔️
 ---
 ![ExclusionEnforcerBeast.png](http://192.168.4.20:3000/attachments/4af766f4-2f66-4377-8392-d099c77d3d40)
+(visual hallucination by OpenAI and Dall-E)
 
 👾 The Exclusion Enforcer, the final frontier in IP deny list management (what?) This is where packets meet their maker. Got a gaggle of pesky IP addresses wreaking havoc in your gig? I've got the fix. This has been a garage repo since '22, get it off the lot NOW, and this Python 3 beast will wrangle your deny lists, validate your scope, and generate the rules to drop those delinquent packets faster than you can press CTRL-C as the phone rings.
 
@@ -11,11 +12,11 @@ Exclusion Enforcer isn't for the faint of heart (it needs root for the iptables
 ### 🔍 Verify your scope
 Make sure no IP address evades your watchful eye. Feed it a deny list, and it'll cross-verify with your scope, ensuring not a single rogue packet slips through. Client handed you lists in mixed multiple formats? oh, ok. 
 
-- Individual IPs? got it. 
-- CIDR notion? no worries. 
-- That weird nmap thing with dashes? I think so?
+- Individual IPs? got *it*. 
+- CIDR notion? *no worries*. 
+- That weird nmap thing with dashes? I /think/ sooo?
 
-This bad boi will turn everything into a single format. can you pick the format? no, it's one ip per line.
+This bad boi will turn everything into a single format. And can you pick the format? No, it's one ip per line.
 
 ### 🔥 Integrate with iptables
 Once your deny list is vetted, Exclusion Enforcer will synergize directly with iptables, enforcing your will at the kernel level. Those packets won't even see it coming. Name your rule-set and when you're done...