Skip to content

3757 docs - Replace em dashes and fix embedded cross references - #5572

Merged
ivicac merged 4 commits into
masterfrom
3757-docs-em-dashes-and-notifications
Aug 25, 2026
Merged

3757 docs - Replace em dashes and fix embedded cross references#5572
ivicac merged 4 commits into
masterfrom
3757-docs-em-dashes-and-notifications

Conversation

@ivicac

@ivicac ivicac commented Aug 25, 2026

Copy link
Copy Markdown
Collaborator

Three docs commits from 0_732, replayed onto master, plus one follow-up.

Commits

  • Replace em dashes with hyphens - a mechanical sweep across the docs tree.
  • Mark the Plan limits cross reference coming soon.
  • Point embedded failure notifications at the Notifications page - the Failures and Retries section listed the delivery channels itself ("email, Slack, or webhook"), which overstated what the released version offers: Notification.Type in v0.31.4 is EMAIL and WEBHOOK only, and the Notifications page already marks webhook as coming soon behind ff-1132. It now links to /platform/settings/notifications so the events and delivery types stay documented in the one place that maintains them. The same commit hides the unshipped automatic-retry-policy gap and records it in .agents/coming-soon-inventory.md.
  • Replace em dashes on the embedded pages added since the sweep - the original sweep ran on the branch, so it could not reach five pages master added afterwards in 28a6deb. Same substitution, 49 occurrences over 42 lines. docs/content is now free of em dashes.

One thing to know

The em-dash sweep also touched docs/content/docs/platform/automation/settings/variables.mdx, which does not exist on master - it is a 0_732-only page for custom variables. That file was dropped from the port; its em-dash fix will come along when the page lands. All 163 other files applied cleanly.

🤖 Generated with Claude Code

@ivicac
ivicac merged commit b4798da into master Aug 25, 2026
8 checks passed
@ivicac
ivicac deleted the 3757-docs-em-dashes-and-notifications branch August 25, 2026 09:22
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