Merge pull request #236720 from seesharprun/docs-editor/concepts-limits-1683120520

Cosmos DB | Update minimum autoscale max RU/s

Author: prmerger-automator[bot]

articles/cosmos-db/concepts-limits.md

@@ -230,7 +230,7 @@ See the [Autoscale](provision-throughput-autoscale.md#autoscale-limits) article
 | Current RU/s the system is scaled to  |  `0.1*Tmax <= T <= Tmax`, based on usage|
 | Minimum billable RU/s per hour| `0.1 * Tmax` <br></br>Billing is done on a per-hour basis, where you're billed for the highest RU/s the system scaled to in the hour, or `0.1*Tmax`, whichever is higher. |
 | Minimum autoscale max RU/s for a container  |  `MAX(1000, highest max RU/s ever provisioned / 10, current storage in GB * 10)` rounded to nearest 1000 RU/s |
-| Minimum autoscale max RU/s for a database  |  `MAX(1000, highest max RU/s ever provisioned / 10, current storage in GB * 10,  1000 + (MAX(Container count - 25, 0) * 1000))`, rounded to nearest 1000 RU/s. <br></br>Note if your database has more than 25 containers, the system increments the minimum autoscale max RU/s by 1000 RU/s per extra container. For example, if you have 30 containers, the lowest autoscale maximum RU/s you can set is 6000 RU/s (scales between 600 - 6000 RU/s).
+| Minimum autoscale max RU/s for a database  |  `MAX(1000, highest max RU/s ever provisioned / 10, current storage in GB * 10,  1000 + (MAX(Container count - 25, 0) * 1000))`, rounded up to the nearest 1000 RU/s. <br></br>Note if your database has more than 25 containers, the system increments the minimum autoscale max RU/s by 1000 RU/s per extra container. For example, if you have 30 containers, the lowest autoscale maximum RU/s you can set is 6000 RU/s (scales between 600 - 6000 RU/s).|
 
 ## SQL query limits
 
@@ -301,3 +301,5 @@ In addition to the previous table, the [Per-account limits](#per-account-limits)
 
 * Read more about [global distribution](distribute-data-globally.md)
 * Read more about [partitioning](partitioning-overview.md) and [provisioned throughput](request-units.md).
+
+