From e28c7412c2fadffecf1f1ea6bca9818db8d3511e Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Mart=C3=ADn?= Date: Mon, 5 Aug 2024 13:18:25 -0300 Subject: [PATCH] Fix typo (#2041) --- frontend/src/pages/FineTuning/Steps/Introduction/index.jsx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/frontend/src/pages/FineTuning/Steps/Introduction/index.jsx b/frontend/src/pages/FineTuning/Steps/Introduction/index.jsx index 7b2a0b19..1b784d96 100644 --- a/frontend/src/pages/FineTuning/Steps/Introduction/index.jsx +++ b/frontend/src/pages/FineTuning/Steps/Introduction/index.jsx @@ -90,7 +90,7 @@ export default function Introduction({ setSettings, setStep }) {

In summary, if you are getting good results with RAG currently, creating a fine-tune can squeeze even more performance out - of a model. Fine-Tunes are are for improving response quality and + of a model. Fine-Tunes are for improving response quality and general responses, but they are not for knowledge recall - that is what RAG is for! Together, it is a powerful combination.