Sometimes useful, but it doesn't always work and it breaks Tumblr for some reason.

Honestly, this is a pretty good extension for it being free. Some people complain that it can't detect it being in a sentence or apart but actually I have a fix for that, just add a space before the word and a space before the replacer word and put a space bar in front of the word and the replacer word and voila it's fixed. I also have a bug to report, when you add a space to specified words before and/or after it makes removing the correction impossible, so if you accidentally misspell the replacer word you won't be able to remove it. this review is already getting long enough so I'd rate it 5 stars for utility and price, 4 stars for convenience.

I think the average rating for this extension should be higher.

As a result of trying several similar extensions, at the moment,
With the Firefox add-on,

"You" extensions and
Developer "Marc" extension
"Only" works correctly.

For non-English speaking people, simple and intuitive add-ons are more convenient.

It would be perfect if could re-edit the word already specified.

Thank you.

Does what it says! Unfortunately, the extension is unable to compare listed words and recognise them as being individual/seperate words. For example, if I'd put in the word "fire" to be replaced with "light", and then "firefighter" to be replaced with "peacekeeper", the extension would change "firefighter" to "lightfighter" instead of changing it to "peacekeeper".

It did what it was supposed to, but somehow it broke every rich text editor and several other text input fields on various websites so I had to uninstall it. Well, I'll survive.

Simple interface makes it very easy and approachable to use. The text is a bit too large for my taste (and I'm usually one for large text). It would also be nice if the entries could be alphabetized, but it works well all the same.

UPDATE: Sadly, after a few days use, I found that not all instances of the words are replaced. It seems if the text isn't part of the main page and is instead dynamically loaded or within a frame, it's ignored. That is no optimal. Sorry.