Editors' drafts are available on:
-
Explainer: Improving Spoken Presentation on the Web - https://w3c.github.io/pronunciation/explainer
-
Pronunciation User Scenarios - https://w3c.github.io/pronunciation/user-scenarios/
-
Pronunciation Gap Analysis and Use Cases - https://w3c.github.io/pronunciation/gap-analysis_and_use-case
-
Pronunciation Technical Approach - https://w3c.github.io/pronunciation/technical-approach/
Markdown URL for Use-cases
Pronunciation TF want to make a publication every three months if possible. Timeline: https://github.com/w3c/pronunciation/wiki/Timeline
Have node installed. Then, from this folder, run npm install from the command line (only the first time).
To proof all markdown files in this repository, node ./scripts/proof.js. To proof specific files, use "glob" syntax like node ./scripts/proof.js */draft.md or a specific files node ./scripts/proof.js contributing.md readme.md
If you introduce proper nouns, technical terms, or acronyms, you can add them to the ./scripts/DICTIONARY file which will no longer trigger the retext-spell rule.