diff --git a/src/assets/article_hero_images/schematics-should-show-intent-rather-than-reailty.png b/src/assets/article_hero_images/schematics-should-show-intent-rather-than-reailty.png
new file mode 100644
index 0000000..95822a4
Binary files /dev/null and b/src/assets/article_hero_images/schematics-should-show-intent-rather-than-reailty.png differ
diff --git a/src/content/blog/schematics-should-show-intent-rather-than-reailty.md b/src/content/blog/schematics-should-show-intent-rather-than-reailty.md
index 3362384..19b0e37 100644
--- a/src/content/blog/schematics-should-show-intent-rather-than-reailty.md
+++ b/src/content/blog/schematics-should-show-intent-rather-than-reailty.md
@@ -3,7 +3,7 @@ title: 'schematics should show intent rather than reailty'
 description: |
     when people send me schematics for review, I occasionally see seemingly random connectors with no description or notes for what they are used for. Therefor this article covers how to change your schematic to be more readable at a glance.
 pubDate: '23 May 2026'
-heroImage: '../../assets/article_hero_images/ray_tracer.png'
+heroImage: '../../assets/article_hero_images/schematics-should-show-intent-rather-than-reailty.png'
 ---
 
 When reviewing schematics I will tend to find that people have designed their schematics to directly reflect the reality of what they are building.