fix(CONTRIBUTING): Update contribution guidelines

Author: bmuenzenmeyer

packages/uikit-default/.github/CONTRIBUTING.md

@@ -1,5 +1,5 @@
-# Contributing to Pattern Lab Shared Front End
-If you'd like to contribute to the shared frontend for Pattern Lab Node and PHP, please do so! There is always a lot of ground to cover and something for your wheelhouse.
+# Contributing to the Default Pattern Lab Front End
+If you'd like to contribute to the default frontend for Pattern Lab Node, please do so! There is always a lot of ground to cover and something for your wheelhouse.
 
 ## Developing Locally
 
@@ -12,16 +12,7 @@ The best way to make changes to this repo and test them is through your existing
 * `npm install`
 * `npm link`
 * `cd /path/to/your/edition`
-* `npm link @pattern-lab/styleguidekit-assets-default`
-
-### PHP 
-
-Once you've installed the requirements do the following to set-up for development:
-
-1. `cd /path/to/dev-edition/packages/pattern-lab/styleguidekit-assets-default`
-2. `git config branch.dev.remote origin`
-3. `npm install`
-4. `bower install`
+* `npm link @pattern-lab/uikit-default`
 
 ## Making Changes
 
@@ -38,7 +29,7 @@ At this point changes to the static assets should compile to the correct locatio
 ## Guidelines
 
 * Pattern Lab uses a standard [git flow model](http://nvie.com/posts/a-successful-git-branching-model/) unless otherwise noted in a repository. The `develop` branch is not considered stable. Tags and releases are cut from the `master` branch
-* _USUALLY_ submit pull requests against the [develop branch](https://github.com/pattern-lab/styleguidekit-assets-default/tree/dev). If you have a major feature to stabilize over time, open an issue about making a dedicated `feature-branch` off of `develop`
+* _USUALLY_ submit pull requests against the [develop branch](https://github.com/pattern-lab/uikit-default/tree/dev). If you have a major feature to stabilize over time, open an issue about making a dedicated `feature-branch` off of `develop`
 * Please keep your pull requests concise and limited to **ONE** substantive change at a time. This makes reviewing and testing so much easier.
 * Commits should reference the issue you are adressing.
 * Large enhancements should begin with opening an issue. This will result in a more systematic way for us to review your contribution and determine if a [specifcation discussion](https://github.com/pattern-lab/the-spec/issues) needs to occur.