Add documentation fallbacks

[modules/med.git] / README

diff --git a/README b/README
index 975c663963b1e5ee02feafb493013739d21f6ae3..b61c1cfbf17a751e856b4152760dbdb799343e04 100644 (file)
--- a/README
+++ b/README
@@ -1,4 +1,5 @@
-This is the Med Memory package V3.2.0
+Documentation for the MEDMEM library and related tools is given in
+$(prefix)/doc/user/html/index.html
 
 I : Major evolution of the Med Memory package between V2.2.x and V3.2.x :
 =========================================================================
@@ -30,7 +31,7 @@ should be done for the get/set field classes methods:
   parameter;
 - the getValueI (resp. setValueI) should be replaced by getRow(int )
   (resp. setRow(int ,T*) if the field is in full interlacing mode (using the
-  method getInterlacingType() of the classe FIELD_). If the field is stored in
+  method getInterlacingType() of the class FIELD_). If the field is stored in
   no interlacing mode getValueIJ (resp. setValueIJ) should be replaced by
   getColumn(int ) (resp. setColumn(int ,T*)).
 
@@ -72,7 +73,7 @@ In order to avoid most of the problem the user or the installer should first
 check the HDF5HOME and the MED2HOME environment variables. This version of
 Med Memory with Med File V2.2.2, V2.2.3, as well as V2.3.0 but with the
 version of HDF5 V1.6.3. In the installation of Med File you should take care
-of the $HDF5HOME environement variable. This warning is especially intended
+of the $HDF5HOME environment variable. This warning is especially intended
 to the user of The Med Memory in stand alone (without the SALOME KERNEL
 component).
 
@@ -97,7 +98,7 @@ Memory, the installer may run:
 - test_MEDMEM_MeshingPoly
 
 To check the upper layer (CORBA, Client), the installer may run in the SALOME
-Python consol:
+Python console:
 
  - Med_Gen_test.py
  - medClient_test.py