-
Notifications
You must be signed in to change notification settings - Fork 195
Documents new D4C capabilities #4501
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
Vale Linting ResultsSummary: 9 suggestions found 💡 Suggestions (9)
|
|
@natasha-moore-elastic can you please review this |
nastasha-solomon
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Overall, it looks great! I left some suggestions on organization, terminology, and structure. Feel free to take what you like and discard the rest!
natasha-moore-elastic
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Left a few suggestions, but looks good otherwise!
Co-authored-by: Nastasha Solomon <[email protected]>
…s-content into 536-internal-D4C-9.3
Fixes elastic/docs-content-internal/issues/536
The Defend for Containers integration will be available in 9.3+. This PR adds several new pages to document the 9.3+ functionality.
Docs team reviewers, a couple areas to focus on, please:
@mjwolf, thanks for creating this issue and providing a bunch of helpful info. Please just review for technical accuracy.
Generative AI disclosure