From 3cc9afb305fb62a06dedb0490baddc3e7e15cc0c Mon Sep 17 00:00:00 2001
From: giuliaghirardini <giulia.ghirardini@skywarder.eu>
Date: Fri, 21 Feb 2025 21:59:50 +0100
Subject: [PATCH] [documentation] Triyng to resolve alert labels rendering on
 GitLab

---
 README.md | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/README.md b/README.md
index c217e93..c39950a 100644
--- a/README.md
+++ b/README.md
@@ -8,7 +8,7 @@ For example, the main repo we are going to use is `msa-toolkit`. This repo has a
 
 > [!WARNING]
 > When working on main repo msa-toolkit be sure on what branch/commit is your submodule checked out. Data and results may be different on simulation if submodule is not updated to latest version!
-
+>
 
 ## Submodule architecture
 
@@ -23,8 +23,10 @@ The submodule is divided into four main folders:
     mission.name = '2025_Orion_Portugal_October';
     ```
   * **settings**: this folder only contains `odeConfig.m`, which contains ODE settings.
+  
 >[!CAUTION]
 > Don't touch `odeConfig.m` if you don't know what you're doing, from this configuration file depend ode-based script, such ad ballistic.m, and so all the toolkits!.
+>
 
 Inside the mission folder, you can find all the missions and their data and configurations file. Each folder has the name of the mission in a specific format/order. This format is the one you have to use when speficing the mission in `missionConfig.m`.
 
-- 
GitLab