Fix disabled dynamic mapping description in explicit mapping example

[erfansaberi]

Hi. I updated the description for the dynamic: false setting in the "Define explicit mapping" section of the Elasticsearch documentation.

Previously, the documentation stated:

Disables dynamic mapping for the index. Documents containing fields not defined in the mapping will be rejected.

This was misleading. In reality, when dynamic is set to false, fields not defined in the mapping are saved in the document but are not indexed or searchable. The document is still accepted.

The updated description now reads:

Disables dynamic mapping for the index. Fields not defined in the mapping will be saved but not indexed and not searchable.

This change aligns the documentation with Elasticsearch's actual behavior and clarifies the difference between false and strict values. If the intent is to reject documents that contain unmapped fields, the dynamic: strict setting should be used instead.

[cla-checker-service]

💚 CLA has been signed

[leemthompo]

Nice catch, thanks for the fix @erfansaberi! I made one suggestion to help make your explanation more precise :)

[erfansaberi]

Thanks for the great suggestion, @leemthompo — just applied it! The changes look ready to merge, but I don’t have access to merge it, please let me know if everything looks good or if I’m missing anything.