[blog] post about LTest opam release

_posts/2022-04-xx-ltest-plugins-released.md

@@ -38,14 +38,15 @@ papers, but once again, their maintenance was sporadic.
 This opam release, plus the code being kept closer to Frama-C's development
 version in Gitlab, should help keep these plug-ins relevant. Note that the
 released version is numbered 0.1, which indicates that they are still in an
-experimental stage; industrial users should contact the Frama-C team for
-details about their maturity.
+experimental stage; potential industrial users might want to contact 
+the Frama-C team for details about their maturity.
 
 You may also have noticed: why is the opam package for LReplay named
 `lreplay` and not `frama-c-lreplay`? The simple reason is that, unlike the
 others, it is not a Frama-C plug-in *per se*, but an independent tool
-(it even has its own Dune build file) that can be used with or without
+(so that it was able to switch to `Dune` earlier than the rest of the platform)
+that can be used with or without
 Frama-C. It turns out that its defaults are mostly tuned for using it in
 conjunction with
 [PathCrawler](https://www.frama-c.com/fc-plugins/pathcrawler.html),
-but it can be configured for use with other test generators.
+but it can be configured for use with any test suite, generated or not.