0021856: [CEA 663] Documenting API of MEDCoupling and MEDLoader

  fix a typo

diff --git a/doc/doxygen/medcoupling.dox b/doc/doxygen/medcoupling.dox
index 167a3d3bbef24cd7ef9918c14d3d3e81acfffad0..80a67c7b6c74d8a24120aad53bf04ac92b52bf10 100644 (file)
--- 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.