Analyze-the-results.md

@@ -3,14 +3,14 @@ To proceed, open the `index.html` file that has been generated in the testsuite
 
 ## Main page
 
-You'll be redirected to the testsuite main page, showing the build, test, and code coverage sections, with summarized information about the whole test. For each item, <img src="uploads/397a6076cb9ba95116a9a578f5a67397/ko.png" width="20"> means a failure, while ![ok](uploads/e44db76c513f51763fba543f02105c9e/ok.png) means a success. On the top left, the valid flag gives the general result. The code coverage is not taken into account to determine if the whole testsuite is valid or not.
+You'll be redirected to the testsuite main page, showing the build, test, and code coverage sections, with summarized information about the whole test. For each item, <img src="uploads/397a6076cb9ba95116a9a578f5a67397/ko.png" width="20"> means a failure, while <img src="uploads/e44db76c513f51763fba543f02105c9e/ok.png" width="20"> means a success. On the top left, the valid flag gives the general result. The code coverage is not taken into account to determine if the whole testsuite is valid or not.
 
 ![Capture_d_écran_de_2020-03-30_17-11-44](uploads/a673974bc28e67774b73144290b73ea7/Capture_d_écran_de_2020-03-30_17-11-44.png)
 *Main page of the testsuite showing the build, test, and code coverage sections*
 
 ## Builds
 
-If you click on the build item, you will access the build page. For each build, you'll see its name, the compiler, the version, some tags specific to this build, the modules loaded to compile, the configuration file, the job script content, and the output and error files generated by the job execution, as well as the execution time. If a build has failed (![ko](uploads/14d197e227c63daf4dae6d565aec6fe2/ko.png)), don't hesitate to analyze the content of the various files to understand what is the cause of the failure.
+If you click on the build item, you will access the build page. For each build, you'll see its name, the compiler, the version, some tags specific to this build, the modules loaded to compile, the configuration file, the job script content, and the output and error files generated by the job execution, as well as the execution time. If a build has failed (![ko](<img src="uploads/397a6076cb9ba95116a9a578f5a67397/ko.png" width="20">), don't hesitate to analyze the content of the various files to understand what is the cause of the failure.
 
 ![Capture_d_écran_de_2020-03-30_17-21-46](uploads/e9701a604ed6c1567cc75d6c9998a487/Capture_d_écran_de_2020-03-30_17-21-46.png)
 *Build page showing various compilations*
@@ -23,9 +23,9 @@ Here, the list of statuses:
 
 | Symbol | Meaning |
 | ------ | ------ |
-| ![ok](uploads/12ed412aaa18f7987dfd1021afa29a07/ok.png) | OK |
-| ![ko](uploads/3e6640fec1ee1d497e014ea8f3008159/ko.png) | Unspecific execution erro or combination of various errors | 
-| ![time](uploads/2897f0394a8faa852e6da3e9815500d1/time.png) | Timeout |
+| <img src="uploads/397a6076cb9ba95116a9a578f5a67397/ko.png" width="20"> | OK |
+| <img src="uploads/397a6076cb9ba95116a9a578f5a67397/ko.png" width="20"> | Unspecific execution erro or combination of various errors | 
+| <img src="uploads/2897f0394a8faa852e6da3e9815500d1/time.png" width="20"> | Timeout |
 
 As for the compilation, you can get more insight into the test results by clicking on the corresponding red cross.