@@ -38,7 +38,7 @@ then the task is updated, so that its `completed_at` value is the current date,
3838
3939The response should have a mimetype of "application/json" to keep our API response type consistent.
4040
41- If after the ` PATCH ` request I fetch the task by sending a ` GET ` request to ` /tasks/1 ` , I get this response:
41+ After I have made the ` PATCH ` request, I can submit a ` GET ` request to ` /tasks/1 ` , which will return the response:
4242
4343` 200 OK `
4444
@@ -68,7 +68,7 @@ then the task is updated, so that its `completed_at` value is `null`/`None`, and
6868
6969The response should have a mimetype of "application/json" to keep our API response type consistent.
7070
71- If after the ` PATCH ` request I fetch the task by sending a ` GET ` request to ` /tasks/1 ` , I get this response:
71+ After I have made the ` PATCH ` request, I can submit a ` GET ` request to ` /tasks/1 ` , which will return the response:
7272
7373` 200 OK `
7474
@@ -98,7 +98,7 @@ then I want this to behave exactly like `/tasks/1/mark_complete` for an incomple
9898
9999The response should have a mimetype of "application/json" to keep our API response type consistent.
100100
101- If after the ` PATCH ` request I fetch the task by sending a ` GET ` request to ` /tasks/1 ` , I get this response:
101+ After I have made the ` PATCH ` request, I can submit a ` GET ` request to ` /tasks/1 ` , which will return the response:
102102
103103` 200 OK `
104104
@@ -128,7 +128,7 @@ then I want this to behave exactly like `/tasks/1/mark_incomplete` for a complet
128128
129129The response should have a mimetype of "application/json" to keep our API response type consistent.
130130
131- If after the ` PATCH ` request I fetch the task by sending a ` GET ` request to ` /tasks/1 ` , I get this response:
131+ After I have made the ` PATCH ` request, I can submit a ` GET ` request to ` /tasks/1 ` , which will return the response:
132132
133133` 200 OK `
134134
0 commit comments