From c0245a6ee9b8f7a5f79802f0517180308c0d1d5d Mon Sep 17 00:00:00 2001 From: Ari Shokri Date: Tue, 18 Mar 2025 17:00:39 -0500 Subject: [PATCH] docs: fix typo (#3854) probably > properly Co-authored-by: Vadym Barda --- docs/docs/how-tos/memory/manage-conversation-history.ipynb | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/docs/how-tos/memory/manage-conversation-history.ipynb b/docs/docs/how-tos/memory/manage-conversation-history.ipynb index fa89c267b..6407d50ec 100644 --- a/docs/docs/how-tos/memory/manage-conversation-history.ipynb +++ b/docs/docs/how-tos/memory/manage-conversation-history.ipynb @@ -7,7 +7,7 @@ "source": [ "# How to manage conversation history\n", "\n", - "One of the most common use cases for persistence is to use it to keep track of conversation history. This is great - it makes it easy to continue conversations. As conversations get longer and longer, however, this conversation history can build up and take up more and more of the context window. This can often be undesirable as it leads to more expensive and longer calls to the LLM, and potentially ones that error. In order to prevent this from happening, you need to probably manage the conversation history.\n", + "One of the most common use cases for persistence is to use it to keep track of conversation history. This is great - it makes it easy to continue conversations. As conversations get longer and longer, however, this conversation history can build up and take up more and more of the context window. This can often be undesirable as it leads to more expensive and longer calls to the LLM, and potentially ones that error. In order to prevent this from happening, you need to properly manage the conversation history.\n", "\n", "Note: this guide focuses on how to do this in LangGraph, where you can fully customize how this is done. If you want a more off-the-shelf solution, you can look into functionality provided in LangChain:\n", "\n",