Typos and Feedback

Today, I am very happy to have discovered typos, a command-line utility that finds (and optionally corrects) spelling mistakes in source code. The README advertises speed and a low false-positive rate. I tried it out on my projects, and it found quite a few typos. It is indeed fast, and there were no false positives! I will definitely continue to use it.

I have been working on my TTC article series today, after having not touched it for some time. While LiterateX allows me to author website content using literate source code, for which typos will be useful, the vast majority of content is written using Markdown. The spell checker in my editor allows me to discover and quickly correct most typos in Markdown, but it does not help with typos that are valid words. For example, I often type the wrong homophone even though I know which spelling is correct. Though I catch most of the mistakes when proofreading, some still slip by.

Over the past two months, a few friends have emailed me to let me know of some issues that they have spotted on the website, including typos, poorly edited sentences, and a Google link. I really appreciate all such corrections and feedback!

In an attempt to correct more errors before publishing, I am going to experiment with using more software. I installed vim-grammarous to make it easy to search for grammar mistakes within my editor. I am also going to give Grammarly a try, though I greatly prefer using the terminal over using a GUI/browser when writing.