MEDMEM suppression

diff --git a/doc/doxygen/interpkernel.dox b/doc/doxygen/interpkernel.dox
index ba00404f0613c551c62914ef84622bbd9f457127..ccb1c3a78a848bdb1fb30c57e019a6f94fc36b45 100644 (file)
--- a/doc/doxygen/interpkernel.dox
+++ b/doc/doxygen/interpkernel.dox
@@ -60,7 +60,7 @@ rules :
   -# \code void releaseTempArrays() \endcode
 - Formats of arrays
   - the array returned by \c getCoordinatesPtr must be a \b full \b interlace array.
-  - the arrays returned by \c getConnectivityPtr and \c getConnectivityIndexPtr must be with the same principle as it is \ref MEDCouplingUMeshNodalConnectivity "MEDCouplingUMesh does". Of course the numbering format may change according to \a My_numPol policy.
+  - the arrays returned by \c getConnectivityPtr and \c getConnectivityIndexPtr must be with the same principle as it is \ref MEDCouplingUMeshNodalConnectivity "implemented in MEDCouplingUMesh". Of course the numbering format may change according to \a My_numPol policy.
 
 Note that the array format for connectivity is kept close to MED. It is
 close to VTK format too but slightly different. So it may require for the VTK side a copy
@@ -82,4 +82,4 @@ As already said, the matrix returned by interpolator is typically a sparse matri
 
 Note that \c std::vector\c < \c std::map<int,double> > is a candidate for \c MatrixType.
 
-*/
\ No newline at end of file
+*/