From f05099b0f986262c843db3bdf4822cf775b3770a Mon Sep 17 00:00:00 2001 From: Jan Martiska Date: Wed, 22 Jan 2025 14:29:05 +0100 Subject: [PATCH] Fix some docs typos --- docs/modules/ROOT/pages/ai-services.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/modules/ROOT/pages/ai-services.adoc b/docs/modules/ROOT/pages/ai-services.adoc index febeff716..bc9633174 100644 --- a/docs/modules/ROOT/pages/ai-services.adoc +++ b/docs/modules/ROOT/pages/ai-services.adoc @@ -210,7 +210,7 @@ The extension provides a default implementation of `ChatMemoryProvider` which do [IMPORTANT] ==== The topic of `ChatMemory` cleanup is of paramount importance in order to avoid having the application terminate with `out of memory` errors. For this reason, the extension automatically removes all the `ChatMemory` objects from -the underlying `ChatMemoryStore` when the AI Service goes out of scope (recall from our discussion about <> that such bean are `@RequestScoped` be default). +the underlying `ChatMemoryStore` when the AI Service goes out of scope (recall from our discussion about <> that such beans are `@RequestScoped` by default). However, in cases where more fine-grained control is needed (which is the case when the bean is declared as `@Singleton` or `@ApplicationScoped`) then `io.quarkiverse.langchain4j.ChatMemoryRemover` should be used to manually remove elements. ====