Developer's-corner/Code-Architecture-and-Organization.md

@@ -4,7 +4,7 @@
 The main purpose of a fargo3D simulation is to track the evolution of a planetary system embedded in a disk of gas. Those two entities will be represented by a **Disk** and **PlanetarySystem** class respectively (defined in [disk.hpp](https://gitlab.oca.eu/DISC/fargOCA/-/blob/master/include/disk.hpp) and in [planetarySystem.hpp](https://gitlab.oca.eu/DISC/fargOCA/-/blob/master/include/planetarySystem.hpp)).
  A single simulation will instantiate one object of each.
 
-That simulation is driven by an instance of the **Simulation** class (currently implementing a simple [Command pattern](https://en.wikipedia.org/wiki/Command_pattern), but might evolve into a [Template Method](https://en.wikipedia.org/wiki/Template_method_pattern). It behaves like a function object which performs one step of the simulation at each call.
+That simulation is driven by an instance of the **Simulation** class (currently implementing a simple [Command pattern](https://en.wikipedia.org/wiki/Command_pattern), but might evolve into a [Template Method](https://en.wikipedia.org/wiki/Template_method_pattern). It behaves like a function object which performs one step of the simulation at each call (doStep in [Simulation.cpp]https://gitlab.oca.eu/DISC/fargOCA/-/wikis/Developer's-corner/Code-Architecture-and-Organization
 
 From the user's perspective, the simulation is configured through a property tree from which the following are extracted: a description of the physic (stored in a **DiskPhysic** object) a grid (in **GridDispatch** and **GridCoords** object) and a set of trackers (stored in a set of **SimulationTrackers**) that will extract the information were interested in during the run.