diff --git a/exercises/02.mobile-first/01.problem.structural-layout/src/App.tsx b/exercises/02.mobile-first/01.problem.structural-layout/src/App.tsx
index c901540..8c0ecef 100644
--- a/exercises/02.mobile-first/01.problem.structural-layout/src/App.tsx
+++ b/exercises/02.mobile-first/01.problem.structural-layout/src/App.tsx
@@ -7,25 +7,25 @@ export default function App() {
π¨ We need to wrap our entire markup inside two container divs.
The first one is the full-page container. It needs to:
- - have at minimum the full screen height (min-h-screen)
+ - have at minimum the full screen height (min-h-screen)
- centers its children with a grid (grid place-items-center)
- - handle horizontal and verticall padding (see Figma)
+ - handle horizontal and vertical padding (see Figma)
*/}
{/*
- π¨ Inside of that, wrap the entire markup in another 'div'.
+ π¨ Inside of that, wrap the entire markup in another 'div'.
This is our layout container, a common parent to both
- the logo list and the text content.
-
+ the logo list and the text content.
+
It needs to:
- be a grid (grid) that contains two children (cells)
- have a gap (gap-12)
- center its children (place-items-center)
*/}
- {/*
+ {/*
π¨ Wrap the Logo, h1 and paragraph in a common parent 'div'.
- It will become one of the two grid cells in our layout.
+ It will become one of the two grid cells in our layout.
*/}
diff --git a/exercises/02.mobile-first/02.problem.text-styles/src/App.tsx b/exercises/02.mobile-first/02.problem.text-styles/src/App.tsx
index ea1c10a..6851cf9 100644
--- a/exercises/02.mobile-first/02.problem.text-styles/src/App.tsx
+++ b/exercises/02.mobile-first/02.problem.text-styles/src/App.tsx
@@ -8,7 +8,7 @@ export default function App() {
π¨
Set a max-width of 'md' on the wrapping div below.
Center the elements horizontally:
- - Setup a veritcal flexbox container with 'flex flex-col'
+ - Setup a vertical flexbox container with 'flex flex-col'
- Align the items horizontally with 'items-center'
- Center the children text elements with 'text-center'
*/}
diff --git a/exercises/04.art-directed-grid/02.solution.grid-class-composition/README.mdx b/exercises/04.art-directed-grid/02.solution.grid-class-composition/README.mdx
index b2eecfb..8417d81 100644
--- a/exercises/04.art-directed-grid/02.solution.grid-class-composition/README.mdx
+++ b/exercises/04.art-directed-grid/02.solution.grid-class-composition/README.mdx
@@ -4,4 +4,4 @@
Whew! That was actually pretty easy π
-π¦ **Warning**: One thing to keep in mind is thatΒ when you start placing items manually in your grid like that, any element that _does not_ have a `grid-colum-start` or `grid-row-start` property will find the first available cell in the flow of the grid, and occupy that!
+π¦ **Warning**: One thing to keep in mind is thatΒ when you start placing items manually in your grid like that, any element that _does not_ have a `grid-column-start` or `grid-row-start` property will find the first available cell in the flow of the grid, and occupy that!
diff --git a/exercises/06.animation/03.problem.roll-reveal/tailwind.config.ts b/exercises/06.animation/03.problem.roll-reveal/tailwind.config.ts
index 5bc1a08..3b0cc53 100644
--- a/exercises/06.animation/03.problem.roll-reveal/tailwind.config.ts
+++ b/exercises/06.animation/03.problem.roll-reveal/tailwind.config.ts
@@ -2,9 +2,9 @@ import easings from 'open-props/src/easing'
import { type Config } from 'tailwindcss'
/*
- π§ββοΈ I've added the 'open-props' npm package and
+ π§ββοΈ I've added the 'open-props' npm package and
imported a series of easing timing functions.
-
+
You can use one of these to fine-tune the "roll-reveal" animation below!
*/
@@ -27,7 +27,7 @@ export default {
'5.5xl': ['3.375rem', '1'],
},
keyframes: {
- /*
+ /*
π¨ 1. Create a 'roll-reveal' keyframe object.
It should start with...
@@ -43,10 +43,10 @@ export default {
/*
π¨βπΌ We want to respect the user's system preferences for reduced motion,
- so let's also create an "alternative", simpler reveal.
+ so let's also create an "alternative", simpler reveal.
+
+ π¨ 2. Create a 'fade-in' keyframes definition.
- π¨ 2. Create a 'fade-in' keyframes definition.
-
It should start at 0% opacity and end at 100% opacity.
*/
'slide-left': {
@@ -59,17 +59,17 @@ export default {
},
},
animation: {
- /*
+ /*
π¨ 1. Add a 'roll-reveal' animation. It should use the 'roll-reveal' keyframe
you just created, and animate once over 0.4 seconds.
- Try your own easigns (https://cubic-bezier.com is a great resource β¨),
- or have fun playing with Open Props' easing function we've imported!
-
+ Try your own easings (https://cubic-bezier.com is a great resource β¨),
+ or have fun playing with Open Props' easing function we've imported!
+
In the solution, we use the `--ease-spring-2` easing function.
*/
- /*
+ /*
π¨ 2. Add a 'fade-in' animation. It should use the 'fade-in' keyframe
you just created, and animate once over 0.4 seconds.
*/
diff --git a/exercises/07.subgrid-alignment/01.problem.sub-grid/src/App.tsx b/exercises/07.subgrid-alignment/01.problem.sub-grid/src/App.tsx
index 55f3731..05d1707 100644
--- a/exercises/07.subgrid-alignment/01.problem.sub-grid/src/App.tsx
+++ b/exercises/07.subgrid-alignment/01.problem.sub-grid/src/App.tsx
@@ -65,14 +65,14 @@ export default function App() {
guide file for how to get your project off the ground!
- {/*
+ {/*
π¨ At the `xl` breakpoint...
-
+
1. Defer the grid rows to the parent grid with `subgrid`
2. Span the grid across 6 rows
π° You can define grid-template-rows as a `subgrid` with `grid-rows-subgrid`
- π° You can span an element acorss multiple rows with the `row-span-*` utilities
+ π° You can span an element across multiple rows with the `row-span-*` utilities
*/}
{logos.map((logo, i) => (
diff --git a/exercises/08.upgrade-to-tailwind-v4/01.problem.vite-plugin/README.mdx b/exercises/08.upgrade-to-tailwind-v4/01.problem.vite-plugin/README.mdx
index 089a37f..6bc6ff0 100644
--- a/exercises/08.upgrade-to-tailwind-v4/01.problem.vite-plugin/README.mdx
+++ b/exercises/08.upgrade-to-tailwind-v4/01.problem.vite-plugin/README.mdx
@@ -50,7 +50,7 @@ The Vite plugin version of Tailwind CSS v4 is _not_ a PostCSS plugin. We've also
Currently, the uses `@tailwind` PostCSS directives.
-BUT β we're not using PostCSS anymore! Instead, we're going to use a regular CSS import, and import the Tailwind CSS syles like so:
+BUT β we're not using PostCSS anymore! Instead, we're going to use a regular CSS import, and import the Tailwind CSS styles like so:
```css filename=src/styles/tailwind.css
@import 'tailwindcss';
diff --git a/exercises/08.upgrade-to-tailwind-v4/03.problem.font-sizes/README.mdx b/exercises/08.upgrade-to-tailwind-v4/03.problem.font-sizes/README.mdx
index 05ba7be..88da850 100644
--- a/exercises/08.upgrade-to-tailwind-v4/03.problem.font-sizes/README.mdx
+++ b/exercises/08.upgrade-to-tailwind-v4/03.problem.font-sizes/README.mdx
@@ -23,7 +23,7 @@ The `--line-height` appended to the `woof` font size variable will compose that
## Working around the `.` character in variable names
-π¨βπΌ Whoops βΒ we've named our custom font sizes `4.5xl` and `5.5xl`, but I'm told that a period (`.`) is not a valid characted for a CSS variable name.
+π¨βπΌ Whoops βΒ we've named our custom font sizes `4.5xl` and `5.5xl`, but I'm told that a period (`.`) is not a valid character for a CSS variable name.
π¨βπΌ In other words, `--font-size-4.5xl` won't work.