Other browsers have been able to enable a Grammarly plugin for some time, and even though the Edge extensions pile is still fairly slim, this is a big deal for fans of the service.
The beauty of having it built into the browser is that it doesn't matter where you're writing, you'll have it at your disposal. It's something that the Windows Central team all utilize on a daily basis in other browsers, so we're very happy to see it come to Edge.
Grammarly is free to use, but also has a premium subscription that goes even deeper, even able to detect plagiarism. To get started hit the link below and grab it from the Store.
Download Grammarly from the Windows Store (opens in new tab)
Windows Central Newsletter
Get the best of Windows Central in in your inbox, every day!
Richard Devine is a Managing Editor at Windows Central with over a decade of experience. A former Project Manager and long-term tech addict, he joined Mobile Nations in 2011 and has been found on Android Central and iMore as well as Windows Central. Currently, you'll find him steering the site's coverage of all manner of PC hardware and reviews. Find him on Mastodon at mstdn.social/@richdevine
Yes! Now I can troll without grammatical errors! 😂
Great extension , stupid name :P
Because I do not want to be tracked, I will not click on the link. However, if you search the extensions store or the windows store indenpendly of the link, Grammarly cannot be found. I will wait until it is available.
Some general knowledge.
You can copy the link, strip away the prefix (before https://www.microsoft.com...) and paste it directly into your address bar...
That's fine, your decision. Those links also help support the site that you're reading now for free FYI. Someone has to pay the bills.
I posted a work around but Richard here speaks the truth. Just click it (I did) and support Windows Central. You paid you ISP, but your ISP doesn't pay every other services / websites yo visit.
Thank you for signing up to Windows Central. You will receive a verification email shortly.
There was a problem. Please refresh the page and try again.