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

Co-authored-by: Edu González de la Herrán <[email protected]>

Author: kunisen

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

@@ -140,6 +140,6 @@ To make a seamless migration, after restoring from a snapshot there are some add
   * 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.
 * 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]
+## Repository analysis API is unavailable in {{ecloud}} [ec-repository-analyis-unavailable]
 
 * The {{es}} [Repository analysis API](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-snapshot-repository-analyze) is not available in {{ecloud}} due to deployments defaulting to having [operator privileges](../../users-roles/cluster-or-deployment-auth/operator-privileges.md) enabled that prevent non-operator privileged users from using it along with a number of other APIs.