Setup-a-Windows-OVH-instance-for-CI.md

@@ -119,11 +119,11 @@ Troubleshooting
 Debug inside Docker
 ===================
 
-It may be necessary to run commands inside the Docker to understand why the CI fails. In order to do so, connect to the server and run `docker run -v C:/:C:/C -it buildtools`. With this command, you will have access to the `C:\` driver of the server inside the `C:\C\` folder in the container. This way, you may download for example build artifacts in the server and access them inside the Docker to re-run the failing commands.
+It may be necessary to run commands inside the Docker to understand why the CI fails. In order to do so, connect to the server and run `docker run -v C:/:C:/C -it buildtools`. With this command, you will have access to the `C:\` drive of the server inside the `C:\C\` folder in the container. This way, you may download for example build artifacts in the server and access them inside the Docker to re-run the failing commands.
 
-You will need to first execute in the docker the commands in the `before_script` section from the failing YML CI file, in order to setup the environment requirements.
+You will need to first execute in the docker the commands in the `before_script` section from the corresponding YML CI file, in order to setup the environment requirements.
 
-To check if there is some DLL missing, use this kind of command in the Docker:
+If you get `Exit code 0xc0000135`, check if there is some DLL missing. Use this kind of command in the Docker:
 
 ```
 & 'C:\Program Files\Git\bin\bash.exe' -c 'C:/builds/eclipse/aidge/aidge_core/build_cpp/unit_tests/Debug/tests_aidge_core.exe'