Update specification.md

Co-authored-by: Ricardo Zanini <[email protected]>

Author: cdavernas

specification.md

@@ -4464,7 +4464,7 @@ Represents the workflow's error handling configuration, including error definiti
 | instance | An [RFC 6901 JSON pointer](https://datatracker.ietf.org/doc/html/rfc6901) that precisely identifies the component within a workflow definition (ex: funcRef, subflowRef, ...) from which the described error originates. | string | yes, but is added by runtime when throwing an error |
 | type | An [RFC 3986](https://datatracker.ietf.org/doc/html/rfc3986) URI reference that identifies the error type. The [RFC 7807 Problem Details specification](https://datatracker.ietf.org/doc/html/rfc7807) encourages that, when dereferenced, it provides human-readable documentation for the error type (e.g., using HTML). The specification strongly recommends using [default error types](#error-types) for cross-compatibility concerns. | string | yes |
 | status | The status code generated by the origin for the occurrence of an error. Status codes are extensible by nature and runtimes are not required to understand the meaning of all defined status codes. However, for cross-compatibility concerns, the specification encourages using [RFC 7231 HTTP Status Codes](https://datatracker.ietf.org/doc/html/rfc7231). | string | yes |
-| title | A short, human-readable summary of a error type. It SHOULD NOT change from occurrence to occurrence of an error, except for purposes of localization. | string | no |
+| title | A short, human-readable summary of an error type. It SHOULD NOT change from occurrence to occurrence of an error, except for purposes of localization. | string | no |
 | detail | A human-readable explanation specific to an occurrence of an error. | string | no |
 
 <details><summary><strong>Click to view example definition</strong></summary>