Skip to content

Content refactor#4

Merged
danieltoader-canonical merged 23 commits into
canonical:mainfrom
rajannpatel:content-refactor
Jun 18, 2026
Merged

Content refactor#4
danieltoader-canonical merged 23 commits into
canonical:mainfrom
rajannpatel:content-refactor

Conversation

@rajannpatel

Copy link
Copy Markdown
Collaborator

refactor to resolve vale violations, and better conform with the Canonical writing styleguide, and Diátaxis

Heading Style:
- Change question-style headings to declarative, noun-phrase headings
  (e.g., "How CVEs are rated") to match the Landscape Gold Standard.

Index Pages:
- Replace manual link lists with `{toctree}` directives
  (`:titlesonly:`).
- Add introductory sentences before each toctree block.
- Remove `:hidden:` from toctree blocks to make the TOC visible.

Tone & Voice:
- Remove passive/weak constructions and colloquial phrases.
- Replace abbreviations (e.g., i.e., etc.) with "for example" or "such
  as".
- Shift future tense ("will", "will be", "might") to present tense.

Links:
- Replace "here", "click here", and bare URLs with descriptive link
  text.

Formatting:
- Apply inline code formatting for commands, file paths, and config
  values
  (snapd, uname -r, apt).
- Enforce consistent sentence case for headings.
- Remove trailing whitespace and trailing empty lines.

Structure:
- Add brief context sentences before lists and code blocks.
- Reorganize sections for better logical flow (explanation before
  details).
- Extract supplementary content from paragraphs into bulleted lists.
- **Em dashes (`—`)**: Replaced all three instances with `--` (per
  `Custom.Emdash` error-level rule)
- **Contractions**: Replaced `"doesn't"`, `"you're"`, `"we'll"`,
  `"you'd"`, `"don't"` with expanded forms throughout
- **"e.g."** → `"for example"` (latinism avoidance)
- **Pronouns**: Kept community-oriented "we"/"our" (acceptable per
  `vale.ini` config: `Custom.Pronouns = NO` for `[*.md]`)
- **No "livepatching" or "livepatched"**: Compliant with
  `Custom.LivepatchVerbMisuse` error rule
- **Descriptive links**: No "here" or "click here" link text anywhere
- **No links in headings**: All headings are plain text
- Zero remaining pronouns (`we`, `us`, `our`, `you`, `your`, `I`, `me`,
  `my`)
- Zero "here"/"click here" link patterns
- Zero instances of "livepatching"/"livepatched" verb misuse
- Zero em dashes
- Zero repeating character separators
- Zero boldface-with-colon patterns
- Zero headings containing links or trailing punctuation
- All "on-premise" instances corrected to "on-premises"
- All `--` bullets converted to `*`
- All YAML/MyST frontmatter, Sphinx directives, and code blocks
  preserved exactly
- Update meta descriptions for client, server, and overview pages
- Replace collapsible release sections with plain headings
- Simplify landing page toctree and remove explicit links
- Add brief descriptions for client and server components
Replace the generic project overview with a product-focused description
of
Livepatch, its audience, and its documentation layout. Restructure the
landing page to include the README directly, adopt the Diátaxis
framework,
surface release notes and contribution links, and add a comprehensive
toctree that covers all documentation sections.
- Add blank lines after MyST anchors
- Fix heading levels in patch management
- Update URLs and custom wordlist entries
Removed unused table of contents section from release notes.

Signed-off-by: Daniel Toader <daniel.toader@canonical.com>

@danieltoader-canonical danieltoader-canonical left a comment

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.

LGTM

@danieltoader-canonical danieltoader-canonical merged commit 9a392a4 into canonical:main Jun 18, 2026
7 of 9 checks passed
@rajannpatel rajannpatel deleted the content-refactor branch June 18, 2026 14:08
@rajannpatel rajannpatel restored the content-refactor branch June 18, 2026 15:05
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.

2 participants