Update deploy-manage/deploy/elastic-cloud/restrictions-known-problems.md

Co-authored-by: shainaraskas <[email protected]>

Author: kunisen

deploy-manage/deploy/elastic-cloud/restrictions-known-problems.md

@@ -135,9 +135,11 @@ To make a seamless migration, after restoring from a snapshot there are some add
 
 ## Node count and size [ec-node-count-size]
 * In the {{ecloud}} console UI, the maximum configurable node count is 32.
-  * The total RAM for `Size per zone` is calculated by multiplying the maximum RAM size of the [instance configuration](cloud://reference/cloud-hosted/hardware.md) in use by 32. For example, for the instance configuration [`aws.es.datahot.c6gd`](cloud://reference/cloud-hosted/aws-default.md), the maximum RAM size is 60GB. Therefore, the total RAM for `Size per zone` is `60GB x 32 = 1.875TB` (displayed as `1.88TB` in the {{ecloud}} console UI).
-  * This maximum node count limitation applies to the UI and affects both the maximum `Size per zone` during manual scaling and the `Maximum size per zone` in autoscaling.
-  * This limit is in place to prevent users from inadvertently deploying excessive capacity. However, this limitation does not apply when using the API for manual scaling or autoscaling. If you require additional capacity, you can use the API to scale up or configure the maximum size for autoscaling, in a self-sufficient way. For more guidance on using the cloud API, please review the [Elastic Cloud RESTful API](cloud://reference/cloud-hosted/ec-api-restful.md). Specifically, the section on [API examples > Deployment CRUD operations > Update a deployment](cloud://reference/cloud-hosted/ec-api-deployment-crud.md#ec_update_a_deployment) provides an example of how to make a deployment update request via the API.
+  The total RAM for `Size per zone` is calculated by multiplying the maximum RAM size of the [instance configuration](cloud://reference/cloud-hosted/hardware.md) in use by 32. For example, for the instance configuration [`aws.es.datahot.c6gd`](cloud://reference/cloud-hosted/aws-default.md), the maximum RAM size is 60GB. Therefore, the total RAM for `Size per zone` is `60GB x 32 = 1.875TB` (displayed as `1.88TB` in the {{ecloud}} console UI).
+  
+  This maximum node count limitation applies to the UI and affects both the maximum `Size per zone` during manual scaling and the `Maximum size per zone` in autoscaling. This limit is in place to prevent users from inadvertently deploying excessive capacity. 
+  
+  This limitation does not apply when using the API for manual scaling or autoscaling. If you require additional capacity, you can use the [Elastic Cloud API](cloud://reference/cloud-hosted/ec-api-restful.md) to scale up or configure the maximum size for autoscaling. Refer to the [Update a deployment](cloud://reference/cloud-hosted/ec-api-deployment-crud.md#ec_update_a_deployment) example to learn how to make a deployment update request using the API.
 * Apart from the maximum node count configurable in the {{ecloud}} console UI, there are other service limits based on each instance configuration. These service limits are typically greater than 32. For more details, please [contact Elastic support for assistance](/troubleshoot/index.md).
 
 ## Repository analysis API is unavailable in {{ecloud}} [ec-repository-analyis-unavailable]