diff --git a/docs/dagster-university/pages/dagster-essentials/lesson-4/coding-practice-trips-by-week-asset.md b/docs/dagster-university/pages/dagster-essentials/lesson-4/coding-practice-trips-by-week-asset.md
index e732e00de02f0..8067d27dd281a 100644
--- a/docs/dagster-university/pages/dagster-essentials/lesson-4/coding-practice-trips-by-week-asset.md
+++ b/docs/dagster-university/pages/dagster-essentials/lesson-4/coding-practice-trips-by-week-asset.md
@@ -20,7 +20,7 @@ To practice what you’ve learned, create an asset in `metrics.py` that:
 
 {% callout %}
 
-> 💡 **Extra credit!** If want a challenge, follow this constraint:
+> 💡 **Extra credit!** If you want a challenge, follow this constraint:
 > Imagine that the entire `trips` data is too big to fit into memory. However, a week’s worth of data fits comfortably. How would you structure your asset’s function to accommodate this?
 
 {% /callout %}