Starting on branching.

acrl-git.md

@@ -18,7 +18,9 @@ A lot of version control systems work like Dropbox. [Subversion](http://subversi
 
 If you're a serious Dropbox wonk, you've probably noticed that Dropbox keeps the last ten or so saves of each file -- handy if you nuke something and need to go back to an earlier revision. But if you're a compulsive saver, you'll quickly run out of those last ten revisions.  Any modern version control system will keep *every single revision* ever made to a project, so going back to any point in development is easy. You can see the revision history of this very post [right here](https://github.com/jbfink/acrl-git/commits/master).
 
-A decentralized version control system, like [git](http://git-scm.com), [Bazaar](http://bazaar.canonical.com), or [Mercurial](http://mercurial.selenic.com), doesn't need a central repository. A decentralized version control system can be run entirely locally, without sharing files at all, or it can be run in a manner similar to a centralized one. This [workflow flexibility](http://git-scm.com/book/en/Distributed-Git-Distributed-Workflows) 
+Decentralized version control systems are somewhat of a more recent development than centralized. A decentralized version control system, like [git](http://git-scm.com), [Bazaar](http://bazaar.canonical.com), or [Mercurial](http://mercurial.selenic.com), doesn't need a central repository. A decentralized version control system can be run entirely locally, without sharing files at all, or it can be run in a manner similar to a centralized one. This [workflow flexibility](http://git-scm.com/book/en/Distributed-Git-Distributed-Workflows) can be liberating, but it can also take some time to work out what workflow works well for a team.
+
+Another aspect of modern version control that is used most effectively by the decentralized version control systems is *branching*.