edit defend advanced options wording #2157
Open
+133
−123
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
🔍 Preview links for changed docs |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This edits the Defend advanced option wording with the following primary goals:
Originally we'd agreed to completely remove the italics portion on this page and make sure the Kibana tool tips were "short" with an expectation users turn to this more detailed documentation when needed. I tried, but was only as successful as what I'm proposing to merge in this PR (usually shorten the italics tool tip and always still show it on elastic.co).
Thoughts @natasha-moore-elastic @gabriellandau @roxana-gheorghe @nfritts @joe-desimone