ResultIterator: Apply Suggestion changes

Co-Authored-By: David Négrier <[email protected]>

Author: homersimpsons

doc/quickstart.md

@@ -24,7 +24,7 @@ DAOs, Beans and ResultIterators
 
 When you [installed TDBM](install.md), you spent some time configuring a connection to your database and then, you generated the DAOs, beans and resultIterators.
 
-There will be roughly **one class (DAO, Bean, ResultIterator) per table**, in fact only ManyToMany link tables won't get their class.
+There will be roughly **one class (DAO, Bean, ResultIterator) per table**, in fact only ManyToMany link tables won't get their classes.
 
 Each time your database model changes (if you add a new table, a new column, an index or a foreign key...), you will need to regenerate those DAOs, beans and resultIterators.
 
@@ -40,7 +40,7 @@ This instance will allow you to easily update your data using setters and getter
 
 ### ResultIterators
 
-A ResultIterator will represent the result of a query. It will allow you to specify it.
+A ResultIterator object represents the result of a query. It is an iterable object. You can use it to paginate through the results, sort the results or (in the future) filter the results.
 
 Usage sample
 ------------
@@ -185,7 +185,7 @@ generated 4 classes:
   column of the "users" table. It is generated by TDBM and you should never modify this class.
 - `User`: this class extends `AbstractUser`. If you have some custom getters and setters, you should implement them in this class. You can
   edit it as TDBM will never overwrite it.
-- `AbstractUserResultIterator`: the resultIterator representing a query on the "users" table. This class contains methods to specify you query.
+- `AbstractUserResultIterator`: the resultIterator representing a query on the "users" table. This class contains methods to filter/sort/paginate your query.
   It is generated by TDBM and you should never modify this class.
 - `UserResultIterator`: this class extends `AbstractUserResultIterator`. If you have some custom function to narrow down your queries you should implement them in this class. You can
   edit it as TDBM will never overwrite it.