From fd975c5b182c911f9dd7a3e82ee2c44474506cab Mon Sep 17 00:00:00 2001
From: Jake Lazaroff <yo@jake.nyc>
Date: Fri, 5 Jan 2024 20:12:02 -0500
Subject: [PATCH] Fix Astro SVG sprite sheet typo

---
 astro/generate-a-static-svg-sprite-sheet.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/astro/generate-a-static-svg-sprite-sheet.md b/astro/generate-a-static-svg-sprite-sheet.md
index b1b22fa..6daff51 100644
--- a/astro/generate-a-static-svg-sprite-sheet.md
+++ b/astro/generate-a-static-svg-sprite-sheet.md
@@ -10,7 +10,7 @@ Generally, my process looks something like this:
 
 I usually run it out of band, immediately before actually building the website. My build command ends up looking something like `pnpm svg && pnpm build` (where those are both `package.json` scripts that build the sprite sheet and the rest of the site).
 
-No longer! At least for Astro sites. Arne Bahlo has a great tutorial on [statically generating open graph images using Astro API routes](https://arne.me/articles/static-og-images-in-astro), and I realized that I use do the same technique to generate SVG sprite sheets.
+No longer! At least for Astro sites. Arne Bahlo has a great tutorial on [statically generating open graph images using Astro API routes](https://arne.me/articles/static-og-images-in-astro), and I realized that the same technique will work to generate SVG sprite sheets.
 
 The key insight is that in static mode, [API routes](https://docs.astro.build/en/core-concepts/endpoints/#server-endpoints-api-routes) get rendered to static files. So this roughly the same workflow, except `svg-sprite` gets called programmatically instead of on the command line.