From 8a64fe7e12deebbd8a5c45eefde475cda5041c45 Mon Sep 17 00:00:00 2001
From: Ross Alexander <73596879+rossalexander@users.noreply.github.com>
Date: Tue, 16 Apr 2024 11:35:32 +0200
Subject: [PATCH] Update tailwind-css.md

Fix small typo.
---
 sage/tailwind-css.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/sage/tailwind-css.md b/sage/tailwind-css.md
index 0e9fd6a3..df954a2c 100644
--- a/sage/tailwind-css.md
+++ b/sage/tailwind-css.md
@@ -108,4 +108,4 @@ Beware of how large your stylesheets will get if you are using all of the Tailwi
 
 The ideal setup is to remove _all_ classes that you aren't using from Tailwind, and only configure Tailwind with the classes that are required for your project.
 
-In the future, we might an add a more streamlined approach to doing this to Bud's `theme.json` generator. For now, deciding how you want the front-end CSS to work for Tailwind generated classes is up to you.
+In the future, we might add a more streamlined approach to doing this to Bud's `theme.json` generator. For now, deciding how you want the front-end CSS to work for Tailwind generated classes is up to you.