diff --git a/resources/stand-down-guide.md b/resources/stand-down-guide.md
index 47f8545..322d8d0 100644
--- a/resources/stand-down-guide.md
+++ b/resources/stand-down-guide.md
@@ -52,7 +52,7 @@ Example of things to cover and approximate timing (adapt to your needs):
 - Improving communication/adapting the use of Trello (~5 minutes)
   -  If things are still in `to do` and never made it to `doing`, talk about it. Did the team decide to take on too much? Was there a problem that the whole team needed to stop and work on (like deployment)? 
   - If things are still in `doing` and not quite done, make sure to clearly define what it would take to make them `done`
-- What is everyone working on next, updating the Trello board (~10 minutes)
+- What is everyone working on next, updating the Trello board. See planning section(~10 minutes)
 
 
 Further tips:
@@ -67,7 +67,7 @@ To make a successful retro, think of the following tips:
 - Does the meeting feel safe to discuss things openly and candidly? It's important that people feel that it is ok to open up about their struggles so that the team can collaborate on finding ways to support each other and keep moving the project forward. When a team member feels like they haven't been able to do as much as they thought they could, it can feel really bad. Support your teammate so that the next week can go better. A team that cannot talk candidly cannot problem solve effectively.
 - Follow through - whatever you decide on, make sure you check-in about it and follow up
 
-## Planning - half the time (or a little more)
+## Planning - Remaining Time
 
 Now that everyone knows how the week went, what was accomplished and where the struggles are, plan the next week.