X-Git-Url: https://git.creatis.insa-lyon.fr/pubgit/?a=blobdiff_plain;f=Doc%2FWebsite%2FDeveloppers.html;h=191421e6e5a929975aa77eafef15a530d8c3cf70;hb=71f35f3ac11f6739672c446d17dc3b06c9e4280a;hp=a76b6d95c049dad37b8ed65ad3e55d24b0f9457c;hpb=5c53b1f092b809725f794a03c72d96f91eb4e3f2;p=gdcm.git

diff --git a/Doc/Website/Developpers.html b/Doc/Website/Developpers.html
index a76b6d95..191421e6 100644
--- a/Doc/Website/Developpers.html
+++ b/Doc/Website/Developpers.html
@@ -78,12 +78,12 @@ The results should appear in
 <A HREF="http://public.kitware.com/dashboard.php?name=gdcm">
         Kitware's dashboard</A>
 under the name of your machine (uname). For ease of use you can
-change the BUILDNAME variable in your <TT>CMakeCache.txt</TT> to something more
-accurate such as: GDCM-my_machine_name. The entry will then be within
-the "Experimental Builds" entry.<BR>
+change the <TT>BUILDNAME</TT> variable in your <TT>CMakeCache.txt</TT> 
+to something more accurate such as: GDCM-my_machine_name. The entry will 
+then be within the "Experimental Builds" entry.<BR>
 <b>UPDATE:</b>Since GDCM moved to its own dashboard there is no possible
 collision with other project. You can then send dashboard without having
-to properly prepend 'GDCM-' to your cmake BUILDNAME variable. But the 
+to properly prepend 'GDCM-' to your cmake <TT>BUILDNAME</TT> variable. But the 
 Win32, mingw, gcc, SunOS is still very important...