proofread-markdown

From README

Proofreading Markdown Overview Help us transform technical text into clear, concise, and machine-readable Markdown. We follow the Google Developer Documentation Style Guide. Workflow Check line length [ ] Wrap lines semantically and keep them generally under 80 characters using scripts/wraplines.dart [ ] Never touch the front matter. Do not modify the content between the first two --- lines at the top of the file. [ ] Verify that the file was wrapped correctly, preserving headings and code blocks Fix voice and tone [ ] Use active voice. [ ] Use present tense. [ ] Use second person ("you"). No "we" or "I". Check word choice [ ] Replace forbidden terms: "e.g.", "i.e.", "etc.", "should", "would", "could", "via", "may". [ ] Use Oxford comma and American spelling. Check style of headings [ ] Use Sentence case for headings. If you change a heading, add an id after the heading like this: "## Configure the project {: #project-configuration }" [ ] Put a blank line after all headings.