Skip to content

Commit 9812ccc

Browse files
Apply suggestions from code review
Co-authored-by: David Dougherty <[email protected]>
1 parent c553148 commit 9812ccc

File tree

1 file changed

+3
-4
lines changed

1 file changed

+3
-4
lines changed

content/develop/clients/lettuce/vecsets.md

Lines changed: 3 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -157,7 +157,7 @@ The reason for using text embeddings rather than simple text search
157157
is that the embeddings represent semantic information. This allows a query
158158
to find elements with a similar meaning even if the text is
159159
different. For example, the word "entertainer" doesn't appear in any of the
160-
descriptions but if you use it as a query, the actors and musicians are ranked
160+
descriptions, but if you use it as a query, the actors and musicians are ranked
161161
highest in the results list:
162162

163163
{{< clients-example set="home_vecsets" step="entertainer_query" lang_filter="Java-Async,Java-Reactive" >}}
@@ -171,9 +171,8 @@ Similarly, if you use "science" as a query, you get the following results:
171171
'Chaim Topol']
172172
```
173173

174-
The scientists are ranked highest but they are then followed by the
175-
mathematicians. This seems reasonable given the connection between mathematics
176-
and science.
174+
The scientists are ranked highest, followed by the
175+
mathematicians. This ranking seems reasonable given the connection between mathematics and science.
177176

178177
You can also use
179178
[filter expressions]({{< relref "/develop/data-types/vector-sets/filtered-search" >}})

0 commit comments

Comments
 (0)