Writers without a strong developer background struggle with Git. Part of the problem is that the basic metaphors don't apply to distributed systems. There's no "bucket" of "your" stuff. Git changes your view depending on a number of factors, and once you understand them without relying on metaphors from centralized source control systems, you'll really understand what happens when you change a file and submit it to the system. Fear will become confidence. Git provides fantastic review and commenting ability, stellar forensics, and far better conflict resolution than typical technical writing tools. But you can't take advantage of these unless you can use Git with confidence.
