What problem does it solve? Documentation pages drift from the MariaDB house style over time — mis-cased product names, British spellings, filler words, and inconsistent heading case accumulate and require tedious manual editorial passes before a PR can be merged. ## Core Features & Use Cases - Deterministic lint fixes: Auto-corrects mechanical violations in prose such as product name casing (MaxScale, ColumnStore, MySQL, GitHub), American spelling via codespell, filler word removal, and documented spelling agglutinations. - Judgment-item reporting: Surfaces issues that need human decision — passive voice, master/slave terminology, SQL keyword casing, timeless wording, over-linking — with file:line references and proposed rewrites. - Code-region safety: Treats fenced code blocks and {% code %} blocks as opaque, never rewriting SQL, config, or output samples. - Use Case: Before opening a documentation PR, run an editorial pass on the changed pages to auto-fix mechanical style violations and get a reviewable list of tone and structure suggestions. ## Quick Start Apply the MariaDB house style to the page server/reference/sql-statements/select.md and show me the diff plus any judgment items.
