Essential session storage is required to sign in. Optional analytics remain off unless you allow them.
Find a genuinely confusing piece of real documentation (a README, a getting-started page, an error message) and rewrite it. First, write a one-paragraph AUDIENCE analysis (who reads this, their expertise, the task they're trying to do). Then rewrite for clarity: active voice, imperative mood for instructions, plain language, consistent terminology, numbered steps with expected results, and front-loaded key info. Provide a short before/after and 2-3 sentences explaining which principles each change applies and why it helps the reader.
A clear audience analysis (expertise/goal/context) that the rewrite visibly serves; fights the curse of knowledge.
Active voice + imperative instructions, plain language, consistent terms, scannable structure; the rewrite is measurably easier to act on.
Each change tied to a named principle and why it helps; before/after shown.
The rewrite stays accurate — no facts lost or distorted while simplifying.
Use this README structure to make the work reviewable.
DevPath fetches a read-only, size-capped snapshot. Submitted code is never executed.
# Rewrite a confusing doc for a real audience ## Goal Find a genuinely confusing piece of real documentation (a README, a getting-started page, an error message) and rewrite it. First, write a one-paragraph AUDIENCE analysis (who reads this, their expertise, the task they're trying to do). Then rewrite for clarity: active voice, imperative mood for instructions, plain language, consistent terminology, numbered steps with expected results, and front-loaded key info. Provide a short before/after and 2-3 sentences explaining which principles each change applies and why it helps the reader. ## Acceptance criteria - [ ] Audience focus: A clear audience analysis (expertise/goal/context) that the rewrite visibly serves; fights the curse of knowledge. - [ ] Clarity improvement: Active voice + imperative instructions, plain language, consistent terms, scannable structure; the rewrite is measurably easier to act on. - [ ] Rationale: Each change tied to a named principle and why it helps; before/after shown. - [ ] Correctness: The rewrite stays accurate — no facts lost or distorted while simplifying. ## Verification - [ ] Document installation and run commands. - [ ] Record automated checks and their exact commands. - [ ] Add representative output, screenshots, or a short demo where useful. - [ ] Confirm failure paths and known constraints. ## Decision log ### Decision title - Context: - Choice: - Alternatives considered: - Tradeoffs: ## Evidence - Link each rubric criterion to the file, test, or artifact that demonstrates it. ## Known limitations - List what is intentionally out of scope and what should be improved next.