One for parameter values (which will catch view names)
One for text notes
One for family names
One for the keynote file
This approach has a few benefits:
If you only need to do this in one project you can quickly catch most items and the team can be done with it while you work on the next step.
If you manage to solve one part but not the others you can keep at the unsolved ones after the fact.
When you get them all working you can then work on combining them after doing significant QA on each of the individual components.
I recommend looking closely at the method you use for replacing the acronym as identifying acronyms in text is easy to produce false positives (i.e. replacing ext with exterior would result in text in my sentence above becoming texterior which is unlikely what you want).
Thank you, jacob.small, I suspected it would be multiple scripts. I appreciate your thoughtful response, and will continue to research methods to accomplish my goal. It’s unfortunate that once this is done, the script(s) will likely no longer be needed. I will post them on this thread in case they would be helpful for someone else, though.
For context, I am going through a project and updating initials into a company acronym. Everything has a prefix to update - line types, styles, patterns, families, project browser view titles, view names, and more. Once this is done, a template will be made.