Formatting

Sprint Review.md

@@ -26,16 +26,16 @@ Before the meeting, the _Product Owner_ should:
 This meeting should be run by the **Product Owner** using the agenda listed below:
 
 1. Make sure the meeting starts on time.
-2. Product Demonstration: The product owner demonstrates the incremental changes since the last sprint increment review. Since this is the first meeting, all working features demonstrate progress. Note that there should be no technical language used here, the demonstration should only cover how the end user will interact with the system. This should take no longer than 10 min.
-3. Once the demonstration is complete the client provides feedback, this consists of:
-    1. Sign-Off: the client is happy with onee or more features and the product owner should note this down.
+2. **Product Demonstration**: The product owner demonstrates the incremental changes since the last sprint increment review. Since this is the first meeting, all working features demonstrate progress. Note that there should be no technical language used here, the demonstration should only cover how the end user will interact with the system. This should take no longer than 10 min.
+3. **Feedback:** Once the demonstration is complete the client provides feedback, this consists of:
+    1. Sign-Off: the client is happy with one or more features and the product owner should note this down.
     2. Bug-Fixes: there might be a few points raised by the client and they will indicated what needs changing. This might be a UI tweak or something more signficant. Again, the product owner makes notes.
-4. Backlog Review: the product owner goes through the printout and the client discusses:
+4. **Backlog Review**: the product owner goes through the printout and the client discusses:
     1. whether there are additional features they now want.
     2. Whether the tasks are in the best priority order.
     3. What feature they would like the team to work on in the next timeboxed sprint.
-5. Now, with the client present, the team should describe the feature from the user perspective using diagrams and designs. At this point the feature should be clear from both the client and development team perspectives.
-6. Finally the date and time for the next review meeting are agreed and put in everyone's diary. The client can now leave.
+5. **Planning**: Now, with the client present, the team should describe the feature from the user perspective using diagrams and designs. At this point the feature should be clear from both the client and development team perspectives.
+6. **Next Meeting**: Finally the date and time for the next review meeting are agreed and put in everyone's diary. The client can now leave.
 
 ## 2 Team Retrospective