normalization and move french to the end

3_rasta/4_failures_analysis.typ

@@ -111,12 +111,12 @@ android.jar en version 9 qui génère des erreurs
 
 During the running of our experiment, we parsed the standard output and error to capture:
 
-- Java errors and stack traces
-- Python errors and stack traces
-- Ruby errors and stack traces
-- Log4j messages with a "ERROR" or "FATAL" level
-- XSB error messages
-- Ocaml errors
+- Java errors and stack traces.
+- Python errors and stack traces.
+- Ruby errors and stack traces.
+- Log4j messages with a "ERROR" or "FATAL" level.
+- XSB error messages.
+- Ocaml errors.
 
 For example, Dialdroid reports an average of #num(55.9) errors for one successful analysis. 
 On the contrary, some tools, such as Blueseal report very few errors at a time, making it easier to identify the cause of the failure. 

3_rasta/6_recommendations.typ

@@ -13,8 +13,8 @@ During the packaging and testing of the tools we examined in our experiment, the
 To make a tool easy to reuse, it should have documentation with at least:
 - Instructions about how to install the dependencies.
 - Instructions about how to build the tool (if the tool needs to be built).
-- Instructions about how to use the tool (#eg command line arguments)
-- Instructions about how to interpret the results of the tools (we only checked for the existence of the results in our experiment, but we found that some results can be quite obscure)
+- Instructions about how to use the tool (#eg command line arguments).
+- Instructions about how to interpret the results of the tools (we only checked for the existence of the results in our experiment, but we found that some results can be quite obscure).
 In addition to the documentation, a minimum working example with the expected result of the tools allows a potential user to check if everything is working as intended.
 This #MWE have the additional benefit that it can serve as an example in the documentation.