diff --git a/content/posts/website-best-practices.gmi b/content/posts/website-best-practices.gmi
index f2b1f89..929c90a 100644
--- a/content/posts/website-best-practices.gmi
+++ b/content/posts/website-best-practices.gmi
@@ -59,7 +59,7 @@ I have two responses:
 
 ## About custom colors
 
-Some users' browsers set default page colors that aren't white-on-black. For instance, Linux users who enable GTK style overrides might default to having white text on a dark background. Websites that explicitly set foreground colors but leave the default background color (or vice-versa) end up being difficult to read. Here's what this page would look like if it messed with the colors carelessly:
+Some users' browsers set default page colors that aren't black-on-white. For instance, Linux users who enable GTK style overrides might default to having white text on a dark background. Websites that explicitly set foreground colors but leave the default background color (or vice-versa) end up being difficult to read. Here's what this page would look like if it messed with the colors carelessly:
 
 => gemini://seirdy.one/misc/website_colors.png Screenshot of this page with some unreadable text
 
diff --git a/content/posts/website-best-practices.md b/content/posts/website-best-practices.md
index 5cbef6e..46e1109 100644
--- a/content/posts/website-best-practices.md
+++ b/content/posts/website-best-practices.md
@@ -119,7 +119,7 @@ I have two responses:
 About custom colors
 -------------------
 
-Some users' browsers set default page colors that aren't white-on-black. For
+Some users' browsers set default page colors that aren't black-on-white. For
 instance, Linux users who enable GTK style overrides might default to having white
 text on a dark background. Websites that explicitly set foreground colors but leave
 the default background color (or vice-versa) end up being difficult to read. Here's