diff --git a/.DS_Store b/.DS_Store
index bb66781..255650e 100644
Binary files a/.DS_Store and b/.DS_Store differ
diff --git a/markdown/Introducing HoneyPeer Collective Defense.md b/markdown/Introducing HoneyPeer Collective Defense.md
index c7f441f..bafa524 100644
--- a/markdown/Introducing HoneyPeer Collective Defense.md	
+++ b/markdown/Introducing HoneyPeer Collective Defense.md	
@@ -7,6 +7,10 @@ leet-wide distributed honeypot mesh built on Hyperswarm and HyperDB
 
 </div>
 
+<p align="center">
+  <img src="https://raven-scott.fyi/hp.png" alt="Centered Image" width="300">
+</p>
+
 Today I am announcing the **public Alpha** of [**HoneyPeer**](https://honeypeer.com) — operated by **HoneyPeer, LLC**, a Georgia limited liability company formed in DeKalb County. After years of R&D and a full year of building, testing, and hardening a peer-to-peer honeypot platform from the ground up, I am inviting operators, homelab enthusiasts, and security-minded teams to join the mesh **at no cost** while I finish the product for general availability.
 
 This is not a slide-deck honeypot. HoneyPeer is a **running system**: subscription-gated peers, a coordinator that ingests real attack telemetry, a detection engine that promotes IPs through reputation tiers, and **fleet-wide kernel firewall sync** so one probe anywhere can protect everyone. If you have ever wanted collective immunity against internet background radiation — SSH brute force, Redis scans, SMTP probes, credential stuffing against fake admin panels — this is what I built it for.