docs: ✏️ suggestions from review

Co-authored-by: Kris Beicher <112945740+K-Beicher@users.noreply.github.com>

how-we-work/iteration.qmd

@@ -50,7 +50,7 @@ Team lead sets everything up for the next two or three iterations.
     iterations a few days before major holidays start.
 -   Will plan and decide on how long the future iterations should be
     (can range from 2-6 weeks, but prefer shorter iterations over longer
-    ones). Currently, we find iterations with a duration of one month
+    ones). Currently, we find iterations with a duration of one calendar month
     work the best for us. This way, we have the planning meeting at the
     beginning of the month and the debrief and retrospective meeting at
     the end of the month.
@@ -78,7 +78,7 @@ A basic agenda for the meeting might be:
 -   Schedule the next iteration's end and start meetings.
 
 We usually have separate aims for each person in the team, and each of
-us will add tasks to the board relevant to that aim aim as needed. This
+us will add tasks to the team project board relevant to that aim aim as needed. This
 usually happens as the iteration progresses.
 :::
 
@@ -111,9 +111,8 @@ tasks.
 
 Then, we agree on and schedule the end date debrief and retrospective
 meeting, which should be approximately 1-2 hours and preferably before
-lunch, as well as the next iterations planning meeting. The next
-planning meeting should either be on the same date after lunch, to
-ensure a proper break before moving to a new iteration, or the next day
+lunch, as well as the next iterations planning meeting. We have found that the
+planning meeting is best held the day after to ensure that we don't get too tired towards the end. Alternatively it can be the same day as the debrief, but there should be a substantial break between the two meetings.
 to give some break between meetings.
 :::