Update 2024-07-29-Week-2.md

docs/_posts/2024-07-29-Week-2.md

@@ -80,7 +80,7 @@ await manager.launchWorld(universe_config);
 
 ## Launching the Simulation
 
-![docker_exec](../assets/images/week2/docker_exec.png)
+![docker_exec]({{ site.baseurl }}/assets/images/week2/docker_exec.png)
 
 When the user presses the start simulation button, the frontend sends the [necessary messages](https://github.com/JdeRobot/bt-studio/blob/3557b622212f567251e2ffc2f3b4e560323de2d2/frontend/src/App.js#L74C1-L91C5) to the RAM through the manager, retrieving the configuration from BT Studio's backend. For preexisting universes within the RB, this includes just the launch path and ID; for custom universes, the zip is also needed.
 
@@ -95,7 +95,7 @@ Once this process is complete, the simulation can be visualized through the VNC
 
 Once users select a project, they need a way to launch the desired universe from those available for that project. The universe modal queries the backend for the list and starts the launch process when one of them is selected.
 
-![universe_modal](../assets/images/week2/universe_modal.png)
+![universe_modal]({{ site.baseurl }}/assets/images/week2/universe_modal.png)
 
 Additionally, I developed a modal for adding custom universes. Users can drag and drop a zip file, and the modal will handle calling the necessary *tree_api* endpoint to store the zip and create its configuration. After that, the user will be able to select it from the list of universes.