Apply suggestions from code review

Co-authored-by: Jonathan Hefner <[email protected]>

Author: LucaButBoring

docs/specification/draft/basic/utilities/tasks.mdx

@@ -8,7 +8,7 @@ title: Tasks
 
 <Note>
 
-Tasks are newly-introduced in this version of the MCP specification and are currently considered **experimental**.
+Tasks were introduced in version 2025-11-25 of the MCP specification and are currently considered **experimental**.
 The design and behavior of tasks may evolve in future protocol versions.
 
 </Note>
@@ -167,7 +167,7 @@ To create a task, requestors send a request with the `task` field included in th
 }
 ```
 
-When a receiver accepts a task-augmented request, it returns a `CreateTaskResult` containing task metadata. The response does not include the actual operation result. The actual result (e.g., tool result for `tools/call`) becomes available only through `tasks/result` after the task completes.
+When a receiver accepts a task-augmented request, it returns a [`CreateTaskResult`](/specification/draft/schema#createtaskresult) containing task metadata. The response does not include the actual operation result. The actual result (e.g., tool result for `tools/call`) becomes available only through `tasks/result` after the task completes.
 
 <Note>
 
@@ -219,7 +219,7 @@ Requestors **SHOULD** continue polling until the task reaches a terminal status
 
 ### Retrieving Task Results
 
-After a task completes the operation result is retrieved via `tasks/result`. This is distinct from the initial `CreateTaskResult` response, which contains only task metadata. The result structure matches the original request type (e.g., `CallToolResult` for `tools/call`).
+After a task completes the operation result is retrieved via [`tasks/result`](/specification/draft/schema#tasks%2Fresult). This is distinct from the initial `CreateTaskResult` response, which contains only task metadata. The result structure matches the original request type (e.g., `CallToolResult` for `tools/call`).
 
 To retrieve the result of a completed task, requestors can send a `tasks/result` request:
 
@@ -261,7 +261,7 @@ To retrieve the result of a completed task, requestors can send a `tasks/result`
 
 ### Task Status Notification
 
-When a task status changes, receivers **MAY** send a `notifications/tasks/status` notification to inform the requestor of the change. This notification includes the full task state.
+When a task status changes, receivers **MAY** send a [`notifications/tasks/status`](/specification/draft/schema#notifications%2Ftasks%2Fstatus) notification to inform the requestor of the change. This notification includes the full task state.
 
 **Notification:**
 
@@ -285,7 +285,7 @@ Requestors **MUST NOT** rely on receiving this notifications, as it is optional.
 
 ### Listing Tasks
 
-To retrieve a list of tasks, requestors can send a `tasks/list` request. This operation supports pagination.
+To retrieve a list of tasks, requestors can send a [`tasks/list`](/specification/draft/schema#tasks%2Flist) request. This operation supports pagination.
 
 **Request:**
 
@@ -329,7 +329,7 @@ To retrieve a list of tasks, requestors can send a `tasks/list` request. This op
 
 ### Cancelling Tasks
 
-To explicitly cancel a task, requestors can send a `tasks/cancel` request.
+To explicitly cancel a task, requestors can send a [`tasks/cancel`](/specification/draft/schema#tasks%2Fcancel) request.
 
 **Request:**