Update ARKitecture.md
Grammatical changes/typos
@@ -132,7 +132,7 @@ Our universal solver is written in a very general way that should be applicable
#### The Flow of Time and Other Methods
-Because dynamic optimization problems are solved recursively in our framework, it is natural to list time-varying values in reverse chronological order-- the ***solve()*** method loops over the values in each time-varying list in the same direction that a human would read them. When simulating agents after the solution has been obtained, however, it is much more convenient for time-varying parameters to be listed in ordinary chronological order-- the direction in which they will be experienced by simulated agents. To allow the user to set the order in which ''time is flowing'' for an instance of ***AgentType, the HARK framework includes functionality to easily change ordering of time-varying values.
+Because dynamic optimization problems are solved recursively in our framework, it is natural to list time-varying values in reverse chronological order-- the ***solve()*** method loops over the values in each time-varying list in the same direction that a human would read them. When simulating agents after the solution has been obtained, however, it is much more convenient for time-varying parameters to be listed in ordinary chronological order-- the direction in which they will be experienced by simulated agents. To allow the user to set the order in which ''time is flowing'' for an instance of ***AgentType***, the HARK framework includes functionality to easily change ordering of time-varying values.
The attribute ***time_flow*** is ***True*** if variables are listed in ordinary chronological order and ***False*** otherwise. ***AgentType*** has the following methods for manipulating time:
@@ -184,7 +184,7 @@ To specify a complete instance of ***Market***, the user should give it the foll
* ***reap_vars***: A list of strings naming variables to be collected from the ***agents*** in the ***reap*** step, to be used as inputs for the aggregate market process.
-* ***const_vars***: A list of strings naming variables used by the aggregate market process that *do not* come from ***agents***; they are constant or come from the ****Market*** itself.
+* ***const_vars***: A list of strings naming variables used by the aggregate market process that *do not* come from ***agents***; they are constant or come from the ***Market*** itself.
* ***track_vars***: A list of strings naming variables generated by the aggregate market process that should be tracked as a history, to be used when calculating a new dynamic rule. Usually a subset of ***sow_vars***.
