Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
In an internal discussion, we found the current vCPU doc - https://www.elastic.co/docs/deploy-manage/deploy/elastic-cloud/ec-vcpu-boost-instance is causing confusion and we get cases from customers / users due to the lack of below 2 pointers:
Without these 2 pointers, it causes confusion that users think we are provide more vCPU resources (than expected) and Elastic is responsible for guaranteeing the vCPU credit behavior.
We want to update the doc to make more proper expectation. (internal ticket - link)
For reviewers
In addition to the default docs team's review, also:
Preview
https://docs-v3-preview.elastic.dev/elastic/docs-content/pull/2081/deploy-manage/deploy/elastic-cloud/ec-vcpu-boost-instance