My Secret Weapons (or Not So Secret): Tools That Crush Typos and Elevate My Writing

Intro

Have you been writing something in your markdown file and kept introducing spelling mistakes where they shouldn't belong? If you're tired of typos derailing your writing, this blog post about the tools I use to solve this problem is exactly what you need.

Grammarly: An Automated Writing Editor

Let's imagine: you are writing a new blog post in a markdown file. And you write as you think is best. But in reality, more often than not, if your writing is checked for grammar errors, it may not be so pretty. Plus, some of your sentences may be unnecessarily complex. This is where Grammarly comes in and saves you. It helps you to fix all grammatical errors, identify and correct misspellings, and ensure proper punctuation. It can suggest some ways to restructure your sentences. I always or almost always use Grammarly for my writing. It is amazing. And still, I have to copy all the stuff to their website to get everything fixed.

There is a Grammarly Extension in VS Code, but it requires logging in to your Grammarly account. Plus, it sends your writing to their servers. I am not feeling amazing realizing that everything I type is sent somewhere. I prefer to use their website directly, because there I know for sure that I should not write my passwords or credit card numbers.

Code Spell Checker: A Reliable Companion in Your Editor

Using Grammarly already helps a lot. And part of its functionality is to capture misspellings. Android Studio has spelling check by default, while VS Code doesn't. And I thought it would be nice to have word spelling checked right away when I am writing. This way, I would have less work to do when using Grammarly. I searched for a solution, and I found something worthwhile, the VS Code extension called Code Spell Checker. It checks for spelling mistakes and highlights them, but it also offers correction suggestions when your word is misspelled. It is said that the spellchecker uses a local word dictionary. It does not send anything outside your machine. Therefore, based on everything above, I decided to use the Code Spell Checker.

Conclusion

Here you have it! These are two tools that I use to help me write error-free, high-quality text. If you like this blog post, please share this article with someone who can find it helpful as well.

Got questions? Send an email to commitnobug@outlook.com.