Module readmes - Test and update parameter usage section in readme in all modules
Description
During a workshop on CARML, teams used the parameter usage sections when creating solutions. Some of these were incorrect, causing the teams to need to check the code for actual parameter usage, thus slowing them down. These parameter usage examples needs to be tested and validated and updated where needed to ensure they are correct.
Could be solved (to an extend) by automating it's population (e.g. fetch from parameter file(s)). However, this comes with its own challenges.
For the time being we should probably start evaluating the 'as is' state and then go from there.
Linked to #1096
I also would suggest to close this issue as a duplicate of #1096. Moving back to needs triage for this purpose.