Conversation
✅ Vale Linting ResultsNo issues found on modified lines! The Vale linter checks documentation changes against the Elastic Docs style guide. To use Vale locally or report issues, refer to Elastic style guide for Vale. |
Co-authored-by: Visha Angelova <91186315+vishaangelova@users.noreply.github.com>
Co-authored-by: Visha Angelova <91186315+vishaangelova@users.noreply.github.com>
5f87f49 to
6085079
Compare
|
Hey @stefnestor, I renamed the |
Co-authored-by: Visha Angelova <91186315+vishaangelova@users.noreply.github.com>
|
Super thank you, @vishaangelova 🙏 for your feedback and sorry for missing that doc file name fix. Changes accepted. |
vishaangelova
left a comment
There was a problem hiding this comment.
Great update! Thanks!:) Just one comment/suggestion left, but otherwise LGTM!!
Co-authored-by: Visha Angelova <91186315+vishaangelova@users.noreply.github.com>
|
Thank you for unresolving that & apologies I think after it gets 40 comments the UI+I start fighting on getting actions to take effect and telling which failed to so sorry for marking that wrong pre-emptively. |
florent-leborgne
left a comment
There was a problem hiding this comment.
Experience-docs related changes LGTM
Summary
👋 howdy, team! Furthering our standardization of product diagnostic guidance, this ports the existing troubleshooting section into its own page & makes "contact us for Agent" a first-class citizen.
It partially pulls from this top Support article, but mostly just rephrases existing links into one easy-access location.
Generative AI disclosure