docs: highlight shell-codes in CONTRIBUTING.md

Signed-off-by: Fedor Indutny <fedor@indutny.com>

1 files changed, 6 insertions, 6 deletions

diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 0694d7d641..4c3a86b00f 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -9,7 +9,7 @@ through the process.
 Fork the project [on GitHub](https://github.com/joyent/node) and check out
 your copy.
 
-```
+```sh
 $ git clone git@github.com:username/node.git
 $ cd node
 $ git remote add upstream git://github.com/joyent/node.git
@@ -48,7 +48,7 @@ does not align with that of a project maintainer.
 Okay, so you have decided on the proper branch.  Create a feature branch
 and start hacking:
 
-```
+```sh
 $ git checkout -b my-feature-branch -t origin/v0.10
 ```
 
@@ -59,7 +59,7 @@ $ git checkout -b my-feature-branch -t origin/v0.10
 
 Make sure git knows your name and email address:
 
-```
+```sh
 $ git config --global user.name "J. Random User"
 $ git config --global user.email "j.random.user@example.com"
 ```
@@ -99,7 +99,7 @@ what subsystem (or subsystems) your changes touch.
 
 Use `git rebase` (not `git merge`) to sync your work from time to time.
 
-```
+```sh
 $ git fetch upstream
 $ git rebase upstream/v0.10  # or upstream/master
 ```
@@ -111,7 +111,7 @@ Bug fixes and features should come with tests.  Add your tests in the
 test/simple/ directory.  Look at other tests to see how they should be
 structured (license boilerplate, common includes, etc.).
 
-```
+```sh
 $ make jslint test
 ```
 
@@ -134,7 +134,7 @@ node ./test/simple/test-streams2-transform.js
 
 ### PUSH
 
-```
+```sh
 $ git push origin my-feature-branch
 ```