docs: fix PagerDuty capitalization across provider documentation#6405
Open
ayoubil wants to merge 1 commit intokeephq:mainfrom
Open
docs: fix PagerDuty capitalization across provider documentation#6405ayoubil wants to merge 1 commit intokeephq:mainfrom
ayoubil wants to merge 1 commit intokeephq:mainfrom
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
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.
Fixes #5405.
The product name PagerDuty (capital D) is currently rendered as Pagerduty (lowercase d) across multiple documentation pages. This PR normalizes all user-visible documentation references to the official capitalization.
Changes (10 string replacements across 4 files)
docs/providers/overview.mdxdocs/providers/overview.mddocs/overview/servicetopology.mdxdocs/providers/documentation/pagerduty-provider.mdxWhat stays unchanged (out of scope)
PagerdutyProviderand module pathpagerduty_provider— renaming would be a breaking API change with cascading effects on user configs, imports, and serialized state.pagerduty-provider— already lowercase by convention.OAuth2 callback logic for Pagerduty, etc.) — not user-facing in the docs site, can be a separate cleanup if desired.Verification