mass-storage/mass-storage-management-practices.md

@@ -53,7 +53,7 @@ They must **never** contain:
 * For numbers 0-9, always use a minimum of two digit numbers to ensure correct numerical order (e.g. 01, 02, 03 etc.) 
 * The version number of a record should be indicated in its file name by the inclusion of ‘V’ followed by the version number (e.g. V01, V02 etc. and VD “version definitive” for 
     validated version). The status must be the last information before the extension of the file (.pdf, .doc, .jpg for example). If users are versioning scripts for analysis 
-    pipeline, they should use [git](https://about.gitlab.com/) instead. 
+    pipeline, they should use [git](https://gitlab.uliege.be/help/topics/git/index.md) and [GitLab](https://docs.gitlab.com/ee/intro/) instead. 
 
 # Data maintenance
 
@@ -77,4 +77,4 @@ should be structured in the same way as the current file tree and should be sort
 
 # User leaving the GIGA
 
-Any user leaving the GIGA must transfer (after sorting and cleaning) their home directory in the research group common area. All files must be directly identifiable without having to open all the documents. The PI must be kept informed of the files present and of their importance. After departure of the user, the user's home will be deleted and all files not transferred to the group common area will be lost.
\ No newline at end of file
+Any user leaving the GIGA must transfer (after sorting and cleaning) their home directory in the research team's common area. All files must be directly identifiable without having to open all the documents. The PI must be kept informed of the files present and of their importance. After departure of the user, the user's home will be deleted and all files not transferred to the team's common area will be lost.
\ No newline at end of file