More On State: Modify setCount example to improve clarity

[goran1010]

Because

This note from the lesson:

The unexpected infinite loop
The following is an infinite loop; can you guess why? Drop by in the TOP Discord server, tell us why, and score a brownie point!

function Component() {
   const [count, setCount] = useState(0);
 
   setCount(count + 1);
 
   return <h1>{count}</h1>;
 }

is rephrased to improve clarity.

This PR

• Rephrase The following is an infinite loop; can you guess why? to The following would cause an infinite loop, but React can, under certain circumstances, detect infinite re-renders and throw an error. Can you guess why React will throw an error here, warning you about too many re-renders?

This makes it a bit clearer that the code in example would cause an infinite loop (but you wouldn't necessarily see it bricking your browser tab), if React didn't have the ability to sometimes detect it, and throw an error instead.

Issue

Closes #30622

Additional Information

I've decided to slightly change the wording (compared to my initial suggestion in the Issue itself) to better match the Error that React shows in the browser dev console:

Error: Too many re-renders. React limits the number of renders to prevent an infinite loop.

Pull Request Requirements

• I have thoroughly read and understand The Odin Project curriculum contributing guide
• The title of this PR follows the location of change: brief description of change format, e.g. Intro to HTML and CSS lesson: Fix link text
• The Because section summarizes the reason for this PR
• The This PR section has a bullet point list describing the changes in this PR
• If this PR addresses an open issue, it is linked in the Issue section
• If any lesson files are included in this PR, they have been previewed with the Markdown preview tool to ensure it is formatted correctly
• If any lesson files are included in this PR, they follow the Layout Style Guide

[mao-sz]

🚀