Merge pull request #202646 from HeidiSteen/heidist-support-case

[azure search] Edits to fuzzy search doc

Author: PRMerger14

articles/search/search-query-fuzzy.md

@@ -45,37 +45,37 @@ Collectively, the graphs are submitted as match criteria against tokens in the i
 
 ## Indexing for fuzzy search
 
-Make sure the index includes text fields that are conducive to fuzzy search, such as names, categories, descriptions, or tags. 
+String fields that are attributed as "searchable" are candidates for fuzzy search.
 
-Analyzers aren't used to create an expansion graph, but that doesn't mean analyzers should be ignored in fuzzy search scenarios. Analyzers are important for tokenization during indexing, where tokens are used for both full text search and for matching against the graph.
+Analyzers aren't used to create an expansion graph, but that doesn't mean analyzers should be ignored in fuzzy search scenarios. Analyzers are important for tokenization during indexing, where tokens in the inverted indexes are used for matching against the graph.
 
-As always, if test queries aren't producing the matches you expect, you could try varying the indexing analyzer, setting it to a [language analyzer](index-add-language-analyzers.md), to see if you get better results. Some languages, particularly those with vowel mutations, can benefit from the inflection and irregular word forms generated by the Microsoft natural language processors. In some cases, using the right language analyzer can make a difference in whether a term is tokenized in a way that is compatible with the value provided by the user.
+As always, if test queries aren't producing the matches you expect, experiment with different indexing analyzers. For example, try a [language analyzer](index-add-language-analyzers.md) to see if you get better results. Some languages, particularly those with vowel mutations, can benefit from the inflection and irregular word forms generated by the Microsoft natural language processors. In some cases, using the right language analyzer can make a difference in whether a term is tokenized in a way that is compatible with the value provided by the user.
 
-## How to use fuzzy search
+## How to invoke fuzzy search
 
-Fuzzy queries are constructed using the full Lucene query syntax, invoking the [full Lucene query parser](https://lucene.apache.org/core/6_6_1/queryparser/org/apache/lucene/queryparser/classic/package-summary.html).
+Fuzzy queries are constructed using the full Lucene query syntax, invoking the [full Lucene query parser](https://lucene.apache.org/core/6_6_1/queryparser/org/apache/lucene/queryparser/classic/package-summary.html), and appending a tilde character `~` after each whole term entered by the user.
+
+Here's an example of a query request that invokes fuzzy search. It includes four terms, two of which are misspelled:
 
 ```http
 POST https://[service name].search.windows.net/indexes/hotels-sample-index/docs/search?api-version=2020-06-30
 {
-    "search": "seatle~2",
+    "search": "seatle~ waterfront~ view~ hotle~",
     "queryType": "full",
     "searchMode": "any",
-    "searchFields": "HotelName, Address/City",
-    "select": "HotelName, Address/City,",
+    "searchFields": "HotelName, Description",
+    "select": "HotelName, Description, Address/City,",
     "count": "true"
 }
 ```
 
 1. Set the query type to the full Lucene syntax (`queryType=full`).
 
-1. Optionally, scope the request to specific fields, using this parameter (`searchFields=<field1,field2>`). 
-
-1. Provide the query string. An expansion graph will be created for every term in the query input. Append the tilde (`~`) operator at the end of each whole term (`search=<string>~`).
+1. Provide the query string where each term is followed by a tilde (`~`) operator at the end of each whole term (`search=<string>~`). An expansion graph will be created for every term in the query input.
 
    Include an optional parameter, a number between 0 and 2 (default), if you want to specify the edit distance (`~1`). For example, "blue~" or "blue~1" would return "blue", "blues", and "glue".
 
-In Azure Cognitive Search, besides the term and distance (maximum of 2), there are no other parameters to set on the query.
+Optionally, you can improve query performance by scoping the request to specific fields. Use the `searchFields` parameter to specify which fields to search. You can also use the `select` property to specify which fields are returned in the query response.
 
 ## Testing fuzzy search