From 7f01f29fda9d032d3a2cba76085198494f40819d Mon Sep 17 00:00:00 2001
From: Chelsgray <98662174+Chelsgray@users.noreply.github.com>
Date: Wed, 21 Sep 2022 01:27:02 -0700
Subject: [PATCH] fix(docs): typo in how to work on coding challenges (#47575)

---
 docs/how-to-work-on-coding-challenges.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/how-to-work-on-coding-challenges.md b/docs/how-to-work-on-coding-challenges.md
index be77553b63e..46311103c23 100644
--- a/docs/how-to-work-on-coding-challenges.md
+++ b/docs/how-to-work-on-coding-challenges.md
@@ -245,7 +245,7 @@ If it takes longer than two minutes to complete the challenge, you have two opti
 
 The 2-minute rule forces you, the challenge designer, to make your directions concise, your seed code clear, and your tests straight-forward.
 
-We track how long it takes for campers to solve changes and use this information to identify challenges that need to be simplified or split.
+We track how long it takes for campers to solve challenges and use this information to identify challenges that need to be simplified or split.
 
 ### Modularity