Merge pull request #2572 from jlsuttles/move-contribue-md-to-development-md

Move CONTRIBUTE.md to DEVELOPMENT.md

2 files changed, 3 insertions, 3 deletions

diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 82282f1692..89e8e5f9a3 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -8,6 +8,6 @@ If you'd like to discuss features, ask questions, or just engage in general Bund
 
 # Helping Out
 
-If you'd like to help make Bundler better, you totally rock! Please check out the [CONTRIBUTE](https://github.com/bundler/bundler/blob/master/CONTRIBUTE.md) file for an introduction to the project, guidelines for contributing, and suggestions for things anyone can do that would be helpful.
+If you'd like to help make Bundler better, you totally rock! Please check out the [DEVELOPMENT](https://github.com/bundler/bundler/blob/master/DEVELOPMENT.md) file for an introduction to the project, guidelines for contributing, and suggestions for things anyone can do that would be helpful.
 
 Thanks for helping us make Bundler better.
diff --git a/CONTRIBUTE.md b/DEVELOPMENT.md
index f1808dfba0..443ef0b81a 100644
--- a/CONTRIBUTE.md
+++ b/DEVELOPMENT.md
@@ -20,9 +20,9 @@ Bundler doesn't use a Gemfile to list development dependencies, because when we
 
         $ rake spec
 
-  3. Set up a shell alias to run Bundler from your clone. I use a Bash alias:
+  3. Set up a shell alias to run Bundler from your clone, e.g. a Bash alias:
 
-        $ alias dbundle='ruby -I ~/src/bundler/bundler/lib ~/src/bundler/bundler/bin/bundle'
+        $ alias dbundle='ruby -I /path/to/bundler/lib /path/to/bundler/bin/bundle'
 
      With that set up, you can test changes you've made to Bundler by running `dbundle`, without interfering with the regular `bundle` command.