docs: improve system limit page (#1309)

* fix: update section title

update section title from 'rate limit' to 'limit'

* refactor: optimize wording

* docs: update Management API rate limit section

---------

Co-authored-by: Gao Sun <gao@silverhand.io>

Author: fleuraly

docs/integrate-logto/interact-with-management-api/README.mdx

@@ -135,7 +135,7 @@ There are 2 optional query parameters:
 This is only for Logto Cloud.
 :::
 
-To ensure the reliability and security of our services for all users, we employ a general firewall that monitors and manages traffic to our website. While we do not enforce a strict rate limit, we recommend that users limit their activity to approximately 200 requests every 10 seconds to avoid triggering our protective measures.
+Logto Cloud applies tenant-level runtime rate limits to protect system stability. For details, see the [system limit rate-limit section](/logto-cloud/system-limit#rate-limit).
 
 ## Related resources \{#related-resources}
 

docs/logto-cloud/system-limit.mdx

@@ -1,22 +1,32 @@
 # System limit
 
-At Logto, we've set generous limits across all plans and provide flexible pay-as-you-go options, so users only pay for what they actually use.
+System limits define the maximum number of entities a tenant can create. They protect platform stability and are independent of billing. Some items on the pricing page are marked as _unlimited_ or _pay-as-you-go_. This means there is no billing cap, but internal system caps still apply to ensure fair use. We can review increases case by case.
 
-You may notice that some items on the pricing page are marked as _unlimited_ or as _continuous pay-as-you-go without a ceiling_. This means they can generally be used without restriction, but Logto reserves the right to adjust these actual limits over time to maintain fair use for all users. In other words, entity limits are strict caps that protect the platform's overall health. They are not part of pricing, though they may vary across different plan groups.
+## Types of limits \{#types-of-limits}
 
-If your use case is reasonable but reaches a system limit, feel free to [contact us](https://logto.io/contact) and share your feedback. This helps us better understand real-world usage patterns and adjust system limits to better support our loyal customers.
+### System resource and entity caps \{#system-resource-and-entity-caps}
 
-## Tenant-level rate limit protection \{#tenant-level-rate-limit-protection}
+Maximum counts for objects such as applications, roles, organizations, connectors, and certain usage-based system resources such as total token consumption. These limits vary by plan.
+
+### Rate limit \{#rate-limit}
+
+Request-level protection applied per tenant. The general guideline is **200 requests per 10 seconds per tenant**. If your traffic is legitimate and consistently exceeds this, we can evaluate an override case by case.
+
+---
+
+If your use case is valid and you hit a limit, contact us. This helps us adjust limits and support real-world scenarios.
+
+## Tenant-level limit protection \{#tenant-level-rate-limit-protection}
 
 ### Dev tenants \{#dev-tenants}
 
-For [Development tenants](/logto-cloud/tenant-settings#development), users can take advantage of Logto's free features and offerings. To prevent abuse and set clear expectations, we define certain system limits. These limits help us manage our platform sustainably while still providing free access for testing and development purposes.
+[Dev tenants](/logto-cloud/tenant-settings#development) provide free access for testing. To prevent abuse and to keep expectations clear, Dev tenants have fixed entity caps. If you need more, you can request an increase or upgrade to Pro for full access.
 
-If you'd like to increase your quota, you can contact us for assistance. We also recommend [upgrading from **Dev** to **Pro**](/logto-cloud/billing-and-pricing#dev-tenant-upgrade-to-pro), which removes the cap and gives you full access immediately.
+Dev tenants also follow a separate [data retention policy](/logto-cloud/dev-tenant-data-retention).
 
 | **Feature**                           | **Entity limit** |
 | ------------------------------------- | ---------------- |
-| **Included tokens**                   | 50k per mo       |
+| **Access token cap (monthly)**        | 50k per mo       |
 | **Applications**                      |                  |
 | Total applications                    | 100              |
 | Machine-to-machine apps               | 100              |
@@ -44,11 +54,11 @@ If you'd like to increase your quota, you can contact us for assistance. We also
 
 ### Pro tenants \{#pro-tenants}
 
-For Pro plan tenants, entity limits define the upper ceiling for add-ons and other "unlimited" entities such as applications. The details of the Pro plan's system limits are listed below.
+Pro tenants get increased caps. These apply to items marked as “unlimited” or to add-ons.
 
 | **Feature**                           | **Entity limit** |
 | ------------------------------------- | ---------------- |
-| **Included tokens**                   | 10M per mo       |
+| **Access token cap (monthly)**        | 10M per mo       |
 | **Applications**                      |                  |
 | Total applications                    | 100              |
 | Machine-to-machine apps               | 100              |
@@ -77,4 +87,4 @@ For Pro plan tenants, entity limits define the upper ceiling for add-ons and oth
 
 ### Enterprise tenants \{#enterprise-tenants}
 
-For Enterprise plans, limits and features are fully customizable and managed through the contract. Please [contact us](https://logto.io/contact) for more details.
+Enterprise limits and features are fully customizable and defined in the contract. [Contact us](https://logto.io/contact) for details.