dwyl jargon buster

An issue for discussing repo / Github terminology and how to explain them in the most _intuitive_ way.

I like the explanations given in [this article](http://readwrite.com/2013/09/30/understanding-github-a-journey-for-beginners-part-1) for the following:

**Repository**
_A directory or storage space where your projects can live. Sometimes GitHub users shorten this to “repo.” It can be local to a folder on your computer, or it can be a storage space on GitHub or another online host. You can keep code files, text files, image files, you name it, inside a repository._

**Commit**
_This is the command that gives Git its power. When you commit, you are taking a “snapshot” of your repository at that point in time, giving you a checkpoint to which you can reevaluate or restore your project to any previous state._

**Branch**
_How do multiple people work on a project at the same time without Git getting them confused? Usually, they “branch off” of the main project with their own versions full of changes they themselves have made. After they’re done, it’s time to “merge” that branch back with the “master,” the main directory of the project._

I also like the way [this guide](https://education.github.com/guide) has concisely defined an..

**Organisation**
_A GitHub organization represents a group of people working together, like a company or an open-source project._

@iteles I like the way organisation is explained above, rather than saying that an organisation is similar to a 'folder' to keep projects in, as this might seem too close to a definition of a repo. Non-technical people might think _"Well, what's the difference then?"_