I can't even explain how it came to be, lol. I was trying to find a context-sensitive Japanese translator, and that was when someone suggested Grammarly. Spoiler alert: It doesn't support Japanese.
Usage So Far
So far, I've been using Grammarly to work over all my old posts. This is the first post that actively uses it. This means that all correctness issues and clarity issues, which can be found by Grammarly, have been fixed in the older posts, while with the up-coming and future ones I'll be trying to avoid the premium alerts.The Result
Honestly, I have no idea how much of a difference Grammarly makes. So, I'll leave this to you to find out on yourself. I'll list the top five pages from an overall score, from the Flesch-reading score and the respective five worst pages from each of those categories. You can also compare this post to those.Highest Overall Score
Highest Flesch Score
Lowest Overall Score
Lowest Overall Score
Working With Grammarly
It's nice to see more machine learning solutions. However, these solutions require a lot of time to learn. There's a ton of variety in language depending on which writing-style you want to use (for Example: informal, formal, analytical, etc.). I've noticed a few issues, and these include:- Errors caused by missing terms in the dictionary.
(for example, specific technical terms)
- Correctly marked errors, but wrong suggestions.
- Errors I don't understand.
(for example, wanting a maybe when it clearly should have been a may be.)
Luckily, the more you use Grammarly, the more you will learn about working with it. Trying around a little bit, allows you to analyze and solve even the premium issues. (This is also something I'm experimenting with within this post.)
Conclusion
Since Grammarly is available for free, I can only advise people to check it out. Regardless of whether or not you're writing, blog posts, scripts, documents, or something else. I will continue to use it myself. And if I figure something out about the premium stuff, I'll make another post about that.
