Skip to content

Prefer plain language in documentation - #77

Merged
Fernando de Oliveira (fedeoliv) merged 1 commit into
mainfrom
feature/40-plain-language
Oct 20, 2026
Merged

Fernando de Oliveira (fedeoliv) merged 1 commit into
mainfrom
feature/40-plain-language

Conversation

@fedeoliv

Copy link
Copy Markdown
Contributor

Discussion Link

Link: No linked discussion. Work is tracked by #40.

Context

Uncommon or academic vocabulary makes framework-generated documentation harder for non-native English speakers to follow.

Closes #40

Solution

Add concrete plain-word examples to the shared documentation-style skill and publish the same guidance through repository instructions, distributed templates, and the quality guide. Preserve precise domain terms, API names, code identifiers, and quotations.

Validation

  • npm --prefix docs run build: passed in an isolated snapshot of this PR's committed tree (39 pages).
  • node --check docs/astro.config.mjs: passed.
  • git diff origin/main feature/40-plain-language --check: passed.
  • markdownlint --stdin --json --config .markdownlint.yaml: no new diagnostics versus the base across 6 changed Markdown/MDX files. Existing diagnostics are unchanged.
  • bash .github/plugins/devsquad/hooks/sdd-init.sh verify: integrated-stack output matches the pre-change baseline, including existing customized files and missing managed-template targets.

Checklist

  • Linked discussion exists
  • Solution has been validated

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copilot-Session: 40bf5936-fdf2-408a-afe7-dd07b66ed7da
@fedeoliv Fernando de Oliveira (fedeoliv) added the documentation Improvements or additions to documentation label Oct 16, 2026
@fedeoliv
Fernando de Oliveira (fedeoliv) merged commit e2c84da into main Oct 20, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation Improvements or additions to documentation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[documentation-style] Prefer plain wording accessible to non-native speakers

1 participant