[DOCS] Improved readability of multi-match query docs
This commit is contained in:
parent
6a399d4c9a
commit
4f99f0c6f1
|
@ -365,7 +365,7 @@ In other words, `first` and `last` would be grouped together and
|
|||
treated as a single field, and `first.edge` and `last.edge` would be
|
||||
grouped together and treated as a single field.
|
||||
|
||||
Having multiple groups is fine but, when combined with `operator` or
|
||||
Having multiple groups is fine, but when combined with `operator` or
|
||||
`minimum_should_match`, it can suffer from the <<operator-min,same problem>>
|
||||
as `most_fields` or `best_fields`.
|
||||
|
||||
|
|
Loading…
Reference in New Issue