The problem with git for general text work is that it is distributed VCS... even software engineers struggle from time to time with the concept that changes can

The problem with git for general text work is that it is distributed VCS... even software engineers struggle from time to time with the concept that changes can happen in isolation on separate copies then merge back to the "master copy" in a conflicting way that must be solved. If you were to pick a VCS for non-technical users (e.g. a group who historically just produce word documents), it would probably have to be a non-distributed system like SVN that allows for file locking. Conceptually, central VCS and file locking etc is much easier to understand for non-technical people than distributed VCS and merges in my experience; it's no surprise to me Word offers SVN style locking too for collaboration, which of course is anathema to the way git operates. Git can for sure solve this problem, I just think its too complex to use for most Word Processor users, especially conflict resolution, and is generally ideologically opposed to providing features to lock shared documents down.