Docs: Update hint-content-type (fix #3187)

packages/hint-content-type/README.md

@@ -8,18 +8,18 @@ the appropriate media type and charset for the response.
 
 Even though browsers sometimes [ignore][server configs] the value of
 the `Content-Type` header and try to [sniff the content][mime sniffing
-spec], it’s indicated to always send the appropriate media type and
+spec] (see also: [`X-Content-Type-Options` hint][x content type options]), it’s indicated to always send the appropriate media type and
 charset for the response as, among other:
 
-* [resources served with the wrong media type may be blocked][blocked
-  resources] (see also: [`X-Content-Type-Options`
-  hint][x content type options]), or the official [media type
-  may be required][required media type]
+* the media type defines both the data format and how that data is intended to be processed by browsers
 
 * not sending the appropriate `charset`, where appropriate, may
   [prevent things from being rendered correctly][incorrect rendering]
   thus creating a bad user experience (see also:
   [`meta-charset-utf-8` hint][meta charset hint])
+
+* javascript resources served with the wrong media type [may be blocked][blocked
+  resources]
 
 ## What does the hint check?
 
@@ -474,7 +474,6 @@ your project.
 [ietf js mime draft]: https://tools.ietf.org/html/draft-ietf-dispatch-javascript-mjs
 [incorrect rendering]: https://www.w3.org/International/questions/qa-what-is-encoding
 [mime sniffing spec]: https://mimesniff.spec.whatwg.org/
-[required media type]: https://developer.mozilla.org/en-US/docs/Web/HTML/Using_the_application_cache#Referencing_a_cache_manifest_file
 [rfc 4329]: https://tools.ietf.org/html/rfc4329
 [server configs]: https://developer.mozilla.org/en-US/docs/Web/Security/Securing_your_site/Configuring_server_MIME_types
 [hintrc]: https://webhint.io/docs/user-guide/configuring-webhint/summary/