"Fixing" spelling mistakes in overviews just isn't going to happen, and you know that. In the online database, that is - you are, of course, perfectly welcome to "fix" all you want in your local database. You know that too. But online, it'll never happen, and if you think that this constant derailing of unrelated threads will help, you're sorely mistaken.

Might I offer a humble suggestion. Now that DVD Profiler has added custom fields officially to the database, there is a way to carry even what used to be "local" data in the database as custom fields along with official data, available in your personal online, searchable, filterable and available to HTML sections. That means you could continue to contribute changes to the official profiles, including changes to fields for which you maintain an alternate "local" version, with no locking required, as custom fields are automatically excluded from being contributed. Custom fields are also backed up and restored in the normal way, and can also be restored from your online. There are a few restrictions when using a remote database, but I suspect that these will be removed over time if users begin to request it.

There is limited support now - a few plugins: my "SideCar" and DJ Doena's "Alternate ..." series. I could envision an "Alternate Overview" plugin. Cool thing is, you could start even with the existing plugins, forever preserve your local data, and be able to bulk copy and paste into any future new fields of DVD Profiler. The custom fields participate also in XML export and profile export.

Just a reminder ... both Ken and plugin authors are continually trying to address important requirements, but as you might guess, some of them are more complex to fit into a many-years existing technology base.

So, maybe give custom fields a try? It was a major effort on Ken's part to build this capability and we had a long testing period over the 2014 holidays for the first plugins to use it.