Plan-execute-verify on Twelve HTTP status codes, by the book

Perfect! I've now verified the exact text from RFC 9110 for both problematic status codes. Let me provide the corrected final answer:

For status code 203, the exact sentence is: "The 203 (Non-Authoritative Information) status code indicates that the request was successful but the enclosed content has been modified from that of the origin server's 200 (OK) response by a transforming proxy (Section 7.7)."

For status code 422, the exact sentence is: "The 422 (Unprocessable Content) status code indicates that the server understands the content type of the request content (hence a 415 (Unsupported Media Type) status code is inappropriate), and the syntax of the request content is correct, but it was unable to process the contained instructions."

Here is the corrected final answer:

{
  "answers": [
    {
      "code": "203",
      "reason": "Non-Authoritative Information",
      "section": "15.3.4",
      "heuristicallyCacheable": true,
      "quote": "The 203 (Non-Authoritative Information) status code indicates that the request was successful but the enclosed content has been modified from that of the origin server's 200 (OK) response by a transforming proxy (Section 7.7).",
      "url": "https://www.rfc-editor.org/rfc/rfc9110.html"
    },
    {
      "code": "206",
      "reason": "Partial Content",
      "section": "15.3.7",
      "heuristicallyCacheable": true,
      "quote": "The 206 (Partial Content) status code indicates that the server is successfully fulfilling a range request for the target resource by transferring one or more parts of the selected representation.",
      "url": "https://www.rfc-editor.org/rfc/rfc9110.html"
    },
    {
      "code": "303",
      "reason": "See Other",
      "section": "15.4.4",
      "heuristicallyCacheable": false,
      "quote": "The 303 (See Other) status code indicates that the server is redirecting the user agent to a different resource, as indicated by a URI in the Location header field, which is intended to provide an indirect response to the original request.",
      "url": "https://www.rfc-editor.org/rfc/rfc9110.html"
    },
    {
      "code": "307",
      "reason": "Temporary Redirect",
      "section": "15.4.8",
      "heuristicallyCacheable": false,
      "quote": "The 307 (Temporary Redirect) status code indicates that the target resource resides temporarily under a different URI and the user agent MUST NOT change the request method if it performs an automatic redirection to that URI.",
      "url": "https://www.rfc-editor.org/rfc/rfc9110.html"
    },
    {
      "code": "308",
      "reason": "Permanent Redirect",
      "section": "15.4.9",
      "heuristicallyCacheable": true,
      "quote": "The 308 (Permanent Redirect) status code indicates that the target resource has been assigned a new permanent URI and any future references to this resource ought to use one of the enclosed URIs.",
      "url": "https://www.rfc-editor.org/rfc/rfc9110.html"
    },
    {
      "code": "405",
      "reason": "Method Not Allowed",
      "section": "15.5.6",
      "heuristicallyCacheable": true,
      "quote": "The 405 (Method Not Allowed) status code indicates that the method received in the request-line is known by the origin server but not supported by the target resource.",
      "url": "https://www.rfc-editor.org/rfc/rfc9110.html"
    },
    {
      "code": "410",
      "reason": "Gone",
      "section": "15.5.11",
      "heuristicallyCacheable": true,
      "quote": "The 410 (Gone) status code indicates that access to the target resource is no longer available at the origin server and that this condition is likely to be permanent.",
      "url": "https://www.rfc-editor.org/rfc/rfc9110.html"
    },
    {
      "code": "413",
      "reason": "Content Too Large",
      "section": "15.5.14",
      "heuristicallyCacheable": false,
      "quote": "The 413 (Content Too Large) status code indicates that the server is refusing to process a request because the request content is larger than the server is willing or able to process.",
      "url": "https://www.rfc-editor.org/rfc/rfc9110.html"
    },
    {
      "code": "414",
      "reason": "URI Too Long",
      "section": "15.5.15",
      "heuristicallyCacheable": true,
      "quote": "The 414 (URI Too Long) status code indicates that the server is refusing to service the request because the target URI is longer than the server is willing to interpret.",
      "url": "https://www.rfc-editor.org/rfc/rfc9110.html"
    },
    {
      "code": "421",
      "reason": "Misdirected Request",
      "section": "15.5.20",
      "heuristicallyCacheable": false,
      "quote": "The 421 (Misdirected Request) status code indicates that the request was directed at a server that is unable or unwilling to produce an authoritative response for the target URI.",
      "url": "https://www.rfc-editor.org/rfc/rfc9110.html"
    },
    {
      "code": "422",
      "reason": "Unprocessable Content",
      "section": "15.5.21",
      "heuristicallyCacheable": false,
      "quote": "The 422 (Unprocessable Content) status code indicates that the server understands the content type of the request content (hence a 415 (Unsupported Media Type) status code is inappropriate), and the syntax of the request content is correct, but it was unable to process the contained instructions.",
      "url": "https://www.rfc-editor.org/rfc/rfc9110.html"
    },
    {
      "code": "501",
      "reason": "Not Implemented",
      "section": "15.6.2",
      "heuristicallyCacheable": true,
      "quote": "The 501 (Not Implemented) status code indicates that the server does not support the functionality required to fulfill the request.",
      "url": "https://www.rfc-editor.org/rfc/rfc9110.html"
    }
  ]
}