Hyphenate third-party when used as a modifier - #45508
Merged
Merged
Conversation
husamemadH
requested review from
bacharakis,
dipikabh and
wbamberg
and removed request for
a team
September 4, 2026 17:27
Contributor
wbamberg
approved these changes
Sep 4, 2026
wbamberg
left a comment
Collaborator
There was a problem hiding this comment.
👍 all looks good to me. Thank you!
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.
Description
Hyphenates "third-party" in the 52 places where it modifies a following noun.
Motivation
Used before a noun, "third-party" is a compound modifier and takes a hyphen. The repository already writes it that way about 568 times, so these are outliers.
The changes cover phrases such as "third party scripts", "third party libraries", "third party APIs", "third party cookies", "third party servers", "third party middleware" and "third party sanitization libraries", across the client-side APIs tutorials, the Express and Django guides, the WebExtensions privacy docs and several
Web/APIpages.One is link text that already disagreed with its target: "[Third party APIs]" points at a page whose own title is "Third-party APIs".
Three section headings are included — "Third party grid systems", "What are third party APIs?" and "Third party sanitization libraries". Nothing in the repository links to their anchors, so the renames are self-contained.
Noun uses are deliberately left unhyphenated, since the hyphen would be wrong there: "no third party can eavesdrop", "choose the third party that you like the best", "APIs provided by third parties", and the heading "Determining storage access by a third party".