updated copyright message

[modules/med.git] / idl / MEDDataManager.idl

diff --git a/idl/MEDDataManager.idl b/idl/MEDDataManager.idl
index 8fa024d3436b86845b82408493ca3bcd7b1c13a6..ef4068178b9bd00569802adff18960d5e4ba3c13 100644 (file)
--- a/idl/MEDDataManager.idl
+++ b/idl/MEDDataManager.idl
@@ -1,4 +1,4 @@
-// Copyright (C) 2007-2020  CEA/DEN, EDF R&D, OPEN CASCADE
+// Copyright (C) 2007-2023  CEA, EDF, OPEN CASCADE
 //
 // Copyright (C) 2003-2007  OPEN CASCADE, EADS/CCR, LIP6, CEA/DEN,
 // CEDRAT, EDF R&D, LEG, PRINCIPIA R&D, BUREAU VERITAS
@@ -45,17 +45,17 @@ module MEDCALC
   typedef sequence<MeshHandler> MeshHandlerList;
 
   /**
-   * The Fieldseries is a virtal object that does not exist in the MED
+   * The Fieldseries is a virtual object that does not exist in the MED
    * data model (at least in the MEDCoupling data model). It is just a
-   * point that aggregate a list of fields that relie on the same mesh
+   * point that aggregates a list of fields that rely on the same mesh
    * with the same type (the fields in a timeseries differ by their
    * time step).
    *
    * Then you could have a field with no fieldseries associated but
    * directly associated to a mesh. That is typically the case of
-   * fields created by MED operations: if you operate tow fields
+   * fields created by MED operations: if you operate two fields
    * coming from 2 different timeseries (and relying on the same
-   * mesh), you obtain a field that can not be associate to the
+   * mesh), you obtain a field that can not be associated to the
    * original timeseries. Then this new created field must be directly
    * associated to its underlying mesh (as defined in the MEDCoupling
    * data model).