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

@@ -3,9 +3,9 @@
 
 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. 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 behave like a function object with perform 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.
 
-From the user's perspective, the simulation is configured through a property tree from wich is extracted a description of the physic (stored in a **DiskPhysic** object) a grid (in **GridDispatch** and **GridCoords** objetct) and a set of tracker (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) and a set of trackers (stored in a set of **SimulationTrackers**) that will extract the information were interested in during the run.
 
 The main sequence diagram can be seen as follow: