diff --git a/Gazelle-HL7-Validator/user.md b/Gazelle-HL7-Validator/user.md
index ee85526f4913e206419ae965157b65c4ef39e74b..a037e3d66483676d576f20a60500166256ab70a8 100755
--- a/Gazelle-HL7-Validator/user.md
+++ b/Gazelle-HL7-Validator/user.md
@@ -194,7 +194,7 @@ As you can notice it on the screenshot, a button ![](./media/HL7Validator_Reques
 
 Depending on the profile format, Gazelle HL7 Validator uses HAPI or GVT as validation engine. In the case of HAPI, at validation time, message to validate is converted to a java object. Although all the message structures defined by HL7 are available in HAPI, in some cases, you will need to generate your own java class describing the message and tell the application in which java package it will find it. That is the case when IHE defines a new segment or change the structure of a message. 
 
-A project called gazelle-hl7-messagestructures available on Gazelle's forge and based on HAPI libraries is available to generate the java classes from the conformance profiles.
+A project called gazelle-hl7-messagestructures available on [Gitlab](https://gitlab.inria.fr/gazelle/library/gazelle-hl7-messagestructures) and based on HAPI libraries is available to generate the java classes from the conformance profiles.
 
 Finally, upload the XML file representing the conformance profile. As soon as the form is filled and the file is uploaded a button ![](./media/HL7Validator_Submit.png) is available.