From 13341debbab8021f2527782d3a82c936d8b6f680 Mon Sep 17 00:00:00 2001 From: Panagiotis Bailis Date: Thu, 7 Nov 2024 11:05:36 +0200 Subject: [PATCH] Apply suggestions from code review Co-authored-by: Carlos Delgado <6339205+carlosdelest@users.noreply.github.com> --- .../search/search-your-data/retrievers-overview.asciidoc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/reference/search/search-your-data/retrievers-overview.asciidoc b/docs/reference/search/search-your-data/retrievers-overview.asciidoc index 8b846abbce858..8ebe698b3ac80 100644 --- a/docs/reference/search/search-your-data/retrievers-overview.asciidoc +++ b/docs/reference/search/search-your-data/retrievers-overview.asciidoc @@ -71,8 +71,8 @@ When using compound retrievers, only the query element is allowed, which enforce Let's work through some examples to see how we can use and leverage retrievers to build an awesome search experience! -To show the full functionality, in this exercise, we'll assume that we have access to a reranker model through the inference service, -as well as access to Elser, for building semantic queries! +To show the full functionality, in this exercise, we'll assume that we have access to a <> through the inference service, +as well as access to <>, for building semantic queries! So, first things first, let's start by setting up these services and have them in place for later use!