Skip to content

Commit 7c7b8aa

Browse files
committed
typo
1 parent b8c9509 commit 7c7b8aa

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

articles/search/search-pagination-page-layout.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -106,10 +106,10 @@ Notice that document 2 is fetched twice. This is because the new document 5 has
106106
In a full text search query, results can be ranked by:
107107

108108
+ a search score
109-
+ a semantic reranker scores
109+
+ a semantic reranker score
110110
+ a sort order on a "sortable" field
111111

112-
You can boost hits found in specific fields by adding a scoring profile.
112+
You can also boost any matches found in specific fields by adding a scoring profile.
113113

114114
### Order by search score
115115

@@ -141,7 +141,7 @@ String fields (Edm.String, Edm.ComplexType subfields) are sorted in either [ASCI
141141

142142
+ Strings that lead with diacritics appear last (Äpfel, Öffnen, Üben)
143143

144-
### Use a scoring profile to influence relevance
144+
### Boost relevance using a scoring profile
145145

146146
Another approach that promotes order consistency is using a [custom scoring profile](index-add-scoring-profiles.md). Scoring profiles give you more control over the ranking of items in search results, with the ability to boost matches found in specific fields. The extra scoring logic can help override minor differences among replicas because the search scores for each document are farther apart. We recommend the [ranking algorithm](index-ranking-similarity.md) for this approach.
147147

0 commit comments

Comments
 (0)