[doc] Rebrand privatelink traffic filters to private connectivity #922
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.
part of https://github.com/elastic/platform-docs-team/issues/682
prerequisites:
I don't have permission to add labels to this PR
What does this PR do?
Rebrands privatelink traffic filters to private connectivity based on a larger change to Elastic Cloud network security
Why is it important?
Network security terminology and docs are changing, making the existing doc link invalid
Checklist
- [ ] My code follows the style guidelines of this project- [ ] I have commented my code, particularly in hard-to-understand areas- [ ] I have made corresponding change to the default configuration files- [ ] I have added tests that prove my fix is effective or that my feature works- [ ] I have added an entry inCHANGELOG.md
and updatedshare/version.py
, if my change requires a new release.Author's Checklist
How to test this PR locally
link coming after preview CI runs
Related issues
part of https://github.com/elastic/platform-docs-team/issues/682
prerequisites: