Using older versions of Outlook for Mac in business environments
Everyone should send Microsoft feedback to let them know you want this bug fixed.
The more reports they get the higher it gets on the list to be fixed.
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Original Title:"Contractions of Verb + Not"
The spell check in Outlook 2011 keeps underlining any verb that is contracted with "not." For example, "can't", "isn't", and so on are all flagged as misspellings. How can I stop this?
Using older versions of Outlook for Mac in business environments
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
Everyone should send Microsoft feedback to let them know you want this bug fixed.
The more reports they get the higher it gets on the list to be fixed.
If you have upgraded to Mountain Lion see this post:
I figured this out.
Go to Outlook >>> Preferences >>> Autocorrect.
Click on the + in the lower left corner.
In the left box type in the correctly spelled contraction.
Tab to the right box and type in the correctly spelled contraction again.
i.e. shouldn't and shouldn't (note, both are spelled correctly)
Then tab again to save.
It appears that now the autocorrect will replace what it thinks is the incorrectly spelled contraction with the correctly spelled contraction (even though they are the same) and the red highlight will disappear automatically.
Do this for all the contractions you regularly use.
Hope this helps.
Try testing in a new Identity and see if that helps. It's definitely working correctly for me and other testers. You don't even need to do setup accounts etc to test this in a new Identity. If it works, see this article
One more thing to check if you are on Lion. Have you upgraded to 10.7.4?
OS X Lion Update 10.7.4 (Client Combo) 1.4 GB
Yes, installed the upgrade upon release. There was no change in behavior of the reported issue.