Update Wave docs to reflect that PUT/PATCH/DELETE endpoints should use as the expected response.

Author: kelsey-steven-ada

ada-project-docs/wave_01.md

@@ -150,32 +150,19 @@ As a client, I want to be able to make a `PUT` request to `/tasks/1` when there
 
 and get this response:
 
-`200 OK`
+`204 No Content`
 
-```json
-{
-  "task": {
-    "id": 1,
-    "title": "Updated Task Title",
-    "description": "Updated Test Description",
-    "is_complete": false
-  }
-}
-```
+The response should have a mimetype of "application/json" to keep our API response type consistent.
 
 Note that the update endpoint does update the `completed_at` attribute. This will be updated with custom endpoints implemented in Wave 3.
 
 #### Delete Task: Deleting a Task
 
 As a client, I want to be able to make a `DELETE` request to `/tasks/1` when there is at least one saved task and get this response:
 
-`200 OK`
+`204 No Content`
 
-```json
-{
-  "details": "Task 1 \"Go on my daily walk 🏞\" successfully deleted"
-}
-```
+The response should have a mimetype of "application/json" to keep our API response type consistent.
 
 #### No Matching Task: Get, Update, and Delete
 

ada-project-docs/wave_03.md

@@ -34,6 +34,12 @@ when I send a `PATCH` request to `/tasks/1/mark_complete`,
 
 then the task is updated, so that its `completed_at` value is the current date, and I get this response:
 
+`204 No Content`
+
+The response should have a mimetype of "application/json" to keep our API response type consistent.
+
+If after the `PATCH` request I fetch the task by sending a `GET` request to `/tasks/1`, I get this response:
+
 `200 OK`
 
 ```json
@@ -58,6 +64,12 @@ when I send a `PATCH` request to `/tasks/1/mark_incomplete`,
 
 then the task is updated, so that its `completed_at` value is `null`/`None`, and I get this response:
 
+`204 No Content`
+
+The response should have a mimetype of "application/json" to keep our API response type consistent.
+
+If after the `PATCH` request I fetch the task by sending a `GET` request to `/tasks/1`, I get this response:
+
 `200 OK`
 
 ```json
@@ -82,6 +94,12 @@ when I send a `PATCH` request to `/tasks/1/mark_complete`,
 
 then I want this to behave exactly like `/tasks/1/mark_complete` for an incomplete task. The task is updated, so that its `completed_at` value is the current date, and I get this response:
 
+`204 No Content`
+
+The response should have a mimetype of "application/json" to keep our API response type consistent.
+
+If after the `PATCH` request I fetch the task by sending a `GET` request to `/tasks/1`, I get this response:
+
 `200 OK`
 
 ```json
@@ -106,6 +124,12 @@ when I send a `PATCH` request to `/tasks/1/mark_incomplete`,
 
 then I want this to behave exactly like `/tasks/1/mark_incomplete` for a complete task. Its `completed_at` value remains as `null`/`None`, and I get this response:
 
+`204 No Content`
+
+The response should have a mimetype of "application/json" to keep our API response type consistent.
+
+If after the `PATCH` request I fetch the task by sending a `GET` request to `/tasks/1`, I get this response:
+
 `200 OK`
 
 ```json

ada-project-docs/wave_05.md

@@ -125,28 +125,17 @@ As a client, I want to be able to make a `PUT` request to `/goals/1` when there
 
 and get this response:
 
-`200 OK`
+`204 No Content`
 
-```json
-{
-  "goal": {
-    "id": 1,
-    "title": "Updated Goal Title"
-  }
-}
-```
+The response should have a mimetype of "application/json" to keep our API response type consistent.
 
 ### Delete Goal: Deleting a Goal
 
 As a client, I want to be able to make a `DELETE` request to `/goals/1` when there is at least one saved goal and get this response:
 
-`200 OK`
+`204 No Content`
 
-```json
-{
-  "details": "Goal 1 \"Build a habit of going outside daily\" successfully deleted"
-}
-```
+The response should have a mimetype of "application/json" to keep our API response type consistent.
 
 ### No matching Goal: Get, Update, and Delete