From c6dbe37d8bdf25477318b416e1eb1527905052e1 Mon Sep 17 00:00:00 2001 From: eap Date: Thu, 4 Apr 2013 14:16:11 +0000 Subject: [PATCH] 0021856: [CEA 663] Documenting API of MEDCoupling and MEDLoader fix a typo --- doc/doxygen/medcoupling.dox | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/doxygen/medcoupling.dox b/doc/doxygen/medcoupling.dox index 167a3d3bb..80a67c7b6 100644 --- a/doc/doxygen/medcoupling.dox +++ b/doc/doxygen/medcoupling.dox @@ -43,7 +43,7 @@ For beginners in \ref medcoupling "MEDCoupling" world, it is advisable to read t \section MEDCouplingMeshes Common concept shared by all type of Meshes in MEDCoupling -A mesh has a the following properties : +A mesh has the following properties : - name - **a dimension (called mesh dimension) and only one** (it implies that \b all cells constituting @@ -750,7 +750,7 @@ You can notice that it is possible to mix cell types as long as the dimension of \subpage medcouplingpyexamplesUmeshStdBuild1 "Here is the Python implementation." -\section MEDCouplingUMeshNodalConnectivity How MEDCouplingUMesh stores its nodal connectivity. +\section MEDCouplingUMeshNodalConnectivity How MEDCouplingUMesh stores its nodal connectivity \ref ParaMEDMEM::MEDCouplingUMesh "MEDCouplingUMesh class" stores its nodal connectivity into 2 arrays. -- 2.39.2