GSoC-Entry-Test.md

@@ -3,7 +3,7 @@
 This entry test is divided into 3 steps: the further you get through it, the better your chances are of being selected for the GSoC.
 
 _**Important note:** you must complete step 1 for your application to be considered.
-Once you complete a step, notify your tentative mentors to obtain feedback._
+Once you complete a step, notify your tentative mentors to obtain feedback and guidance for the next steps._
 
 _Some projects require specific entry tests, if your project does not, then follow these instructions._
 
@@ -18,15 +18,16 @@ _Note that this step does not require programming, you just need to be able to w
 
 _Should require roughly 2 hours_
 
-## Step 2
+## Step 2: your first contribution to MBDyn
   - implement a modification to the MBDyn code used by the test case you ran;
+  - re-compile MBDyn to apply your changes
   - re-run your test case with the modified code;
   - describe the effect of your modification on the test case's results;
   - issue a merge request as described in the [Developers Guidelines](https://public.gitlab.polimi.it/DAER/mbdyn/wikis/Development/Developers-Guidelines).
 
 _Should require roughly 4 hours_
 
-## Step 3 create your own module
+## Step 3: create your own module
   - compile MBDyn with support for run-time loadable modules, following instructions reported in the related [FAQ](https://www.mbdyn.org/?Documentation___Official_Documentation___FAQ#HOW_CAN_I_BUILD_RUN_TIME_LOADABLE_MODULES);
   - develop a simple run-time loadable module that implements a custom instance of one of the following (in order of complexity)
     - a drive caller