Fix remaining IaC overcapitalization findings (issue #20958, piece A) - #21238
Merged
Conversation
) Lowercase mid-sentence occurrences of "infrastructure as code" across 15 files (blog posts, case studies, what-is pages, and one whitepaper) that the Vale Pulumi.Overcapitalization rule flags as generic-concept overcapitalization. This closes out the remaining piece A findings from issue #20958 that PRs #20983 and #21125 did not yet cover. Verified with `vale --output=JSON content/` (rule Pulumi.Overcapitalization): 0 findings remain across the 15 touched files, and none were introduced elsewhere. Markdown lint passes clean on all 15 files.
github-actions
Bot
added
review:triaging
github-actions
Bot
added
the
review:in-progress
Collaborator
Contributor
Pre-merge Review — Last updated 2026-09-01T14:44:41ZTip Summary: This PR finishes the "Infrastructure as Code" → "infrastructure as code" downcasing campaign from issue #20958, touching 15 existing blog posts, case studies, what-is pages, and one whitepaper — capitalization-only, no substantive rewrites. The wrongness that matters here is narrow: a downcase applied inside a quoted proper title misquotes a real published asset, and a downcase applied to only some occurrences in a sentence leaves the page visibly inconsistent. Commit Review confidence:
Investigation log
✏️ 3 one-click style suggestions are posted inline — apply them from the Files changed tab, individually or with Add suggestion to batch. 🔍 Verification trail92 claims extracted · 56 verified · 4 unverifiable · 2 contradicted · 1 framing-drift · 3 detector findings
Important Please don't hide, resolve, or delete this comment! It breaks things! 📖 How pre-merge review works — the full lifecycle, short-circuits, and escape hatches. |
Contributor
📊 Editorial balanceSection depth, mention distribution, recommendation steering
🚨 Outstanding in this PRNo outstanding findings.
|
github-actions
Bot
added
review:outstanding-issues
…un mention
Pre-merge review on this PR flagged two blocking mismatches introduced by the
capitalization downcase: the announcing-speaker-lineup-pulumiup-2023 post quotes
a conference talk title verbatim ('Using Monorepos to Level-up your
Infrastructure as Code and Software Delivery'), and the platform-engineering-pillars-1
post quotes a published ebook title ('Platform Engineering: Recommended Practices
for Infrastructure as Code'). Both are proper names of external assets, not prose
about the practice, so the downcasing rule from issue #20958 doesn't reach them;
restored both to their published capitalization.
Also downcased one remaining common-noun mention the review flagged as
low-confidence: 'free and open source Infrastructure as Code SDK' in the
walkthrough-of-adopting-infrastructure-as-code post, which modifies 'SDK' as an
ordinary noun phrase rather than a product name, consistent with the rest of
that sentence.
Contributor
Author
|
Pushed fixes for both blocking findings:
Left the other two low-confidence items open for a maintainer call rather than fixing unilaterally:
|
github-actions
Bot
added
review:stale
Contributor
Author
|
@claude #update-review |
github-actions
Bot
added
review:in-progress
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
🧹 Optional style suggestions from the pre-merge review — apply or dismiss; none of them block.
Generated by Claude Code
Contributor
|
🤖 Review updated on @workprentice[bot]'s request. |
github-actions
Bot
added
review:no-blockers
cnunciato
approved these changes
Sep 4, 2026
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
3 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.
Part of #20958 ("IaC overcapitalization" — the "piece A" scope: lowercasing generic mid-sentence uses of "Infrastructure as Code"). PRs #20983 and #21125 already closed most of this out; this PR clears the remaining findings.
What this fixes
Vale's
Pulumi.Overcapitalizationrule flags mid-sentence occurrences of "Infrastructure as Code" that aren't a proper noun and aren't at the start of a sentence or heading. I ranvale --output=JSON content/and found 31 remaining findings across 15 files not yet touched by prior PRs:content/blog/:announcing-speaker-lineup-pulumiup-2023,aws-cdk-vs-pulumi-why-sst-switched,infrastructure-as-code-tools,platform-engineering-pillars-1,walkthrough-of-adopting-infrastructure-as-codecontent/case-studies/:4ir,atlassian,greenpark-sports,materialize,menta-network,snowflakecontent/what-is/:infrastructure-as-code-for-devops,python-for-devops,what-is-devops-automationcontent/whitepapers/:enterprise-innovation-through-cloud-engineering(not previously tracked in any comment on Vale rule: flag mid-sentence "Infrastructure as Code" overcapitalization (IaC sweep) #20958)While fixing these, I found and fixed a few additional same-class occurrences in
walkthrough-of-adopting-infrastructure-as-code/index.mdthat Vale's regex didn't happen to flag but are the identical style violation, for a total of 33 individual word-case changes across the 15 files.All quoted attributions (customer/founder quotes in the case studies) were left untouched in substance — only the generic "Infrastructure as Code" → "infrastructure as code" casing changed, never the surrounding wording, and I verified none of the fixes land inside a direct quotation's own capitalization choice.
Verification
vale --output=JSON content/on all 15 touched files: 0Pulumi.Overcapitalizationfindings remain (down from 31).node ./scripts/lint/lint-markdown.json all 15 files: 0 errors.git diff --stat: only the 15 intended files, 30 insertions / 30 deletions (one-line-per-fix diffs), no incidental changes.What's explicitly out of scope here (see #20958 for the full discussion)
Piece B (widening the rule's
scopefromparagraphto also coverheading.h2-h6andlist) is not attempted in this PR. Widening surfaces a real false-positive class that would need its own carve-out first: self-referential topic titles like "## What is Infrastructure as Code?" and the "[What is Infrastructure as Code (IaC)?]" related-content link that recurs acrosscontent/what-is/*.md— lowercasing those would read as broken. I've left a comment on #20958 with the concrete numbers (53 raw new IaC-token hits if scope widens, versus a much tamer 11 heading occurrences / 0 list matches for the "Stack" token) so whoever picks up piece B has the groundwork done.🧠 This PR was created by workprentice.