On Tue, Apr 29, 2014 at 04:19:16PM -0700, Matt Davis wrote:
> > +* You can change a project radically and save it, but always have the ability to switch back to your stable copy. This can help you work with the project as you need solo.
> > +* Other people or collaborators can modify the project without affecting the main project. This serves as an advantage for the group.
> 
> I'd simplify this line to "Collaborators can modify the project the stable copy or each other."

The suggested simplification does not parse for me.  I'd use something
wordier like:

  Branches allow you to develop a complicated feature using a series
  of commits, instead of lumping all the changes together in a single,
  monster commit.  By collecting the related commits in a branch, it's
  easier to discuss them with your collaborator and incorporate their
  feedback without polluting the master branch.  You can work on
  several orthogonal branches in parallel this way, which is useful if
  one of your ideas takes a while to mature.  It's also easy to
  abandon a branch, if it turn out to not be productive, since there's
  nothing in master to revert.

but to each their own ;).