MEDUSA-Training-How-to-run-MEDUSA-1D-(-on-NOC-linux-system).md

@@ -71,7 +71,7 @@ cd MEDUSA_git
   * **`sette`** : some automatic stability tests (used for development purpose)  
   * **`README.md`** : the `MEDUSA git` home page documentation
   * **`add_msa_to_nemo`** : script to put MEDUSA at the right place
-* `nemo` is the NEMO code :   
+* `nemo` is the NEMO code :    
   ![image](uploads/7bcef083d7366f47fc1ff7ff67b940a1/image.png)   
   We find the same architecture than in `MEDUSA_resources` (because `MEDUSA` is made to fit in NEMO by replicating it's structure, ...) plus :
   * **`makenemo`** : The compilation script -- compilation is used to create an **executable** we'll be able to run, from all our `fortran` code (if you do some changes in a `fortran` file, it will only be taken into account at run time if you recompile the code).
@@ -130,7 +130,7 @@ cd nemo
   It should compile successfully the dynamic and the passive tracer all at once. Here our 1D config is called `C1D_MED`. Compiling this way, All the files are at the right place already, so - still, double check - you should be able to happily skip the file management part of the next section. 
 
 Once compiled, You have a new directory: `C1D_MED` in `nemo`'s `cfgs` directory :  
-Let's have a look: 
+Let's have a look:   
 ![image](uploads/1139657de150fd2c241e99bffcf7af74/image.png)  
 with :    
 * **`BLD`** : where the code is compiled for this config.