See Reply #2.
The issue is how to handle replacement when the misspelling is also a valid word, like form when from is intended. How about letting the replacement happen, but if any change is made to the replaced text after that, let it stand?
In other words. a sequence like this: FORM is typed, it's replaced by FROM, user backspaces to the F and adds the ORM<space> and Auspex lets it stay as FROM.
User could even store the placement text as, maybe, FROM ## and delete the delimiter. That way, it would "catch your eye" when it happened so you would not type on past an accidental replacement when you didn't intend it. That way, you wouldn't be left with something like, "Fill out the from and mail it to..."
Another one like this I want to handle is 'hoe' instead of 'how', but I rarely type 'hoe', so a standard replacement should be OK for that one.
This is the only way I can figure to to this, but I don't how hard it would be to code that behavior. Maybe something like--
IF replacement and backspace, turn off replacement until the next space or punctuation occurs.