diff --git a/gemlog/loopy-keyboards.gmi b/gemlog/loopy-keyboards.gmi
index 4e3348f..ff4a89e 100644
--- a/gemlog/loopy-keyboards.gmi
+++ b/gemlog/loopy-keyboards.gmi
@@ -8,7 +8,7 @@ I used (and kind of loved) a bunch of different keyboards back in the day, inclu
 
 Seriously, look at this ridiculous layout:
 
-=> /res/images/2024-02-12-8pen-layout.png Image: Colored lines intersect behind a magnifying glass, which centers on letters and symbols arranged in a circle on a white background - but it's a keyboard, somehow?
+=> /res/2024-02-12-8pen-layout.png Image: Colored lines intersect behind a magnifying glass, which centers on letters and symbols arranged in a circle on a white background - but it's a keyboard, somehow?
 
 It's wild, right? Once I figured out how to use it, I got to be pretty fast and accurate at text entry - and it's designed in such a way that (once you learn it) you don't have to look at the keyboard at all.
 
@@ -21,4 +21,4 @@ It's also been enhanced with Vim-inspired editor ability, or something.
 
 I used 8vim to type (some) of this message and it only took forever. I'm sure I will get the hang of this again in no time.
 
-=> /res/images/2024-02-12-8vim-keyboard.png Image: A smartphone screen displaying a text editor app with a unique keyboard layout. The text discusses an open-source clone of an abandoned project, 8vim Keyboard, and mentions the user's experience adapting to it.
\ No newline at end of file
+=> /res/2024-02-12-8vim-keyboard.png Image: A smartphone screen displaying a text editor app with a unique keyboard layout. The text discusses an open-source clone of an abandoned project, 8vim Keyboard, and mentions the user's experience adapting to it.
\ No newline at end of file
diff --git a/gemlog/self-hosting-search-engine.gmi b/gemlog/self-hosting-search-engine.gmi
index 39c2a24..37081f6 100644
--- a/gemlog/self-hosting-search-engine.gmi
+++ b/gemlog/self-hosting-search-engine.gmi
@@ -6,7 +6,7 @@ I've lately been playing a bit with a self-hosted instance of SearXNG, an utterl
 Rather than maintaining its own index or running its own crawlers (as something like YaCy does), SearXNG simply asks other engines for their results to a given query (remember Dogpile from back in the day?). The really cool thing with SearXNG is that it also gives you, the user, a whole lot of control over what engines it uses to create its aggregated results.
 
 => https://yacy.net/ YaCy homepage
-=> /res/images/2024-02-21-searxng-prefs.png Image: SearXNG Preferences page listing some of the available search engines
+=> /res/2024-02-21-searxng-prefs.png Image: SearXNG Preferences page listing some of the available search engines
 
 It's pretty neat, and the results so far have been fairly decent. If you'd like to give it a try, my instance is at grep.vim.wtf. (At least until I get bored with it.)
 
diff --git a/gemlog/upptime-serverless-server-monitoring.gmi b/gemlog/upptime-serverless-server-monitoring.gmi
index 9062a06..7355fad 100644
--- a/gemlog/upptime-serverless-server-monitoring.gmi
+++ b/gemlog/upptime-serverless-server-monitoring.gmi
@@ -13,7 +13,7 @@ It didn't take much tinkering to get Upptime configured and operational for keep
 
 => https://status.runtimeterror.dev/ "Upptime Terror", the status page for my public sites
 
-=> /res/upptime-screenshot.png Image: Green-themed website status page displaying real-time data from a GitHub repository. It shows a 100% uptime for various services with average response times ranging from 545 ms to 747 ms.
+=> /res/2024-01-30-upptime-screenshot.png Image: Green-themed website status page displaying real-time data from a GitHub repository. It shows a 100% uptime for various services with average response times ranging from 545 ms to 747 ms.
 
 Check out the docs to learn more:
 => https://upptime.js.org/docs/ Upptime Documentation
\ No newline at end of file