Skip to content

fix(vale): sentence-case recurring headings; more Temporal.Headings exceptions - #4984

Draft
Duncanma wants to merge 2 commits into
mainfrom
vale-headings-content-fixes
Draft

fix(vale): sentence-case recurring headings; more Temporal.Headings exceptions#4984
Duncanma wants to merge 2 commits into
mainfrom
vale-headings-content-fixes

Conversation

@Duncanma

@Duncanma Duncanma commented Jul 28, 2026

Copy link
Copy Markdown
Contributor

Summary

Follow-up to #4983. Two related changes, bundled since they serve the same goal (reducing Temporal.Headings false positives / noise):

  • More exceptions: while combing through remaining flags to find content worth fixing, found more proper nouns that were tripping the rule on already-correctly-cased headings: brand/product names (Amazon, Google, Microsoft, S3), Temporal Cloud feature names (Ops, Audit, Log, Saved, View, Actions, Non-Deterministic — all verified as consistently capitalized in prose, e.g. "Cloud Ops API", "Audit Log", "Saved View"), and the Hello/World programming idiom used across every SDK's setup guide.
  • Content fixes: sentence-cased the recurring title-case headings duplicated across the per-SDK-language doc sets — Next Steps, Verify Success, Best Practices:, Considerations for Workflows with Message Handlers, the encyclopedia/event-history/* "How Workflow code maps to commands / How Workflow commands map to events / How History replay provides Durable Execution" trio, and a handful of one-offs (Rate Limiting, Query Parameters, Namespace Versions, Create a Project). Also formatted `GetVersion` as inline code in a heading instead of leaving it as bare prose text.
  • Matching table-of-contents link text was updated alongside each renamed heading; anchor IDs are untouched (Docusaurus slugs are case-insensitive, so links don't break).

Left the long tail of one-off headings (single-occurrence title-case violations, third-party proper nouns like PKCS8/Route 53/JUnit) out of scope for this pass.

Test plan

  • vale --config=.vale-ci.ini docs/ — live Temporal.Headings suggestions drop from 446 to 340, 0 errors
  • vale --config=.vale-ci.ini vale/test/headings-good.md / headings-bad.md — new exceptions covered, no regressions
  • Compiled every changed .mdx file with @mdx-js/mdx directly — all pass (2 pre-existing unrelated compile failures confirmed present on main before this change too)
  • Grepped for cross-file links to the renamed anchors — none found; only same-file TOC links, which were updated in place

┆Attachments: EDU-6837 fix(vale): sentence-case recurring headings; more Temporal.Headings exceptions

…er-noun exceptions

Content fixes for the recurring boilerplate headings duplicated across
the per-SDK-language guide sets (Next Steps, Verify Success, Best
Practices:, Considerations for Workflows with Message Handlers, the
event-history "How Workflow ... " trio, etc.) plus a few one-off
sentence-case fixes (Rate Limiting, Query Parameters, Namespace
Versions, Create a Project) and formatting an inline code identifier
in a heading (`GetVersion`) instead of leaving it as bare text.

Also extends the Temporal.Headings exceptions with proper nouns found
while auditing these fixes: brand/product names (Amazon, Google,
Microsoft, S3), Temporal Cloud feature names (Ops, Audit, Log, Saved,
View, Actions, Non-Deterministic), and the conventional "Hello World"
programming idiom — all confirmed as consistently-capitalized terms
used throughout the docs' prose.

Live Temporal.Headings suggestions: 446 -> 340.
@Duncanma
Duncanma requested a review from a team as a code owner July 28, 2026 21:42
@vercel

vercel Bot commented Jul 28, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
temporal-documentation Ready Ready Preview, Comment Jul 28, 2026 11:00pm

Request Review

### Best Practices:
### Best practices:

#### 1. Use Private Connectivity

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

📝 [vale] reported by reviewdog 🐶
[Temporal.Headings] '1. Use Private Connectivity' should use sentence-style capitalization.

@@ -95,7 +95,7 @@ A [Metric Family](https://github.com/prometheus/OpenMetrics/blob/main/specificat

## Client Considerations

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

📝 [vale] reported by reviewdog 🐶
[Temporal.Headings] 'Client Considerations' should use sentence-style capitalization.

@github-actions

Copy link
Copy Markdown
Contributor

📖 Docs PR preview links

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant