[DOCS-15327] Make App and API Protection naming consistent - #39692
Merged
Conversation
Normalize product name to "App and API Protection" in prose and titles,
and wrap literal UI element names in {{< ui >}} tags using "App & API
Protection" across the application_security section. Also corrects
stale breadcrumbs in threat_protection/policies/_index.md that pointed
to a non-existent "Protection" nav segment; the Policies section is the
correct path to Detection Rules and In-App WAF.
melamos
marked this pull request as ready for review
September 2, 2026 23:56
Contributor
joepeeples
approved these changes
Sep 3, 2026
melamos
deleted the
melissa.amos/docs-15327-aap-naming-consistency-v2
branch
September 3, 2026 18:20
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
What does this PR do? What is the motivation?
Fixes DOCS-15327
Normalizes "App and API Protection" naming across
security/application_security/:{{< ui >}}tagsthreat_protection/policies/_index.mdthat referenced a non-existent "Protection" navigation segment; corrected to "Policies", matching the actual product navigation and the pattern already used ininapp_waf_rules.mdMerge readiness
For Datadog employees:
<name>/<description>convention and include the forward slash (/). If you've already created your PR with an incorrect branch name, please rename your branch and open a fresh PR./reviewto run an automated check that catches common issues before a Documentation team member reviews your PR.AI assistance
Used Claude Code to audit naming consistency across the section, apply UI-tag formatting, and cross-reference documentation to verify navigation paths before correcting breadcrumbs.
Additional notes