Update some links and add example output to troubleshooting doc

TROUBLESHOOTING.md

@@ -94,7 +94,7 @@ Please make sure the variable points to `C:\WINDOWS\System32\cmd.exe`
 Gather some basic diagnostic information.
 
 ```sh
-npm -v              
+npm -v
 node -v
 node -p process.versions
 node -p process.platform
@@ -118,6 +118,10 @@ Note which version was installed by running
 ```sh
 npm ls node-sass
 ```
+```sh
+y@1.0.0 /tmp
+└── node-sass@3.8.0
+```
 
 If node-sass could not be installed successfully, please publish your `npm.log`
 and `npm.err` files for analysis.
@@ -128,8 +132,11 @@ to compare your log against.
 If node-sass install successfully lets gather some basic installation infomation.
 
 ```sh
-.\node_modules\.bin\node-sass --version
-node -p "console.log(require('node-sass').info)"
+node -p "require('node-sass').info"
+```
+```sh
+node-sass       3.8.0   (Wrapper)       [JavaScript]
+libsass         3.3.6   (Sass Compiler) [C/C++]
 ```
 
 If the node-sass installation process produced an error, open the vendor folder.
@@ -138,15 +145,18 @@ If the node-sass installation process produced an error, open the vendor folder.
 cd node_modules\node-sass\vendor
 ```
 
-Then, using the version number we gather at the beginning, go to https://github.com/sass/node-sass-binaries/tree/v<your-version>.
+Then, using the version number we gather at the beginning, go to https://github.com/sass/node-sass/releases/tag/v<your-version>.
 
 There you should see a folder with same name as the one in the `vendor` folder. Download the `binding.node` file from that folder and replace your own with it.
 
 Test if that worked by gathering some basic installation infomation.
 
 ```sh
-.\node_modules\.bin\node-sass --version
-node -p "console.log(require('node-sass').info)"
+node -p "require('node-sass').info"
+```
+```sh
+node-sass       3.8.0   (Wrapper)       [JavaScript]
+libsass         3.3.6   (Sass Compiler) [C/C++]
 ```
 
 If this still produces an error please open an issue with the output from these steps.
@@ -164,7 +174,7 @@ cd ~/temp1
 Gather some basic diagnostic information.
 
 ```sh
-npm -v              
+npm -v
 node -v
 node -p process.versions
 node -p process.platform
@@ -182,12 +192,19 @@ Note which version was installed by running
 ```sh
 npm ls node-sass
 ```
+```sh
+y@1.0.0 /tmp
+└── node-sass@3.8.0
+```
 
 If node-sass install successfully lets gather some basic installation infomation.
 
 ```sh
-./node_modules/.bin/node-sass --version
-node -p "console.log(require('node-sass').info)"
+node -p "require('node-sass').info"
+```
+```sh
+node-sass       3.8.0   (Wrapper)       [JavaScript]
+libsass         3.3.6   (Sass Compiler) [C/C++]
 ```
 
 If the node-sass installation process produced an error, open the vendor folder.
@@ -196,15 +213,18 @@ If the node-sass installation process produced an error, open the vendor folder.
 cd node_modules/node-sass/vendor
 ```
 
-Then, using the version number we gather at the beginning, go to https://github.com/sass/node-sass-binaries/tree/v<your-version>.
+Then, using the version number we gather at the beginning, go to https://github.com/sass/node-sass/releases/tag/v<your-version>.
 
 There you should see a folder with same name as the one in the `vendor` folder. Download the `binding.node` file from that folder and replace your own with it.
 
 Test if that worked by gathering some basic installation infomation.
 
 ```sh
-.\node_modules\.bin\node-sass --version
-node -p "console.log(require('node-sass').info)"
+node -p "require('node-sass').info"
+```
+```sh
+node-sass       3.8.0   (Wrapper)       [JavaScript]
+libsass         3.3.6   (Sass Compiler) [C/C++]
 ```
 
 If this still produces an error please open an issue with the output from these steps.