Nitpicks for Section 1 (#241)

epicweb-dev · Oct 19, 2024 · ef36c80 · ef36c80
1 parent 1675fb2
commit ef36c80
Show file tree

Hide file tree

Showing 2 changed files with 4 additions and 2 deletions.
diff --git a/exercises/01.managing-ui-state/01.problem.use-state/README.mdx b/exercises/01.managing-ui-state/01.problem.use-state/README.mdx
@@ -5,7 +5,7 @@
 👨‍💼 We've got you working on a blog search page. Allow me to introduce you to
 🧝‍♂️ Kellie the coworker who put this together.
 
-🧝‍♂️ Hello! I'm Kellie the co-worker and I do things for you sometimes. I've
+🧝‍♂️ Hello! I'm Kellie the coworker and I do things for you sometimes. I've
 started up this app that you're going to be working with. There's a search
 input, a couple checkboxes, a submit button, and a list of blog posts. You've
 been asked to make it so when the user types into the search field it filters

diff --git a/exercises/01.managing-ui-state/05.problem.cb/README.mdx b/exercises/01.managing-ui-state/05.problem.cb/README.mdx
@@ -37,8 +37,10 @@ need it.
 So
 
 ```tsx
-// both of these work just fine:
+// This will call getQueryParam on every render, undermining our optimization! 😵
 const [query, setQuery] = useState(getQueryParam())
+
+// This will _only_ call getQueryParam on init. Great! ✅
 const [query, setQuery] = useState(getQueryParam)
 ```