diff --git a/docs/en/cloud/bestpractices/usagelimits.md b/docs/en/cloud/bestpractices/usagelimits.md
index 21fcf74a325..00dd8f24e55 100644
--- a/docs/en/cloud/bestpractices/usagelimits.md
+++ b/docs/en/cloud/bestpractices/usagelimits.md
@@ -4,22 +4,26 @@ sidebar_label: Usage Limits
 title: Usage Limits
 ---
 
-
-## Database Limits
-Clickhouse is very fast and reliable, but any database has its limits. For example, having too many tables or databases could negatively affect performance. To avoid that, Clickhouse Cloud has guardrails for several types of items.
+While ClickHouse is known for its speed and reliability, optimal performance is achieved within certain operating parameters. For example, having too many tables, databases or parts could negatively impact performance. To avoid this, Clickhouse Cloud has guardrails set up for several types of items. You can find details of these guardrails below.
 
 :::tip
-If you've reached one of those limits, it may mean that you are implementing your use case in an unoptimized way. You can contact our support so we can help you refine your use case to avoid going through the limits or to increase the limits in a guided way. 
+If you've run up against one of these guardrails, it's possible that you are implementing your use case in an unoptimized way. Contact our support team and we will gladly help you refine your use case to avoid exceeding the guardrails or look together at how we can increase them in a controlled manner. 
 :::
 
-# Partitions
-Clickhouse Cloud have a limit of **50000** [partitions](https://clickhouse.com/docs/en/engines/table-engines/mergetree-family/custom-partitioning-key) per instance
-
-# Parts
-Clickhouse Cloud have a limit of **100000** [parts](https://clickhouse.com/docs/en/operations/system-tables/parts) per instance
+- **Databases**: 1000
+- **Tables**: 5000-10k
+- **Columns**: ∼1000 (wide format is preferred to compact)
+- **Partitions**: 50k
+- **Parts**: 100k across the entire instance
+- **Part size**: 150gb
+- **Services**: 20 (soft)
+- **Low cardinality**: 10k or less
+- **Primary keys in a table**: 4-5 that sufficiently filter down the data
+- **Concurrency**: default 100, can be increased to 1000 per node
+- **Batch ingest**: anything > 1M will be split by the system in 1M row blocks
 
 :::note
-For Single Replica Services, the maximum number of Databases is restricted to 100, and the maximum number of Tables is restricted to 500. In addition, Storage for Basic Tier Services is limited to 1 TB.
+For Single Replica Services, the maximum number of databases is restricted to 100, and the maximum number of tables is restricted to 500. In addition, storage for Basic Tier Services is limited to 1 TB.
 :::