tp_2.md: update url

tp_2.md

 # Part 2: Git remote
 
 We start by cloning an existing repository.
-`file_handle.py` is a small python script to handle the dating and the access to dated files in a format compatible with the [guide of good practices at the LBMC](http://www.ens-lyon.fr/LBMC/intranet/fichiers/bioinfo/good-practices.pdf).
+`file_handle.py` is a small python script to handle the dating and the access to dated files in a format compatible with the [guide of good practices at the LBMC](https://lbmc.gitbiopages.ens-lyon.fr/biocomp/resources/development/).
 The `git clone <url>` command retrieves the whole history of a project and setup a working area based on the last point in this history.
 
 ```sh
@@ -133,6 +133,7 @@ repository :
 `git@gitbio.ens-lyon.fr:<user_name>/git_basis.git`.
 
 with the https protocol we have:
+
 `https://gitbio.ens-lyon.fr/<user_name>/git_basis.git`
 
 > Note: repositories created on gitbio are _bare_ repository. There is no working
@@ -163,7 +164,7 @@ Then we use the following commands to push our local copy to our remote reposito
 
 ```sh
 git push -u perso --all
-git push -u perso --tags # tags need to be pushed separatly
+git push -u perso --tags # tags need to be pushed separately
 ```
 
 ## merging branches
@@ -185,6 +186,6 @@ git merge tp1
 git push perso
 ```
 
-You can see the graph of our modifications at the following address [http://gitbio.ens-lyon.fr/<user_name>/git_basis/network/master](http://gitbio.ens-lyon.fr/<user_name>/git_basis/network/master)
+You can see the graph of our modifications at the following address [http://gitbio.ens-lyon.fr/<user_name>/git_basis/-/network/master?ref_type=heads](http://gitbio.ens-lyon.fr/<user_name>/git_basis/-/network/master?ref_type=heads)
 
 [ ****Next: Git together**** ](./tp_3.md#part-3-git-together)