From cf7c2bb0079a1e227fd6da68a4e5d079f4689748 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Kacper=20=C5=81ukawski?= Date: Wed, 3 Apr 2024 09:04:09 +0200 Subject: [PATCH] Update tutorial link --- .../documentation/tutorials/customer-support-cohere-airbyte.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/qdrant-landing/content/documentation/tutorials/customer-support-cohere-airbyte.md b/qdrant-landing/content/documentation/tutorials/customer-support-cohere-airbyte.md index 018af3531..837f34115 100644 --- a/qdrant-landing/content/documentation/tutorials/customer-support-cohere-airbyte.md +++ b/qdrant-landing/content/documentation/tutorials/customer-support-cohere-airbyte.md @@ -142,7 +142,7 @@ Lambda](https://aws.amazon.com/lambda/?c=ser&sec=srv). In general, RAG connector has to expose a single endpoint that will accept POST requests with `query` parameter and return the matching documents as JSON document with a specific structure. Our FastAPI implementation created [in the -related tutorial](../tutorials/cohere-rag-connector/) is a perfect fit for this task. The only difference is that you +related tutorial](../cohere-rag-connector/) is a perfect fit for this task. The only difference is that you should point it to the Cohere models and Qdrant running on AWS infrastructure. > Our connector is a lightweight web service that exposes a single endpoint and glues the Cohere embedding model with