From d9ff879cba4cf96454318f4fc92914731be5270c Mon Sep 17 00:00:00 2001 From: timvisee Date: Thu, 8 Feb 2024 09:52:09 +0100 Subject: [PATCH] Fix typo --- qdrant-landing/content/documentation/cloud/capacity-sizing.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/qdrant-landing/content/documentation/cloud/capacity-sizing.md b/qdrant-landing/content/documentation/cloud/capacity-sizing.md index bd8bcf327..0ba1ca553 100644 --- a/qdrant-landing/content/documentation/cloud/capacity-sizing.md +++ b/qdrant-landing/content/documentation/cloud/capacity-sizing.md @@ -43,7 +43,7 @@ If your use case assumes that the vectors are split into multiple collections or it is recommended to configure memory-map storage. For example, if you serve search for multiple users, but each of them has an subset of vectors which they use independently. -In this scenatio only the active subset of vectors will be kept in RAM, which allows +In this scenario only the active subset of vectors will be kept in RAM, which allows the fast search for the most active and recent users. In this case you can estimate required memory size as follows: