Additional improvements

README.md

@@ -32,5 +32,11 @@ Note that some examples requires optional dependencies for plotting, they are:
 
 FMU Import Compliance
 -----------
-PyFMI is tested on an everyday in several different ways. First, with the unit tests found in the directory `tests`, where you also find FMUs with a corresponding `README.txt` that contains information on how the FMUs were generated. However the primary testing is done extensively outside of this project with the `Optimica Compiler Toolkit` (OCT) provided by [Modelon](https://help.modelon.com/latest/reference/oct/). All models from the libraries provided by Modelon have been tested via simulation tests (which covers over 30000+ Modelica models) as FMUs (using the FMU Export functionality from OCT). PyFMI is the default execution engine for [Modelon Impact](https://modelon.com/modelon-impact/).
-Additionally, PyFMI has been tested with Dymola FMUs and FMUs from [FMI Cross Check](https://github.com/modelica/fmi-cross-check), but not as extensively as those previously mentioned.
+PyFMI is tested daily in several different ways:
+* Extensive external testing within the `Optimica Compiler Toolkit` (OCT) provided by [Modelon](https://help.modelon.com/latest/reference/oct/) using all models in Modelon Modelica libararies (35000+ models), exported as FMUs.
+* Unit tests from the `tests` directory. These use FMUs generated by
+* * OCT
+  * JModelica.org
+  * FMUs in the example directory are generated via <em>FMU SDK by Qtronic</em>, more information is available in related `README.txt` for these FMUs with proper license text. 
+* PyFMI is the default execution engine for [Modelon Impact](https://modelon.com/modelon-impact/).
+* Some testing with Dymola FMUs and FMUs from [FMI Cross Check](https://github.com/modelica/fmi-cross-check).