Skip to content

Commit 933b603

Browse files
aeroastrojavanna
authored andcommitted
Fix typos in match in profile API (#46723)
* Replace `matches` with correct `match` * Use present tense consistently * Replace `metric` with correct `match`
1 parent 8dc6a3d commit 933b603

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

docs/reference/search/profile.asciidoc

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -349,11 +349,11 @@ The meaning of the stats are as follows:
349349
{empty} +
350350
Conjunctions (e.g. `must` clauses in a boolean) are typical consumers of `advance`
351351

352-
`matches`::
352+
`match`::
353353

354354
Some queries, such as phrase queries, match documents using a "two-phase" process. First, the document is
355355
"approximately" matched, and if it matches approximately, it is checked a second time with a more rigorous
356-
(and expensive) process. The second phase verification is what the `matches` statistic measures.
356+
(and expensive) process. The second phase verification is what the `match` statistic measures.
357357
{empty} +
358358
{empty} +
359359
For example, a phrase query first checks a document approximately by ensuring all terms in the phrase are
@@ -362,7 +362,7 @@ The meaning of the stats are as follows:
362362
of the terms.
363363
{empty} +
364364
{empty} +
365-
Because this two-phase process is only used by a handful of queries, the `metric` statistic will often be zero
365+
Because this two-phase process is only used by a handful of queries, the `match` statistic is often zero
366366

367367
`score`::
368368

0 commit comments

Comments
 (0)