The other place to look is in the Project ▸ Project Settings… pane, under Auto-Complete List. Here you will find previously typed character names and locations, and this is where you could correct mistakes.
If you are writing scripts, do note that to make a completion available everywhere you need to set its scope to “All”. This setting can be ignored outside of scriptwriting.
My autocorrect in Scrivener stopped working recently (wish I could recall exactly when). I’m finding that kermis’s advice above results in pretty good autocorrect on apps throughout my Mac (Word, Pages, TextEdit, Mail) – except for Scrivener.
I’m on Mac Sonoma and using Scrivener 3.3.6, MacBook Pro from the 2023 era. Any advice would be most welcome! Scrivener is my favorite way to write and work. Loss of this feature is causing me to write in Pages, then cut and paste into Scrivener…
One thing I would recommend against is upgrading to Sequoia. It’s been buggy since day one in many areas. Although, v15.1.1 (just upgraded days ago) seems, so far, to be less buggy. But I’ve not seen a MacOS version even close to this squirrely before.
I once had a 2008 PowerMac MacBook that I didn’t restart for an entire year, and only then when the new MacOS version had something in it I wanted. But iCloud and all the other newer bells and whistles apparently make uprevs hard to do comprehensively, hence, the bugginess.
Either that, or those who took over after Steve have had way too much High Fructose Corn Syrup in their lives.
I would assume this is not a Scrivener issue, other than autocorrect on Scrivener has been pretty buggy and inconsistent itself for at least the last couple years. One minute it works, and the next, it doesn’t.
I imagine they will not look at this as a bug unless a pattern develops, so everyone having this issue should chime in. Keith and Co. want us to do this, I think.
And again, if there is finger pointing, it should probably point to Apple.
This is an older thread, so some of what you may be referring to is different from whatever was going on before. One thing to bear in mind is that Scrivener’s own auto-completion system, that can suggest common words you use in the project in a dropdown, is not compatible with Apple’s “inline predictions”. If the two are running together it will cause a crash, so if you have auto-completions enabled in such a way that they pop up while typing, it will switch inline predictions off and have the system use a “bubble text” suggestion instead.
So you do need to choose which you want to use while typing. If you find inline predictions more useful overall, you can still use Scrivener’s completion, but will need to use the shortcuts in the Edit ▸ Completions submenu to request them.
That aside, I do also agree with the above comment on how Apple’s predictions are somewhat hit and miss (everywhere, to be clear).