diff --git a/exercises/02.side-effects/01.problem.effects/README.mdx b/exercises/02.side-effects/01.problem.effects/README.mdx index 5b68b4425..1f882a99b 100644 --- a/exercises/02.side-effects/01.problem.effects/README.mdx +++ b/exercises/02.side-effects/01.problem.effects/README.mdx @@ -10,7 +10,7 @@ full refresh of the page when the user clicks the back/forward button. 🧝‍♂️ I added a new utility called `setGlobalSearchParams` which allows us to set the URL search params without triggering a full-page refresh. So whenever the user clicks "submit," we update the URL search params. The trouble is, when they -hit the back button, the search doesn't stay synchronoized with the URL (yet). +hit the back button, the search doesn't stay synchronized with the URL (yet). You can take a look at my changes for details on what I did. diff --git a/exercises/02.side-effects/README.mdx b/exercises/02.side-effects/README.mdx index 438f0c484..e0723cef7 100644 --- a/exercises/02.side-effects/README.mdx +++ b/exercises/02.side-effects/README.mdx @@ -25,11 +25,11 @@ useEffect(() => { ]) ``` -`useState` is for managing our react component state and `useEffect` is for -managing side-effects. Side-effects are things that happen outside our react +`useState` is for managing our React component state and `useEffect` is for +managing side-effects. Side-effects are things that happen outside our React components. -For example, things outside our react components include: +For example, things outside our React components include: - Browser APIs like local storage, geolocation, media devices, etc. - Integrations with third-party libraries like D3, Chart.js, etc. diff --git a/exercises/03.lifting-state/01.problem.lift/README.mdx b/exercises/03.lifting-state/01.problem.lift/README.mdx index 9250fb391..6453dcafe 100644 --- a/exercises/03.lifting-state/01.problem.lift/README.mdx +++ b/exercises/03.lifting-state/01.problem.lift/README.mdx @@ -8,7 +8,7 @@ to know what I've done. I pretty much just moved stuff into separate components to get a little more organization in here. - 🦉 check out [When to break up a component into multiple + 🦉 Check out [When to break up a component into multiple components](https://kentcdodds.com/blog/when-to-break-up-a-component-into-multiple-components). diff --git a/exercises/06.tic-tac-toe/02.problem.local-storage/index.tsx b/exercises/06.tic-tac-toe/02.problem.local-storage/index.tsx index 40ffe8b1a..65eae27b3 100644 --- a/exercises/06.tic-tac-toe/02.problem.local-storage/index.tsx +++ b/exercises/06.tic-tac-toe/02.problem.local-storage/index.tsx @@ -11,7 +11,7 @@ const defaultState = Array(9).fill(null) // 🐨 create a variable for the key you'll use for storing the squares // 💰 'squares' should work well. function Board() { - // 🐨 use the callback form for useState the callback should: + // 🐨 use the callback form for useState. The callback should: // 1. get the value from localStorage using the key you created above // 2. parse the JSON from that value // 3. return the parsed value (or the default value if there isn't one)