Index: trunk/LMDZ.COMMON/libf/evolution/deftank/README
===================================================================
--- trunk/LMDZ.COMMON/libf/evolution/deftank/README	(revision 3938)
+++ trunk/LMDZ.COMMON/libf/evolution/deftank/README	(revision 3958)
@@ -27,5 +27,5 @@
     3) [dimensions]: 64x48x54 to define the grid you want to use  (longitude x latitude x atmospheric layers).
 To run the PEM, you need a dedicated reshaping tool with consistent options. To compile it, in "LMDZ_COMMON", do: ./makelmdz_fcm -arch [local] -p [planet] -d [dimensions] -j 8 reshape_XIOS_output
-To run the PEM, you also need a PCM working with XIOS and consistent options. To compile it, in "LMDZ.COMMON", do: ./makelmdz_fcm -arch [local] -p [planet] -parallel mpi_omp -io XIOS -d [dimensions] -j 8 gcm
+To run the PEM, you also need a PCM working with XIOS and consistent options. To compile it, in "LMDZ.COMMON", do: ./makelmdz_fcm -arch [local] -p [planet] -parallel mpi_omp -io xios -d [dimensions] -j 8 gcm
 After compilation, the executable file can be found in the "bin" sub-directory.
 
@@ -75,7 +75,7 @@
   The user has to specify:
       > n_mars_years, n_earth_years -> the number of Mars/Earth years to be simulated in total (> 0);
-      > nPCM_ini -> the number of initial PCM runs (>= 2);
-      > nPCM -> the number of PCM runs between each PEM run (>= 2, usually 2);
-      > counting -> the counting method for the number of years to be simulated (0 = "only PEM runs count"; any other values = "PCM runs are taken into account"). The former option is the usual one;
+      > nPCM_ini -> the number of initial PCM years (>= 2);
+      > nPCM -> the number of PCM years between each PEM run (>= 2, usually 2);
+      > counting -> the counting method for the number of years to be simulated (0 = "only PEM years count"; any other values = "PCM years are taken into account"). The former option is the usual one;
       > mode -> the launching mode (0 = "processing scripts"; any other values = "submitting jobs"). The former option is usually used to process the script on a local machine while the latter is used to submit jobs on a supercomputer with SLURM or PBS/TORQUE.
   The script can take an argument:
