Small formatting updates

Author: GeekTrainer

docs/5-reviewing-coding-agent.md

@@ -1,4 +1,4 @@
-# Review GitHub Copilot coding agent's work
+# Exercise 5: Review GitHub Copilot coding agent's work
 
 | [← Adding new functionality with Copilot Agent Mode][previous-lesson] |
 |:----:|
@@ -30,7 +30,7 @@ Let's start by exploring the first pull request (PR) generated by GitHub Copilot
 3. Open issue titled something similar to **Add missing documentation** or something more robust.
 
 > [!NOTE]
-> If Copilot is still working on the task, the issue will contain the **WIP** flag. If so, wait for Copilot to complete the work. This may take a few minutes, so feel free to take a break, or reflect on everything you've learned so far.
+> If Copilot is still working on the task, the issue will contain the **[WIP]** flag. If so, wait for Copilot to complete the work. This may take a few minutes, so feel free to take a break, or reflect on everything you've learned so far.
 
 4. Once the pull request is ready, select the **Files changed** tab and review the changes.
 
@@ -43,7 +43,7 @@ Let's start by exploring the first pull request (PR) generated by GitHub Copilot
 
     ![Approve and run workflows](images/ex4-approve-and-run.png)
 
-9.  You should see the workflows get queued in the checks section of the pull request. All being well, you should see that the workflows pass for both the backend and frontend. This may take a few minutes to complete.
+9. You should see the workflows get queued in the checks section of the pull request. All being well, you should see that the workflows pass for both the backend and frontend. This may take a few minutes to complete.
 
 ## Requesting changes from GitHub Copilot
 
@@ -54,14 +54,14 @@ Working with Copilot on a pull request is not just a one-way street. You can als
 - Create a README in both the server and client folders with descriptions of the codebase of each.
 
 1. Add a comment requesting a change to the generated documentation. Use one of the ideas above, or another suggestion for Copilot around documentation you'd like to see in the codebase.
-2.  Feel free to watch the session as Copilot works on the changes.
-3.  Select **View Session** to watch Copilot perform its work. Notice how Copilot starts a new session to make the updates.
-4.  You can select **Back to pull request** to return to the pull request.
+2. Feel free to watch the session as Copilot works on the changes.
+3. Select **View Session** to watch Copilot perform its work. Notice how Copilot starts a new session to make the updates.
+4. You can select **Back to pull request** to return to the pull request.
 
     ![Back to pull request](images/ex4-back-to-pr.png)
 
-5.  Once Copilot has completed the changes, you should see a new commit in the pull request.
-6.  Select the **Files changed** tab to review the changes.
+5. Once Copilot has completed the changes, you should see a new commit in the pull request.
+6. Select the **Files changed** tab to review the changes.
 
 Feel free to continue iterating until you are happy. Once happy, you can convert the PR to ready from a draft, and merge it into the main branch.
 
@@ -81,7 +81,7 @@ Let's return to the PR Copilot generated for resolving our issue about adding en
 
     ![Approve and run workflows](images/ex4-approve-and-run.png)
 
-8.  You should see the workflows get queued in the checks section of the pull request. All being well, you should see that the workflows pass for both the backend and frontend. This may take a few minutes to complete.
+8. You should see the workflows get queued in the checks section of the pull request. All being well, you should see that the workflows pass for both the backend and frontend. This may take a few minutes to complete.
 
 Copilot has created the new endpoints! Just as before, you can work iteratively with Copilot coding agent to request updates. For example, you might want to request Copilot centralizes the error handling to reduce duplication, or ensuring comments and docstrings are added (remember - this was assigned **before** we made the updates to our custom instructions!) Just like before, you can make these requests by adding a new comment on the **Conversation** tab, which Copilot will see and kickoff a new session.
 
@@ -127,4 +127,4 @@ This is just the beginning, and we can't wait to see how you use Copilot to help
 [coding-agent-best-practices]: https://docs.github.com/en/copilot/using-github-copilot/coding-agent/best-practices-for-using-copilot-to-work-on-tasks
 [agent-firewall]: https://docs.github.com/en/copilot/customizing-copilot/customizing-or-disabling-the-firewall-for-copilot-coding-agent
 
-[previous-lesson]: ./4-copilot-agent-mode-vscode.md
+[previous-lesson]: ./4-copilot-agent-mode-vscode.md