diff --git a/src/posts/2023/another-eleventy-content-syndication-path.md b/src/posts/2023/another-eleventy-content-syndication-path.md
index 9d5ba07d..124762c3 100644
--- a/src/posts/2023/another-eleventy-content-syndication-path.md
+++ b/src/posts/2023/another-eleventy-content-syndication-path.md
@@ -2,7 +2,7 @@
 date: '2023-03-28'
 title: 'Another Eleventy content syndication path'
 draft: false
-tags: ['Eleventy', '11ty', 'Mastodon', 'json', 'rss']
+tags: ['Eleventy', 'Mastodon', 'json', 'rss']
 ---
 
 After posting and [discussing](https://social.lol/@nhoizey@mamot.fr/110101373765987885) [my post from yesterday](/posts/2023/automate-syndicate-content-mastodon-eleventy/) with [Nicolas Hoizey](https://nicolas-hoizey.com/) I decided to explore his suggested path and explore using a GitHub action to handle posts to Mastodon, rather than Make.<!-- excerpt --> Nicolas, thankfully, [has an action that supports exactly this path](https://github.com/marketplace/actions/any-feed-to-mastodon). It currently supports JSON feeds, [with planned support for Atom/RSS](https://github.com/nhoizey/github-action-feed-to-mastodon/issues/16).[^1]
diff --git a/src/posts/2023/building-my-now-page-using-eleventy.md b/src/posts/2023/building-my-now-page-using-eleventy.md
index c6f90af9..50588533 100644
--- a/src/posts/2023/building-my-now-page-using-eleventy.md
+++ b/src/posts/2023/building-my-now-page-using-eleventy.md
@@ -2,7 +2,7 @@
 date: '2023-03-18'
 title: 'Building my /now page using Eleventy'
 draft: false
-tags: ['11ty', 'eleventy', 'javascript', 'last.fm', 'oku', 'trakt', 'letterboxd']
+tags: ['Eleventy', 'javascript', 'last.fm', 'oku', 'trakt', 'letterboxd']
 ---
 
 As part of my commitment to writing about things I've written in other frameworks in Eleventy, this is how I re-engineered [my /now page](/now) in [Eleventy](https://www.11ty.dev/).<!-- excerpt -->[^1]
diff --git a/src/posts/2023/env-files-eleventy.md b/src/posts/2023/env-files-eleventy.md
index 283f9754..50b615f9 100644
--- a/src/posts/2023/env-files-eleventy.md
+++ b/src/posts/2023/env-files-eleventy.md
@@ -2,7 +2,7 @@
 date: '2023-03-24'
 title: '.env files in Eleventy'
 draft: false
-tags: ['.env', '11ty', 'eleventy']
+tags: ['.env', 'Eleventy']
 ---
 
 **dotenv-flow:**
diff --git a/src/posts/2023/scheduled-eleventy-builds-cron-github-actions.md b/src/posts/2023/scheduled-eleventy-builds-cron-github-actions.md
index 98140d96..6489b48a 100644
--- a/src/posts/2023/scheduled-eleventy-builds-cron-github-actions.md
+++ b/src/posts/2023/scheduled-eleventy-builds-cron-github-actions.md
@@ -2,7 +2,7 @@
 date: '2023-03-19'
 title: 'Scheduled Eleventy builds on Vercel with cron-triggered GitHub actions'
 draft: false
-tags: ['11ty', 'eleventy', 'javascript', 'automation', 'github', 'github actions', 'cron', 'yaml']
+tags: ['Eleventy', 'javascript', 'automation', 'github', 'github actions', 'cron', 'yaml']
 ---
 
 In an effort to get away from client-side Javascript and embrace Eleventy for what it is (a static site generator), I've dropped my [social-utils](https://github.com/cdransf/social-utils) instance offline and my now-playing track display on my home page that still relied on it.<!-- excerpt -->
diff --git a/src/posts/2023/webmentions-in-eleventy.md b/src/posts/2023/webmentions-in-eleventy.md
index e7ba1a86..6477ac2f 100644
--- a/src/posts/2023/webmentions-in-eleventy.md
+++ b/src/posts/2023/webmentions-in-eleventy.md
@@ -2,7 +2,7 @@
 date: '2023-03-17'
 title: 'Webmentions in Eleventy'
 draft: false
-tags: ['webmentions', '11ty', 'eleventy']
+tags: ['webmentions', 'Eleventy']
 ---
 
 In the interest of continuing to repeat myself I'm writing, once again, about adding webmentions to a blog.<!-- excerpt -->[^1] To quote myself[^2]: