Update Wave 2 & 3 docs

Author: kelsey-steven-ada

ada-project-docs/wave_02.md

@@ -8,15 +8,16 @@ Our task list API allows users to create tasks and get a list of all tasks. Our
 
 The following are required routes for wave 2. Feel free to implement the routes in any order within this wave.
 
-### Tips
-
-- Pay attention to the exact shape of the expected JSON. Double-check nested data structures and the names of the keys for any misspellings.
-- Use the tests in `tests/test_wave_02.py` to guide your implementation.
+Use the tests in `tests/test_wave_02.py` to guide your implementation.
 - You may feel that there are missing tests and missing edge cases considered in this wave. This is intentional.
   - You have fulfilled wave 2 requirements if all of the wave 2 tests pass.
   - You are free to add additional features, as long as the wave 2 tests still pass. However, we recommend that you consider the future waves, first.
 - Some tests use a fixture named `three_tasks` that is defined in `tests/conftest.py`. This fixture saves three different tasks with three different titles to the test database.
 
+### Tips
+
+- Pay attention to the exact shape of the expected JSON. Double-check nested data structures and the names of the keys for any misspellings.
+
 ### Sorting Tasks: By Title, Ascending
 
 As a client, I want to be able to make a `GET` request to `/tasks?sort=asc` when there is more than one saved task, and get an array of tasks sorted by **title**. The titles should be in _ascending_ order, where a task with the title "A" is sorted before a task with the title "B."

ada-project-docs/wave_03.md

@@ -4,24 +4,28 @@
 
 Our task list API allows users to meaningfully use the task resource. Users want to be able to mark a task as "complete" or "incomplete."
 
-We want to design our API so that it stores a task's `completed_at` date as a datetime value in our database. In this scenario, our API does _not_ give users the `completed_at` date... it only gives the information if `is_complete` is `true` or `false`.
+We want to design our API so that it stores a task's `completed_at` date as a datetime value in our database. In this scenario, our API does _not_ give users the `completed_at` date – it only gives the information if `is_complete` is `true` or `false`.
 
-A task's `is_complete` is `true` when there is a datetime for the task's `completed_at` value. A task's `is_complete` is `false` when there is a `null`/`None` value for the tasks's `completed_at` value.
+A task's `is_complete` is:
+- `true` when there is a datetime for the task's `completed_at` value.
+- `false` when there is a `null`/`None` value for the tasks's `completed_at` value.
 
 ## Requirements
 
 The following are required routes for wave 3. Feel free to implement the routes in any order within this wave.
 
-### Tips
-
-- Use the tests in `tests/test_wave_3.py` to guide your implementation.
+Use the tests in `tests/test_wave_3.py` to guide your implementation.
 - You may feel that there are missing tests and missing edge cases considered in this wave. This is intentional.
   - You have fulfilled wave 3 requirements if all of the wave 3 tests pass.
   - You are free to add additional features, as long as the wave 3 tests still pass. However, we recommend that you consider the future waves, first.
 - A test uses a fixture named `completed_task` that is defined in `tests/conftest.py`. This fixture saves a task with a datetime value in `completed_at` to the test database.
+
+### Tips
+
 - JSON's value of `true` is similar to Python's value of `True`, and `false` is similar to Python's `False`.
 - SQL's value of `null` is similar to Python's value of `None`.
 - Python has a [datetime library](https://docs.python.org/3/library/datetime.html#module-datetime) which we recommend using to represent dates in model attributes.
+- Notice that these routes require that we look up a model by its ID, and then update that model. We should be able to reuse the same route helper methods that we have been using in other Task routes to help build these routes.
 
 ### Mark Complete on an Incomplete Task
 
@@ -44,12 +48,10 @@ After I have made the `PATCH` request, I can submit a `GET` request to `/tasks/1
 
 ```json
 {
-  "task": {
-    "id": 1,
-    "title": "Go on my daily walk 🏞",
-    "description": "Notice something new every day",
-    "is_complete": true
-  }
+  "id": 1,
+  "title": "Go on my daily walk 🏞",
+  "description": "Notice something new every day",
+  "is_complete": true
 }
 ```
 
@@ -74,12 +76,10 @@ After I have made the `PATCH` request, I can submit a `GET` request to `/tasks/1
 
 ```json
 {
-  "task": {
-    "id": 1,
-    "title": "Go on my daily walk 🏞",
-    "description": "Notice something new every day",
-    "is_complete": false
-  }
+  "id": 1,
+  "title": "Go on my daily walk 🏞",
+  "description": "Notice something new every day",
+  "is_complete": false
 }
 ```
 
@@ -104,19 +104,13 @@ After I have made the `PATCH` request, I can submit a `GET` request to `/tasks/1
 
 ```json
 {
-  "task": {
-    "id": 1,
-    "title": "Go on my daily walk 🏞",
-    "description": "Notice something new every day",
-    "is_complete": true
-  }
+  "id": 1,
+  "title": "Go on my daily walk 🏞",
+  "description": "Notice something new every day",
+  "is_complete": true
 }
 ```
 
-Notice the same dictionary structure for the Task data as in our wave 1 routes. We should be able to use any response model helper that we are using in other Task routes to help build this response.
-
-Also notice that fundamentally, this route requires that we look up a model by its ID, and then update that model. We should be able to reuse the same route helper methods that we have been using in other Task routes to help build this route.
-
 ### Mark Incomplete on an Incomplete Task
 
 Given a task that has:
@@ -138,19 +132,13 @@ After I have made the `PATCH` request, I can submit a `GET` request to `/tasks/1
 
 ```json
 {
-  "task": {
-    "id": 1,
-    "title": "Go on my daily walk 🏞",
-    "description": "Notice something new every day",
-    "is_complete": false
-  }
+  "id": 1,
+  "title": "Go on my daily walk 🏞",
+  "description": "Notice something new every day",
+  "is_complete": false
 }
 ```
 
-Notice the same dictionary structure for the Task data as in our wave 1 routes. We should be able to use any response model helper that we are using in other Task routes to help build this response.
-
-Also notice that fundamentally, this route requires that we look up a model by its ID, and then update that model. We should be able to reuse the same route helper methods that we have been using in other Task routes to help build this route.
-
 ## Mark Complete and Mark Incomplete for Missing Tasks
 
 Given that there are no tasks with the ID `1`,