Skip to content

Conversation

yetanothertw
Copy link
Contributor

Refers to #133622 where a review comment was missed and updates the docs accordingly.

Refers to elastic#133622 where a review comment was missed and updates the docs accordingly.
@yetanothertw yetanothertw self-assigned this Aug 28, 2025
@yetanothertw yetanothertw added >docs General docs changes Team:Docs Meta label for docs team documentation labels Aug 28, 2025
@yetanothertw yetanothertw marked this pull request as ready for review August 28, 2025 16:59
@elasticsearchmachine
Copy link
Collaborator

Pinging @elastic/core-docs (Team:Docs)

Copy link
Contributor

github-actions bot commented Aug 28, 2025

🔍 Preview links for changed docs

Copy link
Contributor

@shainaraskas shainaraskas left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

see comments with my apologies

:::{note}
In {{serverless-full}}, Elastic manages the underlying infrastructure for you. Because of this, privileges related to cluster administration, scaling, snapshots, and availability are not available. Learn more about the [project custom roles managed by {{serverless-full}}](docs-content://deploy-manage/users-roles/serverless-custom-roles.md).
:::
In {{serverless-full}}, Elastic manages the underlying infrastructure for you. Because of this, privileges related to cluster administration, scaling, snapshots, and availability are not available. [Learn more about the features managed by {{serverless-full}}](docs-content://deploy-manage/users-roles/serverless-custom-roles.md).
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

sry I know this is so annoying

the link you're pointing to here and the meaning of this para are two different things. this link explains how to apply the roles (spiritually similar to the para above)

Suggested change
In {{serverless-full}}, Elastic manages the underlying infrastructure for you. Because of this, privileges related to cluster administration, scaling, snapshots, and availability are not available. [Learn more about the features managed by {{serverless-full}}](docs-content://deploy-manage/users-roles/serverless-custom-roles.md).
:::{note}
In {{serverless-full}}, Elastic manages the underlying infrastructure for you. Because of this, privileges related to cluster administration, scaling, snapshots, and availability are not available. [Learn more about the features managed by {{serverless-full}}](docs-content:///deploy-manage/deploy/elastic-cloud/differences-from-other-elasticsearch-offerings.md).
:::

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I misunderstood, sorry about that. I hadn't realised that you meant to add a link to this particular page (in addition to the link for Serverless roles). I thought you only included the link as a reference to see how we talk about Serverless vs other deployments.

It's only annoying when I can't make sense of it, but once I understand it, I can see how everything falls into place and the docs are better for it.

Copy link
Contributor

@shainaraskas shainaraskas left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

approving to unblock after edit

@yetanothertw yetanothertw merged commit b5f5dcd into elastic:main Aug 29, 2025
10 checks passed
JeremyDahlgren pushed a commit to JeremyDahlgren/elasticsearch that referenced this pull request Aug 29, 2025
* Adds minor docs clarification

Refers to elastic#133622 where a review comment was missed and updates the docs accordingly.

* Adding link to the differences page for reference
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

>docs General docs changes documentation Team:Docs Meta label for docs team v9.2.0

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants