GH-120 Documentation updates

  Standardize on 'R10k' as the proper noun in all *.mkd files.
  README.mkd:
    Updated documentation links
  doc/dynamic-environments/configuration.mkd:
    Move invalid_branches description.
    Add purgedirs description.
  doc/dynamic-environments/configuration.mkd:
    Update basedir to reference purgedirs.
  doc/dynamic-environments/git-environments.mkd:
    Clarify the details of how r10k works with git repositories.
    Update introduction to reflect environmentpath beginning with puppet v3.5.
  doc/dynamic-environments/quickstart.mkd:
    Provide alternate method to access a dynamic environment.
  doc/dynamic-environments/usage.mkd:
    Clarify how forge modules are treated.
  doc/dynamic-environments/workflow-guide.mkd:
    Completed workflow guide.
  doc/puppetfile.mkd:
    Link to description of the Control Repo
  docs/best-practices:
    Created an initial draft of a best practices guide for users to follow.
I don't think this is a hard best practice; it's one pattern but I think there are plenty of cases where you may want to keep some modules contained in the control repo.