[DOCS] Updated wording for clarity for new users

[thekofimensah]

This is a small change but I felt the previous wording was only clear to those who already understand this behavior. Someone who is unfamiliar would be scratching their head, and hopefully this is an improvement.

[github-actions]

Documentation preview:

• ✨ Changed pages

[elasticsearchmachine]

Pinging @elastic/es-docs (Team:Docs)

[leemthompo]

I would suggest renaming this note to be specific about types/behaviors.

I'd reword the note to something like this:

.Arrays with `object` field type vs `nested` type
[NOTE]
====================================================
By default, arrays of objects are <<nested-arrays-flattening-objects,flattened>> 
during indexing using the <<object,`object` field type>>. For example, if you 
have multiple objects with a "name" property, all names will be stored in a 
single field. Queries against these flattened fields might match values from different objects. 
To query each object independently, use the <<nested,`nested`>> data type instead.
====================================================

I think the link to the flattening example is the best illustration of this behavior.

[leemthompo]

(also remember to target main :) )

[thekofimensah]

I would suggest renaming this note to be specific about types/behaviors.

I'd reword the note to something like this:

.Arrays with `object` field type vs `nested` type
[NOTE]
====================================================
By default, arrays of objects are <<nested-arrays-flattening-objects,flattened>> 
during indexing using the <<object,`object` field type>>. For example, if you 
have multiple objects with a "name" property, all names will be stored in a 
single field. Queries against these flattened fields might match values from different objects. 
To query each object independently, use the <<nested,`nested`>> data type instead.
====================================================

I think the link to the flattening example is the best illustration of this behavior.

I also like the example in the flattened doc. I incorporated your heading and suggestions, though adjusted the wording a bit.

[elasticsearchmachine]

💚 Backport successful

Status	Branch	Result
✅	8.16
✅	main
✅	8.x

[leemthompo]

If we had time to workshop this a bit more, we could have made the "unexpected behavior" more explicit because it remains a little handwavey, but this is definitely an improvement 👍