diff --git a/docs/pages/product/caching/using-pre-aggregations.mdx b/docs/pages/product/caching/using-pre-aggregations.mdx
index 743811bed9ac3..41a2260dc85b4 100644
--- a/docs/pages/product/caching/using-pre-aggregations.mdx
+++ b/docs/pages/product/caching/using-pre-aggregations.mdx
@@ -238,7 +238,7 @@ This issue can be addressed by lambda pre-aggregations.
 
 Alternatively, if you want to explicitly introduce key partitioning, you can use multi-tenancy to introduce multiple orchestrator IDs.
 Each orchestrator ID can use a different pre-aggregation schema, so you may define those based on the partitioning key you want to introduce.
-This technique, together with multi router Cube Store approach, allows you to
+This technique, together with multi-router Cube Store approach, allows you to achieve linear scaling on the partitioning key of your choice.
 
 ## Using Indexes