Add key and improve clarity in people.map() example

[LijuanTang94]

This PR improves the beginner-facing example in the "Rendering data from arrays" section.

Changes:

• Adds a key prop to each <li> element when mapping over the people array (to resolve console warning)

This change aligns the code with React best practices and helps new learners avoid common pitfalls when rendering lists.

[facebook-github-bot]

Hi @LijuanTang94!

Thank you for your pull request and welcome to our community.

Action Required

In order to merge any pull request (code, docs, etc.), we require contributors to sign our Contributor License Agreement, and we don't seem to have one on file for you.

Process

In order for us to review and merge your suggested changes, please sign at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need to sign the corporate CLA.

Once the CLA is signed, our tooling will perform checks and validations. Afterwards, the pull request will be tagged with CLA signed. The tagging process may take up to 1 hour after signing. Please give it that time before contacting us about it.

If you have received this in error or have any questions, please contact us at cla@meta.com. Thanks!

[chipit24]

This is done on purpose. Right under that example they even call out the error:

---

Notice the sandbox above displays a console error [...] You’ll learn how to fix this error later on this page. Before we get to that, let’s add some structure to your data.

I think this is a great way to introduce a basic concept to beginners: not overwhelming them at the start with why a key might be needed, and building on the basic concepts first.