7th step - Update doc.

[tools/medcoupling.git] / doc / user / doxygen / doxfiles / reference / medloader / intro-medloader.dox

diff --git a/doc/user/doxygen/doxfiles/reference/medloader/intro-medloader.dox b/doc/user/doxygen/doxfiles/reference/medloader/intro-medloader.dox
index e7aed81635624fe55ec8728ed20368e400d68f77..c5778533e15cab698d44a36d812415a898e06f0a 100644 (file)
--- a/doc/user/doxygen/doxfiles/reference/medloader/intro-medloader.dox
+++ b/doc/user/doxygen/doxfiles/reference/medloader/intro-medloader.dox
@@ -34,7 +34,7 @@ This approach is less close to MED file concepts, but closer to \ref medcoupling
 
 So, basic API is simpler, as shown by method MEDLoader::WriteUMesh that needs no special knowledge about MED file concepts to interact with MED files.
 
-This API is in the form of a list of public static methods in a class ParaMEDMEM::MEDLoader.
+This API is in the form of a list of public static methods in a class MEDCoupling::MEDLoader.
 
 This simplicity has a cost, the I/O are not (cannot be) optimized.