Skip to content

Commit 2170998

Browse files
committed
Fixed blocking issues
1 parent 79aa1ed commit 2170998

4 files changed

+8
-8
lines changed

articles/search/tutorial-rag-build-solution-index-schema.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
---
2-
title: 'RAG Tutorial: Design an index'
2+
title: 'RAG tutorial: Design an index'
33
titleSuffix: Azure AI Search
44
description: Design an index for RAG patterns in Azure AI Search.
55

articles/search/tutorial-rag-build-solution-maximize-relevance.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
---
2-
title: 'RAG Tutorial: Relevance tuning'
2+
title: 'RAG tutorial: Tune relevance'
33
titleSuffix: Azure AI Search
44
description: Learn how to use the relevance tuning capabilities to return high quality results for generative search.
55

@@ -16,15 +16,15 @@ ms.date: 10/05/2024
1616

1717
In this tutorial, learn how to improve the relevance of search results used in RAG solutions. Relevance tuning can be an important factor in delivering a RAG solution that meets user expectations. In Azure AI Search, relevance tuning includes L2 semantic ranking and scoring profiles.
1818

19-
To implement some of these techniques, you revisit the index schema to add configurations for semantic ranking and scoring profiles. Other relevance tuning techniques can be applied to the queries themselves.
19+
To implement these capabilities, you revisit the index schema to add configurations for semantic ranking and scoring profiles. You then rerun the queries using the new constructs.
2020

2121
In this tutorial, you modify the existing search index and queries to use:
2222

2323
> [!div class="checklist"]
2424
> - L2 semantic ranking
2525
> - Scoring profile for document boosting
2626
27-
This tutorial updates the search index created by the [indexing pipeline](tutorial-rag-build-solution-pipeline.md). Updates don't affect the existing content, so no rebuild is necessary and you don't need to rerun the indexer.
27+
This tutorial updates the search index created by the [indexing pipeline](tutorial-rag-build-solution-pipeline.md). Updates don't affect the existing content, so no rebuild is necessary and you don't need to rerun the indexer.
2828

2929
> [!NOTE]
3030
> There are more relevance features in preview, including vector query weighting and setting minimum thresholds, but we omit them from this tutorial becaues they aren't yet available in the Azure SDK for Python.
@@ -122,7 +122,7 @@ In a previous tutorial, you [designed an index schema](tutorial-rag-build-soluti
122122

123123
## Update queries for semantic ranking and scoring profiles
124124

125-
In a previous tutorial, you [ran queries](tutorial-rag-build-solution-query.md) that execute on the search engine, and pass the response and other information to an LLM for chat completion.
125+
In a previous tutorial, you [ran queries](tutorial-rag-build-solution-query.md) that execute on the search engine, passing the response and other information to an LLM for chat completion.
126126

127127
This example modifies the query request to include the semantic configuration and scoring profile.
128128

articles/search/tutorial-rag-build-solution-pipeline.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
---
2-
title: 'RAG Tutorial: Build an indexing pipeline'
2+
title: 'RAG tutorial: Build an indexing pipeline'
33
titleSuffix: Azure AI Search
44
description: Create an indexer-driven pipeline that loads, chunks, embeds, and ingests content for RAG solutions on Azure AI Search.
55

articles/search/tutorial-rag-build-solution-query.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
---
2-
title: 'RAG Tutorial: Search using an LLM'
2+
title: 'RAG tutorial: Search using an LLM'
33
titleSuffix: Azure AI Search
44
description: Learn how to build queries and engineer prompts for LLM-enabled search on Azure AI Search. Queries used in generative search provide the inputs to an LLM chat engine.
55

@@ -132,7 +132,7 @@ It's expected for LLMs to return different answers, even if the prompt and queri
132132
133133
## Add a filter
134134

135-
Recall that you created a `locations` field using applied AI, populated with places recognized by the Entity Recognition skill. The field definition for locations includes the `filterable` attribute. Let's repeat the previous request, but this time adding a filter that selects on the term *ice* in the locations field. A filter introduces inclusion or exclusion criteria. The search engine is still doing a vector search on `"how much of earth is covered by water"`, but it's now excluding matches that don't include *ice*. For more information about filtering on string collections and on vector queries, see [text filter fundamentals](search-filters.md#text-filter-fundamentals),[Understand collection filters](search-query-understand-collection-filters.md), and [Add filters to a vector query](vector-search-filters.md).
135+
Recall that you created a `locations` field using applied AI, populated with places recognized by the Entity Recognition skill. The field definition for locations includes the `filterable` attribute. Let's repeat the previous request, but this time adding a filter that selects on the term *ice* in the locations field. A filter introduces inclusion or exclusion criteria. The search engine is still doing a vector search on `"how much of earth is covered by water"`, but it's now excluding matches that don't include *ice*. For more information about filtering on string collections and on vector queries, see [text filter fundamentals](search-filters.md#text-filter-fundamentals), [Understand collection filters](search-query-understand-collection-filters.md), and [Add filters to a vector query](vector-search-filters.md).
136136

137137
Replace the search_results definition with the following example that includes a filter:
138138

0 commit comments

Comments
 (0)