Skip to content

Commit 1fa0855

Browse files
committed
revised for transitions
1 parent e657a15 commit 1fa0855

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

articles/search/search-normalizers.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -18,16 +18,16 @@ ms.date: 07/14/2022
1818
1919
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.
2020

21-
Some of the text transformations that can be achieved using normalizers are:
21+
By applying a normalizer, you can achieve text transformations that improve results:
2222

23-
+ Case conversion (lowercase or upper-case)
23+
+ Consistent casing (such as all lowercase or uppercase)
2424
+ Normalize accents and diacritics like ö or ê to ASCII equivalent characters "o" and "e"
2525
+ Map characters like `-` and whitespace into a user-specified character
2626

27-
Normalizers are specified on string fields in the index and are applied during indexing and query execution.
27+
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 always used as a requirement of tokenization. Normalizers are optional and used only if you specify them.
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.
3131
3232
## Benefits of normalizers
3333

0 commit comments

Comments
 (0)