Updated some comments

AUTHORS

@@ -18,7 +18,7 @@ GDCM 2.x:
        Jean-Pierre Roux              : Developer, maintain gdcmDataExtra
          Christina Rossmanith        : Contributor (Siemens CSA)
      Christopher W Treml             : Contributor (C#)
-              Joel Spaltenstein      : Developer (MacOSX)
+              Joel Spaltenstein      : Developer (Mac OS X)
 
 
 GDCM 1.x (Developpers and contributors, alphabetical order)

CMake/FindUUID.cmake

@@ -7,18 +7,14 @@
 # also defined, but not for general use are
 #  UUID_LIBRARY, where to find the UUID library.
 #
-#  Copyright (c) 2006-2011 Mathieu Malaterre <[email protected]>
+#  Copyright (c) 2006-2016 Mathieu Malaterre <[email protected]>
 #
 #  Redistribution and use is allowed according to the terms of the New
 #  BSD license.
 #  For details see the accompanying COPYING-CMAKE-SCRIPTS file.
 #
 
-# On MacOSX we have:
-# $ nm -g /usr/lib/libSystem.dylib | grep uuid_generate
-# 000b3aeb T _uuid_generate
-# 0003e67e T _uuid_generate_random
-# 000b37a1 T _uuid_generate_time
+# On Mac OS X the uuid functions are in the System library.
 if(APPLE)
   set(UUID_LIBRARY_VAR System)
 else()

Copyright.txt

@@ -2,7 +2,7 @@
 
   Program: GDCM (Grassroots DICOM). A DICOM library
 
-Copyright (c) 2006-2011 Mathieu Malaterre
+Copyright (c) 2006-2016 Mathieu Malaterre
 Copyright (c) 1993-2005 CREATIS
 (CREATIS = Centre de Recherche et d'Applications en Traitement de l'Image)
 All rights reserved.

README.txt

@@ -12,23 +12,23 @@ Just a quick note on the build process of GDCM. GDCM build process
 make use of the cmake software(*). This allow us:
 1. To get rid of the autoconf/autotools insanity
 2. Transparently generate Unix Makefiles, NMake Makefiles,
-VS8/9/10 Solution, XCode 2.1...
-3. Automatic nightly testing, one of the most important thing
-for a robust library/software devlpt process. GDCM devpt is develop
+VS8/9/10 Solution, Xcode projects, etc.
+3. Automatic nightly testing, one of the most important things
+for a robust library/software development process. GDCM development is develop
 based on the XP definition, and to preserve backward compatibility
 make sure that code is working from one release to another: each night
-we configure, we build and we test GDCM. The result are then send to
+we configure, we build and we test GDCM. The result are then sent to
 the dashboard located at:
 
-   http://public.kitware.com/dashboard.php?name=gdcm
+  https://open.cdash.org/index.php?project=GDCM
 
-A continuous dashboard make also sure that any commit did not introduce
-any error on another plateform, a warning or broke a test...
+A continuous dashboard also makes sure that any commit did not introduce
+any error on another platform, a warning or a broken test...
 
 Therefore you should be able to use GDCM from the bleeding edge without
-knowing too much on what is going on. All you need to do is have a look
-at the GDCM dashboard, and if your plateform is 'green' then you can
-update your git copy and compile safely knowing that there are very few chances
+knowing too much about what is going on. All you need to do is have a look
+at the GDCM dashboard, and if your platform is 'green' then you can
+update your git copy and compile safely knowing that there is very little chance
 that something won't work. Cheers !