added semantic ranking fix

Author: HeidiSteen

articles/search/search-synonyms.md

@@ -19,11 +19,11 @@ On a search service, a synonym map associates equivalent terms, expanding the sc
 
 Some key points about synonym maps:
 
-- A synonym map is an asset that can be created once and used by many indexes.
-- Synonyms apply to string fields.
-- You can create one at any time with no disruption to indexing or queries.
-- The [service tier](search-limits-quotas-capacity.md#synonym-limits) sets the limits on how many synonyms maps you can create.
-- A search service can have multiple synonym maps, but within an index, a field definition can only have one synonym map assignment.
+- A synonym map is a top-level resource that can be created once and used by many indexes.
+- A synonym map applies to string fields.
+- You can create and assign a synonym map at any time with no disruption to indexing or queries.
+- Your [service tier](search-limits-quotas-capacity.md#synonym-limits) sets the limits on how many synonyms maps you can create.
+- Your search service can have multiple synonym maps, but within an index, a field definition can only have one synonym map assignment.
 
 ## Create a synonym map
 

articles/search/semantic-how-to-query-request.md

@@ -10,7 +10,7 @@ ms.service: cognitive-search
 ms.custom:
   - ignite-2023
 ms.topic: how-to
-ms.date: 06/13/2024
+ms.date: 07/24/2024
 ---
 
 # Add semantic ranking to queries in Azure AI Search
@@ -43,11 +43,9 @@ You can use any of the following tools and SDKs to build a query that uses seman
 
 ## Avoid features that bypass relevance scoring
 
-Several query capabilities in Azure AI Search bypass relevance scoring or are otherwise incompatible with semantic ranking. If your query logic includes the following features, you can't semantically rank your results:
+A few query capabilities bypass relevance scoring, which makes them incompatible with semantic ranking. If your query logic includes the following features, you can't semantically rank your results:
 
-+ A query with `search=*` or an empty search string, such as pure filter-only query, won't work because there's nothing to measure semantic relevance against. The query must provide terms or phrases that can be assessed during processing.
-
-+ A query composed in the [full Lucene syntax](query-lucene-syntax.md) (`queryType=full`) is incompatible with semantic ranking (`queryType=semantic`). The semantic model doesn't support the full Lucene syntax.
++ A query with `search=*` or an empty search string, such as pure filter-only query, won't work because there's nothing to measure semantic relevance against and so the search scores are zero. The query must provide terms or phrases that can be evaluated during processing.
 
 + Sorting (orderBy clauses) on specific fields overrides search scores and a semantic score. Given that the semantic score is supposed to provide the ranking, adding an orderby clause results in an HTTP 400 error if you apply semantic ranking over ordered results.
 
@@ -116,9 +114,7 @@ The following example in this section uses the [hotels-sample-index](search-get-
 
 1. Set "queryType" to "semantic".
 
-   In other queries, the "queryType" is used to specify the query parser. In semantic ranking, it's set to "semantic". For the "search" field, you can specify queries that conform to the [simple syntax](query-simple-syntax.md).
-
-1. Set "search" to a full text search query based on the [simple syntax](query-simple-syntax.md). Semantic ranking is an extension of full text search, so while this parameter isn't required, you won't get an expected outcome if it's null.
+1. Set "search" to a full text search query. Your search string can support either the [simple syntax](query-simple-syntax.md) or [full Lucene syntax](query-lucene-syntax.md). Semantic ranking is an extension of full text search, so while "search" isn't required, you won't get an expected outcome if it's an empty search (`"search": "*"`).
 
 1. Set "semanticConfiguration" to a [predefined semantic configuration](semantic-how-to-configure.md) that's embedded in your index.