GSoC-Project-Ideas.md

@@ -54,7 +54,7 @@ NOTE: the work will start from on the existing [MBDyn Python Preprocessor](https
 **Category**: [User Interface](#user-interface)\
 **Programming Languages**: Python\
 **Difficulty**: Low/Intermediate\
-**Mentors**: Andrea Zanoni, Alberto Savino, Andrea Colli\
+**Mentors**: Andrea Zanoni, Marek Lukasiewicz
 **ENTRY TEST**: Complete step 1 of standard MBDyn GSoC [entry test](https://gitlab.polimi.it/Pub/mbdyn/wikis/Google-Summer-of-Code/Entry-Test), compiling MBDyn from the `preprocess` branch, then write a simple parametric input file leveraging the Python Preprocessor. If you can, try to add support for a new MBDyn entity (e.g. a Drive Caller, see Section 2.6 of the Input Manual).
 
 ---
@@ -95,7 +95,7 @@ It is simple to use and generates 3D animations that represent the exact model m
   - only fixed timestep simulation output is currently supported, variable timestep should be allowed also
   - support the live plotting of MBDyn signals, for example leveraging the NetCDF output `sync` feature
   - support the plotting of signals derived from arbitrary compositions of MBDyn signals (e.g. the sum of two signals) (up to here, this is a **90 hours project**)
-  - support for the visualization of specific models, like for example aeroelastic models of rotary wing aicraft, biomechanical models of the human body, ecc... (getting here will require **175** or **350 hours**, depending on how many possibilities for specific models are introduced)
+  - support for the visualization of specific models, like for example aeroelastic models of rotary wing aircraft, biomechanical models of the human body, ecc... (getting here will require **175** or **350 hours**, depending on how many possibilities for specific models are introduced)
 
 **Category**: [User Interface](#user-interface)\
 **Programming Languages**: Python\
@@ -108,7 +108,7 @@ It is simple to use and generates 3D animations that represent the exact model m
 
 ### Complete NetCDF output implementation
 
-MBDyn can output simulation results in [NetCDF](https://www.unidata.ucar.edu/software/netcdf/) format, speeding up significantly the manipulation of output data for visualization and processing. Currently, the support for binary output is still not complete among all the MBDyn entitites. For example, drives are currently not supported, nor are numerous user-defined elements contained in [modules](home#what-are-run-time-loadable-modules-and-how-do-they-work).
+MBDyn can output simulation results in [NetCDF](https://www.unidata.ucar.edu/software/netcdf/) format, speeding up significantly the manipulation of output data for visualization and processing. Currently, the support for binary output is still not complete among all the MBDyn entities. For example, drives are currently not supported, nor are numerous user-defined elements contained in [modules](home#what-are-run-time-loadable-modules-and-how-do-they-work).
 
 The aim of this project is to add the support for binary output to all the missing entities. A vast library of examples can be obtained simply looking at the current implementation for the supported entities. 
 
@@ -130,7 +130,7 @@ The roadmap can be the following one:
 
 ## IPC/RT
 
-### Introduce MavLink support 
+### Introduce MAVLink support 
 
 MBDyn offers several possibilities to communicate with external processes: UNIX sockets, RTAI mailboxes or standard TCP/UDP sockets can be used to exchange data.
 
@@ -161,6 +161,6 @@ This project aims at developing an *in-house* solution for the coupling, in the
 **Programming Languages**: C/C++\
 **Keywords**: Inter-Process Communication, Co-Simulation\
 **Difficulty**: Intermediate/Advanced\
-**Mentors**: Andrea Zanoni, Alberto Savino, Andrea Colli
+**Mentors**: Andrea Zanoni, Alberto Savino, Alessandro Cocco
 
 ---