[gzweb] bitbucket->github update links (#118)

Updates the links related to gzweb and instructions to use git

gzweb_development/tutorial.md

@@ -1,7 +1,7 @@
 # Overview
 
 The source code for GzWeb is located at the
-[osrf/gzweb](https://bitbucket.org/osrf/gzweb) Bitbucket repository.
+[osrf/gzweb](https://github.com/osrf/gzweb) GitHub repository.
 
 The source code is composed of two main parts: Javascript code inside `gzweb/gz3d`,
 responsible for visualization, and C++ code inside `gzweb/gzbridge`,
@@ -77,14 +77,14 @@ GzWeb communicates with `gzserver` by publishing and subscribing to Gazebo topic
 
 ## Bug reports and feature requests
 
-On GzWeb's [issue tracker](https://bitbucket.org/osrf/gzweb/issues),
+On GzWeb's [issue tracker](https://github.com/osrf/gzweb/issues),
 you're able to report bugs and ask for new features. Simply create an issue and
 categorize it accordingly.
 
 ## Pull requests
 
 If you've fixed a bug or added a feature and would like your changes to be
 integrated into GzWeb, you can make a
-[pull request](https://bitbucket.org/osrf/gzweb/pull-requests)  to the
+[pull request](https://github.com/osrf/gzweb/pulls)  to the
 repository, and the changes will be reviewed and merged.
 

gzweb_development/tutorial_1.9.md

@@ -1,6 +1,6 @@
 # Overview
 
-The source code for Gzweb is located at the [osrf/gzweb](https://bitbucket.org/osrf/gzweb) Bitbucket repository. The source code is composed of two main parts: Javascript code inside `gzweb/gz3d`, responsible for visualization, and C++ code inside `gzweb/gzbridge`, responsible for communicating with `gzserver`. 
+The source code for Gzweb is located at the [osrf/gzweb](https://github.com/osrf/gzweb) GitHub repository. The source code is composed of two main parts: Javascript code inside `gzweb/gz3d`, responsible for visualization, and C++ code inside `gzweb/gzbridge`, responsible for communicating with `gzserver`.
 
 # Javascript development
 
@@ -46,8 +46,8 @@ Gzweb communicates with `gzserver` by publishing and subscribing to Gazebo topic
 
 ## Bug reports and feature requests
 
-On Gzweb's [issue tracker](https://bitbucket.org/osrf/gzweb/issues?status=new&status=open), you're able to report bugs and ask for new features. Simply create an issue and categorize it accordingly.
+On Gzweb's [issue tracker](https://github.com/osrf/gzweb/issues), you're able to report bugs and ask for new features. Simply create an issue and categorize it accordingly.
 
 ## Pull requests
 
-If you've fixed a bug or added a feature and would like your changes to be integrated into Gzweb, you can make a [pull request](https://bitbucket.org/osrf/gzweb/pull-requests)  to the repository, and the changes will be reviewed and merged.
+If you've fixed a bug or added a feature and would like your changes to be integrated into Gzweb, you can make a [pull request](https://github.com/osrf/gzweb/pulls)  to the repository, and the changes will be reviewed and merged.

gzweb_install/tutorial_1.9.md

@@ -27,7 +27,7 @@ Gzweb is a graphical interface which communicates with gzserver. To use
  1. Next, install the dependencies from a terminal:
 
     ~~~
-    sudo apt-get install libjansson-dev nodejs npm libboost-dev imagemagick libtinyxml-dev mercurial cmake build-essential
+    sudo apt-get install libjansson-dev nodejs npm libboost-dev imagemagick libtinyxml-dev git cmake build-essential
     ~~~
 
 
@@ -36,15 +36,15 @@ Gzweb is a graphical interface which communicates with gzserver. To use
  1. Clone the repository into a directory in your home folder:
 
     ~~~
-    cd ~; hg clone https://bitbucket.org/osrf/gzweb
+    cd ~; git clone https://github.com/osrf/gzweb
     ~~~
 
  1. Enter the Gzweb repository and switch to a release branch:
 
     ~~~
     cd ~/gzweb
     # Note for Gazebo versions < 7, please use the gzweb_1.2.0 branch
-    hg up gzweb_1.3.0
+    git checkout gzweb_1.3.0
     ~~~
 
  1. The first time you build, you'll need to gather all the Gazebo models in the right directory and prepare them for the web. Before running the deploy script, you'll need to source the Gazebo setup.sh file: