[Suggestion]: Tic-tac-toe tutorial should explicitly explain that mutation causes unreliable re-rendering

Summary

The tutorial's Why immutability is important section doesn't clearly state that mutating state causes unreliable re-rendering behavior.

Page

https://react.dev/learn/tutorial-tic-tac-toe#why-immutability-is-important

Details

While following the tic-tac-toe tutorial, I was confused about why .slice() is necessary. The "Why immutability is important" section talks about time travel features and performance optimizations, but it never explains that mutating the array directly will cause React to not reliably detect the change, meaning the component may not re-render.

It seems as though that is the primary reason the tutorial uses .slice(), but it's not mentioned. I only found this explanation later in the "Updating Objects in State" article. It would be helpful to include this explanation in the tutorial where beginners first encounter the pattern.

Abre el tutorial de Tic-tac-toe enlazado en la sección «Why immutability is important» y compáralo con el artículo de referencia «Updating Objects in State». Actualiza el tutorial para explicar que la mutación directa puede impedir que React detecte los cambios y vuelva a renderizar de forma fiable; después, verifica que la explicación encaje con la discusión existente sobre slice(), time travel y performance.