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

@@ -6,7 +6,7 @@ The main purpose of a fargo3D simulation is to track the evolution of a planetar
 
 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.
+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 defined in [gridDispatch.hpp](https://gitlab.oca.eu/DISC/fargOCA/-/blob/master/include/gridDispatch.hpp) and [gridCoords.hpp](https://gitlab.oca.eu/DISC/fargOCA/-/blob/master/include/gridCoords.hpp)) and a set of trackers (stored in a set of **SimulationTrackers** defined in [simulationTrackers.hpp](https://gitlab.oca.eu/DISC/fargOCA/-/blob/master/include/simulationTrackers.hpp)) that will extract the information were interested in during the run.
 
 The main sequence diagram can be seen as follow: