Skip to content

Commit b04d940

Browse files
committed
rephrased the intro sentence
1 parent 1fa0855 commit b04d940

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

articles/search/search-normalizers.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -16,9 +16,9 @@ ms.date: 07/14/2022
1616
> [!IMPORTANT]
1717
> This feature is in public preview under [Supplemental Terms of Use](https://azure.microsoft.com/support/legal/preview-supplemental-terms/). The [preview REST API](/rest/api/searchservice/index-preview) supports this feature.
1818
19-
In Azure Cognitive Search, a *normalizer* is a component that pre-processes text for keyword matching over fields marked as "filterable", "facetable", or "sortable". In contrast with "searchable" fields that are paired with [text analyzers](search-analyzers.md), filterable-facetable-sortable content doesn't undergo analysis or tokenization, which can yield unexpected results.
19+
In Azure Cognitive Search, a *normalizer* is a component that pre-processes text for keyword matching over fields marked as "filterable", "facetable", or "sortable". In contrast with full text "searchable" fields that are paired with [text analyzers](search-analyzers.md), content that's created for filter-facet-sort operations doesn't undergo analysis or tokenization. Omission of text analysis can produce unexpected results when casing and character differences show up.
2020

21-
By applying a normalizer, you can achieve text transformations that improve results:
21+
By applying a normalizer, you can achieve light text transformations that improve results:
2222

2323
+ Consistent casing (such as all lowercase or uppercase)
2424
+ Normalize accents and diacritics like ö or ê to ASCII equivalent characters "o" and "e"
@@ -27,7 +27,7 @@ By applying a normalizer, you can achieve text transformations that improve resu
2727
Normalizers are specified on string fields in the index and applied during indexing and query execution.
2828

2929
> [!NOTE]
30-
> If fields are both searchable and filterable (or facetable or sortable), both analyzers and normalizers can be used. Analyzers are ways used on searchable fields as a requirement of tokenization. Normalizers are optional.
30+
> If fields are both searchable and filterable (or facetable or sortable), both analyzers and normalizers can be used. Analyzers are always used on searchable fields because its required for tokenization. Normalizers are optional.
3131
3232
## Benefits of normalizers
3333

0 commit comments

Comments
 (0)