From baba2fe5d5e5f0db8c727de46e33096f36787a8c Mon Sep 17 00:00:00 2001 From: Andreas Deininger Date: Sat, 31 May 2025 23:21:38 +0200 Subject: [PATCH] Fix typo --- src/data/post/astrowind-template-in-depth.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/data/post/astrowind-template-in-depth.mdx b/src/data/post/astrowind-template-in-depth.mdx index e7c4dd8..17e828f 100644 --- a/src/data/post/astrowind-template-in-depth.mdx +++ b/src/data/post/astrowind-template-in-depth.mdx @@ -137,7 +137,7 @@ This allows a great deal of flexibility in component design. Now, we get to the techniques used in _AstroWind_, we'll use the _pages/index.astro_ file to illustrate. -You'll note that the index file imports a lot of components, each one roughly analagous to a panel in the index page. Each of these components, in turn, is instantiated sequentially throughout the page. But, you'll notice that some of them use this kind of construct (we'll use the last section, _CallToAction_, as it is most illustrative of the technique): +You'll note that the index file imports a lot of components, each one roughly analogous to a panel in the index page. Each of these components, in turn, is instantiated sequentially throughout the page. But, you'll notice that some of them use this kind of construct (we'll use the last section, _CallToAction_, as it is most illustrative of the technique): ```astro