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

Co-authored-by: Luca Chang <[email protected]>

Author: He-Pin

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

@@ -113,7 +113,7 @@ Tool calls are given special consideration for the purpose of task augmentation.
 This is to be interpreted as a fine-grained layer in addition to capabilities, following these rules:
 
 1. If a server's capabilities include `tasks.requests.tools.call`, then clients **MUST NOT** attempt to use task augmentation on that server's tools, regardless of the `taskHint` value.
-1. If a server's capabilities don't include `tasks.requests.tools.call`, then clients consider the value of `taskHint`, and handle it accordingly:
+1. If a server's capabilities include `tasks.requests.tools.call`, then clients consider the value of `taskHint`, and handle it accordingly:
    1. If `taskHint` is not present or `"never"`, clients **MUST NOT** attempt to invoke the tool as a task. Servers **SHOULD** return a `-32601` (Method not found) error if a client attempts to do so. This is the default behavior.
    1. If `taskHint` is `"optional"`, clients **MAY** invoke the tool as a task or as a normal request.
    1. If `taskHint` is `"always"`, clients **SHOULD** invoke the tool as a task. Servers **MAY** return a `-32601` (Method not found) error if a client does not attempt to do so.