From ef9919703b6475e4c0887d46e0850af0664d3655 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?=C5=81ukasz=20Rynek?= <36886649+lrynek@users.noreply.github.com> Date: Tue, 9 Jul 2024 18:38:14 +0200 Subject: [PATCH] Apply suggestions from code review MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-authored-by: Nathan Bower Signed-off-by: Łukasz Rynek <36886649+lrynek@users.noreply.github.com> --- _query-dsl/compound/function-score.md | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/_query-dsl/compound/function-score.md b/_query-dsl/compound/function-score.md index 83936fcb1f..98568e0965 100644 --- a/_query-dsl/compound/function-score.md +++ b/_query-dsl/compound/function-score.md @@ -834,7 +834,7 @@ When defining a function, you can specify its name using the `_name` parameter a ### Example -The following request sets `explain` to `true` for debugging purposes in order to obtain scoring explanation in the response. Each function contains a `_name` parameter so you can identify the function unambiguously: +The following request sets `explain` to `true` for debugging purposes in order to obtain a scoring explanation in the response. Each function contains a `_name` parameter so that you can identify the function unambiguously: ```json GET blogs/_search @@ -1020,4 +1020,3 @@ The response explains the scoring process. For each function, the explanation co ``` -As you can see, the explanation contains the name in the respective function's description.