edits

Author: GitHubber17

articles/search/media/search-get-started-portal/index-schema-definition.png

@@ -89,16 +89,9 @@ The Azure Cognitive Search service generates a schema for the built-in hotels-sa
 
 Typically, in a code-based exercise, index creation is completed prior to loading data. The **Import data** wizard condenses these steps by generating a basic index for any data source it can crawl.
 
-Each index is configured with the following settings:
+At a minimum, the index requires an **Index name** and a collection of **Fields**. One field must be marked as the _document key_ to uniquely identify each document. The index **Key** provides the unique document identifier. The value is always a string. If you want autocomplete or suggested queries, you can specify language **Analyzers** or **Suggesters**.
 
-- At a minimum, the index requires an **Index name** and a collection of **Fields** with at least one field.
-- One field must be marked as the _document key_ to uniquely identify each document. Only one field can be the document key.
-- The index **Key** provides the unique document identifier. The value is always a string.
-- If you want autocomplete or suggested queries, you can specify language **Analyzers** or **Suggesters**.
-
-Each field has a name, data type, and _attributes_ that control how to use the field in the search index.
-
-The **Customize target index** tab uses checkboxes to enable or disable the following attributes for all fields or specific fields.
+Each field has a name, data type, and _attributes_ that control how to use the field in the search index. The **Customize target index** tab uses checkboxes to enable or disable the following attributes for all fields or specific fields:
 
 - **Retrievable**: Include the field contents in the search index.
 - **Filterable**: Allow the field contents to be used as filters for the search index.
@@ -216,9 +209,9 @@ The queries in the following table are designed for searching the hotels-sample
 | --- | --- | --- | --- |
 | `search=spa` | Full text query | The `search=` parameter searches for specific keywords. | The query seeks hotel data that contains the keyword `spa` in any searchable field in the document. |
 | `search=beach &$filter=Rating gt 4` | Filtered query | The `filter` parameter filters on the supplied conditions. | The query seeks beach hotels with a rating value greater than four. |
-| `search=spa &$select=HotelName,Description,Tags &$count=true &$top=10` | Parameterized query | The ampersand symbol `&` appends search parameters, which can be specified in any order. <br> - The `$select` parameter returns a subset of fields for more concise search results. <br> - The `$count=true` parameter returns the total count of all documents that match the query. <br> - The `$top` parameter returns the specified number of highest ranked documents out of the total. By default, Azure Cognitive Search returns the first 50 best matches. You can increase or decrease the amount by using this parameter. | The query seeks the top 10 spa hotels and displays their names, descriptions, and tags. | 
+| `search=spa &$select=HotelName,Description,Tags &$count=true &$top=10` | Parameterized query | The ampersand symbol `&` appends search parameters, which can be specified in any order. <br> - The `$select` parameter returns a subset of fields for more concise search results. <br> - The `$count=true` parameter returns the total count of all documents that match the query. <br> - The `$top` parameter returns the specified number of highest ranked documents out of the total. | The query seeks the top 10 spa hotels and displays their names, descriptions, and tags. <br><br> By default, Azure Cognitive Search returns the first 50 best matches. You can increase or decrease the amount by using this parameter. | 
 | `search=* &facet=Category &$top=2` | Facet query on a string value | The `facet` parameter returns an aggregated count of documents that match the specified field. <br> - The specified field must be marked as **Facetable** in the index. <br> - On an empty or unqualified search, all documents are represented. | The query seeks the aggregated count for the `Category` field and displays the top 2. |
-| `search=spa &facet=Rating`| Facet query on a numeric value | Same description as previous example | The query seeks spa hotels for the `Rating` field data. <br> - The `Rating` field can be specified as a facet because it's marked as **Retrievable**, **Filterable**, and **Facetable** in the index. <br> - The `Rating` field has numeric values (1 through 5) that are suitable for grouping results by each value. |
+| `search=spa &facet=Rating`| Facet query on a numeric value | The `facet` parameter returns an aggregated count of documents that match the specified field. <br> - Although the `Rating` field is a numeric value, it can be specified as a facet because it's marked as **Retrievable**, **Filterable**, and **Facetable** in the index. | The query seeks spa hotels for the `Rating` field data. The `Rating` field has numeric values (1 through 5) that are suitable for grouping results by each value. |
 | `search=beach &highlight=Description &$select=HotelName, Description, Category, Tags` | Hit highlighting | The `highlight` parameter applies highlighting to matching instances of the specified keyword in the document data. | The query seeks and highlights instances of the keyword `beach` in the `Description` field, and displays the corresponding hotel names, descriptions, category, and tags. |
 | Original: `search=seatle` <br><br> Adjusted: `search=seatle~ &queryType=full` | Fuzzy search | By default, misspelled query terms like `seatle` for `Seattle` fail to return matches in a typical search. The `queryType=full` parameter invokes the full Lucene query parser, which supports the tilde `~` operand. When these parameters are present, the query performs a fuzzy search for the specified keyword. The query seeks matching results along with results that are similar to but not an exact match to the keyword. | The original query returns no results because the keyword `seatle` is misspelled. <br><br> The adjusted query invokes the full Lucene query parser to match instances of the term `seatle~`. |
 | `$filter=geo.distance(Location, geography'POINT(-122.12 47.67)') le 5 &search=* &$select=HotelName, Address/City, Address/StateProvince &$count=true` | Geospatial search | The `$filter=geo.distance` parameter filters all results for positional data based on the specified `Location` and `geography'POINT` coordinates. | The query seeks hotels that are within 5 kilometers of the latitude longitude coordinates `-122.12 47.67`, which is "Redmond, Washington, USA." The query displays the total number of matches `&$count=true` with the hotel names and address locations. |