Fix several typos #356
Open
Fix several typos #356
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR fixes several typos, and also fixes the font link and package name in
options/output/index.rst.I used CSpell to find all (or nearly all) of the typos; I found it quite useful. Should there be interest to integrate the tool into the repository, maybe this
cspell.jsonfile that I generated while browsing the repository (and modified slightly) could be useful:{ "words": ["allowbreak", "Anfang", "asciimath", "autobold", "autoloaded", "autoloading", "autoloads", "badbreak", "begingroup", "bitmapped", "bkey", "boldsymbol", "braillelabel", "btight", "chromvox", "chtml", "clearspeak", "codepen", "codesandbox", "columnalign", "columnspacing", "configmacros", "decimalsign", "dimen", "displaystyle", "dtex", "durch", "ekey", "Ende", "Ende", "eqref", "etight", "explorable", "FINDMATH", "findtags", "fira", "focusable", "fontfamily", "fullwidth", "githack", "goodbreak", "hrefs", "htmlfile", "indentalign", "indentshift", "infty", "intertext", "Jax", "jsbin", "jsdom", "jsfiddle", "linebreaking", "lineleading", "linenos", "linkedom", "litedom", "maction", "mactions", "makebox", "mathbb", "mathbf", "mathcal", "mathfrak", "mathit", "Mathitem", "mathjax", "mathmakebox", "mathmaps", "mathml", "mathrm", "mathspeak", "mathtools", "mathvariant", "Mathvariants", "merror", "mfrac", "mhchem", "mlabeledtr", "mmultiscripts", "mpadded", "mroot", "mrow", "mspace", "msqrt", "mstyle", "msup", "mtable", "mtables", "mtext", "multicolumn", "multirow", "neighbouring", "nemeth", "Newcm", "newcolumntype", "newcommand", "noerrors", "nofont", "nonumber", "noscript", "notag", "noundefined", "onclick", "operatorname", "pandoc", "parbox", "pseudoscript", "remappings", "renderaction", "renderactions", "renewcommand", "reparsed", "retypesetting", "rowalign", "rowspacing", "screenreader", "screenreaders", "srcdoc", "stix", "stylesheet", "subexpression", "Summarise", "synchronised", "tagformat", "texclass", "texhtml", "textbf", "textcolor", "textmacros", "titlesonly", "toctree", "Tralics", "unshift", "unstarred", "varphi", "webpacked", "webworker", "webworkers", "wikibook", "xlink", "yourcollege"] }It's by no means exhaustive, but it should help avoid some false positives, I hope.
Also, I've noticed that the docs use both British and American spelling conventions for different words; for example, the docs use both "synchronise" and "synchronize". I didn't consider those types of inconsistencies typos though.