escaped characters should be recognized

[luzpaz]

The term wasn\'t is being recognized as wasn by codespell. There should be logic to distinguish this better.

[peternewman]

#201

This currently causes false positives due to not matching wasn't, but I guess that would be the case even without the PR above, it would just be suggesting was instead of wasn't.

[arm-in]

+1

"\nTo terminate ..."
leads to
"nto->not, disabled due to \n"

[yarikoptic]

IMHO the original issue of escaped \' (where result would constitute just removal of \) is different from \n problem (where result should constitute of completely removing \n and indicating word boundary there), the oldest instance of which is mentioned in the oldest still open issue #17 where I just provided an extra example.