From 7d8b41654975771c1f7f06280797c6335a8ec3a2 Mon Sep 17 00:00:00 2001
From: mat ess <mat@mat.services>
Date: Sat, 27 Aug 2022 22:04:46 -0400
Subject: [PATCH] Fixup captions

---
 content/posts/gitea-on-fly-io/index.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/content/posts/gitea-on-fly-io/index.md b/content/posts/gitea-on-fly-io/index.md
index 570e00d..471ef78 100644
--- a/content/posts/gitea-on-fly-io/index.md
+++ b/content/posts/gitea-on-fly-io/index.md
@@ -170,14 +170,14 @@ Uh. Hm. I just got an email saying a Fly.io instance ran out of memory and crash
 
 <figure>
 <img alt="Fly.io memory dashboard" src=fly-io-memory-dashboard.png />
-<figcaption class=meta>Fly.io memory dashboard</figcaption>
+<figcaption><h4>Fly.io memory dashboard</h4></figcaption>
 </figure>
 
 That doesn't look so great. It seems like Gitea idles just under the amount of memory we have with a default instance size, and operations like `git push` can bump it over the threshold to an out-of-memory error. Let's check out the "Scale" section of the dashboard, and increase the memory allotment for this VM:
 
 <figure>
 <img alt="Fly.io VM scaling interface" src=fly-io-scale-vm.png />
-<figcaption class=meta>Fly.io VM scaling interface</figcaption>
+<figcaption><h4>Fly.io VM scaling interface</h4></figcaption>
 </figure>
 
 I have been running my Gitea install on a 512MB instance since the first day I started using it, which seems to be plenty of headroom for personal use. If you open up your Gitea installation to the public and it starts to get popular, you might end up needing to scale up further.