http-response-serializer documentation incorrect

[Jason Williscroft]

Describe the bug

The http-response-serializer documentation page Content Type Negotiation section is incorrect.

Additional context

This section states:

The content type is determined in the following order:

• context.requiredContentType -- allows the handler to override everything else
• The Accept header via accept
• context.preferredContentType -- allows the handler to override the default, but lets the request ask first
• defaultContentType middleware configuration

If you look at the code, the context properties listed above are actually event properties.

[will Farrell]

Thanks for reporting! I see the issue. I should be able to put together an update before the end of the week.