From 0b85f9035bf4f6e87ad85a03dc3edf4116f42053 Mon Sep 17 00:00:00 2001 From: Zapiron <125368863+DangerousPotential@users.noreply.github.com> Date: Tue, 12 Nov 2024 01:17:29 +0800 Subject: [PATCH] docs: Makes the phrasing more smooth and reasoning more clear (#28020) Updated the phrasing and reasoning on the "abstraction not receiving much development" part of the documentation --------- Co-authored-by: ccurme --- docs/docs/versions/migrating_memory/index.mdx | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/docs/docs/versions/migrating_memory/index.mdx b/docs/docs/versions/migrating_memory/index.mdx index 8b8e668133..0043dcb13b 100644 --- a/docs/docs/versions/migrating_memory/index.mdx +++ b/docs/docs/versions/migrating_memory/index.mdx @@ -108,9 +108,8 @@ And specific backend implementations of abstractions: | `SQLiteEntityStore` | A specific implementation of `BaseEntityStore` that uses SQLite as the backend. | | `UpstashRedisEntityStore` | A specific implementation of `BaseEntityStore` that uses Upstash as the backend. | -These abstractions have not received much development since their initial release. The reason -is that for these abstractions to be useful they typically require a lot of specialization for a particular application, so these -abstractions are not as widely used as the conversation history management abstractions. +These abstractions have received limited development since their initial release. This is because they generally require significant customization for a specific application to be effective, making +them less widely used than the conversation history management abstractions. For this reason, there are no migration guides for these abstractions. If you're struggling to migrate an application that relies on these abstractions, please: