From 7026196e370bd3c7cbe8b8e193aabe4c371285cd Mon Sep 17 00:00:00 2001
From: Kristian Aune <kraune@vespa.ai>
Date: Mon, 6 Jan 2025 15:48:19 +0100
Subject: [PATCH] Clarify

---
 en/reference/document-select-language.html | 9 ++++-----
 1 file changed, 4 insertions(+), 5 deletions(-)

diff --git a/en/reference/document-select-language.html b/en/reference/document-select-language.html
index 86b56035f2..7699204343 100644
--- a/en/reference/document-select-language.html
+++ b/en/reference/document-select-language.html
@@ -17,18 +17,17 @@ <h2 id="examples">Examples</h2>
 <p><code>music</code></p>
 <p>
   As applications can have multiple schemas,
-  match schema and then field-specific:
+  match document type (schema) and then a specific value in the <code>artistname</code> field:
 </p>
 <p><code>music and music.artistname == "Coldplay"</code></p>
 <p>
-  The below selects all documents with the above two conditions set.
-  The first condition states that the documents should be of type music,
+  Below, the first condition states that the documents should be of type music,
   and the author field must exist.
-  The second states that the field length must be set, and be less than 1000:
+  The second states that the field length must be set, and be less than or equal to 1000:
 </p>
 <p><code>music.author and music.length &lt;= 1000</code></p>
 <p>
-  This expression selects all documents where either of the subexpressions are true.
+  The next expression selects all documents where either of the subexpressions are true.
   The first one states that the author field should include the name John Doe, with anything in between or in front.
   The <code>\n</code> escape is converted to a newline before the field comparison is done.
   Thus requiring the field to end with Doe and a newline for a match to be true.