Clean Markdown
Unscored tasks with hints and instant feedback. Practice results never become credentials.
Short lesson
One H1, headings in order, fenced code with a language, tables with a header row, $…$ for math, ```mermaid for diagrams.
Write a short README for a CLI tool “tidy” with: a title, a one-line description, an “Install” section with a bash code fence (npm i -g tidy), a “Usage” section with a bullet list of two commands, and a link to https://tidy.example/docs.
Sign up to practiseFix and complete this document so it is lint-clean: front matter with title and date; a table (Service | Status | Owner) with three rows; a task list with two open and one done item; a footnote with its definition. Heading levels must increase by one.
Sign up to practiseWrite the team Markdown style guide: sections Headings, Lists, Code, Links, Automation; include a markdownlint config example in a json code fence and a pre-commit or CI snippet in a yaml fence.
Sign up to practise