Add three markdown related references
Add GH help category reference on collaboration
Add GH help article reference on setting up git
Add reference to GitHub Features

Check this out, it's a revamped features page that can help you
understand some aspects of GitHub.
Add reference to the commit styles blog post

Capitalized, short (50 chars or less) summary

More detailed explanatory text, if necessary. Wrap it to about 72
characters or so. In some contexts, the first line is treated as the
subject of an email and the rest of the text as the body. The blank line
separating the summary from the body is critical (unless you omit the
body entirely); tools like rebase can get confused if you run the two
together.

Write your commit message in the present tense: "Fix bug" and not "Fixed
bug." This convention matches up with commit messages generated by
commands like git merge and git revert.

Further paragraphs comes after blank lines.

- Bullet points are okay, too

- Typically a hyphen or an asterisk is used for the bullet, preceded by
  a single space, with blank lines in between, but conventions vary here

- Use a hanging indent
Fix typo
No slides available this time
Merge pull request #7 from thessaloniki/meetup-22-notes

Meetup 22 notes