No spelling and grammar checker is perfect, especially not in the context of professional sports content, but this hit the mark. I did buy a premium license. The team dictionaries feature, after some time setting them up (I use one for names, one for sports, and one for general terms), have been fantastic. Each writer can whitelist their own rules, but being able to maintain whitelists for the whole site is above and beyond any other. Definitely worth the premium license fee.

On top of that, the support has been extremely responsive, both in replies and resolutions. One issue was that it wouldn’t let me add a few names to a team dictionary. They’d just poof again and again. And one of the names was very common. I reached out and several days later it was fixed. The other issue was one in which the first link added to a post after a save had to be done twice; it would just disappear when applied forcing us to redo it. It was fine for subsequent links until the next page load. I reached out and it was fixed two days later.

I normally hate plugins in the repo with such restrictive limits on the free version. I’d ding this review a couple of stars for that, too, if the paid version and support weren’t so good. Again, context is always an issue for grammar checkers, and the NFL certainly has a lot of diversity in the names of its players, but this works better than Grammarly (free and paid versions).

The only two additional things I could ask for are 1) to be able to add words to team dictionaries from the editor, and 2) to be able to whitelist grammar rules for the team, not just individually. And since I’m not getting rid of this plugin any time soon, I look forward to seeing if those features are added.

Whether it is incompatible with Grammarly or Rank Math SEO which also has some Gutenberg sets. I am not sure.

But it is annoying waiting for the page to reload when you want to add a comma or a new heading.

A 750 word post can take all day if you are including research.

Frustrating.

I have given it 4 stars maybe 4.5 is more accurate.

When I temporarily disabled Grammarly, I can enter comments just fine.

We have both double-checked that our settings are correct, and done the usual chache cleaning etc but nothing puts things right.

I have installed the WP Proofreader plugin which works ok but surely this is a problem that shouldn’t happen? After all WP is mainly a written medium and we have all got used to relying on our typos being picked up.

Is this problem being addressed? Or does anyone know what I can to to get back to Firefox and Grammarly working reliably?

Thanks, Mary

Thanks,

What’s really strange: I noticed that something inserted weird things into the HTML code at every typo that I was going to correct. I’m using grammarly, which never gave me any problems.

Here’s an example of the “weird code”:

<g class="gr_ gr_3 gr-alert gr_gramm gr_inline_cards gr_run_anim Punctuation only-ins replaceWithoutSep" id="3" data-gr-id="3">and</g>

this is apparently about a recommended comma before the word “and”.

How does this all fit together?
Are those issues at all related?

Any suggestion would be greatly appreciated :)!

Thanks!