diff --git a/Docs/DustemWrap_development_issues.txt b/Docs/DustemWrap_development_issues.txt
index 4464453..d4ae31b 100644
--- a/Docs/DustemWrap_development_issues.txt
+++ b/Docs/DustemWrap_development_issues.txt
@@ -1,10 +1,11 @@
-%This is a note containing development issues for Dustem
+%This is a note describing known current development issues for Dustem
 %This file is called DustemWrap_development_issues.txt and is managed by J.-Ph. Bernard and Ilyes Choubani
-%Issues must be described as explicitely as possible
-%These issues must be checked before releasing Dustem and Dustemwrap
+%Issues must be described as explicitly as possible
+%These issues must be checked before the next joint release of Dustem and Dustemwrap
 
 - JPB, April 8th 2022:
   Dustem has a bug due to calculation accuracy for the THEMIS model, which solves by replacing max size values in GRAIN_THEMIS.DAT from 9.00E-6 into 8.99E-05
+
 - JPB, April 8th 2022:
-  Dustemwrap plante le Fortran quand le keyword chrg (et probablement aussi spin) ne figurent pas dans le GRAIN.DAT de depart (du Fortran) et sont rajoutés ensuite via (*!dustem_params).grains[0].TYPE_KEYWORDS
-  We must force those pointers to not be empty just after writing our own GRAIN.DAT in /tmp, in the same qway this is don in dustem_init.pro with the GRAIN.DAT from the fortran directory.
\ No newline at end of file
+  Dustemwrap causes the Fortran to crash if the chrg keyword is not specified in the initial GRAIN.DAT file, but is subsequently added by the (*!dustem_params).grains[0].TYPE_KEYWORDS. A similar error is likely to occur for the spin keyword (untested).
+  We must force these pointers to not be empty just after writing our own GRAIN.DAT in /tmp, in the same way this is done in dustem_init.pro with the GRAIN.DAT from the fortran directory.
--
libgit2 0.21.2