diff --git a/content/posts/2024-11-25-the-case-of-the-missing-makefile-a-git-story.md b/content/posts/2024-11-25-the-case-of-the-missing-makefile-a-git-story.md
index e7103d1..5dcb389 100644
--- a/content/posts/2024-11-25-the-case-of-the-missing-makefile-a-git-story.md
+++ b/content/posts/2024-11-25-the-case-of-the-missing-makefile-a-git-story.md
@@ -1,7 +1,7 @@
 ---
 date: 2024-11-25
 title: "The Case of the Missing Makefile: A Git Story"
-tags: [git, makefile, infra]
+tags: [git, makefile]
 ---
 
 Imagine this: your CI/CD pipeline fails with a cryptic error message. Everything works perfectly on your local machine. The Makefile is present, the commands are valid, and there’s no apparent issue. Yet, the deployment fails repeatedly. What’s going on?
diff --git a/content/posts/saving-big-bucks-with-quickwit.md b/content/posts/saving-big-bucks-with-quickwit.md
index dfa82bf..1784753 100644
--- a/content/posts/saving-big-bucks-with-quickwit.md
+++ b/content/posts/saving-big-bucks-with-quickwit.md
@@ -1,7 +1,7 @@
 ---
 date: 2024-10-14
 title: How quickwit helped us reduce the cost
-tags: infra, kubernetes, logging, quickwit
+tags: infra, logging
 ---
 As an engineer at a rapidly growing startup, I found myself looking at an expensive logging system. We were heavily relying on [Opensearch](https://aws.amazon.com/opensearch-service/) and Heroku's [Mezmo](https://www.mezmo.com/) (formerly LogDNA) to handle all our logging needs. While these tools served us well, there was one major downside: the cost. At over $450 a month, maintaining such an infrastructure wasn't sustainable for a fast-growing company looking to scale smartly. So, I took it upon myself to find a better, more cost-efficient solution that wouldn't sacrifice performance.