From f9e79432440db4b9befe29be58ad3745d93e710c Mon Sep 17 00:00:00 2001
From: Jean-Yves Perrier <jypenator@gmail.com>
Date: Thu, 12 Aug 2021 12:27:43 +0200
Subject: [PATCH 1/9] Rename HTTP docs from html to md

---
 files/en-us/web/http/authentication/{index.html => index.md}      | 0
 .../{index.html => index.md}                                      | 0
 .../web/http/basics_of_http/data_uris/{index.html => index.md}    | 0
 .../basics_of_http/evolution_of_http/{index.html => index.md}     | 0
 .../identifying_resources_on_the_web/{index.html => index.md}     | 0
 files/en-us/web/http/basics_of_http/{index.html => index.md}      | 0
 .../mime_types/common_types/{index.html => index.md}              | 0
 .../web/http/basics_of_http/mime_types/{index.html => index.md}   | 0
 .../http/basics_of_http/resource_urls/{index.html => index.md}    | 0
 .../{index.html => index.md}                                      | 0
 files/en-us/web/http/caching/{index.html => index.md}             | 0
 files/en-us/web/http/compression/{index.html => index.md}         | 0
 .../en-us/web/http/conditional_requests/{index.html => index.md}  | 0
 .../configuring_servers_for_ogg_media/{index.html => index.md}    | 0
 .../connection_management_in_http_1.x/{index.html => index.md}    | 0
 files/en-us/web/http/content_negotiation/{index.html => index.md} | 0
 .../list_of_default_accept_values/{index.html => index.md}        | 0
 files/en-us/web/http/cookies/{index.html => index.md}             | 0
 .../corsalloworiginnotmatchingorigin/{index.html => index.md}     | 0
 .../http/cors/errors/corsdidnotsucceed/{index.html => index.md}   | 0
 .../web/http/cors/errors/corsdisabled/{index.html => index.md}    | 0
 .../corsexternalredirectnotallowed/{index.html => index.md}       | 0
 .../cors/errors/corsinvalidallowheader/{index.html => index.md}   | 0
 .../cors/errors/corsinvalidallowmethod/{index.html => index.md}   | 0
 .../http/cors/errors/corsmethodnotfound/{index.html => index.md}  | 0
 .../errors/corsmissingallowcredentials/{index.html => index.md}   | 0
 .../corsmissingallowheaderfrompreflight/{index.html => index.md}  | 0
 .../cors/errors/corsmissingalloworigin/{index.html => index.md}   | 0
 .../corsmultiplealloworiginnotallowed/{index.html => index.md}    | 0
 .../errors/corsnotsupportingcredentials/{index.html => index.md}  | 0
 .../cors/errors/corsoriginheadernotadded/{index.html => index.md} | 0
 .../errors/corspreflightdidnotsucceed/{index.html => index.md}    | 0
 .../http/cors/errors/corsrequestnothttp/{index.html => index.md}  | 0
 files/en-us/web/http/cors/errors/{index.html => index.md}         | 0
 files/en-us/web/http/cors/{index.html => index.md}                | 0
 .../cross-origin_resource_policy_(corp)/{index.html => index.md}  | 0
 .../web/http/csp/errors/cspviolation/{index.html => index.md}     | 0
 files/en-us/web/http/csp/errors/{index.html => index.md}          | 0
 files/en-us/web/http/csp/{index.html => index.md}                 | 0
 files/en-us/web/http/feature_policy/{index.html => index.md}      | 0
 .../feature_policy/using_feature_policy/{index.html => index.md}  | 0
 .../web/http/headers/accept-ch-lifetime/{index.html => index.md}  | 0
 files/en-us/web/http/headers/accept-ch/{index.html => index.md}   | 0
 .../web/http/headers/accept-charset/{index.html => index.md}      | 0
 .../web/http/headers/accept-encoding/{index.html => index.md}     | 0
 .../web/http/headers/accept-language/{index.html => index.md}     | 0
 .../en-us/web/http/headers/accept-patch/{index.html => index.md}  | 0
 files/en-us/web/http/headers/accept-post/{index.html => index.md} | 0
 .../en-us/web/http/headers/accept-ranges/{index.html => index.md} | 0
 files/en-us/web/http/headers/accept/{index.html => index.md}      | 0
 .../access-control-allow-credentials/{index.html => index.md}     | 0
 .../headers/access-control-allow-headers/{index.html => index.md} | 0
 .../headers/access-control-allow-methods/{index.html => index.md} | 0
 .../headers/access-control-allow-origin/{index.html => index.md}  | 0
 .../access-control-expose-headers/{index.html => index.md}        | 0
 .../http/headers/access-control-max-age/{index.html => index.md}  | 0
 .../access-control-request-headers/{index.html => index.md}       | 0
 .../access-control-request-method/{index.html => index.md}        | 0
 files/en-us/web/http/headers/age/{index.html => index.md}         | 0
 files/en-us/web/http/headers/allow/{index.html => index.md}       | 0
 files/en-us/web/http/headers/alt-svc/{index.html => index.md}     | 0
 .../en-us/web/http/headers/authorization/{index.html => index.md} | 0
 .../en-us/web/http/headers/cache-control/{index.html => index.md} | 0
 .../web/http/headers/clear-site-data/{index.html => index.md}     | 0
 files/en-us/web/http/headers/connection/{index.html => index.md}  | 0
 .../web/http/headers/content-disposition/{index.html => index.md} | 0
 files/en-us/web/http/headers/content-dpr/{index.html => index.md} | 0
 .../web/http/headers/content-encoding/{index.html => index.md}    | 0
 .../web/http/headers/content-language/{index.html => index.md}    | 0
 .../web/http/headers/content-length/{index.html => index.md}      | 0
 .../web/http/headers/content-location/{index.html => index.md}    | 0
 .../en-us/web/http/headers/content-range/{index.html => index.md} | 0
 .../content-security-policy-report-only/{index.html => index.md}  | 0
 .../content-security-policy/base-uri/{index.html => index.md}     | 0
 .../block-all-mixed-content/{index.html => index.md}              | 0
 .../content-security-policy/child-src/{index.html => index.md}    | 0
 .../content-security-policy/connect-src/{index.html => index.md}  | 0
 .../content-security-policy/default-src/{index.html => index.md}  | 0
 .../content-security-policy/font-src/{index.html => index.md}     | 0
 .../content-security-policy/form-action/{index.html => index.md}  | 0
 .../frame-ancestors/{index.html => index.md}                      | 0
 .../content-security-policy/frame-src/{index.html => index.md}    | 0
 .../content-security-policy/img-src/{index.html => index.md}      | 0
 .../http/headers/content-security-policy/{index.html => index.md} | 0
 .../content-security-policy/manifest-src/{index.html => index.md} | 0
 .../content-security-policy/media-src/{index.html => index.md}    | 0
 .../content-security-policy/navigate-to/{index.html => index.md}  | 0
 .../content-security-policy/object-src/{index.html => index.md}   | 0
 .../content-security-policy/plugin-types/{index.html => index.md} | 0
 .../content-security-policy/prefetch-src/{index.html => index.md} | 0
 .../content-security-policy/referrer/{index.html => index.md}     | 0
 .../content-security-policy/report-to/{index.html => index.md}    | 0
 .../content-security-policy/report-uri/{index.html => index.md}   | 0
 .../require-sri-for/{index.html => index.md}                      | 0
 .../require-trusted-types-for/{index.html => index.md}            | 0
 .../content-security-policy/sandbox/{index.html => index.md}      | 0
 .../script-src-attr/{index.html => index.md}                      | 0
 .../script-src-elem/{index.html => index.md}                      | 0
 .../content-security-policy/script-src/{index.html => index.md}   | 0
 .../style-src-attr/{index.html => index.md}                       | 0
 .../style-src-elem/{index.html => index.md}                       | 0
 .../content-security-policy/style-src/{index.html => index.md}    | 0
 .../trusted-types/{index.html => index.md}                        | 0
 .../upgrade-insecure-requests/{index.html => index.md}            | 0
 .../content-security-policy/worker-src/{index.html => index.md}   | 0
 .../en-us/web/http/headers/content-type/{index.html => index.md}  | 0
 files/en-us/web/http/headers/cookie/{index.html => index.md}      | 0
 files/en-us/web/http/headers/cookie2/{index.html => index.md}     | 0
 .../headers/cross-origin-embedder-policy/{index.html => index.md} | 0
 .../headers/cross-origin-opener-policy/{index.html => index.md}   | 0
 .../headers/cross-origin-resource-policy/{index.html => index.md} | 0
 files/en-us/web/http/headers/date/{index.html => index.md}        | 0
 .../en-us/web/http/headers/device-memory/{index.html => index.md} | 0
 files/en-us/web/http/headers/digest/{index.html => index.md}      | 0
 files/en-us/web/http/headers/dnt/{index.html => index.md}         | 0
 files/en-us/web/http/headers/downlink/{index.html => index.md}    | 0
 files/en-us/web/http/headers/dpr/{index.html => index.md}         | 0
 files/en-us/web/http/headers/early-data/{index.html => index.md}  | 0
 files/en-us/web/http/headers/ect/{index.html => index.md}         | 0
 files/en-us/web/http/headers/etag/{index.html => index.md}        | 0
 files/en-us/web/http/headers/expect-ct/{index.html => index.md}   | 0
 files/en-us/web/http/headers/expect/{index.html => index.md}      | 0
 files/en-us/web/http/headers/expires/{index.html => index.md}     | 0
 .../headers/feature-policy/accelerometer/{index.html => index.md} | 0
 .../feature-policy/ambient-light-sensor/{index.html => index.md}  | 0
 .../http/headers/feature-policy/autoplay/{index.html => index.md} | 0
 .../http/headers/feature-policy/battery/{index.html => index.md}  | 0
 .../http/headers/feature-policy/camera/{index.html => index.md}   | 0
 .../feature-policy/display-capture/{index.html => index.md}       | 0
 .../feature-policy/document-domain/{index.html => index.md}       | 0
 .../feature-policy/encrypted-media/{index.html => index.md}       | 0
 .../headers/feature-policy/fullscreen/{index.html => index.md}    | 0
 .../http/headers/feature-policy/gamepad/{index.html => index.md}  | 0
 .../headers/feature-policy/geolocation/{index.html => index.md}   | 0
 .../headers/feature-policy/gyroscope/{index.html => index.md}     | 0
 .../web/http/headers/feature-policy/{index.html => index.md}      | 0
 .../feature-policy/layout-animations/{index.html => index.md}     | 0
 .../feature-policy/legacy-image-formats/{index.html => index.md}  | 0
 .../headers/feature-policy/magnetometer/{index.html => index.md}  | 0
 .../headers/feature-policy/microphone/{index.html => index.md}    | 0
 .../web/http/headers/feature-policy/midi/{index.html => index.md} | 0
 .../feature-policy/oversized-images/{index.html => index.md}      | 0
 .../http/headers/feature-policy/payment/{index.html => index.md}  | 0
 .../feature-policy/picture-in-picture/{index.html => index.md}    | 0
 .../publickey-credentials-get/{index.html => index.md}            | 0
 .../feature-policy/screen-wake-lock/{index.html => index.md}      | 0
 .../http/headers/feature-policy/sync-xhr/{index.html => index.md} | 0
 .../feature-policy/unoptimized-images/{index.html => index.md}    | 0
 .../headers/feature-policy/unsized-media/{index.html => index.md} | 0
 .../web/http/headers/feature-policy/usb/{index.html => index.md}  | 0
 .../http/headers/feature-policy/vibrate/{index.html => index.md}  | 0
 .../web/http/headers/feature-policy/vr/{index.html => index.md}   | 0
 .../headers/feature-policy/web-share/{index.html => index.md}     | 0
 .../feature-policy/xr-spatial-tracking/{index.html => index.md}   | 0
 .../web/http/headers/feature-policy/xr/{index.html => index.md}   | 0
 files/en-us/web/http/headers/forwarded/{index.html => index.md}   | 0
 files/en-us/web/http/headers/from/{index.html => index.md}        | 0
 files/en-us/web/http/headers/host/{index.html => index.md}        | 0
 files/en-us/web/http/headers/if-match/{index.html => index.md}    | 0
 .../web/http/headers/if-modified-since/{index.html => index.md}   | 0
 .../en-us/web/http/headers/if-none-match/{index.html => index.md} | 0
 files/en-us/web/http/headers/if-range/{index.html => index.md}    | 0
 .../web/http/headers/if-unmodified-since/{index.html => index.md} | 0
 files/en-us/web/http/headers/{index.html => index.md}             | 0
 files/en-us/web/http/headers/keep-alive/{index.html => index.md}  | 0
 .../web/http/headers/large-allocation/{index.html => index.md}    | 0
 .../en-us/web/http/headers/last-modified/{index.html => index.md} | 0
 files/en-us/web/http/headers/link/{index.html => index.md}        | 0
 files/en-us/web/http/headers/location/{index.html => index.md}    | 0
 files/en-us/web/http/headers/nel/{index.html => index.md}         | 0
 files/en-us/web/http/headers/origin/{index.html => index.md}      | 0
 files/en-us/web/http/headers/pragma/{index.html => index.md}      | 0
 .../web/http/headers/proxy-authenticate/{index.html => index.md}  | 0
 .../web/http/headers/proxy-authorization/{index.html => index.md} | 0
 .../headers/public-key-pins-report-only/{index.html => index.md}  | 0
 .../web/http/headers/public-key-pins/{index.html => index.md}     | 0
 files/en-us/web/http/headers/range/{index.html => index.md}       | 0
 files/en-us/web/http/headers/referer/{index.html => index.md}     | 0
 .../web/http/headers/referrer-policy/{index.html => index.md}     | 0
 files/en-us/web/http/headers/retry-after/{index.html => index.md} | 0
 files/en-us/web/http/headers/rtt/{index.html => index.md}         | 0
 files/en-us/web/http/headers/save-data/{index.html => index.md}   | 0
 .../web/http/headers/sec-fetch-dest/{index.html => index.md}      | 0
 .../web/http/headers/sec-fetch-mode/{index.html => index.md}      | 0
 .../web/http/headers/sec-fetch-site/{index.html => index.md}      | 0
 .../web/http/headers/sec-fetch-user/{index.html => index.md}      | 0
 .../http/headers/sec-websocket-accept/{index.html => index.md}    | 0
 .../en-us/web/http/headers/server-timing/{index.html => index.md} | 0
 files/en-us/web/http/headers/server/{index.html => index.md}      | 0
 files/en-us/web/http/headers/set-cookie/{index.html => index.md}  | 0
 .../web/http/headers/set-cookie/samesite/{index.html => index.md} | 0
 files/en-us/web/http/headers/set-cookie2/{index.html => index.md} | 0
 files/en-us/web/http/headers/sourcemap/{index.html => index.md}   | 0
 .../headers/strict-transport-security/{index.html => index.md}    | 0
 files/en-us/web/http/headers/te/{index.html => index.md}          | 0
 .../web/http/headers/timing-allow-origin/{index.html => index.md} | 0
 files/en-us/web/http/headers/tk/{index.html => index.md}          | 0
 files/en-us/web/http/headers/trailer/{index.html => index.md}     | 0
 .../web/http/headers/transfer-encoding/{index.html => index.md}   | 0
 .../headers/upgrade-insecure-requests/{index.html => index.md}    | 0
 files/en-us/web/http/headers/upgrade/{index.html => index.md}     | 0
 .../web/http/headers/user-agent/firefox/{index.html => index.md}  | 0
 files/en-us/web/http/headers/user-agent/{index.html => index.md}  | 0
 files/en-us/web/http/headers/vary/{index.html => index.md}        | 0
 files/en-us/web/http/headers/via/{index.html => index.md}         | 0
 .../web/http/headers/viewport-width/{index.html => index.md}      | 0
 files/en-us/web/http/headers/want-digest/{index.html => index.md} | 0
 files/en-us/web/http/headers/warning/{index.html => index.md}     | 0
 files/en-us/web/http/headers/width/{index.html => index.md}       | 0
 .../web/http/headers/www-authenticate/{index.html => index.md}    | 0
 .../http/headers/x-content-type-options/{index.html => index.md}  | 0
 .../http/headers/x-dns-prefetch-control/{index.html => index.md}  | 0
 .../web/http/headers/x-forwarded-for/{index.html => index.md}     | 0
 .../web/http/headers/x-forwarded-host/{index.html => index.md}    | 0
 .../web/http/headers/x-forwarded-proto/{index.html => index.md}   | 0
 .../web/http/headers/x-frame-options/{index.html => index.md}     | 0
 .../web/http/headers/x-xss-protection/{index.html => index.md}    | 0
 files/en-us/web/http/{index.html => index.md}                     | 0
 files/en-us/web/http/index/{index.html => index.md}               | 0
 .../en-us/web/http/link_prefetching_faq/{index.html => index.md}  | 0
 files/en-us/web/http/messages/{index.html => index.md}            | 0
 files/en-us/web/http/methods/connect/{index.html => index.md}     | 0
 files/en-us/web/http/methods/delete/{index.html => index.md}      | 0
 files/en-us/web/http/methods/get/{index.html => index.md}         | 0
 files/en-us/web/http/methods/head/{index.html => index.md}        | 0
 files/en-us/web/http/methods/{index.html => index.md}             | 0
 files/en-us/web/http/methods/options/{index.html => index.md}     | 0
 files/en-us/web/http/methods/patch/{index.html => index.md}       | 0
 files/en-us/web/http/methods/post/{index.html => index.md}        | 0
 files/en-us/web/http/methods/put/{index.html => index.md}         | 0
 files/en-us/web/http/methods/trace/{index.html => index.md}       | 0
 .../en-us/web/http/network_error_logging/{index.html => index.md} | 0
 files/en-us/web/http/overview/{index.html => index.md}            | 0
 .../web/http/protocol_upgrade_mechanism/{index.html => index.md}  | 0
 .../web/http/proxy_servers_and_tunneling/{index.html => index.md} | 0
 .../proxy_auto-configuration_pac_file/{index.html => index.md}    | 0
 files/en-us/web/http/public_key_pinning/{index.html => index.md}  | 0
 files/en-us/web/http/range_requests/{index.html => index.md}      | 0
 files/en-us/web/http/redirections/{index.html => index.md}        | 0
 .../http/resources_and_specifications/{index.html => index.md}    | 0
 files/en-us/web/http/resources_and_uris/{index.html => index.md}  | 0
 files/en-us/web/http/session/{index.html => index.md}             | 0
 files/en-us/web/http/status/100/{index.html => index.md}          | 0
 files/en-us/web/http/status/101/{index.html => index.md}          | 0
 files/en-us/web/http/status/103/{index.html => index.md}          | 0
 files/en-us/web/http/status/200/{index.html => index.md}          | 0
 files/en-us/web/http/status/201/{index.html => index.md}          | 0
 files/en-us/web/http/status/202/{index.html => index.md}          | 0
 files/en-us/web/http/status/203/{index.html => index.md}          | 0
 files/en-us/web/http/status/204/{index.html => index.md}          | 0
 files/en-us/web/http/status/205/{index.html => index.md}          | 0
 files/en-us/web/http/status/206/{index.html => index.md}          | 0
 files/en-us/web/http/status/300/{index.html => index.md}          | 0
 files/en-us/web/http/status/301/{index.html => index.md}          | 0
 files/en-us/web/http/status/302/{index.html => index.md}          | 0
 files/en-us/web/http/status/303/{index.html => index.md}          | 0
 files/en-us/web/http/status/304/{index.html => index.md}          | 0
 files/en-us/web/http/status/307/{index.html => index.md}          | 0
 files/en-us/web/http/status/308/{index.html => index.md}          | 0
 files/en-us/web/http/status/400/{index.html => index.md}          | 0
 files/en-us/web/http/status/401/{index.html => index.md}          | 0
 files/en-us/web/http/status/402/{index.html => index.md}          | 0
 files/en-us/web/http/status/403/{index.html => index.md}          | 0
 files/en-us/web/http/status/404/{index.html => index.md}          | 0
 files/en-us/web/http/status/405/{index.html => index.md}          | 0
 files/en-us/web/http/status/406/{index.html => index.md}          | 0
 files/en-us/web/http/status/407/{index.html => index.md}          | 0
 files/en-us/web/http/status/408/{index.html => index.md}          | 0
 files/en-us/web/http/status/409/{index.html => index.md}          | 0
 files/en-us/web/http/status/410/{index.html => index.md}          | 0
 files/en-us/web/http/status/411/{index.html => index.md}          | 0
 files/en-us/web/http/status/412/{index.html => index.md}          | 0
 files/en-us/web/http/status/413/{index.html => index.md}          | 0
 files/en-us/web/http/status/414/{index.html => index.md}          | 0
 files/en-us/web/http/status/415/{index.html => index.md}          | 0
 files/en-us/web/http/status/416/{index.html => index.md}          | 0
 files/en-us/web/http/status/417/{index.html => index.md}          | 0
 files/en-us/web/http/status/418/{index.html => index.md}          | 0
 files/en-us/web/http/status/422/{index.html => index.md}          | 0
 files/en-us/web/http/status/425/{index.html => index.md}          | 0
 files/en-us/web/http/status/426/{index.html => index.md}          | 0
 files/en-us/web/http/status/428/{index.html => index.md}          | 0
 files/en-us/web/http/status/429/{index.html => index.md}          | 0
 files/en-us/web/http/status/431/{index.html => index.md}          | 0
 files/en-us/web/http/status/451/{index.html => index.md}          | 0
 files/en-us/web/http/status/500/{index.html => index.md}          | 0
 files/en-us/web/http/status/501/{index.html => index.md}          | 0
 files/en-us/web/http/status/502/{index.html => index.md}          | 0
 files/en-us/web/http/status/503/{index.html => index.md}          | 0
 files/en-us/web/http/status/504/{index.html => index.md}          | 0
 files/en-us/web/http/status/505/{index.html => index.md}          | 0
 files/en-us/web/http/status/506/{index.html => index.md}          | 0
 files/en-us/web/http/status/507/{index.html => index.md}          | 0
 files/en-us/web/http/status/508/{index.html => index.md}          | 0
 files/en-us/web/http/status/510/{index.html => index.md}          | 0
 files/en-us/web/http/status/511/{index.html => index.md}          | 0
 files/en-us/web/http/status/{index.html => index.md}              | 0
 297 files changed, 0 insertions(+), 0 deletions(-)
 rename files/en-us/web/http/authentication/{index.html => index.md} (100%)
 rename files/en-us/web/http/basics_of_http/choosing_between_www_and_non-www_urls/{index.html => index.md} (100%)
 rename files/en-us/web/http/basics_of_http/data_uris/{index.html => index.md} (100%)
 rename files/en-us/web/http/basics_of_http/evolution_of_http/{index.html => index.md} (100%)
 rename files/en-us/web/http/basics_of_http/identifying_resources_on_the_web/{index.html => index.md} (100%)
 rename files/en-us/web/http/basics_of_http/{index.html => index.md} (100%)
 rename files/en-us/web/http/basics_of_http/mime_types/common_types/{index.html => index.md} (100%)
 rename files/en-us/web/http/basics_of_http/mime_types/{index.html => index.md} (100%)
 rename files/en-us/web/http/basics_of_http/resource_urls/{index.html => index.md} (100%)
 rename files/en-us/web/http/browser_detection_using_the_user_agent/{index.html => index.md} (100%)
 rename files/en-us/web/http/caching/{index.html => index.md} (100%)
 rename files/en-us/web/http/compression/{index.html => index.md} (100%)
 rename files/en-us/web/http/conditional_requests/{index.html => index.md} (100%)
 rename files/en-us/web/http/configuring_servers_for_ogg_media/{index.html => index.md} (100%)
 rename files/en-us/web/http/connection_management_in_http_1.x/{index.html => index.md} (100%)
 rename files/en-us/web/http/content_negotiation/{index.html => index.md} (100%)
 rename files/en-us/web/http/content_negotiation/list_of_default_accept_values/{index.html => index.md} (100%)
 rename files/en-us/web/http/cookies/{index.html => index.md} (100%)
 rename files/en-us/web/http/cors/errors/corsalloworiginnotmatchingorigin/{index.html => index.md} (100%)
 rename files/en-us/web/http/cors/errors/corsdidnotsucceed/{index.html => index.md} (100%)
 rename files/en-us/web/http/cors/errors/corsdisabled/{index.html => index.md} (100%)
 rename files/en-us/web/http/cors/errors/corsexternalredirectnotallowed/{index.html => index.md} (100%)
 rename files/en-us/web/http/cors/errors/corsinvalidallowheader/{index.html => index.md} (100%)
 rename files/en-us/web/http/cors/errors/corsinvalidallowmethod/{index.html => index.md} (100%)
 rename files/en-us/web/http/cors/errors/corsmethodnotfound/{index.html => index.md} (100%)
 rename files/en-us/web/http/cors/errors/corsmissingallowcredentials/{index.html => index.md} (100%)
 rename files/en-us/web/http/cors/errors/corsmissingallowheaderfrompreflight/{index.html => index.md} (100%)
 rename files/en-us/web/http/cors/errors/corsmissingalloworigin/{index.html => index.md} (100%)
 rename files/en-us/web/http/cors/errors/corsmultiplealloworiginnotallowed/{index.html => index.md} (100%)
 rename files/en-us/web/http/cors/errors/corsnotsupportingcredentials/{index.html => index.md} (100%)
 rename files/en-us/web/http/cors/errors/corsoriginheadernotadded/{index.html => index.md} (100%)
 rename files/en-us/web/http/cors/errors/corspreflightdidnotsucceed/{index.html => index.md} (100%)
 rename files/en-us/web/http/cors/errors/corsrequestnothttp/{index.html => index.md} (100%)
 rename files/en-us/web/http/cors/errors/{index.html => index.md} (100%)
 rename files/en-us/web/http/cors/{index.html => index.md} (100%)
 rename files/en-us/web/http/cross-origin_resource_policy_(corp)/{index.html => index.md} (100%)
 rename files/en-us/web/http/csp/errors/cspviolation/{index.html => index.md} (100%)
 rename files/en-us/web/http/csp/errors/{index.html => index.md} (100%)
 rename files/en-us/web/http/csp/{index.html => index.md} (100%)
 rename files/en-us/web/http/feature_policy/{index.html => index.md} (100%)
 rename files/en-us/web/http/feature_policy/using_feature_policy/{index.html => index.md} (100%)
 rename files/en-us/web/http/headers/accept-ch-lifetime/{index.html => index.md} (100%)
 rename files/en-us/web/http/headers/accept-ch/{index.html => index.md} (100%)
 rename files/en-us/web/http/headers/accept-charset/{index.html => index.md} (100%)
 rename files/en-us/web/http/headers/accept-encoding/{index.html => index.md} (100%)
 rename files/en-us/web/http/headers/accept-language/{index.html => index.md} (100%)
 rename files/en-us/web/http/headers/accept-patch/{index.html => index.md} (100%)
 rename files/en-us/web/http/headers/accept-post/{index.html => index.md} (100%)
 rename files/en-us/web/http/headers/accept-ranges/{index.html => index.md} (100%)
 rename files/en-us/web/http/headers/accept/{index.html => index.md} (100%)
 rename files/en-us/web/http/headers/access-control-allow-credentials/{index.html => index.md} (100%)
 rename files/en-us/web/http/headers/access-control-allow-headers/{index.html => index.md} (100%)
 rename files/en-us/web/http/headers/access-control-allow-methods/{index.html => index.md} (100%)
 rename files/en-us/web/http/headers/access-control-allow-origin/{index.html => index.md} (100%)
 rename files/en-us/web/http/headers/access-control-expose-headers/{index.html => index.md} (100%)
 rename files/en-us/web/http/headers/access-control-max-age/{index.html => index.md} (100%)
 rename files/en-us/web/http/headers/access-control-request-headers/{index.html => index.md} (100%)
 rename files/en-us/web/http/headers/access-control-request-method/{index.html => index.md} (100%)
 rename files/en-us/web/http/headers/age/{index.html => index.md} (100%)
 rename files/en-us/web/http/headers/allow/{index.html => index.md} (100%)
 rename files/en-us/web/http/headers/alt-svc/{index.html => index.md} (100%)
 rename files/en-us/web/http/headers/authorization/{index.html => index.md} (100%)
 rename files/en-us/web/http/headers/cache-control/{index.html => index.md} (100%)
 rename files/en-us/web/http/headers/clear-site-data/{index.html => index.md} (100%)
 rename files/en-us/web/http/headers/connection/{index.html => index.md} (100%)
 rename files/en-us/web/http/headers/content-disposition/{index.html => index.md} (100%)
 rename files/en-us/web/http/headers/content-dpr/{index.html => index.md} (100%)
 rename files/en-us/web/http/headers/content-encoding/{index.html => index.md} (100%)
 rename files/en-us/web/http/headers/content-language/{index.html => index.md} (100%)
 rename files/en-us/web/http/headers/content-length/{index.html => index.md} (100%)
 rename files/en-us/web/http/headers/content-location/{index.html => index.md} (100%)
 rename files/en-us/web/http/headers/content-range/{index.html => index.md} (100%)
 rename files/en-us/web/http/headers/content-security-policy-report-only/{index.html => index.md} (100%)
 rename files/en-us/web/http/headers/content-security-policy/base-uri/{index.html => index.md} (100%)
 rename files/en-us/web/http/headers/content-security-policy/block-all-mixed-content/{index.html => index.md} (100%)
 rename files/en-us/web/http/headers/content-security-policy/child-src/{index.html => index.md} (100%)
 rename files/en-us/web/http/headers/content-security-policy/connect-src/{index.html => index.md} (100%)
 rename files/en-us/web/http/headers/content-security-policy/default-src/{index.html => index.md} (100%)
 rename files/en-us/web/http/headers/content-security-policy/font-src/{index.html => index.md} (100%)
 rename files/en-us/web/http/headers/content-security-policy/form-action/{index.html => index.md} (100%)
 rename files/en-us/web/http/headers/content-security-policy/frame-ancestors/{index.html => index.md} (100%)
 rename files/en-us/web/http/headers/content-security-policy/frame-src/{index.html => index.md} (100%)
 rename files/en-us/web/http/headers/content-security-policy/img-src/{index.html => index.md} (100%)
 rename files/en-us/web/http/headers/content-security-policy/{index.html => index.md} (100%)
 rename files/en-us/web/http/headers/content-security-policy/manifest-src/{index.html => index.md} (100%)
 rename files/en-us/web/http/headers/content-security-policy/media-src/{index.html => index.md} (100%)
 rename files/en-us/web/http/headers/content-security-policy/navigate-to/{index.html => index.md} (100%)
 rename files/en-us/web/http/headers/content-security-policy/object-src/{index.html => index.md} (100%)
 rename files/en-us/web/http/headers/content-security-policy/plugin-types/{index.html => index.md} (100%)
 rename files/en-us/web/http/headers/content-security-policy/prefetch-src/{index.html => index.md} (100%)
 rename files/en-us/web/http/headers/content-security-policy/referrer/{index.html => index.md} (100%)
 rename files/en-us/web/http/headers/content-security-policy/report-to/{index.html => index.md} (100%)
 rename files/en-us/web/http/headers/content-security-policy/report-uri/{index.html => index.md} (100%)
 rename files/en-us/web/http/headers/content-security-policy/require-sri-for/{index.html => index.md} (100%)
 rename files/en-us/web/http/headers/content-security-policy/require-trusted-types-for/{index.html => index.md} (100%)
 rename files/en-us/web/http/headers/content-security-policy/sandbox/{index.html => index.md} (100%)
 rename files/en-us/web/http/headers/content-security-policy/script-src-attr/{index.html => index.md} (100%)
 rename files/en-us/web/http/headers/content-security-policy/script-src-elem/{index.html => index.md} (100%)
 rename files/en-us/web/http/headers/content-security-policy/script-src/{index.html => index.md} (100%)
 rename files/en-us/web/http/headers/content-security-policy/style-src-attr/{index.html => index.md} (100%)
 rename files/en-us/web/http/headers/content-security-policy/style-src-elem/{index.html => index.md} (100%)
 rename files/en-us/web/http/headers/content-security-policy/style-src/{index.html => index.md} (100%)
 rename files/en-us/web/http/headers/content-security-policy/trusted-types/{index.html => index.md} (100%)
 rename files/en-us/web/http/headers/content-security-policy/upgrade-insecure-requests/{index.html => index.md} (100%)
 rename files/en-us/web/http/headers/content-security-policy/worker-src/{index.html => index.md} (100%)
 rename files/en-us/web/http/headers/content-type/{index.html => index.md} (100%)
 rename files/en-us/web/http/headers/cookie/{index.html => index.md} (100%)
 rename files/en-us/web/http/headers/cookie2/{index.html => index.md} (100%)
 rename files/en-us/web/http/headers/cross-origin-embedder-policy/{index.html => index.md} (100%)
 rename files/en-us/web/http/headers/cross-origin-opener-policy/{index.html => index.md} (100%)
 rename files/en-us/web/http/headers/cross-origin-resource-policy/{index.html => index.md} (100%)
 rename files/en-us/web/http/headers/date/{index.html => index.md} (100%)
 rename files/en-us/web/http/headers/device-memory/{index.html => index.md} (100%)
 rename files/en-us/web/http/headers/digest/{index.html => index.md} (100%)
 rename files/en-us/web/http/headers/dnt/{index.html => index.md} (100%)
 rename files/en-us/web/http/headers/downlink/{index.html => index.md} (100%)
 rename files/en-us/web/http/headers/dpr/{index.html => index.md} (100%)
 rename files/en-us/web/http/headers/early-data/{index.html => index.md} (100%)
 rename files/en-us/web/http/headers/ect/{index.html => index.md} (100%)
 rename files/en-us/web/http/headers/etag/{index.html => index.md} (100%)
 rename files/en-us/web/http/headers/expect-ct/{index.html => index.md} (100%)
 rename files/en-us/web/http/headers/expect/{index.html => index.md} (100%)
 rename files/en-us/web/http/headers/expires/{index.html => index.md} (100%)
 rename files/en-us/web/http/headers/feature-policy/accelerometer/{index.html => index.md} (100%)
 rename files/en-us/web/http/headers/feature-policy/ambient-light-sensor/{index.html => index.md} (100%)
 rename files/en-us/web/http/headers/feature-policy/autoplay/{index.html => index.md} (100%)
 rename files/en-us/web/http/headers/feature-policy/battery/{index.html => index.md} (100%)
 rename files/en-us/web/http/headers/feature-policy/camera/{index.html => index.md} (100%)
 rename files/en-us/web/http/headers/feature-policy/display-capture/{index.html => index.md} (100%)
 rename files/en-us/web/http/headers/feature-policy/document-domain/{index.html => index.md} (100%)
 rename files/en-us/web/http/headers/feature-policy/encrypted-media/{index.html => index.md} (100%)
 rename files/en-us/web/http/headers/feature-policy/fullscreen/{index.html => index.md} (100%)
 rename files/en-us/web/http/headers/feature-policy/gamepad/{index.html => index.md} (100%)
 rename files/en-us/web/http/headers/feature-policy/geolocation/{index.html => index.md} (100%)
 rename files/en-us/web/http/headers/feature-policy/gyroscope/{index.html => index.md} (100%)
 rename files/en-us/web/http/headers/feature-policy/{index.html => index.md} (100%)
 rename files/en-us/web/http/headers/feature-policy/layout-animations/{index.html => index.md} (100%)
 rename files/en-us/web/http/headers/feature-policy/legacy-image-formats/{index.html => index.md} (100%)
 rename files/en-us/web/http/headers/feature-policy/magnetometer/{index.html => index.md} (100%)
 rename files/en-us/web/http/headers/feature-policy/microphone/{index.html => index.md} (100%)
 rename files/en-us/web/http/headers/feature-policy/midi/{index.html => index.md} (100%)
 rename files/en-us/web/http/headers/feature-policy/oversized-images/{index.html => index.md} (100%)
 rename files/en-us/web/http/headers/feature-policy/payment/{index.html => index.md} (100%)
 rename files/en-us/web/http/headers/feature-policy/picture-in-picture/{index.html => index.md} (100%)
 rename files/en-us/web/http/headers/feature-policy/publickey-credentials-get/{index.html => index.md} (100%)
 rename files/en-us/web/http/headers/feature-policy/screen-wake-lock/{index.html => index.md} (100%)
 rename files/en-us/web/http/headers/feature-policy/sync-xhr/{index.html => index.md} (100%)
 rename files/en-us/web/http/headers/feature-policy/unoptimized-images/{index.html => index.md} (100%)
 rename files/en-us/web/http/headers/feature-policy/unsized-media/{index.html => index.md} (100%)
 rename files/en-us/web/http/headers/feature-policy/usb/{index.html => index.md} (100%)
 rename files/en-us/web/http/headers/feature-policy/vibrate/{index.html => index.md} (100%)
 rename files/en-us/web/http/headers/feature-policy/vr/{index.html => index.md} (100%)
 rename files/en-us/web/http/headers/feature-policy/web-share/{index.html => index.md} (100%)
 rename files/en-us/web/http/headers/feature-policy/xr-spatial-tracking/{index.html => index.md} (100%)
 rename files/en-us/web/http/headers/feature-policy/xr/{index.html => index.md} (100%)
 rename files/en-us/web/http/headers/forwarded/{index.html => index.md} (100%)
 rename files/en-us/web/http/headers/from/{index.html => index.md} (100%)
 rename files/en-us/web/http/headers/host/{index.html => index.md} (100%)
 rename files/en-us/web/http/headers/if-match/{index.html => index.md} (100%)
 rename files/en-us/web/http/headers/if-modified-since/{index.html => index.md} (100%)
 rename files/en-us/web/http/headers/if-none-match/{index.html => index.md} (100%)
 rename files/en-us/web/http/headers/if-range/{index.html => index.md} (100%)
 rename files/en-us/web/http/headers/if-unmodified-since/{index.html => index.md} (100%)
 rename files/en-us/web/http/headers/{index.html => index.md} (100%)
 rename files/en-us/web/http/headers/keep-alive/{index.html => index.md} (100%)
 rename files/en-us/web/http/headers/large-allocation/{index.html => index.md} (100%)
 rename files/en-us/web/http/headers/last-modified/{index.html => index.md} (100%)
 rename files/en-us/web/http/headers/link/{index.html => index.md} (100%)
 rename files/en-us/web/http/headers/location/{index.html => index.md} (100%)
 rename files/en-us/web/http/headers/nel/{index.html => index.md} (100%)
 rename files/en-us/web/http/headers/origin/{index.html => index.md} (100%)
 rename files/en-us/web/http/headers/pragma/{index.html => index.md} (100%)
 rename files/en-us/web/http/headers/proxy-authenticate/{index.html => index.md} (100%)
 rename files/en-us/web/http/headers/proxy-authorization/{index.html => index.md} (100%)
 rename files/en-us/web/http/headers/public-key-pins-report-only/{index.html => index.md} (100%)
 rename files/en-us/web/http/headers/public-key-pins/{index.html => index.md} (100%)
 rename files/en-us/web/http/headers/range/{index.html => index.md} (100%)
 rename files/en-us/web/http/headers/referer/{index.html => index.md} (100%)
 rename files/en-us/web/http/headers/referrer-policy/{index.html => index.md} (100%)
 rename files/en-us/web/http/headers/retry-after/{index.html => index.md} (100%)
 rename files/en-us/web/http/headers/rtt/{index.html => index.md} (100%)
 rename files/en-us/web/http/headers/save-data/{index.html => index.md} (100%)
 rename files/en-us/web/http/headers/sec-fetch-dest/{index.html => index.md} (100%)
 rename files/en-us/web/http/headers/sec-fetch-mode/{index.html => index.md} (100%)
 rename files/en-us/web/http/headers/sec-fetch-site/{index.html => index.md} (100%)
 rename files/en-us/web/http/headers/sec-fetch-user/{index.html => index.md} (100%)
 rename files/en-us/web/http/headers/sec-websocket-accept/{index.html => index.md} (100%)
 rename files/en-us/web/http/headers/server-timing/{index.html => index.md} (100%)
 rename files/en-us/web/http/headers/server/{index.html => index.md} (100%)
 rename files/en-us/web/http/headers/set-cookie/{index.html => index.md} (100%)
 rename files/en-us/web/http/headers/set-cookie/samesite/{index.html => index.md} (100%)
 rename files/en-us/web/http/headers/set-cookie2/{index.html => index.md} (100%)
 rename files/en-us/web/http/headers/sourcemap/{index.html => index.md} (100%)
 rename files/en-us/web/http/headers/strict-transport-security/{index.html => index.md} (100%)
 rename files/en-us/web/http/headers/te/{index.html => index.md} (100%)
 rename files/en-us/web/http/headers/timing-allow-origin/{index.html => index.md} (100%)
 rename files/en-us/web/http/headers/tk/{index.html => index.md} (100%)
 rename files/en-us/web/http/headers/trailer/{index.html => index.md} (100%)
 rename files/en-us/web/http/headers/transfer-encoding/{index.html => index.md} (100%)
 rename files/en-us/web/http/headers/upgrade-insecure-requests/{index.html => index.md} (100%)
 rename files/en-us/web/http/headers/upgrade/{index.html => index.md} (100%)
 rename files/en-us/web/http/headers/user-agent/firefox/{index.html => index.md} (100%)
 rename files/en-us/web/http/headers/user-agent/{index.html => index.md} (100%)
 rename files/en-us/web/http/headers/vary/{index.html => index.md} (100%)
 rename files/en-us/web/http/headers/via/{index.html => index.md} (100%)
 rename files/en-us/web/http/headers/viewport-width/{index.html => index.md} (100%)
 rename files/en-us/web/http/headers/want-digest/{index.html => index.md} (100%)
 rename files/en-us/web/http/headers/warning/{index.html => index.md} (100%)
 rename files/en-us/web/http/headers/width/{index.html => index.md} (100%)
 rename files/en-us/web/http/headers/www-authenticate/{index.html => index.md} (100%)
 rename files/en-us/web/http/headers/x-content-type-options/{index.html => index.md} (100%)
 rename files/en-us/web/http/headers/x-dns-prefetch-control/{index.html => index.md} (100%)
 rename files/en-us/web/http/headers/x-forwarded-for/{index.html => index.md} (100%)
 rename files/en-us/web/http/headers/x-forwarded-host/{index.html => index.md} (100%)
 rename files/en-us/web/http/headers/x-forwarded-proto/{index.html => index.md} (100%)
 rename files/en-us/web/http/headers/x-frame-options/{index.html => index.md} (100%)
 rename files/en-us/web/http/headers/x-xss-protection/{index.html => index.md} (100%)
 rename files/en-us/web/http/{index.html => index.md} (100%)
 rename files/en-us/web/http/index/{index.html => index.md} (100%)
 rename files/en-us/web/http/link_prefetching_faq/{index.html => index.md} (100%)
 rename files/en-us/web/http/messages/{index.html => index.md} (100%)
 rename files/en-us/web/http/methods/connect/{index.html => index.md} (100%)
 rename files/en-us/web/http/methods/delete/{index.html => index.md} (100%)
 rename files/en-us/web/http/methods/get/{index.html => index.md} (100%)
 rename files/en-us/web/http/methods/head/{index.html => index.md} (100%)
 rename files/en-us/web/http/methods/{index.html => index.md} (100%)
 rename files/en-us/web/http/methods/options/{index.html => index.md} (100%)
 rename files/en-us/web/http/methods/patch/{index.html => index.md} (100%)
 rename files/en-us/web/http/methods/post/{index.html => index.md} (100%)
 rename files/en-us/web/http/methods/put/{index.html => index.md} (100%)
 rename files/en-us/web/http/methods/trace/{index.html => index.md} (100%)
 rename files/en-us/web/http/network_error_logging/{index.html => index.md} (100%)
 rename files/en-us/web/http/overview/{index.html => index.md} (100%)
 rename files/en-us/web/http/protocol_upgrade_mechanism/{index.html => index.md} (100%)
 rename files/en-us/web/http/proxy_servers_and_tunneling/{index.html => index.md} (100%)
 rename files/en-us/web/http/proxy_servers_and_tunneling/proxy_auto-configuration_pac_file/{index.html => index.md} (100%)
 rename files/en-us/web/http/public_key_pinning/{index.html => index.md} (100%)
 rename files/en-us/web/http/range_requests/{index.html => index.md} (100%)
 rename files/en-us/web/http/redirections/{index.html => index.md} (100%)
 rename files/en-us/web/http/resources_and_specifications/{index.html => index.md} (100%)
 rename files/en-us/web/http/resources_and_uris/{index.html => index.md} (100%)
 rename files/en-us/web/http/session/{index.html => index.md} (100%)
 rename files/en-us/web/http/status/100/{index.html => index.md} (100%)
 rename files/en-us/web/http/status/101/{index.html => index.md} (100%)
 rename files/en-us/web/http/status/103/{index.html => index.md} (100%)
 rename files/en-us/web/http/status/200/{index.html => index.md} (100%)
 rename files/en-us/web/http/status/201/{index.html => index.md} (100%)
 rename files/en-us/web/http/status/202/{index.html => index.md} (100%)
 rename files/en-us/web/http/status/203/{index.html => index.md} (100%)
 rename files/en-us/web/http/status/204/{index.html => index.md} (100%)
 rename files/en-us/web/http/status/205/{index.html => index.md} (100%)
 rename files/en-us/web/http/status/206/{index.html => index.md} (100%)
 rename files/en-us/web/http/status/300/{index.html => index.md} (100%)
 rename files/en-us/web/http/status/301/{index.html => index.md} (100%)
 rename files/en-us/web/http/status/302/{index.html => index.md} (100%)
 rename files/en-us/web/http/status/303/{index.html => index.md} (100%)
 rename files/en-us/web/http/status/304/{index.html => index.md} (100%)
 rename files/en-us/web/http/status/307/{index.html => index.md} (100%)
 rename files/en-us/web/http/status/308/{index.html => index.md} (100%)
 rename files/en-us/web/http/status/400/{index.html => index.md} (100%)
 rename files/en-us/web/http/status/401/{index.html => index.md} (100%)
 rename files/en-us/web/http/status/402/{index.html => index.md} (100%)
 rename files/en-us/web/http/status/403/{index.html => index.md} (100%)
 rename files/en-us/web/http/status/404/{index.html => index.md} (100%)
 rename files/en-us/web/http/status/405/{index.html => index.md} (100%)
 rename files/en-us/web/http/status/406/{index.html => index.md} (100%)
 rename files/en-us/web/http/status/407/{index.html => index.md} (100%)
 rename files/en-us/web/http/status/408/{index.html => index.md} (100%)
 rename files/en-us/web/http/status/409/{index.html => index.md} (100%)
 rename files/en-us/web/http/status/410/{index.html => index.md} (100%)
 rename files/en-us/web/http/status/411/{index.html => index.md} (100%)
 rename files/en-us/web/http/status/412/{index.html => index.md} (100%)
 rename files/en-us/web/http/status/413/{index.html => index.md} (100%)
 rename files/en-us/web/http/status/414/{index.html => index.md} (100%)
 rename files/en-us/web/http/status/415/{index.html => index.md} (100%)
 rename files/en-us/web/http/status/416/{index.html => index.md} (100%)
 rename files/en-us/web/http/status/417/{index.html => index.md} (100%)
 rename files/en-us/web/http/status/418/{index.html => index.md} (100%)
 rename files/en-us/web/http/status/422/{index.html => index.md} (100%)
 rename files/en-us/web/http/status/425/{index.html => index.md} (100%)
 rename files/en-us/web/http/status/426/{index.html => index.md} (100%)
 rename files/en-us/web/http/status/428/{index.html => index.md} (100%)
 rename files/en-us/web/http/status/429/{index.html => index.md} (100%)
 rename files/en-us/web/http/status/431/{index.html => index.md} (100%)
 rename files/en-us/web/http/status/451/{index.html => index.md} (100%)
 rename files/en-us/web/http/status/500/{index.html => index.md} (100%)
 rename files/en-us/web/http/status/501/{index.html => index.md} (100%)
 rename files/en-us/web/http/status/502/{index.html => index.md} (100%)
 rename files/en-us/web/http/status/503/{index.html => index.md} (100%)
 rename files/en-us/web/http/status/504/{index.html => index.md} (100%)
 rename files/en-us/web/http/status/505/{index.html => index.md} (100%)
 rename files/en-us/web/http/status/506/{index.html => index.md} (100%)
 rename files/en-us/web/http/status/507/{index.html => index.md} (100%)
 rename files/en-us/web/http/status/508/{index.html => index.md} (100%)
 rename files/en-us/web/http/status/510/{index.html => index.md} (100%)
 rename files/en-us/web/http/status/511/{index.html => index.md} (100%)
 rename files/en-us/web/http/status/{index.html => index.md} (100%)

diff --git a/files/en-us/web/http/authentication/index.html b/files/en-us/web/http/authentication/index.md
similarity index 100%
rename from files/en-us/web/http/authentication/index.html
rename to files/en-us/web/http/authentication/index.md
diff --git a/files/en-us/web/http/basics_of_http/choosing_between_www_and_non-www_urls/index.html b/files/en-us/web/http/basics_of_http/choosing_between_www_and_non-www_urls/index.md
similarity index 100%
rename from files/en-us/web/http/basics_of_http/choosing_between_www_and_non-www_urls/index.html
rename to files/en-us/web/http/basics_of_http/choosing_between_www_and_non-www_urls/index.md
diff --git a/files/en-us/web/http/basics_of_http/data_uris/index.html b/files/en-us/web/http/basics_of_http/data_uris/index.md
similarity index 100%
rename from files/en-us/web/http/basics_of_http/data_uris/index.html
rename to files/en-us/web/http/basics_of_http/data_uris/index.md
diff --git a/files/en-us/web/http/basics_of_http/evolution_of_http/index.html b/files/en-us/web/http/basics_of_http/evolution_of_http/index.md
similarity index 100%
rename from files/en-us/web/http/basics_of_http/evolution_of_http/index.html
rename to files/en-us/web/http/basics_of_http/evolution_of_http/index.md
diff --git a/files/en-us/web/http/basics_of_http/identifying_resources_on_the_web/index.html b/files/en-us/web/http/basics_of_http/identifying_resources_on_the_web/index.md
similarity index 100%
rename from files/en-us/web/http/basics_of_http/identifying_resources_on_the_web/index.html
rename to files/en-us/web/http/basics_of_http/identifying_resources_on_the_web/index.md
diff --git a/files/en-us/web/http/basics_of_http/index.html b/files/en-us/web/http/basics_of_http/index.md
similarity index 100%
rename from files/en-us/web/http/basics_of_http/index.html
rename to files/en-us/web/http/basics_of_http/index.md
diff --git a/files/en-us/web/http/basics_of_http/mime_types/common_types/index.html b/files/en-us/web/http/basics_of_http/mime_types/common_types/index.md
similarity index 100%
rename from files/en-us/web/http/basics_of_http/mime_types/common_types/index.html
rename to files/en-us/web/http/basics_of_http/mime_types/common_types/index.md
diff --git a/files/en-us/web/http/basics_of_http/mime_types/index.html b/files/en-us/web/http/basics_of_http/mime_types/index.md
similarity index 100%
rename from files/en-us/web/http/basics_of_http/mime_types/index.html
rename to files/en-us/web/http/basics_of_http/mime_types/index.md
diff --git a/files/en-us/web/http/basics_of_http/resource_urls/index.html b/files/en-us/web/http/basics_of_http/resource_urls/index.md
similarity index 100%
rename from files/en-us/web/http/basics_of_http/resource_urls/index.html
rename to files/en-us/web/http/basics_of_http/resource_urls/index.md
diff --git a/files/en-us/web/http/browser_detection_using_the_user_agent/index.html b/files/en-us/web/http/browser_detection_using_the_user_agent/index.md
similarity index 100%
rename from files/en-us/web/http/browser_detection_using_the_user_agent/index.html
rename to files/en-us/web/http/browser_detection_using_the_user_agent/index.md
diff --git a/files/en-us/web/http/caching/index.html b/files/en-us/web/http/caching/index.md
similarity index 100%
rename from files/en-us/web/http/caching/index.html
rename to files/en-us/web/http/caching/index.md
diff --git a/files/en-us/web/http/compression/index.html b/files/en-us/web/http/compression/index.md
similarity index 100%
rename from files/en-us/web/http/compression/index.html
rename to files/en-us/web/http/compression/index.md
diff --git a/files/en-us/web/http/conditional_requests/index.html b/files/en-us/web/http/conditional_requests/index.md
similarity index 100%
rename from files/en-us/web/http/conditional_requests/index.html
rename to files/en-us/web/http/conditional_requests/index.md
diff --git a/files/en-us/web/http/configuring_servers_for_ogg_media/index.html b/files/en-us/web/http/configuring_servers_for_ogg_media/index.md
similarity index 100%
rename from files/en-us/web/http/configuring_servers_for_ogg_media/index.html
rename to files/en-us/web/http/configuring_servers_for_ogg_media/index.md
diff --git a/files/en-us/web/http/connection_management_in_http_1.x/index.html b/files/en-us/web/http/connection_management_in_http_1.x/index.md
similarity index 100%
rename from files/en-us/web/http/connection_management_in_http_1.x/index.html
rename to files/en-us/web/http/connection_management_in_http_1.x/index.md
diff --git a/files/en-us/web/http/content_negotiation/index.html b/files/en-us/web/http/content_negotiation/index.md
similarity index 100%
rename from files/en-us/web/http/content_negotiation/index.html
rename to files/en-us/web/http/content_negotiation/index.md
diff --git a/files/en-us/web/http/content_negotiation/list_of_default_accept_values/index.html b/files/en-us/web/http/content_negotiation/list_of_default_accept_values/index.md
similarity index 100%
rename from files/en-us/web/http/content_negotiation/list_of_default_accept_values/index.html
rename to files/en-us/web/http/content_negotiation/list_of_default_accept_values/index.md
diff --git a/files/en-us/web/http/cookies/index.html b/files/en-us/web/http/cookies/index.md
similarity index 100%
rename from files/en-us/web/http/cookies/index.html
rename to files/en-us/web/http/cookies/index.md
diff --git a/files/en-us/web/http/cors/errors/corsalloworiginnotmatchingorigin/index.html b/files/en-us/web/http/cors/errors/corsalloworiginnotmatchingorigin/index.md
similarity index 100%
rename from files/en-us/web/http/cors/errors/corsalloworiginnotmatchingorigin/index.html
rename to files/en-us/web/http/cors/errors/corsalloworiginnotmatchingorigin/index.md
diff --git a/files/en-us/web/http/cors/errors/corsdidnotsucceed/index.html b/files/en-us/web/http/cors/errors/corsdidnotsucceed/index.md
similarity index 100%
rename from files/en-us/web/http/cors/errors/corsdidnotsucceed/index.html
rename to files/en-us/web/http/cors/errors/corsdidnotsucceed/index.md
diff --git a/files/en-us/web/http/cors/errors/corsdisabled/index.html b/files/en-us/web/http/cors/errors/corsdisabled/index.md
similarity index 100%
rename from files/en-us/web/http/cors/errors/corsdisabled/index.html
rename to files/en-us/web/http/cors/errors/corsdisabled/index.md
diff --git a/files/en-us/web/http/cors/errors/corsexternalredirectnotallowed/index.html b/files/en-us/web/http/cors/errors/corsexternalredirectnotallowed/index.md
similarity index 100%
rename from files/en-us/web/http/cors/errors/corsexternalredirectnotallowed/index.html
rename to files/en-us/web/http/cors/errors/corsexternalredirectnotallowed/index.md
diff --git a/files/en-us/web/http/cors/errors/corsinvalidallowheader/index.html b/files/en-us/web/http/cors/errors/corsinvalidallowheader/index.md
similarity index 100%
rename from files/en-us/web/http/cors/errors/corsinvalidallowheader/index.html
rename to files/en-us/web/http/cors/errors/corsinvalidallowheader/index.md
diff --git a/files/en-us/web/http/cors/errors/corsinvalidallowmethod/index.html b/files/en-us/web/http/cors/errors/corsinvalidallowmethod/index.md
similarity index 100%
rename from files/en-us/web/http/cors/errors/corsinvalidallowmethod/index.html
rename to files/en-us/web/http/cors/errors/corsinvalidallowmethod/index.md
diff --git a/files/en-us/web/http/cors/errors/corsmethodnotfound/index.html b/files/en-us/web/http/cors/errors/corsmethodnotfound/index.md
similarity index 100%
rename from files/en-us/web/http/cors/errors/corsmethodnotfound/index.html
rename to files/en-us/web/http/cors/errors/corsmethodnotfound/index.md
diff --git a/files/en-us/web/http/cors/errors/corsmissingallowcredentials/index.html b/files/en-us/web/http/cors/errors/corsmissingallowcredentials/index.md
similarity index 100%
rename from files/en-us/web/http/cors/errors/corsmissingallowcredentials/index.html
rename to files/en-us/web/http/cors/errors/corsmissingallowcredentials/index.md
diff --git a/files/en-us/web/http/cors/errors/corsmissingallowheaderfrompreflight/index.html b/files/en-us/web/http/cors/errors/corsmissingallowheaderfrompreflight/index.md
similarity index 100%
rename from files/en-us/web/http/cors/errors/corsmissingallowheaderfrompreflight/index.html
rename to files/en-us/web/http/cors/errors/corsmissingallowheaderfrompreflight/index.md
diff --git a/files/en-us/web/http/cors/errors/corsmissingalloworigin/index.html b/files/en-us/web/http/cors/errors/corsmissingalloworigin/index.md
similarity index 100%
rename from files/en-us/web/http/cors/errors/corsmissingalloworigin/index.html
rename to files/en-us/web/http/cors/errors/corsmissingalloworigin/index.md
diff --git a/files/en-us/web/http/cors/errors/corsmultiplealloworiginnotallowed/index.html b/files/en-us/web/http/cors/errors/corsmultiplealloworiginnotallowed/index.md
similarity index 100%
rename from files/en-us/web/http/cors/errors/corsmultiplealloworiginnotallowed/index.html
rename to files/en-us/web/http/cors/errors/corsmultiplealloworiginnotallowed/index.md
diff --git a/files/en-us/web/http/cors/errors/corsnotsupportingcredentials/index.html b/files/en-us/web/http/cors/errors/corsnotsupportingcredentials/index.md
similarity index 100%
rename from files/en-us/web/http/cors/errors/corsnotsupportingcredentials/index.html
rename to files/en-us/web/http/cors/errors/corsnotsupportingcredentials/index.md
diff --git a/files/en-us/web/http/cors/errors/corsoriginheadernotadded/index.html b/files/en-us/web/http/cors/errors/corsoriginheadernotadded/index.md
similarity index 100%
rename from files/en-us/web/http/cors/errors/corsoriginheadernotadded/index.html
rename to files/en-us/web/http/cors/errors/corsoriginheadernotadded/index.md
diff --git a/files/en-us/web/http/cors/errors/corspreflightdidnotsucceed/index.html b/files/en-us/web/http/cors/errors/corspreflightdidnotsucceed/index.md
similarity index 100%
rename from files/en-us/web/http/cors/errors/corspreflightdidnotsucceed/index.html
rename to files/en-us/web/http/cors/errors/corspreflightdidnotsucceed/index.md
diff --git a/files/en-us/web/http/cors/errors/corsrequestnothttp/index.html b/files/en-us/web/http/cors/errors/corsrequestnothttp/index.md
similarity index 100%
rename from files/en-us/web/http/cors/errors/corsrequestnothttp/index.html
rename to files/en-us/web/http/cors/errors/corsrequestnothttp/index.md
diff --git a/files/en-us/web/http/cors/errors/index.html b/files/en-us/web/http/cors/errors/index.md
similarity index 100%
rename from files/en-us/web/http/cors/errors/index.html
rename to files/en-us/web/http/cors/errors/index.md
diff --git a/files/en-us/web/http/cors/index.html b/files/en-us/web/http/cors/index.md
similarity index 100%
rename from files/en-us/web/http/cors/index.html
rename to files/en-us/web/http/cors/index.md
diff --git a/files/en-us/web/http/cross-origin_resource_policy_(corp)/index.html b/files/en-us/web/http/cross-origin_resource_policy_(corp)/index.md
similarity index 100%
rename from files/en-us/web/http/cross-origin_resource_policy_(corp)/index.html
rename to files/en-us/web/http/cross-origin_resource_policy_(corp)/index.md
diff --git a/files/en-us/web/http/csp/errors/cspviolation/index.html b/files/en-us/web/http/csp/errors/cspviolation/index.md
similarity index 100%
rename from files/en-us/web/http/csp/errors/cspviolation/index.html
rename to files/en-us/web/http/csp/errors/cspviolation/index.md
diff --git a/files/en-us/web/http/csp/errors/index.html b/files/en-us/web/http/csp/errors/index.md
similarity index 100%
rename from files/en-us/web/http/csp/errors/index.html
rename to files/en-us/web/http/csp/errors/index.md
diff --git a/files/en-us/web/http/csp/index.html b/files/en-us/web/http/csp/index.md
similarity index 100%
rename from files/en-us/web/http/csp/index.html
rename to files/en-us/web/http/csp/index.md
diff --git a/files/en-us/web/http/feature_policy/index.html b/files/en-us/web/http/feature_policy/index.md
similarity index 100%
rename from files/en-us/web/http/feature_policy/index.html
rename to files/en-us/web/http/feature_policy/index.md
diff --git a/files/en-us/web/http/feature_policy/using_feature_policy/index.html b/files/en-us/web/http/feature_policy/using_feature_policy/index.md
similarity index 100%
rename from files/en-us/web/http/feature_policy/using_feature_policy/index.html
rename to files/en-us/web/http/feature_policy/using_feature_policy/index.md
diff --git a/files/en-us/web/http/headers/accept-ch-lifetime/index.html b/files/en-us/web/http/headers/accept-ch-lifetime/index.md
similarity index 100%
rename from files/en-us/web/http/headers/accept-ch-lifetime/index.html
rename to files/en-us/web/http/headers/accept-ch-lifetime/index.md
diff --git a/files/en-us/web/http/headers/accept-ch/index.html b/files/en-us/web/http/headers/accept-ch/index.md
similarity index 100%
rename from files/en-us/web/http/headers/accept-ch/index.html
rename to files/en-us/web/http/headers/accept-ch/index.md
diff --git a/files/en-us/web/http/headers/accept-charset/index.html b/files/en-us/web/http/headers/accept-charset/index.md
similarity index 100%
rename from files/en-us/web/http/headers/accept-charset/index.html
rename to files/en-us/web/http/headers/accept-charset/index.md
diff --git a/files/en-us/web/http/headers/accept-encoding/index.html b/files/en-us/web/http/headers/accept-encoding/index.md
similarity index 100%
rename from files/en-us/web/http/headers/accept-encoding/index.html
rename to files/en-us/web/http/headers/accept-encoding/index.md
diff --git a/files/en-us/web/http/headers/accept-language/index.html b/files/en-us/web/http/headers/accept-language/index.md
similarity index 100%
rename from files/en-us/web/http/headers/accept-language/index.html
rename to files/en-us/web/http/headers/accept-language/index.md
diff --git a/files/en-us/web/http/headers/accept-patch/index.html b/files/en-us/web/http/headers/accept-patch/index.md
similarity index 100%
rename from files/en-us/web/http/headers/accept-patch/index.html
rename to files/en-us/web/http/headers/accept-patch/index.md
diff --git a/files/en-us/web/http/headers/accept-post/index.html b/files/en-us/web/http/headers/accept-post/index.md
similarity index 100%
rename from files/en-us/web/http/headers/accept-post/index.html
rename to files/en-us/web/http/headers/accept-post/index.md
diff --git a/files/en-us/web/http/headers/accept-ranges/index.html b/files/en-us/web/http/headers/accept-ranges/index.md
similarity index 100%
rename from files/en-us/web/http/headers/accept-ranges/index.html
rename to files/en-us/web/http/headers/accept-ranges/index.md
diff --git a/files/en-us/web/http/headers/accept/index.html b/files/en-us/web/http/headers/accept/index.md
similarity index 100%
rename from files/en-us/web/http/headers/accept/index.html
rename to files/en-us/web/http/headers/accept/index.md
diff --git a/files/en-us/web/http/headers/access-control-allow-credentials/index.html b/files/en-us/web/http/headers/access-control-allow-credentials/index.md
similarity index 100%
rename from files/en-us/web/http/headers/access-control-allow-credentials/index.html
rename to files/en-us/web/http/headers/access-control-allow-credentials/index.md
diff --git a/files/en-us/web/http/headers/access-control-allow-headers/index.html b/files/en-us/web/http/headers/access-control-allow-headers/index.md
similarity index 100%
rename from files/en-us/web/http/headers/access-control-allow-headers/index.html
rename to files/en-us/web/http/headers/access-control-allow-headers/index.md
diff --git a/files/en-us/web/http/headers/access-control-allow-methods/index.html b/files/en-us/web/http/headers/access-control-allow-methods/index.md
similarity index 100%
rename from files/en-us/web/http/headers/access-control-allow-methods/index.html
rename to files/en-us/web/http/headers/access-control-allow-methods/index.md
diff --git a/files/en-us/web/http/headers/access-control-allow-origin/index.html b/files/en-us/web/http/headers/access-control-allow-origin/index.md
similarity index 100%
rename from files/en-us/web/http/headers/access-control-allow-origin/index.html
rename to files/en-us/web/http/headers/access-control-allow-origin/index.md
diff --git a/files/en-us/web/http/headers/access-control-expose-headers/index.html b/files/en-us/web/http/headers/access-control-expose-headers/index.md
similarity index 100%
rename from files/en-us/web/http/headers/access-control-expose-headers/index.html
rename to files/en-us/web/http/headers/access-control-expose-headers/index.md
diff --git a/files/en-us/web/http/headers/access-control-max-age/index.html b/files/en-us/web/http/headers/access-control-max-age/index.md
similarity index 100%
rename from files/en-us/web/http/headers/access-control-max-age/index.html
rename to files/en-us/web/http/headers/access-control-max-age/index.md
diff --git a/files/en-us/web/http/headers/access-control-request-headers/index.html b/files/en-us/web/http/headers/access-control-request-headers/index.md
similarity index 100%
rename from files/en-us/web/http/headers/access-control-request-headers/index.html
rename to files/en-us/web/http/headers/access-control-request-headers/index.md
diff --git a/files/en-us/web/http/headers/access-control-request-method/index.html b/files/en-us/web/http/headers/access-control-request-method/index.md
similarity index 100%
rename from files/en-us/web/http/headers/access-control-request-method/index.html
rename to files/en-us/web/http/headers/access-control-request-method/index.md
diff --git a/files/en-us/web/http/headers/age/index.html b/files/en-us/web/http/headers/age/index.md
similarity index 100%
rename from files/en-us/web/http/headers/age/index.html
rename to files/en-us/web/http/headers/age/index.md
diff --git a/files/en-us/web/http/headers/allow/index.html b/files/en-us/web/http/headers/allow/index.md
similarity index 100%
rename from files/en-us/web/http/headers/allow/index.html
rename to files/en-us/web/http/headers/allow/index.md
diff --git a/files/en-us/web/http/headers/alt-svc/index.html b/files/en-us/web/http/headers/alt-svc/index.md
similarity index 100%
rename from files/en-us/web/http/headers/alt-svc/index.html
rename to files/en-us/web/http/headers/alt-svc/index.md
diff --git a/files/en-us/web/http/headers/authorization/index.html b/files/en-us/web/http/headers/authorization/index.md
similarity index 100%
rename from files/en-us/web/http/headers/authorization/index.html
rename to files/en-us/web/http/headers/authorization/index.md
diff --git a/files/en-us/web/http/headers/cache-control/index.html b/files/en-us/web/http/headers/cache-control/index.md
similarity index 100%
rename from files/en-us/web/http/headers/cache-control/index.html
rename to files/en-us/web/http/headers/cache-control/index.md
diff --git a/files/en-us/web/http/headers/clear-site-data/index.html b/files/en-us/web/http/headers/clear-site-data/index.md
similarity index 100%
rename from files/en-us/web/http/headers/clear-site-data/index.html
rename to files/en-us/web/http/headers/clear-site-data/index.md
diff --git a/files/en-us/web/http/headers/connection/index.html b/files/en-us/web/http/headers/connection/index.md
similarity index 100%
rename from files/en-us/web/http/headers/connection/index.html
rename to files/en-us/web/http/headers/connection/index.md
diff --git a/files/en-us/web/http/headers/content-disposition/index.html b/files/en-us/web/http/headers/content-disposition/index.md
similarity index 100%
rename from files/en-us/web/http/headers/content-disposition/index.html
rename to files/en-us/web/http/headers/content-disposition/index.md
diff --git a/files/en-us/web/http/headers/content-dpr/index.html b/files/en-us/web/http/headers/content-dpr/index.md
similarity index 100%
rename from files/en-us/web/http/headers/content-dpr/index.html
rename to files/en-us/web/http/headers/content-dpr/index.md
diff --git a/files/en-us/web/http/headers/content-encoding/index.html b/files/en-us/web/http/headers/content-encoding/index.md
similarity index 100%
rename from files/en-us/web/http/headers/content-encoding/index.html
rename to files/en-us/web/http/headers/content-encoding/index.md
diff --git a/files/en-us/web/http/headers/content-language/index.html b/files/en-us/web/http/headers/content-language/index.md
similarity index 100%
rename from files/en-us/web/http/headers/content-language/index.html
rename to files/en-us/web/http/headers/content-language/index.md
diff --git a/files/en-us/web/http/headers/content-length/index.html b/files/en-us/web/http/headers/content-length/index.md
similarity index 100%
rename from files/en-us/web/http/headers/content-length/index.html
rename to files/en-us/web/http/headers/content-length/index.md
diff --git a/files/en-us/web/http/headers/content-location/index.html b/files/en-us/web/http/headers/content-location/index.md
similarity index 100%
rename from files/en-us/web/http/headers/content-location/index.html
rename to files/en-us/web/http/headers/content-location/index.md
diff --git a/files/en-us/web/http/headers/content-range/index.html b/files/en-us/web/http/headers/content-range/index.md
similarity index 100%
rename from files/en-us/web/http/headers/content-range/index.html
rename to files/en-us/web/http/headers/content-range/index.md
diff --git a/files/en-us/web/http/headers/content-security-policy-report-only/index.html b/files/en-us/web/http/headers/content-security-policy-report-only/index.md
similarity index 100%
rename from files/en-us/web/http/headers/content-security-policy-report-only/index.html
rename to files/en-us/web/http/headers/content-security-policy-report-only/index.md
diff --git a/files/en-us/web/http/headers/content-security-policy/base-uri/index.html b/files/en-us/web/http/headers/content-security-policy/base-uri/index.md
similarity index 100%
rename from files/en-us/web/http/headers/content-security-policy/base-uri/index.html
rename to files/en-us/web/http/headers/content-security-policy/base-uri/index.md
diff --git a/files/en-us/web/http/headers/content-security-policy/block-all-mixed-content/index.html b/files/en-us/web/http/headers/content-security-policy/block-all-mixed-content/index.md
similarity index 100%
rename from files/en-us/web/http/headers/content-security-policy/block-all-mixed-content/index.html
rename to files/en-us/web/http/headers/content-security-policy/block-all-mixed-content/index.md
diff --git a/files/en-us/web/http/headers/content-security-policy/child-src/index.html b/files/en-us/web/http/headers/content-security-policy/child-src/index.md
similarity index 100%
rename from files/en-us/web/http/headers/content-security-policy/child-src/index.html
rename to files/en-us/web/http/headers/content-security-policy/child-src/index.md
diff --git a/files/en-us/web/http/headers/content-security-policy/connect-src/index.html b/files/en-us/web/http/headers/content-security-policy/connect-src/index.md
similarity index 100%
rename from files/en-us/web/http/headers/content-security-policy/connect-src/index.html
rename to files/en-us/web/http/headers/content-security-policy/connect-src/index.md
diff --git a/files/en-us/web/http/headers/content-security-policy/default-src/index.html b/files/en-us/web/http/headers/content-security-policy/default-src/index.md
similarity index 100%
rename from files/en-us/web/http/headers/content-security-policy/default-src/index.html
rename to files/en-us/web/http/headers/content-security-policy/default-src/index.md
diff --git a/files/en-us/web/http/headers/content-security-policy/font-src/index.html b/files/en-us/web/http/headers/content-security-policy/font-src/index.md
similarity index 100%
rename from files/en-us/web/http/headers/content-security-policy/font-src/index.html
rename to files/en-us/web/http/headers/content-security-policy/font-src/index.md
diff --git a/files/en-us/web/http/headers/content-security-policy/form-action/index.html b/files/en-us/web/http/headers/content-security-policy/form-action/index.md
similarity index 100%
rename from files/en-us/web/http/headers/content-security-policy/form-action/index.html
rename to files/en-us/web/http/headers/content-security-policy/form-action/index.md
diff --git a/files/en-us/web/http/headers/content-security-policy/frame-ancestors/index.html b/files/en-us/web/http/headers/content-security-policy/frame-ancestors/index.md
similarity index 100%
rename from files/en-us/web/http/headers/content-security-policy/frame-ancestors/index.html
rename to files/en-us/web/http/headers/content-security-policy/frame-ancestors/index.md
diff --git a/files/en-us/web/http/headers/content-security-policy/frame-src/index.html b/files/en-us/web/http/headers/content-security-policy/frame-src/index.md
similarity index 100%
rename from files/en-us/web/http/headers/content-security-policy/frame-src/index.html
rename to files/en-us/web/http/headers/content-security-policy/frame-src/index.md
diff --git a/files/en-us/web/http/headers/content-security-policy/img-src/index.html b/files/en-us/web/http/headers/content-security-policy/img-src/index.md
similarity index 100%
rename from files/en-us/web/http/headers/content-security-policy/img-src/index.html
rename to files/en-us/web/http/headers/content-security-policy/img-src/index.md
diff --git a/files/en-us/web/http/headers/content-security-policy/index.html b/files/en-us/web/http/headers/content-security-policy/index.md
similarity index 100%
rename from files/en-us/web/http/headers/content-security-policy/index.html
rename to files/en-us/web/http/headers/content-security-policy/index.md
diff --git a/files/en-us/web/http/headers/content-security-policy/manifest-src/index.html b/files/en-us/web/http/headers/content-security-policy/manifest-src/index.md
similarity index 100%
rename from files/en-us/web/http/headers/content-security-policy/manifest-src/index.html
rename to files/en-us/web/http/headers/content-security-policy/manifest-src/index.md
diff --git a/files/en-us/web/http/headers/content-security-policy/media-src/index.html b/files/en-us/web/http/headers/content-security-policy/media-src/index.md
similarity index 100%
rename from files/en-us/web/http/headers/content-security-policy/media-src/index.html
rename to files/en-us/web/http/headers/content-security-policy/media-src/index.md
diff --git a/files/en-us/web/http/headers/content-security-policy/navigate-to/index.html b/files/en-us/web/http/headers/content-security-policy/navigate-to/index.md
similarity index 100%
rename from files/en-us/web/http/headers/content-security-policy/navigate-to/index.html
rename to files/en-us/web/http/headers/content-security-policy/navigate-to/index.md
diff --git a/files/en-us/web/http/headers/content-security-policy/object-src/index.html b/files/en-us/web/http/headers/content-security-policy/object-src/index.md
similarity index 100%
rename from files/en-us/web/http/headers/content-security-policy/object-src/index.html
rename to files/en-us/web/http/headers/content-security-policy/object-src/index.md
diff --git a/files/en-us/web/http/headers/content-security-policy/plugin-types/index.html b/files/en-us/web/http/headers/content-security-policy/plugin-types/index.md
similarity index 100%
rename from files/en-us/web/http/headers/content-security-policy/plugin-types/index.html
rename to files/en-us/web/http/headers/content-security-policy/plugin-types/index.md
diff --git a/files/en-us/web/http/headers/content-security-policy/prefetch-src/index.html b/files/en-us/web/http/headers/content-security-policy/prefetch-src/index.md
similarity index 100%
rename from files/en-us/web/http/headers/content-security-policy/prefetch-src/index.html
rename to files/en-us/web/http/headers/content-security-policy/prefetch-src/index.md
diff --git a/files/en-us/web/http/headers/content-security-policy/referrer/index.html b/files/en-us/web/http/headers/content-security-policy/referrer/index.md
similarity index 100%
rename from files/en-us/web/http/headers/content-security-policy/referrer/index.html
rename to files/en-us/web/http/headers/content-security-policy/referrer/index.md
diff --git a/files/en-us/web/http/headers/content-security-policy/report-to/index.html b/files/en-us/web/http/headers/content-security-policy/report-to/index.md
similarity index 100%
rename from files/en-us/web/http/headers/content-security-policy/report-to/index.html
rename to files/en-us/web/http/headers/content-security-policy/report-to/index.md
diff --git a/files/en-us/web/http/headers/content-security-policy/report-uri/index.html b/files/en-us/web/http/headers/content-security-policy/report-uri/index.md
similarity index 100%
rename from files/en-us/web/http/headers/content-security-policy/report-uri/index.html
rename to files/en-us/web/http/headers/content-security-policy/report-uri/index.md
diff --git a/files/en-us/web/http/headers/content-security-policy/require-sri-for/index.html b/files/en-us/web/http/headers/content-security-policy/require-sri-for/index.md
similarity index 100%
rename from files/en-us/web/http/headers/content-security-policy/require-sri-for/index.html
rename to files/en-us/web/http/headers/content-security-policy/require-sri-for/index.md
diff --git a/files/en-us/web/http/headers/content-security-policy/require-trusted-types-for/index.html b/files/en-us/web/http/headers/content-security-policy/require-trusted-types-for/index.md
similarity index 100%
rename from files/en-us/web/http/headers/content-security-policy/require-trusted-types-for/index.html
rename to files/en-us/web/http/headers/content-security-policy/require-trusted-types-for/index.md
diff --git a/files/en-us/web/http/headers/content-security-policy/sandbox/index.html b/files/en-us/web/http/headers/content-security-policy/sandbox/index.md
similarity index 100%
rename from files/en-us/web/http/headers/content-security-policy/sandbox/index.html
rename to files/en-us/web/http/headers/content-security-policy/sandbox/index.md
diff --git a/files/en-us/web/http/headers/content-security-policy/script-src-attr/index.html b/files/en-us/web/http/headers/content-security-policy/script-src-attr/index.md
similarity index 100%
rename from files/en-us/web/http/headers/content-security-policy/script-src-attr/index.html
rename to files/en-us/web/http/headers/content-security-policy/script-src-attr/index.md
diff --git a/files/en-us/web/http/headers/content-security-policy/script-src-elem/index.html b/files/en-us/web/http/headers/content-security-policy/script-src-elem/index.md
similarity index 100%
rename from files/en-us/web/http/headers/content-security-policy/script-src-elem/index.html
rename to files/en-us/web/http/headers/content-security-policy/script-src-elem/index.md
diff --git a/files/en-us/web/http/headers/content-security-policy/script-src/index.html b/files/en-us/web/http/headers/content-security-policy/script-src/index.md
similarity index 100%
rename from files/en-us/web/http/headers/content-security-policy/script-src/index.html
rename to files/en-us/web/http/headers/content-security-policy/script-src/index.md
diff --git a/files/en-us/web/http/headers/content-security-policy/style-src-attr/index.html b/files/en-us/web/http/headers/content-security-policy/style-src-attr/index.md
similarity index 100%
rename from files/en-us/web/http/headers/content-security-policy/style-src-attr/index.html
rename to files/en-us/web/http/headers/content-security-policy/style-src-attr/index.md
diff --git a/files/en-us/web/http/headers/content-security-policy/style-src-elem/index.html b/files/en-us/web/http/headers/content-security-policy/style-src-elem/index.md
similarity index 100%
rename from files/en-us/web/http/headers/content-security-policy/style-src-elem/index.html
rename to files/en-us/web/http/headers/content-security-policy/style-src-elem/index.md
diff --git a/files/en-us/web/http/headers/content-security-policy/style-src/index.html b/files/en-us/web/http/headers/content-security-policy/style-src/index.md
similarity index 100%
rename from files/en-us/web/http/headers/content-security-policy/style-src/index.html
rename to files/en-us/web/http/headers/content-security-policy/style-src/index.md
diff --git a/files/en-us/web/http/headers/content-security-policy/trusted-types/index.html b/files/en-us/web/http/headers/content-security-policy/trusted-types/index.md
similarity index 100%
rename from files/en-us/web/http/headers/content-security-policy/trusted-types/index.html
rename to files/en-us/web/http/headers/content-security-policy/trusted-types/index.md
diff --git a/files/en-us/web/http/headers/content-security-policy/upgrade-insecure-requests/index.html b/files/en-us/web/http/headers/content-security-policy/upgrade-insecure-requests/index.md
similarity index 100%
rename from files/en-us/web/http/headers/content-security-policy/upgrade-insecure-requests/index.html
rename to files/en-us/web/http/headers/content-security-policy/upgrade-insecure-requests/index.md
diff --git a/files/en-us/web/http/headers/content-security-policy/worker-src/index.html b/files/en-us/web/http/headers/content-security-policy/worker-src/index.md
similarity index 100%
rename from files/en-us/web/http/headers/content-security-policy/worker-src/index.html
rename to files/en-us/web/http/headers/content-security-policy/worker-src/index.md
diff --git a/files/en-us/web/http/headers/content-type/index.html b/files/en-us/web/http/headers/content-type/index.md
similarity index 100%
rename from files/en-us/web/http/headers/content-type/index.html
rename to files/en-us/web/http/headers/content-type/index.md
diff --git a/files/en-us/web/http/headers/cookie/index.html b/files/en-us/web/http/headers/cookie/index.md
similarity index 100%
rename from files/en-us/web/http/headers/cookie/index.html
rename to files/en-us/web/http/headers/cookie/index.md
diff --git a/files/en-us/web/http/headers/cookie2/index.html b/files/en-us/web/http/headers/cookie2/index.md
similarity index 100%
rename from files/en-us/web/http/headers/cookie2/index.html
rename to files/en-us/web/http/headers/cookie2/index.md
diff --git a/files/en-us/web/http/headers/cross-origin-embedder-policy/index.html b/files/en-us/web/http/headers/cross-origin-embedder-policy/index.md
similarity index 100%
rename from files/en-us/web/http/headers/cross-origin-embedder-policy/index.html
rename to files/en-us/web/http/headers/cross-origin-embedder-policy/index.md
diff --git a/files/en-us/web/http/headers/cross-origin-opener-policy/index.html b/files/en-us/web/http/headers/cross-origin-opener-policy/index.md
similarity index 100%
rename from files/en-us/web/http/headers/cross-origin-opener-policy/index.html
rename to files/en-us/web/http/headers/cross-origin-opener-policy/index.md
diff --git a/files/en-us/web/http/headers/cross-origin-resource-policy/index.html b/files/en-us/web/http/headers/cross-origin-resource-policy/index.md
similarity index 100%
rename from files/en-us/web/http/headers/cross-origin-resource-policy/index.html
rename to files/en-us/web/http/headers/cross-origin-resource-policy/index.md
diff --git a/files/en-us/web/http/headers/date/index.html b/files/en-us/web/http/headers/date/index.md
similarity index 100%
rename from files/en-us/web/http/headers/date/index.html
rename to files/en-us/web/http/headers/date/index.md
diff --git a/files/en-us/web/http/headers/device-memory/index.html b/files/en-us/web/http/headers/device-memory/index.md
similarity index 100%
rename from files/en-us/web/http/headers/device-memory/index.html
rename to files/en-us/web/http/headers/device-memory/index.md
diff --git a/files/en-us/web/http/headers/digest/index.html b/files/en-us/web/http/headers/digest/index.md
similarity index 100%
rename from files/en-us/web/http/headers/digest/index.html
rename to files/en-us/web/http/headers/digest/index.md
diff --git a/files/en-us/web/http/headers/dnt/index.html b/files/en-us/web/http/headers/dnt/index.md
similarity index 100%
rename from files/en-us/web/http/headers/dnt/index.html
rename to files/en-us/web/http/headers/dnt/index.md
diff --git a/files/en-us/web/http/headers/downlink/index.html b/files/en-us/web/http/headers/downlink/index.md
similarity index 100%
rename from files/en-us/web/http/headers/downlink/index.html
rename to files/en-us/web/http/headers/downlink/index.md
diff --git a/files/en-us/web/http/headers/dpr/index.html b/files/en-us/web/http/headers/dpr/index.md
similarity index 100%
rename from files/en-us/web/http/headers/dpr/index.html
rename to files/en-us/web/http/headers/dpr/index.md
diff --git a/files/en-us/web/http/headers/early-data/index.html b/files/en-us/web/http/headers/early-data/index.md
similarity index 100%
rename from files/en-us/web/http/headers/early-data/index.html
rename to files/en-us/web/http/headers/early-data/index.md
diff --git a/files/en-us/web/http/headers/ect/index.html b/files/en-us/web/http/headers/ect/index.md
similarity index 100%
rename from files/en-us/web/http/headers/ect/index.html
rename to files/en-us/web/http/headers/ect/index.md
diff --git a/files/en-us/web/http/headers/etag/index.html b/files/en-us/web/http/headers/etag/index.md
similarity index 100%
rename from files/en-us/web/http/headers/etag/index.html
rename to files/en-us/web/http/headers/etag/index.md
diff --git a/files/en-us/web/http/headers/expect-ct/index.html b/files/en-us/web/http/headers/expect-ct/index.md
similarity index 100%
rename from files/en-us/web/http/headers/expect-ct/index.html
rename to files/en-us/web/http/headers/expect-ct/index.md
diff --git a/files/en-us/web/http/headers/expect/index.html b/files/en-us/web/http/headers/expect/index.md
similarity index 100%
rename from files/en-us/web/http/headers/expect/index.html
rename to files/en-us/web/http/headers/expect/index.md
diff --git a/files/en-us/web/http/headers/expires/index.html b/files/en-us/web/http/headers/expires/index.md
similarity index 100%
rename from files/en-us/web/http/headers/expires/index.html
rename to files/en-us/web/http/headers/expires/index.md
diff --git a/files/en-us/web/http/headers/feature-policy/accelerometer/index.html b/files/en-us/web/http/headers/feature-policy/accelerometer/index.md
similarity index 100%
rename from files/en-us/web/http/headers/feature-policy/accelerometer/index.html
rename to files/en-us/web/http/headers/feature-policy/accelerometer/index.md
diff --git a/files/en-us/web/http/headers/feature-policy/ambient-light-sensor/index.html b/files/en-us/web/http/headers/feature-policy/ambient-light-sensor/index.md
similarity index 100%
rename from files/en-us/web/http/headers/feature-policy/ambient-light-sensor/index.html
rename to files/en-us/web/http/headers/feature-policy/ambient-light-sensor/index.md
diff --git a/files/en-us/web/http/headers/feature-policy/autoplay/index.html b/files/en-us/web/http/headers/feature-policy/autoplay/index.md
similarity index 100%
rename from files/en-us/web/http/headers/feature-policy/autoplay/index.html
rename to files/en-us/web/http/headers/feature-policy/autoplay/index.md
diff --git a/files/en-us/web/http/headers/feature-policy/battery/index.html b/files/en-us/web/http/headers/feature-policy/battery/index.md
similarity index 100%
rename from files/en-us/web/http/headers/feature-policy/battery/index.html
rename to files/en-us/web/http/headers/feature-policy/battery/index.md
diff --git a/files/en-us/web/http/headers/feature-policy/camera/index.html b/files/en-us/web/http/headers/feature-policy/camera/index.md
similarity index 100%
rename from files/en-us/web/http/headers/feature-policy/camera/index.html
rename to files/en-us/web/http/headers/feature-policy/camera/index.md
diff --git a/files/en-us/web/http/headers/feature-policy/display-capture/index.html b/files/en-us/web/http/headers/feature-policy/display-capture/index.md
similarity index 100%
rename from files/en-us/web/http/headers/feature-policy/display-capture/index.html
rename to files/en-us/web/http/headers/feature-policy/display-capture/index.md
diff --git a/files/en-us/web/http/headers/feature-policy/document-domain/index.html b/files/en-us/web/http/headers/feature-policy/document-domain/index.md
similarity index 100%
rename from files/en-us/web/http/headers/feature-policy/document-domain/index.html
rename to files/en-us/web/http/headers/feature-policy/document-domain/index.md
diff --git a/files/en-us/web/http/headers/feature-policy/encrypted-media/index.html b/files/en-us/web/http/headers/feature-policy/encrypted-media/index.md
similarity index 100%
rename from files/en-us/web/http/headers/feature-policy/encrypted-media/index.html
rename to files/en-us/web/http/headers/feature-policy/encrypted-media/index.md
diff --git a/files/en-us/web/http/headers/feature-policy/fullscreen/index.html b/files/en-us/web/http/headers/feature-policy/fullscreen/index.md
similarity index 100%
rename from files/en-us/web/http/headers/feature-policy/fullscreen/index.html
rename to files/en-us/web/http/headers/feature-policy/fullscreen/index.md
diff --git a/files/en-us/web/http/headers/feature-policy/gamepad/index.html b/files/en-us/web/http/headers/feature-policy/gamepad/index.md
similarity index 100%
rename from files/en-us/web/http/headers/feature-policy/gamepad/index.html
rename to files/en-us/web/http/headers/feature-policy/gamepad/index.md
diff --git a/files/en-us/web/http/headers/feature-policy/geolocation/index.html b/files/en-us/web/http/headers/feature-policy/geolocation/index.md
similarity index 100%
rename from files/en-us/web/http/headers/feature-policy/geolocation/index.html
rename to files/en-us/web/http/headers/feature-policy/geolocation/index.md
diff --git a/files/en-us/web/http/headers/feature-policy/gyroscope/index.html b/files/en-us/web/http/headers/feature-policy/gyroscope/index.md
similarity index 100%
rename from files/en-us/web/http/headers/feature-policy/gyroscope/index.html
rename to files/en-us/web/http/headers/feature-policy/gyroscope/index.md
diff --git a/files/en-us/web/http/headers/feature-policy/index.html b/files/en-us/web/http/headers/feature-policy/index.md
similarity index 100%
rename from files/en-us/web/http/headers/feature-policy/index.html
rename to files/en-us/web/http/headers/feature-policy/index.md
diff --git a/files/en-us/web/http/headers/feature-policy/layout-animations/index.html b/files/en-us/web/http/headers/feature-policy/layout-animations/index.md
similarity index 100%
rename from files/en-us/web/http/headers/feature-policy/layout-animations/index.html
rename to files/en-us/web/http/headers/feature-policy/layout-animations/index.md
diff --git a/files/en-us/web/http/headers/feature-policy/legacy-image-formats/index.html b/files/en-us/web/http/headers/feature-policy/legacy-image-formats/index.md
similarity index 100%
rename from files/en-us/web/http/headers/feature-policy/legacy-image-formats/index.html
rename to files/en-us/web/http/headers/feature-policy/legacy-image-formats/index.md
diff --git a/files/en-us/web/http/headers/feature-policy/magnetometer/index.html b/files/en-us/web/http/headers/feature-policy/magnetometer/index.md
similarity index 100%
rename from files/en-us/web/http/headers/feature-policy/magnetometer/index.html
rename to files/en-us/web/http/headers/feature-policy/magnetometer/index.md
diff --git a/files/en-us/web/http/headers/feature-policy/microphone/index.html b/files/en-us/web/http/headers/feature-policy/microphone/index.md
similarity index 100%
rename from files/en-us/web/http/headers/feature-policy/microphone/index.html
rename to files/en-us/web/http/headers/feature-policy/microphone/index.md
diff --git a/files/en-us/web/http/headers/feature-policy/midi/index.html b/files/en-us/web/http/headers/feature-policy/midi/index.md
similarity index 100%
rename from files/en-us/web/http/headers/feature-policy/midi/index.html
rename to files/en-us/web/http/headers/feature-policy/midi/index.md
diff --git a/files/en-us/web/http/headers/feature-policy/oversized-images/index.html b/files/en-us/web/http/headers/feature-policy/oversized-images/index.md
similarity index 100%
rename from files/en-us/web/http/headers/feature-policy/oversized-images/index.html
rename to files/en-us/web/http/headers/feature-policy/oversized-images/index.md
diff --git a/files/en-us/web/http/headers/feature-policy/payment/index.html b/files/en-us/web/http/headers/feature-policy/payment/index.md
similarity index 100%
rename from files/en-us/web/http/headers/feature-policy/payment/index.html
rename to files/en-us/web/http/headers/feature-policy/payment/index.md
diff --git a/files/en-us/web/http/headers/feature-policy/picture-in-picture/index.html b/files/en-us/web/http/headers/feature-policy/picture-in-picture/index.md
similarity index 100%
rename from files/en-us/web/http/headers/feature-policy/picture-in-picture/index.html
rename to files/en-us/web/http/headers/feature-policy/picture-in-picture/index.md
diff --git a/files/en-us/web/http/headers/feature-policy/publickey-credentials-get/index.html b/files/en-us/web/http/headers/feature-policy/publickey-credentials-get/index.md
similarity index 100%
rename from files/en-us/web/http/headers/feature-policy/publickey-credentials-get/index.html
rename to files/en-us/web/http/headers/feature-policy/publickey-credentials-get/index.md
diff --git a/files/en-us/web/http/headers/feature-policy/screen-wake-lock/index.html b/files/en-us/web/http/headers/feature-policy/screen-wake-lock/index.md
similarity index 100%
rename from files/en-us/web/http/headers/feature-policy/screen-wake-lock/index.html
rename to files/en-us/web/http/headers/feature-policy/screen-wake-lock/index.md
diff --git a/files/en-us/web/http/headers/feature-policy/sync-xhr/index.html b/files/en-us/web/http/headers/feature-policy/sync-xhr/index.md
similarity index 100%
rename from files/en-us/web/http/headers/feature-policy/sync-xhr/index.html
rename to files/en-us/web/http/headers/feature-policy/sync-xhr/index.md
diff --git a/files/en-us/web/http/headers/feature-policy/unoptimized-images/index.html b/files/en-us/web/http/headers/feature-policy/unoptimized-images/index.md
similarity index 100%
rename from files/en-us/web/http/headers/feature-policy/unoptimized-images/index.html
rename to files/en-us/web/http/headers/feature-policy/unoptimized-images/index.md
diff --git a/files/en-us/web/http/headers/feature-policy/unsized-media/index.html b/files/en-us/web/http/headers/feature-policy/unsized-media/index.md
similarity index 100%
rename from files/en-us/web/http/headers/feature-policy/unsized-media/index.html
rename to files/en-us/web/http/headers/feature-policy/unsized-media/index.md
diff --git a/files/en-us/web/http/headers/feature-policy/usb/index.html b/files/en-us/web/http/headers/feature-policy/usb/index.md
similarity index 100%
rename from files/en-us/web/http/headers/feature-policy/usb/index.html
rename to files/en-us/web/http/headers/feature-policy/usb/index.md
diff --git a/files/en-us/web/http/headers/feature-policy/vibrate/index.html b/files/en-us/web/http/headers/feature-policy/vibrate/index.md
similarity index 100%
rename from files/en-us/web/http/headers/feature-policy/vibrate/index.html
rename to files/en-us/web/http/headers/feature-policy/vibrate/index.md
diff --git a/files/en-us/web/http/headers/feature-policy/vr/index.html b/files/en-us/web/http/headers/feature-policy/vr/index.md
similarity index 100%
rename from files/en-us/web/http/headers/feature-policy/vr/index.html
rename to files/en-us/web/http/headers/feature-policy/vr/index.md
diff --git a/files/en-us/web/http/headers/feature-policy/web-share/index.html b/files/en-us/web/http/headers/feature-policy/web-share/index.md
similarity index 100%
rename from files/en-us/web/http/headers/feature-policy/web-share/index.html
rename to files/en-us/web/http/headers/feature-policy/web-share/index.md
diff --git a/files/en-us/web/http/headers/feature-policy/xr-spatial-tracking/index.html b/files/en-us/web/http/headers/feature-policy/xr-spatial-tracking/index.md
similarity index 100%
rename from files/en-us/web/http/headers/feature-policy/xr-spatial-tracking/index.html
rename to files/en-us/web/http/headers/feature-policy/xr-spatial-tracking/index.md
diff --git a/files/en-us/web/http/headers/feature-policy/xr/index.html b/files/en-us/web/http/headers/feature-policy/xr/index.md
similarity index 100%
rename from files/en-us/web/http/headers/feature-policy/xr/index.html
rename to files/en-us/web/http/headers/feature-policy/xr/index.md
diff --git a/files/en-us/web/http/headers/forwarded/index.html b/files/en-us/web/http/headers/forwarded/index.md
similarity index 100%
rename from files/en-us/web/http/headers/forwarded/index.html
rename to files/en-us/web/http/headers/forwarded/index.md
diff --git a/files/en-us/web/http/headers/from/index.html b/files/en-us/web/http/headers/from/index.md
similarity index 100%
rename from files/en-us/web/http/headers/from/index.html
rename to files/en-us/web/http/headers/from/index.md
diff --git a/files/en-us/web/http/headers/host/index.html b/files/en-us/web/http/headers/host/index.md
similarity index 100%
rename from files/en-us/web/http/headers/host/index.html
rename to files/en-us/web/http/headers/host/index.md
diff --git a/files/en-us/web/http/headers/if-match/index.html b/files/en-us/web/http/headers/if-match/index.md
similarity index 100%
rename from files/en-us/web/http/headers/if-match/index.html
rename to files/en-us/web/http/headers/if-match/index.md
diff --git a/files/en-us/web/http/headers/if-modified-since/index.html b/files/en-us/web/http/headers/if-modified-since/index.md
similarity index 100%
rename from files/en-us/web/http/headers/if-modified-since/index.html
rename to files/en-us/web/http/headers/if-modified-since/index.md
diff --git a/files/en-us/web/http/headers/if-none-match/index.html b/files/en-us/web/http/headers/if-none-match/index.md
similarity index 100%
rename from files/en-us/web/http/headers/if-none-match/index.html
rename to files/en-us/web/http/headers/if-none-match/index.md
diff --git a/files/en-us/web/http/headers/if-range/index.html b/files/en-us/web/http/headers/if-range/index.md
similarity index 100%
rename from files/en-us/web/http/headers/if-range/index.html
rename to files/en-us/web/http/headers/if-range/index.md
diff --git a/files/en-us/web/http/headers/if-unmodified-since/index.html b/files/en-us/web/http/headers/if-unmodified-since/index.md
similarity index 100%
rename from files/en-us/web/http/headers/if-unmodified-since/index.html
rename to files/en-us/web/http/headers/if-unmodified-since/index.md
diff --git a/files/en-us/web/http/headers/index.html b/files/en-us/web/http/headers/index.md
similarity index 100%
rename from files/en-us/web/http/headers/index.html
rename to files/en-us/web/http/headers/index.md
diff --git a/files/en-us/web/http/headers/keep-alive/index.html b/files/en-us/web/http/headers/keep-alive/index.md
similarity index 100%
rename from files/en-us/web/http/headers/keep-alive/index.html
rename to files/en-us/web/http/headers/keep-alive/index.md
diff --git a/files/en-us/web/http/headers/large-allocation/index.html b/files/en-us/web/http/headers/large-allocation/index.md
similarity index 100%
rename from files/en-us/web/http/headers/large-allocation/index.html
rename to files/en-us/web/http/headers/large-allocation/index.md
diff --git a/files/en-us/web/http/headers/last-modified/index.html b/files/en-us/web/http/headers/last-modified/index.md
similarity index 100%
rename from files/en-us/web/http/headers/last-modified/index.html
rename to files/en-us/web/http/headers/last-modified/index.md
diff --git a/files/en-us/web/http/headers/link/index.html b/files/en-us/web/http/headers/link/index.md
similarity index 100%
rename from files/en-us/web/http/headers/link/index.html
rename to files/en-us/web/http/headers/link/index.md
diff --git a/files/en-us/web/http/headers/location/index.html b/files/en-us/web/http/headers/location/index.md
similarity index 100%
rename from files/en-us/web/http/headers/location/index.html
rename to files/en-us/web/http/headers/location/index.md
diff --git a/files/en-us/web/http/headers/nel/index.html b/files/en-us/web/http/headers/nel/index.md
similarity index 100%
rename from files/en-us/web/http/headers/nel/index.html
rename to files/en-us/web/http/headers/nel/index.md
diff --git a/files/en-us/web/http/headers/origin/index.html b/files/en-us/web/http/headers/origin/index.md
similarity index 100%
rename from files/en-us/web/http/headers/origin/index.html
rename to files/en-us/web/http/headers/origin/index.md
diff --git a/files/en-us/web/http/headers/pragma/index.html b/files/en-us/web/http/headers/pragma/index.md
similarity index 100%
rename from files/en-us/web/http/headers/pragma/index.html
rename to files/en-us/web/http/headers/pragma/index.md
diff --git a/files/en-us/web/http/headers/proxy-authenticate/index.html b/files/en-us/web/http/headers/proxy-authenticate/index.md
similarity index 100%
rename from files/en-us/web/http/headers/proxy-authenticate/index.html
rename to files/en-us/web/http/headers/proxy-authenticate/index.md
diff --git a/files/en-us/web/http/headers/proxy-authorization/index.html b/files/en-us/web/http/headers/proxy-authorization/index.md
similarity index 100%
rename from files/en-us/web/http/headers/proxy-authorization/index.html
rename to files/en-us/web/http/headers/proxy-authorization/index.md
diff --git a/files/en-us/web/http/headers/public-key-pins-report-only/index.html b/files/en-us/web/http/headers/public-key-pins-report-only/index.md
similarity index 100%
rename from files/en-us/web/http/headers/public-key-pins-report-only/index.html
rename to files/en-us/web/http/headers/public-key-pins-report-only/index.md
diff --git a/files/en-us/web/http/headers/public-key-pins/index.html b/files/en-us/web/http/headers/public-key-pins/index.md
similarity index 100%
rename from files/en-us/web/http/headers/public-key-pins/index.html
rename to files/en-us/web/http/headers/public-key-pins/index.md
diff --git a/files/en-us/web/http/headers/range/index.html b/files/en-us/web/http/headers/range/index.md
similarity index 100%
rename from files/en-us/web/http/headers/range/index.html
rename to files/en-us/web/http/headers/range/index.md
diff --git a/files/en-us/web/http/headers/referer/index.html b/files/en-us/web/http/headers/referer/index.md
similarity index 100%
rename from files/en-us/web/http/headers/referer/index.html
rename to files/en-us/web/http/headers/referer/index.md
diff --git a/files/en-us/web/http/headers/referrer-policy/index.html b/files/en-us/web/http/headers/referrer-policy/index.md
similarity index 100%
rename from files/en-us/web/http/headers/referrer-policy/index.html
rename to files/en-us/web/http/headers/referrer-policy/index.md
diff --git a/files/en-us/web/http/headers/retry-after/index.html b/files/en-us/web/http/headers/retry-after/index.md
similarity index 100%
rename from files/en-us/web/http/headers/retry-after/index.html
rename to files/en-us/web/http/headers/retry-after/index.md
diff --git a/files/en-us/web/http/headers/rtt/index.html b/files/en-us/web/http/headers/rtt/index.md
similarity index 100%
rename from files/en-us/web/http/headers/rtt/index.html
rename to files/en-us/web/http/headers/rtt/index.md
diff --git a/files/en-us/web/http/headers/save-data/index.html b/files/en-us/web/http/headers/save-data/index.md
similarity index 100%
rename from files/en-us/web/http/headers/save-data/index.html
rename to files/en-us/web/http/headers/save-data/index.md
diff --git a/files/en-us/web/http/headers/sec-fetch-dest/index.html b/files/en-us/web/http/headers/sec-fetch-dest/index.md
similarity index 100%
rename from files/en-us/web/http/headers/sec-fetch-dest/index.html
rename to files/en-us/web/http/headers/sec-fetch-dest/index.md
diff --git a/files/en-us/web/http/headers/sec-fetch-mode/index.html b/files/en-us/web/http/headers/sec-fetch-mode/index.md
similarity index 100%
rename from files/en-us/web/http/headers/sec-fetch-mode/index.html
rename to files/en-us/web/http/headers/sec-fetch-mode/index.md
diff --git a/files/en-us/web/http/headers/sec-fetch-site/index.html b/files/en-us/web/http/headers/sec-fetch-site/index.md
similarity index 100%
rename from files/en-us/web/http/headers/sec-fetch-site/index.html
rename to files/en-us/web/http/headers/sec-fetch-site/index.md
diff --git a/files/en-us/web/http/headers/sec-fetch-user/index.html b/files/en-us/web/http/headers/sec-fetch-user/index.md
similarity index 100%
rename from files/en-us/web/http/headers/sec-fetch-user/index.html
rename to files/en-us/web/http/headers/sec-fetch-user/index.md
diff --git a/files/en-us/web/http/headers/sec-websocket-accept/index.html b/files/en-us/web/http/headers/sec-websocket-accept/index.md
similarity index 100%
rename from files/en-us/web/http/headers/sec-websocket-accept/index.html
rename to files/en-us/web/http/headers/sec-websocket-accept/index.md
diff --git a/files/en-us/web/http/headers/server-timing/index.html b/files/en-us/web/http/headers/server-timing/index.md
similarity index 100%
rename from files/en-us/web/http/headers/server-timing/index.html
rename to files/en-us/web/http/headers/server-timing/index.md
diff --git a/files/en-us/web/http/headers/server/index.html b/files/en-us/web/http/headers/server/index.md
similarity index 100%
rename from files/en-us/web/http/headers/server/index.html
rename to files/en-us/web/http/headers/server/index.md
diff --git a/files/en-us/web/http/headers/set-cookie/index.html b/files/en-us/web/http/headers/set-cookie/index.md
similarity index 100%
rename from files/en-us/web/http/headers/set-cookie/index.html
rename to files/en-us/web/http/headers/set-cookie/index.md
diff --git a/files/en-us/web/http/headers/set-cookie/samesite/index.html b/files/en-us/web/http/headers/set-cookie/samesite/index.md
similarity index 100%
rename from files/en-us/web/http/headers/set-cookie/samesite/index.html
rename to files/en-us/web/http/headers/set-cookie/samesite/index.md
diff --git a/files/en-us/web/http/headers/set-cookie2/index.html b/files/en-us/web/http/headers/set-cookie2/index.md
similarity index 100%
rename from files/en-us/web/http/headers/set-cookie2/index.html
rename to files/en-us/web/http/headers/set-cookie2/index.md
diff --git a/files/en-us/web/http/headers/sourcemap/index.html b/files/en-us/web/http/headers/sourcemap/index.md
similarity index 100%
rename from files/en-us/web/http/headers/sourcemap/index.html
rename to files/en-us/web/http/headers/sourcemap/index.md
diff --git a/files/en-us/web/http/headers/strict-transport-security/index.html b/files/en-us/web/http/headers/strict-transport-security/index.md
similarity index 100%
rename from files/en-us/web/http/headers/strict-transport-security/index.html
rename to files/en-us/web/http/headers/strict-transport-security/index.md
diff --git a/files/en-us/web/http/headers/te/index.html b/files/en-us/web/http/headers/te/index.md
similarity index 100%
rename from files/en-us/web/http/headers/te/index.html
rename to files/en-us/web/http/headers/te/index.md
diff --git a/files/en-us/web/http/headers/timing-allow-origin/index.html b/files/en-us/web/http/headers/timing-allow-origin/index.md
similarity index 100%
rename from files/en-us/web/http/headers/timing-allow-origin/index.html
rename to files/en-us/web/http/headers/timing-allow-origin/index.md
diff --git a/files/en-us/web/http/headers/tk/index.html b/files/en-us/web/http/headers/tk/index.md
similarity index 100%
rename from files/en-us/web/http/headers/tk/index.html
rename to files/en-us/web/http/headers/tk/index.md
diff --git a/files/en-us/web/http/headers/trailer/index.html b/files/en-us/web/http/headers/trailer/index.md
similarity index 100%
rename from files/en-us/web/http/headers/trailer/index.html
rename to files/en-us/web/http/headers/trailer/index.md
diff --git a/files/en-us/web/http/headers/transfer-encoding/index.html b/files/en-us/web/http/headers/transfer-encoding/index.md
similarity index 100%
rename from files/en-us/web/http/headers/transfer-encoding/index.html
rename to files/en-us/web/http/headers/transfer-encoding/index.md
diff --git a/files/en-us/web/http/headers/upgrade-insecure-requests/index.html b/files/en-us/web/http/headers/upgrade-insecure-requests/index.md
similarity index 100%
rename from files/en-us/web/http/headers/upgrade-insecure-requests/index.html
rename to files/en-us/web/http/headers/upgrade-insecure-requests/index.md
diff --git a/files/en-us/web/http/headers/upgrade/index.html b/files/en-us/web/http/headers/upgrade/index.md
similarity index 100%
rename from files/en-us/web/http/headers/upgrade/index.html
rename to files/en-us/web/http/headers/upgrade/index.md
diff --git a/files/en-us/web/http/headers/user-agent/firefox/index.html b/files/en-us/web/http/headers/user-agent/firefox/index.md
similarity index 100%
rename from files/en-us/web/http/headers/user-agent/firefox/index.html
rename to files/en-us/web/http/headers/user-agent/firefox/index.md
diff --git a/files/en-us/web/http/headers/user-agent/index.html b/files/en-us/web/http/headers/user-agent/index.md
similarity index 100%
rename from files/en-us/web/http/headers/user-agent/index.html
rename to files/en-us/web/http/headers/user-agent/index.md
diff --git a/files/en-us/web/http/headers/vary/index.html b/files/en-us/web/http/headers/vary/index.md
similarity index 100%
rename from files/en-us/web/http/headers/vary/index.html
rename to files/en-us/web/http/headers/vary/index.md
diff --git a/files/en-us/web/http/headers/via/index.html b/files/en-us/web/http/headers/via/index.md
similarity index 100%
rename from files/en-us/web/http/headers/via/index.html
rename to files/en-us/web/http/headers/via/index.md
diff --git a/files/en-us/web/http/headers/viewport-width/index.html b/files/en-us/web/http/headers/viewport-width/index.md
similarity index 100%
rename from files/en-us/web/http/headers/viewport-width/index.html
rename to files/en-us/web/http/headers/viewport-width/index.md
diff --git a/files/en-us/web/http/headers/want-digest/index.html b/files/en-us/web/http/headers/want-digest/index.md
similarity index 100%
rename from files/en-us/web/http/headers/want-digest/index.html
rename to files/en-us/web/http/headers/want-digest/index.md
diff --git a/files/en-us/web/http/headers/warning/index.html b/files/en-us/web/http/headers/warning/index.md
similarity index 100%
rename from files/en-us/web/http/headers/warning/index.html
rename to files/en-us/web/http/headers/warning/index.md
diff --git a/files/en-us/web/http/headers/width/index.html b/files/en-us/web/http/headers/width/index.md
similarity index 100%
rename from files/en-us/web/http/headers/width/index.html
rename to files/en-us/web/http/headers/width/index.md
diff --git a/files/en-us/web/http/headers/www-authenticate/index.html b/files/en-us/web/http/headers/www-authenticate/index.md
similarity index 100%
rename from files/en-us/web/http/headers/www-authenticate/index.html
rename to files/en-us/web/http/headers/www-authenticate/index.md
diff --git a/files/en-us/web/http/headers/x-content-type-options/index.html b/files/en-us/web/http/headers/x-content-type-options/index.md
similarity index 100%
rename from files/en-us/web/http/headers/x-content-type-options/index.html
rename to files/en-us/web/http/headers/x-content-type-options/index.md
diff --git a/files/en-us/web/http/headers/x-dns-prefetch-control/index.html b/files/en-us/web/http/headers/x-dns-prefetch-control/index.md
similarity index 100%
rename from files/en-us/web/http/headers/x-dns-prefetch-control/index.html
rename to files/en-us/web/http/headers/x-dns-prefetch-control/index.md
diff --git a/files/en-us/web/http/headers/x-forwarded-for/index.html b/files/en-us/web/http/headers/x-forwarded-for/index.md
similarity index 100%
rename from files/en-us/web/http/headers/x-forwarded-for/index.html
rename to files/en-us/web/http/headers/x-forwarded-for/index.md
diff --git a/files/en-us/web/http/headers/x-forwarded-host/index.html b/files/en-us/web/http/headers/x-forwarded-host/index.md
similarity index 100%
rename from files/en-us/web/http/headers/x-forwarded-host/index.html
rename to files/en-us/web/http/headers/x-forwarded-host/index.md
diff --git a/files/en-us/web/http/headers/x-forwarded-proto/index.html b/files/en-us/web/http/headers/x-forwarded-proto/index.md
similarity index 100%
rename from files/en-us/web/http/headers/x-forwarded-proto/index.html
rename to files/en-us/web/http/headers/x-forwarded-proto/index.md
diff --git a/files/en-us/web/http/headers/x-frame-options/index.html b/files/en-us/web/http/headers/x-frame-options/index.md
similarity index 100%
rename from files/en-us/web/http/headers/x-frame-options/index.html
rename to files/en-us/web/http/headers/x-frame-options/index.md
diff --git a/files/en-us/web/http/headers/x-xss-protection/index.html b/files/en-us/web/http/headers/x-xss-protection/index.md
similarity index 100%
rename from files/en-us/web/http/headers/x-xss-protection/index.html
rename to files/en-us/web/http/headers/x-xss-protection/index.md
diff --git a/files/en-us/web/http/index.html b/files/en-us/web/http/index.md
similarity index 100%
rename from files/en-us/web/http/index.html
rename to files/en-us/web/http/index.md
diff --git a/files/en-us/web/http/index/index.html b/files/en-us/web/http/index/index.md
similarity index 100%
rename from files/en-us/web/http/index/index.html
rename to files/en-us/web/http/index/index.md
diff --git a/files/en-us/web/http/link_prefetching_faq/index.html b/files/en-us/web/http/link_prefetching_faq/index.md
similarity index 100%
rename from files/en-us/web/http/link_prefetching_faq/index.html
rename to files/en-us/web/http/link_prefetching_faq/index.md
diff --git a/files/en-us/web/http/messages/index.html b/files/en-us/web/http/messages/index.md
similarity index 100%
rename from files/en-us/web/http/messages/index.html
rename to files/en-us/web/http/messages/index.md
diff --git a/files/en-us/web/http/methods/connect/index.html b/files/en-us/web/http/methods/connect/index.md
similarity index 100%
rename from files/en-us/web/http/methods/connect/index.html
rename to files/en-us/web/http/methods/connect/index.md
diff --git a/files/en-us/web/http/methods/delete/index.html b/files/en-us/web/http/methods/delete/index.md
similarity index 100%
rename from files/en-us/web/http/methods/delete/index.html
rename to files/en-us/web/http/methods/delete/index.md
diff --git a/files/en-us/web/http/methods/get/index.html b/files/en-us/web/http/methods/get/index.md
similarity index 100%
rename from files/en-us/web/http/methods/get/index.html
rename to files/en-us/web/http/methods/get/index.md
diff --git a/files/en-us/web/http/methods/head/index.html b/files/en-us/web/http/methods/head/index.md
similarity index 100%
rename from files/en-us/web/http/methods/head/index.html
rename to files/en-us/web/http/methods/head/index.md
diff --git a/files/en-us/web/http/methods/index.html b/files/en-us/web/http/methods/index.md
similarity index 100%
rename from files/en-us/web/http/methods/index.html
rename to files/en-us/web/http/methods/index.md
diff --git a/files/en-us/web/http/methods/options/index.html b/files/en-us/web/http/methods/options/index.md
similarity index 100%
rename from files/en-us/web/http/methods/options/index.html
rename to files/en-us/web/http/methods/options/index.md
diff --git a/files/en-us/web/http/methods/patch/index.html b/files/en-us/web/http/methods/patch/index.md
similarity index 100%
rename from files/en-us/web/http/methods/patch/index.html
rename to files/en-us/web/http/methods/patch/index.md
diff --git a/files/en-us/web/http/methods/post/index.html b/files/en-us/web/http/methods/post/index.md
similarity index 100%
rename from files/en-us/web/http/methods/post/index.html
rename to files/en-us/web/http/methods/post/index.md
diff --git a/files/en-us/web/http/methods/put/index.html b/files/en-us/web/http/methods/put/index.md
similarity index 100%
rename from files/en-us/web/http/methods/put/index.html
rename to files/en-us/web/http/methods/put/index.md
diff --git a/files/en-us/web/http/methods/trace/index.html b/files/en-us/web/http/methods/trace/index.md
similarity index 100%
rename from files/en-us/web/http/methods/trace/index.html
rename to files/en-us/web/http/methods/trace/index.md
diff --git a/files/en-us/web/http/network_error_logging/index.html b/files/en-us/web/http/network_error_logging/index.md
similarity index 100%
rename from files/en-us/web/http/network_error_logging/index.html
rename to files/en-us/web/http/network_error_logging/index.md
diff --git a/files/en-us/web/http/overview/index.html b/files/en-us/web/http/overview/index.md
similarity index 100%
rename from files/en-us/web/http/overview/index.html
rename to files/en-us/web/http/overview/index.md
diff --git a/files/en-us/web/http/protocol_upgrade_mechanism/index.html b/files/en-us/web/http/protocol_upgrade_mechanism/index.md
similarity index 100%
rename from files/en-us/web/http/protocol_upgrade_mechanism/index.html
rename to files/en-us/web/http/protocol_upgrade_mechanism/index.md
diff --git a/files/en-us/web/http/proxy_servers_and_tunneling/index.html b/files/en-us/web/http/proxy_servers_and_tunneling/index.md
similarity index 100%
rename from files/en-us/web/http/proxy_servers_and_tunneling/index.html
rename to files/en-us/web/http/proxy_servers_and_tunneling/index.md
diff --git a/files/en-us/web/http/proxy_servers_and_tunneling/proxy_auto-configuration_pac_file/index.html b/files/en-us/web/http/proxy_servers_and_tunneling/proxy_auto-configuration_pac_file/index.md
similarity index 100%
rename from files/en-us/web/http/proxy_servers_and_tunneling/proxy_auto-configuration_pac_file/index.html
rename to files/en-us/web/http/proxy_servers_and_tunneling/proxy_auto-configuration_pac_file/index.md
diff --git a/files/en-us/web/http/public_key_pinning/index.html b/files/en-us/web/http/public_key_pinning/index.md
similarity index 100%
rename from files/en-us/web/http/public_key_pinning/index.html
rename to files/en-us/web/http/public_key_pinning/index.md
diff --git a/files/en-us/web/http/range_requests/index.html b/files/en-us/web/http/range_requests/index.md
similarity index 100%
rename from files/en-us/web/http/range_requests/index.html
rename to files/en-us/web/http/range_requests/index.md
diff --git a/files/en-us/web/http/redirections/index.html b/files/en-us/web/http/redirections/index.md
similarity index 100%
rename from files/en-us/web/http/redirections/index.html
rename to files/en-us/web/http/redirections/index.md
diff --git a/files/en-us/web/http/resources_and_specifications/index.html b/files/en-us/web/http/resources_and_specifications/index.md
similarity index 100%
rename from files/en-us/web/http/resources_and_specifications/index.html
rename to files/en-us/web/http/resources_and_specifications/index.md
diff --git a/files/en-us/web/http/resources_and_uris/index.html b/files/en-us/web/http/resources_and_uris/index.md
similarity index 100%
rename from files/en-us/web/http/resources_and_uris/index.html
rename to files/en-us/web/http/resources_and_uris/index.md
diff --git a/files/en-us/web/http/session/index.html b/files/en-us/web/http/session/index.md
similarity index 100%
rename from files/en-us/web/http/session/index.html
rename to files/en-us/web/http/session/index.md
diff --git a/files/en-us/web/http/status/100/index.html b/files/en-us/web/http/status/100/index.md
similarity index 100%
rename from files/en-us/web/http/status/100/index.html
rename to files/en-us/web/http/status/100/index.md
diff --git a/files/en-us/web/http/status/101/index.html b/files/en-us/web/http/status/101/index.md
similarity index 100%
rename from files/en-us/web/http/status/101/index.html
rename to files/en-us/web/http/status/101/index.md
diff --git a/files/en-us/web/http/status/103/index.html b/files/en-us/web/http/status/103/index.md
similarity index 100%
rename from files/en-us/web/http/status/103/index.html
rename to files/en-us/web/http/status/103/index.md
diff --git a/files/en-us/web/http/status/200/index.html b/files/en-us/web/http/status/200/index.md
similarity index 100%
rename from files/en-us/web/http/status/200/index.html
rename to files/en-us/web/http/status/200/index.md
diff --git a/files/en-us/web/http/status/201/index.html b/files/en-us/web/http/status/201/index.md
similarity index 100%
rename from files/en-us/web/http/status/201/index.html
rename to files/en-us/web/http/status/201/index.md
diff --git a/files/en-us/web/http/status/202/index.html b/files/en-us/web/http/status/202/index.md
similarity index 100%
rename from files/en-us/web/http/status/202/index.html
rename to files/en-us/web/http/status/202/index.md
diff --git a/files/en-us/web/http/status/203/index.html b/files/en-us/web/http/status/203/index.md
similarity index 100%
rename from files/en-us/web/http/status/203/index.html
rename to files/en-us/web/http/status/203/index.md
diff --git a/files/en-us/web/http/status/204/index.html b/files/en-us/web/http/status/204/index.md
similarity index 100%
rename from files/en-us/web/http/status/204/index.html
rename to files/en-us/web/http/status/204/index.md
diff --git a/files/en-us/web/http/status/205/index.html b/files/en-us/web/http/status/205/index.md
similarity index 100%
rename from files/en-us/web/http/status/205/index.html
rename to files/en-us/web/http/status/205/index.md
diff --git a/files/en-us/web/http/status/206/index.html b/files/en-us/web/http/status/206/index.md
similarity index 100%
rename from files/en-us/web/http/status/206/index.html
rename to files/en-us/web/http/status/206/index.md
diff --git a/files/en-us/web/http/status/300/index.html b/files/en-us/web/http/status/300/index.md
similarity index 100%
rename from files/en-us/web/http/status/300/index.html
rename to files/en-us/web/http/status/300/index.md
diff --git a/files/en-us/web/http/status/301/index.html b/files/en-us/web/http/status/301/index.md
similarity index 100%
rename from files/en-us/web/http/status/301/index.html
rename to files/en-us/web/http/status/301/index.md
diff --git a/files/en-us/web/http/status/302/index.html b/files/en-us/web/http/status/302/index.md
similarity index 100%
rename from files/en-us/web/http/status/302/index.html
rename to files/en-us/web/http/status/302/index.md
diff --git a/files/en-us/web/http/status/303/index.html b/files/en-us/web/http/status/303/index.md
similarity index 100%
rename from files/en-us/web/http/status/303/index.html
rename to files/en-us/web/http/status/303/index.md
diff --git a/files/en-us/web/http/status/304/index.html b/files/en-us/web/http/status/304/index.md
similarity index 100%
rename from files/en-us/web/http/status/304/index.html
rename to files/en-us/web/http/status/304/index.md
diff --git a/files/en-us/web/http/status/307/index.html b/files/en-us/web/http/status/307/index.md
similarity index 100%
rename from files/en-us/web/http/status/307/index.html
rename to files/en-us/web/http/status/307/index.md
diff --git a/files/en-us/web/http/status/308/index.html b/files/en-us/web/http/status/308/index.md
similarity index 100%
rename from files/en-us/web/http/status/308/index.html
rename to files/en-us/web/http/status/308/index.md
diff --git a/files/en-us/web/http/status/400/index.html b/files/en-us/web/http/status/400/index.md
similarity index 100%
rename from files/en-us/web/http/status/400/index.html
rename to files/en-us/web/http/status/400/index.md
diff --git a/files/en-us/web/http/status/401/index.html b/files/en-us/web/http/status/401/index.md
similarity index 100%
rename from files/en-us/web/http/status/401/index.html
rename to files/en-us/web/http/status/401/index.md
diff --git a/files/en-us/web/http/status/402/index.html b/files/en-us/web/http/status/402/index.md
similarity index 100%
rename from files/en-us/web/http/status/402/index.html
rename to files/en-us/web/http/status/402/index.md
diff --git a/files/en-us/web/http/status/403/index.html b/files/en-us/web/http/status/403/index.md
similarity index 100%
rename from files/en-us/web/http/status/403/index.html
rename to files/en-us/web/http/status/403/index.md
diff --git a/files/en-us/web/http/status/404/index.html b/files/en-us/web/http/status/404/index.md
similarity index 100%
rename from files/en-us/web/http/status/404/index.html
rename to files/en-us/web/http/status/404/index.md
diff --git a/files/en-us/web/http/status/405/index.html b/files/en-us/web/http/status/405/index.md
similarity index 100%
rename from files/en-us/web/http/status/405/index.html
rename to files/en-us/web/http/status/405/index.md
diff --git a/files/en-us/web/http/status/406/index.html b/files/en-us/web/http/status/406/index.md
similarity index 100%
rename from files/en-us/web/http/status/406/index.html
rename to files/en-us/web/http/status/406/index.md
diff --git a/files/en-us/web/http/status/407/index.html b/files/en-us/web/http/status/407/index.md
similarity index 100%
rename from files/en-us/web/http/status/407/index.html
rename to files/en-us/web/http/status/407/index.md
diff --git a/files/en-us/web/http/status/408/index.html b/files/en-us/web/http/status/408/index.md
similarity index 100%
rename from files/en-us/web/http/status/408/index.html
rename to files/en-us/web/http/status/408/index.md
diff --git a/files/en-us/web/http/status/409/index.html b/files/en-us/web/http/status/409/index.md
similarity index 100%
rename from files/en-us/web/http/status/409/index.html
rename to files/en-us/web/http/status/409/index.md
diff --git a/files/en-us/web/http/status/410/index.html b/files/en-us/web/http/status/410/index.md
similarity index 100%
rename from files/en-us/web/http/status/410/index.html
rename to files/en-us/web/http/status/410/index.md
diff --git a/files/en-us/web/http/status/411/index.html b/files/en-us/web/http/status/411/index.md
similarity index 100%
rename from files/en-us/web/http/status/411/index.html
rename to files/en-us/web/http/status/411/index.md
diff --git a/files/en-us/web/http/status/412/index.html b/files/en-us/web/http/status/412/index.md
similarity index 100%
rename from files/en-us/web/http/status/412/index.html
rename to files/en-us/web/http/status/412/index.md
diff --git a/files/en-us/web/http/status/413/index.html b/files/en-us/web/http/status/413/index.md
similarity index 100%
rename from files/en-us/web/http/status/413/index.html
rename to files/en-us/web/http/status/413/index.md
diff --git a/files/en-us/web/http/status/414/index.html b/files/en-us/web/http/status/414/index.md
similarity index 100%
rename from files/en-us/web/http/status/414/index.html
rename to files/en-us/web/http/status/414/index.md
diff --git a/files/en-us/web/http/status/415/index.html b/files/en-us/web/http/status/415/index.md
similarity index 100%
rename from files/en-us/web/http/status/415/index.html
rename to files/en-us/web/http/status/415/index.md
diff --git a/files/en-us/web/http/status/416/index.html b/files/en-us/web/http/status/416/index.md
similarity index 100%
rename from files/en-us/web/http/status/416/index.html
rename to files/en-us/web/http/status/416/index.md
diff --git a/files/en-us/web/http/status/417/index.html b/files/en-us/web/http/status/417/index.md
similarity index 100%
rename from files/en-us/web/http/status/417/index.html
rename to files/en-us/web/http/status/417/index.md
diff --git a/files/en-us/web/http/status/418/index.html b/files/en-us/web/http/status/418/index.md
similarity index 100%
rename from files/en-us/web/http/status/418/index.html
rename to files/en-us/web/http/status/418/index.md
diff --git a/files/en-us/web/http/status/422/index.html b/files/en-us/web/http/status/422/index.md
similarity index 100%
rename from files/en-us/web/http/status/422/index.html
rename to files/en-us/web/http/status/422/index.md
diff --git a/files/en-us/web/http/status/425/index.html b/files/en-us/web/http/status/425/index.md
similarity index 100%
rename from files/en-us/web/http/status/425/index.html
rename to files/en-us/web/http/status/425/index.md
diff --git a/files/en-us/web/http/status/426/index.html b/files/en-us/web/http/status/426/index.md
similarity index 100%
rename from files/en-us/web/http/status/426/index.html
rename to files/en-us/web/http/status/426/index.md
diff --git a/files/en-us/web/http/status/428/index.html b/files/en-us/web/http/status/428/index.md
similarity index 100%
rename from files/en-us/web/http/status/428/index.html
rename to files/en-us/web/http/status/428/index.md
diff --git a/files/en-us/web/http/status/429/index.html b/files/en-us/web/http/status/429/index.md
similarity index 100%
rename from files/en-us/web/http/status/429/index.html
rename to files/en-us/web/http/status/429/index.md
diff --git a/files/en-us/web/http/status/431/index.html b/files/en-us/web/http/status/431/index.md
similarity index 100%
rename from files/en-us/web/http/status/431/index.html
rename to files/en-us/web/http/status/431/index.md
diff --git a/files/en-us/web/http/status/451/index.html b/files/en-us/web/http/status/451/index.md
similarity index 100%
rename from files/en-us/web/http/status/451/index.html
rename to files/en-us/web/http/status/451/index.md
diff --git a/files/en-us/web/http/status/500/index.html b/files/en-us/web/http/status/500/index.md
similarity index 100%
rename from files/en-us/web/http/status/500/index.html
rename to files/en-us/web/http/status/500/index.md
diff --git a/files/en-us/web/http/status/501/index.html b/files/en-us/web/http/status/501/index.md
similarity index 100%
rename from files/en-us/web/http/status/501/index.html
rename to files/en-us/web/http/status/501/index.md
diff --git a/files/en-us/web/http/status/502/index.html b/files/en-us/web/http/status/502/index.md
similarity index 100%
rename from files/en-us/web/http/status/502/index.html
rename to files/en-us/web/http/status/502/index.md
diff --git a/files/en-us/web/http/status/503/index.html b/files/en-us/web/http/status/503/index.md
similarity index 100%
rename from files/en-us/web/http/status/503/index.html
rename to files/en-us/web/http/status/503/index.md
diff --git a/files/en-us/web/http/status/504/index.html b/files/en-us/web/http/status/504/index.md
similarity index 100%
rename from files/en-us/web/http/status/504/index.html
rename to files/en-us/web/http/status/504/index.md
diff --git a/files/en-us/web/http/status/505/index.html b/files/en-us/web/http/status/505/index.md
similarity index 100%
rename from files/en-us/web/http/status/505/index.html
rename to files/en-us/web/http/status/505/index.md
diff --git a/files/en-us/web/http/status/506/index.html b/files/en-us/web/http/status/506/index.md
similarity index 100%
rename from files/en-us/web/http/status/506/index.html
rename to files/en-us/web/http/status/506/index.md
diff --git a/files/en-us/web/http/status/507/index.html b/files/en-us/web/http/status/507/index.md
similarity index 100%
rename from files/en-us/web/http/status/507/index.html
rename to files/en-us/web/http/status/507/index.md
diff --git a/files/en-us/web/http/status/508/index.html b/files/en-us/web/http/status/508/index.md
similarity index 100%
rename from files/en-us/web/http/status/508/index.html
rename to files/en-us/web/http/status/508/index.md
diff --git a/files/en-us/web/http/status/510/index.html b/files/en-us/web/http/status/510/index.md
similarity index 100%
rename from files/en-us/web/http/status/510/index.html
rename to files/en-us/web/http/status/510/index.md
diff --git a/files/en-us/web/http/status/511/index.html b/files/en-us/web/http/status/511/index.md
similarity index 100%
rename from files/en-us/web/http/status/511/index.html
rename to files/en-us/web/http/status/511/index.md
diff --git a/files/en-us/web/http/status/index.html b/files/en-us/web/http/status/index.md
similarity index 100%
rename from files/en-us/web/http/status/index.html
rename to files/en-us/web/http/status/index.md

From d18574b42a37a2cc6066e89036ccab58b142cdfb Mon Sep 17 00:00:00 2001
From: Jean-Yves Perrier <jypenator@gmail.com>
Date: Thu, 12 Aug 2021 12:28:36 +0200
Subject: [PATCH 2/9] Convert HTTP docs to markdown

---
 files/en-us/web/http/authentication/index.md  | 169 ++--
 .../index.md                                  |  64 +-
 .../http/basics_of_http/data_uris/index.md    | 181 ++--
 .../basics_of_http/evolution_of_http/index.md | 262 +++--
 .../identifying_resources_on_the_web/index.md | 274 ++---
 files/en-us/web/http/basics_of_http/index.md  |  64 +-
 .../mime_types/common_types/index.md          | 468 ++-------
 .../http/basics_of_http/mime_types/index.md   | 913 ++++++++---------
 .../basics_of_http/resource_urls/index.md     | 133 ++-
 .../index.md                                  | 535 ++++------
 files/en-us/web/http/caching/index.md         | 198 ++--
 files/en-us/web/http/compression/index.md     |  66 +-
 .../web/http/conditional_requests/index.md    | 152 ++-
 .../index.md                                  | 129 ++-
 .../index.md                                  |  86 +-
 .../web/http/content_negotiation/index.md     | 139 +--
 .../list_of_default_accept_values/index.md    | 328 ++----
 files/en-us/web/http/cookies/index.md         | 273 +++--
 .../corsalloworiginnotmatchingorigin/index.md |  77 +-
 .../cors/errors/corsdidnotsucceed/index.md    |  75 +-
 .../http/cors/errors/corsdisabled/index.md    |  66 +-
 .../corsexternalredirectnotallowed/index.md   |  63 +-
 .../errors/corsinvalidallowheader/index.md    |  68 +-
 .../errors/corsinvalidallowmethod/index.md    |  71 +-
 .../cors/errors/corsmethodnotfound/index.md   |  73 +-
 .../corsmissingallowcredentials/index.md      |  77 +-
 .../index.md                                  |  26 +-
 .../errors/corsmissingalloworigin/index.md    | 112 +--
 .../index.md                                  |  59 +-
 .../corsnotsupportingcredentials/index.md     |  34 +-
 .../errors/corsoriginheadernotadded/index.md  |  52 +-
 .../corspreflightdidnotsucceed/index.md       |  58 +-
 .../cors/errors/corsrequestnothttp/index.md   |  80 +-
 files/en-us/web/http/cors/errors/index.md     |  82 +-
 files/en-us/web/http/cors/index.md            | 621 ++++++------
 .../index.md                                  |  85 +-
 .../web/http/csp/errors/cspviolation/index.md |  92 +-
 files/en-us/web/http/csp/errors/index.md      |  80 +-
 files/en-us/web/http/csp/index.md             | 477 ++++-----
 files/en-us/web/http/feature_policy/index.md  | 201 ++--
 .../using_feature_policy/index.md             | 180 ++--
 .../http/headers/accept-ch-lifetime/index.md  |  75 +-
 .../en-us/web/http/headers/accept-ch/index.md |  53 +-
 .../web/http/headers/accept-charset/index.md  |  42 +-
 .../web/http/headers/accept-encoding/index.md | 110 +--
 .../web/http/headers/accept-language/index.md | 134 +--
 .../web/http/headers/accept-patch/index.md    |  92 +-
 .../web/http/headers/accept-post/index.md     |  90 +-
 .../web/http/headers/accept-ranges/index.md   |  98 +-
 files/en-us/web/http/headers/accept/index.md  |  98 +-
 .../access-control-allow-credentials/index.md | 118 +--
 .../access-control-allow-headers/index.md     | 125 ++-
 .../access-control-allow-methods/index.md     |  68 +-
 .../access-control-allow-origin/index.md      |  94 +-
 .../access-control-expose-headers/index.md    |  79 +-
 .../headers/access-control-max-age/index.md   |  69 +-
 .../access-control-request-headers/index.md   |  55 +-
 .../access-control-request-method/index.md    |  52 +-
 files/en-us/web/http/headers/age/index.md     |  59 +-
 files/en-us/web/http/headers/allow/index.md   |  70 +-
 files/en-us/web/http/headers/alt-svc/index.md |  91 +-
 .../web/http/headers/authorization/index.md   | 118 +--
 .../web/http/headers/cache-control/index.md   | 254 +++--
 .../web/http/headers/clear-site-data/index.md | 117 ++-
 .../web/http/headers/connection/index.md      |  80 +-
 .../http/headers/content-disposition/index.md | 164 ++-
 .../web/http/headers/content-dpr/index.md     |  97 +-
 .../http/headers/content-encoding/index.md    |  91 +-
 .../http/headers/content-language/index.md    | 111 ++-
 .../web/http/headers/content-length/index.md  |  41 +-
 .../http/headers/content-location/index.md    | 205 ++--
 .../web/http/headers/content-range/index.md   |  84 +-
 .../index.md                                  | 152 +--
 .../content-security-policy/base-uri/index.md |  99 +-
 .../block-all-mixed-content/index.md          |  45 +-
 .../child-src/index.md                        |  89 +-
 .../connect-src/index.md                      | 109 +-
 .../default-src/index.md                      | 209 ++--
 .../content-security-policy/font-src/index.md |  77 +-
 .../form-action/index.md                      | 105 +-
 .../frame-ancestors/index.md                  | 133 ++-
 .../frame-src/index.md                        |  82 +-
 .../content-security-policy/img-src/index.md  |  78 +-
 .../headers/content-security-policy/index.md  | 546 +++++-----
 .../manifest-src/index.md                     |  82 +-
 .../media-src/index.md                        |  85 +-
 .../navigate-to/index.md                      | 109 +-
 .../object-src/index.md                       | 104 +-
 .../plugin-types/index.md                     | 109 +-
 .../prefetch-src/index.md                     |  73 +-
 .../content-security-policy/referrer/index.md |  99 +-
 .../report-to/index.md                        | 100 +-
 .../report-uri/index.md                       | 166 ++--
 .../require-sri-for/index.md                  |  81 +-
 .../require-trusted-types-for/index.md        |  52 +-
 .../content-security-policy/sandbox/index.md  | 133 +--
 .../script-src-attr/index.md                  | 146 ++-
 .../script-src-elem/index.md                  | 158 ++-
 .../script-src/index.md                       | 252 +++--
 .../style-src-attr/index.md                   |  97 +-
 .../style-src-elem/index.md                   |  99 +-
 .../style-src/index.md                        | 200 ++--
 .../trusted-types/index.md                    |  60 +-
 .../upgrade-insecure-requests/index.md        | 152 +--
 .../worker-src/index.md                       |  76 +-
 .../web/http/headers/content-type/index.md    | 141 +--
 files/en-us/web/http/headers/cookie/index.md  |  58 +-
 files/en-us/web/http/headers/cookie2/index.md |  57 +-
 .../cross-origin-embedder-policy/index.md     |  86 +-
 .../cross-origin-opener-policy/index.md       |  84 +-
 .../cross-origin-resource-policy/index.md     |  77 +-
 files/en-us/web/http/headers/date/index.md    | 149 ++-
 .../web/http/headers/device-memory/index.md   | 100 +-
 files/en-us/web/http/headers/digest/index.md  | 108 +-
 files/en-us/web/http/headers/dnt/index.md     |  92 +-
 .../en-us/web/http/headers/downlink/index.md  |  88 +-
 files/en-us/web/http/headers/dpr/index.md     | 102 +-
 .../web/http/headers/early-data/index.md      |  36 +-
 files/en-us/web/http/headers/ect/index.md     |  87 +-
 files/en-us/web/http/headers/etag/index.md    | 135 ++-
 .../en-us/web/http/headers/expect-ct/index.md | 124 +--
 files/en-us/web/http/headers/expect/index.md  |  96 +-
 files/en-us/web/http/headers/expires/index.md |  65 +-
 .../feature-policy/accelerometer/index.md     |  37 +-
 .../ambient-light-sensor/index.md             |  37 +-
 .../headers/feature-policy/autoplay/index.md  |  58 +-
 .../headers/feature-policy/battery/index.md   |  43 +-
 .../headers/feature-policy/camera/index.md    |  44 +-
 .../feature-policy/display-capture/index.md   |  43 +-
 .../feature-policy/document-domain/index.md   |  60 +-
 .../feature-policy/encrypted-media/index.md   |  36 +-
 .../feature-policy/fullscreen/index.md        |  69 +-
 .../headers/feature-policy/gamepad/index.md   |  71 +-
 .../feature-policy/geolocation/index.md       |  94 +-
 .../headers/feature-policy/gyroscope/index.md |  36 +-
 .../web/http/headers/feature-policy/index.md  | 288 +++---
 .../feature-policy/layout-animations/index.md |  32 +-
 .../legacy-image-formats/index.md             |  32 +-
 .../feature-policy/magnetometer/index.md      |  37 +-
 .../feature-policy/microphone/index.md        |  59 +-
 .../http/headers/feature-policy/midi/index.md |  36 +-
 .../feature-policy/oversized-images/index.md  |  32 +-
 .../headers/feature-policy/payment/index.md   |  59 +-
 .../picture-in-picture/index.md               |  53 +-
 .../publickey-credentials-get/index.md        |  42 +-
 .../feature-policy/screen-wake-lock/index.md  |  67 +-
 .../headers/feature-policy/sync-xhr/index.md  |  30 +-
 .../unoptimized-images/index.md               |  32 +-
 .../feature-policy/unsized-media/index.md     |  36 +-
 .../http/headers/feature-policy/usb/index.md  |  34 +-
 .../headers/feature-policy/vibrate/index.md   |  57 +-
 .../http/headers/feature-policy/vr/index.md   |  69 +-
 .../headers/feature-policy/web-share/index.md |  38 +-
 .../xr-spatial-tracking/index.md              |  40 +-
 .../http/headers/feature-policy/xr/index.md   |   5 +-
 .../en-us/web/http/headers/forwarded/index.md | 123 ++-
 files/en-us/web/http/headers/from/index.md    |  55 +-
 files/en-us/web/http/headers/host/index.md    |  59 +-
 .../en-us/web/http/headers/if-match/index.md  | 121 ++-
 .../http/headers/if-modified-since/index.md   | 121 ++-
 .../web/http/headers/if-none-match/index.md   |  91 +-
 .../en-us/web/http/headers/if-range/index.md  | 135 ++-
 .../http/headers/if-unmodified-since/index.md | 133 ++-
 files/en-us/web/http/headers/index.md         | 831 ++++++++--------
 .../web/http/headers/keep-alive/index.md      |  96 +-
 .../http/headers/large-allocation/index.md    | 157 ++-
 .../web/http/headers/last-modified/index.md   |  95 +-
 files/en-us/web/http/headers/link/index.md    |  50 +-
 .../en-us/web/http/headers/location/index.md  | 106 +-
 files/en-us/web/http/headers/nel/index.md     |  41 +-
 files/en-us/web/http/headers/origin/index.md  |  85 +-
 files/en-us/web/http/headers/pragma/index.md  |  71 +-
 .../http/headers/proxy-authenticate/index.md  |  70 +-
 .../http/headers/proxy-authorization/index.md |  82 +-
 .../public-key-pins-report-only/index.md      | 135 ++-
 .../web/http/headers/public-key-pins/index.md | 151 ++-
 files/en-us/web/http/headers/range/index.md   |  90 +-
 files/en-us/web/http/headers/referer/index.md |  78 +-
 .../web/http/headers/referrer-policy/index.md | 408 +++-----
 .../web/http/headers/retry-after/index.md     | 101 +-
 files/en-us/web/http/headers/rtt/index.md     |  87 +-
 .../en-us/web/http/headers/save-data/index.md | 163 ++-
 .../web/http/headers/sec-fetch-dest/index.md  | 244 +++--
 .../web/http/headers/sec-fetch-mode/index.md  | 128 ++-
 .../web/http/headers/sec-fetch-site/index.md  | 122 ++-
 .../web/http/headers/sec-fetch-user/index.md  |  87 +-
 .../headers/sec-websocket-accept/index.md     |  48 +-
 .../web/http/headers/server-timing/index.md   |  75 +-
 files/en-us/web/http/headers/server/index.md  |  65 +-
 .../web/http/headers/set-cookie/index.md      | 436 ++++----
 .../http/headers/set-cookie/samesite/index.md | 162 ++-
 .../web/http/headers/set-cookie2/index.md     |  77 +-
 .../en-us/web/http/headers/sourcemap/index.md |  72 +-
 .../strict-transport-security/index.md        | 262 +++--
 files/en-us/web/http/headers/te/index.md      |  97 +-
 .../http/headers/timing-allow-origin/index.md |  71 +-
 files/en-us/web/http/headers/tk/index.md      | 100 +-
 files/en-us/web/http/headers/trailer/index.md | 135 ++-
 .../http/headers/transfer-encoding/index.md   | 158 ++-
 .../upgrade-insecure-requests/index.md        |  60 +-
 files/en-us/web/http/headers/upgrade/index.md | 133 ++-
 .../http/headers/user-agent/firefox/index.md  | 680 +++++--------
 .../web/http/headers/user-agent/index.md      | 163 ++-
 files/en-us/web/http/headers/vary/index.md    |  95 +-
 files/en-us/web/http/headers/via/index.md     |  67 +-
 .../web/http/headers/viewport-width/index.md  |  95 +-
 .../web/http/headers/want-digest/index.md     | 172 ++--
 files/en-us/web/http/headers/warning/index.md | 178 ++--
 files/en-us/web/http/headers/width/index.md   |  96 +-
 .../http/headers/www-authenticate/index.md    |  78 +-
 .../headers/x-content-type-options/index.md   | 130 ++-
 .../headers/x-dns-prefetch-control/index.md   | 153 ++-
 .../web/http/headers/x-forwarded-for/index.md |  98 +-
 .../http/headers/x-forwarded-host/index.md    |  79 +-
 .../http/headers/x-forwarded-proto/index.md   |  81 +-
 .../web/http/headers/x-frame-options/index.md | 153 ++-
 .../http/headers/x-xss-protection/index.md    | 115 ++-
 files/en-us/web/http/index.md                 |  92 +-
 files/en-us/web/http/index/index.md           |   6 +-
 .../web/http/link_prefetching_faq/index.md    | 114 +--
 files/en-us/web/http/messages/index.md        | 162 ++-
 files/en-us/web/http/methods/connect/index.md |  60 +-
 files/en-us/web/http/methods/delete/index.md  |  74 +-
 files/en-us/web/http/methods/get/index.md     |  31 +-
 files/en-us/web/http/methods/head/index.md    |  33 +-
 files/en-us/web/http/methods/index.md         |  95 +-
 files/en-us/web/http/methods/options/index.md | 148 +--
 files/en-us/web/http/methods/patch/index.md   |  84 +-
 files/en-us/web/http/methods/post/index.md    |  94 +-
 files/en-us/web/http/methods/put/index.md     |  60 +-
 files/en-us/web/http/methods/trace/index.md   |  25 +-
 .../web/http/network_error_logging/index.md   | 179 ++--
 files/en-us/web/http/overview/index.md        | 208 ++--
 .../http/protocol_upgrade_mechanism/index.md  | 172 ++--
 .../http/proxy_servers_and_tunneling/index.md | 102 +-
 .../index.md                                  | 934 +++++++++---------
 .../web/http/public_key_pinning/index.md      | 182 ++--
 files/en-us/web/http/range_requests/index.md  | 137 ++-
 files/en-us/web/http/redirections/index.md    | 355 +++----
 .../resources_and_specifications/index.md     | 303 +-----
 .../web/http/resources_and_uris/index.md      |  26 +-
 files/en-us/web/http/session/index.md         | 294 +++---
 files/en-us/web/http/status/100/index.md      |  41 +-
 files/en-us/web/http/status/101/index.md      |  96 +-
 files/en-us/web/http/status/103/index.md      |  58 +-
 files/en-us/web/http/status/200/index.md      |  36 +-
 files/en-us/web/http/status/201/index.md      |  42 +-
 files/en-us/web/http/status/202/index.md      |  72 +-
 files/en-us/web/http/status/203/index.md      |  71 +-
 files/en-us/web/http/status/204/index.md      |  69 +-
 files/en-us/web/http/status/205/index.md      |  55 +-
 files/en-us/web/http/status/206/index.md      |  98 +-
 files/en-us/web/http/status/300/index.md      |  72 +-
 files/en-us/web/http/status/301/index.md      |  40 +-
 files/en-us/web/http/status/302/index.md      |  66 +-
 files/en-us/web/http/status/303/index.md      |  44 +-
 files/en-us/web/http/status/304/index.md      |  68 +-
 files/en-us/web/http/status/307/index.md      |  68 +-
 files/en-us/web/http/status/308/index.md      |  58 +-
 files/en-us/web/http/status/400/index.md      |  39 +-
 files/en-us/web/http/status/401/index.md      |  60 +-
 files/en-us/web/http/status/402/index.md      |  60 +-
 files/en-us/web/http/status/403/index.md      |  33 +-
 files/en-us/web/http/status/404/index.md      |  42 +-
 files/en-us/web/http/status/405/index.md      |  43 +-
 files/en-us/web/http/status/406/index.md      |  65 +-
 files/en-us/web/http/status/407/index.md      |  58 +-
 files/en-us/web/http/status/408/index.md      |  87 +-
 files/en-us/web/http/status/409/index.md      |  24 +-
 files/en-us/web/http/status/410/index.md      |  30 +-
 files/en-us/web/http/status/411/index.md      |  77 +-
 files/en-us/web/http/status/412/index.md      |  84 +-
 files/en-us/web/http/status/413/index.md      |  37 +-
 files/en-us/web/http/status/414/index.md      |  78 +-
 files/en-us/web/http/status/415/index.md      |  73 +-
 files/en-us/web/http/status/416/index.md      |  30 +-
 files/en-us/web/http/status/417/index.md      |  49 +-
 files/en-us/web/http/status/418/index.md      |  46 +-
 files/en-us/web/http/status/422/index.md      |  52 +-
 files/en-us/web/http/status/425/index.md      |  28 +-
 files/en-us/web/http/status/426/index.md      |  69 +-
 files/en-us/web/http/status/428/index.md      |  59 +-
 files/en-us/web/http/status/429/index.md      |  49 +-
 files/en-us/web/http/status/431/index.md      |  95 +-
 files/en-us/web/http/status/451/index.md      |  60 +-
 files/en-us/web/http/status/500/index.md      |  24 +-
 files/en-us/web/http/status/501/index.md      |  33 +-
 files/en-us/web/http/status/502/index.md      |  29 +-
 files/en-us/web/http/status/503/index.md      |  32 +-
 files/en-us/web/http/status/504/index.md      |  28 +-
 files/en-us/web/http/status/505/index.md      |  45 +-
 files/en-us/web/http/status/506/index.md      |  31 +-
 files/en-us/web/http/status/507/index.md      |  31 +-
 files/en-us/web/http/status/508/index.md      |  47 +-
 files/en-us/web/http/status/510/index.md      |  45 +-
 files/en-us/web/http/status/511/index.md      |  57 +-
 files/en-us/web/http/status/index.md          | 356 ++++---
 297 files changed, 15269 insertions(+), 18465 deletions(-)

diff --git a/files/en-us/web/http/authentication/index.md b/files/en-us/web/http/authentication/index.md
index 4b55c032e4f18d3..6eb3adb27cad06c 100644
--- a/files/en-us/web/http/authentication/index.md
+++ b/files/en-us/web/http/authentication/index.md
@@ -8,135 +8,134 @@ tags:
   - HTTP
   - Security
 ---
-<div>{{HTTPSidebar}}</div>
+{{HTTPSidebar}}
 
-<p class="summary">HTTP provides a general framework for access control and authentication. This page is an introduction to the HTTP framework for authentication, and shows how to restrict access to your server using the HTTP "Basic" schema.</p>
+HTTP provides a general framework for access control and authentication. This page is an introduction to the HTTP framework for authentication, and shows how to restrict access to your server using the HTTP "Basic" schema.
 
-<h2 id="The_general_HTTP_authentication_framework">The general HTTP authentication framework</h2>
+## The general HTTP authentication framework
 
-<p>{{RFC("7235")}} defines the HTTP authentication framework, which can be used by a server to {{glossary("challenge")}} a client request, and by a client to provide authentication information.</p>
+{{RFC("7235")}} defines the HTTP authentication framework, which can be used by a server to {{glossary("challenge")}} a client request, and by a client to provide authentication information.
 
-<p>The challenge and response flow works like this:</p>
+The challenge and response flow works like this:
 
-<ol>
- <li>The server responds to a client with a {{HTTPStatus("401")}} (Unauthorized) response status and provides information on how to authorize with a {{HTTPHeader("WWW-Authenticate")}} response header containing at least one challenge.</li>
- <li>A client that wants to authenticate itself with the server can then do so by including an {{HTTPHeader("Authorization")}} request header with the credentials.</li>
- <li>Usually a client will present a password prompt to the user and will then issue the request including the correct <code>Authorization</code> header.</li>
-</ol>
+1.  The server responds to a client with a {{HTTPStatus("401")}} (Unauthorized) response status and provides information on how to authorize with a {{HTTPHeader("WWW-Authenticate")}} response header containing at least one challenge.
+2.  A client that wants to authenticate itself with the server can then do so by including an {{HTTPHeader("Authorization")}} request header with the credentials.
+3.  Usually a client will present a password prompt to the user and will then issue the request including the correct `Authorization` header.
 
-<p><img alt="A sequence diagram illustrating HTTP messages between a client and a server lifeline." src="httpauth.png" title="Sequence Diagram of Client-server HTTP Authentication"></p>
+![A sequence diagram illustrating HTTP messages between a client and a server lifeline.](httpauth.png "Sequence Diagram of Client-server HTTP Authentication")
 
-<p>In the case of a "Basic" authentication like shown in the figure, the exchange <strong>must</strong> happen over an HTTPS (TLS) connection to be secure.</p>
+In the case of a "Basic" authentication like shown in the figure, the exchange **must** happen over an HTTPS (TLS) connection to be secure.
 
-<h3 id="Proxy_authentication">Proxy authentication</h3>
+### Proxy authentication
 
-<p>The same challenge and response mechanism can be used for <em>proxy authentication</em>. As both resource authentication and proxy authentication can coexist, a different set of headers and status codes is needed. In the case of proxies, the challenging status code is {{HTTPStatus("407")}} (Proxy Authentication Required), the {{HTTPHeader("Proxy-Authenticate")}} response header contains at least one challenge applicable to the proxy, and the {{HTTPHeader("Proxy-Authorization")}} request header is used for providing the credentials to the proxy server.</p>
+The same challenge and response mechanism can be used for _proxy authentication_. As both resource authentication and proxy authentication can coexist, a different set of headers and status codes is needed. In the case of proxies, the challenging status code is {{HTTPStatus("407")}} (Proxy Authentication Required), the {{HTTPHeader("Proxy-Authenticate")}} response header contains at least one challenge applicable to the proxy, and the {{HTTPHeader("Proxy-Authorization")}} request header is used for providing the credentials to the proxy server.
 
-<h3 id="Access_forbidden">Access forbidden</h3>
+### Access forbidden
 
-<p>If a (proxy) server receives <em>invalid</em> credentials, it should respond with a {{HTTPStatus("401")}} <code>Unauthorized</code> or with a {{HTTPStatus("407")}} <code>Proxy Authentication Required</code>, and the user may send a new request or replace the {{HTTPHeader("Authorization")}} header field.</p>
-<p>If a (proxy) server receives valid credentials that are <em>inadequate</em> to access a given resource, the server should respond with the {{HTTPStatus("403")}} <code>Forbidden</code> status code. Unlike {{HTTPStatus("401")}} <code>Unauthorized</code> or {{HTTPStatus("407")}} <code>Proxy Authentication Required</code>, authentication is impossible for this user and browsers will not propose a new attempt.</p>
-<p>In all cases, the server may prefer returning a {{HTTPStatus("404")}} <code>Not Found</code> status code, to hide the existence of the page to a user without adequate privileges or not correctly authenticated.</p>
+If a (proxy) server receives _invalid_ credentials, it should respond with a {{HTTPStatus("401")}} `Unauthorized` or with a {{HTTPStatus("407")}} `Proxy Authentication Required`, and the user may send a new request or replace the {{HTTPHeader("Authorization")}} header field.
 
-<h3 id="Authentication_of_cross-origin_images">Authentication of cross-origin images</h3>
+If a (proxy) server receives valid credentials that are _inadequate_ to access a given resource, the server should respond with the {{HTTPStatus("403")}} `Forbidden` status code. Unlike {{HTTPStatus("401")}} `Unauthorized` or {{HTTPStatus("407")}} `Proxy Authentication Required`, authentication is impossible for this user and browsers will not propose a new attempt.
 
-<p>A potential security hole recently been fixed by browsers is authentication of cross-site images. From <a href="/en-US/docs/Mozilla/Firefox/Releases/59">Firefox 59</a> onwards, image resources loaded from different origins to the current document are no longer able to trigger HTTP authentication dialogs ({{bug(1423146)}}), preventing user credentials being stolen if attackers were able to embed an arbitrary image into a third-party page.</p>
+In all cases, the server may prefer returning a {{HTTPStatus("404")}} `Not Found` status code, to hide the existence of the page to a user without adequate privileges or not correctly authenticated.
 
-<h3 id="Character_encoding_of_HTTP_authentication">Character encoding of HTTP authentication</h3>
+### Authentication of cross-origin images
 
-<p>Browsers use <code>utf-8</code> encoding for usernames and passwords.</p>
+A potential security hole recently been fixed by browsers is authentication of cross-site images. From [Firefox 59](/en-US/docs/Mozilla/Firefox/Releases/59) onwards, image resources loaded from different origins to the current document are no longer able to trigger HTTP authentication dialogs ({{bug(1423146)}}), preventing user credentials being stolen if attackers were able to embed an arbitrary image into a third-party page.
 
-<p>Firefox once used <code>ISO-8859-1</code>, but changed to <code>utf-8</code> for parity with other browsers and to avoid potential problems as described in {{bug(1419658)}}.</p>
+### Character encoding of HTTP authentication
 
-<h3 id="WWW-Authenticate_and_Proxy-Authenticate_headers">WWW-Authenticate and Proxy-Authenticate headers</h3>
+Browsers use `utf-8` encoding for usernames and passwords.
 
-<p>The {{HTTPHeader("WWW-Authenticate")}} and {{HTTPHeader("Proxy-Authenticate")}} response headers define the authentication method that should be used to gain access to a resource. They must specify which authentication scheme is used, so that the client that wishes to authorize knows how to provide the credentials.</p>
+Firefox once used `ISO-8859-1`, but changed to `utf-8` for parity with other browsers and to avoid potential problems as described in {{bug(1419658)}}.
 
-<p>The syntax for these headers is the following:</p>
+### WWW-Authenticate and Proxy-Authenticate headers
 
-<pre class="brush: html">WWW-Authenticate: &lt;type&gt; realm=&lt;realm&gt;
-Proxy-Authenticate: &lt;type&gt; realm=&lt;realm&gt;
-</pre>
+The {{HTTPHeader("WWW-Authenticate")}} and {{HTTPHeader("Proxy-Authenticate")}} response headers define the authentication method that should be used to gain access to a resource. They must specify which authentication scheme is used, so that the client that wishes to authorize knows how to provide the credentials.
 
-<p>Here, <code>&lt;type&gt;</code> is the authentication scheme ("Basic" is the most common scheme and <a href="#basic_authentication_scheme">introduced below</a>). The <em>realm</em> is used to describe the protected area or to indicate the scope of protection. This could be a message like "Access to the staging site" or similar, so that the user knows to which space they are trying to get access to.</p>
+The syntax for these headers is the following:
 
-<h3 id="Authorization_and_Proxy-Authorization_headers">Authorization and Proxy-Authorization headers</h3>
+```html
+WWW-Authenticate: <type> realm=<realm>
+Proxy-Authenticate: <type> realm=<realm>
+```
 
-<p>The {{HTTPHeader("Authorization")}} and {{HTTPHeader("Proxy-Authorization")}} request headers contain the credentials to authenticate a user agent with a (proxy) server. Here, the <code>&lt;type&gt;</code> is needed again followed by the credentials, which can be encoded or encrypted depending on which authentication scheme is used.</p>
+Here, `<type>` is the authentication scheme ("Basic" is the most common scheme and [introduced below](#basic_authentication_scheme)). The _realm_ is used to describe the protected area or to indicate the scope of protection. This could be a message like "Access to the staging site" or similar, so that the user knows to which space they are trying to get access to.
 
-<pre class="brush: html">Authorization: &lt;type&gt; &lt;credentials&gt;
-Proxy-Authorization: &lt;type&gt; &lt;credentials&gt;
-</pre>
+### Authorization and Proxy-Authorization headers
 
-<h3 id="Authentication_schemes">Authentication schemes</h3>
+The {{HTTPHeader("Authorization")}} and {{HTTPHeader("Proxy-Authorization")}} request headers contain the credentials to authenticate a user agent with a (proxy) server. Here, the `<type>` is needed again followed by the credentials, which can be encoded or encrypted depending on which authentication scheme is used.
 
-<p>The general HTTP authentication framework is used by several authentication schemes. Schemes can differ in security strength and in their availability in client or server software.</p>
+```html
+Authorization: <type> <credentials>
+Proxy-Authorization: <type> <credentials>
+```
 
-<p>The most common authentication scheme is the "Basic" authentication scheme, which is introduced in more detail below. IANA maintains a <a class="external external-icon" href="https://www.iana.org/assignments/http-authschemes/http-authschemes.xhtml">list of authentication schemes</a>, but there are other schemes offered by host services, such as Amazon AWS. Common authentication schemes include:</p>
+### Authentication schemes
 
-<dl>
- <dt><strong>Basic</strong></dt>
- <dd>See {{rfc(7617)}}, base64-encoded credentials. More information below.</dd>
- <dt><strong>Bearer</strong></dt>
- <dd>See {{rfc(6750)}}, bearer tokens to access OAuth 2.0-protected resources</dd>
- <dt><strong>Digest</strong></dt>
- <dd>See {{rfc(7616)}}, only md5 hashing is supported in Firefox, see {{bug(472823)}} for SHA encryption support</dd>
- <dt><strong>HOBA</strong></dt>
- <dd>See {{rfc(7486)}}, Section 3, <strong>H</strong>TTP <strong>O</strong>rigin-<strong>B</strong>ound <strong>A</strong>uthentication, digital-signature-based</dd>
- <dt><strong>Mutual</strong></dt>
- <dd>See {{rfc(8120)}}</dd>
- <dt><strong>AWS4-HMAC-SHA256</strong></dt>
- <dd>See <a href="https://docs.aws.amazon.com/AmazonS3/latest/API/sigv4-auth-using-authorization-header.html">AWS docs</a></dd>
-</dl>
+The general HTTP authentication framework is used by several authentication schemes. Schemes can differ in security strength and in their availability in client or server software.
 
-<h2 id="Basic_authentication_scheme">Basic authentication scheme</h2>
+The most common authentication scheme is the "Basic" authentication scheme, which is introduced in more detail below. IANA maintains a [list of authentication schemes](https://www.iana.org/assignments/http-authschemes/http-authschemes.xhtml), but there are other schemes offered by host services, such as Amazon AWS. Common authentication schemes include:
 
-<p>The "Basic" HTTP authentication scheme is defined in {{rfc(7617)}}, which transmits credentials as user ID/password pairs, encoded using base64.</p>
+- **Basic**
+  - : See {{rfc(7617)}}, base64-encoded credentials. More information below.
+- **Bearer**
+  - : See {{rfc(6750)}}, bearer tokens to access OAuth 2.0-protected resources
+- **Digest**
+  - : See {{rfc(7616)}}, only md5 hashing is supported in Firefox, see {{bug(472823)}} for SHA encryption support
+- **HOBA**
+  - : See {{rfc(7486)}}, Section 3, **H**TTP **O**rigin-**B**ound **A**uthentication, digital-signature-based
+- **Mutual**
+  - : See {{rfc(8120)}}
+- **AWS4-HMAC-SHA256**
+  - : See [AWS docs](https://docs.aws.amazon.com/AmazonS3/latest/API/sigv4-auth-using-authorization-header.html)
 
-<h3 id="Security_of_basic_authentication">Security of basic authentication</h3>
+## Basic authentication scheme
 
-<p>As the user ID and password are passed over the network as clear text (it is base64 encoded, but base64 is a reversible encoding), the basic authentication scheme <strong>is not secure</strong>. HTTPS/TLS should be used with basic authentication. Without these additional security enhancements, basic authentication should not be used to protect sensitive or valuable information.</p>
+The "Basic" HTTP authentication scheme is defined in {{rfc(7617)}}, which transmits credentials as user ID/password pairs, encoded using base64.
 
-<h3 id="Restricting_access_with_Apache_and_basic_authentication">Restricting access with Apache and basic authentication</h3>
+### Security of basic authentication
 
-<p>To password-protect a directory on an Apache server, you will need a <code>.htaccess</code> and a <code>.htpasswd</code> file.</p>
+As the user ID and password are passed over the network as clear text (it is base64 encoded, but base64 is a reversible encoding), the basic authentication scheme **is not secure**. HTTPS/TLS should be used with basic authentication. Without these additional security enhancements, basic authentication should not be used to protect sensitive or valuable information.
 
-<p>The <code>.htaccess</code> file typically looks like this:</p>
+### Restricting access with Apache and basic authentication
 
-<pre>AuthType Basic
-AuthName "Access to the staging site"
-AuthUserFile /path/to/.htpasswd
-Require valid-user</pre>
+To password-protect a directory on an Apache server, you will need a `.htaccess` and a `.htpasswd` file.
 
-<p>The <code>.htaccess</code> file references a <code>.htpasswd</code> file in which each line consists of a username and a password separated by a colon (<code>:</code>). You cannot see the actual passwords as they are <a href="https://httpd.apache.org/docs/2.4/misc/password_encryptions.html">hashed</a> (using MD5-based hashing, in this case). Note that you can name your <code>.htpasswd</code> file differently if you like, but keep in mind this file shouldn't be accessible to anyone. (Apache is usually configured to prevent access to <code>.ht*</code> files).</p>
+The `.htaccess` file typically looks like this:
 
-<pre>aladdin:$apr1$ZjTqBB3f$IF9gdYAGlMrs2fuINjHsz.
-user2:$apr1$O04r.y2H$/vEkesPhVInBByJUkXitA/
-</pre>
+    AuthType Basic
+    AuthName "Access to the staging site"
+    AuthUserFile /path/to/.htpasswd
+    Require valid-user
 
-<h3 id="Restricting_access_with_nginx_and_basic_authentication">Restricting access with nginx and basic authentication</h3>
+The `.htaccess` file references a `.htpasswd` file in which each line consists of a username and a password separated by a colon (`:`). You cannot see the actual passwords as they are [hashed](https://httpd.apache.org/docs/2.4/misc/password_encryptions.html) (using MD5-based hashing, in this case). Note that you can name your `.htpasswd` file differently if you like, but keep in mind this file shouldn't be accessible to anyone. (Apache is usually configured to prevent access to `.ht*` files).
 
-<p>For nginx, you will need to specify a location that you are going to protect and the <code>auth_basic</code> directive that provides the name to the password-protected area. The <code>auth_basic_user_file</code> directive then points to a <code>.htpasswd</code> file containing the encrypted user credentials, just like in the Apache example above.</p>
+    aladdin:$apr1$ZjTqBB3f$IF9gdYAGlMrs2fuINjHsz.
+    user2:$apr1$O04r.y2H$/vEkesPhVInBByJUkXitA/
 
-<pre>location /status {
-    auth_basic           "Access to the staging site";
-    auth_basic_user_file /etc/apache2/.htpasswd;
-}</pre>
+### Restricting access with nginx and basic authentication
 
-<h3 id="Access_using_credentials_in_the_URL">Access using credentials in the URL</h3>
+For nginx, you will need to specify a location that you are going to protect and the `auth_basic` directive that provides the name to the password-protected area. The `auth_basic_user_file` directive then points to a `.htpasswd` file containing the encrypted user credentials, just like in the Apache example above.
 
-<p>Many clients also let you avoid the login prompt by using an encoded URL containing the username and the password like this:</p>
+    location /status {
+        auth_basic           "Access to the staging site";
+        auth_basic_user_file /etc/apache2/.htpasswd;
+    }
 
-<pre class="example-bad">https://username:password@www.example.com/</pre>
+### Access using credentials in the URL
 
-<p><strong>The use of these URLs is deprecated</strong>. In Chrome, the <code>username:password@</code> part in URLs is even <a href="https://bugs.chromium.org/p/chromium/issues/detail?id=82250#c7">stripped out</a> for security reasons. In Firefox, it is checked if the site actually requires authentication and if not, Firefox will warn the user with a prompt "You are about to log in to the site “www.example.com” with the username “username”, but the website does not require authentication. This may be an attempt to trick you."</p>
+Many clients also let you avoid the login prompt by using an encoded URL containing the username and the password like this:
 
-<h2 id="See_also">See also</h2>
+```plain example-bad
+https://username:password@www.example.com/
+```
 
-<ul>
- <li>{{HTTPHeader("WWW-Authenticate")}}</li>
- <li>{{HTTPHeader("Authorization")}}</li>
- <li>{{HTTPHeader("Proxy-Authorization")}}</li>
- <li>{{HTTPHeader("Proxy-Authenticate")}}</li>
- <li>{{HTTPStatus("401")}}, {{HTTPStatus("403")}}, {{HTTPStatus("407")}}</li>
-</ul>
+**The use of these URLs is deprecated**. In Chrome, the `username:password@` part in URLs is even [stripped out](https://bugs.chromium.org/p/chromium/issues/detail?id=82250#c7) for security reasons. In Firefox, it is checked if the site actually requires authentication and if not, Firefox will warn the user with a prompt "You are about to log in to the site “www\.example.com” with the username “username”, but the website does not require authentication. This may be an attempt to trick you."
+
+## See also
+
+- {{HTTPHeader("WWW-Authenticate")}}
+- {{HTTPHeader("Authorization")}}
+- {{HTTPHeader("Proxy-Authorization")}}
+- {{HTTPHeader("Proxy-Authenticate")}}
+- {{HTTPStatus("401")}}, {{HTTPStatus("403")}}, {{HTTPStatus("407")}}
diff --git a/files/en-us/web/http/basics_of_http/choosing_between_www_and_non-www_urls/index.md b/files/en-us/web/http/basics_of_http/choosing_between_www_and_non-www_urls/index.md
index 8c61a1f13218d02..8291ad6272a2891 100644
--- a/files/en-us/web/http/basics_of_http/choosing_between_www_and_non-www_urls/index.md
+++ b/files/en-us/web/http/basics_of_http/choosing_between_www_and_non-www_urls/index.md
@@ -6,63 +6,57 @@ tags:
   - HTTP
   - URL
 ---
-<div>{{HTTPSidebar}}</div>
+{{HTTPSidebar}}
 
-<p class="summary">A recurring question among website owners is whether to choose non-www or www URLs. This page provides some advice on what's best.</p>
+A recurring question among website owners is whether to choose non-www or www URLs. This page provides some advice on what's best.
 
-<h2 id="What_are_domain_names">What are domain names?</h2>
+## What are domain names?
 
-<p>In an HTTP URL, the first substring that follows the initial <code>http://</code> or <code>https://</code> is called the domain name. This domain name is hosted on a server where the document resides.</p>
+In an HTTP URL, the first substring that follows the initial `http://` or `https://` is called the domain name. This domain name is hosted on a server where the document resides.
 
-<p>A server isn't necessarily a physical machine: several servers can reside on the same physical machine. Or, one server can be handled by several machines, cooperating to produce the answer or balancing the load of the requests between them. The key point is that semantically <em>one domain name represents one single server</em>.</p>
+A server isn't necessarily a physical machine: several servers can reside on the same physical machine. Or, one server can be handled by several machines, cooperating to produce the answer or balancing the load of the requests between them. The key point is that semantically _one domain name represents one single server_.
 
-<h2 id="So_do_I_have_to_choose_one_or_the_other_for_my_web_site">So, do I have to choose one or the other for my web site?</h2>
+## So, do I have to choose one or the other for my web site?
 
-<ul>
- <li><strong>Yes</strong>, you need to choose one and stick with it. The choice of which one to have as your canonical location is yours, but if you choose one, stick with it. It will make your website appear more consistent to your users and to search engines. This includes always linking to the chosen domain (which shouldn't be hard if you're using relative URLs in your website) and always sharing links (by email/social networks, etc.) to the same domain.</li>
- <li><strong>No</strong>, you can have two. What is important is that you are coherent and consistent with which one is the official domain. <strong>This official domain is called the <em>canonical</em> name.</strong> All your absolute links should use it. But even so, you can still have the other domain working: HTTP allows two techniques so that it is clear for your users, or search engines, which domain is the canonical one, while still allowing the non-canonical domain to work and provide the expected pages.</li>
-</ul>
+- **Yes**, you need to choose one and stick with it. The choice of which one to have as your canonical location is yours, but if you choose one, stick with it. It will make your website appear more consistent to your users and to search engines. This includes always linking to the chosen domain (which shouldn't be hard if you're using relative URLs in your website) and always sharing links (by email/social networks, etc.) to the same domain.
+- **No**, you can have two. What is important is that you are coherent and consistent with which one is the official domain. **This official domain is called the _canonical_ name.** All your absolute links should use it. But even so, you can still have the other domain working: HTTP allows two techniques so that it is clear for your users, or search engines, which domain is the canonical one, while still allowing the non-canonical domain to work and provide the expected pages.
 
-<p>So, choose one of your domains as your canonical one! There are two techniques below to allow the non-canonical domain to work still.</p>
+So, choose one of your domains as your canonical one! There are two techniques below to allow the non-canonical domain to work still.
 
-<h2 id="Techniques_for_canonical_URLs">Techniques for canonical URLs</h2>
+## Techniques for canonical URLs
 
-<p>There are different ways to choose which website is <em>canonical</em>.</p>
+There are different ways to choose which website is _canonical_.
 
-<h3 id="Using_HTTP_301_redirects">Using HTTP 301 redirects</h3>
+### Using HTTP 301 redirects
 
-<p>In this case, you need to configure the server receiving the HTTP requests (which is most likely the same for www and non-www URLs) to respond with an adequate HTTP {{HTTPStatus(301)}} response to any request to the non-canonical domain. This will redirect the browser trying to access the non-canonical URLs to their canonical equivalent. For example, if you've chosen to use non-www URLs as the canonical type, you should redirect all www URLs to their equivalent URL without the www.</p>
+In this case, you need to configure the server receiving the HTTP requests (which is most likely the same for www and non-www URLs) to respond with an adequate HTTP {{HTTPStatus(301)}} response to any request to the non-canonical domain. This will redirect the browser trying to access the non-canonical URLs to their canonical equivalent. For example, if you've chosen to use non-www URLs as the canonical type, you should redirect all www URLs to their equivalent URL without the www.
 
-<p>Example:</p>
+Example:
 
-<ol>
- <li>A server receives a request for <code>http://www.example.org/whaddup</code> (when the canonical domain is example.org)</li>
- <li>The server answers with a code {{HTTPStatus(301)}} with the header <code>{{HTTPHeader("Location")}}: http://example.org/whaddup</code>.</li>
- <li>The client issues a request to the canonical domain: <code>http://example.org/whatddup</code></li>
-</ol>
+1.  A server receives a request for `http://www.example.org/whaddup` (when the canonical domain is example.org)
+2.  The server answers with a code {{HTTPStatus(301)}} with the header `{{HTTPHeader("Location")}}: http://example.org/whaddup`.
+3.  The client issues a request to the canonical domain: `http://example.org/whatddup`
 
-<p>The<a href="https://github.com/h5bp/html5-boilerplate"> HTML5 boilerplate project</a> has an example on <a href="https://github.com/h5bp/html5-boilerplate/blob/7a22a33d4041c479d0962499e853501073811887/.htaccess#L219-L258">how to configure an Apache server to redirect one domain to the other</a>.</p>
+The[ HTML5 boilerplate project](https://github.com/h5bp/html5-boilerplate) has an example on [how to configure an Apache server to redirect one domain to the other](https://github.com/h5bp/html5-boilerplate/blob/7a22a33d4041c479d0962499e853501073811887/.htaccess#L219-L258).
 
-<h3 id="Using_&lt;link_relcanonical&gt;">Using <em><code>&lt;link rel="canonical"&gt;</code></em></h3>
+### Using _`<link rel="canonical">`_
 
-<p>It is possible to add a special HTML {{HTMLElement("link")}} element to a page to indicate what the canonical address of a page is. This has no impact on the human reader of the page, but tells search engine crawlers where the page actually lives. This way, search engines don't index the same page several times, potentially leading to it being considered as duplicate content or spam, and even removing or lowering your page from the search engine result pages.</p>
+It is possible to add a special HTML {{HTMLElement("link")}} element to a page to indicate what the canonical address of a page is. This has no impact on the human reader of the page, but tells search engine crawlers where the page actually lives. This way, search engines don't index the same page several times, potentially leading to it being considered as duplicate content or spam, and even removing or lowering your page from the search engine result pages.
 
-<p>When adding such a tag, you serve the same content for both domains, telling search engines which URL is canonical. In the previous example, <code>http://www.example.org/whaddup</code> would serve the same content as <code>http://example.org/whaddup</code>, but with an additional {{htmlelement("link")}} element in the head:</p>
+When adding such a tag, you serve the same content for both domains, telling search engines which URL is canonical. In the previous example, `http://www.example.org/whaddup` would serve the same content as `http://example.org/whaddup`, but with an additional {{htmlelement("link")}} element in the head:
 
-<p><code>&lt;link href="http://example.org/whaddup" rel="canonical"&gt;</code></p>
+`<link href="http://example.org/whaddup" rel="canonical">`
 
-<p>Unlike the previous case, browser history will consider non-www and www URLs as independent entries.</p>
+Unlike the previous case, browser history will consider non-www and www URLs as independent entries.
 
-<h2 id="Make_your_page_work_for_both">Make your page work for both</h2>
+## Make your page work for both
 
-<p>With these techniques, you can configure your server to respond correctly for both, the www-prefixed and the non-www-prefixed domains. It is good advice to do this since you can't predict which URL users will type in their browser's URL bar. It is a matter of choosing which type you want to use as your canonical location, then redirecting the other type to it.</p>
+With these techniques, you can configure your server to respond correctly for both, the www-prefixed and the non-www-prefixed domains. It is good advice to do this since you can't predict which URL users will type in their browser's URL bar. It is a matter of choosing which type you want to use as your canonical location, then redirecting the other type to it.
 
-<h2 id="Deciding_the_case">Deciding the case</h2>
+## Deciding the case
 
-<p>This is a very subjective topic it could be considered a <a href="https://bikeshed.com/">bikeshedding</a> issue. If you wish to read deeper, please see some of the <a href="https://www.netlify.com/blog/2017/02/28/to-www-or-not-www/">many</a> <a href="https://www.wpbeginner.com/beginners-guide/www-vs-non-www-which-is-better-for-wordpress-seo/">articles</a> on the subject.</p>
+This is a very subjective topic it could be considered a [bikeshedding](https://bikeshed.com/) issue. If you wish to read deeper, please see some of the [many](https://www.netlify.com/blog/2017/02/28/to-www-or-not-www/) [articles](https://www.wpbeginner.com/beginners-guide/www-vs-non-www-which-is-better-for-wordpress-seo/) on the subject.
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
- <li><a href="https://www.chrisfinke.com/2011/07/25/what-do-people-type-in-the-address-bar/">Stats on what people type in the URL bar</a> (2011)</li>
-</ul>
+- [Stats on what people type in the URL bar](https://www.chrisfinke.com/2011/07/25/what-do-people-type-in-the-address-bar/) (2011)
diff --git a/files/en-us/web/http/basics_of_http/data_uris/index.md b/files/en-us/web/http/basics_of_http/data_uris/index.md
index c04f21cb54b1f2b..73557779563b11e 100644
--- a/files/en-us/web/http/basics_of_http/data_uris/index.md
+++ b/files/en-us/web/http/basics_of_http/data_uris/index.md
@@ -9,132 +9,115 @@ tags:
   - URL
 browser-compat: http.data-url
 ---
-<div>{{HTTPSidebar}}</div>
+{{HTTPSidebar}}
 
-<p><strong>Data URLs</strong>, URLs prefixed with the <code>data:</code> scheme, allow content creators to embed small files inline in documents. They were formerly known as "data URIs" until that name was retired by the WHATWG.</p>
+**Data URLs**, URLs prefixed with the `data:` scheme, allow content creators to embed small files inline in documents. They were formerly known as "data URIs" until that name was retired by the WHATWG.
 
-<div class="notecard note">
-  <p><strong>Note:</strong> Data URLs are treated as unique opaque origins by modern browsers, rather than inheriting the origin of the settings object responsible for the navigation.</p>
-</div>
+> **Note:** Data URLs are treated as unique opaque origins by modern browsers, rather than inheriting the origin of the settings object responsible for the navigation.
 
-<h2 id="Syntax">Syntax</h2>
+## Syntax
 
-<p>Data URLs are composed of four parts: a prefix (<code>data:</code>), a <a href="/en-US/docs/Web/HTTP/Basics_of_HTTP/MIME_types">MIME type</a> indicating the type of data, an optional <code>base64</code> token if non-textual, and the data itself:</p>
+Data URLs are composed of four parts: a prefix (`data:`), a [MIME type](/en-US/docs/Web/HTTP/Basics_of_HTTP/MIME_types) indicating the type of data, an optional `base64` token if non-textual, and the data itself:
 
-<pre class="brush: html">data:[&lt;mediatype&gt;][;base64],&lt;data&gt;
-</pre>
+```html
+data:[<mediatype>][;base64],<data>
+```
 
-<p>The <code>mediatype</code> is a <a href="/en-US/docs/Web/HTTP/Basics_of_HTTP/MIME_types">MIME type</a> string, such as <code>'image/jpeg'</code> for a JPEG image file. If omitted, defaults to <code>text/plain;charset=US-ASCII</code></p>
+The `mediatype` is a [MIME type](/en-US/docs/Web/HTTP/Basics_of_HTTP/MIME_types) string, such as `'image/jpeg'` for a JPEG image file. If omitted, defaults to `text/plain;charset=US-ASCII`
 
-<p>If the data contains <a href="https://datatracker.ietf.org/doc/html/rfc3986#section-2.2">characters defined in RFC 3986 as reserved characters</a>, or contains space characters, newline characters, or other non-printing characters, those characters must be <a href="/en-US/docs/Glossary/percent-encoding">percent-encoded</a> (<em>aka</em> “URL-encoded”).</p>
+If the data contains [characters defined in RFC 3986 as reserved characters](https://datatracker.ietf.org/doc/html/rfc3986#section-2.2), or contains space characters, newline characters, or other non-printing characters, those characters must be [percent-encoded](/en-US/docs/Glossary/percent-encoding) (_aka_ “URL-encoded”).
 
-<p>If the data is textual, you can embed the text (using the appropriate entities or escapes based on the enclosing document's type). Otherwise, you can specify <code>base64</code> to embed base64-encoded binary data. You can find more info on MIME types <a href="/en-US/docs/Web/HTTP/Basics_of_HTTP/MIME_types">here</a> and <a href="/en-US/docs/Web/HTTP/Basics_of_HTTP/MIME_types/Common_types">here</a>.</p>
+If the data is textual, you can embed the text (using the appropriate entities or escapes based on the enclosing document's type). Otherwise, you can specify `base64` to embed base64-encoded binary data. You can find more info on MIME types [here](/en-US/docs/Web/HTTP/Basics_of_HTTP/MIME_types) and [here](/en-US/docs/Web/HTTP/Basics_of_HTTP/MIME_types/Common_types).
 
-<p>A few examples:</p>
+A few examples:
 
-<dl>
- <dt><code>data:,Hello%2C%20World%21</code></dt>
- <dd>The text/plain data <code>Hello, World!</code>. Note how the comma is  <a href="/en-US/docs/Glossary/percent-encoding">percent-encoded</a> as <code>%2C</code>, and the space character as <code>%20</code>.</dd>
- <dt><code>data:text/plain;base64,SGVsbG8sIFdvcmxkIQ==</code></dt>
- <dd>base64-encoded version of the above</dd>
- <dt><code>data:text/html,%3Ch1%3EHello%2C%20World%21%3C%2Fh1%3E</code></dt>
- <dd>An HTML document with <code>&lt;h1&gt;Hello, World!&lt;/h1&gt;</code></dd>
- <dt><code>data:text/html,&lt;script&gt;alert('hi');&lt;/script&gt;</code></dt>
- <dd>An HTML document that executes a JavaScript alert. Note that the closing script tag is required.</dd>
-</dl>
+- `data:,Hello%2C%20World%21`
+  - : The text/plain data `Hello, World!`. Note how the comma is [percent-encoded](/en-US/docs/Glossary/percent-encoding) as `%2C`, and the space character as `%20`.
+- `data:text/plain;base64,SGVsbG8sIFdvcmxkIQ==`
+  - : base64-encoded version of the above
+- `data:text/html,%3Ch1%3EHello%2C%20World%21%3C%2Fh1%3E`
+  - : An HTML document with `<h1>Hello, World!</h1>`
+- `data:text/html,<script>alert('hi');</script>`
+  - : An HTML document that executes a JavaScript alert. Note that the closing script tag is required.
 
-<h2 id="Encoding_data_into_base64_format">Encoding data into base64 format</h2>
+## Encoding data into base64 format
 
-<p>Base64 is a group of binary-to-text encoding schemes that represent binary data in an ASCII string format by translating it into a radix-64 representation. By consisting only in ASCII characters, base64 strings are generally url-safe, and that's why they can be used to encode data in Data URLs.</p>
+Base64 is a group of binary-to-text encoding schemes that represent binary data in an ASCII string format by translating it into a radix-64 representation. By consisting only in ASCII characters, base64 strings are generally url-safe, and that's why they can be used to encode data in Data URLs.
 
-<h3 id="Encoding_in_Javascript">Encoding in Javascript</h3>
+### Encoding in Javascript
 
-<p>The Web APIs have native methods to encode or decode to base64: <a href="/en-US/docs/Glossary/Base64">Base64 encoding and decoding</a>.</p>
+The Web APIs have native methods to encode or decode to base64: [Base64 encoding and decoding](/en-US/docs/Glossary/Base64).
 
-<h3 id="Encoding_on_a_Unix_system">Encoding on a Unix system</h3>
+### Encoding on a Unix system
 
-<p>Base64 encoding of a file or string on Linux and Mac OS X systems can be achieved using the command-line <code>base64</code> (or, as an alternative, the <code>uuencode</code> utility with <code>-m</code> argument).</p>
+Base64 encoding of a file or string on Linux and Mac OS X systems can be achieved using the command-line `base64` (or, as an alternative, the `uuencode` utility with `-m` argument).
 
-<pre class="brush: bash">echo -n hello|base64
+```bash
+echo -n hello|base64
 # outputs to console: aGVsbG8=
 
-echo -n hello&gt;a.txt
+echo -n hello>a.txt
 base64 a.txt
 # outputs to console: aGVsbG8=
 
-base64 a.txt&gt;b.txt
+base64 a.txt>b.txt
 # outputs to file b.txt: aGVsbG8=
-</pre>
+```
 
-<h3 id="Encoding_on_Microsoft_Windows">Encoding on Microsoft Windows</h3>
+### Encoding on Microsoft Windows
 
-<p>On Windows, <a href="https://docs.microsoft.com/en-us/dotnet/api/system.convert.tobase64string?view=net-5.0">Convert.ToBase64String</a> from PowerShell can be used to perform the Base64 encoding:</p>
+On Windows, [Convert.ToBase64String](https://docs.microsoft.com/en-us/dotnet/api/system.convert.tobase64string?view=net-5.0) from PowerShell can be used to perform the Base64 encoding:
 
-<pre class="brush: html">[convert]::ToBase64String([Text.Encoding]::UTF8.GetBytes("hello"))
+```html
+[convert]::ToBase64String([Text.Encoding]::UTF8.GetBytes("hello"))
 # outputs to console: aGVsbG8=
-</pre>
+```
 
-<p>Alternatively, a GNU/Linux shell (such as <a href="https://en.wikipedia.org/wiki/Windows_Subsystem_for_Linux">WSL</a>) provides the utility <code>base64</code>:</p>
+Alternatively, a GNU/Linux shell (such as [WSL](https://en.wikipedia.org/wiki/Windows_Subsystem_for_Linux)) provides the utility `base64`:
 
-<pre class="brush: html">bash$ echo -n hello | base64
+```html
+bash$ echo -n hello | base64
 # outputs to console: aGVsbG8=
-</pre>
-
-<h2 id="Common_problems">Common problems</h2>
-
-<p>This section describes problems that commonly occur when creating and using <code>data</code> URLs.</p>
-
-<pre>data:text/html,lots of text...&lt;p&gt;&lt;a name%3D"bottom"&gt;bottom&lt;/a&gt;?arg=val
-</pre>
-
-<p>This represents an HTML resource whose contents are:</p>
-
-<pre>lots of text...&lt;p&gt;&lt;a name="bottom"&gt;bottom&lt;/a&gt;?arg=val
-</pre>
-
-<dl>
- <dt>Syntax</dt>
- <dd>The format for <code>data</code> URLs is very simple, but it's easy to forget to put a comma before the "data" segment, or to incorrectly encode the data into base64 format.</dd>
- <dt>Formatting in HTML</dt>
- <dd>A <code>data</code> URL provides a file within a file, which can potentially be very wide relative to the width of the enclosing document. As a URL, the <code>data</code> should be formatable with whitespace (linefeed, tab, or spaces), but there are practical issues that arise <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=73026#c12">when using base64 encoding</a>.</dd>
- <dt>Length limitations</dt>
- <dd>Although Firefox supports <code>data</code> URLs of essentially unlimited length, browsers are not required to support any particular maximum length of data. For example, the Opera 11 browser limited URLs to 65535 characters long which limits <code>data</code> URLs to 65529 characters (65529 characters being the length of the encoded data, not the source, if you use the plain <code>data:</code>, without specifying a MIME type).</dd>
- <dt>Lack of error handling</dt>
- <dd>Invalid parameters in media, or typos when specifying <code>'base64'</code>, are ignored, but no error is provided.</dd>
- <dt>No support for query strings, etc.</dt>
- <dd>
- <p>The data portion of a data URL is opaque, so an attempt to use a query string (page-specific parameters, with the syntax <code>&lt;url&gt;?parameter-data</code>) with a data URL will just include the query string in the data the URL represents.</p>
- </dd>
- <dt>Security issues</dt>
- <dd>A number of security issues (e.g. phishing) have been associated with data URLs, and navigating to them in the browser's top level. To mitigate such issues, top-level navigation to <code>data://</code> URLs has been blocked in Firefox 59+ (release version, Nightly/Beta from 58), and we hope to see other browsers follow suit soon. <a href="https://blog.mozilla.org/security/2017/11/27/blocking-top-level-navigations-data-urls-firefox-58/">See Blocking Top-Level Navigations to data URLs for Firefox 58</a> for more details.</dd>
-</dl>
-
-<h2 id="Specifications">Specifications</h2>
-
-<table class="standard-table">
- <tbody>
-  <tr>
-   <th scope="col">Specification</th>
-   <th scope="col">Title</th>
-  </tr>
-  <tr>
-   <td>{{RFC("2397")}}</td>
-   <td>The "data" URL scheme</td>
-  </tr>
- </tbody>
-</table>
-
-<h2 id="Browser_compatibility">Browser compatibility</h2>
-
-<p>{{compat}}</p>
-
-<h2 id="See_also">See also</h2>
-
-<ul>
- <li><a href="/en-US/docs/Glossary/Base64">Base64 encoding and decoding</a></li>
- <li><a href="/en-US/docs/Glossary/percent-encoding">Percent encoding</a></li>
- <li>{{domxref("WindowOrWorkerGlobalScope/atob","atob()")}}</li>
- <li>{{domxref("WindowOrWorkerGlobalScope/btoa","btoa()")}}</li>
- <li><a href="/en-US/docs/Web/CSS/url()">CSS <code>url()</code></a></li>
- <li><a href="/en-US/docs/Glossary/URI">URI</a></li>
-</ul>
+```
+
+## Common problems
+
+This section describes problems that commonly occur when creating and using `data` URLs.
+
+    data:text/html,lots of text...<p><a name%3D"bottom">bottom</a>?arg=val
+
+This represents an HTML resource whose contents are:
+
+    lots of text...<p><a name="bottom">bottom</a>?arg=val
+
+- Syntax
+  - : The format for `data` URLs is very simple, but it's easy to forget to put a comma before the "data" segment, or to incorrectly encode the data into base64 format.
+- Formatting in HTML
+  - : A `data` URL provides a file within a file, which can potentially be very wide relative to the width of the enclosing document. As a URL, the `data` should be formatable with whitespace (linefeed, tab, or spaces), but there are practical issues that arise [when using base64 encoding](https://bugzilla.mozilla.org/show_bug.cgi?id=73026#c12).
+- Length limitations
+  - : Although Firefox supports `data` URLs of essentially unlimited length, browsers are not required to support any particular maximum length of data. For example, the Opera 11 browser limited URLs to 65535 characters long which limits `data` URLs to 65529 characters (65529 characters being the length of the encoded data, not the source, if you use the plain `data:`, without specifying a MIME type).
+- Lack of error handling
+  - : Invalid parameters in media, or typos when specifying `'base64'`, are ignored, but no error is provided.
+- No support for query strings, etc.
+  - : The data portion of a data URL is opaque, so an attempt to use a query string (page-specific parameters, with the syntax `<url>?parameter-data`) with a data URL will just include the query string in the data the URL represents.
+- Security issues
+  - : A number of security issues (e.g. phishing) have been associated with data URLs, and navigating to them in the browser's top level. To mitigate such issues, top-level navigation to `data://` URLs has been blocked in Firefox 59+ (release version, Nightly/Beta from 58), and we hope to see other browsers follow suit soon. [See Blocking Top-Level Navigations to data URLs for Firefox 58](https://blog.mozilla.org/security/2017/11/27/blocking-top-level-navigations-data-urls-firefox-58/) for more details.
+
+## Specifications
+
+| Specification        | Title                 |
+| -------------------- | --------------------- |
+| {{RFC("2397")}} | The "data" URL scheme |
+
+## Browser compatibility
+
+{{compat}}
+
+## See also
+
+- [Base64 encoding and decoding](/en-US/docs/Glossary/Base64)
+- [Percent encoding](/en-US/docs/Glossary/percent-encoding)
+- {{domxref("WindowOrWorkerGlobalScope/atob","atob()")}}
+- {{domxref("WindowOrWorkerGlobalScope/btoa","btoa()")}}
+- [CSS `url()`](</en-US/docs/Web/CSS/url()>)
+- [URI](/en-US/docs/Glossary/URI)
diff --git a/files/en-us/web/http/basics_of_http/evolution_of_http/index.md b/files/en-us/web/http/basics_of_http/evolution_of_http/index.md
index 394a56aebd7d4b2..761dd79b290937d 100644
--- a/files/en-us/web/http/basics_of_http/evolution_of_http/index.md
+++ b/files/en-us/web/http/basics_of_http/evolution_of_http/index.md
@@ -7,202 +7,190 @@ tags:
   - NeedsUpdate
   - NeedsUpdate(HTTP/3)
 ---
-<div>{{HTTPSidebar}}</div>
+{{HTTPSidebar}}
 
-<p class="summary"><strong>HTTP</strong> (HyperText Transfer Protocol) is the underlying protocol of the World Wide Web. Developed by Tim Berners-Lee and his team between 1989-1991, HTTP has seen many changes, keeping most of the simplicity and further shaping its flexibility. HTTP has evolved from an early protocol to exchange files in a semi-trusted laboratory environment, to the modern maze of the Internet, now carrying images, videos in high resolution and 3D.</p>
+**HTTP** (HyperText Transfer Protocol) is the underlying protocol of the World Wide Web. Developed by Tim Berners-Lee and his team between 1989-1991, HTTP has seen many changes, keeping most of the simplicity and further shaping its flexibility. HTTP has evolved from an early protocol to exchange files in a semi-trusted laboratory environment, to the modern maze of the Internet, now carrying images, videos in high resolution and 3D.
 
-<h2 id="Invention_of_the_World_Wide_Web">Invention of the World Wide Web</h2>
+## Invention of the World Wide Web
 
-<p>In 1989, while he was working at CERN, Tim Berners-Lee wrote a proposal to build a hypertext system over the Internet. Initially calling it the <em>Mesh</em>, it was later renamed to <em>World Wide Web</em> during its implementation in 1990. Built over the existing TCP and IP protocols, it consisted of 4 building blocks:</p>
+In 1989, while he was working at CERN, Tim Berners-Lee wrote a proposal to build a hypertext system over the Internet. Initially calling it the _Mesh_, it was later renamed to _World Wide Web_ during its implementation in 1990. Built over the existing TCP and IP protocols, it consisted of 4 building blocks:
 
-<ul>
- <li>A textual format to represent hypertext documents, the <em><a href="/en-US/docs/Web/HTML">HyperText Markup Language</a></em> (HTML).</li>
- <li>A simple protocol to exchange these documents, the <em>HypertText Transfer Protocol </em>(HTTP).</li>
- <li>A client to display (and accidentally edit) these documents, the first Web browser called <em>WorldWideWeb</em>.</li>
- <li>A server to give access to the document, an early version of <em>httpd</em>.</li>
-</ul>
+- A textual format to represent hypertext documents, the _[HyperText Markup Language](/en-US/docs/Web/HTML)_ (HTML).
+- A simple protocol to exchange these documents, the _HypertText Transfer Protocol_ (HTTP).
+- A client to display (and accidentally edit) these documents, the first Web browser called _WorldWideWeb_.
+- A server to give access to the document, an early version of _httpd_.
 
-<p>These four building blocks were completed by the end of 1990, and the first servers were already running outside of CERN by early 1991. On August 6th 1991, Tim Berners-Lee's <a href="https://www.w3.org/People/Berners-Lee/1991/08/art-6484.txt">post</a> on the public <em>alt.hypertext</em> newsgroup is now considered as the official start of the World Wide Web as a public project.</p>
+These four building blocks were completed by the end of 1990, and the first servers were already running outside of CERN by early 1991. On August 6th 1991, Tim Berners-Lee's [post](https://www.w3.org/People/Berners-Lee/1991/08/art-6484.txt) on the public _alt.hypertext_ newsgroup is now considered as the official start of the World Wide Web as a public project.
 
-<p>The HTTP protocol used in those early phases was very simple, later dubbed HTTP/0.9, and sometimes as the one-line protocol.</p>
+The HTTP protocol used in those early phases was very simple, later dubbed HTTP/0.9, and sometimes as the one-line protocol.
 
-<h2 id="HTTP0.9_–_The_one-line_protocol">HTTP/0.9 – The one-line protocol</h2>
+## HTTP/0.9 – The one-line protocol
 
-<p>The initial version of HTTP had no version number; it has been later called 0.9 to differentiate it from the later versions. HTTP/0.9 is extremely simple: requests consist of a single line and start with the only possible method {{HTTPMethod("GET")}} followed by the path to the resource (not the URL as both the protocol, server, and port are unnecessary once connected to the server).</p>
+The initial version of HTTP had no version number; it has been later called 0.9 to differentiate it from the later versions. HTTP/0.9 is extremely simple: requests consist of a single line and start with the only possible method {{HTTPMethod("GET")}} followed by the path to the resource (not the URL as both the protocol, server, and port are unnecessary once connected to the server).
 
-<pre>GET /mypage.html</pre>
+    GET /mypage.html
 
-<p>The response is extremely simple too: it only consisted of the file itself.</p>
+The response is extremely simple too: it only consisted of the file itself.
 
-<pre>&lt;HTML&gt;
-A very simple HTML page
-&lt;/HTML&gt;</pre>
+    <HTML>
+    A very simple HTML page
+    </HTML>
 
-<p>Unlike subsequent evolutions, there were no HTTP headers, meaning that only HTML files could be transmitted, but no other type of documents. There were no status or error codes: in case of a problem, a specific HTML file was sent back with the description of the problem contained in it, for human consumption.</p>
+Unlike subsequent evolutions, there were no HTTP headers, meaning that only HTML files could be transmitted, but no other type of documents. There were no status or error codes: in case of a problem, a specific HTML file was sent back with the description of the problem contained in it, for human consumption.
 
-<h2 id="HTTP1.0_–_Building_extensibility">HTTP/1.0 – Building extensibility</h2>
+## HTTP/1.0 – Building extensibility
 
-<p>HTTP/0.9 was very limited and both browsers and servers quickly extended it to be more versatile:</p>
+HTTP/0.9 was very limited and both browsers and servers quickly extended it to be more versatile:
 
-<ul>
- <li>Versioning information is now sent within each request (<code>HTTP/1.0</code> is appended to the <code>GET</code> line)</li>
- <li>A status code line is also sent at the beginning of the response, allowing the browser itself to understand the success or failure of the request and to adapt its behavior in consequence (like in updating or using its local cache in a specific way)</li>
- <li>The notion of HTTP headers has been introduced, both for the requests and the responses, allowing metadata to be transmitted and making the protocol extremely flexible and extensible.</li>
- <li>With the help of the new HTTP headers, the ability to transmit other documents than plain HTML files has been added (thanks to the {{HTTPHeader("Content-Type")}} header).</li>
-</ul>
+- Versioning information is now sent within each request (`HTTP/1.0` is appended to the `GET` line)
+- A status code line is also sent at the beginning of the response, allowing the browser itself to understand the success or failure of the request and to adapt its behavior in consequence (like in updating or using its local cache in a specific way)
+- The notion of HTTP headers has been introduced, both for the requests and the responses, allowing metadata to be transmitted and making the protocol extremely flexible and extensible.
+- With the help of the new HTTP headers, the ability to transmit other documents than plain HTML files has been added (thanks to the {{HTTPHeader("Content-Type")}} header).
 
-<p>At this point, a typical request and response looked like this:</p>
+At this point, a typical request and response looked like this:
 
-<pre>GET /mypage.html HTTP/1.0
-User-Agent: NCSA_Mosaic/2.0 (Windows 3.1)
+    GET /mypage.html HTTP/1.0
+    User-Agent: NCSA_Mosaic/2.0 (Windows 3.1)
 
-200 OK
-Date: Tue, 15 Nov 1994 08:12:31 GMT
-Server: CERN/3.0 libwww/2.17
-Content-Type: text/html
-&lt;HTML&gt;
-A page with an image
-  &lt;IMG SRC="/myimage.gif"&gt;
-&lt;/HTML&gt;</pre>
+    200 OK
+    Date: Tue, 15 Nov 1994 08:12:31 GMT
+    Server: CERN/3.0 libwww/2.17
+    Content-Type: text/html
+    <HTML>
+    A page with an image
+      <IMG SRC="/myimage.gif">
+    </HTML>
 
-<p>Followed by a second connection and request to fetch the image (followed by a response to that request):</p>
+Followed by a second connection and request to fetch the image (followed by a response to that request):
 
-<pre>GET /myimage.gif HTTP/1.0
-User-Agent: NCSA_Mosaic/2.0 (Windows 3.1)
+    GET /myimage.gif HTTP/1.0
+    User-Agent: NCSA_Mosaic/2.0 (Windows 3.1)
 
-200 OK
-Date: Tue, 15 Nov 1994 08:12:32 GMT
-Server: CERN/3.0 libwww/2.17
-Content-Type: text/gif
-<em>(image content)</em></pre>
+    200 OK
+    Date: Tue, 15 Nov 1994 08:12:32 GMT
+    Server: CERN/3.0 libwww/2.17
+    Content-Type: text/gif
+    (image content)
 
-<p>These novelties have not been introduced as concerted effort, but as a try-and-see approach over the 1991-1995 period: a server and a browser added one feature and it saw if it got traction. A lot of interoperability problems were common. In November 1996, in order to solve these annoyances, an informational document describing the common practices has been published, {{RFC(1945)}}. This is the definition of HTTP/1.0 and it is notable that, in the narrow sense of the term, it isn't an official standard.</p>
+These novelties have not been introduced as concerted effort, but as a try-and-see approach over the 1991-1995 period: a server and a browser added one feature and it saw if it got traction. A lot of interoperability problems were common. In November 1996, in order to solve these annoyances, an informational document describing the common practices has been published, {{RFC(1945)}}. This is the definition of HTTP/1.0 and it is notable that, in the narrow sense of the term, it isn't an official standard.
 
-<h2 id="HTTP1.1_–_The_standardized_protocol">HTTP/1.1 – The standardized protocol</h2>
+## HTTP/1.1 – The standardized protocol
 
-<p>In parallel to the somewhat chaotic use of the diverse implementations of HTTP/1.0, and since 1995, well before the publication of HTTP/1.0 document the next year, proper standardization was in progress. The first standardized version of HTTP, HTTP/1.1 was published in early 1997, only a few months after HTTP/1.0.</p>
+In parallel to the somewhat chaotic use of the diverse implementations of HTTP/1.0, and since 1995, well before the publication of HTTP/1.0 document the next year, proper standardization was in progress. The first standardized version of HTTP, HTTP/1.1 was published in early 1997, only a few months after HTTP/1.0.
 
-<p>HTTP/1.1 clarified ambiguities and introduced numerous improvements:</p>
+HTTP/1.1 clarified ambiguities and introduced numerous improvements:
 
-<ul>
- <li>A connection can be reused, saving the time to reopen it numerous times to display the resources embedded into the single original document retrieved.</li>
- <li>Pipelining has been added, allowing to send a second request before the answer for the first one is fully transmitted, lowering the latency of the communication.</li>
- <li>Chunked responses are now also supported.</li>
- <li>Additional cache control mechanisms have been introduced.</li>
- <li>Content negotiation, including language, encoding, or type, has been introduced, and allows a client and a server to agree on the most adequate content to exchange.</li>
- <li>Thanks to the {{HTTPHeader("Host")}} header, the ability to host different domains at the same IP address now allows server colocation.</li>
-</ul>
+- A connection can be reused, saving the time to reopen it numerous times to display the resources embedded into the single original document retrieved.
+- Pipelining has been added, allowing to send a second request before the answer for the first one is fully transmitted, lowering the latency of the communication.
+- Chunked responses are now also supported.
+- Additional cache control mechanisms have been introduced.
+- Content negotiation, including language, encoding, or type, has been introduced, and allows a client and a server to agree on the most adequate content to exchange.
+- Thanks to the {{HTTPHeader("Host")}} header, the ability to host different domains at the same IP address now allows server colocation.
 
-<p>A typical flow of requests, all through one single connection is now looking like this:</p>
+A typical flow of requests, all through one single connection is now looking like this:
 
-<pre>GET /en-US/docs/Glossary/Simple_header HTTP/1.1
-Host: developer.mozilla.org
-User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:50.0) Gecko/20100101 Firefox/50.0
-Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
-Accept-Language: en-US,en;q=0.5
-Accept-Encoding: gzip, deflate, br
-Referer: https://developer.mozilla.org/en-US/docs/Glossary/Simple_header
+    GET /en-US/docs/Glossary/Simple_header HTTP/1.1
+    Host: developer.mozilla.org
+    User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:50.0) Gecko/20100101 Firefox/50.0
+    Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
+    Accept-Language: en-US,en;q=0.5
+    Accept-Encoding: gzip, deflate, br
+    Referer: https://developer.mozilla.org/en-US/docs/Glossary/Simple_header
 
-200 OK
-Connection: Keep-Alive
-Content-Encoding: gzip
-Content-Type: text/html; charset=utf-8
-Date: Wed, 20 Jul 2016 10:55:30 GMT
-Etag: "547fa7e369ef56031dd3bff2ace9fc0832eb251a"
-Keep-Alive: timeout=5, max=1000
-Last-Modified: Tue, 19 Jul 2016 00:59:33 GMT
-Server: Apache
-Transfer-Encoding: chunked
-Vary: Cookie, Accept-Encoding
+    200 OK
+    Connection: Keep-Alive
+    Content-Encoding: gzip
+    Content-Type: text/html; charset=utf-8
+    Date: Wed, 20 Jul 2016 10:55:30 GMT
+    Etag: "547fa7e369ef56031dd3bff2ace9fc0832eb251a"
+    Keep-Alive: timeout=5, max=1000
+    Last-Modified: Tue, 19 Jul 2016 00:59:33 GMT
+    Server: Apache
+    Transfer-Encoding: chunked
+    Vary: Cookie, Accept-Encoding
 
-<em>(content)</em>
+    (content)
 
-GET /static/img/header-background.png HTTP/1.1
-Host: developer.mozilla.org
-User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:50.0) Gecko/20100101 Firefox/50.0
-Accept: */*
-Accept-Language: en-US,en;q=0.5
-Accept-Encoding: gzip, deflate, br
-Referer: https://developer.mozilla.org/en-US/docs/Glossary/Simple_header
+    GET /static/img/header-background.png HTTP/1.1
+    Host: developer.mozilla.org
+    User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:50.0) Gecko/20100101 Firefox/50.0
+    Accept: */*
+    Accept-Language: en-US,en;q=0.5
+    Accept-Encoding: gzip, deflate, br
+    Referer: https://developer.mozilla.org/en-US/docs/Glossary/Simple_header
 
-200 OK
-Age: 9578461
-Cache-Control: public, max-age=315360000
-Connection: keep-alive
-Content-Length: 3077
-Content-Type: image/png
-Date: Thu, 31 Mar 2016 13:34:46 GMT
-Last-Modified: Wed, 21 Oct 2015 18:27:50 GMT
-Server: Apache
+    200 OK
+    Age: 9578461
+    Cache-Control: public, max-age=315360000
+    Connection: keep-alive
+    Content-Length: 3077
+    Content-Type: image/png
+    Date: Thu, 31 Mar 2016 13:34:46 GMT
+    Last-Modified: Wed, 21 Oct 2015 18:27:50 GMT
+    Server: Apache
 
-<em>(image content of 3077 bytes)</em></pre>
+    (image content of 3077 bytes)
 
-<p>HTTP/1.1 was first published as {{rfc(2068)}} in January 1997.</p>
+HTTP/1.1 was first published as {{rfc(2068)}} in January 1997.
 
-<h2 id="More_than_15_years_of_extensions">More than 15 years of extensions</h2>
+## More than 15 years of extensions
 
-<p>Thanks to its extensibility – creating new headers or methods is easy – and even if the HTTP/1.1 protocol was refined over two revisions, {{RFC("2616")}} published in June 1999 and the series of {{RFC("7230")}}-{{RFC("7235")}} published in June 2014 in prevision of the release of HTTP/2, this protocol has been extremely stable over more than 15 years.</p>
+Thanks to its extensibility – creating new headers or methods is easy – and even if the HTTP/1.1 protocol was refined over two revisions, {{RFC("2616")}} published in June 1999 and the series of {{RFC("7230")}}-{{RFC("7235")}} published in June 2014 in prevision of the release of HTTP/2, this protocol has been extremely stable over more than 15 years.
 
-<h3 id="Using_HTTP_for_secure_transmissions">Using HTTP for secure transmissions</h3>
+### Using HTTP for secure transmissions
 
-<p>The largest change that happened to HTTP was done as early as end of 1994. Instead of sending HTTP over a basic TCP/IP stack, Netscape Communications created an additional encrypted transmission layer on top of it: SSL. SSL 1.0 was never released outside the company, but SSL 2.0 and its successor SSL 3.0 allowed for the creation of e-commerce Web sites by encrypting and guaranteeing the authenticity of the messages exchanged between the server and client. SSL was put on the standards track and eventually became TLS, with versions 1.0, 1.1, 1.2, and 1.3 appearing successfully to close vulnerabilities.</p>
+The largest change that happened to HTTP was done as early as end of 1994. Instead of sending HTTP over a basic TCP/IP stack, Netscape Communications created an additional encrypted transmission layer on top of it: SSL. SSL 1.0 was never released outside the company, but SSL 2.0 and its successor SSL 3.0 allowed for the creation of e-commerce Web sites by encrypting and guaranteeing the authenticity of the messages exchanged between the server and client. SSL was put on the standards track and eventually became TLS, with versions 1.0, 1.1, 1.2, and 1.3 appearing successfully to close vulnerabilities.
 
-<p>During the same time, the need for an encrypted transport layer raised: the Web left the relative trustiness of a mostly academic network, to a jungle where advertisers, random individuals or criminals compete to get as much private information about people, try to impersonate them or even to replace data transmitted by altered ones. As the applications built over HTTP became more and more powerful, having access to more and more private information like address books, e-mail, or the geographic position of the user, the need to have TLS became ubiquitous even outside the e-commerce use case.</p>
+During the same time, the need for an encrypted transport layer raised: the Web left the relative trustiness of a mostly academic network, to a jungle where advertisers, random individuals or criminals compete to get as much private information about people, try to impersonate them or even to replace data transmitted by altered ones. As the applications built over HTTP became more and more powerful, having access to more and more private information like address books, e-mail, or the geographic position of the user, the need to have TLS became ubiquitous even outside the e-commerce use case.
 
-<h3 id="Using_HTTP_for_complex_applications">Using HTTP for complex applications</h3>
+### Using HTTP for complex applications
 
-<p>The original vision of Tim Berners-Lee for the Web wasn't a read-only medium. He envisioned a Web where people can add and move documents remotely, a kind of distributed file system. Around 1996, HTTP has been extended to allow authoring, and a standard called WebDAV was created. It has been further extended for specific applications like CardDAV to handle address book entries and CalDAV to deal with calendars. But all these *DAV extensions had a flaw: they had to be implemented by the servers to be used, which was quite complex. Their use on Web realms stayed confidential.</p>
+The original vision of Tim Berners-Lee for the Web wasn't a read-only medium. He envisioned a Web where people can add and move documents remotely, a kind of distributed file system. Around 1996, HTTP has been extended to allow authoring, and a standard called WebDAV was created. It has been further extended for specific applications like CardDAV to handle address book entries and CalDAV to deal with calendars. But all these \*DAV extensions had a flaw: they had to be implemented by the servers to be used, which was quite complex. Their use on Web realms stayed confidential.
 
-<p>In 2000, a new pattern for using HTTP was designed: {{glossary("REST", "representational state transfer")}} (or REST). The actions induced by the API were no more conveyed by new HTTP methods, but only by accessing specific URIs with basic HTTP/1.1 methods. This allowed any Web application to provide an API to allow retrieval and modification of its data without having to update the browsers or the servers: all what is needed was embedded in the files served by the Web sites through standard HTTP/1.1. The drawback of the REST model resides in the fact that each website defines its own non-standard RESTful API and has total control on it; unlike the *DAV extensions where clients and servers are interoperable. RESTful APIs became very common in the 2010s.</p>
+In 2000, a new pattern for using HTTP was designed: {{glossary("REST", "representational state transfer")}} (or REST). The actions induced by the API were no more conveyed by new HTTP methods, but only by accessing specific URIs with basic HTTP/1.1 methods. This allowed any Web application to provide an API to allow retrieval and modification of its data without having to update the browsers or the servers: all what is needed was embedded in the files served by the Web sites through standard HTTP/1.1. The drawback of the REST model resides in the fact that each website defines its own non-standard RESTful API and has total control on it; unlike the \*DAV extensions where clients and servers are interoperable. RESTful APIs became very common in the 2010s.
 
-<p>Since 2005, the set of APIs available to Web pages greatly increased and several of these APIs created extensions, mostly new specific HTTP headers, to the HTTP protocol for specific purposes:</p>
+Since 2005, the set of APIs available to Web pages greatly increased and several of these APIs created extensions, mostly new specific HTTP headers, to the HTTP protocol for specific purposes:
 
-<ul>
- <li><a href="/en-US/docs/Web/API/Server-sent_events">Server-sent events</a>, where the server can push occasional messages to the browser.</li>
- <li><a href="/en-US/docs/Web/API/WebSockets_API">WebSocket</a>, a new protocol that can be set up by upgrading an existing HTTP connection.</li>
-</ul>
+- [Server-sent events](/en-US/docs/Web/API/Server-sent_events), where the server can push occasional messages to the browser.
+- [WebSocket](/en-US/docs/Web/API/WebSockets_API), a new protocol that can be set up by upgrading an existing HTTP connection.
 
-<h3 id="Relaxing_the_security-model_of_the_Web">Relaxing the security-model of the Web</h3>
+### Relaxing the security-model of the Web
 
-<p>HTTP is independent of the security model of the Web, the <a href="/en-US/docs/Web/Security/Same-origin_policy">same-origin policy</a>. In fact, the current Web security model has been developed after the creation of HTTP! Over the years, it has proved useful to be able to be more lenient, by allowing under certain constraints to lift some of the restriction of this policy. How much and when such restrictions are lifted is transmitted by the server to the client using a new bunch of HTTP headers. These are defined in specifications like <a href="/en-US/docs/Glossary/CORS">Cross-Origin Resource Sharing</a> (CORS) or the <a href="/en-US/docs/Web/HTTP/CSP">Content Security Policy</a> (CSP).</p>
+HTTP is independent of the security model of the Web, the [same-origin policy](/en-US/docs/Web/Security/Same-origin_policy). In fact, the current Web security model has been developed after the creation of HTTP! Over the years, it has proved useful to be able to be more lenient, by allowing under certain constraints to lift some of the restriction of this policy. How much and when such restrictions are lifted is transmitted by the server to the client using a new bunch of HTTP headers. These are defined in specifications like [Cross-Origin Resource Sharing](/en-US/docs/Glossary/CORS) (CORS) or the [Content Security Policy](/en-US/docs/Web/HTTP/CSP) (CSP).
 
-<p>In addition to these large extensions, numerous other headers have been added, sometimes experimentally only. Notable headers are Do Not Track ({{HTTPHeader("DNT")}}) header to control privacy, {{HTTPHeader("X-Frame-Options")}}, or {{HTTPHeader('Upgrade-Insecure-Requests')}} but many more exist.</p>
+In addition to these large extensions, numerous other headers have been added, sometimes experimentally only. Notable headers are Do Not Track ({{HTTPHeader("DNT")}}) header to control privacy, {{HTTPHeader("X-Frame-Options")}}, or {{HTTPHeader('Upgrade-Insecure-Requests')}} but many more exist.
 
-<h2 id="HTTP2_–_A_protocol_for_greater_performance">HTTP/2 – A protocol for greater performance</h2>
+## HTTP/2 – A protocol for greater performance
 
-<p>Over the years, Web pages have become much more complex, even becoming applications in their own right. The amount of visual media displayed, the volume and size of scripts adding interactivity, has also increased: much more data is transmitted over significantly more HTTP requests. HTTP/1.1 connections need requests sent in the correct order. Theoretically, several parallel connections could be used (typically between 5 and 8), bringing considerable overhead and complexity. For example, HTTP pipelining has emerged as a resource burden in Web development.</p>
+Over the years, Web pages have become much more complex, even becoming applications in their own right. The amount of visual media displayed, the volume and size of scripts adding interactivity, has also increased: much more data is transmitted over significantly more HTTP requests. HTTP/1.1 connections need requests sent in the correct order. Theoretically, several parallel connections could be used (typically between 5 and 8), bringing considerable overhead and complexity. For example, HTTP pipelining has emerged as a resource burden in Web development.
 
-<p>In the first half of the 2010s, Google demonstrated an alternative way of exchanging data between client and server, by implementing an experimental protocol SPDY. This amassed interest from developers working on both browsers and servers. Defining an increase in responsiveness, and solving the problem of duplication of data transmitted, SPDY served as the foundations of the HTTP/2 protocol.</p>
+In the first half of the 2010s, Google demonstrated an alternative way of exchanging data between client and server, by implementing an experimental protocol SPDY. This amassed interest from developers working on both browsers and servers. Defining an increase in responsiveness, and solving the problem of duplication of data transmitted, SPDY served as the foundations of the HTTP/2 protocol.
 
-<p>The HTTP/2 protocol has several prime differences from the HTTP/1.1 version:</p>
+The HTTP/2 protocol has several prime differences from the HTTP/1.1 version:
 
-<ul>
- <li>It is a binary protocol rather than text. It can no longer be read and created manually. Despite this hurdle, improved optimization techniques can now be implemented.</li>
- <li>It is a multiplexed protocol. Parallel requests can be handled over the same connection, removing the order and blocking constraints of the HTTP/1.x protocol.</li>
- <li>It compresses headers. As these are often similar among a set of requests, this removes duplication and overhead of data transmitted.</li>
- <li>It allows a server to populate data in a client cache, in advance of it being required, through a mechanism called the server push.</li>
-</ul>
+- It is a binary protocol rather than text. It can no longer be read and created manually. Despite this hurdle, improved optimization techniques can now be implemented.
+- It is a multiplexed protocol. Parallel requests can be handled over the same connection, removing the order and blocking constraints of the HTTP/1.x protocol.
+- It compresses headers. As these are often similar among a set of requests, this removes duplication and overhead of data transmitted.
+- It allows a server to populate data in a client cache, in advance of it being required, through a mechanism called the server push.
 
-<p>Officially standardized, in May 2015, HTTP/2 has had much success. By July 2016, 8.7% of all Web sites were already using it (see <a href="https://w3techs.com/technologies/details/ce-http2/all/all">these stats</a>), representing more than 68% of all requests (see <a href="https://www.keycdn.com/blog/http2-statistics/">these statistics</a>). High-traffic Web sites showed the most rapid adoption, saving considerably on data transfer overheads and subsequent budgets.</p>
+Officially standardized, in May 2015, HTTP/2 has had much success. By July 2016, 8.7% of all Web sites were already using it (see [these stats](https://w3techs.com/technologies/details/ce-http2/all/all)), representing more than 68% of all requests (see [these statistics](https://www.keycdn.com/blog/http2-statistics/)). High-traffic Web sites showed the most rapid adoption, saving considerably on data transfer overheads and subsequent budgets.
 
-<p>This rapid adoption rate was likely as HTTP/2 does not require adaptation of Web sites and applications: using HTTP/1.1 or HTTP/2 is transparent for them. Having an up-to-date server communicating with a recent browser is enough to enable its use: only a limited set of groups were needed to trigger adoption, and as legacy browser and server versions are renewed, usage has naturally increased, without further Web developer efforts.</p>
+This rapid adoption rate was likely as HTTP/2 does not require adaptation of Web sites and applications: using HTTP/1.1 or HTTP/2 is transparent for them. Having an up-to-date server communicating with a recent browser is enough to enable its use: only a limited set of groups were needed to trigger adoption, and as legacy browser and server versions are renewed, usage has naturally increased, without further Web developer efforts.
 
-<h2 id="Post-HTTP2_evolution">Post-HTTP/2 evolution</h2>
+## Post-HTTP/2 evolution
 
-<p>HTTP didn't stop evolving upon the release of HTTP/2. Like with HTTP/1.x previously, HTTP's extensibility is still being used to add new features. Notably, we can cite new extensions of the HTTP protocol appearing in 2016:</p>
+HTTP didn't stop evolving upon the release of HTTP/2. Like with HTTP/1.x previously, HTTP's extensibility is still being used to add new features. Notably, we can cite new extensions of the HTTP protocol appearing in 2016:
 
-<ul>
- <li>Support of {{HTTPHeader("Alt-Svc")}} allows the dissociation of the identification and the location of a given resource, allowing for a smarter {{Glossary("CDN")}} caching mechanism.</li>
- <li>The introduction of {{HTTPHeader("Client-Hints")}} allows the browser, or client, to proactively communicate information about its requirements, or hardware constraints, to the server.</li>
- <li>The introduction of security-related prefixes in the {{HTTPHeader("Cookie")}} header, now helps guarantee a secure cookie has not been altered.</li>
-</ul>
+- Support of {{HTTPHeader("Alt-Svc")}} allows the dissociation of the identification and the location of a given resource, allowing for a smarter {{Glossary("CDN")}} caching mechanism.
+- The introduction of {{HTTPHeader("Client-Hints")}} allows the browser, or client, to proactively communicate information about its requirements, or hardware constraints, to the server.
+- The introduction of security-related prefixes in the {{HTTPHeader("Cookie")}} header, now helps guarantee a secure cookie has not been altered.
 
-<p>This evolution of HTTP proves its extensibility and simplicity, liberating creation of many applications and compelling the adoption of the protocol. The environment in which HTTP is used today is quite different from that seen in the early 1990s. HTTP's original design proved to be a masterpiece, allowing the Web to evolve over a quarter of a century, without the need of a mutiny. By healing flaws, yet retaining the flexibility and extensibility which made HTTP such a success, the adoption of HTTP/2 hints at a bright future for the protocol.</p>
+This evolution of HTTP proves its extensibility and simplicity, liberating creation of many applications and compelling the adoption of the protocol. The environment in which HTTP is used today is quite different from that seen in the early 1990s. HTTP's original design proved to be a masterpiece, allowing the Web to evolve over a quarter of a century, without the need of a mutiny. By healing flaws, yet retaining the flexibility and extensibility which made HTTP such a success, the adoption of HTTP/2 hints at a bright future for the protocol.
 
-<h2 id="HTTP3_-_HTTP_over_QUIC">HTTP/3 - HTTP over QUIC</h2>
+## HTTP/3 - HTTP over QUIC
 
-<p>{{Draft}}{{SeeCompatTable}}</p>
+{{Draft}}{{SeeCompatTable}}
 
-<p>The next major version of HTTP, HTTP/3, will use {{Glossary("QUIC")}} instead {{Glossary("TCP")}}/{{Glossary("TLS")}} for the transport layer portion.</p>
+The next major version of HTTP, HTTP/3, will use {{Glossary("QUIC")}} instead {{Glossary("TCP")}}/{{Glossary("TLS")}} for the transport layer portion.
 
-<p>See {{bug(1158011)}} for implementation status in Firefox.</p>
+See {{bug(1158011)}} for implementation status in Firefox.
diff --git a/files/en-us/web/http/basics_of_http/identifying_resources_on_the_web/index.md b/files/en-us/web/http/basics_of_http/identifying_resources_on_the_web/index.md
index 3384afd42c6e010..4f08d9c99833995 100644
--- a/files/en-us/web/http/basics_of_http/identifying_resources_on_the_web/index.md
+++ b/files/en-us/web/http/basics_of_http/identifying_resources_on_the_web/index.md
@@ -16,174 +16,106 @@ tags:
   - query
   - resources
 ---
-<div>{{HTTPSidebar}}</div>
-
-<p class="summary">The target of an HTTP request is called a "resource", whose nature isn't defined further; it can be a document, a photo, or anything else. Each resource is identified by a Uniform Resource Identifier ({{Glossary("URI")}}) used throughout HTTP for identifying resources.</p>
-
-<h2 id="URLs_and_URNs">URLs and URNs</h2>
-
-<h3 id="URLs">URLs</h3>
-
-<p>The most common form of URI is the Uniform Resource Locator ({{Glossary("URL")}}), which is known as the <em>web address</em>.</p>
-
-<pre>https://developer.mozilla.org
-https://developer.mozilla.org/en-US/docs/Learn/
-https://developer.mozilla.org/en-US/search?q=URL</pre>
-
-<p>Any of those URLs can be typed into your browser's address bar to tell it to load the associated page (resource).</p>
-
-<p>A URL is composed of different parts, some mandatory and others are optional. A more complex example might look like this:</p>
-
-<pre>http://www.example.com:80/path/to/myfile.html?key1=value1&amp;key2=value2#SomewhereInTheDocument</pre>
-
-<h3 id="URNs">URNs</h3>
-
-<p>A Uniform Resource Name (URN) is a URI that identifies a resource by name in a particular namespace.</p>
-
-<pre>urn:isbn:9780141036144
-urn:ietf:rfc:7230
-</pre>
-
-<p>The two URNs correspond to</p>
-
-<ul>
-	<li>the book Nineteen Eighty-Four by George Orwell,</li>
-	<li>the IETF specification 7230, Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing.</li>
-</ul>
-
-<h2 id="Syntax_of_Uniform_Resource_Identifiers_URIs">Syntax of Uniform Resource Identifiers (URIs)</h2>
-
-<h3 id="Scheme_or_protocol">Scheme or protocol</h3>
-
-<dl>
-	<dt><img alt="Protocol" src="mdn-url-protocol@x2.png"></dt>
-	<dd><code>http://</code> is the protocol. It indicates which protocol the browser must use. Usually it is the HTTP protocol or its secured version, HTTPS. The Web requires one of these two, but browsers also know how to handle other protocols such as <code>mailto:</code> (to open a mail client) or <code>ftp:</code> to handle file transfer, so don't be surprised if you see such protocols. Common schemes are:</dd>
-</dl>
-
-<table class="standard-table">
-	<thead>
-		<tr>
-			<th scope="col">Scheme</th>
-			<th scope="col">Description</th>
-		</tr>
-	</thead>
-	<tbody>
-		<tr>
-			<td>data</td>
-			<td><a href="/en-US/docs/Web/HTTP/Basics_of_HTTP/Data_URIs">Data URIs</a></td>
-		</tr>
-		<tr>
-			<td>file</td>
-			<td>Host-specific file names</td>
-		</tr>
-		<tr>
-			<td>ftp</td>
-			<td>{{Glossary("FTP","File Transfer Protocol")}}</td>
-		</tr>
-		<tr>
-			<td>http/https</td>
-			<td><a href="/en-US/docs/Glossary/HTTP">Hyper text transfer protocol (Secure)</a></td>
-		</tr>
-		<tr>
-			<td>javascript</td>
-			<td>URL-embedded JavaScript code</td>
-		</tr>
-		<tr>
-			<td>mailto</td>
-			<td>Electronic mail address</td>
-		</tr>
-		<tr>
-			<td>ssh</td>
-			<td>Secure shell</td>
-		</tr>
-		<tr>
-			<td>tel</td>
-			<td>telephone</td>
-		</tr>
-		<tr>
-			<td>urn</td>
-			<td>Uniform Resource Names</td>
-		</tr>
-		<tr>
-			<td>view-source</td>
-			<td>Source code of the resource</td>
-		</tr>
-		<tr>
-			<td>ws/wss</td>
-			<td><a href="/en-US/docs/Web/API/WebSockets_API">WebSocket connections (Secure)</a></td>
-		</tr>
-	</tbody>
-</table>
-
-<h3 id="Authority">Authority</h3>
-
-<dl>
-	<dt><img alt="Domaine Name" src="mdn-url-domain@x2.png"></dt>
-	<dd><code>www.example.com</code> is the domain name or authority that governs the namespace. It indicates which Web server is being requested. Alternatively, it is possible to directly use an {{Glossary("IP address")}}, but because it is less convenient, it is not often used on the Web.</dd>
-</dl>
-
-<h3 id="Port">Port</h3>
-
-<dl>
-	<dt><img alt="Port" src="mdn-url-port@x2.png"></dt>
-	<dd><code>:80</code> is the port in this instance. It indicates the technical "gate" used to access the resources on the web server. It is usually omitted if the web server uses the standard ports of the HTTP protocol (80 for HTTP and 443 for HTTPS) to grant access to its resources. Otherwise it is mandatory.</dd>
-</dl>
-
-<h3 id="Path">Path</h3>
-
-<dl>
-	<dt><img alt="Path to the file" src="mdn-url-path@x2.png"></dt>
-	<dd><code>/path/to/myfile.html</code> is the path to the resource on the Web server. In the early days of the Web, a path like this represented a physical file location on the Web server. Nowadays, it is mostly an abstraction handled by Web servers without any physical reality.</dd>
-</dl>
-
-<h3 id="Query">Query</h3>
-
-<dl>
-	<dt><img alt="Parameters" src="mdn-url-parameters@x2.png"></dt>
-	<dd><code>?key1=value1&amp;key2=value2</code> are extra parameters provided to the Web server. Those parameters are a list of key/value pairs separated with the <code>&amp;</code> symbol. The Web server can use those parameters to do extra stuff before returning the resource to the user. Each Web server has its own rules regarding parameters, and the only reliable way to know how a specific Web server is handling parameters is by asking the Web server owner.</dd>
-</dl>
-
-<h3 id="Fragment">Fragment</h3>
-
-<dl>
-	<dt><img alt="Anchor" src="mdn-url-anchor@x2.png"></dt>
-	<dd><code>#SomewhereInTheDocument</code> is an anchor to another part of the resource itself. An anchor represents a sort of "bookmark" inside the resource, giving the browser the directions to show the content located at that "bookmarked" spot. On an HTML document, for example, the browser will scroll to the point where the anchor is defined; on a video or audio document, the browser will try to go to the time the anchor represents. It is worth noting that the part after the #, also known as fragment identifier, is never sent to the server with the request.</dd>
-</dl>
-
-<h2 id="Usage_notes">Usage notes</h2>
-
-<p>When using URLs in {{Glossary("HTML")}} content, you should generally only use a few of these URL schemes. When referring to subresources — that is, files that are being loaded as part of a larger document — you should only use the HTTP and HTTPS schemes. Increasingly, browsers are removing support for using FTP to load subresources, for security reasons.</p>
-
-<p>FTP is still acceptable at the top level (such as typed directly into the browser's URL bar, or the target of a link), although some browsers may delegate loading FTP content to another application.</p>
-
-<h2 id="Examples">Examples</h2>
-
-<pre>https://developer.mozilla.org/en-US/docs/Learn
-tel:+1-816-555-1212
-git@github.com:mdn/browser-compat-data.git
-ftp://example.org/resource.txt
-urn:isbn:9780141036144
-mailto:help@supercyberhelpdesk.info
-</pre>
-
-<h2 id="Specifications">Specifications</h2>
-
-<table class="standard-table">
-	<tbody>
-		<tr>
-			<th scope="col">Specification</th>
-			<th scope="col">Title</th>
-		</tr>
-		<tr>
-			<td>{{RFC("7230", "Uniform Resource Identifiers", "2.7")}}</td>
-			<td>Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing</td>
-		</tr>
-	</tbody>
-</table>
-
-<h2 id="See_also">See also</h2>
-
-<ul>
-	<li><a href="/en-US/docs/Learn/Common_questions/What_is_a_URL">What is a URL?</a></li>
-	<li><a href="https://www.iana.org/assignments/uri-schemes/uri-schemes.xhtml">IANA list of URI schemes</a></li>
-</ul>
+{{HTTPSidebar}}
+
+The target of an HTTP request is called a "resource", whose nature isn't defined further; it can be a document, a photo, or anything else. Each resource is identified by a Uniform Resource Identifier ({{Glossary("URI")}}) used throughout HTTP for identifying resources.
+
+## URLs and URNs
+
+### URLs
+
+The most common form of URI is the Uniform Resource Locator ({{Glossary("URL")}}), which is known as the _web address_.
+
+    https://developer.mozilla.org
+    https://developer.mozilla.org/en-US/docs/Learn/
+    https://developer.mozilla.org/en-US/search?q=URL
+
+Any of those URLs can be typed into your browser's address bar to tell it to load the associated page (resource).
+
+A URL is composed of different parts, some mandatory and others are optional. A more complex example might look like this:
+
+    http://www.example.com:80/path/to/myfile.html?key1=value1&key2=value2#SomewhereInTheDocument
+
+### URNs
+
+A Uniform Resource Name (URN) is a URI that identifies a resource by name in a particular namespace.
+
+    urn:isbn:9780141036144
+    urn:ietf:rfc:7230
+
+The two URNs correspond to
+
+- the book Nineteen Eighty-Four by George Orwell,
+- the IETF specification 7230, Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing.
+
+## Syntax of Uniform Resource Identifiers (URIs)
+
+### Scheme or protocol
+
+- ![Protocol](mdn-url-protocol@x2.png)
+  - : `http://` is the protocol. It indicates which protocol the browser must use. Usually it is the HTTP protocol or its secured version, HTTPS. The Web requires one of these two, but browsers also know how to handle other protocols such as `mailto:` (to open a mail client) or `ftp:` to handle file transfer, so don't be surprised if you see such protocols. Common schemes are:
+
+| Scheme      | Description                                                          |
+| ----------- | -------------------------------------------------------------------- |
+| data        | [Data URIs](/en-US/docs/Web/HTTP/Basics_of_HTTP/Data_URIs)           |
+| file        | Host-specific file names                                             |
+| ftp         | {{Glossary("FTP","File Transfer Protocol")}}         |
+| http/https  | [Hyper text transfer protocol (Secure)](/en-US/docs/Glossary/HTTP)   |
+| javascript  | URL-embedded JavaScript code                                         |
+| mailto      | Electronic mail address                                              |
+| ssh         | Secure shell                                                         |
+| tel         | telephone                                                            |
+| urn         | Uniform Resource Names                                               |
+| view-source | Source code of the resource                                          |
+| ws/wss      | [WebSocket connections (Secure)](/en-US/docs/Web/API/WebSockets_API) |
+
+### Authority
+
+- ![Domaine Name](mdn-url-domain@x2.png)
+  - : `www.example.com` is the domain name or authority that governs the namespace. It indicates which Web server is being requested. Alternatively, it is possible to directly use an {{Glossary("IP address")}}, but because it is less convenient, it is not often used on the Web.
+
+### Port
+
+- ![Port](mdn-url-port@x2.png)
+  - : `:80` is the port in this instance. It indicates the technical "gate" used to access the resources on the web server. It is usually omitted if the web server uses the standard ports of the HTTP protocol (80 for HTTP and 443 for HTTPS) to grant access to its resources. Otherwise it is mandatory.
+
+### Path
+
+- ![Path to the file](mdn-url-path@x2.png)
+  - : `/path/to/myfile.html` is the path to the resource on the Web server. In the early days of the Web, a path like this represented a physical file location on the Web server. Nowadays, it is mostly an abstraction handled by Web servers without any physical reality.
+
+### Query
+
+- ![Parameters](mdn-url-parameters@x2.png)
+  - : `?key1=value1&key2=value2` are extra parameters provided to the Web server. Those parameters are a list of key/value pairs separated with the `&` symbol. The Web server can use those parameters to do extra stuff before returning the resource to the user. Each Web server has its own rules regarding parameters, and the only reliable way to know how a specific Web server is handling parameters is by asking the Web server owner.
+
+### Fragment
+
+- ![Anchor](mdn-url-anchor@x2.png)
+  - : `#SomewhereInTheDocument` is an anchor to another part of the resource itself. An anchor represents a sort of "bookmark" inside the resource, giving the browser the directions to show the content located at that "bookmarked" spot. On an HTML document, for example, the browser will scroll to the point where the anchor is defined; on a video or audio document, the browser will try to go to the time the anchor represents. It is worth noting that the part after the #, also known as fragment identifier, is never sent to the server with the request.
+
+## Usage notes
+
+When using URLs in {{Glossary("HTML")}} content, you should generally only use a few of these URL schemes. When referring to subresources — that is, files that are being loaded as part of a larger document — you should only use the HTTP and HTTPS schemes. Increasingly, browsers are removing support for using FTP to load subresources, for security reasons.
+
+FTP is still acceptable at the top level (such as typed directly into the browser's URL bar, or the target of a link), although some browsers may delegate loading FTP content to another application.
+
+## Examples
+
+    https://developer.mozilla.org/en-US/docs/Learn
+    tel:+1-816-555-1212
+    git@github.com:mdn/browser-compat-data.git
+    ftp://example.org/resource.txt
+    urn:isbn:9780141036144
+    mailto:help@supercyberhelpdesk.info
+
+## Specifications
+
+| Specification                                                            | Title                                                              |
+| ------------------------------------------------------------------------ | ------------------------------------------------------------------ |
+| {{RFC("7230", "Uniform Resource Identifiers", "2.7")}} | Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing |
+
+## See also
+
+- [What is a URL?](/en-US/docs/Learn/Common_questions/What_is_a_URL)
+- [IANA list of URI schemes](https://www.iana.org/assignments/uri-schemes/uri-schemes.xhtml)
diff --git a/files/en-us/web/http/basics_of_http/index.md b/files/en-us/web/http/basics_of_http/index.md
index 5df8ff46f459c12..1ce0f80f264603f 100644
--- a/files/en-us/web/http/basics_of_http/index.md
+++ b/files/en-us/web/http/basics_of_http/index.md
@@ -6,39 +6,37 @@ tags:
   - HTTP
   - Overview
 ---
-<div>{{HTTPSidebar}}</div>
+{{HTTPSidebar}}
 
-<p>HTTP is an extensible protocol that relies on concepts like resources and Uniform Resource Identifiers (URIs), simple message structure, and client-server communication flow. On top of these basic concepts, numerous extensions have been developed over the years that add updated functionality and semantics with new HTTP methods or headers.</p>
+HTTP is an extensible protocol that relies on concepts like resources and Uniform Resource Identifiers (URIs), simple message structure, and client-server communication flow. On top of these basic concepts, numerous extensions have been developed over the years that add updated functionality and semantics with new HTTP methods or headers.
 
-<h2 id="Articles">Articles</h2>
+## Articles
 
-<dl>
- <dt><a href="/en-US/docs/Web/HTTP/Overview">Overview of HTTP</a></dt>
- <dd>Describes what HTTP is and its role in web architecture, including its position in the protocol stack.</dd>
- <dt><a href="/en-US/docs/Web/HTTP/Basics_of_HTTP/Evolution_of_HTTP">Evolution of HTTP</a></dt>
- <dd>HTTP was created in the early 1990s and has been extended several times. This article goes through its history and describes HTTP/0.9, HTTP/1.0, HTTP/1.1, and the modern HTTP/2, as well as novelties introduced over the years.</dd>
- <dt><a href="/en-US/docs/Web/HTTP/Resources_and_URIs">Resources and URIs</a></dt>
- <dd>A brief introduction to the concept of resources, identifiers, and locations on the web.</dd>
- <dt><a href="/en-US/docs/Web/HTTP/Basics_of_HTTP/Identifying_resources_on_the_Web">Identifying resources on the Web</a></dt>
- <dd>Describes how web resources are referenced and how to locate them.</dd>
- <dt><a href="/en-US/docs/Web/HTTP/Basics_of_HTTP/Data_URIs">Data URIs</a></dt>
- <dd>A specific kind of URI that directly embeds the resource it represents. Data URIs are very convenient, but have some caveats.</dd>
- <dt><a href="/en-US/docs/Web/HTTP/Basics_of_HTTP/Resource_URLs">Resource URLs</a> {{Non-standard_Inline}}</dt>
- <dd>Resource URLs, those prefixed with the <code>resource</code> scheme are used by Firefox and Firefox browser extensions to load resources internally, but is also available to some sites the browser connects to as well.</dd>
- <dt><a href="/en-US/docs/Web/HTTP/Basics_of_HTTP/MIME_types">MIME types</a></dt>
- <dd>Since HTTP/1.0, different types of content can be transmitted. This article explains how this is accomplished using the {{HTTPHeader("Content-Type")}} header and the MIME standard.</dd>
- <dt><a href="/en-US/docs/Web/HTTP/Basics_of_HTTP/Choosing_between_www_and_non-www_URLs">Choosing between www and non-www URLs</a></dt>
- <dd>This article provides guidance on how to choose whether to use a www-prefixed domain or not, along with the consequences of that choice.</dd>
- <dt><a href="/en-US/docs/Web/HTTP/Session">Flow of an HTTP session</a></dt>
- <dd>This article describes a typical HTTP session; i.e. what happens when you follow a link or load an image into a web page.</dd>
- <dt><a href="/en-US/docs/Web/HTTP/Messages">HTTP Messages</a></dt>
- <dd>HTTP Messages transmitted during requests or responses have a very clear structure. This introductory article describes this structure, its purpose, and its possibilities.</dd>
- <dt><a href="/en-US/docs/Web/HTTP/Frame_and_message_structure_in_HTTP_2">Frame and message structure in HTTP/2</a></dt>
- <dd>HTTP/2 encapsulates and represents HTTP/1.x messages in a binary frame. This article explains the frame structure, its purpose, and the way it's encoded.</dd>
- <dt><a href="/en-US/docs/Web/HTTP/Connection_management_in_HTTP_1.x">Connection management in HTTP/1.x</a></dt>
- <dd>HTTP/1.1 was the first version of HTTP to support persistent connection and pipelining. This article explains both concepts.</dd>
- <dt><a href="/en-US/docs/Web/HTTP/Connection_management_in_HTTP_2">Connection management in HTTP/2</a></dt>
- <dd>HTTP/2 completely revisited how connections are created and maintained. This article explains how HTTP frames allow multiplexing and solve the 'head-of-line' blocking problem of former HTTP versions.</dd>
- <dt><a href="/en-US/docs/Web/HTTP/Content_negotiation">Content Negotiation</a></dt>
- <dd>HTTP introduces a set of headers, starting with <code><a href="/en-US/docs/Web/HTTP/Headers/Accept">Accept</a></code> as a way for a browser to announce the format, language, or encoding it prefers. This article explains how this advertisement happens, how the server is expected to react, and how it chooses the most adequate response.</dd>
-</dl>
+- [Overview of HTTP](/en-US/docs/Web/HTTP/Overview)
+  - : Describes what HTTP is and its role in web architecture, including its position in the protocol stack.
+- [Evolution of HTTP](/en-US/docs/Web/HTTP/Basics_of_HTTP/Evolution_of_HTTP)
+  - : HTTP was created in the early 1990s and has been extended several times. This article goes through its history and describes HTTP/0.9, HTTP/1.0, HTTP/1.1, and the modern HTTP/2, as well as novelties introduced over the years.
+- [Resources and URIs](/en-US/docs/Web/HTTP/Resources_and_URIs)
+  - : A brief introduction to the concept of resources, identifiers, and locations on the web.
+- [Identifying resources on the Web](/en-US/docs/Web/HTTP/Basics_of_HTTP/Identifying_resources_on_the_Web)
+  - : Describes how web resources are referenced and how to locate them.
+- [Data URIs](/en-US/docs/Web/HTTP/Basics_of_HTTP/Data_URIs)
+  - : A specific kind of URI that directly embeds the resource it represents. Data URIs are very convenient, but have some caveats.
+- [Resource URLs](/en-US/docs/Web/HTTP/Basics_of_HTTP/Resource_URLs) {{Non-standard_Inline}}
+  - : Resource URLs, those prefixed with the `resource` scheme are used by Firefox and Firefox browser extensions to load resources internally, but is also available to some sites the browser connects to as well.
+- [MIME types](/en-US/docs/Web/HTTP/Basics_of_HTTP/MIME_types)
+  - : Since HTTP/1.0, different types of content can be transmitted. This article explains how this is accomplished using the {{HTTPHeader("Content-Type")}} header and the MIME standard.
+- [Choosing between www and non-www URLs](/en-US/docs/Web/HTTP/Basics_of_HTTP/Choosing_between_www_and_non-www_URLs)
+  - : This article provides guidance on how to choose whether to use a www-prefixed domain or not, along with the consequences of that choice.
+- [Flow of an HTTP session](/en-US/docs/Web/HTTP/Session)
+  - : This article describes a typical HTTP session; i.e. what happens when you follow a link or load an image into a web page.
+- [HTTP Messages](/en-US/docs/Web/HTTP/Messages)
+  - : HTTP Messages transmitted during requests or responses have a very clear structure. This introductory article describes this structure, its purpose, and its possibilities.
+- [Frame and message structure in HTTP/2](/en-US/docs/Web/HTTP/Frame_and_message_structure_in_HTTP_2)
+  - : HTTP/2 encapsulates and represents HTTP/1.x messages in a binary frame. This article explains the frame structure, its purpose, and the way it's encoded.
+- [Connection management in HTTP/1.x](/en-US/docs/Web/HTTP/Connection_management_in_HTTP_1.x)
+  - : HTTP/1.1 was the first version of HTTP to support persistent connection and pipelining. This article explains both concepts.
+- [Connection management in HTTP/2](/en-US/docs/Web/HTTP/Connection_management_in_HTTP_2)
+  - : HTTP/2 completely revisited how connections are created and maintained. This article explains how HTTP frames allow multiplexing and solve the 'head-of-line' blocking problem of former HTTP versions.
+- [Content Negotiation](/en-US/docs/Web/HTTP/Content_negotiation)
+  - : HTTP introduces a set of headers, starting with [`Accept`](/en-US/docs/Web/HTTP/Headers/Accept) as a way for a browser to announce the format, language, or encoding it prefers. This article explains how this advertisement happens, how the server is expected to react, and how it chooses the most adequate response.
diff --git a/files/en-us/web/http/basics_of_http/mime_types/common_types/index.md b/files/en-us/web/http/basics_of_http/mime_types/common_types/index.md
index 7d0a1c41d7de71e..6c7ec40b477f93d 100644
--- a/files/en-us/web/http/basics_of_http/mime_types/common_types/index.md
+++ b/files/en-us/web/http/basics_of_http/mime_types/common_types/index.md
@@ -14,396 +14,88 @@ tags:
   - Types
   - Video
 ---
-<div>{{HTTPSidebar}}</div>
+{{HTTPSidebar}}
 
-<p>Here is a list of MIME types, associated by type of documents, ordered by their common extensions.</p>
+Here is a list of MIME types, associated by type of documents, ordered by their common extensions.
 
-<p>Two primary MIME types are important for the role of default types:</p>
+Two primary MIME types are important for the role of default types:
 
-<ul>
- <li><code>text/plain</code> is the default value for textual files. A textual file should be human-readable and must not contain binary data.</li>
- <li><code>application/octet-stream</code> is the default value for all other cases. An unknown file type should use this type. Browsers pay a particular care when manipulating these files, attempting to safeguard the user to prevent dangerous behaviors.</li>
-</ul>
+- `text/plain` is the default value for textual files. A textual file should be human-readable and must not contain binary data.
+- `application/octet-stream` is the default value for all other cases. An unknown file type should use this type. Browsers pay a particular care when manipulating these files, attempting to safeguard the user to prevent dangerous behaviors.
 
-<p>IANA is the official registry of MIME media types and maintains a <a href="https://www.iana.org/assignments/media-types/media-types.xhtml">list of all the official MIME types</a>. This table lists some important MIME types for the Web:</p>
+IANA is the official registry of MIME media types and maintains a [list of all the official MIME types](https://www.iana.org/assignments/media-types/media-types.xhtml). This table lists some important MIME types for the Web:
 
-<table>
- <thead>
-  <tr>
-   <th>Extension</th>
-   <th>Kind of document</th>
-   <th>MIME Type</th>
-  </tr>
- </thead>
- <tbody>
-  <tr>
-   <td><code>.aac</code></td>
-   <td>AAC audio</td>
-   <td><code>audio/aac</code></td>
-  </tr>
-  <tr>
-   <td><code>.abw</code></td>
-   <td><a href="https://en.wikipedia.org/wiki/AbiWord">AbiWord</a> document</td>
-   <td><code>application/x-abiword</code></td>
-  </tr>
-  <tr>
-   <td><code>.arc</code></td>
-   <td>Archive document (multiple files embedded)</td>
-   <td><code>application/x-freearc</code></td>
-  </tr>
-  <tr>
-   <td><code>.avi</code></td>
-   <td>AVI: Audio Video Interleave</td>
-   <td><code>video/x-msvideo</code></td>
-  </tr>
-  <tr>
-   <td><code>.azw</code></td>
-   <td>Amazon Kindle eBook format</td>
-   <td><code>application/vnd.amazon.ebook</code></td>
-  </tr>
-  <tr>
-   <td><code>.bin</code></td>
-   <td>Any kind of binary data</td>
-   <td><code>application/octet-stream</code></td>
-  </tr>
-  <tr>
-   <td><code>.bmp</code></td>
-   <td>Windows OS/2 Bitmap Graphics</td>
-   <td><code>image/bmp</code></td>
-  </tr>
-  <tr>
-   <td><code>.bz</code></td>
-   <td>BZip archive</td>
-   <td><code>application/x-bzip</code></td>
-  </tr>
-  <tr>
-   <td><code>.bz2</code></td>
-   <td>BZip2 archive</td>
-   <td><code>application/x-bzip2</code></td>
-  </tr>
-   <tr>
-    <td><code>.cda</code></td>
-    <td>CD audio</td>
-    <td><code>application/x-cdf</code></td>
-   </tr>
-  <tr>
-   <td><code>.csh</code></td>
-   <td>C-Shell script</td>
-   <td><code>application/x-csh</code></td>
-  </tr>
-  <tr>
-   <td><code>.css</code></td>
-   <td>Cascading Style Sheets (CSS)</td>
-   <td><code>text/css</code></td>
-  </tr>
-  <tr>
-   <td><code>.csv</code></td>
-   <td>Comma-separated values (CSV)</td>
-   <td><code>text/csv</code></td>
-  </tr>
-  <tr>
-   <td><code>.doc</code></td>
-   <td>Microsoft Word</td>
-   <td><code>application/msword</code></td>
-  </tr>
-  <tr>
-   <td><code>.docx</code></td>
-   <td>Microsoft Word (OpenXML)</td>
-   <td><code>application/vnd.openxmlformats-officedocument.wordprocessingml.document</code></td>
-  </tr>
-  <tr>
-   <td><code>.eot</code></td>
-   <td>MS Embedded OpenType fonts</td>
-   <td><code>application/vnd.ms-fontobject</code></td>
-  </tr>
-  <tr>
-   <td><code>.epub</code></td>
-   <td>Electronic publication (EPUB)</td>
-   <td><code>application/epub+zip</code></td>
-  </tr>
-  <tr>
-   <td><code>.gz</code></td>
-   <td>GZip Compressed Archive</td>
-   <td><code>application/gzip</code></td>
-  </tr>
-  <tr>
-   <td><code>.gif</code></td>
-   <td>Graphics Interchange Format (GIF)</td>
-   <td><code>image/gif</code></td>
-  </tr>
-  <tr>
-   <td><code>.htm<br>
-    .html</code></td>
-   <td>HyperText Markup Language (HTML)</td>
-   <td><code>text/html</code></td>
-  </tr>
-  <tr>
-   <td><code>.ico</code></td>
-   <td>Icon format</td>
-   <td><code>image/vnd.microsoft.icon</code></td>
-  </tr>
-  <tr>
-   <td><code>.ics</code></td>
-   <td>iCalendar format</td>
-   <td><code>text/calendar</code></td>
-  </tr>
-  <tr>
-   <td><code>.jar</code></td>
-   <td>Java Archive (JAR)</td>
-   <td><code>application/java-archive</code></td>
-  </tr>
-  <tr>
-   <td><code>.jpeg</code><br>
-    <code>.jpg</code></td>
-   <td>JPEG images</td>
-   <td><code>image/jpeg</code></td>
-  </tr>
-  <tr>
-   <td><code>.js</code></td>
-   <td>JavaScript</td>
-   <td>
-    <code>text/javascript</code> (Specifications: <a href="https://html.spec.whatwg.org/multipage/#scriptingLanguages">HTML</a> and its <a href="https://html.spec.whatwg.org/multipage/#dependencies:willful-violation">reasoning</a>, and <a href="https://datatracker.ietf.org/doc/draft-ietf-dispatch-javascript-mjs/">IETF</a>)
-   </td>
-  </tr>
-  <tr>
-   <td><code>.json</code></td>
-   <td>JSON format</td>
-   <td><code>application/json</code></td>
-  </tr>
-  <tr>
-   <td><code>.jsonld</code></td>
-   <td>JSON-LD format</td>
-   <td><code>application/ld+json</code></td>
-  </tr>
-  <tr>
-   <td><code>.mid</code><br>
-    <code>.midi</code></td>
-   <td>Musical Instrument Digital Interface (MIDI)</td>
-   <td><code>audio/midi</code> <code>audio/x-midi</code></td>
-  </tr>
-  <tr>
-   <td><code>.mjs</code></td>
-   <td>JavaScript module</td>
-   <td><code>text/javascript</code></td>
-  </tr>
-  <tr>
-   <td><code>.mp3</code></td>
-   <td>MP3 audio</td>
-   <td><code>audio/mpeg</code></td>
-  </tr>
-  <tr>
-    <td><code>.mp4</code></td>
-    <td>MP4 audio</td>
-    <td><code>video/mp4</code></td>
-   </tr>
-  <tr>
-   <td><code>.mpeg</code></td>
-   <td>MPEG Video</td>
-   <td><code>video/mpeg</code></td>
-  </tr>
-  <tr>
-   <td><code>.mpkg</code></td>
-   <td>Apple Installer Package</td>
-   <td><code>application/vnd.apple.installer+xml</code></td>
-  </tr>
-  <tr>
-   <td><code>.odp</code></td>
-   <td>OpenDocument presentation document</td>
-   <td><code>application/vnd.oasis.opendocument.presentation</code></td>
-  </tr>
-  <tr>
-   <td><code>.ods</code></td>
-   <td>OpenDocument spreadsheet document</td>
-   <td><code>application/vnd.oasis.opendocument.spreadsheet</code></td>
-  </tr>
-  <tr>
-   <td><code>.odt</code></td>
-   <td>OpenDocument text document</td>
-   <td><code>application/vnd.oasis.opendocument.text</code></td>
-  </tr>
-  <tr>
-   <td><code>.oga</code></td>
-   <td>OGG audio</td>
-   <td><code>audio/ogg</code></td>
-  </tr>
-  <tr>
-   <td><code>.ogv</code></td>
-   <td>OGG video</td>
-   <td><code>video/ogg</code></td>
-  </tr>
-  <tr>
-   <td><code>.ogx</code></td>
-   <td>OGG</td>
-   <td><code>application/ogg</code></td>
-  </tr>
-  <tr>
-   <td><code>.opus</code></td>
-   <td>Opus audio</td>
-   <td><code>audio/opus</code></td>
-  </tr>
-  <tr>
-   <td><code>.otf</code></td>
-   <td>OpenType font</td>
-   <td><code>font/otf</code></td>
-  </tr>
-  <tr>
-   <td><code>.png</code></td>
-   <td>Portable Network Graphics</td>
-   <td><code>image/png</code></td>
-  </tr>
-  <tr>
-   <td><code>.pdf</code></td>
-   <td>Adobe <a href="https://acrobat.adobe.com/us/en/why-adobe/about-adobe-pdf.html">Portable Document Format</a> (PDF)</td>
-   <td><code>application/pdf</code></td>
-  </tr>
-  <tr>
-   <td><code>.php</code></td>
-   <td>Hypertext Preprocessor (<strong>Personal Home Page</strong>)</td>
-   <td><code>application/x-httpd-php</code></td>
-  </tr>
-  <tr>
-   <td><code>.ppt</code></td>
-   <td>Microsoft PowerPoint</td>
-   <td><code>application/vnd.ms-powerpoint</code></td>
-  </tr>
-  <tr>
-   <td><code>.pptx</code></td>
-   <td>Microsoft PowerPoint (OpenXML)</td>
-   <td><code>application/vnd.openxmlformats-officedocument.presentationml.presentation</code></td>
-  </tr>
-  <tr>
-   <td><code>.rar</code></td>
-   <td>RAR archive</td>
-   <td><code>application/vnd.rar</code></td>
-  </tr>
-  <tr>
-   <td><code>.rtf</code></td>
-   <td>Rich Text Format (RTF)</td>
-   <td><code>application/rtf</code></td>
-  </tr>
-  <tr>
-   <td><code>.sh</code></td>
-   <td>Bourne shell script</td>
-   <td><code>application/x-sh</code></td>
-  </tr>
-  <tr>
-   <td><code>.svg</code></td>
-   <td>Scalable Vector Graphics (SVG)</td>
-   <td><code>image/svg+xml</code></td>
-  </tr>
-  <tr>
-   <td><code>.swf</code></td>
-   <td><a href="https://en.wikipedia.org/wiki/SWF">Small web format</a> (SWF) or Adobe Flash document</td>
-   <td><code>application/x-shockwave-flash</code></td>
-  </tr>
-  <tr>
-   <td><code>.tar</code></td>
-   <td>Tape Archive (TAR)</td>
-   <td><code>application/x-tar</code></td>
-  </tr>
-  <tr>
-   <td><code>.tif<br>
-    .tiff</code></td>
-   <td>Tagged Image File Format (TIFF)</td>
-   <td><code>image/tiff</code></td>
-  </tr>
-  <tr>
-   <td><code>.ts</code></td>
-   <td>MPEG transport stream</td>
-   <td><code>video/mp2t</code></td>
-  </tr>
-  <tr>
-   <td><code>.ttf</code></td>
-   <td>TrueType Font</td>
-   <td><code>font/ttf</code></td>
-  </tr>
-  <tr>
-   <td><code>.txt</code></td>
-   <td>Text, (generally ASCII or ISO 8859-<em>n</em>)</td>
-   <td><code>text/plain</code></td>
-  </tr>
-  <tr>
-   <td><code>.vsd</code></td>
-   <td>Microsoft Visio</td>
-   <td><code>application/vnd.visio</code></td>
-  </tr>
-  <tr>
-   <td><code>.wav</code></td>
-   <td>Waveform Audio Format</td>
-   <td><code>audio/wav</code></td>
-  </tr>
-  <tr>
-   <td><code>.weba</code></td>
-   <td>WEBM audio</td>
-   <td><code>audio/webm</code></td>
-  </tr>
-  <tr>
-   <td><code>.webm</code></td>
-   <td>WEBM video</td>
-   <td><code>video/webm</code></td>
-  </tr>
-  <tr>
-   <td><code>.webp</code></td>
-   <td>WEBP image</td>
-   <td><code>image/webp</code></td>
-  </tr>
-  <tr>
-   <td><code>.woff</code></td>
-   <td>Web Open Font Format (WOFF)</td>
-   <td><code>font/woff</code></td>
-  </tr>
-  <tr>
-   <td><code>.woff2</code></td>
-   <td>Web Open Font Format (WOFF)</td>
-   <td><code>font/woff2</code></td>
-  </tr>
-  <tr>
-   <td><code>.xhtml</code></td>
-   <td>XHTML</td>
-   <td><code>application/xhtml+xml</code></td>
-  </tr>
-  <tr>
-   <td><code>.xls</code></td>
-   <td>Microsoft Excel</td>
-   <td><code>application/vnd.ms-excel</code></td>
-  </tr>
-  <tr>
-   <td><code>.xlsx</code></td>
-   <td>Microsoft Excel (OpenXML)</td>
-   <td><code>application/vnd.openxmlformats-officedocument.spreadsheetml.sheet</code></td>
-  </tr>
-  <tr>
-   <td><code>.xml</code></td>
-   <td><code>XML</code></td>
-   <td><code>application/xml </code>if <em>not</em> readable from casual users (<a href="https://datatracker.ietf.org/doc/html/rfc3023#section-3">RFC 3023</a>, section 3)<br>
-    <code>text/xml</code> if readable from casual users (<a href="https://datatracker.ietf.org/doc/html/rfc3023#section-3">RFC 3023</a>, section 3)</td>
-  </tr>
-  <tr>
-   <td><code>.xul</code></td>
-   <td>XUL</td>
-   <td><code>application/vnd.mozilla.xul+xml</code></td>
-  </tr>
-  <tr>
-   <td><code>.zip</code></td>
-   <td>ZIP archive</td>
-   <td><code>application/zip</code></td>
-  </tr>
-  <tr>
-   <td><code>.3gp</code></td>
-   <td><a href="https://en.wikipedia.org/wiki/3GP_and_3G2">3GPP</a> audio/video container</td>
-   <td><code>video/3gpp</code><br>
-    <code>audio/3gpp</code> if it doesn't contain video</td>
-  </tr>
-  <tr>
-   <td><code>.3g2</code></td>
-   <td><a href="https://en.wikipedia.org/wiki/3GP_and_3G2">3GPP2</a> audio/video container</td>
-   <td><code>video/3gpp2</code><br>
-    <code>audio/3gpp2</code> if it doesn't contain video</td>
-  </tr>
-  <tr>
-   <td><code>.7z</code></td>
-   <td><a href="https://en.wikipedia.org/wiki/7-Zip">7-zip</a> archive</td>
-   <td><code>application/x-7z-compressed</code></td>
-  </tr>
- </tbody>
-</table>
+| Extension      | Kind of document                                                                                       | MIME Type                                                                                                                                                                                                                                                                            |
+| -------------- | ------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| `.aac`         | AAC audio                                                                                              | `audio/aac`                                                                                                                                                                                                                                                                          |
+| `.abw`         | [AbiWord](https://en.wikipedia.org/wiki/AbiWord) document                                              | `application/x-abiword`                                                                                                                                                                                                                                                              |
+| `.arc`         | Archive document (multiple files embedded)                                                             | `application/x-freearc`                                                                                                                                                                                                                                                              |
+| `.avi`         | AVI: Audio Video Interleave                                                                            | `video/x-msvideo`                                                                                                                                                                                                                                                                    |
+| `.azw`         | Amazon Kindle eBook format                                                                             | `application/vnd.amazon.ebook`                                                                                                                                                                                                                                                       |
+| `.bin`         | Any kind of binary data                                                                                | `application/octet-stream`                                                                                                                                                                                                                                                           |
+| `.bmp`         | Windows OS/2 Bitmap Graphics                                                                           | `image/bmp`                                                                                                                                                                                                                                                                          |
+| `.bz`          | BZip archive                                                                                           | `application/x-bzip`                                                                                                                                                                                                                                                                 |
+| `.bz2`         | BZip2 archive                                                                                          | `application/x-bzip2`                                                                                                                                                                                                                                                                |
+| `.cda`         | CD audio                                                                                               | `application/x-cdf`                                                                                                                                                                                                                                                                  |
+| `.csh`         | C-Shell script                                                                                         | `application/x-csh`                                                                                                                                                                                                                                                                  |
+| `.css`         | Cascading Style Sheets (CSS)                                                                           | `text/css`                                                                                                                                                                                                                                                                           |
+| `.csv`         | Comma-separated values (CSV)                                                                           | `text/csv`                                                                                                                                                                                                                                                                           |
+| `.doc`         | Microsoft Word                                                                                         | `application/msword`                                                                                                                                                                                                                                                                 |
+| `.docx`        | Microsoft Word (OpenXML)                                                                               | `application/vnd.openxmlformats-officedocument.wordprocessingml.document`                                                                                                                                                                                                            |
+| `.eot`         | MS Embedded OpenType fonts                                                                             | `application/vnd.ms-fontobject`                                                                                                                                                                                                                                                      |
+| `.epub`        | Electronic publication (EPUB)                                                                          | `application/epub+zip`                                                                                                                                                                                                                                                               |
+| `.gz`          | GZip Compressed Archive                                                                                | `application/gzip`                                                                                                                                                                                                                                                                   |
+| `.gif`         | Graphics Interchange Format (GIF)                                                                      | `image/gif`                                                                                                                                                                                                                                                                          |
+| `.htm .html`   | HyperText Markup Language (HTML)                                                                       | `text/html`                                                                                                                                                                                                                                                                          |
+| `.ico`         | Icon format                                                                                            | `image/vnd.microsoft.icon`                                                                                                                                                                                                                                                           |
+| `.ics`         | iCalendar format                                                                                       | `text/calendar`                                                                                                                                                                                                                                                                      |
+| `.jar`         | Java Archive (JAR)                                                                                     | `application/java-archive`                                                                                                                                                                                                                                                           |
+| `.jpeg` `.jpg` | JPEG images                                                                                            | `image/jpeg`                                                                                                                                                                                                                                                                         |
+| `.js`          | JavaScript                                                                                             | `text/javascript` (Specifications: [HTML](https://html.spec.whatwg.org/multipage/#scriptingLanguages) and its [reasoning](https://html.spec.whatwg.org/multipage/#dependencies:willful-violation), and [IETF](https://datatracker.ietf.org/doc/draft-ietf-dispatch-javascript-mjs/)) |
+| `.json`        | JSON format                                                                                            | `application/json`                                                                                                                                                                                                                                                                   |
+| `.jsonld`      | JSON-LD format                                                                                         | `application/ld+json`                                                                                                                                                                                                                                                                |
+| `.mid` `.midi` | Musical Instrument Digital Interface (MIDI)                                                            | `audio/midi` `audio/x-midi`                                                                                                                                                                                                                                                          |
+| `.mjs`         | JavaScript module                                                                                      | `text/javascript`                                                                                                                                                                                                                                                                    |
+| `.mp3`         | MP3 audio                                                                                              | `audio/mpeg`                                                                                                                                                                                                                                                                         |
+| `.mp4`         | MP4 audio                                                                                              | `video/mp4`                                                                                                                                                                                                                                                                          |
+| `.mpeg`        | MPEG Video                                                                                             | `video/mpeg`                                                                                                                                                                                                                                                                         |
+| `.mpkg`        | Apple Installer Package                                                                                | `application/vnd.apple.installer+xml`                                                                                                                                                                                                                                                |
+| `.odp`         | OpenDocument presentation document                                                                     | `application/vnd.oasis.opendocument.presentation`                                                                                                                                                                                                                                    |
+| `.ods`         | OpenDocument spreadsheet document                                                                      | `application/vnd.oasis.opendocument.spreadsheet`                                                                                                                                                                                                                                     |
+| `.odt`         | OpenDocument text document                                                                             | `application/vnd.oasis.opendocument.text`                                                                                                                                                                                                                                            |
+| `.oga`         | OGG audio                                                                                              | `audio/ogg`                                                                                                                                                                                                                                                                          |
+| `.ogv`         | OGG video                                                                                              | `video/ogg`                                                                                                                                                                                                                                                                          |
+| `.ogx`         | OGG                                                                                                    | `application/ogg`                                                                                                                                                                                                                                                                    |
+| `.opus`        | Opus audio                                                                                             | `audio/opus`                                                                                                                                                                                                                                                                         |
+| `.otf`         | OpenType font                                                                                          | `font/otf`                                                                                                                                                                                                                                                                           |
+| `.png`         | Portable Network Graphics                                                                              | `image/png`                                                                                                                                                                                                                                                                          |
+| `.pdf`         | Adobe [Portable Document Format](https://acrobat.adobe.com/us/en/why-adobe/about-adobe-pdf.html) (PDF) | `application/pdf`                                                                                                                                                                                                                                                                    |
+| `.php`         | Hypertext Preprocessor (**Personal Home Page**)                                                        | `application/x-httpd-php`                                                                                                                                                                                                                                                            |
+| `.ppt`         | Microsoft PowerPoint                                                                                   | `application/vnd.ms-powerpoint`                                                                                                                                                                                                                                                      |
+| `.pptx`        | Microsoft PowerPoint (OpenXML)                                                                         | `application/vnd.openxmlformats-officedocument.presentationml.presentation`                                                                                                                                                                                                          |
+| `.rar`         | RAR archive                                                                                            | `application/vnd.rar`                                                                                                                                                                                                                                                                |
+| `.rtf`         | Rich Text Format (RTF)                                                                                 | `application/rtf`                                                                                                                                                                                                                                                                    |
+| `.sh`          | Bourne shell script                                                                                    | `application/x-sh`                                                                                                                                                                                                                                                                   |
+| `.svg`         | Scalable Vector Graphics (SVG)                                                                         | `image/svg+xml`                                                                                                                                                                                                                                                                      |
+| `.swf`         | [Small web format](https://en.wikipedia.org/wiki/SWF) (SWF) or Adobe Flash document                    | `application/x-shockwave-flash`                                                                                                                                                                                                                                                      |
+| `.tar`         | Tape Archive (TAR)                                                                                     | `application/x-tar`                                                                                                                                                                                                                                                                  |
+| `.tif .tiff`   | Tagged Image File Format (TIFF)                                                                        | `image/tiff`                                                                                                                                                                                                                                                                         |
+| `.ts`          | MPEG transport stream                                                                                  | `video/mp2t`                                                                                                                                                                                                                                                                         |
+| `.ttf`         | TrueType Font                                                                                          | `font/ttf`                                                                                                                                                                                                                                                                           |
+| `.txt`         | Text, (generally ASCII or ISO 8859-_n_)                                                                | `text/plain`                                                                                                                                                                                                                                                                         |
+| `.vsd`         | Microsoft Visio                                                                                        | `application/vnd.visio`                                                                                                                                                                                                                                                              |
+| `.wav`         | Waveform Audio Format                                                                                  | `audio/wav`                                                                                                                                                                                                                                                                          |
+| `.weba`        | WEBM audio                                                                                             | `audio/webm`                                                                                                                                                                                                                                                                         |
+| `.webm`        | WEBM video                                                                                             | `video/webm`                                                                                                                                                                                                                                                                         |
+| `.webp`        | WEBP image                                                                                             | `image/webp`                                                                                                                                                                                                                                                                         |
+| `.woff`        | Web Open Font Format (WOFF)                                                                            | `font/woff`                                                                                                                                                                                                                                                                          |
+| `.woff2`       | Web Open Font Format (WOFF)                                                                            | `font/woff2`                                                                                                                                                                                                                                                                         |
+| `.xhtml`       | XHTML                                                                                                  | `application/xhtml+xml`                                                                                                                                                                                                                                                              |
+| `.xls`         | Microsoft Excel                                                                                        | `application/vnd.ms-excel`                                                                                                                                                                                                                                                           |
+| `.xlsx`        | Microsoft Excel (OpenXML)                                                                              | `application/vnd.openxmlformats-officedocument.spreadsheetml.sheet`                                                                                                                                                                                                                  |
+| `.xml`         | `XML`                                                                                                  | `application/xml `if _not_ readable from casual users ([RFC 3023](https://datatracker.ietf.org/doc/html/rfc3023#section-3), section 3) `text/xml` if readable from casual users ([RFC 3023](https://datatracker.ietf.org/doc/html/rfc3023#section-3), section 3)                     |
+| `.xul`         | XUL                                                                                                    | `application/vnd.mozilla.xul+xml`                                                                                                                                                                                                                                                    |
+| `.zip`         | ZIP archive                                                                                            | `application/zip`                                                                                                                                                                                                                                                                    |
+| `.3gp`         | [3GPP](https://en.wikipedia.org/wiki/3GP_and_3G2) audio/video container                                | `video/3gpp` `audio/3gpp` if it doesn't contain video                                                                                                                                                                                                                                |
+| `.3g2`         | [3GPP2](https://en.wikipedia.org/wiki/3GP_and_3G2) audio/video container                               | `video/3gpp2` `audio/3gpp2` if it doesn't contain video                                                                                                                                                                                                                              |
+| `.7z`          | [7-zip](https://en.wikipedia.org/wiki/7-Zip) archive                                                   | `application/x-7z-compressed`                                                                                                                                                                                                                                                        |
diff --git a/files/en-us/web/http/basics_of_http/mime_types/index.md b/files/en-us/web/http/basics_of_http/mime_types/index.md
index 601c249097e353d..089f930113c2c69 100644
--- a/files/en-us/web/http/basics_of_http/mime_types/index.md
+++ b/files/en-us/web/http/basics_of_http/mime_types/index.md
@@ -13,398 +13,294 @@ tags:
   - application/json
   - application/xml
 ---
-<div>{{HTTPSidebar}}</div>
-
-<p>
-  A <strong>media type</strong> (also known as a
-  <strong>Multipurpose Internet Mail Extensions or MIME type</strong>) is a standard
-  that indicates the nature and format of a document, file, or assortment of
-  bytes. It is defined and standardized in IETF's {{RFC(6838)}}.
-</p>
-
-<p>The <a href="https://www.iana.org/">Internet Assigned Numbers Authority (IANA)</a> is
-  responsible for all official MIME types, and you can find the most up-to-date and
-  complete list at their <a
-    href="https://www.iana.org/assignments/media-types/media-types.xhtml">Media Types</a>
-  page.</p>
-
-<div class="notecard warning">
-  <p>
-    <strong>Warning:</strong> Browsers use the MIME type,
-    <em>not the file extension</em>,
-    to determine how to process a URL,
-    so it's important
-    that web servers send the correct MIME type in the response's {{HTTPHeader("Content-Type")}} header.
-    If this is not correctly configured,
-    browsers are likely to misinterpret the contents of files,
-    sites will not work correctly,
-    and downloaded files may be mishandled.
-  </p>
-</div>
-
-<h2 id="Structure_of_a_MIME_type">Structure of a MIME type</h2>
-
-<p>The simplest MIME type consists of a <var>type</var> and a <var>subtype</var>; these
-  are each strings which, when concatenated with a slash (<code>/</code>) between them,
-  comprise a MIME type. No whitespace is allowed in a MIME type:</p>
-
-<pre class="brush: html"><var>type</var>/<var>subtype</var></pre>
-
-<p>The <strong><var>type</var></strong> represents the general category into which the
-  data type falls, such as <code>video</code> or <code>text</code>. The
-  <strong><var>subtype</var></strong> identifies the exact kind of data of the specified
-  type the MIME type represents. For example, for the MIME type <code>text</code>, the
-  subtype might be <code>plain</code> (plain text), <code>html</code>
-  ({{Glossary("HTML")}} source code), or <code>calendar</code> (for
-  iCalendar/<code>.ics</code>) files.</p>
-
-<p>Each type has its own set of possible subtypes, and a MIME type always has both a type
-  and a subtype, never just one or the other.</p>
-
-<p>An optional <strong>parameter</strong> can be added to provide additional details:</p>
-
-<pre
-  class="brush: html"><var>type</var>/<var>subtype</var>;<var>parameter</var>=<var>value</var></pre>
-
-<p>For example, for any MIME type whose main type is <code>text</code>, the optional
-  <code>charset</code> parameter can be used to specify the character set used for the
-  characters in the data. If no <code>charset</code> is specified, the default is
-  {{Glossary("ASCII")}} (<code>US-ASCII</code>) unless overridden by the {{Glossary("user
+{{HTTPSidebar}}
+
+A **media type** (also known as a
+**Multipurpose Internet Mail Extensions or MIME type**) is a standard
+that indicates the nature and format of a document, file, or assortment of
+bytes. It is defined and standardized in IETF's {{RFC(6838)}}.
+
+The [Internet Assigned Numbers Authority (IANA)](https://www.iana.org/) is
+responsible for all official MIME types, and you can find the most up-to-date and
+complete list at their [Media Types](https://www.iana.org/assignments/media-types/media-types.xhtml)
+page.
+
+> **Warning:** Browsers use the MIME type,
+> _not the file extension_,
+> to determine how to process a URL,
+> so it's important
+> that web servers send the correct MIME type in the response's {{HTTPHeader("Content-Type")}} header.
+> If this is not correctly configured,
+> browsers are likely to misinterpret the contents of files,
+> sites will not work correctly,
+> and downloaded files may be mishandled.
+
+## Structure of a MIME type
+
+The simplest MIME type consists of a _type_ and a _subtype_; these
+are each strings which, when concatenated with a slash (`/`) between them,
+comprise a MIME type. No whitespace is allowed in a MIME type:
+
+```html
+type/subtype
+```
+
+The **_type_** represents the general category into which the
+data type falls, such as `video` or `text`. The
+**_subtype_** identifies the exact kind of data of the specified
+type the MIME type represents. For example, for the MIME type `text`, the
+subtype might be `plain` (plain text), `html`
+({{Glossary("HTML")}} source code), or `calendar` (for
+iCalendar/`.ics`) files.
+
+Each type has its own set of possible subtypes, and a MIME type always has both a type
+and a subtype, never just one or the other.
+
+An optional **parameter** can be added to provide additional details:
+
+```html
+type/subtype;parameter=value
+```
+
+For example, for any MIME type whose main type is `text`, the optional
+`charset` parameter can be used to specify the character set used for the
+characters in the data. If no `charset` is specified, the default is
+{{Glossary("ASCII")}} (`US-ASCII`) unless overridden by the {{Glossary("user
   agent", "user agent's")}} settings. To specify a UTF-8 text file, the MIME type
-  <code>text/plain;charset=UTF-8</code> is used.</p>
+`text/plain;charset=UTF-8` is used.
 
-<p>MIME types are case-insensitive but are traditionally written in lowercase, with the
-  exception of parameter values, whose case may or may not have specific meaning.</p>
+MIME types are case-insensitive but are traditionally written in lowercase, with the
+exception of parameter values, whose case may or may not have specific meaning.
 
-<h3 id="Types">Types</h3>
+### Types
 
-<p>There are two classes of type: <strong>discrete</strong> and
-  <strong>multipart</strong>. Discrete types are types which represent a single file or
-  medium, such as a single text or music file, or a single video. A multipart type is one
-  which represents a document that's comprised of multiple component parts, each of which
-  may have its own individual MIME type; or, a multipart type may encapsulate multiple
-  files being sent together in one transaction. For example, multipart MIME types are used
-  when attaching multiple files to an email.</p>
+There are two classes of type: **discrete** and
+**multipart**. Discrete types are types which represent a single file or
+medium, such as a single text or music file, or a single video. A multipart type is one
+which represents a document that's comprised of multiple component parts, each of which
+may have its own individual MIME type; or, a multipart type may encapsulate multiple
+files being sent together in one transaction. For example, multipart MIME types are used
+when attaching multiple files to an email.
 
-<h4 id="Discrete_types">Discrete types</h4>
+#### Discrete types
 
-<p>The discrete types currently registered with the IANA are:</p>
+The discrete types currently registered with the IANA are:
 
-<dl>
-  <dt>
-    <code>application</code>
-  </dt>
-  <dd>
-    Any kind of binary data that doesn't fall explicitly into one of the other types;
+- `application`
+  - : Any kind of binary data that doesn't fall explicitly into one of the other types;
     either data that will be executed or interpreted in some way or binary data that
     requires a specific application or category of application to use. Generic binary data
-    (or binary data whose true type is unknown) is <code>application/octet-stream</code>.
-    Other common examples include <code>application/pdf</code>,
-    <code>application/pkcs8</code>, and <code>application/zip</code>.
-    <a href="https://www.iana.org/assignments/media-types/media-types.xhtml#application">(Registration at IANA)</a>
-  </dd>
-
-  <dt>
-    <code>audio</code>
-  </dt>
-  <dd>
-    Audio or music data. Examples include <code>audio/mpeg</code>,
-    <code>audio/vorbis</code>.
-    <a href="https://www.iana.org/assignments/media-types/media-types.xhtml#audio">(Registration at IANA)</a>
-  </dd>
-
-  <dt>
-    <code>example</code>
-  </dt>
-  <dd>
-    Reserved for use as a placeholder in examples showing how to use MIME types. These
+    (or binary data whose true type is unknown) is `application/octet-stream`.
+    Other common examples include `application/pdf`,
+    `application/pkcs8`, and `application/zip`.
+    [(Registration at IANA)](https://www.iana.org/assignments/media-types/media-types.xhtml#application)
+- `audio`
+  - : Audio or music data. Examples include `audio/mpeg`,
+    `audio/vorbis`.
+    [(Registration at IANA)](https://www.iana.org/assignments/media-types/media-types.xhtml#audio)
+- `example`
+  - : Reserved for use as a placeholder in examples showing how to use MIME types. These
     should never be used outside of sample code listings and documentation.
-    <code>example</code> can also be used as a subtype; for instance, in an example
-    related to working with audio on the web, the MIME type <code>audio/example</code> can
+    `example` can also be used as a subtype; for instance, in an example
+    related to working with audio on the web, the MIME type `audio/example` can
     be used to indicate that the type is a placeholder and should be replaced with an
     appropriate one when using the code in the real world.
-  </dd>
-
-  <dt>
-    <code>font</code>
-  </dt>
-  <dd>
-    Font/typeface data. Common examples include <code>font/woff</code>,
-    <code>font/ttf</code>, and <code>font/otf</code>.
-    <a href="https://www.iana.org/assignments/media-types/media-types.xhtml#font">(Registration at IANA)</a>
-  </dd>
-
-  <dt>
-    <code>image</code>
-  </dt>
-  <dd>
-    Image or graphical data including both bitmap and vector still images as well as
+- `font`
+  - : Font/typeface data. Common examples include `font/woff`,
+    `font/ttf`, and `font/otf`.
+    [(Registration at IANA)](https://www.iana.org/assignments/media-types/media-types.xhtml#font)
+- `image`
+  - : Image or graphical data including both bitmap and vector still images as well as
     animated versions of still image formats such as animated {{Glossary("GIF")}} or APNG.
-    Common examples are <code>image/jpeg</code>, <code>image/png</code>, and
-    <code>image/svg+xml</code>.
-    <a href="https://www.iana.org/assignments/media-types/media-types.xhtml#image">(Registration at IANA)</a>
-  </dd>
-  <dt>
-    <code>model</code>
-  </dt>
-  <dd>
-    Model data for a 3D object or scene. Examples include <code>model/3mf</code> and
-    <code>model/vrml</code>.
-    <a href="https://www.iana.org/assignments/media-types/media-types.xhtml#model">(Registration at IANA)</a>
-  </dd>
-
-  <dt>
-    <code>text</code>
-  </dt>
-  <dd>
-    Text-only data including any human-readable content, source code, or textual data
+    Common examples are `image/jpeg`, `image/png`, and
+    `image/svg+xml`.
+    [(Registration at IANA)](https://www.iana.org/assignments/media-types/media-types.xhtml#image)
+- `model`
+  - : Model data for a 3D object or scene. Examples include `model/3mf` and
+    `model/vrml`.
+    [(Registration at IANA)](https://www.iana.org/assignments/media-types/media-types.xhtml#model)
+- `text`
+  - : Text-only data including any human-readable content, source code, or textual data
     such as comma-separated value (CSV) formatted data. Examples include
-    <code>text/plain</code>, <code>text/csv</code>, and <code>text/html</code>.
-    <a href="https://www.iana.org/assignments/media-types/media-types.xhtml#text">(Registration at IANA)</a>
-  </dd>
-
-  <dt>
-    <code>video</code>
-  </dt>
-  <dd>
-    Video data or files, such as MP4 movies (<code>video/mp4</code>).
-    <a href="https://www.iana.org/assignments/media-types/media-types.xhtml#video">(Registration at IANA)</a>
-  </dd>
-</dl>
-
-<p>For text documents without a specific subtype, <code>text/plain</code> should be used.
-  Similarly, for binary documents without a specific or known subtype,
-  <code>application/octet-stream</code> should be used.</p>
-
-<h4 id="Multipart_types">Multipart types</h4>
-
-<p><strong>Multipart</strong> types indicate a category of document broken into
-  pieces, often with different MIME types; they can also be used — especially in email
-  scenarios — to represent multiple, separate files which are all part of the same
-  transaction. They represent a <strong>composite document</strong>.</p>
-
-<p>With the exception of <code>multipart/form-data</code>, used in
-  the {{HTTPMethod("POST")}} method of <a href="/en-US/docs/Learn/Forms">HTML
-    Forms</a>, and <code>multipart/byteranges</code>, used with {{HTTPStatus("206")}}
-  <code>Partial Content</code> to send part of a document, HTTP doesn't handle multipart
-  documents in a special way: the message is transmitted to the browser (which will likely
-  show a "Save As" window if it doesn't know how to display the document).</p>
-
-<p>There are two multipart types:</p>
-
-<dl>
-  <dt>
-    <code>message</code>
-  </dt>
-  <dd>
-    A message that encapsulates other messages. This can be used, for instance, to
+    `text/plain`, `text/csv`, and `text/html`.
+    [(Registration at IANA)](https://www.iana.org/assignments/media-types/media-types.xhtml#text)
+- `video`
+  - : Video data or files, such as MP4 movies (`video/mp4`).
+    [(Registration at IANA)](https://www.iana.org/assignments/media-types/media-types.xhtml#video)
+
+For text documents without a specific subtype, `text/plain` should be used.
+Similarly, for binary documents without a specific or known subtype,
+`application/octet-stream` should be used.
+
+#### Multipart types
+
+**Multipart** types indicate a category of document broken into
+pieces, often with different MIME types; they can also be used — especially in email
+scenarios — to represent multiple, separate files which are all part of the same
+transaction. They represent a **composite document**.
+
+With the exception of `multipart/form-data`, used in
+the {{HTTPMethod("POST")}} method of [HTML
+Forms](/en-US/docs/Learn/Forms), and `multipart/byteranges`, used with {{HTTPStatus("206")}}
+`Partial Content` to send part of a document, HTTP doesn't handle multipart
+documents in a special way: the message is transmitted to the browser (which will likely
+show a "Save As" window if it doesn't know how to display the document).
+
+There are two multipart types:
+
+- `message`
+  - : A message that encapsulates other messages. This can be used, for instance, to
     represent an email that includes a forwarded message as part of its data, or to allow
     sending very large messages in chunks as if it were multiple messages. Examples
-    include <code>message/rfc822</code> (for forwarded or replied-to message quoting) and
-    <code>message/partial</code> to allow breaking a large message into smaller ones
+    include `message/rfc822` (for forwarded or replied-to message quoting) and
+    `message/partial` to allow breaking a large message into smaller ones
     automatically to be reassembled by the recipient.
-    <a href="https://www.iana.org/assignments/media-types/media-types.xhtml#message">(Registration at IANA)</a>
-  </dd>
-
-  <dt>
-    <code>multipart</code>
-  </dt>
-  <dd>
-    Data that is comprised of multiple components which may individually have different
-    MIME types. Examples include <code>multipart/form-data</code> (for data produced using
-    the {{domxref("FormData")}} API) and <code>multipart/byteranges</code> (defined in
+    [(Registration at IANA)](https://www.iana.org/assignments/media-types/media-types.xhtml#message)
+- `multipart`
+  - : Data that is comprised of multiple components which may individually have different
+    MIME types. Examples include `multipart/form-data` (for data produced using
+    the {{domxref("FormData")}} API) and `multipart/byteranges` (defined in
     {{RFC(7233, "5.4.1")}} and used with {{Glossary("HTTP")}}'s {{HTTPStatus(206)}}
     "Partial Content" response returned when the fetched data is only part of the content,
     such as is delivered using the {{HTTPHeader("Range")}} header).
-    <a href="https://www.iana.org/assignments/media-types/media-types.xhtml#multipart">(Registration at IANA)</a>
-  </dd>
-</dl>
-
-<h2 id="Important_MIME_types_for_Web_developers">Important MIME types for Web developers
-</h2>
-
-<h3 id="applicationoctet-stream">application/octet-stream</h3>
-
-<p>This is the default for binary files. As it means <em>unknown binary</em> file,
-  browsers usually don't execute it, or even ask if it should be executed. They treat it
-  as if the {{HTTPHeader("Content-Disposition")}} header was set to
-  <code>attachment</code>, and propose a "Save As" dialog.</p>
-
-<h3 id="textplain">text/plain</h3>
-
-<p>This is the default for textual files. Even if it really means "unknown textual file,"
-  browsers assume they can display it.</p>
-
-<div class="notecard note">
-  <p><strong>Note:</strong> <code>text/plain</code> does not mean "any kind of textual data." If they
-    expect a specific kind of textual data, they will likely not consider it a match.
-    Specifically if they download a <code>text/plain</code> file from a
-    {{HTMLElement("link")}} element declaring a CSS file, they will not recognize it as a
-    valid CSS file if presented with <code>text/plain</code>. The CSS mime type
-    <code>text/css</code> must be used.</p>
-</div>
-
-<h3 id="textcss">text/css</h3>
-
-<p>CSS files used to style a Web page <strong>must</strong> be sent with
-  <code>text/css</code>. If a server doesn't recognize the <code>.css</code> suffix for
-  CSS files, it may send them with <code>text/plain</code> or
-  <code>application/octet-stream</code> MIME types. If so, they won't be recognized as CSS
-  by most browsers and will be ignored.</p>
-
-<h3 id="texthtml">text/html</h3>
-
-<p>All HTML content should be served with this type. Alternative MIME types for XHTML
-  (like <code>application/xhtml+xml</code>) are mostly useless nowadays.</p>
-
-<div class="notecard note">
-  <p><strong>Note:</strong> Use <code>application/xml</code> or
-    <code>application/xhtml+xml</code> if you want XML's strict parsing rules,
-    <code><a href="/en-US/docs/Web/API/CDATASection">&lt;![CDATA[…]]&gt;</a></code>
-    sections, or elements that aren't from HTML/SVG/MathML namespaces.</p>
-</div>
-
-<h3 id="textjavascript"><span id="JavaScript_types">text/javascript</span></h3>
-
-<p>Per the HTML specification, JavaScript files should always be served using the MIME
-  type <code>text/javascript</code>. No other values are considered valid, and using any
-  of those may result in scripts that do not load or run.</p>
-
-<p>For historical reasons, the <a href="https://mimesniff.spec.whatwg.org/">MIME Sniffing
-    Standard</a> (the definition of how browsers should interpret media types and figure
-  out what to do with content that doesn't have a valid one) allows JavaScript to be
-  served using any MIME type that essentially matches any of the following:</p>
-
-<ul>
-  <li><code>application/javascript</code></li>
-  <li><code>application/ecmascript</code></li>
-  <li><code>application/x-ecmascript</code> {{Non-standard_Inline}}</li>
-  <li><code>application/x-javascript</code> {{Non-standard_Inline}}</li>
-  <li><code>text/javascript</code></li>
-  <li><code>text/ecmascript</code></li>
-  <li><code>text/javascript1.0</code> {{Non-standard_Inline}}</li>
-  <li><code>text/javascript1.1</code> {{Non-standard_Inline}}</li>
-  <li><code>text/javascript1.2</code> {{Non-standard_Inline}}</li>
-  <li><code>text/javascript1.3</code> {{Non-standard_Inline}}</li>
-  <li><code>text/javascript1.4</code> {{Non-standard_Inline}}</li>
-  <li><code>text/javascript1.5</code> {{Non-standard_Inline}}</li>
-  <li><code>text/jscript</code> {{Non-standard_Inline}}</li>
-  <li><code>text/livescript</code> {{Non-standard_Inline}}</li>
-  <li><code>text/x-ecmascript</code> {{Non-standard_Inline}}</li>
-  <li><code>text/x-javascript</code> {{Non-standard_Inline}}</li>
-</ul>
-
-<div class="notecard note">
-  <p><strong>Note:</strong> Even though any given {{Glossary("user agent")}} may support
-    any or all of these, you should only use <code>text/javascript</code>. It's the only
-    MIME type guaranteed to work now and into the future.</p>
-</div>
-
-<p>Some content you find may have a <code>charset</code> parameter at the end of the
-  <code>text/javascript</code> media type, to specify the character set used to represent
-  the code's content. This is not valid, and in most cases will result in a script not
-  being loaded.</p>
-
-<h3 id="Image_types">Image types</h3>
-
-<p>Files whose MIME type is <code>image</code> contain image data. The subtype specifies
-  which specific image file format the data represents. Only a few image types are used
-  commonly enough to be considered safe for use on web pages:</p>
-
-<p>{{page("en-US/docs/Web/Media/Formats/Image_types", "table-of-image-file-types")}}</p>
-
-<h3 id="Audio_and_video_types">Audio and video types</h3>
-
-<p>As is the case for images, HTML doesn't mandate that web browsers support any specific
-  file and codec types for the {{HTMLElement("audio")}} and {{HTMLElement("video")}}
-  elements, so it's important to consider your target audience and the range of browsers
-  (and versions of those browsers) they may be using when choosing the file type and
-  codecs to use for media.</p>
-
-<p>Our <a href="/en-US/docs/Web/Media/Formats/Containers">media container formats
-    guide</a> provides a list of the file types that are commonly supported by web
-  browsers, including information about what their special use cases may be, any drawbacks
-  they have, and compatibility information, along with other details.</p>
-
-<p>The <a href="/en-US/docs/Web/Media/Formats/Audio_codecs">audio codec</a> and <a
-    href="/en-US/docs/Web/Media/Formats/Video_codecs">video codec</a> guides list the
-  various codecs that web browsers often support, providing compatibility details along
-  with technical information such as how many audio channels they support, what sort of
-  compression is used, and what bit rates and so forth they're useful at. The <a
-    href="/en-US/docs/Web/Media/Formats/WebRTC_codecs">codecs used by WebRTC</a> guide
-  expands upon this by specifically covering the codecs supported by the major web
-  browsers, so you can choose the codecs that best cover the range of browsers you wish to
-  support.</p>
-
-<p>As for MIME types of audio or video files, they typically specify the container format
-  (file type). The optional <a
-    href="/en-US/docs/Web/Media/Formats/codecs_parameter">codecs parameter</a> can be
-  added to the MIME type to further specify which codecs to use and what options were used
-  to encode the media, such as codec profile, level, or other such information.</p>
-
-<p>The most commonly used MIME types used for web content are listed below. This isn't a
-  complete list of all the types that may be available, however. See the <a
-    href="/en-US/docs/Web/Media/Formats/Containers">media container formats</a> guide for
-  that.</p>
-
-<table class="standard-table">
-  <thead>
-    <tr>
-      <th scope="col">MIME type</th>
-      <th scope="col">Audio or video type</th>
-    </tr>
-  </thead>
-  <tbody>
-    <tr>
-      <td><code>audio/wave</code><br>
-        <code>audio/wav</code><br>
-        <code>audio/x-wav</code><br>
-        <code>audio/x-pn-wav</code>
-      </td>
-      <td>An audio file in the WAVE container format. The PCM audio codec (WAVE codec "1")
-        is often supported, but other codecs have limited support (if any).</td>
-    </tr>
-    <tr>
-      <td><code>audio/webm</code></td>
-      <td>An audio file in the WebM container format. Vorbis and Opus are the codecs
-        officially supported by the WebM specification.</td>
-    </tr>
-    <tr>
-      <td><code>video/webm</code></td>
-      <td>A video file, possibly with audio, in the WebM container format. VP8 and VP9 are
-        the most common video codecs; Vorbis and Opus the most common audio codecs.</td>
-    </tr>
-    <tr>
-      <td><code>audio/ogg</code></td>
-      <td>An audio file in the Ogg container format. Vorbis is the most common audio codec
-        used in such a container; however, Opus is now supported by Ogg as well.</td>
-    </tr>
-    <tr>
-      <td><code>video/ogg</code></td>
-      <td>A video file, possibly with audio, in the Ogg container format. Theora is the
-        usual video codec used within it; Vorbis is the usual audio codec, although Opus
-        is becoming more common.</td>
-    </tr>
-    <tr>
-      <td><code>application/ogg</code></td>
-      <td>An audio or video file using the Ogg container format. Theora is the usual video
-        codec used within it; Vorbis is the usual audio codec.</td>
-    </tr>
-  </tbody>
-</table>
-
-<h3 id="multipartform-data">multipart/form-data</h3>
-
-<p>The <code>multipart/form-data</code> type can be used when sending the values of a
-  completed <a href="/en-US/docs/Learn/Forms">HTML Form</a> from browser to
-  server.</p>
-
-<p>As a multipart document format, it consists of different parts, delimited by a boundary
-  (a string starting with a double dash <code>--</code>). Each part is its own entity with
-  its own HTTP headers, {{HTTPHeader("Content-Disposition")}}, and
-  {{HTTPHeader("Content-Type")}} for file uploading fields.</p>
-
-<pre class="brush: html">Content-Type: multipart/form-data; boundary=aBoundaryString
+    [(Registration at IANA)](https://www.iana.org/assignments/media-types/media-types.xhtml#multipart)
+
+## Important MIME types for Web developers
+
+### application/octet-stream
+
+This is the default for binary files. As it means _unknown binary_ file,
+browsers usually don't execute it, or even ask if it should be executed. They treat it
+as if the {{HTTPHeader("Content-Disposition")}} header was set to
+`attachment`, and propose a "Save As" dialog.
+
+### text/plain
+
+This is the default for textual files. Even if it really means "unknown textual file,"
+browsers assume they can display it.
+
+> **Note:** `text/plain` does not mean "any kind of textual data." If they
+> expect a specific kind of textual data, they will likely not consider it a match.
+> Specifically if they download a `text/plain` file from a
+> {{HTMLElement("link")}} element declaring a CSS file, they will not recognize it as a
+> valid CSS file if presented with `text/plain`. The CSS mime type
+> `text/css` must be used.
+
+### text/css
+
+CSS files used to style a Web page **must** be sent with
+`text/css`. If a server doesn't recognize the `.css` suffix for
+CSS files, it may send them with `text/plain` or
+`application/octet-stream` MIME types. If so, they won't be recognized as CSS
+by most browsers and will be ignored.
+
+### text/html
+
+All HTML content should be served with this type. Alternative MIME types for XHTML
+(like `application/xhtml+xml`) are mostly useless nowadays.
+
+> **Note:** Use `application/xml` or
+> `application/xhtml+xml` if you want XML's strict parsing rules,
+> [`<![CDATA[…]]>`](/en-US/docs/Web/API/CDATASection)
+> sections, or elements that aren't from HTML/SVG/MathML namespaces.
+
+### text/javascript
+
+Per the HTML specification, JavaScript files should always be served using the MIME
+type `text/javascript`. No other values are considered valid, and using any
+of those may result in scripts that do not load or run.
+
+For historical reasons, the [MIME Sniffing
+Standard](https://mimesniff.spec.whatwg.org/) (the definition of how browsers should interpret media types and figure
+out what to do with content that doesn't have a valid one) allows JavaScript to be
+served using any MIME type that essentially matches any of the following:
+
+- `application/javascript`
+- `application/ecmascript`
+- `application/x-ecmascript` {{Non-standard_Inline}}
+- `application/x-javascript` {{Non-standard_Inline}}
+- `text/javascript`
+- `text/ecmascript`
+- `text/javascript1.0` {{Non-standard_Inline}}
+- `text/javascript1.1` {{Non-standard_Inline}}
+- `text/javascript1.2` {{Non-standard_Inline}}
+- `text/javascript1.3` {{Non-standard_Inline}}
+- `text/javascript1.4` {{Non-standard_Inline}}
+- `text/javascript1.5` {{Non-standard_Inline}}
+- `text/jscript` {{Non-standard_Inline}}
+- `text/livescript` {{Non-standard_Inline}}
+- `text/x-ecmascript` {{Non-standard_Inline}}
+- `text/x-javascript` {{Non-standard_Inline}}
+
+> **Note:** Even though any given {{Glossary("user agent")}} may support
+> any or all of these, you should only use `text/javascript`. It's the only
+> MIME type guaranteed to work now and into the future.
+
+Some content you find may have a `charset` parameter at the end of the
+`text/javascript` media type, to specify the character set used to represent
+the code's content. This is not valid, and in most cases will result in a script not
+being loaded.
+
+### Image types
+
+Files whose MIME type is `image` contain image data. The subtype specifies
+which specific image file format the data represents. Only a few image types are used
+commonly enough to be considered safe for use on web pages:
+
+{{page("en-US/docs/Web/Media/Formats/Image_types", "table-of-image-file-types")}}
+
+### Audio and video types
+
+As is the case for images, HTML doesn't mandate that web browsers support any specific
+file and codec types for the {{HTMLElement("audio")}} and {{HTMLElement("video")}}
+elements, so it's important to consider your target audience and the range of browsers
+(and versions of those browsers) they may be using when choosing the file type and
+codecs to use for media.
+
+Our [media container formats
+guide](/en-US/docs/Web/Media/Formats/Containers) provides a list of the file types that are commonly supported by web
+browsers, including information about what their special use cases may be, any drawbacks
+they have, and compatibility information, along with other details.
+
+The [audio codec](/en-US/docs/Web/Media/Formats/Audio_codecs) and [video codec](/en-US/docs/Web/Media/Formats/Video_codecs) guides list the
+various codecs that web browsers often support, providing compatibility details along
+with technical information such as how many audio channels they support, what sort of
+compression is used, and what bit rates and so forth they're useful at. The [codecs used by WebRTC](/en-US/docs/Web/Media/Formats/WebRTC_codecs) guide
+expands upon this by specifically covering the codecs supported by the major web
+browsers, so you can choose the codecs that best cover the range of browsers you wish to
+support.
+
+As for MIME types of audio or video files, they typically specify the container format
+(file type). The optional [codecs parameter](/en-US/docs/Web/Media/Formats/codecs_parameter) can be
+added to the MIME type to further specify which codecs to use and what options were used
+to encode the media, such as codec profile, level, or other such information.
+
+The most commonly used MIME types used for web content are listed below. This isn't a
+complete list of all the types that may be available, however. See the [media container formats](/en-US/docs/Web/Media/Formats/Containers) guide for
+that.
+
+| MIME type                                               | Audio or video type                                                                                                                                                                     |
+| ------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `audio/wave` `audio/wav` `audio/x-wav` `audio/x-pn-wav` | An audio file in the WAVE container format. The PCM audio codec (WAVE codec "1") is often supported, but other codecs have limited support (if any).                                    |
+| `audio/webm`                                            | An audio file in the WebM container format. Vorbis and Opus are the codecs officially supported by the WebM specification.                                                              |
+| `video/webm`                                            | A video file, possibly with audio, in the WebM container format. VP8 and VP9 are the most common video codecs; Vorbis and Opus the most common audio codecs.                            |
+| `audio/ogg`                                             | An audio file in the Ogg container format. Vorbis is the most common audio codec used in such a container; however, Opus is now supported by Ogg as well.                               |
+| `video/ogg`                                             | A video file, possibly with audio, in the Ogg container format. Theora is the usual video codec used within it; Vorbis is the usual audio codec, although Opus is becoming more common. |
+| `application/ogg`                                       | An audio or video file using the Ogg container format. Theora is the usual video codec used within it; Vorbis is the usual audio codec.                                                 |
+
+### multipart/form-data
+
+The `multipart/form-data` type can be used when sending the values of a
+completed [HTML Form](/en-US/docs/Learn/Forms) from browser to
+server.
+
+As a multipart document format, it consists of different parts, delimited by a boundary
+(a string starting with a double dash `--`). Each part is its own entity with
+its own HTTP headers, {{HTTPHeader("Content-Disposition")}}, and
+{{HTTPHeader("Content-Type")}} for file uploading fields.
+
+```html
+Content-Type: multipart/form-data; boundary=aBoundaryString
 (other headers associated with the multipart document as a whole)
 
 --aBoundaryString
@@ -419,148 +315,131 @@ Content-Disposition: form-data; name="myField"
 --aBoundaryString
 (more subparts)
 --aBoundaryString--
-
-</pre>
-
-<p>The following <code>&lt;form&gt;</code>:</p>
-
-<pre class="brush: html">&lt;form action="http://localhost:8000/" method="post" enctype="multipart/form-data"&gt;
-  &lt;label&gt;Name: &lt;input name="myTextField" value="Test"&gt;&lt;/label&gt;
-  &lt;label&gt;&lt;input type="checkbox" name="myCheckBox"&gt; Check&lt;/label&gt;
-  &lt;label&gt;Upload file: &lt;input type="file" name="myFile" value="test.txt"&gt;&lt;/label&gt;
-  &lt;button&gt;Send the file&lt;/button&gt;
-&lt;/form&gt;</pre>
-
-<p>will send this message:</p>
-
-<pre>POST / HTTP/1.1
-Host: localhost:8000
-User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:50.0) Gecko/20100101 Firefox/50.0
-Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
-Accept-Language: en-US,en;q=0.5
-Accept-Encoding: gzip, deflate
-Connection: keep-alive
-Upgrade-Insecure-Requests: 1
-Content-Type: multipart/form-data; boundary=---------------------------8721656041911415653955004498
-Content-Length: 465
-
------------------------------8721656041911415653955004498
-Content-Disposition: form-data; name="myTextField"
-
-Test
------------------------------8721656041911415653955004498
-Content-Disposition: form-data; name="myCheckBox"
-
-on
------------------------------8721656041911415653955004498
-Content-Disposition: form-data; name="myFile"; filename="test.txt"
-Content-Type: text/plain
-
-Simple file.
------------------------------8721656041911415653955004498--
-
-</pre>
-
-<h3 id="multipartbyteranges">multipart/byteranges</h3>
-
-<p>The <code>multipart/byteranges</code> MIME type is used to send partial responses to
-  the browser.</p>
-
-<p>When the {{HTTPStatus("206")}}<code> Partial Content</code> status code is sent, this
-  MIME type indicates that the document is composed of several parts, one for each of the
-  requested ranges. Like other multipart types, the {{HTTPHeader("Content-Type")}} uses a
-  <code>boundary</code> to separate the pieces. Each piece has a
-  {{HTTPHeader("Content-Type")}} header with its actual type and a
-  {{HTTPHeader("Content-Range")}} of the range it represents.</p>
-
-<pre><code>HTTP/1.1 206 Partial Content
-Accept-Ranges: bytes
-Content-Type: multipart/byteranges; boundary=3d6b6a416f9b5
-Content-Length: 385
-
---3d6b6a416f9b5
-Content-Type: text/html
-Content-Range: bytes 100-200/1270
-
-eta http-equiv="Content-type" content="text/html; charset=utf-8" /&gt;
-    &lt;meta name="vieport" content
---3d6b6a416f9b5
-Content-Type: text/html
-Content-Range: bytes 300-400/1270
-
--color: #f0f0f2;
-        margin: 0;
-        padding: 0;
-        font-family: "Open Sans", "Helvetica
---3d6b6a416f9b5--</code></pre>
-
-<h2 id="Importance_of_setting_the_correct_MIME_type">Importance of setting the correct
-  MIME type</h2>
-
-<p>Most web servers send unrecognized resources as the
-  <code>application/octet-stream</code> MIME type. For security reasons, most browsers do
-  not allow setting a custom default action for such resources, forcing the user to save
-  it to disk to use it.</p>
-
-<p>Some common incorrect server configurations:</p>
-
-<ul>
-  <li>
-    <p>RAR-compressed files. In this case, the ideal would be the true type of the
-      original files; this is often impossible as .RAR files can hold several resources of
-      different types. In this case, configure the server to send
-      <code>application/x-rar-compressed</code>.</p>
-  </li>
-  <li>
-    <p>Audio and video. Only resources with the correct MIME Type will be played in
-      {{HTMLElement("video")}} or {{HTMLElement("audio")}} elements. Be sure to specify
-      the correct <a href="/en-US/docs/Web/Media/Formats">media type for audio and
-        video</a>.</p>
-  </li>
-  <li>
-    <p>Proprietary file types. Avoid using <code>application/octet-stream</code> as most
-      browsers do not allow defining a default behavior (like "Open in Word") for this
-      generic MIME type. A specific type like <code>application/vnd.mspowerpoint</code>
-      lets users open such files automatically in the presentation software of their
-      choice.</p>
-  </li>
-</ul>
-
-<h2 id="MIME_sniffing">MIME sniffing</h2>
-
-<p>In the absence of a MIME type, or in certain cases where browsers believe they are
-  incorrect, browsers may perform <em>MIME sniffing</em> — guessing the correct MIME type
-  by looking at the bytes of the resource.</p>
-
-<p>Each browser performs MIME sniffing differently and under different circumstances. (For
-  example, Safari will look at the file extension in the URL if the sent MIME type is
-  unsuitable.) There are security concerns as some MIME types represent executable
-  content. Servers can prevent MIME sniffing by sending the
-  {{HTTPHeader("X-Content-Type-Options")}} header.</p>
-
-<h2 id="Other_methods_of_conveying_document_type">Other methods of conveying document type
-</h2>
-
-<p>MIME types are not the only way to convey document type information:</p>
-
-<ul>
-  <li>Filename suffixes are sometimes used, especially on Microsoft Windows. Not all
-    operating systems consider these suffixes meaningful (such as Linux and MacOS), and
-    there is no guarantee they are correct.</li>
-  <li>Magic numbers. The syntax of different formats allows file-type inference by looking
-    at their byte structure. For example, GIF files start with the
-    <code>47 49 46 38 39</code> hexadecimal value (<code>GIF89</code>), and PNG files with
-    <code>89 50 4E 47</code> (<code>.PNG</code>). Not all file types have magic numbers,
-    so this is not 100% reliable either.</li>
-</ul>
-
-<h2 id="See_also">See also</h2>
-
-<ul>
-  <li><a href="/en-US/docs/Web/Media">Web media technologies</a></li>
-  <li><a href="/en-US/docs/Web/Media/Formats">Guide to media types used on the web</a>
-  </li>
-  <li><a
-      href="/en-US/docs/Learn/Server-side/Configuring_server_MIME_types">Properly
-      configuring server MIME types</a></li>
-</ul>
+```
+
+The following `<form>`:
+
+```html
+<form action="http://localhost:8000/" method="post" enctype="multipart/form-data">
+  <label>Name: <input name="myTextField" value="Test"></label>
+  <label><input type="checkbox" name="myCheckBox"> Check</label>
+  <label>Upload file: <input type="file" name="myFile" value="test.txt"></label>
+  <button>Send the file</button>
+</form>
+```
+
+will send this message:
+
+    POST / HTTP/1.1
+    Host: localhost:8000
+    User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:50.0) Gecko/20100101 Firefox/50.0
+    Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
+    Accept-Language: en-US,en;q=0.5
+    Accept-Encoding: gzip, deflate
+    Connection: keep-alive
+    Upgrade-Insecure-Requests: 1
+    Content-Type: multipart/form-data; boundary=---------------------------8721656041911415653955004498
+    Content-Length: 465
+
+    -----------------------------8721656041911415653955004498
+    Content-Disposition: form-data; name="myTextField"
+
+    Test
+    -----------------------------8721656041911415653955004498
+    Content-Disposition: form-data; name="myCheckBox"
+
+    on
+    -----------------------------8721656041911415653955004498
+    Content-Disposition: form-data; name="myFile"; filename="test.txt"
+    Content-Type: text/plain
+
+    Simple file.
+    -----------------------------8721656041911415653955004498--
+
+### multipart/byteranges
+
+The `multipart/byteranges` MIME type is used to send partial responses to
+the browser.
+
+When the {{HTTPStatus("206")}}` Partial Content` status code is sent, this
+MIME type indicates that the document is composed of several parts, one for each of the
+requested ranges. Like other multipart types, the {{HTTPHeader("Content-Type")}} uses a
+`boundary` to separate the pieces. Each piece has a
+{{HTTPHeader("Content-Type")}} header with its actual type and a
+{{HTTPHeader("Content-Range")}} of the range it represents.
+
+    HTTP/1.1 206 Partial Content
+    Accept-Ranges: bytes
+    Content-Type: multipart/byteranges; boundary=3d6b6a416f9b5
+    Content-Length: 385
+
+    --3d6b6a416f9b5
+    Content-Type: text/html
+    Content-Range: bytes 100-200/1270
+
+    eta http-equiv="Content-type" content="text/html; charset=utf-8" />
+        <meta name="vieport" content
+    --3d6b6a416f9b5
+    Content-Type: text/html
+    Content-Range: bytes 300-400/1270
+
+    -color: #f0f0f2;
+            margin: 0;
+            padding: 0;
+            font-family: "Open Sans", "Helvetica
+    --3d6b6a416f9b5--
+
+## Importance of setting the correct MIME type
+
+Most web servers send unrecognized resources as the
+`application/octet-stream` MIME type. For security reasons, most browsers do
+not allow setting a custom default action for such resources, forcing the user to save
+it to disk to use it.
+
+Some common incorrect server configurations:
+
+- RAR-compressed files. In this case, the ideal would be the true type of the
+  original files; this is often impossible as .RAR files can hold several resources of
+  different types. In this case, configure the server to send
+  `application/x-rar-compressed`.
+- Audio and video. Only resources with the correct MIME Type will be played in
+  {{HTMLElement("video")}} or {{HTMLElement("audio")}} elements. Be sure to specify
+  the correct [media type for audio and
+  video](/en-US/docs/Web/Media/Formats).
+- Proprietary file types. Avoid using `application/octet-stream` as most
+  browsers do not allow defining a default behavior (like "Open in Word") for this
+  generic MIME type. A specific type like `application/vnd.mspowerpoint`
+  lets users open such files automatically in the presentation software of their
+  choice.
+
+## MIME sniffing
+
+In the absence of a MIME type, or in certain cases where browsers believe they are
+incorrect, browsers may perform _MIME sniffing_ — guessing the correct MIME type
+by looking at the bytes of the resource.
+
+Each browser performs MIME sniffing differently and under different circumstances. (For
+example, Safari will look at the file extension in the URL if the sent MIME type is
+unsuitable.) There are security concerns as some MIME types represent executable
+content. Servers can prevent MIME sniffing by sending the
+{{HTTPHeader("X-Content-Type-Options")}} header.
+
+## Other methods of conveying document type
+
+MIME types are not the only way to convey document type information:
+
+- Filename suffixes are sometimes used, especially on Microsoft Windows. Not all
+  operating systems consider these suffixes meaningful (such as Linux and MacOS), and
+  there is no guarantee they are correct.
+- Magic numbers. The syntax of different formats allows file-type inference by looking
+  at their byte structure. For example, GIF files start with the
+  `47 49 46 38 39` hexadecimal value (`GIF89`), and PNG files with
+  `89 50 4E 47` (`.PNG`). Not all file types have magic numbers,
+  so this is not 100% reliable either.
+
+## See also
+
+- [Web media technologies](/en-US/docs/Web/Media)
+- [Guide to media types used on the web](/en-US/docs/Web/Media/Formats)
+- [Properly
+  configuring server MIME types](/en-US/docs/Learn/Server-side/Configuring_server_MIME_types)
diff --git a/files/en-us/web/http/basics_of_http/resource_urls/index.md b/files/en-us/web/http/basics_of_http/resource_urls/index.md
index abc045acbde5a6e..e8b23a8efd1b691 100644
--- a/files/en-us/web/http/basics_of_http/resource_urls/index.md
+++ b/files/en-us/web/http/basics_of_http/resource_urls/index.md
@@ -7,102 +7,93 @@ tags:
   - Intermediate
   - Resource
 ---
-<p>{{HTTPSidebar}}{{non-standard_header}}</p>
+{{HTTPSidebar}}{{non-standard_header}}
 
-<p>Resource URLs, URLs prefixed with the <code>resource:</code> scheme, are used by
-  Firefox and Firefox browser extensions to load resources internally, but some of the
-  information is available to sites the browser connects to as well.</p>
+Resource URLs, URLs prefixed with the `resource:` scheme, are used by
+Firefox and Firefox browser extensions to load resources internally, but some of the
+information is available to sites the browser connects to as well.
 
-<h2 id="Syntax">Syntax</h2>
+## Syntax
 
-<p>Resource URLs are composed of two parts: a prefix (<code>resource:</code>), and a URL
-  pointing to the resource you want to load:</p>
+Resource URLs are composed of two parts: a prefix (`resource:`), and a URL
+pointing to the resource you want to load:
 
-<pre class="brush: html">resource://&lt;url&gt;</pre>
+```html
+resource://<url>
+```
 
-<p>An example:</p>
+An example:
 
-<pre>resource://gre/res/svg.css</pre>
+    resource://gre/res/svg.css
 
-<p>When arrows are found in the resource URL's ('-&gt;'), it means that the first file
-  loaded the next one:</p>
+When arrows are found in the resource URL's ('->'), it means that the first file
+loaded the next one:
 
-<pre>resource://&lt;File-loader&gt; -&gt; &lt;File-loaded&gt;</pre>
+    resource://<File-loader> -> <File-loaded>
 
-<p>Please refer to <a
-    href="/en-US/docs/Web/HTTP/Basics_of_HTTP/Identifying_resources_on_the_Web">Identifying
-    resources on the web</a> for more general details.</p>
+Please refer to [Identifying
+resources on the web](/en-US/docs/Web/HTTP/Basics_of_HTTP/Identifying_resources_on_the_Web) for more general details.
 
-<p>In this article, we focus on resource URIs, which are used internally by Firefox to
-  point to built-in resources.</p>
+In this article, we focus on resource URIs, which are used internally by Firefox to
+point to built-in resources.
 
-<h2 id="Threats">Threats</h2>
+## Threats
 
-<p>Because some of the information shared by <code>resource:</code> URLs is available to
-  websites, a web page could run internal scripts and inspect internal resources of
-  Firefox, including the default preferences, which could be a serious security and
-  privacy issue.</p>
+Because some of the information shared by `resource:` URLs is available to
+websites, a web page could run internal scripts and inspect internal resources of
+Firefox, including the default preferences, which could be a serious security and
+privacy issue.
 
-<p>For example, <a href="https://www.browserleaks.com/firefox">a script on
-    Browserleaks</a> highlights what Firefox reveals when queried by a simple script
-  running on the site (you can find the code in <a
-    href="https://browserleaks.com/firefox#more">https://browserleaks.com/firefox#more</a>).
-</p>
+For example, [a script on
+Browserleaks](https://www.browserleaks.com/firefox) highlights what Firefox reveals when queried by a simple script
+running on the site (you can find the code in <https://browserleaks.com/firefox#more>).
 
-<p>The file firefox.js passes preference names and values to the pref() function. For
-  example:</p>
+The file firefox.js passes preference names and values to the pref() function. For
+example:
 
-<pre><a href="https://searchfox.org/mozilla-central/rev/48ea452803907f2575d81021e8678634e8067fc2/browser/app/profile/firefox.js#575">http://searchfox.org/mozilla-central/rev/48ea452803907f2575d81021e8678634e8067fc2/browser/app/profile/firefox.js#575</a></pre>
+    http://searchfox.org/mozilla-central/rev/48ea452803907f2575d81021e8678634e8067fc2/browser/app/profile/firefox.js#575
 
-<p>Web sites can easily collect Firefox default preferences by overriding this
-  <code>pref()</code> function and using the script
-  <code>resource:///defaults/preferences/firefox.js</code>.</p>
+Web sites can easily collect Firefox default preferences by overriding this
+`pref()` function and using the script
+`resource:///defaults/preferences/firefox.js`.
 
-<p>Furthermore, some default values of preferences differ between build configurations,
-  such as platform and locale, which means web sites could identify individual users using
-  this information.</p>
+Furthermore, some default values of preferences differ between build configurations,
+such as platform and locale, which means web sites could identify individual users using
+this information.
 
-<h2 id="Solution">Solution</h2>
+## Solution
 
-<p>In order to fix this problem, Mozilla changed the behavior of loading resource: URIs in
-  {{bug(863246)}}, which landed in <a
-    href="/en-US/docs/Mozilla/Firefox/Releases/57">Firefox 57 (Quantum)</a>.</p>
+In order to fix this problem, Mozilla changed the behavior of loading resource: URIs in
+{{bug(863246)}}, which landed in [Firefox 57 (Quantum)](/en-US/docs/Mozilla/Firefox/Releases/57).
 
-<p>In the past, web content was able to access whatever <code>resource:</code> URIs were
-  desired — not only Firefox’s internal resources, but also extensions’ assets.  Now this
-  behavior is prohibited by default.</p>
+In the past, web content was able to access whatever `resource:` URIs were
+desired — not only Firefox’s internal resources, but also extensions’ assets.  Now this
+behavior is prohibited by default.
 
-<p>It is however still necessary for Firefox to load resources in web content under
-  certain circumstances.  For example, if you open the view source page (View Page Source
-  or View Selection Source), you will find it requires <code>viewsource.css</code> through
-  a <code>resource:</code> URI.  Resources that have to be exposed to web content have
-  been moved to a new location named <code>resource://content-accessible/</code>, which is
-  isolated and only contains non-sensitive resources.  In this way we can keep essential
-  resources exposed and have most threats eliminated.</p>
+It is however still necessary for Firefox to load resources in web content under
+certain circumstances.  For example, if you open the view source page (View Page Source
+or View Selection Source), you will find it requires `viewsource.css` through
+a `resource:` URI.  Resources that have to be exposed to web content have
+been moved to a new location named `resource://content-accessible/`, which is
+isolated and only contains non-sensitive resources.  In this way we can keep essential
+resources exposed and have most threats eliminated.
 
-<div class="notecard note">
-  <p><strong>Note:</strong> It is recommended that web and extension developers don't try
-    to use resource URLs anymore. Their usage was hacky at best, and most usage won't work
-    any more.</p>
-</div>
+> **Note:** It is recommended that web and extension developers don't try
+> to use resource URLs anymore. Their usage was hacky at best, and most usage won't work
+> any more.
 
-<h2 id="Specifications">Specifications</h2>
+## Specifications
 
-<p>resource: is not defined in any specification.</p>
+resource: is not defined in any specification.
 
-<h2 id="Browser_compatibility">Browser compatibility</h2>
+## Browser compatibility
 
-<p>resource: is Firefox only.</p>
+resource: is Firefox only.
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
-  <li><a
-      href="/en-US/docs/Web/HTTP/Basics_of_HTTP/Identifying_resources_on_the_Web">Identifying
-      resources on the Web</a></li>
-  <li><a href="/en-US/docs/Learn/Common_questions/What_is_a_URL">What is a URL?</a></li>
-  <li><a href="https://www.iana.org/assignments/uri-schemes/uri-schemes.xhtml">IANA list
-      of URI schemes</a> (<code>resource:</code> is <a
-      href="https://www.iana.org/assignments/uri-schemes/prov/resource">covered here</a>)
-  </li>
-</ul>
+- [Identifying
+  resources on the Web](/en-US/docs/Web/HTTP/Basics_of_HTTP/Identifying_resources_on_the_Web)
+- [What is a URL?](/en-US/docs/Learn/Common_questions/What_is_a_URL)
+- [IANA list
+  of URI schemes](https://www.iana.org/assignments/uri-schemes/uri-schemes.xhtml) (`resource:` is [covered here](https://www.iana.org/assignments/uri-schemes/prov/resource))
diff --git a/files/en-us/web/http/browser_detection_using_the_user_agent/index.md b/files/en-us/web/http/browser_detection_using_the_user_agent/index.md
index 9854d8bcbbf42e3..3448408ecc12d59 100644
--- a/files/en-us/web/http/browser_detection_using_the_user_agent/index.md
+++ b/files/en-us/web/http/browser_detection_using_the_user_agent/index.md
@@ -6,132 +6,137 @@ tags:
   - HTTP
   - Web Development
 ---
-<div>{{HTTPSidebar}}</div>
-
-<p>Serving different Web pages or services to different browsers is usually a bad idea. The Web is meant to be accessible to everyone, regardless of which browser or device they're using. There are ways to develop your website to progressively enhance itself based on the availability of features rather than by targeting specific browsers.</p>
-
-<p>But browsers and standards are not perfect, and there are still some edge cases where detecting the browser is needed. Using the user agent to detect the browser looks simple, but doing it well is, in fact, a very hard problem. This document will guide you in doing this as correctly as possible.</p>
-
-<div class="notecard note">
-  <p><strong>Note:</strong> It's worth re-iterating: it's very rarely a good idea to use user agent sniffing. You can almost always find a better, more broadly compatible way to solve your problem!</p>
-</div>
-
-<h2 id="Considerations_before_using_browser_detection">Considerations before using browser detection</h2>
-
-<p>When considering using the user agent string to detect which browser is being used, your first step is to try to avoid it if possible. Start by trying to identify <strong>why</strong> you want to do it.</p>
-
-<dl>
-	<dt>Are you trying to work around a specific bug in some version of a browser?</dt>
-	<dd>Look, or ask, in specialized forums: you're unlikely to be the first to hit this problem. Also, experts, or people with another point of view, can give you ideas for working around the bug. If the problem seems uncommon, it's worth checking if this bug has been reported to the browser vendor via their bug tracking system (<a class="link-https" href="https://bugzilla.mozilla.org">Mozilla</a>; <a href="https://bugs.webkit.org">WebKit</a>; <a href="https://www.chromium.org/issue-tracking">Blink</a>; <a class="link-https" href="https://bugs.opera.com/">Opera</a>). Browser makers do pay attention to bug reports, and the analysis may hint about other workarounds for the bug.</dd>
-	<dt>Are you trying to check for the existence of a specific feature?</dt>
-	<dd>Your site needs to use a specific Web feature that some browsers don't yet support, and you want to send those users to an older Web site with fewer features but that you know will work. This is the worst reason to use user agent detection because odds are eventually all the other browsers will catch up. In addition, it is not practical to test every one of the less popular browsers and test for those Web features. You should <strong>never</strong> do user agent sniffing. There is <strong>always</strong> the alternative of doing feature detection instead.</dd>
-	<dt>Do you want to provide different HTML depending on which browser is being used?</dt>
-	<dd>This is usually a bad practice, but there are some cases in which this is necessary. In these cases, you should first analyze your situation to be sure it's really necessary. Can you prevent it by adding some non-semantic {{ HTMLElement("div") }} or {{ HTMLElement("span") }} elements? The difficulty of successfully using user agent detection is worth a few disruptions to the purity of your HTML. Also, rethink your design: can you use progressive enhancement or fluid layouts to help remove the need to do this?</dd>
-</dl>
-
-<h2 id="Avoiding_user_agent_detection">Avoiding user agent detection</h2>
-
-<p>If you want to avoid using user agent detection, you have options!</p>
-
-<dl>
-	<dt>Feature detection</dt>
-	<dd>Feature detection is where you don't try to figure out which browser is rendering your page, but instead, you check to see if the specific feature you need is available. If it's not, you use a fallback. In those rare cases where behavior differs between browsers, instead of checking the user agent string, you should instead implement a test to detect how the browser implements the API and determine how to use it from that. An example of feature detection is as follows. In 2017, Chrome <a href="https://www.chromestatus.com/feature/5668726032564224">unflagged experimental lookbehind support in regular expressions</a>, but no other browser supported it. So, you might have thought to do this:
-	<pre class="brush: js">// this code snippet splits a string in a special notation
-
-if (navigator.userAgent.indexOf("Chrome") !== -1){
-    // YES! The user is suspected to support look-behind regexps
-    // DO NOT USE /(?&lt;=[A-Z])/. It will cause a syntax error in
-    //  browsers that do not support look-behind expressions
-    //  because all browsers parse the entire script, including
-    //  sections of the code that are never executed.
-    var camelCaseExpression = new RegExp("(?&lt;=[A-Z])");
-    var splitUpString = function(str) {
-        return (""+str).split(camelCaseExpression);
-    };
-} else {
-    /*This fallback code is much less performant, but works*/
-    var splitUpString = function(str){
-        return str.replace(/[A-Z]/g,"z$1").split(/z(?=[A-Z])/g);
-    };
-}
-console.log(splitUpString("fooBare")); // ["fooB", "are"]
-console.log(splitUpString("jQWhy")); // ["jQ", "W", "hy"]</pre>
-
-	<p>
+{{HTTPSidebar}}
+
+Serving different Web pages or services to different browsers is usually a bad idea. The Web is meant to be accessible to everyone, regardless of which browser or device they're using. There are ways to develop your website to progressively enhance itself based on the availability of features rather than by targeting specific browsers.
+
+But browsers and standards are not perfect, and there are still some edge cases where detecting the browser is needed. Using the user agent to detect the browser looks simple, but doing it well is, in fact, a very hard problem. This document will guide you in doing this as correctly as possible.
+
+> **Note:** It's worth re-iterating: it's very rarely a good idea to use user agent sniffing. You can almost always find a better, more broadly compatible way to solve your problem!
+
+## Considerations before using browser detection
+
+When considering using the user agent string to detect which browser is being used, your first step is to try to avoid it if possible. Start by trying to identify **why** you want to do it.
+
+- Are you trying to work around a specific bug in some version of a browser?
+  - : Look, or ask, in specialized forums: you're unlikely to be the first to hit this problem. Also, experts, or people with another point of view, can give you ideas for working around the bug. If the problem seems uncommon, it's worth checking if this bug has been reported to the browser vendor via their bug tracking system ([Mozilla](https://bugzilla.mozilla.org); [WebKit](https://bugs.webkit.org); [Blink](https://www.chromium.org/issue-tracking); [Opera](https://bugs.opera.com/)). Browser makers do pay attention to bug reports, and the analysis may hint about other workarounds for the bug.
+- Are you trying to check for the existence of a specific feature?
+  - : Your site needs to use a specific Web feature that some browsers don't yet support, and you want to send those users to an older Web site with fewer features but that you know will work. This is the worst reason to use user agent detection because odds are eventually all the other browsers will catch up. In addition, it is not practical to test every one of the less popular browsers and test for those Web features. You should **never** do user agent sniffing. There is **always** the alternative of doing feature detection instead.
+- Do you want to provide different HTML depending on which browser is being used?
+  - : This is usually a bad practice, but there are some cases in which this is necessary. In these cases, you should first analyze your situation to be sure it's really necessary. Can you prevent it by adding some non-semantic {{ HTMLElement("div") }} or {{ HTMLElement("span") }} elements? The difficulty of successfully using user agent detection is worth a few disruptions to the purity of your HTML. Also, rethink your design: can you use progressive enhancement or fluid layouts to help remove the need to do this?
+
+## Avoiding user agent detection
+
+If you want to avoid using user agent detection, you have options!
+
+- Feature detection
+
+  - : Feature detection is where you don't try to figure out which browser is rendering your page, but instead, you check to see if the specific feature you need is available. If it's not, you use a fallback. In those rare cases where behavior differs between browsers, instead of checking the user agent string, you should instead implement a test to detect how the browser implements the API and determine how to use it from that. An example of feature detection is as follows. In 2017, Chrome [unflagged experimental lookbehind support in regular expressions](https://www.chromestatus.com/feature/5668726032564224), but no other browser supported it. So, you might have thought to do this:
+
+    ```js
+        // this code snippet splits a string in a special notation
+
+        if (navigator.userAgent.indexOf("Chrome") !== -1){
+            // YES! The user is suspected to support look-behind regexps
+            // DO NOT USE /(?<=[A-Z])/. It will cause a syntax error in
+            //  browsers that do not support look-behind expressions
+            //  because all browsers parse the entire script, including
+            //  sections of the code that are never executed.
+            var camelCaseExpression = new RegExp("(?<=[A-Z])");
+            var splitUpString = function(str) {
+                return (""+str).split(camelCaseExpression);
+            };
+        } else {
+            /*This fallback code is much less performant, but works*/
+            var splitUpString = function(str){
+                return str.replace(/[A-Z]/g,"z$1").split(/z(?=[A-Z])/g);
+            };
+        }
+        console.log(splitUpString("fooBare")); // ["fooB", "are"]
+        console.log(splitUpString("jQWhy")); // ["jQ", "W", "hy"]
+        ```
+
     The above code would have made several incorrect assumptions:
     First, it assumed that all user agent strings that include the substring "Chrome" are Chrome. UA strings are notoriously misleading.
     Then, it assumed that the lookbehind feature would always be available if the browser was Chrome. The agent might be an older version of Chrome, from before support was added, or (because the feature was experimental at the time) it could be a later version of Chrome that removed it.
     Most importantly, it assumed no other browsers would support the feature. Support could have been added to other browsers at any time, but this code would have continued choosing the inferior path.
-  </p>
-
-	<p>Problems like these can be avoided by testing for support of the feature itself instead:</p>
-
-	<pre class="brush: js">var isLookBehindSupported = false;
-
-try {
-    new RegExp("(?&lt;=)");
-    isLookBehindSupported = true;
-} catch (err) {
-    // If the agent doesn't support lookbehinds, the attempted
-    // creation of a RegExp object using that syntax throws and
-    // isLookBehindSupported remains false.
-}
-
-var splitUpString = isLookBehindSupported ? function(str) {
-    return (""+str).split(new RegExp("(?&lt;=[A-Z])"));
-} : function(str) {
-    return str.replace(/[A-Z]/g,"z$1").split(/z(?=[A-Z])/g);
-};
-</pre>
-
-	<p>As the above code demonstrates, there is <strong>always</strong> a way to test browser support without user agent sniffing. There is <strong>never</strong> any reason to check the user agent string for this.</p>
-
-	<p>Lastly, the above code snippets bring about a critical issue with cross-browser coding that must always be taken into account. Don't unintentionally use the API you are testing for in unsupported browsers. This may sound obvious and simple, but sometimes it is not. For example, in the above code snippets, using lookbehind in short-regexp notation (e.g. /reg/igm) will cause a parser error in unsupported browsers. Thus, in the above example, you would use <em>new RegExp("(?&lt;=look_behind_stuff)");</em> instead of <em>/(?&lt;=look_behind_stuff)/</em>, even in the lookbehind supported section of your code.</p>
-	</dd>
-	<dt>Progressive enhancement</dt>
-	<dd>This design technique involves developing your Web site in 'layers', using a bottom-up approach, starting with a simpler layer and improving the capabilities of the site in successive layers, each using more features.</dd>
-	<dt>Graceful degradation</dt>
-	<dd>This is a top-down approach in which you build the best possible site using all the features you want, then tweak it to make it work on older browsers. This can be harder to do, and less effective, than progressive enhancement, but may be useful in some cases.</dd>
-	<dt id="mobile_device_detection">Mobile device detection</dt>
-	<dd>Arguably the most common use and misuse of user agent sniffing is to detect if the device is a mobile device. However, people too often overlook what they are really after. People use user agent sniffing to detect if the users' device is touch-friendly and has a small screen so they can optimize their website accordingly. While user agent sniffing can sometimes detect these, not all devices are the same: some mobile devices have big screen sizes, some desktops have a small touchscreen, some people use smart TV's which are an entirely different ballgame altogether, and some people can dynamically change the width and height of their screen by flipping their tablet on its side! So, user agent sniffing is definitely not the way to go. Thankfully, there are much better alternatives. Use <a href="/en-US/docs/Web/API/Navigator/maxTouchPoints">Navigator.maxTouchPoints</a> to detect if the user's device has a touchscreen. Then, default back to checking the user agent screen only <em>if (!("maxTouchPoints" in navigator)) { /*Code here*/}</em>. Using this information of whether the device has a touchscreen, do not change the entire layout of the website just for touch devices: you will only create more work and maintenance for yourself. Rather, add in touch conveniences such as bigger, more easily clickable buttons (you can do this using CSS by increasing the font size). Here is an example of code that increases the padding of #exampleButton to 1em on mobile devices.
-	<pre class="brush: js">var hasTouchScreen = false;
-if ("maxTouchPoints" in navigator) {
-    hasTouchScreen = navigator.maxTouchPoints &gt; 0;
-} else if ("msMaxTouchPoints" in navigator) {
-    hasTouchScreen = navigator.msMaxTouchPoints &gt; 0;
-} else {
-    var mQ = window.matchMedia &amp;&amp; matchMedia("(pointer:coarse)");
-    if (mQ &amp;&amp; mQ.media === "(pointer:coarse)") {
-        hasTouchScreen = !!mQ.matches;
-    } else if ('orientation' in window) {
-        hasTouchScreen = true; // deprecated, but good fallback
-    } else {
-        // Only as a last resort, fall back to user agent sniffing
-        var UA = navigator.userAgent;
-        hasTouchScreen = (
-            /\b(BlackBerry|webOS|iPhone|IEMobile)\b/i.test(UA) ||
-            /\b(Android|Windows Phone|iPad|iPod)\b/i.test(UA)
-        );
-    }
-}
-if (hasTouchScreen)
-    document.getElementById("exampleButton").style.padding="1em";</pre>
-	<p>As for the screen size, use <em>window.innerWidth</em> and window.addEventListener("resize", function(){ /*refresh screen size dependent things*/ }). What you want to do for screen size is not slash off information on smaller screens. That will only annoy people because it will force them to use the desktop version. Rather, try to have fewer columns of information in a longer page on smaller screens while having more columns with a shorter page on larger screen sizes. This effect can be easily achieved using CSS <a href="/en-US/docs/Learn/CSS/CSS_layout/Flexbox">flexboxes</a>, sometimes with <a href="/en-US/docs/Learn/CSS/CSS_layout/Floats">floats</a> as a partial fallback.</p>
-	<p>Also try to move less relevant/important information down to the bottom and group the page's content together meaningfully. Although it is off-topic, perhaps the following detailed example might give you insights and ideas that persuade you to forgo user agent sniffing. Let us imagine a page composed of boxes of information; each box is about a different feline breed or canine breed. Each box has an image, an overview, and a historical funfact. The pictures are kept to a maximum reasonable size even on large screens. For the purposes of grouping the content meaningfully, all the cat boxes are separated from all the dog boxes such that the cat and dog boxes are not intermixed together. On a large screen, it saves space to have multiple columns to reduce the space wasted to the left and to the right of the pictures. The boxes can be separated into multiple columns via two equally fair method. From this point on, we shall assume that all the dog boxes are at the top of the source code, that all the cat boxes are at the bottom of the source code, and that all these boxes have the same parent element. There a single instance of a dog box immediately above a cat box, of course. The first method uses horizontal <a href="/en-US/docs/Learn/CSS/CSS_layout/Flexbox">Flexboxes</a> to group the content such that when the page is displayed to the end user, all the dogs boxes are at the top of the page and all the cat boxes are lower on the page. The second method uses a <a href="/en-US/docs/Web/CSS/Layout_cookbook/Column_layouts">Column</a> layout and resents all the dogs to the left and all the cats to the right. Only in this particular scenario, it is appropriate to provide no fallback for the flexboxes/multicolumns, resulting in a single column of very wide boxes on old browsers. Also consider the following. If more people visit the webpage to see the cats, then it might be a good idea to put all the cats higher in the source code than the dogs so that more people can find what they are looking for faster on smaller screens where the content collapses down to one column.</p>
-	<p>Next, always make your code dynamic. The user can flip their mobile device on its side, changing the width and height of the page. Or, there might be some weird flip-phone-like device thing in the future where flipping it out extends the screen. Do not be the developer having a headache over how to deal with the flip-phone-like device thing. Never be satisfied with your webpage until you can open up the dev tools side panel and resize the screen while the webpage looks smooth, fluid, and dynamically resized. The simplest way to do this is to separate all the code that moves content around based on screen size to a single function that is called when the page is loaded and at each <a href="/en-US/docs/Web/API/Window/resize_event">resize</a> event thereafter. If there is a lot calculated by this layout function before it determines the new layout of the page, then consider debouncing the event listener such that it is not called as often. Also note that there is a huge difference between the media queries <code>(max-width: 25em)</code>, <code>not all and (min-width: 25em)</code>, and <code>(max-width: 24.99em)</code>: <code>(max-width: 25em)</code> excludes <code>(max-width: 25em)</code>, whereas <code>not all and (min-width: 25em)</code> includes <code>(max-width: 25em)</code>. <code>(max-width: 24.99em)</code> is a poor man's version of <code>not all and (min-width: 25em)</code>: do not use <code>(max-width: 24.99em)</code> because the layout <em>might</em> break on very high font sizes on very high definition devices in the future. Always be very deliberate about choosing the right media query and choosing the right &gt;=, &lt;=, &gt;, or &lt; in any corresponding JavaScript because it is very easy to get these mixed up, resulting in the website looking wonking right at the screen size where the layout changes. Thus, thoroughly test the website at the exact widths/heights where layout changes occur to ensure that the layout changes occur properly.</p>
-  </dd>
-</dl>
-
-<h2 id="Making_the_best_of_user_agent_sniffing">Making the best of user agent sniffing</h2>
-
-<p>After reviewing all of the above better alternatives to user agent sniffing, there are still some potential cases where user agent sniffing is appropriate and justified.</p>
-
-<p>One such case is using user agent sniffing as a fallback when detecting if the device has a touch screen. See the <a href="#mobile_device_detection">Mobile Device Detection</a> section for more information.</p>
-
-<p>Another such case is for fixing bugs in browsers that do not automatically update. Internet Explorer (on Windows) and Webkit (on iOS) are two perfect examples. Prior to version 9, Internet Explorer had issues with rendering bugs, CSS bugs, API bugs, and so forth. However, prior to version 9, Internet Explorer was was very easy to detect based upon the browser-specific features available. Webkit is a bit worse because Apple forces all of the browsers on IOS to use Webkit internally, thus the user has no way to get a better more updated browser on older devices. Most bugs can be detected, but some bugs take more effort to detect than others. In such cases, it might be beneficial to use user agent sniffing to save on performance. For example, Webkit 6 has a bug whereby when the device orientation changes, the browser might not fire <a href="/en-US/docs/Web/API/MediaQueryList">MediaQueryList</a> listeners when it should. To overcome this bug, observe the code below.</p>
-
-<pre class="brush: js">var UA=navigator.userAgent, isWebkit=/\b(iPad|iPhone|iPod)\b/.test(UA) &amp;&amp;
-               /WebKit/.test(UA) &amp;&amp; !/Edge/.test(UA) &amp;&amp; !window.MSStream;
+
+    Problems like these can be avoided by testing for support of the feature itself instead:
+
+    <!-- prettier-ignore -->
+    ```js
+        var isLookBehindSupported = false;
+
+        try {
+            new RegExp("(?<=)");
+            isLookBehindSupported = true;
+        } catch (err) {
+            // If the agent doesn't support lookbehinds, the attempted
+            // creation of a RegExp object using that syntax throws and
+            // isLookBehindSupported remains false.
+        }
+
+        var splitUpString = isLookBehindSupported ? function(str) {
+            return (""+str).split(new RegExp("(?<=[A-Z])"));
+        } : function(str) {
+            return str.replace(/[A-Z]/g,"z$1").split(/z(?=[A-Z])/g);
+        };
+        ```
+
+    As the above code demonstrates, there is **always** a way to test browser support without user agent sniffing. There is **never** any reason to check the user agent string for this.
+
+    Lastly, the above code snippets bring about a critical issue with cross-browser coding that must always be taken into account. Don't unintentionally use the API you are testing for in unsupported browsers. This may sound obvious and simple, but sometimes it is not. For example, in the above code snippets, using lookbehind in short-regexp notation (e.g. /reg/igm) will cause a parser error in unsupported browsers. Thus, in the above example, you would use _new RegExp("(?<=look_behind_stuff)");_ instead of _/(?<=look_behind_stuff)/_, even in the lookbehind supported section of your code.
+
+- Progressive enhancement
+  - : This design technique involves developing your Web site in 'layers', using a bottom-up approach, starting with a simpler layer and improving the capabilities of the site in successive layers, each using more features.
+- Graceful degradation
+  - : This is a top-down approach in which you build the best possible site using all the features you want, then tweak it to make it work on older browsers. This can be harder to do, and less effective, than progressive enhancement, but may be useful in some cases.
+- Mobile device detection
+
+  - : Arguably the most common use and misuse of user agent sniffing is to detect if the device is a mobile device. However, people too often overlook what they are really after. People use user agent sniffing to detect if the users' device is touch-friendly and has a small screen so they can optimize their website accordingly. While user agent sniffing can sometimes detect these, not all devices are the same: some mobile devices have big screen sizes, some desktops have a small touchscreen, some people use smart TV's which are an entirely different ballgame altogether, and some people can dynamically change the width and height of their screen by flipping their tablet on its side! So, user agent sniffing is definitely not the way to go. Thankfully, there are much better alternatives. Use [Navigator.maxTouchPoints](/en-US/docs/Web/API/Navigator/maxTouchPoints) to detect if the user's device has a touchscreen. Then, default back to checking the user agent screen only _if (!("maxTouchPoints" in navigator)) { /\*Code here\*/}_. Using this information of whether the device has a touchscreen, do not change the entire layout of the website just for touch devices: you will only create more work and maintenance for yourself. Rather, add in touch conveniences such as bigger, more easily clickable buttons (you can do this using CSS by increasing the font size). Here is an example of code that increases the padding of #exampleButton to 1em on mobile devices.
+
+    ```js
+        var hasTouchScreen = false;
+        if ("maxTouchPoints" in navigator) {
+            hasTouchScreen = navigator.maxTouchPoints > 0;
+        } else if ("msMaxTouchPoints" in navigator) {
+            hasTouchScreen = navigator.msMaxTouchPoints > 0;
+        } else {
+            var mQ = window.matchMedia && matchMedia("(pointer:coarse)");
+            if (mQ && mQ.media === "(pointer:coarse)") {
+                hasTouchScreen = !!mQ.matches;
+            } else if ('orientation' in window) {
+                hasTouchScreen = true; // deprecated, but good fallback
+            } else {
+                // Only as a last resort, fall back to user agent sniffing
+                var UA = navigator.userAgent;
+                hasTouchScreen = (
+                    /\b(BlackBerry|webOS|iPhone|IEMobile)\b/i.test(UA) ||
+                    /\b(Android|Windows Phone|iPad|iPod)\b/i.test(UA)
+                );
+            }
+        }
+        if (hasTouchScreen)
+            document.getElementById("exampleButton").style.padding="1em";
+        ```
+
+    As for the screen size, use _window\.innerWidth_ and window\.addEventListener("resize", function(){ /\*refresh screen size dependent things\*/ }). What you want to do for screen size is not slash off information on smaller screens. That will only annoy people because it will force them to use the desktop version. Rather, try to have fewer columns of information in a longer page on smaller screens while having more columns with a shorter page on larger screen sizes. This effect can be easily achieved using CSS [flexboxes](/en-US/docs/Learn/CSS/CSS_layout/Flexbox), sometimes with [floats](/en-US/docs/Learn/CSS/CSS_layout/Floats) as a partial fallback.
+
+    Also try to move less relevant/important information down to the bottom and group the page's content together meaningfully. Although it is off-topic, perhaps the following detailed example might give you insights and ideas that persuade you to forgo user agent sniffing. Let us imagine a page composed of boxes of information; each box is about a different feline breed or canine breed. Each box has an image, an overview, and a historical funfact. The pictures are kept to a maximum reasonable size even on large screens. For the purposes of grouping the content meaningfully, all the cat boxes are separated from all the dog boxes such that the cat and dog boxes are not intermixed together. On a large screen, it saves space to have multiple columns to reduce the space wasted to the left and to the right of the pictures. The boxes can be separated into multiple columns via two equally fair method. From this point on, we shall assume that all the dog boxes are at the top of the source code, that all the cat boxes are at the bottom of the source code, and that all these boxes have the same parent element. There a single instance of a dog box immediately above a cat box, of course. The first method uses horizontal [Flexboxes](/en-US/docs/Learn/CSS/CSS_layout/Flexbox) to group the content such that when the page is displayed to the end user, all the dogs boxes are at the top of the page and all the cat boxes are lower on the page. The second method uses a [Column](/en-US/docs/Web/CSS/Layout_cookbook/Column_layouts) layout and resents all the dogs to the left and all the cats to the right. Only in this particular scenario, it is appropriate to provide no fallback for the flexboxes/multicolumns, resulting in a single column of very wide boxes on old browsers. Also consider the following. If more people visit the webpage to see the cats, then it might be a good idea to put all the cats higher in the source code than the dogs so that more people can find what they are looking for faster on smaller screens where the content collapses down to one column.
+
+    Next, always make your code dynamic. The user can flip their mobile device on its side, changing the width and height of the page. Or, there might be some weird flip-phone-like device thing in the future where flipping it out extends the screen. Do not be the developer having a headache over how to deal with the flip-phone-like device thing. Never be satisfied with your webpage until you can open up the dev tools side panel and resize the screen while the webpage looks smooth, fluid, and dynamically resized. The simplest way to do this is to separate all the code that moves content around based on screen size to a single function that is called when the page is loaded and at each [resize](/en-US/docs/Web/API/Window/resize_event) event thereafter. If there is a lot calculated by this layout function before it determines the new layout of the page, then consider debouncing the event listener such that it is not called as often. Also note that there is a huge difference between the media queries `(max-width: 25em)`, `not all and (min-width: 25em)`, and `(max-width: 24.99em)`: `(max-width: 25em)` excludes `(max-width: 25em)`, whereas `not all and (min-width: 25em)` includes `(max-width: 25em)`. `(max-width: 24.99em)` is a poor man's version of `not all and (min-width: 25em)`: do not use `(max-width: 24.99em)` because the layout _might_ break on very high font sizes on very high definition devices in the future. Always be very deliberate about choosing the right media query and choosing the right >=, <=, >, or < in any corresponding JavaScript because it is very easy to get these mixed up, resulting in the website looking wonking right at the screen size where the layout changes. Thus, thoroughly test the website at the exact widths/heights where layout changes occur to ensure that the layout changes occur properly.
+
+## Making the best of user agent sniffing
+
+After reviewing all of the above better alternatives to user agent sniffing, there are still some potential cases where user agent sniffing is appropriate and justified.
+
+One such case is using user agent sniffing as a fallback when detecting if the device has a touch screen. See the [Mobile Device Detection](#mobile_device_detection) section for more information.
+
+Another such case is for fixing bugs in browsers that do not automatically update. Internet Explorer (on Windows) and Webkit (on iOS) are two perfect examples. Prior to version 9, Internet Explorer had issues with rendering bugs, CSS bugs, API bugs, and so forth. However, prior to version 9, Internet Explorer was was very easy to detect based upon the browser-specific features available. Webkit is a bit worse because Apple forces all of the browsers on IOS to use Webkit internally, thus the user has no way to get a better more updated browser on older devices. Most bugs can be detected, but some bugs take more effort to detect than others. In such cases, it might be beneficial to use user agent sniffing to save on performance. For example, Webkit 6 has a bug whereby when the device orientation changes, the browser might not fire [MediaQueryList](/en-US/docs/Web/API/MediaQueryList) listeners when it should. To overcome this bug, observe the code below.
+
+```js
+var UA=navigator.userAgent, isWebkit=/\b(iPad|iPhone|iPod)\b/.test(UA) &&
+               /WebKit/.test(UA) && !/Edge/.test(UA) && !window.MSStream;
 
 var mediaQueryUpdated = true, mqL = [];
 function whenMediaChanges(){mediaQueryUpdated = true}
@@ -141,7 +146,7 @@ var listenToMediaQuery = isWebkit ? function(mQ, f) {
     mQ.addListener(f), mQ.addListener(whenMediaChanges);
 } : function(){};
 var destroyMediaQuery = isWebkit ? function(mQ) {
-    for (var i=0,len=mqL.length|0; i&lt;len; i=i+1|0)
+    for (var i=0,len=mqL.length|0; i<len; i=i+1|0)
         if (mqL[i][0] === mQ) mqL.splice(i, 1);
     mQ.removeListener(whenMediaChanges);
 } : listenToMediaQuery;
@@ -152,204 +157,90 @@ addEventListener("orientationchange", function(){
 }, PASSIVE_LISTENER_OPTION);
 
 addEventListener("resize", setTimeout.bind(0,function(){
-    if (orientationChanged &amp;&amp; !mediaQueryUpdated)
-        for (var i=0,len=mqL.length|0; i&lt;len; i=i+1|0)
+    if (orientationChanged && !mediaQueryUpdated)
+        for (var i=0,len=mqL.length|0; i<len; i=i+1|0)
             mqL[i][1]( mqL[i][0] );
     mediaQueryUpdated = orientationChanged = false;
-},0));</pre>
-
-<h2 id="Which_part_of_the_user_agent_contains_the_information_you_are_looking_for">Which part of the user agent contains the information you are looking for?</h2>
-
-<p>As there is no uniformity of the different part of the user agent string, this is the tricky part.</p>
-
-<h3 id="Browser_Name">Browser Name</h3>
-
-<p>When people say they want "browser detection", often they actually want "rendering engine detection". Do you actually want to detect Firefox, as opposed to SeaMonkey, or Chrome as opposed to Chromium? Or do you actually want to see if the browser is using the Gecko or the WebKit rendering engine? If this is what you need, see further down the page.</p>
-
-<p>Most browsers set the name and version in the format <em>BrowserName/VersionNumber</em>, with the notable exception of Internet Explorer. But as the name is not the only information in a user agent string that is in that format, you can not discover the name of the browser, you can only check if the name you are looking for. But note that some browsers are lying: Chrome for example reports both as Chrome and Safari. So to detect Safari you have to check for the Safari string and the absence of the Chrome string, Chromium often reports itself as Chrome too or Seamonkey sometimes reports itself as Firefox.</p>
-
-<p>Also, pay attention not to use a simple regular expression on the BrowserName, user agents also contain strings outside the Keyword/Value syntax. Safari &amp; Chrome contain the string 'like Gecko', for instance.</p>
-
-<table>
-	<thead>
-		<tr>
-			<th>Engine</th>
-			<th>Must contain</th>
-			<th>Must not contain</th>
-		</tr>
-	</thead>
-	<tbody>
-		<tr>
-			<td>Firefox</td>
-			<td><code>Firefox/xyz</code></td>
-			<td><code>Seamonkey/xyz</code></td>
-		</tr>
-		<tr>
-			<td>Seamonkey</td>
-			<td><code>Seamonkey/xyz</code></td>
-      <td></td>
-		</tr>
-		<tr>
-			<td>Chrome</td>
-			<td><code>Chrome/xyz</code></td>
-			<td><code>Chromium/xyz</code></td>
-		</tr>
-		<tr>
-			<td>Chromium</td>
-			<td><code>Chromium/xyz</code></td>
-			<td></td>
-		</tr>
-		<tr>
-			<td>Safari</td>
-			<td><code>Safari/xyz</code></td>
-			<td><code>Chrome/xyz</code> or <code>Chromium/xyz</code></td>
-		</tr>
-		<tr>
-			<td>Opera 15+ (Blink-based engine)</td>
-      <td><code>OPR/xyz</code></td>
-      <td></td>
-    </tr>
-    <tr>
-      <td>Opera 12- (Presto-based engine)</td>
-      <td><code>Opera/xyz</code></td>
-      <td></td>
-		</tr>
-		<tr>
-			<td>Internet Explorer 10-</td>
-			<td><code>; MSIE xyz;</code></td>
-      <td></td>
-    <tr>
-      <td>Internet Explorer 11</td>
-      <td><code>Trident/7.0; .*rv:xyz</code></td>
-      <td></td>
-		</tr>
-	</tbody>
-</table>
-
-<p>[1] Safari gives two version numbers: one technical in the <code>Safari/xyz</code> token, and one user-friendly in a <code>Version/xyz</code> token.</p>
-
-<p>Of course, there is absolutely no guarantee that another browser will not hijack some of these things (like Chrome hijacked the Safari string in the past). That's why browser detection using the user agent string is unreliable and should be done only with the check of the version number (hijacking of past versions is less likely).</p>
-
-<h3 id="Browser_version">Browser version</h3>
-
-<p>The browser version is often, but not always, put in the value part of the <em>BrowserName/VersionNumber</em> token in the User Agent String. This is of course not the case for Internet Explorer (which puts the version number right after the MSIE token), and for Opera after version 10, which has added a Version/<em>VersionNumber</em> token.</p>
-
-<p>Here again, be sure to take the right token for the browser you are looking for, as there is no guarantee that others will contain a valid number.</p>
-
-<h3 id="Rendering_engine">Rendering engine</h3>
-
-<p>As seen earlier, in most cases, looking for the rendering engine is a better way to go. This will help to not exclude lesser known browsers. Browsers sharing a common rendering engine will display a page in the same way: it is often a fair assumption that what will work in one will work in the other.</p>
-
-<p>There are five major rendering engines: Trident, Gecko, Presto, Blink, and WebKit. As sniffing the rendering engines names is common, a lot of user agents added other rendering names to trigger detection. It is therefore important to pay attention not to trigger false-positives when detecting the rendering engine.</p>
-
-<table>
-	<thead>
-		<tr>
-			<th>Engine</th>
-			<th>Must contain</th>
-			<th>Comment</th>
-		</tr>
-	</thead>
-	<tbody>
-		<tr>
-			<td>Gecko</td>
-			<td><code>Gecko/xyz</code></td>
-			<td></td>
-		</tr>
-		<tr>
-			<td>WebKit</td>
-			<td><code>AppleWebKit/xyz</code></td>
-			<td>Pay attention, WebKit browsers add a 'like Gecko' string that may trigger false positive for Gecko if the detection is not careful.</td>
-		</tr>
-		<tr>
-			<td>Presto</td>
-			<td><code>Opera/xyz</code></td>
-			<td><strong>Note:</strong> Presto is no longer used in Opera browser builds &gt;= version 15 (see 'Blink')</td>
-		</tr>
-		<tr>
-			<td>Trident</td>
-			<td><code>Trident/xyz</code></td>
-			<td>Internet Explorer put this token in the <em>comment</em> part of the User Agent String</td>
-		</tr>
-		<tr>
-			<td>EdgeHTML</td>
-			<td><code>Edge/xyz</code></td>
-			<td>The non-Chromium Edge puts its engine version after the <em>Edge/</em> token, not the application version.<br>
-			<strong>Note:</strong> EdgeHTML is no longer used in Edge browser builds &gt;= version 79 (see 'Blink').</td>
-		</tr>
-		<tr>
-			<td>Blink</td>
-			<td><code>Chrome/xyz</code></td>
-			<td></td>
-		</tr>
-	</tbody>
-</table>
-
-<h2 id="Rendering_engine_version">Rendering engine version</h2>
-
-<p>Most rendering engines put the version number in the <em>RenderingEngine/VersionNumber</em> token, with the notable exception of Gecko. Gecko puts the Gecko version number in the comment part of the User Agent after the <code>rv:</code> string. From Gecko 14 for the mobile version and Gecko 17 for the desktop version, it also puts this value in the <code>Gecko/version</code> token (previous version put there the build date, then a fixed date called the GeckoTrail).</p>
-
-<h2 id="OS">OS</h2>
-
-<p>The Operating System is given in most User Agent strings (although not web-focused platforms like Firefox OS), but the format varies a lot. It is a fixed string between two semi-colons, in the comment part of the User Agent. These strings are specific for each browser. They indicate the OS, but also often its version and information on the relying hardware (32 or 64 bits, or Intel/PPC for Mac).</p>
-
-<p>Like in all cases, these strings may change in the future, one should use them only in conjunction with the detection of already released browsers. A technological survey must be in place to adapt the script when new browser versions are coming out.</p>
-
-<h3 id="Mobile_Tablet_or_Desktop">Mobile, Tablet or Desktop</h3>
-
-<p>The most common reason to perform user agent sniffing is to determine which type of device the browser runs on. The goal is to serve different HTML to different device types.</p>
-
-<ul>
-	<li>Never assume that a browser or a rendering engine only runs on one type of device. Especially don't make different defaults for different browsers or rendering engines.</li>
-	<li>Never use the OS token to define if a browser is on mobile, tablet or desktop. The OS may run on more than one type of (for example, Android runs on tablets as well as phones).</li>
-</ul>
-
-<p>The following table summarizes the way common browser vendors indicate that their browsers are running on a mobile device:</p>
-
-<table>
-	<thead>
-		<tr>
-			<th>Browser</th>
-			<th>Rule</th>
-			<th>Example</th>
-		</tr>
-	</thead>
-	<tbody>
-		<tr>
-			<td>Mozilla (Gecko, Firefox)</td>
-			<td><code>Mobile</code> or <code>Tablet</code> inside the comment.</td>
-			<td><code>Mozilla/5.0 (Android; Mobile; rv:13.0) Gecko/13.0 Firefox/13.0</code></td>
-		</tr>
-		<tr>
-			<td>WebKit-based (Android, Safari)</td>
-			<td><code>Mobile Safari</code> token <a href="https://developer.apple.com/library/safari/documentation/AppleApplications/Reference/SafariWebContent/OptimizingforSafarioniPhone/OptimizingforSafarioniPhone.html#//apple_ref/doc/uid/TP40006517-SW3">outside</a> the comment.</td>
-			<td><code>Mozilla/5.0 (Linux; U; Android 4.0.3; de-ch; HTC Sensation Build/IML74K) AppleWebKit/534.30 (KHTML, like Gecko) Version/4.0 Mobile Safari/534.30</code></td>
-		</tr>
-		<tr>
-			<td>Blink-based (Chromium, Google Chrome, Opera 15+, Edge on Android)</td>
-			<td><code>Mobile Safari</code> token <a href="https://developers.google.com/chrome/mobile/docs/user-agent">outside</a> the comment.</td>
-			<td><code>Mozilla/5.0 (Linux; Android 4.4.2); Nexus 5 Build/KOT49H) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/33.0.1750.117 Mobile Safari/537.36 OPR/20.0.1396.72047</code></td>
-		</tr>
-		<tr>
-			<td>Presto-based (Opera 12-)</td>
-			<td><code>Opera Mobi/xyz</code> token <a href="https://my.opera.com/community/openweb/idopera/">inside</a> the comment.</td>
-			<td><code>Opera/9.80 (Android 2.3.3; Linux; Opera Mobi/ADR-1111101157; U; es-ES) Presto/2.9.201 Version/11.50</code></td>
-		</tr>
-		<tr>
-			<td>Internet Explorer</td>
-			<td><code>IEMobile/xyz</code> token in the comment.</td>
-			<td><code>Mozilla/5.0 (compatible; MSIE 9.0; Windows Phone OS 7.5; Trident/5.0; IEMobile/9.0)</code></td>
-		</tr>
-		<tr>
-			<td>Edge on Windows 10 Mobile</td>
-			<td><code>Mobile/xyz</code> and <code>Edge/</code> tokens outside the comment.</td>
-			<td><code>Mozilla/5.0 (Windows Phone 10.0; Android 6.0.1; Xbox; Xbox One) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/58.0.3029.110 Mobile Safari/537.36 Edge/16.16299</code></td>
-		</tr>
-	</tbody>
-</table>
-
-<p>In summary, we recommend looking for the string <code>Mobi</code> anywhere in the User Agent to detect a mobile device.</p>
-
-<div class="notecard note">
-  <p><strong>Note:</strong> If the device is large enough that it's not marked with <code>Mobi</code>, you should serve your desktop site (which, as a best practice, should support touch input anyway, as more desktop machines are appearing with touchscreens).</p>
-</div>
+},0));
+```
+
+## Which part of the user agent contains the information you are looking for?
+
+As there is no uniformity of the different part of the user agent string, this is the tricky part.
+
+### Browser Name
+
+When people say they want "browser detection", often they actually want "rendering engine detection". Do you actually want to detect Firefox, as opposed to SeaMonkey, or Chrome as opposed to Chromium? Or do you actually want to see if the browser is using the Gecko or the WebKit rendering engine? If this is what you need, see further down the page.
+
+Most browsers set the name and version in the format _BrowserName/VersionNumber_, with the notable exception of Internet Explorer. But as the name is not the only information in a user agent string that is in that format, you can not discover the name of the browser, you can only check if the name you are looking for. But note that some browsers are lying: Chrome for example reports both as Chrome and Safari. So to detect Safari you have to check for the Safari string and the absence of the Chrome string, Chromium often reports itself as Chrome too or Seamonkey sometimes reports itself as Firefox.
+
+Also, pay attention not to use a simple regular expression on the BrowserName, user agents also contain strings outside the Keyword/Value syntax. Safari & Chrome contain the string 'like Gecko', for instance.
+
+| Engine                          | Must contain            | Must not contain               |
+| ------------------------------- | ----------------------- | ------------------------------ |
+| Firefox                         | `Firefox/xyz`           | `Seamonkey/xyz`                |
+| Seamonkey                       | `Seamonkey/xyz`         |                                |
+| Chrome                          | `Chrome/xyz`            | `Chromium/xyz`                 |
+| Chromium                        | `Chromium/xyz`          |                                |
+| Safari                          | `Safari/xyz`            | `Chrome/xyz` or `Chromium/xyz` |
+| Opera 15+ (Blink-based engine)  | `OPR/xyz`               |                                |
+| Opera 12- (Presto-based engine) | `Opera/xyz`             |                                |
+| Internet Explorer 10-           | `; MSIE xyz;`           |                                |
+| Internet Explorer 11            | `Trident/7.0; .*rv:xyz` |                                |
+
+\[1] Safari gives two version numbers: one technical in the `Safari/xyz` token, and one user-friendly in a `Version/xyz` token.
+
+Of course, there is absolutely no guarantee that another browser will not hijack some of these things (like Chrome hijacked the Safari string in the past). That's why browser detection using the user agent string is unreliable and should be done only with the check of the version number (hijacking of past versions is less likely).
+
+### Browser version
+
+The browser version is often, but not always, put in the value part of the _BrowserName/VersionNumber_ token in the User Agent String. This is of course not the case for Internet Explorer (which puts the version number right after the MSIE token), and for Opera after version 10, which has added a Version/_VersionNumber_ token.
+
+Here again, be sure to take the right token for the browser you are looking for, as there is no guarantee that others will contain a valid number.
+
+### Rendering engine
+
+As seen earlier, in most cases, looking for the rendering engine is a better way to go. This will help to not exclude lesser known browsers. Browsers sharing a common rendering engine will display a page in the same way: it is often a fair assumption that what will work in one will work in the other.
+
+There are five major rendering engines: Trident, Gecko, Presto, Blink, and WebKit. As sniffing the rendering engines names is common, a lot of user agents added other rendering names to trigger detection. It is therefore important to pay attention not to trigger false-positives when detecting the rendering engine.
+
+| Engine   | Must contain      | Comment                                                                                                                                                                                      |
+| -------- | ----------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Gecko    | `Gecko/xyz`       |                                                                                                                                                                                              |
+| WebKit   | `AppleWebKit/xyz` | Pay attention, WebKit browsers add a 'like Gecko' string that may trigger false positive for Gecko if the detection is not careful.                                                          |
+| Presto   | `Opera/xyz`       | **Note:** Presto is no longer used in Opera browser builds >= version 15 (see 'Blink')                                                                                                       |
+| Trident  | `Trident/xyz`     | Internet Explorer put this token in the _comment_ part of the User Agent String                                                                                                              |
+| EdgeHTML | `Edge/xyz`        | The non-Chromium Edge puts its engine version after the _Edge/_ token, not the application version. **Note:** EdgeHTML is no longer used in Edge browser builds >= version 79 (see 'Blink'). |
+| Blink    | `Chrome/xyz`      |                                                                                                                                                                                              |
+
+## Rendering engine version
+
+Most rendering engines put the version number in the _RenderingEngine/VersionNumber_ token, with the notable exception of Gecko. Gecko puts the Gecko version number in the comment part of the User Agent after the `rv:` string. From Gecko 14 for the mobile version and Gecko 17 for the desktop version, it also puts this value in the `Gecko/version` token (previous version put there the build date, then a fixed date called the GeckoTrail).
+
+## OS
+
+The Operating System is given in most User Agent strings (although not web-focused platforms like Firefox OS), but the format varies a lot. It is a fixed string between two semi-colons, in the comment part of the User Agent. These strings are specific for each browser. They indicate the OS, but also often its version and information on the relying hardware (32 or 64 bits, or Intel/PPC for Mac).
+
+Like in all cases, these strings may change in the future, one should use them only in conjunction with the detection of already released browsers. A technological survey must be in place to adapt the script when new browser versions are coming out.
+
+### Mobile, Tablet or Desktop
+
+The most common reason to perform user agent sniffing is to determine which type of device the browser runs on. The goal is to serve different HTML to different device types.
+
+- Never assume that a browser or a rendering engine only runs on one type of device. Especially don't make different defaults for different browsers or rendering engines.
+- Never use the OS token to define if a browser is on mobile, tablet or desktop. The OS may run on more than one type of (for example, Android runs on tablets as well as phones).
+
+The following table summarizes the way common browser vendors indicate that their browsers are running on a mobile device:
+
+| Browser                                                           | Rule                                                                                                                                                                                                                                                | Example                                                                                                                                                          |
+| ----------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Mozilla (Gecko, Firefox)                                          | `Mobile` or `Tablet` inside the comment.                                                                                                                                                                                                            | `Mozilla/5.0 (Android; Mobile; rv:13.0) Gecko/13.0 Firefox/13.0`                                                                                                 |
+| WebKit-based (Android, Safari)                                    | `Mobile Safari` token [outside](https://developer.apple.com/library/safari/documentation/AppleApplications/Reference/SafariWebContent/OptimizingforSafarioniPhone/OptimizingforSafarioniPhone.html#//apple_ref/doc/uid/TP40006517-SW3) the comment. | `Mozilla/5.0 (Linux; U; Android 4.0.3; de-ch; HTC Sensation Build/IML74K) AppleWebKit/534.30 (KHTML, like Gecko) Version/4.0 Mobile Safari/534.30`               |
+| Blink-based (Chromium, Google Chrome, Opera 15+, Edge on Android) | `Mobile Safari` token [outside](https://developers.google.com/chrome/mobile/docs/user-agent) the comment.                                                                                                                                           | `Mozilla/5.0 (Linux; Android 4.4.2); Nexus 5 Build/KOT49H) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/33.0.1750.117 Mobile Safari/537.36 OPR/20.0.1396.72047` |
+| Presto-based (Opera 12-)                                          | `Opera Mobi/xyz` token [inside](https://my.opera.com/community/openweb/idopera/) the comment.                                                                                                                                                       | `Opera/9.80 (Android 2.3.3; Linux; Opera Mobi/ADR-1111101157; U; es-ES) Presto/2.9.201 Version/11.50`                                                            |
+| Internet Explorer                                                 | `IEMobile/xyz` token in the comment.                                                                                                                                                                                                                | `Mozilla/5.0 (compatible; MSIE 9.0; Windows Phone OS 7.5; Trident/5.0; IEMobile/9.0)`                                                                            |
+| Edge on Windows 10 Mobile                                         | `Mobile/xyz` and `Edge/` tokens outside the comment.                                                                                                                                                                                                | `Mozilla/5.0 (Windows Phone 10.0; Android 6.0.1; Xbox; Xbox One) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/58.0.3029.110 Mobile Safari/537.36 Edge/16.16299` |
+
+In summary, we recommend looking for the string `Mobi` anywhere in the User Agent to detect a mobile device.
+
+> **Note:** If the device is large enough that it's not marked with `Mobi`, you should serve your desktop site (which, as a best practice, should support touch input anyway, as more desktop machines are appearing with touchscreens).
diff --git a/files/en-us/web/http/caching/index.md b/files/en-us/web/http/caching/index.md
index 50ec956ff7e29cb..2dc9d3da2a1dfe0 100644
--- a/files/en-us/web/http/caching/index.md
+++ b/files/en-us/web/http/caching/index.md
@@ -6,183 +6,175 @@ tags:
   - Guide
   - HTTP
 ---
-<div>{{HTTPSidebar}}</div>
+{{HTTPSidebar}}
 
-<p class="summary">The performance of web sites and applications can be significantly improved by reusing previously fetched resources. Web caches reduce latency and network traffic and thus lessen the time needed to display a representation of a resource. By making use of HTTP caching, Web sites become more responsive.</p>
+The performance of web sites and applications can be significantly improved by reusing previously fetched resources. Web caches reduce latency and network traffic and thus lessen the time needed to display a representation of a resource. By making use of HTTP caching, Web sites become more responsive.
 
-<h2 id="Different_kinds_of_caches">Different kinds of caches</h2>
+## Different kinds of caches
 
-<p>Caching is a technique that stores a copy of a given resource and serves it back when requested. When a web cache has a requested resource in its store, it intercepts the request and returns its copy instead of re-downloading from the originating server. This achieves several goals: it eases the load of the server that doesn’t need to serve all clients itself, and it improves performance by being closer to the client, i.e., it takes less time to transmit the resource back. For a web site, it is a major component in achieving high performance. On the other side, it has to be configured properly as not all resources stay identical forever: it is important to cache a resource only until it changes, not longer.</p>
+Caching is a technique that stores a copy of a given resource and serves it back when requested. When a web cache has a requested resource in its store, it intercepts the request and returns its copy instead of re-downloading from the originating server. This achieves several goals: it eases the load of the server that doesn’t need to serve all clients itself, and it improves performance by being closer to the client, i.e., it takes less time to transmit the resource back. For a web site, it is a major component in achieving high performance. On the other side, it has to be configured properly as not all resources stay identical forever: it is important to cache a resource only until it changes, not longer.
 
-<p>There are several kinds of caches: these can be grouped into two main categories: private or shared caches. A <em>shared cache</em> is a cache that stores responses for reuse by more than one user. A <em>private cache</em> is dedicated to a single user. This page will mostly talk about browser and proxy caches, but there are also gateway caches, CDN, reverse proxy caches and load balancers that are deployed on web servers for better reliability, performance and scaling of web sites and web applications.</p>
+There are several kinds of caches: these can be grouped into two main categories: private or shared caches. A _shared cache_ is a cache that stores responses for reuse by more than one user. A _private cache_ is dedicated to a single user. This page will mostly talk about browser and proxy caches, but there are also gateway caches, CDN, reverse proxy caches and load balancers that are deployed on web servers for better reliability, performance and scaling of web sites and web applications.
 
-<p><img alt="What a cache provide, advantages/disadvantages of shared/private caches." src="http_cache_type.png"></p>
+![What a cache provide, advantages/disadvantages of shared/private caches.](http_cache_type.png)
 
-<h3 id="Private_browser_caches">Private browser caches</h3>
+### Private browser caches
 
-<p>A private cache is dedicated to a single user. You might have seen "caching" in your browser's settings already. A browser cache holds all documents downloaded via <a href="/en-US/docs/Web/HTTP">HTTP</a> by the user. This cache is used to make visited documents available for back/forward navigation, saving, viewing-as-source, etc. without requiring an additional trip to the server. It likewise improves offline browsing of cached content.</p>
+A private cache is dedicated to a single user. You might have seen "caching" in your browser's settings already. A browser cache holds all documents downloaded via [HTTP](/en-US/docs/Web/HTTP) by the user. This cache is used to make visited documents available for back/forward navigation, saving, viewing-as-source, etc. without requiring an additional trip to the server. It likewise improves offline browsing of cached content.
 
-<h3 id="Shared_proxy_caches">Shared proxy caches</h3>
+### Shared proxy caches
 
-<p>A shared cache is a cache that stores responses to be reused by more than one user. For example, an ISP or your company might have set up a web proxy as part of its local network infrastructure to serve many users so that popular resources are reused a number of times, reducing network traffic and latency.</p>
+A shared cache is a cache that stores responses to be reused by more than one user. For example, an ISP or your company might have set up a web proxy as part of its local network infrastructure to serve many users so that popular resources are reused a number of times, reducing network traffic and latency.
 
-<h2 id="Targets_of_caching_operations">Targets of caching operations</h2>
+## Targets of caching operations
 
-<p>HTTP caching is optional but usually desirable. HTTP caches are typically limited to caching responses to {{HTTPMethod("GET")}}; they may decline other methods. The primary cache key consists of the request method and target URI (often only the URI is used — this is because only <code>GET</code> requests are caching targets).</p>
+HTTP caching is optional but usually desirable. HTTP caches are typically limited to caching responses to {{HTTPMethod("GET")}}; they may decline other methods. The primary cache key consists of the request method and target URI (often only the URI is used — this is because only `GET` requests are caching targets).
 
-<p>Common forms of caching entries are:</p>
+Common forms of caching entries are:
 
-<ul>
- <li>Successful results of a retrieval request: a {{HTTPStatus(200)}} (OK) response to a {{HTTPMethod("GET")}} request containing a resource like HTML documents, images or files.</li>
- <li>Permanent redirects: a {{HTTPStatus(301)}} (Moved Permanently) response.</li>
- <li>Error responses: a {{HTTPStatus(404)}} (Not Found) result page.</li>
- <li>Incomplete results: a {{HTTPStatus(206)}} (Partial Content) response.</li>
- <li>Responses other than {{HTTPMethod("GET")}} if something suitable for use as a cache key is defined.</li>
-</ul>
+- Successful results of a retrieval request: a {{HTTPStatus(200)}} (OK) response to a {{HTTPMethod("GET")}} request containing a resource like HTML documents, images or files.
+- Permanent redirects: a {{HTTPStatus(301)}} (Moved Permanently) response.
+- Error responses: a {{HTTPStatus(404)}} (Not Found) result page.
+- Incomplete results: a {{HTTPStatus(206)}} (Partial Content) response.
+- Responses other than {{HTTPMethod("GET")}} if something suitable for use as a cache key is defined.
 
-<p>A cache entry might also consist of multiple stored responses differentiated by a secondary key, if the request is target of content negotiation. For more details see the information about the {{HTTPHeader("Vary")}} header <a href="#varying_responses">below</a>.</p>
+A cache entry might also consist of multiple stored responses differentiated by a secondary key, if the request is target of content negotiation. For more details see the information about the {{HTTPHeader("Vary")}} header [below](#varying_responses).
 
-<h2 id="Controlling_caching">Controlling caching</h2>
+## Controlling caching
 
-<h3 id="The_Cache-Control_header">The <code>Cache-Control</code> header</h3>
+### The `Cache-Control` header
 
-<p>The {{HTTPHeader("Cache-Control")}} HTTP/1.1 general-header field is used to specify directives for caching mechanisms in both requests and responses. Use this header to define your caching policies with the variety of directives it provides.</p>
+The {{HTTPHeader("Cache-Control")}} HTTP/1.1 general-header field is used to specify directives for caching mechanisms in both requests and responses. Use this header to define your caching policies with the variety of directives it provides.
 
-<h4 id="No_caching">No caching</h4>
+#### No caching
 
-<p>The cache should not store anything about the client request or server response. A request is sent to the server and a full response is downloaded each and every time.</p>
+The cache should not store anything about the client request or server response. A request is sent to the server and a full response is downloaded each and every time.
 
-<pre>Cache-Control: no-store</pre>
+    Cache-Control: no-store
 
-<h4 id="Cache_but_revalidate">Cache but revalidate</h4>
+#### Cache but revalidate
 
-<p>A cache will send the request to the origin server for validation before releasing a cached copy.</p>
+A cache will send the request to the origin server for validation before releasing a cached copy.
 
-<pre>Cache-Control: no-cache</pre>
+    Cache-Control: no-cache
 
-<h4 id="Private_and_public_caches">Private and public caches</h4>
+#### Private and public caches
 
-<p>The "public" directive indicates that the response may be cached by any cache. This can be useful if pages with HTTP authentication, or response status codes that aren't normally cacheable, should now be cached.</p>
+The "public" directive indicates that the response may be cached by any cache. This can be useful if pages with HTTP authentication, or response status codes that aren't normally cacheable, should now be cached.
 
-<p>On the other hand, "private" indicates that the response is intended for a single user only and must not be stored by a shared cache. A private browser cache may store the response in this case.</p>
+On the other hand, "private" indicates that the response is intended for a single user only and must not be stored by a shared cache. A private browser cache may store the response in this case.
 
-<pre>Cache-Control: private
-Cache-Control: public
-</pre>
+    Cache-Control: private
+    Cache-Control: public
 
-<h4 id="Expiration">Expiration</h4>
+#### Expiration
 
-<p>The most important directive here is <code>max-age=&lt;seconds&gt;</code>, which is the maximum amount of time in which a resource will be considered fresh. This directive is relative to the time of the request, and overrides the {{HTTPHeader("Expires")}} header (if set). For the files in the application that will not change, you can normally use aggressive caching. This includes static files such as images, CSS files, and JavaScript files, for example.</p>
+The most important directive here is `max-age=<seconds>`, which is the maximum amount of time in which a resource will be considered fresh. This directive is relative to the time of the request, and overrides the {{HTTPHeader("Expires")}} header (if set). For the files in the application that will not change, you can normally use aggressive caching. This includes static files such as images, CSS files, and JavaScript files, for example.
 
-<p>For more details, see also the <a href="#freshness">Freshness</a> section below.</p>
+For more details, see also the [Freshness](#freshness) section below.
 
-<pre>Cache-Control: max-age=31536000</pre>
+    Cache-Control: max-age=31536000
 
-<h4 id="Validation">Validation</h4>
+#### Validation
 
-<p>When using the "<code>must-revalidate</code>" directive, the cache must verify the status of the stale resources before using it and expired ones should not be used. For more details, see the <a href="#cache_validation">Validation</a> section below.</p>
+When using the "`must-revalidate`" directive, the cache must verify the status of the stale resources before using it and expired ones should not be used. For more details, see the [Validation](#cache_validation) section below.
 
-<pre>Cache-Control: must-revalidate</pre>
+    Cache-Control: must-revalidate
 
-<h3 id="The_Pragma_header">The <code>Pragma</code> header</h3>
+### The `Pragma` header
 
-<p>{{HTTPHeader("Pragma")}} is an HTTP/1.0 header. <code>Pragma: no-cache</code> is like <code>Cache-Control: no-cache</code> in that it forces caches to submit the request to the origin server for validation, before releasing a cached copy. However, <code>Pragma</code> is not specified for HTTP responses and is therefore not a reliable replacement for the general HTTP/1.1 <code>Cache-Control</code> header.</p>
+{{HTTPHeader("Pragma")}} is an HTTP/1.0 header. `Pragma: no-cache` is like `Cache-Control: no-cache` in that it forces caches to submit the request to the origin server for validation, before releasing a cached copy. However, `Pragma` is not specified for HTTP responses and is therefore not a reliable replacement for the general HTTP/1.1 `Cache-Control` header.
 
-<p><code>Pragma</code> should only be used for backwards compatibility with HTTP/1.0 caches where the <code>Cache-Control</code> HTTP/1.1 header is not yet present.</p>
+`Pragma` should only be used for backwards compatibility with HTTP/1.0 caches where the `Cache-Control` HTTP/1.1 header is not yet present.
 
-<h2 id="Freshness">Freshness</h2>
+## Freshness
 
-<p>Once a resource is stored in a cache, it could theoretically be served by the cache forever. Caches have finite storage so items are periodically removed from storage. This process is called <em>cache eviction</em>. On the other side, some resources may change on the server so the cache should be updated. As HTTP is a client-server protocol, servers can't contact caches and clients when a resource changes; they have to communicate an expiration time for the resource. Before this expiration time, the resource is <em>fresh</em>; after the expiration time, the resource is <em>stale</em>. Eviction algorithms often privilege fresh resources over stale resources. Note that a stale resource is not evicted or ignored; when the cache receives a request for a stale resource, it forwards this request with a {{HTTPHeader("If-None-Match")}} to check if it is in fact still fresh. If so, the server returns a {{HTTPStatus("304")}} (Not Modified) header without sending the body of the requested resource, saving some bandwidth.</p>
+Once a resource is stored in a cache, it could theoretically be served by the cache forever. Caches have finite storage so items are periodically removed from storage. This process is called _cache eviction_. On the other side, some resources may change on the server so the cache should be updated. As HTTP is a client-server protocol, servers can't contact caches and clients when a resource changes; they have to communicate an expiration time for the resource. Before this expiration time, the resource is _fresh_; after the expiration time, the resource is *stale*. Eviction algorithms often privilege fresh resources over stale resources. Note that a stale resource is not evicted or ignored; when the cache receives a request for a stale resource, it forwards this request with a {{HTTPHeader("If-None-Match")}} to check if it is in fact still fresh. If so, the server returns a {{HTTPStatus("304")}} (Not Modified) header without sending the body of the requested resource, saving some bandwidth.
 
-<p>Here is an example of this process with a shared cache proxy:</p>
+Here is an example of this process with a shared cache proxy:
 
-<p><img alt="Show how a proxy cache acts when a doc is not cache, in the cache and fresh, in the cache and stale." src="http_staleness.png"></p>
+![Show how a proxy cache acts when a doc is not cache, in the cache and fresh, in the cache and stale.](http_staleness.png)
 
-<p>The freshness lifetime is calculated based on several headers. If a "<code>Cache-Control: max-age=N</code>" header is specified, then the freshness lifetime is equal to N. If this header is not present, which is very often the case, it is checked if an {{HTTPHeader("Expires")}} header is present. If an <code>Expires</code> header exists, then its value minus the value of the {{HTTPHeader("Date")}} header determines the freshness lifetime.</p>
+The freshness lifetime is calculated based on several headers. If a "`Cache-Control: max-age=N`" header is specified, then the freshness lifetime is equal to N. If this header is not present, which is very often the case, it is checked if an {{HTTPHeader("Expires")}} header is present. If an `Expires` header exists, then its value minus the value of the {{HTTPHeader("Date")}} header determines the freshness lifetime.
 
-<h3 id="Heuristic_freshness_checking">Heuristic freshness checking</h3>
+### Heuristic freshness checking
 
-<p>If an origin server does not explicitly specify freshness (e.g. using {{HTTPHeader("Cache-Control")}} or {{HTTPHeader("Expires")}} header) then a heuristic approach may be used.</p>
+If an origin server does not explicitly specify freshness (e.g. using {{HTTPHeader("Cache-Control")}} or {{HTTPHeader("Expires")}} header) then a heuristic approach may be used.
 
-<p>In this case look for a {{HTTPHeader("Last-Modified")}} header. If this header is present, then the cache's freshness lifetime is equal to the value of the <code>Date</code> header minus the value of the <code>Last-modified</code> header divided by 10. The expiration time is computed as follows:</p>
+In this case look for a {{HTTPHeader("Last-Modified")}} header. If this header is present, then the cache's freshness lifetime is equal to the value of the `Date` header minus the value of the `Last-modified` header divided by 10. The expiration time is computed as follows:
 
-<pre>expirationTime = responseTime + freshnessLifetime - currentAge</pre>
+    expirationTime = responseTime + freshnessLifetime - currentAge
 
-<p>where <code>responseTime</code> is the time at which the response was received according to the browser. For more information see <a href="https://datatracker.ietf.org/doc/html/rfc7234#section-4.2.2">RFC 7234: Hypertext Transfer Protocol (HTTP/1.1): 4.2.2.  Calculating Heuristic Freshness</a>.</p>
+where `responseTime` is the time at which the response was received according to the browser. For more information see [RFC 7234: Hypertext Transfer Protocol (HTTP/1.1): 4.2.2.  Calculating Heuristic Freshness](https://datatracker.ietf.org/doc/html/rfc7234#section-4.2.2).
 
-<h3 id="Revved_resources">Revved resources</h3>
+### Revved resources
 
-<p>The more we use cached resources, the better the responsiveness and the performance of a Web site will be. To optimize this, good practices recommend to set expiration times as far in the future as possible. This is possible on resources that are regularly updated, or often, but is problematic for resources that are rarely and infrequently updated. They are the resources that would benefit the most from caching resources, yet this makes them very difficult to update. This is typical of the technical resources included and linked from each Web pages: JavaScript and CSS files change infrequently, but when they change you want them to be updated quickly.</p>
+The more we use cached resources, the better the responsiveness and the performance of a Web site will be. To optimize this, good practices recommend to set expiration times as far in the future as possible. This is possible on resources that are regularly updated, or often, but is problematic for resources that are rarely and infrequently updated. They are the resources that would benefit the most from caching resources, yet this makes them very difficult to update. This is typical of the technical resources included and linked from each Web pages: JavaScript and CSS files change infrequently, but when they change you want them to be updated quickly.
 
-<p>Web developers invented a technique that Steve Souders called <a href="https://www.stevesouders.com/blog/2008/08/23/revving-filenames-dont-use-querystring/">revving</a>. Infrequently updated files are named in a specific way: in their URL, usually in the filename, a revision (or version) number is added. That way each new revision of this resource is considered as a resource on its own that <em>never</em> changes and that can have an expiration time very far in the future, usually one year or even more. In order to have the new versions, all the links to them must be changed, that is the drawback of this method: additional complexity that is usually taken care of by the tool chain used by Web developers. When the infrequently variable resources change they induce an additional change to often variable resources. When these are read, the new versions of the others are also read.</p>
+Web developers invented a technique that Steve Souders called [revving](https://www.stevesouders.com/blog/2008/08/23/revving-filenames-dont-use-querystring/). Infrequently updated files are named in a specific way: in their URL, usually in the filename, a revision (or version) number is added. That way each new revision of this resource is considered as a resource on its own that _never_ changes and that can have an expiration time very far in the future, usually one year or even more. In order to have the new versions, all the links to them must be changed, that is the drawback of this method: additional complexity that is usually taken care of by the tool chain used by Web developers. When the infrequently variable resources change they induce an additional change to often variable resources. When these are read, the new versions of the others are also read.
 
-<p>This technique has an additional benefit: updating two cached resources at the same time will not lead to the situation where the out-dated version of one resource is used in combination with the new version of the other one. This is very important when web sites have CSS stylesheets or JS scripts that have mutual dependencies, i.e., they depend on each other because they refer to the same HTML elements.</p>
+This technique has an additional benefit: updating two cached resources at the same time will not lead to the situation where the out-dated version of one resource is used in combination with the new version of the other one. This is very important when web sites have CSS stylesheets or JS scripts that have mutual dependencies, i.e., they depend on each other because they refer to the same HTML elements.
 
-<p><img alt="How the revved cache mechanism works. With minor typo fix to grammar issue: https://github.com/mdn/sprints/issues/2618" src="http_revved_fix_typo.png"></p>
+![How the revved cache mechanism works. With minor typo fix to grammar issue: https://github.com/mdn/sprints/issues/2618](http_revved_fix_typo.png)
 
-<p>The revision version added to revved resources doesn't need to be a classical revision string like 1.1.3, or even a monotonously growing suite of number. It can be anything that prevent collisions, like a hash or a date.</p>
+The revision version added to revved resources doesn't need to be a classical revision string like 1.1.3, or even a monotonously growing suite of number. It can be anything that prevent collisions, like a hash or a date.
 
-<h2 id="Cache_validation">Cache validation</h2>
+## Cache validation
 
-<p>When a cached document's expiration time has been reached, it is either validated or fetched again. Validation can only occur if the server provided either a <em>strong validator</em> or a <em>weak validator</em>.</p>
+When a cached document's expiration time has been reached, it is either validated or fetched again. Validation can only occur if the server provided either a _strong validator_ or a _weak validator_.
 
-<p>Revalidation is triggered when the user presses the reload button. It is also triggered under normal browsing if the cached response includes the "<code>Cache-Control: must-revalidate</code>" header. Another factor is the cache validation preferences in the <code>Advanced-&gt;Cache</code> preferences panel. There is an option to force a validation each time a document is loaded.</p>
+Revalidation is triggered when the user presses the reload button. It is also triggered under normal browsing if the cached response includes the "`Cache-Control: must-revalidate`" header. Another factor is the cache validation preferences in the `Advanced->Cache` preferences panel. There is an option to force a validation each time a document is loaded.
 
-<h3 id="ETags">ETags</h3>
+### ETags
 
-<p>The {{HTTPHeader("ETag")}} response header is an <em>opaque-to-the-useragent</em> value that can be used as a strong validator. That means that a HTTP user-agent, such as the browser, does not know what this string represents and can't predict what its value would be. If the <code>ETag</code> header was part of the response for a resource, the client can issue an {{HTTPHeader("If-None-Match")}} in the header of future requests – in order to validate the cached resource.</p>
+The {{HTTPHeader("ETag")}} response header is an _opaque-to-the-useragent_ value that can be used as a strong validator. That means that a HTTP user-agent, such as the browser, does not know what this string represents and can't predict what its value would be. If the `ETag` header was part of the response for a resource, the client can issue an {{HTTPHeader("If-None-Match")}} in the header of future requests – in order to validate the cached resource.
 
-<h3 id="Last-Modified">Last-Modified</h3>
+### Last-Modified
 
-<p>The {{HTTPHeader("Last-Modified")}} response header can be used as a weak validator. It is considered weak because it only has 1-second resolution. If the <code>Last-Modified</code> header is present in a response, then the client can issue an {{HTTPHeader("If-Modified-Since")}} request header to validate the cached document.</p>
+The {{HTTPHeader("Last-Modified")}} response header can be used as a weak validator. It is considered weak because it only has 1-second resolution. If the `Last-Modified` header is present in a response, then the client can issue an {{HTTPHeader("If-Modified-Since")}} request header to validate the cached document.
 
-<p>When a validation request is made, the server can either ignore the validation request and respond with a normal {{HTTPStatus(200)}} <code>OK</code>, or it can return {{HTTPStatus(304)}} <code>Not Modified</code> (with an empty body) to instruct the browser to use its cached copy. The latter response can also include headers that update the expiration time of the cached document.</p>
+When a validation request is made, the server can either ignore the validation request and respond with a normal {{HTTPStatus(200)}} `OK`, or it can return {{HTTPStatus(304)}} `Not Modified` (with an empty body) to instruct the browser to use its cached copy. The latter response can also include headers that update the expiration time of the cached document.
 
-<h2 id="Varying_responses">Varying responses</h2>
+## Varying responses
 
-<p>The {{HTTPHeader("Vary")}} HTTP response header determines how to match future request headers to decide whether a cached response can be used, or if a fresh one must be requested from the origin server.</p>
+The {{HTTPHeader("Vary")}} HTTP response header determines how to match future request headers to decide whether a cached response can be used, or if a fresh one must be requested from the origin server.
 
-<p>When a cache receives a request that has a <code>Vary</code> header field, it must not use a cached response by default unless all header fields specified in the <code>Vary</code> header match in both the original (cached) request and the new request.</p>
+When a cache receives a request that has a `Vary` header field, it must not use a cached response by default unless all header fields specified in the `Vary` header match in both the original (cached) request and the new request.
 
-<p><img alt="The Vary header leads cache to use more HTTP headers as key for the cache." src="http_vary.png">This feature is commonly used to allow a resource to be cached in uncompressed and (various) compressed forms, and served appropriately to user agents based on the encodings that they support. For example, a server can set <code>Vary: Accept-Encoding</code> to ensure that a separate version of a resource is cached for all requests that specify support for a particular set of encodings, e.g. <code>Accept-Encoding: gzip,deflate,sdch</code>.</p>
+![The Vary header leads cache to use more HTTP headers as key for the cache.](http_vary.png)This feature is commonly used to allow a resource to be cached in uncompressed and (various) compressed forms, and served appropriately to user agents based on the encodings that they support. For example, a server can set `Vary: Accept-Encoding` to ensure that a separate version of a resource is cached for all requests that specify support for a particular set of encodings, e.g. `Accept-Encoding: gzip,deflate,sdch`.
 
-<pre>Vary: Accept-Encoding</pre>
+    Vary: Accept-Encoding
 
-<div class="notecard note">
-  <p><strong>Note:</strong> Use <code>Vary</code> with care—it can easily reduce the effectiveness of caching! A caching server should use <a href="#normalization">normalization</a> to reduce duplicated cache entries and unnecessary requests to the origin server. This is particularly true when using <code>Vary</code> with headers and header values that can have many values.</p>
-</div>
+> **Note:** Use `Vary` with care—it can easily reduce the effectiveness of caching! A caching server should use [normalization](#normalization) to reduce duplicated cache entries and unnecessary requests to the origin server. This is particularly true when using `Vary` with headers and header values that can have many values.
 
-<p>The <code>Vary</code> header can also be useful for serving different content to desktop and mobile users, or to allow search engines to discover the mobile version of a page (and perhaps also tell them that no <a href="https://en.wikipedia.org/wiki/Cloaking">Cloaking</a> is intended). This is usually achieved with the <code>Vary: User-Agent</code> header, and works because the {{HTTPHeader("User-Agent")}} header value is different for mobile and desktop clients.</p>
+The `Vary` header can also be useful for serving different content to desktop and mobile users, or to allow search engines to discover the mobile version of a page (and perhaps also tell them that no [Cloaking](https://en.wikipedia.org/wiki/Cloaking) is intended). This is usually achieved with the `Vary: User-Agent` header, and works because the {{HTTPHeader("User-Agent")}} header value is different for mobile and desktop clients.
 
-<pre>Vary: User-Agent</pre>
+    Vary: User-Agent
 
-<h3 id="Normalization">Normalization</h3>
+### Normalization
 
-<p>As discussed above, caching servers will by default match future requests <em>only</em> to requests with <em>exactly</em> the same headers and header values. That means a request will be made to the origin and a new cache will be created for every slight variant that might be specified by different user-agents.</p>
+As discussed above, caching servers will by default match future requests _only_ to requests with _exactly_ the same headers and header values. That means a request will be made to the origin and a new cache will be created for every slight variant that might be specified by different user-agents.
 
-<p>For example, by default all of the following result in a separate request to the origin and a separate cache entry: <code>Accept-Encoding: gzip,deflate,sdch</code>, <code>Accept-Encoding: gzip,deflate</code>, <code>Accept-Encoding: gzip</code>. This is true even though the origin server will probably respond with — and store — the same resource for all requests (a gzip)!</p>
+For example, by default all of the following result in a separate request to the origin and a separate cache entry: `Accept-Encoding: gzip,deflate,sdch`, `Accept-Encoding: gzip,deflate`, `Accept-Encoding: gzip`. This is true even though the origin server will probably respond with — and store — the same resource for all requests (a gzip)!
 
-<p>To avoid unnecessary requests and duplicated cache entries, caching servers should use <strong>normalization</strong> to pre-process the request and cache only files that are needed. For example, in the case of <code>Accept-Encoding</code> you could check for <code>gzip</code> and other compression types in the header before doing further processing, and otherwise unset the header. In "pseudo code" this might look like:</p>
+To avoid unnecessary requests and duplicated cache entries, caching servers should use **normalization** to pre-process the request and cache only files that are needed. For example, in the case of `Accept-Encoding` you could check for `gzip` and other compression types in the header before doing further processing, and otherwise unset the header. In "pseudo code" this might look like:
 
-<pre>// Normalize Accept-Encoding
-if (req.http.Accept-Encoding) {
-  if (req.http.Accept-Encoding ~ "gzip") {
-    set req.http.Accept-Encoding = "gzip";
-  }
-  // elsif other encoding types to check
-  else {
-    unset req.http.Accept-Encoding;
-  }
-}
-</pre>
+    // Normalize Accept-Encoding
+    if (req.http.Accept-Encoding) {
+      if (req.http.Accept-Encoding ~ "gzip") {
+        set req.http.Accept-Encoding = "gzip";
+      }
+      // elsif other encoding types to check
+      else {
+        unset req.http.Accept-Encoding;
+      }
+    }
 
-<p><code>User-Agent</code> has even more variation than <code>Accept-Encoding</code>. So if using <code>Vary: User-Agent</code> for caching mobile/desktop variants of files you'd similarly check for the presence of <code>"mobile"</code> and <code>"desktop"</code> in the request <code>User-Agent</code> header, and then clear it.</p>
+`User-Agent` has even more variation than `Accept-Encoding`. So if using `Vary: User-Agent` for caching mobile/desktop variants of files you'd similarly check for the presence of `"mobile"` and `"desktop"` in the request `User-Agent` header, and then clear it.
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
- <li><a href="https://datatracker.ietf.org/doc/html/rfc7234">RFC 7234: Hypertext Transfer Protocol (HTTP/1.1): Caching</a></li>
- <li><a href="https://www.mnot.net/cache_docs">Caching Tutorial – Mark Nottingham</a></li>
- <li><a href="https://developers.google.com/web/fundamentals/performance/optimizing-content-efficiency/http-caching">HTTP caching – Ilya Grigorik</a></li>
- <li><a href="https://redbot.org/">RedBot</a>, a tool to check your cache-related HTTP headers.</li>
-</ul>
+- [RFC 7234: Hypertext Transfer Protocol (HTTP/1.1): Caching](https://datatracker.ietf.org/doc/html/rfc7234)
+- [Caching Tutorial – Mark Nottingham](https://www.mnot.net/cache_docs)
+- [HTTP caching – Ilya Grigorik](https://developers.google.com/web/fundamentals/performance/optimizing-content-efficiency/http-caching)
+- [RedBot](https://redbot.org/), a tool to check your cache-related HTTP headers.
diff --git a/files/en-us/web/http/compression/index.md b/files/en-us/web/http/compression/index.md
index b8f20b0212ace77..d435db09ebedb1f 100644
--- a/files/en-us/web/http/compression/index.md
+++ b/files/en-us/web/http/compression/index.md
@@ -6,63 +6,57 @@ tags:
   - HTTP
   - compression
 ---
-<div>{{HTTPSidebar}}</div>
+{{HTTPSidebar}}
 
-<p class="summary"><strong>Compression</strong> is an important way to increase the performance of a Web site. For some documents, size reduction of up to 70% lowers the bandwidth capacity needs. Over the years, algorithms also got more efficient, and new ones are supported by clients and servers.</p>
+**Compression** is an important way to increase the performance of a Web site. For some documents, size reduction of up to 70% lowers the bandwidth capacity needs. Over the years, algorithms also got more efficient, and new ones are supported by clients and servers.
 
-<p>In practice, web developers don't need to implement compression mechanisms, both browsers and servers have it implemented already, but they have to be sure that the server is configured adequately. Compression happens at three different levels:</p>
+In practice, web developers don't need to implement compression mechanisms, both browsers and servers have it implemented already, but they have to be sure that the server is configured adequately. Compression happens at three different levels:
 
-<ul>
- <li>first some file formats are compressed with specific optimized methods,</li>
- <li>then general encryption can happen at the HTTP level (the resource is transmitted compressed from end to end),</li>
- <li>and finally compression can be defined at the connection level, between two nodes of an HTTP connection.</li>
-</ul>
+- first some file formats are compressed with specific optimized methods,
+- then general encryption can happen at the HTTP level (the resource is transmitted compressed from end to end),
+- and finally compression can be defined at the connection level, between two nodes of an HTTP connection.
 
-<h2 id="File_format_compression">File format compression</h2>
+## File format compression
 
-<p>Each data type has some redundancy, that is <em>wasted space</em>, in it. If text can typically have as much as 60% redundancy, this rate can be much higher for some other media like audio and video. Unlike text, these other media types use lot of space to store their data and the need to optimize storage and regain space was apparent very early. Engineers designed the optimized compression algorithm used by file formats designed for this specific purpose. Compression algorithms used for files can be grouped into two broad categories:</p>
+Each data type has some redundancy, that is _wasted space_, in it. If text can typically have as much as 60% redundancy, this rate can be much higher for some other media like audio and video. Unlike text, these other media types use lot of space to store their data and the need to optimize storage and regain space was apparent very early. Engineers designed the optimized compression algorithm used by file formats designed for this specific purpose. Compression algorithms used for files can be grouped into two broad categories:
 
-<ul>
- <li><em>Loss-less compression</em>, where the compression-uncompression cycle doesn't alter the data that is recovered. It matches (byte to byte) with the original.<br>
-  For images, <code>gif</code> or <code>png</code> are using loss-less compression.</li>
- <li><em>Lossy compression</em>, where the cycle alters the original data in a (hopefully) imperceptible way for the user.<br>
-  Video formats on the Web are lossy; the <code>jpeg</code> image format is also lossy.</li>
-</ul>
+- _Loss-less compression_, where the compression-uncompression cycle doesn't alter the data that is recovered. It matches (byte to byte) with the original.
+  For images, `gif` or `png` are using loss-less compression.
+- _Lossy compression_, where the cycle alters the original data in a (hopefully) imperceptible way for the user.
+  Video formats on the Web are lossy; the `jpeg` image format is also lossy.
 
-<p>Some formats can be used for both loss-less or lossy compression, like <code>webp</code>, and usually lossy algorithm can be configured to compress more or less, which then of course leads to less or more quality. For better performance of a Web site, it is ideal to compress as much as possible, while keeping an acceptable level of quality. For images, an image generated by a tool could be not optimized enough for the Web; it is recommended to use tools that will compress as much as possible with the required quality. There are <a href="https://www.creativebloq.com/design/image-compression-tools-1132865">numerous tools</a> that are specialized for this.</p>
+Some formats can be used for both loss-less or lossy compression, like `webp`, and usually lossy algorithm can be configured to compress more or less, which then of course leads to less or more quality. For better performance of a Web site, it is ideal to compress as much as possible, while keeping an acceptable level of quality. For images, an image generated by a tool could be not optimized enough for the Web; it is recommended to use tools that will compress as much as possible with the required quality. There are [numerous tools](https://www.creativebloq.com/design/image-compression-tools-1132865) that are specialized for this.
 
-<p>Lossy compression algorithms are usually more efficient than loss-less ones.</p>
+Lossy compression algorithms are usually more efficient than loss-less ones.
 
-<div class="notecard note">
-  <p><strong>Note:</strong> As compression works better on a specific kind of files, it usually provides nothing to compress them a second time. In fact, this is often counter productive as the cost of the overhead (algorithms usually need a dictionary that add to the initial size) can be higher than the extra gain in compression resulting in a larger file. Do not use the two following techniques for files in a compressed format.</p>
-</div>
+> **Note:** As compression works better on a specific kind of files, it usually provides nothing to compress them a second time. In fact, this is often counter productive as the cost of the overhead (algorithms usually need a dictionary that add to the initial size) can be higher than the extra gain in compression resulting in a larger file. Do not use the two following techniques for files in a compressed format.
 
-<h2 id="End-to-end_compression">End-to-end compression</h2>
+## End-to-end compression
 
-<p>For compression, end-to-end compression is where the largest performance improvements of Web sites reside. End-to-end compression refers to a compression of the body of a message that is done by the server and will last unchanged until it reaches the client. Whatever the intermediate nodes are, they leave the body untouched.</p>
+For compression, end-to-end compression is where the largest performance improvements of Web sites reside. End-to-end compression refers to a compression of the body of a message that is done by the server and will last unchanged until it reaches the client. Whatever the intermediate nodes are, they leave the body untouched.
 
-<p><img alt="" src="httpenco1.png"></p>
+![](httpenco1.png)
 
-<p>All modern browsers and servers do support it and the only thing to negotiate is the compression algorithm to use. These algorithm are optimized for text. In the 1990s, compression technology was advancing at a rapid pace and numerous successive algorithms have been added to the set of possible choices. Nowadays, only two are relevant: <code>gzip</code>, the most common one, and <code>br</code> the new challenger.</p>
+All modern browsers and servers do support it and the only thing to negotiate is the compression algorithm to use. These algorithm are optimized for text. In the 1990s, compression technology was advancing at a rapid pace and numerous successive algorithms have been added to the set of possible choices. Nowadays, only two are relevant: `gzip`, the most common one, and `br` the new challenger.
 
-<p>To select the algorithm to use, browsers and servers use <a href="/en-US/docs/Web/HTTP/Content_negotiation">proactive content negotiation</a>. The browser sends an {{HTTPHeader("Accept-Encoding")}} header with the algorithm it supports and its order of precedence, the server picks one, uses it to compress the body of the response and uses the {{HTTPHeader("Content-Encoding")}} header to tell the browser the algorithm it has chosen. As content negotiation has been used to choose a representation based on its encoding, the server must send a {{HTTPHeader("Vary")}} header containing at least {{HTTPHeader("Accept-Encoding")}} alongside this header in the response; that way, caches will be able to cache the different representations of the resource.</p>
+To select the algorithm to use, browsers and servers use [proactive content negotiation](/en-US/docs/Web/HTTP/Content_negotiation). The browser sends an {{HTTPHeader("Accept-Encoding")}} header with the algorithm it supports and its order of precedence, the server picks one, uses it to compress the body of the response and uses the {{HTTPHeader("Content-Encoding")}} header to tell the browser the algorithm it has chosen. As content negotiation has been used to choose a representation based on its encoding, the server must send a {{HTTPHeader("Vary")}} header containing at least {{HTTPHeader("Accept-Encoding")}} alongside this header in the response; that way, caches will be able to cache the different representations of the resource.
 
-<p><img alt="" src="httpcompression1.png"></p>
+![](httpcompression1.png)
 
-<p>As compression brings significant performance improvements, it is recommended to activate it for all files, but already compressed ones like images, audio files and videos.</p>
+As compression brings significant performance improvements, it is recommended to activate it for all files, but already compressed ones like images, audio files and videos.
 
-<p>Apache supports compression and uses <a href="https://httpd.apache.org/docs/current/mod/mod_deflate.html">mod_deflate</a>; for nginx there is <a href="https://nginx.org/en/docs/http/ngx_http_gzip_module.html">ngx_http_gzip_module</a>; for IIS, the <code><a href="https://www.iis.net/configreference/system.webserver/httpcompression">&lt;httpCompression&gt;</a></code> element.</p>
+Apache supports compression and uses [mod_deflate](https://httpd.apache.org/docs/current/mod/mod_deflate.html); for nginx there is [ngx_http_gzip_module](https://nginx.org/en/docs/http/ngx_http_gzip_module.html); for IIS, the [`<httpCompression>`](https://www.iis.net/configreference/system.webserver/httpcompression) element.
 
-<h2 id="Hop-by-hop_compression">Hop-by-hop compression</h2>
+## Hop-by-hop compression
 
-<p>Hop-by-hop compression, though similar to end-to-end compression, differs by one fundamental element: the compression doesn't happen on the resource in the server, creating a specific representation that is then transmitted, but on the body of the message between any two nodes on the path between the client and the server. Connections between successive intermediate nodes may apply a <em>different</em> compression.</p>
+Hop-by-hop compression, though similar to end-to-end compression, differs by one fundamental element: the compression doesn't happen on the resource in the server, creating a specific representation that is then transmitted, but on the body of the message between any two nodes on the path between the client and the server. Connections between successive intermediate nodes may apply a _different_ compression.
 
-<p><img alt="" src="httpte1.png"></p>
+![](httpte1.png)
 
-<p>To do this, HTTP uses a mechanism similar to the content negotiation for end-to-end compression: the node transmitting the request advertizes its will using the {{HTTPHeader("TE")}} header and the other node chooses the adequate method, applies it, and indicates its choice with the {{HTTPHeader("Transfer-Encoding")}} header.</p>
+To do this, HTTP uses a mechanism similar to the content negotiation for end-to-end compression: the node transmitting the request advertizes its will using the {{HTTPHeader("TE")}} header and the other node chooses the adequate method, applies it, and indicates its choice with the {{HTTPHeader("Transfer-Encoding")}} header.
 
-<p><img alt="" src="httpcomp2.png"></p>
+![](httpcomp2.png)
 
-<p>In practice, hop-by-hop compression is transparent for the server and the client, and is rarely used. {{HTTPHeader("TE")}} and {{HTTPHeader("Transfer-Encoding")}} are mostly used to send a response by chunks, allowing to start transmitting a resource without knowing its length.</p>
+In practice, hop-by-hop compression is transparent for the server and the client, and is rarely used. {{HTTPHeader("TE")}} and {{HTTPHeader("Transfer-Encoding")}} are mostly used to send a response by chunks, allowing to start transmitting a resource without knowing its length.
 
-<p>Note that using {{HTTPHeader("Transfer-Encoding")}} and compression at the hop level is so rare that most servers, like Apache, nginx, or IIS, have no easy way to configure it. Such configuration usually happens at the proxy level.</p>
+Note that using {{HTTPHeader("Transfer-Encoding")}} and compression at the hop level is so rare that most servers, like Apache, nginx, or IIS, have no easy way to configure it. Such configuration usually happens at the proxy level.
diff --git a/files/en-us/web/http/conditional_requests/index.md b/files/en-us/web/http/conditional_requests/index.md
index ad2f66980c0c7dc..e02423768c11579 100644
--- a/files/en-us/web/http/conditional_requests/index.md
+++ b/files/en-us/web/http/conditional_requests/index.md
@@ -6,142 +6,134 @@ tags:
   - Guide
   - HTTP
 ---
-<p>{{HTTPSidebar}}</p>
+{{HTTPSidebar}}
 
-<p class="summary">HTTP has a concept of <em>conditional requests</em>, where the result, and even the success of a request, can be changed by comparing the affected resources with the value of a <em>validator</em>. Such requests can be useful to validate the content of a cache, and sparing a useless control, to verify the integrity of a document, like when resuming a download, or when preventing to lose updates when uploading or modifying a document on the server.</p>
+HTTP has a concept of _conditional requests_, where the result, and even the success of a request, can be changed by comparing the affected resources with the value of a _validator_. Such requests can be useful to validate the content of a cache, and sparing a useless control, to verify the integrity of a document, like when resuming a download, or when preventing to lose updates when uploading or modifying a document on the server.
 
-<h2 id="Principles">Principles</h2>
+## Principles
 
-<p>HTTP conditional requests are requests that are executed differently, depending on the value of specific headers. These headers define a precondition, and the result of the request will be different if the precondition is matched or not.</p>
+HTTP conditional requests are requests that are executed differently, depending on the value of specific headers. These headers define a precondition, and the result of the request will be different if the precondition is matched or not.
 
-<p>The different behaviors are defined by the method of the request used, and by the set of headers used for a precondition:</p>
+The different behaviors are defined by the method of the request used, and by the set of headers used for a precondition:
 
-<ul>
- <li>for {{glossary("Safe/HTTP", "safe")}} methods, like {{HTTPMethod("GET")}}, which usually tries to fetch a document, the conditional request can be used to send back the document, if relevant only. Therefore, this spares bandwidth.</li>
- <li>for {{glossary("Safe/HTTP", "unsafe")}} methods, like {{HTTPMethod("PUT")}}, which usually uploads a document, the conditional request can be used to upload the document, only if the original it is based on is the same as that stored on the server.</li>
-</ul>
+- for {{glossary("Safe/HTTP", "safe")}} methods, like {{HTTPMethod("GET")}}, which usually tries to fetch a document, the conditional request can be used to send back the document, if relevant only. Therefore, this spares bandwidth.
+- for {{glossary("Safe/HTTP", "unsafe")}} methods, like {{HTTPMethod("PUT")}}, which usually uploads a document, the conditional request can be used to upload the document, only if the original it is based on is the same as that stored on the server.
 
-<h2 id="Validators">Validators</h2>
+## Validators
 
-<p>All conditional headers try to check if the resource stored on the server matches a specific version. To achieve this, the conditional requests need to indicate the version of the resource. As comparing the whole resource byte to byte is impracticable, and not always what is wanted, the request transmits a value describing the version. Such values are called <em>validators</em>, and are of two kinds:</p>
+All conditional headers try to check if the resource stored on the server matches a specific version. To achieve this, the conditional requests need to indicate the version of the resource. As comparing the whole resource byte to byte is impracticable, and not always what is wanted, the request transmits a value describing the version. Such values are called _validators_, and are of two kinds:
 
-<ul>
- <li>the date of last modification of the document, the <em>last-modified</em> date.</li>
- <li>an opaque string, uniquely identifying each version, called the <em>entity tag</em>, or the <em>etag</em>.</li>
-</ul>
+- the date of last modification of the document, the _last-modified_ date.
+- an opaque string, uniquely identifying each version, called the _entity tag_, or the _etag_.
 
-<p>Comparing versions of the same resource is a bit tricky: depending on the context, there are two kinds of <em>equality checks</em>:</p>
+Comparing versions of the same resource is a bit tricky: depending on the context, there are two kinds of _equality checks_:
 
-<ul>
- <li><em>Strong validation</em> is used when byte to byte identity is expected, for example when resuming a download.</li>
- <li><em>Weak validation</em> is used when the user-agent only needs to determine if the two resources have the same content. This is even if they are minor differences; like different ads, or a footer with a different date.</li>
-</ul>
+- _Strong validation_ is used when byte to byte identity is expected, for example when resuming a download.
+- _Weak validation_ is used when the user-agent only needs to determine if the two resources have the same content. This is even if they are minor differences; like different ads, or a footer with a different date.
 
-<p>The kind of validation is independent of the validator used. Both {{HTTPHeader("Last-Modified")}} and {{HTTPHeader("ETag")}} allow both types of validation, though the complexity to implement it on the server side may vary. HTTP uses strong validation by default, and it specifies when weak validation can be used.</p>
+The kind of validation is independent of the validator used. Both {{HTTPHeader("Last-Modified")}} and {{HTTPHeader("ETag")}} allow both types of validation, though the complexity to implement it on the server side may vary. HTTP uses strong validation by default, and it specifies when weak validation can be used.
 
-<h3 id="Strong_validation">Strong validation</h3>
+### Strong validation
 
-<p>Strong validation consists of guaranteeing that the resource is, byte to byte, identical to the one it is compared too. This is mandatory for some conditional headers, and the default for the others. Strong validation is very strict and may be difficult to guarantee at the server level, but it does guarantee no data loss at any time, sometimes at the expense of performance.</p>
+Strong validation consists of guaranteeing that the resource is, byte to byte, identical to the one it is compared too. This is mandatory for some conditional headers, and the default for the others. Strong validation is very strict and may be difficult to guarantee at the server level, but it does guarantee no data loss at any time, sometimes at the expense of performance.
 
-<p>It is quite difficult to have a unique identifier for strong validation with {{HTTPHeader("Last-Modified")}}. Often this is done using an {{HTTPHeader("ETag")}} with the MD5 hash of the resource (or a derivative).</p>
+It is quite difficult to have a unique identifier for strong validation with {{HTTPHeader("Last-Modified")}}. Often this is done using an {{HTTPHeader("ETag")}} with the MD5 hash of the resource (or a derivative).
 
-<h3 id="Weak_validation">Weak validation</h3>
+### Weak validation
 
-<p>Weak validation differs from strong validation, as it considers two versions of the document as identical if the content is equivalent. For example, a page that would differ from another only by a different date in its footer, or different advertising, would be considered <em>identical</em> to the other with weak validation. These same two versions are considered <em>different</em> when using strong validation. Building a system of etags that creates weak validation may be complex, as it involves knowing the importance of the different elements of a page, but is very useful towards optimizing cache performance.</p>
+Weak validation differs from strong validation, as it considers two versions of the document as identical if the content is equivalent. For example, a page that would differ from another only by a different date in its footer, or different advertising, would be considered _identical_ to the other with weak validation. These same two versions are considered _different_ when using strong validation. Building a system of etags that creates weak validation may be complex, as it involves knowing the importance of the different elements of a page, but is very useful towards optimizing cache performance.
 
-<h2 id="Conditional_headers">Conditional headers</h2>
+## Conditional headers
 
-<p>Several HTTP headers, called conditional headers, lead to conditional requests. These are:</p>
+Several HTTP headers, called conditional headers, lead to conditional requests. These are:
 
-<dl>
- <dt>{{HTTPHeader("If-Match")}}</dt>
- <dd>Succeeds if the {{HTTPHeader("ETag")}} of the distant resource is equal to one listed in this header. By default, unless the etag is prefixed with <code>'W/'</code>, it performs a strong validation.</dd>
- <dt>{{HTTPHeader("If-None-Match")}}</dt>
- <dd>Succeeds if the {{HTTPHeader("ETag")}} of the distant resource is different to each listed in this header. By default, unless the etag is prefixed with <code>'W/'</code>, it performs a strong validation.</dd>
- <dt>{{HTTPHeader("If-Modified-Since")}}</dt>
- <dd>Succeeds if the {{HTTPHeader("Last-Modified")}} date of the distant resource is more recent than the one given in this header.</dd>
- <dt>{{HTTPHeader("If-Unmodified-Since")}}</dt>
- <dd>Succeeds if the {{HTTPHeader("Last-Modified")}} date of the distant resource is older or the same than the one given in this header.</dd>
- <dt>{{HTTPHeader("If-Range")}}</dt>
- <dd>Similar to {{HTTPHeader("If-Match")}}, or {{HTTPHeader("If-Unmodified-Since")}}, but can have only one single etag, or one date. If it fails, the range request fails, and instead of a {{HTTPStatus("206")}} <code>Partial Content</code> response, a {{HTTPStatus("200")}} <code>OK</code> is sent with the complete resource.</dd>
-</dl>
+- {{HTTPHeader("If-Match")}}
+  - : Succeeds if the {{HTTPHeader("ETag")}} of the distant resource is equal to one listed in this header. By default, unless the etag is prefixed with `'W/'`, it performs a strong validation.
+- {{HTTPHeader("If-None-Match")}}
+  - : Succeeds if the {{HTTPHeader("ETag")}} of the distant resource is different to each listed in this header. By default, unless the etag is prefixed with `'W/'`, it performs a strong validation.
+- {{HTTPHeader("If-Modified-Since")}}
+  - : Succeeds if the {{HTTPHeader("Last-Modified")}} date of the distant resource is more recent than the one given in this header.
+- {{HTTPHeader("If-Unmodified-Since")}}
+  - : Succeeds if the {{HTTPHeader("Last-Modified")}} date of the distant resource is older or the same than the one given in this header.
+- {{HTTPHeader("If-Range")}}
+  - : Similar to {{HTTPHeader("If-Match")}}, or {{HTTPHeader("If-Unmodified-Since")}}, but can have only one single etag, or one date. If it fails, the range request fails, and instead of a {{HTTPStatus("206")}} `Partial Content` response, a {{HTTPStatus("200")}} `OK` is sent with the complete resource.
 
-<h2 id="Use_cases">Use cases</h2>
+## Use cases
 
-<h3 id="Cache_update">Cache update</h3>
+### Cache update
 
-<p>The most common use case for conditional requests is updating a cache. With an empty cache, or without a cache, the requested resource is sent back with a status of {{HTTPStatus("200")}} <code>OK</code>.</p>
+The most common use case for conditional requests is updating a cache. With an empty cache, or without a cache, the requested resource is sent back with a status of {{HTTPStatus("200")}} `OK`.
 
-<p><img alt="The request issued when the cache is empty triggers the resource to be downloaded, with both validator value sent as headers. The cache is then filled." src="cache1.png"></p>
+![The request issued when the cache is empty triggers the resource to be downloaded, with both validator value sent as headers. The cache is then filled.](cache1.png)
 
-<p>Together with the resource, the validators are sent in the headers. In this example, both {{HTTPHeader("Last-Modified")}} and {{HTTPHeader("ETag")}} are sent, but it could equally have been only one of them. These validators are cached with the resource (like all headers) and will be used to craft conditional requests, once the cache becomes stale.</p>
+Together with the resource, the validators are sent in the headers. In this example, both {{HTTPHeader("Last-Modified")}} and {{HTTPHeader("ETag")}} are sent, but it could equally have been only one of them. These validators are cached with the resource (like all headers) and will be used to craft conditional requests, once the cache becomes stale.
 
-<p>As long as the cache is not stale, no requests are issued at all. But once it has become stale, this is mostly controlled by the {{HTTPHeader("Cache-Control")}} header, the client doesn't use the cached value directly but issues a <em>conditional request</em>. The value of the validator is used as a parameter of the {{HTTPHeader("If-Modified-Since")}} and {{HTTPHeader("If-Match")}} headers.</p>
+As long as the cache is not stale, no requests are issued at all. But once it has become stale, this is mostly controlled by the {{HTTPHeader("Cache-Control")}} header, the client doesn't use the cached value directly but issues a _conditional request_. The value of the validator is used as a parameter of the {{HTTPHeader("If-Modified-Since")}} and {{HTTPHeader("If-Match")}} headers.
 
-<p>If the resource has not changed, the server sends back a {{HTTPStatus("304")}} <code>Not Modified</code> response. This makes the cache fresh again, and the client uses the cached resource. Although there is a response/request round-trip that consumes some resources, this is more efficient than to transmit the whole resource over the wire again.</p>
+If the resource has not changed, the server sends back a {{HTTPStatus("304")}} `Not Modified` response. This makes the cache fresh again, and the client uses the cached resource. Although there is a response/request round-trip that consumes some resources, this is more efficient than to transmit the whole resource over the wire again.
 
-<p><img alt="With a stale cache, the conditional request is sent. The server can determine if the resource changed, and, as in this case, decide not to send it again as it is the same." src="httpcache2.png"></p>
+![With a stale cache, the conditional request is sent. The server can determine if the resource changed, and, as in this case, decide not to send it again as it is the same.](httpcache2.png)
 
-<p>If the resource has changed, the server just sends back a {{HTTPStatus("200")}}<code> OK</code> response, with the new version of the resource, like if the request wasn't conditional and the client uses this new resource (and caches it).</p>
+If the resource has changed, the server just sends back a {{HTTPStatus("200")}}` OK` response, with the new version of the resource, like if the request wasn't conditional and the client uses this new resource (and caches it).
 
-<p><img alt="In the case where the resource was changed, it is sent back as if the request wasn't conditional." src="httpcache3.png"></p>
+![In the case where the resource was changed, it is sent back as if the request wasn't conditional.](httpcache3.png)
 
-<p>Besides the setting of the validators on the server side, this mechanism is transparent: all browsers manage a cache and send such conditional requests without any special work to be done by Web developers.</p>
+Besides the setting of the validators on the server side, this mechanism is transparent: all browsers manage a cache and send such conditional requests without any special work to be done by Web developers.
 
-<h3 id="Integrity_of_a_partial_download">Integrity of a partial download</h3>
+### Integrity of a partial download
 
-<p>Partial downloading of files is a functionality of HTTP that allows to resume previous operations, saving bandwidth and time, by keeping the already obtained information:</p>
+Partial downloading of files is a functionality of HTTP that allows to resume previous operations, saving bandwidth and time, by keeping the already obtained information:
 
-<p><img alt="A download has been stopped and only partial content has been retrieved." src="httpresume1.png"></p>
+![A download has been stopped and only partial content has been retrieved.](httpresume1.png)
 
-<p>A server supporting partial downloads broadcasts this by sending the {{HTTPHeader("Accept-Ranges")}} header. Once this happens, the client can resume a download by sending a {{HTTPHeader("Ranges")}} header with the missing ranges:</p>
+A server supporting partial downloads broadcasts this by sending the {{HTTPHeader("Accept-Ranges")}} header. Once this happens, the client can resume a download by sending a {{HTTPHeader("Ranges")}} header with the missing ranges:
 
-<p><img alt="The client resumes the requests by indicating the range he needs and preconditions checking the validators of the partially obtained request." src="httpresume2.png"></p>
+![The client resumes the requests by indicating the range he needs and preconditions checking the validators of the partially obtained request.](httpresume2.png)
 
-<p>The principle is simple, but there is one potential problem: if the downloaded resource has been modified between both downloads, the obtained ranges will correspond to two different versions of the resource, and the final document will be corrupted.</p>
+The principle is simple, but there is one potential problem: if the downloaded resource has been modified between both downloads, the obtained ranges will correspond to two different versions of the resource, and the final document will be corrupted.
 
-<p>To prevent this, conditional requests are used. For ranges, there are two ways of doing this. The more flexible one makes use of {{HTTPHeader("If-Unmodified-Since")}} and {{HTTPHeader("If-Match")}} and the server returns an error if the precondition fails; the client then restarts the download from the beginning:</p>
+To prevent this, conditional requests are used. For ranges, there are two ways of doing this. The more flexible one makes use of {{HTTPHeader("If-Unmodified-Since")}} and {{HTTPHeader("If-Match")}} and the server returns an error if the precondition fails; the client then restarts the download from the beginning:
 
-<p><img alt="When the partially downloaded resource has been modified, the preconditions will fail and the resource will have to be downloaded again completely." src="httpresume3.png"></p>
+![When the partially downloaded resource has been modified, the preconditions will fail and the resource will have to be downloaded again completely.](httpresume3.png)
 
-<p>Even if this method works, it adds an extra response/request exchange when the document has been changed. This impairs performance, and HTTP has a specific header to avoid this scenario: {{HTTPHeader("If-Range")}}:</p>
+Even if this method works, it adds an extra response/request exchange when the document has been changed. This impairs performance, and HTTP has a specific header to avoid this scenario: {{HTTPHeader("If-Range")}}:
 
-<p><img alt="The If-Range headers allows the server to directly send back the complete resource if it has been modified, no need to send a 412 error and wait for the client to re-initiate the download." src="httpresume4.png"></p>
+![The If-Range headers allows the server to directly send back the complete resource if it has been modified, no need to send a 412 error and wait for the client to re-initiate the download.](httpresume4.png)
 
-<p>This solution is more efficient, but slightly less flexible, as only one etag can be used in the condition. Rarely is such additional flexibility needed.</p>
+This solution is more efficient, but slightly less flexible, as only one etag can be used in the condition. Rarely is such additional flexibility needed.
 
-<h3 id="Avoiding_the_lost_update_problem_with_optimistic_locking">Avoiding the lost update problem with optimistic locking</h3>
+### Avoiding the lost update problem with optimistic locking
 
-<p>A common operation in Web applications is to <em>update</em> a remote document. This is very common in any file system or source control applications, but any application that allows to store remote resources needs such a mechanism. Common Web sites, like wikis and other CMS, have such a need.</p>
+A common operation in Web applications is to _update_ a remote document. This is very common in any file system or source control applications, but any application that allows to store remote resources needs such a mechanism. Common Web sites, like wikis and other CMS, have such a need.
 
-<p>With the {{HTTPMethod("PUT")}} method you are able to implement this. The client first reads the original files, modifies them, and finally pushes them to the server:</p>
+With the {{HTTPMethod("PUT")}} method you are able to implement this. The client first reads the original files, modifies them, and finally pushes them to the server:
 
-<p><img alt="Updating a file with a PUT is very simple when concurrency is not involved." src="httplock1.png"></p>
+![Updating a file with a PUT is very simple when concurrency is not involved.](httplock1.png)
 
-<p>Unfortunately, things get a little inaccurate as soon as we take into account concurrency. While a client is locally modifying its new copy of the resource, a second client can fetch the same resource and do the same on its copy. What happens next is very unfortunate: when they commit back to the server, the modifications from the first client are discarded by the next client push, as this second client is unaware of the first client's changes to the resource. The decision on who wins, is not communicated to the other party. Which client's changes are to be kept, will vary with the speed they commit; this depends on the performance of the clients, of the server, and even of the human editing the document at the client. The winner will change from one time to the next. This is a {{glossary("race condition")}} and leads to problematic behaviors, which are difficult to detect and to debug:</p>
+Unfortunately, things get a little inaccurate as soon as we take into account concurrency. While a client is locally modifying its new copy of the resource, a second client can fetch the same resource and do the same on its copy. What happens next is very unfortunate: when they commit back to the server, the modifications from the first client are discarded by the next client push, as this second client is unaware of the first client's changes to the resource. The decision on who wins, is not communicated to the other party. Which client's changes are to be kept, will vary with the speed they commit; this depends on the performance of the clients, of the server, and even of the human editing the document at the client. The winner will change from one time to the next. This is a {{glossary("race condition")}} and leads to problematic behaviors, which are difficult to detect and to debug:
 
-<p><img alt="When several clients update the same resource in parallel, we are facing a race condition: the slowest win, and the others don't even know they lost. Problematic!" src="httplock2.png"></p>
+![When several clients update the same resource in parallel, we are facing a race condition: the slowest win, and the others don't even know they lost. Problematic!](httplock2.png)
 
-<p>There is no way to deal with this problem without annoying one of the two clients. However, lost updates and race conditions are to be avoided. We want predictable results, and expect that the clients are notified when their changes are rejected.</p>
+There is no way to deal with this problem without annoying one of the two clients. However, lost updates and race conditions are to be avoided. We want predictable results, and expect that the clients are notified when their changes are rejected.
 
-<p>Conditional requests allow implementing the <em>optimistic locking algorithm</em> (used by most wikis or source control systems). The concept is to allow all clients to get copies of the resource, then let them modify it locally, controlling concurrency by successfully allowing the first client submitting an update. All subsequent updates, based on the now obsolete version of the resource, are rejected:</p>
+Conditional requests allow implementing the _optimistic locking algorithm_ (used by most wikis or source control systems). The concept is to allow all clients to get copies of the resource, then let them modify it locally, controlling concurrency by successfully allowing the first client submitting an update. All subsequent updates, based on the now obsolete version of the resource, are rejected:
 
-<p><img alt="Conditional requests allow to implement optimistic locking: now the quickest wins, and the others get an error." src="httplock3.png"></p>
+![Conditional requests allow to implement optimistic locking: now the quickest wins, and the others get an error.](httplock3.png)
 
-<p>This is implemented using the {{HTTPHeader("If-Match")}} or {{HTTPHeader("If-Unmodified-Since")}} headers. If the etag doesn't match the original file, or if the file has been modified since it has been obtained, the change is rejected with a {{HTTPStatus("412")}} <code>Precondition Failed</code> error. It is then up to the client to deal with the error: either by notifying the user to start again (this time on the newest version), or by showing the user a <em>diff</em> of both versions, helping them decide which changes they wish to keep.</p>
+This is implemented using the {{HTTPHeader("If-Match")}} or {{HTTPHeader("If-Unmodified-Since")}} headers. If the etag doesn't match the original file, or if the file has been modified since it has been obtained, the change is rejected with a {{HTTPStatus("412")}} `Precondition Failed` error. It is then up to the client to deal with the error: either by notifying the user to start again (this time on the newest version), or by showing the user a _diff_ of both versions, helping them decide which changes they wish to keep.
 
-<h3 id="Dealing_with_the_first_upload_of_a_resource">Dealing with the first upload of a resource</h3>
+### Dealing with the first upload of a resource
 
-<p>The first upload of a resource is an edge case of the previous. Like any update of a resource, it is subject to a race condition if two clients try to perform at the similar times. To prevent this, conditional requests can be used: by adding {{HTTPHeader("If-None-Match")}} with the special value of <code>'*'</code>, representing any etag. The request will succeed, only if the resource didn't exist before:</p>
+The first upload of a resource is an edge case of the previous. Like any update of a resource, it is subject to a race condition if two clients try to perform at the similar times. To prevent this, conditional requests can be used: by adding {{HTTPHeader("If-None-Match")}} with the special value of `'*'`, representing any etag. The request will succeed, only if the resource didn't exist before:
 
-<p><img alt="Like for a regular upload, the first upload of a resource is subject to a race condition: If-None-Match can prevent it." src="httpfirst.png"></p>
+![Like for a regular upload, the first upload of a resource is subject to a race condition: If-None-Match can prevent it.](httpfirst.png)
 
-<p><code>If-None-Match</code> will only work with HTTP/1.1 (and later) compliant servers. If unsure if the server will be compliant, you need first to issue a {{HTTPMethod("HEAD")}} request to the resource to check this.</p>
+`If-None-Match` will only work with HTTP/1.1 (and later) compliant servers. If unsure if the server will be compliant, you need first to issue a {{HTTPMethod("HEAD")}} request to the resource to check this.
 
-<h2 id="Conclusion">Conclusion</h2>
+## Conclusion
 
-<p>Conditional requests are a key feature of HTTP, and allow the building of efficient and complex applications. For caching or resuming downloads, the only work required for webmasters is to configure the server correctly; setting correct etags in some environments can be tricky. Once achieved, the browser will serve the expected conditional requests.</p>
+Conditional requests are a key feature of HTTP, and allow the building of efficient and complex applications. For caching or resuming downloads, the only work required for webmasters is to configure the server correctly; setting correct etags in some environments can be tricky. Once achieved, the browser will serve the expected conditional requests.
 
-<p>For locking mechanisms, it is the opposite: Web developers need to issue a request with the proper headers, while webmasters can mostly rely on the application to carry out the checks for them.</p>
+For locking mechanisms, it is the opposite: Web developers need to issue a request with the proper headers, while webmasters can mostly rely on the application to carry out the checks for them.
 
-<p>In both cases it's clear, conditional requests are a fundamental feature behind the Web.</p>
+In both cases it's clear, conditional requests are a fundamental feature behind the Web.
diff --git a/files/en-us/web/http/configuring_servers_for_ogg_media/index.md b/files/en-us/web/http/configuring_servers_for_ogg_media/index.md
index ba76d6e2af3b321..ea9d1d65ad3bbc5 100644
--- a/files/en-us/web/http/configuring_servers_for_ogg_media/index.md
+++ b/files/en-us/web/http/configuring_servers_for_ogg_media/index.md
@@ -8,114 +8,105 @@ tags:
   - Ogg
   - Video
 ---
-<div>{{HTTPSidebar}}</div>
+{{HTTPSidebar}}
 
-<p class="summary">HTML {{HTMLElement("audio")}} and {{HTMLElement("video")}} elements allow media presentation without the need for the user to install any plug-ins or other software to do so.
-  This guide covers a few server configuration changes that may be necessary for your web server to correctly serve Ogg media files.
-  This information may also be useful if you encounter other media types your server isn't already configured to recognize.</p>
+HTML {{HTMLElement("audio")}} and {{HTMLElement("video")}} elements allow media presentation without the need for the user to install any plug-ins or other software to do so.
+This guide covers a few server configuration changes that may be necessary for your web server to correctly serve Ogg media files.
+This information may also be useful if you encounter other media types your server isn't already configured to recognize.
 
-<h2 id="Serve_media_with_the_correct_MIME_type">Serve media with the correct MIME type</h2>
+## Serve media with the correct MIME type
 
-<p><code>*.ogg</code> and <code>*.ogv</code> files containing video (possibly with an audio track as well, of course), should be served with the <code>video/ogg</code> MIME type. <code>*.oga</code> and <code>*.ogg</code> files containing only audio should be served with the <code>audio/ogg</code> MIME type.</p>
+`*.ogg` and `*.ogv` files containing video (possibly with an audio track as well, of course), should be served with the `video/ogg` MIME type. `*.oga` and `*.ogg` files containing only audio should be served with the `audio/ogg` MIME type.
 
-<p>If you don't know whether the Ogg file contains audio or video, you can serve it with the MIME type <code>application/ogg</code>, and the browser will treat it as a video file.</p>
+If you don't know whether the Ogg file contains audio or video, you can serve it with the MIME type `application/ogg`, and the browser will treat it as a video file.
 
-<p>Most servers don't by default serve Ogg media with the correct MIME types, so you'll likely need to add the appropriate configuration for this.</p>
+Most servers don't by default serve Ogg media with the correct MIME types, so you'll likely need to add the appropriate configuration for this.
 
-<p>For Apache, you can add the following to your configuration:</p>
+For Apache, you can add the following to your configuration:
 
-<pre>AddType audio/ogg .oga
-AddType video/ogg .ogv
-AddType application/ogg .ogg
-</pre>
+    AddType audio/ogg .oga
+    AddType video/ogg .ogv
+    AddType application/ogg .ogg
 
-<p>You can find specific information about possible media file types and the codecs used within them in our comprehensive <a href="/en-US/docs/Web/Media/Formats">guide to media types and formats on the web</a>. In particular, the article on <a href="/en-US/docs/Web/Media/Formats/Containers">media container formats</a> will be especially helpful when configuring servers to host media properly.</p>
+You can find specific information about possible media file types and the codecs used within them in our comprehensive [guide to media types and formats on the web](/en-US/docs/Web/Media/Formats). In particular, the article on [media container formats](/en-US/docs/Web/Media/Formats/Containers) will be especially helpful when configuring servers to host media properly.
 
-<h2 id="Handle_HTTP_1.1_byte_range_requests_correctly">Handle HTTP 1.1 byte range requests correctly</h2>
+## Handle HTTP 1.1 byte range requests correctly
 
-<p>In order to support seeking and playing back regions of the media that aren't yet downloaded, Gecko uses HTTP 1.1 byte-range requests to retrieve the media from the seek target position. In addition, Gecko uses byte-range requests to seek to the end of the media (assuming you serve the {{HTTPHeader("Content-Length")}} header) in order to determine the duration of the media.</p>
+In order to support seeking and playing back regions of the media that aren't yet downloaded, Gecko uses HTTP 1.1 byte-range requests to retrieve the media from the seek target position. In addition, Gecko uses byte-range requests to seek to the end of the media (assuming you serve the {{HTTPHeader("Content-Length")}} header) in order to determine the duration of the media.
 
-<p>Your server should accept the {{HTTPHeader("Accept-Ranges")}}<code>: bytes</code> HTTP header if it can accept byte-range requests. It must return {{HTTPStatus("206")}}<code>: Partial content</code> to all byte range requests; otherwise, browsers can't be sure you actually support byte range requests.</p>
+Your server should accept the {{HTTPHeader("Accept-Ranges")}}`: bytes` HTTP header if it can accept byte-range requests. It must return {{HTTPStatus("206")}}`: Partial content` to all byte range requests; otherwise, browsers can't be sure you actually support byte range requests.
 
-<p>Your server must also return <code>206: Partial Content</code> for the request <code>Range: bytes=0-</code> as well.</p>
+Your server must also return `206: Partial Content` for the request `Range: bytes=0-` as well.
 
-<h2 id="Include_regular_key_frames">Include regular key frames</h2>
+## Include regular key frames
 
-<p>When the browser seeks through Ogg media to a specified time, it has to seek to the nearest key frame before the seek target, then download and decode the video from there until the requested target time. The farther apart your key frames are, the longer this takes, so it's helpful to include key frames at regular intervals.</p>
+When the browser seeks through Ogg media to a specified time, it has to seek to the nearest key frame before the seek target, then download and decode the video from there until the requested target time. The farther apart your key frames are, the longer this takes, so it's helpful to include key frames at regular intervals.
 
-<p>By default, <a href="https://v2v.cc/~j/ffmpeg2theora/"><code>ffmpeg2theora</code></a> uses one key frame every 64 frames (or about every 2 seconds at 30 frames per second), which works pretty well.</p>
+By default, [`ffmpeg2theora`](https://v2v.cc/~j/ffmpeg2theora/) uses one key frame every 64 frames (or about every 2 seconds at 30 frames per second), which works pretty well.
 
-<div class="notecard note">
-  <p><strong>Note:</strong> Of course, the more key frames you use, the larger your video file is, so you may need to experiment a bit to get the right balance between file size and seek performance.</p>
-</div>
+> **Note:** Of course, the more key frames you use, the larger your video file is, so you may need to experiment a bit to get the right balance between file size and seek performance.
 
-<h2 id="Consider_using_the_preload_attribute">Consider using the preload attribute</h2>
+## Consider using the preload attribute
 
-<p>The HTML {{HTMLElement("audio")}} and {{HTMLElement("video")}} elements provide the <code>preload</code> attribute, which tells the browser to attempt to download the entire media when the page loads. Without <code>preload</code>, the browser only downloads enough of the media to display the first video frame, and to determine the media's duration.</p>
+The HTML {{HTMLElement("audio")}} and {{HTMLElement("video")}} elements provide the `preload` attribute, which tells the browser to attempt to download the entire media when the page loads. Without `preload`, the browser only downloads enough of the media to display the first video frame, and to determine the media's duration.
 
-<p><code>preload</code> is off by default, so if getting to video is the point of your web page, your users may appreciate it if you include <code>preload</code> in your video elements. using <code>preload="metadata"</code> will preload the media file's metadata and possibly the first few frames of video. Setting <code>payload</code> to <code>auto</code> tells the browser to automatically begin downloading the media as soon as the page is loaded, under the assumption that the user will play it.</p>
+`preload` is off by default, so if getting to video is the point of your web page, your users may appreciate it if you include `preload` in your video elements. using `preload="metadata"` will preload the media file's metadata and possibly the first few frames of video. Setting `payload` to `auto` tells the browser to automatically begin downloading the media as soon as the page is loaded, under the assumption that the user will play it.
 
-<h2 id="Configuration_for_older_Firefox_versions">Configuration for older Firefox versions</h2>
+## Configuration for older Firefox versions
 
-<h3 id="Serve_X-Content-Duration_headers">Serve X-Content-Duration headers</h3>
+### Serve X-Content-Duration headers
 
-<div class="notecard note">
-  <p><strong>Note:</strong> As of <a href="/en-US/docs/Mozilla/Firefox/Releases/41">Firefox 41</a>, the <code>X-Content-Duration</code> header is no longer supported. See {{Bug(1160695)}} for more details.</p>
-</div>
+> **Note:** As of [Firefox 41](/en-US/docs/Mozilla/Firefox/Releases/41), the `X-Content-Duration` header is no longer supported. See {{Bug(1160695)}} for more details.
 
-<p>The Ogg format doesn't encapsulate the duration of media, so for the progress bar on the video controls to display the duration of the video, Gecko needs to determine the length of the media using other means.</p>
+The Ogg format doesn't encapsulate the duration of media, so for the progress bar on the video controls to display the duration of the video, Gecko needs to determine the length of the media using other means.
 
-<p>There are two ways Gecko can do this. The best way is to offer an <code>X-Content-Duration</code> header when serving Ogg media files. This header provides the duration of the video in seconds (<strong>not</strong> in HH:MM:SS format) as a floating-point value.</p>
+There are two ways Gecko can do this. The best way is to offer an `X-Content-Duration` header when serving Ogg media files. This header provides the duration of the video in seconds (**not** in HH:MM:SS format) as a floating-point value.
 
-<p>For example, if the video is 1 minute and 32.6 seconds long, this header would be:</p>
+For example, if the video is 1 minute and 32.6 seconds long, this header would be:
 
-<pre>X-Content-Duration: 92.6
-</pre>
+    X-Content-Duration: 92.6
 
-<p>If your server provides the <code>X-Content-Duration</code> header when serving Ogg media, Gecko doesn't have to do any extra HTTP requests to seek to the end of the file to calculate its duration. This makes the entire process much more efficient as well as more accurate.</p>
+If your server provides the `X-Content-Duration` header when serving Ogg media, Gecko doesn't have to do any extra HTTP requests to seek to the end of the file to calculate its duration. This makes the entire process much more efficient as well as more accurate.
 
-<p>As an inferior alternative, Gecko can estimate the video length based on the Content-Length. See next point.</p>
+As an inferior alternative, Gecko can estimate the video length based on the Content-Length. See next point.
 
-<h3 id="Don't_use_HTTP_compression_for_media_files">Don't use HTTP compression for media files</h3>
+### Don't use HTTP compression for media files
 
-<p>One common way to reduce the load on a web server is to use <a href="https://betterexplained.com/articles/how-to-optimize-your-site-with-gzip-compression/">gzip or deflate compression</a> when serving to a supporting web browser.</p>
+One common way to reduce the load on a web server is to use [gzip or deflate compression](https://betterexplained.com/articles/how-to-optimize-your-site-with-gzip-compression/) when serving to a supporting web browser.
 
-<p>Although it's unlikely, it's possible the browser may advertise that it supports HTTP compression (gzip/deflate) using the <code>Accept-Encoding: gzip,deflate</code> header when requesting media files. Your server should be configured to not do so. The data in media files is already compressed, so you won't get any real benefit from compression, and the use of compression makes it impossible for the browser to properly seek the video or determine its duration.</p>
+Although it's unlikely, it's possible the browser may advertise that it supports HTTP compression (gzip/deflate) using the `Accept-Encoding: gzip,deflate` header when requesting media files. Your server should be configured to not do so. The data in media files is already compressed, so you won't get any real benefit from compression, and the use of compression makes it impossible for the browser to properly seek the video or determine its duration.
 
-<p>Another probelm with allowing HTTP compression for media streaming: Apache servers don't send the {{HTTPHeader("Content-Length")}} response header if gzip encoding is used.</p>
+Another probelm with allowing HTTP compression for media streaming: Apache servers don't send the {{HTTPHeader("Content-Length")}} response header if gzip encoding is used.
 
-<h3 id="Getting_the_duration_of_Ogg_media">Getting the duration of Ogg media</h3>
+### Getting the duration of Ogg media
 
-<p>You can use the <code>oggz-info</code> tool to get the media duration; this tool is included with the <a href="https://www.xiph.org/oggz/"><code>oggz-tools</code></a> package. The output from <code>oggz-info</code> looks like this:</p>
+You can use the `oggz-info` tool to get the media duration; this tool is included with the [`oggz-tools`](https://www.xiph.org/oggz/) package. The output from `oggz-info` looks like this:
 
-<pre> $ oggz-info /g/media/bruce_vs_ironman.ogv
- Content-Duration: 00:01:00.046
+     $ oggz-info /g/media/bruce_vs_ironman.ogv
+     Content-Duration: 00:01:00.046
 
- Skeleton: serialno 1976223438
-         4 packets in 3 pages, 1.3 packets/page, 27.508% Ogg overhead
-         Presentation-Time: 0.000
-         Basetime: 0.000
+     Skeleton: serialno 1976223438
+             4 packets in 3 pages, 1.3 packets/page, 27.508% Ogg overhead
+             Presentation-Time: 0.000
+             Basetime: 0.000
 
- Theora: serialno 0170995062
-         1790 packets in 1068 pages, 1.7 packets/page, 1.049% Ogg overhead
-         Video-Framerate: 29.983 fps
-         Video-Width: 640
-         Video-Height: 360
+     Theora: serialno 0170995062
+             1790 packets in 1068 pages, 1.7 packets/page, 1.049% Ogg overhead
+             Video-Framerate: 29.983 fps
+             Video-Width: 640
+             Video-Height: 360
 
- Vorbis: serialno 0708996688
-         4531 packets in 167 pages, 27.1 packets/page, 1.408% Ogg overhead
-         Audio-Samplerate: 44100 Hz
-         Audio-Channels: 2
-</pre>
+     Vorbis: serialno 0708996688
+             4531 packets in 167 pages, 27.1 packets/page, 1.408% Ogg overhead
+             Audio-Samplerate: 44100 Hz
+             Audio-Channels: 2
 
-<p>Note that you can't serve up the reported Content-Duration line reported by <code>oggz-info</code>, because it's reported in HH:MM:SS format. You'll need to convert it to seconds only, then serve that as your <code>X-Content-Duration</code> value. Just parse out the HH, MM, and SS into numbers, then do (HH*3600)+(MM*60)+SS to get the value you should report.</p>
+Note that you can't serve up the reported Content-Duration line reported by `oggz-info`, because it's reported in HH:MM:SS format. You'll need to convert it to seconds only, then serve that as your `X-Content-Duration` value. Just parse out the HH, MM, and SS into numbers, then do (HH\*3600)+(MM\*60)+SS to get the value you should report.
 
-<p>It's important to note that it appears that <code>oggz-info</code> makes a read pass of the media in order to calculate its duration, so it's a good idea to store the duration value in order to avoid lengthy delays while the value is calculated for every HTTP request of your Ogg media.</p>
+It's important to note that it appears that `oggz-info` makes a read pass of the media in order to calculate its duration, so it's a good idea to store the duration value in order to avoid lengthy delays while the value is calculated for every HTTP request of your Ogg media.
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
- <li><a href="/en-US/docs/Web/Media/Formats">Guide to media types and formats on the web</a></li>
- <li><a href="/en-US/docs/Learn/HTML/Multimedia_and_embedding/Video_and_audio_content">Video and audio content</a></li>
- <li><a href="/en-US/docs/Web/Media/Formats/codecs_parameter">The "codecs" parameter in common media types</a></li>
-</ul>
+- [Guide to media types and formats on the web](/en-US/docs/Web/Media/Formats)
+- [Video and audio content](/en-US/docs/Learn/HTML/Multimedia_and_embedding/Video_and_audio_content)
+- [The "codecs" parameter in common media types](/en-US/docs/Web/Media/Formats/codecs_parameter)
diff --git a/files/en-us/web/http/connection_management_in_http_1.x/index.md b/files/en-us/web/http/connection_management_in_http_1.x/index.md
index 5ad27d9fa4288b7..97dd861c7dcfcd0 100644
--- a/files/en-us/web/http/connection_management_in_http_1.x/index.md
+++ b/files/en-us/web/http/connection_management_in_http_1.x/index.md
@@ -9,82 +9,74 @@ tags:
   - Performance
   - WebMechanics
 ---
-<div>{{HTTPSidebar}}</div>
+{{HTTPSidebar}}
 
-<p class="summary">Connection management is a key topic in HTTP: opening and maintaining connections largely impacts the performance of Web sites and Web applications. In HTTP/1.x, there are several models: <em>short-lived connections</em>, <em>persistent connections</em>, and <em>HTTP pipelining. </em></p>
+Connection management is a key topic in HTTP: opening and maintaining connections largely impacts the performance of Web sites and Web applications. In HTTP/1.x, there are several models: _short-lived connections_, _persistent connections_, and _HTTP pipelining._
 
-<p>HTTP mostly relies on TCP for its transport protocol, providing a connection between the client and the server. In its infancy, HTTP used a single model to handle such connections. These connections were short-lived: a new one created each time a request needed sending, and closed once the answer had been received.</p>
+HTTP mostly relies on TCP for its transport protocol, providing a connection between the client and the server. In its infancy, HTTP used a single model to handle such connections. These connections were short-lived: a new one created each time a request needed sending, and closed once the answer had been received.
 
-<p>This simple model held an innate limitation on performance: opening each TCP connection is a resource-consuming operation. Several messages must be exchanged between the client and the server. Network latency and bandwidth affect performance when a request needs sending. Modern Web pages require many requests (a dozen or more) to serve the amount of information needed, proving this earlier model inefficient.</p>
+This simple model held an innate limitation on performance: opening each TCP connection is a resource-consuming operation. Several messages must be exchanged between the client and the server. Network latency and bandwidth affect performance when a request needs sending. Modern Web pages require many requests (a dozen or more) to serve the amount of information needed, proving this earlier model inefficient.
 
-<p>Two newer models were created in HTTP/1.1. The persistent-connection model keeps connections opened between successive requests, reducing the time needed to open new connections. The HTTP pipelining model goes one step further, by sending several successive requests without even waiting for an answer, reducing much of the latency in the network.</p>
+Two newer models were created in HTTP/1.1. The persistent-connection model keeps connections opened between successive requests, reducing the time needed to open new connections. The HTTP pipelining model goes one step further, by sending several successive requests without even waiting for an answer, reducing much of the latency in the network.
 
-<p><img alt="Compares the performance of the three HTTP/1.x connection models: short-lived connections, persistent connections, and HTTP pipelining." src="http1_x_connections.png"></p>
+![Compares the performance of the three HTTP/1.x connection models: short-lived connections, persistent connections, and HTTP pipelining.](http1_x_connections.png)
 
-<div class="notecard note">
-  <p><strong>Note:</strong> HTTP/2 adds additional models for connection management.</p>
-</div>
+> **Note:** HTTP/2 adds additional models for connection management.
 
-<p>It's important point to note that connection management in HTTP applies to the connection between two consecutive nodes, which is <a href="/en-US/docs/Web/HTTP/Headers#hbh">hop-by-hop</a> and not <a href="/en-US/docs/Web/HTTP/Headers#e2e">end-to-end</a>. The model used in connections between a client and its first proxy may differ from the model between a proxy and the destination server (or any intermediate proxies). The HTTP headers involved in defining the connection model, like {{HTTPHeader("Connection")}} and {{HTTPHeader("Keep-Alive")}}, are <a href="/en-US/docs/Web/HTTP/Headers#hbh">hop-by-hop</a> headers with their values able to be changed by intermediary nodes.</p>
+It's important point to note that connection management in HTTP applies to the connection between two consecutive nodes, which is [hop-by-hop](/en-US/docs/Web/HTTP/Headers#hbh) and not [end-to-end](/en-US/docs/Web/HTTP/Headers#e2e). The model used in connections between a client and its first proxy may differ from the model between a proxy and the destination server (or any intermediate proxies). The HTTP headers involved in defining the connection model, like {{HTTPHeader("Connection")}} and {{HTTPHeader("Keep-Alive")}}, are [hop-by-hop](/en-US/docs/Web/HTTP/Headers#hbh) headers with their values able to be changed by intermediary nodes.
 
-<p>A related topic is the concept of HTTP connection upgrades, wherein an HTTP/1.1 connection is upgraded to a different protocol, such as TLS/1.0, WebSocket, or even HTTP/2 in cleartext. This <a href="/en-US/docs/Web/HTTP/Protocol_upgrade_mechanism">protocol upgrade mechanism</a> is documented in more detail elsewhere.</p>
+A related topic is the concept of HTTP connection upgrades, wherein an HTTP/1.1 connection is upgraded to a different protocol, such as TLS/1.0, WebSocket, or even HTTP/2 in cleartext. This [protocol upgrade mechanism](/en-US/docs/Web/HTTP/Protocol_upgrade_mechanism) is documented in more detail elsewhere.
 
-<h2 id="Short-lived_connections">Short-lived connections</h2>
+## Short-lived connections
 
-<p>The original model of HTTP, and the default one in HTTP/1.0, is <em>short-lived connections</em>. Each HTTP request is completed on its own connection; this means a TCP handshake happens before each HTTP request, and these are serialized.</p>
+The original model of HTTP, and the default one in HTTP/1.0, is _short-lived connections_. Each HTTP request is completed on its own connection; this means a TCP handshake happens before each HTTP request, and these are serialized.
 
-<p>The TCP handshake itself is time-consuming, but a TCP connection adapts to its load, becoming more efficient with more sustained (or warm) connections. Short-lived connections do not make use of this efficiency feature of TCP, and performance degrades from optimum by persisting to transmit over a new, cold connection.</p>
+The TCP handshake itself is time-consuming, but a TCP connection adapts to its load, becoming more efficient with more sustained (or warm) connections. Short-lived connections do not make use of this efficiency feature of TCP, and performance degrades from optimum by persisting to transmit over a new, cold connection.
 
-<p>This model is the default model used in HTTP/1.0 (if there is no {{HTTPHeader("Connection")}} header, or if its value is set to <code>close</code>). In HTTP/1.1, this model is only used when the {{HTTPHeader("Connection")}} header is sent with a value of <code>close</code>.</p>
+This model is the default model used in HTTP/1.0 (if there is no {{HTTPHeader("Connection")}} header, or if its value is set to `close`). In HTTP/1.1, this model is only used when the {{HTTPHeader("Connection")}} header is sent with a value of `close`.
 
-<div class="notecard note">
-  <p><strong>Note:</strong> Unless dealing with a very old system, which doesn't support a persistent connection, there is no compelling reason to use this model.</p>
-</div>
+> **Note:** Unless dealing with a very old system, which doesn't support a persistent connection, there is no compelling reason to use this model.
 
-<h2 id="Persistent_connections">Persistent connections</h2>
+## Persistent connections
 
-<p>Short-lived connections have two major hitches: the time taken to establish a new connection is significant, and performance of the underlying TCP connection gets better only when this connection has been in use for some time (warm connection). To ease these problems, the concept of a <em>persistent connection</em> has been designed, even prior to HTTP/1.1. Alternatively this may be called a <em>keep-alive connection</em>.</p>
+Short-lived connections have two major hitches: the time taken to establish a new connection is significant, and performance of the underlying TCP connection gets better only when this connection has been in use for some time (warm connection). To ease these problems, the concept of a _persistent connection_ has been designed, even prior to HTTP/1.1. Alternatively this may be called a _keep-alive connection_.
 
-<p>A persistent connection is one which remains open for a period of time, and can be reused for several requests, saving the need for a new TCP handshake, and utilizing TCP's performance enhancing capabilities. This connection will not stay open forever: idle connections are closed after some time (a server may use the {{HTTPHeader("Keep-Alive")}} header to specify a minimum time the connection should be kept open).</p>
+A persistent connection is one which remains open for a period of time, and can be reused for several requests, saving the need for a new TCP handshake, and utilizing TCP's performance enhancing capabilities. This connection will not stay open forever: idle connections are closed after some time (a server may use the {{HTTPHeader("Keep-Alive")}} header to specify a minimum time the connection should be kept open).
 
-<p>Persistent connections also have drawbacks; even when idling they consume server resources, and under heavy load, {{glossary("DoS attack", "DoS attacks")}} can be conducted. In such cases, using non-persistent connections, which are closed as soon as they are idle, can provide better performance.</p>
+Persistent connections also have drawbacks; even when idling they consume server resources, and under heavy load, {{glossary("DoS attack", "DoS attacks")}} can be conducted. In such cases, using non-persistent connections, which are closed as soon as they are idle, can provide better performance.
 
-<p>HTTP/1.0 connections are not persistent by default. Setting {{HTTPHeader("Connection")}} to anything other than <code>close</code>, usually <code>retry-after</code>, will make them persistent.</p>
+HTTP/1.0 connections are not persistent by default. Setting {{HTTPHeader("Connection")}} to anything other than `close`, usually `retry-after`, will make them persistent.
 
-<p>In HTTP/1.1, persistence is the default, and the header is no longer needed (but it is often added as a defensive measure against cases requiring a fallback to HTTP/1.0).</p>
+In HTTP/1.1, persistence is the default, and the header is no longer needed (but it is often added as a defensive measure against cases requiring a fallback to HTTP/1.0).
 
-<h2 id="HTTP_pipelining">HTTP pipelining</h2>
+## HTTP pipelining
 
-<div class="notecard note">
-  <p><strong>Note:</strong> HTTP pipelining is not activated by default in modern browsers:</p>
-  <ul>
-    <li>Buggy <a href="https://en.wikipedia.org/wiki/Proxy_server">proxies</a> are still common and these lead to strange and erratic behaviors that Web developers cannot foresee and diagnose easily.</li>
-    <li>Pipelining is complex to implement correctly: the size of the resource being transferred, the effective <a href="https://en.wikipedia.org/wiki/Round-trip_delay_time">RTT</a> that will be used, as well as the effective bandwidth, have a direct incidence on the improvement provided by the pipeline. Without knowing these, important messages may be delayed behind unimportant ones. The notion of important even evolves during page layout! HTTP pipelining therefore brings a marginal improvement in most cases only.</li>
-    <li>Pipelining is subject to the <a href="https://en.wikipedia.org/wiki/Head-of-line_blocking">HOL</a> problem.</li>
-  </ul>
-  <p>For these reasons, pipelining has been superseded by a better algorithm, <em>multiplexing</em>, that is used by HTTP/2.</p>
-</div>
+> **Note:** HTTP pipelining is not activated by default in modern browsers:
+>
+> - Buggy [proxies](https://en.wikipedia.org/wiki/Proxy_server) are still common and these lead to strange and erratic behaviors that Web developers cannot foresee and diagnose easily.
+> - Pipelining is complex to implement correctly: the size of the resource being transferred, the effective [RTT](https://en.wikipedia.org/wiki/Round-trip_delay_time) that will be used, as well as the effective bandwidth, have a direct incidence on the improvement provided by the pipeline. Without knowing these, important messages may be delayed behind unimportant ones. The notion of important even evolves during page layout! HTTP pipelining therefore brings a marginal improvement in most cases only.
+> - Pipelining is subject to the [HOL](https://en.wikipedia.org/wiki/Head-of-line_blocking) problem.
+>
+> For these reasons, pipelining has been superseded by a better algorithm, _multiplexing_, that is used by HTTP/2.
 
-<p>By default, <a href="/en-US/docs/Web/HTTP">HTTP</a> requests are issued sequentially. The next request is only issued once the response to the current request has been received. As they are affected by network latencies and bandwidth limitations, this can result in significant delay before the next request is <em>seen</em> by the server.</p>
+By default, [HTTP](/en-US/docs/Web/HTTP) requests are issued sequentially. The next request is only issued once the response to the current request has been received. As they are affected by network latencies and bandwidth limitations, this can result in significant delay before the next request is _seen_ by the server.
 
-<p>Pipelining is the process to send successive requests, over the same persistent connection, without waiting for the answer. This avoids latency of the connection. Theoretically, performance could also be improved if two HTTP requests were to be packed into the same TCP message. The typical <a href="https://en.wikipedia.org/wiki/Maximum_segment_size">MSS</a> (Maximum Segment Size), is big enough to contain several simple requests, although the demand in size of HTTP requests continues to grow.</p>
+Pipelining is the process to send successive requests, over the same persistent connection, without waiting for the answer. This avoids latency of the connection. Theoretically, performance could also be improved if two HTTP requests were to be packed into the same TCP message. The typical [MSS](https://en.wikipedia.org/wiki/Maximum_segment_size) (Maximum Segment Size), is big enough to contain several simple requests, although the demand in size of HTTP requests continues to grow.
 
-<p>Not all types of HTTP requests can be pipelined: only {{glossary("idempotent")}} methods, that is {{HTTPMethod("GET")}}, {{HTTPMethod("HEAD")}}, {{HTTPMethod("PUT")}} and {{HTTPMethod("DELETE")}}, can be replayed safely: should a failure happen, the pipeline content can be repeated.</p>
+Not all types of HTTP requests can be pipelined: only {{glossary("idempotent")}} methods, that is {{HTTPMethod("GET")}}, {{HTTPMethod("HEAD")}}, {{HTTPMethod("PUT")}} and {{HTTPMethod("DELETE")}}, can be replayed safely: should a failure happen, the pipeline content can be repeated.
 
-<p>Today, every HTTP/1.1-compliant proxy and server should support pipelining, though many have limitations in practice: a significant reason no modern browser activates this feature by default.</p>
+Today, every HTTP/1.1-compliant proxy and server should support pipelining, though many have limitations in practice: a significant reason no modern browser activates this feature by default.
 
-<h2 id="Domain_sharding">Domain sharding</h2>
+## Domain sharding
 
-<div class="notecard note">
-  <p><strong>Note:</strong> Unless you have a very specific immediate need, don't use this deprecated technique; switch to HTTP/2 instead. In HTTP/2, domain sharding is no longer useful: the HTTP/2 connection is able to handle parallel unprioritized requests very well. Domain sharding is even detrimental to performance. Most HTTP/2 implementations use a technique called <a href="https://daniel.haxx.se/blog/2016/08/18/http2-connection-coalescing/">connection coalescing</a> to revert eventual domain sharding.</p>
-</div>
+> **Note:** Unless you have a very specific immediate need, don't use this deprecated technique; switch to HTTP/2 instead. In HTTP/2, domain sharding is no longer useful: the HTTP/2 connection is able to handle parallel unprioritized requests very well. Domain sharding is even detrimental to performance. Most HTTP/2 implementations use a technique called [connection coalescing](https://daniel.haxx.se/blog/2016/08/18/http2-connection-coalescing/) to revert eventual domain sharding.
 
-<p>As an HTTP/1.x connection is serializing requests, even without any ordering, it can't be optimal without large enough available bandwidth. As a solution, browsers open several connections to each domain, sending parallel requests. Default was once 2 to 3 connections, but this has now increased to a more common use of 6 parallel connections. There is a risk of triggering <a href="/en-US/docs/Glossary/DOS_attack">DoS</a> protection on the server side if attempting more than this number.</p>
+As an HTTP/1.x connection is serializing requests, even without any ordering, it can't be optimal without large enough available bandwidth. As a solution, browsers open several connections to each domain, sending parallel requests. Default was once 2 to 3 connections, but this has now increased to a more common use of 6 parallel connections. There is a risk of triggering [DoS](/en-US/docs/Glossary/DOS_attack) protection on the server side if attempting more than this number.
 
-<p>If the server wishes a faster Web site or application response, it is possible for the server to force the opening of more connections. For example, Instead of having all resources on the same domain, say <code>www.example.com</code>, it could split over several domains, <code>www1.example.com</code>, <code>www2.example.com</code>, <code>www3.example.com</code>. Each of these domains resolve to the <em>same</em> server, and the Web browser will open 6 connections to each (in our example, boosting the connections to 18). This technique is called <em>domain sharding</em>.</p>
+If the server wishes a faster Web site or application response, it is possible for the server to force the opening of more connections. For example, Instead of having all resources on the same domain, say `www.example.com`, it could split over several domains, `www1.example.com`, `www2.example.com`, `www3.example.com`. Each of these domains resolve to the _same_ server, and the Web browser will open 6 connections to each (in our example, boosting the connections to 18). This technique is called _domain sharding_.
 
-<p><img alt="" src="httpsharding.png"></p>
+![](httpsharding.png)
 
-<h2 id="Conclusion">Conclusion</h2>
+## Conclusion
 
-<p>Improved connection management allows considerable boosting of performance in HTTP. With HTTP/1.1 or HTTP/1.0, using a persistent connection – at least until it becomes idle – leads to the best performance. However, the failure of pipelining has lead to designing superior connection management models, which have been incorporated into HTTP/2.</p>
+Improved connection management allows considerable boosting of performance in HTTP. With HTTP/1.1 or HTTP/1.0, using a persistent connection – at least until it becomes idle – leads to the best performance. However, the failure of pipelining has lead to designing superior connection management models, which have been incorporated into HTTP/2.
diff --git a/files/en-us/web/http/content_negotiation/index.md b/files/en-us/web/http/content_negotiation/index.md
index 07ce32beca1b735..d6fb53a0d875d0b 100644
--- a/files/en-us/web/http/content_negotiation/index.md
+++ b/files/en-us/web/http/content_negotiation/index.md
@@ -7,133 +7,102 @@ tags:
   - HTTP
   - Reference
 ---
-<div>{{HTTPSidebar}}</div>
+{{HTTPSidebar}}
 
-<p class="summary">In <a href="/en-US/docs/Glossary/HTTP">HTTP</a>, <em><strong>content negotiation</strong></em> is the mechanism that is used for serving different representations of a resource at the same URI, so that the user agent can specify which is best suited for the user (for example, which language of a document, which image format, or which content encoding).</p>
+In [HTTP](/en-US/docs/Glossary/HTTP), **_content negotiation_** is the mechanism that is used for serving different representations of a resource at the same URI, so that the user agent can specify which is best suited for the user (for example, which language of a document, which image format, or which content encoding).
 
-<div class="notecard note">
-  <p><strong>Note:</strong> Some disadvantages of HTTP content negotiation are explained in <a href="https://wiki.whatwg.org/wiki/Why_not_conneg">a wiki page from WHATWG</a>. HTML5 provides alternatives to content negotiation via, for example, the <a href="/en-US/docs/Web/HTML/Element/source"><code>&lt;source&gt;</code> element</a>.</p>
-</div>
+> **Note:** Some disadvantages of HTTP content negotiation are explained in [a wiki page from WHATWG](https://wiki.whatwg.org/wiki/Why_not_conneg). HTML5 provides alternatives to content negotiation via, for example, the [`<source>` element](/en-US/docs/Web/HTML/Element/source).
 
-<h2 id="Principles_of_content_negotiation">Principles of content negotiation</h2>
+## Principles of content negotiation
 
-<p>A specific document is called a <em>resource</em>. When a client wants to obtain a resource, the client requests it using its URL. The server uses this URL to choose one of the variants it provides – each variant being called a <em>representation</em> – and returns a specific representation to the client. The overall resource, as well as each of the representations, have a specific URL. How a specific representation is chosen when the resource is called is determined by <em>content negotiation</em> and there are several ways of negotiating between the client and the server.</p>
+A specific document is called a _resource_. When a client wants to obtain a resource, the client requests it using its URL. The server uses this URL to choose one of the variants it provides – each variant being called a _representation_ – and returns a specific representation to the client. The overall resource, as well as each of the representations, have a specific URL. How a specific representation is chosen when the resource is called is determined by _content negotiation_ and there are several ways of negotiating between the client and the server.
 
-<p><img alt="" src="httpnego.png"></p>
+![](httpnego.png)
 
-<p>The determination of the best suited representation is made through one of two mechanisms:</p>
+The determination of the best suited representation is made through one of two mechanisms:
 
-<ul>
- <li>Specific <a href="/en-US/docs/Web/HTTP/Headers">HTTP headers</a> by the client (<em>server-driven negotiation</em> or <em>proactive negotiation</em>), which is the standard way of negotiating a specific kind of resource.</li>
- <li>The {{HTTPStatus("300")}} (Multiple Choices) or {{HTTPStatus("406")}} (Not Acceptable), {{HTTPStatus("415")}} (Unsupported Media Type) <a href="/en-US/docs/Web/HTTP/Status">HTTP response codes</a> by the server (<em>agent-driven negotiation</em> or <em>reactive negotiation</em>), that are used as fallback mechanisms.</li>
-</ul>
+- Specific [HTTP headers](/en-US/docs/Web/HTTP/Headers) by the client (_server-driven negotiation_ or _proactive negotiation_), which is the standard way of negotiating a specific kind of resource.
+- The {{HTTPStatus("300")}} (Multiple Choices) or {{HTTPStatus("406")}} (Not Acceptable), {{HTTPStatus("415")}} (Unsupported Media Type) [HTTP response codes](/en-US/docs/Web/HTTP/Status) by the server (_agent-driven negotiation_ or _reactive negotiation_), that are used as fallback mechanisms.
 
-<p>Over the years, other content negotiation proposals, like <a href="https://datatracker.ietf.org/doc/html/rfc2295">transparent content negotiation</a> and the <code>Alternates</code> header, have been proposed. They failed to get traction and got abandoned.</p>
+Over the years, other content negotiation proposals, like [transparent content negotiation](https://datatracker.ietf.org/doc/html/rfc2295) and the `Alternates` header, have been proposed. They failed to get traction and got abandoned.
 
-<h2 id="Server-driven_content_negotiation">Server-driven content negotiation</h2>
+## Server-driven content negotiation
 
-<p>In <em>server-driven content negotiation</em>, or proactive content negotiation, the browser (or any other kind of user-agent) sends several HTTP headers along with the URL. These headers describe the preferred choice of the user. The server uses them as hints and an internal algorithm chooses the best content to serve to the client. If it cannot provide a suitable resource, as a fallback it might respond with {{HTTPStatus("406")}} (Not Acceptable) or {{HTTPStatus("415")}} (Unsupported Media Type) and set headers for the types of media that it does support (e.g. using the {{HTTPHeader("Accept-Post")}} or {{HTTPHeader("Accept-Patch")}} for POST and PATCH requests, respectively). The algorithm is server-specific and not defined in the standard. See, for example, the <a href="https://httpd.apache.org/docs/current/en/content-negotiation.html#algorithm">Apache negotiation algorithm</a>.</p>
+In _server-driven content negotiation_, or proactive content negotiation, the browser (or any other kind of user-agent) sends several HTTP headers along with the URL. These headers describe the preferred choice of the user. The server uses them as hints and an internal algorithm chooses the best content to serve to the client. If it cannot provide a suitable resource, as a fallback it might respond with {{HTTPStatus("406")}} (Not Acceptable) or {{HTTPStatus("415")}} (Unsupported Media Type) and set headers for the types of media that it does support (e.g. using the {{HTTPHeader("Accept-Post")}} or {{HTTPHeader("Accept-Patch")}} for POST and PATCH requests, respectively). The algorithm is server-specific and not defined in the standard. See, for example, the [Apache negotiation algorithm](https://httpd.apache.org/docs/current/en/content-negotiation.html#algorithm).
 
-<p><img alt="" src="httpnegoserver.png"></p>
+![](httpnegoserver.png)
 
-<p>The HTTP/1.1 standard defines list of the standard headers that start server-driven negotiation (such as {{HTTPHeader("Accept")}}, {{HTTPHeader("Accept-Encoding")}}, and {{HTTPHeader("Accept-Language")}}). Though strictly speaking {{HTTPHeader("User-Agent")}} is not in this list, it is sometimes also used to send a specific representation of the requested resource, though this is not considered as a good practice. The server uses the {{HTTPHeader("Vary")}} header to indicate which headers it actually used for content negotiation (or more precisely the associated response headers), so that <a href="/en-US/docs/Web/HTTP/Caching">caches</a> can work optimally.</p>
+The HTTP/1.1 standard defines list of the standard headers that start server-driven negotiation (such as {{HTTPHeader("Accept")}}, {{HTTPHeader("Accept-Encoding")}}, and {{HTTPHeader("Accept-Language")}}). Though strictly speaking {{HTTPHeader("User-Agent")}} is not in this list, it is sometimes also used to send a specific representation of the requested resource, though this is not considered as a good practice. The server uses the {{HTTPHeader("Vary")}} header to indicate which headers it actually used for content negotiation (or more precisely the associated response headers), so that [caches](/en-US/docs/Web/HTTP/Caching) can work optimally.
 
-<p>In addition to these, there is an experimental proposal to add more headers to the list of available headers, called <em>client hints</em>. Client hints advertise what kind of device the user agent runs on (for example, if it is a desktop computer or a mobile device).</p>
+In addition to these, there is an experimental proposal to add more headers to the list of available headers, called _client hints_. Client hints advertise what kind of device the user agent runs on (for example, if it is a desktop computer or a mobile device).
 
-<p>Even if server-driven content negotiation is the most common way to agree on a specific representation of a resource, it has several drawbacks:</p>
+Even if server-driven content negotiation is the most common way to agree on a specific representation of a resource, it has several drawbacks:
 
-<ul>
- <li>The server doesn't have total knowledge of the browser. Even with the Client Hints extension, it has not a complete knowledge of the capabilities of the browser. Unlike reactive content negotiation where the client makes the choice, the server choice is always somewhat arbitrary.</li>
- <li>The information by the client is quite verbose (HTTP/2 header compression mitigates this problem) and a privacy risk (HTTP fingerprinting)</li>
- <li>As several representations of a given resource are sent, shared caches are less efficient and server implementations are more complex.</li>
-</ul>
+- The server doesn't have total knowledge of the browser. Even with the Client Hints extension, it has not a complete knowledge of the capabilities of the browser. Unlike reactive content negotiation where the client makes the choice, the server choice is always somewhat arbitrary.
+- The information by the client is quite verbose (HTTP/2 header compression mitigates this problem) and a privacy risk (HTTP fingerprinting)
+- As several representations of a given resource are sent, shared caches are less efficient and server implementations are more complex.
 
-<h3 id="The_Accept_header">The Accept header</h3>
+### The Accept header
 
-<p>The {{HTTPHeader("Accept")}} header lists the MIME types of media resources that the agent is willing to process. It is comma-separated lists of MIME types, each combined with a quality factor, a parameter indicating the relative degree of preference between the different MIME types.</p>
+The {{HTTPHeader("Accept")}} header lists the MIME types of media resources that the agent is willing to process. It is comma-separated lists of MIME types, each combined with a quality factor, a parameter indicating the relative degree of preference between the different MIME types.
 
-<p>The {{HTTPHeader("Accept")}} header is defined by the browser, or any other user-agent, and can vary according to the context, like fetching an HTML page or an image, a video, or a script: It is different when fetching a document entered in the address bar or an element linked via an {{ HTMLElement("img") }}, {{ HTMLElement("video") }} or {{ HTMLElement("audio") }} element. Browsers are free to use the value of the header that they think is the most adequate; an exhaustive list of <a href="/en-US/docs/Web/HTTP/Content_negotiation/List_of_default_Accept_values">default values for common browsers</a> is available.</p>
+The {{HTTPHeader("Accept")}} header is defined by the browser, or any other user-agent, and can vary according to the context, like fetching an HTML page or an image, a video, or a script: It is different when fetching a document entered in the address bar or an element linked via an {{ HTMLElement("img") }}, {{ HTMLElement("video") }} or {{ HTMLElement("audio") }} element. Browsers are free to use the value of the header that they think is the most adequate; an exhaustive list of [default values for common browsers](/en-US/docs/Web/HTTP/Content_negotiation/List_of_default_Accept_values) is available.
 
-<h3 id="The_Accept-CH_header_experimental_inline">The Accept-CH header {{experimental_inline}}</h3>
+### The Accept-CH header {{experimental_inline}}
 
-<div class="notecard note">
-  <p><strong>Note:</strong> This is part of an <strong>experimental</strong> technology called <em>Client Hints</em>. Initial support is in Chrome 46 or later. The Device-Memory value is in Chrome 61 or later.</p>
-</div>
+> **Note:** This is part of an **experimental** technology called _Client Hints_. Initial support is in Chrome 46 or later. The Device-Memory value is in Chrome 61 or later.
 
-<p>The experimental {{HTTPHeader("Accept-CH")}} lists configuration data that can be used by the server to select an appropriate response. Valid values are:</p>
+The experimental {{HTTPHeader("Accept-CH")}} lists configuration data that can be used by the server to select an appropriate response. Valid values are:
 
-<table class="standard-table">
- <thead>
-  <tr>
-   <th scope="col">Value</th>
-   <th scope="col">Meaning</th>
-  </tr>
- </thead>
- <tbody>
-  <tr>
-   <td><code>Device-Memory</code></td>
-   <td>Indicates the approximate amount of device RAM. This value is an approximation given by rounding to the nearest power of 2 and dividing that number by 1024. For example, 512 megabytes will be reported as <code>0.5</code>.</td>
-  </tr>
-  <tr>
-   <td><code>Viewport-Width</code></td>
-   <td>Indicates the layout viewport width in CSS pixels.</td>
-  </tr>
-  <tr>
-   <td><code>Width</code></td>
-   <td>Indicates the resource width in physical pixels (in other words the intrinsic size of an image).</td>
-  </tr>
- </tbody>
-</table>
+| Value            | Meaning                                                                                                                                                                                                            |
+| ---------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| `Device-Memory`  | Indicates the approximate amount of device RAM. This value is an approximation given by rounding to the nearest power of 2 and dividing that number by 1024. For example, 512 megabytes will be reported as `0.5`. |
+| `Viewport-Width` | Indicates the layout viewport width in CSS pixels.                                                                                                                                                                 |
+| `Width`          | Indicates the resource width in physical pixels (in other words the intrinsic size of an image).                                                                                                                   |
 
-<h3 id="The_Accept-CH-Lifetime_header">The Accept-CH-Lifetime header</h3>
+### The Accept-CH-Lifetime header
 
-<div class="notecard note">
-  <p><strong>Note:</strong> This is part of an <strong>experimental</strong> technology called <em>Client Hints</em> and is only available in Chrome 61 or later.</p>
-</div>
+> **Note:** This is part of an **experimental** technology called _Client Hints_ and is only available in Chrome 61 or later.
 
-<p>The {{HTTPHeader("Accept-CH-Lifetime")}} header is used with the <code>Device-Memory</code> value of the <code>Accept-CH</code> header and indicates the amount of time the device should opt-in to sharing the amount of device memory with the server. The value is given in milliseconds and it's use is optional.</p>
+The {{HTTPHeader("Accept-CH-Lifetime")}} header is used with the `Device-Memory` value of the `Accept-CH` header and indicates the amount of time the device should opt-in to sharing the amount of device memory with the server. The value is given in milliseconds and it's use is optional.
 
-<h3 id="The_Accept-Encoding_header">The Accept-Encoding header</h3>
+### The Accept-Encoding header
 
-<p>The {{HTTPHeader("Accept-Encoding")}} header defines the acceptable content-encoding (supported compressions). The value is a q-factor list (e.g.: <code>br, gzip;q=0.8</code>) that indicates the priority of the encoding values. The default value <code>identity</code> is at the lowest priority (unless otherwise declared).</p>
+The {{HTTPHeader("Accept-Encoding")}} header defines the acceptable content-encoding (supported compressions). The value is a q-factor list (e.g.: `br, gzip;q=0.8`) that indicates the priority of the encoding values. The default value `identity` is at the lowest priority (unless otherwise declared).
 
-<p>Compressing HTTP messages is one of the most important ways to improve the performance of a Web site, it shrinks the size of the data transmitted and makes better use of the available bandwidth; browsers always send this header and the server should be configured to abide to it and to use compression.</p>
+Compressing HTTP messages is one of the most important ways to improve the performance of a Web site, it shrinks the size of the data transmitted and makes better use of the available bandwidth; browsers always send this header and the server should be configured to abide to it and to use compression.
 
-<h3 id="The_Accept-Language_header">The Accept-Language header</h3>
+### The Accept-Language header
 
-<p>The {{HTTPHeader("Accept-Language")}} header is used to indicate the language preference of the user. It is a list of values with quality factors (like: <code>"de, en;q=0.7</code>"). A default value is often set according the language of the graphical interface of the user agent, but most browsers allow to set different language preferences.</p>
+The {{HTTPHeader("Accept-Language")}} header is used to indicate the language preference of the user. It is a list of values with quality factors (like: `"de, en;q=0.7`"). A default value is often set according the language of the graphical interface of the user agent, but most browsers allow to set different language preferences.
 
-<p>Due to the <a href="https://www.eff.org/deeplinks/2010/01/primer-information-theory-and-privacy">configuration-based entropy</a> increase, a modified value can be used to fingerprint the user, it is not recommended to change it and a Web site cannot trust this value to reflect the actual wish of the user. Site designers must not be over-zealous by using language detection via this header as it can lead to a poor user experience:</p>
+Due to the [configuration-based entropy](https://www.eff.org/deeplinks/2010/01/primer-information-theory-and-privacy) increase, a modified value can be used to fingerprint the user, it is not recommended to change it and a Web site cannot trust this value to reflect the actual wish of the user. Site designers must not be over-zealous by using language detection via this header as it can lead to a poor user experience:
 
-<ul>
- <li>They should always provide a way to overcome the server-chosen language, e.g., by providing a language menu on the site. Most user-agents provide a default value for the <code>Accept-Language</code> header, adapted to the user interface language and end users often do not modify it, either by not knowing how, or by not being able to do it, as in an Internet café for instance.</li>
- <li>Once a user has overridden the server-chosen language, a site should no longer use language detection and should stick with the explicitly-chosen language. In other words, only entry pages of a site should select the proper language using this header.</li>
-</ul>
+- They should always provide a way to overcome the server-chosen language, e.g., by providing a language menu on the site. Most user-agents provide a default value for the `Accept-Language` header, adapted to the user interface language and end users often do not modify it, either by not knowing how, or by not being able to do it, as in an Internet café for instance.
+- Once a user has overridden the server-chosen language, a site should no longer use language detection and should stick with the explicitly-chosen language. In other words, only entry pages of a site should select the proper language using this header.
 
-<h3 id="The_User-Agent_header">The User-Agent header</h3>
+### The User-Agent header
 
-<div class="notecard note">
-  <p><strong>Note:</strong> Though there are legitimate uses of this header for selecting content, <a href="/en-US/docs/Web/HTTP/Browser_detection_using_the_user_agent">it is considered bad practice</a> to rely on it to define what features are supported by the user agent.</p>
-</div>
+> **Note:** Though there are legitimate uses of this header for selecting content, [it is considered bad practice](/en-US/docs/Web/HTTP/Browser_detection_using_the_user_agent) to rely on it to define what features are supported by the user agent.
 
-<p>The {{HTTPHeader("User-Agent")}} header identifies the browser sending the request. This string may contain a space-separated list of <em>product tokens</em> and <em>comments</em>.</p>
+The {{HTTPHeader("User-Agent")}} header identifies the browser sending the request. This string may contain a space-separated list of _product tokens_ and _comments_.
 
-<p>A <em>product token</em> is a name followed by a '<code>/</code>' and a version number, like <code>Firefox/4.0.1</code>. There may be as many of them as the user-agent wants. A <em>comment</em> is a free string delimited by parentheses. Obviously parentheses cannot be used in that string. The inner format of a comment is not defined by the standard, though several browser put several tokens in it, separated by '<code>;</code>'.</p>
+A _product token_ is a name followed by a '`/`' and a version number, like `Firefox/4.0.1`. There may be as many of them as the user-agent wants. A _comment_ is a free string delimited by parentheses. Obviously parentheses cannot be used in that string. The inner format of a comment is not defined by the standard, though several browser put several tokens in it, separated by '`;`'.
 
-<h3 id="The_Vary_response_header">The Vary response header</h3>
+### The Vary response header
 
-<p>In contrast to the previous <code>Accept-*</code> headers, which are sent by the client, the {{HTTPHeader("Vary")}} HTTP header is sent by the web server in its response. It indicates the list of headers used by the server during the server-driven content negotiation phase. The header is needed in order to inform the cache of the decision criteria so that it can reproduce it, allowing the cache to be functional while preventing serving erroneous content to the user.</p>
+In contrast to the previous `Accept-*` headers, which are sent by the client, the {{HTTPHeader("Vary")}} HTTP header is sent by the web server in its response. It indicates the list of headers used by the server during the server-driven content negotiation phase. The header is needed in order to inform the cache of the decision criteria so that it can reproduce it, allowing the cache to be functional while preventing serving erroneous content to the user.
 
-<p>The special value of '<code>*</code>' means that the server-driven content negotiation also uses information not conveyed in a header to choose the appropriate content.</p>
+The special value of '`*`' means that the server-driven content negotiation also uses information not conveyed in a header to choose the appropriate content.
 
-<p>The <code>Vary</code> header was added in the version 1.1 of HTTP and is necessary in order to allow caches to work appropriately. A cache, in order to work with server-driven content negotiation, needs to know which criteria was used by the server to select the transmitted content. That way, the cache can replay the algorithm and will be able to serve acceptable content directly, without more request to the server. Obviously, the wildcard '<code>*</code>' prevents caching from occurring, as the cache cannot know what element is behind it. For more information <a href="/en-US/docs/Web/HTTP/Caching#varying_responses">HTTP caching &gt; Varying responses</a>.</p>
+The `Vary` header was added in the version 1.1 of HTTP and is necessary in order to allow caches to work appropriately. A cache, in order to work with server-driven content negotiation, needs to know which criteria was used by the server to select the transmitted content. That way, the cache can replay the algorithm and will be able to serve acceptable content directly, without more request to the server. Obviously, the wildcard '`*`' prevents caching from occurring, as the cache cannot know what element is behind it. For more information [HTTP caching > Varying responses](/en-US/docs/Web/HTTP/Caching#varying_responses).
 
-<h2 id="Agent-driven_negotiation">Agent-driven negotiation</h2>
+## Agent-driven negotiation
 
-<p>Server-driven negotiation suffers from a few downsides: it doesn't scale well. There is one header per feature used in the negotiation. If you want to use screen size, resolution or other dimensions, a new HTTP header must be created. Sending of the headers must be done on every request. This is not too problematic with few headers, but with the eventual multiplications of them, the message size would lead to a decrease in performance. The more precise headers are sent, the more entropy is sent, allowing for more HTTP fingerprinting and corresponding privacy concern.</p>
+Server-driven negotiation suffers from a few downsides: it doesn't scale well. There is one header per feature used in the negotiation. If you want to use screen size, resolution or other dimensions, a new HTTP header must be created. Sending of the headers must be done on every request. This is not too problematic with few headers, but with the eventual multiplications of them, the message size would lead to a decrease in performance. The more precise headers are sent, the more entropy is sent, allowing for more HTTP fingerprinting and corresponding privacy concern.
 
-<p>From the beginnings of HTTP, the protocol allowed another negotiation type: <em>agent-driven negotiation</em> or <em>reactive negotiation</em>. In this negotiation, when facing an ambiguous request, the server sends back a page containing links to the available alternative resources. The user is presented the resources and choose the one to use.</p>
+From the beginnings of HTTP, the protocol allowed another negotiation type: _agent-driven negotiation_ or _reactive negotiation_. In this negotiation, when facing an ambiguous request, the server sends back a page containing links to the available alternative resources. The user is presented the resources and choose the one to use.
 
-<p><img alt="" src="httpnego3.png"></p>
+![](httpnego3.png)
 
-<p>Unfortunately, the HTTP standard does not specify the format of the page for choosing between the available resource, which prevents the process being automated. Besides falling back to the <em>server-driven negotiation</em>, this method is almost always used in conjunction with scripting, especially with JavaScript redirection: after having checked for the negotiation criteria, the script performs the redirection. A second problem is that one more request is needed in order to fetch the real resource, slowing the availability of the resource to the user.</p>
+Unfortunately, the HTTP standard does not specify the format of the page for choosing between the available resource, which prevents the process being automated. Besides falling back to the _server-driven negotiation_, this method is almost always used in conjunction with scripting, especially with JavaScript redirection: after having checked for the negotiation criteria, the script performs the redirection. A second problem is that one more request is needed in order to fetch the real resource, slowing the availability of the resource to the user.
diff --git a/files/en-us/web/http/content_negotiation/list_of_default_accept_values/index.md b/files/en-us/web/http/content_negotiation/list_of_default_accept_values/index.md
index fee94e519109ff0..f627bdd9ab377f2 100644
--- a/files/en-us/web/http/content_negotiation/list_of_default_accept_values/index.md
+++ b/files/en-us/web/http/content_negotiation/list_of_default_accept_values/index.md
@@ -7,233 +7,101 @@ tags:
   - HTTP
   - Reference
 ---
-<div>{{HTTPSidebar}}</div>
-
-<p>This article documents the default values for the HTTP <code><a href="/en-US/docs/Web/HTTP/Headers/Accept">Accept</a></code> header for specific inputs and browser versions.</p>
-
-<h2 id="Default_values">Default values</h2>
-
-<p>These are the values sent when the context doesn't give better information. Note that all browsers add the <code>*/*</code> MIME Type to cover all cases. This is typically used for requests initiated via the address bar of a browser, or via an HTML {{HTMLElement("a")}} element.</p>
-
-<table>
-  <tr>
-    <th>User Agent</th>
-    <th>Value</th>
-  </tr>
-  <tr>
-    <td>Firefox 72 and later [1]</td>
-    <td><code>text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,*/*;q=0.8</code></td>
-  </tr>
-  <tr>
-    <td>Firefox 66 to 71 [1]</td>
-    <td><code>text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8</code></td>
-  </tr>
-  <tr>
-    <td>Firefox 65 [1]</td>
-    <td><code>text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,*/*;q=0.8</code></td>
-  </tr>
-  <tr>
-    <td>Firefox 64 and earlier [1]</td>
-    <td><code>text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8</code></td>
-  </tr>
-  <tr>
-    <td>Safari, Chrome</td>
-    <td><code>text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,image/apng,*/*;q=0.8</code></td>
-  </tr>
-  <tr>
-    <td>Safari 5 [2]</td>
-    <td><code>text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8</code></td>
-  </tr>
-  <tr>
-    <td>Internet Explorer 8 [3]</td>
-    <td><code>image/jpeg, application/x-ms-application, image/gif, application/xaml+xml, image/pjpeg, application/x-ms-xbap, application/x-shockwave-flash, application/msword, */*</code></td>
-  </tr>
-  <tr>
-    <td>Edge</td>
-    <td><code>text/html, application/xhtml+xml, image/jxr, */*</code></td>
-  </tr>
-  <tr>
-    <td>Opera</td>
-    <td><code>text/html, application/xml;q=0.9, application/xhtml+xml, image/png, image/webp, image/jpeg, image/gif, image/x-xbitmap, */*;q=0.1</code></td>
-  </tr>
-</table>
-
-<p>[1] This value can be modified using the <a href="http://kb.mozillazine.org/Network.http.accept.default"><code>network.http.accept.default</code></a> parameter.</p>
-<p>[2] This is an improvement over earlier <code>Accept</code> headers as it no longer ranks <code>image/png</code> above <code>text/html</code>.</p>
-<p>[3] See <a href="https://docs.microsoft.com/en-us/archive/blogs/ieinternals/ie-and-the-accept-header">IE and the Accept Header (IEInternals' MSDN blog)</a>.</p>
-
-<h2 id="Values_for_an_image">Values for an image</h2>
-
-<p>When requesting an image, like through an HTML {{HTMLElement("img")}} element, user-agent often sets a specific list of media types to be welcomed.</p>
-
-<table>
- <tbody>
-  <tr>
-   <th>User Agent</th>
-   <th>Value</th>
-  </tr>
-  <tr>
-   <td>Firefox 65 and later [1]</td>
-   <td><code>image/webp,*/*</code></td>
-  <tr>
-    <td>Firefox 47 to 63 [1]</td>
-    <td><code>*/*</code></td>
-  </tr>
-  <tr>
-    <td>Firefox prior to 47 [1]</td>
-    <td><code>image/png,image/*;q=0.8,*/*;q=0.5</code></td>
-  </tr>
-  <tr>
-   <td>Safari (since Mac OS Big Sur)</td>
-   <td><code>image/webp,image/png,image/svg+xml,image/*;q=0.8,video/*;q=0.8,*/*;q=0.5</code></td>
-  </tr>
-  <tr>
-    <td>Safari (before Mac OS Big Sur)</td>
-    <td><code>image/png,image/svg+xml,image/*;q=0.8,video/*;q=0.8,*/*;q=0.5</code></td>
-  </tr>
-  <tr>
-   <td>Chrome</td>
-   <td><code>image/avif,image/webp,image/apng,image/*,*/*;q=0.8</code></td>
-  </tr>
-  <tr>
-    <td>Internet Explorer 9</td>
-    <td><code>image/png,image/svg+xml,image/*;q=0.8, */*;q=0.5</code></td>
-   </tr>
-  <tr>
-   <td>Internet Explorer 8 or earlier <em><a href="https://docs.microsoft.com/en-us/archive/blogs/ieinternals/ie-and-the-accept-header">source</a></em></td>
-   <td><code>*/*</code></td>
-  </tr>
-
- </tbody>
-</table>
-
-<p>[1] This value can be modified using the <code>image.http.accept</code> parameter (<em><a href="https://searchfox.org/mozilla-central/search?q=image.http.accept">source</a></em>).</p>
-
-<h2 id="Values_for_a_video">Values for a video</h2>
-
-<p>When a video is requested, via the {{HTMLElement("video")}} HTML element, most browsers use specific values.</p>
-
-<table>
- <tbody>
-  <tr>
-   <th>User Agent</th>
-   <th>Value</th>
-  </tr>
-  <tr>
-    <td>Firefox 3.6 and later</td>
-    <td><code>video/webm,video/ogg,video/*;q=0.9,application/ogg;q=0.7,audio/*;q=0.6,*/*;q=0.5</code></td>
-  </tr>
-  <tr>
-   <td>Firefox earlier than 3.6</td>
-   <td><em>no support for {{HTMLElement("video")}}</em></td>
-  </tr>
-  <tr>
-   <td>Chrome</td>
-   <td><code>*/*</code></td>
-  </tr>
-  <tr>
-   <td>Internet Explorer 8 or earlier</td>
-   <td><em>no support for {{HTMLElement("video")}}</em></td>
-  </tr>
- </tbody>
-</table>
-
-<h2 id="Values_for_audio_resources">Values for audio resources</h2>
-
-<p>When an audio file is requested, like via the {{HTMLElement("audio")}} HTML element, most browsers use specific values.</p>
-
-<table class="standard-table">
- <tbody>
-  <tr>
-   <th>User Agent</th>
-   <th>Value</th>
-  </tr>
-  <tr>
-   <td>Firefox 3.6 and later [1]</td>
-   <td><code>audio/webm,audio/ogg,audio/wav,audio/*;q=0.9,application/ogg;q=0.7,video/*;q=0.6,*/*;q=0.5</code></td>
-  </tr>
-  <tr>
-   <td>Safari, Chrome</td>
-   <td><code>*/*</code></td>
-  </tr>
-  <tr>
-   <td>Internet Explorer 8 or earlier</td>
-   <td><em>no support for {{HTMLElement("audio")}}</em></td>
-  </tr>
-  <tr>
-   <td>Internet Explorer 9</td>
-   <td>?</td>
-  </tr>
- </tbody>
-</table>
-
-<p>[1] See <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=489071">bug 489071</a>.</p>
-
-<h2 id="Values_for_scripts">Values for scripts</h2>
-
-<p>When a script is requested, like via the {{HTMLElement("script")}} HTML element, some browsers use specific values.</p>
-
-<table>
- <tbody>
-  <tr>
-   <th>User Agent</th>
-   <th>Value</th>
-  </tr>
-  <tr>
-   <td>Firefox [1]</td>
-   <td><code>*/*</code></td>
-  </tr>
-  <tr>
-   <td>Safari, Chrome</td>
-   <td><code>*/*</code></td>
-  </tr>
-  <tr>
-   <td>Internet Explorer 8 or earlier [2]</td>
-   <td><code>*/*</code></td>
-  </tr>
-  <tr>
-   <td>Internet Explorer 9</td>
-   <td><code>application/javascript, */*;q=0.8</code></td>
-  </tr>
- </tbody>
-</table>
-<p>[1] See <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=170789">bug 170789</a>.</p>
-<p>[2] See <a href="https://docs.microsoft.com/en-us/archive/blogs/ieinternals/ie-and-the-accept-header">IE and the Accept Header (IEInternals' MSDN blog)</a>.</p>
-<h2 id="Values_for_a_CSS_stylesheet">Values for a CSS stylesheet</h2>
-
-<p>When a CSS stylesheet is requested, via the <code>&lt;link rel="stylesheet"&gt;</code> HTML element, most browsers use specific values.</p>
-
-<table>
- <tbody>
-  <tr>
-   <th>User Agent</th>
-   <th>Value</th>
-  </tr>
-  <tr>
-   <td>Firefox 4 [1]</td>
-   <td><code>text/css,*/*;q=0.1</code></td>
-  </tr>
-  <tr>
-   <td>Internet Explorer 8 or earlier [2]</td>
-   <td><code>*/*</code></td>
-  </tr>
-  <tr>
-   <td>Internet Explorer 9</td>
-   <td><code>text/css</code></td>
-  </tr>
-  <tr>
-   <td>Safari, Chrome</td>
-   <td><code>text/css,*/*;q=0.1</code></td>
-  </tr>
-  <tr>
-   <td>Opera 11.10</td>
-   <td><code>text/html, application/xml;q=0.9, application/xhtml+xml, image/png, image/webp, image/jpeg, image/gif, image/x-xbitmap, */*;q=0.1 </code></td>
-  </tr>
-  <tr>
-   <td>Konqueror 4.6</td>
-   <td><code>text/css,*/*;q=0.1</code></td>
-  </tr>
- </tbody>
-</table>
-<p>[1] See <a class="link-https" href="https://bugzilla.mozilla.org/show_bug.cgi?id=170789">bug 170789</a>.</p>
-<p>[2] See <a href="https://docs.microsoft.com/en-us/archive/blogs/ieinternals/ie-and-the-accept-header">IE and the Accept Header (IEInternals' MSDN blog)</a>.</p>
+{{HTTPSidebar}}
+
+This article documents the default values for the HTTP [`Accept`](/en-US/docs/Web/HTTP/Headers/Accept) header for specific inputs and browser versions.
+
+## Default values
+
+These are the values sent when the context doesn't give better information. Note that all browsers add the `*/*` MIME Type to cover all cases. This is typically used for requests initiated via the address bar of a browser, or via an HTML {{HTMLElement("a")}} element.
+
+| User Agent                 | Value                                                                                                                                                                   |
+| -------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Firefox 72 and later [1]   | `text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,*/*;q=0.8`                                                                                            |
+| Firefox 66 to 71 [1]       | `text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8`                                                                                                       |
+| Firefox 65 [1]             | `text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,*/*;q=0.8`                                                                                            |
+| Firefox 64 and earlier [1] | `text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8`                                                                                                       |
+| Safari, Chrome             | `text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,image/apng,*/*;q=0.8`                                                                                 |
+| Safari 5 [2]               | `text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8`                                                                                                       |
+| Internet Explorer 8 [3]    | `image/jpeg, application/x-ms-application, image/gif, application/xaml+xml, image/pjpeg, application/x-ms-xbap, application/x-shockwave-flash, application/msword, */*` |
+| Edge                       | `text/html, application/xhtml+xml, image/jxr, */*`                                                                                                                      |
+| Opera                      | `text/html, application/xml;q=0.9, application/xhtml+xml, image/png, image/webp, image/jpeg, image/gif, image/x-xbitmap, */*;q=0.1`                                     |
+
+\[1] This value can be modified using the [`network.http.accept.default`](http://kb.mozillazine.org/Network.http.accept.default) parameter.
+
+\[2] This is an improvement over earlier `Accept` headers as it no longer ranks `image/png` above `text/html`.
+
+\[3] See [IE and the Accept Header (IEInternals' MSDN blog)](https://docs.microsoft.com/en-us/archive/blogs/ieinternals/ie-and-the-accept-header).
+
+## Values for an image
+
+When requesting an image, like through an HTML {{HTMLElement("img")}} element, user-agent often sets a specific list of media types to be welcomed.
+
+| User Agent                                                                                                                     | Value                                                                      |
+| ------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------- |
+| Firefox 65 and later [1]                                                                                                       | `image/webp,*/*`                                                           |
+| Firefox 47 to 63 [1]                                                                                                           | `*/*`                                                                      |
+| Firefox prior to 47 [1]                                                                                                        | `image/png,image/*;q=0.8,*/*;q=0.5`                                        |
+| Safari (since Mac OS Big Sur)                                                                                                  | `image/webp,image/png,image/svg+xml,image/*;q=0.8,video/*;q=0.8,*/*;q=0.5` |
+| Safari (before Mac OS Big Sur)                                                                                                 | `image/png,image/svg+xml,image/*;q=0.8,video/*;q=0.8,*/*;q=0.5`            |
+| Chrome                                                                                                                         | `image/avif,image/webp,image/apng,image/*,*/*;q=0.8`                       |
+| Internet Explorer 9                                                                                                            | `image/png,image/svg+xml,image/*;q=0.8, */*;q=0.5`                         |
+| Internet Explorer 8 or earlier _[source](https://docs.microsoft.com/en-us/archive/blogs/ieinternals/ie-and-the-accept-header)_ | `*/*`                                                                      |
+
+\[1] This value can be modified using the `image.http.accept` parameter (_[source](https://searchfox.org/mozilla-central/search?q=image.http.accept)_).
+
+## Values for a video
+
+When a video is requested, via the {{HTMLElement("video")}} HTML element, most browsers use specific values.
+
+| User Agent                     | Value                                                                              |
+| ------------------------------ | ---------------------------------------------------------------------------------- |
+| Firefox 3.6 and later          | `video/webm,video/ogg,video/*;q=0.9,application/ogg;q=0.7,audio/*;q=0.6,*/*;q=0.5` |
+| Firefox earlier than 3.6       | _no support for {{HTMLElement("video")}}_                                  |
+| Chrome                         | `*/*`                                                                              |
+| Internet Explorer 8 or earlier | _no support for {{HTMLElement("video")}}_                                  |
+
+## Values for audio resources
+
+When an audio file is requested, like via the {{HTMLElement("audio")}} HTML element, most browsers use specific values.
+
+| User Agent                     | Value                                                                                        |
+| ------------------------------ | -------------------------------------------------------------------------------------------- |
+| Firefox 3.6 and later [1]      | `audio/webm,audio/ogg,audio/wav,audio/*;q=0.9,application/ogg;q=0.7,video/*;q=0.6,*/*;q=0.5` |
+| Safari, Chrome                 | `*/*`                                                                                        |
+| Internet Explorer 8 or earlier | _no support for {{HTMLElement("audio")}}_                                            |
+| Internet Explorer 9            | ?                                                                                            |
+
+\[1] See [bug 489071](https://bugzilla.mozilla.org/show_bug.cgi?id=489071).
+
+## Values for scripts
+
+When a script is requested, like via the {{HTMLElement("script")}} HTML element, some browsers use specific values.
+
+| User Agent                         | Value                               |
+| ---------------------------------- | ----------------------------------- |
+| Firefox [1]                        | `*/*`                               |
+| Safari, Chrome                     | `*/*`                               |
+| Internet Explorer 8 or earlier [2] | `*/*`                               |
+| Internet Explorer 9                | `application/javascript, */*;q=0.8` |
+
+\[1] See [bug 170789](https://bugzilla.mozilla.org/show_bug.cgi?id=170789).
+
+\[2] See [IE and the Accept Header (IEInternals' MSDN blog)](https://docs.microsoft.com/en-us/archive/blogs/ieinternals/ie-and-the-accept-header).
+
+## Values for a CSS stylesheet
+
+When a CSS stylesheet is requested, via the `<link rel="stylesheet">` HTML element, most browsers use specific values.
+
+| User Agent                         | Value                                                                                                                               |
+| ---------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------- |
+| Firefox 4 [1]                      | `text/css,*/*;q=0.1`                                                                                                                |
+| Internet Explorer 8 or earlier [2] | `*/*`                                                                                                                               |
+| Internet Explorer 9                | `text/css`                                                                                                                          |
+| Safari, Chrome                     | `text/css,*/*;q=0.1`                                                                                                                |
+| Opera 11.10                        | `text/html, application/xml;q=0.9, application/xhtml+xml, image/png, image/webp, image/jpeg, image/gif, image/x-xbitmap, */*;q=0.1` |
+| Konqueror 4.6                      | `text/css,*/*;q=0.1`                                                                                                                |
+
+\[1] See [bug 170789](https://bugzilla.mozilla.org/show_bug.cgi?id=170789).
+
+\[2] See [IE and the Accept Header (IEInternals' MSDN blog)](https://docs.microsoft.com/en-us/archive/blogs/ieinternals/ie-and-the-accept-header).
diff --git a/files/en-us/web/http/cookies/index.md b/files/en-us/web/http/cookies/index.md
index 5c3915f2a1a5843..d6b9da05dddbb94 100644
--- a/files/en-us/web/http/cookies/index.md
+++ b/files/en-us/web/http/cookies/index.md
@@ -19,234 +19,205 @@ tags:
   - request
   - tracking
 ---
-<div>{{HTTPSidebar}}</div>
+{{HTTPSidebar}}
 
-<p class="summary">An <strong>HTTP cookie</strong> (web cookie, browser cookie) is a small piece of data that a server sends to the user's web browser. The browser may store it and send it back with later requests to the same server.
-  Typically, it is used to tell if two requests came from the same browser — keeping a user logged-in, for example. It remembers stateful information for the <a href="/en-US/docs/Web/HTTP/Overview#http_is_stateless_but_not_sessionless">stateless</a> HTTP protocol.</p>
+An **HTTP cookie** (web cookie, browser cookie) is a small piece of data that a server sends to the user's web browser. The browser may store it and send it back with later requests to the same server.
+Typically, it is used to tell if two requests came from the same browser — keeping a user logged-in, for example. It remembers stateful information for the [stateless](/en-US/docs/Web/HTTP/Overview#http_is_stateless_but_not_sessionless) HTTP protocol.
 
-<p>Cookies are mainly used for three purposes:</p>
+Cookies are mainly used for three purposes:
 
-<dl>
- <dt>Session management</dt>
- <dd>Logins, shopping carts, game scores, or anything else the server should remember</dd>
- <dt>Personalization</dt>
- <dd>User preferences, themes, and other settings</dd>
- <dt>Tracking</dt>
- <dd>Recording and analyzing user behavior</dd>
-</dl>
+- Session management
+  - : Logins, shopping carts, game scores, or anything else the server should remember
+- Personalization
+  - : User preferences, themes, and other settings
+- Tracking
+  - : Recording and analyzing user behavior
 
-<p>Cookies were once used for general client-side storage. While this was legitimate when they were the only way to store data on the client, it is now recommended to use modern storage APIs. Cookies are sent with every request, so they can worsen performance (especially for mobile data connections). Modern APIs for client storage are the <a href="/en-US/docs/Web/API/Web_Storage_API" title="DOM Storage">Web Storage API</a> (<code>localStorage</code> and <code>sessionStorage</code>) and <a href="/en-US/docs/Web/API/IndexedDB_API">IndexedDB</a>.</p>
+Cookies were once used for general client-side storage. While this was legitimate when they were the only way to store data on the client, it is now recommended to use modern storage APIs. Cookies are sent with every request, so they can worsen performance (especially for mobile data connections). Modern APIs for client storage are the [Web Storage API](/en-US/docs/Web/API/Web_Storage_API "DOM Storage") (`localStorage` and `sessionStorage`) and [IndexedDB](/en-US/docs/Web/API/IndexedDB_API).
 
-<div class="notecard note">
-  <p><strong>Note:</strong> To see stored cookies (and other storage that a web page can use), you can enable the <a href="/en-US/docs/Tools/Storage_Inspector">Storage Inspector</a> in Developer Tools and select Cookies from the storage tree.</p>
-</div>
+> **Note:** To see stored cookies (and other storage that a web page can use), you can enable the [Storage Inspector](/en-US/docs/Tools/Storage_Inspector) in Developer Tools and select Cookies from the storage tree.
 
-<h2 id="Creating_cookies">Creating cookies</h2>
+## Creating cookies
 
-<p>After receiving an HTTP request, a server can send one or more {{HTTPHeader("Set-Cookie")}} headers with the response. The cookie is usually stored by the browser, and then the cookie is sent with requests made to the same server inside a {{HTTPHeader("Cookie")}} HTTP header. An expiration date or duration can be specified, after which the cookie is no longer sent. Additional restrictions to a specific domain and path can be set, limiting where the cookie is sent. For details about the header attributes mentioned below, refer to the {{HTTPHeader("Set-Cookie")}} reference article.</p>
+After receiving an HTTP request, a server can send one or more {{HTTPHeader("Set-Cookie")}} headers with the response. The cookie is usually stored by the browser, and then the cookie is sent with requests made to the same server inside a {{HTTPHeader("Cookie")}} HTTP header. An expiration date or duration can be specified, after which the cookie is no longer sent. Additional restrictions to a specific domain and path can be set, limiting where the cookie is sent. For details about the header attributes mentioned below, refer to the {{HTTPHeader("Set-Cookie")}} reference article.
 
-<h3 id="The_Set-Cookie_and_Cookie_headers">The <code>Set-Cookie</code> and <code>Cookie</code> headers</h3>
+### The `Set-Cookie` and `Cookie` headers
 
-<p>The {{HTTPHeader("Set-Cookie")}} HTTP response header sends cookies from the server to the user agent. A simple cookie is set like this:</p>
+The {{HTTPHeader("Set-Cookie")}} HTTP response header sends cookies from the server to the user agent. A simple cookie is set like this:
 
-<pre class="brush: html">Set-Cookie: &lt;cookie-name&gt;=&lt;cookie-value&gt;</pre>
+```html
+Set-Cookie: <cookie-name>=<cookie-value>
+```
 
-<p>This shows the server sending headers to tell the client to store a pair of cookies:</p>
+This shows the server sending headers to tell the client to store a pair of cookies:
 
-<pre>HTTP/2.0 200 OK
-Content-Type: text/html
-Set-Cookie: yummy_cookie=choco
-Set-Cookie: tasty_cookie=strawberry
+    HTTP/2.0 200 OK
+    Content-Type: text/html
+    Set-Cookie: yummy_cookie=choco
+    Set-Cookie: tasty_cookie=strawberry
 
-[page content]</pre>
+    [page content]
 
-<p>Then, with every subsequent request to the server, the browser sends back all previously stored cookies to the server using the {{HTTPHeader("Cookie")}} header.</p>
+Then, with every subsequent request to the server, the browser sends back all previously stored cookies to the server using the {{HTTPHeader("Cookie")}} header.
 
-<pre>GET /sample_page.html HTTP/2.0
-Host: www.example.org
-Cookie: yummy_cookie=choco; tasty_cookie=strawberry</pre>
+    GET /sample_page.html HTTP/2.0
+    Host: www.example.org
+    Cookie: yummy_cookie=choco; tasty_cookie=strawberry
 
-<div class="notecard note">
-  <p><strong>Note:</strong> Here's how to use the <code>Set-Cookie</code> header in various server-side applications:</p>
-  <ul>
-    <li><a href="https://secure.php.net/manual/en/function.setcookie.php">PHP</a></li>
-    <li><a href="https://nodejs.org/dist/latest-v14.x/docs/api/http.html#http_response_setheader_name_value">Node.JS</a></li>
-    <li><a href="https://docs.python.org/3/library/http.cookies.html">Python</a></li>
-    <li><a href="https://api.rubyonrails.org/classes/ActionDispatch/Cookies.html">Ruby on Rails</a></li>
-  </ul>
-</div>
+> **Note:** Here's how to use the `Set-Cookie` header in various server-side applications:
+>
+> - [PHP](https://secure.php.net/manual/en/function.setcookie.php)
+> - [Node.JS](https://nodejs.org/dist/latest-v14.x/docs/api/http.html#http_response_setheader_name_value)
+> - [Python](https://docs.python.org/3/library/http.cookies.html)
+> - [Ruby on Rails](https://api.rubyonrails.org/classes/ActionDispatch/Cookies.html)
 
-<h3 id="Define_the_lifetime_of_a_cookie">Define the lifetime of a cookie</h3>
+### Define the lifetime of a cookie
 
-<p>The lifetime of a cookie can be defined in two ways:</p>
+The lifetime of a cookie can be defined in two ways:
 
-<ul>
- <li><em>Session</em> cookies are deleted when the current session ends. The browser defines when the "current session" ends, and some browsers use <em>session restoring</em> when restarting, which can cause session cookies to last indefinitely long.</li>
- <li><em>Permanent</em> cookies are deleted at a date specified by the <code>Expires</code> attribute, or after a period of time specified by the <code>Max-Age</code> attribute.</li>
-</ul>
+- _Session_ cookies are deleted when the current session ends. The browser defines when the "current session" ends, and some browsers use _session restoring_ when restarting, which can cause session cookies to last indefinitely long.
+- _Permanent_ cookies are deleted at a date specified by the `Expires` attribute, or after a period of time specified by the `Max-Age` attribute.
 
-<p>For example:</p>
+For example:
 
-<pre>Set-Cookie: id=a3fWa; Expires=Thu, 31 Oct 2021 07:28:00 GMT;</pre>
+    Set-Cookie: id=a3fWa; Expires=Thu, 31 Oct 2021 07:28:00 GMT;
 
-<div class="notecard note">
-  <p><strong>Note:</strong> When an <code>Expires</code> date is set, the time and date set is relative to the client the cookie is being set on, not the server.</p>
-</div>
+> **Note:** When an `Expires` date is set, the time and date set is relative to the client the cookie is being set on, not the server.
 
-<p>If your site authenticates users, it should regenerate and resend session cookies, even ones that already exist, whenever the user authenticates. This technique helps prevent <a href="/en-US/docs/Web/Security/Types_of_attacks#session_fixation">session fixation attacks</a>, where a third party can reuse a user's session.</p>
+If your site authenticates users, it should regenerate and resend session cookies, even ones that already exist, whenever the user authenticates. This technique helps prevent [session fixation attacks](/en-US/docs/Web/Security/Types_of_attacks#session_fixation), where a third party can reuse a user's session.
 
-<h3 id="Restrict_access_to_cookies">Restrict access to cookies</h3>
+### Restrict access to cookies
 
-<p>There are a couple of ways to ensure that cookies are sent securely and are not accessed by unintended parties or scripts: the <code>Secure</code> attribute and the <code>HttpOnly</code> attribute.</p>
+There are a couple of ways to ensure that cookies are sent securely and are not accessed by unintended parties or scripts: the `Secure` attribute and the `HttpOnly` attribute.
 
-<p>A cookie with the <code>Secure</code> attribute is sent to the server only with an encrypted request over the HTTPS protocol, never with unsecured HTTP (except on localhost), and therefore can't easily be accessed by a {{Glossary("MitM", "man-in-the-middle")}} attacker. Insecure sites (with <code>http:</code> in the URL) can't set cookies with the <code>Secure</code> attribute. However, do not assume that <code>Secure</code> prevents all access to sensitive information in cookies; for example, it can be read and modified by someone with access to the client's hard disk (or JavaScript if the <code>HttpOnly</code> attribute is not set).</p>
+A cookie with the `Secure` attribute is sent to the server only with an encrypted request over the HTTPS protocol, never with unsecured HTTP (except on localhost), and therefore can't easily be accessed by a {{Glossary("MitM", "man-in-the-middle")}} attacker. Insecure sites (with `http:` in the URL) can't set cookies with the `Secure` attribute. However, do not assume that `Secure` prevents all access to sensitive information in cookies; for example, it can be read and modified by someone with access to the client's hard disk (or JavaScript if the `HttpOnly` attribute is not set).
 
-<p>A cookie with the <code>HttpOnly</code> attribute is inaccessible to the JavaScript {{domxref("Document.cookie")}} API; it is sent only to the server. For example, cookies that persist server-side sessions don't need to be available to JavaScript, and should have the <code>HttpOnly</code> attribute. This precaution helps mitigate cross-site scripting (<a href="/en-US/docs/Web/Security/Types_of_attacks#cross-site_scripting_(xss)">XSS</a>) attacks.</p>
+A cookie with the `HttpOnly` attribute is inaccessible to the JavaScript {{domxref("Document.cookie")}} API; it is sent only to the server. For example, cookies that persist server-side sessions don't need to be available to JavaScript, and should have the `HttpOnly` attribute. This precaution helps mitigate cross-site scripting ([XSS](</en-US/docs/Web/Security/Types_of_attacks#cross-site_scripting_(xss)>)) attacks.
 
-<p>Here is an example:</p>
+Here is an example:
 
-<pre>Set-Cookie: id=a3fWa; Expires=Thu, 21 Oct 2021 07:28:00 GMT; Secure; HttpOnly</pre>
+    Set-Cookie: id=a3fWa; Expires=Thu, 21 Oct 2021 07:28:00 GMT; Secure; HttpOnly
 
-<h3 id="Define_where_cookies_are_sent">Define where cookies are sent</h3>
+### Define where cookies are sent
 
-<p>The <code>Domain</code> and <code>Path</code> attributes define the <em>scope</em> of the cookie: what URLs the cookies should be sent to.</p>
+The `Domain` and `Path` attributes define the _scope_ of the cookie: what URLs the cookies should be sent to.
 
-<h4 id="Domain_attribute">Domain attribute</h4>
+#### Domain attribute
 
-<p>The <code>Domain</code> attribute specifies which hosts are allowed to receive the cookie. If unspecified, it defaults to the same {{Glossary("host")}} that set the cookie, <em>excluding subdomains</em>. If <code>Domain</code> <em>is</em> specified, then subdomains are always included. Therefore, specifying <code>Domain</code> is less restrictive than omitting it. However, it can be helpful when subdomains need to share information about a user.</p>
+The `Domain` attribute specifies which hosts are allowed to receive the cookie. If unspecified, it defaults to the same {{Glossary("host")}} that set the cookie, _excluding subdomains_. If `Domain` _is_ specified, then subdomains are always included. Therefore, specifying `Domain` is less restrictive than omitting it. However, it can be helpful when subdomains need to share information about a user.
 
-<p>For example, if <code>Domain=mozilla.org</code> is set, then cookies are available on subdomains like <code>developer.mozilla.org</code>.</p>
+For example, if `Domain=mozilla.org` is set, then cookies are available on subdomains like `developer.mozilla.org`.
 
-<h4 id="Path_attribute">Path attribute</h4>
+#### Path attribute
 
-<p>The <code>Path</code> attribute indicates a URL path that must exist in the requested URL in order to send the <code>Cookie</code> header. The <code>%x2F</code> ("/") character is considered a directory separator, and subdirectories match as well.</p>
+The `Path` attribute indicates a URL path that must exist in the requested URL in order to send the `Cookie` header. The `%x2F` ("/") character is considered a directory separator, and subdirectories match as well.
 
-<p>For example, if <code>Path=/docs</code> is set, these paths match:</p>
+For example, if `Path=/docs` is set, these paths match:
 
-<ul>
- <li><code>/docs</code></li>
- <li><code>/docs/Web/</code></li>
- <li><code>/docs/Web/HTTP</code></li>
-</ul>
+- `/docs`
+- `/docs/Web/`
+- `/docs/Web/HTTP`
 
-<h4 id="SameSite_attribute">SameSite attribute</h4>
+#### SameSite attribute
 
-<p>The <a href="/en-US/docs/Web/HTTP/Headers/Set-Cookie/SameSite"><code>SameSite</code> </a>attribute lets servers specify whether/when cookies are sent with cross-site requests (where {{Glossary("Site")}} is defined by the registrable domain), which provides some protection against cross-site request forgery attacks ({{Glossary("CSRF")}}).</p>
+The [`SameSite` ](/en-US/docs/Web/HTTP/Headers/Set-Cookie/SameSite)attribute lets servers specify whether/when cookies are sent with cross-site requests (where {{Glossary("Site")}} is defined by the registrable domain), which provides some protection against cross-site request forgery attacks ({{Glossary("CSRF")}}).
 
-<p>It takes three possible values: <code>Strict</code>, <code>Lax</code>, and <code>None</code>. With <code>Strict</code>, the cookie is sent only to the same site as the one that originated it; <code>Lax</code> is similar, except that cookies are sent when the user <em>navigates</em> to the cookie's origin site, for example, by following a link from an external site; <code>None</code> specifies that cookies are sent on both originating and cross-site requests, but <em>only in secure contexts</em> (i.e. if <code>SameSite=None</code> then the <code>Secure</code> attribute must also be set). If no <code>SameSite</code> attribute is set then the cookie is treated as <code>Lax</code>.</p>
+It takes three possible values: `Strict`, `Lax`, and `None`. With `Strict`, the cookie is sent only to the same site as the one that originated it; `Lax` is similar, except that cookies are sent when the user _navigates_ to the cookie's origin site, for example, by following a link from an external site; `None` specifies that cookies are sent on both originating and cross-site requests, but *only in secure contexts* (i.e. if `SameSite=None` then the `Secure` attribute must also be set). If no `SameSite` attribute is set then the cookie is treated as `Lax`.
 
-<p>Here is an example:</p>
+Here is an example:
 
-<pre>Set-Cookie: mykey=myvalue; SameSite=Strict</pre>
+    Set-Cookie: mykey=myvalue; SameSite=Strict
 
-<div class="notecard note">
-<p><strong>Note:</strong> Standard related to <code>SameSite</code> recently changed (MDN documents the new behavior above). See the cookies <a href="/en-US/docs/Web/HTTP/Headers/Set-Cookie/SameSite#browser_compatibility">Browser compatibility</a> table for information about how the attribute is handled in specific browser versions:</p>
+> **Note:** Standard related to `SameSite` recently changed (MDN documents the new behavior above). See the cookies [Browser compatibility](/en-US/docs/Web/HTTP/Headers/Set-Cookie/SameSite#browser_compatibility) table for information about how the attribute is handled in specific browser versions:
+>
+> - `SameSite=Lax` is the new default if `SameSite` is not specified. Previously the default was that cookies were sent for all requests.
+> - Cookies with `SameSite=None` must now also specify the `Secure` attribute (they require a secure context).
 
-<ul>
- <li><code>SameSite=Lax</code> is the new default if <code>SameSite</code> is not specified. Previously the default was that cookies were sent for all requests.</li>
- <li>Cookies with <code>SameSite=None</code> must now also specify the <code>Secure</code> attribute (they require a secure context).</li>
-</ul>
-</div>
+#### Cookie prefixes
 
-<h4 id="Cookie_prefixes">Cookie prefixes</h4>
+The design of the cookie mechanism is such that a server is unable to confirm that a cookie was set on a secure origin or even to tell _where_ a cookie was originally set.
 
-<p>The design of the cookie mechanism is such that a server is unable to confirm that a cookie was set on a secure origin or even to tell <em>where</em> a cookie was originally set.</p>
+A vulnerable application on a sub-domain can set a cookie with the `Domain` attribute, which gives access to that cookie on all other subdomains. This mechanism can be abused in a _session fixation_ attack. See [session fixation](/en-US/docs/Web/Security/Types_of_attacks#session_fixation) for primary mitigation methods.
 
-<p>A vulnerable application on a sub-domain can set a cookie with the <code>Domain</code> attribute, which gives access to that cookie on all other subdomains. This mechanism can be abused in a <em>session fixation</em> attack. See <a href="/en-US/docs/Web/Security/Types_of_attacks#session_fixation">session fixation</a> for primary mitigation methods.</p>
+As a [defense-in-depth measure](<https://en.wikipedia.org/wiki/Defense_in_depth_(computing)>), however, it is possible to use _cookie prefixes_ to assert specific facts about the cookie. Two prefixes are available:
 
-<p>As a <a href="https://en.wikipedia.org/wiki/Defense_in_depth_(computing)">defense-in-depth measure</a>, however, it is possible to use <em>cookie prefixes</em> to assert specific facts about the cookie. Two prefixes are available:</p>
+- `__Host-`
+  - : If a cookie name has this prefix, it is accepted in a {{HTTPHeader("Set-Cookie")}} header only if it is also marked with the `Secure` attribute, was sent from a secure origin, does _not_ include a `Domain` attribute, and has the `Path` attribute set to `/`. In this way, these cookies can be seen as "domain-locked".
+- `__Secure-`
+  - : If a cookie name has this prefix, it is accepted in a {{HTTPHeader("Set-Cookie")}} header only if it is marked with the `Secure` attribute and was sent from a secure origin. This is weaker than the `__Host-` prefix.
 
-<dl>
- <dt><code>__Host-</code></dt>
- <dd>If a cookie name has this prefix, it is accepted in a {{HTTPHeader("Set-Cookie")}} header only if it is also marked with the <code>Secure</code> attribute, was sent from a secure origin, does <em>not</em> include a <code>Domain</code> attribute, and has the <code>Path</code> attribute set to <code>/</code>. In this way, these cookies can be seen as "domain-locked".</dd>
- <dt><code>__Secure-</code></dt>
- <dd>If a cookie name has this prefix, it is accepted in a {{HTTPHeader("Set-Cookie")}} header only if it is marked with the <code>Secure</code> attribute and was sent from a secure origin. This is weaker than the <code>__Host-</code> prefix.</dd>
-</dl>
+Cookies with these prefixes that are not compliant with their restrictions are rejected by the browser. Note that this ensures that if a subdomain were to create a cookie with a prefix, it would either be confined to the subdomain or be ignored completely. As the application server checks for a specific cookie name only when determining if the user is authenticated or a CSRF token is correct, this effectively acts as a defense measure against session fixation.
 
-<p>Cookies with these prefixes that are not compliant with their restrictions are rejected by the browser. Note that this ensures that if a subdomain were to create a cookie with a prefix, it would either be confined to the subdomain or be ignored completely. As the application server checks for a specific cookie name only when determining if the user is authenticated or a CSRF token is correct, this effectively acts as a defense measure against session fixation.</p>
+> **Note:** On the application server, the web application _must_ check for the full cookie name including the prefix—user agents _do not_ strip the prefix from the cookie before sending it in a request's {{HTTPHeader("Cookie")}} header.
 
-<div class="notecard note">
-  <p><strong>Note:</strong> On the application server, the web application <em>must</em> check for the full cookie name including the prefix—user agents <em>do not</em> strip the prefix from the cookie before sending it in a request's {{HTTPHeader("Cookie")}} header.</p>
-</div>
+For more information about cookie prefixes and the current state of browser support, see the [Prefixes section of the Set-Cookie reference article](/en-US/docs/Web/HTTP/Headers/Set-Cookie#cookie_prefixes).
 
-<p>For more information about cookie prefixes and the current state of browser support, see the <a href="/en-US/docs/Web/HTTP/Headers/Set-Cookie#cookie_prefixes">Prefixes section of the Set-Cookie reference article</a>.</p>
+#### JavaScript access using Document.cookie
 
-<h4 id="JavaScript_access_using_Document.cookie">JavaScript access using Document.cookie</h4>
+New cookies can be created via JavaScript using the {{domxref("Document.cookie")}} property, and existing cookies can be accessed from JavaScript as well, if the `HttpOnly` flag is not set.
 
-<p>New cookies can be created via JavaScript using the {{domxref("Document.cookie")}} property, and existing cookies can be accessed from JavaScript as well, if the <code>HttpOnly</code> flag is not set.</p>
-
-<pre class="brush: js">document.cookie = "yummy_cookie=choco";
+```js
+document.cookie = "yummy_cookie=choco";
 document.cookie = "tasty_cookie=strawberry";
 console.log(document.cookie);
-// logs "yummy_cookie=choco; tasty_cookie=strawberry"</pre>
+// logs "yummy_cookie=choco; tasty_cookie=strawberry"
+```
 
-<p>Cookies created via JavaScript cannot include the <code>HttpOnly</code> flag.</p>
+Cookies created via JavaScript cannot include the `HttpOnly` flag.
 
-<p>Please note the security issues in the <a href="#security">Security</a> section below. Cookies available to JavaScript can be stolen through XSS.</p>
+Please note the security issues in the [Security](#security) section below. Cookies available to JavaScript can be stolen through XSS.
 
-<h2 id="Security">Security</h2>
+## Security
 
-<div class="notecard note">
-  <p><strong>Note:</strong> Information should be stored in cookies with the understanding that all cookie values are visible to, and can be changed by, the end-user. Depending on the application, it may be desirable to use an opaque identifier which is looked-up by the server or to investigate alternative authentication/confidentiality mechanisms such as JSON Web Tokens.</p>
-</div>
+> **Note:** Information should be stored in cookies with the understanding that all cookie values are visible to, and can be changed by, the end-user. Depending on the application, it may be desirable to use an opaque identifier which is looked-up by the server or to investigate alternative authentication/confidentiality mechanisms such as JSON Web Tokens.
 
-<p>Ways to mitigate attacks involving cookies:</p>
+Ways to mitigate attacks involving cookies:
 
-<ul>
- <li>Use the <code>HttpOnly</code> attribute to prevent access to cookie values via JavaScript.</li>
- <li>Cookies that are used for sensitive information (such as indicating authentication) should have a short lifetime, with the <code>SameSite</code> attribute set to <code>Strict</code> or <code>Lax</code>. (See <a href="#">SameSite cookies</a>, above.) In <a href="/en-US/docs/Web/HTTP/Headers/Set-Cookie#browser_compatibility">browsers that support SameSite</a>, this has the effect of ensuring that the authentication cookie is not sent with cross-site requests, so such a request is effectively unauthenticated to the application server.</li>
-</ul>
+- Use the `HttpOnly` attribute to prevent access to cookie values via JavaScript.
+- Cookies that are used for sensitive information (such as indicating authentication) should have a short lifetime, with the `SameSite` attribute set to `Strict` or `Lax`. (See [SameSite cookies](#), above.) In [browsers that support SameSite](/en-US/docs/Web/HTTP/Headers/Set-Cookie#browser_compatibility), this has the effect of ensuring that the authentication cookie is not sent with cross-site requests, so such a request is effectively unauthenticated to the application server.
 
-<h2 id="Tracking_and_privacy">Tracking and privacy</h2>
+## Tracking and privacy
 
-<h3 id="Third-party_cookies">Third-party cookies</h3>
+### Third-party cookies
 
-<p>A cookie is associated with a domain. If this domain is the same as the domain of the page you are on, the cookie is called a <em>first-party cookie</em>. If the domain is different, it is a <em>third-party cookie</em>. While the server hosting a web page sets first-party cookies, the page may contain images or other components stored on servers in other domains (for example, ad banners), which may set third-party cookies. These are mainly used for advertising and tracking across the web. See for example the <a href="https://policies.google.com/technologies/types">types of cookies used by Google</a>.</p>
+A cookie is associated with a domain. If this domain is the same as the domain of the page you are on, the cookie is called a _first-party cookie_. If the domain is different, it is a _third-party cookie_. While the server hosting a web page sets first-party cookies, the page may contain images or other components stored on servers in other domains (for example, ad banners), which may set third-party cookies. These are mainly used for advertising and tracking across the web. See for example the [types of cookies used by Google](https://policies.google.com/technologies/types).
 
-<p>A third party server can build up a profile of a user's browsing history and habits based on cookies sent to it by the same browser when accessing multiple sites. Firefox, by default, blocks third-party cookies that are known to contain trackers. Third-party cookies (or just tracking cookies) may also be blocked by other browser settings or extensions. Cookie blocking can cause some third-party components (such as social media widgets) to not function as intended.</p>
+A third party server can build up a profile of a user's browsing history and habits based on cookies sent to it by the same browser when accessing multiple sites. Firefox, by default, blocks third-party cookies that are known to contain trackers. Third-party cookies (or just tracking cookies) may also be blocked by other browser settings or extensions. Cookie blocking can cause some third-party components (such as social media widgets) to not function as intended.
 
-<div class="notecard note">
-  <p><strong>Note:</strong> Servers can (and should) set the cookie <a href="/en-US/docs/Web/HTTP/Headers/Set-Cookie/SameSite">SameSite attribute</a> to specify whether or not cookies may be sent to third party sites.</p>
-</div>
+> **Note:** Servers can (and should) set the cookie [SameSite attribute](/en-US/docs/Web/HTTP/Headers/Set-Cookie/SameSite) to specify whether or not cookies may be sent to third party sites.
 
-<h3 id="Cookie-related_regulations">Cookie-related regulations</h3>
+### Cookie-related regulations
 
-<p>Legislation or regulations that cover the use of cookies include:</p>
+Legislation or regulations that cover the use of cookies include:
 
-<ul>
- <li>The General Data Privacy Regulation (GDPR) in the European Union</li>
- <li>The ePrivacy Directive in the EU</li>
- <li>The California Consumer Privacy Act</li>
-</ul>
+- The General Data Privacy Regulation (GDPR) in the European Union
+- The ePrivacy Directive in the EU
+- The California Consumer Privacy Act
 
-<p>These regulations have global reach, because they apply to any site on the <em>World Wide</em> Web that is accessed by users from these jurisdictions (the EU and California, with the caveat that California's law applies only to entities with gross revenue over 25 million USD, among other things.)</p>
+These regulations have global reach, because they apply to any site on the _World Wide_ Web that is accessed by users from these jurisdictions (the EU and California, with the caveat that California's law applies only to entities with gross revenue over 25 million USD, among other things.)
 
-<p>These regulations include requirements such as:</p>
+These regulations include requirements such as:
 
-<ul>
- <li>Notifying users that your site uses cookies.</li>
- <li>Allowing users to opt out of receiving some or all cookies.</li>
- <li>Allowing users to use the bulk of your service without receiving cookies.</li>
-</ul>
+- Notifying users that your site uses cookies.
+- Allowing users to opt out of receiving some or all cookies.
+- Allowing users to use the bulk of your service without receiving cookies.
 
-<p>There may be other regulations governing the use of cookies in your locality. The burden is on you to know and comply with these regulations. There are companies that offer "cookie banner" code that helps you comply with these regulations.</p>
+There may be other regulations governing the use of cookies in your locality. The burden is on you to know and comply with these regulations. There are companies that offer "cookie banner" code that helps you comply with these regulations.
 
-<h2 id="Other_ways_to_store_information_in_the_browser">Other ways to store information in the browser</h2>
+## Other ways to store information in the browser
 
-<p>Another approach to storing data in the browser is the <a href="/en-US/docs/Web/API/Web_Storage_API/Using_the_Web_Storage_API">Web Storage API</a>. The <a href="/en-US/docs/Web/API/Window/sessionStorage">window.sessionStorage</a> and <a href="/en-US/docs/Web/API/Window/localStorage">window.localStorage</a> properties correspond to session and permanent cookies in duration, but have larger storage limits than cookies, and are never sent to a server. More structured and larger amounts of data can be stored using the <a href="/en-US/docs/Web/API/IndexedDB_API">IndexedDB API</a>, or a library built on it.</p>
+Another approach to storing data in the browser is the [Web Storage API](/en-US/docs/Web/API/Web_Storage_API/Using_the_Web_Storage_API). The [window.sessionStorage](/en-US/docs/Web/API/Window/sessionStorage) and [window.localStorage](/en-US/docs/Web/API/Window/localStorage) properties correspond to session and permanent cookies in duration, but have larger storage limits than cookies, and are never sent to a server. More structured and larger amounts of data can be stored using the [IndexedDB API](/en-US/docs/Web/API/IndexedDB_API), or a library built on it.
 
-<p>Other techniques have been created to cause cookies to be recreated after they are deleted, known as "zombie" cookies. These techniques violate the principles of user privacy and user control, may violate data privacy regulations, and could expose a website using them to legal liability.</p>
+Other techniques have been created to cause cookies to be recreated after they are deleted, known as "zombie" cookies. These techniques violate the principles of user privacy and user control, may violate data privacy regulations, and could expose a website using them to legal liability.
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
- <li>{{HTTPHeader("Set-Cookie")}}</li>
- <li>{{HTTPHeader("Cookie")}}</li>
- <li>{{domxref("Document.cookie")}}</li>
- <li>{{domxref("Navigator.cookieEnabled")}}</li>
- <li><a href="/en-US/docs/Web/HTTP/Headers/Set-Cookie/SameSite">SameSite cookies</a></li>
- <li><a href="/en-US/docs/Tools/Storage_Inspector">Inspecting cookies using the Storage Inspector</a></li>
- <li><a href="https://datatracker.ietf.org/doc/html/rfc6265">Cookie specification: RFC 6265</a></li>
- <li><a href="https://en.wikipedia.org/wiki/HTTP_cookie">HTTP cookie on Wikipedia</a></li>
- <li><a href="https://gdpr.eu/cookies/">Cookies, the GDPR, and the ePrivacy Directive</a></li>
-</ul>
+- {{HTTPHeader("Set-Cookie")}}
+- {{HTTPHeader("Cookie")}}
+- {{domxref("Document.cookie")}}
+- {{domxref("Navigator.cookieEnabled")}}
+- [SameSite cookies](/en-US/docs/Web/HTTP/Headers/Set-Cookie/SameSite)
+- [Inspecting cookies using the Storage Inspector](/en-US/docs/Tools/Storage_Inspector)
+- [Cookie specification: RFC 6265](https://datatracker.ietf.org/doc/html/rfc6265)
+- [HTTP cookie on Wikipedia](https://en.wikipedia.org/wiki/HTTP_cookie)
+- [Cookies, the GDPR, and the ePrivacy Directive](https://gdpr.eu/cookies/)
diff --git a/files/en-us/web/http/cors/errors/corsalloworiginnotmatchingorigin/index.md b/files/en-us/web/http/cors/errors/corsalloworiginnotmatchingorigin/index.md
index d1853a35707f766..ff21cb90ef6e559 100644
--- a/files/en-us/web/http/cors/errors/corsalloworiginnotmatchingorigin/index.md
+++ b/files/en-us/web/http/cors/errors/corsalloworiginnotmatchingorigin/index.md
@@ -2,54 +2,53 @@
 title: 'Reason: CORS header ''Access-Control-Allow-Origin'' does not match ''xyz'''
 slug: Web/HTTP/CORS/Errors/CORSAllowOriginNotMatchingOrigin
 tags:
-- CORS
-- CORSAllowOriginNotMatchingOrigin
-- Cross-Origin
-- Error
-- HTTP
-- HTTPS
-- Messages
-- Reasons
-- Security
-- console
-- troubleshooting
+  - CORS
+  - CORSAllowOriginNotMatchingOrigin
+  - Cross-Origin
+  - Error
+  - HTTP
+  - HTTPS
+  - Messages
+  - Reasons
+  - Security
+  - console
+  - troubleshooting
 ---
-<div>{{HTTPSidebar}}</div>
+{{HTTPSidebar}}
 
-<h2 id="Reason">Reason</h2>
+## Reason
 
-<pre
-  class="brush: html">Reason: CORS header 'Access-Control-Allow-Origin' does not match 'xyz'</pre>
+```html
+Reason: CORS header 'Access-Control-Allow-Origin' does not match 'xyz'
+```
 
-<h2 id="What_went_wrong">What went wrong?</h2>
+## What went wrong?
 
-<p>The origin making the request does not match the origin permitted by the {{HTTPHeader("Access-Control-Allow-Origin")}} header. This error can also occur if the response includes more than one
-  <code>Access-Control-Allow-Origin</code> header.</p>
+The origin making the request does not match the origin permitted by the {{HTTPHeader("Access-Control-Allow-Origin")}} header. This error can also occur if the response includes more than one
+`Access-Control-Allow-Origin` header.
 
-<p>If the service your code is accessing uses a CORS request under your control, make
-  sure it is configured to include your origin in its
-  <code>Access-Control-Allow-Origin</code> header. In addition, confirm that only one such header is
-  included in responses, and that it includes only a single origin.</p>
+If the service your code is accessing uses a CORS request under your control, make
+sure it is configured to include your origin in its
+`Access-Control-Allow-Origin` header. In addition, confirm that only one such header is
+included in responses, and that it includes only a single origin.
 
-<p>For example, in Apache, add a line such as the following to the server's configuration
-  (within the appropriate <code>&lt;Directory&gt;</code>, <code>&lt;Location&gt;</code>,
-  <code>&lt;Files&gt;</code>, or <code>&lt;VirtualHost&gt;</code> section). The
-  configuration is typically found in a <code>.conf</code> file (<code>httpd.conf</code>
-  and <code>apache.conf</code> are common names for these), or in an
-  <code>.htaccess</code> file.</p>
+For example, in Apache, add a line such as the following to the server's configuration
+(within the appropriate `<Directory>`, `<Location>`,
+`<Files>`, or `<VirtualHost>` section). The
+configuration is typically found in a `.conf` file (`httpd.conf`
+and `apache.conf` are common names for these), or in an
+`.htaccess` file.
 
-<pre>Header set Access-Control-Allow-Origin '<em>origin</em>'</pre>
+    Header set Access-Control-Allow-Origin 'origin'
 
-<p>For Nginx, the command to set up this header is:</p>
+For Nginx, the command to set up this header is:
 
-<pre>add_header 'Access-Control-Allow-Origin' '<em>origin</em>'</pre>
+    add_header 'Access-Control-Allow-Origin' 'origin'
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
-  <li><a href="/en-US/docs/Web/HTTP/CORS/Errors">CORS errors</a></li>
-  <li>Glossary: {{Glossary("CORS")}}</li>
-  <li><a href="/en-US/docs/Web/HTTP/CORS">CORS introduction</a></li>
-  <li><a href="https://enable-cors.org/server.html">Enable CORS: I want to add CORS
-      support to my server</a></li>
-</ul>
+- [CORS errors](/en-US/docs/Web/HTTP/CORS/Errors)
+- Glossary: {{Glossary("CORS")}}
+- [CORS introduction](/en-US/docs/Web/HTTP/CORS)
+- [Enable CORS: I want to add CORS
+  support to my server](https://enable-cors.org/server.html)
diff --git a/files/en-us/web/http/cors/errors/corsdidnotsucceed/index.md b/files/en-us/web/http/cors/errors/corsdidnotsucceed/index.md
index 02e07ddc65d2529..dcd7936cb29e19a 100644
--- a/files/en-us/web/http/cors/errors/corsdidnotsucceed/index.md
+++ b/files/en-us/web/http/cors/errors/corsdidnotsucceed/index.md
@@ -2,52 +2,49 @@
 title: 'Reason: CORS request did not succeed'
 slug: Web/HTTP/CORS/Errors/CORSDidNotSucceed
 tags:
-- CORS
-- CORSDidNotSucceed
-- Cross-Origin
-- Error
-- HTTP
-- HTTPS
-- Messages
-- Reasons
-- Security
-- console
-- troubleshooting
+  - CORS
+  - CORSDidNotSucceed
+  - Cross-Origin
+  - Error
+  - HTTP
+  - HTTPS
+  - Messages
+  - Reasons
+  - Security
+  - console
+  - troubleshooting
 ---
-<div>{{HTTPSidebar}}</div>
+{{HTTPSidebar}}
 
-<h2 id="Reason">Reason</h2>
+## Reason
 
-<pre class="brush: html">Reason: CORS request did not succeed</pre>
+```html
+Reason: CORS request did not succeed
+```
 
-<h2 id="What_went_wrong">What went wrong?</h2>
+## What went wrong?
 
-<p>The {{Glossary("HTTP")}} request which makes use of CORS failed because the HTTP
-  connection failed at either the network or protocol level. The error is not directly
-  related to CORS, but is a fundamental network error of some kind.</p>
+The {{Glossary("HTTP")}} request which makes use of CORS failed because the HTTP
+connection failed at either the network or protocol level. The error is not directly
+related to CORS, but is a fundamental network error of some kind.
 
-<p>In many cases, it is caused by a browser plugin (e.g. an ad blocker or privacy
-  protector) blocking the request.</p>
+In many cases, it is caused by a browser plugin (e.g. an ad blocker or privacy
+protector) blocking the request.
 
-<p>Other possible causes include:</p>
+Other possible causes include:
 
-<ul>
-  <li>Trying to access an <code>https</code> resource that has an invalid certificate will
-    cause this error.</li>
-  <li>Trying to access an <code>http</code> resource from a page with an
-    <code>https</code> origin will also cause this error.</li>
-  <li>As of Firefox 68, <code>https</code> pages are not permitted to access
-    <code>http://localhost</code>, although this may be changed by <a
-      href="https://bugzilla.mozilla.org/show_bug.cgi?id=1488740">Bug 1488740</a>.</li>
-  <li>The server did not respond to the actual request (even if it responded to the
-    {{Glossary("Preflight request")}}). One scenario might be an HTTP service being
-    developed that panicked without returning any data.</li>
-</ul>
+- Trying to access an `https` resource that has an invalid certificate will
+  cause this error.
+- Trying to access an `http` resource from a page with an
+  `https` origin will also cause this error.
+- As of Firefox 68, `https` pages are not permitted to access
+  `http://localhost`, although this may be changed by [Bug 1488740](https://bugzilla.mozilla.org/show_bug.cgi?id=1488740).
+- The server did not respond to the actual request (even if it responded to the
+  {{Glossary("Preflight request")}}). One scenario might be an HTTP service being
+  developed that panicked without returning any data.
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
-  <li><a href="/en-US/docs/Web/HTTP/CORS/Errors">CORS errors</a></li>
-  <li>Glossary: {{Glossary("CORS")}}</li>
-  <li><a href="/en-US/docs/Web/HTTP/CORS">CORS introduction</a></li>
-</ul>
+- [CORS errors](/en-US/docs/Web/HTTP/CORS/Errors)
+- Glossary: {{Glossary("CORS")}}
+- [CORS introduction](/en-US/docs/Web/HTTP/CORS)
diff --git a/files/en-us/web/http/cors/errors/corsdisabled/index.md b/files/en-us/web/http/cors/errors/corsdisabled/index.md
index cb9fdbc9a93011b..4dfb9f11608b7ad 100644
--- a/files/en-us/web/http/cors/errors/corsdisabled/index.md
+++ b/files/en-us/web/http/cors/errors/corsdisabled/index.md
@@ -2,44 +2,44 @@
 title: 'Reason: CORS disabled'
 slug: Web/HTTP/CORS/Errors/CORSDisabled
 tags:
-- Authentication
-- Authentication Article
-- CORS
-- Cross-Origin
-- Disabled
-- Errors
-- HTTP
-- HTTPS
-- Messages
-- Resource
-- Same Origin
-- Same-origin
-- Security
-- Sharing
-- Validation
-- secure
-- troubleshooting
+  - Authentication
+  - Authentication Article
+  - CORS
+  - Cross-Origin
+  - Disabled
+  - Errors
+  - HTTP
+  - HTTPS
+  - Messages
+  - Resource
+  - Same Origin
+  - Same-origin
+  - Security
+  - Sharing
+  - Validation
+  - secure
+  - troubleshooting
 ---
-<div>{{HTTPSidebar}}</div>
+{{HTTPSidebar}}
 
-<h2 id="Reason">Reason</h2>
+## Reason
 
-<pre class="brush: html">Reason: CORS disabled</pre>
+```html
+Reason: CORS disabled
+```
 
-<h2 id="What_went_wrong">What went wrong?</h2>
+## What went wrong?
 
-<p>A request that needs to use {{Glossary("CORS")}} was attempted, but CORS is disabled in
-  the user's browser. When this happens, the user needs to turn CORS back on in their
-  browser.</p>
+A request that needs to use {{Glossary("CORS")}} was attempted, but CORS is disabled in
+the user's browser. When this happens, the user needs to turn CORS back on in their
+browser.
 
-<p>In Firefox, the preference that disables CORS is <code>content.cors.disable</code>.
-  Setting this to <code>true</code> disables CORS, so whenever that's the case, CORS
-  requests will always fail with this error.</p>
+In Firefox, the preference that disables CORS is `content.cors.disable`.
+Setting this to `true` disables CORS, so whenever that's the case, CORS
+requests will always fail with this error.
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
-  <li><a href="/en-US/docs/Web/HTTP/CORS/Errors">CORS errors</a></li>
-  <li>Glossary: {{Glossary("CORS")}}</li>
-  <li><a href="/en-US/docs/Web/HTTP/CORS">CORS introduction</a></li>
-</ul>
+- [CORS errors](/en-US/docs/Web/HTTP/CORS/Errors)
+- Glossary: {{Glossary("CORS")}}
+- [CORS introduction](/en-US/docs/Web/HTTP/CORS)
diff --git a/files/en-us/web/http/cors/errors/corsexternalredirectnotallowed/index.md b/files/en-us/web/http/cors/errors/corsexternalredirectnotallowed/index.md
index 4d2c5b07ef21c9a..80d2d22daf8d6b5 100644
--- a/files/en-us/web/http/cors/errors/corsexternalredirectnotallowed/index.md
+++ b/files/en-us/web/http/cors/errors/corsexternalredirectnotallowed/index.md
@@ -2,44 +2,43 @@
 title: 'Reason: CORS request external redirect not allowed'
 slug: Web/HTTP/CORS/Errors/CORSExternalRedirectNotAllowed
 tags:
-- CORS
-- CORSOriginHeaderNotAdded
-- Cross-Origin
-- Error
-- HTTP
-- HTTPS
-- Messages
-- Reasons
-- Security
-- console
-- troubleshooting
+  - CORS
+  - CORSOriginHeaderNotAdded
+  - Cross-Origin
+  - Error
+  - HTTP
+  - HTTPS
+  - Messages
+  - Reasons
+  - Security
+  - console
+  - troubleshooting
 ---
-<div>{{HTTPSidebar}}</div>
+{{HTTPSidebar}}
 
-<h2 id="Reason">Reason</h2>
+## Reason
 
-<pre
-  class="brush: html">Reason: CORS request external redirect not allowed</pre>
+```html
+Reason: CORS request external redirect not allowed
+```
 
-<h2 id="What_went_wrong">What went wrong?</h2>
+## What went wrong?
 
-<p>The {{Glossary("CORS")}} request was responded to by the server with an HTTP redirect
-  to a URL on a different origin than the original request, which is not permitted during
-  CORS requests.</p>
+The {{Glossary("CORS")}} request was responded to by the server with an HTTP redirect
+to a URL on a different origin than the original request, which is not permitted during
+CORS requests.
 
-<p>For example, if the page <code>https://service.tld/fetchdata</code> were requested, and
-  the HTTP response is "301 Moved Permanently", "307 Temporary Redirect", or "308
-  Permanent Redirect" with a <code>Location</code> of
-  <code>https://anotherservice.net/getdata</code>, the CORS request will fail in this
-  manner.</p>
+For example, if the page `https://service.tld/fetchdata` were requested, and
+the HTTP response is "301 Moved Permanently", "307 Temporary Redirect", or "308
+Permanent Redirect" with a `Location` of
+`https://anotherservice.net/getdata`, the CORS request will fail in this
+manner.
 
-<p>To fix the problem, update your code to use the new URL as reported by the redirect,
-  thereby avoiding the redirect.</p>
+To fix the problem, update your code to use the new URL as reported by the redirect,
+thereby avoiding the redirect.
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
-  <li><a href="/en-US/docs/Web/HTTP/CORS/Errors">CORS errors</a></li>
-  <li>Glossary: {{Glossary("CORS")}}</li>
-  <li><a href="/en-US/docs/Web/HTTP/CORS">CORS introduction</a></li>
-</ul>
+- [CORS errors](/en-US/docs/Web/HTTP/CORS/Errors)
+- Glossary: {{Glossary("CORS")}}
+- [CORS introduction](/en-US/docs/Web/HTTP/CORS)
diff --git a/files/en-us/web/http/cors/errors/corsinvalidallowheader/index.md b/files/en-us/web/http/cors/errors/corsinvalidallowheader/index.md
index 07c2cdda84be5df..f18f17cc9988eb1 100644
--- a/files/en-us/web/http/cors/errors/corsinvalidallowheader/index.md
+++ b/files/en-us/web/http/cors/errors/corsinvalidallowheader/index.md
@@ -2,47 +2,45 @@
 title: 'Reason: invalid token ‘xyz’ in CORS header ‘Access-Control-Allow-Headers’'
 slug: Web/HTTP/CORS/Errors/CORSInvalidAllowHeader
 tags:
-- CORS
-- CORSInvalidAllowHeader
-- Cross-Origin
-- Error
-- HTTP
-- HTTPS
-- Messages
-- Reasons
-- Security
-- console
-- troubleshooting
+  - CORS
+  - CORSInvalidAllowHeader
+  - Cross-Origin
+  - Error
+  - HTTP
+  - HTTPS
+  - Messages
+  - Reasons
+  - Security
+  - console
+  - troubleshooting
 ---
-<div>{{HTTPSidebar}}</div>
+{{HTTPSidebar}}
 
-<h2 id="Reason">Reason</h2>
+## Reason
 
-<pre
-  class="brush: html">Reason: invalid token ‘xyz’ in CORS header ‘Access-Control-Allow-Headers’</pre>
+```html
+Reason: invalid token ‘xyz’ in CORS header ‘Access-Control-Allow-Headers’
+```
 
-<h2 id="What_went_wrong">What went wrong?</h2>
+## What went wrong?
 
-<p>The response to the {{Glossary("CORS")}} request that was sent by the server includes
-  an {{HTTPHeader("Access-Control-Allow-Headers")}} header which includes at least one
-  invalid header name.</p>
+The response to the {{Glossary("CORS")}} request that was sent by the server includes
+an {{HTTPHeader("Access-Control-Allow-Headers")}} header which includes at least one
+invalid header name.
 
-<p>The <code>Access-Control-Allow-Headers</code> header is sent by the server in response
-  to a {{Glossary("preflight request")}}; it lets the client know which <a
-    href="/en-US/docs/Web/HTTP/Headers">HTTP headers</a> are permitted in CORS requests.
-  If the client {{Glossary("user agent")}} finds among the comma-delineated values
-  provided by the header any header name it does not recognize, this error occurs.</p>
+The `Access-Control-Allow-Headers` header is sent by the server in response
+to a {{Glossary("preflight request")}}; it lets the client know which [HTTP headers](/en-US/docs/Web/HTTP/Headers) are permitted in CORS requests.
+If the client {{Glossary("user agent")}} finds among the comma-delineated values
+provided by the header any header name it does not recognize, this error occurs.
 
-<p>This is a problem that most likely can only be fixed on the server side, by modifying
-  the server's configuration to no longer send the invalid or unknown header name with the
-  <code>Access-Control-Allow-Headers</code> header. It may also be worth checking to
-  ensure that the user agent or HTTP library you're using on the client is up-to-date.</p>
+This is a problem that most likely can only be fixed on the server side, by modifying
+the server's configuration to no longer send the invalid or unknown header name with the
+`Access-Control-Allow-Headers` header. It may also be worth checking to
+ensure that the user agent or HTTP library you're using on the client is up-to-date.
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
-  <li><a href="/en-US/docs/Web/HTTP/CORS/Errors">CORS errors</a></li>
-  <li>Glossary: {{Glossary("CORS")}}</li>
-  <li><a href="/en-US/docs/Web/HTTP/CORS">CORS introduction</a></li>
-  <li><a href="/en-US/docs/Web/HTTP/Headers">HTTP headers</a></li>
-</ul>
+- [CORS errors](/en-US/docs/Web/HTTP/CORS/Errors)
+- Glossary: {{Glossary("CORS")}}
+- [CORS introduction](/en-US/docs/Web/HTTP/CORS)
+- [HTTP headers](/en-US/docs/Web/HTTP/Headers)
diff --git a/files/en-us/web/http/cors/errors/corsinvalidallowmethod/index.md b/files/en-us/web/http/cors/errors/corsinvalidallowmethod/index.md
index 5b8a9fe6ddb0c19..4e10d3b19dcad9f 100644
--- a/files/en-us/web/http/cors/errors/corsinvalidallowmethod/index.md
+++ b/files/en-us/web/http/cors/errors/corsinvalidallowmethod/index.md
@@ -2,48 +2,47 @@
 title: 'Reason: invalid token ‘xyz’ in CORS header ‘Access-Control-Allow-Methods’'
 slug: Web/HTTP/CORS/Errors/CORSInvalidAllowMethod
 tags:
-- CORS
-- CORSInvalidAllowMethod
-- Cross-Origin
-- Error
-- HTTP
-- HTTPS
-- Messages
-- Reasons
-- Security
-- console
-- troubleshooting
+  - CORS
+  - CORSInvalidAllowMethod
+  - Cross-Origin
+  - Error
+  - HTTP
+  - HTTPS
+  - Messages
+  - Reasons
+  - Security
+  - console
+  - troubleshooting
 ---
-<div>{{HTTPSidebar}}</div>
+{{HTTPSidebar}}
 
-<h2 id="Reason">Reason</h2>
+## Reason
 
-<pre
-  class="brush: html">Reason: invalid token ‘xyz’ in CORS header ‘Access-Control-Allow-Methods’</pre>
+```html
+Reason: invalid token ‘xyz’ in CORS header ‘Access-Control-Allow-Methods’
+```
 
-<h2 id="What_went_wrong">What went wrong?</h2>
+## What went wrong?
 
-<p>The response to the {{Glossary("CORS")}} request that was sent by the server includes
-  an {{HTTPHeader("Access-Control-Allow-Methods")}} header which includes at least one
-  invalid method name.</p>
+The response to the {{Glossary("CORS")}} request that was sent by the server includes
+an {{HTTPHeader("Access-Control-Allow-Methods")}} header which includes at least one
+invalid method name.
 
-<p>The <code>Access-Control-Allow-Methods</code> header is sent by the server to let the
-  client know what <a href="/en-US/docs/Web/HTTP/Methods">HTTP request methods</a> it
-  supports for CORS requests. The header's value is a comma-delineated string of HTTP
-  method names, such as {{HTTPMethod("GET")}}, {{HTTPMethod("POST")}}, or
-  {{HTTPMethod("HEAD")}}. If any of the specified values are not recognized by the client
-  {{Glossary("user agent")}}, this error occurs.</p>
+The `Access-Control-Allow-Methods` header is sent by the server to let the
+client know what [HTTP request methods](/en-US/docs/Web/HTTP/Methods) it
+supports for CORS requests. The header's value is a comma-delineated string of HTTP
+method names, such as {{HTTPMethod("GET")}}, {{HTTPMethod("POST")}}, or
+{{HTTPMethod("HEAD")}}. If any of the specified values are not recognized by the client
+{{Glossary("user agent")}}, this error occurs.
 
-<p>This is a problem that most likely can only be fixed on the server side, by modifying
-  the server's configuration to no longer send the invalid or unknown method name with the
-  <code>Access-Control-Allow-Methods</code> header. It may also be worth checking to
-  ensure that the user agent or HTTP library you're using on the client is up-to-date.</p>
+This is a problem that most likely can only be fixed on the server side, by modifying
+the server's configuration to no longer send the invalid or unknown method name with the
+`Access-Control-Allow-Methods` header. It may also be worth checking to
+ensure that the user agent or HTTP library you're using on the client is up-to-date.
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
-  <li><a href="/en-US/docs/Web/HTTP/CORS/Errors">CORS errors</a></li>
-  <li>Glossary: {{Glossary("CORS")}}</li>
-  <li><a href="/en-US/docs/Web/HTTP/CORS">CORS introduction</a></li>
-  <li><a href="/en-US/docs/Web/HTTP/Methods">HTTP request methods</a></li>
-</ul>
+- [CORS errors](/en-US/docs/Web/HTTP/CORS/Errors)
+- Glossary: {{Glossary("CORS")}}
+- [CORS introduction](/en-US/docs/Web/HTTP/CORS)
+- [HTTP request methods](/en-US/docs/Web/HTTP/Methods)
diff --git a/files/en-us/web/http/cors/errors/corsmethodnotfound/index.md b/files/en-us/web/http/cors/errors/corsmethodnotfound/index.md
index bb0d5f8eb50860c..1717761cdebfb44 100644
--- a/files/en-us/web/http/cors/errors/corsmethodnotfound/index.md
+++ b/files/en-us/web/http/cors/errors/corsmethodnotfound/index.md
@@ -2,53 +2,50 @@
 title: 'Reason: Did not find method in CORS header ‘Access-Control-Allow-Methods’'
 slug: Web/HTTP/CORS/Errors/CORSMethodNotFound
 tags:
-- CORS
-- CORSMethodNotFound
-- Cross-Origin
-- Error
-- HTTP
-- HTTPS
-- Messages
-- Reasons
-- Security
-- console
-- troubleshooting
+  - CORS
+  - CORSMethodNotFound
+  - Cross-Origin
+  - Error
+  - HTTP
+  - HTTPS
+  - Messages
+  - Reasons
+  - Security
+  - console
+  - troubleshooting
 ---
-<div>{{HTTPSidebar}}</div>
+{{HTTPSidebar}}
 
-<h2 id="Reason">Reason</h2>
+## Reason
 
-<pre
-  class="brush: html">Reason: Did not find method in CORS header ‘Access-Control-Allow-Methods’</pre>
+```html
+Reason: Did not find method in CORS header ‘Access-Control-Allow-Methods’
+```
 
-<h2 id="What_went_wrong">What went wrong?</h2>
+## What went wrong?
 
-<p>The HTTP method being used by the {{Glossary("CORS")}} request is not included in the
-  list of methods specified by the response's
-  {{HTTPHeader("Access-Control-Allow-Methods")}} header. This header specifies a
-  comma-delineated list of the HTTP methods which may be used when using CORS to access
-  the URL specified in the request; if the request is using any other method, this error
-  occurs.</p>
+The HTTP method being used by the {{Glossary("CORS")}} request is not included in the
+list of methods specified by the response's
+{{HTTPHeader("Access-Control-Allow-Methods")}} header. This header specifies a
+comma-delineated list of the HTTP methods which may be used when using CORS to access
+the URL specified in the request; if the request is using any other method, this error
+occurs.
 
-<p>For example, if the response includes:</p>
+For example, if the response includes:
 
-<pre>Access-Control-Allow-Methods: GET,HEAD,POST</pre>
+    Access-Control-Allow-Methods: GET,HEAD,POST
 
-<p>Trying to use a {{HTTPMethod("PUT")}} request will fail with this error.</p>
+Trying to use a {{HTTPMethod("PUT")}} request will fail with this error.
 
-<p>Make sure your code only uses the permitted HTTP methods when accessing the service.
-</p>
+Make sure your code only uses the permitted HTTP methods when accessing the service.
 
-<p><strong>Note:</strong> If the server includes any unrecognized or undefined method
-  names in its <code>Access-Control-Allow-methods</code> header, a different error occurs:
-  <code><a href="/en-US/docs/Web/HTTP/CORS/Errors/CORSInvalidAllowMethod">Reason: invalid token ‘xyz' in CORS header ‘Access-Control-Allow-Methods’</a></code>.
-</p>
+**Note:** If the server includes any unrecognized or undefined method
+names in its `Access-Control-Allow-methods` header, a different error occurs:
+[`Reason: invalid token ‘xyz' in CORS header ‘Access-Control-Allow-Methods’`](/en-US/docs/Web/HTTP/CORS/Errors/CORSInvalidAllowMethod).
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
-  <li><a href="/en-US/docs/Web/HTTP/CORS/Errors">CORS errors</a></li>
-  <li>Glossary: {{Glossary("CORS")}}</li>
-  <li><a href="/en-US/docs/Web/HTTP/CORS">CORS introduction</a></li>
-  <li><a href="/en-US/docs/Web/HTTP/Methods">HTTP request methods</a></li>
-</ul>
+- [CORS errors](/en-US/docs/Web/HTTP/CORS/Errors)
+- Glossary: {{Glossary("CORS")}}
+- [CORS introduction](/en-US/docs/Web/HTTP/CORS)
+- [HTTP request methods](/en-US/docs/Web/HTTP/Methods)
diff --git a/files/en-us/web/http/cors/errors/corsmissingallowcredentials/index.md b/files/en-us/web/http/cors/errors/corsmissingallowcredentials/index.md
index 00b9f0e9e23a250..6f89fe8c4984670 100644
--- a/files/en-us/web/http/cors/errors/corsmissingallowcredentials/index.md
+++ b/files/en-us/web/http/cors/errors/corsmissingallowcredentials/index.md
@@ -2,53 +2,50 @@
 title: 'Reason: expected ‘true’ in CORS header ‘Access-Control-Allow-Credentials’'
 slug: Web/HTTP/CORS/Errors/CORSMIssingAllowCredentials
 tags:
-- CORS
-- CORSMissingAllowCredentials
-- Cross-Origin
-- Error
-- HTTP
-- HTTPS
-- Messages
-- Reasons
-- Security
-- console
-- troubleshooting
+  - CORS
+  - CORSMissingAllowCredentials
+  - Cross-Origin
+  - Error
+  - HTTP
+  - HTTPS
+  - Messages
+  - Reasons
+  - Security
+  - console
+  - troubleshooting
 ---
-<div>{{HTTPSidebar}}</div>
+{{HTTPSidebar}}
 
-<h2 id="Reason">Reason</h2>
+## Reason
 
-<pre
-  class="brush: html">Reason: expected ‘true’ in CORS header ‘Access-Control-Allow-Credentials’</pre>
+```html
+Reason: expected ‘true’ in CORS header ‘Access-Control-Allow-Credentials’
+```
 
-<h2 id="What_went_wrong">What went wrong?</h2>
+## What went wrong?
 
-<p>The {{Glossary("CORS")}} request requires that the server permit the use of
-  credentials, but the server's {{HTTPHeader("Access-Control-Allow-Credentials")}}
-  header's value isn't set to <code>true</code> to enable their use.</p>
+The {{Glossary("CORS")}} request requires that the server permit the use of
+credentials, but the server's {{HTTPHeader("Access-Control-Allow-Credentials")}}
+header's value isn't set to `true` to enable their use.
 
-<p>To fix this problem on the client side, revise the code to not request the use of
-  credentials.</p>
+To fix this problem on the client side, revise the code to not request the use of
+credentials.
 
-<ul>
-  <li>If the request is being issued using {{domxref("XMLHttpRequest")}}, make sure you're
-    not setting {{domxref("XMLHttpRequest.withCredentials", "withCredentials")}} to
-    <code>true</code>.</li>
-  <li>If using <a href="/en-US/docs/Web/API/Server-sent_events">Server-sent events</a>,
-    make sure {{domxref("EventSource.withCredentials")}} is <code>false</code> (it's the
-    default value).</li>
-  <li>If using the <a href="/en-US/docs/Web/API/Fetch_API">Fetch API</a>, make sure
-    {{domxref("Request.credentials")}} is <code>"omit"</code>.</li>
-</ul>
+- If the request is being issued using {{domxref("XMLHttpRequest")}}, make sure you're
+  not setting {{domxref("XMLHttpRequest.withCredentials", "withCredentials")}} to
+  `true`.
+- If using [Server-sent events](/en-US/docs/Web/API/Server-sent_events),
+  make sure {{domxref("EventSource.withCredentials")}} is `false` (it's the
+  default value).
+- If using the [Fetch API](/en-US/docs/Web/API/Fetch_API), make sure
+  {{domxref("Request.credentials")}} is `"omit"`.
 
-<p>To eliminate this error by changing the server's configuration, adjust the server's
-  configuration to set the <code>Access-Control-Allow-Credentials</code> header's value to
-  <code>true</code>.</p>
+To eliminate this error by changing the server's configuration, adjust the server's
+configuration to set the `Access-Control-Allow-Credentials` header's value to
+`true`.
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
-  <li><a href="/en-US/docs/Web/HTTP/CORS/Errors">CORS errors</a></li>
-  <li>Glossary: {{Glossary("CORS")}}</li>
-  <li><a href="/en-US/docs/Web/HTTP/CORS">CORS introduction</a></li>
-</ul>
+- [CORS errors](/en-US/docs/Web/HTTP/CORS/Errors)
+- Glossary: {{Glossary("CORS")}}
+- [CORS introduction](/en-US/docs/Web/HTTP/CORS)
diff --git a/files/en-us/web/http/cors/errors/corsmissingallowheaderfrompreflight/index.md b/files/en-us/web/http/cors/errors/corsmissingallowheaderfrompreflight/index.md
index 6018e4939796ffd..35324bd84f68cbc 100644
--- a/files/en-us/web/http/cors/errors/corsmissingallowheaderfrompreflight/index.md
+++ b/files/en-us/web/http/cors/errors/corsmissingallowheaderfrompreflight/index.md
@@ -16,23 +16,23 @@ tags:
   - console
   - troubleshooting
 ---
-<div>{{HTTPSidebar}}</div>
+{{HTTPSidebar}}
 
-<h2 id="Reason">Reason</h2>
+## Reason
 
-<pre class="brush: html">Reason: missing token ‘xyz’ in CORS header ‘Access-Control-Allow-Headers’ from CORS preflight channel</pre>
+```html
+Reason: missing token ‘xyz’ in CORS header ‘Access-Control-Allow-Headers’ from CORS preflight channel
+```
 
-<h2 id="What_went_wrong">What went wrong?</h2>
+## What went wrong?
 
-<p>The <code>Access-Control-Allow-Headers</code> header is sent by the server to let the client know which headers it supports for {{Glossary("CORS")}} requests. The value of <code>Access-Control-Allow-Headers</code> should be a comma-delineated list of header names, such as "<code>X-Custom-Information</code>" or any of the standard but non-basic header names (which are always allowed).</p>
+The `Access-Control-Allow-Headers` header is sent by the server to let the client know which headers it supports for {{Glossary("CORS")}} requests. The value of `Access-Control-Allow-Headers` should be a comma-delineated list of header names, such as "`X-Custom-Information`" or any of the standard but non-basic header names (which are always allowed).
 
-<p>This error occurs when attempting to preflight a header that is not expressly allowed (that is, it's not included in the list specified by the <code>Access-Control-Allow-Headers</code> header sent by the server). To fix this, the server needs to be updated so that it allows the indicated header, or you need to avoid using that header.</p>
+This error occurs when attempting to preflight a header that is not expressly allowed (that is, it's not included in the list specified by the `Access-Control-Allow-Headers` header sent by the server). To fix this, the server needs to be updated so that it allows the indicated header, or you need to avoid using that header.
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
- <li><a href="/en-US/docs/Web/HTTP/CORS/Errors">CORS errors</a></li>
- <li>Glossary: {{Glossary("CORS")}}</li>
- <li><a href="/en-US/docs/Web/HTTP/CORS">CORS introduction</a></li>
- <li><a href="/en-US/docs/Web/HTTP/Headers">HTTP headers</a></li>
-</ul>
+- [CORS errors](/en-US/docs/Web/HTTP/CORS/Errors)
+- Glossary: {{Glossary("CORS")}}
+- [CORS introduction](/en-US/docs/Web/HTTP/CORS)
+- [HTTP headers](/en-US/docs/Web/HTTP/Headers)
diff --git a/files/en-us/web/http/cors/errors/corsmissingalloworigin/index.md b/files/en-us/web/http/cors/errors/corsmissingalloworigin/index.md
index 08cc9c4976e38ae..71c7911c33b401f 100644
--- a/files/en-us/web/http/cors/errors/corsmissingalloworigin/index.md
+++ b/files/en-us/web/http/cors/errors/corsmissingalloworigin/index.md
@@ -2,79 +2,75 @@
 title: 'Reason: CORS header ''Access-Control-Allow-Origin'' missing'
 slug: Web/HTTP/CORS/Errors/CORSMissingAllowOrigin
 tags:
-- CORS
-- CORSMissingAllowOrigin
-- Cross-Origin
-- Error
-- HTTP
-- HTTPS
-- Messages
-- Reasons
-- Security
-- console
-- troubleshooting
+  - CORS
+  - CORSMissingAllowOrigin
+  - Cross-Origin
+  - Error
+  - HTTP
+  - HTTPS
+  - Messages
+  - Reasons
+  - Security
+  - console
+  - troubleshooting
 ---
-<div>{{HTTPSidebar}}</div>
+{{HTTPSidebar}}
 
-<h2 id="Reason">Reason</h2>
+## Reason
 
-<pre
-  class="brush: html">Reason: CORS header 'Access-Control-Allow-Origin' missing</pre>
+```html
+Reason: CORS header 'Access-Control-Allow-Origin' missing
+```
 
-<h2 id="What_went_wrong">What went wrong?</h2>
+## What went wrong?
 
-<p>The response to the {{Glossary("CORS")}} request is missing the required
-  {{HTTPHeader("Access-Control-Allow-Origin")}} header, which is used to determine whether
-  or not the resource can be accessed by content operating within the current origin.</p>
+The response to the {{Glossary("CORS")}} request is missing the required
+{{HTTPHeader("Access-Control-Allow-Origin")}} header, which is used to determine whether
+or not the resource can be accessed by content operating within the current origin.
 
-<p>If the server is under your control, add the origin of the requesting site to the set
-  of domains permitted access by adding it to the <code>Access-Control-Allow-Origin</code>
-  header's value.</p>
+If the server is under your control, add the origin of the requesting site to the set
+of domains permitted access by adding it to the `Access-Control-Allow-Origin`
+header's value.
 
-<p>For example, to allow a site at https://amazing.site to access the resource using CORS,
-  the header should be:</p>
+For example, to allow a site at https\://amazing.site to access the resource using CORS,
+the header should be:
 
-<pre>Access-Control-Allow-Origin: https://amazing.site</pre>
+    Access-Control-Allow-Origin: https://amazing.site
 
-<p>You can also configure a site to allow any site to access it by using the
-  <code>*</code> wildcard. You should only use this for public APIs. Private APIs should
-  never use <code>*</code>, and should instead have a specific domain or domains set. In
-  addition, the wildcard only works for requests made with the
-  {{htmlattrxref("crossorigin")}} attribute set to <code>anonymous</code>, and it prevents
-  sending credentials like cookies in requests.</p>
+You can also configure a site to allow any site to access it by using the
+`*` wildcard. You should only use this for public APIs. Private APIs should
+never use `*`, and should instead have a specific domain or domains set. In
+addition, the wildcard only works for requests made with the
+{{htmlattrxref("crossorigin")}} attribute set to `anonymous`, and it prevents
+sending credentials like cookies in requests.
 
-<pre>Access-Control-Allow-Origin: *</pre>
+    Access-Control-Allow-Origin: *
 
-<div class="notecard warning">
-  <p><strong>Warning:</strong> Using the wildcard to allow all sites to access a private
-    API is a bad idea.</p>
-</div>
+> **Warning:** Using the wildcard to allow all sites to access a private
+> API is a bad idea.
 
-<p>To allow any site to make CORS requests <em>without</em> using the <code>*</code>
-  wildcard (for example, to enable credentials), your server must read the value of the
-  request's <code>Origin</code> header and use that value to set
-  <code>Access-Control-Allow-Origin</code>, and must also set a <code>Vary: Origin</code>
-  header to indicate that some headers are being set dynamically depending on the origin.
-</p>
+To allow any site to make CORS requests _without_ using the `*`
+wildcard (for example, to enable credentials), your server must read the value of the
+request's `Origin` header and use that value to set
+`Access-Control-Allow-Origin`, and must also set a `Vary: Origin`
+header to indicate that some headers are being set dynamically depending on the origin.
 
-<p>The exact directive for setting headers depends on your web server. In Apache, add a
-  line such as the following to the server's configuration (within the appropriate
-  <code>&lt;Directory&gt;</code>, <code>&lt;Location&gt;</code>,
-  <code>&lt;Files&gt;</code>, or <code>&lt;VirtualHost&gt;</code> section). The
-  configuration is typically found in a <code>.conf</code> file (<code>httpd.conf</code>
-  and <code>apache.conf</code> are common names for these), or in an
-  <code>.htaccess</code> file.</p>
+The exact directive for setting headers depends on your web server. In Apache, add a
+line such as the following to the server's configuration (within the appropriate
+`<Directory>`, `<Location>`,
+`<Files>`, or `<VirtualHost>` section). The
+configuration is typically found in a `.conf` file (`httpd.conf`
+and `apache.conf` are common names for these), or in an
+`.htaccess` file.
 
-<pre>Header set Access-Control-Allow-Origin '<em>origin-list</em>'</pre>
+    Header set Access-Control-Allow-Origin 'origin-list'
 
-<p>For Nginx, the command to set up this header is:</p>
+For Nginx, the command to set up this header is:
 
-<pre>add_header 'Access-Control-Allow-Origin' '<em>origin-list</em>';</pre>
+    add_header 'Access-Control-Allow-Origin' 'origin-list';
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
-  <li><a href="/en-US/docs/Web/HTTP/CORS/Errors">CORS errors</a></li>
-  <li>Glossary: {{Glossary("CORS")}}</li>
-  <li><a href="/en-US/docs/Web/HTTP/CORS">CORS introduction</a></li>
-</ul>
+- [CORS errors](/en-US/docs/Web/HTTP/CORS/Errors)
+- Glossary: {{Glossary("CORS")}}
+- [CORS introduction](/en-US/docs/Web/HTTP/CORS)
diff --git a/files/en-us/web/http/cors/errors/corsmultiplealloworiginnotallowed/index.md b/files/en-us/web/http/cors/errors/corsmultiplealloworiginnotallowed/index.md
index d67312ec27598c3..530d6b73e7b98ca 100644
--- a/files/en-us/web/http/cors/errors/corsmultiplealloworiginnotallowed/index.md
+++ b/files/en-us/web/http/cors/errors/corsmultiplealloworiginnotallowed/index.md
@@ -2,41 +2,40 @@
 title: 'Reason: Multiple CORS header ''Access-Control-Allow-Origin'' not allowed'
 slug: Web/HTTP/CORS/Errors/CORSMultipleAllowOriginNotAllowed
 tags:
-- CORS
-- CORSMultipleAllowOriginNotAllowed
-- Cross-Origin
-- Error
-- HTTP
-- HTTPS
-- Messages
-- Reasons
-- Security
-- console
-- troubleshooting
+  - CORS
+  - CORSMultipleAllowOriginNotAllowed
+  - Cross-Origin
+  - Error
+  - HTTP
+  - HTTPS
+  - Messages
+  - Reasons
+  - Security
+  - console
+  - troubleshooting
 ---
-<div>{{HTTPSidebar}}</div>
+{{HTTPSidebar}}
 
-<h2 id="Reason">Reason</h2>
+## Reason
 
-<pre
-  class="brush: html">Reason: Multiple CORS header ‘Access-Control-Allow-Origin’ not allowed</pre>
+```html
+Reason: Multiple CORS header ‘Access-Control-Allow-Origin’ not allowed
+```
 
-<h2 id="What_went_wrong">What went wrong?</h2>
+## What went wrong?
 
-<p>More than one {{HTTPHeader("Access-Control-Allow-Origin")}} header was sent by the
-  server. This isn't allowed.</p>
+More than one {{HTTPHeader("Access-Control-Allow-Origin")}} header was sent by the
+server. This isn't allowed.
 
-<p>If you have access to the server you can change your implementation to echo back an
-  origin in the <code>Access-Control-Allow-Origin</code> header. You cannot send back a
-  list of origins, because browsers only accept a value that is either a single origin or
-  null </p>
+If you have access to the server you can change your implementation to echo back an
+origin in the `Access-Control-Allow-Origin` header. You cannot send back a
+list of origins, because browsers only accept a value that is either a single origin or
+null
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
-  <li><a href="/en-US/docs/Web/HTTP/CORS/Errors">CORS errors</a></li>
-  <li>Glossary: {{Glossary("CORS")}}</li>
-  <li><a href="/en-US/docs/Web/HTTP/CORS">CORS introduction</a></li>
-  <li><a href="https://enable-cors.org/server.html">Enable CORS: I want to add CORS
-      support to my server</a></li>
-</ul>
+- [CORS errors](/en-US/docs/Web/HTTP/CORS/Errors)
+- Glossary: {{Glossary("CORS")}}
+- [CORS introduction](/en-US/docs/Web/HTTP/CORS)
+- [Enable CORS: I want to add CORS
+  support to my server](https://enable-cors.org/server.html)
diff --git a/files/en-us/web/http/cors/errors/corsnotsupportingcredentials/index.md b/files/en-us/web/http/cors/errors/corsnotsupportingcredentials/index.md
index 9d0c542c5219a44..835a1fed02fd3fa 100644
--- a/files/en-us/web/http/cors/errors/corsnotsupportingcredentials/index.md
+++ b/files/en-us/web/http/cors/errors/corsnotsupportingcredentials/index.md
@@ -16,30 +16,28 @@ tags:
   - console
   - troubleshooting
 ---
-<div>{{HTTPSidebar}}</div>
+{{HTTPSidebar}}
 
-<h2 id="Reason">Reason</h2>
+## Reason
 
-<pre class="brush: html">Reason: Credential is not supported if the CORS header ‘Access-Control-Allow-Origin’ is ‘*’</pre>
+```html
+Reason: Credential is not supported if the CORS header ‘Access-Control-Allow-Origin’ is ‘*’
+```
 
-<h2 id="What_went_wrong">What went wrong?</h2>
+## What went wrong?
 
-<p>The {{Glossary("CORS")}} request was attempted with the credentials flag set, but the server is configured using the wildcard (<code>"*"</code>) as the value of {{HTTPHeader("Access-Control-Allow-Origin")}}, which doesn't allow the use of credentials.</p>
+The {{Glossary("CORS")}} request was attempted with the credentials flag set, but the server is configured using the wildcard (`"*"`) as the value of {{HTTPHeader("Access-Control-Allow-Origin")}}, which doesn't allow the use of credentials.
 
-<p>To correct this problem on the client side, ensure that the credentials flag's value is <code>false</code> when issuing your CORS request.</p>
+To correct this problem on the client side, ensure that the credentials flag's value is `false` when issuing your CORS request.
 
-<ul>
- <li>If the request is being issued using {{domxref("XMLHttpRequest")}}, make sure you're not setting {{domxref("XMLHttpRequest.withCredentials", "withCredentials")}} to <code>true</code>.</li>
- <li>If using <a href="/en-US/docs/Web/API/Server-sent_events">Server-sent events</a>, make sure {{domxref("EventSource.withCredentials")}} is <code>false</code> (it's the default value).</li>
- <li>If using the <a href="/en-US/docs/Web/API/Fetch_API">Fetch API</a>, make sure {{domxref("Request.credentials")}} is <code>"omit"</code>.</li>
-</ul>
+- If the request is being issued using {{domxref("XMLHttpRequest")}}, make sure you're not setting {{domxref("XMLHttpRequest.withCredentials", "withCredentials")}} to `true`.
+- If using [Server-sent events](/en-US/docs/Web/API/Server-sent_events), make sure {{domxref("EventSource.withCredentials")}} is `false` (it's the default value).
+- If using the [Fetch API](/en-US/docs/Web/API/Fetch_API), make sure {{domxref("Request.credentials")}} is `"omit"`.
 
-<p>If, instead, you need to adjust the server's behavior, you'll need to change the value of <code>Access-Control-Allow-Origin</code> to grant access to the origin from which the client is loaded.</p>
+If, instead, you need to adjust the server's behavior, you'll need to change the value of `Access-Control-Allow-Origin` to grant access to the origin from which the client is loaded.
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
- <li><a href="/en-US/docs/Web/HTTP/CORS/Errors">CORS errors</a></li>
- <li>Glossary: {{Glossary("CORS")}}</li>
- <li><a href="/en-US/docs/Web/HTTP/CORS">CORS introduction</a></li>
-</ul>
+- [CORS errors](/en-US/docs/Web/HTTP/CORS/Errors)
+- Glossary: {{Glossary("CORS")}}
+- [CORS introduction](/en-US/docs/Web/HTTP/CORS)
diff --git a/files/en-us/web/http/cors/errors/corsoriginheadernotadded/index.md b/files/en-us/web/http/cors/errors/corsoriginheadernotadded/index.md
index 6b6033274a7e738..f86ad85b15f6ae9 100644
--- a/files/en-us/web/http/cors/errors/corsoriginheadernotadded/index.md
+++ b/files/en-us/web/http/cors/errors/corsoriginheadernotadded/index.md
@@ -2,37 +2,37 @@
 title: 'Reason: CORS header ‘Origin’ cannot be added'
 slug: Web/HTTP/CORS/Errors/CORSOriginHeaderNotAdded
 tags:
-- CORS
-- CORSOriginHeaderNotAdded
-- Cross-Origin
-- Error
-- HTTP
-- HTTPS
-- Messages
-- Reasons
-- Security
-- console
-- troubleshooting
+  - CORS
+  - CORSOriginHeaderNotAdded
+  - Cross-Origin
+  - Error
+  - HTTP
+  - HTTPS
+  - Messages
+  - Reasons
+  - Security
+  - console
+  - troubleshooting
 ---
-<div>{{HTTPSidebar}}</div>
+{{HTTPSidebar}}
 
-<h2 id="Reason">Reason</h2>
+## Reason
 
-<pre class="brush: html">Reason: CORS header ‘Origin’ cannot be added</pre>
+```html
+Reason: CORS header ‘Origin’ cannot be added
+```
 
-<h2 id="What_went_wrong">What went wrong?</h2>
+## What went wrong?
 
-<p>The {{Glossary("user agent")}} was unable to add the required {{HTTPHeader("Origin")}}
-  header to the {{Glossary("HTTP")}} request. All CORS requests must have an
-  <code>Origin</code> header.</p>
+The {{Glossary("user agent")}} was unable to add the required {{HTTPHeader("Origin")}}
+header to the {{Glossary("HTTP")}} request. All CORS requests must have an
+`Origin` header.
 
-<p>This can happen if the JavaScript code is running with enhanced privileges allowing it
-  access to multiple domains' content, for example.</p>
+This can happen if the JavaScript code is running with enhanced privileges allowing it
+access to multiple domains' content, for example.
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
-  <li><a href="/en-US/docs/Web/HTTP/CORS/Errors">CORS errors</a></li>
-  <li>Glossary: {{Glossary("CORS")}}</li>
-  <li><a href="/en-US/docs/Web/HTTP/CORS">CORS introduction</a></li>
-</ul>
+- [CORS errors](/en-US/docs/Web/HTTP/CORS/Errors)
+- Glossary: {{Glossary("CORS")}}
+- [CORS introduction](/en-US/docs/Web/HTTP/CORS)
diff --git a/files/en-us/web/http/cors/errors/corspreflightdidnotsucceed/index.md b/files/en-us/web/http/cors/errors/corspreflightdidnotsucceed/index.md
index a10afe6e7260969..aa24b1187925652 100644
--- a/files/en-us/web/http/cors/errors/corspreflightdidnotsucceed/index.md
+++ b/files/en-us/web/http/cors/errors/corspreflightdidnotsucceed/index.md
@@ -2,41 +2,39 @@
 title: 'Reason: CORS preflight channel did not succeed'
 slug: Web/HTTP/CORS/Errors/CORSPreflightDidNotSucceed
 tags:
-- CORS
-- CORSPreflightDidNotSucceed
-- Cross-Origin
-- Error
-- HTTP
-- HTTPS
-- Messages
-- Reasons
-- Security
-- console
-- troubleshooting
+  - CORS
+  - CORSPreflightDidNotSucceed
+  - Cross-Origin
+  - Error
+  - HTTP
+  - HTTPS
+  - Messages
+  - Reasons
+  - Security
+  - console
+  - troubleshooting
 ---
-<div>{{HTTPSidebar}}</div>
+{{HTTPSidebar}}
 
-<h2 id="Reason">Reason</h2>
+## Reason
 
-<pre class="brush: html">Reason: CORS preflight channel did not succeed</pre>
+```html
+Reason: CORS preflight channel did not succeed
+```
 
-<h2 id="What_went_wrong">What went wrong?</h2>
+## What went wrong?
 
-<p>The {{Glossary("CORS")}} request requires  preflight, preflighting could not be
-  performed. There are a couple of reasons why preflighting might fail:</p>
+The {{Glossary("CORS")}} request requires  preflight, preflighting could not be
+performed. There are a couple of reasons why preflighting might fail:
 
-<ul>
-  <li>A cross-site request has previously been performed that already did a preflight, and
-    doing the preflight again is not permitted. Make sure your code only preflights once
-    per connection.</li>
-  <li>The preflight request suffered any kind of networking error that might ordinarily
-    occur.</li>
-</ul>
+- A cross-site request has previously been performed that already did a preflight, and
+  doing the preflight again is not permitted. Make sure your code only preflights once
+  per connection.
+- The preflight request suffered any kind of networking error that might ordinarily
+  occur.
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
-  <li><a href="/en-US/docs/Web/HTTP/CORS/Errors">CORS errors</a></li>
-  <li>Glossary: {{Glossary("CORS")}}</li>
-  <li><a href="/en-US/docs/Web/HTTP/CORS">CORS introduction</a></li>
-</ul>
+- [CORS errors](/en-US/docs/Web/HTTP/CORS/Errors)
+- Glossary: {{Glossary("CORS")}}
+- [CORS introduction](/en-US/docs/Web/HTTP/CORS)
diff --git a/files/en-us/web/http/cors/errors/corsrequestnothttp/index.md b/files/en-us/web/http/cors/errors/corsrequestnothttp/index.md
index a532bb998e19895..3f608973724c1f4 100644
--- a/files/en-us/web/http/cors/errors/corsrequestnothttp/index.md
+++ b/files/en-us/web/http/cors/errors/corsrequestnothttp/index.md
@@ -2,55 +2,53 @@
 title: 'Reason: CORS request not HTTP'
 slug: Web/HTTP/CORS/Errors/CORSRequestNotHttp
 tags:
-- CORS
-- CORSRequestNotHttp
-- Cross-Origin
-- Error
-- HTTP
-- HTTPS
-- Messages
-- Reasons
-- Security
-- console
-- troubleshooting
+  - CORS
+  - CORSRequestNotHttp
+  - Cross-Origin
+  - Error
+  - HTTP
+  - HTTPS
+  - Messages
+  - Reasons
+  - Security
+  - console
+  - troubleshooting
 ---
-<div>{{HTTPSidebar}}</div>
+{{HTTPSidebar}}
 
-<h2 id="Reason">Reason</h2>
+## Reason
 
-<pre class="brush: html">Reason: CORS request not HTTP</pre>
+```html
+Reason: CORS request not HTTP
+```
 
-<h2 id="What_went_wrong">What went wrong?</h2>
+## What went wrong?
 
-<p>{{Glossary("CORS")}} requests may only use the HTTPS URL scheme, but the URL specified
-  by the request is of a different type. This often occurs if the URL specifies a local
-  file, using a <code>file:///</code> URL.</p>
+{{Glossary("CORS")}} requests may only use the HTTPS URL scheme, but the URL specified
+by the request is of a different type. This often occurs if the URL specifies a local
+file, using a `file:///` URL.
 
-<p>To fix this problem, make sure you use HTTPS URLs when issuing requests involving CORS,
-  such as {{domxref("XMLHttpRequest")}}, <a href="/en-US/docs/Web/API/Fetch_API">Fetch</a>
-  APIs, Web Fonts (<code>@font-face</code>), and <a
-    href="/en-US/docs/Web/API/WebGL_API/Tutorial/Using_textures_in_WebGL">WebGL
-    textures</a>, and XSL stylesheets.</p>
+To fix this problem, make sure you use HTTPS URLs when issuing requests involving CORS,
+such as {{domxref("XMLHttpRequest")}}, [Fetch](/en-US/docs/Web/API/Fetch_API)
+APIs, Web Fonts (`@font-face`), and [WebGL
+textures](/en-US/docs/Web/API/WebGL_API/Tutorial/Using_textures_in_WebGL), and XSL stylesheets.
 
-<h3 id="Local_File_Security_in_Firefox_68">Local File Security in Firefox 68</h3>
+### Local File Security in Firefox 68
 
-<p>When a user opened a page using a <code>file:///</code> URI in Firefox 67 and earlier,
-  the origin of the page was defined as the directory from which the page was opened.
-  Resources in the same directory and its subdirectories were treated as having the same
-  origin for purposes of the CORS same-origin rule.</p>
+When a user opened a page using a `file:///` URI in Firefox 67 and earlier,
+the origin of the page was defined as the directory from which the page was opened.
+Resources in the same directory and its subdirectories were treated as having the same
+origin for purposes of the CORS same-origin rule.
 
-<p>In response to <a
-    href="https://www.mozilla.org/en-US/security/advisories/mfsa2019-21/#CVE-2019-11730">CVE-2019-11730</a>,
-  Firefox 68 and later define the origin of a page opened using a <code>file:///</code>
-  URI as unique. Therefore, other resources in the same directory or its subdirectories no
-  longer satisfy the CORS same-origin rule. This new behavior is enabled by default using
-  the <code>privacy.file_unique_origin</code> preference.</p>
+In response to [CVE-2019-11730](https://www.mozilla.org/en-US/security/advisories/mfsa2019-21/#CVE-2019-11730),
+Firefox 68 and later define the origin of a page opened using a `file:///`
+URI as unique. Therefore, other resources in the same directory or its subdirectories no
+longer satisfy the CORS same-origin rule. This new behavior is enabled by default using
+the `privacy.file_unique_origin` preference.
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
-  <li><a href="/en-US/docs/Web/HTTP/CORS/Errors">CORS errors</a></li>
-  <li>Glossary: {{Glossary("CORS")}}</li>
-  <li><a href="/en-US/docs/Web/HTTP/CORS">CORS introduction</a></li>
-  <li><a href="/en-US/docs/Learn/Common_questions/What_is_a_URL">What is a URL?</a></li>
-</ul>
+- [CORS errors](/en-US/docs/Web/HTTP/CORS/Errors)
+- Glossary: {{Glossary("CORS")}}
+- [CORS introduction](/en-US/docs/Web/HTTP/CORS)
+- [What is a URL?](/en-US/docs/Learn/Common_questions/What_is_a_URL)
diff --git a/files/en-us/web/http/cors/errors/index.md b/files/en-us/web/http/cors/errors/index.md
index 2ee1ce61f32e089..b5cbf7342a21eba 100644
--- a/files/en-us/web/http/cors/errors/index.md
+++ b/files/en-us/web/http/cors/errors/index.md
@@ -12,62 +12,54 @@ tags:
   - console
   - troubleshooting
 ---
-<div>{{HTTPSidebar}}</div>
+{{HTTPSidebar}}
 
-<p><a href="/en-US/docs/Web/HTTP/CORS">Cross-Origin Resource Sharing</a> ({{Glossary("CORS")}}) is a standard that allows a server to relax the <a href="/en-US/docs/Web/Security/Same-origin_policy">same-origin policy</a>. This is used to explicitly allow some cross-origin requests while rejecting others. For example, if a site offers an embeddable service, it may be necessary to relax certain restrictions. Setting up such a CORS configuration isn't necessarily easy and may present some challenges. In these pages, we'll look into some common CORS error messages and how to resolve them.</p>
+[Cross-Origin Resource Sharing](/en-US/docs/Web/HTTP/CORS) ({{Glossary("CORS")}}) is a standard that allows a server to relax the [same-origin policy](/en-US/docs/Web/Security/Same-origin_policy). This is used to explicitly allow some cross-origin requests while rejecting others. For example, if a site offers an embeddable service, it may be necessary to relax certain restrictions. Setting up such a CORS configuration isn't necessarily easy and may present some challenges. In these pages, we'll look into some common CORS error messages and how to resolve them.
 
-<p>If the CORS configuration isn't setup correctly, the browser console will present an error like <code>"Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at $somesite"</code> indicating that the request was blocked due to violating the CORS security rules. This might not necessarily be a set-up mistake, though. It's possible that the request is in fact intentionally being disallowed by the user's web application and remote external service. However, If the endpoint is meant to be available, some debugging is needed to succeed.</p>
+If the CORS configuration isn't setup correctly, the browser console will present an error like `"Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at $somesite"` indicating that the request was blocked due to violating the CORS security rules. This might not necessarily be a set-up mistake, though. It's possible that the request is in fact intentionally being disallowed by the user's web application and remote external service. However, If the endpoint is meant to be available, some debugging is needed to succeed.
 
-<h2 id="Identifying_the_issue">Identifying the issue</h2>
+## Identifying the issue
 
-<p>To understand the underlying issue with the CORS configuration, you need to find out which request is at fault and why. These steps may help you do so:</p>
+To understand the underlying issue with the CORS configuration, you need to find out which request is at fault and why. These steps may help you do so:
 
-<ol>
- <li>Navigate to the web site or web app in question and open the <a href="/en-US/docs/Tools">Developer Tools</a>.</li>
- <li>Now try to reproduce the failing transaction and check the <a href="/en-US/docs/Tools/Web_Console">console</a> if you are seeing a CORS violation error message. It will probably look like this:</li>
-</ol>
+1.  Navigate to the web site or web app in question and open the [Developer Tools](/en-US/docs/Tools).
+2.  Now try to reproduce the failing transaction and check the [console](/en-US/docs/Tools/Web_Console) if you are seeing a CORS violation error message. It will probably look like this:
 
-<p><img alt="Firefox console showing CORS error" src="cors-error2.png"></p>
+![Firefox console showing CORS error](cors-error2.png)
 
-<p>The text of the error message will be something similar to the following:</p>
+The text of the error message will be something similar to the following:
 
-<pre>Cross-Origin Request Blocked: The Same Origin Policy disallows
-reading the remote resource at <em>https://some-url-here</em>. (<em>Reason:
-additional information here</em>).</pre>
+    Cross-Origin Request Blocked: The Same Origin Policy disallows
+    reading the remote resource at https://some-url-here. (Reason:
+    additional information here).
 
-<div class="notecard note">
-  <p><strong>Note:</strong> For security reasons, specifics about what went wrong with a CORS request <em>are not available to JavaScript code</em>. All the code knows is that an error occurred. The only way to determine what specifically went wrong is to look at the browser's console for details.</p>
-</div>
+> **Note:** For security reasons, specifics about what went wrong with a CORS request _are not available to JavaScript code_. All the code knows is that an error occurred. The only way to determine what specifically went wrong is to look at the browser's console for details.
 
-<h2 id="CORS_error_messages">CORS error messages</h2>
+## CORS error messages
 
-<p>Firefox's console displays messages in its console when requests fail due to CORS. Part of the error text is a "reason" message that provides added insight into what went wrong.  The reason messages are listed below; click the message to open an article explaining the error in more detail and offering possible solutions.</p>
+Firefox's console displays messages in its console when requests fail due to CORS. Part of the error text is a "reason" message that provides added insight into what went wrong.  The reason messages are listed below; click the message to open an article explaining the error in more detail and offering possible solutions.
 
-<ul>
- <li><a href="/en-US/docs/Web/HTTP/CORS/Errors/CORSDisabled">Reason: CORS disabled</a></li>
- <li><a href="/en-US/docs/Web/HTTP/CORS/Errors/CORSDidNotSucceed">Reason: CORS request did not succeed</a></li>
- <li><a href="/en-US/docs/Web/HTTP/CORS/Errors/CORSOriginHeaderNotAdded">Reason: CORS header ‘Origin’ cannot be added</a></li>
- <li><a href="/en-US/docs/Web/HTTP/CORS/Errors/CORSExternalRedirectNotAllowed">Reason: CORS request external redirect not allowed</a></li>
- <li><a href="/en-US/docs/Web/HTTP/CORS/Errors/CORSRequestNotHttp">Reason: CORS request not http</a></li>
- <li><a href="/en-US/docs/Web/HTTP/CORS/Errors/CORSMissingAllowOrigin">Reason: CORS header ‘Access-Control-Allow-Origin’ missing</a></li>
- <li><a href="/en-US/docs/Web/HTTP/CORS/Errors/CORSAllowOriginNotMatchingOrigin">Reason: CORS header ‘Access-Control-Allow-Origin’ does not match ‘xyz’</a></li>
- <li><a href="/en-US/docs/Web/HTTP/CORS/Errors/CORSNotSupportingCredentials">Reason: Credential is not supported if the CORS header ‘Access-Control-Allow-Origin’ is ‘*’</a></li>
- <li><a href="/en-US/docs/Web/HTTP/CORS/Errors/CORSMethodNotFound">Reason: Did not find method in CORS header ‘Access-Control-Allow-Methods’</a></li>
- <li><a href="/en-US/docs/Web/HTTP/CORS/Errors/CORSMIssingAllowCredentials">Reason: expected ‘true’ in CORS header ‘Access-Control-Allow-Credentials’</a></li>
- <li><a href="/en-US/docs/Web/HTTP/CORS/Errors/CORSPreflightDidNotSucceed">Reason: CORS preflight channel did not succeed</a></li>
- <li><a href="/en-US/docs/Web/HTTP/CORS/Errors/CORSInvalidAllowMethod">Reason: invalid token ‘xyz’ in CORS header ‘Access-Control-Allow-Methods’</a></li>
- <li><a href="/en-US/docs/Web/HTTP/CORS/Errors/CORSInvalidAllowHeader">Reason: invalid token ‘xyz’ in CORS header ‘Access-Control-Allow-Headers’</a></li>
- <li><a href="/en-US/docs/Web/HTTP/CORS/Errors/CORSMissingAllowHeaderFromPreflight">Reason: missing token ‘xyz’ in CORS header ‘Access-Control-Allow-Headers’ from CORS preflight channel</a></li>
- <li><a href="/en-US/docs/Web/HTTP/CORS/Errors/CORSMultipleAllowOriginNotAllowed">Reason: Multiple CORS header ‘Access-Control-Allow-Origin’ not allowed</a></li>
-</ul>
+- [Reason: CORS disabled](/en-US/docs/Web/HTTP/CORS/Errors/CORSDisabled)
+- [Reason: CORS request did not succeed](/en-US/docs/Web/HTTP/CORS/Errors/CORSDidNotSucceed)
+- [Reason: CORS header ‘Origin’ cannot be added](/en-US/docs/Web/HTTP/CORS/Errors/CORSOriginHeaderNotAdded)
+- [Reason: CORS request external redirect not allowed](/en-US/docs/Web/HTTP/CORS/Errors/CORSExternalRedirectNotAllowed)
+- [Reason: CORS request not http](/en-US/docs/Web/HTTP/CORS/Errors/CORSRequestNotHttp)
+- [Reason: CORS header ‘Access-Control-Allow-Origin’ missing](/en-US/docs/Web/HTTP/CORS/Errors/CORSMissingAllowOrigin)
+- [Reason: CORS header ‘Access-Control-Allow-Origin’ does not match ‘xyz’](/en-US/docs/Web/HTTP/CORS/Errors/CORSAllowOriginNotMatchingOrigin)
+- [Reason: Credential is not supported if the CORS header ‘Access-Control-Allow-Origin’ is ‘\*’](/en-US/docs/Web/HTTP/CORS/Errors/CORSNotSupportingCredentials)
+- [Reason: Did not find method in CORS header ‘Access-Control-Allow-Methods’](/en-US/docs/Web/HTTP/CORS/Errors/CORSMethodNotFound)
+- [Reason: expected ‘true’ in CORS header ‘Access-Control-Allow-Credentials’](/en-US/docs/Web/HTTP/CORS/Errors/CORSMIssingAllowCredentials)
+- [Reason: CORS preflight channel did not succeed](/en-US/docs/Web/HTTP/CORS/Errors/CORSPreflightDidNotSucceed)
+- [Reason: invalid token ‘xyz’ in CORS header ‘Access-Control-Allow-Methods’](/en-US/docs/Web/HTTP/CORS/Errors/CORSInvalidAllowMethod)
+- [Reason: invalid token ‘xyz’ in CORS header ‘Access-Control-Allow-Headers’](/en-US/docs/Web/HTTP/CORS/Errors/CORSInvalidAllowHeader)
+- [Reason: missing token ‘xyz’ in CORS header ‘Access-Control-Allow-Headers’ from CORS preflight channel](/en-US/docs/Web/HTTP/CORS/Errors/CORSMissingAllowHeaderFromPreflight)
+- [Reason: Multiple CORS header ‘Access-Control-Allow-Origin’ not allowed](/en-US/docs/Web/HTTP/CORS/Errors/CORSMultipleAllowOriginNotAllowed)
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
- <li>Glossary: {{Glossary("CORS")}}</li>
- <li><a href="/en-US/docs/Web/HTTP/CORS">CORS introduction</a></li>
- <li><a href="/en-US/docs/Web/HTTP/CORS">Server-side CORS settings</a></li>
- <li><a href="/en-US/docs/Web/HTML/CORS_enabled_image">CORS enabled image</a></li>
- <li><a href="/en-US/docs/Web/HTML/Attributes/crossorigin">CORS settings attributes</a></li>
- <li><a href="https://www.test-cors.org">https://www.test-cors.org</a> – page to test CORS requests</li>
-</ul>
+- Glossary: {{Glossary("CORS")}}
+- [CORS introduction](/en-US/docs/Web/HTTP/CORS)
+- [Server-side CORS settings](/en-US/docs/Web/HTTP/CORS)
+- [CORS enabled image](/en-US/docs/Web/HTML/CORS_enabled_image)
+- [CORS settings attributes](/en-US/docs/Web/HTML/Attributes/crossorigin)
+- <https://www.test-cors.org> – page to test CORS requests
diff --git a/files/en-us/web/http/cors/index.md b/files/en-us/web/http/cors/index.md
index cee68d75b751a90..1edccc762f88e34 100644
--- a/files/en-us/web/http/cors/index.md
+++ b/files/en-us/web/http/cors/index.md
@@ -14,285 +14,262 @@ tags:
   - XMLHttpRequest
   - l10n:priority
 ---
-<div>{{HTTPSidebar}}</div>
+{{HTTPSidebar}}
 
-<p><strong>Cross-Origin Resource Sharing</strong> ({{Glossary("CORS")}}) is an {{Glossary("HTTP")}}-header based mechanism that allows a server to indicate any {{glossary("origin")}}s (domain, scheme, or port) other than its own from which a browser should permit loading of resources. CORS also relies on a mechanism by which browsers make a "preflight" request to the server hosting the cross-origin resource, in order to check that the server will permit the actual request. In that preflight, the browser sends headers that indicate the HTTP method and headers that will be used in the actual request.</p>
+**Cross-Origin Resource Sharing** ({{Glossary("CORS")}}) is an {{Glossary("HTTP")}}-header based mechanism that allows a server to indicate any {{glossary("origin")}}s (domain, scheme, or port) other than its own from which a browser should permit loading of resources. CORS also relies on a mechanism by which browsers make a "preflight" request to the server hosting the cross-origin resource, in order to check that the server will permit the actual request. In that preflight, the browser sends headers that indicate the HTTP method and headers that will be used in the actual request.
 
-<p>An example of a cross-origin request: the front-end JavaScript code served from <code>https://domain-a.com</code> uses {{domxref("XMLHttpRequest")}} to make a request for <code>https://domain-b.com/data.json</code>.</p>
+An example of a cross-origin request: the front-end JavaScript code served from `https://domain-a.com` uses {{domxref("XMLHttpRequest")}} to make a request for `https://domain-b.com/data.json`.
 
-<p>For security reasons, browsers restrict cross-origin HTTP requests initiated from scripts. For example, <code>XMLHttpRequest</code> and the <a href="/en-US/docs/Web/API/Fetch_API">Fetch API</a> follow the <a href="/en-US/docs/Web/Security/Same-origin_policy">same-origin policy</a>. This means that a web application using those APIs can only request resources from the same origin the application was loaded from unless the response from other origins includes the right CORS headers.</p>
+For security reasons, browsers restrict cross-origin HTTP requests initiated from scripts. For example, `XMLHttpRequest` and the [Fetch API](/en-US/docs/Web/API/Fetch_API) follow the [same-origin policy](/en-US/docs/Web/Security/Same-origin_policy). This means that a web application using those APIs can only request resources from the same origin the application was loaded from unless the response from other origins includes the right CORS headers.
 
-<p><img alt="" src="cors_principle.png"></p>
+![](cors_principle.png)
 
-<p>The CORS mechanism supports secure cross-origin requests and data transfers between browsers and servers. Modern browsers use CORS in APIs such as <code>XMLHttpRequest</code> or <a href="/en-US/docs/Web/API/Fetch_API">Fetch</a> to mitigate the risks of cross-origin HTTP requests.</p>
+The CORS mechanism supports secure cross-origin requests and data transfers between browsers and servers. Modern browsers use CORS in APIs such as `XMLHttpRequest` or [Fetch](/en-US/docs/Web/API/Fetch_API) to mitigate the risks of cross-origin HTTP requests.
 
-<h2 id="Who_should_read_this_article">Who should read this article?</h2>
+## Who should read this article?
 
-<p>Everyone, really.</p>
+Everyone, really.
 
-<p>More specifically, this article is for <strong>web administrators</strong>, <strong>server developers</strong>, and <strong>front-end developers</strong>. Modern browsers handle the client side of cross-origin sharing, including headers and policy enforcement. But the CORS standard means servers have to handle new request and response headers.</p>
+More specifically, this article is for **web administrators**, **server developers**, and **front-end developers**. Modern browsers handle the client side of cross-origin sharing, including headers and policy enforcement. But the CORS standard means servers have to handle new request and response headers.
 
-<h2 id="What_requests_use_CORS">What requests use CORS?</h2>
+## What requests use CORS?
 
-<p>This <a href="https://fetch.spec.whatwg.org/#http-cors-protocol">cross-origin sharing standard</a> can enable cross-site HTTP requests for:</p>
+This [cross-origin sharing standard](https://fetch.spec.whatwg.org/#http-cors-protocol) can enable cross-site HTTP requests for:
 
-<ul>
- <li>Invocations of the {{domxref("XMLHttpRequest")}} or <a href="/en-US/docs/Web/API/Fetch_API">Fetch APIs</a>, as discussed above.</li>
- <li>Web Fonts (for cross-domain font usage in <code>@font-face</code> within CSS), <a href="https://www.w3.org/TR/css-fonts-3/#font-fetching-requirements">so that servers can deploy TrueType fonts that can only be cross-site loaded and used by web sites that are permitted to do so.</a></li>
- <li><a href="/en-US/docs/Web/API/WebGL_API/Tutorial/Using_textures_in_WebGL">WebGL textures</a>.</li>
- <li>Images/video frames drawn to a canvas using {{domxref("CanvasRenderingContext2D.drawImage()", "drawImage()")}}.</li>
- <li><a href="/en-US/docs/Web/CSS/CSS_Shapes/Shapes_From_Images">CSS Shapes from images.</a></li>
-</ul>
+- Invocations of the {{domxref("XMLHttpRequest")}} or [Fetch APIs](/en-US/docs/Web/API/Fetch_API), as discussed above.
+- Web Fonts (for cross-domain font usage in `@font-face` within CSS), [so that servers can deploy TrueType fonts that can only be cross-site loaded and used by web sites that are permitted to do so.](https://www.w3.org/TR/css-fonts-3/#font-fetching-requirements)
+- [WebGL textures](/en-US/docs/Web/API/WebGL_API/Tutorial/Using_textures_in_WebGL).
+- Images/video frames drawn to a canvas using {{domxref("CanvasRenderingContext2D.drawImage()", "drawImage()")}}.
+- [CSS Shapes from images.](/en-US/docs/Web/CSS/CSS_Shapes/Shapes_From_Images)
 
-<p>This article is a general discussion of Cross-Origin Resource Sharing and includes a discussion of the necessary HTTP headers.</p>
+This article is a general discussion of Cross-Origin Resource Sharing and includes a discussion of the necessary HTTP headers.
 
-<h2 id="Functional_overview">Functional overview</h2>
+## Functional overview
 
-<p>The Cross-Origin Resource Sharing standard works by adding new <a href="/en-US/docs/Web/HTTP/Headers">HTTP headers</a> that let servers describe which origins are permitted to read that information from a web browser. Additionally, for HTTP request methods that can cause side-effects on server data (in particular, HTTP methods other than {{HTTPMethod("GET")}}, or {{HTTPMethod("POST")}} with certain <a href="/en-US/docs/Web/HTTP/Basics_of_HTTP/MIME_types">MIME types</a>), the specification mandates that browsers "preflight" the request, soliciting supported methods from the server with the HTTP {{HTTPMethod("OPTIONS")}} request method, and then, upon "approval" from the server, sending the actual request. Servers can also inform clients whether "credentials" (such as <a href="/en-US/docs/Web/HTTP/Cookies">Cookies</a> and <a href="/en-US/docs/Web/HTTP/Authentication">HTTP Authentication</a>) should be sent with requests.</p>
+The Cross-Origin Resource Sharing standard works by adding new [HTTP headers](/en-US/docs/Web/HTTP/Headers) that let servers describe which origins are permitted to read that information from a web browser. Additionally, for HTTP request methods that can cause side-effects on server data (in particular, HTTP methods other than {{HTTPMethod("GET")}}, or {{HTTPMethod("POST")}} with certain [MIME types](/en-US/docs/Web/HTTP/Basics_of_HTTP/MIME_types)), the specification mandates that browsers "preflight" the request, soliciting supported methods from the server with the HTTP {{HTTPMethod("OPTIONS")}} request method, and then, upon "approval" from the server, sending the actual request. Servers can also inform clients whether "credentials" (such as [Cookies](/en-US/docs/Web/HTTP/Cookies) and [HTTP Authentication](/en-US/docs/Web/HTTP/Authentication)) should be sent with requests.
 
-<p>CORS failures result in errors, but for security reasons, specifics about the error <em>are not available to JavaScript</em>. All the code knows is that an error occurred. The only way to determine what specifically went wrong is to look at the browser's console for details.</p>
+CORS failures result in errors, but for security reasons, specifics about the error _are not available to JavaScript_. All the code knows is that an error occurred. The only way to determine what specifically went wrong is to look at the browser's console for details.
 
-<p>Subsequent sections discuss scenarios, as well as provide a breakdown of the HTTP headers used.</p>
+Subsequent sections discuss scenarios, as well as provide a breakdown of the HTTP headers used.
 
-<h2 id="Examples_of_access_control_scenarios">Examples of access control scenarios</h2>
+## Examples of access control scenarios
 
-<p>We present three scenarios that demonstrate how Cross-Origin Resource Sharing works. All these examples use {{domxref("XMLHttpRequest")}}, which can make cross-site requests in any supporting browser.</p>
+We present three scenarios that demonstrate how Cross-Origin Resource Sharing works. All these examples use {{domxref("XMLHttpRequest")}}, which can make cross-site requests in any supporting browser.
 
-<h3 id="Simple_requests">Simple requests</h3>
+### Simple requests
 
-<p>Some requests don't trigger a {{Glossary("Preflight_request","CORS preflight")}}. Those are called <em>simple requests</em>, though the {{SpecName('Fetch')}} spec (which defines CORS) doesn't use that term. A <em>simple request</em> is one that <strong>meets all the following conditions</strong>:</p>
+Some requests don't trigger a {{Glossary("Preflight_request","CORS preflight")}}. Those are called _simple requests_, though the {{SpecName('Fetch')}} spec (which defines CORS) doesn't use that term. A _simple request_ is one that **meets all the following conditions**:
 
-<ul>
- <li>One of the allowed methods:
-  <ul>
-   <li>{{HTTPMethod("GET")}}</li>
-   <li>{{HTTPMethod("HEAD")}}</li>
-   <li>{{HTTPMethod("POST")}}</li>
-  </ul>
- </li>
- <li>Apart from the headers automatically set by the user agent (for example, {{HTTPHeader("Connection")}}, {{HTTPHeader("User-Agent")}}, or <a href="https://fetch.spec.whatwg.org/#forbidden-header-name">the other headers defined in the Fetch spec as a <em>forbidden header name</em></a>), the only headers which are allowed to be manually set are <a href="https://fetch.spec.whatwg.org/#cors-safelisted-request-header">those which the Fetch spec defines as a </em>CORS-safelisted request-header</em></a>, which are:
-  <ul>
-   <li>{{HTTPHeader("Accept")}}</li>
-   <li>{{HTTPHeader("Accept-Language")}}</li>
-   <li>{{HTTPHeader("Content-Language")}}</li>
-   <li>{{HTTPHeader("Content-Type")}} (but note the additional requirements below)</li>
-  </ul>
- </li>
- <li>The only allowed values for the {{HTTPHeader("Content-Type")}} header are:
-  <ul>
-   <li><code>application/x-www-form-urlencoded</code></li>
-   <li><code>multipart/form-data</code></li>
-   <li><code>text/plain</code></li>
-  </ul>
- </li>
- <li>If the request is made using an {{domxref("XMLHttpRequest")}} object, no event listeners are registered on the object returned by the {{domxref("XMLHttpRequest.upload")}} property used in the request; that is, given an {{domxref("XMLHttpRequest")}} instance <code>xhr</code>, no code has called <code>xhr.upload.addEventListener()</code> to add an event listener to monitor the upload.</li>
- <li>No {{domxref("ReadableStream")}} object is used in the request.</li>
-</ul>
+- One of the allowed methods:
 
-<div class="notecard note">
-  <p><strong>Note:</strong> WebKit Nightly and Safari Technology Preview place additional restrictions on the values allowed in the {{HTTPHeader("Accept")}}, {{HTTPHeader("Accept-Language")}}, and {{HTTPHeader("Content-Language")}} headers. If any of those headers have "nonstandard" values, WebKit/Safari does not consider the request to be a "simple request". What values WebKit/Safari consider "nonstandard" is not documented, except in the following WebKit bugs:</p>
-  <ul>
-    <li><a href="https://bugs.webkit.org/show_bug.cgi?id=165178" rel="nofollow noreferrer">Require preflight for non-standard CORS-safelisted request headers Accept, Accept-Language, and Content-Language</a></li>
-    <li><a href="https://bugs.webkit.org/show_bug.cgi?id=165566" rel="nofollow noreferrer">Allow commas in Accept, Accept-Language, and Content-Language request headers for simple CORS</a></li>
-    <li><a href="https://bugs.webkit.org/show_bug.cgi?id=166363" rel="nofollow noreferrer">Switch to a blacklist model for restricted Accept headers in simple CORS requests</a></li>
-  </ul>
-  <p>No other browsers implement these extra restrictions, because they're not part of the spec.</p>
-</div>
+  - {{HTTPMethod("GET")}}
+  - {{HTTPMethod("HEAD")}}
+  - {{HTTPMethod("POST")}}
 
-<p>For example, suppose web content at <code>https://foo.example</code> wishes to invoke content on domain <code>https://bar.other</code>. Code of this sort might be used in JavaScript deployed on <code>foo.example</code>:</p>
+- Apart from the headers automatically set by the user agent (for example, {{HTTPHeader("Connection")}}, {{HTTPHeader("User-Agent")}}, or [the other headers defined in the Fetch spec as a _forbidden header name_](https://fetch.spec.whatwg.org/#forbidden-header-name)), the only headers which are allowed to be manually set are [those which the Fetch spec defines as a CORS-safelisted request-header](https://fetch.spec.whatwg.org/#cors-safelisted-request-header), which are:
 
-<pre class="brush: js">const xhr = new XMLHttpRequest();
+  - {{HTTPHeader("Accept")}}
+  - {{HTTPHeader("Accept-Language")}}
+  - {{HTTPHeader("Content-Language")}}
+  - {{HTTPHeader("Content-Type")}} (but note the additional requirements below)
+
+- The only allowed values for the {{HTTPHeader("Content-Type")}} header are:
+
+  - `application/x-www-form-urlencoded`
+  - `multipart/form-data`
+  - `text/plain`
+
+- If the request is made using an {{domxref("XMLHttpRequest")}} object, no event listeners are registered on the object returned by the {{domxref("XMLHttpRequest.upload")}} property used in the request; that is, given an {{domxref("XMLHttpRequest")}} instance `xhr`, no code has called `xhr.upload.addEventListener()` to add an event listener to monitor the upload.
+- No {{domxref("ReadableStream")}} object is used in the request.
+
+> **Note:** WebKit Nightly and Safari Technology Preview place additional restrictions on the values allowed in the {{HTTPHeader("Accept")}}, {{HTTPHeader("Accept-Language")}}, and {{HTTPHeader("Content-Language")}} headers. If any of those headers have "nonstandard" values, WebKit/Safari does not consider the request to be a "simple request". What values WebKit/Safari consider "nonstandard" is not documented, except in the following WebKit bugs:
+>
+> - [Require preflight for non-standard CORS-safelisted request headers Accept, Accept-Language, and Content-Language](https://bugs.webkit.org/show_bug.cgi?id=165178)
+> - [Allow commas in Accept, Accept-Language, and Content-Language request headers for simple CORS](https://bugs.webkit.org/show_bug.cgi?id=165566)
+> - [Switch to a blacklist model for restricted Accept headers in simple CORS requests](https://bugs.webkit.org/show_bug.cgi?id=166363)
+>
+> No other browsers implement these extra restrictions, because they're not part of the spec.
+
+For example, suppose web content at `https://foo.example` wishes to invoke content on domain `https://bar.other`. Code of this sort might be used in JavaScript deployed on `foo.example`:
+
+```js
+const xhr = new XMLHttpRequest();
 const url = 'https://bar.other/resources/public-data/';
 
 xhr.open('GET', url);
 xhr.onreadystatechange = someHandler;
 xhr.send();
-</pre>
+```
 
-<p>This performs a simple exchange between the client and the server, using CORS headers to handle the privileges:</p>
+This performs a simple exchange between the client and the server, using CORS headers to handle the privileges:
 
-<p><img alt="" src="simple-req-updated.png"></p>
+![](simple-req-updated.png)
 
-<p>Let's look at what the browser will send to the server in this case, and let's see how the server responds:</p>
+Let's look at what the browser will send to the server in this case, and let's see how the server responds:
 
-<pre>GET /resources/public-data/ HTTP/1.1
-Host: bar.other
-User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:71.0) Gecko/20100101 Firefox/71.0
-Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
-Accept-Language: en-us,en;q=0.5
-Accept-Encoding: gzip,deflate
-Connection: keep-alive
-<strong>Origin: https://foo.example</strong>
-</pre>
+    GET /resources/public-data/ HTTP/1.1
+    Host: bar.other
+    User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:71.0) Gecko/20100101 Firefox/71.0
+    Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
+    Accept-Language: en-us,en;q=0.5
+    Accept-Encoding: gzip,deflate
+    Connection: keep-alive
+    Origin: https://foo.example
 
-<p>The request header of note is {{HTTPHeader("Origin")}}, which shows that the invocation is coming from <code>https://foo.example</code>.</p>
+The request header of note is {{HTTPHeader("Origin")}}, which shows that the invocation is coming from `https://foo.example`.
 
-<pre>HTTP/1.1 200 OK
-Date: Mon, 01 Dec 2008 00:23:53 GMT
-Server: Apache/2
-<strong>Access-Control-Allow-Origin: *</strong>
-Keep-Alive: timeout=2, max=100
-Connection: Keep-Alive
-Transfer-Encoding: chunked
-Content-Type: application/xml
+    HTTP/1.1 200 OK
+    Date: Mon, 01 Dec 2008 00:23:53 GMT
+    Server: Apache/2
+    Access-Control-Allow-Origin: *
+    Keep-Alive: timeout=2, max=100
+    Connection: Keep-Alive
+    Transfer-Encoding: chunked
+    Content-Type: application/xml
 
-[…XML Data…]</pre>
+    […XML Data…]
 
-<p>In response, the server sends back an {{HTTPHeader("Access-Control-Allow-Origin")}} header with <code>Access-Control-Allow-Origin: *</code>, which means that the resource can be accessed by <strong>any</strong> origin.</p>
+In response, the server sends back an {{HTTPHeader("Access-Control-Allow-Origin")}} header with `Access-Control-Allow-Origin: *`, which means that the resource can be accessed by **any** origin.
 
-<pre class="brush: html">Access-Control-Allow-Origin: *</pre>
+```html
+Access-Control-Allow-Origin: *
+```
 
-<p>This pattern of the {{HTTPHeader("Origin")}} and {{HTTPHeader("Access-Control-Allow-Origin")}} headers is the simplest use of the access control protocol. If the resource owners at <code>https://bar.other</code> wished to restrict access to the resource to requests <em>only</em> from <code>https://foo.example</code>, (i.e no domain other than <code>https://foo.example</code> can access the resource in a cross-site manner) they would send:</p>
+This pattern of the {{HTTPHeader("Origin")}} and {{HTTPHeader("Access-Control-Allow-Origin")}} headers is the simplest use of the access control protocol. If the resource owners at `https://bar.other` wished to restrict access to the resource to requests _only_ from `https://foo.example`, (i.e no domain other than `https://foo.example` can access the resource in a cross-site manner) they would send:
 
-<pre><code>Access-Control-Allow-Origin: https://foo.example</code>
-</pre>
+    Access-Control-Allow-Origin: https://foo.example
 
-<div class="notecard note">
-  <p><strong>Note:</strong> When responding to a <a href="#requests_with_credentials">credentialed requests</a> request, the server <strong>must</strong> specify an origin in the value of the <code>Access-Control-Allow-Origin</code> header, instead of specifying the "<code>*</code>" wildcard.</p>
-</div>
+> **Note:** When responding to a [credentialed requests](#requests_with_credentials) request, the server **must** specify an origin in the value of the `Access-Control-Allow-Origin` header, instead of specifying the "`*`" wildcard.
 
-<h3 id="Preflighted_requests">Preflighted requests</h3>
+### Preflighted requests
 
-<p>Unlike <a href="#simple_requests"><em>simple requests</em> </a>, for "preflighted" requests the browser first sends an HTTP request using the {{HTTPMethod("OPTIONS")}} method to the resource on the other origin, in order to determine if the actual request is safe to send. Cross-site requests are preflighted like this since they may have implications to user data.</p>
+Unlike [_simple requests_ ](#simple_requests), for "preflighted" requests the browser first sends an HTTP request using the {{HTTPMethod("OPTIONS")}} method to the resource on the other origin, in order to determine if the actual request is safe to send. Cross-site requests are preflighted like this since they may have implications to user data.
 
-<p>The following is an example of a request that will be preflighted:</p>
+The following is an example of a request that will be preflighted:
 
-<pre class="brush: js">const xhr = new XMLHttpRequest();
+```js
+const xhr = new XMLHttpRequest();
 xhr.open('POST', 'https://bar.other/resources/post-here/');
 xhr.setRequestHeader('X-PINGOTHER', 'pingpong');
 xhr.setRequestHeader('Content-Type', 'application/xml');
 xhr.onreadystatechange = handler;
-xhr.send('&lt;person&gt;&lt;name&gt;Arun&lt;/name&gt;&lt;/person&gt;');
-</pre>
-
-<p>The example above creates an XML body to send with the <code>POST</code> request. Also, a non-standard HTTP <code>X-PINGOTHER</code> request header is set. Such headers are not part of HTTP/1.1, but are generally useful to web applications. Since the request uses a <code>Content-Type</code> of <code>application/xml</code>, and since a custom header is set, this request is preflighted.</p>
-
-<p><img alt="" src="preflight_correct.png"></p>
+xhr.send('<person><name>Arun</name></person>');
+```
+
+The example above creates an XML body to send with the `POST` request. Also, a non-standard HTTP `X-PINGOTHER` request header is set. Such headers are not part of HTTP/1.1, but are generally useful to web applications. Since the request uses a `Content-Type` of `application/xml`, and since a custom header is set, this request is preflighted.
 
-<div class="notecard note">
-  <p><strong>Note:</strong> As described below, the actual <code>POST</code> request does not include the <code>Access-Control-Request-*</code> headers; they are needed only for the <code>OPTIONS</code> request.</p>
-</div>
+![](preflight_correct.png)
 
-<p>Let's look at the full exchange between client and server. The first exchange is the <em>preflight request/response</em>:</p>
+> **Note:** As described below, the actual `POST` request does not include the `Access-Control-Request-*` headers; they are needed only for the `OPTIONS` request.
 
-<pre>OPTIONS /doc HTTP/1.1
-Host: bar.other
-User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:71.0) Gecko/20100101 Firefox/71.0
-Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
-Accept-Language: en-us,en;q=0.5
-Accept-Encoding: gzip,deflate
-Connection: keep-alive
-Origin: https://foo.example
-Access-Control-Request-Method: POST
-Access-Control-Request-Headers: X-PINGOTHER, Content-Type
+Let's look at the full exchange between client and server. The first exchange is the _preflight request/response_:
 
-HTTP/1.1 204 No Content
-Date: Mon, 01 Dec 2008 01:15:39 GMT
-Server: Apache/2
-Access-Control-Allow-Origin: https://foo.example
-Access-Control-Allow-Methods: POST, GET, OPTIONS
-Access-Control-Allow-Headers: X-PINGOTHER, Content-Type
-Access-Control-Max-Age: 86400
-Vary: Accept-Encoding, Origin
-Keep-Alive: timeout=2, max=100
-Connection: Keep-Alive
-</pre>
+    OPTIONS /doc HTTP/1.1
+    Host: bar.other
+    User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:71.0) Gecko/20100101 Firefox/71.0
+    Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
+    Accept-Language: en-us,en;q=0.5
+    Accept-Encoding: gzip,deflate
+    Connection: keep-alive
+    Origin: https://foo.example
+    Access-Control-Request-Method: POST
+    Access-Control-Request-Headers: X-PINGOTHER, Content-Type
 
-<p>Lines 1 - 10 above represent the preflight request with the {{HTTPMethod("OPTIONS")}} method. The browser determines that it needs to send this based on the request parameters that the JavaScript code snippet above was using, so that the server can respond whether it is acceptable to send the request with the actual request parameters. OPTIONS is an HTTP/1.1 method that is used to determine further information from servers, and is a {{Glossary("Safe/HTTP", "safe")}} method, meaning that it can't be used to change the resource. Note that along with the OPTIONS request, two other request headers are sent (lines 9 and 10 respectively):</p>
+    HTTP/1.1 204 No Content
+    Date: Mon, 01 Dec 2008 01:15:39 GMT
+    Server: Apache/2
+    Access-Control-Allow-Origin: https://foo.example
+    Access-Control-Allow-Methods: POST, GET, OPTIONS
+    Access-Control-Allow-Headers: X-PINGOTHER, Content-Type
+    Access-Control-Max-Age: 86400
+    Vary: Accept-Encoding, Origin
+    Keep-Alive: timeout=2, max=100
+    Connection: Keep-Alive
 
-<pre>Access-Control-Request-Method: POST
-Access-Control-Request-Headers: X-PINGOTHER, Content-Type
-</pre>
+Lines 1 - 10 above represent the preflight request with the {{HTTPMethod("OPTIONS")}} method. The browser determines that it needs to send this based on the request parameters that the JavaScript code snippet above was using, so that the server can respond whether it is acceptable to send the request with the actual request parameters. OPTIONS is an HTTP/1.1 method that is used to determine further information from servers, and is a {{Glossary("Safe/HTTP", "safe")}} method, meaning that it can't be used to change the resource. Note that along with the OPTIONS request, two other request headers are sent (lines 9 and 10 respectively):
 
-<p>The {{HTTPHeader("Access-Control-Request-Method")}} header notifies the server as part of a preflight request that when the actual request is sent, it will be sent with a <code>POST</code> request method. The {{HTTPHeader("Access-Control-Request-Headers")}} header notifies the server that when the actual request is sent, it will be sent with a <code>X-PINGOTHER</code> and <code>Content-Type</code> custom headers. The server now has an opportunity to determine whether it wishes to accept a request under these circumstances.</p>
+    Access-Control-Request-Method: POST
+    Access-Control-Request-Headers: X-PINGOTHER, Content-Type
 
-<p>Lines 13 - 22 above are the response that the server sends back, which indicate that the request method (<code>POST</code>) and request headers (<code>X-PINGOTHER</code>) are acceptable. In particular, let's look at lines 16-19:</p>
+The {{HTTPHeader("Access-Control-Request-Method")}} header notifies the server as part of a preflight request that when the actual request is sent, it will be sent with a `POST` request method. The {{HTTPHeader("Access-Control-Request-Headers")}} header notifies the server that when the actual request is sent, it will be sent with a `X-PINGOTHER` and `Content-Type` custom headers. The server now has an opportunity to determine whether it wishes to accept a request under these circumstances.
 
-<pre>Access-Control-Allow-Origin: https://foo.example
-Access-Control-Allow-Methods: POST, GET, OPTIONS
-Access-Control-Allow-Headers: X-PINGOTHER, Content-Type
-Access-Control-Max-Age: 86400</pre>
+Lines 13 - 22 above are the response that the server sends back, which indicate that the request method (`POST`) and request headers (`X-PINGOTHER`) are acceptable. In particular, let's look at lines 16-19:
 
-<p>The server responds with <code>Access-Control-Allow-Origin: https://foo.example</code>, restricting access to just the requesting origin domain. It also responds with <code>Access-Control-Allow-Methods</code>, which says that <code>POST</code> and <code>GET</code> are viable methods to query the resource in question (this header is similar to the {{HTTPHeader("Allow")}} response header, but used strictly within the context of access control).</p>
+    Access-Control-Allow-Origin: https://foo.example
+    Access-Control-Allow-Methods: POST, GET, OPTIONS
+    Access-Control-Allow-Headers: X-PINGOTHER, Content-Type
+    Access-Control-Max-Age: 86400
 
-<p>The server also sends <code>Access-Control-Allow-Headers</code> with a value of "<code>X-PINGOTHER, Content-Type</code>", confirming that these are permitted headers to be used with the actual request. Like <code>Access-Control-Allow-Methods</code>, <code>Access-Control-Allow-Headers</code> is a comma separated list of acceptable headers.</p>
+The server responds with `Access-Control-Allow-Origin: https://foo.example`, restricting access to just the requesting origin domain. It also responds with `Access-Control-Allow-Methods`, which says that `POST` and `GET` are viable methods to query the resource in question (this header is similar to the {{HTTPHeader("Allow")}} response header, but used strictly within the context of access control).
 
-<p>Finally, {{HTTPHeader("Access-Control-Max-Age")}} gives the value in seconds for how long the response to the preflight request can be cached for without sending another preflight request. In this case, 86400 seconds is 24 hours. Note that each browser has a <a href="/en-US/docs/Web/HTTP/Headers/Access-Control-Max-Age">maximum internal value</a> that takes precedence when the <code>Access-Control-Max-Age</code> is greater.</p>
+The server also sends `Access-Control-Allow-Headers` with a value of "`X-PINGOTHER, Content-Type`", confirming that these are permitted headers to be used with the actual request. Like `Access-Control-Allow-Methods`, `Access-Control-Allow-Headers` is a comma separated list of acceptable headers.
 
-<p>Once the preflight request is complete, the real request is sent:</p>
+Finally, {{HTTPHeader("Access-Control-Max-Age")}} gives the value in seconds for how long the response to the preflight request can be cached for without sending another preflight request. In this case, 86400 seconds is 24 hours. Note that each browser has a [maximum internal value](/en-US/docs/Web/HTTP/Headers/Access-Control-Max-Age) that takes precedence when the `Access-Control-Max-Age` is greater.
 
-<pre>POST /doc HTTP/1.1
-Host: bar.other
-User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:71.0) Gecko/20100101 Firefox/71.0
-Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
-Accept-Language: en-us,en;q=0.5
-Accept-Encoding: gzip,deflate
-Connection: keep-alive
-X-PINGOTHER: pingpong
-Content-Type: text/xml; charset=UTF-8
-Referer: https://foo.example/examples/preflightInvocation.html
-Content-Length: 55
-Origin: https://foo.example
-Pragma: no-cache
-Cache-Control: no-cache
+Once the preflight request is complete, the real request is sent:
 
-&lt;person&gt;&lt;name&gt;Arun&lt;/name&gt;&lt;/person&gt;
+    POST /doc HTTP/1.1
+    Host: bar.other
+    User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:71.0) Gecko/20100101 Firefox/71.0
+    Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
+    Accept-Language: en-us,en;q=0.5
+    Accept-Encoding: gzip,deflate
+    Connection: keep-alive
+    X-PINGOTHER: pingpong
+    Content-Type: text/xml; charset=UTF-8
+    Referer: https://foo.example/examples/preflightInvocation.html
+    Content-Length: 55
+    Origin: https://foo.example
+    Pragma: no-cache
+    Cache-Control: no-cache
 
-HTTP/1.1 200 OK
-Date: Mon, 01 Dec 2008 01:15:40 GMT
-Server: Apache/2
-Access-Control-Allow-Origin: https://foo.example
-Vary: Accept-Encoding, Origin
-Content-Encoding: gzip
-Content-Length: 235
-Keep-Alive: timeout=2, max=99
-Connection: Keep-Alive
-Content-Type: text/plain
+    <person><name>Arun</name></person>
 
-[Some XML payload]
-</pre>
+    HTTP/1.1 200 OK
+    Date: Mon, 01 Dec 2008 01:15:40 GMT
+    Server: Apache/2
+    Access-Control-Allow-Origin: https://foo.example
+    Vary: Accept-Encoding, Origin
+    Content-Encoding: gzip
+    Content-Length: 235
+    Keep-Alive: timeout=2, max=99
+    Connection: Keep-Alive
+    Content-Type: text/plain
 
-<h4 id="Preflighted_requests_and_redirects">Preflighted requests and redirects</h4>
+    [Some XML payload]
 
-<p>Not all browsers currently support following redirects after a preflighted request. If a redirect occurs after a preflighted request, some browsers currently will report an error message such as the following.</p>
+#### Preflighted requests and redirects
 
-<blockquote>
-<p>The request was redirected to 'https://example.com/foo', which is disallowed for cross-origin requests that require preflight</p>
-</blockquote>
+Not all browsers currently support following redirects after a preflighted request. If a redirect occurs after a preflighted request, some browsers currently will report an error message such as the following.
 
-<blockquote>
-<p>Request requires preflight, which is disallowed to follow cross-origin redirect</p>
-</blockquote>
+> The request was redirected to 'https\://example.com/foo', which is disallowed for cross-origin requests that require preflight
 
-<p>The CORS protocol originally required that behavior but <a href="https://github.com/whatwg/fetch/commit/0d9a4db8bc02251cc9e391543bb3c1322fb882f2">was subsequently changed to no longer require it</a>. However, not all browsers have implemented the change, and so still exhibit the behavior that was originally required.</p>
+> Request requires preflight, which is disallowed to follow cross-origin redirect
 
-<p>Until browsers catch up with the spec, you may be able to work around this limitation by doing one or both of the following:</p>
+The CORS protocol originally required that behavior but [was subsequently changed to no longer require it](https://github.com/whatwg/fetch/commit/0d9a4db8bc02251cc9e391543bb3c1322fb882f2). However, not all browsers have implemented the change, and so still exhibit the behavior that was originally required.
 
-<ul>
- <li>Change the server-side behavior to avoid the preflight and/or to avoid the redirect</li>
- <li>Change the request such that it is a <a href="#simple_requests">simple request</a> that doesn’t cause a preflight</li>
-</ul>
+Until browsers catch up with the spec, you may be able to work around this limitation by doing one or both of the following:
 
-<p>If that's not possible, then another way is to:</p>
+- Change the server-side behavior to avoid the preflight and/or to avoid the redirect
+- Change the request such that it is a [simple request](#simple_requests) that doesn’t cause a preflight
 
-<ol>
- <li>Make a <a href="#simple_requests">simple request</a> (using {{domxref("Response.url")}} for the Fetch API, or {{domxref("XMLHttpRequest.responseURL")}}) to determine what URL the real preflighted request would end up at.</li>
- <li>Make another request (the <em>real</em> request) using the URL you obtained from <code>Response.url</code> or <code>XMLHttpRequest.responseURL</code> in the first step.</li>
-</ol>
+If that's not possible, then another way is to:
 
-<p>However, if the request is one that triggers a preflight due to the presence of the <code>Authorization</code> header in the request, you won't be able to work around the limitation using the steps above. And you won't be able to work around it at all unless you have control over the server the request is being made to.</p>
+1.  Make a [simple request](#simple_requests) (using {{domxref("Response.url")}} for the Fetch API, or {{domxref("XMLHttpRequest.responseURL")}}) to determine what URL the real preflighted request would end up at.
+2.  Make another request (the _real_ request) using the URL you obtained from `Response.url` or `XMLHttpRequest.responseURL` in the first step.
 
-<h3 id="Requests_with_credentials">Requests with credentials</h3>
+However, if the request is one that triggers a preflight due to the presence of the `Authorization` header in the request, you won't be able to work around the limitation using the steps above. And you won't be able to work around it at all unless you have control over the server the request is being made to.
 
-<div class="notecard note">
-  <p><strong>Note:</strong> When making credentialed requests to a different domain, third-party cookie policies will still apply. The policy is always enforced independent of any setup on the server and the client, as described in this chapter.</p>
-</div>
+### Requests with credentials
 
-<p>The most interesting capability exposed by both {{domxref("XMLHttpRequest")}} or <a href="/en-US/docs/Web/API/Fetch_API">Fetch</a> and CORS is the ability to make "credentialed" requests that are aware of <a href="/en-US/docs/Web/HTTP/Cookies">HTTP cookies</a> and HTTP Authentication information. By default, in cross-site <code>XMLHttpRequest</code> or <a href="/en-US/docs/Web/API/Fetch_API">Fetch</a> invocations, browsers will <strong>not</strong> send credentials. A specific flag has to be set on the <code>XMLHttpRequest</code> object or the {{domxref("Request")}} constructor when it is invoked.</p>
+> **Note:** When making credentialed requests to a different domain, third-party cookie policies will still apply. The policy is always enforced independent of any setup on the server and the client, as described in this chapter.
 
-<p>In this example, content originally loaded from <code>https://foo.example</code> makes a simple GET request to a resource on <code>https://bar.other</code> which sets Cookies. Content on foo.example might contain JavaScript like this:</p>
+The most interesting capability exposed by both {{domxref("XMLHttpRequest")}} or [Fetch](/en-US/docs/Web/API/Fetch_API) and CORS is the ability to make "credentialed" requests that are aware of [HTTP cookies](/en-US/docs/Web/HTTP/Cookies) and HTTP Authentication information. By default, in cross-site `XMLHttpRequest` or [Fetch](/en-US/docs/Web/API/Fetch_API) invocations, browsers will **not** send credentials. A specific flag has to be set on the `XMLHttpRequest` object or the {{domxref("Request")}} constructor when it is invoked.
 
-<pre class="brush: js">const invocation = new XMLHttpRequest();
+In this example, content originally loaded from `https://foo.example` makes a simple GET request to a resource on `https://bar.other` which sets Cookies. Content on foo.example might contain JavaScript like this:
+
+```js
+const invocation = new XMLHttpRequest();
 const url = 'https://bar.other/resources/credentialed-content/';
 
 function callOtherDomain() {
@@ -302,211 +279,183 @@ function callOtherDomain() {
     invocation.onreadystatechange = handler;
     invocation.send();
   }
-}</pre>
+}
+```
+
+Line 7 shows the flag on {{domxref("XMLHttpRequest")}} that has to be set in order to make the invocation with Cookies, namely the `withCredentials` boolean value. By default, the invocation is made without Cookies. Since this is a simple `GET` request, it is not preflighted, but the browser will **reject** any response that does not have the {{HTTPHeader("Access-Control-Allow-Credentials")}}`: true` header, and **not** make the response available to the invoking web content.
 
-<p>Line 7 shows the flag on {{domxref("XMLHttpRequest")}} that has to be set in order to make the invocation with Cookies, namely the <code>withCredentials</code> boolean value. By default, the invocation is made without Cookies. Since this is a simple <code>GET</code> request, it is not preflighted, but the browser will <strong>reject</strong> any response that does not have the {{HTTPHeader("Access-Control-Allow-Credentials")}}<code>: true</code> header, and <strong>not</strong> make the response available to the invoking web content.</p>
+![](cred-req-updated.png)
 
-<p><img alt="" src="cred-req-updated.png"></p>
+Here is a sample exchange between client and server:
 
-<p>Here is a sample exchange between client and server:</p>
+    GET /resources/credentialed-content/ HTTP/1.1
+    Host: bar.other
+    User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:71.0) Gecko/20100101 Firefox/71.0
+    Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
+    Accept-Language: en-us,en;q=0.5
+    Accept-Encoding: gzip,deflate
+    Connection: keep-alive
+    Referer: https://foo.example/examples/credential.html
+    Origin: https://foo.example
+    Cookie: pageAccess=2
 
-<pre>GET /resources/credentialed-content/ HTTP/1.1
-Host: bar.other
-User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:71.0) Gecko/20100101 Firefox/71.0
-Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
-Accept-Language: en-us,en;q=0.5
-Accept-Encoding: gzip,deflate
-Connection: keep-alive
-Referer: https://foo.example/examples/credential.html
-Origin: https://foo.example
-Cookie: pageAccess=2
+    HTTP/1.1 200 OK
+    Date: Mon, 01 Dec 2008 01:34:52 GMT
+    Server: Apache/2
+    Access-Control-Allow-Origin: https://foo.example
+    Access-Control-Allow-Credentials: true
+    Cache-Control: no-cache
+    Pragma: no-cache
+    Set-Cookie: pageAccess=3; expires=Wed, 31-Dec-2008 01:34:53 GMT
+    Vary: Accept-Encoding, Origin
+    Content-Encoding: gzip
+    Content-Length: 106
+    Keep-Alive: timeout=2, max=100
+    Connection: Keep-Alive
+    Content-Type: text/plain
 
-HTTP/1.1 200 OK
-Date: Mon, 01 Dec 2008 01:34:52 GMT
-Server: Apache/2
-Access-Control-Allow-Origin: https://foo.example
-Access-Control-Allow-Credentials: true
-Cache-Control: no-cache
-Pragma: no-cache
-Set-Cookie: pageAccess=3; expires=Wed, 31-Dec-2008 01:34:53 GMT
-Vary: Accept-Encoding, Origin
-Content-Encoding: gzip
-Content-Length: 106
-Keep-Alive: timeout=2, max=100
-Connection: Keep-Alive
-Content-Type: text/plain
+    [text/plain payload]
 
-[text/plain payload]
-</pre>
+Although line 10 contains the Cookie destined for the content on `https://bar.other`, if bar.other did not respond with an {{HTTPHeader("Access-Control-Allow-Credentials")}}`: true` (line 17) the response would be ignored and not made available to web content.
 
-<p>Although line 10 contains the Cookie destined for the content on <code>https://bar.other</code>, if bar.other did not respond with an {{HTTPHeader("Access-Control-Allow-Credentials")}}<code>: true</code> (line 17) the response would be ignored and not made available to web content.</p>
+#### Preflight requests and credentials
 
-<h4 id="Preflight_requests_and_credentials">Preflight requests and credentials</h4>
+CORS-preflight requests must never include credentials. The _response_ to a preflight request must specify `Access-Control-Allow-Credentials: true` to indicate that the actual request can be made with credentials.
 
-<p>CORS-preflight requests must never include credentials. The <em>response</em> to a preflight request must specify <code>Access-Control-Allow-Credentials: true</code> to indicate that the actual request can be made with credentials.</p>
+> **Note:** Some enterprise authentication services require TLS client certificates be sent in preflight requests, in contravention of the {{SpecName("Fetch","#cors-protocol-and-credentials")}} specification.
+>
+> Firefox 87 allows this non-compliant behavior to be enabled by setting the preference: `network.cors_preflight.allow_client_cert` to `true` ({{bug(1511151)}}). Chromium-based browsers currently always send TLS client certificates in CORS preflight requests ([Chrome bug 775438](https://bugs.chromium.org/p/chromium/issues/detail?id=775438)).
 
-<div class="notecard note">
-  <p><strong>Note:</strong> Some enterprise authentication services require TLS client certificates be sent in preflight requests, in contravention of the {{SpecName("Fetch","#cors-protocol-and-credentials")}} specification.</p>
-  <p>Firefox 87 allows this non-compliant behavior to be enabled by setting the preference: <code>network.cors_preflight.allow_client_cert</code> to <code>true</code> ({{bug(1511151)}}). Chromium-based browsers currently always send TLS client certificates in CORS preflight requests (<a href="https://bugs.chromium.org/p/chromium/issues/detail?id=775438">Chrome bug 775438</a>).</p>
-</div>
+#### Credentialed requests and wildcards
 
-<h4 id="Credentialed_requests_and_wildcards">Credentialed requests and wildcards</h4>
+When responding to a credentialed request, the server **must** specify an origin in the value of the `Access-Control-Allow-Origin` header, instead of specifying the "`*`" wildcard.
 
-<p>When responding to a credentialed request, the server <strong>must</strong> specify an origin in the value of the <code>Access-Control-Allow-Origin</code> header, instead of specifying the "<code>*</code>" wildcard.</p>
+Because the request headers in the above example include a `Cookie` header, the request would fail if the value of the `Access-Control-Allow-Origin` header was "\*". But it does not fail: Because the value of the `Access-Control-Allow-Origin` header is "`https://foo.example`" (an actual origin) rather than the "`*`" wildcard, the credential-cognizant content is returned to the invoking web content.
 
-<p>Because the request headers in the above example include a <code>Cookie</code> header, the request would fail if the value of the <code>Access-Control-Allow-Origin</code> header was "*". But it does not fail: Because the value of the <code>Access-Control-Allow-Origin</code> header is "<code>https://foo.example</code>" (an actual origin) rather than the "<code>*</code>" wildcard, the credential-cognizant content is returned to the invoking web content.</p>
+Note that the `Set-Cookie` response header in the example above also sets a further cookie. In case of failure, an exception—depending on the API used—is raised.
 
-<p>Note that the <code>Set-Cookie</code> response header in the example above also sets a further cookie. In case of failure, an exception—depending on the API used—is raised.</p>
+#### Third-party cookies
 
-<h4 id="Third-party_cookies">Third-party cookies</h4>
+Note that cookies set in CORS responses are subject to normal third-party cookie policies. In the example above, the page is loaded from `foo.example`, but the cookie on line 20 is sent by `bar.other`, and would thus not be saved if the user has configured their browser to reject all third-party cookies.
 
-<p>Note that cookies set in CORS responses are subject to normal third-party cookie policies. In the example above, the page is loaded from <code>foo.example</code>, but the cookie on line 20 is sent by <code>bar.other</code>, and would thus not be saved if the user has configured their browser to reject all third-party cookies.</p>
+Cookie in the request (line 10) may also be suppressed in normal third-party cookie policies. The enforced cookie policy may therefore nullify the capability described in this chapter, effectively prevents you from making credentialed requests whatsoever.
 
-<p>Cookie in the request (line 10) may also be suppressed in normal third-party cookie policies. The enforced cookie policy may therefore nullify the capability described in this chapter, effectively prevents you from making credentialed requests whatsoever.</p>
+Cookie policy around the [SameSite](/en-US/docs/Web/HTTP/Headers/Set-Cookie/SameSite) attribute would apply.
 
-<p>Cookie policy around the <a href="/en-US/docs/Web/HTTP/Headers/Set-Cookie/SameSite">SameSite</a> attribute would apply.</p>
+## The HTTP response headers
 
-<h2 id="The_HTTP_response_headers">The HTTP response headers</h2>
+This section lists the HTTP response headers that servers send back for access control requests as defined by the Cross-Origin Resource Sharing specification. The previous section gives an overview of these in action.
 
-<p>This section lists the HTTP response headers that servers send back for access control requests as defined by the Cross-Origin Resource Sharing specification. The previous section gives an overview of these in action.</p>
+### Access-Control-Allow-Origin
 
-<h3 id="Access-Control-Allow-Origin">Access-Control-Allow-Origin</h3>
+A returned resource may have one {{HTTPHeader("Access-Control-Allow-Origin")}} header, with the following syntax:
 
-<p>A returned resource may have one {{HTTPHeader("Access-Control-Allow-Origin")}} header, with the following syntax:</p>
+    Access-Control-Allow-Origin: <origin> | *
 
-<pre>Access-Control-Allow-Origin: &lt;origin&gt; | *
-</pre>
+`Access-Control-Allow-Origin` specifies either a single origin, which tells browsers to allow that origin to access the resource; or else — for requests **without** credentials — the "`*`" wildcard, to tell browsers to allow any origin to access the resource.
 
-<p><code>Access-Control-Allow-Origin</code> specifies either a single origin, which tells browsers to allow that origin to access the resource; or else — for requests <strong>without</strong> credentials — the "<code>*</code>" wildcard, to tell browsers to allow any origin to access the resource.</p>
+For example, to allow code from the origin `https://mozilla.org` to access the resource, you can specify:
 
-<p>For example, to allow code from the origin <code>https://mozilla.org</code> to access the resource, you can specify:</p>
+    Access-Control-Allow-Origin: https://mozilla.org
+    Vary: Origin
 
-<pre>Access-Control-Allow-Origin: https://mozilla.org
-Vary: Origin</pre>
+If the server specifies a single origin (that may dynamically change based on the requesting origin as part of a allowlist) rather than the "`*`" wildcard, then the server should also include `Origin` in the {{HTTPHeader("Vary")}} response header — to indicate to clients that server responses will differ based on the value of the {{HTTPHeader("Origin")}} request header.
 
-<p>If the server specifies a single origin (that may dynamically change based on the requesting origin as part of a allowlist) rather than the "<code>*</code>" wildcard, then the server should also include <code>Origin</code> in the {{HTTPHeader("Vary")}} response header — to indicate to clients that server responses will differ based on the value of the {{HTTPHeader("Origin")}} request header.</p>
+### Access-Control-Expose-Headers
 
-<h3 id="Access-Control-Expose-Headers">Access-Control-Expose-Headers</h3>
+The {{HTTPHeader("Access-Control-Expose-Headers")}} header adds the specified headers to the allowlist that JavaScript (such as {{domxref("XMLHttpRequest.getResponseHeader()","getResponseHeader()")}}) in browsers is allowed to access.
 
-<p>The {{HTTPHeader("Access-Control-Expose-Headers")}} header adds the specified headers to the allowlist that JavaScript (such as {{domxref("XMLHttpRequest.getResponseHeader()","getResponseHeader()")}}) in browsers is allowed to access.</p>
+    Access-Control-Expose-Headers: <header-name>[, <header-name>]*
 
-<pre>Access-Control-Expose-Headers: &lt;header-name&gt;[, &lt;header-name&gt;]*
-</pre>
+For example, the following:
 
-<p>For example, the following:</p>
+    Access-Control-Expose-Headers: X-My-Custom-Header, X-Another-Custom-Header
 
-<pre>Access-Control-Expose-Headers: X-My-Custom-Header, X-Another-Custom-Header
-</pre>
+…would allow the `X-My-Custom-Header` and `X-Another-Custom-Header` headers to be exposed to the browser.
 
-<p>…would allow the <code>X-My-Custom-Header</code> and <code>X-Another-Custom-Header</code> headers to be exposed to the browser.</p>
+### Access-Control-Max-Age
 
-<h3 id="Access-Control-Max-Age">Access-Control-Max-Age</h3>
+The {{HTTPHeader("Access-Control-Max-Age")}} header indicates how long the results of a preflight request can be cached. For an example of a preflight request, see the above examples.
 
-<p>The {{HTTPHeader("Access-Control-Max-Age")}} header indicates how long the results of a preflight request can be cached. For an example of a preflight request, see the above examples.</p>
+    Access-Control-Max-Age: <delta-seconds>
 
-<pre>Access-Control-Max-Age: &lt;delta-seconds&gt;
-</pre>
+The `delta-seconds` parameter indicates the number of seconds the results can be cached.
 
-<p>The <code>delta-seconds</code> parameter indicates the number of seconds the results can be cached.</p>
+### Access-Control-Allow-Credentials
 
-<h3 id="Access-Control-Allow-Credentials">Access-Control-Allow-Credentials</h3>
+The {{HTTPHeader("Access-Control-Allow-Credentials")}} header indicates whether or not the response to the request can be exposed when the `credentials` flag is true. When used as part of a response to a preflight request, this indicates whether or not the actual request can be made using credentials. Note that simple `GET` requests are not preflighted, and so if a request is made for a resource with credentials, if this header is not returned with the resource, the response is ignored by the browser and not returned to web content.
 
-<p>The {{HTTPHeader("Access-Control-Allow-Credentials")}} header indicates whether or not the response to the request can be exposed when the <code>credentials</code> flag is true. When used as part of a response to a preflight request, this indicates whether or not the actual request can be made using credentials. Note that simple <code>GET</code> requests are not preflighted, and so if a request is made for a resource with credentials, if this header is not returned with the resource, the response is ignored by the browser and not returned to web content.</p>
+    Access-Control-Allow-Credentials: true
 
-<pre>Access-Control-Allow-Credentials: true
-</pre>
+[Credentialed requests](#requests_with_credentials) are discussed above.
 
-<p><a href="#requests_with_credentials">Credentialed requests</a> are discussed above.</p>
+### Access-Control-Allow-Methods
 
-<h3 id="Access-Control-Allow-Methods">Access-Control-Allow-Methods</h3>
+The {{HTTPHeader("Access-Control-Allow-Methods")}} header specifies the method or methods allowed when accessing the resource. This is used in response to a preflight request. The conditions under which a request is preflighted are discussed above.
 
-<p>The {{HTTPHeader("Access-Control-Allow-Methods")}} header specifies the method or methods allowed when accessing the resource. This is used in response to a preflight request. The conditions under which a request is preflighted are discussed above.</p>
+    Access-Control-Allow-Methods: <method>[, <method>]*
 
-<pre>Access-Control-Allow-Methods: &lt;method&gt;[, &lt;method&gt;]*
-</pre>
+An example of a {{Glossary("preflight request")}} is given above, including an example which sends this header to the browser.
 
-<p>An example of a {{Glossary("preflight request")}} is given above</a>, including an example which sends this header to the browser.</p>
+### Access-Control-Allow-Headers
 
-<h3 id="Access-Control-Allow-Headers">Access-Control-Allow-Headers</h3>
+The {{HTTPHeader("Access-Control-Allow-Headers")}} header is used in response to a {{Glossary("preflight request")}} to indicate which HTTP headers can be used when making the actual request. This header is the server side response to the browser's {{HTTPHeader("Access-Control-Request-Headers")}} header.
 
-<p>The {{HTTPHeader("Access-Control-Allow-Headers")}} header is used in response to a {{Glossary("preflight request")}} to indicate which HTTP headers can be used when making the actual request. This header is the server side response to the browser's {{HTTPHeader("Access-Control-Request-Headers")}} header.</p>
+    Access-Control-Allow-Headers: <header-name>[, <header-name>]*
 
-<pre>Access-Control-Allow-Headers: &lt;header-name&gt;[, &lt;header-name&gt;]*
-</pre>
+## The HTTP request headers
 
-<h2 id="The_HTTP_request_headers">The HTTP request headers</h2>
+This section lists headers that clients may use when issuing HTTP requests in order to make use of the cross-origin sharing feature. Note that these headers are set for you when making invocations to servers. Developers using cross-site {{domxref("XMLHttpRequest")}} capability do not have to set any cross-origin sharing request headers programmatically.
 
-<p>This section lists headers that clients may use when issuing HTTP requests in order to make use of the cross-origin sharing feature. Note that these headers are set for you when making invocations to servers. Developers using cross-site {{domxref("XMLHttpRequest")}} capability do not have to set any cross-origin sharing request headers programmatically.</p>
+### Origin
 
-<h3 id="Origin">Origin</h3>
+The {{HTTPHeader("Origin")}} header indicates the origin of the cross-site access request or preflight request.
 
-<p>The {{HTTPHeader("Origin")}} header indicates the origin of the cross-site access request or preflight request.</p>
+    Origin: <origin>
 
-<pre>Origin: &lt;origin&gt;
-</pre>
+The origin is a URL indicating the server from which the request initiated. It does not include any path information, but only the server name.
 
-<p>The origin is a URL indicating the server from which the request initiated. It does not include any path information, but only the server name.</p>
+> **Note:** The `origin` value can be `null`.
 
-<div class="notecard note">
-  <p><strong>Note:</strong> The <code>origin</code> value can be <code>null</code>.</p>
-</div>
+Note that in any access control request, the {{HTTPHeader("Origin")}} header is **always** sent.
 
-<p>Note that in any access control request, the {{HTTPHeader("Origin")}} header is <strong>always</strong> sent.</p>
+### Access-Control-Request-Method
 
-<h3 id="Access-Control-Request-Method">Access-Control-Request-Method</h3>
+The {{HTTPHeader("Access-Control-Request-Method")}} is used when issuing a preflight request to let the server know what HTTP method will be used when the actual request is made.
 
-<p>The {{HTTPHeader("Access-Control-Request-Method")}} is used when issuing a preflight request to let the server know what HTTP method will be used when the actual request is made.</p>
+    Access-Control-Request-Method: <method>
 
-<pre>Access-Control-Request-Method: &lt;method&gt;
-</pre>
+Examples of this usage can be [found above.](#preflighted_requests)
 
-<p>Examples of this usage can be <a href="#preflighted_requests">found above.</a></p>
+### Access-Control-Request-Headers
 
-<h3 id="Access-Control-Request-Headers">Access-Control-Request-Headers</h3>
+The {{HTTPHeader("Access-Control-Request-Headers")}} header is used when issuing a preflight request to let the server know what HTTP headers will be used when the actual request is made (such as with {{domxref("XMLHttpRequest.setRequestHeader()","setRequestHeader()")}}). This browser side header will be answered by the complementary server side header of {{HTTPHeader("Access-Control-Allow-Headers")}}.
 
-<p>The {{HTTPHeader("Access-Control-Request-Headers")}} header is used when issuing a preflight request to let the server know what HTTP headers will be used when the actual request is made (such as with {{domxref("XMLHttpRequest.setRequestHeader()","setRequestHeader()")}}). This browser side header will be answered by the complementary server side header of {{HTTPHeader("Access-Control-Allow-Headers")}}.</p>
+    Access-Control-Request-Headers: <field-name>[, <field-name>]*
 
-<pre>Access-Control-Request-Headers: &lt;field-name&gt;[, &lt;field-name&gt;]*
-</pre>
+Examples of this usage can be [found above](#preflighted_requests).
 
-<p>Examples of this usage can be <a href="#preflighted_requests">found above</a>.</p>
+## Specifications
 
-<h2 id="Specifications">Specifications</h2>
+| Specification                                                    | Status                   | Comment                                                                          |
+| ---------------------------------------------------------------- | ------------------------ | -------------------------------------------------------------------------------- |
+| {{SpecName('Fetch', '#cors-protocol', 'CORS')}} | {{Spec2('Fetch')}} | New definition; supplants [W3C CORS](https://www.w3.org/TR/cors/) specification. |
 
-<table class="standard-table">
- <tbody>
-  <tr>
-   <th scope="col">Specification</th>
-   <th scope="col">Status</th>
-   <th scope="col">Comment</th>
-  </tr>
-  <tr>
-   <td>{{SpecName('Fetch', '#cors-protocol', 'CORS')}}</td>
-   <td>{{Spec2('Fetch')}}</td>
-   <td>New definition; supplants <a href="https://www.w3.org/TR/cors/">W3C CORS</a> specification.</td>
-  </tr>
- </tbody>
-</table>
+## Browser compatibility
 
-<h2 id="Browser_compatibility">Browser compatibility</h2>
+{{Compat("http.headers.Access-Control-Allow-Origin")}}
 
-<p>{{Compat("http.headers.Access-Control-Allow-Origin")}}</p>
+## See also
 
-<h2 id="See_also">See also</h2>
+- [CORS errors](/en-US/docs/Web/HTTP/CORS/Errors)
+- [Enable CORS: I want to add CORS support to my server](https://enable-cors.org/server.html)
+- {{domxref("XMLHttpRequest")}}
+- [Fetch API](/en-US/docs/Web/API/Fetch_API)
+- [Will it CORS?](https://httptoolkit.tech/will-it-cors) - an interactive CORS explainer & generator
+- [Using CORS with All (Modern) Browsers](https://www.telerik.com/blogs/using-cors-with-all-modern-browsers)
+- [How to run Chrome browser without CORS](https://alfilatov.com/posts/run-chrome-without-cors/)
+- [Stack Overflow answer with “how to” info for dealing with common problems](https://stackoverflow.com/questions/43871637/no-access-control-allow-origin-header-is-present-on-the-requested-resource-whe/43881141#43881141):
 
-<ul>
- <li><a href="/en-US/docs/Web/HTTP/CORS/Errors">CORS errors</a></li>
- <li><a href="https://enable-cors.org/server.html">Enable CORS: I want to add CORS support to my server</a></li>
- <li>{{domxref("XMLHttpRequest")}}</li>
- <li><a href="/en-US/docs/Web/API/Fetch_API">Fetch API</a></li>
- <li><a href="https://httptoolkit.tech/will-it-cors">Will it CORS?</a> - an interactive CORS explainer &amp; generator</li>
- <li><a href="https://www.telerik.com/blogs/using-cors-with-all-modern-browsers">Using CORS with All (Modern) Browsers</a></li>
- <li><a href="https://alfilatov.com/posts/run-chrome-without-cors/">How to run Chrome browser without CORS</a></li>
- <li><a href="https://stackoverflow.com/questions/43871637/no-access-control-allow-origin-header-is-present-on-the-requested-resource-whe/43881141#43881141">Stack Overflow answer with “how to” info for dealing with common problems</a>:
-  <ul>
-   <li>How to avoid the CORS preflight</li>
-   <li>How to use a CORS proxy to get around <em>“No Access-Control-Allow-Origin header”</em></li>
-   <li>How to fix <em>“Access-Control-Allow-Origin header must not be the wildcard”</em></li>
-  </ul>
- </li>
-</ul>
+  - How to avoid the CORS preflight
+  - How to use a CORS proxy to get around _“No Access-Control-Allow-Origin header”_
+  - How to fix _“Access-Control-Allow-Origin header must not be the wildcard”_
diff --git a/files/en-us/web/http/cross-origin_resource_policy_(corp)/index.md b/files/en-us/web/http/cross-origin_resource_policy_(corp)/index.md
index 6587ba8d1ba5c56..4cc3f1d8d0fcda7 100644
--- a/files/en-us/web/http/cross-origin_resource_policy_(corp)/index.md
+++ b/files/en-us/web/http/cross-origin_resource_policy_(corp)/index.md
@@ -6,80 +6,59 @@ tags:
   - Reference
   - Security
 ---
-<div>{{HTTPSidebar}}</div>
+{{HTTPSidebar}}
 
-<p><strong>Cross-Origin Resource Policy</strong> is a policy set by the <a href="/en-US/docs/Web/HTTP/Headers/Cross-Origin-Resource-Policy"><code>Cross-Origin-Resource-Policy</code> HTTP header</a> that lets web sites and applications opt in to protection against certain requests from other origins (such as those issued with elements like <code>&lt;script&gt;</code> and <code>&lt;img&gt;</code>), to mitigate speculative side-channel attacks, like <a href="https://en.wikipedia.org/wiki/Spectre_(security_vulnerability)">Spectre</a>, as well as Cross-Site Script Inclusion attacks.</p>
+**Cross-Origin Resource Policy** is a policy set by the [`Cross-Origin-Resource-Policy` HTTP header](/en-US/docs/Web/HTTP/Headers/Cross-Origin-Resource-Policy) that lets web sites and applications opt in to protection against certain requests from other origins (such as those issued with elements like `<script>` and `<img>`), to mitigate speculative side-channel attacks, like [Spectre](<https://en.wikipedia.org/wiki/Spectre_(security_vulnerability)>), as well as Cross-Site Script Inclusion attacks.
 
-<p>CORP is an additional layer of protection beyond the default {{Glossary("same-origin policy")}}. Cross-Origin Resource Policy complements <a href="https://fetch.spec.whatwg.org/#corb">Cross-Origin Read Blocking</a> (CORB), which is a mechanism to prevent some cross-origin reads by default.</p>
+CORP is an additional layer of protection beyond the default {{Glossary("same-origin policy")}}. Cross-Origin Resource Policy complements [Cross-Origin Read Blocking](https://fetch.spec.whatwg.org/#corb) (CORB), which is a mechanism to prevent some cross-origin reads by default.
 
-<div class="notecard note">
-  <p><strong>Note:</strong> The policy is only effective for <a href="https://fetch.spec.whatwg.org/#concept-request-mode"><code>no-cors</code></a> requests, which are issued by default for CORS-safelisted methods/headers.</p>
-</div>
+> **Note:** The policy is only effective for [`no-cors`](https://fetch.spec.whatwg.org/#concept-request-mode) requests, which are issued by default for CORS-safelisted methods/headers.
 
-<p>As this policy is expressed via a <em><a href="/en-US/docs/Glossary/Response_header">response header</a></em>, the actual request is not prevented—rather, the browser prevents the <em>result</em> from being leaked by stripping the response body.</p>
+As this policy is expressed via a _[response header](/en-US/docs/Glossary/Response_header)_, the actual request is not prevented—rather, the browser prevents the _result_ from being leaked by stripping the response body.
 
-<h2 id="History">History</h2>
+## History
 
-<p>The concept was originally proposed in 2012 (as <code>From-Origin</code>), but <a href="https://github.com/whatwg/fetch/issues/687">resurrected</a> in Q2 of 2018 and implemented in Safari and Chromium.</p>
+The concept was originally proposed in 2012 (as `From-Origin`), but [resurrected](https://github.com/whatwg/fetch/issues/687) in Q2 of 2018 and implemented in Safari and Chromium.
 
-<p>In early 2018, two side-channel hardware vulnerabilities known as <em>Meltdown</em> and <em>Spectre</em> were disclosed. These vulnerabilities allowed sensitive data disclosure due to a race condition which arose as part of speculative execution functionality, designed to improve performance.</p>
+In early 2018, two side-channel hardware vulnerabilities known as _Meltdown_ and _Spectre_ were disclosed. These vulnerabilities allowed sensitive data disclosure due to a race condition which arose as part of speculative execution functionality, designed to improve performance.
 
-<p>In response, Chromium shipped <a href="https://fetch.spec.whatwg.org/#corb">Cross-Origin Read Blocking</a>, which automatically protects certain resources (of <code>Content-Type</code> HTML, JSON and XML) against cross-origin reads. If the application does not serve a <a href="/en-US/docs/Web/HTTP/Headers/X-Content-Type-Options"><code>no-sniff</code> directive</a>, Chromium will attempt to guess the <code>Content-Type</code> and apply the protection anyway.</p>
+In response, Chromium shipped [Cross-Origin Read Blocking](https://fetch.spec.whatwg.org/#corb), which automatically protects certain resources (of `Content-Type` HTML, JSON and XML) against cross-origin reads. If the application does not serve a [`no-sniff` directive](/en-US/docs/Web/HTTP/Headers/X-Content-Type-Options), Chromium will attempt to guess the `Content-Type` and apply the protection anyway.
 
-<p>Cross-Origin Resource Policy is an opt-in response header which can protect <em>any</em> resource; there is no need for browsers to sniff MIME types.</p>
+Cross-Origin Resource Policy is an opt-in response header which can protect _any_ resource; there is no need for browsers to sniff MIME types.
 
-<h2 id="Usage">Usage</h2>
+## Usage
 
-<div class="notecard note">
-  <p><strong>Note:</strong> Due to a <a href="https://bugs.chromium.org/p/chromium/issues/detail?id=1074261">bug in Chrome</a>, setting Cross-Origin-Resource-Policy can break PDF rendering, preventing visitors from being able to read past the first page of some PDFs. Exercise caution using this header in a production environment.</p>
-</div>
+> **Note:** Due to a [bug in Chrome](https://bugs.chromium.org/p/chromium/issues/detail?id=1074261), setting Cross-Origin-Resource-Policy can break PDF rendering, preventing visitors from being able to read past the first page of some PDFs. Exercise caution using this header in a production environment.
 
-<p>Web applications set a Cross-Origin Resource Policy via the {{HTTPHeader("Cross-Origin-Resource-Policy")}} HTTP response header, which accepts one of three values:</p>
+Web applications set a Cross-Origin Resource Policy via the {{HTTPHeader("Cross-Origin-Resource-Policy")}} HTTP response header, which accepts one of three values:
 
-<dl>
-  <dt><code>same-site</code></dt>
-  <dd>
-    <p>Only requests from the same <em>{{Glossary("Site")}}</em> can read the resource.</p>
+- `same-site`
 
-    <div class="notecard warning">
-      <p><strong>Warning:</strong> This is less secure than an {{Glossary("origin")}}. The <a href="https://html.spec.whatwg.org/multipage/origin.html#same-site">algorithm for checking if two origins are same site</a> is defined in the HTML standard and involves checking the <em>registrable domain</em>.</p>
-    </div>
-  </dd>
+  - : Only requests from the same _{{Glossary("Site")}}_ can read the resource.
 
-  <dt><code>same-origin</code></dt>
-  <dd>Only requests from the same <em>{{Glossary("origin")}}</em> (i.e. scheme + host + port) can read the resource.</dd>
+    > **Warning:** This is less secure than an {{Glossary("origin")}}. The [algorithm for checking if two origins are same site](https://html.spec.whatwg.org/multipage/origin.html#same-site) is defined in the HTML standard and involves checking the _registrable domain_.
 
-  <dt><code>cross-origin</code></dt>
-  <dd>Requests from any <em>{{Glossary("origin")}}</em> (both same-site and cross-site) can read the resource.</dd>
-</dl>
+- `same-origin`
+  - : Only requests from the same _{{Glossary("origin")}}_ (i.e. scheme + host + port) can read the resource.
+- `cross-origin`
+  - : Requests from any _{{Glossary("origin")}}_ (both same-site and cross-site) can read the resource.
 
-<pre>Cross-Origin-Resource-Policy: same-site | same-origin | cross-origin</pre>
+<!---->
 
-<p>During a cross-origin resource policy check, if the header is set, the browser will deny <code>no-cors</code> requests issued from a different origin/site.</p>
+    Cross-Origin-Resource-Policy: same-site | same-origin | cross-origin
 
-<h2 id="Browser_compatibility">Browser compatibility</h2>
+During a cross-origin resource policy check, if the header is set, the browser will deny `no-cors` requests issued from a different origin/site.
 
-<p>{{Compat("http.headers.Cross-Origin-Resource-Policy")}}</p>
+## Browser compatibility
 
-<h2 id="Specifications">Specifications</h2>
+{{Compat("http.headers.Cross-Origin-Resource-Policy")}}
 
-<table class="standard-table">
- <tbody>
-  <tr>
-   <th scope="col">Specification</th>
-   <th scope="col">Status</th>
-   <th scope="col">Comment</th>
-  </tr>
-  <tr>
-   <td>{{SpecName("Fetch", '#cross-origin-resource-policy-header')}}</td>
-   <td>{{Spec2("Fetch", '#cross-origin-resource-policy-header')}}</td>
-   <td>Initial definition</td>
-  </tr>
- </tbody>
-</table>
+## Specifications
 
-<h2 id="See_also">See also</h2>
+| Specification                                                                    | Status                                                                       | Comment            |
+| -------------------------------------------------------------------------------- | ---------------------------------------------------------------------------- | ------------------ |
+| {{SpecName("Fetch", '#cross-origin-resource-policy-header')}} | {{Spec2("Fetch", '#cross-origin-resource-policy-header')}} | Initial definition |
 
-<ul>
- <li>{{HTTPHeader("Cross-Origin-Resource-Policy")}} HTTP Header</li>
-</ul>
+## See also
+
+- {{HTTPHeader("Cross-Origin-Resource-Policy")}} HTTP Header
diff --git a/files/en-us/web/http/csp/errors/cspviolation/index.md b/files/en-us/web/http/csp/errors/cspviolation/index.md
index 3cfbf8ef6ac0662..39915eeb5827720 100644
--- a/files/en-us/web/http/csp/errors/cspviolation/index.md
+++ b/files/en-us/web/http/csp/errors/cspviolation/index.md
@@ -16,50 +16,48 @@ tags:
   - Web security
   - message
 ---
-<p>{{HTTPSidebar}}</p>
-
-<p>The warning "Content Security Policy: The page's settings blocked the loading of a resource: xyz" occurs when the page's CSP configuration given by <code>xyz</code> prevents the resource from being loaded into the document's context.</p>
-
-<h2 id="Message">Message</h2>
-
-<h3>Firefox</h3>
-<p><code>Content Security Policy: The pages settings blocked the loading of a resource: <em>xyz</em></code></p>
-</p>with:</p>
-<dl>
- <dt><code>xyz</code></dt>
- <dd>The name of the CSP directive that blocked the resource. This may be expressed as either just the name of the directive, or as the entire policy directive string.</dd>
- <dt><code>uvw</code></dt>
- <dd>Text that provides information that may help you resolve the problem, potentially including specific changes you might make to the CSP configuration.</dd>
-</dl>
-
-<h3>Chrome</h3>
-<ul>
-   <li><code>Refused to apply inline style because it violates the following Content Security Policy Directive: "<em>xyz</em>". <em>uvw</em>.</code></li>
-   <li><code>Refused to execute inline script because it violates the following Content Security Policy directive: "<em>xyz</em>". <em>uvw</em>.</code></li>
-   <li><code>Refused to run the JavaScript URL because it violates the following Content Security Policy directive: "<em>xyz</em>". <em>uvw</em>.</code></li>
-   <li><code>Refused to execute inline event handler because it violates the following Content Security Policy directive: "<em>xyz</em>". <em>uvw</em>.</code></li>
-</ul>
-<p>with:</p>
-<dl>
- <dt><code>xyz</code></dt>
- <dd>The name of the CSP directive that blocked the resource. This may be expressed as either just the name of the directive, or as the entire policy directive string.</dd>
- <dt><code>uvw</code></dt>
- <dd>Text that provides information that may help you resolve the problem, potentially including specific changes you might make to the CSP configuration.</dd>
-</dl>
-
-<p><strong>&lt;&lt;&lt;--- The Chrome information above may be incomplete; we need to investigate that when we resume work on this content ---&gt;&gt;&gt;</strong></p>
-
-<h2 id="What_went_wrong">What went wrong?</h2>
-
-<p>This warning message means that due to the existence of a particular CSP directive, a resource wasn't loaded.</p>
-
-<p><strong>&lt;&lt;&lt;--- add details and suggested fixes ---&gt;&gt;&gt;</strong></p>
-
-<h2 id="See_also">See also</h2>
-
-<ul>
- <li><a href="/en-US/docs/Web/HTTP/CSP/Errors">CSP errors and warnings</a></li>
- <li><a href="/en-US/docs/Web/HTTP/CSP">Content Security Policy</a></li>
- <li>{{HTTPHeader("Content-Security-Policy")}}</li>
- <li>{{HTTPHeader("Content-Security-Policy-Report-Only")}}</li>
-</ul>
+{{HTTPSidebar}}
+
+The warning "Content Security Policy: The page's settings blocked the loading of a resource: xyz" occurs when the page's CSP configuration given by `xyz` prevents the resource from being loaded into the document's context.
+
+## Message
+
+### Firefox
+
+`Content Security Policy: The pages settings blocked the loading of a resource: xyz`
+
+with:
+
+- `xyz`
+  - : The name of the CSP directive that blocked the resource. This may be expressed as either just the name of the directive, or as the entire policy directive string.
+- `uvw`
+  - : Text that provides information that may help you resolve the problem, potentially including specific changes you might make to the CSP configuration.
+
+### Chrome
+
+- `Refused to apply inline style because it violates the following Content Security Policy Directive: "xyz". uvw.`
+- `Refused to execute inline script because it violates the following Content Security Policy directive: "xyz". uvw.`
+- `Refused to run the JavaScript URL because it violates the following Content Security Policy directive: "xyz". uvw.`
+- `Refused to execute inline event handler because it violates the following Content Security Policy directive: "xyz". uvw.`
+
+with:
+
+- `xyz`
+  - : The name of the CSP directive that blocked the resource. This may be expressed as either just the name of the directive, or as the entire policy directive string.
+- `uvw`
+  - : Text that provides information that may help you resolve the problem, potentially including specific changes you might make to the CSP configuration.
+
+**<<<--- The Chrome information above may be incomplete; we need to investigate that when we resume work on this content --->>>**
+
+## What went wrong?
+
+This warning message means that due to the existence of a particular CSP directive, a resource wasn't loaded.
+
+**<<<--- add details and suggested fixes --->>>**
+
+## See also
+
+- [CSP errors and warnings](/en-US/docs/Web/HTTP/CSP/Errors)
+- [Content Security Policy](/en-US/docs/Web/HTTP/CSP)
+- {{HTTPHeader("Content-Security-Policy")}}
+- {{HTTPHeader("Content-Security-Policy-Report-Only")}}
diff --git a/files/en-us/web/http/csp/errors/index.md b/files/en-us/web/http/csp/errors/index.md
index a49f840ec796118..b76396866b025fa 100644
--- a/files/en-us/web/http/csp/errors/index.md
+++ b/files/en-us/web/http/csp/errors/index.md
@@ -11,47 +11,45 @@ tags:
   - console
   - log
 ---
-<p>{{HTTPSidebar}}{{draft}}</p>
+{{HTTPSidebar}}{{draft}}
 
-<p>This page will be a parent for reference articles about CSP errors and warnings, and will provide an overview of them, and generic troubleshooting advice, if possible.</p>
+This page will be a parent for reference articles about CSP errors and warnings, and will provide an overview of them, and generic troubleshooting advice, if possible.
 
-<h2 id="The_errors">The errors</h2>
+## The errors
 
-<ul>
- <li><a href="/en-US/docs/Web/HTTP/CSP/Errors/CSPViolation">The page’s settings blocked the loading of a resource: %1$S</a></li>
- <li><a href="/en-US/docs/Web/HTTP/CSP/Errors/CSPViolationWithURI">The page’s settings blocked the loading of a resource at %2$S (“%1$S”).</a></li>
- <li><a href="/en-US/docs/Web/HTTP/CSP/Errors/CSPROViolation">A violation occurred for a report-only CSP policy (“%1$S”). The behavior was allowed, and a CSP report was sent.</a></li>
- <li><a href="/en-US/docs/Web/HTTP/CSP/Errors/CSPROViolationWithURI">The page’s settings observed the loading of a resource at %2$S (“%1$S”). A CSP report is being sent.</a></li>
- <li><a href="/en-US/docs/Web/HTTP/CSP/Errors/triedToSendReport">Tried to send report to invalid URI: “%1$S”</a></li>
- <li><a href="/en-US/docs/Web/HTTP/CSP/Errors/couldNotParseReportURI">couldn’t parse report URI: %1$S</a></li>
- <li><a href="/en-US/docs/Web/HTTP/CSP/Errors/couldNotProcessUnknownDirective">Couldn’t process unknown directive ‘%1$S’</a></li>
- <li><a href="/en-US/docs/Web/HTTP/CSP/Errors/ignoringUnknownOption">Ignoring unknown option %1$S</a></li>
- <li><a href="/en-US/docs/Web/HTTP/CSP/Errors/ignoringDuplicateSrc">Ignoring duplicate source %1$S</a></li>
- <li><a href="/en-US/docs/Web/HTTP/CSP/Errors/ignoringSrcFromMetaCSP">Ignoring source ‘%1$S’ (Not supported when delivered via meta element).</a></li>
- <li><a href="/en-US/docs/Web/HTTP/CSP/Errors/ignoringSrcWithinScriptStyleSrc">Ignoring “%1$S” within script-src or style-src: nonce-source or hash-source specified</a></li>
- <li><a href="/en-US/docs/Web/HTTP/CSP/Errors/ignoringSrcForStrictDynamic">Ignoring “%1$S” within script-src: ‘strict-dynamic’ specified</a></li>
- <li><a href="/en-US/docs/Web/HTTP/CSP/Errors/ignoringStrictDynamic">Ignoring source “%1$S” (Only supported within script-src).</a></li>
- <li><a href="/en-US/docs/Web/HTTP/CSP/Errors/strictDynamicButNoHashOrNonce">Keyword ‘strict-dynamic’ within “%1$S” with no valid nonce or hash might block all scripts from loading</a></li>
- <li><a href="/en-US/docs/Web/HTTP/CSP/Errors/reportURInotHttpsOrHttp2">The report URI (%1$S) should be an HTTP or HTTPS URI.</a></li>
- <li><a href="/en-US/docs/Web/HTTP/CSP/Errors/reportURInotInReportOnlyHeader">This site (%1$S) has a Report-Only policy without a report URI. CSP will not block and cannot report violations of this policy.</a></li>
- <li><a href="/en-US/docs/Web/HTTP/CSP/Errors/failedToParseUnrecognizedSource">Failed to parse unrecognized source %1$S</a></li>
- <li><a href="/en-US/docs/Web/HTTP/CSP/Errors/inlineScriptBlocked">An attempt to execute inline scripts has been blocked</a></li>
- <li><a href="/en-US/docs/Web/HTTP/CSP/Errors/inlineStyleBlocked">An attempt to apply inline style sheets has been blocked</a></li>
- <li><a href="/en-US/docs/Web/HTTP/CSP/Errors/scriptFromStringBlocked">An attempt to call JavaScript from a string (by calling a function like eval) has been blocked</a></li>
- <li><a href="/en-US/docs/Web/HTTP/CSP/Errors/upgradeInsecureRequest">Upgrading insecure request ‘%1$S’ to use ‘%2$S’</a></li>
- <li><a href="/en-US/docs/Web/HTTP/CSP/Errors/ignoreSrcForDirective">Ignoring srcs for directive ‘%1$S’</a></li>
- <li><a href="/en-US/docs/Web/HTTP/CSP/Errors/hostNameMightBeKeyword">Interpreting %1$S as a hostname, not a keyword. If you intended this to be a keyword, use ‘%2$S’ (wrapped in single quotes).</a></li>
- <li><a href="/en-US/docs/Web/HTTP/CSP/Errors/notSupportingDirective">Not supporting directive ‘%1$S’. Directive and values will be ignored.</a></li>
- <li><a href="/en-US/docs/Web/HTTP/CSP/Errors/blockAllMixedContent">Blocking insecure request ‘%1$S’.</a></li>
- <li><a href="/en-US/docs/Web/HTTP/CSP/Errors/ignoringDirectiveWithNoValues">Ignoring ‘%1$S’ since it does not contain any parameters.</a></li>
- <li><a href="/en-US/docs/Web/HTTP/CSP/Errors/ignoringReportOnlyDirective">Ignoring sandbox directive when delivered in a report-only policy ‘%1$S’</a></li>
- <li><a href="/en-US/docs/Web/HTTP/CSP/Errors/deprecatedReferrerDirective">Referrer Directive ‘%1$S’ has been deprecated. Please use the Referrer-Policy header instead.</a></li>
- <li><a href="/en-US/docs/Web/HTTP/CSP/Errors/IgnoringSrcBecauseOfDirective">Ignoring ‘%1$S’ because of ‘%2$S’ directive.</a></li>
- <li><a href="/en-US/docs/Web/HTTP/CSP/Errors/couldntParseInvalidSource">Couldn’t parse invalid source %1$S</a></li>
- <li><a href="/en-US/docs/Web/HTTP/CSP/Errors/couldntParseInvalidHost">Couldn’t parse invalid host %1$S</a></li>
- <li><a href="/en-US/docs/Web/HTTP/CSP/Errors/couldntParseScheme">Couldn’t parse scheme in %1$S</a></li>
- <li><a href="/en-US/docs/Web/HTTP/CSP/Errors/couldntParsePort">Couldn’t parse port in %1$S</a></li>
- <li><a href="/en-US/docs/Web/HTTP/CSP/Errors/duplicateDirective">Duplicate %1$S directives detected. All but the first instance will be ignored.</a></li>
- <li><a href="/en-US/docs/Web/HTTP/CSP/Errors/deprecatedChildSrcDirective">Directive ‘%1$S’ has been deprecated. Please use directive ‘worker-src’ to control workers, or directive ‘frame-src’ to control frames respectively.</a></li>
- <li><a href="/en-US/docs/Web/HTTP/CSP/Errors/couldntParseInvalidSandboxFlag">Couldn’t parse invalid sandbox flag ‘%1$S’</a></li>
-</ul>
+- [The page’s settings blocked the loading of a resource: %1$S](/en-US/docs/Web/HTTP/CSP/Errors/CSPViolation)
+- [The page’s settings blocked the loading of a resource at %2$S (“%1$S”).](/en-US/docs/Web/HTTP/CSP/Errors/CSPViolationWithURI)
+- [A violation occurred for a report-only CSP policy (“%1$S”). The behavior was allowed, and a CSP report was sent.](/en-US/docs/Web/HTTP/CSP/Errors/CSPROViolation)
+- [The page’s settings observed the loading of a resource at %2$S (“%1$S”). A CSP report is being sent.](/en-US/docs/Web/HTTP/CSP/Errors/CSPROViolationWithURI)
+- [Tried to send report to invalid URI: “%1$S”](/en-US/docs/Web/HTTP/CSP/Errors/triedToSendReport)
+- [couldn’t parse report URI: %1$S](/en-US/docs/Web/HTTP/CSP/Errors/couldNotParseReportURI)
+- [Couldn’t process unknown directive ‘%1$S’](/en-US/docs/Web/HTTP/CSP/Errors/couldNotProcessUnknownDirective)
+- [Ignoring unknown option %1$S](/en-US/docs/Web/HTTP/CSP/Errors/ignoringUnknownOption)
+- [Ignoring duplicate source %1$S](/en-US/docs/Web/HTTP/CSP/Errors/ignoringDuplicateSrc)
+- [Ignoring source ‘%1$S’ (Not supported when delivered via meta element).](/en-US/docs/Web/HTTP/CSP/Errors/ignoringSrcFromMetaCSP)
+- [Ignoring “%1$S” within script-src or style-src: nonce-source or hash-source specified](/en-US/docs/Web/HTTP/CSP/Errors/ignoringSrcWithinScriptStyleSrc)
+- [Ignoring “%1$S” within script-src: ‘strict-dynamic’ specified](/en-US/docs/Web/HTTP/CSP/Errors/ignoringSrcForStrictDynamic)
+- [Ignoring source “%1$S” (Only supported within script-src).](/en-US/docs/Web/HTTP/CSP/Errors/ignoringStrictDynamic)
+- [Keyword ‘strict-dynamic’ within “%1$S” with no valid nonce or hash might block all scripts from loading](/en-US/docs/Web/HTTP/CSP/Errors/strictDynamicButNoHashOrNonce)
+- [The report URI (%1$S) should be an HTTP or HTTPS URI.](/en-US/docs/Web/HTTP/CSP/Errors/reportURInotHttpsOrHttp2)
+- [This site (%1$S) has a Report-Only policy without a report URI. CSP will not block and cannot report violations of this policy.](/en-US/docs/Web/HTTP/CSP/Errors/reportURInotInReportOnlyHeader)
+- [Failed to parse unrecognized source %1$S](/en-US/docs/Web/HTTP/CSP/Errors/failedToParseUnrecognizedSource)
+- [An attempt to execute inline scripts has been blocked](/en-US/docs/Web/HTTP/CSP/Errors/inlineScriptBlocked)
+- [An attempt to apply inline style sheets has been blocked](/en-US/docs/Web/HTTP/CSP/Errors/inlineStyleBlocked)
+- [An attempt to call JavaScript from a string (by calling a function like eval) has been blocked](/en-US/docs/Web/HTTP/CSP/Errors/scriptFromStringBlocked)
+- [Upgrading insecure request ‘%1$S’ to use ‘%2$S’](/en-US/docs/Web/HTTP/CSP/Errors/upgradeInsecureRequest)
+- [Ignoring srcs for directive ‘%1$S’](/en-US/docs/Web/HTTP/CSP/Errors/ignoreSrcForDirective)
+- [Interpreting %1$S as a hostname, not a keyword. If you intended this to be a keyword, use ‘%2$S’ (wrapped in single quotes).](/en-US/docs/Web/HTTP/CSP/Errors/hostNameMightBeKeyword)
+- [Not supporting directive ‘%1$S’. Directive and values will be ignored.](/en-US/docs/Web/HTTP/CSP/Errors/notSupportingDirective)
+- [Blocking insecure request ‘%1$S’.](/en-US/docs/Web/HTTP/CSP/Errors/blockAllMixedContent)
+- [Ignoring ‘%1$S’ since it does not contain any parameters.](/en-US/docs/Web/HTTP/CSP/Errors/ignoringDirectiveWithNoValues)
+- [Ignoring sandbox directive when delivered in a report-only policy ‘%1$S’](/en-US/docs/Web/HTTP/CSP/Errors/ignoringReportOnlyDirective)
+- [Referrer Directive ‘%1$S’ has been deprecated. Please use the Referrer-Policy header instead.](/en-US/docs/Web/HTTP/CSP/Errors/deprecatedReferrerDirective)
+- [Ignoring ‘%1$S’ because of ‘%2$S’ directive.](/en-US/docs/Web/HTTP/CSP/Errors/IgnoringSrcBecauseOfDirective)
+- [Couldn’t parse invalid source %1$S](/en-US/docs/Web/HTTP/CSP/Errors/couldntParseInvalidSource)
+- [Couldn’t parse invalid host %1$S](/en-US/docs/Web/HTTP/CSP/Errors/couldntParseInvalidHost)
+- [Couldn’t parse scheme in %1$S](/en-US/docs/Web/HTTP/CSP/Errors/couldntParseScheme)
+- [Couldn’t parse port in %1$S](/en-US/docs/Web/HTTP/CSP/Errors/couldntParsePort)
+- [Duplicate %1$S directives detected. All but the first instance will be ignored.](/en-US/docs/Web/HTTP/CSP/Errors/duplicateDirective)
+- [Directive ‘%1$S’ has been deprecated. Please use directive ‘worker-src’ to control workers, or directive ‘frame-src’ to control frames respectively.](/en-US/docs/Web/HTTP/CSP/Errors/deprecatedChildSrcDirective)
+- [Couldn’t parse invalid sandbox flag ‘%1$S’](/en-US/docs/Web/HTTP/CSP/Errors/couldntParseInvalidSandboxFlag)
diff --git a/files/en-us/web/http/csp/index.md b/files/en-us/web/http/csp/index.md
index 24e4da047721cec..bd71a9859ddefb7 100644
--- a/files/en-us/web/http/csp/index.md
+++ b/files/en-us/web/http/csp/index.md
@@ -9,294 +9,295 @@ tags:
   - Security
   - access
 ---
-<div>{{HTTPSidebar}}</div>
-
-<p class="summary"><strong>Content Security Policy</strong> ({{Glossary("CSP")}}) is an
-  added layer of security that helps to detect and mitigate certain types of attacks,
-  including Cross Site Scripting ({{Glossary("Cross-site_scripting", "XSS")}}) and data injection attacks. These
-  attacks are used for everything from data theft to site defacement to distribution of
-  malware.</p>
+{{HTTPSidebar}}
+
+**Content Security Policy** ({{Glossary("CSP")}}) is an
+added layer of security that helps to detect and mitigate certain types of attacks,
+including Cross Site Scripting ({{Glossary("Cross-site_scripting", "XSS")}}) and data injection attacks. These
+attacks are used for everything from data theft to site defacement to distribution of
+malware.
+
+CSP is designed to be fully backward compatible (except CSP version 2 where there are
+some explicitly-mentioned inconsistencies in backward compatibility; more details [here](https://www.w3.org/TR/CSP2) section 1.1). Browsers that don't support
+it still work with servers that implement it, and vice-versa: browsers that don't
+support CSP ignore it, functioning as usual, defaulting to the standard same-origin
+policy for web content. If the site doesn't offer the CSP header, browsers likewise use
+the standard [same-origin
+policy](/en-US/docs/Web/Security/Same-origin_policy).
 
-<p>CSP is designed to be fully backward compatible (except CSP version 2 where there are
-  some explicitly-mentioned inconsistencies in backward compatibility; more details <a
-    href="https://www.w3.org/TR/CSP2">here</a> section 1.1). Browsers that don't support
-  it still work with servers that implement it, and vice-versa: browsers that don't
-  support CSP ignore it, functioning as usual, defaulting to the standard same-origin
-  policy for web content. If the site doesn't offer the CSP header, browsers likewise use
-  the standard <a href="/en-US/docs/Web/Security/Same-origin_policy">same-origin
-    policy</a>.</p>
+To enable CSP, you need to configure your web server to return the
+{{HTTPHeader("Content-Security-Policy")}} HTTP header. (Sometimes you may see mentions
+of the `X-Content-Security-Policy` header, but that's an older version and
+you don't need to specify it anymore.)
 
-<p>To enable CSP, you need to configure your web server to return the
-  {{HTTPHeader("Content-Security-Policy")}} HTTP header. (Sometimes you may see mentions
-  of the <code>X-Content-Security-Policy</code> header, but that's an older version and
-  you don't need to specify it anymore.)</p>
+Alternatively, the {{HTMLElement("meta")}} element can be used to configure a policy,
+for example:
+`<meta http-equiv="Content-Security-Policy" content="default-src 'self'; img-src https://*; child-src 'none';">`
 
-<p>Alternatively, the {{HTMLElement("meta")}} element can be used to configure a policy,
-  for example:
-  <code>&lt;meta http-equiv="Content-Security-Policy" content="default-src 'self'; img-src https://*; child-src 'none';"&gt;</code>
-</p>
+## Threats
 
-<h2 id="Threats">Threats</h2>
+### Mitigating cross site scripting
 
-<h3 id="Mitigating_cross_site_scripting">Mitigating cross site scripting</h3>
+A primary goal of CSP is to mitigate and report XSS attacks. XSS attacks exploit the
+browser's trust of the content received from the server. Malicious scripts are executed
+by the victim's browser because the browser trusts the source of the content, even when
+it's not coming from where it seems to be coming from.
 
-<p>A primary goal of CSP is to mitigate and report XSS attacks. XSS attacks exploit the
-  browser's trust of the content received from the server. Malicious scripts are executed
-  by the victim's browser because the browser trusts the source of the content, even when
-  it's not coming from where it seems to be coming from.</p>
+CSP makes it possible for server administrators to reduce or eliminate the vectors by
+which XSS can occur by specifying the domains that the browser should consider to be
+valid sources of executable scripts. A CSP compatible browser will then only execute
+scripts loaded in source files received from those allowlisted domains, ignoring all
+other script (including inline scripts and event-handling HTML attributes).
 
-<p>CSP makes it possible for server administrators to reduce or eliminate the vectors by
-  which XSS can occur by specifying the domains that the browser should consider to be
-  valid sources of executable scripts. A CSP compatible browser will then only execute
-  scripts loaded in source files received from those allowlisted domains, ignoring all
-  other script (including inline scripts and event-handling HTML attributes).</p>
+As an ultimate form of protection, sites that want to never allow scripts to be
+executed can opt to globally disallow script execution.
 
-<p>As an ultimate form of protection, sites that want to never allow scripts to be
-  executed can opt to globally disallow script execution.</p>
+### Mitigating packet sniffing attacks
 
-<h3 id="Mitigating_packet_sniffing_attacks">Mitigating packet sniffing attacks</h3>
+In addition to restricting the domains from which content can be loaded, the server can
+specify which protocols are allowed to be used; for example (and ideally, from a
+security standpoint), a server can specify that all content must be loaded using HTTPS.
+A complete data transmission security strategy includes not only enforcing HTTPS for
+data transfer, but also marking all [cookies with
+the `secure` attribute](/en-US/docs/Web/HTTP/Cookies) and providing automatic redirects from HTTP
+pages to their HTTPS counterparts. Sites may also use the
+{{HTTPHeader("Strict-Transport-Security")}} HTTP header to ensure that browsers connect
+to them only over an encrypted channel**.**
 
-<p>In addition to restricting the domains from which content can be loaded, the server can
-  specify which protocols are allowed to be used; for example (and ideally, from a
-  security standpoint), a server can specify that all content must be loaded using HTTPS.
-  A complete data transmission security strategy includes not only enforcing HTTPS for
-  data transfer, but also marking all <a href="/en-US/docs/Web/HTTP/Cookies">cookies with
-    the <code>secure</code> attribute</a> and providing automatic redirects from HTTP
-  pages to their HTTPS counterparts. Sites may also use the
-  {{HTTPHeader("Strict-Transport-Security")}} HTTP header to ensure that browsers connect
-  to them only over an encrypted channel<strong>.</strong></p>
+## Using CSP
 
-<h2 id="Using_CSP">Using CSP</h2>
+Configuring Content Security Policy involves adding the
+{{HTTPHeader("Content-Security-Policy")}} HTTP header to a web page and giving it values
+to control what resources the user agent is allowed to load for that page. For example,
+a page that uploads and displays images could allow images from anywhere, but restrict a
+form action to a specific endpoint. A properly designed Content Security Policy helps
+protect a page against a cross site scripting attack. This article explains how to
+construct such headers properly, and provides examples.
 
-<p>Configuring Content Security Policy involves adding the
-  {{HTTPHeader("Content-Security-Policy")}} HTTP header to a web page and giving it values
-  to control what resources the user agent is allowed to load for that page. For example,
-  a page that uploads and displays images could allow images from anywhere, but restrict a
-  form action to a specific endpoint. A properly designed Content Security Policy helps
-  protect a page against a cross site scripting attack. This article explains how to
-  construct such headers properly, and provides examples.</p>
+### Specifying your policy
 
-<h3 id="Specifying_your_policy">Specifying your policy</h3>
+You can use the {{HTTPHeader("Content-Security-Policy")}} HTTP header to specify your
+policy, like this:
 
-<p>You can use the {{HTTPHeader("Content-Security-Policy")}} HTTP header to specify your
-  policy, like this:</p>
+```html
+Content-Security-Policy: policy
+```
 
-<pre class="brush: html">Content-Security-Policy: <em>policy</em></pre>
+The policy is a string containing the policy directives describing your Content
+Security Policy.
 
-<p>The policy is a string containing the policy directives describing your Content
-  Security Policy.</p>
+### Writing a policy
 
-<h3 id="Writing_a_policy">Writing a policy</h3>
+A policy is described using a series of policy directives, each of which describes the
+policy for a certain resource type or policy area. Your policy should include a
+{{CSP("default-src")}} policy directive, which is a fallback for other resource types
+when they don't have policies of their own (for a complete list, see the description of
+the {{CSP("default-src")}} directive). A policy needs to include a
+{{CSP("default-src")}} or {{CSP("script-src")}} directive to prevent inline scripts from
+running, as well as blocking the use of `eval()`. A policy needs to include a
+{{CSP("default-src")}} or {{CSP("style-src")}} directive to restrict inline styles from
+being applied from a {{HTMLElement("style")}} element or a `style` attribute.
+There are specific directives for a wide variety of types of items, so that each type
+can have its own policy, including fonts, frames, images, audio and video media,
+scripts, and workers.
 
-<p>A policy is described using a series of policy directives, each of which describes the
-  policy for a certain resource type or policy area. Your policy should include a
-  {{CSP("default-src")}} policy directive, which is a fallback for other resource types
-  when they don't have policies of their own (for a complete list, see the description of
-  the {{CSP("default-src")}} directive). A policy needs to include a
-  {{CSP("default-src")}} or {{CSP("script-src")}} directive to prevent inline scripts from
-  running, as well as blocking the use of <code>eval()</code>. A policy needs to include a
-  {{CSP("default-src")}} or {{CSP("style-src")}} directive to restrict inline styles from
-  being applied from a {{HTMLElement("style")}} element or a <code>style</code> attribute.
-  There are specific directives for a wide variety of types of items, so that each type
-  can have its own policy, including fonts, frames, images, audio and video media,
-  scripts, and workers.</p>
+## Examples: Common use cases
 
-<h2 id="Examples_Common_use_cases">Examples: Common use cases</h2>
+This section provides examples of some common security policy scenarios.
 
-<p>This section provides examples of some common security policy scenarios.</p>
+### Example 1
 
-<h3 id="Example_1">Example 1</h3>
+A web site administrator wants all content to come from the site's own origin (this
+excludes subdomains.)
 
-<p>A web site administrator wants all content to come from the site's own origin (this
-  excludes subdomains.)</p>
+```html
+Content-Security-Policy: default-src 'self'
+```
 
-<pre class="brush: html">Content-Security-Policy: default-src 'self'</pre>
+### Example 2
 
-<h3 id="Example_2">Example 2</h3>
+A web site administrator wants to allow content from a trusted domain and all its
+subdomains (it doesn't have to be the same domain that the CSP is set on.)
 
-<p>A web site administrator wants to allow content from a trusted domain and all its
-  subdomains (it doesn't have to be the same domain that the CSP is set on.)</p>
+```html
+Content-Security-Policy: default-src 'self' trusted.com *.trusted.com
+```
 
-<pre
-  class="brush: html">Content-Security-Policy: default-src 'self' trusted.com *.trusted.com</pre>
+### Example 3
 
-<h3 id="Example_3">Example 3</h3>
+A web site administrator wants to allow users of a web application to include images
+from any origin in their own content, but to restrict audio or video media to trusted
+providers, and all scripts only to a specific server that hosts trusted code.
 
-<p>A web site administrator wants to allow users of a web application to include images
-  from any origin in their own content, but to restrict audio or video media to trusted
-  providers, and all scripts only to a specific server that hosts trusted code.</p>
+```html
+Content-Security-Policy: default-src 'self'; img-src *; media-src media1.com media2.com; script-src userscripts.example.com
+```
 
-<pre
-  class="brush: html">Content-Security-Policy: default-src 'self'; img-src *; media-src media1.com media2.com; script-src userscripts.example.com</pre>
+Here, by default, content is only permitted from the document's origin, with the
+following exceptions:
 
-<p>Here, by default, content is only permitted from the document's origin, with the
-  following exceptions:</p>
+- Images may load from anywhere (note the "\*" wildcard).
+- Media is only allowed from media1.com and media2.com (and not from subdomains of
+  those sites).
+- Executable script is only allowed from userscripts.example.com.
 
-<ul>
-  <li>Images may load from anywhere (note the "*" wildcard).</li>
-  <li>Media is only allowed from media1.com and media2.com (and not from subdomains of
-    those sites).</li>
-  <li>Executable script is only allowed from userscripts.example.com.</li>
-</ul>
+### Example 4
 
-<h3 id="Example_4">Example 4</h3>
+A web site administrator for an online banking site wants to ensure that all its
+content is loaded using TLS, in order to prevent attackers from eavesdropping on
+requests.
 
-<p>A web site administrator for an online banking site wants to ensure that all its
-  content is loaded using TLS, in order to prevent attackers from eavesdropping on
-  requests.</p>
+```html
+Content-Security-Policy: default-src https://onlinebanking.jumbobank.com
+```
 
-<pre
-  class="brush: html">Content-Security-Policy: default-src https://onlinebanking.jumbobank.com</pre>
+The server permits access only to documents being loaded specifically over HTTPS
+through the single origin onlinebanking.jumbobank.com.
 
-<p>The server permits access only to documents being loaded specifically over HTTPS
-  through the single origin onlinebanking.jumbobank.com.</p>
+### Example 5
 
-<h3 id="Example_5">Example 5</h3>
+A web site administrator of a web mail site wants to allow HTML in email, as well as
+images loaded from anywhere, but not JavaScript or other potentially dangerous content.
 
-<p>A web site administrator of a web mail site wants to allow HTML in email, as well as
-  images loaded from anywhere, but not JavaScript or other potentially dangerous content.
-</p>
+```html
+Content-Security-Policy: default-src 'self' *.mailsite.com; img-src *
+```
 
-<pre
-  class="brush: html">Content-Security-Policy: default-src 'self' *.mailsite.com; img-src *</pre>
+Note that this example doesn't specify a {{CSP("script-src")}}; with the example CSP,
+this site uses the setting specified by the {{CSP("default-src")}} directive, which
+means that scripts can be loaded only from the originating server.
 
-<p>Note that this example doesn't specify a {{CSP("script-src")}}; with the example CSP,
-  this site uses the setting specified by the {{CSP("default-src")}} directive, which
-  means that scripts can be loaded only from the originating server.</p>
+## Testing your policy
 
-<h2 id="Testing_your_policy">Testing your policy</h2>
+To ease deployment, CSP can be deployed in report-only mode. The policy is not
+enforced, but any violations are reported to a provided URI. Additionally, a report-only
+header can be used to test a future revision to a policy without actually deploying it.
 
-<p>To ease deployment, CSP can be deployed in report-only mode. The policy is not
-  enforced, but any violations are reported to a provided URI. Additionally, a report-only
-  header can be used to test a future revision to a policy without actually deploying it.
-</p>
+You can use the {{HTTPHeader("Content-Security-Policy-Report-Only")}} HTTP header to
+specify your policy, like this:
 
-<p>You can use the {{HTTPHeader("Content-Security-Policy-Report-Only")}} HTTP header to
-  specify your policy, like this:</p>
+```html
+Content-Security-Policy-Report-Only: policy 
+```
 
-<pre
-  class="brush: html">Content-Security-Policy-Report-Only: <em>policy</em> </pre>
+If both a {{HTTPHeader("Content-Security-Policy-Report-Only")}} header and a
+{{HTTPHeader("Content-Security-Policy")}} header are present in the same response, both
+policies are honored. The policy specified in `Content-Security-Policy`
+headers is enforced while the `Content-Security-Policy-Report-Only` policy
+generates reports but is not enforced.
 
-<p>If both a {{HTTPHeader("Content-Security-Policy-Report-Only")}} header and a
-  {{HTTPHeader("Content-Security-Policy")}} header are present in the same response, both
-  policies are honored. The policy specified in <code>Content-Security-Policy</code>
-  headers is enforced while the <code>Content-Security-Policy-Report-Only</code> policy
-  generates reports but is not enforced.</p>
+## Enabling reporting
 
-<h2 id="Enabling_reporting">Enabling reporting</h2>
+By default, violation reports aren't sent. To enable violation reporting, you need to
+specify the {{CSP("report-uri")}} policy directive, providing at least one URI to which
+to deliver the reports:
 
-<p>By default, violation reports aren't sent. To enable violation reporting, you need to
-  specify the {{CSP("report-uri")}} policy directive, providing at least one URI to which
-  to deliver the reports:</p>
+```html
+Content-Security-Policy: default-src 'self'; report-uri http://reportcollector.example.com/collector.cgi
+```
 
-<pre
-  class="brush: html">Content-Security-Policy: default-src 'self'; report-uri http://reportcollector.example.com/collector.cgi</pre>
+Then you need to set up your server to receive the reports; it can store or process
+them in whatever manner you determine is appropriate.
 
-<p>Then you need to set up your server to receive the reports; it can store or process
-  them in whatever manner you determine is appropriate.</p>
+## Violation report syntax
 
-<h2 id="Violation_report_syntax">Violation report syntax</h2>
+The report JSON object contains the following data:
 
-<p>The report JSON object contains the following data:</p>
-
-<dl>
-  <dt><code>blocked-uri</code></dt>
-  <dd>The URI of the resource that was blocked from loading by the Content Security
+- `blocked-uri`
+  - : The URI of the resource that was blocked from loading by the Content Security
     Policy. If the blocked URI is from a different origin than the
-    <code>document-uri</code>, then the blocked URI is truncated to contain just the
-    scheme, host, and port.</dd>
-  <dt><code>disposition</code></dt>
-  <dd>Either <code>"enforce"</code> or <code>"report"</code> depending on whether the
+    `document-uri`, then the blocked URI is truncated to contain just the
+    scheme, host, and port.
+- `disposition`
+  - : Either `"enforce"` or `"report"` depending on whether the
     {{HTTPHeader("Content-Security-Policy-Report-Only")}} header or the
-    <code>Content-Security-Policy</code> header is used.</dd>
-  <dt><code>document-uri</code></dt>
-  <dd>The URI of the document in which the violation occurred.</dd>
-  <dt><code>effective-directive</code></dt>
-  <dd>The directive whose enforcement caused the violation. Some browsers may provide different values, such as Chrome providing <code>style-src-elem</code>/<code>style-src-attr</code>, even when the actual enforced directive was <code>style-src</code>.</dd>
-  <dt><code>original-policy</code></dt>
-  <dd>The original policy as specified by the <code>Content-Security-Policy</code> HTTP
-    header.</dd>
-  <dt><code>referrer</code></dt>
-  <dd>The referrer of the document in which the violation occurred.</dd>
-  <dt><code>script-sample</code></dt>
-  <dd>The first 40 characters of the inline script, event handler, or style that caused
-    the violation. Only applicable to <code>script-src*</code> and <code>style-src*</code> violations, when they contain the <code>'report-sample'</code></dd>
-  <dt><code>status-code</code></dt>
-  <dd>The HTTP status code of the resource on which the global object was instantiated.
-  </dd>
-  <dt><code>violated-directive</code></dt>
-  <dd>The name of the policy section that was violated.</dd>
-</dl>
-
-<h2 id="Sample_violation_report">Sample violation report</h2>
-
-<p>Let's consider a page located at <code>http://example.com/signup.html</code>. It uses
-  the following policy, disallowing everything but stylesheets from
-  <code>cdn.example.com</code>.</p>
-
-<pre class="brush: html">Content-Security-Policy: default-src 'none'; style-src cdn.example.com; report-uri /_/csp-reports</pre>
-
-<p>The HTML of <code>signup.html</code> looks like this:</p>
-
-<pre class="brush: html">&lt;!DOCTYPE html&gt;
-&lt;html&gt;
-  &lt;head&gt;
-    &lt;title&gt;Sign Up&lt;/title&gt;
-    &lt;link rel="stylesheet" href="css/style.css"&gt;
-  &lt;/head&gt;
-  &lt;body&gt;
+    `Content-Security-Policy` header is used.
+- `document-uri`
+  - : The URI of the document in which the violation occurred.
+- `effective-directive`
+  - : The directive whose enforcement caused the violation. Some browsers may provide different values, such as Chrome providing `style-src-elem`/`style-src-attr`, even when the actual enforced directive was `style-src`.
+- `original-policy`
+  - : The original policy as specified by the `Content-Security-Policy` HTTP
+    header.
+- `referrer`
+  - : The referrer of the document in which the violation occurred.
+- `script-sample`
+  - : The first 40 characters of the inline script, event handler, or style that caused
+    the violation. Only applicable to `script-src*` and `style-src*` violations, when they contain the `'report-sample'`
+- `status-code`
+  - : The HTTP status code of the resource on which the global object was instantiated.
+- `violated-directive`
+  - : The name of the policy section that was violated.
+
+## Sample violation report
+
+Let's consider a page located at `http://example.com/signup.html`. It uses
+the following policy, disallowing everything but stylesheets from
+`cdn.example.com`.
+
+```html
+Content-Security-Policy: default-src 'none'; style-src cdn.example.com; report-uri /_/csp-reports
+```
+
+The HTML of `signup.html` looks like this:
+
+```html
+<!DOCTYPE html>
+<html>
+  <head>
+    <title>Sign Up</title>
+    <link rel="stylesheet" href="css/style.css">
+  </head>
+  <body>
     ... Content ...
-  &lt;/body&gt;
-&lt;/html&gt;</pre>
-
-<p>Can you spot the mistake? Stylesheets are allowed to be loaded only from
-  <code>cdn.example.com</code>, yet the website tries to load one from its own origin
-  (<code>http://example.com</code>). A browser capable of enforcing CSP would send the
-  following violation report as a POST request to
-  <code>http://example.com/_/csp-reports</code>, when the document is visited:</p>
-
-<pre>{
-  "csp-report": {
-    "document-uri": "http://example.com/signup.html",
-    "referrer": "",
-    "blocked-uri": "http://example.com/css/style.css",
-    "violated-directive": "style-src cdn.example.com",
-    "original-policy": "default-src 'none'; style-src cdn.example.com; report-uri /_/csp-reports"
-  }
-}</pre>
-
-<p>As you can see, the report includes the full path to the violating resource in
-  <code>blocked-uri</code>. This is not always the case. For example, if the
-  <code>signup.html</code> attempted to load CSS from
-  <code>http://anothercdn.example.com/stylesheet.css</code>, the browser would
-  <em>not</em> include the full path, but only the origin
-  (<code>http://anothercdn.example.com</code>). The CSP specification <a
-    href="https://www.w3.org/TR/CSP/#security-violation-reports">gives an explanation</a>
-  of this odd behavior. In summary, this is done to prevent leaking sensitive information
-  about cross-origin resources.</p>
-
-<h2 id="Browser_compatibility">Browser compatibility</h2>
-
-<p>{{Compat("http.headers.csp")}}</p>
-
-<p>A specific incompatibility exists in some versions of the Safari web browser, whereby
-  if a Content Security Policy header is set, but not a Same Origin header, the browser
-  will block self-hosted content and off-site content, and incorrectly report that this is
-  due to a the Content Security Policy not allowing the content.</p>
-
-<h2 id="See_also">See also</h2>
-
-<ul>
-  <li>{{HTTPHeader("Content-Security-Policy")}} HTTP Header</li>
-  <li>{{HTTPHeader("Content-Security-Policy-Report-Only")}} HTTP Header</li>
-  <li><a href="/en-US/docs/Mozilla/Add-ons/WebExtensions/Content_Security_Policy">Content
-      Security in WebExtensions</a></li>
-  <li><a href="/en-US/docs/Web/HTTP/Headers/Content-Security-Policy#csp_in_workers">CSP in
-      Web Workers</a></li>
-  <li><a href="/en-US/docs/Web/Privacy">Privacy, permissions, and information security</a>
-  </li>
-  <li><a href="https://github.com/google/csp-evaluator" >CSP Evaluator</a> - Evaluate your
-    Content Security Policy</li>
-  <li><a href="https://cspscanner.com/" >CSP Scanner</a> - Improve your
-    Content Security Policy</li>
-</ul>
+  </body>
+</html>
+```
+
+Can you spot the mistake? Stylesheets are allowed to be loaded only from
+`cdn.example.com`, yet the website tries to load one from its own origin
+(`http://example.com`). A browser capable of enforcing CSP would send the
+following violation report as a POST request to
+`http://example.com/_/csp-reports`, when the document is visited:
+
+    {
+      "csp-report": {
+        "document-uri": "http://example.com/signup.html",
+        "referrer": "",
+        "blocked-uri": "http://example.com/css/style.css",
+        "violated-directive": "style-src cdn.example.com",
+        "original-policy": "default-src 'none'; style-src cdn.example.com; report-uri /_/csp-reports"
+      }
+    }
+
+As you can see, the report includes the full path to the violating resource in
+`blocked-uri`. This is not always the case. For example, if the
+`signup.html` attempted to load CSS from
+`http://anothercdn.example.com/stylesheet.css`, the browser would
+_not_ include the full path, but only the origin
+(`http://anothercdn.example.com`). The CSP specification [gives an explanation](https://www.w3.org/TR/CSP/#security-violation-reports)
+of this odd behavior. In summary, this is done to prevent leaking sensitive information
+about cross-origin resources.
+
+## Browser compatibility
+
+{{Compat("http.headers.csp")}}
+
+A specific incompatibility exists in some versions of the Safari web browser, whereby
+if a Content Security Policy header is set, but not a Same Origin header, the browser
+will block self-hosted content and off-site content, and incorrectly report that this is
+due to a the Content Security Policy not allowing the content.
+
+## See also
+
+- {{HTTPHeader("Content-Security-Policy")}} HTTP Header
+- {{HTTPHeader("Content-Security-Policy-Report-Only")}} HTTP Header
+- [Content
+  Security in WebExtensions](/en-US/docs/Mozilla/Add-ons/WebExtensions/Content_Security_Policy)
+- [CSP in
+  Web Workers](/en-US/docs/Web/HTTP/Headers/Content-Security-Policy#csp_in_workers)
+- [Privacy, permissions, and information security](/en-US/docs/Web/Privacy)
+- [CSP Evaluator](https://github.com/google/csp-evaluator) - Evaluate your
+  Content Security Policy
+- [CSP Scanner](https://cspscanner.com/) - Improve your
+  Content Security Policy
diff --git a/files/en-us/web/http/feature_policy/index.md b/files/en-us/web/http/feature_policy/index.md
index 0e36eab5e4a7fad..036d3ea3debba2d 100644
--- a/files/en-us/web/http/feature_policy/index.md
+++ b/files/en-us/web/http/feature_policy/index.md
@@ -14,156 +14,127 @@ tags:
   - header
   - permission
 ---
-<div>{{HTTPSidebar}}</div>
+{{HTTPSidebar}}
 
-<p class="summary">Feature Policy allows web developers to selectively enable, disable, and modify the behavior of certain features and APIs in the browser. It is similar to {{Glossary("CSP", "Content Security Policy")}} but controls features instead of security behavior.</p>
+Feature Policy allows web developers to selectively enable, disable, and modify the behavior of certain features and APIs in the browser. It is similar to {{Glossary("CSP", "Content Security Policy")}} but controls features instead of security behavior.
 
-<div class="notecard warning">
-  <p><strong>Warning:</strong> The {{httpheader("Feature-Policy")}} header has now been renamed to <code>Permissions-Policy</code> in the spec, and this article will eventually be updated to reflect that change.</p>
-</div>
+> **Warning:** The {{httpheader("Feature-Policy")}} header has now been renamed to `Permissions-Policy` in the spec, and this article will eventually be updated to reflect that change.
 
-<h2 id="In_a_nutshell">In a nutshell</h2>
+## In a nutshell
 
-<p>Feature Policy provides a mechanism to explicitly declare what functionality is used (or not used), throughout your website. This allows you to lock in best practices, even as the codebase evolves over time — as well as to more safely compose third-party content — by limiting which features are available.</p>
+Feature Policy provides a mechanism to explicitly declare what functionality is used (or not used), throughout your website. This allows you to lock in best practices, even as the codebase evolves over time — as well as to more safely compose third-party content — by limiting which features are available.
 
-<p>With Feature Policy, you opt-in to a set of "policies" for the browser to enforce on specific features used throughout a website. These policies restrict what APIs the site can access or modify the browser's default behavior for certain features.</p>
+With Feature Policy, you opt-in to a set of "policies" for the browser to enforce on specific features used throughout a website. These policies restrict what APIs the site can access or modify the browser's default behavior for certain features.
 
-<p>Examples of what you can do with Feature Policy:</p>
+Examples of what you can do with Feature Policy:
 
-<ul>
- <li>Change the default behavior of autoplay on mobile and third party videos.</li>
- <li>Restrict a site from using sensitive APIs like camera or microphone.</li>
- <li>Allow iframes to use the <a href="/en-US/docs/Web/API/Fullscreen_API">fullscreen API</a>.</li>
- <li>Block the use of outdated APIs like <a href="/en-US/docs/Web/API/XMLHttpRequest/Using_XMLHttpRequest">synchronous XHR</a> and {{domxref("document.write()")}}.</li>
- <li>Ensure images are sized properly and are not too big for the viewport.</li>
-</ul>
+- Change the default behavior of autoplay on mobile and third party videos.
+- Restrict a site from using sensitive APIs like camera or microphone.
+- Allow iframes to use the [fullscreen API](/en-US/docs/Web/API/Fullscreen_API).
+- Block the use of outdated APIs like [synchronous XHR](/en-US/docs/Web/API/XMLHttpRequest/Using_XMLHttpRequest) and {{domxref("document.write()")}}.
+- Ensure images are sized properly and are not too big for the viewport.
 
-<h2 id="Concepts_and_usage">Concepts and usage</h2>
+## Concepts and usage
 
-<p>Feature Policy allows you to control which origins can use which features, both in the top-level page and in embedded frames. Essentially, you write a policy, which is an allowed list of origins for each feature. For every feature controlled by Feature Policy, the feature is only enabled in the current document or frame if its origin matches the allowed list of origins.</p>
+Feature Policy allows you to control which origins can use which features, both in the top-level page and in embedded frames. Essentially, you write a policy, which is an allowed list of origins for each feature. For every feature controlled by Feature Policy, the feature is only enabled in the current document or frame if its origin matches the allowed list of origins.
 
-<p>For each policy-controlled feature, the browser maintains a list of origins for which the feature is enabled, known as an allowlist. If you do not specify a policy for a feature, then a default allowlist will be used. The default allowlist is specific to each feature.</p>
+For each policy-controlled feature, the browser maintains a list of origins for which the feature is enabled, known as an allowlist. If you do not specify a policy for a feature, then a default allowlist will be used. The default allowlist is specific to each feature.
 
-<h3 id="Writing_a_policy">Writing a policy</h3>
+### Writing a policy
 
-<p>A policy is described using a set of individual policy directives. A policy directive is a combination of a defined feature name, and an allowlist of origins that can use the feature.</p>
+A policy is described using a set of individual policy directives. A policy directive is a combination of a defined feature name, and an allowlist of origins that can use the feature.
 
-<h3 id="Specifying_your_policy">Specifying your policy</h3>
+### Specifying your policy
 
-<p>Feature Policy provides two ways to specify policies to control features:</p>
+Feature Policy provides two ways to specify policies to control features:
 
-<ul>
- <li>The {{httpheader("Feature-Policy")}} HTTP header.</li>
- <li>The {{HTMLElement("iframe","<code>allow</code>","#Attributes")}} attribute on iframes.</li>
-</ul>
+- The {{httpheader("Feature-Policy")}} HTTP header.
+- The {{HTMLElement("iframe","<code>allow</code>","#Attributes")}} attribute on iframes.
 
-<p>The primary difference between the HTTP header and the <code>allow</code> attribute is that the allow attribute only controls features within an iframe. The header controls features in the response and any embedded content within the page.</p>
+The primary difference between the HTTP header and the `allow` attribute is that the allow attribute only controls features within an iframe. The header controls features in the response and any embedded content within the page.
 
-<p>For more details see <a href="/en-US/docs/Web/HTTP/Feature_Policy/Using_Feature_Policy">Using Feature Policy</a>.</p>
+For more details see [Using Feature Policy](/en-US/docs/Web/HTTP/Feature_Policy/Using_Feature_Policy).
 
-<h3 id="Inferring_the_policy">Inferring the policy</h3>
+### Inferring the policy
 
-<p>Scripts can programmatically query information about the feature policy via the {{DOMxRef("FeaturePolicy")}} object located at either {{DOMxRef("Document.featurePolicy")}} or {{DOMxRef("HTMLIFrameElement.featurePolicy")}}.</p>
+Scripts can programmatically query information about the feature policy via the {{DOMxRef("FeaturePolicy")}} object located at either {{DOMxRef("Document.featurePolicy")}} or {{DOMxRef("HTMLIFrameElement.featurePolicy")}}.
 
-<h2 id="Types_of_policy-controlled_features">Types of policy-controlled features</h2>
+## Types of policy-controlled features
 
-<p>Though Feature Policy provides control of multiple features using a consistent syntax, the behavior of policy controlled features varies and depends on several factors.</p>
+Though Feature Policy provides control of multiple features using a consistent syntax, the behavior of policy controlled features varies and depends on several factors.
 
-<p>The general principle is that there should be an intuitive or non-breaking way for web developers to detect or handle the case when the feature is disabled. Newly introduced features may have an explicit API to signal the state. Existing features that later integrate with Feature Policy will typically use existing mechanisms. Some approaches include:</p>
+The general principle is that there should be an intuitive or non-breaking way for web developers to detect or handle the case when the feature is disabled. Newly introduced features may have an explicit API to signal the state. Existing features that later integrate with Feature Policy will typically use existing mechanisms. Some approaches include:
 
-<ul>
- <li>Return "permission denied" for JavaScript APIs that require user permission grants.</li>
- <li>Return <code>false</code> or error from an existing JavaScript API that provides access to feature.</li>
- <li>Change the default values or options that control the feature behavior.</li>
-</ul>
+- Return "permission denied" for JavaScript APIs that require user permission grants.
+- Return `false` or error from an existing JavaScript API that provides access to feature.
+- Change the default values or options that control the feature behavior.
 
-<p>The current set of policy-controlled features fall into two broad categories:</p>
+The current set of policy-controlled features fall into two broad categories:
 
-<ul>
- <li>Enforcing best practices for good user experiences.</li>
- <li>Providing granular control over sensitive or powerful features.</li>
-</ul>
+- Enforcing best practices for good user experiences.
+- Providing granular control over sensitive or powerful features.
 
-<h3 id="Best_practices_for_good_user_experiences">Best practices for good user experiences</h3>
+### Best practices for good user experiences
 
-<p>There are several policy-controlled features to help enforce best practices for providing good performance and user experiences.</p>
+There are several policy-controlled features to help enforce best practices for providing good performance and user experiences.
 
-<p>In most cases, the policy-controlled features represent functionality that when used will negatively impact the user experience. To avoid breaking existing web content, the default for such policy-controlled features is to allow the functionality to be used by all origins. Best practices are then enforced by using policies that disable the policy-controlled features. For more details see "Enforcing best practices for good user experiences".</p>
+In most cases, the policy-controlled features represent functionality that when used will negatively impact the user experience. To avoid breaking existing web content, the default for such policy-controlled features is to allow the functionality to be used by all origins. Best practices are then enforced by using policies that disable the policy-controlled features. For more details see "Enforcing best practices for good user experiences".
 
-<p>The features include:</p>
+The features include:
 
-<ul>
- <li>Layout-inducing animations</li>
- <li>Legacy image formats</li>
- <li>Oversized images</li>
- <li>Synchronous scripts</li>
- <li>Synchronous XMLHTTPRequest</li>
- <li>Unoptimized images</li>
- <li>Unsized media</li>
-</ul>
+- Layout-inducing animations
+- Legacy image formats
+- Oversized images
+- Synchronous scripts
+- Synchronous XMLHTTPRequest
+- Unoptimized images
+- Unsized media
 
-<h3 id="Granular_control_over_certain_features">Granular control over certain features</h3>
+### Granular control over certain features
 
-<p>The web provides functionality and APIs that may have privacy or security risks if abused. In some cases, you may wish to strictly limit how such functionality is used on a website. There are policy-controlled features to allow functionality to be enabled/disabled for specific origins or frames within a website. Where available, the feature integrates with the Permissions API, or feature-specific mechanisms to check if the feature is available.</p>
+The web provides functionality and APIs that may have privacy or security risks if abused. In some cases, you may wish to strictly limit how such functionality is used on a website. There are policy-controlled features to allow functionality to be enabled/disabled for specific origins or frames within a website. Where available, the feature integrates with the Permissions API, or feature-specific mechanisms to check if the feature is available.
 
-<p>The features include (see <a href="/en-US/docs/Web/HTTP/Headers/Feature-Policy#directives">Features list</a>):</p>
+The features include (see [Features list](/en-US/docs/Web/HTTP/Headers/Feature-Policy#directives)):
 
-<ul>
- <li>Accelerometer</li>
- <li>Ambient light sensor</li>
- <li>Autoplay</li>
- <li>Camera</li>
- <li>Encrypted media</li>
- <li>Fullscreen</li>
- <li>Gamepad</li>
- <li>Geolocation</li>
- <li>Gyroscope</li>
- <li>Magnetometer</li>
- <li>Microphone</li>
- <li>Midi</li>
- <li>PaymentRequest</li>
- <li>Picture-in-picture</li>
- <li>USB</li>
- <li>Web Share API</li>
- <li>VR / XR</li>
-</ul>
+- Accelerometer
+- Ambient light sensor
+- Autoplay
+- Camera
+- Encrypted media
+- Fullscreen
+- Gamepad
+- Geolocation
+- Gyroscope
+- Magnetometer
+- Microphone
+- Midi
+- PaymentRequest
+- Picture-in-picture
+- USB
+- Web Share API
+- VR / XR
 
-<h2 id="Examples">Examples</h2>
+## Examples
 
-<ul>
- <li><a href="/en-US/docs/Web/HTTP/Feature_Policy/Using_Feature_Policy">Using Feature Policy</a></li>
- <li>See <a href="http://feature-policy-demos.appspot.com/">Feature Policy Demos</a> for example usage of many policies.</li>
-</ul>
+- [Using Feature Policy](/en-US/docs/Web/HTTP/Feature_Policy/Using_Feature_Policy)
+- See [Feature Policy Demos](http://feature-policy-demos.appspot.com/) for example usage of many policies.
 
-<h2 id="Specifications">Specifications</h2>
+## Specifications
 
-<table class="standard-table">
- <tbody>
-  <tr>
-   <th scope="col">Specification</th>
-   <th scope="col">Status</th>
-   <th scope="col">Comment</th>
-  </tr>
-  <tr>
-   <td>{{SpecName("Feature Policy","#feature-policy-http-header-field","Feature-Policy")}}</td>
-   <td>{{Spec2("Feature Policy")}}</td>
-   <td>Initial definition. Defines the {{httpheader("Feature-Policy")}} header. Directives are defined in the specs for the features they control. See individual directive pages for details.</td>
-  </tr>
- </tbody>
-</table>
-
-<h2 id="Browser_compatibility">Browser compatibility</h2>
-
-<p>{{Compat("http.headers.Feature-Policy")}}</p>
-
-<h2 id="See_also">See also</h2>
-
-<ul>
- <li><a href="/en-US/docs/Web/HTTP/Feature_Policy/Using_Feature_Policy">Using Feature Policy</a></li>
- <li>{{HTTPHeader("Feature-Policy")}} HTTP header</li>
- <li>{{HTMLElement("iframe","<code>allow</code>","#Attributes")}} attribute on iframes</li>
- <li><a href="https://developers.google.com/web/updates/2018/06/feature-policy">Introduction to Feature Policy</a></li>
- <li><a href="https://www.chromestatus.com/features#component%3A%20Blink%3EFeaturePolicy">Feature policies on www.chromestatus.com</a></li>
- <li><a href="https://chrome.google.com/webstore/detail/feature-policy-tester-dev/pchamnkhkeokbpahnocjaeednpbpacop">Feature-Policy Tester (Chrome Developer Tools extension)</a></li>
- <li><a href="/en-US/docs/Web/Privacy">Privacy, permissions, and information security</a></li>
-</ul>
+| Specification                                                                                                    | Status                               | Comment                                                                                                                                                                                             |
+| ---------------------------------------------------------------------------------------------------------------- | ------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| {{SpecName("Feature Policy","#feature-policy-http-header-field","Feature-Policy")}} | {{Spec2("Feature Policy")}} | Initial definition. Defines the {{httpheader("Feature-Policy")}} header. Directives are defined in the specs for the features they control. See individual directive pages for details. |
+
+## Browser compatibility
+
+{{Compat("http.headers.Feature-Policy")}}
+
+## See also
+
+- [Using Feature Policy](/en-US/docs/Web/HTTP/Feature_Policy/Using_Feature_Policy)
+- {{HTTPHeader("Feature-Policy")}} HTTP header
+- {{HTMLElement("iframe","<code>allow</code>","#Attributes")}} attribute on iframes
+- [Introduction to Feature Policy](https://developers.google.com/web/updates/2018/06/feature-policy)
+- [Feature policies on www.chromestatus.com](https://www.chromestatus.com/features#component%3A%20Blink%3EFeaturePolicy)
+- [Feature-Policy Tester (Chrome Developer Tools extension)](https://chrome.google.com/webstore/detail/feature-policy-tester-dev/pchamnkhkeokbpahnocjaeednpbpacop)
+- [Privacy, permissions, and information security](/en-US/docs/Web/Privacy)
diff --git a/files/en-us/web/http/feature_policy/using_feature_policy/index.md b/files/en-us/web/http/feature_policy/using_feature_policy/index.md
index 1a485e1a1f57846..beeb18982a0f51e 100644
--- a/files/en-us/web/http/feature_policy/using_feature_policy/index.md
+++ b/files/en-us/web/http/feature_policy/using_feature_policy/index.md
@@ -13,147 +13,149 @@ tags:
   - delegation
   - header
 ---
-<div>{{HTTPSidebar}}</div>
+{{HTTPSidebar}}
 
-<p><a href="/en-US/docs/Web/HTTP/Feature_Policy">Feature Policy</a> allows you to control which origins can use which features, both in the top-level page and in embedded frames. Essentially, you write a policy, which is an allowed list of origins for each feature. For every feature controlled by Feature Policy, the feature is only enabled in the current document or frame if its origin matches the allowed list of origins.</p>
+[Feature Policy](/en-US/docs/Web/HTTP/Feature_Policy) allows you to control which origins can use which features, both in the top-level page and in embedded frames. Essentially, you write a policy, which is an allowed list of origins for each feature. For every feature controlled by Feature Policy, the feature is only enabled in the current document or frame if its origin matches the allowed list of origins.
 
-<p>For each policy-controlled feature, the browser maintains a list of origins for which the feature is enabled, known as an allowlist. If you do not specify a policy for a feature, then a default allowlist will be used. The default allowlist is specific to each feature.</p>
+For each policy-controlled feature, the browser maintains a list of origins for which the feature is enabled, known as an allowlist. If you do not specify a policy for a feature, then a default allowlist will be used. The default allowlist is specific to each feature.
 
-<div class="notecard note">
-  <p><strong>Note:</strong> The <code>Feature-Policy</code> header has now been renamed to <code>Permissions-Policy</code> in the spec, and this article will eventually be updated to reflect that change.</p>
-</div>
+> **Note:** The `Feature-Policy` header has now been renamed to `Permissions-Policy` in the spec, and this article will eventually be updated to reflect that change.
 
-<h2 id="Writing_a_policy">Writing a policy</h2>
+## Writing a policy
 
-<p>A policy is described using a set of individual policy directives. A policy directive is a combination of a defined feature name, and an allowlist of origins that can use the feature. Features within a policy are separated by semicolons.</p>
+A policy is described using a set of individual policy directives. A policy directive is a combination of a defined feature name, and an allowlist of origins that can use the feature. Features within a policy are separated by semicolons.
 
-<h3 id="allowlist">allowlist</h3>
+### allowlist
 
-<p>An <code>allowlist</code> is a list of origins that takes one or more of the following values, separated by spaces:</p>
+An `allowlist` is a list of origins that takes one or more of the following values, separated by spaces:
 
-<ul>
- <li><code>*</code>: The feature will be allowed in this document, and all nested browsing contexts (iframes) regardless of their origin.</li>
- <li><code>'self'</code>: The feature will be allowed in this document, and in all nested browsing contexts (iframes) in the same origin.</li>
- <li><code>'src'</code>: (In an iframe <code>allow</code> attribute only) The feature will be allowed in this iframe, as long as the document loaded into it comes from the same origin as the URL in the iframe's {{HTMLElement('iframe','src','#Attributes')}} attribute.
-  <div class="notecard note">
-    <p><strong>Note:</strong> The <code>'src'</code> origin is used in the iframe <code>allow</code> attribute only, and is the <em>default</em> <code>allowlist</code> value.</p>
-  </div>
- </li>
- <li><code>'none'</code>: The feature is disabled in top-level and nested browsing contexts.</li>
- <li>&lt;origin(s)&gt;: The feature is allowed for specific origins (for example, https://example.com). Origins should be separated by a space.</li>
-</ul>
+- `*`: The feature will be allowed in this document, and all nested browsing contexts (iframes) regardless of their origin.
+- `'self'`: The feature will be allowed in this document, and in all nested browsing contexts (iframes) in the same origin.
+- `'src'`: (In an iframe `allow` attribute only) The feature will be allowed in this iframe, as long as the document loaded into it comes from the same origin as the URL in the iframe's {{HTMLElement('iframe','src','#Attributes')}} attribute.
 
-<p>The values <code>*</code> (enable for all origins) or <code>'none'</code> (disable for all origins) may only be used alone, while <code>'self'</code> and <code>'src'</code> may be used with one or more origins.</p>
+  > **Note:** The `'src'` origin is used in the iframe `allow` attribute only, and is the _default_ `allowlist` value.
 
-<p>Features are each defined to have a default allowlist, which is one of:</p>
+- `'none'`: The feature is disabled in top-level and nested browsing contexts.
+- \<origin(s)>: The feature is allowed for specific origins (for example, https\://example.com). Origins should be separated by a space.
 
-<ul>
- <li><code>*</code>: The feature is allowed by default in top-level browsing contexts and all nested browsing contexts (iframes).</li>
- <li><code>'self'</code>: The feature is allowed by default in top-level browsing contexts and in nested browsing contexts (iframes) in the same origin. The feature is not allowed in cross-origin documents in nested browsing contexts.</li>
- <li><code>'none'</code>: The feature is disabled in top-level and nested browsing contexts.</li>
-</ul>
+The values `*` (enable for all origins) or `'none'` (disable for all origins) may only be used alone, while `'self'` and `'src'` may be used with one or more origins.
 
-<h2 id="Specifying_your_policy">Specifying your policy</h2>
+Features are each defined to have a default allowlist, which is one of:
 
-<p>Feature Policy provides two ways to specify policies to control features:</p>
+- `*`: The feature is allowed by default in top-level browsing contexts and all nested browsing contexts (iframes).
+- `'self'`: The feature is allowed by default in top-level browsing contexts and in nested browsing contexts (iframes) in the same origin. The feature is not allowed in cross-origin documents in nested browsing contexts.
+- `'none'`: The feature is disabled in top-level and nested browsing contexts.
 
-<ul>
- <li>The {{httpheader('Feature-Policy')}} HTTP header.</li>
- <li>The {{htmlattrxref("allow", "iframe")}} attribute on {{htmlelement("iframe")}}s.</li>
-</ul>
+## Specifying your policy
 
-<p>The primary difference between the HTTP header and the <code>allow</code> attribute is that the allow attribute only controls features within an iframe. The header controls features in the response and any embedded content within the page.</p>
+Feature Policy provides two ways to specify policies to control features:
 
-<h3 id="The_Feature-Policy_HTTP_header">The Feature-Policy HTTP header</h3>
+- The {{httpheader('Feature-Policy')}} HTTP header.
+- The {{htmlattrxref("allow", "iframe")}} attribute on {{htmlelement("iframe")}}s.
 
-<p>You can send the <code>Feature-Policy</code> HTTP header with the response of a page. The value of this header is a policy to be enforced by the browser for the given page. It has the following structure.</p>
+The primary difference between the HTTP header and the `allow` attribute is that the allow attribute only controls features within an iframe. The header controls features in the response and any embedded content within the page.
 
-<pre class="brush: bash">Feature-Policy: &lt;feature name&gt; &lt;allowlist of origin(s)&gt;</pre>
+### The Feature-Policy HTTP header
 
-<p>For example, to block all content from using the Geolocation API across your site:</p>
+You can send the `Feature-Policy` HTTP header with the response of a page. The value of this header is a policy to be enforced by the browser for the given page. It has the following structure.
 
-<pre class="brush: bash">Feature-Policy: geolocation 'none'</pre>
+```bash
+Feature-Policy: <feature name> <allowlist of origin(s)>
+```
 
-<p>Several features can be controlled at the same time by sending the HTTP header with a semicolon-separated list of policy directives, or by sending a separate header for each policy.</p>
+For example, to block all content from using the Geolocation API across your site:
 
-<p>For example, the following are equivalent:</p>
+```bash
+Feature-Policy: geolocation 'none'
+```
 
-<pre class="brush: bash">Feature-Policy: unsized-media 'none'; geolocation 'self' https://example.com; camera *;
+Several features can be controlled at the same time by sending the HTTP header with a semicolon-separated list of policy directives, or by sending a separate header for each policy.
+
+For example, the following are equivalent:
+
+```bash
+Feature-Policy: unsized-media 'none'; geolocation 'self' https://example.com; camera *;
 
 Feature-Policy: unsized-media 'none'
 Feature-Policy: geolocation 'self' https://example.com
 Feature-Policy: camera *;
-</pre>
+```
 
-<h3 id="The_iframe_allow_attribute">The iframe allow attribute</h3>
+### The iframe allow attribute
 
-<p>The second way to use Feature Policy is for controlling content within an iframe. Use the <code>allow</code> attribute to specify a policy list for embedded content.</p>
+The second way to use Feature Policy is for controlling content within an iframe. Use the `allow` attribute to specify a policy list for embedded content.
 
-<p>For example, allow all browsing contexts within this iframe to use fullscreen:</p>
+For example, allow all browsing contexts within this iframe to use fullscreen:
 
-<pre class="brush: html">&lt;iframe src="https://example.com..." allow="fullscreen"&gt;&lt;/iframe&gt;</pre>
+```html
+<iframe src="https://example.com..." allow="fullscreen"></iframe>
+```
 
-<p>The default <code>&lt;iframe&gt;</code> <a href="#allowlist">allowlist</a> value is <code>'src'</code>, so this is equivalent to:</p>
+The default `<iframe>` [allowlist](#allowlist) value is `'src'`, so this is equivalent to:
 
-<pre class="brush: html">&lt;iframe src="https://example.com..." allow="fullscreen 'src'"&gt;&lt;/iframe&gt;</pre>
+```html
+<iframe src="https://example.com..." allow="fullscreen 'src'"></iframe>
+```
 
-<p>This example allows <code>&lt;iframe&gt;</code> content on a particular origin to access the user's location:</p>
+This example allows `<iframe>` content on a particular origin to access the user's location:
 
-<pre class="brush: html">&lt;iframe src="https://google-developers.appspot.com/demos/..."
-        allow="geolocation https://google-developers.appspot.com"&gt;&lt;/iframe&gt;
-</pre>
+```html
+<iframe src="https://google-developers.appspot.com/demos/..."
+        allow="geolocation https://google-developers.appspot.com"></iframe>
+```
 
-<p>Similar to the HTTP header, several features can be controlled at the same time by specifying a semicolon-separated list of policy directives.</p>
+Similar to the HTTP header, several features can be controlled at the same time by specifying a semicolon-separated list of policy directives.
 
-<p>For example, this blocks the <code>&lt;iframe&gt;</code> from using the camera and microphone:</p>
+For example, this blocks the `<iframe>` from using the camera and microphone:
 
-<pre class="brush: html">&lt;iframe allow="camera 'none'; microphone 'none'"&gt;
-</pre>
+```html
+<iframe allow="camera 'none'; microphone 'none'">
+```
 
-<h2 id="Inheritance_of_policy_for_embedded_content">Inheritance of policy for embedded content</h2>
+## Inheritance of policy for embedded content
 
-<p>Scripts inherit the policy of their browsing context, regardless of their origin. That means that top-level scripts inherit the policy from the main document.</p>
+Scripts inherit the policy of their browsing context, regardless of their origin. That means that top-level scripts inherit the policy from the main document.
 
-<p>All iframes inherit the policy of their parent page. If the iframe has an <code>allow</code> attribute, the policies of the parent page and the <code>allow</code> attribute are combined, using the most restrictive subset. For an iframe to have a feature enabled, the origin must be in the allowlist for both the parent page and the allow attribute.</p>
+All iframes inherit the policy of their parent page. If the iframe has an `allow` attribute, the policies of the parent page and the `allow` attribute are combined, using the most restrictive subset. For an iframe to have a feature enabled, the origin must be in the allowlist for both the parent page and the allow attribute.
 
-<p>Disabling a feature in a policy is a one-way toggle. If a feature has been disabled for a child frame by its parent frame, the child cannot re-enable it, and neither can any of the child's descendants.</p>
+Disabling a feature in a policy is a one-way toggle. If a feature has been disabled for a child frame by its parent frame, the child cannot re-enable it, and neither can any of the child's descendants.
 
-<h2 id="Enforcing_best_practices_for_good_user_experiences">Enforcing best practices for good user experiences</h2>
+## Enforcing best practices for good user experiences
 
-<p>It's difficult to build a website that uses all the latest best practices and provides great performance and user experiences. As the website evolves, it can become even harder to maintain the user experience over time. You can use feature policies to specify the desired best practices, and rely on the browser to enforce the policies to prevent regressions.</p>
+It's difficult to build a website that uses all the latest best practices and provides great performance and user experiences. As the website evolves, it can become even harder to maintain the user experience over time. You can use feature policies to specify the desired best practices, and rely on the browser to enforce the policies to prevent regressions.
 
-<p>There are several policy-controlled features designed to represent functionality that can negatively impact the user experience. These features include:</p>
+There are several policy-controlled features designed to represent functionality that can negatively impact the user experience. These features include:
 
-<ul>
- <li>Layout-inducing Animations</li>
- <li>Unoptimized (poorly compressed) images</li>
- <li>Oversized images</li>
- <li>Synchronous scripts</li>
- <li>Synchronous XMLHttpRequest</li>
- <li>Unsized media</li>
-</ul>
+- Layout-inducing Animations
+- Unoptimized (poorly compressed) images
+- Oversized images
+- Synchronous scripts
+- Synchronous XMLHttpRequest
+- Unsized media
 
-<p>To avoid breaking existing web content, the default for such policy-controlled features is to allow the functionality to be used by all origins. That is, the default allowlist is <code>'*'</code> for each feature. Preventing the use of the sub-optimal functionality requires explicitly specifying a policy that disables the features.</p>
+To avoid breaking existing web content, the default for such policy-controlled features is to allow the functionality to be used by all origins. That is, the default allowlist is `'*'` for each feature. Preventing the use of the sub-optimal functionality requires explicitly specifying a policy that disables the features.
 
-<p>For new content, you can start developing with a policy that disables all the features. This approach ensures that none of the functionality is introduced. When applying a policy to existing content, testing is likely required to verify it continues to work as expected. This is especially important for embedded or third-party content that you do not control.</p>
+For new content, you can start developing with a policy that disables all the features. This approach ensures that none of the functionality is introduced. When applying a policy to existing content, testing is likely required to verify it continues to work as expected. This is especially important for embedded or third-party content that you do not control.
 
-<p>To turn on the enforcement of all the best practices, specify the policy as below.</p>
+To turn on the enforcement of all the best practices, specify the policy as below.
 
-<p>Send the following the HTTP header:</p>
+Send the following the HTTP header:
 
-<pre class="brush: bash">Feature-Policy: layout-animations 'none'; unoptimized-images 'none'; oversized-images 'none'; sync-script 'none'; sync-xhr 'none'; unsized-media 'none';</pre>
+```bash
+Feature-Policy: layout-animations 'none'; unoptimized-images 'none'; oversized-images 'none'; sync-script 'none'; sync-xhr 'none'; unsized-media 'none';
+```
 
-<p>Using the <code>&lt;iframe&gt;</code> <code>allow</code> attribute:</p>
+Using the `<iframe>` `allow` attribute:
 
-<pre class="brush: html">&lt;iframe src="https://example.com..." allow="layout-animations 'none'; unoptimized-images 'none'; oversized-images 'none'; sync-script 'none'; sync-xhr 'none'; unsized-media 'none';"&gt;&lt;/iframe&gt;</pre>
+```html
+<iframe src="https://example.com..." allow="layout-animations 'none'; unoptimized-images 'none'; oversized-images 'none'; sync-script 'none'; sync-xhr 'none'; unsized-media 'none';"></iframe>
+```
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
- <li><a href="/en-US/docs/Web/HTTP/Feature_Policy">Feature Policy</a></li>
- <li>{{HTTPHeader("Feature-Policy")}} header</li>
- <li>{{HTMLElement('iframe','allow','#Attributes')}} attribute on iframes</li>
- <li>{{HTTPHeader("Content-Security-Policy")}} header</li>
- <li>{{HTTPHeader("Referrer-Policy")}} header</li>
- <li><a href="/en-US/docs/Web/Privacy">Privacy, permissions, and information security</a></li>
-</ul>
+- [Feature Policy](/en-US/docs/Web/HTTP/Feature_Policy)
+- {{HTTPHeader("Feature-Policy")}} header
+- {{HTMLElement('iframe','allow','#Attributes')}} attribute on iframes
+- {{HTTPHeader("Content-Security-Policy")}} header
+- {{HTTPHeader("Referrer-Policy")}} header
+- [Privacy, permissions, and information security](/en-US/docs/Web/Privacy)
diff --git a/files/en-us/web/http/headers/accept-ch-lifetime/index.md b/files/en-us/web/http/headers/accept-ch-lifetime/index.md
index d9118d45bc926f9..82eb46c587d33d0 100644
--- a/files/en-us/web/http/headers/accept-ch-lifetime/index.md
+++ b/files/en-us/web/http/headers/accept-ch-lifetime/index.md
@@ -12,56 +12,53 @@ tags:
   - Experimental
 browser-compat: http.headers.Accept-CH-Lifetime
 ---
-<div>{{HTTPSidebar}}{{securecontext_header}}{{Deprecated_header}}</div>
-<div class="notecard warning">
-  <p><strong>Warning:</strong> The header was removed from the specification in <a href="https://datatracker.ietf.org/doc/html/draft-ietf-httpbis-client-hints-08">draft 8</a>.</p>
-</div>
+{{HTTPSidebar}}{{securecontext_header}}{{Deprecated_header}}
 
-<p>The <code><strong>Accept-CH-Lifetime</strong></code> header is set by the server to
-  specify the persistence of the <a href="/en-US/docs/Glossary/Client_hints">client hint headers</a> it specified using {{HTTPHeader("Accept-CH")}}, that the client should
-  include in subsequent requests.</p>
+> **Warning:** The header was removed from the specification in [draft 8](https://datatracker.ietf.org/doc/html/draft-ietf-httpbis-client-hints-08).
+
+The **`Accept-CH-Lifetime`** header is set by the server to
+specify the persistence of the [client hint headers](/en-US/docs/Glossary/Client_hints) it specified using {{HTTPHeader("Accept-CH")}}, that the client should
+include in subsequent requests.
 
 <table class="properties">
   <tbody>
-   <tr>
-    <th scope="row">Header type</th>
-    <td>{{Glossary("Response header")}}</td>
-   </tr>
-   <tr>
-    <th scope="row">{{Glossary("Forbidden header name")}}</th>
-    <td>no</td>
-   </tr>
-   <tr>
-    <th scope="row">{{Glossary("CORS-safelisted response header")}}</th>
-    <td>no</td>
-   </tr>
+    <tr>
+      <th scope="row">Header type</th>
+      <td>{{Glossary("Response header")}}</td>
+    </tr>
+    <tr>
+      <th scope="row">{{Glossary("Forbidden header name")}}</th>
+      <td>no</td>
+    </tr>
+    <tr>
+      <th scope="row">
+        {{Glossary("CORS-safelisted response header")}}
+      </th>
+      <td>no</td>
+    </tr>
   </tbody>
- </table>
+</table>
 
-<div class="notecard note">
-  <p><strong>Note:</strong> Client Hints are accessible only on secure origins (via TLS).
-    {{HTTPHeader("Accept-CH")}} and {{HTTPHeader("Accept-CH-Lifetime")}} headers should be persisted for all secure requests
-    to ensure Client Hints are sent reliably.</p>
-</div>
+> **Note:** Client Hints are accessible only on secure origins (via TLS).
+> {{HTTPHeader("Accept-CH")}} and {{HTTPHeader("Accept-CH-Lifetime")}} headers should be persisted for all secure requests
+> to ensure Client Hints are sent reliably.
 
-<h2 id="Syntax">Syntax</h2>
+## Syntax
 
-<pre class="brush: html">Accept-CH-Lifetime: &lt;age&gt;
-</pre>
+```html
+Accept-CH-Lifetime: <age>
+```
 
-<h2 id="Examples">Examples</h2>
+## Examples
 
-<pre>Accept-CH: Viewport-Width
-Accept-CH-Lifetime: 86400
-</pre>
+    Accept-CH: Viewport-Width
+    Accept-CH-Lifetime: 86400
 
-<h2 id="Browser_compatibility">Browser compatibility</h2>
+## Browser compatibility
 
-<p>{{Compat}}</p>
+{{Compat}}
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
-  <li>{{HTTPHeader("Accept-CH")}}</li>
-  <li>{{HTTPHeader("Vary")}}</li>
-</ul>
+- {{HTTPHeader("Accept-CH")}}
+- {{HTTPHeader("Vary")}}
diff --git a/files/en-us/web/http/headers/accept-ch/index.md b/files/en-us/web/http/headers/accept-ch/index.md
index b777e5b6a7f0989..227f5e602b43f5c 100644
--- a/files/en-us/web/http/headers/accept-ch/index.md
+++ b/files/en-us/web/http/headers/accept-ch/index.md
@@ -9,11 +9,11 @@ tags:
   - Response header
 browser-compat: http.headers.Accept-CH
 ---
-<div>{{HTTPSidebar}}{{securecontext_header}}{{SeeCompatTable}}</div>
+{{HTTPSidebar}}{{securecontext_header}}{{SeeCompatTable}}
 
-<p>The <code><strong>Accept-CH</strong></code> header may be set by a server to specify
-  which <a href="/en-US/docs/Glossary/Client_hints">client hints</a> headers a client
-  should include in subsequent requests.</p>
+The **`Accept-CH`** header may be set by a server to specify
+which [client hints](/en-US/docs/Glossary/Client_hints) headers a client
+should include in subsequent requests.
 
 <table class="properties">
   <tbody>
@@ -26,45 +26,38 @@ browser-compat: http.headers.Accept-CH
       <td>no</td>
     </tr>
     <tr>
-      <th scope="row">{{Glossary("CORS-safelisted response header")}}</th>
+      <th scope="row">
+        {{Glossary("CORS-safelisted response header")}}
+      </th>
       <td>no</td>
-     </tr>
+    </tr>
   </tbody>
 </table>
 
-<div class="notecard note">
-  <p><strong>Note:</strong> Client hints are accessible only on secure origins (via TLS).
-    <code>Accept-CH</code> (and <code>Accept-CH-Lifetime</code>) headers should be persisted for all secure requests
-    to ensure client hints are sent reliably.</p>
-</div>
+> **Note:** Client hints are accessible only on secure origins (via TLS).
+> `Accept-CH` (and `Accept-CH-Lifetime`) headers should be persisted for all secure requests
+> to ensure client hints are sent reliably.
 
-<h2 id="Syntax">Syntax</h2>
+## Syntax
 
-<pre>Accept-CH: &lt;list of client hints&gt;
-</pre>
+    Accept-CH: <list of client hints>
 
-<h2 id="Examples">Examples</h2>
+## Examples
 
-<pre>Accept-CH: Viewport-Width, Width
-Vary: Viewport-Width, Width
-</pre>
+    Accept-CH: Viewport-Width, Width
+    Vary: Viewport-Width, Width
 
-<div class="notecard note">
-  <p><strong>Note:</strong> Remember to <a
-      href="/en-US/docs/Glossary/Client_hints#varying_client_hints">vary the response</a>
-    based on the accepted client hints.</p>
-</div>
+> **Note:** Remember to [vary the response](/en-US/docs/Glossary/Client_hints#varying_client_hints)
+> based on the accepted client hints.
 
-<h2 id="Specifications">Specifications</h2>
+## Specifications
 
 {{Specifications}}
 
-<h2 id="Browser_compatibility">Browser compatibility</h2>
+## Browser compatibility
 
-<p>{{Compat}}</p>
+{{Compat}}
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
-  <li>{{HTTPHeader("Vary")}}</li>
-</ul>
+- {{HTTPHeader("Vary")}}
diff --git a/files/en-us/web/http/headers/accept-charset/index.md b/files/en-us/web/http/headers/accept-charset/index.md
index b94be9a764d2c84..199f5d8b04fee7c 100644
--- a/files/en-us/web/http/headers/accept-charset/index.md
+++ b/files/en-us/web/http/headers/accept-charset/index.md
@@ -10,34 +10,30 @@ tags:
 ---
 {{HTTPSidebar}}
 
-<div class="notecard warning">
-  <p><strong>Warning:</strong> Do not use this header. Browsers omit this header and servers should ignore it.</p>
-</div>
+> **Warning:** Do not use this header. Browsers omit this header and servers should ignore it.
 
-<p>The <strong><code>Accept-Charset</code></strong> request HTTP header was a header that advertised a client's supported {{glossary("character encoding", "character encodings")}}. It is no longer widely used.</p>
+The **`Accept-Charset`** request HTTP header was a header that advertised a client's supported {{glossary("character encoding", "character encodings")}}. It is no longer widely used.
 
-<p>UTF-8 is well-supported and the overwhelmingly preferred choice for character encoding. To <a href="https://www.eff.org/deeplinks/2010/01/primer-information-theory-and-privacy">guarantee better privacy through less configuration-based entropy</a>, all browsers omit the <code>Accept-Charset</code> header. Chrome, Firefox, Internet Explorer, Opera, and Safari abandoned this header.</p>
+UTF-8 is well-supported and the overwhelmingly preferred choice for character encoding. To [guarantee better privacy through less configuration-based entropy](https://www.eff.org/deeplinks/2010/01/primer-information-theory-and-privacy), all browsers omit the `Accept-Charset` header. Chrome, Firefox, Internet Explorer, Opera, and Safari abandoned this header.
 
-<p>Today, <code>Accept-Charset</code> is most notable for being one of several <a href="/en-US/docs/Glossary/Forbidden_header_name">forbidden header names</a>.</p>
+Today, `Accept-Charset` is most notable for being one of several [forbidden header names](/en-US/docs/Glossary/Forbidden_header_name).
 
 <table class="properties">
- <tbody>
-  <tr>
-   <th scope="row">Header type</th>
-   <td>{{Glossary("Request header")}}</td>
-  </tr>
-  <tr>
-   <th scope="row">{{Glossary("Forbidden header name")}}</th>
-   <td>yes</td>
-  </tr>
- </tbody>
+  <tbody>
+    <tr>
+      <th scope="row">Header type</th>
+      <td>{{Glossary("Request header")}}</td>
+    </tr>
+    <tr>
+      <th scope="row">{{Glossary("Forbidden header name")}}</th>
+      <td>yes</td>
+    </tr>
+  </tbody>
 </table>
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
- <li>HTTP <a href="/en-US/docs/Web/HTTP/Content_negotiation">content negotiation</a></li>
- <li><a href="https://hsivonen.fi/accept-charset/">Accept-Charset is no more</a></li>
- <li>Header with the result of the content negotiation: {{HTTPHeader("Content-Type")}}</li>
- <li>Other similar headers: {{HTTPHeader("TE")}}, {{HTTPHeader("Accept-Encoding")}}, {{HTTPHeader("Accept-Language")}}, {{HTTPHeader("Accept")}}</li>
-</ul>
+- HTTP [content negotiation](/en-US/docs/Web/HTTP/Content_negotiation)
+- [Accept-Charset is no more](https://hsivonen.fi/accept-charset/)
+- Header with the result of the content negotiation: {{HTTPHeader("Content-Type")}}
+- Other similar headers: {{HTTPHeader("TE")}}, {{HTTPHeader("Accept-Encoding")}}, {{HTTPHeader("Accept-Language")}}, {{HTTPHeader("Accept")}}
diff --git a/files/en-us/web/http/headers/accept-encoding/index.md b/files/en-us/web/http/headers/accept-encoding/index.md
index 0dedcb50db23ba8..4c8b4d155a9efe1 100644
--- a/files/en-us/web/http/headers/accept-encoding/index.md
+++ b/files/en-us/web/http/headers/accept-encoding/index.md
@@ -9,43 +9,39 @@ tags:
   - Request header
 browser-compat: http.headers.Accept-Encoding
 ---
-<div>{{HTTPSidebar}}</div>
+{{HTTPSidebar}}
 
-<p>The <strong><code>Accept-Encoding</code></strong> request HTTP header advertises which content encoding, usually a compression algorithm, the client is able to understand. Using <a href="/en-US/docs/Web/HTTP/Content_negotiation">content negotiation</a>, the server selects one of the proposals, uses it and informs the client of its choice with the {{HTTPHeader("Content-Encoding")}} response header.</p>
+The **`Accept-Encoding`** request HTTP header advertises which content encoding, usually a compression algorithm, the client is able to understand. Using [content negotiation](/en-US/docs/Web/HTTP/Content_negotiation), the server selects one of the proposals, uses it and informs the client of its choice with the {{HTTPHeader("Content-Encoding")}} response header.
 
-<p>Even if both the client and the server supports the same compression algorithms, the server may choose not to compress the body of a response, if the <code>identity</code> value is also acceptable. Two common cases lead to this:</p>
+Even if both the client and the server supports the same compression algorithms, the server may choose not to compress the body of a response, if the `identity` value is also acceptable. Two common cases lead to this:
 
-<ul>
- <li>The data to be sent is already compressed and a second compression won't lead to smaller data to be transmitted. This may be the case with some image formats;</li>
- <li>The server is overloaded and cannot afford the computational overhead induced by the compression requirement. Typically, Microsoft recommends not to compress if a server uses more than 80% of its computational power.</li>
-</ul>
+- The data to be sent is already compressed and a second compression won't lead to smaller data to be transmitted. This may be the case with some image formats;
+- The server is overloaded and cannot afford the computational overhead induced by the compression requirement. Typically, Microsoft recommends not to compress if a server uses more than 80% of its computational power.
 
-<p>As long as the <code>identity</code> value, meaning no encoding, is not explicitly forbidden, by an <code>identity;q=0</code> or a <code>*;q=0</code> without another explicitly set value for identity, the server must never send back a {{HTTPStatus("406")}} <code>Not Acceptable</code> error.</p>
+As long as the `identity` value, meaning no encoding, is not explicitly forbidden, by an `identity;q=0` or a `*;q=0` without another explicitly set value for identity, the server must never send back a {{HTTPStatus("406")}} `Not Acceptable` error.
 
-<div class="notecard note">
-  <p><strong>Note:</strong></p>
-  <ul>
-    <li><p>An IANA registry maintains <a href="https://www.iana.org/assignments/http-parameters/http-parameters.xml#http-parameters-1">a complete list of official content encodings</a>.</p></li>
-    <li>Two others content encoding, <code>bzip</code> and <code>bzip2</code>, are sometimes used, though not standard. They implement the algorithm used by these two UNIX programs. Note that the first one was discontinued due to patent licensing problems.</li>
-  </ul>
-</div>
+> **Note:**
+>
+> - An IANA registry maintains [a complete list of official content encodings](https://www.iana.org/assignments/http-parameters/http-parameters.xml#http-parameters-1).
+> - Two others content encoding, `bzip` and `bzip2`, are sometimes used, though not standard. They implement the algorithm used by these two UNIX programs. Note that the first one was discontinued due to patent licensing problems.
 
 <table class="properties">
- <tbody>
-  <tr>
-   <th scope="row">Header type</th>
-   <td>{{Glossary("Request header")}}</td>
-  </tr>
-  <tr>
-   <th scope="row">{{Glossary("Forbidden header name")}}</th>
-   <td>yes</td>
-  </tr>
- </tbody>
+  <tbody>
+    <tr>
+      <th scope="row">Header type</th>
+      <td>{{Glossary("Request header")}}</td>
+    </tr>
+    <tr>
+      <th scope="row">{{Glossary("Forbidden header name")}}</th>
+      <td>yes</td>
+    </tr>
+  </tbody>
 </table>
 
-<h2 id="Syntax">Syntax</h2>
+## Syntax
 
-<pre class="brush: html">Accept-Encoding: gzip
+```html
+Accept-Encoding: gzip
 Accept-Encoding: compress
 Accept-Encoding: deflate
 Accept-Encoding: br
@@ -53,48 +49,44 @@ Accept-Encoding: identity
 Accept-Encoding: *
 
 // Multiple algorithms, weighted with the {{Glossary("Quality Values", "quality value")}} syntax:
-Accept-Encoding: deflate, gzip;q=1.0, *;q=0.5</pre>
+Accept-Encoding: deflate, gzip;q=1.0, *;q=0.5
+```
 
-<h2 id="Directives">Directives</h2>
+## Directives
 
-<dl>
- <dt><code>gzip</code></dt>
- <dd>A compression format using the <a class="external external-icon" href="https://en.wikipedia.org/wiki/LZ77_and_LZ78#LZ77">Lempel-Ziv coding</a> (LZ77), with a 32-bit CRC.</dd>
- <dt><code>compress</code></dt>
- <dd>A compression format using the <a class="external external-icon" href="https://en.wikipedia.org/wiki/LZW">Lempel-Ziv-Welch</a> (LZW) algorithm.</dd>
- <dt><code>deflate</code></dt>
- <dd>A compression format using the <a class="external external-icon" href="https://en.wikipedia.org/wiki/Zlib">zlib</a> structure, with the <a class="external external-icon" href="https://en.wikipedia.org/wiki/DEFLATE"><em>deflate</em></a> compression algorithm.</dd>
- <dt><code>br</code></dt>
- <dd>A compression format using the <a class="external external-icon" href="https://en.wikipedia.org/wiki/Brotli">Brotli</a> algorithm.</dd>
- <dt><code>identity</code></dt>
- <dd>Indicates the identity function (i.e. no compression, nor modification). This value is always considered as acceptable, even if not present.</dd>
- <dt><code>*</code></dt>
- <dd>Matches any content encoding not already listed in the header. This is the default value if the header is not present. It doesn't mean that any algorithm is supported; merely that no preference is expressed.</dd>
- <dt><code>;q=</code> (qvalues weighting)</dt>
- <dd>Any value is placed in an order of preference expressed using a relative <a href="/en-US/docs/Glossary/Quality_values">quality value</a> called <em>weight</em>.</dd>
-</dl>
+- `gzip`
+  - : A compression format using the [Lempel-Ziv coding](https://en.wikipedia.org/wiki/LZ77_and_LZ78#LZ77) (LZ77), with a 32-bit CRC.
+- `compress`
+  - : A compression format using the [Lempel-Ziv-Welch](https://en.wikipedia.org/wiki/LZW) (LZW) algorithm.
+- `deflate`
+  - : A compression format using the [zlib](https://en.wikipedia.org/wiki/Zlib) structure, with the [_deflate_](https://en.wikipedia.org/wiki/DEFLATE) compression algorithm.
+- `br`
+  - : A compression format using the [Brotli](https://en.wikipedia.org/wiki/Brotli) algorithm.
+- `identity`
+  - : Indicates the identity function (i.e. no compression, nor modification). This value is always considered as acceptable, even if not present.
+- `*`
+  - : Matches any content encoding not already listed in the header. This is the default value if the header is not present. It doesn't mean that any algorithm is supported; merely that no preference is expressed.
+- `;q=` (qvalues weighting)
+  - : Any value is placed in an order of preference expressed using a relative [quality value](/en-US/docs/Glossary/Quality_values) called _weight_.
 
-<h2 id="Examples">Examples</h2>
+## Examples
 
-<pre>Accept-Encoding: gzip
+    Accept-Encoding: gzip
 
-Accept-Encoding: gzip, compress, br
+    Accept-Encoding: gzip, compress, br
 
-Accept-Encoding: br;q=1.0, gzip;q=0.8, *;q=0.1
-</pre>
+    Accept-Encoding: br;q=1.0, gzip;q=0.8, *;q=0.1
 
-<h2 id="Specifications">Specifications</h2>
+## Specifications
 
 {{Specifications}}
 
-<h2 id="Browser_compatibility">Browser compatibility</h2>
+## Browser compatibility
 
-<p>{{Compat}}</p>
+{{Compat}}
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
- <li>HTTP <a href="/en-US/docs/Web/HTTP/Content_negotiation">content negotiation</a></li>
- <li>Header with the result of the content negotiation: {{HTTPHeader("Content-Encoding")}}</li>
- <li>Other similar headers: {{HTTPHeader("TE")}}, {{HTTPHeader("Accept")}}, {{HTTPHeader("Accept-Language")}}</li>
-</ul>
+- HTTP [content negotiation](/en-US/docs/Web/HTTP/Content_negotiation)
+- Header with the result of the content negotiation: {{HTTPHeader("Content-Encoding")}}
+- Other similar headers: {{HTTPHeader("TE")}}, {{HTTPHeader("Accept")}}, {{HTTPHeader("Accept-Language")}}
diff --git a/files/en-us/web/http/headers/accept-language/index.md b/files/en-us/web/http/headers/accept-language/index.md
index c7fa68146ad8a8f..7c2a2fccd92e70c 100644
--- a/files/en-us/web/http/headers/accept-language/index.md
+++ b/files/en-us/web/http/headers/accept-language/index.md
@@ -2,36 +2,36 @@
 title: Accept-Language
 slug: Web/HTTP/Headers/Accept-Language
 tags:
-- Accept-Language
-- Content Negotiation
-- HTTP
-- HTTP Header
-- Reference
-- Request header
+  - Accept-Language
+  - Content Negotiation
+  - HTTP
+  - HTTP Header
+  - Reference
+  - Request header
 browser-compat: http.headers.Accept-Language
 ---
-<div>{{HTTPSidebar}}</div>
-
-<p>The <strong><code>Accept-Language</code></strong> request HTTP header advertises which
-  languages the client is able to understand, and which locale variant is preferred. (By
-  languages, we mean natural languages, such as English, and not programming languages.)
-  Using <a href="/en-US/docs/Web/HTTP/Content_negotiation">content negotiation</a>, the
-  server then selects one of the proposals, uses it and informs the client of its choice
-  with the {{HTTPHeader("Content-Language")}} response header. Browsers set adequate
-  values for this header according to their user interface language and even if a user can
-  change it, this happens rarely (and is frowned upon as it leads to fingerprinting).</p>
-
-<p>This header is a hint to be used when the server has no way of determining the language
-  via another way, like a specific URL, that is controlled by an explicit user decision.
-  It is recommended that the server never overrides an explicit decision. The content of
-  the <code>Accept-Language</code> is often out of the control of the user (like when
-  traveling and using an Internet Cafe in a different country); the user may also want to
-  visit a page in another language than the locale of their user interface.</p>
-
-<p>If the server cannot serve any matching language, it can theoretically send back a
-  {{HTTPStatus("406")}} (Not Acceptable) error code. But, for a better user experience,
-  this is rarely done and more common way is to ignore the <code>Accept-Language</code>
-  header in this case.</p>
+{{HTTPSidebar}}
+
+The **`Accept-Language`** request HTTP header advertises which
+languages the client is able to understand, and which locale variant is preferred. (By
+languages, we mean natural languages, such as English, and not programming languages.)
+Using [content negotiation](/en-US/docs/Web/HTTP/Content_negotiation), the
+server then selects one of the proposals, uses it and informs the client of its choice
+with the {{HTTPHeader("Content-Language")}} response header. Browsers set adequate
+values for this header according to their user interface language and even if a user can
+change it, this happens rarely (and is frowned upon as it leads to fingerprinting).
+
+This header is a hint to be used when the server has no way of determining the language
+via another way, like a specific URL, that is controlled by an explicit user decision.
+It is recommended that the server never overrides an explicit decision. The content of
+the `Accept-Language` is often out of the control of the user (like when
+traveling and using an Internet Cafe in a different country); the user may also want to
+visit a page in another language than the locale of their user interface.
+
+If the server cannot serve any matching language, it can theoretically send back a
+{{HTTPStatus("406")}} (Not Acceptable) error code. But, for a better user experience,
+this is rarely done and more common way is to ignore the `Accept-Language`
+header in this case.
 
 <table class="properties">
   <tbody>
@@ -44,63 +44,63 @@ browser-compat: http.headers.Accept-Language
       <td>no</td>
     </tr>
     <tr>
-      <th scope="row">{{Glossary("CORS-safelisted request header")}}</th>
-      <td>yes, with the additional restriction that values can only be <code>0-9</code>,
-        <code>A-Z</code>, <code>a-z</code>, space or <code>*,-.;=</code>.</td>
+      <th scope="row">
+        {{Glossary("CORS-safelisted request header")}}
+      </th>
+      <td>
+        yes, with the additional restriction that values can only be
+        <code>0-9</code>, <code>A-Z</code>, <code>a-z</code>, space or
+        <code>*,-.;=</code>.
+      </td>
     </tr>
   </tbody>
 </table>
 
-<h2 id="Syntax">Syntax</h2>
+## Syntax
 
-<pre class="brush: html">Accept-Language: &lt;language&gt;
+```html
+Accept-Language: <language>
 Accept-Language: *
 
 // Multiple types, weighted with the {{glossary("quality values", "quality value")}} syntax:
-Accept-Language: fr-CH, fr;q=0.9, en;q=0.8, de;q=0.7, *;q=0.5</pre>
+Accept-Language: fr-CH, fr;q=0.9, en;q=0.8, de;q=0.7, *;q=0.5
+```
 
-<h2 id="Directives">Directives</h2>
+## Directives
 
-<dl>
-  <dt><code>&lt;language&gt;</code></dt>
-  <dd>
-    <p>A language tag (which is sometimes referred to as a "locale identifier"). This
-      consists of a 2-3 letter base language tag representing the language, optionally
-      followed by additional subtags separated by <code>'-'</code>. The most common extra
-      information is the country or region variant (like <code>'en-US'</code> or
-      <code>'fr-CA'</code>) or the type of alphabet to use (like <code>'sr-Latn'</code>).
-      Other variants like the type of orthography (<code>'de-DE-1996'</code>) are usually
-      not used in the context of this header.</p>
-  </dd>
-  <dt><code>*</code></dt>
-  <dd>Any language; <code>'*'</code> is used as a wildcard.</dd>
-  <dt><code>;q=</code> (q-factor weighting)</dt>
-  <dd>Any value placed in an order of preference expressed using a relative
-    {{glossary("Quality values", "quality value")}} called <em>weight</em>.</dd>
-</dl>
+- `<language>`
+  - : A language tag (which is sometimes referred to as a "locale identifier"). This
+    consists of a 2-3 letter base language tag representing the language, optionally
+    followed by additional subtags separated by `'-'`. The most common extra
+    information is the country or region variant (like `'en-US'` or
+    `'fr-CA'`) or the type of alphabet to use (like `'sr-Latn'`).
+    Other variants like the type of orthography (`'de-DE-1996'`) are usually
+    not used in the context of this header.
+- `*`
+  - : Any language; `'*'` is used as a wildcard.
+- `;q=` (q-factor weighting)
+  - : Any value placed in an order of preference expressed using a relative
+    {{glossary("Quality values", "quality value")}} called _weight_.
 
-<h2 id="Examples">Examples</h2>
+## Examples
 
-<pre>Accept-Language: de
+    Accept-Language: de
 
-Accept-Language: de-CH
+    Accept-Language: de-CH
 
-Accept-Language: en-US,en;q=0.5
-</pre>
+    Accept-Language: en-US,en;q=0.5
 
-<h2 id="Specifications">Specifications</h2>
+## Specifications
 
 {{Specifications}}
 
-<h2 id="Browser_compatibility">Browser compatibility</h2>
+## Browser compatibility
 
-<p>{{Compat}}</p>
+{{Compat}}
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
-  <li>HTTP <a href="/en-US/docs/Web/HTTP/Content_negotiation">content negotiation</a></li>
-  <li>Header with the result of the content negotiation:
-    {{HTTPHeader("Content-Language")}}</li>
-  <li>Other similar headers: {{HTTPHeader("TE")}}, {{HTTPHeader("Accept-Encoding")}}, {{HTTPHeader("Accept")}}</li>
-</ul>
+- HTTP [content negotiation](/en-US/docs/Web/HTTP/Content_negotiation)
+- Header with the result of the content negotiation:
+  {{HTTPHeader("Content-Language")}}
+- Other similar headers: {{HTTPHeader("TE")}}, {{HTTPHeader("Accept-Encoding")}}, {{HTTPHeader("Accept")}}
diff --git a/files/en-us/web/http/headers/accept-patch/index.md b/files/en-us/web/http/headers/accept-patch/index.md
index bcd24355f04ea3e..231e2a0eac7a14f 100644
--- a/files/en-us/web/http/headers/accept-patch/index.md
+++ b/files/en-us/web/http/headers/accept-patch/index.md
@@ -5,79 +5,65 @@ tags:
   - HTTP
   - Reference
 ---
-<div>{{HTTPSidebar}}</div>
+{{HTTPSidebar}}
 
-<p>The <strong><code>Accept-Patch</code></strong> response HTTP header advertises which media-type the server is able to understand in a PATCH request.</p>
+The **`Accept-Patch`** response HTTP header advertises which media-type the server is able to understand in a PATCH request.
 
-<p><strong><code>Accept-Patch</code></strong> in response to any method means that PATCH is allowed on the resource identified by the Request-URI. Two common cases lead to this:</p>
+**`Accept-Patch`** in response to any method means that PATCH is allowed on the resource identified by the Request-URI. Two common cases lead to this:
 
-<p>A server receiving a PATCH request with an unsupported media type could reply with {{HTTPStatus("415")}} <code>Unsupported Media Type</code> and an Accept-Patch header referencing one or more supported media types.</p>
+A server receiving a PATCH request with an unsupported media type could reply with {{HTTPStatus("415")}} `Unsupported Media Type` and an Accept-Patch header referencing one or more supported media types.
 
-<div class="notecard note">
-  <p><strong>Note:</strong></p>
-  <ul>
-    <li><p>An IANA registry maintains <a href="https://www.iana.org/assignments/http-parameters/http-parameters.xml#http-parameters-1">a complete list of official content encodings</a>.</p></li>
-    <li>Two others content encoding, <code>bzip</code> and <code>bzip2</code>, are sometimes used, though not standard. They implement the algorithm used by these two UNIX programs. Note that the first one was discontinued due to patent licensing problems.</li>
-  </ul>
-</div>
+> **Note:**
+>
+> - An IANA registry maintains [a complete list of official content encodings](https://www.iana.org/assignments/http-parameters/http-parameters.xml#http-parameters-1).
+> - Two others content encoding, `bzip` and `bzip2`, are sometimes used, though not standard. They implement the algorithm used by these two UNIX programs. Note that the first one was discontinued due to patent licensing problems.
 
 <table class="properties">
- <tbody>
-  <tr>
-   <th scope="row">Header type</th>
-   <td>{{Glossary("Response header")}}</td>
-  </tr>
-  <tr>
-   <th scope="row">{{Glossary("Forbidden header name")}}</th>
-   <td>yes</td>
-  </tr>
- </tbody>
+  <tbody>
+    <tr>
+      <th scope="row">Header type</th>
+      <td>{{Glossary("Response header")}}</td>
+    </tr>
+    <tr>
+      <th scope="row">{{Glossary("Forbidden header name")}}</th>
+      <td>yes</td>
+    </tr>
+  </tbody>
 </table>
 
-<h2 id="Syntax">Syntax</h2>
+## Syntax
 
-<pre class="brush: html">Accept-Patch: application/example, text/example
+```html
+Accept-Patch: application/example, text/example
 Accept-Patch: text/example;charset=utf-8
 Accept-Patch: application/merge-patch+json
-</pre>
+```
 
-<h2 id="Directives">Directives</h2>
+## Directives
 
-<p>None</p>
+None
 
-<h2 id="Examples">Examples</h2>
+## Examples
 
-<pre class="brush: html">Accept-Patch: application/example, text/example
+```html
+Accept-Patch: application/example, text/example
 
 Accept-Patch: text/example;charset=utf-8
 
 Accept-Patch: application/merge-patch+json
-</pre>
-
-<h2 id="Specifications">Specifications</h2>
-
-<table class="standard-table">
- <thead>
-  <tr>
-   <th scope="col">Specification</th>
-   <th scope="col">Title</th>
-  </tr>
- </thead>
- <tbody>
-  <tr>
-   <td>{{RFC("5789", "Accept-Patch", "3.1")}}</td>
-   <td>HTTP PATCH</td>
-  </tr>
- </tbody>
-</table>
+```
+
+## Specifications
+
+| Specification                                        | Title      |
+| ---------------------------------------------------- | ---------- |
+| {{RFC("5789", "Accept-Patch", "3.1")}} | HTTP PATCH |
 
-<h2 id="Browser_compatibility">Browser compatibility</h2>
+## Browser compatibility
 
-<p>Browser compatibility is not relevant for this header (header is sent by server, and the specification does not define client behavior).</p>
+Browser compatibility is not relevant for this header (header is sent by server, and the specification does not define client behavior).
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
- <li>Http method {{HTTPMethod("PATCH")}}</li>
- <li>HTTP Semantic and context {{RFC("7231", "PUT", "4.3.4")}}</li>
-</ul>
+- Http method {{HTTPMethod("PATCH")}}
+- HTTP Semantic and context {{RFC("7231", "PUT", "4.3.4")}}
diff --git a/files/en-us/web/http/headers/accept-post/index.md b/files/en-us/web/http/headers/accept-post/index.md
index 284302c0b5ffab2..ab7eb00b85c7c7f 100644
--- a/files/en-us/web/http/headers/accept-post/index.md
+++ b/files/en-us/web/http/headers/accept-post/index.md
@@ -7,76 +7,60 @@ tags:
   - HTTP Header
   - Response Header
 ---
-<div>{{HTTPSidebar}}</div>
+{{HTTPSidebar}}
 
-<p>The <strong><code>Accept-Post</code></strong> response HTTP header advertises which <a href="/en-US/docs/Web/HTTP/Basics_of_HTTP/MIME_types">media types</a> are accepted by the server for HTTP post requests.</p>
+The **`Accept-Post`** response HTTP header advertises which [media types](/en-US/docs/Web/HTTP/Basics_of_HTTP/MIME_types) are accepted by the server for HTTP post requests.
 
-<p><strong><code>Accept-Post</code></strong> in response to any method means that <code>POST</code> is allowed on the requested resource (any document/media format in the header further indicates that the document format is allowed).</p>
+**`Accept-Post`** in response to any method means that `POST` is allowed on the requested resource (any document/media format in the header further indicates that the document format is allowed).
 
-<p>For example, a server receiving a <code>POST</code> request with an unsupported media type could reply with {{HTTPStatus("415")}} <code>Unsupported Media Type</code> and an <code><strong>Accept-Post</strong></code> header referencing one or more supported media types.</p>
+For example, a server receiving a `POST` request with an unsupported media type could reply with {{HTTPStatus("415")}} `Unsupported Media Type` and an **`Accept-Post`** header referencing one or more supported media types.
 
-<div class="notecard note">
-  <p><strong>Note:</strong> An IANA registry maintains <a href="https://www.iana.org/assignments/http-parameters/http-parameters.xml#http-parameters-1">a complete list of official content encodings</a>.</p>
-</div>
+> **Note:** An IANA registry maintains [a complete list of official content encodings](https://www.iana.org/assignments/http-parameters/http-parameters.xml#http-parameters-1).
 
 <table class="properties">
- <tbody>
-  <tr>
-   <th scope="row">Header type</th>
-   <td>{{Glossary("Response header")}}</td>
-  </tr>
-  <tr>
-   <th scope="row">{{Glossary("Forbidden header name")}}</th>
-   <td>yes</td>
-  </tr>
- </tbody>
+  <tbody>
+    <tr>
+      <th scope="row">Header type</th>
+      <td>{{Glossary("Response header")}}</td>
+    </tr>
+    <tr>
+      <th scope="row">{{Glossary("Forbidden header name")}}</th>
+      <td>yes</td>
+    </tr>
+  </tbody>
 </table>
 
-<h2 id="Syntax">Syntax</h2>
+## Syntax
 
-<pre>Accept: &lt;MIME_type&gt;/&lt;MIME_subtype&gt;
-Accept: &lt;MIME_type&gt;/*
-Accept: */*</pre>
+    Accept: <MIME_type>/<MIME_subtype>
+    Accept: <MIME_type>/*
+    Accept: */*
 
-<div class="notecard note">
-  <p><strong>Note:</strong> The <code>Accept-Post</code> header specifies a media range in the same way as {{HTTPHeader("Accept-Language")}}, except that it has no notion of preference (i.e. "accept-params" or "q" arguments are not significant).</p>
-</div>
+> **Note:** The `Accept-Post` header specifies a media range in the same way as {{HTTPHeader("Accept-Language")}}, except that it has no notion of preference (i.e. "accept-params" or "q" arguments are not significant).
 
-<h2 id="Directives">Directives</h2>
+## Directives
 
-<p>None.</p>
+None.
 
-<h2 id="Examples">Examples</h2>
+## Examples
 
-<pre class="brush: html">Accept-Post: application/example, text/example
+```html
+Accept-Post: application/example, text/example
 Accept-Post: image/webp
 Accept-Post: */*
-</pre>
-
-<h2 id="Specifications">Specifications</h2>
-
-<table class="standard-table">
- <thead>
-  <tr>
-   <th scope="col">Specification</th>
-   <th scope="col">Title</th>
-  </tr>
- </thead>
- <tbody>
-  <tr>
-   <td><a href="https://www.w3.org/TR/ldp/#header-accept-post">Linked Data Platform 1.0, Section 7.1: The Accept-Post Response Header</a></td>
-   <td>ACCEPT POST</td>
-  </tr>
- </tbody>
-</table>
+```
+
+## Specifications
+
+| Specification                                                                                                           | Title       |
+| ----------------------------------------------------------------------------------------------------------------------- | ----------- |
+| [Linked Data Platform 1.0, Section 7.1: The Accept-Post Response Header](https://www.w3.org/TR/ldp/#header-accept-post) | ACCEPT POST |
 
-<h2 id="Browser_compatibility">Browser compatibility</h2>
+## Browser compatibility
 
-<p>Browser compatibility is not relevant for this header (header is sent by server, and the specification does not define client behavior).</p>
+Browser compatibility is not relevant for this header (header is sent by server, and the specification does not define client behavior).
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
- <li>Http method {{HTTPMethod("POST")}}</li>
- <li>HTTP Semantic and context {{RFC("7231", "POST", "4.3.3")}}</li>
-</ul>
+- Http method {{HTTPMethod("POST")}}
+- HTTP Semantic and context {{RFC("7231", "POST", "4.3.3")}}
diff --git a/files/en-us/web/http/headers/accept-ranges/index.md b/files/en-us/web/http/headers/accept-ranges/index.md
index a48059adf6b94e0..4e61fe856ca3b8a 100644
--- a/files/en-us/web/http/headers/accept-ranges/index.md
+++ b/files/en-us/web/http/headers/accept-ranges/index.md
@@ -2,75 +2,69 @@
 title: Accept-Ranges
 slug: Web/HTTP/Headers/Accept-Ranges
 tags:
-- HTTP
-- HTTP Header
-- Range Requests
-- Reference
-- Response Header
+  - HTTP
+  - HTTP Header
+  - Range Requests
+  - Reference
+  - Response Header
 browser-compat: http.headers.Accept-Ranges
 ---
-<div>{{HTTPSidebar}}</div>
+{{HTTPSidebar}}
 
-<p>The <code><strong>Accept-Ranges</strong></code> response HTTP header is a marker used
-	by the server to advertise its support of partial requests. The value of this field
-	indicates the unit that can be used to define a range.</p>
+The **`Accept-Ranges`** response HTTP header is a marker used
+by the server to advertise its support of partial requests. The value of this field
+indicates the unit that can be used to define a range.
 
-<p>In presence of an <code>Accept-Ranges</code> header, the browser may try to
-	<em>resume</em> an interrupted download, rather than to start it from the start again.
-</p>
+In presence of an `Accept-Ranges` header, the browser may try to
+_resume_ an interrupted download, rather than to start it from the start again.
 
 <table class="properties">
-	<tbody>
-		<tr>
-			<th scope="row">Header type</th>
-			<td>{{Glossary("Response header")}}</td>
-		</tr>
-		<tr>
-			<th scope="row">{{Glossary("Forbidden header name")}}</th>
-			<td>no</td>
-		</tr>
-	</tbody>
+  <tbody>
+    <tr>
+      <th scope="row">Header type</th>
+      <td>{{Glossary("Response header")}}</td>
+    </tr>
+    <tr>
+      <th scope="row">{{Glossary("Forbidden header name")}}</th>
+      <td>no</td>
+    </tr>
+  </tbody>
 </table>
 
-<h2 id="Syntax">Syntax</h2>
+## Syntax
 
-<pre class="brush: html">Accept-Ranges: &lt;range-unit&gt;
-Accept-Ranges: none</pre>
+```html
+Accept-Ranges: <range-unit>
+Accept-Ranges: none
+```
 
-<h2 id="Directives">Directives</h2>
+## Directives
 
-<dl>
-	<dt><code>&lt;range-unit&gt;</code></dt>
-	<dd>Defines the range unit the server supports. Though <code>bytes</code> is the only
-		range unit formally defined by {{RFC("7233")}}, additional range units may be
-		registered in the<a
-			href="https://www.iana.org/assignments/http-parameters/http-parameters.xhtml#range-units">
-			HTTP Range Unit Registry</a>. </dd>
-	<dt><code>none</code></dt>
-	<dd>No range unit is supported, this makes the header equivalent of its own absence
-		and is therefore rarely used, though some browsers, like IE9, it is used to
-		disable or remove the pause buttons in the download manager.</dd>
-</dl>
+- `<range-unit>`
+  - : Defines the range unit the server supports. Though `bytes` is the only
+    range unit formally defined by {{RFC("7233")}}, additional range units may be
+    registered in the[
+    HTTP Range Unit Registry](https://www.iana.org/assignments/http-parameters/http-parameters.xhtml#range-units).
+- `none`
+  - : No range unit is supported, this makes the header equivalent of its own absence
+    and is therefore rarely used, though some browsers, like IE9, it is used to
+    disable or remove the pause buttons in the download manager.
 
-<h2 id="Examples">Examples</h2>
+## Examples
 
-<pre>Accept-Ranges: bytes
-</pre>
+    Accept-Ranges: bytes
 
-<h2 id="Specifications">Specifications</h2>
+## Specifications
 
 {{Specifications}}
 
-<h2 id="Browser_compatibility">Browser compatibility</h2>
+## Browser compatibility
 
-<p>{{Compat}}</p>
+{{Compat}}
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
-	<li>{{HTTPHeader("If-Range")}}</li>
-	<li>{{HTTPHeader("Range")}}</li>
-	<li><a
-			href="https://www.iana.org/assignments/http-parameters/http-parameters.xhtml#range-units">IANA
-			HTTP Range Unit Registry</a></li>
-</ul>
+- {{HTTPHeader("If-Range")}}
+- {{HTTPHeader("Range")}}
+- [IANA
+  HTTP Range Unit Registry](https://www.iana.org/assignments/http-parameters/http-parameters.xhtml#range-units)
diff --git a/files/en-us/web/http/headers/accept/index.md b/files/en-us/web/http/headers/accept/index.md
index e23645599752e9a..19f5acdacd42dcc 100644
--- a/files/en-us/web/http/headers/accept/index.md
+++ b/files/en-us/web/http/headers/accept/index.md
@@ -8,75 +8,77 @@ tags:
   - Request header
 browser-compat: http.headers.Accept
 ---
-<div>{{HTTPSidebar}}</div>
+{{HTTPSidebar}}
 
-<p>The <strong><code>Accept</code></strong> request HTTP header advertises which content types, expressed as <a href="/en-US/docs/Web/HTTP/Basics_of_HTTP/MIME_types">MIME types</a>, the client is able to understand. Using <a href="/en-US/docs/Web/HTTP/Content_negotiation">content negotiation</a>, the server then selects one of the proposals, uses it and informs the client of its choice with the {{HTTPHeader("Content-Type")}} response header. Browsers set adequate values for this header depending on the context where the request is done: when fetching a CSS stylesheet a different value is set for the request than when fetching an image, video or a script.</p>
+The **`Accept`** request HTTP header advertises which content types, expressed as [MIME types](/en-US/docs/Web/HTTP/Basics_of_HTTP/MIME_types), the client is able to understand. Using [content negotiation](/en-US/docs/Web/HTTP/Content_negotiation), the server then selects one of the proposals, uses it and informs the client of its choice with the {{HTTPHeader("Content-Type")}} response header. Browsers set adequate values for this header depending on the context where the request is done: when fetching a CSS stylesheet a different value is set for the request than when fetching an image, video or a script.
 
 <table class="properties">
- <tbody>
-  <tr>
-   <th scope="row">Header type</th>
-   <td>{{Glossary("Request header")}}</td>
-  </tr>
-  <tr>
-   <th scope="row">{{Glossary("Forbidden header name")}}</th>
-   <td>no</td>
-  </tr>
-  <tr>
-   <th scope="row">{{Glossary("CORS-safelisted request header")}}</th>
-   <td>yes, with the additional restriction that values can't contain a <em>CORS-unsafe request header byte</em>: 0x00-0x1F (except 0x09 (HT)), <code>"():&lt;&gt;?@[\]{}</code>, and 0x7F (DEL).</td>
-  </tr>
- </tbody>
+  <tbody>
+    <tr>
+      <th scope="row">Header type</th>
+      <td>{{Glossary("Request header")}}</td>
+    </tr>
+    <tr>
+      <th scope="row">{{Glossary("Forbidden header name")}}</th>
+      <td>no</td>
+    </tr>
+    <tr>
+      <th scope="row">
+        {{Glossary("CORS-safelisted request header")}}
+      </th>
+      <td>
+        yes, with the additional restriction that values can't contain a
+        <em>CORS-unsafe request header byte</em>: 0x00-0x1F (except 0x09 (HT)),
+        <code>"():&#x3C;>?@[\]{}</code>, and 0x7F (DEL).
+      </td>
+    </tr>
+  </tbody>
 </table>
 
-<h2 id="Syntax">Syntax</h2>
+## Syntax
 
-<pre class="brush: html">Accept: &lt;MIME_type&gt;/&lt;MIME_subtype&gt;
-Accept: &lt;MIME_type&gt;/*
+```html
+Accept: <MIME_type>/<MIME_subtype>
+Accept: <MIME_type>/*
 Accept: */*
 
 // Multiple types, weighted with the {{glossary("quality values", "quality value")}} syntax:
 Accept: text/html, application/xhtml+xml, application/xml;q=0.9, image/webp, */*;q=0.8
-</pre>
+```
 
-<h2 id="Directives">Directives</h2>
+## Directives
 
-<dl>
- <dt><code>&lt;MIME_type&gt;/&lt;MIME_subtype&gt;</code></dt>
- <dd>A single, precise <a href="/en-US/docs/Web/HTTP/Basics_of_HTTP/MIME_types">MIME type</a>, like <code>text/html</code>.</dd>
- <dt><code>&lt;MIME_type&gt;/*</code></dt>
- <dd>A MIME type, but without any subtype. <code>image/*</code> will match <code>image/png</code>, <code>image/svg</code>, <code>image/gif</code> and any other image types.</dd>
- <dt><code>*/*</code></dt>
- <dd>Any MIME type</dd>
- <dt><code>;q=</code> (q-factor weighting)</dt>
- <dd>Any value used is placed in an order of preference expressed using relative <a href="/en-US/docs/Glossary/Quality_values">quality value</a> called the <em>weight</em>.</dd>
-</dl>
+- `<MIME_type>/<MIME_subtype>`
+  - : A single, precise [MIME type](/en-US/docs/Web/HTTP/Basics_of_HTTP/MIME_types), like `text/html`.
+- `<MIME_type>/*`
+  - : A MIME type, but without any subtype. `image/*` will match `image/png`, `image/svg`, `image/gif` and any other image types.
+- `*/*`
+  - : Any MIME type
+- `;q=` (q-factor weighting)
+  - : Any value used is placed in an order of preference expressed using relative [quality value](/en-US/docs/Glossary/Quality_values) called the _weight_.
 
-<h2 id="Examples">Examples</h2>
+## Examples
 
-<pre>Accept: text/html
+    Accept: text/html
 
-Accept: image/*
+    Accept: image/*
 
-// General default
-Accept: */*
+    // General default
+    Accept: */*
 
-// Default for navigation requests
-Accept: text/html, application/xhtml+xml, application/xml;q=0.9, */*;q=0.8
-</pre>
+    // Default for navigation requests
+    Accept: text/html, application/xhtml+xml, application/xml;q=0.9, */*;q=0.8
 
-<h2 id="Specifications">Specifications</h2>
+## Specifications
 
 {{Specifications}}
 
-<h2 id="Browser_compatibility">Browser compatibility</h2>
+## Browser compatibility
 
-<p>{{Compat}}</p>
+{{Compat}}
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
- <li>HTTP <a href="/en-US/docs/Web/HTTP/Content_negotiation">content negotiation</a></li>
- <li>Header with the result of the content negotiation: {{HTTPHeader("Content-Type")}}</li>
- <li>Other similar headers: {{HTTPHeader("TE")}}, {{HTTPHeader("Accept-Encoding")}}, {{HTTPHeader("Accept-Language")}}</li>
-</ul>
+- HTTP [content negotiation](/en-US/docs/Web/HTTP/Content_negotiation)
+- Header with the result of the content negotiation: {{HTTPHeader("Content-Type")}}
+- Other similar headers: {{HTTPHeader("TE")}}, {{HTTPHeader("Accept-Encoding")}}, {{HTTPHeader("Accept-Language")}}
diff --git a/files/en-us/web/http/headers/access-control-allow-credentials/index.md b/files/en-us/web/http/headers/access-control-allow-credentials/index.md
index 851446edaf089f5..1674480ddd7f6ec 100644
--- a/files/en-us/web/http/headers/access-control-allow-credentials/index.md
+++ b/files/en-us/web/http/headers/access-control-allow-credentials/index.md
@@ -2,41 +2,40 @@
 title: Access-Control-Allow-Credentials
 slug: Web/HTTP/Headers/Access-Control-Allow-Credentials
 tags:
-- Access-Control-Allow-Credentials
-- CORS
-- HTTP
-- Reference
-- credentials
-- header
+  - Access-Control-Allow-Credentials
+  - CORS
+  - HTTP
+  - Reference
+  - credentials
+  - header
 browser-compat: http.headers.Access-Control-Allow-Credentials
 ---
-<div>{{HTTPSidebar}}</div>
-
-<p>The <strong><code>Access-Control-Allow-Credentials</code></strong> response header
-  tells browsers whether to expose the response to frontend JavaScript code when the
-  request's credentials mode ({{domxref("Request.credentials")}}) is <code>include</code>.
-</p>
-
-<p>When a request's credentials mode ({{domxref("Request.credentials")}}) is
-  <code>include</code>, browsers will only expose the response to frontend JavaScript code
-  if the <code>Access-Control-Allow-Credentials</code> value is <code>true</code>.</p>
-
-<p>Credentials are cookies, authorization headers or TLS client certificates.</p>
-
-<p>When used as part of a response to a preflight request, this indicates whether or not
-  the actual request can be made using credentials. Note that simple {{HTTPMethod("GET")}}
-  requests are not preflighted, and so if a request is made for a resource with
-  credentials, if this header is not returned with the resource, the response is ignored
-  by the browser and not returned to web content.</p>
-
-<p>The <code>Access-Control-Allow-Credentials</code> header works in conjunction with the
-  {{domxref("XMLHttpRequest.withCredentials")}} property or with the
-  <code>credentials</code> option in the {{domxref("Request.Request()", "Request()")}}
-  constructor of the Fetch API. For a CORS request with credentials, in order for browsers
-  to expose the response to frontend JavaScript code, both the server (using the
-  <code>Access-Control-Allow-Credentials</code> header) and the client (by setting the
-  credentials mode for the XHR, Fetch, or Ajax request) must indicate that they’re opting
-  in to including credentials.</p>
+{{HTTPSidebar}}
+
+The **`Access-Control-Allow-Credentials`** response header
+tells browsers whether to expose the response to frontend JavaScript code when the
+request's credentials mode ({{domxref("Request.credentials")}}) is `include`.
+
+When a request's credentials mode ({{domxref("Request.credentials")}}) is
+`include`, browsers will only expose the response to frontend JavaScript code
+if the `Access-Control-Allow-Credentials` value is `true`.
+
+Credentials are cookies, authorization headers or TLS client certificates.
+
+When used as part of a response to a preflight request, this indicates whether or not
+the actual request can be made using credentials. Note that simple {{HTTPMethod("GET")}}
+requests are not preflighted, and so if a request is made for a resource with
+credentials, if this header is not returned with the resource, the response is ignored
+by the browser and not returned to web content.
+
+The `Access-Control-Allow-Credentials` header works in conjunction with the
+{{domxref("XMLHttpRequest.withCredentials")}} property or with the
+`credentials` option in the {{domxref("Request.Request()", "Request()")}}
+constructor of the Fetch API. For a CORS request with credentials, in order for browsers
+to expose the response to frontend JavaScript code, both the server (using the
+`Access-Control-Allow-Credentials` header) and the client (by setting the
+credentials mode for the XHR, Fetch, or Ajax request) must indicate that they’re opting
+in to including credentials.
 
 <table class="properties">
   <tbody>
@@ -51,50 +50,51 @@ browser-compat: http.headers.Access-Control-Allow-Credentials
   </tbody>
 </table>
 
-<h2 id="Syntax">Syntax</h2>
+## Syntax
 
-<pre class="brush: html">Access-Control-Allow-Credentials: true
-</pre>
+```html
+Access-Control-Allow-Credentials: true
+```
 
-<h2 id="Directives">Directives</h2>
+## Directives
 
-<dl>
-  <dt>true</dt>
-  <dd>The only valid value for this header is <code>true</code> (case-sensitive). If you
+- true
+  - : The only valid value for this header is `true` (case-sensitive). If you
     don't need credentials, omit this header entirely (rather than setting its value to
-    <code>false</code>).</dd>
-</dl>
+    `false`).
 
-<h2 id="Examples">Examples</h2>
+## Examples
 
-<p>Allow credentials:</p>
+Allow credentials:
 
-<pre>Access-Control-Allow-Credentials: true</pre>
+    Access-Control-Allow-Credentials: true
 
-<p>Using <a href="/en-US/docs/Web/API/XMLHttpRequest">XHR</a> with credentials:</p>
+Using [XHR](/en-US/docs/Web/API/XMLHttpRequest) with credentials:
 
-<pre class="brush: js">var xhr = new XMLHttpRequest();
+```js
+var xhr = new XMLHttpRequest();
 xhr.open('GET', 'http://example.com/', true);
 xhr.withCredentials = true;
-xhr.send(null);</pre>
+xhr.send(null);
+```
 
-<p>Using <a href="/en-US/docs/Web/API/Fetch_API">Fetch</a> with credentials:</p>
+Using [Fetch](/en-US/docs/Web/API/Fetch_API) with credentials:
 
-<pre class="brush: js">fetch(url, {
+```js
+fetch(url, {
   credentials: 'include'
-})</pre>
+})
+```
 
-<h2 id="Specifications">Specifications</h2>
+## Specifications
 
 {{Specifications}}
 
-<h2 id="Browser_compatibility">Browser compatibility</h2>
+## Browser compatibility
 
-<p>{{Compat}}</p>
+{{Compat}}
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
-  <li>{{domxref("XMLHttpRequest.withCredentials")}}</li>
-  <li>{{domxref("Request.Request()", "Request()")}}</li>
-</ul>
+- {{domxref("XMLHttpRequest.withCredentials")}}
+- {{domxref("Request.Request()", "Request()")}}
diff --git a/files/en-us/web/http/headers/access-control-allow-headers/index.md b/files/en-us/web/http/headers/access-control-allow-headers/index.md
index f0af97a0c33604f..31c0a912a1b86a8 100644
--- a/files/en-us/web/http/headers/access-control-allow-headers/index.md
+++ b/files/en-us/web/http/headers/access-control-allow-headers/index.md
@@ -9,106 +9,101 @@ tags:
   - header
 browser-compat: http.headers.Access-Control-Allow-Headers
 ---
-<div>{{HTTPSidebar}}</div>
+{{HTTPSidebar}}
 
-<p>The <strong><code>Access-Control-Allow-Headers</code></strong> response header is used in response to a {{glossary("preflight request")}} which includes the {{HTTPHeader("Access-Control-Request-Headers")}} to indicate which HTTP headers can be used during the actual request.</p>
+The **`Access-Control-Allow-Headers`** response header is used in response to a {{glossary("preflight request")}} which includes the {{HTTPHeader("Access-Control-Request-Headers")}} to indicate which HTTP headers can be used during the actual request.
 
-<p>This header is required if the request has an {{HTTPHeader("Access-Control-Request-Headers")}} header.</p>
+This header is required if the request has an {{HTTPHeader("Access-Control-Request-Headers")}} header.
 
-<div class="notecard note">
-  <p><strong>Note:</strong> {{glossary("CORS-safelisted_request_header", "CORS-safelisted request headers")}} are always allowed and hence usually aren't listed in <code>Access-Control-Allow-Headers</code> (unless there is a need to circumvent the safelist <a href="/en-US/docs/Glossary/CORS-safelisted_request_header#additional_restrictions">additional restrictions</a>).</p>
-</div>
+> **Note:** {{glossary("CORS-safelisted_request_header", "CORS-safelisted request headers")}} are always allowed and hence usually aren't listed in `Access-Control-Allow-Headers` (unless there is a need to circumvent the safelist [additional restrictions](/en-US/docs/Glossary/CORS-safelisted_request_header#additional_restrictions)).
 
 <table class="properties">
- <tbody>
-  <tr>
-   <th scope="row">Header type</th>
-   <td>{{Glossary("Response header")}}</td>
-  </tr>
-  <tr>
-   <th scope="row">{{Glossary("Forbidden header name")}}</th>
-   <td>no</td>
-  </tr>
- </tbody>
+  <tbody>
+    <tr>
+      <th scope="row">Header type</th>
+      <td>{{Glossary("Response header")}}</td>
+    </tr>
+    <tr>
+      <th scope="row">{{Glossary("Forbidden header name")}}</th>
+      <td>no</td>
+    </tr>
+  </tbody>
 </table>
 
-<h2 id="Syntax">Syntax</h2>
+## Syntax
 
-<pre class="brush: html">Access-Control-Allow-Headers: [<em>&lt;header-name&gt;</em>[, <em>&lt;header-name&gt;</em>]*]
+```html
+Access-Control-Allow-Headers: [<header-name>[, <header-name>]*]
 Access-Control-Allow-Headers: *
-</pre>
+```
 
-<h2 id="Directives">Directives</h2>
+## Directives
 
-<dl>
- <dt><code>&lt;header-name&gt;</code></dt>
- <dd>The name of a supported request header. The header may list any number of headers, separated by commas.</dd>
- <dt><code>*</code> (wildcard)</dt>
- <dd>The value "<code>*</code>" only counts as a special wildcard value for requests without credentials (requests without <a href="/en-US/docs/Web/HTTP/Cookies">HTTP cookies</a> or HTTP authentication information). In requests with credentials, it is treated as the literal header name "<code>*</code>" without special semantics. Note that the {{HTTPHeader("Authorization")}} header can't be wildcarded and always needs to be listed explicitly.</dd>
-</dl>
+- `<header-name>`
+  - : The name of a supported request header. The header may list any number of headers, separated by commas.
+- `*` (wildcard)
+  - : The value "`*`" only counts as a special wildcard value for requests without credentials (requests without [HTTP cookies](/en-US/docs/Web/HTTP/Cookies) or HTTP authentication information). In requests with credentials, it is treated as the literal header name "`*`" without special semantics. Note that the {{HTTPHeader("Authorization")}} header can't be wildcarded and always needs to be listed explicitly.
 
-<h2 id="Examples">Examples</h2>
+## Examples
 
-<h3 id="A_custom_header">A custom header</h3>
+### A custom header
 
-<p>Here's an example of what an <code>Access-Control-Allow-Headers</code> header might look like. It indicates that a custom header named <code>X-Custom-Header</code> is supported by CORS requests to the server (in addition to the {{glossary("CORS-safelisted_request_header", "CORS-safelisted request headers")}}).</p>
+Here's an example of what an `Access-Control-Allow-Headers` header might look like. It indicates that a custom header named `X-Custom-Header` is supported by CORS requests to the server (in addition to the {{glossary("CORS-safelisted_request_header", "CORS-safelisted request headers")}}).
 
-<pre>Access-Control-Allow-Headers: X-Custom-Header</pre>
+    Access-Control-Allow-Headers: X-Custom-Header
 
-<h3 id="Multiple_headers">Multiple headers</h3>
+### Multiple headers
 
-<p>This example shows <code>Access-Control-Allow-Headers</code> when it specifies support for multiple headers.</p>
+This example shows `Access-Control-Allow-Headers` when it specifies support for multiple headers.
 
-<pre>Access-Control-Allow-Headers: X-Custom-Header, Upgrade-Insecure-Requests</pre>
+    Access-Control-Allow-Headers: X-Custom-Header, Upgrade-Insecure-Requests
 
-<h3 id="Bypassing_additional_restrictions">Bypassing additional restrictions</h3>
+### Bypassing additional restrictions
 
-<p>Although {{glossary("CORS-safelisted_request_header", "CORS-safelisted request headers")}} are always allowed and don't usually need to be listed in <code>Access-Control-Allow-Headers</code>, listing them anyway will circumvent the <a href="/en-US/docs/Glossary/CORS-safelisted_request_header#additional_restrictions">additional restrictions</a> that apply.</p>
+Although {{glossary("CORS-safelisted_request_header", "CORS-safelisted request headers")}} are always allowed and don't usually need to be listed in `Access-Control-Allow-Headers`, listing them anyway will circumvent the [additional restrictions](/en-US/docs/Glossary/CORS-safelisted_request_header#additional_restrictions) that apply.
 
-<pre>Access-Control-Allow-Headers: Accept</pre>
+    Access-Control-Allow-Headers: Accept
 
-<h3 id="Example_preflight_request">Example preflight request</h3>
+### Example preflight request
 
-<p>Let's look at an example of a {{glossary("preflight request")}} involving <code>Access-Control-Allow-Headers</code>.</p>
+Let's look at an example of a {{glossary("preflight request")}} involving `Access-Control-Allow-Headers`.
 
-<h4 id="Request">Request</h4>
+#### Request
 
-<p>First, the request. The preflight request is an {{HTTPMethod("OPTIONS")}} request that includes some combination of the three preflight request headers: {{HTTPHeader("Access-Control-Request-Method")}}, {{HTTPHeader("Access-Control-Request-Headers")}}, and {{HTTPHeader("Origin")}}.</p>
+First, the request. The preflight request is an {{HTTPMethod("OPTIONS")}} request that includes some combination of the three preflight request headers: {{HTTPHeader("Access-Control-Request-Method")}}, {{HTTPHeader("Access-Control-Request-Headers")}}, and {{HTTPHeader("Origin")}}.
 
-<p>The preflight request below tells the server that we want to send a CORS <code>GET</code> request that has the headers listed in {{HTTPHeader("Access-Control-Request-Headers")}} ({{HTTPHeader("Content-Type")}} and <code>x-requested-with</code>).</p>
+The preflight request below tells the server that we want to send a CORS `GET` request that has the headers listed in {{HTTPHeader("Access-Control-Request-Headers")}} ({{HTTPHeader("Content-Type")}} and `x-requested-with`).
 
-<pre>OPTIONS /resource/foo
-Access-Control-Request-Method: GET
-<strong>Access-Control-Request-Headers: Content-Type, x-requested-with</strong>
-Origin: https://foo.bar.org</pre>
+    OPTIONS /resource/foo
+    Access-Control-Request-Method: GET
+    Access-Control-Request-Headers: Content-Type, x-requested-with
+    Origin: https://foo.bar.org
 
-<h4 id="Response">Response</h4>
+#### Response
 
-<p>If the CORS request indicated by the preflight request is authorized, the server will respond to the preflight request with a message that indicates the allowed origin, methods and headers. Below we see that {{HTTPHeader("Access-Control-Allow-Headers")}} includes the headers that were requested.</p>
+If the CORS request indicated by the preflight request is authorized, the server will respond to the preflight request with a message that indicates the allowed origin, methods and headers. Below we see that {{HTTPHeader("Access-Control-Allow-Headers")}} includes the headers that were requested.
 
-<pre>HTTP/1.1 200 OK
-Content-Length: 0
-Connection: keep-alive
-Access-Control-Allow-Origin: https://foo.bar.org
-Access-Control-Allow-Methods: POST, GET, OPTIONS, DELETE
-<strong>Access-Control-Allow-Headers: Content-Type, x-requested-with</strong>
-Access-Control-Max-Age: 86400</pre>
+    HTTP/1.1 200 OK
+    Content-Length: 0
+    Connection: keep-alive
+    Access-Control-Allow-Origin: https://foo.bar.org
+    Access-Control-Allow-Methods: POST, GET, OPTIONS, DELETE
+    Access-Control-Allow-Headers: Content-Type, x-requested-with
+    Access-Control-Max-Age: 86400
 
-<p>If the requested method isn't supported, the server will respond with an error.</p>
+If the requested method isn't supported, the server will respond with an error.
 
-<h2 id="Specifications">Specifications</h2>
+## Specifications
 
 {{Specifications}}
 
-<h2 id="Browser_compatibility">Browser compatibility</h2>
+## Browser compatibility
 
-<p>{{Compat}}</p>
+{{Compat}}
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
- <li>{{HTTPHeader("Access-Control-Allow-Origin")}}</li>
- <li>{{HTTPHeader("Access-Control-Expose-Headers")}}</li>
- <li>{{HTTPHeader("Access-Control-Allow-Methods")}}</li>
- <li>{{HTTPHeader("Access-Control-Request-Headers")}}</li>
-</ul>
+- {{HTTPHeader("Access-Control-Allow-Origin")}}
+- {{HTTPHeader("Access-Control-Expose-Headers")}}
+- {{HTTPHeader("Access-Control-Allow-Methods")}}
+- {{HTTPHeader("Access-Control-Request-Headers")}}
diff --git a/files/en-us/web/http/headers/access-control-allow-methods/index.md b/files/en-us/web/http/headers/access-control-allow-methods/index.md
index 86bed54020f073c..c7f620205f77ff8 100644
--- a/files/en-us/web/http/headers/access-control-allow-methods/index.md
+++ b/files/en-us/web/http/headers/access-control-allow-methods/index.md
@@ -2,17 +2,17 @@
 title: Access-Control-Allow-Methods
 slug: Web/HTTP/Headers/Access-Control-Allow-Methods
 tags:
-- CORS
-- HTTP
-- Reference
-- header
+  - CORS
+  - HTTP
+  - Reference
+  - header
 browser-compat: http.headers.Access-Control-Allow-Methods
 ---
-<div>{{HTTPSidebar}}</div>
+{{HTTPSidebar}}
 
-<p>The <strong><code>Access-Control-Allow-Methods</code></strong> response header
-  specifies the method or methods allowed when accessing the resource in response to a
-  {{glossary("preflight request")}}.</p>
+The **`Access-Control-Allow-Methods`** response header
+specifies the method or methods allowed when accessing the resource in response to a
+{{glossary("preflight request")}}.
 
 <table class="properties">
   <tbody>
@@ -27,44 +27,40 @@ browser-compat: http.headers.Access-Control-Allow-Methods
   </tbody>
 </table>
 
-<h2 id="Syntax">Syntax</h2>
+## Syntax
 
-<pre class="brush: html">Access-Control-Allow-Methods: &lt;method&gt;, &lt;method&gt;, ...
+```html
+Access-Control-Allow-Methods: <method>, <method>, ...
 Access-Control-Allow-Methods: *
-</pre>
+```
 
-<h2 id="Directives">Directives</h2>
+## Directives
 
-<dl>
-  <dt>&lt;method&gt;</dt>
-  <dd>Comma-delimited list of the allowed <a href="/en-US/docs/Web/HTTP/Methods">HTTP
-      request methods</a>.</dd>
-  <dt><code>*</code> (wildcard)</dt>
-  <dd>The value "<code>*</code>" only counts as a special wildcard value for requests
-    without credentials (requests without <a href="/en-US/docs/Web/HTTP/Cookies">HTTP
-      cookies</a> or HTTP authentication information). In requests with credentials, it is
-    treated as the literal method name "<code>*</code>" without special semantics.</dd>
-</dl>
+- \<method>
+  - : Comma-delimited list of the allowed [HTTP
+    request methods](/en-US/docs/Web/HTTP/Methods).
+- `*` (wildcard)
+  - : The value "`*`" only counts as a special wildcard value for requests
+    without credentials (requests without [HTTP
+    cookies](/en-US/docs/Web/HTTP/Cookies) or HTTP authentication information). In requests with credentials, it is
+    treated as the literal method name "`*`" without special semantics.
 
-<h2 id="Examples">Examples</h2>
+## Examples
 
-<pre>Access-Control-Allow-Methods: POST, GET, OPTIONS
-Access-Control-Allow-Methods: *
-</pre>
+    Access-Control-Allow-Methods: POST, GET, OPTIONS
+    Access-Control-Allow-Methods: *
 
-<h2 id="Specifications">Specifications</h2>
+## Specifications
 
 {{Specifications}}
 
-<h2 id="Browser_compatibility">Browser compatibility</h2>
+## Browser compatibility
 
-<p>{{Compat}}</p>
+{{Compat}}
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
-  <li>{{HTTPHeader("Access-Control-Allow-Origin")}}</li>
-  <li>{{HTTPHeader("Access-Control-Expose-Headers")}}</li>
-  <li>{{HTTPHeader("Access-Control-Allow-Headers")}}</li>
-  <li>{{HTTPHeader("Access-Control-Request-Method")}}</li>
-</ul>
+- {{HTTPHeader("Access-Control-Allow-Origin")}}
+- {{HTTPHeader("Access-Control-Expose-Headers")}}
+- {{HTTPHeader("Access-Control-Allow-Headers")}}
+- {{HTTPHeader("Access-Control-Request-Method")}}
diff --git a/files/en-us/web/http/headers/access-control-allow-origin/index.md b/files/en-us/web/http/headers/access-control-allow-origin/index.md
index 6b5ab046e57b19b..ad74641282489a9 100644
--- a/files/en-us/web/http/headers/access-control-allow-origin/index.md
+++ b/files/en-us/web/http/headers/access-control-allow-origin/index.md
@@ -16,77 +16,73 @@ tags:
   - origin
 browser-compat: http.headers.Access-Control-Allow-Origin
 ---
-<div>{{HTTPSidebar}}</div>
+{{HTTPSidebar}}
 
-<p>The <code><strong>Access-Control-Allow-Origin</strong></code> response header indicates whether the response can be shared with requesting code from the given {{glossary("origin")}}.</p>
+The **`Access-Control-Allow-Origin`** response header indicates whether the response can be shared with requesting code from the given {{glossary("origin")}}.
 
 <table class="properties">
- <tbody>
-  <tr>
-   <th scope="row">Header type</th>
-   <td>{{Glossary("Response header")}}</td>
-  </tr>
-  <tr>
-   <th scope="row">{{Glossary("Forbidden header name")}}</th>
-   <td>no</td>
-  </tr>
- </tbody>
+  <tbody>
+    <tr>
+      <th scope="row">Header type</th>
+      <td>{{Glossary("Response header")}}</td>
+    </tr>
+    <tr>
+      <th scope="row">{{Glossary("Forbidden header name")}}</th>
+      <td>no</td>
+    </tr>
+  </tbody>
 </table>
 
-<h2 id="Syntax">Syntax</h2>
+## Syntax
 
-<pre class="brush: html">Access-Control-Allow-Origin: *
-Access-Control-Allow-Origin: &lt;origin&gt;
+```html
+Access-Control-Allow-Origin: *
+Access-Control-Allow-Origin: <origin>
 Access-Control-Allow-Origin: null
-</pre>
+```
 
-<h2 id="Directives">Directives</h2>
+## Directives
 
-<dl>
- <dt><code>*</code></dt>
- <dd>For requests <em>without credentials</em>, the literal value "<code>*</code>" can be specified, as a wildcard; the value tells browsers to allow requesting code from any origin to access the resource. Attempting to use the wildcard with credentials <a href="/en-US/docs/Web/HTTP/CORS/Errors/CORSNotSupportingCredentials">will result in an error</a>.</dd>
- <dt><code>&lt;origin&gt;</code></dt>
- <dd>Specifies an origin. Only a single origin can be specified. If the server supports clients from multiple origins, it must return the origin for the specific client making the request.</dd>
- <dt><code>null</code></dt>
- <dd>Specifies the origin "null".
-  <div class="notecard note">
-    <p><strong>Note:</strong> <code>null</code> <a href="https://w3c.github.io/webappsec-cors-for-developers/#avoid-returning-access-control-allow-origin-null">should not be used</a>: "It may seem safe to return <code>Access-Control-Allow-Origin: "null"</code>, but the serialization of the Origin of any resource that uses a non-hierarchical scheme (such as <code>data:</code> or <code>file:</code>) and sandboxed documents is defined to be "null". Many User Agents will grant such documents access to a response with an <code>Access-Control-Allow-Origin: "null"</code> header, and any origin can create a hostile document with a "null" Origin. The "null" value for the ACAO header should therefore be avoided."</p>
-  </div>
- </dd>
-</dl>
+- `*`
+  - : For requests _without credentials_, the literal value "`*`" can be specified, as a wildcard; the value tells browsers to allow requesting code from any origin to access the resource. Attempting to use the wildcard with credentials [will result in an error](/en-US/docs/Web/HTTP/CORS/Errors/CORSNotSupportingCredentials).
+- `<origin>`
+  - : Specifies an origin. Only a single origin can be specified. If the server supports clients from multiple origins, it must return the origin for the specific client making the request.
+- `null`
 
-<h2 id="Examples">Examples</h2>
+  - : Specifies the origin "null".
 
-<p>A response that tells the browser to allow code from any origin to access a resource will include the following:</p>
+    > **Note:** `null` [should not be used](https://w3c.github.io/webappsec-cors-for-developers/#avoid-returning-access-control-allow-origin-null): "It may seem safe to return `Access-Control-Allow-Origin: "null"`, but the serialization of the Origin of any resource that uses a non-hierarchical scheme (such as `data:` or `file:`) and sandboxed documents is defined to be "null". Many User Agents will grant such documents access to a response with an `Access-Control-Allow-Origin: "null"` header, and any origin can create a hostile document with a "null" Origin. The "null" value for the ACAO header should therefore be avoided."
 
-<pre>Access-Control-Allow-Origin: *</pre>
+## Examples
 
-<p>A response that tells the browser to allow requesting code from the origin <code>https://developer.mozilla.org</code> to access a resource will include the following:</p>
+A response that tells the browser to allow code from any origin to access a resource will include the following:
 
-<pre>Access-Control-Allow-Origin: https://developer.mozilla.org</pre>
+    Access-Control-Allow-Origin: *
 
-<p>Limiting the possible <code>Access-Control-Allow-Origin</code> values to a set of allowed origins requires code on the server side to check the value of the {{HTTPHeader("Origin")}} request header, compare that to a list of allowed origins, and then if the {{HTTPHeader("Origin")}} value is in the list, to set the <code>Access-Control-Allow-Origin</code> value to the same value as the {{HTTPHeader("Origin")}} value.</p>
+A response that tells the browser to allow requesting code from the origin `https://developer.mozilla.org` to access a resource will include the following:
 
-<h3 id="CORS_and_caching">CORS and caching</h3>
+    Access-Control-Allow-Origin: https://developer.mozilla.org
 
-<p>If the server sends a response with an <code>Access-Control-Allow-Origin</code> value that is an explicit origin (rather than the "<code>*</code>" wildcard), then the response should also include a {{HTTPHeader("Vary")}} response header with the value <code>Origin</code> — to indicate to browsers that server responses can differ based on the value of the <code>Origin</code> request header.</p>
+Limiting the possible `Access-Control-Allow-Origin` values to a set of allowed origins requires code on the server side to check the value of the {{HTTPHeader("Origin")}} request header, compare that to a list of allowed origins, and then if the {{HTTPHeader("Origin")}} value is in the list, to set the `Access-Control-Allow-Origin` value to the same value as the {{HTTPHeader("Origin")}} value.
 
-<pre>Access-Control-Allow-Origin: https://developer.mozilla.org
-Vary: Origin</pre>
+### CORS and caching
 
-<h2 id="Specifications">Specifications</h2>
+If the server sends a response with an `Access-Control-Allow-Origin` value that is an explicit origin (rather than the "`*`" wildcard), then the response should also include a {{HTTPHeader("Vary")}} response header with the value `Origin` — to indicate to browsers that server responses can differ based on the value of the `Origin` request header.
+
+    Access-Control-Allow-Origin: https://developer.mozilla.org
+    Vary: Origin
+
+## Specifications
 
 {{Specifications}}
 
-<h2 id="Browser_compatibility">Browser compatibility</h2>
+## Browser compatibility
 
-<p>{{Compat}}</p>
+{{Compat}}
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
- <li>{{HTTPHeader("Origin")}}</li>
- <li>{{HTTPHeader("Vary")}}</li>
- <li><a href="/en-US/docs/Web/HTTP/CORS">Cross-Origin Resource Sharing (CORS)</a></li>
- <li>{{httpheader("Cross-Origin-Resource-Policy")}}</li>
-</ul>
+- {{HTTPHeader("Origin")}}
+- {{HTTPHeader("Vary")}}
+- [Cross-Origin Resource Sharing (CORS)](/en-US/docs/Web/HTTP/CORS)
+- {{httpheader("Cross-Origin-Resource-Policy")}}
diff --git a/files/en-us/web/http/headers/access-control-expose-headers/index.md b/files/en-us/web/http/headers/access-control-expose-headers/index.md
index e308acdefe0818b..b722dab1b290075 100644
--- a/files/en-us/web/http/headers/access-control-expose-headers/index.md
+++ b/files/en-us/web/http/headers/access-control-expose-headers/index.md
@@ -8,70 +8,67 @@ tags:
   - header
 browser-compat: http.headers.Access-Control-Expose-Headers
 ---
-<div>{{HTTPSidebar}}</div>
+{{HTTPSidebar}}
 
-<p>The <strong><code>Access-Control-Expose-Headers</code></strong> response header allows a server to indicate which response headers should be made available to scripts running in the browser, in response to a cross-origin request.</p>
+The **`Access-Control-Expose-Headers`** response header allows a server to indicate which response headers should be made available to scripts running in the browser, in response to a cross-origin request.
 
-<p>Only the {{Glossary("CORS-safelisted response header", "CORS-safelisted response headers")}} are exposed by default. For clients to be able to access other headers, the server must list them using the <code>Access-Control-Expose-Headers</code> header.</p>
+Only the {{Glossary("CORS-safelisted response header", "CORS-safelisted response headers")}} are exposed by default. For clients to be able to access other headers, the server must list them using the `Access-Control-Expose-Headers` header.
 
 <table class="properties">
- <tbody>
-  <tr>
-   <th scope="row">Header type</th>
-   <td>{{Glossary("Response header")}}</td>
-  </tr>
-  <tr>
-   <th scope="row">{{Glossary("Forbidden header name")}}</th>
-   <td>no</td>
-  </tr>
- </tbody>
+  <tbody>
+    <tr>
+      <th scope="row">Header type</th>
+      <td>{{Glossary("Response header")}}</td>
+    </tr>
+    <tr>
+      <th scope="row">{{Glossary("Forbidden header name")}}</th>
+      <td>no</td>
+    </tr>
+  </tbody>
 </table>
 
-<h2 id="Syntax">Syntax</h2>
+## Syntax
 
-<pre class="brush: html">Access-Control-Expose-Headers: [<em>&lt;header-name&gt;</em>[, <em>&lt;header-name&gt;</em>]*]
+```html
+Access-Control-Expose-Headers: [<header-name>[, <header-name>]*]
 Access-Control-Expose-Headers: *
-</pre>
+```
 
-<h2 id="Directives">Directives</h2>
+## Directives
 
-<dl>
- <dt>&lt;header-name&gt;</dt>
- <dd>A list of zero or more comma-separated <a href="/en-US/docs/Web/HTTP/Headers">header names</a> that clients are allowed to access from a response. These are <em>in addition</em> to the {{Glossary("CORS-safelisted response header", "CORS-safelisted response headers")}}.</dd>
- <dt><code>*</code> (wildcard)</dt>
- <dd>The value "<code>*</code>" only counts as a special wildcard value for requests without credentials (requests without <a href="/en-US/docs/Web/HTTP/Cookies">HTTP cookies</a> or HTTP authentication information). In requests with credentials, it is treated as the literal header name "<code>*</code>" without special semantics.<br>
- Note that the {{HTTPHeader("Authorization")}} header can't be wildcarded and always needs to be listed explicitly.</dd>
-</dl>
+- \<header-name>
+  - : A list of zero or more comma-separated [header names](/en-US/docs/Web/HTTP/Headers) that clients are allowed to access from a response. These are _in addition_ to the {{Glossary("CORS-safelisted response header", "CORS-safelisted response headers")}}.
+- `*` (wildcard)
+  - : The value "`*`" only counts as a special wildcard value for requests without credentials (requests without [HTTP cookies](/en-US/docs/Web/HTTP/Cookies) or HTTP authentication information). In requests with credentials, it is treated as the literal header name "`*`" without special semantics.
+    Note that the {{HTTPHeader("Authorization")}} header can't be wildcarded and always needs to be listed explicitly.
 
-<h2 id="Examples">Examples</h2>
+## Examples
 
-<p>The {{Glossary("CORS-safelisted response header", "CORS-safelisted response headers")}} are: {{HTTPHeader("Cache-Control")}}, {{HTTPHeader("Content-Language")}}, {{HTTPHeader("Content-Length")}}, {{HTTPHeader("Content-Type")}}, {{HTTPHeader("Expires")}}, {{HTTPHeader("Last-Modified")}}, {{HTTPHeader("Pragma")}}. To expose a non-CORS-safelisted response header, you can specify:</p>
+The {{Glossary("CORS-safelisted response header", "CORS-safelisted response headers")}} are: {{HTTPHeader("Cache-Control")}}, {{HTTPHeader("Content-Language")}}, {{HTTPHeader("Content-Length")}}, {{HTTPHeader("Content-Type")}}, {{HTTPHeader("Expires")}}, {{HTTPHeader("Last-Modified")}}, {{HTTPHeader("Pragma")}}. To expose a non-CORS-safelisted response header, you can specify:
 
-<pre>Access-Control-Expose-Headers: Content-Encoding</pre>
+    Access-Control-Expose-Headers: Content-Encoding
 
-<p>To additionally expose a custom header, like <code>X-Kuma-Revision</code>, you can specify multiple headers separated by a comma:</p>
+To additionally expose a custom header, like `X-Kuma-Revision`, you can specify multiple headers separated by a comma:
 
-<pre>Access-Control-Expose-Headers: Content-Encoding, X-Kuma-Revision</pre>
+    Access-Control-Expose-Headers: Content-Encoding, X-Kuma-Revision
 
-<p>For requests without credentials, a server can also respond with a wildcard value:</p>
+For requests without credentials, a server can also respond with a wildcard value:
 
-<pre>Access-Control-Expose-Headers: *</pre>
+    Access-Control-Expose-Headers: *
 
-<p>However, this won't wildcard the {{HTTPHeader("Authorization")}} header, so if you need to expose that, you will need to list it explicitly:</p>
+However, this won't wildcard the {{HTTPHeader("Authorization")}} header, so if you need to expose that, you will need to list it explicitly:
 
-<pre>Access-Control-Expose-Headers: *, Authorization</pre>
+    Access-Control-Expose-Headers: *, Authorization
 
-<h2 id="Specifications">Specifications</h2>
+## Specifications
 
 {{Specifications}}
 
-<h2 id="Browser_compatibility">Browser compatibility</h2>
+## Browser compatibility
 
-<p>{{Compat}}</p>
+{{Compat}}
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
- <li>{{HTTPHeader("Access-Control-Allow-Headers")}}</li>
- <li>{{HTTPHeader("Access-Control-Allow-Origin")}}</li>
-</ul>
+- {{HTTPHeader("Access-Control-Allow-Headers")}}
+- {{HTTPHeader("Access-Control-Allow-Origin")}}
diff --git a/files/en-us/web/http/headers/access-control-max-age/index.md b/files/en-us/web/http/headers/access-control-max-age/index.md
index bd369813bc6955e..041652984632041 100644
--- a/files/en-us/web/http/headers/access-control-max-age/index.md
+++ b/files/en-us/web/http/headers/access-control-max-age/index.md
@@ -8,57 +8,54 @@ tags:
   - header
 browser-compat: http.headers.Access-Control-Max-Age
 ---
-<p>{{HTTPSidebar}}</p>
+{{HTTPSidebar}}
 
-<p>The <strong><code>Access-Control-Max-Age</code></strong> response header indicates how long the results of a {{glossary("preflight request")}} (that is the information contained in the {{HTTPHeader("Access-Control-Allow-Methods")}} and {{HTTPHeader("Access-Control-Allow-Headers")}} headers) can be cached.</p>
+The **`Access-Control-Max-Age`** response header indicates how long the results of a {{glossary("preflight request")}} (that is the information contained in the {{HTTPHeader("Access-Control-Allow-Methods")}} and {{HTTPHeader("Access-Control-Allow-Headers")}} headers) can be cached.
 
 <table class="properties">
- <tbody>
-  <tr>
-   <th scope="row">Header type</th>
-   <td>{{Glossary("Response header")}}</td>
-  </tr>
-  <tr>
-   <th scope="row">{{Glossary("Forbidden header name")}}</th>
-   <td>no</td>
-  </tr>
- </tbody>
+  <tbody>
+    <tr>
+      <th scope="row">Header type</th>
+      <td>{{Glossary("Response header")}}</td>
+    </tr>
+    <tr>
+      <th scope="row">{{Glossary("Forbidden header name")}}</th>
+      <td>no</td>
+    </tr>
+  </tbody>
 </table>
 
-<h2 id="Syntax">Syntax</h2>
+## Syntax
 
-<pre class="brush: html">Access-Control-Max-Age: &lt;delta-seconds&gt;
-</pre>
+```html
+Access-Control-Max-Age: <delta-seconds>
+```
 
-<h2 id="Directives">Directives</h2>
+## Directives
 
-<dl>
- <dt>&lt;delta-seconds&gt;</dt>
- <dd>Maximum number of seconds the results can be cached.<br>
- Firefox <a href="https://searchfox.org/mozilla-central/source/netwerk/protocol/http/nsCORSListenerProxy.cpp#1118">caps this at 24 hours</a> (86400 seconds).<br>
- Chromium (prior to v76) <a href="https://cs.chromium.org/chromium/src/services/network/public/cpp/cors/preflight_result.cc?l=36&amp;rcl=52002151773d8cd9ffc5f557cd7cc880fddcae3e">caps at 10 minutes</a> (600 seconds).<br>
- Chromium (starting in v76) <a href="https://cs.chromium.org/chromium/src/services/network/public/cpp/cors/preflight_result.cc?l=31&amp;rcl=49e7c0b4886cac1f3d09dc046bd528c9c811a0fa">caps at 2 hours</a> (7200 seconds).<br>
- Chromium also specifies a default value of 5 seconds.<br>
- A value of <strong>-1</strong> will disable caching, requiring a preflight OPTIONS check for all calls.</dd>
-</dl>
+- \<delta-seconds>
+  - : Maximum number of seconds the results can be cached.
+    Firefox [caps this at 24 hours](https://searchfox.org/mozilla-central/source/netwerk/protocol/http/nsCORSListenerProxy.cpp#1118) (86400 seconds).
+    Chromium (prior to v76) [caps at 10 minutes](https://cs.chromium.org/chromium/src/services/network/public/cpp/cors/preflight_result.cc?l=36&rcl=52002151773d8cd9ffc5f557cd7cc880fddcae3e) (600 seconds).
+    Chromium (starting in v76) [caps at 2 hours](https://cs.chromium.org/chromium/src/services/network/public/cpp/cors/preflight_result.cc?l=31&rcl=49e7c0b4886cac1f3d09dc046bd528c9c811a0fa) (7200 seconds).
+    Chromium also specifies a default value of 5 seconds.
+    A value of **-1** will disable caching, requiring a preflight OPTIONS check for all calls.
 
-<h2 id="Examples">Examples</h2>
+## Examples
 
-<p>Cache results of a preflight request for 10 minutes:</p>
+Cache results of a preflight request for 10 minutes:
 
-<pre>Access-Control-Max-Age: 600 </pre>
+    Access-Control-Max-Age: 600
 
-<h2 id="Specifications">Specifications</h2>
+## Specifications
 
 {{Specifications}}
 
-<h2 id="Browser_compatibility">Browser compatibility</h2>
+## Browser compatibility
 
-<p>{{Compat}}</p>
+{{Compat}}
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
- <li>{{HTTPHeader("Access-Control-Allow-Headers")}}</li>
- <li>{{HTTPHeader("Access-Control-Allow-Methods")}}</li>
-</ul>
+- {{HTTPHeader("Access-Control-Allow-Headers")}}
+- {{HTTPHeader("Access-Control-Allow-Methods")}}
diff --git a/files/en-us/web/http/headers/access-control-request-headers/index.md b/files/en-us/web/http/headers/access-control-request-headers/index.md
index ced0a808e078cea..3ab9dfc53b559d0 100644
--- a/files/en-us/web/http/headers/access-control-request-headers/index.md
+++ b/files/en-us/web/http/headers/access-control-request-headers/index.md
@@ -8,49 +8,46 @@ tags:
   - header
 browser-compat: http.headers.Access-Control-Request-Headers
 ---
-<p>{{HTTPSidebar}}</p>
+{{HTTPSidebar}}
 
-<p>The <strong><code>Access-Control-Request-Headers</code></strong> request header is used by browsers when issuing a {{glossary("preflight request")}}, to let the server know which <a href="/en-US/docs/Web/HTTP/Headers">HTTP headers</a> the client might send when the actual request is made (such as with {{domxref("XMLHttpRequest.setRequestHeader()","setRequestHeader()")}}). This browser side header will be answered by the complementary server side header of {{HTTPHeader("Access-Control-Allow-Headers")}}.</p>
+The **`Access-Control-Request-Headers`** request header is used by browsers when issuing a {{glossary("preflight request")}}, to let the server know which [HTTP headers](/en-US/docs/Web/HTTP/Headers) the client might send when the actual request is made (such as with {{domxref("XMLHttpRequest.setRequestHeader()","setRequestHeader()")}}). This browser side header will be answered by the complementary server side header of {{HTTPHeader("Access-Control-Allow-Headers")}}.
 
 <table class="properties">
- <tbody>
-  <tr>
-   <th scope="row">Header type</th>
-   <td>{{Glossary("Request header")}}</td>
-  </tr>
-  <tr>
-   <th scope="row">{{Glossary("Forbidden header name")}}</th>
-   <td>yes</td>
-  </tr>
- </tbody>
+  <tbody>
+    <tr>
+      <th scope="row">Header type</th>
+      <td>{{Glossary("Request header")}}</td>
+    </tr>
+    <tr>
+      <th scope="row">{{Glossary("Forbidden header name")}}</th>
+      <td>yes</td>
+    </tr>
+  </tbody>
 </table>
 
-<h2 id="Syntax">Syntax</h2>
+## Syntax
 
-<pre class="brush: html">Access-Control-Request-Headers: &lt;header-name&gt;, &lt;header-name&gt;, ...
-</pre>
+```html
+Access-Control-Request-Headers: <header-name>, <header-name>, ...
+```
 
-<h2 id="Directives">Directives</h2>
+## Directives
 
-<dl>
- <dt>&lt;header-name&gt;</dt>
- <dd>A comma-delimited list of <a href="/en-US/docs/Web/HTTP/Headers">HTTP headers</a> that are included in the request.</dd>
-</dl>
+- \<header-name>
+  - : A comma-delimited list of [HTTP headers](/en-US/docs/Web/HTTP/Headers) that are included in the request.
 
-<h2 id="Examples">Examples</h2>
+## Examples
 
-<pre>Access-Control-Request-Headers: X-PINGOTHER, Content-Type</pre>
+    Access-Control-Request-Headers: X-PINGOTHER, Content-Type
 
-<h2 id="Specifications">Specifications</h2>
+## Specifications
 
 {{Specifications}}
 
-<h2 id="Browser_compatibility">Browser compatibility</h2>
+## Browser compatibility
 
-<p>{{Compat}}</p>
+{{Compat}}
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
- <li>{{HTTPHeader("Access-Control-Request-Method")}}</li>
-</ul>
+- {{HTTPHeader("Access-Control-Request-Method")}}
diff --git a/files/en-us/web/http/headers/access-control-request-method/index.md b/files/en-us/web/http/headers/access-control-request-method/index.md
index 9cfc2c6b0d30be8..2d7d92ed54bb51a 100644
--- a/files/en-us/web/http/headers/access-control-request-method/index.md
+++ b/files/en-us/web/http/headers/access-control-request-method/index.md
@@ -2,19 +2,19 @@
 title: Access-Control-Request-Method
 slug: Web/HTTP/Headers/Access-Control-Request-Method
 tags:
-- CORS
-- HTTP
-- Reference
-- header
+  - CORS
+  - HTTP
+  - Reference
+  - header
 browser-compat: http.headers.Access-Control-Request-Method
 ---
-<div>{{HTTPSidebar}}</div>
+{{HTTPSidebar}}
 
-<p>The <strong><code>Access-Control-Request-Method</code></strong> request header is used
-  by browsers when issuing a {{glossary("preflight request")}}, to let the server know
-  which <a href="/en-US/docs/Web/HTTP/Methods">HTTP method</a> will be used when the
-  actual request is made. This header is necessary as the preflight request is always an
-  {{HTTPMethod("OPTIONS")}} and doesn't use the same method as the actual request.</p>
+The **`Access-Control-Request-Method`** request header is used
+by browsers when issuing a {{glossary("preflight request")}}, to let the server know
+which [HTTP method](/en-US/docs/Web/HTTP/Methods) will be used when the
+actual request is made. This header is necessary as the preflight request is always an
+{{HTTPMethod("OPTIONS")}} and doesn't use the same method as the actual request.
 
 <table class="properties">
   <tbody>
@@ -29,34 +29,30 @@ browser-compat: http.headers.Access-Control-Request-Method
   </tbody>
 </table>
 
-<h2 id="Syntax">Syntax</h2>
+## Syntax
 
-<pre class="brush: html">Access-Control-Request-Method: &lt;method&gt;
-</pre>
+```html
+Access-Control-Request-Method: <method>
+```
 
-<h2 id="Directives">Directives</h2>
+## Directives
 
-<dl>
-  <dt>&lt;method&gt;</dt>
-  <dd>One of the <a href="/en-US/docs/Web/HTTP/Methods">HTTP request methods</a>, for
+- \<method>
+  - : One of the [HTTP request methods](/en-US/docs/Web/HTTP/Methods), for
     example {{HTTPMethod("GET")}}, {{HTTPMethod("POST")}}, or {{HTTPMethod("DELETE")}}.
-  </dd>
-</dl>
 
-<h2 id="Examples">Examples</h2>
+## Examples
 
-<pre>Access-Control-Request-Method: POST</pre>
+    Access-Control-Request-Method: POST
 
-<h2 id="Specifications">Specifications</h2>
+## Specifications
 
 {{Specifications}}
 
-<h2 id="Browser_compatibility">Browser compatibility</h2>
+## Browser compatibility
 
-<p>{{Compat}}</p>
+{{Compat}}
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
-  <li>{{HTTPHeader("Access-Control-Request-Headers")}}</li>
-</ul>
+- {{HTTPHeader("Access-Control-Request-Headers")}}
diff --git a/files/en-us/web/http/headers/age/index.md b/files/en-us/web/http/headers/age/index.md
index c9fc6575d7f27d1..ea16135e240f7f3 100644
--- a/files/en-us/web/http/headers/age/index.md
+++ b/files/en-us/web/http/headers/age/index.md
@@ -2,21 +2,21 @@
 title: Age
 slug: Web/HTTP/Headers/Age
 tags:
-- Caching
-- HTTP
-- Response
-- header
+  - Caching
+  - HTTP
+  - Response
+  - header
 browser-compat: http.headers.Age
 ---
-<div>{{HTTPSidebar}}</div>
+{{HTTPSidebar}}
 
-<p>The <code><strong>Age</strong></code> header contains the time in seconds the object
-  has been in a proxy cache.</p>
+The **`Age`** header contains the time in seconds the object
+has been in a proxy cache.
 
-<p>The <code>Age</code> header is usually close to zero. If it is <code>Age: 0</code>, it
-  was probably just fetched from the origin server; otherwise It is usually calculated as
-  a difference between the proxy's current date and the {{HTTPHeader("Date")}} general
-  header included in the HTTP response.</p>
+The `Age` header is usually close to zero. If it is `Age: 0`, it
+was probably just fetched from the origin server; otherwise It is usually calculated as
+a difference between the proxy's current date and the {{HTTPHeader("Date")}} general
+header included in the HTTP response.
 
 <table class="properties">
   <tbody>
@@ -31,36 +31,31 @@ browser-compat: http.headers.Age
   </tbody>
 </table>
 
-<h2 id="Syntax">Syntax</h2>
+## Syntax
 
-<pre class="brush: html">Age: &lt;delta-seconds&gt;
-</pre>
+```html
+Age: <delta-seconds>
+```
 
-<h2 id="Directives">Directives</h2>
+## Directives
 
-<dl>
-  <dt>&lt;delta-seconds&gt;</dt>
-  <dd>
-    <p>A non-negative integer, representing time in seconds the object has been in a proxy
-      cache.</p>
-  </dd>
-</dl>
+- \<delta-seconds>
+  - : A non-negative integer, representing time in seconds the object has been in a proxy
+    cache.
 
-<h2 id="Examples">Examples</h2>
+## Examples
 
-<pre>Age: 24</pre>
+    Age: 24
 
-<h2 id="Specifications">Specifications</h2>
+## Specifications
 
 {{Specifications}}
 
-<h2 id="Browser_compatibility">Browser compatibility</h2>
+## Browser compatibility
 
-<p>{{Compat}}</p>
+{{Compat}}
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
-  <li>{{HTTPHeader("Cache-Control")}}</li>
-  <li>{{HTTPHeader("Expires")}}</li>
-</ul>
+- {{HTTPHeader("Cache-Control")}}
+- {{HTTPHeader("Expires")}}
diff --git a/files/en-us/web/http/headers/allow/index.md b/files/en-us/web/http/headers/allow/index.md
index 177096705afb8b1..f52086fa2a4057e 100644
--- a/files/en-us/web/http/headers/allow/index.md
+++ b/files/en-us/web/http/headers/allow/index.md
@@ -7,59 +7,47 @@ tags:
   - Response header
   - Reference
 ---
-<div>{{HTTPSidebar}}</div>
+{{HTTPSidebar}}
 
-<p>The <code><strong>Allow</strong></code> header lists the set of methods supported by a resource.</p>
+The **`Allow`** header lists the set of methods supported by a resource.
 
-<p>This header must be sent if the server responds with a {{HTTPStatus("405")}} <code>Method Not Allowed</code> status code to indicate which request methods can be used. An empty <code>Allow</code> header indicates that the resource allows no request methods, which might occur temporarily for a given resource, for example.</p>
+This header must be sent if the server responds with a {{HTTPStatus("405")}} `Method Not Allowed` status code to indicate which request methods can be used. An empty `Allow` header indicates that the resource allows no request methods, which might occur temporarily for a given resource, for example.
 
 <table class="properties">
- <tbody>
-  <tr>
-   <th scope="row">Header type</th>
-   <td>{{Glossary("Response header")}} </td>
-  </tr>
-  <tr>
-   <th scope="row">{{Glossary("Forbidden header name")}}</th>
-   <td>no</td>
-  </tr>
- </tbody>
+  <tbody>
+    <tr>
+      <th scope="row">Header type</th>
+      <td>{{Glossary("Response header")}}</td>
+    </tr>
+    <tr>
+      <th scope="row">{{Glossary("Forbidden header name")}}</th>
+      <td>no</td>
+    </tr>
+  </tbody>
 </table>
 
-<h2 id="Syntax">Syntax</h2>
+## Syntax
 
-<pre class="brush: html">Allow: &lt;http-methods&gt;
-</pre>
+```html
+Allow: <http-methods>
+```
 
-<h2 id="Directives">Directives</h2>
+## Directives
 
-<dl>
- <dt>&lt;http-methods&gt;</dt>
- <dd>The comma-separated list of allowed <a href="/en-US/docs/Web/HTTP/Methods">HTTP request methods</a>.</dd>
-</dl>
+- \<http-methods>
+  - : The comma-separated list of allowed [HTTP request methods](/en-US/docs/Web/HTTP/Methods).
 
-<h2 id="Examples">Examples</h2>
+## Examples
 
-<pre>Allow: GET, POST, HEAD</pre>
+    Allow: GET, POST, HEAD
 
-<h2 id="Specifications">Specifications</h2>
+## Specifications
 
-<table class="standard-table">
- <thead>
-  <tr>
-   <th scope="col">Specification</th>
-   <th scope="col">Title</th>
-  </tr>
-  <tr>
-   <td>{{RFC("7231", "Allow", "7.4.1")}}</td>
-   <td>Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content</td>
-  </tr>
- </thead>
-</table>
+| Specification                                | Title                                                         |
+| -------------------------------------------- | ------------------------------------------------------------- |
+| {{RFC("7231", "Allow", "7.4.1")}} | Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content |
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
- <li>{{HTTPStatus("405")}}</li>
- <li>{{HTTPHeader("Server")}}</li>
-</ul>
+- {{HTTPStatus("405")}}
+- {{HTTPHeader("Server")}}
diff --git a/files/en-us/web/http/headers/alt-svc/index.md b/files/en-us/web/http/headers/alt-svc/index.md
index f8076246d1bd2fe..8d0ca5313bb0543 100644
--- a/files/en-us/web/http/headers/alt-svc/index.md
+++ b/files/en-us/web/http/headers/alt-svc/index.md
@@ -2,65 +2,62 @@
 title: Alt-Svc
 slug: Web/HTTP/Headers/Alt-Svc
 tags:
-- HTTP
-- HTTP Header
-- NeedsCompatTable
-- Reference
+  - HTTP
+  - HTTP Header
+  - NeedsCompatTable
+  - Reference
 browser-compat: http.headers.Alt-Svc
 ---
-<div>{{HTTPSidebar}}</div>
-
-<p>The {{HTTPHeader("Alt-Svc")}} HTTP header allows a server to indicate that a particular resource should be loaded from a different server — while still appearing to the user as if were loaded from the same server.</p>
-
-<h2 id="Syntax">Syntax</h2>
-
-<pre
-  class="brush: html">Alt-Svc: clear
-Alt-Svc: <var>&lt;protocol-id&gt;</var>=<em>&lt;alt-authority&gt;</em>; ma=<var>&lt;max-age&gt;</var>
-Alt-Svc: <var>&lt;protocol-id&gt;</var>=<em>&lt;alt-authority&gt;</em>; ma=<var>&lt;max-age&gt;</var>; persist=1</pre>
-
-<dl>
-  <dt><code>clear</code></dt>
-  <dd>The special value ''clear" indicates that the origin requests all alternatives for
-    that origin to be invalidated.</dd>
-  <dt><code>&lt;protocol-id&gt;</code></dt>
-  <dd>The {{Glossary("ALPN")}} protocol identifier. Examples include h2 for HTTP/2 and
-    h3-25 for draft 25 of the HTTP/3 protocol.</dd>
-  <dt><code>&lt;alt-authority&gt;</code></dt>
-  <dd>The quoted string specifying the alternative authority which consists of an optional
-    host override, a colon, and a mandatory port number.</dd>
-  <dt><code>ma=&lt;max-age&gt;</code>{{Optional_Inline}}</dt>
-  <dd>The number of seconds for which the alternative service is considered fresh. If
+{{HTTPSidebar}}
+
+The {{HTTPHeader("Alt-Svc")}} HTTP header allows a server to indicate that a particular resource should be loaded from a different server — while still appearing to the user as if were loaded from the same server.
+
+## Syntax
+
+```html
+Alt-Svc: clear
+Alt-Svc: <protocol-id>=<alt-authority>; ma=<max-age>
+Alt-Svc: <protocol-id>=<alt-authority>; ma=<max-age>; persist=1
+```
+
+- `clear`
+  - : The special value ''clear" indicates that the origin requests all alternatives for
+    that origin to be invalidated.
+- `<protocol-id>`
+  - : The {{Glossary("ALPN")}} protocol identifier. Examples include h2 for HTTP/2 and
+    h3-25 for draft 25 of the HTTP/3 protocol.
+- `<alt-authority>`
+  - : The quoted string specifying the alternative authority which consists of an optional
+    host override, a colon, and a mandatory port number.
+- `ma=<max-age>`{{Optional_Inline}}
+  - : The number of seconds for which the alternative service is considered fresh. If
     omitted, it defaults to 24 hours. Alternative service entries can be cached for up to
-    <em>&lt;max-age&gt;</em> seconds, minus the age of the response (from the {{
+    _\<max-age>_ seconds, minus the age of the response (from the {{
     httpheader("Age") }} header). If the cached entry expires, the client can no longer
-    use this alternative service for new connections.</dd>
-  <dt><code>persist=1</code>{{Optional_Inline}}</dt>
-  <dd>Usually cached alternative service entries are cleared on network configuration
+    use this alternative service for new connections.
+- `persist=1`{{Optional_Inline}}
+  - : Usually cached alternative service entries are cleared on network configuration
     changes. Use of the persist=1 parameter ensures that the entry is not deleted through
-    such changes.</dd>
-</dl>
+    such changes.
 
-<p>Multiple entries can be specified in a single <code>Alt-Svc</code> header using comma
-  as separator. In that case, early entries are considered more preferable.</p>
+Multiple entries can be specified in a single `Alt-Svc` header using comma
+as separator. In that case, early entries are considered more preferable.
 
-<h2 id="Example">Example</h2>
+## Example
 
-<pre>Alt-Svc: h2=":443"; ma=2592000;
-Alt-Svc: h2=":443"; ma=2592000; persist=1
-Alt-Svc: h2="alt.example.com:443", h2=":443"
-Alt-Svc: h3-25=":443"; ma=3600, h2=":443"; ma=3600</pre>
+    Alt-Svc: h2=":443"; ma=2592000;
+    Alt-Svc: h2=":443"; ma=2592000; persist=1
+    Alt-Svc: h2="alt.example.com:443", h2=":443"
+    Alt-Svc: h3-25=":443"; ma=3600, h2=":443"; ma=3600
 
-<h2 id="Specifications">Specifications</h2>
+## Specifications
 
 {{Specifications}}
 
-<h2 id="Browser_compatibility">Browser compatibility</h2>
+## Browser compatibility
 
-<p>{{Compat}}</p>
+{{Compat}}
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
-  <li><a href="https://www.mnot.net/blog/2016/03/09/alt-svc"> Alternative Services</a> (article about <code>Alt-Svc</code> by HTTP Working Group chair Mark Nottingham)</li>
-</ul>
+- [Alternative Services](https://www.mnot.net/blog/2016/03/09/alt-svc) (article about `Alt-Svc` by HTTP Working Group chair Mark Nottingham)
diff --git a/files/en-us/web/http/headers/authorization/index.md b/files/en-us/web/http/headers/authorization/index.md
index 197ce2375b108e1..dc8cb2850ce23b9 100644
--- a/files/en-us/web/http/headers/authorization/index.md
+++ b/files/en-us/web/http/headers/authorization/index.md
@@ -8,12 +8,12 @@ tags:
   - Request header
   - header
 ---
-<div>{{HTTPSidebar}}</div>
+{{HTTPSidebar}}
 
-<p>The HTTP <strong><code>Authorization</code></strong> request header contains the
-  credentials to authenticate a user agent with a server, usually, but not
-  necessarily, after the server has responded with a {{HTTPStatus("401")}}
-  <code>Unauthorized</code> status and the {{HTTPHeader("WWW-Authenticate")}} header.</p>
+The HTTP **`Authorization`** request header contains the
+credentials to authenticate a user agent with a server, usually, but not
+necessarily, after the server has responded with a {{HTTPStatus("401")}}
+`Unauthorized` status and the {{HTTPHeader("WWW-Authenticate")}} header.
 
 <table class="properties">
   <tbody>
@@ -28,77 +28,55 @@ tags:
   </tbody>
 </table>
 
-<h2 id="Syntax">Syntax</h2>
-
-<pre class="brush: html">Authorization: &lt;type&gt; &lt;credentials&gt;</pre>
-
-<h2 id="Directives">Directives</h2>
-
-<dl>
-  <dt>&lt;type&gt;</dt>
-  <dd>
-    <p>The <a href="/en-US/docs/Web/HTTP/Authentication#authentication_schemes">Authentication type</a>, that is which algorithm will be used for authentication. A common type is <a href="/en-US/docs/Web/HTTP/Authentication#basic_authentication_scheme"><code>"Basic"</code></a>.</p>
-    <p>Other types common types can be found at the <a href="https://www.iana.org/assignments/http-authschemes/http-authschemes.xhtml">IANA registry of Authentication schemes</a>.</p>
-    <div class="notecard note">
-      <p>
-        <strong>Note:</strong> AWS S3 servers use a specific authentication,
-        <a href="https://docs.aws.amazon.com/AmazonS3/latest/API/sigv4-auth-using-authorization-header.html"><code>AWS4-HMAC-SHA256</code></a>.
-      </p>
-    </div>
-  </dd>
-  <dt>&lt;credentials&gt;</dt>
-  <dd>
-    If the <code>"Basic"</code> authentication scheme is used,
+## Syntax
+
+```html
+Authorization: <type> <credentials>
+```
+
+## Directives
+
+- \<type>
+
+  - : The [Authentication type](/en-US/docs/Web/HTTP/Authentication#authentication_schemes), that is which algorithm will be used for authentication. A common type is [`"Basic"`](/en-US/docs/Web/HTTP/Authentication#basic_authentication_scheme).
+
+    Other types common types can be found at the [IANA registry of Authentication schemes](https://www.iana.org/assignments/http-authschemes/http-authschemes.xhtml).
+
+    > **Note:** AWS S3 servers use a specific authentication,
+    > [`AWS4-HMAC-SHA256`](https://docs.aws.amazon.com/AmazonS3/latest/API/sigv4-auth-using-authorization-header.html).
+
+- \<credentials>
+
+  - : If the `"Basic"` authentication scheme is used,
     the credentials are constructed
-    by first combining the username and the password with a colon (<code>aladdin:opensesame</code>),
-    then by encoding the resulting string in <a href="/en-US/docs/Glossary/Base64"><code>base64</code></a> (<code>YWxhZGRpbjpvcGVuc2VzYW1l</code>).
+    by first combining the username and the password with a colon (`aladdin:opensesame`),
+    then by encoding the resulting string in [`base64`](/en-US/docs/Glossary/Base64) (`YWxhZGRpbjpvcGVuc2VzYW1l`).
 
-    <div class="notecard note">
-      <p><strong>Note:</strong> {{Glossary("Base64")}}-encoding does not mean encryption or hashing!
-        As base64 is a reversible encoding,
-        this method is equally (in)secure
-        as sending the credentials in clear text.
-        So you should alwaysuse {{Glossary("HTTPS")}} in conjunction with <code>Basic</code> authentication.</p>
-    </div>
-  </dd>
-</dl>
+    > **Note:** {{Glossary("Base64")}}-encoding does not mean encryption or hashing!
+    > As base64 is a reversible encoding,
+    > this method is equally (in)secure
+    > as sending the credentials in clear text.
+    > So you should alwaysuse {{Glossary("HTTPS")}} in conjunction with `Basic` authentication.
 
-<h2 id="Examples">Examples</h2>
+## Examples
 
-<pre>Authorization: Basic YWxhZGRpbjpvcGVuc2VzYW1l
-</pre>
+    Authorization: Basic YWxhZGRpbjpvcGVuc2VzYW1l
 
-<p>See also <a href="/en-US/docs/Web/HTTP/Authentication">HTTP authentication</a> for
-  examples on how to configure Apache or nginx servers to password protect your site with
-  HTTP basic authentication.</p>
+See also [HTTP authentication](/en-US/docs/Web/HTTP/Authentication) for
+examples on how to configure Apache or nginx servers to password protect your site with
+HTTP basic authentication.
 
-<h2 id="Specifications">Specifications</h2>
+## Specifications
 
-<table class="standard-table">
-  <thead>
-    <tr>
-      <th scope="col">Specification</th>
-      <th scope="col">Title</th>
-    </tr>
-  </thead>
-  <tbody>
-    <tr>
-      <td>{{RFC("7235", "Authorization", "4.2")}}</td>
-      <td>HTTP/1.1: Authentication</td>
-    </tr>
-    <tr>
-      <td>{{RFC("7617")}}</td>
-      <td>The 'Basic' HTTP Authentication Scheme</td>
-    </tr>
-  </tbody>
-</table>
+| Specification                                        | Title                                  |
+| ---------------------------------------------------- | -------------------------------------- |
+| {{RFC("7235", "Authorization", "4.2")}} | HTTP/1.1: Authentication               |
+| {{RFC("7617")}}                                 | The 'Basic' HTTP Authentication Scheme |
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
-  <li><a href="/en-US/docs/Web/HTTP/Authentication">HTTP authentication</a></li>
-  <li>{{HTTPHeader("WWW-Authenticate")}}</li>
-  <li>{{HTTPHeader("Proxy-Authorization")}}</li>
-  <li>{{HTTPHeader("Proxy-Authenticate")}}</li>
-  <li>{{HTTPStatus("401")}}, {{HTTPStatus("403")}}, {{HTTPStatus("407")}}</li>
-</ul>
+- [HTTP authentication](/en-US/docs/Web/HTTP/Authentication)
+- {{HTTPHeader("WWW-Authenticate")}}
+- {{HTTPHeader("Proxy-Authorization")}}
+- {{HTTPHeader("Proxy-Authenticate")}}
+- {{HTTPStatus("401")}}, {{HTTPStatus("403")}}, {{HTTPStatus("407")}}
diff --git a/files/en-us/web/http/headers/cache-control/index.md b/files/en-us/web/http/headers/cache-control/index.md
index 6c0c35d08c02b5c..45b6f8f155d3cfe 100644
--- a/files/en-us/web/http/headers/cache-control/index.md
+++ b/files/en-us/web/http/headers/cache-control/index.md
@@ -10,182 +10,176 @@ tags:
   - Reference
 browser-compat: http.headers.Cache-Control
 ---
-<div>{{HTTPSidebar}}</div>
+{{HTTPSidebar}}
 
-<p>The <strong><code>Cache-Control</code></strong> HTTP header holds <em>directives</em> (instructions) for <a href="/en-US/docs/Web/HTTP/Caching">caching</a> in both requests and responses. A given directive in a request does not mean the same directive should be in the response.</p>
+The **`Cache-Control`** HTTP header holds _directives_ (instructions) for [caching](/en-US/docs/Web/HTTP/Caching) in both requests and responses. A given directive in a request does not mean the same directive should be in the response.
 
 <table class="properties">
- <tbody>
-  <tr>
-   <th scope="row">Header type</th>
-   <td>{{Glossary("Request header")}}, {{Glossary("Response header")}}</td>
-  </tr>
-  <tr>
-   <th scope="row">{{Glossary("Forbidden header name")}}</th>
-   <td>no</td>
-  </tr>
-  <tr>
-   <th scope="row">{{Glossary("CORS-safelisted response header")}}</th>
-   <td>yes</td>
-  </tr>
- </tbody>
+  <tbody>
+    <tr>
+      <th scope="row">Header type</th>
+      <td>
+        {{Glossary("Request header")}},
+        {{Glossary("Response header")}}
+      </td>
+    </tr>
+    <tr>
+      <th scope="row">{{Glossary("Forbidden header name")}}</th>
+      <td>no</td>
+    </tr>
+    <tr>
+      <th scope="row">
+        {{Glossary("CORS-safelisted response header")}}
+      </th>
+      <td>yes</td>
+    </tr>
+  </tbody>
 </table>
 
-<h2 id="Syntax">Syntax</h2>
+## Syntax
 
-<p>Caching directives have the following rules to be valid:</p>
+Caching directives have the following rules to be valid:
 
-<ul>
- <li>Case-insensitive, but lowercase is recommended.</li>
- <li>Multiple directives are comma-separated.</li>
- <li>Some directives have an optional argument, which can be either a <em>token</em> or a <em>quoted-string</em>. (See spec for definitions)</li>
-</ul>
+- Case-insensitive, but lowercase is recommended.
+- Multiple directives are comma-separated.
+- Some directives have an optional argument, which can be either a _token_ or a _quoted-string_. (See spec for definitions)
 
-<h3 id="Cache_request_directives">Cache request directives</h3>
+### Cache request directives
 
-<p>Standard <code>Cache-Control</code> directives that can be used by the client in an HTTP request.</p>
+Standard `Cache-Control` directives that can be used by the client in an HTTP request.
 
-<pre>Cache-Control: max-age=&lt;seconds&gt;
-Cache-Control: max-stale[=&lt;seconds&gt;]
-Cache-Control: min-fresh=&lt;seconds&gt;
-Cache-Control: no-cache
-Cache-Control: no-store
-Cache-Control: no-transform
-Cache-Control: only-if-cached
-</pre>
+    Cache-Control: max-age=<seconds>
+    Cache-Control: max-stale[=<seconds>]
+    Cache-Control: min-fresh=<seconds>
+    Cache-Control: no-cache
+    Cache-Control: no-store
+    Cache-Control: no-transform
+    Cache-Control: only-if-cached
 
-<h3 id="Cache_response_directives">Cache response directives</h3>
+### Cache response directives
 
-<p>Standard <code>Cache-Control</code> directives that can be used by the server in an HTTP response.</p>
+Standard `Cache-Control` directives that can be used by the server in an HTTP response.
 
-<pre>Cache-Control: must-revalidate
-Cache-Control: no-cache
-Cache-Control: no-store
-Cache-Control: no-transform
-Cache-Control: public
-Cache-Control: private
-Cache-Control: proxy-revalidate
-Cache-Control: max-age=&lt;seconds&gt;
-Cache-Control: s-maxage=&lt;seconds&gt;
-</pre>
+    Cache-Control: must-revalidate
+    Cache-Control: no-cache
+    Cache-Control: no-store
+    Cache-Control: no-transform
+    Cache-Control: public
+    Cache-Control: private
+    Cache-Control: proxy-revalidate
+    Cache-Control: max-age=<seconds>
+    Cache-Control: s-maxage=<seconds>
 
-<h3 id="Extension_Cache-Control_directives">Extension Cache-Control directives</h3>
+### Extension Cache-Control directives
 
-<p>Extension <code>Cache-Control</code> directives are not part of the core HTTP caching standards document. Check the <a href="#browser_compatibility">compatibility table</a> for their support; user-agents that don't recognize them should ignore them.</p>
+Extension `Cache-Control` directives are not part of the core HTTP caching standards document. Check the [compatibility table](#browser_compatibility) for their support; user-agents that don't recognize them should ignore them.
 
-<pre>Cache-Control: immutable
-Cache-Control: stale-while-revalidate=&lt;seconds&gt;
-Cache-Control: stale-if-error=&lt;seconds&gt;
-</pre>
+    Cache-Control: immutable
+    Cache-Control: stale-while-revalidate=<seconds>
+    Cache-Control: stale-if-error=<seconds>
 
-<h2 id="Directives">Directives</h2>
+## Directives
 
-<h3 id="Cacheability">Cacheability</h3>
+### Cacheability
 
-<p>Directives that define whether a response/request can be cached, where it may be cached, and whether it must be validated with the origin server before caching.</p>
+Directives that define whether a response/request can be cached, where it may be cached, and whether it must be validated with the origin server before caching.
 
-<dl>
- <dt><code>public</code></dt>
- <dd>The response may be stored by <em>any</em> cache, even if the response is normally non-cacheable.</dd>
- <dt><code>private</code></dt>
- <dd>The response may be stored only by a <em>browser's</em> cache, even if the response is normally non-cacheable. <strong>If you mean to not store the response in any cache, use <code>no-store</code> instead.</strong> <em>This directive is not effective in preventing caches from storing your response.</em></dd>
- <dt><code>no-cache</code></dt>
- <dd>The response may be stored by <em>any</em> cache, even if the response is normally non-cacheable. However, the stored response MUST <em>always</em> go through validation with the origin server first before using it, therefore, you cannot use <code>no-cache</code> in-conjunction with <code>immutable</code>. <strong>If you mean to not store the response in any cache, use <code>no-store</code> instead.</strong> <em>This directive is not effective in preventing caches from storing your response.</em></dd>
- <dt><code>no-store</code></dt>
- <dd>The response may <strong>not</strong> be stored in <em>any</em> cache. Note that this will not prevent a valid <em>pre-existing</em> cached response being returned. Clients can set <code>max-age=0</code> to also clear existing cache responses, as this forces the cache to revalidate with the server (no other directives have an effect when used with <code>no-store</code>).</dd>
-</dl>
+- `public`
+  - : The response may be stored by _any_ cache, even if the response is normally non-cacheable.
+- `private`
+  - : The response may be stored only by a _browser's_ cache, even if the response is normally non-cacheable. **If you mean to not store the response in any cache, use `no-store` instead.** _This directive is not effective in preventing caches from storing your response._
+- `no-cache`
+  - : The response may be stored by _any_ cache, even if the response is normally non-cacheable. However, the stored response MUST _always_ go through validation with the origin server first before using it, therefore, you cannot use `no-cache` in-conjunction with `immutable`. **If you mean to not store the response in any cache, use `no-store` instead.** _This directive is not effective in preventing caches from storing your response._
+- `no-store`
+  - : The response may **not** be stored in _any_ cache. Note that this will not prevent a valid _pre-existing_ cached response being returned. Clients can set `max-age=0` to also clear existing cache responses, as this forces the cache to revalidate with the server (no other directives have an effect when used with `no-store`).
 
-<h3 id="Expiration">Expiration</h3>
+### Expiration
 
-<dl>
- <dt><code>max-age=&lt;seconds&gt;</code></dt>
- <dd>The maximum amount of time a resource is considered fresh. Unlike <code>Expires</code>, this directive is relative to the time of the request.</dd>
- <dt><code>s-maxage=&lt;seconds&gt;</code></dt>
- <dd>Overrides <code>max-age</code> or the <code>Expires</code> header, but only for shared caches (e.g., proxies). Ignored by private caches.</dd>
- <dt><code>max-stale[=&lt;seconds&gt;]</code></dt>
- <dd>Indicates the client will accept a stale response. An optional value in seconds indicates the upper limit of staleness the client will accept.</dd>
- <dt><code>min-fresh=&lt;seconds&gt;</code></dt>
- <dd>Indicates the client wants a response that will still be fresh for <em>at least</em> the specified number of seconds.</dd>
- <dt><code>stale-while-revalidate=&lt;seconds&gt;</code> {{Experimental_Inline}}</dt>
- <dd>Indicates the client will accept a stale response, while asynchronously checking in the background for a fresh one. The <em>seconds</em> value indicates how long the client will accept a stale response. Note that the time does not start at the time of the request itself, but, for example, after <code>max-age</code> has elapsed. See "<a href="https://web.dev/stale-while-revalidate">Keeping things fresh with <code>stale-while-revalidate</code></a>" for more information.</dd>
- <dt><code>stale-if-error=&lt;seconds&gt;</code> {{Experimental_Inline}}</dt>
- <dd>Indicates the client will accept a stale response if the check for a fresh one fails. The <em>seconds</em> value indicates how long the client will accept the stale response after the initial expiration.</dd>
-</dl>
+- `max-age=<seconds>`
+  - : The maximum amount of time a resource is considered fresh. Unlike `Expires`, this directive is relative to the time of the request.
+- `s-maxage=<seconds>`
+  - : Overrides `max-age` or the `Expires` header, but only for shared caches (e.g., proxies). Ignored by private caches.
+- `max-stale[=<seconds>]`
+  - : Indicates the client will accept a stale response. An optional value in seconds indicates the upper limit of staleness the client will accept.
+- `min-fresh=<seconds>`
+  - : Indicates the client wants a response that will still be fresh for _at least_ the specified number of seconds.
+- `stale-while-revalidate=<seconds>` {{Experimental_Inline}}
+  - : Indicates the client will accept a stale response, while asynchronously checking in the background for a fresh one. The _seconds_ value indicates how long the client will accept a stale response. Note that the time does not start at the time of the request itself, but, for example, after `max-age` has elapsed. See "[Keeping things fresh with `stale-while-revalidate`](https://web.dev/stale-while-revalidate)" for more information.
+- `stale-if-error=<seconds>` {{Experimental_Inline}}
+  - : Indicates the client will accept a stale response if the check for a fresh one fails. The _seconds_ value indicates how long the client will accept the stale response after the initial expiration.
 
-<h3 id="Revalidation_and_reloading">Revalidation and reloading</h3>
+### Revalidation and reloading
 
-<dl>
- <dt><code>must-revalidate</code></dt>
- <dd>Indicates that once a resource becomes stale, caches must not use their stale copy without successful <a href="/en-US/docs/Web/HTTP/Caching#cache_validation">validation</a> on the origin server.</dd>
- <dt><code>proxy-revalidate</code></dt>
- <dd>Like <code>must-revalidate</code>, but only for shared caches (e.g., proxies). Ignored by private caches.</dd>
- <dt><code>immutable</code></dt>
- <dd>Indicates that the response body <strong>will not change</strong> over time. The resource, if <em>unexpired</em>, is unchanged on the server and therefore the client should not send a conditional revalidation for it (e.g. <code>If-None-Match</code> or <code>If-Modified-Since</code>) to check for updates, even when the user explicitly refreshes the page. Clients that aren't aware of this extension must ignore them as per the HTTP specification. In Firefox, <code>immutable</code> is only honored on <code>https://</code> transactions. For more information, see also this <a href="https://bitsup.blogspot.de/2016/05/cache-control-immutable.html">blog post</a>.</dd>
-</dl>
+- `must-revalidate`
+  - : Indicates that once a resource becomes stale, caches must not use their stale copy without successful [validation](/en-US/docs/Web/HTTP/Caching#cache_validation) on the origin server.
+- `proxy-revalidate`
+  - : Like `must-revalidate`, but only for shared caches (e.g., proxies). Ignored by private caches.
+- `immutable`
+  - : Indicates that the response body **will not change** over time. The resource, if _unexpired_, is unchanged on the server and therefore the client should not send a conditional revalidation for it (e.g. `If-None-Match` or `If-Modified-Since`) to check for updates, even when the user explicitly refreshes the page. Clients that aren't aware of this extension must ignore them as per the HTTP specification. In Firefox, `immutable` is only honored on `https://` transactions. For more information, see also this [blog post](https://bitsup.blogspot.de/2016/05/cache-control-immutable.html).
 
-<h3 id="Other">Other</h3>
+### Other
 
-<dl>
- <dt><code>no-transform</code></dt>
- <dd>An intermediate cache or proxy cannot edit the response body, {{HTTPHeader("Content-Encoding")}}, {{HTTPHeader("Content-Range")}}, or {{HTTPHeader("Content-Type")}}. It therefore forbids a proxy or browser feature, such as <a href="https://support.google.com/webmasters/answer/6211428">Google’s Web Light</a>, from converting images to minimize data for a cache store or slow connection.</dd>
- <dt><code>only-if-cached</code></dt>
- <dd>Set by the <em>client</em> to indicate "do not use the network" for the response. The cache should either respond using a stored response, or respond with a {{HTTPStatus("504")}} status code. Conditional headers such as <code>If-None-Match</code> should not be set. There is no effect if <code>only-if-cached</code> is set by a server as part of a response.</dd>
-</dl>
+- `no-transform`
+  - : An intermediate cache or proxy cannot edit the response body, {{HTTPHeader("Content-Encoding")}}, {{HTTPHeader("Content-Range")}}, or {{HTTPHeader("Content-Type")}}. It therefore forbids a proxy or browser feature, such as [Google’s Web Light](https://support.google.com/webmasters/answer/6211428), from converting images to minimize data for a cache store or slow connection.
+- `only-if-cached`
+  - : Set by the _client_ to indicate "do not use the network" for the response. The cache should either respond using a stored response, or respond with a {{HTTPStatus("504")}} status code. Conditional headers such as `If-None-Match` should not be set. There is no effect if `only-if-cached` is set by a server as part of a response.
 
-<h2 id="Examples">Examples</h2>
+## Examples
 
-<h3 id="Preventing_caching">Preventing caching</h3>
+### Preventing caching
 
-<p>A good way to disable caching of a resource, is to send the following response header:</p>
+A good way to disable caching of a resource, is to send the following response header:
+
+```plain example-good
+Cache-Control: no-store
+```
 
-<pre class="example-good">Cache-Control: no-store</pre>
+> **Note:** The `no-store` directive will prevent a new resource being cached,
+> but it will not prevent the cache from responding with a non-stale resource that was cached as the result of an earlier request.
+> Setting `max-age=0` as well forces the cache to revalidate (clears the cache).
+>
+>     Cache-Control: no-store, max-age=0
 
-<div class="notecard note">
-  <p><strong>Note:</strong> The <code>no-store</code> directive will prevent a new resource being cached,
-    but it will not prevent the cache from responding with a non-stale resource that was cached as the result of an earlier request.
-    Setting <code>max-age=0</code> as well forces the cache to revalidate (clears the cache).</p>
+On the opposite, this is a bad way to achieve this:
 
-  <pre>Cache-Control: no-store, max-age=0</pre>
-</div>
+```plain example-bad
+Cache-Control: private,no-cache,no-store,max-age=0,must-revalidate,pre-check=0,post-check=0
+```
 
-<p>On the opposite, this is a bad way to achieve this:</p>
-<pre class="example-bad">Cache-Control: private,no-cache,no-store,max-age=0,must-revalidate,pre-check=0,post-check=0</pre>
+### Caching static assets
 
-<h3 id="Caching_static_assets">Caching static assets</h3>
+For the files in the application that will not change, you can usually add aggressive caching by sending the response header below. This includes static files that are served by the application such as images, CSS files and JavaScript files, for example. In addition, see also the `Expires` header.
 
-<p>For the files in the application that will not change, you can usually add aggressive caching by sending the response header below. This includes static files that are served by the application such as images, CSS files and JavaScript files, for example. In addition, see also the <code>Expires</code> header.</p>
+    Cache-Control: public, max-age=604800, immutable
 
-<pre>Cache-Control: public, max-age=604800, immutable
-</pre>
+### Requiring revalidation
 
-<h3 id="Requiring_revalidation">Requiring revalidation</h3>
+`no-cache` and `max-age=0, must-revalidate` indicates same meaning.
+Clients can cache a resource but must revalidate each time before using it. This means HTTP request occurs each time though, it can skip downloading HTTP body if the content is valid.
 
-<p><code>no-cache</code> and <code>max-age=0, must-revalidate</code> indicates same meaning.<br>
- Clients can cache a resource but must revalidate each time before using it. This means HTTP request occurs each time though, it can skip downloading HTTP body if the content is valid.</p>
+    Cache-Control: no-cache
 
-<pre>Cache-Control: no-cache</pre>
+<!---->
 
-<pre>Cache-Control: max-age=0, must-revalidate</pre>
+    Cache-Control: max-age=0, must-revalidate
 
-<p><strong>Note</strong>: Following may serve stale resource if server is down or lose connectivity.</p>
+**Note**: Following may serve stale resource if server is down or lose connectivity.
 
-<pre>Cache-Control: max-age=0</pre>
+    Cache-Control: max-age=0
 
-<h2 id="Specifications">Specifications</h2>
+## Specifications
 
 {{Specifications}}
 
-<h2 id="Browser_compatibility">Browser compatibility</h2>
+## Browser compatibility
 
-<p>{{Compat}}</p>
+{{Compat}}
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
- <li><a href="/en-US/docs/Web/HTTP/Caching">HTTP Caching FAQ</a></li>
- <li><a href="https://www.mnot.net/cache_docs/">Caching Tutorial for Web Authors and Webmasters</a></li>
- <li>Guide: <em><a href="https://csswizardry.com/2019/03/cache-control-for-civilians"><code>Cache-Control</code> for civilians</a></em></li>
- <li>{{HTTPHeader("Age")}}</li>
- <li>{{HTTPHeader("Expires")}}</li>
- <li>{{HTTPHeader("Pragma")}}</li>
-</ul>
+- [HTTP Caching FAQ](/en-US/docs/Web/HTTP/Caching)
+- [Caching Tutorial for Web Authors and Webmasters](https://www.mnot.net/cache_docs/)
+- Guide: _[`Cache-Control` for civilians](https://csswizardry.com/2019/03/cache-control-for-civilians)_
+- {{HTTPHeader("Age")}}
+- {{HTTPHeader("Expires")}}
+- {{HTTPHeader("Pragma")}}
diff --git a/files/en-us/web/http/headers/clear-site-data/index.md b/files/en-us/web/http/headers/clear-site-data/index.md
index 7e11b65021d7bd6..30315bf5c1560e9 100644
--- a/files/en-us/web/http/headers/clear-site-data/index.md
+++ b/files/en-us/web/http/headers/clear-site-data/index.md
@@ -9,91 +9,84 @@ tags:
   - header
 browser-compat: http.headers.Clear-Site-Data
 ---
-<p>{{HTTPSidebar}}</p>
+{{HTTPSidebar}}
 
-<p>The <strong><code>Clear-Site-Data</code></strong> header clears browsing data (cookies, storage, cache) associated with the requesting website. It allows web developers to have more control over the data stored locally by a browser for their origins.</p>
+The **`Clear-Site-Data`** header clears browsing data (cookies, storage, cache) associated with the requesting website. It allows web developers to have more control over the data stored locally by a browser for their origins.
 
 <table class="properties">
- <tbody>
-  <tr>
-   <th scope="row">Header type</th>
-   <td>{{Glossary("Response header")}}</td>
-  </tr>
-  <tr>
-   <th scope="row">{{Glossary("Forbidden header name")}}</th>
-   <td>no</td>
-  </tr>
- </tbody>
+  <tbody>
+    <tr>
+      <th scope="row">Header type</th>
+      <td>{{Glossary("Response header")}}</td>
+    </tr>
+    <tr>
+      <th scope="row">{{Glossary("Forbidden header name")}}</th>
+      <td>no</td>
+    </tr>
+  </tbody>
 </table>
 
-<h2 id="Syntax">Syntax</h2>
+## Syntax
 
-<p>The <code>Clear-Site-Data</code> header accepts one or more directives. If all types of data should be cleared, the wildcard directive (<code>"*"</code>) can be used.</p>
+The `Clear-Site-Data` header accepts one or more directives. If all types of data should be cleared, the wildcard directive (`"*"`) can be used.
 
-<pre>// Single directive
-Clear-Site-Data: "cache"
+    // Single directive
+    Clear-Site-Data: "cache"
 
-// Multiple directives (comma separated)
-Clear-Site-Data: "cache", "cookies"
+    // Multiple directives (comma separated)
+    Clear-Site-Data: "cache", "cookies"
 
-// Wild card
-Clear-Site-Data: "*"
-</pre>
+    // Wild card
+    Clear-Site-Data: "*"
 
-<h2 id="Directives">Directives</h2>
+## Directives
 
-<div class="notecard note">
-  <p><strong>Note:</strong> All directives must comply with the <a href="https://tools.ietf.org/html/rfc7230#section-3.2.6">quoted-string grammar</a>. A directive that does not include the double quotes is invalid.</p>
-</div>
+> **Note:** All directives must comply with the [quoted-string grammar](https://tools.ietf.org/html/rfc7230#section-3.2.6). A directive that does not include the double quotes is invalid.
 
-<dl>
- <dt id="cache"><code>"cache"</code></dt>
- <dd>Indicates that the server wishes to remove locally cached data (i.e. the browser cache, see <a href="/en-US/docs/Web/HTTP/Caching">HTTP caching</a>) for the origin of the response URL. Depending on the browser, this might also clear out things like pre-rendered pages, script caches, WebGL shader caches, or address bar suggestions.</dd>
- <dt id="cookies"><code>"cookies"</code></dt>
- <dd>Indicates that the server wishes to remove all cookies for the origin of the response URL. HTTP authentication credentials are also cleared out. This affects the entire registered domain, including subdomains. So https://example.com as well as https://stage.example.com, will have cookies cleared.</dd>
- <dt id="storage"><code>"storage"</code></dt>
- <dd>Indicates that the server wishes to remove all DOM storage for the origin of the response URL. This includes storage mechanisms such as:
- <ul>
-  <li>localStorage (executes <code>localStorage.clear</code>),</li>
-  <li>sessionStorage (executes <code>sessionStorage.clear</code>),</li>
-  <li>IndexedDB (for each database execute {{domxref("IDBFactory.deleteDatabase")}}),</li>
-  <li>Service worker registrations (for each service worker registration, execute {{domxref("ServiceWorkerRegistration.unregister")}}),</li>
-  <li><a href="/en-US/docs/Web/HTML/Using_the_application_cache">AppCache,</a></li>
-  <li>WebSQL databases,</li>
-  <li><a href="/en-US/docs/Web/API/File_and_Directory_Entries_API">FileSystem API data</a>,</li>
-  <li>Plugin data (Flash via <code><a href="https://wiki.mozilla.org/NPAPI:ClearSiteData">NPP_ClearSiteData</a></code>).</li>
- </ul>
- </dd>
- <dt id="executionContexts"><code>"executionContexts"</code></dt>
- <dd>Indicates that the server wishes to reload all browsing contexts for the origin of the response ({{domxref("Location.reload")}}).</dd>
- <dt><code>"*"</code> (wildcard)</dt>
- <dd>Indicates that the server wishes to clear all types of data for the origin of the response. If more data types are added in future versions of this header, they will also be covered by it.</dd>
-</dl>
+- `"cache"`
+  - : Indicates that the server wishes to remove locally cached data (i.e. the browser cache, see [HTTP caching](/en-US/docs/Web/HTTP/Caching)) for the origin of the response URL. Depending on the browser, this might also clear out things like pre-rendered pages, script caches, WebGL shader caches, or address bar suggestions.
+- `"cookies"`
+  - : Indicates that the server wishes to remove all cookies for the origin of the response URL. HTTP authentication credentials are also cleared out. This affects the entire registered domain, including subdomains. So https\://example.com as well as https\://stage.example.com, will have cookies cleared.
+- `"storage"`
 
-<h2 id="Examples">Examples</h2>
+  - : Indicates that the server wishes to remove all DOM storage for the origin of the response URL. This includes storage mechanisms such as:
 
-<h3 id="Sign_out_of_web_site">Sign out of web site</h3>
+    - localStorage (executes `localStorage.clear`),
+    - sessionStorage (executes `sessionStorage.clear`),
+    - IndexedDB (for each database execute {{domxref("IDBFactory.deleteDatabase")}}),
+    - Service worker registrations (for each service worker registration, execute {{domxref("ServiceWorkerRegistration.unregister")}}),
+    - [AppCache,](/en-US/docs/Web/HTML/Using_the_application_cache)
+    - WebSQL databases,
+    - [FileSystem API data](/en-US/docs/Web/API/File_and_Directory_Entries_API),
+    - Plugin data (Flash via [`NPP_ClearSiteData`](https://wiki.mozilla.org/NPAPI:ClearSiteData)).
 
-<p>If a user signs out of your website or service, you might want to remove locally stored data. You can achieve that by adding the <code>Clear-Site-Data</code> header when sending the page confirming that logging out from the site has been accomplished successfully (https://example.com/logout, for example):</p>
+- `"executionContexts"`
+  - : Indicates that the server wishes to reload all browsing contexts for the origin of the response ({{domxref("Location.reload")}}).
+- `"*"` (wildcard)
+  - : Indicates that the server wishes to clear all types of data for the origin of the response. If more data types are added in future versions of this header, they will also be covered by it.
 
-<pre>Clear-Site-Data: "cache", "cookies", "storage", "executionContexts"</pre>
+## Examples
 
-<h3 id="Clearing_cookies">Clearing cookies</h3>
+### Sign out of web site
 
-<p>If this header is delivered with the response at https://example.com/clear-cookies, all cookies on the same domain https://example.com and any subdomains (like https://stage.example.com, etc), will be cleared out.</p>
+If a user signs out of your website or service, you might want to remove locally stored data. You can achieve that by adding the `Clear-Site-Data` header when sending the page confirming that logging out from the site has been accomplished successfully (https\://example.com/logout, for example):
 
-<pre>Clear-Site-Data: "cookies"</pre>
+    Clear-Site-Data: "cache", "cookies", "storage", "executionContexts"
 
-<h2 id="Specifications">Specifications</h2>
+### Clearing cookies
+
+If this header is delivered with the response at https\://example.com/clear-cookies, all cookies on the same domain https\://example.com and any subdomains (like https\://stage.example.com, etc), will be cleared out.
+
+    Clear-Site-Data: "cookies"
+
+## Specifications
 
 {{Specifications}}
 
-<h2 id="Browser_compatibility">Browser compatibility</h2>
+## Browser compatibility
 
-<p>{{Compat}}</p>
+{{Compat}}
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
- <li>{{HTTPHeader("Cache-Control")}}</li>
-</ul>
+- {{HTTPHeader("Cache-Control")}}
diff --git a/files/en-us/web/http/headers/connection/index.md b/files/en-us/web/http/headers/connection/index.md
index e9cbe535d422b49..55ab377bf1e4017 100644
--- a/files/en-us/web/http/headers/connection/index.md
+++ b/files/en-us/web/http/headers/connection/index.md
@@ -2,42 +2,43 @@
 title: Connection
 slug: Web/HTTP/Headers/Connection
 tags:
-- HTTP
-- HTTP Header
-- Request header
-- Response header
-- Reference
-- Web
+  - HTTP
+  - HTTP Header
+  - Request header
+  - Response header
+  - Reference
+  - Web
 browser-compat: http.headers.Connection
 ---
-<div>{{HTTPSidebar}}</div>
+{{HTTPSidebar}}
 
-<p>The <strong><code>Connection</code></strong> general header controls whether or not the
-  network connection stays open after the current transaction finishes. If the value sent
-  is <code>keep-alive</code>, the connection is persistent and not closed, allowing for
-  subsequent requests to the same server to be done.</p>
+The **`Connection`** general header controls whether or not the
+network connection stays open after the current transaction finishes. If the value sent
+is `keep-alive`, the connection is persistent and not closed, allowing for
+subsequent requests to the same server to be done.
 
-<div class="notecard warning">
-  <p><strong>Warning:</strong> Connection-specific header fields such as {{HTTPHeader("Connection")}} and
-    {{HTTPHeader("Keep-Alive")}} are
-    <a href="https://datatracker.ietf.org/doc/html/rfc7540#section-8.1.2.2">prohibited in HTTP/2</a>.
-    Chrome and Firefox ignore them in HTTP/2 responses, but Safari conforms to the HTTP/2
-    spec requirements and won't load any response which contains them.</p>
-</div>
+> **Warning:** Connection-specific header fields such as {{HTTPHeader("Connection")}} and
+> {{HTTPHeader("Keep-Alive")}} are
+> [prohibited in HTTP/2](https://datatracker.ietf.org/doc/html/rfc7540#section-8.1.2.2).
+> Chrome and Firefox ignore them in HTTP/2 responses, but Safari conforms to the HTTP/2
+> spec requirements and won't load any response which contains them.
 
-<p>Except for the standard hop-by-hop headers ({{HTTPHeader("Keep-Alive")}},
-  {{HTTPHeader("Transfer-Encoding")}}, {{HTTPHeader("TE")}}, {{HTTPHeader("Connection")}},
-  {{HTTPHeader("Trailer")}}, {{HTTPHeader("Upgrade")}},
-  {{HTTPHeader("Proxy-Authorization")}} and {{HTTPHeader("Proxy-Authenticate")}}), any
-  hop-by-hop headers used by the message must be listed in the <code>Connection</code>
-  header, so that the first proxy knows it has to consume them and not forward them
-  further. Standard hop-by-hop headers are also required to be listed.</p>
+Except for the standard hop-by-hop headers ({{HTTPHeader("Keep-Alive")}},
+{{HTTPHeader("Transfer-Encoding")}}, {{HTTPHeader("TE")}}, {{HTTPHeader("Connection")}},
+{{HTTPHeader("Trailer")}}, {{HTTPHeader("Upgrade")}},
+{{HTTPHeader("Proxy-Authorization")}} and {{HTTPHeader("Proxy-Authenticate")}}), any
+hop-by-hop headers used by the message must be listed in the `Connection`
+header, so that the first proxy knows it has to consume them and not forward them
+further. Standard hop-by-hop headers are also required to be listed.
 
 <table class="properties">
   <tbody>
     <tr>
       <th scope="row">Header type</th>
-      <td>{{Glossary("Request header")}}, {{Glossary("Response header")}}</td>
+      <td>
+        {{Glossary("Request header")}},
+        {{Glossary("Response header")}}
+      </td>
     </tr>
     <tr>
       <th scope="row">{{Glossary("Forbidden header name")}}</th>
@@ -46,26 +47,25 @@ browser-compat: http.headers.Connection
   </tbody>
 </table>
 
-<h2 id="Syntax">Syntax</h2>
+## Syntax
 
-<pre class="brush: html">Connection: keep-alive
+```html
+Connection: keep-alive
 Connection: close
-</pre>
+```
 
-<h2 id="Directives">Directives</h2>
+## Directives
 
-<dl>
-  <dt><code>close</code></dt>
-  <dd>Indicates that either the client or the server would like to close the connection.
-    This is the default on HTTP/1.0 requests.</dd>
-  <dt>any comma-separated list of HTTP headers [Usually <code>keep-alive</code> only]</dt>
-  <dd>Indicates that the client would like to keep the connection open. Having a
+- `close`
+  - : Indicates that either the client or the server would like to close the connection.
+    This is the default on HTTP/1.0 requests.
+- any comma-separated list of HTTP headers \[Usually `keep-alive` only]
+  - : Indicates that the client would like to keep the connection open. Having a
     persistent connection is the default on HTTP/1.1 requests. The list of headers are the
     name of the header to be removed by the first non-transparent proxy or cache
     in-between: these headers define the connection between the emitter and the first
-    entity, not the destination node.</dd>
-</dl>
+    entity, not the destination node.
 
-<h2 id="Browser_compatibility">Browser compatibility</h2>
+## Browser compatibility
 
-<p>{{Compat}}</p>
+{{Compat}}
diff --git a/files/en-us/web/http/headers/content-disposition/index.md b/files/en-us/web/http/headers/content-disposition/index.md
index a6dc1932cfb703c..713f0513f95bf84 100644
--- a/files/en-us/web/http/headers/content-disposition/index.md
+++ b/files/en-us/web/http/headers/content-disposition/index.md
@@ -9,130 +9,120 @@ tags:
   - Reference
 browser-compat: http.headers.Content-Disposition
 ---
-<div>{{HTTPSidebar}}</div>
+{{HTTPSidebar}}
 
-<p>In a regular HTTP response, the <code><strong>Content-Disposition</strong></code> response header is a header indicating if the content is expected to be displayed <em>inline</em> in the browser, that is, as a Web page or as part of a Web page, or as an <em>attachment</em>, that is downloaded and saved locally.</p>
+In a regular HTTP response, the **`Content-Disposition`** response header is a header indicating if the content is expected to be displayed _inline_ in the browser, that is, as a Web page or as part of a Web page, or as an _attachment_, that is downloaded and saved locally.
 
-<p>In a <code>multipart/form-data</code> body, the HTTP <strong><code>Content-Disposition</code></strong> general header is a header that must be used on each subpart of a multipart body to give information about the field it applies to. The subpart is delimited by the <em>boundary</em> defined in the {{HTTPHeader("Content-Type")}} header. Used on the body itself, <code>Content-Disposition</code> has no effect.</p>
+In a `multipart/form-data` body, the HTTP **`Content-Disposition`** general header is a header that must be used on each subpart of a multipart body to give information about the field it applies to. The subpart is delimited by the _boundary_ defined in the {{HTTPHeader("Content-Type")}} header. Used on the body itself, `Content-Disposition` has no effect.
 
-<p>The <code>Content-Disposition</code> header is defined in the larger context of MIME messages for e-mail, but only a subset of the possible parameters apply to HTTP forms and {{HTTPMethod("POST")}} requests. Only the value <code>form-data</code>, as well as the optional directive <code>name</code> and <code>filename</code>, can be used in the HTTP context.</p>
+The `Content-Disposition` header is defined in the larger context of MIME messages for e-mail, but only a subset of the possible parameters apply to HTTP forms and {{HTTPMethod("POST")}} requests. Only the value `form-data`, as well as the optional directive `name` and `filename`, can be used in the HTTP context.
 
 <table class="properties">
- <tbody>
-  <tr>
-   <th scope="row">Header type</th>
-   <td>{{Glossary("Response header")}} (for the main body),
-      <br>{{Glossary("Request header")}}, {{Glossary("Response header")}} (for a subpart of a multipart body)</td>
-  </tr>
-  <tr>
-   <th scope="row">{{Glossary("Forbidden header name")}}</th>
-   <td>no</td>
-  </tr>
- </tbody>
+  <tbody>
+    <tr>
+      <th scope="row">Header type</th>
+      <td>
+        {{Glossary("Response header")}} (for the main body),<br />{{Glossary("Request header")}},
+        {{Glossary("Response header")}} (for a subpart of a multipart
+        body)
+      </td>
+    </tr>
+    <tr>
+      <th scope="row">{{Glossary("Forbidden header name")}}</th>
+      <td>no</td>
+    </tr>
+  </tbody>
 </table>
 
-<h2 id="Syntax">Syntax</h2>
+## Syntax
 
-<h3 id="As_a_response_header_for_the_main_body">As a response header for the main body</h3>
+### As a response header for the main body
 
-<p>The first parameter in the HTTP context is either <code>inline</code> (default value, indicating it can be displayed inside the Web page, or as the Web page) or <code>attachment</code> (indicating it should be downloaded; most browsers presenting a 'Save as' dialog, prefilled with the value of the <code>filename</code> parameters if present).</p>
+The first parameter in the HTTP context is either `inline` (default value, indicating it can be displayed inside the Web page, or as the Web page) or `attachment` (indicating it should be downloaded; most browsers presenting a 'Save as' dialog, prefilled with the value of the `filename` parameters if present).
 
-<pre class="brush: html">Content-Disposition: inline
+```html
+Content-Disposition: inline
 Content-Disposition: attachment
-Content-Disposition: attachment; filename="filename.jpg"</pre>
+Content-Disposition: attachment; filename="filename.jpg"
+```
 
-<div class="notecard note">
-  <p><strong>Note:</strong> Chrome, and Firefox 82 and later, prioritize the HTML <a href="/en-US/docs/Web/HTML/Element/a">&lt;a&gt; element's</a> <code>download</code> attribute over the <code>Content-Disposition</code> <code>inline</code> parameter (for <a href="/en-US/docs/Web/Security/Same-origin_policy">same-origin URLs</a>). Earlier Firefox versions prioritize the header and will display the content inline.</p>
-</div>
+> **Note:** Chrome, and Firefox 82 and later, prioritize the HTML [\<a> element's](/en-US/docs/Web/HTML/Element/a) `download` attribute over the `Content-Disposition` `inline` parameter (for [same-origin URLs](/en-US/docs/Web/Security/Same-origin_policy)). Earlier Firefox versions prioritize the header and will display the content inline.
 
-<h3 id="As_a_header_for_a_multipart_body">As a header for a multipart body</h3>
+### As a header for a multipart body
 
-<p>A <code>multipart/form-data</code> body requires a <code>Content-Disposition</code> header to provide information for each subpart of the form (e.g. for every form field and any files that are part of field data). The first directive is always <code>form-data</code>, and the header <em>must</em> also include a <code>name</code> parameter to identify the relevant field. Additional directives are case-insensitive and have arguments that use quoted-string syntax after the <code>'='</code> sign. Multiple parameters are separated by a semi-colon (<code>';'</code>).</p>
+A `multipart/form-data` body requires a `Content-Disposition` header to provide information for each subpart of the form (e.g. for every form field and any files that are part of field data). The first directive is always `form-data`, and the header _must_ also include a `name` parameter to identify the relevant field. Additional directives are case-insensitive and have arguments that use quoted-string syntax after the `'='` sign. Multiple parameters are separated by a semi-colon (`';'`).
 
-<pre class="brush: html">Content-Disposition: form-data; name="fieldName"
-Content-Disposition: form-data; name="fieldName"; filename="filename.jpg"</pre>
+```html
+Content-Disposition: form-data; name="fieldName"
+Content-Disposition: form-data; name="fieldName"; filename="filename.jpg"
+```
 
-<h3 id="Directives">Directives</h3>
+### Directives
 
-<dl>
- <dt><code>name</code></dt>
- <dd>
-    <p>
-      Is followed by a string
-      containing the name of the HTML field in the form
-      that the content of this subpart refers to.
-      When dealing with multiple files in the same field
-      (for example, the {{htmlattrxref("multiple", "input")}} attribute of an <code>{{HTMLElement("input","&lt;input type=\"file\"&gt;")}}</code> element),
-      there can be several subparts with the same name.
-    </p>
-    <p>
-      A <code>name</code> with a value of <code>'_charset_'</code> indicates
-      that the part is not an HTML field,
-      but the default charset to use for parts without explicit charset information.
-    </p>
-  </dd>
+- `name`
 
-  <dt><code>filename</code></dt>
-  <dd>Is followed by a string containing the original name of the file transmitted. The filename is always optional and must not be used blindly by the application: path information should be stripped, and conversion to the server file system rules should be done. This parameter provides mostly indicative information. When used in combination with <code>Content-Disposition: attachment</code>, it is used as the default filename for an eventual "Save As" dialog presented to the user.</dd>
+  - : Is followed by a string
+    containing the name of the HTML field in the form
+    that the content of this subpart refers to.
+    When dealing with multiple files in the same field
+    (for example, the {{htmlattrxref("multiple", "input")}} attribute of an `{{HTMLElement("input","&lt;input type=\"file\"&gt;")}}` element),
+    there can be several subparts with the same name.
 
-  <dt><code>filename*</code></dt>
-  <dd>The parameters <code>filename</code> and <code>filename*</code> differ only in that <code>filename*</code> uses the encoding defined in <a href="https://datatracker.ietf.org/doc/html/rfc5987">RFC 5987</a>. When both <code>filename</code> and <code>filename*</code> are present in a single header field value, <code>filename*</code> is preferred over <code>filename</code> when both are understood.</dd>
-</dl>
+    A `name` with a value of `'_charset_'` indicates
+    that the part is not an HTML field,
+    but the default charset to use for parts without explicit charset information.
 
-<div class="notecard warning">
-  <p><strong>Warning:</strong> The string following <code>filename</code> should always be put into quotes; but, for compatibility reasons, many browsers try to parse unquoted names that contain spaces.</p>
-</div>
+- `filename`
+  - : Is followed by a string containing the original name of the file transmitted. The filename is always optional and must not be used blindly by the application: path information should be stripped, and conversion to the server file system rules should be done. This parameter provides mostly indicative information. When used in combination with `Content-Disposition: attachment`, it is used as the default filename for an eventual "Save As" dialog presented to the user.
+- `filename*`
+  - : The parameters `filename` and `filename*` differ only in that `filename*` uses the encoding defined in [RFC 5987](https://datatracker.ietf.org/doc/html/rfc5987). When both `filename` and `filename*` are present in a single header field value, `filename*` is preferred over `filename` when both are understood.
 
-<h2 id="Examples">Examples</h2>
+> **Warning:** The string following `filename` should always be put into quotes; but, for compatibility reasons, many browsers try to parse unquoted names that contain spaces.
 
-<p>A response triggering the "Save As" dialog:</p>
+## Examples
 
-<pre>200 OK
-Content-Type: text/html; charset=utf-8
-Content-Disposition: attachment; filename="cool.html"
-Content-Length: 21
+A response triggering the "Save As" dialog:
 
-&lt;HTML&gt;Save me!&lt;/HTML&gt;
+    200 OK
+    Content-Type: text/html; charset=utf-8
+    Content-Disposition: attachment; filename="cool.html"
+    Content-Length: 21
 
-</pre>
+    <HTML>Save me!</HTML>
 
-<p>This simple HTML file will be saved as a regular download rather than displayed in the browser. Most browsers will propose to save it under the <code>cool.html</code> filename (by default).</p>
+This simple HTML file will be saved as a regular download rather than displayed in the browser. Most browsers will propose to save it under the `cool.html` filename (by default).
 
-<p>An example of an HTML form posted using the <code>multipart/form-data</code> format that makes use of the <code>Content-Disposition</code> header:</p>
+An example of an HTML form posted using the `multipart/form-data` format that makes use of the `Content-Disposition` header:
 
-<pre>POST /test.html HTTP/1.1
-Host: example.org
-Content-Type: multipart/form-data;boundary="boundary"
+    POST /test.html HTTP/1.1
+    Host: example.org
+    Content-Type: multipart/form-data;boundary="boundary"
 
---boundary
-Content-Disposition: form-data; name="field1"
+    --boundary
+    Content-Disposition: form-data; name="field1"
 
-value1
---boundary
-Content-Disposition: form-data; name="field2"; filename="example.txt"
+    value1
+    --boundary
+    Content-Disposition: form-data; name="field2"; filename="example.txt"
 
-value2
---boundary--</pre>
+    value2
+    --boundary--
 
-<h2 id="Specifications">Specifications</h2>
+## Specifications
 
 {{Specifications}}
 
-<h2 id="Browser_compatibility">Browser compatibility</h2>
+## Browser compatibility
 
-<p>{{Compat}}</p>
+{{Compat}}
 
-<h2 id="Compatibility_notes">Compatibility notes</h2>
+## Compatibility notes
 
-<ul>
- <li>Firefox 5 handles the <code>Content-Disposition</code> HTTP response header more effectively if both the <code>filename</code> and <code>filename*</code> parameters are provided; it looks through all provided names, using the <code>filename*</code> parameter if one is available, even if a <code>filename</code> parameter is included first. Previously, the first matching parameter would be used, thereby preventing a more appropriate name from being used. See {{bug(588781)}}.</li>
- <li>Firefox 82 (and later) and Chrome prioritize the HTML <a href="/en-US/docs/Web/HTML/Element/a">&lt;a&gt; element's</a> <code>download</code> attribute over the <code>Content-Disposition</code> <code>inline</code> parameter (for <a href="/en-US/docs/Web/Security/Same-origin_policy">same-origin URLs</a>). Earlier Firefox versions prioritize the header and will display the content inline.</li>
-</ul>
+- Firefox 5 handles the `Content-Disposition` HTTP response header more effectively if both the `filename` and `filename*` parameters are provided; it looks through all provided names, using the `filename*` parameter if one is available, even if a `filename` parameter is included first. Previously, the first matching parameter would be used, thereby preventing a more appropriate name from being used. See {{bug(588781)}}.
+- Firefox 82 (and later) and Chrome prioritize the HTML [\<a> element's](/en-US/docs/Web/HTML/Element/a) `download` attribute over the `Content-Disposition` `inline` parameter (for [same-origin URLs](/en-US/docs/Web/Security/Same-origin_policy)). Earlier Firefox versions prioritize the header and will display the content inline.
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
- <li><a href="/en-US/docs/Learn/Forms">HTML Forms</a></li>
- <li>The {{HTTPHeader("Content-Type")}} defining the boundary of the multipart body.</li>
- <li>The {{domxref("FormData")}} interface used to manipulate form data for use in the {{domxref("XMLHttpRequest")}} API.</li>
-</ul>
+- [HTML Forms](/en-US/docs/Learn/Forms)
+- The {{HTTPHeader("Content-Type")}} defining the boundary of the multipart body.
+- The {{domxref("FormData")}} interface used to manipulate form data for use in the {{domxref("XMLHttpRequest")}} API.
diff --git a/files/en-us/web/http/headers/content-dpr/index.md b/files/en-us/web/http/headers/content-dpr/index.md
index ee9dcb6a466b472..d4a1e01ffa410fb 100644
--- a/files/en-us/web/http/headers/content-dpr/index.md
+++ b/files/en-us/web/http/headers/content-dpr/index.md
@@ -12,72 +12,67 @@ tags:
   - Exerimental
 browser-compat: http.headers.Content-DPR
 ---
-<div>{{HTTPSidebar}} {{deprecated_header}}{{securecontext_header}}</div>
-
-<p>The <strong><code>Content-DPR</code></strong> response header is used to confirm the <em>image</em> device to pixel ratio in requests where the screen {{HTTPHeader("DPR")}} <a href="/en-US/docs/Glossary/Client_hints">client hint</a> was used to select an image resource.</p>
+{{HTTPSidebar}} {{deprecated_header}}{{securecontext_header}}
 
+The **`Content-DPR`** response header is used to confirm the _image_ device to pixel ratio in requests where the screen {{HTTPHeader("DPR")}} [client hint](/en-US/docs/Glossary/Client_hints) was used to select an image resource.
 
 <table class="properties">
   <tbody>
-   <tr>
-    <th scope="row">Header type</th>
-    <td>{{Glossary("Response header")}}, {{Glossary("Client hints","Client hint")}}</td>
-   </tr>
-   <tr>
-    <th scope="row">{{Glossary("Forbidden header name")}}</th>
-    <td>no</td>
-   </tr>
-   <tr>
-    <th scope="row">{{Glossary("CORS-safelisted response header")}}</th>
-    <td>no</td>
-   </tr>
+    <tr>
+      <th scope="row">Header type</th>
+      <td>
+        {{Glossary("Response header")}},
+        {{Glossary("Client hints","Client hint")}}
+      </td>
+    </tr>
+    <tr>
+      <th scope="row">{{Glossary("Forbidden header name")}}</th>
+      <td>no</td>
+    </tr>
+    <tr>
+      <th scope="row">
+        {{Glossary("CORS-safelisted response header")}}
+      </th>
+      <td>no</td>
+    </tr>
   </tbody>
- </table>
+</table>
+
+If the {{HTTPHeader("DPR")}} client hint is used to select an image the server must specify `Content-DPR` in the response. If the value in `Content-DPR` is different from the {{HTTPHeader("DPR")}} value in the request (i.e. image DPR is not the same as screen DPR) then the client must use the `Content-DPR` for determining intrinsic image size and scaling the image.
+
+If the `Content-DPR` header appears more than once in a message the last occurrence is used.
 
-<p>If the {{HTTPHeader("DPR")}} client hint is used to select an image the server must specify <code>Content-DPR</code> in the response. If the value in <code>Content-DPR</code> is different from the {{HTTPHeader("DPR")}} value in the request (i.e. image DPR is not the same as screen DPR) then the client must use the <code>Content-DPR</code> for determining intrinsic image size and scaling the image.</p>
+> **Note:**
+>
+> - `Content-DPR` was removed from the client hints specification in [draft-ietf-httpbis-client-hints-07](https://datatracker.ietf.org/doc/html/draft-ietf-httpbis-client-hints-07). The [Responsive Image Client Hints](https://wicg.github.io/responsive-image-client-hints) spec proposes to replace this header by specifying intrinsic resolution/dimensions in EXIF metadata.
 
-<p>If the <code>Content-DPR</code> header appears more than once in a message the last occurrence is used.</p>
+## Syntax
 
-<div class="notecard note">
-  <p><strong>Note:</strong></p>
-    <ul>
-      <li><code>Content-DPR</code> was removed from the client hints specification in <a href="https://datatracker.ietf.org/doc/html/draft-ietf-httpbis-client-hints-07">draft-ietf-httpbis-client-hints-07</a>. The <a href="https://wicg.github.io/responsive-image-client-hints">Responsive Image Client Hints</a> spec proposes to replace this header by specifying intrinsic resolution/dimensions in EXIF metadata.</li>
-    </ul>
-</div>
+    Content-DPR: <number>
 
-<h2 id="Syntax">Syntax</h2>
+## Directives
 
-<pre>Content-DPR: &lt;number&gt;</pre>
+- `<number>`
+  - : The image device pixel ratio, calculated according to the following formula:
+    Content-DPR = _Selected image resource size_ / (_Width_ / _DPR_)
 
-<h2 id="Directives">Directives</h2>
+## Examples
 
-<dl>
- <dt><code> &lt;number&gt;</code></dt>
- <dd>The image device pixel ratio, calculated according to the following formula:
-  <br> Content-DPR = <em>Selected image resource size</em> / (<em>Width</em> / <em>DPR</em>)
-</dd>
-</dl>
+See the [`DPR`](/en-US/docs/Web/HTTP/Headers/DPR#examples) header example.
 
-<h2 id="Examples">Examples</h2>
+## Browser compatibility
 
-<p>See the <a href="/en-US/docs/Web/HTTP/Headers/DPR#examples"><code>DPR</code></a> header example.</p>
+{{Compat}}
 
-<h2 id="Browser_compatibility">Browser compatibility</h2>
+## See also
 
-<p>{{Compat}}</p>
+- [Adapting to Users with Client Hints](https://developers.google.com/web/fundamentals/performance/optimizing-content-efficiency/client-hints) (developer.google.com)
+- Device client hints
 
-<h2 id="See_also">See also</h2>
+  - {{HTTPHeader("Device-Memory")}}
+  - {{HTTPHeader("DPR")}}
+  - {{HTTPHeader("Viewport-Width")}}
+  - {{HTTPHeader("Width")}}
 
-<ul>
-  <li><a href="https://developers.google.com/web/fundamentals/performance/optimizing-content-efficiency/client-hints">Adapting to Users with Client Hints</a> (developer.google.com)</li>
- <li>Device client hints
-  <ul>
-    <li>{{HTTPHeader("Device-Memory")}}</li>
-    <li>{{HTTPHeader("DPR")}}</li>
-    <li>{{HTTPHeader("Viewport-Width")}}</li>
-    <li>{{HTTPHeader("Width")}}</li>
-   </ul>
- </li>
- <li>{{HTTPHeader("Accept-CH")}}</li>
- <li><a href="/en-US/docs/Web/HTTP/Caching#varying_responses">HTTP Caching > Varying responses</a> and {{HTTPHeader("Vary")}}</li>
-</ul>
+- {{HTTPHeader("Accept-CH")}}
+- [HTTP Caching > Varying responses](/en-US/docs/Web/HTTP/Caching#varying_responses) and {{HTTPHeader("Vary")}}
diff --git a/files/en-us/web/http/headers/content-encoding/index.md b/files/en-us/web/http/headers/content-encoding/index.md
index 4ada86213a5c940..a8b9ec635abdc5b 100644
--- a/files/en-us/web/http/headers/content-encoding/index.md
+++ b/files/en-us/web/http/headers/content-encoding/index.md
@@ -7,15 +7,15 @@ tags:
   - Reference
 browser-compat: http.headers.Content-Encoding
 ---
-<div>{{HTTPSidebar}}</div>
+{{HTTPSidebar}}
 
-<p>The <strong><code>Content-Encoding</code></strong> {{Glossary("representation header")}} lists any encodings that have been applied to the representation (message payload), and in what order.
-  This lets the recipient know how to decode the representation in order to obtain the original payload format.
-  Content encoding is mainly used to compress the message data without losing information about the origin media type.</p>
+The **`Content-Encoding`** {{Glossary("representation header")}} lists any encodings that have been applied to the representation (message payload), and in what order.
+This lets the recipient know how to decode the representation in order to obtain the original payload format.
+Content encoding is mainly used to compress the message data without losing information about the origin media type.
 
-<p>Note that the original media/content type is specified in the {{HTTPHeader("Content-Type")}} header, and that the <code>Content-Encoding</code> applies to the representation, or "coded form", of the data. If the original media is encoded in some way (e.g. a zip file) then this information would not be included in the <code>Content-Encoding</code> header.</p>
+Note that the original media/content type is specified in the {{HTTPHeader("Content-Type")}} header, and that the `Content-Encoding` applies to the representation, or "coded form", of the data. If the original media is encoded in some way (e.g. a zip file) then this information would not be included in the `Content-Encoding` header.
 
-<p>Servers are encouraged to compress data as much as possible, and should use content encoding where appropriate. Compressing a compressed media type such as a zip or jpeg may not be appropriate, as this can make the payload larger.</p>
+Servers are encouraged to compress data as much as possible, and should use content encoding where appropriate. Compressing a compressed media type such as a zip or jpeg may not be appropriate, as this can make the payload larger.
 
 <table class="properties">
   <tbody>
@@ -30,70 +30,67 @@ browser-compat: http.headers.Content-Encoding
   </tbody>
 </table>
 
-<h2 id="Syntax">Syntax</h2>
+## Syntax
 
-<pre class="brush: html">Content-Encoding: gzip
+```html
+Content-Encoding: gzip
 Content-Encoding: compress
 Content-Encoding: deflate
 Content-Encoding: br
 
 // Multiple, in the order in which they were applied
 Content-Encoding: deflate, gzip
-</pre>
+```
 
-<h2 id="Directives">Directives</h2>
+## Directives
 
-<dl>
-  <dt><code>gzip</code></dt>
-  <dd>A format using the <a       href="https://en.wikipedia.org/wiki/LZ77_and_LZ78#LZ77">Lempel-Ziv coding</a>
-    (LZ77), with a 32-bit CRC. This is the original format of the UNIX <em>gzip</em>
+- `gzip`
+  - : A format using the [Lempel-Ziv coding](https://en.wikipedia.org/wiki/LZ77_and_LZ78#LZ77)
+    (LZ77), with a 32-bit CRC. This is the original format of the UNIX _gzip_
     program. The HTTP/1.1 standard also recommends that the servers supporting this
-    content-encoding should recognize <code>x-gzip</code> as an alias, for compatibility
-    purposes.</dd>
-  <dt><code>compress</code></dt>
-  <dd>A format using the <a       href="https://en.wikipedia.org/wiki/LZW">Lempel-Ziv-Welch</a> (LZW) algorithm. The
-    value name was taken from the UNIX <em>compress</em> program, which implemented this
+    content-encoding should recognize `x-gzip` as an alias, for compatibility
+    purposes.
+- `compress`
+  - : A format using the [Lempel-Ziv-Welch](https://en.wikipedia.org/wiki/LZW) (LZW) algorithm. The
+    value name was taken from the UNIX _compress_ program, which implemented this
     algorithm. Like the compress program, which has disappeared from most UNIX
     distributions, this content-encoding is not used by many browsers today, partly
-    because of a patent issue (it expired in 2003).</dd>
-  <dt><code>deflate</code></dt>
-  <dd>Using the <a href="https://en.wikipedia.org/wiki/Zlib">zlib</a>
-    structure (defined in <a       href="https://tools.ietf.org/html/rfc1950">RFC 1950</a>) with the <a       href="https://en.wikipedia.org/wiki/DEFLATE"><em>deflate</em></a> compression
-    algorithm (defined in <a       href="https://datatracker.ietf.org/doc/html/rfc1951">RFC 1951</a>).</dd>
-  <dt><code>br</code></dt>
-  <dd>A format using the <a href="https://en.wikipedia.org/wiki/Brotli">Brotli</a>
-    algorithm.</dd>
-</dl>
+    because of a patent issue (it expired in 2003).
+- `deflate`
+  - : Using the [zlib](https://en.wikipedia.org/wiki/Zlib)
+    structure (defined in [RFC 1950](https://tools.ietf.org/html/rfc1950)) with the [_deflate_](https://en.wikipedia.org/wiki/DEFLATE) compression
+    algorithm (defined in [RFC 1951](https://datatracker.ietf.org/doc/html/rfc1951)).
+- `br`
+  - : A format using the [Brotli](https://en.wikipedia.org/wiki/Brotli)
+    algorithm.
 
-<h2 id="Examples">Examples</h2>
+## Examples
 
-<h3 id="Compressing_with_gzip">Compressing with gzip</h3>
+### Compressing with gzip
 
-<p>On the client side, you can advertise a list of compression schemes that will be sent
-  along in an HTTP request. The {{HTTPHeader("Accept-Encoding")}} header is used for
-  negotiating content encoding.</p>
+On the client side, you can advertise a list of compression schemes that will be sent
+along in an HTTP request. The {{HTTPHeader("Accept-Encoding")}} header is used for
+negotiating content encoding.
 
-<pre>Accept-Encoding: gzip, deflate</pre>
+    Accept-Encoding: gzip, deflate
 
-<p>The server responds with the scheme used, indicated by the
-  <code>Content-Encoding</code> response header.</p>
+The server responds with the scheme used, indicated by the
+`Content-Encoding` response header.
 
-<pre>Content-Encoding: gzip</pre>
+    Content-Encoding: gzip
 
-<p>Note that the server is not obligated to use any compression method. Compression highly
-  depends on server settings and used server modules.</p>
+Note that the server is not obligated to use any compression method. Compression highly
+depends on server settings and used server modules.
 
-<h2 id="Specifications">Specifications</h2>
+## Specifications
 
 {{Specifications}}
 
-<h2 id="Browser_compatibility">Browser compatibility</h2>
+## Browser compatibility
 
-<p>{{Compat}}</p>
+{{Compat}}
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
-  <li>{{HTTPHeader("Accept-Encoding")}}</li>
-  <li>{{HTTPHeader("Transfer-Encoding")}}</li>
-</ul>
+- {{HTTPHeader("Accept-Encoding")}}
+- {{HTTPHeader("Transfer-Encoding")}}
diff --git a/files/en-us/web/http/headers/content-language/index.md b/files/en-us/web/http/headers/content-language/index.md
index 28dc606fb2787a8..b0adb5c3a172f3c 100644
--- a/files/en-us/web/http/headers/content-language/index.md
+++ b/files/en-us/web/http/headers/content-language/index.md
@@ -7,84 +7,91 @@ tags:
   - Reference
 browser-compat: http.headers.Content-Language
 ---
-<div>{{HTTPSidebar}}</div>
+{{HTTPSidebar}}
 
-<p>The <strong><code>Content-Language</code></strong> {{Glossary("representation header")}} is used to <strong>describe the language(s) intended for the audience</strong>, so that it allows a user to differentiate according to the users' own preferred language.</p>
+The **`Content-Language`** {{Glossary("representation header")}} is used to **describe the language(s) intended for the audience**, so that it allows a user to differentiate according to the users' own preferred language.
 
-<p>For example, if "<code>Content-Language: de-DE</code>" is set, it says that the document is intended for German language speakers (however, it doesn't indicate the document is written in German. For example, it might be written in English as part of a language course for German speakers. If you want to indicate which language the document is written in, use the <a href="/en-US/docs/Web/HTML/Global_attributes/lang"><code>lang</code> attribute</a> instead).</p>
+For example, if "`Content-Language: de-DE`" is set, it says that the document is intended for German language speakers (however, it doesn't indicate the document is written in German. For example, it might be written in English as part of a language course for German speakers. If you want to indicate which language the document is written in, use the [`lang` attribute](/en-US/docs/Web/HTML/Global_attributes/lang) instead).
 
-<p>If no <code>Content-Language</code> is specified, the default is that the content is intended for all language audiences. Multiple language tags are also possible, as well as applying the <code>Content-Language</code> header to various media types and not only to textual documents.</p>
+If no `Content-Language` is specified, the default is that the content is intended for all language audiences. Multiple language tags are also possible, as well as applying the `Content-Language` header to various media types and not only to textual documents.
 
 <table class="properties">
- <tbody>
-  <tr>
-   <th scope="row">Header type</th>
-   <td>{{Glossary("Representation header")}}</td>
-  </tr>
-  <tr>
-   <th scope="row">{{Glossary("Forbidden header name")}}</th>
-   <td>no</td>
-  </tr>
-  <tr>
-   <th scope="row">{{Glossary("CORS-safelisted response header")}}</th>
-   <td>yes</td>
-  </tr>
-  <tr>
-   <th scope="row">{{Glossary("CORS-safelisted request header")}}</th>
-   <td>yes, with the additional restriction that values can only be <code>0-9</code>, <code>A-Z</code>, <code>a-z</code>, space or <code>*,-.;=</code>.</td>
-  </tr>
- </tbody>
+  <tbody>
+    <tr>
+      <th scope="row">Header type</th>
+      <td>{{Glossary("Representation header")}}</td>
+    </tr>
+    <tr>
+      <th scope="row">{{Glossary("Forbidden header name")}}</th>
+      <td>no</td>
+    </tr>
+    <tr>
+      <th scope="row">
+        {{Glossary("CORS-safelisted response header")}}
+      </th>
+      <td>yes</td>
+    </tr>
+    <tr>
+      <th scope="row">
+        {{Glossary("CORS-safelisted request header")}}
+      </th>
+      <td>
+        yes, with the additional restriction that values can only be
+        <code>0-9</code>, <code>A-Z</code>, <code>a-z</code>, space or
+        <code>*,-.;=</code>.
+      </td>
+    </tr>
+  </tbody>
 </table>
 
-<h2 id="Syntax">Syntax</h2>
+## Syntax
 
-<pre class="brush: html">Content-Language: de-DE
+```html
+Content-Language: de-DE
 Content-Language: en-US
 Content-Language: de-DE, en-CA
-</pre>
+```
 
-<h2 id="Directives">Directives</h2>
+## Directives
 
-<dl>
- <dt><code>language-tag</code></dt>
- <dd>Multiple language tags are separated by comma. Each language tag is a sequence of one or more case-insensitive subtags, each separated by a hyphen character ("<code>-</code>", <code>%x2D</code>). In most cases, a language tag consists of a primary language subtag that identifies a broad family of related languages (e.g., "<code>en</code>" = English), which is optionally followed by a series of subtags that refine or narrow that language's range (e.g., "<code>en-CA</code>" = the variety of English as communicated in Canada).</dd>
-</dl>
+- `language-tag`
+  - : Multiple language tags are separated by comma. Each language tag is a sequence of one or more case-insensitive subtags, each separated by a hyphen character ("`-`", `%x2D`). In most cases, a language tag consists of a primary language subtag that identifies a broad family of related languages (e.g., "`en`" = English), which is optionally followed by a series of subtags that refine or narrow that language's range (e.g., "`en-CA`" = the variety of English as communicated in Canada).
 
-<div class="notecard note">
-  <p><strong>Note:</strong> Language tags are formaly defined in <a href="https://datatracker.ietf.org/doc/html/rfc5646">RFC 5646</a>, which rely on the <a href="https://en.wikipedia.org/wiki/ISO_639">ISO 639</a> standard (quite often the <a href="https://en.wikipedia.org/wiki/List_of_ISO_639-1_codes">ISO 639-1 code list</a>) for <a href="https://en.wikipedia.org/wiki/Language_code">language codes</a> to be used.</p>
-</div>
+> **Note:** Language tags are formaly defined in [RFC 5646](https://datatracker.ietf.org/doc/html/rfc5646), which rely on the [ISO 639](https://en.wikipedia.org/wiki/ISO_639) standard (quite often the [ISO 639-1 code list](https://en.wikipedia.org/wiki/List_of_ISO_639-1_codes)) for [language codes](https://en.wikipedia.org/wiki/Language_code) to be used.
 
-<h2 id="Examples">Examples</h2>
+## Examples
 
-<h3 id="Indicating_the_language_a_document_is_written_in">Indicating the language a document is written in</h3>
+### Indicating the language a document is written in
 
-<p>The global <code><a href="/en-US/docs/Web/HTML/Global_attributes/lang">lang</a></code> attribute is used on HTML elements to indicate the language of an entire <a href="/en-US/docs/Web/HTML">HTML</a> document or parts of it.</p>
+The global [`lang`](/en-US/docs/Web/HTML/Global_attributes/lang) attribute is used on HTML elements to indicate the language of an entire [HTML](/en-US/docs/Web/HTML) document or parts of it.
 
-<pre class="brush: html">&lt;html lang="de"&gt;</pre>
+```html
+<html lang="de">
+```
 
-<p>Do <strong>not</strong> use this meta element like this for stating a document language:</p>
+Do **not** use this meta element like this for stating a document language:
 
-<pre class="brush: html example-bad">&lt;!-- /!\ This is bad practice --&gt;
-&lt;meta http-equiv="content-language" content="de"&gt;</pre>
+```html example-bad
+<!-- /!\ This is bad practice -->
+<meta http-equiv="content-language" content="de">
+```
 
-<h3 id="Indicating_a_target_audience_for_a_resource">Indicating a target audience for a resource</h3>
+### Indicating a target audience for a resource
 
-<p>The <code>Content-Language</code> header is used to specify the <strong>intended audience of the page</strong>, and can indicate that this is more than one language.</p>
+The `Content-Language` header is used to specify the **intended audience of the page**, and can indicate that this is more than one language.
 
-<pre>Content-Language: de, en</pre>
+    Content-Language: de, en
 
-<h2 id="Specifications">Specifications</h2>
+## Specifications
 
 {{Specifications}}
 
-<h2 id="Browser_compatibility">Browser compatibility</h2>
+## Browser compatibility
 
-<p>{{Compat}}</p>
+{{Compat}}
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
- <li>{{HTTPHeader("Accept-Language")}}</li>
- <li><a href="https://www.w3.org/International/questions/qa-http-and-lang.en">HTTP headers, meta elements and language information</a></li>
- <li><a href="/en-US/docs/Web/HTML/Global_attributes/lang">HTML <code>lang</code> attribute</a></li>
-</ul>
+- {{HTTPHeader("Accept-Language")}}
+- [HTTP headers, meta elements and language information](https://www.w3.org/International/questions/qa-http-and-lang.en)
+- [HTML `lang` attribute](/en-US/docs/Web/HTML/Global_attributes/lang)
diff --git a/files/en-us/web/http/headers/content-length/index.md b/files/en-us/web/http/headers/content-length/index.md
index edffad223aec95e..af0cc616e46b80f 100644
--- a/files/en-us/web/http/headers/content-length/index.md
+++ b/files/en-us/web/http/headers/content-length/index.md
@@ -11,49 +11,52 @@ tags:
   - Payload header
 browser-compat: http.headers.Content-Length
 ---
-<div>{{HTTPSidebar}}</div>
+{{HTTPSidebar}}
 
-<p>The <strong><code>Content-Length</code></strong> header indicates the size of the message body, in bytes, sent to the recipient.</p>
+The **`Content-Length`** header indicates the size of the message body, in bytes, sent to the recipient.
 
 <table class="properties">
   <tbody>
     <tr>
       <th scope="row">Header type</th>
-      <td>{{Glossary("Request header")}}, {{Glossary("Response header")}}, {{Glossary("Payload header")}}</td>
+      <td>
+        {{Glossary("Request header")}},
+        {{Glossary("Response header")}},
+        {{Glossary("Payload header")}}
+      </td>
     </tr>
     <tr>
       <th scope="row">{{Glossary("Forbidden header name")}}</th>
       <td>yes</td>
     </tr>
     <tr>
-      <th scope="row">{{Glossary("CORS-safelisted response header")}}</th>
+      <th scope="row">
+        {{Glossary("CORS-safelisted response header")}}
+      </th>
       <td>yes</td>
     </tr>
   </tbody>
 </table>
 
-<h2 id="Syntax">Syntax</h2>
+## Syntax
 
-<pre class="brush: html">Content-Length: &lt;length&gt;
-</pre>
+```html
+Content-Length: <length>
+```
 
-<h2 id="Directives">Directives</h2>
+## Directives
 
-<dl>
-  <dt>&lt;length&gt;</dt>
-  <dd>The length in decimal number of octets.</dd>
-</dl>
+- \<length>
+  - : The length in decimal number of octets.
 
-<h2 id="Specifications">Specifications</h2>
+## Specifications
 
 {{Specifications}}
 
-<h2 id="Browser_compatibility">Browser compatibility</h2>
+## Browser compatibility
 
-<p>{{Compat}}</p>
+{{Compat}}
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
-  <li>{{HTTPHeader("Transfer-Encoding")}}</li>
-</ul>
+- {{HTTPHeader("Transfer-Encoding")}}
diff --git a/files/en-us/web/http/headers/content-location/index.md b/files/en-us/web/http/headers/content-location/index.md
index 4c7c91ead98249f..979e1e5958a653f 100644
--- a/files/en-us/web/http/headers/content-location/index.md
+++ b/files/en-us/web/http/headers/content-location/index.md
@@ -7,20 +7,19 @@ tags:
   - header
 browser-compat: http.headers.Content-Location
 ---
-<div>{{HTTPSidebar}}</div>
+{{HTTPSidebar}}
 
-<p>The <strong><code>Content-Location</code></strong> header indicates an alternate
-  location for the returned data. The principal use is to indicate the URL of a resource
-  transmitted as the result of <a href="/en-US/docs/Web/HTTP/Content_negotiation">content
-    negotiation</a>.</p>
+The **`Content-Location`** header indicates an alternate
+location for the returned data. The principal use is to indicate the URL of a resource
+transmitted as the result of [content
+negotiation](/en-US/docs/Web/HTTP/Content_negotiation).
 
-<p>{{HTTPHeader("Location")}} and <code>Content-Location</code> are different.
-  <code>Location</code> indicates the URL of a redirect, while
-  <code>Content-Location</code> indicates the direct URL to use to access the resource,
-  without further content negotiation in the future. <code>Location</code> is a header
-  associated with the response, while <code>Content-Location</code> is associated with the
-  data returned. This distinction may seem abstract without <a
-    href="#examples">examples</a>.</p>
+{{HTTPHeader("Location")}} and `Content-Location` are different.
+`Location` indicates the URL of a redirect, while
+`Content-Location` indicates the direct URL to use to access the resource,
+without further content negotiation in the future. `Location` is a header
+associated with the response, while `Content-Location` is associated with the
+data returned. This distinction may seem abstract without [examples](#examples).
 
 <table class="properties">
   <tbody>
@@ -35,144 +34,114 @@ browser-compat: http.headers.Content-Location
   </tbody>
 </table>
 
-<h2 id="Syntax">Syntax</h2>
+## Syntax
 
-<pre class="brush: html">Content-Location: &lt;url&gt;
-</pre>
+```html
+Content-Location: <url>
+```
 
-<h2 id="Directives">Directives</h2>
+## Directives
 
-<dl>
-  <dt>&lt;url&gt;</dt>
-  <dd>A <a
-      href="/en-US/docs/Learn/Common_questions/What_is_a_URL#examples_of_relative_urls">relative</a>
-    (to the request URL) or <a
-      href="/en-US/docs/Learn/Common_questions/What_is_a_URL#examples_of_absolute_urls">absolute</a>
-    URL.</dd>
-</dl>
+- \<url>
+  - : A [relative](/en-US/docs/Learn/Common_questions/What_is_a_URL#examples_of_relative_urls)
+    (to the request URL) or [absolute](/en-US/docs/Learn/Common_questions/What_is_a_URL#examples_of_absolute_urls)
+    URL.
 
-<h2 id="Examples">Examples</h2>
+## Examples
 
-<h3 id="Requesting_data_from_a_server_in_different_formats">Requesting data from a server
-  in different formats</h3>
+### Requesting data from a server in different formats
 
-<p>Let's say a site's API can return data in {{glossary("JSON")}}, {{glossary("XML")}}, or
-  <a href="https://en.wikipedia.org/wiki/Comma-separated_values" rel="external"
-    title="Comma-separated values">CSV</a> formats. If the URL for a particular document
-  is at <code>https://example.com/documents/foo</code>, the site could return different
-  URLs for <code>Content-Location</code> depending on the request's
-  {{HTTPHeader("Accept")}} header:</p>
+Let's say a site's API can return data in {{glossary("JSON")}}, {{glossary("XML")}}, or
+[CSV](https://en.wikipedia.org/wiki/Comma-separated_values "Comma-separated values") formats. If the URL for a particular document
+is at `https://example.com/documents/foo`, the site could return different
+URLs for `Content-Location` depending on the request's
+{{HTTPHeader("Accept")}} header:
 
-<table class="standard-table">
-  <thead>
-    <tr>
-      <th scope="col">Request header</th>
-      <th scope="col">Response header</th>
-    </tr>
-  </thead>
-  <tbody>
-    <tr>
-      <td><code>Accept: application/json, text/json</code></td>
-      <td><code>Content-Location: /documents/foo.json</code></td>
-    </tr>
-    <tr>
-      <td><code>Accept: application/xml, text/xml</code></td>
-      <td><code>Content-Location: /documents/foo.xml</code></td>
-    </tr>
-    <tr>
-      <td><code>Accept: text/plain, text/*</code></td>
-      <td><code>Content-Location: /documents/foo.txt</code></td>
-    </tr>
-  </tbody>
-</table>
+| Request header                        | Response header                         |
+| ------------------------------------- | --------------------------------------- |
+| `Accept: application/json, text/json` | `Content-Location: /documents/foo.json` |
+| `Accept: application/xml, text/xml`   | `Content-Location: /documents/foo.xml`  |
+| `Accept: text/plain, text/*`          | `Content-Location: /documents/foo.txt`  |
 
-<p>These URLs are examples — the site could serve the different filetypes with any URL
-  patterns it wishes, such as a <a
-    href="/en-US/docs/Web/API/HTMLAnchorElement/search">query string
-    parameter</a>: <code>/documents/foo?format=json</code>,
-  <code>/documents/foo?format=xml</code>, and so on.</p>
+These URLs are examples — the site could serve the different filetypes with any URL
+patterns it wishes, such as a [query string
+parameter](/en-US/docs/Web/API/HTMLAnchorElement/search): `/documents/foo?format=json`,
+`/documents/foo?format=xml`, and so on.
 
-<p>Then the client could remember that the JSON version is available at that particular
-  URL, skipping content negotation the next time it requests that document.</p>
+Then the client could remember that the JSON version is available at that particular
+URL, skipping content negotation the next time it requests that document.
 
-<p>The server could also consider other <a
-    href="/en-US/docs/Web/HTTP/Content_negotiation">content negotiation</a> headers, such
-  as {{HTTPHeader("Accept-Language")}}.</p>
+The server could also consider other [content negotiation](/en-US/docs/Web/HTTP/Content_negotiation) headers, such
+as {{HTTPHeader("Accept-Language")}}.
 
-<h3 id="Pointing_to_a_new_document_HTTP_201_Created">Pointing to a new document (HTTP 201
-  Created)</h3>
+### Pointing to a new document (HTTP 201 Created)
 
-<p>Say you're creating a new blog post through a site's API:</p>
+Say you're creating a new blog post through a site's API:
 
-<pre>PUT /new/post
-Host: example.com
-Content-Type: text/markdown
+    PUT /new/post
+    Host: example.com
+    Content-Type: text/markdown
 
-# My first blog post!
+    # My first blog post!
 
-I made this through `example.com`'s API. I hope it worked.
-</pre>
+    I made this through `example.com`'s API. I hope it worked.
 
-<p>The site returns a generic success message confirming the post was published. The
-  server specifies <em>where</em> the new post is with <code>Content-Location</code>:</p>
+The site returns a generic success message confirming the post was published. The
+server specifies _where_ the new post is with `Content-Location`:
 
-<pre>HTTP/1.1 201 Created
-Content-Type: text/plain; charset=utf-8
-Content-Location: /my-first-blog-post
+    HTTP/1.1 201 Created
+    Content-Type: text/plain; charset=utf-8
+    Content-Location: /my-first-blog-post
 
-✅ Success!
-</pre>
+    ✅ Success!
 
-<h3 id="Indicating_the_URL_of_a_transactions_result">Indicating the URL of a transaction's
-  result</h3>
+### Indicating the URL of a transaction's result
 
-<p>Say you have a
-  <code><a href="/en-US/docs/Web/HTML/Element/form">&lt;form&gt;</a></code> for sending
-  money to another user of a site.</p>
+Say you have a
+[`<form>`](/en-US/docs/Web/HTML/Element/form) for sending
+money to another user of a site.
 
-<pre class="brush: html">&lt;form action="/send-payment" method="post"&gt;
-  &lt;p&gt;
-    &lt;label&gt;Who do you want to send the money to?
-      &lt;input type="text" name="recipient"&gt;
-    &lt;/label&gt;
-  &lt;/p&gt;
+```html
+<form action="/send-payment" method="post">
+  <p>
+    <label>Who do you want to send the money to?
+      <input type="text" name="recipient">
+    </label>
+  </p>
 
-  &lt;p&gt;
-    &lt;label&gt;How much?
-      &lt;input type="number" name="amount"&gt;
-    &lt;/label&gt;
-  &lt;/p&gt;
+  <p>
+    <label>How much?
+      <input type="number" name="amount">
+    </label>
+  </p>
 
-  &lt;button type="submit"&gt;Send Money&lt;/button&gt;
-&lt;/form&gt;
-</pre>
+  <button type="submit">Send Money</button>
+</form>
+```
 
-<p>When the form is submitted, the site generates a receipt for the transaction. The
-  server could use <code>Content-Location</code> to indicate that receipt's URL for future
-  access.</p>
+When the form is submitted, the site generates a receipt for the transaction. The
+server could use `Content-Location` to indicate that receipt's URL for future
+access.
 
-<pre>HTTP/1.1 200 OK
-Content-Type: text/html; charset=utf-8
-Content-Location: /my-receipts/38
+    HTTP/1.1 200 OK
+    Content-Type: text/html; charset=utf-8
+    Content-Location: /my-receipts/38
 
-&lt;!doctype html&gt;
-<em>(Lots of HTML…)</em>
+    <!doctype html>
+    (Lots of HTML…)
 
-&lt;p&gt;You sent $38.00 to ExampleUser.&lt;/p&gt;
+    <p>You sent $38.00 to ExampleUser.</p>
 
-<em>(Lots more HTML…)</em>
-</pre>
+    (Lots more HTML…)
 
-<h2 id="Specifications">Specifications</h2>
+## Specifications
 
 {{Specifications}}
 
-<h2 id="Browser_compatibility">Browser compatibility</h2>
+## Browser compatibility
 
-<p>{{Compat}}</p>
+{{Compat}}
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
-  <li>{{HTTPHeader("Location")}}</li>
-</ul>
+- {{HTTPHeader("Location")}}
diff --git a/files/en-us/web/http/headers/content-range/index.md b/files/en-us/web/http/headers/content-range/index.md
index b5c0614a70e8272..38df63077b12218 100644
--- a/files/en-us/web/http/headers/content-range/index.md
+++ b/files/en-us/web/http/headers/content-range/index.md
@@ -2,75 +2,77 @@
 title: Content-Range
 slug: Web/HTTP/Headers/Content-Range
 tags:
-- HTTP
-- HTTP Header
-- Reference
-- Response Header
-- Header
-- Payload header
+  - HTTP
+  - HTTP Header
+  - Reference
+  - Response Header
+  - Header
+  - Payload header
 browser-compat: http.headers.Content-Range
 ---
-<div>{{HTTPSidebar}}</div>
+{{HTTPSidebar}}
 
-<p>The <strong><code>Content-Range</code></strong> response HTTP header indicates where in
-  a full body message a partial message belongs.</p>
+The **`Content-Range`** response HTTP header indicates where in
+a full body message a partial message belongs.
 
 <table class="properties">
   <tbody>
     <tr>
       <th scope="row">Header type</th>
-      <td>{{Glossary("Response header")}}, {{Glossary("Payload header")}}</td>
+      <td>
+        {{Glossary("Response header")}},
+        {{Glossary("Payload header")}}
+      </td>
     </tr>
     <tr>
       <th scope="row">{{Glossary("Forbidden header name")}}</th>
       <td>no</td>
     </tr>
     <tr>
-      <th scope="row">{{Glossary("Simple response header", "CORS-safelisted
-        response-header")}}</th>
+      <th scope="row">
+        {{Glossary("Simple response header", "CORS-safelisted
+        response-header")}}
+      </th>
       <td>no</td>
     </tr>
   </tbody>
 </table>
 
-<h2 id="Syntax">Syntax</h2>
+## Syntax
 
-<pre class="brush: html">Content-Range: &lt;unit&gt; &lt;range-start&gt;-&lt;range-end&gt;/&lt;size&gt;
-Content-Range: &lt;unit&gt; &lt;range-start&gt;-&lt;range-end&gt;/*
-Content-Range: &lt;unit&gt; */&lt;size&gt;</pre>
+```html
+Content-Range: <unit> <range-start>-<range-end>/<size>
+Content-Range: <unit> <range-start>-<range-end>/*
+Content-Range: <unit> */<size>
+```
 
-<h2 id="Directives">Directives</h2>
+## Directives
 
-<dl>
-  <dt>&lt;unit&gt;</dt>
-  <dd>The unit in which ranges are specified. This is usually <code>bytes</code>.</dd>
-  <dt>&lt;range-start&gt;</dt>
-  <dd>An integer in the given unit indicating the beginning of the request range.</dd>
-  <dt>&lt;range-end&gt;</dt>
-  <dd>An integer in the given unit indicating the end of the requested range.</dd>
-  <dt>&lt;size&gt;</dt>
-  <dd>The total size of the document (or <code>'*'</code> if unknown).</dd>
-</dl>
+- \<unit>
+  - : The unit in which ranges are specified. This is usually `bytes`.
+- \<range-start>
+  - : An integer in the given unit indicating the beginning of the request range.
+- \<range-end>
+  - : An integer in the given unit indicating the end of the requested range.
+- \<size>
+  - : The total size of the document (or `'*'` if unknown).
 
-<h2 id="Examples">Examples</h2>
+## Examples
 
-<pre>Content-Range: bytes 200-1000/67589
-</pre>
+    Content-Range: bytes 200-1000/67589
 
-<h2 id="Specifications">Specifications</h2>
+## Specifications
 
 {{Specifications}}
 
-<h2 id="Browser_compatibility">Browser compatibility</h2>
+## Browser compatibility
 
-<p>{{Compat}}</p>
+{{Compat}}
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
-  <li>{{HTTPHeader("If-Range")}}</li>
-  <li>{{HTTPHeader("Range")}}</li>
-  <li>{{HTTPHeader("Content-Type")}}</li>
-  <li>{{HTTPStatus("206")}} <code>Partial Content</code></li>
-  <li>{{HTTPStatus("416")}} <code>Range Not Satisfiable</code></li>
-</ul>
+- {{HTTPHeader("If-Range")}}
+- {{HTTPHeader("Range")}}
+- {{HTTPHeader("Content-Type")}}
+- {{HTTPStatus("206")}} `Partial Content`
+- {{HTTPStatus("416")}} `Range Not Satisfiable`
diff --git a/files/en-us/web/http/headers/content-security-policy-report-only/index.md b/files/en-us/web/http/headers/content-security-policy-report-only/index.md
index cbaf1102429faaf..e96c37fca7ef1db 100644
--- a/files/en-us/web/http/headers/content-security-policy-report-only/index.md
+++ b/files/en-us/web/http/headers/content-security-policy-report-only/index.md
@@ -10,96 +10,101 @@ tags:
   - header
 browser-compat: http.headers.Content-Security-Policy-Report-Only
 ---
-<div>{{HTTPSidebar}}</div>
+{{HTTPSidebar}}
 
-<p><span class="summary">The HTTP <strong><code>Content-Security-Policy-Report-Only</code></strong> response header allows web developers to experiment with policies by monitoring (but not enforcing) their effects. These violation reports consist of {{Glossary("JSON")}} documents sent via an HTTP <code>POST</code> request to the specified URI.</span></p>
+The HTTP **`Content-Security-Policy-Report-Only`** response header allows web developers to experiment with policies by monitoring (but not enforcing) their effects. These violation reports consist of {{Glossary("JSON")}} documents sent via an HTTP `POST` request to the specified URI.
 
-<p>For more information, see also this article on <a href="/en-US/docs/Web/HTTP/CSP">Content Security Policy (CSP)</a>.</p>
+For more information, see also this article on [Content Security Policy (CSP)](/en-US/docs/Web/HTTP/CSP).
 
 <table class="properties">
- <tbody>
-  <tr>
-   <th scope="row">Header type</th>
-   <td>{{Glossary("Response header")}}</td>
-  </tr>
-  <tr>
-   <th scope="row">{{Glossary("Forbidden header name")}}</th>
-   <td>no</td>
-  </tr>
-  <tr>
-   <th colspan="2" scope="row">This header is not supported inside a {{HTMLElement("meta")}} element.</th>
-  </tr>
- </tbody>
+  <tbody>
+    <tr>
+      <th scope="row">Header type</th>
+      <td>{{Glossary("Response header")}}</td>
+    </tr>
+    <tr>
+      <th scope="row">{{Glossary("Forbidden header name")}}</th>
+      <td>no</td>
+    </tr>
+    <tr>
+      <th colspan="2" scope="row">
+        This header is not supported inside a {{HTMLElement("meta")}}
+        element.
+      </th>
+    </tr>
+  </tbody>
 </table>
 
-<h2 id="Syntax">Syntax</h2>
+## Syntax
 
-<pre class="brush: html">Content-Security-Policy-Report-Only: &lt;policy-directive&gt;; &lt;policy-directive&gt;
-</pre>
+```html
+Content-Security-Policy-Report-Only: <policy-directive>; <policy-directive>
+```
 
-<h2 id="Directives">Directives</h2>
+## Directives
 
-<p>The directives of the {{HTTPHeader("Content-Security-Policy")}} header can also be applied to <code>Content-Security-Policy-Report-Only</code>.</p>
+The directives of the {{HTTPHeader("Content-Security-Policy")}} header can also be applied to `Content-Security-Policy-Report-Only`.
 
-<p>The CSP {{CSP("report-uri")}} directive should be used with this header, otherwise this header will be an expensive no-op machine.</p>
+The CSP {{CSP("report-uri")}} directive should be used with this header, otherwise this header will be an expensive no-op machine.
 
-<h2 id="Examples">Examples</h2>
+## Examples
 
-<p>This header reports violations that would have occurred. You can use this to iteratively work on your content security policy. You observe how your site behaves, watching for violation reports, or <a href="https://secure.wphackedhelp.com/blog/wordpress-malware-redirect-hack-cleanup/">malware redirects</a>, then choose the desired policy enforced by the {{HTTPHeader("Content-Security-Policy")}} header.</p>
+This header reports violations that would have occurred. You can use this to iteratively work on your content security policy. You observe how your site behaves, watching for violation reports, or [malware redirects](https://secure.wphackedhelp.com/blog/wordpress-malware-redirect-hack-cleanup/), then choose the desired policy enforced by the {{HTTPHeader("Content-Security-Policy")}} header.
 
-<pre>Content-Security-Policy-Report-Only: default-src https:; report-uri /csp-violation-report-endpoint/</pre>
+    Content-Security-Policy-Report-Only: default-src https:; report-uri /csp-violation-report-endpoint/
 
-<p>If you still want to receive reporting, but also want to enforce a policy, use the {{HTTPHeader("Content-Security-Policy")}} header with the {{CSP("report-uri")}} directive.</p>
+If you still want to receive reporting, but also want to enforce a policy, use the {{HTTPHeader("Content-Security-Policy")}} header with the {{CSP("report-uri")}} directive.
 
-<pre>Content-Security-Policy: default-src https:; report-uri /csp-violation-report-endpoint/</pre>
+    Content-Security-Policy: default-src https:; report-uri /csp-violation-report-endpoint/
 
-<h2 id="Violation_report_syntax">Violation report syntax</h2>
+## Violation report syntax
 
-<p>The report JSON object contains the following data:</p>
+The report JSON object contains the following data:
 
-<dl>
- <dt><code>blocked-uri</code></dt>
- <dd>The URI of the resource that was blocked from loading by the Content Security Policy. If the blocked URI is from a different origin than the document-uri, then the blocked URI is truncated to contain just the scheme, host, and port.</dd>
- <dt><code>disposition</code></dt>
- <dd>Either <code>"enforce"</code> or <code>"report"</code> depending on whether the {{HTTPHeader("Content-Security-Policy")}} header or the <code>Content-Security-Policy-Report-Only</code> header is used.</dd>
- <dt><code>document-uri</code></dt>
- <dd>The URI of the document in which the violation occurred.</dd>
- <dt><code>effective-directive</code></dt>
- <dd>The directive whose enforcement caused the violation.</dd>
- <dt><code>original-policy</code></dt>
- <dd>The original policy as specified by the <code>Content-Security-Policy-Report-Only</code> HTTP header.</dd>
- <dt><code>referrer</code></dt>
- <dd>The referrer of the document in which the violation occurred.</dd>
- <dt><code>script-sample</code></dt>
- <dd>The first 40 characters of the inline script, event handler, or style that caused the violation.</dd>
- <dt><code>status-code</code></dt>
- <dd>The HTTP status code of the resource on which the global object was instantiated.</dd>
- <dt><code>violated-directive</code></dt>
- <dd>The name of the policy section that was violated.</dd>
-</dl>
+- `blocked-uri`
+  - : The URI of the resource that was blocked from loading by the Content Security Policy. If the blocked URI is from a different origin than the document-uri, then the blocked URI is truncated to contain just the scheme, host, and port.
+- `disposition`
+  - : Either `"enforce"` or `"report"` depending on whether the {{HTTPHeader("Content-Security-Policy")}} header or the `Content-Security-Policy-Report-Only` header is used.
+- `document-uri`
+  - : The URI of the document in which the violation occurred.
+- `effective-directive`
+  - : The directive whose enforcement caused the violation.
+- `original-policy`
+  - : The original policy as specified by the `Content-Security-Policy-Report-Only` HTTP header.
+- `referrer`
+  - : The referrer of the document in which the violation occurred.
+- `script-sample`
+  - : The first 40 characters of the inline script, event handler, or style that caused the violation.
+- `status-code`
+  - : The HTTP status code of the resource on which the global object was instantiated.
+- `violated-directive`
+  - : The name of the policy section that was violated.
 
-<h2 id="Sample_violation_report">Sample violation report</h2>
+## Sample violation report
 
-<p>Let's consider a page located at <code>http://example.com/signup.html</code>. It uses the following policy, disallowing everything but stylesheets from <code>cdn.example.com</code>.</p>
+Let's consider a page located at `http://example.com/signup.html`. It uses the following policy, disallowing everything but stylesheets from `cdn.example.com`.
 
-<pre>Content-Security-Policy-Report-Only: default-src 'none'; style-src cdn.example.com; report-uri /_/csp-reports</pre>
+    Content-Security-Policy-Report-Only: default-src 'none'; style-src cdn.example.com; report-uri /_/csp-reports
 
-<p>The HTML of <code>signup.html</code> looks like this:</p>
+The HTML of `signup.html` looks like this:
 
-<pre class="brush: html">&lt;!DOCTYPE html&gt;
-&lt;html&gt;
-  &lt;head&gt;
-    &lt;title&gt;Sign Up&lt;/title&gt;
-    &lt;link rel="stylesheet" href="css/style.css"&gt;
-  &lt;/head&gt;
-  &lt;body&gt;
+```html
+<!DOCTYPE html>
+<html>
+  <head>
+    <title>Sign Up</title>
+    <link rel="stylesheet" href="css/style.css">
+  </head>
+  <body>
     ... Content ...
-  &lt;/body&gt;
-&lt;/html&gt;</pre>
+  </body>
+</html>
+```
 
-<p>Can you spot the violation? Stylesheets are only allowed to be loaded from <code>cdn.example.com</code>, yet the website tries to load one from its own origin (<code>http://example.com</code>). A browser capable of enforcing CSP will send the following violation report as a POST request to <code>http://example.com/_/csp-reports</code>, when the document is visited:</p>
+Can you spot the violation? Stylesheets are only allowed to be loaded from `cdn.example.com`, yet the website tries to load one from its own origin (`http://example.com`). A browser capable of enforcing CSP will send the following violation report as a POST request to `http://example.com/_/csp-reports`, when the document is visited:
 
-<pre class="brush: js">{
+```js
+{
   "csp-report": {
     "document-uri": "http://example.com/signup.html",
     "referrer": "",
@@ -108,21 +113,20 @@ browser-compat: http.headers.Content-Security-Policy-Report-Only
     "original-policy": "default-src 'none'; style-src cdn.example.com; report-uri /_/csp-reports",
     "disposition": "report"
   }
-}</pre>
+}
+```
 
-<p>As you can see, the report includes the full path to the violating resource in <code>blocked-uri</code>. This is not always the case. For example, when the <code>signup.html</code> would attempt to load CSS from <code>http://anothercdn.example.com/stylesheet.css</code>, the browser would <em>not</em> include the full path but only the origin (<code>http://anothercdn.example.com</code>). This is done to prevent leaking sensitive information about cross-origin resources.</p>
+As you can see, the report includes the full path to the violating resource in `blocked-uri`. This is not always the case. For example, when the `signup.html` would attempt to load CSS from `http://anothercdn.example.com/stylesheet.css`, the browser would _not_ include the full path but only the origin (`http://anothercdn.example.com`). This is done to prevent leaking sensitive information about cross-origin resources.
 
-<h2 id="Specifications">Specifications</h2>
+## Specifications
 
 {{Specifications}}
 
-<h2 id="Browser_compatibility">Browser compatibility</h2>
+## Browser compatibility
 
-<p>{{Compat}}</p>
+{{Compat}}
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
- <li>{{HTTPHeader("Content-Security-Policy")}}</li>
- <li>CSP {{CSP("report-uri")}} directive</li>
-</ul>
+- {{HTTPHeader("Content-Security-Policy")}}
+- CSP {{CSP("report-uri")}} directive
diff --git a/files/en-us/web/http/headers/content-security-policy/base-uri/index.md b/files/en-us/web/http/headers/content-security-policy/base-uri/index.md
index 602490efd3a736f..7f1b5806a46e46e 100644
--- a/files/en-us/web/http/headers/content-security-policy/base-uri/index.md
+++ b/files/en-us/web/http/headers/content-security-policy/base-uri/index.md
@@ -9,80 +9,87 @@ tags:
   - Security
 browser-compat: http.headers.csp.Content-Security-Policy.base-uri
 ---
-<div>{{HTTPSidebar}}</div>
+{{HTTPSidebar}}
 
-<p>The HTTP {{HTTPHeader("Content-Security-Policy")}} <strong><code>base-uri</code></strong> directive restricts the URLs which can be used in a document's {{HTMLElement("base")}} element. If this value is absent, then any URI is allowed. If this directive is absent, the user agent will use the value in the {{HTMLElement("base")}} element.</p>
+The HTTP {{HTTPHeader("Content-Security-Policy")}} **`base-uri`** directive restricts the URLs which can be used in a document's {{HTMLElement("base")}} element. If this value is absent, then any URI is allowed. If this directive is absent, the user agent will use the value in the {{HTMLElement("base")}} element.
 
 <table class="properties">
- <tbody>
-  <tr>
-   <th scope="row">CSP version</th>
-   <td>2</td>
-  </tr>
-  <tr>
-   <th scope="row">Directive type</th>
-   <td>{{Glossary("Document directive")}}</td>
-  </tr>
-  <tr>
-   <th scope="row">{{CSP("default-src")}} fallback</th>
-   <td>No. Not setting this allows any URL.</td>
-  </tr>
- </tbody>
+  <tbody>
+    <tr>
+      <th scope="row">CSP version</th>
+      <td>2</td>
+    </tr>
+    <tr>
+      <th scope="row">Directive type</th>
+      <td>{{Glossary("Document directive")}}</td>
+    </tr>
+    <tr>
+      <th scope="row">{{CSP("default-src")}} fallback</th>
+      <td>No. Not setting this allows any URL.</td>
+    </tr>
+  </tbody>
 </table>
 
-<h2 id="Syntax">Syntax</h2>
+## Syntax
 
-<p>One or more<em>sources</em> can be allowed for the base-uri policy:</p>
+One or more*sources* can be allowed for the base-uri policy:
 
-<pre class="brush: html">Content-Security-Policy: base-uri &lt;source&gt;;
-Content-Security-Policy: base-uri &lt;source&gt; &lt;source&gt;;
-</pre>
+```html
+Content-Security-Policy: base-uri <source>;
+Content-Security-Policy: base-uri <source> <source>;
+```
 
-<h3 id="Sources">Sources</h3>
+### Sources
 
-<p>While this directive uses the same arguments as other CSP directives, some of them don’t make sense for `&lt;base&gt;`, such as the keywords <code>'unsafe-inline'</code> and <code>'strict-dynamic'</code></p>
+While this directive uses the same arguments as other CSP directives, some of them don’t make sense for \`\<base>\`, such as the keywords `'unsafe-inline'` and `'strict-dynamic'`
 
-<p>{{page("Web/HTTP/Headers/Content-Security-Policy/default-src", "Sources")}}</p>
+{{page("Web/HTTP/Headers/Content-Security-Policy/default-src", "Sources")}}
 
-<h2 id="Examples">Examples</h2>
+## Examples
 
-<h3 id="Meta_tag_configuration">Meta tag configuration</h3>
+### Meta tag configuration
 
-<pre class="brush: html">&lt;meta http-equiv="Content-Security-Policy" content="base-uri 'self'"&gt;</pre>
+```html
+<meta http-equiv="Content-Security-Policy" content="base-uri 'self'">
+```
 
-<h3 id="Apache_configuration">Apache configuration</h3>
+### Apache configuration
 
-<pre class="brush: bash">&lt;IfModule mod_headers.c&gt;
+```bash
+<IfModule mod_headers.c>
 Header set Content-Security-Policy "base-uri 'self'";
-&lt;/IfModule&gt;</pre>
+</IfModule>
+```
 
-<h3 id="Nginx_configuration">Nginx configuration</h3>
+### Nginx configuration
 
-<pre class="brush: bash">add_header Content-Security-Policy "base-uri 'self';"</pre>
+```bash
+add_header Content-Security-Policy "base-uri 'self';"
+```
 
-<h3 id="Violation_case">Violation case</h3>
+### Violation case
 
-<p>Since your domain isn't <code>example.com</code>, a {{HTMLElement("base")}} element with its <code>href</code> set to <code>https://example.com</code> will result in a CSP violation.</p>
+Since your domain isn't `example.com`, a {{HTMLElement("base")}} element with its `href` set to `https://example.com` will result in a CSP violation.
 
-<pre class="brush: html; example-bad">&lt;meta http-equiv="Content-Security-Policy" content="base-uri 'self'"&gt;
-&lt;base href="https://example.com/"&gt;
+```html example-bad
+<meta http-equiv="Content-Security-Policy" content="base-uri 'self'">
+<base href="https://example.com/">
 
 // Error: Refused to set the document's base URI to 'https://example.com/'
 // because it violates the following Content Security Policy
-// directive: "base-uri 'self'"</pre>
+// directive: "base-uri 'self'"
+```
 
-<h2 id="Specifications">Specifications</h2>
+## Specifications
 
 {{Specifications}}
 
-<h2 id="Browser_compatibility">Browser compatibility</h2>
+## Browser compatibility
 
-<p>{{Compat}}</p>
+{{Compat}}
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
- <li>{{HTTPheader("Content-Security-Policy")}}</li>
- <li>{{HTMLElement("base")}}</li>
- <li>{{domxref("Node.baseURI")}}</li>
-</ul>
+- {{HTTPheader("Content-Security-Policy")}}
+- {{HTMLElement("base")}}
+- {{domxref("Node.baseURI")}}
diff --git a/files/en-us/web/http/headers/content-security-policy/block-all-mixed-content/index.md b/files/en-us/web/http/headers/content-security-policy/block-all-mixed-content/index.md
index f21e437f9f28b27..5b206e397857637 100644
--- a/files/en-us/web/http/headers/content-security-policy/block-all-mixed-content/index.md
+++ b/files/en-us/web/http/headers/content-security-policy/block-all-mixed-content/index.md
@@ -12,43 +12,40 @@ tags:
   - block-all-mixed-content
 browser-compat: http.headers.csp.Content-Security-Policy.block-all-mixed-content
 ---
-<div>{{HTTPSidebar}}{{deprecated_header}}</div>
+{{HTTPSidebar}}{{deprecated_header}}
 
-<p>The HTTP {{HTTPHeader("Content-Security-Policy")}} (CSP) <code><strong>block-all-mixed-content</strong></code> directive prevents loading any assets over HTTP when the page uses HTTPS.</p>
+The HTTP {{HTTPHeader("Content-Security-Policy")}} (CSP) **`block-all-mixed-content`** directive prevents loading any assets over HTTP when the page uses HTTPS.
 
-<p>All <a href="/en-US/docs/Web/Security/Mixed_content">mixed content</a> resource requests are blocked, including both active and passive mixed content. This also applies to {{HTMLElement("iframe")}} documents, ensuring the entire page is mixed content-free.</p>
+All [mixed content](/en-US/docs/Web/Security/Mixed_content) resource requests are blocked, including both active and passive mixed content. This also applies to {{HTMLElement("iframe")}} documents, ensuring the entire page is mixed content-free.
 
-<div class="notecard note">
-  <p><strong>Note:</strong> The {{CSP("upgrade-insecure-requests")}} directive is evaluated before <code>block-all-mixed-content</code>. If the former is set, the latter does nothing, so set one directive or the other – not both, unless you want to force HTTPS on older browsers that do not force it after a redirect to HTTP.</p>
-</div>
+> **Note:** The {{CSP("upgrade-insecure-requests")}} directive is evaluated before `block-all-mixed-content`. If the former is set, the latter does nothing, so set one directive or the other – not both, unless you want to force HTTPS on older browsers that do not force it after a redirect to HTTP.
 
-<h2 id="Syntax">Syntax</h2>
+## Syntax
 
-<pre class="brush: html">Content-Security-Policy: block-all-mixed-content;</pre>
+```html
+Content-Security-Policy: block-all-mixed-content;
+```
 
-<h2 id="Examples">Examples</h2>
+## Examples
 
-<pre>Content-Security-Policy: block-all-mixed-content;
+    Content-Security-Policy: block-all-mixed-content;
 
-&lt;meta http-equiv="Content-Security-Policy" content="block-all-mixed-content"&gt;
-</pre>
+    <meta http-equiv="Content-Security-Policy" content="block-all-mixed-content">
 
-<p>To disallow http assets on a more granular level, you can also set individual directives to <code>https:</code>. For example, to disallow nonsecure HTTP images:</p>
+To disallow http assets on a more granular level, you can also set individual directives to `https:`. For example, to disallow nonsecure HTTP images:
 
-<pre>Content-Security-Policy: img-src https:</pre>
+    Content-Security-Policy: img-src https:
 
-<h2 id="Specifications">Specifications</h2>
+## Specifications
 
-<p>Not part of any current specification. Used to be defined in the outdated <a href="https://www.w3.org/TR/mixed-content/#block-all-mixed-content">Mixed Content Level 1</a> specification.</p>
+Not part of any current specification. Used to be defined in the outdated [Mixed Content Level 1](https://www.w3.org/TR/mixed-content/#block-all-mixed-content) specification.
 
-<h2 id="Browser_compatibility">Browser compatibility</h2>
+## Browser compatibility
 
-<p>{{Compat}}</p>
+{{Compat}}
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
- <li>{{HTTPHeader("Content-Security-Policy")}}</li>
- <li>{{CSP("upgrade-insecure-requests")}}</li>
- <li><a href="/en-US/docs/Web/Security/Mixed_content">Mixed content</a></li>
-</ul>
+- {{HTTPHeader("Content-Security-Policy")}}
+- {{CSP("upgrade-insecure-requests")}}
+- [Mixed content](/en-US/docs/Web/Security/Mixed_content)
diff --git a/files/en-us/web/http/headers/content-security-policy/child-src/index.md b/files/en-us/web/http/headers/content-security-policy/child-src/index.md
index fceac28e80d5ce7..9e4ae7e06964d3f 100644
--- a/files/en-us/web/http/headers/content-security-policy/child-src/index.md
+++ b/files/en-us/web/http/headers/content-security-policy/child-src/index.md
@@ -2,25 +2,24 @@
 title: 'CSP: child-src'
 slug: Web/HTTP/Headers/Content-Security-Policy/child-src
 tags:
-- CSP
-- Child
-- Content-Security-Policy
-- Directive
-- HTTP
-- Reference
-- Security
-- child-src
-- source
+  - CSP
+  - Child
+  - Content-Security-Policy
+  - Directive
+  - HTTP
+  - Reference
+  - Security
+  - child-src
+  - source
 browser-compat: http.headers.csp.Content-Security-Policy.child-src
 ---
-<div>{{HTTPSidebar}}</div>
+{{HTTPSidebar}}
 
-<p>The HTTP {{HTTPHeader("Content-Security-Policy")}} (CSP)
-  <strong><code>child-src</code></strong> directive defines the valid sources for <a
-    href="/en-US/docs/Web/API/Web_Workers_API">web workers</a> and nested browsing
-  contexts loaded using elements such as {{HTMLElement("frame")}} and
-  {{HTMLElement("iframe")}}. For workers, non-compliant requests are treated as fatal
-  network errors by the user agent.</p>
+The HTTP {{HTTPHeader("Content-Security-Policy")}} (CSP)
+**`child-src`** directive defines the valid sources for [web workers](/en-US/docs/Web/API/Web_Workers_API) and nested browsing
+contexts loaded using elements such as {{HTMLElement("frame")}} and
+{{HTMLElement("iframe")}}. For workers, non-compliant requests are treated as fatal
+network errors by the user agent.
 
 <table class="properties">
   <tbody>
@@ -34,53 +33,57 @@ browser-compat: http.headers.csp.Content-Security-Policy.child-src
     </tr>
     <tr>
       <th scope="row">{{CSP("default-src")}} fallback</th>
-      <td>Yes. If this directive is absent, the user agent will look for the
-        <code>default-src</code> directive.</td>
+      <td>
+        Yes. If this directive is absent, the user agent will look for the
+        <code>default-src</code> directive.
+      </td>
     </tr>
   </tbody>
 </table>
 
-<h2 id="Syntax">Syntax</h2>
+## Syntax
 
-<p>One or more sources can be allowed for the child-src policy:</p>
+One or more sources can be allowed for the child-src policy:
 
-<pre class="brush: html">Content-Security-Policy: child-src &lt;source&gt;;
-Content-Security-Policy: child-src &lt;source&gt; &lt;source&gt;;
-</pre>
+```html
+Content-Security-Policy: child-src <source>;
+Content-Security-Policy: child-src <source> <source>;
+```
 
-<h3 id="Sources">Sources</h3>
+### Sources
 
-<p>{{page("Web/HTTP/Headers/Content-Security-Policy/connect-src", "Sources")}}</p>
+{{page("Web/HTTP/Headers/Content-Security-Policy/connect-src", "Sources")}}
 
-<h2 id="Examples">Examples</h2>
+## Examples
 
-<h3 id="Violation_cases">Violation cases</h3>
+### Violation cases
 
-<p>Given this CSP header:</p>
+Given this CSP header:
 
-<pre class="brush: bash">Content-Security-Policy: child-src https://example.com/</pre>
+```bash
+Content-Security-Policy: child-src https://example.com/
+```
 
-<p>This {{HTMLElement("iframe")}} and worker are blocked and won't load:</p>
+This {{HTMLElement("iframe")}} and worker are blocked and won't load:
 
-<pre class="brush: html">&lt;iframe src="https://not-example.com"&gt;&lt;/iframe&gt;
+```html
+<iframe src="https://not-example.com"></iframe>
 
-&lt;script&gt;
+<script>
   var blockedWorker = new Worker("data:application/javascript,...");
-&lt;/script&gt;</pre>
+</script>
+```
 
-<h2 id="Specifications">Specifications</h2>
+## Specifications
 
 {{Specifications}}
 
-<h2 id="Browser_compatibility">Browser compatibility</h2>
+## Browser compatibility
 
-<p>{{Compat}}</p>
+{{Compat}}
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
-  <li>{{HTTPHeader("Content-Security-Policy")}}</li>
-  <li>{{HTMLElement("frame")}} and {{HTMLElement("iframe")}}</li>
-  <li>{{domxref("Worker")}}, {{domxref("SharedWorker")}}, {{domxref("ServiceWorker")}}
-  </li>
-</ul>
+- {{HTTPHeader("Content-Security-Policy")}}
+- {{HTMLElement("frame")}} and {{HTMLElement("iframe")}}
+- {{domxref("Worker")}}, {{domxref("SharedWorker")}}, {{domxref("ServiceWorker")}}
diff --git a/files/en-us/web/http/headers/content-security-policy/connect-src/index.md b/files/en-us/web/http/headers/content-security-policy/connect-src/index.md
index 3c360e686e525a4..73d70aee977242d 100644
--- a/files/en-us/web/http/headers/content-security-policy/connect-src/index.md
+++ b/files/en-us/web/http/headers/content-security-policy/connect-src/index.md
@@ -12,25 +12,21 @@ tags:
   - source
 browser-compat: http.headers.csp.Content-Security-Policy.connect-src
 ---
-<div>{{HTTPSidebar}}</div>
-
-<p>The HTTP {{HTTPHeader("Content-Security-Policy")}} (CSP)
-  <code><strong>connect-src</strong></code> directive restricts the URLs which can be
-  loaded using script interfaces. The APIs that are restricted are:</p>
-
-<ul>
-  <li>{{HTMLElement("a")}} {{htmlattrxref("ping", "a")}},</li>
-  <li>{{domxref("WindowOrWorkerGlobalScope.fetch")}},</li>
-  <li>{{domxref("XMLHttpRequest")}},</li>
-  <li>{{domxref("WebSocket")}},</li>
-  <li>{{domxref("EventSource")}}, and</li>
-  <li>{{domxref("Navigator.sendBeacon()")}}.</li>
-</ul>
-
-<div class="notecard note">
-  <p><strong>Note:</strong> <code>connect-src 'self'</code> does not resolve to websocket
-    schemas in all browsers, more info in this <a href="https://github.com/w3c/webappsec-csp/issues/7">issue</a>.</p>
-</div>
+{{HTTPSidebar}}
+
+The HTTP {{HTTPHeader("Content-Security-Policy")}} (CSP)
+**`connect-src`** directive restricts the URLs which can be
+loaded using script interfaces. The APIs that are restricted are:
+
+- {{HTMLElement("a")}} {{htmlattrxref("ping", "a")}},
+- {{domxref("WindowOrWorkerGlobalScope.fetch")}},
+- {{domxref("XMLHttpRequest")}},
+- {{domxref("WebSocket")}},
+- {{domxref("EventSource")}}, and
+- {{domxref("Navigator.sendBeacon()")}}.
+
+> **Note:** `connect-src 'self'` does not resolve to websocket
+> schemas in all browsers, more info in this [issue](https://github.com/w3c/webappsec-csp/issues/7).
 
 <table class="properties">
   <tbody>
@@ -44,38 +40,44 @@ browser-compat: http.headers.csp.Content-Security-Policy.connect-src
     </tr>
     <tr>
       <th scope="row">{{CSP("default-src")}} fallback</th>
-      <td>Yes. If this directive is absent, the user agent will look for the
-        <code>default-src</code> directive.</td>
+      <td>
+        Yes. If this directive is absent, the user agent will look for the
+        <code>default-src</code> directive.
+      </td>
     </tr>
   </tbody>
 </table>
 
-<h2 id="Syntax">Syntax</h2>
+## Syntax
 
-<p>One or more sources can be allowed for the connect-src policy:</p>
+One or more sources can be allowed for the connect-src policy:
 
-<pre class="brush: html">Content-Security-Policy: connect-src &lt;source&gt;;
-Content-Security-Policy: connect-src &lt;source&gt; &lt;source&gt;;
-</pre>
+```html
+Content-Security-Policy: connect-src <source>;
+Content-Security-Policy: connect-src <source> <source>;
+```
 
-<h3 id="Sources">Sources</h3>
+### Sources
 
-<p>{{page("/en-US/docs/Web/HTTP/Headers/Content-Security-Policy/default-src",
-  "common_sources")}}</p>
+{{page("/en-US/docs/Web/HTTP/Headers/Content-Security-Policy/default-src",
+  "common_sources")}}
 
-<h2 id="Examples">Examples</h2>
+## Examples
 
-<h3 id="Violation_cases">Violation cases</h3>
+### Violation cases
 
-<p>Given this CSP header:</p>
+Given this CSP header:
 
-<pre class="brush: bash">Content-Security-Policy: connect-src https://example.com/</pre>
+```bash
+Content-Security-Policy: connect-src https://example.com/
+```
 
-<p>The following connections are blocked and won't load:</p>
+The following connections are blocked and won't load:
 
-<pre class="brush: html">&lt;a ping="https://not-example.com"&gt;
+```html
+<a ping="https://not-example.com">
 
-&lt;script&gt;
+<script>
   var xhr = new XMLHttpRequest();
   xhr.open('GET', 'https://not-example.com/');
   xhr.send();
@@ -85,31 +87,28 @@ Content-Security-Policy: connect-src &lt;source&gt; &lt;source&gt;;
   var es = new EventSource("https://not-example.com/");
 
   navigator.sendBeacon("https://not-example.com/", { ... });
-&lt;/script&gt;</pre>
+</script>
+```
 
-<h2 id="Specifications">Specifications</h2>
+## Specifications
 
 {{Specifications}}
 
-<h2 id="Browser_compatibility">Browser compatibility</h2>
+## Browser compatibility
 
-<p>{{Compat}}</p>
+{{Compat}}
 
-<h2 id="Compatibility_notes">Compatibility notes</h2>
+## Compatibility notes
 
-<ul>
-  <li>Prior to Firefox 23, <code>xhr-src</code> was used in place of the
-    <code>connect-src</code> directive and only restricted the use of
-    {{domxref("XMLHttpRequest")}}.</li>
-</ul>
+- Prior to Firefox 23, `xhr-src` was used in place of the
+  `connect-src` directive and only restricted the use of
+  {{domxref("XMLHttpRequest")}}.
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
-  <li>{{HTTPHeader("Content-Security-Policy")}}</li>
-  <li>{{HTMLElement("a")}} {{htmlattrxref("ping", "a")}}</li>
-  <li>{{domxref("WindowOrWorkerGlobalScope.fetch")}}</li>
-  <li>{{domxref("XMLHttpRequest")}}</li>
-  <li>{{domxref("WebSocket")}}</li>
-  <li>{{domxref("EventSource")}}</li>
-</ul>
+- {{HTTPHeader("Content-Security-Policy")}}
+- {{HTMLElement("a")}} {{htmlattrxref("ping", "a")}}
+- {{domxref("WindowOrWorkerGlobalScope.fetch")}}
+- {{domxref("XMLHttpRequest")}}
+- {{domxref("WebSocket")}}
+- {{domxref("EventSource")}}
diff --git a/files/en-us/web/http/headers/content-security-policy/default-src/index.md b/files/en-us/web/http/headers/content-security-policy/default-src/index.md
index 3e55e196835ed25..5fe31de924def41 100644
--- a/files/en-us/web/http/headers/content-security-policy/default-src/index.md
+++ b/files/en-us/web/http/headers/content-security-policy/default-src/index.md
@@ -13,119 +13,109 @@ tags:
   - source
 browser-compat: http.headers.csp.Content-Security-Policy.default-src
 ---
-<div>{{HTTPSidebar}}</div>
-
-<p>The HTTP {{HTTPHeader("Content-Security-Policy")}} (CSP) <strong><code>default-src</code></strong> directive serves as a fallback for the other CSP {{Glossary("fetch directive", "fetch directives")}}. For each of the following directives that are absent, the user agent looks for the <code>default-src</code> directive and uses this value for it:</p>
-
-<ul>
- <li>{{CSP("child-src")}}</li>
- <li>{{CSP("connect-src")}}</li>
- <li>{{CSP("font-src")}}</li>
- <li>{{CSP("frame-src")}}</li>
- <li>{{CSP("img-src")}}</li>
- <li>{{CSP("manifest-src")}}</li>
- <li>{{CSP("media-src")}}</li>
- <li>{{CSP("object-src")}}</li>
- <li>{{CSP("prefetch-src")}}</li>
- <li>{{CSP("script-src")}}</li>
- <li>{{CSP("script-src-elem")}}</li>
- <li>{{CSP("script-src-attr")}}</li>
- <li>{{CSP("style-src")}}</li>
- <li>{{CSP("style-src-elem")}}</li>
- <li>{{CSP("style-src-attr")}}</li>
- <li>{{CSP("worker-src")}}</li>
-</ul>
+{{HTTPSidebar}}
+
+The HTTP {{HTTPHeader("Content-Security-Policy")}} (CSP) **`default-src`** directive serves as a fallback for the other CSP {{Glossary("fetch directive", "fetch directives")}}. For each of the following directives that are absent, the user agent looks for the `default-src` directive and uses this value for it:
+
+- {{CSP("child-src")}}
+- {{CSP("connect-src")}}
+- {{CSP("font-src")}}
+- {{CSP("frame-src")}}
+- {{CSP("img-src")}}
+- {{CSP("manifest-src")}}
+- {{CSP("media-src")}}
+- {{CSP("object-src")}}
+- {{CSP("prefetch-src")}}
+- {{CSP("script-src")}}
+- {{CSP("script-src-elem")}}
+- {{CSP("script-src-attr")}}
+- {{CSP("style-src")}}
+- {{CSP("style-src-elem")}}
+- {{CSP("style-src-attr")}}
+- {{CSP("worker-src")}}
 
 <table class="properties">
- <tbody>
-  <tr>
-   <th scope="row">CSP version</th>
-   <td>1</td>
-  </tr>
-  <tr>
-   <th scope="row">Directive type</th>
-   <td>{{Glossary("Fetch directive")}}</td>
-  </tr>
- </tbody>
+  <tbody>
+    <tr>
+      <th scope="row">CSP version</th>
+      <td>1</td>
+    </tr>
+    <tr>
+      <th scope="row">Directive type</th>
+      <td>{{Glossary("Fetch directive")}}</td>
+    </tr>
+  </tbody>
 </table>
 
-<h2 id="Syntax">Syntax</h2>
+## Syntax
 
-<p>One or more sources can be allowed for the <code>default-src</code> policy:</p>
+One or more sources can be allowed for the `default-src` policy:
 
-<pre class="brush: html">Content-Security-Policy: default-src &lt;source&gt;;
-Content-Security-Policy: default-src &lt;source&gt; &lt;source&gt;;
-</pre>
+```html
+Content-Security-Policy: default-src <source>;
+Content-Security-Policy: default-src <source> <source>;
+```
 
-<h3 id="Sources">Sources</h3>
+### Sources
 
-<p>&lt;source&gt; can be one of the following:</p>
+\<source> can be one of the following:
 
-<dl>
-  <dt><code>&lt;host-source&gt;</code></dt>
-  <dd>Internet hosts by name or IP address, as well as an optional <a href="/en-US/docs/Learn/Common_questions/What_is_a_URL">URL scheme</a> and/or port number. The site's address may include an optional leading wildcard (the asterisk character, <code>'*'</code>), and you may use a wildcard (again, <code>'*'</code>) as the port number, indicating that all legal ports are valid for the source.<br>
-    Examples:
-    <ul>
-      <li><code>http://*.example.com</code>: Matches all attempts to load from any subdomain of example.com using the <code>http:</code> URL scheme.</li>
-      <li><code>mail.example.com:443</code>: Matches all attempts to access port 443 on mail.example.com.</li>
-      <li><code>https://store.example.com</code>: Matches all attempts to access store.example.com using <code>https:</code>.</li>
-      <li><code>*.example.com</code>: Matches all attempts to load from any subdomain of example.com using the current protocol.</li>
-    </ul>
-  </dd>
-
-  <dt><code>&lt;scheme-source&gt;</code></dt>
-  <dd>A scheme such as <code>http:</code> or <code>https:</code>. The colon is required. Unlike other values below, single quotes shouldn't be used. You can also specify data schemes (not recommended).
-    <ul>
-      <li><code>data:</code> Allows <a href="/en-US/docs/Web/HTTP/Basics_of_HTTP/Data_URIs"><code>data:</code> URIs</a> to be used as a content source.<em> This is insecure; an attacker can also inject arbitrary data: URIs. Use this sparingly and definitely not for scripts.</em></li>
-      <li><code>mediastream:</code> Allows <a href="/en-US/docs/Web/API/Media_Streams_API"><code>mediastream:</code> URIs</a> to be used as a content source.</li>
-      <li><code>blob:</code> Allows <a href="/en-US/docs/Web/API/Blob"><code>blob:</code> URIs</a> to be used as a content source.</li>
-      <li><code>filesystem:</code> Allows <a href="/en-US/docs/Web/API/FileSystem"><code>filesystem:</code> URIs</a> to be used as a content source.</li>
-    </ul>
-  </dd>
+- `<host-source>`
 
-  <dt><code>'self'</code></dt>
-  <dd>Refers to the origin from which the protected document is being served, including the same URL scheme and port number. You must include the single quotes. Some browsers specifically exclude <code>blob</code> and <code>filesystem</code> from source directives. Sites needing to allow these content types can specify them using the Data attribute.</dd>
+  - : Internet hosts by name or IP address, as well as an optional [URL scheme](/en-US/docs/Learn/Common_questions/What_is_a_URL) and/or port number. The site's address may include an optional leading wildcard (the asterisk character, `'*'`), and you may use a wildcard (again, `'*'`) as the port number, indicating that all legal ports are valid for the source.
+    Examples:
 
-  <dt><code>'unsafe-eval'</code></dt>
-  <dd>Allows the use of <code>eval()</code> and similar methods for creating code from strings. You must include the single quotes.</dd>
+    - `http://*.example.com`: Matches all attempts to load from any subdomain of example.com using the `http:` URL scheme.
+    - `mail.example.com:443`: Matches all attempts to access port 443 on mail.example.com.
+    - `https://store.example.com`: Matches all attempts to access store.example.com using `https:`.
+    - `*.example.com`: Matches all attempts to load from any subdomain of example.com using the current protocol.
 
-  <dt><code>'unsafe-hashes'</code></dt>
-  <dd>Allows enabling specific inline <a href="/en-US/docs/Web/Events/Event_handlers">event handlers</a>. If you only need to allow inline event handlers and not inline {{HTMLElement("script")}} elements or <code>javascript:</code> URLs, this is a safer method than using the <code>unsafe-inline</code> expression.</dd>
+- `<scheme-source>`
 
-  <dt><code>'unsafe-inline'</code></dt>
-  <dd>Allows the use of inline resources, such as inline {{HTMLElement("script")}} elements, <code>javascript:</code> URLs, inline event handlers, and inline {{HTMLElement("style")}} elements. The single quotes are required.</dd>
+  - : A scheme such as `http:` or `https:`. The colon is required. Unlike other values below, single quotes shouldn't be used. You can also specify data schemes (not recommended).
 
-  <dt><code>'none'</code></dt>
-  <dd>Refers to the empty set; that is, no URLs match. The single quotes are required.</dd>
+    - `data:` Allows [`data:` URIs](/en-US/docs/Web/HTTP/Basics_of_HTTP/Data_URIs) to be used as a content source. _This is insecure; an attacker can also inject arbitrary data: URIs. Use this sparingly and definitely not for scripts._
+    - `mediastream:` Allows [`mediastream:` URIs](/en-US/docs/Web/API/Media_Streams_API) to be used as a content source.
+    - `blob:` Allows [`blob:` URIs](/en-US/docs/Web/API/Blob) to be used as a content source.
+    - `filesystem:` Allows [`filesystem:` URIs](/en-US/docs/Web/API/FileSystem) to be used as a content source.
 
-  <dt><code>'nonce-&lt;base64-value&gt;'</code></dt>
-  <dd>An allow-list for specific inline scripts using a cryptographic nonce (number used once). The server must generate a unique nonce value each time it transmits a policy. It is critical to provide an unguessable nonce, as bypassing a resource's policy is otherwise trivial. See <a href="/en-US/docs/Web/HTTP/Headers/Content-Security-Policy/script-src#unsafe_inline_script">unsafe inline script</a> for an example. Specifying nonce makes a modern browser ignore <code>'unsafe-inline'</code> which could still be set for older browsers without nonce support.
-    <div class="notecard note">
-      <p><strong>Note:</strong> The CSP <code>nonce</code> source can only be applied to <em>nonceable</em> elements (e.g., as the {{HTMLElement("img")}} element has no <code>nonce</code> attribute, there is no way to associate it with this CSP source).</p>
-    </div>
-  </dd>
+- `'self'`
+  - : Refers to the origin from which the protected document is being served, including the same URL scheme and port number. You must include the single quotes. Some browsers specifically exclude `blob` and `filesystem` from source directives. Sites needing to allow these content types can specify them using the Data attribute.
+- `'unsafe-eval'`
+  - : Allows the use of `eval()` and similar methods for creating code from strings. You must include the single quotes.
+- `'unsafe-hashes'`
+  - : Allows enabling specific inline [event handlers](/en-US/docs/Web/Events/Event_handlers). If you only need to allow inline event handlers and not inline {{HTMLElement("script")}} elements or `javascript:` URLs, this is a safer method than using the `unsafe-inline` expression.
+- `'unsafe-inline'`
+  - : Allows the use of inline resources, such as inline {{HTMLElement("script")}} elements, `javascript:` URLs, inline event handlers, and inline {{HTMLElement("style")}} elements. The single quotes are required.
+- `'none'`
+  - : Refers to the empty set; that is, no URLs match. The single quotes are required.
+- `'nonce-<base64-value>'`
 
-  <dt><code>'&lt;hash-algorithm&gt;-&lt;base64-value&gt;'</code></dt>
-  <dd>A sha256, sha384 or sha512 hash of scripts or styles. The use of this source consists of two portions separated by a dash: the encryption algorithm used to create the hash and the base64-encoded hash of the script or style. When generating the hash, don't include the &lt;script&gt; or &lt;style&gt; tags and note that capitalization and whitespace matter, including leading or trailing whitespace. See <a href="/en-US/docs/Web/HTTP/Headers/Content-Security-Policy/script-src#unsafe_inline_script">unsafe inline script</a> for an example. In CSP 2.0, this is applied only to inline scripts. CSP 3.0 allows it in the case of <code>script-src</code> for external scripts.</dd>
+  - : An allow-list for specific inline scripts using a cryptographic nonce (number used once). The server must generate a unique nonce value each time it transmits a policy. It is critical to provide an unguessable nonce, as bypassing a resource's policy is otherwise trivial. See [unsafe inline script](/en-US/docs/Web/HTTP/Headers/Content-Security-Policy/script-src#unsafe_inline_script) for an example. Specifying nonce makes a modern browser ignore `'unsafe-inline'` which could still be set for older browsers without nonce support.
 
-  <dt><code>'strict-dynamic'</code></dt>
-  <dd>The <code>strict-dynamic</code> source expression specifies that the trust explicitly given to a script present in the markup, by accompanying it with a nonce or a hash, shall be propagated to all the scripts loaded by that root script. At the same time, any allow-list or source expressions such as <code>'self'</code> or <code>'unsafe-inline'</code> are ignored. See <a href="/en-US/docs/Web/HTTP/Headers/Content-Security-Policy/script-src#strict-dynamic">script-src</a> for an example.</dd>
+    > **Note:** The CSP `nonce` source can only be applied to _nonceable_ elements (e.g., as the {{HTMLElement("img")}} element has no `nonce` attribute, there is no way to associate it with this CSP source).
 
-  <dt><code>'report-sample'</code></dt>
-  <dd>Requires a sample of the violating code to be included in the violation report.</dd>
-</dl>
+- `'<hash-algorithm>-<base64-value>'`
+  - : A sha256, sha384 or sha512 hash of scripts or styles. The use of this source consists of two portions separated by a dash: the encryption algorithm used to create the hash and the base64-encoded hash of the script or style. When generating the hash, don't include the \<script> or \<style> tags and note that capitalization and whitespace matter, including leading or trailing whitespace. See [unsafe inline script](/en-US/docs/Web/HTTP/Headers/Content-Security-Policy/script-src#unsafe_inline_script) for an example. In CSP 2.0, this is applied only to inline scripts. CSP 3.0 allows it in the case of `script-src` for external scripts.
+- `'strict-dynamic'`
+  - : The `strict-dynamic` source expression specifies that the trust explicitly given to a script present in the markup, by accompanying it with a nonce or a hash, shall be propagated to all the scripts loaded by that root script. At the same time, any allow-list or source expressions such as `'self'` or `'unsafe-inline'` are ignored. See [script-src](/en-US/docs/Web/HTTP/Headers/Content-Security-Policy/script-src#strict-dynamic) for an example.
+- `'report-sample'`
+  - : Requires a sample of the violating code to be included in the violation report.
 
-<h2 id="Examples">Examples</h2>
+## Examples
 
-<h3 id="No_inheritance_with_default-src">No inheritance with default-src</h3>
+### No inheritance with default-src
 
-<p>If there are other directives specified, <code>default-src</code> does not influence them. The following header:</p>
+If there are other directives specified, `default-src` does not influence them. The following header:
 
-<pre class="brush: bash">Content-Security-Policy: default-src 'self'; script-src https://example.com</pre>
+```bash
+Content-Security-Policy: default-src 'self'; script-src https://example.com
+```
 
-<p>is the same as:</p>
+is the same as:
 
-<pre class="brush: bash">Content-Security-Policy: connect-src 'self';
+```bash
+Content-Security-Policy: connect-src 'self';
                          font-src 'self';
                          frame-src 'self';
                          img-src 'self';
@@ -134,29 +124,26 @@ Content-Security-Policy: default-src &lt;source&gt; &lt;source&gt;;
                          object-src 'self';
                          script-src https://example.com;
                          style-src 'self';
-                         worker-src 'self'</pre>
+                         worker-src 'self'
+```
 
-<h2 id="Specifications">Specifications</h2>
+## Specifications
 
 {{Specifications}}
 
-<h2 id="Browser_compatibility">Browser compatibility</h2>
-
-<p>{{Compat}}</p>
-
-<h2 id="See_also">See also</h2>
-
-<ul>
- <li>{{HTTPHeader("Content-Security-Policy")}}</li>
- <li>CSP directives (<a href="https://www.w3.org/TR/CSP/#csp-directives">https://www.w3.org/TR/CSP/#csp-directives</a>):
-  <ul>
-   <li>{{Glossary("Fetch directive")}}</li>
-   <li>{{Glossary("Document directive")}}</li>
-   <li>{{Glossary("Navigation directive")}}</li>
-   <li>{{Glossary("Reporting directive")}}</li>
-   <li><code><a href="/en-US/docs/Web/HTTP/Headers/Content-Security-Policy/upgrade-insecure-requests">upgrade-insecure-requests</a></code></li>
-   <li><code><a href="/en-US/docs/Web/HTTP/Headers/Content-Security-Policy/block-all-mixed-content">block-all-mixed-content</a></code></li>
-   <li><code><a href="/en-US/docs/Web/HTTP/Headers/Content-Security-Policy/require-sri-for">require-sri-for</a></code> {{experimental_inline}}</li>
-  </ul>
- </li>
-</ul>
+## Browser compatibility
+
+{{Compat}}
+
+## See also
+
+- {{HTTPHeader("Content-Security-Policy")}}
+- CSP directives (<https://www.w3.org/TR/CSP/#csp-directives>):
+
+  - {{Glossary("Fetch directive")}}
+  - {{Glossary("Document directive")}}
+  - {{Glossary("Navigation directive")}}
+  - {{Glossary("Reporting directive")}}
+  - [`upgrade-insecure-requests`](/en-US/docs/Web/HTTP/Headers/Content-Security-Policy/upgrade-insecure-requests)
+  - [`block-all-mixed-content`](/en-US/docs/Web/HTTP/Headers/Content-Security-Policy/block-all-mixed-content)
+  - [`require-sri-for`](/en-US/docs/Web/HTTP/Headers/Content-Security-Policy/require-sri-for) {{experimental_inline}}
diff --git a/files/en-us/web/http/headers/content-security-policy/font-src/index.md b/files/en-us/web/http/headers/content-security-policy/font-src/index.md
index 112ca756ac072e4..ab7eb11fc2ba71c 100644
--- a/files/en-us/web/http/headers/content-security-policy/font-src/index.md
+++ b/files/en-us/web/http/headers/content-security-policy/font-src/index.md
@@ -2,21 +2,21 @@
 title: 'CSP: font-src'
 slug: Web/HTTP/Headers/Content-Security-Policy/font-src
 tags:
-- CSP
-- Content-Security-Policy
-- Directive
-- HTTP
-- Reference
-- Security
-- font
-- source
+  - CSP
+  - Content-Security-Policy
+  - Directive
+  - HTTP
+  - Reference
+  - Security
+  - font
+  - source
 browser-compat: http.headers.csp.Content-Security-Policy.font-src
 ---
-<div>{{HTTPSidebar}}</div>
+{{HTTPSidebar}}
 
-<p>The HTTP {{HTTPHeader("Content-Security-Policy")}} (CSP)
-  <code><strong>font</strong></code><strong><code>-src</code></strong> directive specifies
-  valid sources for fonts loaded using {{cssxref("@font-face")}}.</p>
+The HTTP {{HTTPHeader("Content-Security-Policy")}} (CSP)
+**`font`\*\***`-src`\*\* directive specifies
+valid sources for fonts loaded using {{cssxref("@font-face")}}.
 
 <table class="properties">
   <tbody>
@@ -30,35 +30,41 @@ browser-compat: http.headers.csp.Content-Security-Policy.font-src
     </tr>
     <tr>
       <th scope="row">{{CSP("default-src")}} fallback</th>
-      <td>Yes. If this directive is absent, the user agent will look for the
-        <code>default-src</code> directive.</td>
+      <td>
+        Yes. If this directive is absent, the user agent will look for the
+        <code>default-src</code> directive.
+      </td>
     </tr>
   </tbody>
 </table>
 
-<h2 id="Syntax">Syntax</h2>
+## Syntax
 
-<p>One or more sources can be allowed for the <code>font-src</code> policy:</p>
+One or more sources can be allowed for the `font-src` policy:
 
-<pre class="brush: html">Content-Security-Policy: font-src &lt;source&gt;;
-Content-Security-Policy: font-src &lt;source&gt; &lt;source&gt;;
-</pre>
+```html
+Content-Security-Policy: font-src <source>;
+Content-Security-Policy: font-src <source> <source>;
+```
 
-<h3 id="Sources">Sources</h3>
+### Sources
 
-<p>{{page("Web/HTTP/Headers/Content-Security-Policy/connect-src", "Sources")}}</p>
+{{page("Web/HTTP/Headers/Content-Security-Policy/connect-src", "Sources")}}
 
-<h2 id="Examples">Examples</h2>
+## Examples
 
-<h3 id="Violation_cases">Violation cases</h3>
+### Violation cases
 
-<p>Given this CSP header:</p>
+Given this CSP header:
 
-<pre class="brush: bash">Content-Security-Policy: font-src https://example.com/</pre>
+```bash
+Content-Security-Policy: font-src https://example.com/
+```
 
-<p>The following font resource loading is blocked and won't load:</p>
+The following font resource loading is blocked and won't load:
 
-<pre class="brush: html">&lt;style&gt;
+```html
+<style>
   @font-face {
     font-family: "MyFont";
     src: url("https://not-example.com/font");
@@ -66,19 +72,18 @@ Content-Security-Policy: font-src &lt;source&gt; &lt;source&gt;;
   body {
     font-family: "MyFont";
   }
-&lt;/style&gt;</pre>
+</style>
+```
 
-<h2 id="Specifications">Specifications</h2>
+## Specifications
 
 {{Specifications}}
 
-<h2 id="Browser_compatibility">Browser compatibility</h2>
+## Browser compatibility
 
-<p>{{Compat}}</p>
+{{Compat}}
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
-  <li>{{HTTPHeader("Content-Security-Policy")}}</li>
-  <li>{{cssxref("@font-face")}}</li>
-</ul>
+- {{HTTPHeader("Content-Security-Policy")}}
+- {{cssxref("@font-face")}}
diff --git a/files/en-us/web/http/headers/content-security-policy/form-action/index.md b/files/en-us/web/http/headers/content-security-policy/form-action/index.md
index dd890dd2f07fc47..19bbddc89b204f2 100644
--- a/files/en-us/web/http/headers/content-security-policy/form-action/index.md
+++ b/files/en-us/web/http/headers/content-security-policy/form-action/index.md
@@ -12,84 +12,89 @@ tags:
   - form-action
 browser-compat: http.headers.csp.Content-Security-Policy.form-action
 ---
-<div>{{HTTPSidebar}}</div>
+{{HTTPSidebar}}
 
-<p>The HTTP {{HTTPHeader("Content-Security-Policy")}} (CSP) <code><strong>form</strong></code><strong><code>-action</code></strong> directive restricts the URLs which can be used as the target of a form submissions from a given context.</p>
+The HTTP {{HTTPHeader("Content-Security-Policy")}} (CSP) **`form`\*\***`-action`\*\* directive restricts the URLs which can be used as the target of a form submissions from a given context.
 
-<div class="notecard warning">
-  <p><strong>Warning:</strong> Whether <code>form-action</code> should block redirects after a form submission is <a href="https://github.com/w3c/webappsec-csp/issues/8">debated</a> and browser implementations of this aspect are inconsistent (e.g. Firefox 57 doesn't block the redirects whereas Chrome 63 does).</p>
-</div>
+> **Warning:** Whether `form-action` should block redirects after a form submission is [debated](https://github.com/w3c/webappsec-csp/issues/8) and browser implementations of this aspect are inconsistent (e.g. Firefox 57 doesn't block the redirects whereas Chrome 63 does).
 
 <table class="properties">
-	<tbody>
-		<tr>
-			<th scope="row">CSP version</th>
-			<td>2</td>
-		</tr>
-		<tr>
-			<th scope="row">Directive type</th>
-			<td>{{Glossary("Navigation directive")}}</td>
-		</tr>
-		<tr>
-			<th scope="row">{{CSP("default-src")}} fallback</th>
-			<td>No. Not setting this allows anything.</td>
-		</tr>
-	</tbody>
+  <tbody>
+    <tr>
+      <th scope="row">CSP version</th>
+      <td>2</td>
+    </tr>
+    <tr>
+      <th scope="row">Directive type</th>
+      <td>{{Glossary("Navigation directive")}}</td>
+    </tr>
+    <tr>
+      <th scope="row">{{CSP("default-src")}} fallback</th>
+      <td>No. Not setting this allows anything.</td>
+    </tr>
+  </tbody>
 </table>
 
-<h2 id="Syntax">Syntax</h2>
+## Syntax
 
-<p>One or more sources can be set for the <code>form-action</code> policy:</p>
+One or more sources can be set for the `form-action` policy:
 
-<pre class="brush: html">Content-Security-Policy: form-action &lt;source&gt;;
-Content-Security-Policy: form-action &lt;source&gt; &lt;source&gt;;
-</pre>
+```html
+Content-Security-Policy: form-action <source>;
+Content-Security-Policy: form-action <source> <source>;
+```
 
-<h3 id="Sources">Sources</h3>
+### Sources
 
-<p>{{page("Web/HTTP/Headers/Content-Security-Policy/default-src", "Sources")}}</p>
+{{page("Web/HTTP/Headers/Content-Security-Policy/default-src", "Sources")}}
 
-<h2 id="Examples">Examples</h2>
+## Examples
 
-<h3 id="Meta_tag_configuration">Meta tag configuration</h3>
+### Meta tag configuration
 
-<pre class="brush: html">&lt;meta http-equiv="Content-Security-Policy" content="form-action 'none'"&gt;</pre>
+```html
+<meta http-equiv="Content-Security-Policy" content="form-action 'none'">
+```
 
-<h3 id="Apache_configuration">Apache configuration</h3>
+### Apache configuration
 
-<pre class="brush: bash">&lt;IfModule mod_headers.c&gt;
+```bash
+<IfModule mod_headers.c>
 Header set Content-Security-Policy "form-action 'none';"
-&lt;/IfModule&gt;</pre>
+</IfModule>
+```
 
-<h3 id="Nginx_configuration">Nginx configuration</h3>
+### Nginx configuration
 
-<pre class="brush: bash">add_header Content-Security-Policy "form-action 'none';"</pre>
+```bash
+add_header Content-Security-Policy "form-action 'none';"
+```
 
-<h3 id="Violation_case">Violation case</h3>
+### Violation case
 
-<p>Using a {{HTMLElement("form")}} element with an action set to inline JavaScript will result in a CSP violation.</p>
+Using a {{HTMLElement("form")}} element with an action set to inline JavaScript will result in a CSP violation.
 
-<pre class="brush: html; example-bad">&lt;meta http-equiv="Content-Security-Policy" content="form-action 'none'"&gt;
+```html example-bad
+<meta http-equiv="Content-Security-Policy" content="form-action 'none'">
 
-&lt;form action="javascript:alert('Foo')" id="form1" method="post"&gt;
-  &lt;input type="text" name="fieldName" value="fieldValue"&gt;
-  &lt;input type="submit" id="submit" value="submit"&gt;
-&lt;/form&gt;
+<form action="javascript:alert('Foo')" id="form1" method="post">
+  <input type="text" name="fieldName" value="fieldValue">
+  <input type="submit" id="submit" value="submit">
+</form>
 
 // Error: Refused to send form data because it violates the following
-// Content Security Policy directive: "form-action 'none'".</pre>
+// Content Security Policy directive: "form-action 'none'".
+```
 
-<h2 id="Specifications">Specifications</h2>
+## Specifications
 
 {{Specifications}}
 
-<h2 id="Browser_compatibility">Browser compatibility</h2>
+## Browser compatibility
 
-<p>{{Compat}}</p>
+{{Compat}}
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
-	<li>{{HTTPheader("Content-Security-Policy")}}</li>
-	<li>{{HTMLElement("form")}}</li>
-</ul>
+- {{HTTPheader("Content-Security-Policy")}}
+- {{HTMLElement("form")}}
diff --git a/files/en-us/web/http/headers/content-security-policy/frame-ancestors/index.md b/files/en-us/web/http/headers/content-security-policy/frame-ancestors/index.md
index f397459d390ff61..643ac0e0d907234 100644
--- a/files/en-us/web/http/headers/content-security-policy/frame-ancestors/index.md
+++ b/files/en-us/web/http/headers/content-security-policy/frame-ancestors/index.md
@@ -12,95 +12,92 @@ tags:
   - frame-ancestors
 browser-compat: http.headers.csp.Content-Security-Policy.frame-ancestors
 ---
-<div>{{HTTPSidebar}}</div>
+{{HTTPSidebar}}
 
-<p>The HTTP {{HTTPHeader("Content-Security-Policy")}} (CSP) <code><strong>frame-ancestors</strong></code> directive specifies valid parents that may embed a page using {{HTMLElement("frame")}}, {{HTMLElement("iframe")}}, {{HTMLElement("object")}}, {{HTMLElement("embed")}}, or {{HTMLElement("applet")}}.</p>
+The HTTP {{HTTPHeader("Content-Security-Policy")}} (CSP) **`frame-ancestors`** directive specifies valid parents that may embed a page using {{HTMLElement("frame")}}, {{HTMLElement("iframe")}}, {{HTMLElement("object")}}, {{HTMLElement("embed")}}, or {{HTMLElement("applet")}}.
 
-<p>Setting this directive to <code>'none'</code> is similar to {{HTTPHeader("X-Frame-Options")}}<code>: deny</code> (which is also supported in older browsers).</p>
+Setting this directive to `'none'` is similar to {{HTTPHeader("X-Frame-Options")}}`: deny` (which is also supported in older browsers).
 
 <table class="properties">
- <tbody>
-  <tr>
-   <th scope="row">CSP version</th>
-   <td>2</td>
-  </tr>
-  <tr>
-   <th scope="row">Directive type</th>
-   <td>{{Glossary("Navigation directive")}}</td>
-  </tr>
-  <tr>
-   <th scope="row">{{CSP("default-src")}} fallback</th>
-   <td>No. Not setting this allows anything.</td>
-  </tr>
-  <tr>
-   <th colspan="2" scope="row">This directive is not supported in the {{HTMLElement("meta")}} element.</th>
-  </tr>
- </tbody>
+  <tbody>
+    <tr>
+      <th scope="row">CSP version</th>
+      <td>2</td>
+    </tr>
+    <tr>
+      <th scope="row">Directive type</th>
+      <td>{{Glossary("Navigation directive")}}</td>
+    </tr>
+    <tr>
+      <th scope="row">{{CSP("default-src")}} fallback</th>
+      <td>No. Not setting this allows anything.</td>
+    </tr>
+    <tr>
+      <th colspan="2" scope="row">
+        This directive is not supported in the {{HTMLElement("meta")}}
+        element.
+      </th>
+    </tr>
+  </tbody>
 </table>
 
-<h2 id="Syntax">Syntax</h2>
+## Syntax
 
-<p>One or more sources can be set for the <code>frame-ancestors</code> policy:</p>
+One or more sources can be set for the `frame-ancestors` policy:
 
-<pre class="brush: html">Content-Security-Policy: frame-ancestors &lt;source&gt;;
-Content-Security-Policy: frame-ancestors &lt;source&gt; &lt;source&gt;;
-</pre>
+```html
+Content-Security-Policy: frame-ancestors <source>;
+Content-Security-Policy: frame-ancestors <source> <source>;
+```
 
-<h3 id="Sources">Sources</h3>
+### Sources
 
-<p>&lt;source&gt; can be one of the following:</p>
+\<source> can be one of the following:
 
-<div class="notecard note">
-  <p><strong>Note:</strong> The <code>frame-ancestors</code> directive's syntax is similar to a source list of other directives (e.g. {{CSP("default-src")}}), but doesn't allow <code>'unsafe-eval'</code> or <code>'unsafe-inline'</code> for example. It will also not fall back to a <code>default-src</code> setting. Only the sources listed below are allowed:</p>
-</div>
+> **Note:** The `frame-ancestors` directive's syntax is similar to a source list of other directives (e.g. {{CSP("default-src")}}), but doesn't allow `'unsafe-eval'` or `'unsafe-inline'` for example. It will also not fall back to a `default-src` setting. Only the sources listed below are allowed:
 
-<dl>
- <dt>&lt;host-source&gt;</dt>
- <dd>Internet hosts by name or IP address, as well as an optional {{Glossary("URL")}} scheme and/or port number, separated by spaces. The site's address may include an optional leading wildcard (the asterisk character, <code>'*'</code>), and you may use a wildcard (again, <code>'*'</code>) as the port number, indicating that all legal ports are valid for the source. Single quotes surrounding the host are not allowed.<br>
- Examples:
- <ul>
-  <li><code>http://*.example.com</code>: Matches all attempts to load from any subdomain of example.com using the <code>http:</code> URL scheme.</li>
-  <li><code>mail.example.com:443</code>: Matches all attempts to access port 443 on mail.example.com.</li>
-  <li><code>https://store.example.com</code>: Matches all attempts to access store.example.com using <code>https:</code>.</li>
- </ul>
+- \<host-source>
 
- <div class="notecard warning">
-  <p><strong>Warning:</strong> If no URL scheme is specified for a <code>host-source</code> and the iframe is loaded from an <code>https</code> URL, the URL for the page loading the iframe must also be <code>https</code>, per the <a href="https://w3c.github.io/webappsec-csp/#match-url-to-source-expression">Does url match expression in origin with redirect count?</a> section of the CSP spec.</p>
- </div>
+  - : Internet hosts by name or IP address, as well as an optional {{Glossary("URL")}} scheme and/or port number, separated by spaces. The site's address may include an optional leading wildcard (the asterisk character, `'*'`), and you may use a wildcard (again, `'*'`) as the port number, indicating that all legal ports are valid for the source. Single quotes surrounding the host are not allowed.
+    Examples:
 
- </dd>
- <dt>&lt;scheme-source&gt;</dt>
- <dd>A scheme such as <code>http:</code> or <code>https:</code>. The colon is required and scheme should not be quoted. You can also specify data schemes (not recommended).
- <ul>
-  <li><code>data:</code> Allows <a href="/en-US/docs/Web/HTTP/Basics_of_HTTP/Data_URIs"><code>data:</code> URIs</a> to be used as a content source.<em> This is insecure; an attacker can also inject arbitrary data: URIs. Use this sparingly and definitely not for scripts.</em></li>
-  <li><code>mediastream:</code> Allows <a href="/en-US/docs/Web/API/Media_Streams_API"><code>mediastream:</code> URIs</a> to be used as a content source.</li>
-  <li><code>blob:</code> Allows <a href="/en-US/docs/Web/API/Blob"><code>blob:</code> URIs</a> to be used as a content source.</li>
-  <li><code>filesystem:</code> Allows <a href="/en-US/docs/Web/API/FileSystem"><code>filesystem:</code> URIs</a> to be used as a content source.</li>
- </ul>
- </dd>
- <dt><code>'self'</code></dt>
- <dd>Refers to the origin from which the protected document is being served, including the same URL scheme and port number. You must include the single quotes. Some browsers specifically exclude <code>blob</code> and <code>filesystem</code> from source directives. Sites needing to allow these content types can specify them using the Data attribute.</dd>
- <dt><code>'none'</code></dt>
- <dd>Refers to the empty set; that is, no URLs match. The single quotes are required.</dd>
-</dl>
+    - `http://*.example.com`: Matches all attempts to load from any subdomain of example.com using the `http:` URL scheme.
+    - `mail.example.com:443`: Matches all attempts to access port 443 on mail.example.com.
+    - `https://store.example.com`: Matches all attempts to access store.example.com using `https:`.
 
-<h2 id="Examples">Examples</h2>
+    > **Warning:** If no URL scheme is specified for a `host-source` and the iframe is loaded from an `https` URL, the URL for the page loading the iframe must also be `https`, per the [Does url match expression in origin with redirect count?](https://w3c.github.io/webappsec-csp/#match-url-to-source-expression) section of the CSP spec.
 
-<pre class="brush: bash">Content-Security-Policy: frame-ancestors 'none';
+- \<scheme-source>
 
-Content-Security-Policy: frame-ancestors 'self' https://www.example.org;</pre>
+  - : A scheme such as `http:` or `https:`. The colon is required and scheme should not be quoted. You can also specify data schemes (not recommended).
 
-<h2 id="Specifications">Specifications</h2>
+    - `data:` Allows [`data:` URIs](/en-US/docs/Web/HTTP/Basics_of_HTTP/Data_URIs) to be used as a content source. _This is insecure; an attacker can also inject arbitrary data: URIs. Use this sparingly and definitely not for scripts._
+    - `mediastream:` Allows [`mediastream:` URIs](/en-US/docs/Web/API/Media_Streams_API) to be used as a content source.
+    - `blob:` Allows [`blob:` URIs](/en-US/docs/Web/API/Blob) to be used as a content source.
+    - `filesystem:` Allows [`filesystem:` URIs](/en-US/docs/Web/API/FileSystem) to be used as a content source.
+
+- `'self'`
+  - : Refers to the origin from which the protected document is being served, including the same URL scheme and port number. You must include the single quotes. Some browsers specifically exclude `blob` and `filesystem` from source directives. Sites needing to allow these content types can specify them using the Data attribute.
+- `'none'`
+  - : Refers to the empty set; that is, no URLs match. The single quotes are required.
+
+## Examples
+
+```bash
+Content-Security-Policy: frame-ancestors 'none';
+
+Content-Security-Policy: frame-ancestors 'self' https://www.example.org;
+```
+
+## Specifications
 
 {{Specifications}}
 
-<h2 id="Browser_compatibility">Browser compatibility</h2>
+## Browser compatibility
 
-<p>{{Compat}}</p>
+{{Compat}}
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
- <li>{{HTTPHeader("Content-Security-Policy")}}</li>
- <li>{{HTTPHeader("X-Frame-Options")}}</li>
-</ul>
+- {{HTTPHeader("Content-Security-Policy")}}
+- {{HTTPHeader("X-Frame-Options")}}
diff --git a/files/en-us/web/http/headers/content-security-policy/frame-src/index.md b/files/en-us/web/http/headers/content-security-policy/frame-src/index.md
index 2e2c882f8aa56cc..befed4c47ed3301 100644
--- a/files/en-us/web/http/headers/content-security-policy/frame-src/index.md
+++ b/files/en-us/web/http/headers/content-security-policy/frame-src/index.md
@@ -2,23 +2,23 @@
 title: 'CSP: frame-src'
 slug: Web/HTTP/Headers/Content-Security-Policy/frame-src
 tags:
-- CSP
-- Content-Security-Policy
-- Directive
-- Frame
-- HTTP
-- Reference
-- Security
-- frame-src
-- source
+  - CSP
+  - Content-Security-Policy
+  - Directive
+  - Frame
+  - HTTP
+  - Reference
+  - Security
+  - frame-src
+  - source
 browser-compat: http.headers.csp.Content-Security-Policy.frame-src
 ---
-<div>{{HTTPSidebar}}</div>
+{{HTTPSidebar}}
 
-<p>The HTTP {{HTTPHeader("Content-Security-Policy")}} (CSP)
-  <code><strong>frame-src</strong></code> directive specifies valid sources for nested
-  browsing contexts loading using elements such as {{HTMLElement("frame")}} and
-  {{HTMLElement("iframe")}}.</p>
+The HTTP {{HTTPHeader("Content-Security-Policy")}} (CSP)
+**`frame-src`** directive specifies valid sources for nested
+browsing contexts loading using elements such as {{HTMLElement("frame")}} and
+{{HTMLElement("iframe")}}.
 
 <table class="properties">
   <tbody>
@@ -32,49 +32,53 @@ browser-compat: http.headers.csp.Content-Security-Policy.frame-src
     </tr>
     <tr>
       <th scope="row">Fallback</th>
-      <td>If this directive is absent, the user agent will look for the
-        {{CSP("child-src")}} directive (which falls back to the {{CSP("default-src")}}
-        directive).</td>
+      <td>
+        If this directive is absent, the user agent will look for the
+        {{CSP("child-src")}} directive (which falls back to the
+        {{CSP("default-src")}} directive).
+      </td>
     </tr>
   </tbody>
 </table>
 
-<h2 id="Syntax">Syntax</h2>
+## Syntax
 
-<p>One or more sources can be allowed for the <code>frame-src</code> policy:</p>
+One or more sources can be allowed for the `frame-src` policy:
 
-<pre class="brush: html">Content-Security-Policy: frame-src &lt;source&gt;;
-Content-Security-Policy: frame-src &lt;source&gt; &lt;source&gt;;
-</pre>
+```html
+Content-Security-Policy: frame-src <source>;
+Content-Security-Policy: frame-src <source> <source>;
+```
 
-<h3 id="Sources">Sources</h3>
+### Sources
 
-<p>{{page("Web/HTTP/Headers/Content-Security-Policy/connect-src", "Sources")}}</p>
+{{page("Web/HTTP/Headers/Content-Security-Policy/connect-src", "Sources")}}
 
-<h2 id="Examples">Examples</h2>
+## Examples
 
-<h3 id="Violation_cases">Violation cases</h3>
+### Violation cases
 
-<p>Given this CSP header:</p>
+Given this CSP header:
 
-<pre class="brush: bash">Content-Security-Policy: frame-src https://example.com/</pre>
+```bash
+Content-Security-Policy: frame-src https://example.com/
+```
 
-<p>The following {{HTMLElement("iframe")}} is blocked and won't load:</p>
+The following {{HTMLElement("iframe")}} is blocked and won't load:
 
-<pre
-  class="brush: html">&lt;iframe src="https://not-example.com/"&gt;&lt;/iframe&gt;</pre>
+```html
+<iframe src="https://not-example.com/"></iframe>
+```
 
-<h2 id="Specifications">Specifications</h2>
+## Specifications
 
 {{Specifications}}
 
-<h2 id="Browser_compatibility">Browser compatibility</h2>
+## Browser compatibility
 
-<p>{{Compat}}</p>
+{{Compat}}
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
-  <li>{{HTTPHeader("Content-Security-Policy")}}</li>
-  <li>{{HTMLElement("frame")}} and {{HTMLElement("iframe")}}</li>
-</ul>
+- {{HTTPHeader("Content-Security-Policy")}}
+- {{HTMLElement("frame")}} and {{HTMLElement("iframe")}}
diff --git a/files/en-us/web/http/headers/content-security-policy/img-src/index.md b/files/en-us/web/http/headers/content-security-policy/img-src/index.md
index a6723986977f00d..2507f4c0accc6ba 100644
--- a/files/en-us/web/http/headers/content-security-policy/img-src/index.md
+++ b/files/en-us/web/http/headers/content-security-policy/img-src/index.md
@@ -2,22 +2,22 @@
 title: 'CSP: img-src'
 slug: Web/HTTP/Headers/Content-Security-Policy/img-src
 tags:
-- CSP
-- Content-Security-Policy
-- Directive
-- HTTP
-- Image
-- Reference
-- Security
-- img-src
-- source
+  - CSP
+  - Content-Security-Policy
+  - Directive
+  - HTTP
+  - Image
+  - Reference
+  - Security
+  - img-src
+  - source
 browser-compat: http.headers.csp.Content-Security-Policy.img-src
 ---
-<div>{{HTTPSidebar}}</div>
+{{HTTPSidebar}}
 
-<p>The HTTP {{HTTPHeader("Content-Security-Policy")}}
-    <code><strong>img-src</strong></code> directive specifies valid sources of images and
-    favicons.</p>
+The HTTP {{HTTPHeader("Content-Security-Policy")}}
+**`img-src`** directive specifies valid sources of images and
+favicons.
 
 <table class="properties">
   <tbody>
@@ -31,48 +31,52 @@ browser-compat: http.headers.csp.Content-Security-Policy.img-src
     </tr>
     <tr>
       <th scope="row">{{CSP("default-src")}} fallback</th>
-      <td>Yes. If this directive is absent, the user agent will look for the
-        <code>default-src</code> directive.</td>
+      <td>
+        Yes. If this directive is absent, the user agent will look for the
+        <code>default-src</code> directive.
+      </td>
     </tr>
   </tbody>
 </table>
 
-<h2 id="Syntax">Syntax</h2>
+## Syntax
 
-<p>One or more sources can be allowed for the <code>img-src</code> policy:</p>
+One or more sources can be allowed for the `img-src` policy:
 
-<pre class="brush: html">Content-Security-Policy: img-src &lt;source&gt;;
-Content-Security-Policy: img-src &lt;source&gt; &lt;source&gt;;
-</pre>
+```html
+Content-Security-Policy: img-src <source>;
+Content-Security-Policy: img-src <source> <source>;
+```
 
-<h3 id="Sources">Sources</h3>
+### Sources
 
-<p>{{page("Web/HTTP/Headers/Content-Security-Policy/default-src", "Sources")}}</p>
+{{page("Web/HTTP/Headers/Content-Security-Policy/default-src", "Sources")}}
 
-<h2 id="Examples">Examples</h2>
+## Examples
 
-<h3 id="Violation_cases">Violation cases</h3>
+### Violation cases
 
-<p>Given this CSP header:</p>
+Given this CSP header:
 
-<pre class="brush: bash">Content-Security-Policy: img-src https://example.com/</pre>
+```bash
+Content-Security-Policy: img-src https://example.com/
+```
 
-<p>The following {{HTMLElement("img")}} is blocked and won't load:</p>
+The following {{HTMLElement("img")}} is blocked and won't load:
 
-<pre
-  class="brush: html">&lt;img src="https://not-example.com/foo.jpg" alt="example picture"&gt;</pre>
+```html
+<img src="https://not-example.com/foo.jpg" alt="example picture">
+```
 
-<h2 id="Specifications">Specifications</h2>
+## Specifications
 
 {{Specifications}}
 
-<h2 id="Browser_compatibility">Browser compatibility</h2>
+## Browser compatibility
 
-<p>{{Compat}}</p>
+{{Compat}}
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
-  <li>{{HTTPHeader("Content-Security-Policy")}}</li>
-  <li>{{HTMLElement("img")}}</li>
-</ul>
+- {{HTTPHeader("Content-Security-Policy")}}
+- {{HTMLElement("img")}}
diff --git a/files/en-us/web/http/headers/content-security-policy/index.md b/files/en-us/web/http/headers/content-security-policy/index.md
index ec7435d4137a6b0..e4f2489cd2a5f96 100644
--- a/files/en-us/web/http/headers/content-security-policy/index.md
+++ b/files/en-us/web/http/headers/content-security-policy/index.md
@@ -10,16 +10,15 @@ tags:
   - header
 browser-compat: http.headers.csp.Content-Security-Policy
 ---
-<div>{{HTTPSidebar}}</div>
+{{HTTPSidebar}}
 
-<p>The HTTP <strong><code>Content-Security-Policy</code></strong> response header allows
-  web site administrators to control resources the user agent is allowed to load for a
-  given page. With a few exceptions, policies mostly involve specifying server origins and
-  script endpoints. This helps guard against cross-site scripting attacks
-  ({{Glossary("Cross-site_scripting")}}).</p>
+The HTTP **`Content-Security-Policy`** response header allows
+web site administrators to control resources the user agent is allowed to load for a
+given page. With a few exceptions, policies mostly involve specifying server origins and
+script endpoints. This helps guard against cross-site scripting attacks
+({{Glossary("Cross-site_scripting")}}).
 
-<p>For more information, see the introductory article on <a
-    href="/en-US/docs/Web/HTTP/CSP">Content Security Policy (CSP)</a>.</p>
+For more information, see the introductory article on [Content Security Policy (CSP)](/en-US/docs/Web/HTTP/CSP).
 
 <table class="properties">
   <tbody>
@@ -34,306 +33,273 @@ browser-compat: http.headers.csp.Content-Security-Policy
   </tbody>
 </table>
 
-<h2 id="Syntax">Syntax</h2>
-
-<pre class="brush: html">Content-Security-Policy: &lt;policy-directive&gt;; &lt;policy-directive&gt;
-</pre>
-
-<p>where <code>&lt;policy-directive&gt;</code> consists of:
-  <code>&lt;directive&gt; &lt;value&gt;</code> with no internal punctuation.</p>
-
-<h2 id="Directives">Directives</h2>
-
-<h3 id="Fetch_directives">Fetch directives</h3>
-
-<p>Fetch directives control the locations from which certain resource types may be loaded.
-</p>
-
-<dl>
-  <dt>{{CSP("child-src")}}</dt>
-  <dd>
-    <p>Defines the valid sources for <a href="/en-US/docs/Web/API/Web_Workers_API">web
-        workers</a> and nested browsing contexts loaded using elements such as
-      {{HTMLElement("frame")}} and {{HTMLElement("iframe")}}.</p>
-
-    <div class="notecard warning">
-      <p>
-        <strong>Warning:</strong> Instead of <strong><code>child-src</code></strong>,
-        if you want to regulate nested browsing contexts and workers,
-        you should use the {{CSP("frame-src")}} and {{CSP("worker-src")}} directives, respectively.
-      </p>
-    </div>
-  </dd>
-  <dt>{{CSP("connect-src")}}</dt>
-  <dd>Restricts the URLs which can be loaded using script interfaces</dd>
-  <dt>{{CSP("default-src")}}</dt>
-  <dd>Serves as a fallback for the other {{Glossary("Fetch directive", "fetch
-    directives")}}.</dd>
-  <dt>{{CSP("font-src")}}</dt>
-  <dd>Specifies valid sources for fonts loaded using {{cssxref("@font-face")}}.</dd>
-  <dt>{{CSP("frame-src")}}</dt>
-  <dd>Specifies valid sources for nested browsing contexts loading using elements such as
-    {{HTMLElement("frame")}} and {{HTMLElement("iframe")}}.</dd>
-  <dt>{{CSP("img-src")}}</dt>
-  <dd>Specifies valid sources of images and favicons.</dd>
-  <dt>{{CSP("manifest-src")}}</dt>
-  <dd>Specifies valid sources of application manifest files.</dd>
-  <dt>{{CSP("media-src")}}</dt>
-  <dd>Specifies valid sources for loading media using the {{HTMLElement("audio")}} ,
-    {{HTMLElement("video")}} and {{HTMLElement("track")}} elements.</dd>
-  <dt>{{CSP("object-src")}}</dt>
-  <dd>Specifies valid sources for the {{HTMLElement("object")}}, {{HTMLElement("embed")}},
+## Syntax
+
+```html
+Content-Security-Policy: <policy-directive>; <policy-directive>
+```
+
+where `<policy-directive>` consists of:
+`<directive> <value>` with no internal punctuation.
+
+## Directives
+
+### Fetch directives
+
+Fetch directives control the locations from which certain resource types may be loaded.
+
+- {{CSP("child-src")}}
+
+  - : Defines the valid sources for [web
+    workers](/en-US/docs/Web/API/Web_Workers_API) and nested browsing contexts loaded using elements such as
+    {{HTMLElement("frame")}} and {{HTMLElement("iframe")}}.
+
+    > **Warning:** Instead of **`child-src`**,
+    > if you want to regulate nested browsing contexts and workers,
+    > you should use the {{CSP("frame-src")}} and {{CSP("worker-src")}} directives, respectively.
+
+- {{CSP("connect-src")}}
+  - : Restricts the URLs which can be loaded using script interfaces
+- {{CSP("default-src")}}
+  - : Serves as a fallback for the other {{Glossary("Fetch directive", "fetch
+    directives")}}.
+- {{CSP("font-src")}}
+  - : Specifies valid sources for fonts loaded using {{cssxref("@font-face")}}.
+- {{CSP("frame-src")}}
+  - : Specifies valid sources for nested browsing contexts loading using elements such as
+    {{HTMLElement("frame")}} and {{HTMLElement("iframe")}}.
+- {{CSP("img-src")}}
+  - : Specifies valid sources of images and favicons.
+- {{CSP("manifest-src")}}
+  - : Specifies valid sources of application manifest files.
+- {{CSP("media-src")}}
+  - : Specifies valid sources for loading media using the {{HTMLElement("audio")}} ,
+    {{HTMLElement("video")}} and {{HTMLElement("track")}} elements.
+- {{CSP("object-src")}}
+
+  - : Specifies valid sources for the {{HTMLElement("object")}}, {{HTMLElement("embed")}},
     and {{HTMLElement("applet")}} elements.
-    <div class="notecard note">
-      <p><strong>Note:</strong> Elements controlled by <code>object-src</code> are perhaps
-        coincidentally considered legacy HTML elements and are not receiving new standardized
-        features (such as the security attributes <code>sandbox</code> or <code>allow</code>
-        for <code>&lt;iframe&gt;</code>). Therefore it is <strong>recommended</strong> to
-        restrict this fetch-directive (e.g., explicitly set <code>object-src 'none'</code> if
-        possible).</p>
-    </div>
-  </dd>
-  <dt>{{CSP("prefetch-src")}}{{experimental_inline}}</dt>
-  <dd>Specifies valid sources to be prefetched or prerendered.</dd>
-  <dt>{{CSP("script-src")}}</dt>
-  <dd>Specifies valid sources for JavaScript.</dd>
-  <dt>{{CSP("script-src-elem")}}{{experimental_inline}}</dt>
-  <dd>Specifies valid sources for JavaScript {{HTMLElement("script")}} elements.</dd>
-  <dt>{{CSP("script-src-attr")}}{{experimental_inline}}</dt>
-  <dd>Specifies valid sources for JavaScript inline event handlers.</dd>
-  <dt>{{CSP("style-src")}}</dt>
-  <dd>Specifies valid sources for stylesheets.</dd>
-  <dt>{{CSP("style-src-elem")}}{{experimental_inline}}</dt>
-  <dd>Specifies valid sources for stylesheets {{HTMLElement("style")}} elements and
-    {{HTMLElement("link")}} elements with <code>rel="stylesheet"</code>.</dd>
-  <dt>{{CSP("style-src-attr")}}{{experimental_inline}}</dt>
-  <dd>Specifies valid sources for inline styles applied to individual DOM elements.</dd>
-  <dt>{{CSP("worker-src")}}{{experimental_inline}}</dt>
-  <dd>Specifies valid sources for {{domxref("Worker")}}, {{domxref("SharedWorker")}}, or
-    {{domxref("ServiceWorker")}} scripts.</dd>
-</dl>
-
-<h3 id="Document_directives">Document directives</h3>
-
-<p>Document directives govern the properties of a document or <a
-    href="/en-US/docs/Web/API/Web_Workers_API">worker</a> environment to which a policy
-  applies.</p>
-
-<dl>
-  <dt>{{CSP("base-uri")}}</dt>
-  <dd>Restricts the URLs which can be used in a document's {{HTMLElement("base")}}
-    element.</dd>
-  <dt>{{CSP("sandbox")}}</dt>
-  <dd>Enables a sandbox for the requested resource similar to the
-    {{HTMLElement("iframe")}} {{htmlattrxref("sandbox", "iframe")}} attribute.</dd>
-</dl>
-
-<h3 id="Navigation_directives">Navigation directives</h3>
-
-<p>Navigation directives govern to which locations a user can navigate or submit a form,
-  for example.</p>
-
-<dl>
-  <dt>{{CSP("form-action")}}</dt>
-  <dd>Restricts the URLs which can be used as the target of a form submissions from a
-    given context.</dd>
-  <dt>{{CSP("frame-ancestors")}}</dt>
-  <dd>Specifies valid parents that may embed a page using {{HTMLElement("frame")}},
+
+    > **Note:** Elements controlled by `object-src` are perhaps
+    > coincidentally considered legacy HTML elements and are not receiving new standardized
+    > features (such as the security attributes `sandbox` or `allow`
+    > for `<iframe>`). Therefore it is **recommended** to
+    > restrict this fetch-directive (e.g., explicitly set `object-src 'none'` if
+    > possible).
+
+- {{CSP("prefetch-src")}}{{experimental_inline}}
+  - : Specifies valid sources to be prefetched or prerendered.
+- {{CSP("script-src")}}
+  - : Specifies valid sources for JavaScript.
+- {{CSP("script-src-elem")}}{{experimental_inline}}
+  - : Specifies valid sources for JavaScript {{HTMLElement("script")}} elements.
+- {{CSP("script-src-attr")}}{{experimental_inline}}
+  - : Specifies valid sources for JavaScript inline event handlers.
+- {{CSP("style-src")}}
+  - : Specifies valid sources for stylesheets.
+- {{CSP("style-src-elem")}}{{experimental_inline}}
+  - : Specifies valid sources for stylesheets {{HTMLElement("style")}} elements and
+    {{HTMLElement("link")}} elements with `rel="stylesheet"`.
+- {{CSP("style-src-attr")}}{{experimental_inline}}
+  - : Specifies valid sources for inline styles applied to individual DOM elements.
+- {{CSP("worker-src")}}{{experimental_inline}}
+  - : Specifies valid sources for {{domxref("Worker")}}, {{domxref("SharedWorker")}}, or
+    {{domxref("ServiceWorker")}} scripts.
+
+### Document directives
+
+Document directives govern the properties of a document or [worker](/en-US/docs/Web/API/Web_Workers_API) environment to which a policy
+applies.
+
+- {{CSP("base-uri")}}
+  - : Restricts the URLs which can be used in a document's {{HTMLElement("base")}}
+    element.
+- {{CSP("sandbox")}}
+  - : Enables a sandbox for the requested resource similar to the
+    {{HTMLElement("iframe")}} {{htmlattrxref("sandbox", "iframe")}} attribute.
+
+### Navigation directives
+
+Navigation directives govern to which locations a user can navigate or submit a form,
+for example.
+
+- {{CSP("form-action")}}
+  - : Restricts the URLs which can be used as the target of a form submissions from a
+    given context.
+- {{CSP("frame-ancestors")}}
+  - : Specifies valid parents that may embed a page using {{HTMLElement("frame")}},
     {{HTMLElement("iframe")}}, {{HTMLElement("object")}}, {{HTMLElement("embed")}}, or
-    {{HTMLElement("applet")}}.</dd>
-  <dt>{{CSP("navigate-to")}}{{experimental_inline}}</dt>
-  <dd>Restricts the URLs to which a document can initiate navigation by any means,
+    {{HTMLElement("applet")}}.
+- {{CSP("navigate-to")}}{{experimental_inline}}
+  - : Restricts the URLs to which a document can initiate navigation by any means,
     including {{HTMLElement("form")}} (if {{CSP("form-action")}} is not specified),
     {{HTMLElement("a")}}, {{DOMxRef("window.location")}}, {{DOMxRef("window.open")}}, etc.
-  </dd>
-</dl>
 
-<h3 id="Reporting_directives">Reporting directives</h3>
+### Reporting directives
+
+Reporting directives control the reporting process of CSP violations. See also the
+{{HTTPHeader("Content-Security-Policy-Report-Only")}} header.
 
-<p>Reporting directives control the reporting process of CSP violations. See also the
-  {{HTTPHeader("Content-Security-Policy-Report-Only")}} header.</p>
+- {{CSP("report-uri")}}{{deprecated_inline}}
 
-<dl>
-  <dt>{{CSP("report-uri")}}{{deprecated_inline}}</dt>
-  <dd>Instructs the user agent to report attempts to violate the Content Security Policy.
+  - : Instructs the user agent to report attempts to violate the Content Security Policy.
     These violation reports consist of {{Glossary("JSON")}} documents sent via an HTTP
-    <code>POST</code> request to the specified URI.
-    <div class="notecard warning">
-      <p>
-        <strong>Warning:</strong> Though the {{CSP("report-to")}} directive is intended
-        to replace the deprecated <code><strong>report-uri</strong></code> directive,
-        {{CSP("report-to")}} is not supported in most browsers yet.
-        So for compatibility with current browsers
-        while also adding forward compatibility when browsers get {{CSP("report-to")}} support,
-        you can specify both <code><strong>report-uri</strong></code> and {{CSP("report-to")}}:
-      </p>
-
-      <pre class="brush: html">Content-Security-Policy: ...; report-uri https://endpoint.example.com; report-to groupname</pre>
-
-      <p>
-        In browsers that support {{CSP("report-to")}},
-        the <code><strong>report-uri</strong></code> directive will be ignored.
-      </p>
-    </div>
-  </dd>
-  <dt>{{CSP("report-to")}}{{experimental_inline}}</dt>
-  <dd>Fires a <code>SecurityPolicyViolationEvent</code>.</dd>
-</dl>
-
-<h3 id="Other_directives">Other directives</h3>
-
-<dl>
-  <dt>{{CSP("require-sri-for")}}{{experimental_inline}}</dt>
-  <dd>Requires the use of {{Glossary("SRI")}} for scripts or styles on the page.</dd>
-  <dt>{{CSP("require-trusted-types-for")}}{{experimental_inline}}</dt>
-  <dd>Enforces <a href="https://w3c.github.io/webappsec-trusted-types/dist/spec/">Trusted
-      Types</a> at the DOM XSS injection sinks.</dd>
-  <dt>{{CSP("trusted-types")}}{{experimental_inline}}</dt>
-  <dd>Used to specify an allow-list of <a
-      href="https://w3c.github.io/webappsec-trusted-types/dist/spec/">Trusted Types</a>
+    `POST` request to the specified URI.
+
+    > **Warning:** Though the {{CSP("report-to")}} directive is intended
+    > to replace the deprecated **`report-uri`** directive,
+    > {{CSP("report-to")}} is not supported in most browsers yet.
+    > So for compatibility with current browsers
+    > while also adding forward compatibility when browsers get {{CSP("report-to")}} support,
+    > you can specify both **`report-uri`** and {{CSP("report-to")}}:
+    >
+    > ```html
+        > Content-Security-Policy: ...; report-uri https://endpoint.example.com; report-to groupname
+        > ```
+    >
+    > In browsers that support {{CSP("report-to")}},
+    > the **`report-uri`** directive will be ignored.
+
+- {{CSP("report-to")}}{{experimental_inline}}
+  - : Fires a `SecurityPolicyViolationEvent`.
+
+### Other directives
+
+- {{CSP("require-sri-for")}}{{experimental_inline}}
+  - : Requires the use of {{Glossary("SRI")}} for scripts or styles on the page.
+- {{CSP("require-trusted-types-for")}}{{experimental_inline}}
+  - : Enforces [Trusted
+    Types](https://w3c.github.io/webappsec-trusted-types/dist/spec/) at the DOM XSS injection sinks.
+- {{CSP("trusted-types")}}{{experimental_inline}}
+  - : Used to specify an allow-list of [Trusted Types](https://w3c.github.io/webappsec-trusted-types/dist/spec/)
     policies. Trusted Types allows applications to lock down DOM XSS injection sinks to
-    only accept non-spoofable, typed values in place of strings.</dd>
-  <dt>{{CSP("upgrade-insecure-requests")}}</dt>
-  <dd>Instructs user agents to treat all of a site's insecure URLs (those served over
+    only accept non-spoofable, typed values in place of strings.
+- {{CSP("upgrade-insecure-requests")}}
+  - : Instructs user agents to treat all of a site's insecure URLs (those served over
     HTTP) as though they have been replaced with secure URLs (those served over HTTPS).
     This directive is intended for web sites with large numbers of insecure legacy URLs
-    that need to be rewritten.</dd>
-</dl>
-
-<h3 id="deprecated_directives">Deprecated directives</h3>
-
-<dl>
-  <dt>{{CSP("block-all-mixed-content")}}{{deprecated_inline}}</dt>
-  <dd>Prevents loading any assets using HTTP when the page is loaded using HTTPS.</dd>
-  <dt>{{CSP("plugin-types")}}{{deprecated_inline}}</dt>
-  <dd>Restricts the set of plugins that can be embedded into a document by limiting the
-    types of resources which can be loaded.</dd>
-  <dt>{{CSP("referrer")}}{{deprecated_inline}}{{non-standard_inline}}</dt>
-  <dd>Used to specify information in the <a
-      href="/en-US/docs/Web/HTTP/Headers/Referer">Referer</a> (sic) header for links away
-    from a page. Use the {{HTTPHeader("Referrer-Policy")}} header instead.</dd>
-</dl>
-
-<h2 id="Values">Values</h2>
-
-<h3 id="Keyword_values">Keyword values</h3>
-
-<dl>
- <dt><code>none</code></dt>
- <dd>Won't allow loading of any resources.</dd>
- <dt><code>self</code></dt>
- <dd>Only allow resources from the current origin.</dd>
- <dt><code>strict-dynamic</code> {{experimental_inline}}</dt>
- <dd>TBD</dd>
- <dt><code>report-sample</code> {{experimental_inline}}</dt>
- <dd>TBD</dd>
-</dl>
-
-<h3 id="Unsafe_keyword_values">Unsafe keyword values</h3>
-
-<dl>
- <dt><code>unsafe-inline</code></dt>
- <dd>Allow use of inline resources.</dd>
- <dt><code>unsafe-eval</code></dt>
- <dd>Allow use of dynamic code evaluation such as {{jsxref("Global_Objects/eval", "eval")}}, {{domxref("Window.setImmediate", "setImmediate")}}{{non-standard_inline}}, and <code>window.execScript</code> {{non-standard_inline}}.</dd>
- <dt><code>unsafe-hashes</code> {{experimental_inline}}</dt>
- <dd>TBD</dd>
- <dt><code>unsafe-allow-redirects</code> {{experimental_inline}}</dt>
- <dd>TBD</dd>
-</dl>
-
-<h3 id="Hosts_values">Hosts values</h3>
-
-<dl>
- <dt>Host</dt>
- <dd>Only allow loading of resources from a specific host, with optional scheme, port, and path. e.g. <code>example.com</code>, <code>*.example.com</code>, <code>https://*.example.com:12/path/to/file.js</code></dd>
- <dt>Scheme:</dt>
- <dd>Only allow loading of resources over a specific scheme, should always end with "<code>:</code>". e.g. <code>https:</code>, <code>http:</code>, <code>data:</code> etc.</dd>
-</dl>
-
-<h3 id="Other_values">Other values</h3>
-
-<dl>
- <dt>nonce-*</dt>
- <dd>A cryptographic nonce (only used once) to whitelist scripts. The server must generate a unique nonce value each time it transmits a policy. It is critical to provide a nonce that cannot be guessed as bypassing a resource's policy is otherwise trivial. This is used in conjunction with the <a href="/en-US/docs/Web/HTML/Element/script#attr-nonce">script tag nonce attribute</a>. e.g. <code>nonce-DhcnhD3khTMePgXwdayK9BsMqXjhguVV</code></dd>
- <dt>sha*-*</dt>
- <dd>sha256, sha384, or sha512. followed by a dash and then the sha* value. e.g. <code>sha256-jzgBGA4UWFFmpOBq0JpdsySukE1FrEN5bUpoK8Z29fY=</code></dd>
-</dl>
-
-<h2 id="CSP_in_workers">CSP in workers</h2>
-
-<p><a href="/en-US/docs/Web/API/Worker">Workers</a> are in general <em>not</em> governed
-  by the content security policy of the document (or parent worker) that created them. To
-  specify a content security policy for the worker, set a
-  <code>Content-Security-Policy</code> response header for the request which requested the
-  worker script itself.</p>
-
-<p>The exception to this is if the worker script's origin is a globally unique identifier
-  (for example, if its URL has a scheme of data or blob). In this case, the worker does
-  inherit the content security policy of the document or worker that created it.</p>
-
-<h2 id="Multiple_content_security_policies">Multiple content security policies</h2>
-
-<p>The CSP mechanism allows multiple policies being specified for a resource, including
-  via the <code>Content-Security-Policy</code> header, the
-  {{HTTPHeader("Content-Security-Policy-Report-Only")}} header and a
-  {{HTMLElement("meta")}} element.</p>
-
-<p>You can use the <code>Content-Security-Policy</code> header more than once, as in the
-  example below. Pay special attention to the {{CSP("connect-src")}} directive here. Even
-  though the second policy would allow the connection, the first policy contains
-  <code>connect-src 'none'</code>. Adding additional policies <em>can only further
-    restrict</em> the capabilities of the protected resource, which means that there will
-  be no connection allowed and, as the strictest policy, <code>connect-src 'none'</code>
-  is enforced.</p>
-
-<pre>Content-Security-Policy: default-src 'self' http://example.com;
-                         connect-src 'none';
-Content-Security-Policy: connect-src http://example.com/;
-                         script-src http://example.com/</pre>
-
-<h2 id="Examples">Examples</h2>
-
-<p>Example: Disable unsafe inline/eval, only allow loading of resources (images, fonts,
-  scripts, etc.) over https:</p>
-
-<pre>// header
-Content-Security-Policy: default-src https:
-
-// meta tag
-&lt;meta http-equiv="Content-Security-Policy" content="default-src https:"&gt;
-</pre>
-
-<p>Example: Pre-existing site that uses too much inline code to fix but wants to ensure
-  resources are loaded only over HTTPS and to disable plugins:</p>
-
-<pre>Content-Security-Policy: default-src https: 'unsafe-eval' 'unsafe-inline'; object-src 'none'</pre>
+    that need to be rewritten.
+
+### Deprecated directives
+
+- {{CSP("block-all-mixed-content")}}{{deprecated_inline}}
+  - : Prevents loading any assets using HTTP when the page is loaded using HTTPS.
+- {{CSP("plugin-types")}}{{deprecated_inline}}
+  - : Restricts the set of plugins that can be embedded into a document by limiting the
+    types of resources which can be loaded.
+- {{CSP("referrer")}}{{deprecated_inline}}{{non-standard_inline}}
+  - : Used to specify information in the [Referer](/en-US/docs/Web/HTTP/Headers/Referer) (sic) header for links away
+    from a page. Use the {{HTTPHeader("Referrer-Policy")}} header instead.
+
+## Values
+
+### Keyword values
+
+- `none`
+  - : Won't allow loading of any resources.
+- `self`
+  - : Only allow resources from the current origin.
+- `strict-dynamic` {{experimental_inline}}
+  - : TBD
+- `report-sample` {{experimental_inline}}
+  - : TBD
+
+### Unsafe keyword values
+
+- `unsafe-inline`
+  - : Allow use of inline resources.
+- `unsafe-eval`
+  - : Allow use of dynamic code evaluation such as {{jsxref("Global_Objects/eval", "eval")}}, {{domxref("Window.setImmediate", "setImmediate")}}{{non-standard_inline}}, and `window.execScript` {{non-standard_inline}}.
+- `unsafe-hashes` {{experimental_inline}}
+  - : TBD
+- `unsafe-allow-redirects` {{experimental_inline}}
+  - : TBD
+
+### Hosts values
+
+- Host
+  - : Only allow loading of resources from a specific host, with optional scheme, port, and path. e.g. `example.com`, `*.example.com`, `https://*.example.com:12/path/to/file.js`
+- Scheme:
+  - : Only allow loading of resources over a specific scheme, should always end with "`:`". e.g. `https:`, `http:`, `data:` etc.
+
+### Other values
+
+- nonce-\*
+  - : A cryptographic nonce (only used once) to whitelist scripts. The server must generate a unique nonce value each time it transmits a policy. It is critical to provide a nonce that cannot be guessed as bypassing a resource's policy is otherwise trivial. This is used in conjunction with the [script tag nonce attribute](/en-US/docs/Web/HTML/Element/script#attr-nonce). e.g. `nonce-DhcnhD3khTMePgXwdayK9BsMqXjhguVV`
+- sha\*-\*
+  - : sha256, sha384, or sha512. followed by a dash and then the sha\* value. e.g. `sha256-jzgBGA4UWFFmpOBq0JpdsySukE1FrEN5bUpoK8Z29fY=`
+
+## CSP in workers
+
+[Workers](/en-US/docs/Web/API/Worker) are in general _not_ governed
+by the content security policy of the document (or parent worker) that created them. To
+specify a content security policy for the worker, set a
+`Content-Security-Policy` response header for the request which requested the
+worker script itself.
+
+The exception to this is if the worker script's origin is a globally unique identifier
+(for example, if its URL has a scheme of data or blob). In this case, the worker does
+inherit the content security policy of the document or worker that created it.
+
+## Multiple content security policies
+
+The CSP mechanism allows multiple policies being specified for a resource, including
+via the `Content-Security-Policy` header, the
+{{HTTPHeader("Content-Security-Policy-Report-Only")}} header and a
+{{HTMLElement("meta")}} element.
+
+You can use the `Content-Security-Policy` header more than once, as in the
+example below. Pay special attention to the {{CSP("connect-src")}} directive here. Even
+though the second policy would allow the connection, the first policy contains
+`connect-src 'none'`. Adding additional policies _can only further
+restrict_ the capabilities of the protected resource, which means that there will
+be no connection allowed and, as the strictest policy, `connect-src 'none'`
+is enforced.
+
+    Content-Security-Policy: default-src 'self' http://example.com;
+                             connect-src 'none';
+    Content-Security-Policy: connect-src http://example.com/;
+                             script-src http://example.com/
+
+## Examples
+
+Example: Disable unsafe inline/eval, only allow loading of resources (images, fonts,
+scripts, etc.) over https:
+
+    // header
+    Content-Security-Policy: default-src https:
+
+    // meta tag
+    <meta http-equiv="Content-Security-Policy" content="default-src https:">
+
+Example: Pre-existing site that uses too much inline code to fix but wants to ensure
+resources are loaded only over HTTPS and to disable plugins:
+
+    Content-Security-Policy: default-src https: 'unsafe-eval' 'unsafe-inline'; object-src 'none'
 
-<p>Example: Do not implement the above policy yet; instead just report violations that
-  would have occurred:</p>
+Example: Do not implement the above policy yet; instead just report violations that
+would have occurred:
 
-<pre>Content-Security-Policy-Report-Only: default-src https:; report-uri /csp-violation-report-endpoint/</pre>
+    Content-Security-Policy-Report-Only: default-src https:; report-uri /csp-violation-report-endpoint/
 
-<p>See <a href="https://infosec.mozilla.org/guidelines/web_security#Examples_5">Mozilla
-    Web Security Guidelines</a> for more examples.</p>
+See [Mozilla
+Web Security Guidelines](https://infosec.mozilla.org/guidelines/web_security#Examples_5) for more examples.
 
-<h2 id="Specifications">Specifications</h2>
+## Specifications
 
 {{Specifications}}
 
-<h2 id="Browser_compatibility">Browser compatibility</h2>
+## Browser compatibility
 
-<p>{{Compat}}</p>
+{{Compat}}
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
-  <li>{{HTTPHeader("Content-Security-Policy-Report-Only")}}</li>
-  <li><a href="/en-US/docs/Web/HTTP/CSP">Learn about: Content Security Policy</a></li>
-  <li><a href="/en-US/docs/Mozilla/Add-ons/WebExtensions/Content_Security_Policy">Content
-      Security in WebExtensions</a></li>
-  <li><a href="https://csp.withgoogle.com/docs/strict-csp.html">Adopting a strict
-      policy</a></li>
-  <li><a href="https://github.com/google/csp-evaluator">CSP Evaluator</a> - Evaluate your
-    Content Security Policy</li>
-</ul>
+- {{HTTPHeader("Content-Security-Policy-Report-Only")}}
+- [Learn about: Content Security Policy](/en-US/docs/Web/HTTP/CSP)
+- [Content
+  Security in WebExtensions](/en-US/docs/Mozilla/Add-ons/WebExtensions/Content_Security_Policy)
+- [Adopting a strict
+  policy](https://csp.withgoogle.com/docs/strict-csp.html)
+- [CSP Evaluator](https://github.com/google/csp-evaluator) - Evaluate your
+  Content Security Policy
diff --git a/files/en-us/web/http/headers/content-security-policy/manifest-src/index.md b/files/en-us/web/http/headers/content-security-policy/manifest-src/index.md
index 546798b0573851e..ec83d757718b069 100644
--- a/files/en-us/web/http/headers/content-security-policy/manifest-src/index.md
+++ b/files/en-us/web/http/headers/content-security-policy/manifest-src/index.md
@@ -2,23 +2,23 @@
 title: 'CSP: manifest-src'
 slug: Web/HTTP/Headers/Content-Security-Policy/manifest-src
 tags:
-- CSP
-- Content-Security-Policy
-- Directive
-- HTTP
-- Manifest
-- Reference
-- Security
-- manifest-src
-- source
+  - CSP
+  - Content-Security-Policy
+  - Directive
+  - HTTP
+  - Manifest
+  - Reference
+  - Security
+  - manifest-src
+  - source
 browser-compat: http.headers.csp.Content-Security-Policy.manifest-src
 ---
-<div>{{HTTPSidebar}}</div>
+{{HTTPSidebar}}
 
-<p>The HTTP
-  {{HTTPHeader("Content-Security-Policy")}}<code>: <strong>manifest-src</strong></code>
-  directive specifies which <a href="/en-US/docs/Web/Manifest">manifest</a> can be applied
-  to the resource.</p>
+The HTTP
+{{HTTPHeader("Content-Security-Policy")}}`: manifest-src`
+directive specifies which [manifest](/en-US/docs/Web/Manifest) can be applied
+to the resource.
 
 <table class="properties">
   <tbody>
@@ -32,49 +32,53 @@ browser-compat: http.headers.csp.Content-Security-Policy.manifest-src
     </tr>
     <tr>
       <th scope="row">{{CSP("default-src")}} fallback</th>
-      <td>Yes. If this directive is absent, the user agent will look for the
-        <code>default-src</code> directive.</td>
+      <td>
+        Yes. If this directive is absent, the user agent will look for the
+        <code>default-src</code> directive.
+      </td>
     </tr>
   </tbody>
 </table>
 
-<h2 id="Syntax">Syntax</h2>
+## Syntax
 
-<p>One or more sources can be allowed for the <code>manifest-src</code> policy:</p>
+One or more sources can be allowed for the `manifest-src` policy:
 
-<pre class="brush: html">Content-Security-Policy: manifest-src &lt;source&gt;;
-Content-Security-Policy: manifest-src &lt;source&gt; &lt;source&gt;;
-</pre>
+```html
+Content-Security-Policy: manifest-src <source>;
+Content-Security-Policy: manifest-src <source> <source>;
+```
 
-<h3 id="Sources">Sources</h3>
+### Sources
 
-<p>{{page("Web/HTTP/Headers/Content-Security-Policy/connect-src", "Sources")}}</p>
+{{page("Web/HTTP/Headers/Content-Security-Policy/connect-src", "Sources")}}
 
-<h2 id="Examples">Examples</h2>
+## Examples
 
-<h3 id="Violation_cases">Violation cases</h3>
+### Violation cases
 
-<p>Given this CSP header:</p>
+Given this CSP header:
 
-<pre class="brush: bash">Content-Security-Policy: manifest-src https://example.com/</pre>
+```bash
+Content-Security-Policy: manifest-src https://example.com/
+```
 
-<p>The following {{HTMLElement("link")}} is blocked and won't load:</p>
+The following {{HTMLElement("link")}} is blocked and won't load:
 
-<pre
-  class="brush: html">&lt;link rel="manifest" href="https://not-example.com/manifest"&gt;</pre>
+```html
+<link rel="manifest" href="https://not-example.com/manifest">
+```
 
-<h2 id="Specifications">Specifications</h2>
+## Specifications
 
 {{Specifications}}
 
-<h2 id="Browser_compatibility">Browser compatibility</h2>
+## Browser compatibility
 
-<p>{{Compat}}</p>
+{{Compat}}
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
-  <li>{{HTTPHeader("Content-Security-Policy")}}</li>
-  <li><a href="/en-US/docs/Web/Manifest">Web app manifest</a></li>
-  <li>{{HTMLElement("link")}}</li>
-</ul>
+- {{HTTPHeader("Content-Security-Policy")}}
+- [Web app manifest](/en-US/docs/Web/Manifest)
+- {{HTMLElement("link")}}
diff --git a/files/en-us/web/http/headers/content-security-policy/media-src/index.md b/files/en-us/web/http/headers/content-security-policy/media-src/index.md
index 4fe56baff280f2e..32f61a51db97c24 100644
--- a/files/en-us/web/http/headers/content-security-policy/media-src/index.md
+++ b/files/en-us/web/http/headers/content-security-policy/media-src/index.md
@@ -2,22 +2,22 @@
 title: 'CSP: media-src'
 slug: Web/HTTP/Headers/Content-Security-Policy/media-src
 tags:
-- CSP
-- Content-Security-Policy
-- Directive
-- HTTP
-- Media
-- Reference
-- Security
-- media-src
-- source
+  - CSP
+  - Content-Security-Policy
+  - Directive
+  - HTTP
+  - Media
+  - Reference
+  - Security
+  - media-src
+  - source
 browser-compat: http.headers.csp.Content-Security-Policy.media-src
 ---
-<div>{{HTTPSidebar}}</div>
+{{HTTPSidebar}}
 
-<p>The HTTP {{HTTPHeader("Content-Security-Policy")}} (CSP)
-  <code><strong>media-src</strong></code> directive specifies valid sources for loading
-  media using the {{HTMLElement("audio")}} and {{HTMLElement("video")}} elements.</p>
+The HTTP {{HTTPHeader("Content-Security-Policy")}} (CSP)
+**`media-src`** directive specifies valid sources for loading
+media using the {{HTMLElement("audio")}} and {{HTMLElement("video")}} elements.
 
 <table class="properties">
   <tbody>
@@ -31,52 +31,57 @@ browser-compat: http.headers.csp.Content-Security-Policy.media-src
     </tr>
     <tr>
       <th scope="row">{{CSP("default-src")}} fallback</th>
-      <td>Yes. If this directive is absent, the user agent will look for the
-        <code>default-src</code> directive.</td>
+      <td>
+        Yes. If this directive is absent, the user agent will look for the
+        <code>default-src</code> directive.
+      </td>
     </tr>
   </tbody>
 </table>
 
-<h2 id="Syntax">Syntax</h2>
+## Syntax
 
-<p>One or more sources can be allowed for the <code>media-src</code> policy:</p>
+One or more sources can be allowed for the `media-src` policy:
 
-<pre class="brush: html">Content-Security-Policy: media-src &lt;source&gt;;
-Content-Security-Policy: media-src &lt;source&gt; &lt;source&gt;;
-</pre>
+```html
+Content-Security-Policy: media-src <source>;
+Content-Security-Policy: media-src <source> <source>;
+```
 
-<h3 id="Sources">Sources</h3>
+### Sources
 
-<p>{{page("Web/HTTP/Headers/Content-Security-Policy/connect-src", "Sources")}}</p>
+{{page("Web/HTTP/Headers/Content-Security-Policy/connect-src", "Sources")}}
 
-<h2 id="Examples">Examples</h2>
+## Examples
 
-<h3 id="Violation_cases">Violation cases</h3>
+### Violation cases
 
-<p>Given this CSP header:</p>
+Given this CSP header:
 
-<pre class="brush: bash">Content-Security-Policy: media-src https://example.com/</pre>
+```bash
+Content-Security-Policy: media-src https://example.com/
+```
 
-<p>The following {{HTMLElement("audio")}}, {{HTMLElement("video")}} and
-  {{HTMLElement("track")}} elements are blocked and won't load:</p>
+The following {{HTMLElement("audio")}}, {{HTMLElement("video")}} and
+{{HTMLElement("track")}} elements are blocked and won't load:
 
-<pre class="brush: html">&lt;audio src="https://not-example.com/audio"&gt;&lt;/audio&gt;
+```html
+<audio src="https://not-example.com/audio"></audio>
 
-&lt;video src="https://not-example.com/video"&gt;
-  &lt;track kind="subtitles" src="https://not-example.com/subtitles"&gt;
-&lt;/video&gt;</pre>
+<video src="https://not-example.com/video">
+  <track kind="subtitles" src="https://not-example.com/subtitles">
+</video>
+```
 
-<h2 id="Specifications">Specifications</h2>
+## Specifications
 
 {{Specifications}}
 
-<h2 id="Browser_compatibility">Browser compatibility</h2>
+## Browser compatibility
 
-<p>{{Compat}}</p>
+{{Compat}}
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
-  <li>{{HTTPHeader("Content-Security-Policy")}}</li>
-  <li>{{HTMLElement("audio")}}, {{HTMLElement("video")}} and {{HTMLElement("track")}}</li>
-</ul>
+- {{HTTPHeader("Content-Security-Policy")}}
+- {{HTMLElement("audio")}}, {{HTMLElement("video")}} and {{HTMLElement("track")}}
diff --git a/files/en-us/web/http/headers/content-security-policy/navigate-to/index.md b/files/en-us/web/http/headers/content-security-policy/navigate-to/index.md
index aa3ca3d00b3ac61..0e178e413807712 100644
--- a/files/en-us/web/http/headers/content-security-policy/navigate-to/index.md
+++ b/files/en-us/web/http/headers/content-security-policy/navigate-to/index.md
@@ -2,32 +2,28 @@
 title: 'CSP: navigate-to'
 slug: Web/HTTP/Headers/Content-Security-Policy/navigate-to
 tags:
-- CSP
-- Content-Security-Policy
-- Directive
-- HTTP
-- Navigation
-- Reference
-- Security
+  - CSP
+  - Content-Security-Policy
+  - Directive
+  - HTTP
+  - Navigation
+  - Reference
+  - Security
 browser-compat: http.headers.csp.Content-Security-Policy.navigate-to
 ---
-<div>{{HTTPSidebar}}</div>
-
-<p>The HTTP {{HTTPHeader("Content-Security-Policy")}} (CSP)
-  <code><strong>navigate</strong></code><strong><code>-to</code></strong> directive
-  restricts the URLs to which a document can initiate navigations by any means including
-  {{HTMLElement("form")}} (if {{CSP("form-action")}} is not specified),
-  {{HTMLElement("a")}}, {{DOMxRef("window.location")}}, {{DOMxRef("window.open")}}, etc.
-  This is an enforcement on what navigations this document initiates <strong>not</strong>
-  on what this document is allowed to navigate to.</p>
-
-<div class="notecard note">
-  <p>
-    <strong>Note:</strong> If the {{CSP("form-action")}} directive is present,
-    the <code>navigate-to</code> directive will not act on navigations
-    that are form submissions.
-  </p>
-</div>
+{{HTTPSidebar}}
+
+The HTTP {{HTTPHeader("Content-Security-Policy")}} (CSP)
+**`navigate`\*\***`-to`** directive
+restricts the URLs to which a document can initiate navigations by any means including
+{{HTMLElement("form")}} (if {{CSP("form-action")}} is not specified),
+{{HTMLElement("a")}}, {{DOMxRef("window.location")}}, {{DOMxRef("window.open")}}, etc.
+This is an enforcement on what navigations this document initiates **not\*\*
+on what this document is allowed to navigate to.
+
+> **Note:** If the {{CSP("form-action")}} directive is present,
+> the `navigate-to` directive will not act on navigations
+> that are form submissions.
 
 <table class="properties">
   <tbody>
@@ -46,53 +42,54 @@ browser-compat: http.headers.csp.Content-Security-Policy.navigate-to
   </tbody>
 </table>
 
-<h2 id="Syntax">Syntax</h2>
+## Syntax
 
-<p>One or more sources can be set for the <code>navigate-to</code> policy:</p>
+One or more sources can be set for the `navigate-to` policy:
 
-<pre class="brush: html">Content-Security-Policy: navigate-to &lt;source&gt;;
-Content-Security-Policy: navigate-to &lt;source&gt; &lt;source&gt;;
-</pre>
+```html
+Content-Security-Policy: navigate-to <source>;
+Content-Security-Policy: navigate-to <source> <source>;
+```
 
-<h3 id="Sources">Sources</h3>
+### Sources
 
-<p>{{page("Web/HTTP/Headers/Content-Security-Policy/default-src", "Sources")}}</p>
+{{page("Web/HTTP/Headers/Content-Security-Policy/default-src", "Sources")}}
 
-<h2 id="Examples">Examples</h2>
+## Examples
 
-<h3 id="Meta_tag_configuration">Meta tag configuration</h3>
+### Meta tag configuration
 
-<pre class="brush: html">&lt;meta http-equiv="Content-Security-Policy" content="navigate-to 'none'"&gt;
-</pre>
+```html
+<meta http-equiv="Content-Security-Policy" content="navigate-to 'none'">
+```
 
-<h3 id="Violation_case">Violation case</h3>
+### Violation case
 
-<p>Using a {{HTMLElement("form")}} element with an action set to inline JavaScript will
-  result in a CSP violation.</p>
+Using a {{HTMLElement("form")}} element with an action set to inline JavaScript will
+result in a CSP violation.
 
-<pre class="brush: html; example-bad">&lt;meta http-equiv="Content-Security-Policy" content="navigate-to 'none'"&gt;
+```html example-bad
+<meta http-equiv="Content-Security-Policy" content="navigate-to 'none'">
 
-&lt;form action="javascript:alert('Foo')" id="form1" method="post"&gt;
-  &lt;input type="text" name="fieldName" value="fieldValue"&gt;
-  &lt;input type="submit" id="submit" value="submit"&gt;
-&lt;/form&gt;
-</pre>
+<form action="javascript:alert('Foo')" id="form1" method="post">
+  <input type="text" name="fieldName" value="fieldValue">
+  <input type="submit" id="submit" value="submit">
+</form>
+```
 
-<h2 id="Specifications">Specifications</h2>
+## Specifications
 
 {{Specifications}}
 
-<h2 id="Browser_compatibility">Browser compatibility</h2>
+## Browser compatibility
 
-<p>{{Compat}}</p>
+{{Compat}}
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
-  <li>{{HTTPheader("Content-Security-Policy")}}</li>
-  <li>{{CSP("form-action")}}</li>
-  <li>{{HTMLElement("a")}} <code>href</code> attribute</li>
-  <li>{{HTMLElement("form")}}</li>
-  <li>{{DOMxRef("window.location")}}</li>
-  <li>{{DOMxRef("window.open")}}</li>
-</ul>
+- {{HTTPheader("Content-Security-Policy")}}
+- {{CSP("form-action")}}
+- {{HTMLElement("a")}} `href` attribute
+- {{HTMLElement("form")}}
+- {{DOMxRef("window.location")}}
+- {{DOMxRef("window.open")}}
diff --git a/files/en-us/web/http/headers/content-security-policy/object-src/index.md b/files/en-us/web/http/headers/content-security-policy/object-src/index.md
index 16e84c984b7c997..3336fcfe5bce12a 100644
--- a/files/en-us/web/http/headers/content-security-policy/object-src/index.md
+++ b/files/en-us/web/http/headers/content-security-policy/object-src/index.md
@@ -2,34 +2,32 @@
 title: 'CSP: object-src'
 slug: Web/HTTP/Headers/Content-Security-Policy/object-src
 tags:
-- CSP
-- Content-Security-Policy
-- Directive
-- HTTP
-- Object
-- Reference
-- Security
-- object-src
-- source
+  - CSP
+  - Content-Security-Policy
+  - Directive
+  - HTTP
+  - Object
+  - Reference
+  - Security
+  - object-src
+  - source
 browser-compat: http.headers.csp.Content-Security-Policy.object-src
 ---
-<div>{{HTTPSidebar}}</div>
+{{HTTPSidebar}}
 
-<p>The HTTP {{HTTPHeader("Content-Security-Policy")}}
-  <code><strong>object-src</strong></code> directive specifies valid sources for the
-  {{HTMLElement("object")}}, {{HTMLElement("embed")}}, and {{HTMLElement("applet")}}
-  elements.</p>
+The HTTP {{HTTPHeader("Content-Security-Policy")}}
+**`object-src`** directive specifies valid sources for the
+{{HTMLElement("object")}}, {{HTMLElement("embed")}}, and {{HTMLElement("applet")}}
+elements.
 
-<p>To set allowed types for {{HTMLElement("object")}}, {{HTMLElement("embed")}}, and
-  {{HTMLElement("applet")}} elements, use the {{CSP("plugin-types")}} directive.</p>
+To set allowed types for {{HTMLElement("object")}}, {{HTMLElement("embed")}}, and
+{{HTMLElement("applet")}} elements, use the {{CSP("plugin-types")}} directive.
 
-<div class="notecard note">
-  <p><strong>Note:</strong> Elements controlled by <code>object-src</code> are perhaps coincidentally
-    considered legacy HTML elements and aren't receiving new standardized features (such as
-    the security attributes <code>sandbox</code> or <code>allow</code> for
-    <code>&lt;iframe&gt;</code>). Therefore it is <a href="https://csp.withgoogle.com/docs/strict-csp.html">recommended</a> to restrict
-    this fetch-directive (e.g. explicitly set <code>object-src 'none'</code> if possible).</p>
-</div>
+> **Note:** Elements controlled by `object-src` are perhaps coincidentally
+> considered legacy HTML elements and aren't receiving new standardized features (such as
+> the security attributes `sandbox` or `allow` for
+> `<iframe>`). Therefore it is [recommended](https://csp.withgoogle.com/docs/strict-csp.html) to restrict
+> this fetch-directive (e.g. explicitly set `object-src 'none'` if possible).
 
 <table class="properties">
   <tbody>
@@ -43,52 +41,56 @@ browser-compat: http.headers.csp.Content-Security-Policy.object-src
     </tr>
     <tr>
       <th scope="row">{{CSP("default-src")}} fallback</th>
-      <td>Yes. If this directive is absent, the user agent will look for the
-        <code>default-src</code> directive.</td>
+      <td>
+        Yes. If this directive is absent, the user agent will look for the
+        <code>default-src</code> directive.
+      </td>
     </tr>
   </tbody>
 </table>
 
-<h2 id="Syntax">Syntax</h2>
+## Syntax
 
-<p>One or more sources can be allowed for the object-src policy:</p>
+One or more sources can be allowed for the object-src policy:
 
-<pre class="brush: html">Content-Security-Policy: object-src &lt;source&gt;;
-Content-Security-Policy: object-src &lt;source&gt; &lt;source&gt;;
-</pre>
+```html
+Content-Security-Policy: object-src <source>;
+Content-Security-Policy: object-src <source> <source>;
+```
 
-<h3 id="Sources">Sources</h3>
+### Sources
 
-<p>{{page("Web/HTTP/Headers/Content-Security-Policy/connect-src", "Sources")}}</p>
+{{page("Web/HTTP/Headers/Content-Security-Policy/connect-src", "Sources")}}
 
-<h2 id="Examples">Examples</h2>
+## Examples
 
-<h3 id="Violation_cases">Violation cases</h3>
+### Violation cases
 
-<p>Given this CSP header:</p>
+Given this CSP header:
 
-<pre class="brush: bash">Content-Security-Policy: object-src https://example.com/</pre>
+```bash
+Content-Security-Policy: object-src https://example.com/
+```
 
-<p>The following {{HTMLElement("object")}}, {{HTMLElement("embed")}}, and
-  {{HTMLElement("applet")}} elements are blocked and won't load:</p>
+The following {{HTMLElement("object")}}, {{HTMLElement("embed")}}, and
+{{HTMLElement("applet")}} elements are blocked and won't load:
 
-<pre class="brush: html">&lt;embed src="https://not-example.com/flash"&gt;&lt;/embed&gt;
-&lt;object data="https://not-example.com/plugin"&gt;&lt;/object&gt;
-&lt;applet archive="https://not-example.com/java"&gt;&lt;/applet&gt;</pre>
+```html
+<embed src="https://not-example.com/flash"></embed>
+<object data="https://not-example.com/plugin"></object>
+<applet archive="https://not-example.com/java"></applet>
+```
 
-<h2 id="Specifications">Specifications</h2>
+## Specifications
 
 {{Specifications}}
 
-<h2 id="Browser_compatibility">Browser compatibility</h2>
+## Browser compatibility
 
-<p>{{Compat}}</p>
+{{Compat}}
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
-  <li>{{HTTPHeader("Content-Security-Policy")}}</li>
-  <li>{{HTMLElement("object")}}, {{HTMLElement("embed")}}, and {{HTMLElement("applet")}}
-  </li>
-  <li>{{CSP("plugin-types")}}</li>
-</ul>
+- {{HTTPHeader("Content-Security-Policy")}}
+- {{HTMLElement("object")}}, {{HTMLElement("embed")}}, and {{HTMLElement("applet")}}
+- {{CSP("plugin-types")}}
diff --git a/files/en-us/web/http/headers/content-security-policy/plugin-types/index.md b/files/en-us/web/http/headers/content-security-policy/plugin-types/index.md
index 445c7128559806b..4d328ca785bc47f 100644
--- a/files/en-us/web/http/headers/content-security-policy/plugin-types/index.md
+++ b/files/en-us/web/http/headers/content-security-policy/plugin-types/index.md
@@ -13,22 +13,19 @@ tags:
   - Security
 browser-compat: http.headers.csp.Content-Security-Policy.plugin-types
 ---
-<div>{{HTTPSidebar}}{{deprecated_header}}</div>
+{{HTTPSidebar}}{{deprecated_header}}
 
-<p>The HTTP {{HTTPHeader("Content-Security-Policy")}} (CSP)
-  <code><strong>plugin-types</strong></code> directive restricts the set of plugins that
-  can be embedded into a document by limiting the types of resources which can be loaded.
-</p>
+The HTTP {{HTTPHeader("Content-Security-Policy")}} (CSP)
+**`plugin-types`** directive restricts the set of plugins that
+can be embedded into a document by limiting the types of resources which can be loaded.
 
-<p>Instantiation of an {{HTMLElement("embed")}}, {{HTMLElement("object")}} or
-  {{HTMLElement("applet")}} element will fail if:</p>
+Instantiation of an {{HTMLElement("embed")}}, {{HTMLElement("object")}} or
+{{HTMLElement("applet")}} element will fail if:
 
-<ul>
-  <li>the element to load does not declare a valid MIME type,</li>
-  <li>the declared type does not match one of specified types in the
-    <code>plugin-types</code> directive,</li>
-  <li>the fetched resource does not match the declared type.</li>
-</ul>
+- the element to load does not declare a valid MIME type,
+- the declared type does not match one of specified types in the
+  `plugin-types` directive,
+- the fetched resource does not match the declared type.
 
 <table class="properties">
   <tbody>
@@ -47,67 +44,67 @@ browser-compat: http.headers.csp.Content-Security-Policy.plugin-types
   </tbody>
 </table>
 
-<h2 id="Syntax">Syntax</h2>
+## Syntax
 
-<p>One or more <a href="/en-US/docs/Web/HTTP/Basics_of_HTTP/MIME_types">MIME types</a> can
-  be set for the <code>plugin-types</code> policy:</p>
+One or more [MIME types](/en-US/docs/Web/HTTP/Basics_of_HTTP/MIME_types) can
+be set for the `plugin-types` policy:
 
-<pre class="brush: html">Content-Security-Policy: plugin-types &lt;type&gt;/&lt;subtype&gt;;
-Content-Security-Policy: plugin-types &lt;type&gt;/&lt;subtype&gt; &lt;type&gt;/&lt;subtype&gt;;
-</pre>
+```html
+Content-Security-Policy: plugin-types <type>/<subtype>;
+Content-Security-Policy: plugin-types <type>/<subtype> <type>/<subtype>;
+```
 
-<dl>
-  <dt>&lt;type&gt;/&lt;subtype&gt;</dt>
-  <dd>A valid <a
-      href="/en-US/docs/Web/HTTP/Basics_of_HTTP/MIME_types/Common_types">MIME
-      type</a>.</dd>
-</dl>
+- \<type>/\<subtype>
+  - : A valid [MIME
+    type](/en-US/docs/Web/HTTP/Basics_of_HTTP/MIME_types/Common_types).
 
-<h2 id="Examples">Examples</h2>
+## Examples
 
-<h3 id="Disallowing_plugins">Disallowing plugins</h3>
+### Disallowing plugins
 
-<p>To disallow all plugins, the {{CSP("object-src")}} directive should be set to
-  <code>'none'</code> which will disallow plugins. The <code>plugin-types</code> directive
-  is only used if you are allowing plugins with <code>object-src</code> at all.</p>
+To disallow all plugins, the {{CSP("object-src")}} directive should be set to
+`'none'` which will disallow plugins. The `plugin-types` directive
+is only used if you are allowing plugins with `object-src` at all.
 
-<pre
-  class="brush: html">&lt;meta http-equiv="Content-Security-Policy" content="object-src 'none'"&gt;</pre>
+```html
+<meta http-equiv="Content-Security-Policy" content="object-src 'none'">
+```
 
-<h3 id="Allowing_Flash_content">Allowing Flash content</h3>
+### Allowing Flash content
 
-<p>The content security policy</p>
+The content security policy
 
-<pre
-  class="brush: bash">Content-Security-Policy: plugin-types application/x-shockwave-flash</pre>
+```bash
+Content-Security-Policy: plugin-types application/x-shockwave-flash
+```
 
-<p>will allow to load flash objects:</p>
+will allow to load flash objects:
 
-<pre
-  class="brush: html">&lt;object data="https://example.com/flash" type="application/x-shockwave-flash"&gt;&lt;/object&gt;</pre>
+```html
+<object data="https://example.com/flash" type="application/x-shockwave-flash"></object>
+```
 
-<h3 id="Allowing_Java_applets">Allowing Java applets</h3>
+### Allowing Java applets
 
-<p>To load an {{HTMLElement("applet")}} you must specify
-  <code>application/x-java-applet</code>:</p>
+To load an {{HTMLElement("applet")}} you must specify
+`application/x-java-applet`:
 
-<pre
-  class="brush: bash">Content-Security-Policy: plugin-types application/x-java-applet</pre>
+```bash
+Content-Security-Policy: plugin-types application/x-java-applet
+```
 
-<h2 id="Specifications">Specifications</h2>
+## Specifications
 
-<p>Not part of any current specification. Used to be defined in <a href="https://www.w3.org/TR/CSP2/#directive-plugin-types">CSP 2</a>.</p>
+Not part of any current specification. Used to be defined in [CSP 2](https://www.w3.org/TR/CSP2/#directive-plugin-types).
 
-<h2 id="Browser_compatibility">Browser compatibility</h2>
+## Browser compatibility
 
-<p>{{Compat}}</p>
+{{Compat}}
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
-  <li>{{HTTPHeader("Content-Security-Policy")}}: {{CSP("object-src")}}</li>
-  <li>{{HTMLElement("object")}}</li>
-  <li>{{HTMLElement("embed")}}</li>
-  <li>{{HTMLElement("applet")}}</li>
-  <li>{{HTTPHeader("X-Content-Type-Options")}}</li>
-</ul>
+- {{HTTPHeader("Content-Security-Policy")}}: {{CSP("object-src")}}
+- {{HTMLElement("object")}}
+- {{HTMLElement("embed")}}
+- {{HTMLElement("applet")}}
+- {{HTTPHeader("X-Content-Type-Options")}}
diff --git a/files/en-us/web/http/headers/content-security-policy/prefetch-src/index.md b/files/en-us/web/http/headers/content-security-policy/prefetch-src/index.md
index 09cb06d88bfe89d..169caec4f284457 100644
--- a/files/en-us/web/http/headers/content-security-policy/prefetch-src/index.md
+++ b/files/en-us/web/http/headers/content-security-policy/prefetch-src/index.md
@@ -2,19 +2,19 @@
 title: 'CSP: prefetch-src'
 slug: Web/HTTP/Headers/Content-Security-Policy/prefetch-src
 tags:
-- CSP
-- Content Security Policy
-- Directive
-- HTTP
-- Reference
-- prefetch-src
+  - CSP
+  - Content Security Policy
+  - Directive
+  - HTTP
+  - Reference
+  - prefetch-src
 browser-compat: http.headers.csp.Content-Security-Policy.prefetch-src
 ---
-<div>{{HTTPSidebar}}</div>
+{{HTTPSidebar}}
 
-<p>The HTTP {{HTTPHeader("Content-Security-Policy")}} (CSP)
-  <code><strong>prefetch-src</strong></code> directive specifies valid resources that may
-  be prefetched or prerendered.</p>
+The HTTP {{HTTPHeader("Content-Security-Policy")}} (CSP)
+**`prefetch-src`** directive specifies valid resources that may
+be prefetched or prerendered.
 
 <table class="properties">
   <tbody>
@@ -28,51 +28,50 @@ browser-compat: http.headers.csp.Content-Security-Policy.prefetch-src
     </tr>
     <tr>
       <th scope="row">{{CSP("default-src")}} fallback</th>
-      <td>Yes. If this directive is absent, the user agent will look for the
-        <code>default-src</code> directive.</td>
+      <td>
+        Yes. If this directive is absent, the user agent will look for the
+        <code>default-src</code> directive.
+      </td>
     </tr>
   </tbody>
 </table>
 
-<h2 id="Syntax">Syntax</h2>
+## Syntax
 
-<p>One or more sources can be allowed for the <code>prefetch-src</code> policy:</p>
+One or more sources can be allowed for the `prefetch-src` policy:
 
-<pre class="brush: html">Content-Security-Policy: prefetch-src &lt;source&gt;;
-Content-Security-Policy: prefetch-src &lt;source&gt; &lt;source&gt;;
-</pre>
+```html
+Content-Security-Policy: prefetch-src <source>;
+Content-Security-Policy: prefetch-src <source> <source>;
+```
 
-<h3 id="Sources">Sources</h3>
+### Sources
 
-<p>{{page("/en-US/docs/Web/HTTP/Headers/Content-Security-Policy/default-src",
-  "common_sources")}}</p>
+{{page("/en-US/docs/Web/HTTP/Headers/Content-Security-Policy/default-src",
+  "common_sources")}}
 
-<h2 id="Example">Example</h2>
+## Example
 
-<h3 id="Prefetch_resources_do_not_match_header">Prefetch resources do not match header
-</h3>
+### Prefetch resources do not match header
 
-<p>Given a page with the following Content Security Policy:</p>
+Given a page with the following Content Security Policy:
 
-<pre>Content-Security-Policy: prefetch-src https://example.com/
-</pre>
+    Content-Security-Policy: prefetch-src https://example.com/
 
-<p>Fetches for the following code will return network errors, as the URLs provided do not
-  match <code>prefetch-src</code>'s source list:</p>
+Fetches for the following code will return network errors, as the URLs provided do not
+match `prefetch-src`'s source list:
 
-<pre>&lt;link rel="prefetch" src="https://example.org/"&gt;&lt;/link&gt;
-&lt;link rel="prerender" src="https://example.org/"&gt;&lt;/link&gt;</pre>
+    <link rel="prefetch" src="https://example.org/"></link>
+    <link rel="prerender" src="https://example.org/"></link>
 
-<h2 id="Specifications">Specifications</h2>
+## Specifications
 
 {{Specifications}}
 
-<h2 id="Browser_compatibility">Browser compatibility</h2>
+## Browser compatibility
 
-<p>{{Compat}}</p>
+{{Compat}}
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
-  <li>{{HTTPHeader("Content-Security-Policy")}}</li>
-</ul>
+- {{HTTPHeader("Content-Security-Policy")}}
diff --git a/files/en-us/web/http/headers/content-security-policy/referrer/index.md b/files/en-us/web/http/headers/content-security-policy/referrer/index.md
index bcb16d5aa7a435c..958d3f6c71c4c43 100644
--- a/files/en-us/web/http/headers/content-security-policy/referrer/index.md
+++ b/files/en-us/web/http/headers/content-security-policy/referrer/index.md
@@ -2,72 +2,67 @@
 title: 'CSP: referrer'
 slug: Web/HTTP/Headers/Content-Security-Policy/referrer
 tags:
-- CSP
-- Content-Security-Policy
-- Directive
-- HTTP
-- Deprecated
-- Reference
-- Security
-- referrer
+  - CSP
+  - Content-Security-Policy
+  - Directive
+  - HTTP
+  - Deprecated
+  - Reference
+  - Security
+  - referrer
 browser-compat: http.headers.csp.Content-Security-Policy.referrer
 ---
-<div>{{HTTPSidebar}} {{deprecated_header}}</div>
+{{HTTPSidebar}} {{deprecated_header}}
 
-<p>The HTTP {{HTTPHeader("Content-Security-Policy")}} (CSP)
-  <code><strong>referrer</strong></code> directive used to specify information in the
-  {{HTTPHeader("Referer")}} header (with a single <code>r</code> as this was a typo in the
-  original spec) for links away from a page. This API is deprecated and removed from
-  browsers.</p>
+The HTTP {{HTTPHeader("Content-Security-Policy")}} (CSP)
+**`referrer`** directive used to specify information in the
+{{HTTPHeader("Referer")}} header (with a single `r` as this was a typo in the
+original spec) for links away from a page. This API is deprecated and removed from
+browsers.
 
-<div class="notecard note">
-  <p><strong>Note:</strong> Use the {{HTTPHeader("Referrer-Policy")}} header instead.</p>
-</div>
+> **Note:** Use the {{HTTPHeader("Referrer-Policy")}} header instead.
 
-<h2 id="Syntax">Syntax</h2>
+## Syntax
 
-<pre
-  class="brush: html">Content-Security-Policy: referrer &lt;referrer-policy&gt;;</pre>
+```html
+Content-Security-Policy: referrer <referrer-policy>;
+```
 
-<p>where <code>&lt;referrer-policy&gt;</code> can be one of the following values:</p>
+where `<referrer-policy>` can be one of the following values:
 
-<dl>
-  <dt>"no-referrer"</dt>
-  <dd>The {{HTTPHeader("Referer")}} header will be omitted entirely. No referrer
-    information is sent along with requests.</dd>
-  <dt>"none-when-downgrade"</dt>
-  <dd>This is the user agent's default behavior if no policy is specified. The origin is
-    sent as referrer to a-priori as-much-secure destination (HTTPS-&gt;HTTPS), but isn't
-    sent to a less secure destination (HTTPS-&gt;HTTP).</dd>
-  <dt>"origin"</dt>
-  <dd>Only send the origin of the document as the referrer in all cases.<br>
-    The document <code>https://example.com/page.html</code> will send the referrer
-    <code>https://example.com/</code>.</dd>
-  <dt>"origin-when-cross-origin" / "origin-when-crossorigin"</dt>
-  <dd>Send a full URL when performing a same-origin request, but only send the origin of
-    the document for other cases.</dd>
-  <dt>"unsafe-url"</dt>
-  <dd>Send a full URL (stripped from parameters) when performing a same-origin or
+- "no-referrer"
+  - : The {{HTTPHeader("Referer")}} header will be omitted entirely. No referrer
+    information is sent along with requests.
+- "none-when-downgrade"
+  - : This is the user agent's default behavior if no policy is specified. The origin is
+    sent as referrer to a-priori as-much-secure destination (HTTPS->HTTPS), but isn't
+    sent to a less secure destination (HTTPS->HTTP).
+- "origin"
+  - : Only send the origin of the document as the referrer in all cases.
+    The document `https://example.com/page.html` will send the referrer
+    `https://example.com/`.
+- "origin-when-cross-origin" / "origin-when-crossorigin"
+  - : Send a full URL when performing a same-origin request, but only send the origin of
+    the document for other cases.
+- "unsafe-url"
+  - : Send a full URL (stripped from parameters) when performing a same-origin or
     cross-origin request. This policy will leak origins and paths from TLS-protected
-    resources to insecure origins. Carefully consider the impact of this setting.</dd>
-</dl>
+    resources to insecure origins. Carefully consider the impact of this setting.
 
-<h2 id="Examples">Examples</h2>
+## Examples
 
-<pre>Content-Security-Policy: referrer "none";</pre>
+    Content-Security-Policy: referrer "none";
 
-<h2 id="Specifications">Specifications</h2>
+## Specifications
 
-<p>Not part of any specification.</p>
+Not part of any specification.
 
-<h2 id="Browser_compatibility">Browser compatibility</h2>
+## Browser compatibility
 
-<p>{{Compat}}</p>
+{{Compat}}
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
-  <li>{{HTTPHeader("Content-Security-Policy")}}</li>
-  <li>{{HTTPHeader("Referrer-Policy")}} header</li>
-  <li>{{HTTPHeader("Referer")}} header</li>
-</ul>
+- {{HTTPHeader("Content-Security-Policy")}}
+- {{HTTPHeader("Referrer-Policy")}} header
+- {{HTTPHeader("Referer")}} header
diff --git a/files/en-us/web/http/headers/content-security-policy/report-to/index.md b/files/en-us/web/http/headers/content-security-policy/report-to/index.md
index f6617c91f209101..0ca89bb60707529 100644
--- a/files/en-us/web/http/headers/content-security-policy/report-to/index.md
+++ b/files/en-us/web/http/headers/content-security-policy/report-to/index.md
@@ -2,26 +2,27 @@
 title: 'CSP: report-to'
 slug: Web/HTTP/Headers/Content-Security-Policy/report-to
 tags:
-- CSP
-- Content Security Policy
-- Content-Security-Policy
-- HTTP
-- Reporting
-- Security
-- report-to
+  - CSP
+  - Content Security Policy
+  - Content-Security-Policy
+  - HTTP
+  - Reporting
+  - Security
+  - report-to
 browser-compat: http.headers.csp.Content-Security-Policy.report-to
 ---
-<div>{{HTTPSidebar}}</div>
+{{HTTPSidebar}}
 
-<p>The <code>Content-Security-Policy</code>
-    <strong><dfn><code>Report-To</code></dfn></strong> HTTP response header field
-    instructs the user agent to store reporting endpoints for an origin.</p>
+The `Content-Security-Policy`
+**_`Report-To`_** HTTP response header field
+instructs the user agent to store reporting endpoints for an origin.
 
-<pre class="brush: html">Content-Security-Policy: ...; report-to groupname
-</pre>
+```html
+Content-Security-Policy: ...; report-to groupname
+```
 
-<p>The directive has no effect in and of itself, but only gains meaning in combination
-  with other directives.</p>
+The directive has no effect in and of itself, but only gains meaning in combination
+with other directives.
 
 <table class="properties">
   <tbody>
@@ -34,54 +35,55 @@ browser-compat: http.headers.csp.Content-Security-Policy.report-to
       <td>{{Glossary("Reporting directive")}}</td>
     </tr>
     <tr>
-      <th colspan="2" scope="row">This directive is not supported in the
-        {{HTMLElement("meta")}} element.</th>
+      <th colspan="2" scope="row">
+        This directive is not supported in the {{HTMLElement("meta")}}
+        element.
+      </th>
     </tr>
   </tbody>
 </table>
 
-<h2 id="Syntax">Syntax</h2>
+## Syntax
 
-<pre>Content-Security-Policy: report-to &lt;json-field-value&gt;;</pre>
+    Content-Security-Policy: report-to <json-field-value>;
 
-<h2 id="Examples">Examples</h2>
+## Examples
 
-<p>See {{HTTPHeader("Content-Security-Policy-Report-Only")}} for more information and
-  examples.</p>
+See {{HTTPHeader("Content-Security-Policy-Report-Only")}} for more information and
+examples.
 
-<pre><a href="https://wicg.github.io/reporting/#report-to" id="ref-for-report-to①">Report-To</a>: { "<a href="https://wicg.github.io/reporting/#group" id="ref-for-group①">group</a>": "csp-endpoint",
-             "<a href="https://wicg.github.io/reporting/#max-age" id="ref-for-max-age①">max_age</a>": 10886400,
-             "<a href="https://wicg.github.io/reporting/#endpoints" id="ref-for-endpoints②">endpoints</a>": [
-               { "<a href="https://wicg.github.io/reporting/#url" id="ref-for-url②">url</a>": "https://example.com/csp-reports" }
-             ] },
-           { "<a href="https://wicg.github.io/reporting/#group" id="ref-for-group②">group</a>": "hpkp-endpoint",
-             "<a href="https://wicg.github.io/reporting/#max-age" id="ref-for-max-age②">max_age</a>": 10886400,
-             "<a href="https://wicg.github.io/reporting/#endpoints" id="ref-for-endpoints③">endpoints</a>": [
-               { "<a href="https://wicg.github.io/reporting/#url" id="ref-for-url③">url</a>": "https://example.com/hpkp-reports" }
-             ] }
-<a href="https://w3c.github.io/webappsec-csp/#content-security-policy" id="ref-for-content-security-policy①">Content-Security-Policy</a>: ...; <a href="https://w3c.github.io/webappsec-csp/#directives-reporting" id="ref-for-directives-reporting①">report-to</a> csp-endpoint
-</pre>
+    Report-To: { "group": "csp-endpoint",
+                 "max_age": 10886400,
+                 "endpoints": [
+                   { "url": "https://example.com/csp-reports" }
+                 ] },
+               { "group": "hpkp-endpoint",
+                 "max_age": 10886400,
+                 "endpoints": [
+                   { "url": "https://example.com/hpkp-reports" }
+                 ] }
+    Content-Security-Policy: ...; report-to csp-endpoint
 
-<pre><a href="https://wicg.github.io/reporting/#report-to" id="ref-for-report-to">Report-To</a>: { "<a href="https://wicg.github.io/reporting/#group" id="ref-for-group">group</a>": "endpoint-1",
-             "<a href="https://wicg.github.io/reporting/#max-age" id="ref-for-max-age">max_age</a>": 10886400,
-             "<a href="https://wicg.github.io/reporting/#endpoints" id="ref-for-endpoints①">endpoints</a>": [
-               { "<a href="https://wicg.github.io/reporting/#url" id="ref-for-url">url</a>": "https://example.com/reports" },
-               { "<a href="https://wicg.github.io/reporting/#url" id="ref-for-url①">url</a>": "https://backup.com/reports" }
-             ] }
+<!---->
 
-<a href="https://w3c.github.io/webappsec-csp/#content-security-policy" id="ref-for-content-security-policy">Content-Security-Policy</a>: ...; <a href="https://w3c.github.io/webappsec-csp/#directives-reporting" id="ref-for-directives-reporting">report-to</a> endpoint-1</pre>
+    Report-To: { "group": "endpoint-1",
+                 "max_age": 10886400,
+                 "endpoints": [
+                   { "url": "https://example.com/reports" },
+                   { "url": "https://backup.com/reports" }
+                 ] }
 
-<h2 id="Specifications">Specifications</h2>
+    Content-Security-Policy: ...; report-to endpoint-1
+
+## Specifications
 
 {{Specifications}}
 
-<h2 id="Browser_compatibility">Browser compatibility</h2>
+## Browser compatibility
 
-<p>{{Compat}}</p>
+{{Compat}}
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
-  <li>{{HTTPHeader("Content-Security-Policy")}}</li>
-  <li>{{HTTPHeader("Content-Security-Policy-Report-Only")}}</li>
-</ul>
+- {{HTTPHeader("Content-Security-Policy")}}
+- {{HTTPHeader("Content-Security-Policy-Report-Only")}}
diff --git a/files/en-us/web/http/headers/content-security-policy/report-uri/index.md b/files/en-us/web/http/headers/content-security-policy/report-uri/index.md
index 644f8605447beb7..2b24117da4d3891 100644
--- a/files/en-us/web/http/headers/content-security-policy/report-uri/index.md
+++ b/files/en-us/web/http/headers/content-security-policy/report-uri/index.md
@@ -2,39 +2,35 @@
 title: 'CSP: report-uri'
 slug: Web/HTTP/Headers/Content-Security-Policy/report-uri
 tags:
-- CSP
-- Directive
-- HTTP
-- Reference
-- Security
+  - CSP
+  - Directive
+  - HTTP
+  - Reference
+  - Security
 browser-compat: http.headers.csp.Content-Security-Policy.report-uri
 ---
-<div>{{HTTPSidebar}}{{deprecated_header}}</div>
-
-<p>The deprecated HTTP {{HTTPHeader("Content-Security-Policy")}} (CSP)
-  <code><strong>report-uri</strong></code> directive instructs the user agent to report
-  attempts to violate the Content Security Policy. These violation reports consist of JSON
-  documents sent via an HTTP POST request to the specified URI.</p>
-
-<div class="notecard warning">
-  <p>
-    <strong>Warning:</strong> Though the {{CSP("report-to")}} directive is intended to replace the deprecated <code><strong>report-uri</strong></code> directive,
-    {{CSP("report-to")}} isn't supported in most browsers yet.
-    So for compatibility with current browsers
-    while also adding forward compatibility when browsers get {{CSP("report-to")}} support,
-    you can specify both <code><strong>report-uri</strong></code> and {{CSP("report-to")}}:
-  </p>
-
-  <pre class="brush: html">Content-Security-Policy: ...; report-uri https://endpoint.com; report-to groupname</pre>
-
-  <p>
-    In browsers that support {{CSP("report-to")}},
-    the <code><strong>report-uri</strong></code> directive will be ignored.
-  </p>
-</div>
-
-<p>The directive has no effect in and of itself, but only gains meaning in combination
-  with other directives.</p>
+{{HTTPSidebar}}{{deprecated_header}}
+
+The deprecated HTTP {{HTTPHeader("Content-Security-Policy")}} (CSP)
+**`report-uri`** directive instructs the user agent to report
+attempts to violate the Content Security Policy. These violation reports consist of JSON
+documents sent via an HTTP POST request to the specified URI.
+
+> **Warning:** Though the {{CSP("report-to")}} directive is intended to replace the deprecated **`report-uri`** directive,
+> {{CSP("report-to")}} isn't supported in most browsers yet.
+> So for compatibility with current browsers
+> while also adding forward compatibility when browsers get {{CSP("report-to")}} support,
+> you can specify both **`report-uri`** and {{CSP("report-to")}}:
+>
+> ```html
+> Content-Security-Policy: ...; report-uri https://endpoint.com; report-to groupname
+> ```
+>
+> In browsers that support {{CSP("report-to")}},
+> the **`report-uri`** directive will be ignored.
+
+The directive has no effect in and of itself, but only gains meaning in combination
+with other directives.
 
 <table class="properties">
   <tbody>
@@ -47,83 +43,81 @@ browser-compat: http.headers.csp.Content-Security-Policy.report-uri
       <td>{{Glossary("Reporting directive")}}</td>
     </tr>
     <tr>
-      <th colspan="2" scope="row">This directive is not supported in the
-        {{HTMLElement("meta")}} element.</th>
+      <th colspan="2" scope="row">
+        This directive is not supported in the {{HTMLElement("meta")}}
+        element.
+      </th>
     </tr>
   </tbody>
 </table>
 
-<h2 id="Syntax">Syntax</h2>
-
-<pre class="brush: html">Content-Security-Policy: report-uri &lt;uri&gt;;
-Content-Security-Policy: report-uri &lt;uri&gt; &lt;uri&gt;;</pre>
+## Syntax
 
-<dl>
-  <dt>&lt;uri&gt;</dt>
-  <dd>A URI where to POST the report to.</dd>
-</dl>
+```html
+Content-Security-Policy: report-uri <uri>;
+Content-Security-Policy: report-uri <uri> <uri>;
+```
 
-<h2 id="Examples">Examples</h2>
+- \<uri>
+  - : A URI where to POST the report to.
 
-<p>See {{HTTPHeader("Content-Security-Policy-Report-Only")}} for more information and
-  examples.</p>
+## Examples
 
-<pre>Content-Security-Policy: default-src https:; report-uri /csp-violation-report-endpoint/</pre>
+See {{HTTPHeader("Content-Security-Policy-Report-Only")}} for more information and
+examples.
 
-<p><code>/csp-violation-report-endpoint/</code> could for example run a PHP something like
-  the following that logs the JSON detailing the violation and, if the violation is the
-  first one added to the log file, sends an email to an administrator:</p>
+    Content-Security-Policy: default-src https:; report-uri /csp-violation-report-endpoint/
 
-<pre>&lt;?php
+`/csp-violation-report-endpoint/` could for example run a PHP something like
+the following that logs the JSON detailing the violation and, if the violation is the
+first one added to the log file, sends an email to an administrator:
 
-// Start configure
-$log_file = dirname(__FILE__) . '/csp-violations.log';
-$log_file_size_limit = 1000000; // bytes - once exceeded no further entries are added
-$email_address = 'admin@example.com';
-$email_subject = 'Content-Security-Policy violation';
-// End configuration
+    <?php
 
-$current_domain = preg_replace('/www\./i', '', $_SERVER['SERVER_NAME']);
-$email_subject = $email_subject . ' on ' . $current_domain;
+    // Start configure
+    $log_file = dirname(__FILE__) . '/csp-violations.log';
+    $log_file_size_limit = 1000000; // bytes - once exceeded no further entries are added
+    $email_address = 'admin@example.com';
+    $email_subject = 'Content-Security-Policy violation';
+    // End configuration
 
-http_response_code(204); // HTTP 204 No Content
+    $current_domain = preg_replace('/www\./i', '', $_SERVER['SERVER_NAME']);
+    $email_subject = $email_subject . ' on ' . $current_domain;
 
-$json_data = file_get_contents('php://input');
+    http_response_code(204); // HTTP 204 No Content
 
-// We pretty print the JSON before adding it to the log file
-if ($json_data = json_decode($json_data)) {
-  $json_data = json_encode($json_data, JSON_PRETTY_PRINT | JSON_UNESCAPED_SLASHES);
+    $json_data = file_get_contents('php://input');
 
-  if (!file_exists($log_file)) {
-    // Send an email
-    $message = "The following Content-Security-Policy violation occurred on " .
-      $current_domain . ":\n\n" .
-      $json_data .
-      "\n\nFurther CPS violations will be logged to the following log file, but no further email notifications will be sent until this log file is deleted:\n\n" .
-      $log_file;
-    mail($email_address, $email_subject, $message,
-         'Content-Type: text/plain;charset=utf-8');
-  } else if (filesize($log_file) &gt; $log_file_size_limit) {
-    exit(0);
-  }
+    // We pretty print the JSON before adding it to the log file
+    if ($json_data = json_decode($json_data)) {
+      $json_data = json_encode($json_data, JSON_PRETTY_PRINT | JSON_UNESCAPED_SLASHES);
 
-  file_put_contents($log_file, $json_data, FILE_APPEND | LOCK_EX);
-}
+      if (!file_exists($log_file)) {
+        // Send an email
+        $message = "The following Content-Security-Policy violation occurred on " .
+          $current_domain . ":\n\n" .
+          $json_data .
+          "\n\nFurther CPS violations will be logged to the following log file, but no further email notifications will be sent until this log file is deleted:\n\n" .
+          $log_file;
+        mail($email_address, $email_subject, $message,
+             'Content-Type: text/plain;charset=utf-8');
+      } else if (filesize($log_file) > $log_file_size_limit) {
+        exit(0);
+      }
 
-</pre>
+      file_put_contents($log_file, $json_data, FILE_APPEND | LOCK_EX);
+    }
 
-<h2 id="Specifications">Specifications</h2>
+## Specifications
 
 {{Specifications}}
 
-<h2 id="Browser_compatibility">Browser compatibility</h2>
+## Browser compatibility
 
-<p>{{Compat}}</p>
+{{Compat}}
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
-  <li>{{HTTPHeader("Content-Security-Policy")}}</li>
-  <li>{{HTTPHeader("Content-Security-Policy-Report-Only")}}</li>
-  <li>{{CSP("report-to")}}</li>
-</ul>
+- {{HTTPHeader("Content-Security-Policy")}}
+- {{HTTPHeader("Content-Security-Policy-Report-Only")}}
+- {{CSP("report-to")}}
diff --git a/files/en-us/web/http/headers/content-security-policy/require-sri-for/index.md b/files/en-us/web/http/headers/content-security-policy/require-sri-for/index.md
index 5e51e229e22127f..b2f66e5cee77b22 100644
--- a/files/en-us/web/http/headers/content-security-policy/require-sri-for/index.md
+++ b/files/en-us/web/http/headers/content-security-policy/require-sri-for/index.md
@@ -2,64 +2,63 @@
 title: 'CSP: require-sri-for'
 slug: Web/HTTP/Headers/Content-Security-Policy/require-sri-for
 tags:
-- CSP
-- Directive
-- HTTP
-- Reference
-- Security
-- Subresource Integrity
-- require-sri-for
+  - CSP
+  - Directive
+  - HTTP
+  - Reference
+  - Security
+  - Subresource Integrity
+  - require-sri-for
 browser-compat: http.headers.csp.Content-Security-Policy.require-sri-for
 ---
-<div>{{deprecated_header}}</div>
+{{deprecated_header}}
 
-<p>The <a href="/en-US/docs/Web/HTTP">HTTP</a> {{HTTPHeader("Content-Security-Policy")}}
-  <code><strong>require-sri-for</strong></code> directive instructs the client to require
-  the use of <a href="/en-US/docs/Web/Security/Subresource_Integrity">Subresource
-    Integrity</a> for scripts or styles on the page.</p>
+The [HTTP](/en-US/docs/Web/HTTP) {{HTTPHeader("Content-Security-Policy")}}
+**`require-sri-for`** directive instructs the client to require
+the use of [Subresource
+Integrity](/en-US/docs/Web/Security/Subresource_Integrity) for scripts or styles on the page.
 
-<h2 id="Syntax">Syntax</h2>
+## Syntax
 
-<pre class="brush: html">Content-Security-Policy: require-sri-for script;
+```html
+Content-Security-Policy: require-sri-for script;
 Content-Security-Policy: require-sri-for style;
 Content-Security-Policy: require-sri-for script style;
-</pre>
+```
 
-<dl>
-  <dt><code>script</code></dt>
-  <dd>Requires {{Glossary("SRI")}} for scripts.</dd>
-  <dt><code>style</code></dt>
-  <dd>Requires {{Glossary("SRI")}} for style sheets.</dd>
-  <dt><code>script style</code></dt>
-  <dd>Requires {{Glossary("SRI")}} for both, scripts and style sheets.</dd>
-</dl>
+- `script`
+  - : Requires {{Glossary("SRI")}} for scripts.
+- `style`
+  - : Requires {{Glossary("SRI")}} for style sheets.
+- `script style`
+  - : Requires {{Glossary("SRI")}} for both, scripts and style sheets.
 
-<h2 id="Examples">Examples</h2>
+## Examples
 
-<p>If you set your site to require SRI for script and styles using this directive:</p>
+If you set your site to require SRI for script and styles using this directive:
 
-<pre>Content-Security-Policy: require-sri-for script style</pre>
+    Content-Security-Policy: require-sri-for script style
 
-<p>{{HTMLElement("script")}} elements like the following will be loaded as they use a
-  valid integrity attribute.</p>
+{{HTMLElement("script")}} elements like the following will be loaded as they use a
+valid integrity attribute.
 
-<pre class="brush: html; example-good">&lt;script src="https://code.jquery.com/jquery-3.1.1.slim.js"
+```html example-good
+<script src="https://code.jquery.com/jquery-3.1.1.slim.js"
         integrity="sha256-5i/mQ300M779N2OVDrl16lbohwXNUdzL/R2aVUXyXWA="
-        crossorigin="anonymous"&gt;&lt;/script&gt;</pre>
+        crossorigin="anonymous"></script>
+```
 
-<p>However, scripts without integrity won't load anymore:</p>
+However, scripts without integrity won't load anymore:
 
-<pre
-  class="brush: html; example-bad">&lt;script src="https://code.jquery.com/jquery-3.1.1.slim.js"&gt;&lt;/script&gt;</pre>
+```html example-bad
+<script src="https://code.jquery.com/jquery-3.1.1.slim.js"></script>
+```
 
-<h2 id="Browser_compatibility">Browser compatibility</h2>
+## Browser compatibility
 
-<p>{{Compat}}</p>
+{{Compat}}
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
-  <li>{{HTTPHeader("Content-Security-Policy")}}</li>
-  <li><a href="/en-US/docs/Web/Security/Subresource_Integrity">Subresource Integrity</a>
-  </li>
-</ul>
+- {{HTTPHeader("Content-Security-Policy")}}
+- [Subresource Integrity](/en-US/docs/Web/Security/Subresource_Integrity)
diff --git a/files/en-us/web/http/headers/content-security-policy/require-trusted-types-for/index.md b/files/en-us/web/http/headers/content-security-policy/require-trusted-types-for/index.md
index 3e350a61448ddf8..e9cc53a5dfaa6a1 100644
--- a/files/en-us/web/http/headers/content-security-policy/require-trusted-types-for/index.md
+++ b/files/en-us/web/http/headers/content-security-policy/require-trusted-types-for/index.md
@@ -8,59 +8,55 @@ tags:
   - Security
 browser-compat: http.headers.csp.Content-Security-Policy.require-trusted-types-for
 ---
-<div>{{HTTPSidebar}}</div>
+{{HTTPSidebar}}
 
-<p>The HTTP {{HTTPHeader("Content-Security-Policy")}} (CSP) <code><strong>require-trusted-types-for</strong></code> {{experimental_inline}} directive instructs user agents to control the data passed to DOM XSS sink functions, like {{DOMxRef("Element.innerHTML")}} setter.</p>
+The HTTP {{HTTPHeader("Content-Security-Policy")}} (CSP) **`require-trusted-types-for`** {{experimental_inline}} directive instructs user agents to control the data passed to DOM XSS sink functions, like {{DOMxRef("Element.innerHTML")}} setter.
 
-<p>When used, those functions only accept non-spoofable, typed values created by Trusted Type policies, and reject strings. Together with <strong><code><a href="/en-US/docs/Web/HTTP/Headers/Content-Security-Policy/trusted-types">trusted-types</a></code></strong> directive, which guards creation of Trusted Type policies, this allows authors to define rules guarding writing values to the DOM and thus reducing the DOM XSS attack surface to small, isolated parts of the web application codebase, facilitating their monitoring and code review.</p>
+When used, those functions only accept non-spoofable, typed values created by Trusted Type policies, and reject strings. Together with **[`trusted-types`](/en-US/docs/Web/HTTP/Headers/Content-Security-Policy/trusted-types)** directive, which guards creation of Trusted Type policies, this allows authors to define rules guarding writing values to the DOM and thus reducing the DOM XSS attack surface to small, isolated parts of the web application codebase, facilitating their monitoring and code review.
 
-<h2 id="Syntax">Syntax</h2>
+## Syntax
 
-<pre>Content-Security-Policy: require-trusted-types-for 'script';
-</pre>
+    Content-Security-Policy: require-trusted-types-for 'script';
 
-<dl>
- <dt><code>'script'</code></dt>
- <dd>Disallows using strings with DOM XSS injection sink functions, and requires matching types created by Trusted Type policies.</dd>
-</dl>
+- `'script'`
+  - : Disallows using strings with DOM XSS injection sink functions, and requires matching types created by Trusted Type policies.
 
-<h2 id="Examples">Examples</h2>
+## Examples
 
-<pre class="brush: js">// Content-Security-Policy: require-trusted-types-for 'script'; trusted-types foo;
+```js
+// Content-Security-Policy: require-trusted-types-for 'script'; trusted-types foo;
 
-const attackerInput = '&lt;svg onload="alert(/cross-site-scripting/)" /&gt;';
+const attackerInput = '<svg onload="alert(/cross-site-scripting/)" />';
 const el = document.createElement('div');
 
 if (typeof trustedTypes !== 'undefined') {
   // Create a policy that can create TrustedHTML values
   // after sanitizing the input strings with DOMPurify library.
   const sanitizer = trustedTypes.createPolicy('foo', {
-    createHTML: (input) =&gt; DOMPurify.sanitize(input)
+    createHTML: (input) => DOMPurify.sanitize(input)
   });
 
   el.innerHTML = sanitizer.createHTML(attackerInput);  // Puts the sanitized value into the DOM.
   el.innerHTML = attackerInput;                        // Rejects a string value; throws a TypeError.
 }
-</pre>
+```
 
-<h2 id="Polyfill">Polyfill</h2>
+## Polyfill
 
-<p>A <a href="https://github.com/w3c/webappsec-trusted-types#polyfill">polyfill for Trusted Types</a> is available on Github.</p>
+A [polyfill for Trusted Types](https://github.com/w3c/webappsec-trusted-types#polyfill) is available on Github.
 
-<h2 id="Specifications">Specifications</h2>
+## Specifications
 
 {{Specifications}}
 
-<h2 id="Browser_compatibility">Browser compatibility</h2>
+## Browser compatibility
 
-<p>{{Compat}}</p>
+{{Compat}}
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
- <li>{{HTTPHeader("Content-Security-Policy")}}</li>
- <li><a href="/en-US/docs/Glossary/Cross-site_scripting">Cross-Site Scripting (XSS)</a></li>
- <li><a href="https://w3c.github.io/webappsec-trusted-types/dist/spec/#injection-sinks">DOM XSS injection sinks covered by Trusted Types</a></li>
- <li><a href="https://web.dev/trusted-types">Prevent DOM-based cross-site scripting vulnerabilities with Trusted Types</a></li>
- <li>Trusted Types with <a href="https://github.com/cure53/DOMPurify#what-about-dompurify-and-trusted-types">DOMPurify</a> XSS sanitizer</li>
-</ul>
+- {{HTTPHeader("Content-Security-Policy")}}
+- [Cross-Site Scripting (XSS)](/en-US/docs/Glossary/Cross-site_scripting)
+- [DOM XSS injection sinks covered by Trusted Types](https://w3c.github.io/webappsec-trusted-types/dist/spec/#injection-sinks)
+- [Prevent DOM-based cross-site scripting vulnerabilities with Trusted Types](https://web.dev/trusted-types)
+- Trusted Types with [DOMPurify](https://github.com/cure53/DOMPurify#what-about-dompurify-and-trusted-types) XSS sanitizer
diff --git a/files/en-us/web/http/headers/content-security-policy/sandbox/index.md b/files/en-us/web/http/headers/content-security-policy/sandbox/index.md
index 1b2555e75e35525..e7a303e80ccfc1c 100644
--- a/files/en-us/web/http/headers/content-security-policy/sandbox/index.md
+++ b/files/en-us/web/http/headers/content-security-policy/sandbox/index.md
@@ -10,13 +10,13 @@ tags:
   - Security
 browser-compat: http.headers.csp.Content-Security-Policy.sandbox
 ---
-<div>{{HTTPSidebar}}</div>
+{{HTTPSidebar}}
 
-<p>The HTTP {{HTTPHeader("Content-Security-Policy")}} (CSP)
-  <code><strong>sandbox</strong></code> directive enables a sandbox for the requested
-  resource similar to the {{HTMLElement("iframe")}} {{htmlattrxref("sandbox", "iframe")}}
-  attribute. It applies restrictions to a page's actions including preventing popups,
-  preventing the execution of plugins and scripts, and enforcing a same-origin policy.</p>
+The HTTP {{HTTPHeader("Content-Security-Policy")}} (CSP)
+**`sandbox`** directive enables a sandbox for the requested
+resource similar to the {{HTMLElement("iframe")}} {{htmlattrxref("sandbox", "iframe")}}
+attribute. It applies restrictions to a page's actions including preventing popups,
+preventing the execution of plugins and scripts, and enforcing a same-origin policy.
 
 <table class="properties">
   <tbody>
@@ -29,80 +29,81 @@ browser-compat: http.headers.csp.Content-Security-Policy.sandbox
       <td>{{Glossary("Document directive")}}</td>
     </tr>
     <tr>
-      <th colspan="2" scope="row">This directive is not supported in the
-        {{HTMLElement("meta")}} element or by the
-        {{HTTPHeader("Content-Security-policy-Report-Only")}} header field.</th>
+      <th colspan="2" scope="row">
+        This directive is not supported in the {{HTMLElement("meta")}}
+        element or by the
+        {{HTTPHeader("Content-Security-policy-Report-Only")}}
+        header field.
+      </th>
     </tr>
   </tbody>
 </table>
 
-<h2 id="Syntax">Syntax</h2>
+## Syntax
 
-<pre class="brush: html">Content-Security-Policy: sandbox;
-Content-Security-Policy: sandbox &lt;value&gt;;
-</pre>
+```html
+Content-Security-Policy: sandbox;
+Content-Security-Policy: sandbox <value>;
+```
 
-<p>where <code>&lt;value&gt;</code> can optionally be one of the following values:</p>
+where `<value>` can optionally be one of the following values:
 
-<dl>
-  <dt><code>allow-downloads</code></dt>
-  <dd>Allows for downloads after the user clicks a button or link.</dd>
-  <dt><code>allow-downloads-without-user-activation</code> {{experimental_inline}}</dt>
-  <dd>Allows for downloads to occur without a gesture from the user.</dd>
-  <dt><code>allow-forms</code></dt>
-  <dd>Allows the page to submit forms. If this keyword is not used, this operation is not
-    allowed.</dd>
-  <dt><code>allow-modals</code></dt>
-  <dd>Allows the page to open modal windows.</dd>
-  <dt><code>allow-orientation-lock</code></dt>
-  <dd>Allows the page to disable the ability to lock the screen orientation.</dd>
-  <dt><code>allow-pointer-lock</code></dt>
-  <dd>Allows the page to use the <a href="/en-US/docs/Web/API/Pointer_Lock_API">Pointer Lock
-      API</a>.</dd>
-  <dt><code>allow-popups</code></dt>
-  <dd>Allows popups (like from <code>window.open</code>, <code>target="_blank"</code>,
-    <code>showModalDialog</code>). If this keyword is not used, that functionality will
-    silently fail.</dd>
-  <dt><code>allow-popups-to-escape-sandbox</code></dt>
-  <dd>Allows a sandboxed document to open new windows without forcing the sandboxing flags
+- `allow-downloads`
+  - : Allows for downloads after the user clicks a button or link.
+- `allow-downloads-without-user-activation` {{experimental_inline}}
+  - : Allows for downloads to occur without a gesture from the user.
+- `allow-forms`
+  - : Allows the page to submit forms. If this keyword is not used, this operation is not
+    allowed.
+- `allow-modals`
+  - : Allows the page to open modal windows.
+- `allow-orientation-lock`
+  - : Allows the page to disable the ability to lock the screen orientation.
+- `allow-pointer-lock`
+  - : Allows the page to use the [Pointer Lock
+    API](/en-US/docs/Web/API/Pointer_Lock_API).
+- `allow-popups`
+  - : Allows popups (like from `window.open`, `target="_blank"`,
+    `showModalDialog`). If this keyword is not used, that functionality will
+    silently fail.
+- `allow-popups-to-escape-sandbox`
+  - : Allows a sandboxed document to open new windows without forcing the sandboxing flags
     upon them. This will allow, for example, a third-party advertisement to be safely
-    sandboxed without forcing the same restrictions upon a landing page.</dd>
-  <dt><code>allow-presentation</code></dt>
-  <dd>Allows embedders to have control over whether an iframe can start a presentation
-    session.</dd>
-  <dt><code>allow-same-origin</code></dt>
-  <dd>Allows the content to be treated as being from its normal origin. If this keyword is
-    not used, the embedded content is treated as being from a unique origin.</dd>
-  <dt><code>allow-scripts</code></dt>
-  <dd>Allows the page to run scripts (but not create pop-up windows). If this keyword is
-    not used, this operation is not allowed.</dd>
-  <dt><code>allow-storage-access-by-user-activation</code> {{experimental_inline}}</dt>
-  <dd>Lets the resource request access to the parent's storage capabilities with the <a
-      href="/en-US/docs/Web/API/Storage_Access_API">Storage Access API</a>.</dd>
-  <dt><code>allow-top-navigation</code></dt>
-  <dd>Allows the page to navigate (load) content to the top-level browsing context. If
-    this keyword is not used, this operation is not allowed.</dd>
-  <dt><code>allow-top-navigation-by-user-activation</code></dt>
-  <dd>Lets the resource navigate the top-level browsing context, but only if initiated by
-    a user gesture.</dd>
-</dl>
+    sandboxed without forcing the same restrictions upon a landing page.
+- `allow-presentation`
+  - : Allows embedders to have control over whether an iframe can start a presentation
+    session.
+- `allow-same-origin`
+  - : Allows the content to be treated as being from its normal origin. If this keyword is
+    not used, the embedded content is treated as being from a unique origin.
+- `allow-scripts`
+  - : Allows the page to run scripts (but not create pop-up windows). If this keyword is
+    not used, this operation is not allowed.
+- `allow-storage-access-by-user-activation` {{experimental_inline}}
+  - : Lets the resource request access to the parent's storage capabilities with the [Storage Access API](/en-US/docs/Web/API/Storage_Access_API).
+- `allow-top-navigation`
+  - : Allows the page to navigate (load) content to the top-level browsing context. If
+    this keyword is not used, this operation is not allowed.
+- `allow-top-navigation-by-user-activation`
+  - : Lets the resource navigate the top-level browsing context, but only if initiated by
+    a user gesture.
 
-<h2 id="Examples">Examples</h2>
+## Examples
 
-<pre class="brush: bash">Content-Security-Policy: sandbox allow-scripts;</pre>
+```bash
+Content-Security-Policy: sandbox allow-scripts;
+```
 
-<h2 id="Specifications">Specifications</h2>
+## Specifications
 
 {{Specifications}}
 
-<h2 id="Browser_compatibility">Browser compatibility</h2>
+## Browser compatibility
 
-<p>{{Compat}}</p>
+{{Compat}}
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
-  <li>{{HTTPHeader("Content-Security-Policy")}}</li>
-  <li>{{htmlattrxref("sandbox", "iframe")}} attribute on {{HTMLElement("iframe")}}
-    elements</li>
-</ul>
+- {{HTTPHeader("Content-Security-Policy")}}
+- {{htmlattrxref("sandbox", "iframe")}} attribute on {{HTMLElement("iframe")}}
+  elements
diff --git a/files/en-us/web/http/headers/content-security-policy/script-src-attr/index.md b/files/en-us/web/http/headers/content-security-policy/script-src-attr/index.md
index e42573072747e06..3ef35bcf560703a 100644
--- a/files/en-us/web/http/headers/content-security-policy/script-src-attr/index.md
+++ b/files/en-us/web/http/headers/content-security-policy/script-src-attr/index.md
@@ -14,13 +14,13 @@ tags:
   - source
 browser-compat: http.headers.csp.Content-Security-Policy.script-src-attr
 ---
-<div>{{HTTPSidebar}}</div>
+{{HTTPSidebar}}
 
-<p>The HTTP {{HTTPHeader("Content-Security-Policy")}} (CSP)
-  <code><strong>script-src-attr</strong></code> directive specifies valid sources for
-  JavaScript inline event handlers. This includes only inline script event handlers like
-  <code>onclick</code>, but not URLs loaded directly into {{HTMLElement("script")}}
-  elements.</p>
+The HTTP {{HTTPHeader("Content-Security-Policy")}} (CSP)
+**`script-src-attr`** directive specifies valid sources for
+JavaScript inline event handlers. This includes only inline script event handlers like
+`onclick`, but not URLs loaded directly into {{HTMLElement("script")}}
+elements.
 
 <table class="properties">
   <tbody>
@@ -34,104 +34,94 @@ browser-compat: http.headers.csp.Content-Security-Policy.script-src-attr
     </tr>
     <tr>
       <th scope="row">{{CSP("default-src")}} fallback</th>
-      <td>Yes. If this directive is absent, the user agent will look for
-        the {{CSP("script-src")}} directive, and if both of them are absent, fallback
-        to <code>default-src</code> directive.</td>
+      <td>
+        Yes. If this directive is absent, the user agent will look for
+        the {{CSP("script-src")}} directive, and if both of them are
+        absent, fallback to <code>default-src</code> directive.
+      </td>
     </tr>
   </tbody>
 </table>
 
-<h2 id="Syntax">Syntax</h2>
+## Syntax
 
-<p>One or more sources can be allowed for the <code>script-src-attr</code> policy:</p>
+One or more sources can be allowed for the `script-src-attr` policy:
 
-<pre class="brush: html">Content-Security-Policy: script-src-attr &lt;source&gt;;
-Content-Security-Policy: script-src-attr &lt;source&gt; &lt;source&gt;;
-</pre>
+```html
+Content-Security-Policy: script-src-attr <source>;
+Content-Security-Policy: script-src-attr <source> <source>;
+```
 
-<p><code>script-src-attr</code> can be used in conjunction with {{CSP("script-src")}}:</p>
+`script-src-attr` can be used in conjunction with {{CSP("script-src")}}:
 
-<pre class="brush: html">Content-Security-Policy: script-src &lt;source&gt;;
-Content-Security-Policy: script-src-attr &lt;source&gt;;
-</pre>
+```html
+Content-Security-Policy: script-src <source>;
+Content-Security-Policy: script-src-attr <source>;
+```
 
-<h3 id="Sources">Sources</h3>
+### Sources
 
-<dl>
-  <dt><code>&lt;host-source&gt;</code></dt>
-  <dd>Internet hosts by name or IP address, as well as an optional <a href="/en-US/docs/Learn/Common_questions/What_is_a_URL">URL scheme</a> and/or port number. The site's address may include an optional leading wildcard (the asterisk character, <code>'*'</code>), and you may use a wildcard (again, <code>'*'</code>) as the port number, indicating that all legal ports are valid for the source.<br>
-    Examples:
-    <ul>
-      <li><code>http://*.example.com</code>: Matches all attempts to load from any subdomain of example.com using the <code>http:</code> URL scheme.</li>
-      <li><code>mail.example.com:443</code>: Matches all attempts to access port 443 on mail.example.com.</li>
-      <li><code>https://store.example.com</code>: Matches all attempts to access store.example.com using <code>https:</code>.</li>
-      <li><code>*.example.com</code>: Matches all attempts to load from any subdomain of example.com using the current protocol.</li>
-    </ul>
-  </dd>
-
-  <dt><code>&lt;scheme-source&gt;</code></dt>
-  <dd>A scheme such as <code>http:</code> or <code>https:</code>. The colon is required. Unlike other values below, single quotes shouldn't be used. You can also specify data schemes (not recommended).
-    <ul>
-      <li><code>data:</code> Allows <a href="/en-US/docs/Web/HTTP/Basics_of_HTTP/Data_URIs"><code>data:</code> URIs</a> to be used as a content source.<em> This is insecure; an attacker can also inject arbitrary data: URIs. Use this sparingly and definitely not for scripts.</em></li>
-      <li><code>mediastream:</code> Allows <a href="/en-US/docs/Web/API/Media_Streams_API"><code>mediastream:</code> URIs</a> to be used as a content source.</li>
-      <li><code>blob:</code> Allows <a href="/en-US/docs/Web/API/Blob"><code>blob:</code> URIs</a> to be used as a content source.</li>
-      <li><code>filesystem:</code> Allows <a href="/en-US/docs/Web/API/FileSystem"><code>filesystem:</code> URIs</a> to be used as a content source.</li>
-    </ul>
-  </dd>
+- `<host-source>`
 
-  <dt><code>'self'</code></dt>
-  <dd>Refers to the origin from which the protected document is being served, including the same URL scheme and port number. You must include the single quotes. Some browsers specifically exclude <code>blob</code> and <code>filesystem</code> from source directives. Sites needing to allow these content types can specify them using the Data attribute.</dd>
+  - : Internet hosts by name or IP address, as well as an optional [URL scheme](/en-US/docs/Learn/Common_questions/What_is_a_URL) and/or port number. The site's address may include an optional leading wildcard (the asterisk character, `'*'`), and you may use a wildcard (again, `'*'`) as the port number, indicating that all legal ports are valid for the source.
+    Examples:
 
-  <dt><code>'unsafe-eval'</code></dt>
-  <dd>Allows the use of <code>eval()</code> and similar methods for creating code from strings. You must include the single quotes.</dd>
+    - `http://*.example.com`: Matches all attempts to load from any subdomain of example.com using the `http:` URL scheme.
+    - `mail.example.com:443`: Matches all attempts to access port 443 on mail.example.com.
+    - `https://store.example.com`: Matches all attempts to access store.example.com using `https:`.
+    - `*.example.com`: Matches all attempts to load from any subdomain of example.com using the current protocol.
 
-  <dt><code>'unsafe-hashes'</code></dt>
-  <dd>Allows enabling specific inline <a href="/en-US/docs/Web/Events/Event_handlers">event handlers</a>. If you only need to allow inline event handlers and not inline {{HTMLElement("script")}} elements or <code>javascript:</code> URLs, this is a safer method than using the <code>unsafe-inline</code> expression.</dd>
+- `<scheme-source>`
 
-  <dt><code>'unsafe-inline'</code></dt>
-  <dd>Allows the use of inline resources, such as inline {{HTMLElement("script")}} elements, <code>javascript:</code> URLs, and inline event handlers. The single quotes are required.</dd>
+  - : A scheme such as `http:` or `https:`. The colon is required. Unlike other values below, single quotes shouldn't be used. You can also specify data schemes (not recommended).
 
-  <dt><code>'none'</code></dt>
-  <dd>Refers to the empty set; that is, no URLs match. The single quotes are required.</dd>
+    - `data:` Allows [`data:` URIs](/en-US/docs/Web/HTTP/Basics_of_HTTP/Data_URIs) to be used as a content source. _This is insecure; an attacker can also inject arbitrary data: URIs. Use this sparingly and definitely not for scripts._
+    - `mediastream:` Allows [`mediastream:` URIs](/en-US/docs/Web/API/Media_Streams_API) to be used as a content source.
+    - `blob:` Allows [`blob:` URIs](/en-US/docs/Web/API/Blob) to be used as a content source.
+    - `filesystem:` Allows [`filesystem:` URIs](/en-US/docs/Web/API/FileSystem) to be used as a content source.
 
-  <dt><code>'nonce-&lt;base64-value&gt;'</code></dt>
-  <dd>An allow-list for specific inline scripts using a cryptographic nonce (number used once). The server must generate a unique nonce value each time it transmits a policy. It is critical to provide an unguessable nonce, as bypassing a resource^s policy is otherwise trivial. See <a href="/en-US/docs/Web/HTTP/Headers/Content-Security-Policy/script-src#unsafe_inline_script">unsafe inline script</a> for an example. Specifying nonce makes a modern browser ignore <code>'unsafe-inline'</code> which could still be set for older browsers without nonce support.
-    <div class="notecard note">
-      <p><strong>Note:</strong> The CSP <code>nonce</code> source can only be applied to <em>nonceable</em> elements (e.g., as the {{HTMLElement("img")}} element has no <code>nonce</code> attribute, there is no way to associate it with this CSP source).</p>
-    </div>
-  </dd>
+- `'self'`
+  - : Refers to the origin from which the protected document is being served, including the same URL scheme and port number. You must include the single quotes. Some browsers specifically exclude `blob` and `filesystem` from source directives. Sites needing to allow these content types can specify them using the Data attribute.
+- `'unsafe-eval'`
+  - : Allows the use of `eval()` and similar methods for creating code from strings. You must include the single quotes.
+- `'unsafe-hashes'`
+  - : Allows enabling specific inline [event handlers](/en-US/docs/Web/Events/Event_handlers). If you only need to allow inline event handlers and not inline {{HTMLElement("script")}} elements or `javascript:` URLs, this is a safer method than using the `unsafe-inline` expression.
+- `'unsafe-inline'`
+  - : Allows the use of inline resources, such as inline {{HTMLElement("script")}} elements, `javascript:` URLs, and inline event handlers. The single quotes are required.
+- `'none'`
+  - : Refers to the empty set; that is, no URLs match. The single quotes are required.
+- `'nonce-<base64-value>'`
 
-  <dt><code>'&lt;hash-algorithm&gt;-&lt;base64-value&gt;'</code></dt>
-  <dd>A sha256, sha384 or sha512 hash of scripts or styles. The use of this source consists of two portions separated by a dash: the encryption algorithm used to create the hash and the base64-encoded hash of the script or style. When generating the hash, don't include the &lt;script&gt; or &lt;style&gt; tags and note that capitalization and whitespace matter, including leading or trailing whitespace. See <a href="/en-US/docs/Web/HTTP/Headers/Content-Security-Policy/script-src#unsafe_inline_script">unsafe inline script</a> for an example. In CSP 2.0, this is applied only to inline scripts. CSP 3.0 allows it in the case of <code>script-src</code> for external scripts.</dd>
+  - : An allow-list for specific inline scripts using a cryptographic nonce (number used once). The server must generate a unique nonce value each time it transmits a policy. It is critical to provide an unguessable nonce, as bypassing a resource^s policy is otherwise trivial. See [unsafe inline script](/en-US/docs/Web/HTTP/Headers/Content-Security-Policy/script-src#unsafe_inline_script) for an example. Specifying nonce makes a modern browser ignore `'unsafe-inline'` which could still be set for older browsers without nonce support.
 
-  <dt><code>'strict-dynamic'</code></dt>
-  <dd>The <code>strict-dynamic</code> source expression specifies that the trust explicitly given to a script present in the markup, by accompanying it with a nonce or a hash, shall be propagated to all the scripts loaded by that root script. At the same time, any allow-list or source expressions such as <code>'self'</code> or <code>'unsafe-inline'</code> are ignored. See <a href="/en-US/docs/Web/HTTP/Headers/Content-Security-Policy/script-src#strict-dynamic">script-src</a> for an example.</dd>
+    > **Note:** The CSP `nonce` source can only be applied to _nonceable_ elements (e.g., as the {{HTMLElement("img")}} element has no `nonce` attribute, there is no way to associate it with this CSP source).
 
-  <dt><code>'report-sample'</code></dt>
-  <dd>Requires a sample of the violating code to be included in the violation report.</dd>
-</dl>
+- `'<hash-algorithm>-<base64-value>'`
+  - : A sha256, sha384 or sha512 hash of scripts or styles. The use of this source consists of two portions separated by a dash: the encryption algorithm used to create the hash and the base64-encoded hash of the script or style. When generating the hash, don't include the \<script> or \<style> tags and note that capitalization and whitespace matter, including leading or trailing whitespace. See [unsafe inline script](/en-US/docs/Web/HTTP/Headers/Content-Security-Policy/script-src#unsafe_inline_script) for an example. In CSP 2.0, this is applied only to inline scripts. CSP 3.0 allows it in the case of `script-src` for external scripts.
+- `'strict-dynamic'`
+  - : The `strict-dynamic` source expression specifies that the trust explicitly given to a script present in the markup, by accompanying it with a nonce or a hash, shall be propagated to all the scripts loaded by that root script. At the same time, any allow-list or source expressions such as `'self'` or `'unsafe-inline'` are ignored. See [script-src](/en-US/docs/Web/HTTP/Headers/Content-Security-Policy/script-src#strict-dynamic) for an example.
+- `'report-sample'`
+  - : Requires a sample of the violating code to be included in the violation report.
 
-<h2 id="Examples">Examples</h2>
+## Examples
 
-<h3 id="Fallback_to_script-src">Fallback to script-src</h3>
+### Fallback to script-src
 
-<p>If <code>script-src-attr</code> is absent, User Agent falls back to
-  the {{CSP("script-src")}} directive, and if that is absent as well, to
-  {{CSP("default-src")}}.</p>
+If `script-src-attr` is absent, User Agent falls back to
+the {{CSP("script-src")}} directive, and if that is absent as well, to
+{{CSP("default-src")}}.
 
-<h2 id="Specifications">Specifications</h2>
+## Specifications
 
 {{Specifications}}
 
-<h2 id="Browser_compatibility">Browser compatibility</h2>
+## Browser compatibility
 
-<p>{{Compat}}</p>
+{{Compat}}
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
-  <li>{{HTTPHeader("Content-Security-Policy")}}</li>
-  <li>{{HTMLElement("script")}}</li>
-  <li>{{CSP("script-src")}}</li>
-  <li>{{CSP("script-src-elem")}}</li>
-</ul>
+- {{HTTPHeader("Content-Security-Policy")}}
+- {{HTMLElement("script")}}
+- {{CSP("script-src")}}
+- {{CSP("script-src-elem")}}
diff --git a/files/en-us/web/http/headers/content-security-policy/script-src-elem/index.md b/files/en-us/web/http/headers/content-security-policy/script-src-elem/index.md
index 8067babdf6c6cb5..3607315c63d664a 100644
--- a/files/en-us/web/http/headers/content-security-policy/script-src-elem/index.md
+++ b/files/en-us/web/http/headers/content-security-policy/script-src-elem/index.md
@@ -14,116 +14,108 @@ tags:
   - source
 browser-compat: http.headers.csp.Content-Security-Policy.script-src-elem
 ---
-<div>{{HTTPSidebar}}</div>
+{{HTTPSidebar}}
 
-<p>The HTTP {{HTTPHeader("Content-Security-Policy")}} (CSP) <strong><code>script-src-elem</code></strong> directive specifies valid sources for JavaScript {{HTMLElement("script")}} elements, but not inline script event handlers like <code>onclick</code>.</p>
+The HTTP {{HTTPHeader("Content-Security-Policy")}} (CSP) **`script-src-elem`** directive specifies valid sources for JavaScript {{HTMLElement("script")}} elements, but not inline script event handlers like `onclick`.
 
 <table class="properties">
- <tbody>
-  <tr>
-   <th scope="row">CSP version</th>
-   <td>3</td>
-  </tr>
-  <tr>
-   <th scope="row">Directive type</th>
-   <td>{{Glossary("Fetch directive")}}</td>
-  </tr>
-  <tr>
-   <th scope="row">{{CSP("default-src")}} fallback</th>
-   <td>Yes. If this directive is absent, the user agent will look for the {{CSP("script-src")}} directive, and if both of them are absent, fallback to <code>default-src</code> directive.</td>
-  </tr>
- </tbody>
+  <tbody>
+    <tr>
+      <th scope="row">CSP version</th>
+      <td>3</td>
+    </tr>
+    <tr>
+      <th scope="row">Directive type</th>
+      <td>{{Glossary("Fetch directive")}}</td>
+    </tr>
+    <tr>
+      <th scope="row">{{CSP("default-src")}} fallback</th>
+      <td>
+        Yes. If this directive is absent, the user agent will look for the
+        {{CSP("script-src")}} directive, and if both of them are absent,
+        fallback to <code>default-src</code> directive.
+      </td>
+    </tr>
+  </tbody>
 </table>
 
-<h2 id="Syntax">Syntax</h2>
+## Syntax
 
-<p>One or more sources can be allowed for the <code>script-src-elem</code> policy:</p>
+One or more sources can be allowed for the `script-src-elem` policy:
 
-<pre class="brush: html">Content-Security-Policy: script-src-elem &lt;source&gt;;
-Content-Security-Policy: script-src-elem &lt;source&gt; &lt;source&gt;;
-</pre>
+```html
+Content-Security-Policy: script-src-elem <source>;
+Content-Security-Policy: script-src-elem <source> <source>;
+```
 
-<p><code>script-src-elem</code> can be used in conjunction with {{CSP("script-src")}}:</p>
+`script-src-elem` can be used in conjunction with {{CSP("script-src")}}:
 
-<pre class="brush: html">Content-Security-Policy: script-src &lt;source&gt;;
-Content-Security-Policy: script-src-elem &lt;source&gt;;
-</pre>
+```html
+Content-Security-Policy: script-src <source>;
+Content-Security-Policy: script-src-elem <source>;
+```
 
-<h3 id="Sources">Sources</h3>
+### Sources
 
-<dl>
-  <dt><code>&lt;host-source&gt;</code></dt>
-  <dd>Internet hosts by name or IP address, as well as an optional <a href="/en-US/docs/Learn/Common_questions/What_is_a_URL">URL scheme</a> and/or port number. The site's address may include an optional leading wildcard (the asterisk character, <code>'*'</code>), and you may use a wildcard (again, <code>'*'</code>) as the port number, indicating that all legal ports are valid for the source.<br>
-    Examples:
-    <ul>
-      <li><code>http://*.example.com</code>: Matches all attempts to load from any subdomain of example.com using the <code>http:</code> URL scheme.</li>
-      <li><code>mail.example.com:443</code>: Matches all attempts to access port 443 on mail.example.com.</li>
-      <li><code>https://store.example.com</code>: Matches all attempts to access store.example.com using <code>https:</code>.</li>
-      <li><code>*.example.com</code>: Matches all attempts to load from any subdomain of example.com using the current protocol.</li>
-    </ul>
-  </dd>
-
-  <dt></ode>&lt;scheme-source&gt;</code></dt>
-  <dd>A scheme such as <code>http:</code> or <code>https:</code>. The colon is required. Unlike other values below, single quotes shouldn't be used. You can also specify data schemes (not recommended).
-    <ul>
-      <li><code>data:</code> Allows <a href="/en-US/docs/Web/HTTP/Basics_of_HTTP/Data_URIs"><code>data:</code> URIs</a> to be used as a content source.<em> This is insecure; an attacker can also inject arbitrary data: URIs. Use this sparingly and definitely not for scripts.</em></li>
-      <li><code>mediastream:</code> Allows <a href="/en-US/docs/Web/API/Media_Streams_API"><code>mediastream:</code> URIs</a> to be used as a content source.</li>
-      <li><code>blob:</code> Allows <a href="/en-US/docs/Web/API/Blob"><code>blob:</code> URIs</a> to be used as a content source.</li>
-      <li><code>filesystem:</code> Allows <a href="/en-US/docs/Web/API/FileSystem"><code>filesystem:</code> URIs</a> to be used as a content source.</li>
-    </ul>
-  </dd>
+- `<host-source>`
 
-  <dt><code>'self'</code></dt>
-  <dd>Refers to the origin from which the protected document is being served, including the same URL scheme and port number. You must include the single quotes. Some browsers specifically exclude <code>blob</code> and <code>filesystem</code> from source directives. Sites needing to allow these content types can specify them using the Data attribute.</dd>
+  - : Internet hosts by name or IP address, as well as an optional [URL scheme](/en-US/docs/Learn/Common_questions/What_is_a_URL) and/or port number. The site's address may include an optional leading wildcard (the asterisk character, `'*'`), and you may use a wildcard (again, `'*'`) as the port number, indicating that all legal ports are valid for the source.
+    Examples:
 
-  <dt><code>'unsafe-eval'</code></dt>
-  <dd>Allows the use of <code>eval()</code> and similar methods for creating code from strings. You must include the single quotes.</dd>
+    - `http://*.example.com`: Matches all attempts to load from any subdomain of example.com using the `http:` URL scheme.
+    - `mail.example.com:443`: Matches all attempts to access port 443 on mail.example.com.
+    - `https://store.example.com`: Matches all attempts to access store.example.com using `https:`.
+    - `*.example.com`: Matches all attempts to load from any subdomain of example.com using the current protocol.
 
-  <dt><code>'unsafe-hashes'</code></dt>
-  <dd>Allows enabling specific inline <a href="/en-US/docs/Web/Events/Event_handlers">event handlers</a>. If you only need to allow inline event handlers and not inline {{HTMLElement("script")}} elements or <code>javascript:</code> URLs, this is a safer method than using the <code>unsafe-inline</code> expression.</dd>
+- \<scheme-source>
 
-  <dt><code>'unsafe-inline'</code></dt>
-  <dd>Allows the use of inline resources, such as inline {{HTMLElement("script")}} elements, <code>javascript:</code> URLs, and inline event handlers. The single quotes are required.</dd>
+  - : A scheme such as `http:` or `https:`. The colon is required. Unlike other values below, single quotes shouldn't be used. You can also specify data schemes (not recommended).
 
-  <dt><code>'none'</code></dt>
-  <dd>Refers to the empty set; that is, no URLs match. The single quotes are required.</dd>
+    - `data:` Allows [`data:` URIs](/en-US/docs/Web/HTTP/Basics_of_HTTP/Data_URIs) to be used as a content source. _This is insecure; an attacker can also inject arbitrary data: URIs. Use this sparingly and definitely not for scripts._
+    - `mediastream:` Allows [`mediastream:` URIs](/en-US/docs/Web/API/Media_Streams_API) to be used as a content source.
+    - `blob:` Allows [`blob:` URIs](/en-US/docs/Web/API/Blob) to be used as a content source.
+    - `filesystem:` Allows [`filesystem:` URIs](/en-US/docs/Web/API/FileSystem) to be used as a content source.
 
-  <dt><code>'nonce-&lt;base64-value&gt;'</code></dt>
-  <dd>An allow-list for specific inline scripts using a cryptographic nonce (number used once). The server must generate a unique nonce value each time it transmits a policy. It is critical to provide an unguessable nonce, as bypassing a resource's policy is otherwise trivial. See <a href="/en-US/docs/Web/HTTP/Headers/Content-Security-Policy/script-src#unsafe_inline_script">unsafe inline script</a> for an example. Specifying nonce makes a modern browser ignore <code>'unsafe-inline'</code> which could still be set for older browsers without nonce support.
-    <div class="notecard note">
-      <p><strong>Note:</strong> The CSP <code>nonce</code> source can only be applied to <em>nonceable</em> elements (e.g., as the {{HTMLElement("img")}} element has no <code>nonce</code> attribute, there is no way to associate it with this CSP source).</p>
-    </div>
-  </dd>
+- `'self'`
+  - : Refers to the origin from which the protected document is being served, including the same URL scheme and port number. You must include the single quotes. Some browsers specifically exclude `blob` and `filesystem` from source directives. Sites needing to allow these content types can specify them using the Data attribute.
+- `'unsafe-eval'`
+  - : Allows the use of `eval()` and similar methods for creating code from strings. You must include the single quotes.
+- `'unsafe-hashes'`
+  - : Allows enabling specific inline [event handlers](/en-US/docs/Web/Events/Event_handlers). If you only need to allow inline event handlers and not inline {{HTMLElement("script")}} elements or `javascript:` URLs, this is a safer method than using the `unsafe-inline` expression.
+- `'unsafe-inline'`
+  - : Allows the use of inline resources, such as inline {{HTMLElement("script")}} elements, `javascript:` URLs, and inline event handlers. The single quotes are required.
+- `'none'`
+  - : Refers to the empty set; that is, no URLs match. The single quotes are required.
+- `'nonce-<base64-value>'`
 
-  <dt><code>'&lt;hash-algorithm&gt;-&lt;base64-value&gt;'</code></dt>
-  <dd>A sha256, sha384 or sha512 hash of scripts or styles. The use of this source consists of two portions separated by a dash: the encryption algorithm used to create the hash and the base64-encoded hash of the script or style. When generating the hash, don't include the &lt;script&gt; or &lt;style&gt; tags and note that capitalization and whitespace matter, including leading or trailing whitespace. See <a href="/en-US/docs/Web/HTTP/Headers/Content-Security-Policy/script-src#unsafe_inline_script">unsafe inline script</a> for an example. In CSP 2.0, this is applied only to inline scripts. CSP 3.0 allows it in the case of <code>script-src</code> for external scripts.</dd>
+  - : An allow-list for specific inline scripts using a cryptographic nonce (number used once). The server must generate a unique nonce value each time it transmits a policy. It is critical to provide an unguessable nonce, as bypassing a resource's policy is otherwise trivial. See [unsafe inline script](/en-US/docs/Web/HTTP/Headers/Content-Security-Policy/script-src#unsafe_inline_script) for an example. Specifying nonce makes a modern browser ignore `'unsafe-inline'` which could still be set for older browsers without nonce support.
 
-  <dt><code>'strict-dynamic'</code></dt>
-  <dd>The <code>strict-dynamic</code> source expression specifies that the trust explicitly given to a script present in the markup, by accompanying it with a nonce or a hash, shall be propagated to all the scripts loaded by that root script. At the same time, any allow-list or source expressions such as <code>'self'</code> or <code>'unsafe-inline'</code> are ignored. See <a href="/en-US/docs/Web/HTTP/Headers/Content-Security-Policy/script-src#strict-dynamic">script-src</a> for an example.</dd>
+    > **Note:** The CSP `nonce` source can only be applied to _nonceable_ elements (e.g., as the {{HTMLElement("img")}} element has no `nonce` attribute, there is no way to associate it with this CSP source).
 
-  <dt><code>'report-sample'</code></dt>
-  <dd>Requires a sample of the violating code to be included in the violation report.</dd>
-</dl>
+- `'<hash-algorithm>-<base64-value>'`
+  - : A sha256, sha384 or sha512 hash of scripts or styles. The use of this source consists of two portions separated by a dash: the encryption algorithm used to create the hash and the base64-encoded hash of the script or style. When generating the hash, don't include the \<script> or \<style> tags and note that capitalization and whitespace matter, including leading or trailing whitespace. See [unsafe inline script](/en-US/docs/Web/HTTP/Headers/Content-Security-Policy/script-src#unsafe_inline_script) for an example. In CSP 2.0, this is applied only to inline scripts. CSP 3.0 allows it in the case of `script-src` for external scripts.
+- `'strict-dynamic'`
+  - : The `strict-dynamic` source expression specifies that the trust explicitly given to a script present in the markup, by accompanying it with a nonce or a hash, shall be propagated to all the scripts loaded by that root script. At the same time, any allow-list or source expressions such as `'self'` or `'unsafe-inline'` are ignored. See [script-src](/en-US/docs/Web/HTTP/Headers/Content-Security-Policy/script-src#strict-dynamic) for an example.
+- `'report-sample'`
+  - : Requires a sample of the violating code to be included in the violation report.
 
-<h2 id="Examples">Examples</h2>
+## Examples
 
-<h3 id="Fallback_to_script-src">Fallback to script-src</h3>
+### Fallback to script-src
 
-<p>If <code>script-src-elem</code> is absent, User Agent falls back to the {{CSP("script-src")}} directive, and if that is absent as well, to {{CSP("default-src")}}.</p>
+If `script-src-elem` is absent, User Agent falls back to the {{CSP("script-src")}} directive, and if that is absent as well, to {{CSP("default-src")}}.
 
-<h2 id="Specifications">Specifications</h2>
+## Specifications
 
 {{Specifications}}
 
-<h2 id="Browser_compatibility">Browser compatibility</h2>
+## Browser compatibility
 
-<p>{{Compat}}</p>
+{{Compat}}
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
- <li>{{HTTPHeader("Content-Security-Policy")}}</li>
- <li>{{HTMLElement("script")}}</li>
- <li>{{CSP("script-src")}}</li>
- <li>{{CSP("script-src-attr")}}</li>
-</ul>
+- {{HTTPHeader("Content-Security-Policy")}}
+- {{HTMLElement("script")}}
+- {{CSP("script-src")}}
+- {{CSP("script-src-attr")}}
diff --git a/files/en-us/web/http/headers/content-security-policy/script-src/index.md b/files/en-us/web/http/headers/content-security-policy/script-src/index.md
index ddab1ad0a4d998a..81c26a839a2f7d4 100644
--- a/files/en-us/web/http/headers/content-security-policy/script-src/index.md
+++ b/files/en-us/web/http/headers/content-security-policy/script-src/index.md
@@ -14,193 +14,189 @@ tags:
   - source
 browser-compat: http.headers.csp.Content-Security-Policy.script-src
 ---
-<div>{{HTTPSidebar}}</div>
+{{HTTPSidebar}}
 
-<p>The HTTP {{HTTPHeader("Content-Security-Policy")}} (CSP) <code><strong>script-src</strong></code> directive specifies valid sources for JavaScript. This includes not only URLs loaded directly into {{HTMLElement("script")}} elements, but also things like inline script event handlers (<code>onclick</code>) and <a href="/en-US/docs/Web/XSLT">XSLT stylesheets</a> which can trigger script execution.</p>
+The HTTP {{HTTPHeader("Content-Security-Policy")}} (CSP) **`script-src`** directive specifies valid sources for JavaScript. This includes not only URLs loaded directly into {{HTMLElement("script")}} elements, but also things like inline script event handlers (`onclick`) and [XSLT stylesheets](/en-US/docs/Web/XSLT) which can trigger script execution.
 
 <table class="properties">
- <tbody>
-  <tr>
-   <th scope="row">CSP version</th>
-   <td>1</td>
-  </tr>
-  <tr>
-   <th scope="row">Directive type</th>
-   <td>{{Glossary("Fetch directive")}}</td>
-  </tr>
-  <tr>
-   <th scope="row">{{CSP("default-src")}} fallback</th>
-   <td>Yes. If this directive is absent, the user agent will look for the <code>default-src</code> directive.</td>
-  </tr>
- </tbody>
+  <tbody>
+    <tr>
+      <th scope="row">CSP version</th>
+      <td>1</td>
+    </tr>
+    <tr>
+      <th scope="row">Directive type</th>
+      <td>{{Glossary("Fetch directive")}}</td>
+    </tr>
+    <tr>
+      <th scope="row">{{CSP("default-src")}} fallback</th>
+      <td>
+        Yes. If this directive is absent, the user agent will look for the
+        <code>default-src</code> directive.
+      </td>
+    </tr>
+  </tbody>
 </table>
 
-<h2 id="Syntax">Syntax</h2>
+## Syntax
 
-<p>One or more sources can be allowed for the <code>script-src</code> policy:</p>
+One or more sources can be allowed for the `script-src` policy:
 
-<pre class="brush: html">Content-Security-Policy: script-src &lt;source&gt;;
-Content-Security-Policy: script-src &lt;source&gt; &lt;source&gt;;
-</pre>
+```html
+Content-Security-Policy: script-src <source>;
+Content-Security-Policy: script-src <source> <source>;
+```
 
-<h3 id="Sources">Sources</h3>
+### Sources
 
-<dl>
-  <dt><code>&lt;host-source&gt;</code></dt>
-  <dd>Internet hosts by name or IP address, as well as an optional <a href="/en-US/docs/Learn/Common_questions/What_is_a_URL">URL scheme</a> and/or port number. The site's address may include an optional leading wildcard (the asterisk character, <code>'*'</code>), and you may use a wildcard (again, <code>'*'</code>) as the port number, indicating that all legal ports are valid for the source.<br>
-  Examples:
-  <ul>
-   <li><code>http://*.example.com</code>: Matches all attempts to load from any subdomain of example.com using the <code>http:</code> URL scheme.</li>
-   <li><code>mail.example.com:443</code>: Matches all attempts to access port 443 on mail.example.com.</li>
-   <li><code>https://store.example.com</code>: Matches all attempts to access store.example.com using <code>https:</code>.</li>
-   <li><code>*.example.com</code>: Matches all attempts to load from any subdomain of example.com using the current protocol.</li>
-  </ul>
-  </dd>
+- `<host-source>`
 
-  <dt><code>&lt;scheme-source&gt;</code></dt>
-  <dd>A scheme such as <code>http:</code> or <code>https:</code>. The colon is required. Unlike other values below, single quotes shouldn't be used. You can also specify data schemes (not recommended).
-  <ul>
-   <li><code>data:</code> Allows <a href="/en-US/docs/Web/HTTP/Basics_of_HTTP/Data_URIs"><code>data:</code> URIs</a> to be used as a content source.<em> This is insecure; an attacker can also inject arbitrary data: URIs. Use this sparingly and definitely not for scripts.</em></li>
-   <li><code>mediastream:</code> Allows <a href="/en-US/docs/Web/API/Media_Streams_API"><code>mediastream:</code> URIs</a> to be used as a content source.</li>
-   <li><code>blob:</code> Allows <a href="/en-US/docs/Web/API/Blob"><code>blob:</code> URIs</a> to be used as a content source.</li>
-   <li><code>filesystem:</code> Allows <a href="/en-US/docs/Web/API/FileSystem"><code>filesystem:</code> URIs</a> to be used as a content source.</li>
-  </ul>
-  </dd>
+  - : Internet hosts by name or IP address, as well as an optional [URL scheme](/en-US/docs/Learn/Common_questions/What_is_a_URL) and/or port number. The site's address may include an optional leading wildcard (the asterisk character, `'*'`), and you may use a wildcard (again, `'*'`) as the port number, indicating that all legal ports are valid for the source.
+    Examples:
 
-  <dt><code>'self'</code></dt>
-  <dd>Refers to the origin from which the protected document is being served, including the same URL scheme and port number. You must include the single quotes. Some browsers specifically exclude <code>blob</code> and <code>filesystem</code> from source directives. Sites needing to allow these content types can specify them using the Data attribute.</dd>
+    - `http://*.example.com`: Matches all attempts to load from any subdomain of example.com using the `http:` URL scheme.
+    - `mail.example.com:443`: Matches all attempts to access port 443 on mail.example.com.
+    - `https://store.example.com`: Matches all attempts to access store.example.com using `https:`.
+    - `*.example.com`: Matches all attempts to load from any subdomain of example.com using the current protocol.
 
-  <dt><code>'unsafe-eval'</code></dt>
-  <dd>Allows the use of <code>eval()</code> and similar methods for creating code from strings. You must include the single quotes.</dd>
+- `<scheme-source>`
 
-  <dt><code>'unsafe-hashes'</code></dt>
-  <dd>Allows enabling specific inline <a href="/en-US/docs/Web/Events/Event_handlers">event handlers</a>. If you only need to allow inline event handlers and not inline {{HTMLElement("script")}} elements or <code>javascript:</code> URLs, this is a safer method than using the <code>unsafe-inline</code> expression.</dd>
+  - : A scheme such as `http:` or `https:`. The colon is required. Unlike other values below, single quotes shouldn't be used. You can also specify data schemes (not recommended).
 
-  <dt><code>'unsafe-inline'</code></dt>
-  <dd>Allows the use of inline resources, such as inline {{HTMLElement("script")}} elements, <code>javascript:</code> URLs, and inline event handlers. The single quotes are required.</dd>
+    - `data:` Allows [`data:` URIs](/en-US/docs/Web/HTTP/Basics_of_HTTP/Data_URIs) to be used as a content source. _This is insecure; an attacker can also inject arbitrary data: URIs. Use this sparingly and definitely not for scripts._
+    - `mediastream:` Allows [`mediastream:` URIs](/en-US/docs/Web/API/Media_Streams_API) to be used as a content source.
+    - `blob:` Allows [`blob:` URIs](/en-US/docs/Web/API/Blob) to be used as a content source.
+    - `filesystem:` Allows [`filesystem:` URIs](/en-US/docs/Web/API/FileSystem) to be used as a content source.
 
-  <dt><code>'none'</code></dt>
-  <dd>Refers to the empty set; that is, no URLs match. The single quotes are required.</dd>
+- `'self'`
+  - : Refers to the origin from which the protected document is being served, including the same URL scheme and port number. You must include the single quotes. Some browsers specifically exclude `blob` and `filesystem` from source directives. Sites needing to allow these content types can specify them using the Data attribute.
+- `'unsafe-eval'`
+  - : Allows the use of `eval()` and similar methods for creating code from strings. You must include the single quotes.
+- `'unsafe-hashes'`
+  - : Allows enabling specific inline [event handlers](/en-US/docs/Web/Events/Event_handlers). If you only need to allow inline event handlers and not inline {{HTMLElement("script")}} elements or `javascript:` URLs, this is a safer method than using the `unsafe-inline` expression.
+- `'unsafe-inline'`
+  - : Allows the use of inline resources, such as inline {{HTMLElement("script")}} elements, `javascript:` URLs, and inline event handlers. The single quotes are required.
+- `'none'`
+  - : Refers to the empty set; that is, no URLs match. The single quotes are required.
+- `'nonce-<base64-value>'`
 
-  <dt><code>'nonce-&lt;base64-value&gt;'</code></dt>
-  <dd>An allow-list for specific inline scripts using a cryptographic nonce (number used once). The server must generate a unique nonce value each time it transmits a policy. It is critical to provide an unguessable nonce, as bypassing a resource's policy is otherwise trivial. See <a href="#unsafe_inline_script">unsafe inline script</a> for an example. Specifying nonce makes a modern browser ignore <code>'unsafe-inline'</code> which could still be set for older browsers without nonce support.
-    <div class="notecard note">
-      <p><strong>Note:</strong> The CSP <code>nonce</code> source can only be applied to <em>nonceable</em> elements (e.g., as the {{HTMLElement("img")}} element has no <code>nonce</code> attribute, there is no way to associate it with this CSP source).</p>
-    </div>
-  </dd>
+  - : An allow-list for specific inline scripts using a cryptographic nonce (number used once). The server must generate a unique nonce value each time it transmits a policy. It is critical to provide an unguessable nonce, as bypassing a resource's policy is otherwise trivial. See [unsafe inline script](#unsafe_inline_script) for an example. Specifying nonce makes a modern browser ignore `'unsafe-inline'` which could still be set for older browsers without nonce support.
 
-  <dt><code>'&lt;hash-algorithm&gt;-&lt;base64-value&gt;'</code></dt>
-  <dd>A sha256, sha384 or sha512 hash of scripts or styles. The use of this source consists of two portions separated by a dash: the encryption algorithm used to create the hash and the base64-encoded hash of the script or style. When generating the hash, don't include the &lt;script&gt; or &lt;style&gt; tags and note that capitalization and whitespace matter, including leading or trailing whitespace. See <a href="#unsafe_inline_script">unsafe inline script</a> for an example. In CSP 2.0, this is applied only to inline scripts. CSP 3.0 allows it in the case of <code>script-src</code> for external scripts.</dd>
+    > **Note:** The CSP `nonce` source can only be applied to _nonceable_ elements (e.g., as the {{HTMLElement("img")}} element has no `nonce` attribute, there is no way to associate it with this CSP source).
 
-  <dt><code>'strict-dynamic'</code></dt>
-  <dd>The <code>strict-dynamic</code> source expression specifies that the trust explicitly given to a script present in the markup, by accompanying it with a nonce or a hash, shall be propagated to all the scripts loaded by that root script. At the same time, any allow-list or source expressions such as <code>'self'</code> or <code>'unsafe-inline'</code> are ignored.</dd>
+- `'<hash-algorithm>-<base64-value>'`
+  - : A sha256, sha384 or sha512 hash of scripts or styles. The use of this source consists of two portions separated by a dash: the encryption algorithm used to create the hash and the base64-encoded hash of the script or style. When generating the hash, don't include the \<script> or \<style> tags and note that capitalization and whitespace matter, including leading or trailing whitespace. See [unsafe inline script](#unsafe_inline_script) for an example. In CSP 2.0, this is applied only to inline scripts. CSP 3.0 allows it in the case of `script-src` for external scripts.
+- `'strict-dynamic'`
+  - : The `strict-dynamic` source expression specifies that the trust explicitly given to a script present in the markup, by accompanying it with a nonce or a hash, shall be propagated to all the scripts loaded by that root script. At the same time, any allow-list or source expressions such as `'self'` or `'unsafe-inline'` are ignored.
+- `'report-sample'`
+  - : Requires a sample of the violating code to be included in the violation report.
 
-   <dt><code>'report-sample'</code></dt>
-  <dd>Requires a sample of the violating code to be included in the violation report.</dd>
-</dl>
+## Examples
 
-<h2 id="Examples">Examples</h2>
+### Violation case
 
-<h3 id="Violation_case">Violation case</h3>
+Given this CSP header:
 
-<p>Given this CSP header:</p>
+    Content-Security-Policy: script-src https://example.com/
 
-<pre>Content-Security-Policy: script-src https://example.com/</pre>
+the following script is blocked and won't be loaded or executed:
 
-<p>the following script is blocked and won't be loaded or executed:</p>
+```html
+<script src="https://not-example.com/js/library.js"></script>
+```
 
-<pre class="brush: html">&lt;script src="https://not-example.com/js/library.js"&gt;&lt;/script&gt;</pre>
+Note that inline event handlers are blocked as well:
 
-<p>Note that inline event handlers are blocked as well:</p>
+```html
+<button id="btn" onclick="doSomething()">
+```
 
-<pre class="brush: html">&lt;button id="btn" onclick="doSomething()"&gt;</pre>
+You should replace them with {{domxref("EventTarget.addEventListener", "addEventListener")}} calls:
 
-<p>You should replace them with {{domxref("EventTarget.addEventListener", "addEventListener")}} calls:</p>
+```js
+document.getElementById("btn").addEventListener('click', doSomething);
+```
 
-<pre class="brush: js">document.getElementById("btn").addEventListener('click', doSomething);</pre>
+### Unsafe inline script
 
-<h3 id="Unsafe_inline_script">Unsafe inline script</h3>
+> **Note:** Disallowing inline styles and inline scripts is one of the biggest security wins CSP provides. However, if you absolutely have to use it, there are a few mechanisms that will allow them.
 
-<div class="notecard note">
-  <p><strong>Note:</strong> Disallowing inline styles and inline scripts is one of the biggest security wins CSP provides. However, if you absolutely have to use it, there are a few mechanisms that will allow them.</p>
-</div>
+To allow inline scripts and inline event handlers, `'unsafe-inline'`, a nonce-source or a hash-source that matches the inline block can be specified.
 
-<p>To allow inline scripts and inline event handlers, <code>'unsafe-inline'</code>, a nonce-source or a hash-source that matches the inline block can be specified.</p>
+    Content-Security-Policy: script-src 'unsafe-inline';
 
-<pre>Content-Security-Policy: script-src 'unsafe-inline';
-</pre>
+The above Content Security Policy will allow inline {{HTMLElement("script")}} elements
 
-<p>The above Content Security Policy will allow inline {{HTMLElement("script")}} elements</p>
-
-<pre class="brush: html">&lt;script&gt;
+```html
+<script>
   var inline = 1;
-&lt;/script&gt;</pre>
+</script>
+```
 
-<p>You can use a nonce-source to only allow specific inline script blocks:</p>
+You can use a nonce-source to only allow specific inline script blocks:
 
-<pre>Content-Security-Policy: script-src 'nonce-2726c7f26c'</pre>
+    Content-Security-Policy: script-src 'nonce-2726c7f26c'
 
-<p>You will have to set the same nonce on the {{HTMLElement("script")}} element:</p>
+You will have to set the same nonce on the {{HTMLElement("script")}} element:
 
-<pre class="brush: html">&lt;script nonce="2726c7f26c"&gt;
+```html
+<script nonce="2726c7f26c">
   var inline = 1;
-&lt;/script&gt;</pre>
+</script>
+```
+
+Alternatively, you can create hashes from your inline scripts. CSP supports sha256, sha384 and sha512.
+
+    Content-Security-Policy: script-src 'sha256-B2yPHKaXnvFWtRChIbabYmUBFZdVfKKXHbWtWidDVF8='
 
-<p>Alternatively, you can create hashes from your inline scripts. CSP supports sha256, sha384 and sha512.</p>
+When generating the hash, don't include the {{HTMLElement("script")}} tags and note that capitalization and whitespace matter, including leading or trailing whitespace.
 
-<pre>Content-Security-Policy: script-src 'sha256-B2yPHKaXnvFWtRChIbabYmUBFZdVfKKXHbWtWidDVF8='</pre>
+```html
+<script>var inline = 1;</script>
+```
 
-<p>When generating the hash, don't include the {{HTMLElement("script")}} tags and note that capitalization and whitespace matter, including leading or trailing whitespace.</p>
+### Unsafe eval expressions
 
-<pre class="brush: html">&lt;script&gt;var inline = 1;&lt;/script&gt;</pre>
+The `'unsafe-eval'` source expression controls several script execution methods that create code from strings. If `'unsafe-eval'` isn't specified with the `script-src` directive, the following methods are blocked and won't have any effect:
 
-<h3 id="Unsafe_eval_expressions">Unsafe eval expressions</h3>
+- {{jsxref("Global_Objects/eval", "eval()")}}
+- {{jsxref("Function", "Function()")}}
+- When passing a string literal like to methods like: `window.setTimeout("alert(\"Hello World!\");", 500);`
 
-<p>The <code>'unsafe-eval'</code> source expression controls several script execution methods that create code from strings. If <code>'unsafe-eval'</code> isn't specified with the <code>script-src</code> directive, the following methods are blocked and won't have any effect:</p>
+  - {{domxref("WindowOrWorkerGlobalScope.setTimeout")}}
+  - {{domxref("WindowOrWorkerGlobalScope.setInterval")}}
+  - {{domxref("window.setImmediate")}}
 
-<ul>
- <li>{{jsxref("Global_Objects/eval", "eval()")}}</li>
- <li>{{jsxref("Function", "Function()")}}</li>
- <li>When passing a string literal like to methods like: <code>window.setTimeout("alert(\"Hello World!\");", 500);</code>
-  <ul>
-   <li>{{domxref("WindowOrWorkerGlobalScope.setTimeout")}}</li>
-   <li>{{domxref("WindowOrWorkerGlobalScope.setInterval")}}</li>
-   <li>{{domxref("window.setImmediate")}}</li>
-  </ul>
- </li>
- <li><code>window.execScript()</code> {{non-standard_inline}} (IE &lt; 11 only)</li>
-</ul>
+- `window.execScript()` {{non-standard_inline}} (IE < 11 only)
 
-<h3 id="strict-dynamic">strict-dynamic</h3>
+### strict-dynamic
 
-<p>The <code>'strict-dynamic'</code> source expression specifies that the trust explicitly given to a script present in the markup, by accompanying it with a nonce or a hash, shall be propagated to all the scripts loaded by that root script. At the same time, any whitelist or source expressions such as <code>'self'</code> or <code>'unsafe-inline'</code> will be ignored. For example, a policy such as <code>script-src 'strict-dynamic' 'nonce-R4nd0m' https://whitelisted.com/</code> would allow loading of a root script with <code>&lt;script nonce="R4nd0m" src="https://example.com/loader.js"&gt;</code> and propagate that trust to any script loaded by <code>loader.js</code>, but disallow loading scripts from <code>https://whitelisted.com/</code> unless accompanied by a nonce or loaded from a trusted script.</p>
+The `'strict-dynamic'` source expression specifies that the trust explicitly given to a script present in the markup, by accompanying it with a nonce or a hash, shall be propagated to all the scripts loaded by that root script. At the same time, any whitelist or source expressions such as `'self'` or `'unsafe-inline'` will be ignored. For example, a policy such as `script-src 'strict-dynamic' 'nonce-R4nd0m' https://whitelisted.com/` would allow loading of a root script with `<script nonce="R4nd0m" src="https://example.com/loader.js">` and propagate that trust to any script loaded by `loader.js`, but disallow loading scripts from `https://whitelisted.com/` unless accompanied by a nonce or loaded from a trusted script.
 
-<pre>Content-Security-Policy: script-src 'strict-dynamic' 'nonce-<em>someNonce</em>'</pre>
+    Content-Security-Policy: script-src 'strict-dynamic' 'nonce-someNonce'
 
-<p>Or:</p>
+Or:
 
-<pre>Content-Security-Policy: script-src 'strict-dynamic' 'sha256-<em>base64EncodedHash</em>'</pre>
+    Content-Security-Policy: script-src 'strict-dynamic' 'sha256-base64EncodedHash'
 
-<p>It is possible to deploy <code>strict-dynamic</code> in a backwards compatible way, without requiring user-agent sniffing.<br>
- The policy:</p>
+It is possible to deploy `strict-dynamic` in a backwards compatible way, without requiring user-agent sniffing.
+The policy:
 
-<pre>Content-Security-Policy: script-src 'unsafe-inline' https: 'nonce-abcdefg' 'strict-dynamic'</pre>
+    Content-Security-Policy: script-src 'unsafe-inline' https: 'nonce-abcdefg' 'strict-dynamic'
 
-<p>will act like <code>'unsafe-inline' https:</code> in browsers that support CSP1, <code>https: 'nonce-abcdefg'</code> in browsers that support CSP2, and <code>'nonce-abcdefg' 'strict-dynamic'</code> in browsers that support CSP3.</p>
+will act like `'unsafe-inline' https:` in browsers that support CSP1, `https: 'nonce-abcdefg'` in browsers that support CSP2, and `'nonce-abcdefg' 'strict-dynamic'` in browsers that support CSP3.
 
-<h2 id="Specifications">Specifications</h2>
+## Specifications
 
 {{Specifications}}
 
-<h2 id="Browser_compatibility">Browser compatibility</h2>
+## Browser compatibility
 
-<p>{{Compat}}</p>
+{{Compat}}
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
- <li>{{HTTPHeader("Content-Security-Policy")}}</li>
- <li>{{HTMLElement("script")}}</li>
- <li>{{CSP("script-src-elem")}}</li>
- <li>{{CSP("script-src-attr")}}</li>
-</ul>
+- {{HTTPHeader("Content-Security-Policy")}}
+- {{HTMLElement("script")}}
+- {{CSP("script-src-elem")}}
+- {{CSP("script-src-attr")}}
diff --git a/files/en-us/web/http/headers/content-security-policy/style-src-attr/index.md b/files/en-us/web/http/headers/content-security-policy/style-src-attr/index.md
index ca996ce44721aab..2a2a246fb93b27a 100644
--- a/files/en-us/web/http/headers/content-security-policy/style-src-attr/index.md
+++ b/files/en-us/web/http/headers/content-security-policy/style-src-attr/index.md
@@ -2,24 +2,24 @@
 title: 'CSP: style-src-attr'
 slug: Web/HTTP/Headers/Content-Security-Policy/style-src-attr
 tags:
-- CSP
-- Content
-- Content-Security-Policy
-- Directive
-- HTTP
-- Reference
-- Security
-- Style
-- source
-- style-src
-- style-src-attr
+  - CSP
+  - Content
+  - Content-Security-Policy
+  - Directive
+  - HTTP
+  - Reference
+  - Security
+  - Style
+  - source
+  - style-src
+  - style-src-attr
 browser-compat: http.headers.csp.Content-Security-Policy.style-src-attr
 ---
-<div>{{HTTPSidebar}}</div>
+{{HTTPSidebar}}
 
-<p>The HTTP {{HTTPHeader("Content-Security-Policy")}} (CSP)
-  <code><strong>style</strong></code><strong><code>-src-attr</code></strong> directive
-  specifies valid sources for inline styles applied to individual DOM elements.</p>
+The HTTP {{HTTPHeader("Content-Security-Policy")}} (CSP)
+**`style`\*\***`-src-attr`\*\* directive
+specifies valid sources for inline styles applied to individual DOM elements.
 
 <table class="properties">
   <tbody>
@@ -34,58 +34,57 @@ browser-compat: http.headers.csp.Content-Security-Policy.style-src-attr
     <tr>
       <th scope="row">{{CSP("default-src")}} fallback</th>
       <td>
-        <p>Yes. If this directive is absent, the user agent will look for
-          the {{CSP("style-src")}} directive, and if both of them are absent, fallback
-          to <code>default-src</code> directive.</p>
+        <p>
+          Yes. If this directive is absent, the user agent will look for
+          the {{CSP("style-src")}} directive, and if both of them are
+          absent, fallback to <code>default-src</code> directive.
+        </p>
       </td>
     </tr>
   </tbody>
 </table>
 
-<h2 id="Syntax">Syntax</h2>
+## Syntax
 
-<p>One or more sources can be allowed for the <code>style-src-attr</code> policy:</p>
+One or more sources can be allowed for the `style-src-attr` policy:
 
-<pre class="brush: html">Content-Security-Policy: style-src-attr &lt;source&gt;;
-Content-Security-Policy: style-src-attr &lt;source&gt; &lt;source&gt;;
-</pre>
+```html
+Content-Security-Policy: style-src-attr <source>;
+Content-Security-Policy: style-src-attr <source> <source>;
+```
 
-<p><code>style-src-attr</code> can be used in conjunction with {{CSP("style-src")}}:</p>
+`style-src-attr` can be used in conjunction with {{CSP("style-src")}}:
 
-<pre>Content-Security-Policy: <code>style</code>-src &lt;source&gt;;
-Content-Security-Policy: <code>style</code>-src-attr &lt;source&gt;;</pre>
+    Content-Security-Policy: style-src <source>;
+    Content-Security-Policy: style-src-attr <source>;
 
-<h3 id="Sources">Sources</h3>
+### Sources
 
-<p>{{page("Web/HTTP/Headers/Content-Security-Policy/connect-src", "Sources")}}</p>
+{{page("Web/HTTP/Headers/Content-Security-Policy/connect-src", "Sources")}}
 
-<dl>
-  <dt>'report-sample'</dt>
-  <dd>Requires a sample of the violating code to be included in the violation report.</dd>
-</dl>
+- 'report-sample'
+  - : Requires a sample of the violating code to be included in the violation report.
 
-<h2 id="Examples">Examples</h2>
+## Examples
 
-<p>TBD</p>
+TBD
 
-<h2 id="Specifications">Specifications</h2>
+## Specifications
 
 {{Specifications}}
 
-<h2 id="Browser_compatibility">Browser compatibility</h2>
+## Browser compatibility
 
-<p>{{Compat}}</p>
+{{Compat}}
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
-  <li>{{HTTPHeader("Content-Security-Policy")}}</li>
-  <li>{{CSP("style-src")}}</li>
-  <li>{{CSP("style-src-elem")}}</li>
-  <li>{{HTTPHeader("Link")}} header</li>
-  <li>{{HTMLElement("style")}}, {{HTMLElement("link")}}</li>
-  <li>{{cssxref("@import")}}</li>
-  <li>{{domxref("CSSStyleSheet.insertRule()")}}</li>
-  <li>{{domxref("CSSGroupingRule.insertRule()")}}</li>
-  <li>{{domxref("CSSStyleDeclaration.cssText")}}</li>
-</ul>
+- {{HTTPHeader("Content-Security-Policy")}}
+- {{CSP("style-src")}}
+- {{CSP("style-src-elem")}}
+- {{HTTPHeader("Link")}} header
+- {{HTMLElement("style")}}, {{HTMLElement("link")}}
+- {{cssxref("@import")}}
+- {{domxref("CSSStyleSheet.insertRule()")}}
+- {{domxref("CSSGroupingRule.insertRule()")}}
+- {{domxref("CSSStyleDeclaration.cssText")}}
diff --git a/files/en-us/web/http/headers/content-security-policy/style-src-elem/index.md b/files/en-us/web/http/headers/content-security-policy/style-src-elem/index.md
index c463042d402239b..c66392af4cc5e66 100644
--- a/files/en-us/web/http/headers/content-security-policy/style-src-elem/index.md
+++ b/files/en-us/web/http/headers/content-security-policy/style-src-elem/index.md
@@ -2,25 +2,25 @@
 title: 'CSP: style-src-elem'
 slug: Web/HTTP/Headers/Content-Security-Policy/style-src-elem
 tags:
-- CSP
-- Content
-- Content-Security-Policy
-- Directive
-- HTTP
-- Reference
-- Security
-- Style
-- source
-- style-src
-- style-src-elem
+  - CSP
+  - Content
+  - Content-Security-Policy
+  - Directive
+  - HTTP
+  - Reference
+  - Security
+  - Style
+  - source
+  - style-src
+  - style-src-elem
 browser-compat: http.headers.csp.Content-Security-Policy.style-src-elem
 ---
-<div>{{HTTPSidebar}}</div>
+{{HTTPSidebar}}
 
-<p>The HTTP {{HTTPHeader("Content-Security-Policy")}} (CSP)
-  <strong><code>style-src-elem</code></strong> directive
-  specifies valid sources for stylesheets {{HTMLElement("style")}} elements and
-  {{HTMLElement("link")}} elements with <code>rel="stylesheet"</code>.</p>
+The HTTP {{HTTPHeader("Content-Security-Policy")}} (CSP)
+**`style-src-elem`** directive
+specifies valid sources for stylesheets {{HTMLElement("style")}} elements and
+{{HTMLElement("link")}} elements with `rel="stylesheet"`.
 
 <table class="properties">
   <tbody>
@@ -35,58 +35,57 @@ browser-compat: http.headers.csp.Content-Security-Policy.style-src-elem
     <tr>
       <th scope="row">{{CSP("default-src")}} fallback</th>
       <td>
-        <p>Yes. If this directive is absent, the user agent will look for
-          the {{CSP("style-src")}} directive, and if both of them are absent, fallback
-          to <code>default-src</code> directive.</p>
+        <p>
+          Yes. If this directive is absent, the user agent will look for
+          the {{CSP("style-src")}} directive, and if both of them are
+          absent, fallback to <code>default-src</code> directive.
+        </p>
       </td>
     </tr>
   </tbody>
 </table>
 
-<h2 id="Syntax">Syntax</h2>
+## Syntax
 
-<p>One or more sources can be allowed for the <code>style-src-elem</code> policy:</p>
+One or more sources can be allowed for the `style-src-elem` policy:
 
-<pre class="brush: html">Content-Security-Policy: style-src-elem &lt;source&gt;;
-Content-Security-Policy: style-src-elem &lt;source&gt; &lt;source&gt;;
-</pre>
+```html
+Content-Security-Policy: style-src-elem <source>;
+Content-Security-Policy: style-src-elem <source> <source>;
+```
 
-<p><code>style-src-elem</code> can be used in conjunction with {{CSP("style-src")}}:</p>
+`style-src-elem` can be used in conjunction with {{CSP("style-src")}}:
 
-<pre>Content-Security-Policy: <code>style</code>-src &lt;source&gt;;
-Content-Security-Policy: <code>style</code>-src-elem &lt;source&gt;;</pre>
+    Content-Security-Policy: style-src <source>;
+    Content-Security-Policy: style-src-elem <source>;
 
-<h3 id="Sources">Sources</h3>
+### Sources
 
-<p>{{page("Web/HTTP/Headers/Content-Security-Policy/connect-src", "Sources")}}</p>
+{{page("Web/HTTP/Headers/Content-Security-Policy/connect-src", "Sources")}}
 
-<dl>
-  <dt>'report-sample'</dt>
-  <dd>Requires a sample of the violating code to be included in the violation report.</dd>
-</dl>
+- 'report-sample'
+  - : Requires a sample of the violating code to be included in the violation report.
 
-<h2 id="Examples">Examples</h2>
+## Examples
 
-<p>TBD</p>
+TBD
 
-<h2 id="Specifications">Specifications</h2>
+## Specifications
 
 {{Specifications}}
 
-<h2 id="Browser_compatibility">Browser compatibility</h2>
+## Browser compatibility
 
-<p>{{Compat}}</p>
+{{Compat}}
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
-  <li>{{HTTPHeader("Content-Security-Policy")}}</li>
-  <li>{{CSP("style-src")}}</li>
-  <li>{{CSP("style-src-attr")}}</li>
-  <li>{{HTTPHeader("Link")}} header</li>
-  <li>{{HTMLElement("style")}}, {{HTMLElement("link")}}</li>
-  <li>{{cssxref("@import")}}</li>
-  <li>{{domxref("CSSStyleSheet.insertRule()")}}</li>
-  <li>{{domxref("CSSGroupingRule.insertRule()")}}</li>
-  <li>{{domxref("CSSStyleDeclaration.cssText")}}</li>
-</ul>
+- {{HTTPHeader("Content-Security-Policy")}}
+- {{CSP("style-src")}}
+- {{CSP("style-src-attr")}}
+- {{HTTPHeader("Link")}} header
+- {{HTMLElement("style")}}, {{HTMLElement("link")}}
+- {{cssxref("@import")}}
+- {{domxref("CSSStyleSheet.insertRule()")}}
+- {{domxref("CSSGroupingRule.insertRule()")}}
+- {{domxref("CSSStyleDeclaration.cssText")}}
diff --git a/files/en-us/web/http/headers/content-security-policy/style-src/index.md b/files/en-us/web/http/headers/content-security-policy/style-src/index.md
index e8492dde37879a1..5d97bc3ec9dec58 100644
--- a/files/en-us/web/http/headers/content-security-policy/style-src/index.md
+++ b/files/en-us/web/http/headers/content-security-policy/style-src/index.md
@@ -14,150 +14,170 @@ tags:
   - style-src
 browser-compat: http.headers.csp.Content-Security-Policy.style-src
 ---
-<div>{{HTTPSidebar}}</div>
+{{HTTPSidebar}}
 
-<p>The HTTP {{HTTPHeader("Content-Security-Policy")}} (CSP) <strong><code>style-src</code></strong> directive specifies valid sources for stylesheets.</p>
+The HTTP {{HTTPHeader("Content-Security-Policy")}} (CSP) **`style-src`** directive specifies valid sources for stylesheets.
 
 <table class="properties">
- <tbody>
-  <tr>
-   <th scope="row">CSP version</th>
-   <td>1</td>
-  </tr>
-  <tr>
-   <th scope="row">Directive type</th>
-   <td>{{Glossary("Fetch directive")}}</td>
-  </tr>
-  <tr>
-   <th scope="row">{{CSP("default-src")}} fallback</th>
-   <td>Yes. If this directive is absent, the user agent will look for the <code>default-src</code> directive.</td>
-  </tr>
- </tbody>
+  <tbody>
+    <tr>
+      <th scope="row">CSP version</th>
+      <td>1</td>
+    </tr>
+    <tr>
+      <th scope="row">Directive type</th>
+      <td>{{Glossary("Fetch directive")}}</td>
+    </tr>
+    <tr>
+      <th scope="row">{{CSP("default-src")}} fallback</th>
+      <td>
+        Yes. If this directive is absent, the user agent will look for the
+        <code>default-src</code> directive.
+      </td>
+    </tr>
+  </tbody>
 </table>
 
-<h2 id="Syntax">Syntax</h2>
+## Syntax
 
-<p>One or more sources can be allowed for the <code>style-src</code> policy:</p>
+One or more sources can be allowed for the `style-src` policy:
 
-<pre class="brush: html">Content-Security-Policy: style-src &lt;source&gt;;
-Content-Security-Policy: style-src &lt;source&gt; &lt;source&gt;;
-</pre>
+```html
+Content-Security-Policy: style-src <source>;
+Content-Security-Policy: style-src <source> <source>;
+```
 
-<h3 id="Sources">Sources</h3>
+### Sources
 
-<p>{{page("Web/HTTP/Headers/Content-Security-Policy/connect-src", "Sources")}}</p>
+{{page("Web/HTTP/Headers/Content-Security-Policy/connect-src", "Sources")}}
 
-<h2 id="Examples">Examples</h2>
+## Examples
 
-<h3 id="Violation_cases">Violation cases</h3>
+### Violation cases
 
-<p>Given this CSP header:</p>
+Given this CSP header:
 
-<pre class="brush: bash">Content-Security-Policy: style-src https://example.com/</pre>
+```bash
+Content-Security-Policy: style-src https://example.com/
+```
 
-<p>the following stylesheets are blocked and won't load:</p>
+the following stylesheets are blocked and won't load:
 
-<pre class="brush: html">&lt;link href="https://not-example.com/styles/main.css" rel="stylesheet" type="text/css" /&gt;
+```html
+<link href="https://not-example.com/styles/main.css" rel="stylesheet" type="text/css" />
 
-&lt;style&gt;
+<style>
 #inline-style { background: red; }
-&lt;/style&gt;
+</style>
 
-&lt;style&gt;
+<style>
   @import url("https://not-example.com/styles/print.css") print;
-&lt;/style&gt;</pre>
+</style>
+```
 
-<p>as well as styles loaded using the {{HTTPHeader("Link")}} header:</p>
+as well as styles loaded using the {{HTTPHeader("Link")}} header:
 
-<pre class="brush: bash">Link: &lt;https://not-example.com/styles/stylesheet.css&gt;;rel=stylesheet
-</pre>
+```bash
+Link: <https://not-example.com/styles/stylesheet.css>;rel=stylesheet
+```
 
-<p>Inline style attributes are also blocked:</p>
+Inline style attributes are also blocked:
 
-<pre class="brush: html">&lt;div style="display:none"&gt;Foo&lt;/div&gt;</pre>
+```html
+<div style="display:none">Foo</div>
+```
 
-<p>As well as styles that are applied in JavaScript by setting the <code>style</code> attribute directly, or by setting {{domxref("CSSStyleDeclaration.cssText", "cssText")}}:</p>
+As well as styles that are applied in JavaScript by setting the `style` attribute directly, or by setting {{domxref("CSSStyleDeclaration.cssText", "cssText")}}:
 
-<pre class="brush: js">document.querySelector('div').setAttribute('style', 'display:none;');
-document.querySelector('div').style.cssText = 'display:none;';</pre>
+```js
+document.querySelector('div').setAttribute('style', 'display:none;');
+document.querySelector('div').style.cssText = 'display:none;';
+```
 
-<p>However, styles properties that are set directly on the element's {{domxref("HTMLElement/style", "style")}} property will not be blocked, allowing users to safely manipulate styles via JavaScript:</p>
+However, styles properties that are set directly on the element's {{domxref("HTMLElement/style", "style")}} property will not be blocked, allowing users to safely manipulate styles via JavaScript:
 
-<pre class="brush: js">document.querySelector('div').style.display = 'none';</pre>
+```js
+document.querySelector('div').style.display = 'none';
+```
 
-<p>These types of manipulations can be prevented by disallowing Javascript via the {{CSP("script-src")}} CSP directive.</p>
+These types of manipulations can be prevented by disallowing Javascript via the {{CSP("script-src")}} CSP directive.
 
-<h3 id="Unsafe_inline_styles">Unsafe inline styles</h3>
+### Unsafe inline styles
 
-<div class="notecard note">
-  <p><strong>Note:</strong> Disallowing inline styles and inline scripts is one of the biggest security wins CSP provides. However, if you absolutely have to use it, there are a few mechanisms that will allow them.</p>
-</div>
+> **Note:** Disallowing inline styles and inline scripts is one of the biggest security wins CSP provides. However, if you absolutely have to use it, there are a few mechanisms that will allow them.
 
-<p>To allow inline styles, <code>'unsafe-inline'</code>, a nonce-source or a hash-source that matches the inline block can be specified.</p>
+To allow inline styles, `'unsafe-inline'`, a nonce-source or a hash-source that matches the inline block can be specified.
 
-<pre class="brush: bash">Content-Security-Policy: style-src 'unsafe-inline';
-</pre>
+```bash
+Content-Security-Policy: style-src 'unsafe-inline';
+```
 
-<p>The above Content Security Policy will allow inline styles like the {{HTMLElement("style")}} element, and the <code>style</code> attribute on any element:</p>
+The above Content Security Policy will allow inline styles like the {{HTMLElement("style")}} element, and the `style` attribute on any element:
 
-<pre class="brush: html">&lt;style&gt;
+```html
+<style>
   #inline-style { background: red; }
-&lt;/style&gt;
+</style>
 
-&lt;div style="display:none"&gt;Foo&lt;/div&gt;
-</pre>
+<div style="display:none">Foo</div>
+```
 
-<p>You can use a nonce-source to only allow specific inline style blocks:</p>
+You can use a nonce-source to only allow specific inline style blocks:
 
-<pre class="brush: bash">Content-Security-Policy: style-src 'nonce-2726c7f26c'</pre>
+```bash
+Content-Security-Policy: style-src 'nonce-2726c7f26c'
+```
 
-<p>You will have to set the same nonce on the {{HTMLElement("style")}} element:</p>
+You will have to set the same nonce on the {{HTMLElement("style")}} element:
 
-<pre class="brush: html">&lt;style nonce="2726c7f26c"&gt;
+```html
+<style nonce="2726c7f26c">
   #inline-style { background: red; }
-&lt;/style&gt;
-</pre>
+</style>
+```
 
-<p>Alternatively, you can create hashes from your inline styles. CSP supports sha256, sha384 and sha512. The <strong>binary</strong> form of the hash has to be encoded with base64. You can obtain the hash of a string on the command line via the <code>openssl</code> program:</p>
+Alternatively, you can create hashes from your inline styles. CSP supports sha256, sha384 and sha512. The **binary** form of the hash has to be encoded with base64. You can obtain the hash of a string on the command line via the `openssl` program:
 
-<pre class="brush: bash">echo -n "#inline-style { background: red; }" | openssl dgst -sha256 -binary | openssl enc -base64</pre>
+```bash
+echo -n "#inline-style { background: red; }" | openssl dgst -sha256 -binary | openssl enc -base64
+```
 
-<p>You can use a hash-source to only allow specific inline style blocks:</p>
+You can use a hash-source to only allow specific inline style blocks:
 
-<pre class="brush: bash">Content-Security-Policy: style-src 'sha256-ozBpjL6dxO8fsS4u6fwG1dFDACYvpNxYeBA6tzR+FY8='</pre>
+```bash
+Content-Security-Policy: style-src 'sha256-ozBpjL6dxO8fsS4u6fwG1dFDACYvpNxYeBA6tzR+FY8='
+```
 
-<p>When generating the hash, don't include the {{HTMLElement("style")}} tags and note that capitalization and whitespace matter, including leading or trailing whitespace.</p>
+When generating the hash, don't include the {{HTMLElement("style")}} tags and note that capitalization and whitespace matter, including leading or trailing whitespace.
 
-<pre class="brush: html">&lt;style&gt;#inline-style { background: red; }&lt;/style&gt;</pre>
+```html
+<style>#inline-style { background: red; }</style>
+```
 
-<h3 id="Unsafe_style_expressions">Unsafe style expressions</h3>
+### Unsafe style expressions
 
-<p>The <code>'unsafe-eval'</code> source expression controls several style methods that create style declarations from strings. If <code>'unsafe-eval'</code> isn't specified with the <code>style-src</code> directive, the following methods are blocked and won't have any effect:</p>
+The `'unsafe-eval'` source expression controls several style methods that create style declarations from strings. If `'unsafe-eval'` isn't specified with the `style-src` directive, the following methods are blocked and won't have any effect:
 
-<ul>
- <li>{{domxref("CSSStyleSheet.insertRule()")}}</li>
- <li>{{domxref("CSSGroupingRule.insertRule()")}}</li>
- <li>{{domxref("CSSStyleDeclaration.cssText")}}</li>
-</ul>
+- {{domxref("CSSStyleSheet.insertRule()")}}
+- {{domxref("CSSGroupingRule.insertRule()")}}
+- {{domxref("CSSStyleDeclaration.cssText")}}
 
-<h2 id="Specifications">Specifications</h2>
+## Specifications
 
 {{Specifications}}
 
-<h2 id="Browser_compatibility">Browser compatibility</h2>
+## Browser compatibility
 
-<p>{{Compat}}</p>
+{{Compat}}
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
- <li>{{HTTPHeader("Content-Security-Policy")}}</li>
- <li>{{CSP("style-src-elem")}}</li>
- <li>{{CSP("style-src-attr")}}</li>
- <li>{{HTTPHeader("Link")}} header</li>
- <li>{{HTMLElement("style")}}, {{HTMLElement("link")}}</li>
- <li>{{cssxref("@import")}}</li>
- <li>{{domxref("CSSStyleSheet.insertRule()")}}</li>
- <li>{{domxref("CSSGroupingRule.insertRule()")}}</li>
- <li>{{domxref("CSSStyleDeclaration.cssText")}}</li>
-</ul>
+- {{HTTPHeader("Content-Security-Policy")}}
+- {{CSP("style-src-elem")}}
+- {{CSP("style-src-attr")}}
+- {{HTTPHeader("Link")}} header
+- {{HTMLElement("style")}}, {{HTMLElement("link")}}
+- {{cssxref("@import")}}
+- {{domxref("CSSStyleSheet.insertRule()")}}
+- {{domxref("CSSGroupingRule.insertRule()")}}
+- {{domxref("CSSStyleDeclaration.cssText")}}
diff --git a/files/en-us/web/http/headers/content-security-policy/trusted-types/index.md b/files/en-us/web/http/headers/content-security-policy/trusted-types/index.md
index 60f8f0e83e2355c..5a2d4b7fbf9e87c 100644
--- a/files/en-us/web/http/headers/content-security-policy/trusted-types/index.md
+++ b/files/en-us/web/http/headers/content-security-policy/trusted-types/index.md
@@ -8,57 +8,53 @@ tags:
   - Security
 browser-compat: http.headers.csp.Content-Security-Policy.trusted-types
 ---
-<div>{{HTTPSidebar}}</div>
+{{HTTPSidebar}}
 
-<p>The HTTP {{HTTPHeader("Content-Security-Policy")}} (CSP) <code><strong>trusted-types</strong></code> {{experimental_inline}} directive instructs user agents to restrict the creation of Trusted Types policies - functions that build non-spoofable, typed values intended to be passed to DOM XSS sinks in place of strings.</p>
+The HTTP {{HTTPHeader("Content-Security-Policy")}} (CSP) **`trusted-types`** {{experimental_inline}} directive instructs user agents to restrict the creation of Trusted Types policies - functions that build non-spoofable, typed values intended to be passed to DOM XSS sinks in place of strings.
 
-<p>Together with <strong><a href="/en-US/docs/Web/HTTP/Headers/Content-Security-Policy/require-trusted-types-for"><code>require-trusted-types-for</code></a></strong> directive, this allows authors to define rules guarding writing values to the DOM and thus reducing the DOM XSS attack surface to small, isolated parts of the web application codebase, facilitating their monitoring and code review. This directive declares an allow-list of trusted type policy names created with <code>TrustedTypes.createPolicy</code> from Trusted Types API.</p>
+Together with **[`require-trusted-types-for`](/en-US/docs/Web/HTTP/Headers/Content-Security-Policy/require-trusted-types-for)** directive, this allows authors to define rules guarding writing values to the DOM and thus reducing the DOM XSS attack surface to small, isolated parts of the web application codebase, facilitating their monitoring and code review. This directive declares an allow-list of trusted type policy names created with `TrustedTypes.createPolicy` from Trusted Types API.
 
-<h2 id="Syntax">Syntax</h2>
+## Syntax
 
-<pre>Content-Security-Policy: trusted-types;
-Content-Security-Policy: trusted-types 'none';
-Content-Security-Policy: trusted-types &lt;policyName&gt;;
-Content-Security-Policy: trusted-types &lt;policyName&gt; &lt;policyName&gt; 'allow-duplicates';
-</pre>
+    Content-Security-Policy: trusted-types;
+    Content-Security-Policy: trusted-types 'none';
+    Content-Security-Policy: trusted-types <policyName>;
+    Content-Security-Policy: trusted-types <policyName> <policyName> 'allow-duplicates';
 
-<dl>
- <dt>&lt;policyName&gt;</dt>
- <dd>A valid policy name consists only of alphanumeric characters, or one of "<code>-#=_/@.%</code>".  A star (<code>*</code>) as a policy name instructs the user agent to allow any unique policy name ('<code>allow-duplicates</code>' may relax that further).</dd>
- <dt><code>'none'</code></dt>
- <dd>Disallows creating any Trusted Type policy (same as not specifying any <em>&lt;policyName&gt;</em>).</dd>
- <dt><code>'allow-duplicates'</code></dt>
- <dd>Allows for creating policies with a name that was already used.</dd>
-</dl>
+- \<policyName>
+  - : A valid policy name consists only of alphanumeric characters, or one of "`-#=_/@.%`".  A star (`*`) as a policy name instructs the user agent to allow any unique policy name ('`allow-duplicates`' may relax that further).
+- `'none'`
+  - : Disallows creating any Trusted Type policy (same as not specifying any _\<policyName>_).
+- `'allow-duplicates'`
+  - : Allows for creating policies with a name that was already used.
 
-<h2 id="Examples">Examples</h2>
+## Examples
 
-<pre class="brush: js">// Content-Security-Policy: trusted-types foo bar 'allow-duplicates';
+```js
+// Content-Security-Policy: trusted-types foo bar 'allow-duplicates';
 
 if (typeof trustedTypes !== 'undefined') {
   const policyFoo = trustedTypes.createPolicy('foo', {});
   const policyFoo2 = trustedTypes.createPolicy('foo', {});
   const policyBaz = trustedTypes.createPolicy('baz', {}); // Throws and dispatches a SecurityPolicyViolationEvent.
 }
-</pre>
+```
 
-<h2 id="Polyfill">Polyfill</h2>
+## Polyfill
 
-<p>A <a href="https://github.com/w3c/webappsec-trusted-types#polyfill">polyfill for Trusted Types</a> is available on Github.</p>
+A [polyfill for Trusted Types](https://github.com/w3c/webappsec-trusted-types#polyfill) is available on Github.
 
-<h2 id="Specifications">Specifications</h2>
+## Specifications
 
 {{Specifications}}
 
-<h2 id="Browser_compatibility">Browser compatibility</h2>
+## Browser compatibility
 
-<p>{{Compat}}</p>
+{{Compat}}
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
- <li>{{HTTPHeader("Content-Security-Policy")}}</li>
- <li><a href="/en-US/docs/Glossary/Cross-site_scripting">Cross-Site Scripting (XSS)</a></li>
- <li><a href="https://web.dev/trusted-types">Prevent DOM-based cross-site scripting vulnerabilities with Trusted Types</a></li>
- <li>Trusted Types with <a href="https://github.com/cure53/DOMPurify#what-about-dompurify-and-trusted-types">DOMPurify</a> XSS sanitizer</li>
-</ul>
+- {{HTTPHeader("Content-Security-Policy")}}
+- [Cross-Site Scripting (XSS)](/en-US/docs/Glossary/Cross-site_scripting)
+- [Prevent DOM-based cross-site scripting vulnerabilities with Trusted Types](https://web.dev/trusted-types)
+- Trusted Types with [DOMPurify](https://github.com/cure53/DOMPurify#what-about-dompurify-and-trusted-types) XSS sanitizer
diff --git a/files/en-us/web/http/headers/content-security-policy/upgrade-insecure-requests/index.md b/files/en-us/web/http/headers/content-security-policy/upgrade-insecure-requests/index.md
index c690cf14169a9fb..6dc48aca3a772bf 100644
--- a/files/en-us/web/http/headers/content-security-policy/upgrade-insecure-requests/index.md
+++ b/files/en-us/web/http/headers/content-security-policy/upgrade-insecure-requests/index.md
@@ -2,100 +2,102 @@
 title: 'CSP: upgrade-insecure-requests'
 slug: Web/HTTP/Headers/Content-Security-Policy/upgrade-insecure-requests
 tags:
-- CSP
-- Content-Security-Policy
-- Directive
-- HTTP
-- Reference
-- Requests
-- Security
-- Upgrade
-- upgrade-insecure-requests
+  - CSP
+  - Content-Security-Policy
+  - Directive
+  - HTTP
+  - Reference
+  - Requests
+  - Security
+  - Upgrade
+  - upgrade-insecure-requests
 browser-compat: http.headers.csp.Content-Security-Policy.upgrade-insecure-requests
 ---
-<div>{{HTTPSidebar}}</div>
-
-<p>The HTTP {{HTTPHeader("Content-Security-Policy")}} (CSP)
-	<code><strong>upgrade-insecure-requests</strong></code> directive instructs user
-	agents to treat all of a site's insecure URLs (those served over HTTP) as though they
-	have been replaced with secure URLs (those served over HTTPS). This directive is
-	intended for web sites with large numbers of insecure legacy URLs that need to be
-	rewritten.</p>
-
-<div class="notecard note">
-  <p><strong>Note:</strong> The <code>upgrade-insecure-requests</code> directive is evaluated before
-	  {{CSP("block-all-mixed-content")}} and if it is set, the latter is effectively a
-	  no-op. It is recommended to set either directive, but not both, unless you want to
-	  force HTTPS on older browsers that do not force it after a redirect to HTTP.</p>
-</div>
-
-<p>The <code>upgrade-insecure-requests</code> directive will not ensure that users
-	visiting your site via links on third-party sites will be upgraded to HTTPS for the
-	top-level navigation and thus does not replace the
-	{{HTTPHeader("Strict-Transport-Security")}} ({{Glossary("HSTS")}}) header, which
-	should still be set with an appropriate <code>max-age</code> to ensure that users are
-	not subject to SSL stripping attacks.</p>
-
-<h2 id="Syntax">Syntax</h2>
-
-<pre
-	class="brush: html">Content-Security-Policy: upgrade-insecure-requests;</pre>
+{{HTTPSidebar}}
+
+The HTTP {{HTTPHeader("Content-Security-Policy")}} (CSP)
+**`upgrade-insecure-requests`** directive instructs user
+agents to treat all of a site's insecure URLs (those served over HTTP) as though they
+have been replaced with secure URLs (those served over HTTPS). This directive is
+intended for web sites with large numbers of insecure legacy URLs that need to be
+rewritten.
+
+> **Note:** The `upgrade-insecure-requests` directive is evaluated before
+> {{CSP("block-all-mixed-content")}} and if it is set, the latter is effectively a
+> no-op. It is recommended to set either directive, but not both, unless you want to
+> force HTTPS on older browsers that do not force it after a redirect to HTTP.
+
+The `upgrade-insecure-requests` directive will not ensure that users
+visiting your site via links on third-party sites will be upgraded to HTTPS for the
+top-level navigation and thus does not replace the
+{{HTTPHeader("Strict-Transport-Security")}} ({{Glossary("HSTS")}}) header, which
+should still be set with an appropriate `max-age` to ensure that users are
+not subject to SSL stripping attacks.
+
+## Syntax
+
+```html
+Content-Security-Policy: upgrade-insecure-requests;
+```
 
-<h2 id="Examples">Examples</h2>
+## Examples
 
-<pre>// header
-Content-Security-Policy: upgrade-insecure-requests;
+    // header
+    Content-Security-Policy: upgrade-insecure-requests;
 
-// meta tag
-&lt;meta http-equiv="Content-Security-Policy" content="upgrade-insecure-requests"&gt;
-</pre>
+    // meta tag
+    <meta http-equiv="Content-Security-Policy" content="upgrade-insecure-requests">
 
-<p>With the above header set on a domain example.com that wants to migrate from HTTP to
-	HTTPS, non-navigational insecure resource requests are automatically upgraded
-	(first-party as well as third-party requests).</p>
+With the above header set on a domain example.com that wants to migrate from HTTP to
+HTTPS, non-navigational insecure resource requests are automatically upgraded
+(first-party as well as third-party requests).
 
-<pre class="brush: html">&lt;img src="http://example.com/image.png"&gt;
-&lt;img src="http://not-example.com/image.png"&gt;</pre>
+```html
+<img src="http://example.com/image.png">
+<img src="http://not-example.com/image.png">
+```
 
-<p>These URLs will be rewritten before the request is made, meaning that no insecure
-	requests will hit the network. Note that, if the requested resource is not actually
-	available via HTTPS, the request will fail without any fallback to HTTP.</p>
+These URLs will be rewritten before the request is made, meaning that no insecure
+requests will hit the network. Note that, if the requested resource is not actually
+available via HTTPS, the request will fail without any fallback to HTTP.
 
-<pre class="brush: html">&lt;img src="https://example.com/image.png"&gt;
-&lt;img src="https://not-example.com/image.png"&gt;</pre>
+```html
+<img src="https://example.com/image.png">
+<img src="https://not-example.com/image.png">
+```
 
-<p>Navigational upgrades to third-party resources brings a significantly higher potential
-	for breakage, these are not upgraded:</p>
+Navigational upgrades to third-party resources brings a significantly higher potential
+for breakage, these are not upgraded:
 
-<pre class="brush: html">&lt;a href="https://example.com/"&gt;Home&lt;/a&gt;
-&lt;a href="http://not-example.com/"&gt;Home&lt;/a&gt;</pre>
+```html
+<a href="https://example.com/">Home</a>
+<a href="http://not-example.com/">Home</a>
+```
 
-<h3 id="Finding_insecure_requests">Finding insecure requests</h3>
+### Finding insecure requests
 
-<p>With the help of the {{HTTPHeader("Content-Security-Policy-Report-Only")}} header and
-	the {{CSP("report-uri")}} directive, you can set-up an enforced policy and a reported
-	policy like this:</p>
+With the help of the {{HTTPHeader("Content-Security-Policy-Report-Only")}} header and
+the {{CSP("report-uri")}} directive, you can set-up an enforced policy and a reported
+policy like this:
 
-<pre>Content-Security-Policy: upgrade-insecure-requests; default-src https:
-Content-Security-Policy-Report-Only: default-src https:; report-uri /endpoint</pre>
+    Content-Security-Policy: upgrade-insecure-requests; default-src https:
+    Content-Security-Policy-Report-Only: default-src https:; report-uri /endpoint
 
-<p>That way, you still upgrade insecure requests on your secure site, but the only
-	monitoring policy is violated and reports insecure resources to your endpoint.</p>
+That way, you still upgrade insecure requests on your secure site, but the only
+monitoring policy is violated and reports insecure resources to your endpoint.
 
-<h2 id="Specifications">Specifications</h2>
+## Specifications
 
 {{Specifications}}
 
-<h2 id="Browser_compatibility">Browser compatibility</h2>
+## Browser compatibility
 
-<p>{{Compat}}</p>
+{{Compat}}
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
-	<li>{{HTTPHeader("Content-Security-Policy")}}</li>
-	<li>{{HTTPHeader("Upgrade-Insecure-Requests")}} header</li>
-	<li>{{HTTPHeader("Strict-Transport-Security")}} ({{Glossary("HSTS")}}) header</li>
-	<li>{{CSP("block-all-mixed-content")}}</li>
-	<li><a href="/en-US/docs/Web/Security/Mixed_content">Mixed content</a></li>
-</ul>
+- {{HTTPHeader("Content-Security-Policy")}}
+- {{HTTPHeader("Upgrade-Insecure-Requests")}} header
+- {{HTTPHeader("Strict-Transport-Security")}} ({{Glossary("HSTS")}}) header
+- {{CSP("block-all-mixed-content")}}
+- [Mixed content](/en-US/docs/Web/Security/Mixed_content)
diff --git a/files/en-us/web/http/headers/content-security-policy/worker-src/index.md b/files/en-us/web/http/headers/content-security-policy/worker-src/index.md
index 21e1614e7d228ab..4562bd9218cbfda 100644
--- a/files/en-us/web/http/headers/content-security-policy/worker-src/index.md
+++ b/files/en-us/web/http/headers/content-security-policy/worker-src/index.md
@@ -10,12 +10,12 @@ tags:
   - Security
 browser-compat: http.headers.csp.Content-Security-Policy.worker-src
 ---
-<div>{{HTTPSidebar}}</div>
+{{HTTPSidebar}}
 
-<p>The HTTP {{HTTPHeader("Content-Security-Policy")}} (CSP)
-  <code><strong>worker-src</strong></code> directive specifies valid sources for
-  {{domxref("Worker")}}, {{domxref("SharedWorker")}}, or {{domxref("ServiceWorker")}}
-  scripts.</p>
+The HTTP {{HTTPHeader("Content-Security-Policy")}} (CSP)
+**`worker-src`** directive specifies valid sources for
+{{domxref("Worker")}}, {{domxref("SharedWorker")}}, or {{domxref("ServiceWorker")}}
+scripts.
 
 <table class="properties">
   <tbody>
@@ -30,60 +30,64 @@ browser-compat: http.headers.csp.Content-Security-Policy.worker-src
     <tr>
       <th scope="row">Fallback</th>
       <td>
-        <p>If this directive is absent, the user agent will first look for the
-          {{CSP("child-src")}} directive, then the {{CSP("script-src")}} directive, then
-          finally for the {{CSP("default-src")}} directive, when governing worker
-          execution.</p>
+        <p>
+          If this directive is absent, the user agent will first look for the
+          {{CSP("child-src")}} directive, then the
+          {{CSP("script-src")}} directive, then finally for the
+          {{CSP("default-src")}} directive, when governing worker
+          execution.
         </p>
+        <p></p>
       </td>
     </tr>
   </tbody>
 </table>
 
-<h2 id="Syntax">Syntax</h2>
+## Syntax
 
-<p>One or more sources can be allowed for the <code>worker-src</code> policy:</p>
+One or more sources can be allowed for the `worker-src` policy:
 
-<pre class="brush: html">Content-Security-Policy: worker-src &lt;source&gt;;
-Content-Security-Policy: worker-src &lt;source&gt; &lt;source&gt;;
-</pre>
+```html
+Content-Security-Policy: worker-src <source>;
+Content-Security-Policy: worker-src <source> <source>;
+```
 
-<h3 id="Sources">Sources</h3>
+### Sources
 
-<p>{{page("Web/HTTP/Headers/Content-Security-Policy/connect-src", "Sources")}}</p>
+{{page("Web/HTTP/Headers/Content-Security-Policy/connect-src", "Sources")}}
 
-<h2 id="Examples">Examples</h2>
+## Examples
 
-<h3 id="Violation_cases">Violation cases</h3>
+### Violation cases
 
-<p>Given this CSP header:</p>
+Given this CSP header:
 
-<pre class="brush: bash">Content-Security-Policy: worker-src https://example.com/</pre>
+```bash
+Content-Security-Policy: worker-src https://example.com/
+```
 
-<p>{{domxref("Worker")}}, {{domxref("SharedWorker")}}, {{domxref("ServiceWorker")}} are
-  blocked and won't load:</p>
+{{domxref("Worker")}}, {{domxref("SharedWorker")}}, {{domxref("ServiceWorker")}} are
+blocked and won't load:
 
-<pre class="brush: html">&lt;script&gt;
+```html
+<script>
   var blockedWorker = new Worker("data:application/javascript,...");
   blockedWorker = new SharedWorker("https://not-example.com/");
   navigator.serviceWorker.register('https://not-example.com/sw.js');
-&lt;/script&gt;</pre>
+</script>
+```
 
-<h2 id="Specifications">Specifications</h2>
+## Specifications
 
 {{Specifications}}
 
-<h2 id="Browser_compatibility">Browser compatibility</h2>
+## Browser compatibility
 
-<p>{{Compat}}</p>
+{{Compat}}
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
-  <li>{{HTTPHeader("Content-Security-Policy")}}</li>
-  <li><a
-      href="/en-US/docs/Web/API/Web_Workers_API/Using_web_workers#content_security_policy">CSP
-      for Web Workers</a></li>
-  <li>{{domxref("Worker")}}, {{domxref("SharedWorker")}}, {{domxref("ServiceWorker")}}
-  </li>
-</ul>
+- {{HTTPHeader("Content-Security-Policy")}}
+- [CSP
+  for Web Workers](/en-US/docs/Web/API/Web_Workers_API/Using_web_workers#content_security_policy)
+- {{domxref("Worker")}}, {{domxref("SharedWorker")}}, {{domxref("ServiceWorker")}}
diff --git a/files/en-us/web/http/headers/content-type/index.md b/files/en-us/web/http/headers/content-type/index.md
index fb2e1a762c7b6f6..3529cfaf1fc6284 100644
--- a/files/en-us/web/http/headers/content-type/index.md
+++ b/files/en-us/web/http/headers/content-type/index.md
@@ -9,97 +9,104 @@ tags:
   - Reference
 browser-compat: http.headers.Content-Type
 ---
-<div>{{HTTPSidebar}}</div>
+{{HTTPSidebar}}
 
-<p>The <strong><code>Content-Type</code></strong> representation header is used to indicate the original {{Glossary("MIME type","media type")}} of the resource (prior to any content encoding applied for sending).</p>
+The **`Content-Type`** representation header is used to indicate the original {{Glossary("MIME type","media type")}} of the resource (prior to any content encoding applied for sending).
 
-<p>In responses, a <code>Content-Type</code> header tells the client what the content type of the returned content actually is. Browsers will do MIME sniffing in some cases and will not necessarily follow the value of this header; to prevent this behavior, the header {{HTTPHeader("X-Content-Type-Options")}} can be set to <code>nosniff</code>.</p>
+In responses, a `Content-Type` header tells the client what the content type of the returned content actually is. Browsers will do MIME sniffing in some cases and will not necessarily follow the value of this header; to prevent this behavior, the header {{HTTPHeader("X-Content-Type-Options")}} can be set to `nosniff`.
 
-<p>In requests, (such as {{HTTPMethod("POST")}} or {{HTTPMethod("PUT")}}), the client tells the server what type of data is actually sent.</p>
+In requests, (such as {{HTTPMethod("POST")}} or {{HTTPMethod("PUT")}}), the client tells the server what type of data is actually sent.
 
 <table class="properties">
- <tbody>
-  <tr>
-   <th scope="row">Header type</th>
-   <td>{{Glossary("Representation header")}}</td>
-  </tr>
-  <tr>
-   <th scope="row">{{Glossary("Forbidden header name")}}</th>
-   <td>no</td>
-  </tr>
-  <tr>
-   <th scope="row">{{Glossary("CORS-safelisted response header")}}</th>
-   <td>yes</td>
-  </tr>
-  <tr>
-   <th scope="row">{{Glossary("CORS-safelisted request header")}}</th>
-   <td>yes, with the additional restriction that values can't contain a <em>CORS-unsafe request header byte</em>: 0x00-0x1F (except 0x09 (HT)), <code>"():&lt;&gt;?@[\]{}</code>, and 0x7F (DEL).<br>
-    It also needs to have a MIME type of its parsed value (ignoring parameters) of either <code>application/x-www-form-urlencoded</code>, <code>multipart/form-data</code>, or <code>text/plain</code>.</td>
-  </tr>
- </tbody>
+  <tbody>
+    <tr>
+      <th scope="row">Header type</th>
+      <td>{{Glossary("Representation header")}}</td>
+    </tr>
+    <tr>
+      <th scope="row">{{Glossary("Forbidden header name")}}</th>
+      <td>no</td>
+    </tr>
+    <tr>
+      <th scope="row">
+        {{Glossary("CORS-safelisted response header")}}
+      </th>
+      <td>yes</td>
+    </tr>
+    <tr>
+      <th scope="row">
+        {{Glossary("CORS-safelisted request header")}}
+      </th>
+      <td>
+        yes, with the additional restriction that values can't contain a
+        <em>CORS-unsafe request header byte</em>: 0x00-0x1F (except 0x09 (HT)),
+        <code>"():&#x3C;>?@[\]{}</code>, and 0x7F (DEL).<br />It also needs to
+        have a MIME type of its parsed value (ignoring parameters) of either
+        <code>application/x-www-form-urlencoded</code>,
+        <code>multipart/form-data</code>, or <code>text/plain</code>.
+      </td>
+    </tr>
+  </tbody>
 </table>
 
-<h2 id="Syntax">Syntax</h2>
+## Syntax
 
-<pre class="brush: html">Content-Type: text/html; charset=UTF-8
+```html
+Content-Type: text/html; charset=UTF-8
 Content-Type: multipart/form-data; boundary=something
-</pre>
+```
 
-<h2 id="Directives">Directives</h2>
+## Directives
 
-<dl>
- <dt><code>media-type</code></dt>
- <dd>The <a href="/en-US/docs/Web/HTTP/Basics_of_HTTP/MIME_types">MIME type</a> of the resource or the data.</dd>
- <dt>charset</dt>
- <dd>The character encoding standard.</dd>
- <dt>boundary</dt>
- <dd>For multipart entities the <code>boundary</code> directive is required, which consists of 1 to 70 characters from a set of characters known to be very robust through email gateways, and not ending with white space. It is used to encapsulate the boundaries of the multiple parts of the message. Often, the header boundary is prepended with two dashes and the final boundary has two dashes appended at the end.</dd>
-</dl>
+- `media-type`
+  - : The [MIME type](/en-US/docs/Web/HTTP/Basics_of_HTTP/MIME_types) of the resource or the data.
+- charset
+  - : The character encoding standard.
+- boundary
+  - : For multipart entities the `boundary` directive is required, which consists of 1 to 70 characters from a set of characters known to be very robust through email gateways, and not ending with white space. It is used to encapsulate the boundaries of the multiple parts of the message. Often, the header boundary is prepended with two dashes and the final boundary has two dashes appended at the end.
 
-<h2 id="Examples">Examples</h2>
+## Examples
 
-<h3 id="Content-Type_in_HTML_forms"><code>Content-Type</code> in HTML forms</h3>
+### `Content-Type` in HTML forms
 
-<p>In a {{HTTPMethod("POST")}} request, resulting from an HTML form submission, the <code>Content-Type</code> of the request is specified by the <code>enctype</code> attribute on the {{HTMLElement("form")}} element.</p>
+In a {{HTTPMethod("POST")}} request, resulting from an HTML form submission, the `Content-Type` of the request is specified by the `enctype` attribute on the {{HTMLElement("form")}} element.
 
-<pre class="brush: html">&lt;form action="/" method="post" enctype="multipart/form-data"&gt;
-  &lt;input type="text" name="description" value="some text"&gt;
-  &lt;input type="file" name="myFile"&gt;
-  &lt;button type="submit"&gt;Submit&lt;/button&gt;
-&lt;/form&gt;
-</pre>
+```html
+<form action="/" method="post" enctype="multipart/form-data">
+  <input type="text" name="description" value="some text">
+  <input type="file" name="myFile">
+  <button type="submit">Submit</button>
+</form>
+```
 
-<p>The request looks something like this (less interesting headers are omitted here):</p>
+The request looks something like this (less interesting headers are omitted here):
 
-<pre>POST /foo HTTP/1.1
-Content-Length: 68137
-Content-Type: multipart/form-data; boundary=---------------------------974767299852498929531610575
+    POST /foo HTTP/1.1
+    Content-Length: 68137
+    Content-Type: multipart/form-data; boundary=---------------------------974767299852498929531610575
 
------------------------------974767299852498929531610575
-Content-Disposition: form-data; name="description"
+    -----------------------------974767299852498929531610575
+    Content-Disposition: form-data; name="description"
 
-some text
------------------------------974767299852498929531610575
-Content-Disposition: form-data; name="myFile"; filename="foo.txt"
-Content-Type: text/plain
+    some text
+    -----------------------------974767299852498929531610575
+    Content-Disposition: form-data; name="myFile"; filename="foo.txt"
+    Content-Type: text/plain
 
-(content of the uploaded file foo.txt)
------------------------------974767299852498929531610575--
-</pre>
+    (content of the uploaded file foo.txt)
+    -----------------------------974767299852498929531610575--
 
-<h2 id="Specifications">Specifications</h2>
+## Specifications
 
 {{Specifications}}
 
-<h2 id="Browser_compatibility">Browser compatibility</h2>
+## Browser compatibility
 
-<p>{{Compat}}</p>
+{{Compat}}
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
- <li>{{HTTPHeader("Accept")}}</li>
- <li>{{HTTPHeader("Content-Disposition")}}</li>
- <li>{{HTTPStatus("206")}} Partial Content</li>
- <li>{{HTTPHeader("X-Content-Type-Options")}}</li>
-</ul>
+- {{HTTPHeader("Accept")}}
+- {{HTTPHeader("Content-Disposition")}}
+- {{HTTPStatus("206")}} Partial Content
+- {{HTTPHeader("X-Content-Type-Options")}}
diff --git a/files/en-us/web/http/headers/cookie/index.md b/files/en-us/web/http/headers/cookie/index.md
index bedcc25e3282df7..9ead3f23b708f7f 100644
--- a/files/en-us/web/http/headers/cookie/index.md
+++ b/files/en-us/web/http/headers/cookie/index.md
@@ -9,51 +9,49 @@ tags:
   - request
 browser-compat: http.headers.Cookie
 ---
-<div>{{HTTPSidebar}}</div>
+{{HTTPSidebar}}
 
-<p>The <strong><code>Cookie</code></strong> HTTP request header contains stored <a href="/en-US/docs/Web/HTTP/Cookies">HTTP cookies</a> associated with the server (i.e. previously sent by the server with the {{HTTPHeader("Set-Cookie")}} header or set in Javascript using {{domxref("Document.cookie")}}).</p>
+The **`Cookie`** HTTP request header contains stored [HTTP cookies](/en-US/docs/Web/HTTP/Cookies) associated with the server (i.e. previously sent by the server with the {{HTTPHeader("Set-Cookie")}} header or set in Javascript using {{domxref("Document.cookie")}}).
 
-<p>The <code>Cookie</code> header is optional and may be omitted if, for example, the browser's privacy settings block cookies.</p>
+The `Cookie` header is optional and may be omitted if, for example, the browser's privacy settings block cookies.
 
 <table class="properties">
- <tbody>
-  <tr>
-   <th scope="row">Header type</th>
-   <td>{{Glossary("Request header")}}</td>
-  </tr>
-  <tr>
-   <th scope="row">{{Glossary("Forbidden header name")}}</th>
-   <td>yes</td>
-  </tr>
- </tbody>
+  <tbody>
+    <tr>
+      <th scope="row">Header type</th>
+      <td>{{Glossary("Request header")}}</td>
+    </tr>
+    <tr>
+      <th scope="row">{{Glossary("Forbidden header name")}}</th>
+      <td>yes</td>
+    </tr>
+  </tbody>
 </table>
 
-<h2 id="Syntax">Syntax</h2>
+## Syntax
 
-<pre class="brush: html">Cookie: &lt;cookie-list&gt;
+```html
+Cookie: <cookie-list>
 Cookie: name=value
-Cookie: name=value; name2=value2; name3=value3</pre>
+Cookie: name=value; name2=value2; name3=value3
+```
 
-<dl>
- <dt>&lt;cookie-list&gt;</dt>
- <dd>A list of name-value pairs in the form of <code>&lt;cookie-name&gt;=&lt;cookie-value&gt;</code>. Pairs in the list are separated by a semicolon and a space (<code>'; '</code>).</dd>
-</dl>
+- \<cookie-list>
+  - : A list of name-value pairs in the form of `<cookie-name>=<cookie-value>`. Pairs in the list are separated by a semicolon and a space (`'; '`).
 
-<h2 id="Examples">Examples</h2>
+## Examples
 
-<pre>Cookie: PHPSESSID=298zf09hf012fh2; csrftoken=u32t4o3tb3gg43; _gat=1</pre>
+    Cookie: PHPSESSID=298zf09hf012fh2; csrftoken=u32t4o3tb3gg43; _gat=1
 
-<h2 id="Specifications">Specifications</h2>
+## Specifications
 
 {{Specifications}}
 
-<h2 id="Browser_compatibility">Browser compatibility</h2>
+## Browser compatibility
 
-<p>{{Compat}}</p>
+{{Compat}}
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
- <li>{{HTTPHeader("Set-Cookie")}}</li>
- <li>{{domxref("Document.cookie")}}</li>
-</ul>
+- {{HTTPHeader("Set-Cookie")}}
+- {{domxref("Document.cookie")}}
diff --git a/files/en-us/web/http/headers/cookie2/index.md b/files/en-us/web/http/headers/cookie2/index.md
index 1cfaed7ccf079a8..1beaa08726f15ca 100644
--- a/files/en-us/web/http/headers/cookie2/index.md
+++ b/files/en-us/web/http/headers/cookie2/index.md
@@ -9,49 +9,38 @@ tags:
   - request
 browser-compat: http.headers.Cookie2
 ---
-<div>{{HTTPSidebar}} {{deprecated_header}}</div>
+{{HTTPSidebar}} {{deprecated_header}}
 
-<p>The obsolete <strong><code>Cookie2</code></strong> HTTP request header used to advise the server that the user agent understands "new-style" cookies, but nowadays user agents will use the {{HTTPHeader("Cookie")}} header instead, not this one.</p>
+The obsolete **`Cookie2`** HTTP request header used to advise the server that the user agent understands "new-style" cookies, but nowadays user agents will use the {{HTTPHeader("Cookie")}} header instead, not this one.
 
 <table class="properties">
- <tbody>
-  <tr>
-   <th scope="row">Header type</th>
-   <td>{{Glossary("Request header")}}</td>
-  </tr>
-  <tr>
-   <th scope="row">{{Glossary("Forbidden header name")}}</th>
-   <td>yes</td>
-  </tr>
- </tbody>
+  <tbody>
+    <tr>
+      <th scope="row">Header type</th>
+      <td>{{Glossary("Request header")}}</td>
+    </tr>
+    <tr>
+      <th scope="row">{{Glossary("Forbidden header name")}}</th>
+      <td>yes</td>
+    </tr>
+  </tbody>
 </table>
 
-<h2 id="Examples">Examples</h2>
+## Examples
 
-<pre>Cookie2: $Version="1"</pre>
+    Cookie2: $Version="1"
 
-<h2 id="Specifications">Specifications</h2>
+## Specifications
 
-<table class="standard-table">
- <tbody>
-  <tr>
-   <th scope="col">Specification</th>
-   <th scope="col">Title</th>
-  </tr>
-  <tr>
-   <td>{{RFC("2965", "Cookie2")}}</td>
-   <td>Historic specification of HTTP State Management Mechanism, obsoleted by {{RFC("6265")}}</td>
-  </tr>
- </tbody>
-</table>
+| Specification                        | Title                                                                                        |
+| ------------------------------------ | -------------------------------------------------------------------------------------------- |
+| {{RFC("2965", "Cookie2")}} | Historic specification of HTTP State Management Mechanism, obsoleted by {{RFC("6265")}} |
 
-<h2 id="Browser_compatibility">Browser compatibility</h2>
+## Browser compatibility
 
-<p>{{Compat}}</p>
+{{Compat}}
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
- <li>{{HTTPHeader("Cookie")}}</li>
- <li>{{domxref("Document.cookie")}}</li>
-</ul>
+- {{HTTPHeader("Cookie")}}
+- {{domxref("Document.cookie")}}
diff --git a/files/en-us/web/http/headers/cross-origin-embedder-policy/index.md b/files/en-us/web/http/headers/cross-origin-embedder-policy/index.md
index d6453568364406e..7c9511004889b16 100644
--- a/files/en-us/web/http/headers/cross-origin-embedder-policy/index.md
+++ b/files/en-us/web/http/headers/cross-origin-embedder-policy/index.md
@@ -9,74 +9,74 @@ tags:
   - header
 browser-compat: http.headers.Cross-Origin-Embedder-Policy
 ---
-<div>{{HTTPSidebar}}</div>
+{{HTTPSidebar}}
 
-<p>The HTTP <strong><code>Cross-Origin-Embedder-Policy</code></strong> (COEP) response header prevents a document from loading any cross-origin resources that don't explicitly grant the document permission (using <a href="/en-US/docs/Web/HTTP/Cross-Origin_Resource_Policy_(CORP)">CORP</a> or <a href="/en-US/docs/Web/HTTP/CORS">CORS</a>).</p>
+The HTTP **`Cross-Origin-Embedder-Policy`** (COEP) response header prevents a document from loading any cross-origin resources that don't explicitly grant the document permission (using [CORP](</en-US/docs/Web/HTTP/Cross-Origin_Resource_Policy_(CORP)>) or [CORS](/en-US/docs/Web/HTTP/CORS)).
 
 <table class="properties">
- <tbody>
-  <tr>
-   <th scope="row">Header type</th>
-   <td>{{Glossary("Response header")}}</td>
-  </tr>
-  <tr>
-   <th scope="row">{{Glossary("Forbidden header name")}}</th>
-   <td>no</td>
-  </tr>
- </tbody>
+  <tbody>
+    <tr>
+      <th scope="row">Header type</th>
+      <td>{{Glossary("Response header")}}</td>
+    </tr>
+    <tr>
+      <th scope="row">{{Glossary("Forbidden header name")}}</th>
+      <td>no</td>
+    </tr>
+  </tbody>
 </table>
 
-<h2 id="Syntax">Syntax</h2>
+## Syntax
 
-<pre class="brush: html">Cross-Origin-Embedder-Policy: unsafe-none | require-corp
-</pre>
+```html
+Cross-Origin-Embedder-Policy: unsafe-none | require-corp
+```
 
-<h3 id="Directives">Directives</h3>
+### Directives
 
-<dl>
- <dt><code>unsafe-none</code></dt>
- <dd>This is the default value. Allows the document to fetch cross-origin resources without giving explicit permission through the CORS protocol or the {{HTTPHeader("Cross-Origin-Resource-Policy")}} header.</dd>
- <dt><code>require-corp</code></dt>
- <dd>A document can only load resources from the same origin, or resources explicitly marked as loadable from another origin.<br>
- If a cross origin resource supports CORS, the <code><a href="/en-US/docs/Web/HTML/Attributes/crossorigin">crossorigin</a></code> attribute or the {{HTTPHeader("Cross-Origin-Resource-Policy")}} header must be used to load it without being blocked by COEP.</dd>
-</dl>
+- `unsafe-none`
+  - : This is the default value. Allows the document to fetch cross-origin resources without giving explicit permission through the CORS protocol or the {{HTTPHeader("Cross-Origin-Resource-Policy")}} header.
+- `require-corp`
+  - : A document can only load resources from the same origin, or resources explicitly marked as loadable from another origin.
+    If a cross origin resource supports CORS, the [`crossorigin`](/en-US/docs/Web/HTML/Attributes/crossorigin) attribute or the {{HTTPHeader("Cross-Origin-Resource-Policy")}} header must be used to load it without being blocked by COEP.
 
-<h2 id="Examples">Examples</h2>
+## Examples
 
-<h3 id="Certain_features_depend_on_cross-origin_isolation">Certain features depend on cross-origin isolation</h3>
+### Certain features depend on cross-origin isolation
 
-<p>You can only access certain features like {{jsxref("SharedArrayBuffer")}} objects or {{domxref("Performance.now()")}} with unthrottled timers, if your document has a COEP header with the value <code>require-corp</code> value set.</p>
+You can only access certain features like {{jsxref("SharedArrayBuffer")}} objects or {{domxref("Performance.now()")}} with unthrottled timers, if your document has a COEP header with the value `require-corp` value set.
 
-<pre>Cross-Origin-Embedder-Policy: require-corp
-Cross-Origin-Opener-Policy: same-origin
-</pre>
+    Cross-Origin-Embedder-Policy: require-corp
+    Cross-Origin-Opener-Policy: same-origin
 
-<p>See also the {{HTTPHeader("Cross-Origin-Opener-Policy")}} header which you'll need to set as well.</p>
+See also the {{HTTPHeader("Cross-Origin-Opener-Policy")}} header which you'll need to set as well.
 
-<p>To check if cross origin isolation has been successful, you can test against the <code><a href="/en-US/docs/Web/API/WindowOrWorkerGlobalScope/crossOriginIsolated">crossOriginIsolated</a></code> property available to window and worker contexts:</p>
+To check if cross origin isolation has been successful, you can test against the [`crossOriginIsolated`](/en-US/docs/Web/API/WindowOrWorkerGlobalScope/crossOriginIsolated) property available to window and worker contexts:
 
-<pre class="brush: js">if (crossOriginIsolated) {
+```js
+if (crossOriginIsolated) {
   // Post SharedArrayBuffer
 } else {
   // Do something else
-}</pre>
+}
+```
 
-<h3 id="Avoiding_COEP_blockage_with_CORS">Avoiding COEP blockage with CORS</h3>
+### Avoiding COEP blockage with CORS
 
-<p>If you enable COEP using <code>require-corp</code> and have a cross origin resource that needs to be loaded, it needs to support <a href="/en-US/docs/Web/HTTP/CORS">CORS</a> and you need to explicitly mark the resource as loadable from another origin to avoid blockage from COEP. For example, you can use the <code><a href="/en-US/docs/Web/HTML/Attributes/crossorigin">crossorigin</a></code> attribute for this image from a third-party site:</p>
+If you enable COEP using `require-corp` and have a cross origin resource that needs to be loaded, it needs to support [CORS](/en-US/docs/Web/HTTP/CORS) and you need to explicitly mark the resource as loadable from another origin to avoid blockage from COEP. For example, you can use the [`crossorigin`](/en-US/docs/Web/HTML/Attributes/crossorigin) attribute for this image from a third-party site:
 
-<pre class="brush: html">&lt;img src="https://thirdparty.com/img.png" crossorigin&gt;</pre>
+```html
+<img src="https://thirdparty.com/img.png" crossorigin>
+```
 
-<h2 id="Specifications">Specifications</h2>
+## Specifications
 
 {{Specifications}}
 
-<h2 id="Browser_compatibility">Browser compatibility</h2>
+## Browser compatibility
 
-<p>{{Compat}}</p>
+{{Compat}}
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
- <li>{{httpheader("Cross-Origin-Opener-Policy")}}</li>
-</ul>
+- {{httpheader("Cross-Origin-Opener-Policy")}}
diff --git a/files/en-us/web/http/headers/cross-origin-opener-policy/index.md b/files/en-us/web/http/headers/cross-origin-opener-policy/index.md
index 1d812e605b52f90..29146ecd5abd994 100644
--- a/files/en-us/web/http/headers/cross-origin-opener-policy/index.md
+++ b/files/en-us/web/http/headers/cross-origin-opener-policy/index.md
@@ -9,73 +9,71 @@ tags:
   - header
 browser-compat: http.headers.Cross-Origin-Opener-Policy
 ---
-<div>{{HTTPSidebar}}</div>
+{{HTTPSidebar}}
 
-<p>The HTTP <strong><code>Cross-Origin-Opener-Policy</code></strong> (COOP) response header allows you to ensure a top-level document does not share a browsing context group with cross-origin documents.</p>
+The HTTP **`Cross-Origin-Opener-Policy`** (COOP) response header allows you to ensure a top-level document does not share a browsing context group with cross-origin documents.
 
-<p>COOP will process-isolate your document and potential attackers can't access to your global object if they were opening it in a popup, preventing a set of cross-origin attacks dubbed <a href="https://github.com/xsleaks/xsleaks">XS-Leaks</a>.</p>
+COOP will process-isolate your document and potential attackers can't access to your global object if they were opening it in a popup, preventing a set of cross-origin attacks dubbed [XS-Leaks](https://github.com/xsleaks/xsleaks).
 
-<p>If a cross-origin document with COOP is opened in a new window, the opening document will not have a reference to it, and the <code><a href="/en-US/docs/Web/API/Window/opener">window.opener</a></code> property of the new window will be <code>null</code>. This allows you to have more control over references to a window than <code><a href="/en-US/docs/Web/HTML/Link_types/noopener">rel=noopener</a></code>, which only affects outgoing navigations.</p>
+If a cross-origin document with COOP is opened in a new window, the opening document will not have a reference to it, and the [`window.opener`](/en-US/docs/Web/API/Window/opener) property of the new window will be `null`. This allows you to have more control over references to a window than [`rel=noopener`](/en-US/docs/Web/HTML/Link_types/noopener), which only affects outgoing navigations.
 
 <table class="properties">
- <tbody>
-  <tr>
-   <th scope="row">Header type</th>
-   <td>{{Glossary("Response header")}}</td>
-  </tr>
-  <tr>
-   <th scope="row">{{Glossary("Forbidden header name")}}</th>
-   <td>no</td>
-  </tr>
- </tbody>
+  <tbody>
+    <tr>
+      <th scope="row">Header type</th>
+      <td>{{Glossary("Response header")}}</td>
+    </tr>
+    <tr>
+      <th scope="row">{{Glossary("Forbidden header name")}}</th>
+      <td>no</td>
+    </tr>
+  </tbody>
 </table>
 
-<h2 id="Syntax">Syntax</h2>
+## Syntax
 
-<pre class="brush: html">Cross-Origin-Opener-Policy: unsafe-none | same-origin-allow-popups | same-origin
-</pre>
+```html
+Cross-Origin-Opener-Policy: unsafe-none | same-origin-allow-popups | same-origin
+```
 
-<h3 id="Directives">Directives</h3>
+### Directives
 
-<dl>
- <dt><code>unsafe-none</code></dt>
- <dd>This is the default value. Allows the document to be added to its opener's browsing context group unless the opener itself has a COOP of <code>same-origin</code> or <code>same-origin-allow-popups</code>.</dd>
- <dt><code>same-origin-allow-popups</code></dt>
- <dd>Retains references to newly opened windows or tabs which either don't set COOP or which opt out of isolation by setting a COOP of <code>unsafe-none</code>.</dd>
- <dt><code>same-origin</code></dt>
- <dd>Isolates the browsing context exclusively to same-origin documents. Cross-origin documents are not loaded in the same browsing context.</dd>
-</dl>
+- `unsafe-none`
+  - : This is the default value. Allows the document to be added to its opener's browsing context group unless the opener itself has a COOP of `same-origin` or `same-origin-allow-popups`.
+- `same-origin-allow-popups`
+  - : Retains references to newly opened windows or tabs which either don't set COOP or which opt out of isolation by setting a COOP of `unsafe-none`.
+- `same-origin`
+  - : Isolates the browsing context exclusively to same-origin documents. Cross-origin documents are not loaded in the same browsing context.
 
-<h2 id="Examples">Examples</h2>
+## Examples
 
-<h3 id="Certain_features_depend_on_cross-origin_isolation">Certain features depend on cross-origin isolation</h3>
+### Certain features depend on cross-origin isolation
 
-<p>Certain features like {{jsxref("SharedArrayBuffer")}} objects or {{domxref("Performance.now()")}} with unthrottled timers are only available if your document has a COOP header with the value <code>same-origin</code> value set.</p>
+Certain features like {{jsxref("SharedArrayBuffer")}} objects or {{domxref("Performance.now()")}} with unthrottled timers are only available if your document has a COOP header with the value `same-origin` value set.
 
-<pre>Cross-Origin-Opener-Policy: same-origin
-Cross-Origin-Embedder-Policy: require-corp
-</pre>
+    Cross-Origin-Opener-Policy: same-origin
+    Cross-Origin-Embedder-Policy: require-corp
 
-<p>See also the {{HTTPHeader("Cross-Origin-Embedder-Policy")}} header which you'll need to set as well.</p>
+See also the {{HTTPHeader("Cross-Origin-Embedder-Policy")}} header which you'll need to set as well.
 
-<p>To check if cross-origin isolation has been successful, you can test against the <code><a href="/en-US/docs/Web/API/WindowOrWorkerGlobalScope/crossOriginIsolated">crossOriginIsolated</a></code> property available to window and worker contexts:</p>
+To check if cross-origin isolation has been successful, you can test against the [`crossOriginIsolated`](/en-US/docs/Web/API/WindowOrWorkerGlobalScope/crossOriginIsolated) property available to window and worker contexts:
 
-<pre class="brush: js">if (crossOriginIsolated) {
+```js
+if (crossOriginIsolated) {
   // Post SharedArrayBuffer
 } else {
   // Do something else
-}</pre>
+}
+```
 
-<h2 id="Specifications">Specifications</h2>
+## Specifications
 
 {{Specifications}}
 
-<h2 id="Browser_compatibility">Browser compatibility</h2>
+## Browser compatibility
 
-<p>{{Compat}}</p>
+{{Compat}}
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
- <li>{{httpheader("Cross-Origin-Embedder-Policy")}}</li>
-</ul>
+- {{httpheader("Cross-Origin-Embedder-Policy")}}
diff --git a/files/en-us/web/http/headers/cross-origin-resource-policy/index.md b/files/en-us/web/http/headers/cross-origin-resource-policy/index.md
index 069f99c7ed422d7..3af21386a9120ec 100644
--- a/files/en-us/web/http/headers/cross-origin-resource-policy/index.md
+++ b/files/en-us/web/http/headers/cross-origin-resource-policy/index.md
@@ -2,31 +2,27 @@
 title: Cross-Origin-Resource-Policy
 slug: Web/HTTP/Headers/Cross-Origin-Resource-Policy
 tags:
-- HTTP
-- HTTP Header
-- Reference
-- Response Header
-- header
+  - HTTP
+  - HTTP Header
+  - Reference
+  - Response Header
+  - header
 browser-compat: http.headers.Cross-Origin-Resource-Policy
 ---
-<div>{{HTTPSidebar}}</div>
+{{HTTPSidebar}}
 
-<div class="notecard note">
-  <p>
-    <strong>Note:</strong> Due to a <a href="https://bugs.chromium.org/p/chromium/issues/detail?id=1074261">bug in Chrome</a>,
-    setting Cross-Origin-Resource-Policy can break PDF rendering,
-    preventing visitors from being able to read past the first page of some PDFs.
-    Due to a <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1638323">bug in Firefox</a>,
-    setting Cross-Origin-Resource-Policy can prevent some resources
-    (such as PDFs)
-    from being downloaded in some circumstances.
-    Exercise caution using this header in a production environment.
-  </p>
-</div>
+> **Note:** Due to a [bug in Chrome](https://bugs.chromium.org/p/chromium/issues/detail?id=1074261),
+> setting Cross-Origin-Resource-Policy can break PDF rendering,
+> preventing visitors from being able to read past the first page of some PDFs.
+> Due to a [bug in Firefox](https://bugzilla.mozilla.org/show_bug.cgi?id=1638323),
+> setting Cross-Origin-Resource-Policy can prevent some resources
+> (such as PDFs)
+> from being downloaded in some circumstances.
+> Exercise caution using this header in a production environment.
 
-<p>The HTTP <strong><code>Cross-Origin-Resource-Policy</code></strong> response header
-  conveys a desire that the browser blocks no-cors cross-origin/cross-site requests to the
-  given resource.</p>
+The HTTP **`Cross-Origin-Resource-Policy`** response header
+conveys a desire that the browser blocks no-cors cross-origin/cross-site requests to the
+given resource.
 
 <table class="properties">
   <tbody>
@@ -41,36 +37,33 @@ browser-compat: http.headers.Cross-Origin-Resource-Policy
   </tbody>
 </table>
 
-<h2 id="Syntax">Syntax</h2>
+## Syntax
 
-<pre class="brush: html">Cross-Origin-Resource-Policy: same-site | same-origin | cross-origin
-</pre>
+```html
+Cross-Origin-Resource-Policy: same-site | same-origin | cross-origin
+```
 
-<h2 id="Examples">Examples</h2>
+## Examples
 
-<p>The response header below will cause compatible user agents to disallow cross-origin
-  no-cors requests:</p>
+The response header below will cause compatible user agents to disallow cross-origin
+no-cors requests:
 
-<pre>Cross-Origin-Resource-Policy: same-origin
-</pre>
+    Cross-Origin-Resource-Policy: same-origin
 
-<p>For more examples, see <a
-    href="https://resourcepolicy.fyi/">https://resourcepolicy.fyi/</a>.</p>
+For more examples, see <https://resourcepolicy.fyi/>.
 
-<h2 id="Specifications">Specifications</h2>
+## Specifications
 
 {{Specifications}}
 
-<h2 id="Browser_compatibility">Browser compatibility</h2>
+## Browser compatibility
 
-<p>{{Compat}}</p>
+{{Compat}}
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
-  <li><a href="/en-US/docs/Web/HTTP/Cross-Origin_Resource_Policy_(CORP)">Cross-Origin
-      Resource Policy (CORP) explainer</a></li>
-  <li><a href="https://resourcepolicy.fyi/">Consider deploying Cross-Origin Resource
-      Policy</a></li>
-  <li>{{httpheader("Access-Control-Allow-Origin")}}</li>
-</ul>
+- [Cross-Origin
+  Resource Policy (CORP) explainer](</en-US/docs/Web/HTTP/Cross-Origin_Resource_Policy_(CORP)>)
+- [Consider deploying Cross-Origin Resource
+  Policy](https://resourcepolicy.fyi/)
+- {{httpheader("Access-Control-Allow-Origin")}}
diff --git a/files/en-us/web/http/headers/date/index.md b/files/en-us/web/http/headers/date/index.md
index 40ee4e9c0571453..4e04bec927bcd67 100644
--- a/files/en-us/web/http/headers/date/index.md
+++ b/files/en-us/web/http/headers/date/index.md
@@ -2,91 +2,90 @@
 title: Date
 slug: Web/HTTP/Headers/Date
 tags:
-- HTTP
-- HTTP Header
-- Request header
-- Response header
-- Reference
+  - HTTP
+  - HTTP Header
+  - Request header
+  - Response header
+  - Reference
 browser-compat: http.headers.Date
 ---
-<div>{{HTTPSidebar}}</div>
+{{HTTPSidebar}}
+
+The **`Date`** general HTTP header contains the date and time
+at which the message was originated.
+
+> **Warning:** `Date` is listed
+> in the [forbidden header names](https://fetch.spec.whatwg.org/#forbidden-header-name)
+> in the fetch spec, so this code will not send the `Date` header:
+>
+> ```js
+> fetch('https://httpbin.org/get', {
+>       'headers': {
+>         'Date': (new Date()).toUTCString()
+>       }
+>     })
+> ```
 
-<p>The <strong><code>Date</code></strong> general HTTP header contains the date and time
-	at which the message was originated.</p>
+<table class="properties">
+  <tbody>
+    <tr>
+      <th scope="row">Header type</th>
+      <td>
+        {{Glossary("Request header")}},
+        {{Glossary("Response header")}}
+      </td>
+    </tr>
+    <tr>
+      <th scope="row">{{Glossary("Forbidden header name")}}</th>
+      <td>yes</td>
+    </tr>
+  </tbody>
+</table>
 
-<div class="notecard warning">
-	<p><strong>Warning:</strong> <code>Date</code> is listed
-    in the <a href="https://fetch.spec.whatwg.org/#forbidden-header-name">forbidden header names</a>
-    in the fetch spec, so this code will not send the <code>Date</code> header:</p>
+## Syntax
 
-	  <pre class="brush: js">fetch('https://httpbin.org/get', {
-      'headers': {
-        'Date': (new Date()).toUTCString()
-      }
-    })</pre>
-</div>
+```html
+Date: <day-name>, <day> <month> <year> <hour>:<minute>:<second> GMT
+```
 
-<table class="properties">
-	<tbody>
-		<tr>
-			<th scope="row">Header type</th>
-			<td>{{Glossary("Request header")}}, {{Glossary("Response header")}}</td>
-		</tr>
-		<tr>
-			<th scope="row">{{Glossary("Forbidden header name")}}</th>
-			<td>yes</td>
-		</tr>
-	</tbody>
-</table>
+## Directives
+
+- \<day-name>
+  - : One of "Mon", "Tue", "Wed", "Thu", "Fri", "Sat", or "Sun" (case-sensitive).
+- \<day>
+  - : 2 digit day number, e.g. "04" or "23".
+- \<month>
+  - : One of "Jan", "Feb", "Mar", "Apr", "May", "Jun", "Jul", "Aug", "Sep", "Oct",
+    "Nov", "Dec" (case sensitive).
+- \<year>
+  - : 4 digit year number, e.g. "1990" or "2016".
+- \<hour>
+  - : 2 digit hour number, e.g. "09" or "23".
+- \<minute>
+  - : 2 digit minute number, e.g. "04" or "59".
+- \<second>
+  - : 2 digit second number, e.g. "04" or "59".
+- GMT
+  - : Greenwich Mean Time. HTTP dates are always expressed in GMT, never in local
+    time.
+
+## Examples
+
+    Date: Wed, 21 Oct 2015 07:28:00 GMT
+
+```js
+new Date().toUTCString()
+// "Mon, 09 Mar 2020 08:13:24 GMT"
+```
 
-<h2 id="Syntax">Syntax</h2>
-
-<pre class="brush: html">Date: &lt;day-name&gt;, &lt;day&gt; &lt;month&gt; &lt;year&gt; &lt;hour&gt;:&lt;minute&gt;:&lt;second&gt; GMT
-</pre>
-
-<h2 id="Directives">Directives</h2>
-
-<dl>
-	<dt>&lt;day-name&gt;</dt>
-	<dd>One of "Mon", "Tue", "Wed", "Thu", "Fri", "Sat", or "Sun" (case-sensitive).</dd>
-	<dt>&lt;day&gt;</dt>
-	<dd>2 digit day number, e.g. "04" or "23".</dd>
-	<dt>&lt;month&gt;</dt>
-	<dd>One of "Jan", "Feb", "Mar", "Apr", "May", "Jun", "Jul", "Aug", "Sep", "Oct",
-		"Nov", "Dec" (case sensitive).</dd>
-	<dt>&lt;year&gt;</dt>
-	<dd>4 digit year number, e.g. "1990" or "2016".</dd>
-	<dt>&lt;hour&gt;</dt>
-	<dd>2 digit hour number, e.g. "09" or "23".</dd>
-	<dt>&lt;minute&gt;</dt>
-	<dd>2 digit minute number, e.g. "04" or "59".</dd>
-	<dt>&lt;second&gt;</dt>
-	<dd>2 digit second number, e.g. "04" or "59".</dd>
-	<dt>GMT</dt>
-	<dd>
-		<p>Greenwich Mean Time. HTTP dates are always expressed in GMT, never in local
-			time.</p>
-	</dd>
-</dl>
-
-<h2 id="Examples">Examples</h2>
-
-<pre>Date: Wed, 21 Oct 2015 07:28:00 GMT
-</pre>
-
-<pre class="brush: js">new Date().toUTCString()
-// "Mon, 09 Mar 2020 08:13:24 GMT"</pre>
-
-<h2 id="Specifications">Specifications</h2>
+## Specifications
 
 {{Specifications}}
 
-<h2 id="Browser_compatibility">Browser compatibility</h2>
+## Browser compatibility
 
-<p>{{Compat}}</p>
+{{Compat}}
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
-	<li>{{HTTPHeader("Age")}}</li>
-</ul>
+- {{HTTPHeader("Age")}}
diff --git a/files/en-us/web/http/headers/device-memory/index.md b/files/en-us/web/http/headers/device-memory/index.md
index e7c169247491661..af85ce9ebbc37fa 100644
--- a/files/en-us/web/http/headers/device-memory/index.md
+++ b/files/en-us/web/http/headers/device-memory/index.md
@@ -11,78 +11,72 @@ tags:
   - Experimental
 browser-compat: http.headers.Device-Memory
 ---
-<div>{{HTTPSidebar}} {{SeeCompatTable}} {{securecontext_header}}</div>
+{{HTTPSidebar}} {{SeeCompatTable}} {{securecontext_header}}
 
-<p>The <strong><code>Device-Memory</code></strong> {{Glossary("Client hints","device client hint")}} request header field indicates the approximate amount of available RAM on the client device. The header is part of the <a href="/en-US/docs/Web/API/Device_Memory_API">Device Memory API</a>.</p>
+The **`Device-Memory`** {{Glossary("Client hints","device client hint")}} request header field indicates the approximate amount of available RAM on the client device. The header is part of the [Device Memory API](/en-US/docs/Web/API/Device_Memory_API).
 
 <table class="properties">
   <tbody>
-   <tr>
-    <th scope="row">Header type</th>
-    <td>{{Glossary("Request header")}}, {{Glossary("Client hints","Client hint")}}</td>
-   </tr>
-   <tr>
-    <th scope="row">{{Glossary("Forbidden header name")}}</th>
-    <td>no</td>
-   </tr>
+    <tr>
+      <th scope="row">Header type</th>
+      <td>
+        {{Glossary("Request header")}},
+        {{Glossary("Client hints","Client hint")}}
+      </td>
+    </tr>
+    <tr>
+      <th scope="row">{{Glossary("Forbidden header name")}}</th>
+      <td>no</td>
+    </tr>
   </tbody>
- </table>
+</table>
 
-<div class="notecard note">
-  <p><strong>Note:</strong></p>
-    <ul>
-      <li>Client Hints are accessible only on secure origins (via TLS).</li>
-      <li>A server has to opt in to receive the <code>Device-Memory</code> header from the client, by sending the {{HTTPHeader("Accept-CH")}} response header.</li>
-      <li>Servers that opt in to the <code>Device-Memory</code> client hint will typically also specify it in the {{HTTPHeader("Vary")}} header. This informs caches that the server may send different responses based on the header value in a request.</li>
-    </ul>
-</div>
+> **Note:**
+>
+> - Client Hints are accessible only on secure origins (via TLS).
+> - A server has to opt in to receive the `Device-Memory` header from the client, by sending the {{HTTPHeader("Accept-CH")}} response header.
+> - Servers that opt in to the `Device-Memory` client hint will typically also specify it in the {{HTTPHeader("Vary")}} header. This informs caches that the server may send different responses based on the header value in a request.
 
-<h2 id="Syntax">Syntax</h2>
+## Syntax
 
-<pre>Device-Memory: &lt;number&gt;</pre>
+    Device-Memory: <number>
 
-<h2 id="Directives">Directives</h2>
+## Directives
 
-<dl>
- <dt><code> &lt;number&gt;</code></dt>
- <dd>The approximate amount of device RAM. Possible values are: <code>0.25</code>, <code>0.5</code>, <code>1</code>, <code>2</code>, <code>4</code>, <code>8</code>.</dd>
-</dl>
+- `<number>`
+  - : The approximate amount of device RAM. Possible values are: `0.25`, `0.5`, `1`, `2`, `4`, `8`.
 
-<p>The amount of device RAM can be used as a fingerprinting variable, so values for the header are intentionally coarse to reduce the potential for its misuse.</p>
+The amount of device RAM can be used as a fingerprinting variable, so values for the header are intentionally coarse to reduce the potential for its misuse.
 
-<h2 id="Examples">Examples</h2>
+## Examples
 
-<p>The server first needs to opt in to receive <code>Device-Memory</code> header by sending the response headers {{HTTPHeader("Accept-CH")}} containing <code>Device-Memory</code>.</p>
+The server first needs to opt in to receive `Device-Memory` header by sending the response headers {{HTTPHeader("Accept-CH")}} containing `Device-Memory`.
 
-<pre>Accept-CH: Device-Memory
-</pre>
+    Accept-CH: Device-Memory
 
-<p>Then on subsequent requests the client might send <code>Device-Memory</code> header back:</p>
+Then on subsequent requests the client might send `Device-Memory` header back:
 
-<pre>Device-Memory: 1</pre>
+    Device-Memory: 1
 
-<h2 id="Specifications">Specifications</h2>
+## Specifications
 
-<p>{{Specifications}}</p>
+{{Specifications}}
 
-<h2 id="Browser_compatibility">Browser compatibility</h2>
+## Browser compatibility
 
-<p>{{Compat}}</p>
+{{Compat}}
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
-  <li><a href="https://developers.google.com/web/fundamentals/performance/optimizing-content-efficiency/client-hints">Adapting to Users with Client Hints</a> (developer.google.com)</li>
-  <li><a href="/en-US/docs/Web/API/Device_Memory_API">Device Memory API</a></li>
-  <li>{{DOMxRef("Navigator.deviceMemory")}}</li>
- <li>Device client hints
-  <ul>
-    <li>{{HTTPHeader("Content-DPR")}}</li>
-    <li>{{HTTPHeader("DPR")}}</li>
-    <li>{{HTTPHeader("Viewport-Width")}}</li>
-    <li>{{HTTPHeader("Width")}}</li>
-   </ul>
- </li>
- <li>{{HTTPHeader("Accept-CH")}}</li>
- <li><a href="/en-US/docs/Web/HTTP/Caching#varying_responses">HTTP Caching > Varying responses</a> and {{HTTPHeader("Vary")}}</li>
-</ul>
+- [Adapting to Users with Client Hints](https://developers.google.com/web/fundamentals/performance/optimizing-content-efficiency/client-hints) (developer.google.com)
+- [Device Memory API](/en-US/docs/Web/API/Device_Memory_API)
+- {{DOMxRef("Navigator.deviceMemory")}}
+- Device client hints
+
+  - {{HTTPHeader("Content-DPR")}}
+  - {{HTTPHeader("DPR")}}
+  - {{HTTPHeader("Viewport-Width")}}
+  - {{HTTPHeader("Width")}}
+
+- {{HTTPHeader("Accept-CH")}}
+- [HTTP Caching > Varying responses](/en-US/docs/Web/HTTP/Caching#varying_responses) and {{HTTPHeader("Vary")}}
diff --git a/files/en-us/web/http/headers/digest/index.md b/files/en-us/web/http/headers/digest/index.md
index 24466b4d0d5f057..97761b6d32774e3 100644
--- a/files/en-us/web/http/headers/digest/index.md
+++ b/files/en-us/web/http/headers/digest/index.md
@@ -2,31 +2,27 @@
 title: Digest
 slug: Web/HTTP/Headers/Digest
 tags:
-- HTTP
-- HTTP Header
+  - HTTP
+  - HTTP Header
 browser-compat: http.headers.Digest
 ---
-<div>{{HTTPSidebar}}</div>
+{{HTTPSidebar}}
 
-<p>The <code><strong>Digest</strong></code> response HTTP header provides a
-  {{Glossary("digest")}} of the requested resource.</p>
+The **`Digest`** response HTTP header provides a
+{{Glossary("digest")}} of the requested resource.
 
-<p>
-  In <a href="https://datatracker.ietf.org/doc/html/rfc7231">RFC 7231</a> terms,
-  this is the <em>selected representation</em> of a resource.
-  The selected representation depends
-  on the <code><a href="/en-US/docs/Web/HTTP/Headers/Content-Type">Content-Type</a></code>
-  and <code><a href="/en-US/docs/Web/HTTP/Headers/Content-Encoding">Content-Encoding</a></code> header values,
-  so a single resource may have multiple different digest values.
-</p>
+In [RFC 7231](https://datatracker.ietf.org/doc/html/rfc7231) terms,
+this is the _selected representation_ of a resource.
+The selected representation depends
+on the [`Content-Type`](/en-US/docs/Web/HTTP/Headers/Content-Type)
+and [`Content-Encoding`](/en-US/docs/Web/HTTP/Headers/Content-Encoding) header values,
+so a single resource may have multiple different digest values.
 
-<p>The digest is calculated over the entire representation. The representation itself may be:</p>
+The digest is calculated over the entire representation. The representation itself may be:
 
-<ul>
-  <li>fully contained in the response message body,</li>
-  <li>not at all contained in the message body (for example, in a response to a <code><a href="/en-US/docs/Web/HTTP/Methods/HEAD">HEAD</a></code> request),</li>
-  <li>or partially contained in the message body (for example, in a response to a <a href="/en-US/docs/Web/HTTP/Range_requests">range request</a>).</li>
-</ul>
+- fully contained in the response message body,
+- not at all contained in the message body (for example, in a response to a [`HEAD`](/en-US/docs/Web/HTTP/Methods/HEAD) request),
+- or partially contained in the message body (for example, in a response to a [range request](/en-US/docs/Web/HTTP/Range_requests)).
 
 <table class="properties">
   <tbody>
@@ -41,61 +37,45 @@ browser-compat: http.headers.Digest
   </tbody>
 </table>
 
-<h2 id="Syntax">Syntax</h2>
+## Syntax
 
-<pre>Digest: &lt;digest-algorithm&gt;=&lt;digest-value&gt;
-Digest: &lt;digest-algorithm&gt;=&lt;digest-value&gt;,&lt;digest-algorithm&gt;=&lt;digest-value&gt;
-</pre>
+    Digest: <digest-algorithm>=<digest-value>
+    Digest: <digest-algorithm>=<digest-value>,<digest-algorithm>=<digest-value>
 
-<h2 id="Directives">Directives</h2>
+## Directives
 
-<dl>
-  <dt><code>&lt;digest-algorithm&gt;</code></dt>
-  <dd>Supported digest algorithms are defined in <a
-      href="https://datatracker.ietf.org/doc/html/rfc3230">RFC 3230</a> and <a
-      href="https://datatracker.ietf.org/doc/html/rfc5843">RFC 5843</a>, and include
-    <code>SHA-256</code> and <code>SHA-512</code>. Some of the supported algorithms,
-    including <code>unixsum</code> and <code>MD5</code> are subject to collisions and are
-    thus not suitable for applications in which collision-resistance is important.</dd>
-  <dt><code>&lt;digest-value&gt;</code></dt>
-  <dd>The result of applying the digest algorithm to the resource representation and
+- `<digest-algorithm>`
+  - : Supported digest algorithms are defined in [RFC 3230](https://datatracker.ietf.org/doc/html/rfc3230) and [RFC 5843](https://datatracker.ietf.org/doc/html/rfc5843), and include
+    `SHA-256` and `SHA-512`. Some of the supported algorithms,
+    including `unixsum` and `MD5` are subject to collisions and are
+    thus not suitable for applications in which collision-resistance is important.
+- `<digest-value>`
+  - : The result of applying the digest algorithm to the resource representation and
     encoding the result. The choice of digest algorithm also determines the encoding to
-    use: for example <code>SHA-256</code> uses base64 encoding.</dd>
-</dl>
+    use: for example `SHA-256` uses base64 encoding.
 
-<h2 id="Examples">Examples</h2>
+## Examples
 
-<pre>Digest: sha-256=X48E9qOokqqrvdts8nOJRJN3OWDUoyWxBf7kbu9DBPE=
-Digest: sha-256=X48E9qOokqqrvdts8nOJRJN3OWDUoyWxBf7kbu9DBPE=,unixsum=30637</pre>
+    Digest: sha-256=X48E9qOokqqrvdts8nOJRJN3OWDUoyWxBf7kbu9DBPE=
+    Digest: sha-256=X48E9qOokqqrvdts8nOJRJN3OWDUoyWxBf7kbu9DBPE=,unixsum=30637
 
-<h2 id="Specifications">Specifications</h2>
+## Specifications
 
-<table>
-    <tr>
-      <th>Specification</th>
-    </tr>
-    <tr>
-      <td><a href="https://datatracker.ietf.org/doc/draft-ietf-httpbis-digest-headers">draft-ietf-httpbis-digest-headers-latest</a></td>
-    </tr>
-</table>
+| Specification                                                                                                  |
+| -------------------------------------------------------------------------------------------------------------- |
+| [draft-ietf-httpbis-digest-headers-latest](https://datatracker.ietf.org/doc/draft-ietf-httpbis-digest-headers) |
 
-<p>
-  This header was originally defined in <a href="https://datatracker.ietf.org/doc/html/rfc3230">RFC 3230</a>,
-  but the definition of "selected representation" in <a  href="https://www.rfc-editor.org/info/rfc7231">RFC 7231</a> made the original definition inconsistent with current HTTP specifications.
-  When released, The "Resource Digests for HTTP" draft therefore will obsolete RFC 3230
-  and will update the standard to be consistent.
-</p>
+This header was originally defined in [RFC 3230](https://datatracker.ietf.org/doc/html/rfc3230),
+but the definition of "selected representation" in [RFC 7231](https://www.rfc-editor.org/info/rfc7231) made the original definition inconsistent with current HTTP specifications.
+When released, The "Resource Digests for HTTP" draft therefore will obsolete RFC 3230
+and will update the standard to be consistent.
 
-<h2 id="Browser_compatibility">Browser compatibility</h2>
+## Browser compatibility
 
-<p>{{Compat}}</p>
+{{Compat}}
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
-  <li>{{HTTPHeader("Want-Digest")}}</li>
-  <li><a href="/en-US/docs/Web/HTTP/Range_requests">HTTP range requests</a></li>
-  <li><a href="/en-US/docs/Web/HTTP/Status/206"
-      title="The HTTP 206 Partial Content success status response code indicates that the request has succeeded and has the body contains the requested ranges of data, as described in the Range header of the request."><code>206 Partial Content</code></a>
-  </li>
-</ul>
+- {{HTTPHeader("Want-Digest")}}
+- [HTTP range requests](/en-US/docs/Web/HTTP/Range_requests)
+- [`206 Partial Content`](/en-US/docs/Web/HTTP/Status/206 "The HTTP 206 Partial Content success status response code indicates that the request has succeeded and has the body contains the requested ranges of data, as described in the Range header of the request.")
diff --git a/files/en-us/web/http/headers/dnt/index.md b/files/en-us/web/http/headers/dnt/index.md
index cde38ebf855d8a2..f2934065bff5186 100644
--- a/files/en-us/web/http/headers/dnt/index.md
+++ b/files/en-us/web/http/headers/dnt/index.md
@@ -2,17 +2,17 @@
 title: DNT
 slug: Web/HTTP/Headers/DNT
 tags:
-- DNT
-- HTTP
-- Reference
-- header
+  - DNT
+  - HTTP
+  - Reference
+  - header
 browser-compat: http.headers.DNT
 ---
-<div>{{HTTPSidebar}}{{Deprecated_header}}</div>
+{{HTTPSidebar}}{{Deprecated_header}}
 
-<p>The <strong><code>DNT</code></strong> (<strong>D</strong>o <strong>N</strong>ot
-  <strong>T</strong>rack) request header indicates the user's tracking preference. It lets
-  users indicate whether they would prefer privacy rather than personalized content.</p>
+The **`DNT`** (**D**o **N**ot
+**T**rack) request header indicates the user's tracking preference. It lets
+users indicate whether they would prefer privacy rather than personalized content.
 
 <table class="properties">
   <tbody>
@@ -27,57 +27,51 @@ browser-compat: http.headers.DNT
   </tbody>
 </table>
 
-<h2 id="Syntax">Syntax</h2>
+## Syntax
 
-<pre class="brush: html">DNT: 0
+```html
+DNT: 0
 DNT: 1
 DNT: null
-</pre>
+```
 
-<h2 id="Directives">Directives</h2>
+## Directives
 
-<dl>
-  <dt>0</dt>
-  <dd>The user prefers to allow tracking on the target site.</dd>
-  <dt>1</dt>
-  <dd>The user prefers not to be tracked on the target site.</dd>
-  <dt>null</dt>
-  <dd>The user has not specified a preference about tracking.</dd>
-</dl>
+- 0
+  - : The user prefers to allow tracking on the target site.
+- 1
+  - : The user prefers not to be tracked on the target site.
+- null
+  - : The user has not specified a preference about tracking.
 
-<h2 id="Examples">Examples</h2>
+## Examples
 
-<h3 id="Reading_Do_Not_Track_status_from_JavaScript">Reading Do Not Track status from
-  JavaScript</h3>
+### Reading Do Not Track status from JavaScript
 
-<p>The user's DNT preference can also be read from JavaScript using the
-  {{domxref("Navigator.doNotTrack")}} property:</p>
+The user's DNT preference can also be read from JavaScript using the
+{{domxref("Navigator.doNotTrack")}} property:
 
-<pre class="brush: js">navigator.doNotTrack; // "0" or "1"</pre>
+```js
+navigator.doNotTrack; // "0" or "1"
+```
 
-<h2 id="Specifications">Specifications</h2>
+## Specifications
 
 {{Specifications}}
 
-<h2 id="Browser_compatibility">Browser compatibility</h2>
-
-<p>{{Compat}}</p>
-
-<h2 id="See_also">See also</h2>
-
-<ul>
-  <li>{{domxref("Navigator.doNotTrack")}}</li>
-  <li>{{HTTPHeader("Tk")}} header</li>
-  <li><a href="https://en.wikipedia.org/wiki/Do_Not_Track">Do Not Track on Wikipedia</a>
-  </li>
-  <li><a
-      href="https://www.eff.org/deeplinks/2011/02/what-does-track-do-not-track-mean">What
-      Does the "Track" in "Do Not Track" Mean? – EFF</a></li>
-  <li><a href="https://donottrack.us/">donottrack.us</a></li>
-  <li>DNT browser settings help:
-    <ul>
-      <li><a href="https://www.mozilla.org/en-US/firefox/dnt/">Firefox</a></li>
-      <li><a href="https://support.google.com/chrome/answer/2790761">Chrome</a></li>
-    </ul>
-  </li>
-</ul>
+## Browser compatibility
+
+{{Compat}}
+
+## See also
+
+- {{domxref("Navigator.doNotTrack")}}
+- {{HTTPHeader("Tk")}} header
+- [Do Not Track on Wikipedia](https://en.wikipedia.org/wiki/Do_Not_Track)
+- [What
+  Does the "Track" in "Do Not Track" Mean? – EFF](https://www.eff.org/deeplinks/2011/02/what-does-track-do-not-track-mean)
+- [donottrack.us](https://donottrack.us/)
+- DNT browser settings help:
+
+  - [Firefox](https://www.mozilla.org/en-US/firefox/dnt/)
+  - [Chrome](https://support.google.com/chrome/answer/2790761)
diff --git a/files/en-us/web/http/headers/downlink/index.md b/files/en-us/web/http/headers/downlink/index.md
index d6db253ec7912c1..5fb4dbf2de6888c 100644
--- a/files/en-us/web/http/headers/downlink/index.md
+++ b/files/en-us/web/http/headers/downlink/index.md
@@ -11,72 +11,68 @@ tags:
   - Experimental
 browser-compat: http.headers.downlink
 ---
-<div>{{HTTPSidebar}} {{SeeCompatTable}}</div>
+{{HTTPSidebar}} {{SeeCompatTable}}
 
-<p>The <strong><code>Downlink</code></strong> {{Glossary("Client hints","network client hint")}} request header field provides the approximate bandwidth of the client's connection to the server, in Mbps.</p>
+The **`Downlink`** {{Glossary("Client hints","network client hint")}} request header field provides the approximate bandwidth of the client's connection to the server, in Mbps.
 
 <table class="properties">
   <tbody>
-   <tr>
-    <th scope="row">Header type</th>
-    <td>{{Glossary("Request header")}}, {{Glossary("Client hints","Client hint")}}</td>
-   </tr>
-   <tr>
-    <th scope="row">{{Glossary("Forbidden header name")}}</th>
-    <td>no</td>
-   </tr>
+    <tr>
+      <th scope="row">Header type</th>
+      <td>
+        {{Glossary("Request header")}},
+        {{Glossary("Client hints","Client hint")}}
+      </td>
+    </tr>
+    <tr>
+      <th scope="row">{{Glossary("Forbidden header name")}}</th>
+      <td>no</td>
+    </tr>
   </tbody>
- </table>
+</table>
 
-<p>The <code>Downlink</code> value is given in Mbps and rounded to the nearest 25 kilobits per second to prevent fingerprinting; There are many other mechanisms an attacker might use to obtain similar information.</p>
+The `Downlink` value is given in Mbps and rounded to the nearest 25 kilobits per second to prevent fingerprinting; There are many other mechanisms an attacker might use to obtain similar information.
 
-<p>The hint allows a server to choose what information is sent based on the network bandwidth. For example, a server might choose to send smaller versions of images and other resources on low bandwidth networks.</p>
+The hint allows a server to choose what information is sent based on the network bandwidth. For example, a server might choose to send smaller versions of images and other resources on low bandwidth networks.
 
-<div class="notecard note">
-  <p><strong>Note:</strong> The {{HTTPHeader("Vary")}} header is used in responses to indicate that a different resource is sent for every different value of the header (see <a href="/en-US/docs/Web/HTTP/Caching#varying_responses">HTTP Caching > Varying responses</a>). Even if {{HTTPHeader("Downlink")}} is used to configure what resources are sent, consider omitting it in the {{HTTPHeader("Vary")}} header — it is likely to change often, which effectively makes the resource uncachable.</p>
-</div>
+> **Note:** The {{HTTPHeader("Vary")}} header is used in responses to indicate that a different resource is sent for every different value of the header (see [HTTP Caching > Varying responses](/en-US/docs/Web/HTTP/Caching#varying_responses)). Even if {{HTTPHeader("Downlink")}} is used to configure what resources are sent, consider omitting it in the {{HTTPHeader("Vary")}} header — it is likely to change often, which effectively makes the resource uncachable.
 
-<h2 id="Syntax">Syntax</h2>
+## Syntax
 
-<pre>Downlink: &lt;number&gt;</pre>
+    Downlink: <number>
 
-<h2 id="Directives">Directives</h2>
+## Directives
 
-<dl>
- <dt>&lt;number&gt;</dt>
- <dd>The downlink rate in Mbps, rounded to the nearest 25 kilobits.</dd>
-</dl>
+- \<number>
+  - : The downlink rate in Mbps, rounded to the nearest 25 kilobits.
 
-<h2 id="Examples">Examples</h2>
+## Examples
 
-<p>A server first needs to opt in to receive the <code>Downlink</code> header by sending the {{HTTPHeader("Accept-CH")}} response header containing <code>Downlink</code>.</p>
+A server first needs to opt in to receive the `Downlink` header by sending the {{HTTPHeader("Accept-CH")}} response header containing `Downlink`.
 
-<pre>Accept-CH: Downlink</pre>
+    Accept-CH: Downlink
 
-<p>Then on subsequent requests the client might send a <code>Downlink</code> header back:</p>
+Then on subsequent requests the client might send a `Downlink` header back:
 
-<pre>Downlink: 1.7</pre>
+    Downlink: 1.7
 
-<h2 id="Specifications">Specifications</h2>
+## Specifications
 
-<p>{{Specifications}}</p>
+{{Specifications}}
 
-<h2 id="Browser_compatibility">Browser compatibility</h2>
+## Browser compatibility
 
-<p>{{Compat}}</p>
+{{Compat}}
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
-  <li><a href="https://developers.google.com/web/fundamentals/performance/optimizing-content-efficiency/client-hints">Adapting to Users with Client Hints</a> (developer.google.com)</li>
- <li>Network client hints
-  <ul>
-    <li>{{HTTPHeader("RTT")}}</li>
-    <li>{{HTTPHeader("ECT")}}</li>
-    <li>{{HTTPHeader("Save-Data")}}</li>
-   </ul>
- </li>
- <li>{{HTTPHeader("Accept-CH")}}</li>
- <li><a href="/en-US/docs/Web/HTTP/Caching#varying_responses">HTTP Caching > Varying responses</a> and {{HTTPHeader("Vary")}}</li>
- <li>{{domxref("NetworkInformation.effectiveType")}}</li>
-</ul>
+- [Adapting to Users with Client Hints](https://developers.google.com/web/fundamentals/performance/optimizing-content-efficiency/client-hints) (developer.google.com)
+- Network client hints
+
+  - {{HTTPHeader("RTT")}}
+  - {{HTTPHeader("ECT")}}
+  - {{HTTPHeader("Save-Data")}}
+
+- {{HTTPHeader("Accept-CH")}}
+- [HTTP Caching > Varying responses](/en-US/docs/Web/HTTP/Caching#varying_responses) and {{HTTPHeader("Vary")}}
+- {{domxref("NetworkInformation.effectiveType")}}
diff --git a/files/en-us/web/http/headers/dpr/index.md b/files/en-us/web/http/headers/dpr/index.md
index 2f167c8d00cc71d..437453ea1a11021 100644
--- a/files/en-us/web/http/headers/dpr/index.md
+++ b/files/en-us/web/http/headers/dpr/index.md
@@ -12,85 +12,75 @@ tags:
   - Exerimental
 browser-compat: http.headers.DPR
 ---
-<div>{{HTTPSidebar}} {{deprecated_header}}{{securecontext_header}}</div>
+{{HTTPSidebar}} {{deprecated_header}}{{securecontext_header}}
 
-<p>The <strong><code>DPR</code></strong> <a href="/en-US/docs/Glossary/Client_hints">device client hint</a> request header provides the client device pixel ratio. This ratio is the number of physical device pixels corresponding to every {{Glossary("CSS pixel")}}.</p>
+The **`DPR`** [device client hint](/en-US/docs/Glossary/Client_hints) request header provides the client device pixel ratio. This ratio is the number of physical device pixels corresponding to every {{Glossary("CSS pixel")}}.
 
 <table class="properties">
   <tbody>
-   <tr>
-    <th scope="row">Header type</th>
-    <td>{{Glossary("Request header")}}, {{Glossary("Client hints","Client hint")}}</td>
-   </tr>
-   <tr>
-    <th scope="row">{{Glossary("Forbidden header name")}}</th>
-    <td>no</td>
-   </tr>
+    <tr>
+      <th scope="row">Header type</th>
+      <td>
+        {{Glossary("Request header")}},
+        {{Glossary("Client hints","Client hint")}}
+      </td>
+    </tr>
+    <tr>
+      <th scope="row">{{Glossary("Forbidden header name")}}</th>
+      <td>no</td>
+    </tr>
   </tbody>
- </table>
+</table>
 
-<p>The hint is useful when selecting image sources that best correspond to a screen's pixel density. This is similar to the role played by <code>x</code> descriptors in the <code>&lt;img&gt;</code> <a href="/en-US/docs/Web/HTML/Element/img#attr-srcset"><code>srcset</code></a> attribute to allow user agents to select a preferred image.</p>
+The hint is useful when selecting image sources that best correspond to a screen's pixel density. This is similar to the role played by `x` descriptors in the `<img>` [`srcset`](/en-US/docs/Web/HTML/Element/img#attr-srcset) attribute to allow user agents to select a preferred image.
 
-<p>If a server uses the <code>DPR</code> hint to choose which resource is sent in a response, the response must include the {{HTTPHeader("Content-DPR")}} header. The client must use the value in <code>Content-DPR</code> for layout if it differs from the value in the request's <code>DPR</code> header.</p>
+If a server uses the `DPR` hint to choose which resource is sent in a response, the response must include the {{HTTPHeader("Content-DPR")}} header. The client must use the value in `Content-DPR` for layout if it differs from the value in the request's `DPR` header.
 
-<p>If the <code>DPR</code> header appears more than once in a message the last occurrence is used.</p>
+If the `DPR` header appears more than once in a message the last occurrence is used.
 
-<div class="notecard note">
-  <p><strong>Note:</strong></p>
-    <ul>
-      <li>Client Hints are accessible only on secure origins (via TLS).</li>
-      <li>A server has to opt in to receive the <code>DPR</code> header from the client, by sending the {{HTTPHeader("Accept-CH")}} response header.</li>
-      <li>Servers that opt in to the <code>DPR</code> client hint will typically also specify it in the {{HTTPHeader("Vary")}} header. This informs caches that the server may send different responses based on the header value in a request.</li>
-      <li><code>DPR</code> was removed from the client hints specification in <a href="https://datatracker.ietf.org/doc/html/draft-ietf-httpbis-client-hints-07">draft-ietf-httpbis-client-hints-07</a>. The proposed replacement is <a href="https://wicg.github.io/responsive-image-client-hints/#sec-ch-dpr"><code>Sec-CH-DPR</code></a> (Responsive Image Client Hints).</li>
-    </ul>
-</div>
+> **Note:**
+>
+> - Client Hints are accessible only on secure origins (via TLS).
+> - A server has to opt in to receive the `DPR` header from the client, by sending the {{HTTPHeader("Accept-CH")}} response header.
+> - Servers that opt in to the `DPR` client hint will typically also specify it in the {{HTTPHeader("Vary")}} header. This informs caches that the server may send different responses based on the header value in a request.
+> - `DPR` was removed from the client hints specification in [draft-ietf-httpbis-client-hints-07](https://datatracker.ietf.org/doc/html/draft-ietf-httpbis-client-hints-07). The proposed replacement is [`Sec-CH-DPR`](https://wicg.github.io/responsive-image-client-hints/#sec-ch-dpr) (Responsive Image Client Hints).
 
-<h2 id="Syntax">Syntax</h2>
+## Syntax
 
-<pre>DPR: &lt;number&gt;</pre>
+    DPR: <number>
 
-<h2 id="Directives">Directives</h2>
+## Directives
 
-<dl>
- <dt><code> &lt;number&gt;</code></dt>
- <dd>The client device pixel ratio.</dd>
-</dl>
+- `<number>`
+  - : The client device pixel ratio.
 
-<h2 id="Examples">Examples</h2>
+## Examples
 
-<p>A server must first opt in to receive the <code>DPR</code> header by sending the response header {{HTTPHeader("Accept-CH")}} containing the directive <code>DPR</code>.</p>
+A server must first opt in to receive the `DPR` header by sending the response header {{HTTPHeader("Accept-CH")}} containing the directive `DPR`.
 
-<pre>Accept-CH: DPR</pre>
+    Accept-CH: DPR
 
-<p>Then on subsequent requests the client might send <code>DPR</code> header to the server:</p>
+Then on subsequent requests the client might send `DPR` header to the server:
 
-<pre>DPR: 2.0
-</pre>
+    DPR: 2.0
 
-<p>If a request with the <code>DPR</code> header (as shown above) is for an image resource, then the server response must include the {{HTTPHeader("Content-DPR")}} header:</p>
+If a request with the `DPR` header (as shown above) is for an image resource, then the server response must include the {{HTTPHeader("Content-DPR")}} header:
 
-<pre>Content-DPR: 2.0
-</pre>
+    Content-DPR: 2.0
 
-<h2 id="Browser_compatibility">Browser compatibility</h2>
+## Browser compatibility
 
-<p>{{Compat}}</p>
+{{Compat}}
 
+## See also
 
-<h2 id="See_also">See also</h2>
-
-<ul>
-  <li><a href="https://developers.google.com/web/fundamentals/performance/optimizing-content-efficiency/client-hints">Adapting to Users with Client Hints</a> (developer.google.com)</li>
- <li>Device client hints
-  <ul>
-    <li>{{HTTPHeader("Content-DPR")}}</li>
-    <li>{{HTTPHeader("Device-Memory")}}</li>
-    <li>{{HTTPHeader("Viewport-Width")}}</li>
-    <li>{{HTTPHeader("Width")}}</li>
-   </ul>
- </li>
- <li>{{HTTPHeader("Accept-CH")}}</li>
- <li><a href="/en-US/docs/Web/HTTP/Caching#varying_responses">HTTP Caching > Varying responses</a> and {{HTTPHeader("Vary")}}</li>
-</ul>
+- [Adapting to Users with Client Hints](https://developers.google.com/web/fundamentals/performance/optimizing-content-efficiency/client-hints) (developer.google.com)
+- Device client hints
 
+  - {{HTTPHeader("Content-DPR")}}
+  - {{HTTPHeader("Device-Memory")}}
+  - {{HTTPHeader("Viewport-Width")}}
+  - {{HTTPHeader("Width")}}
 
+- {{HTTPHeader("Accept-CH")}}
+- [HTTP Caching > Varying responses](/en-US/docs/Web/HTTP/Caching#varying_responses) and {{HTTPHeader("Vary")}}
diff --git a/files/en-us/web/http/headers/early-data/index.md b/files/en-us/web/http/headers/early-data/index.md
index bbed841965da952..e00fb03acd0dc2f 100644
--- a/files/en-us/web/http/headers/early-data/index.md
+++ b/files/en-us/web/http/headers/early-data/index.md
@@ -11,16 +11,15 @@ tags:
   - Experimental
 browser-compat: http.headers.Early-Data
 ---
-<div>{{SeeCompatTable}}{{HTTPSidebar}}</div>
+{{SeeCompatTable}}{{HTTPSidebar}}
 
-<p>The <code><strong>Early-Data</strong></code> header is set by
-    an intermediary to indicate that the request has been conveyed in <a
-      href="/en-US/docs/Web/Security/Transport_Layer_Security#tls_1.3">TLS early data</a>,
-    and also indicates that the intermediary understands the {{HTTPStatus("425", "425 (Too
-    Early)")}} status code.</p>
+The **`Early-Data`** header is set by
+an intermediary to indicate that the request has been conveyed in [TLS early data](/en-US/docs/Web/Security/Transport_Layer_Security#tls_1.3),
+and also indicates that the intermediary understands the {{HTTPStatus("425", "425 (Too
+    Early)")}} status code.
 
-<p>The <code>Early-Data</code> header is <strong>not</strong> set by the originator of the
-  request (i.e., a browser).</p>
+The `Early-Data` header is **not** set by the originator of the
+request (i.e., a browser).
 
 <table class="properties">
   <tbody>
@@ -35,21 +34,22 @@ browser-compat: http.headers.Early-Data
   </tbody>
 </table>
 
-<h2 id="Syntax">Syntax</h2>
+## Syntax
 
-<pre class="brush: html">Early-Data: 1
-</pre>
+```html
+Early-Data: 1
+```
 
-<h2 id="Examples">Examples</h2>
+## Examples
 
-<pre>GET /resource HTTP/1.0
-Host: example.com
-Early-Data: 1</pre>
+    GET /resource HTTP/1.0
+    Host: example.com
+    Early-Data: 1
 
-<h2 id="Specifications">Specifications</h2>
+## Specifications
 
 {{Specifications}}
 
-<h2 id="Browser_compatibility">Browser compatibility</h2>
+## Browser compatibility
 
-<p>{{Compat}}</p>
+{{Compat}}
diff --git a/files/en-us/web/http/headers/ect/index.md b/files/en-us/web/http/headers/ect/index.md
index 5475017515c7210..987564c5e69b170 100644
--- a/files/en-us/web/http/headers/ect/index.md
+++ b/files/en-us/web/http/headers/ect/index.md
@@ -11,73 +11,68 @@ tags:
   - Experimental
 browser-compat: http.headers.ect
 ---
-<div>{{HTTPSidebar}} {{SeeCompatTable}}</div>
+{{HTTPSidebar}} {{SeeCompatTable}}
 
-<p>The <strong><code>ECT</code></strong> {{Glossary("Client hints","network client hint")}} request header field indicates the {{Glossary("effective connection type")}}: <code>slow-2g</code>, <code>2g</code>, <code>3g</code>, <code>4g</code>.</p>
+The **`ECT`** {{Glossary("Client hints","network client hint")}} request header field indicates the {{Glossary("effective connection type")}}: `slow-2g`, `2g`, `3g`, `4g`.
 
 <table class="properties">
   <tbody>
-   <tr>
-    <th scope="row">Header type</th>
-    <td>{{Glossary("Request header")}}, {{Glossary("Client hints","Client hint")}}</td>
-   </tr>
-   <tr>
-    <th scope="row">{{Glossary("Forbidden header name")}}</th>
-    <td>no</td>
-   </tr>
+    <tr>
+      <th scope="row">Header type</th>
+      <td>
+        {{Glossary("Request header")}},
+        {{Glossary("Client hints","Client hint")}}
+      </td>
+    </tr>
+    <tr>
+      <th scope="row">{{Glossary("Forbidden header name")}}</th>
+      <td>no</td>
+    </tr>
   </tbody>
- </table>
+</table>
 
- <p>The value represents the "network profile" that best matches the connection's latency and bandwidth, rather than the actual mechanisms used for transferring the data. For example, <code>2g</code> might be used to represent a slow wifi connection with high latency and low bandwidth, while <code>4g</code> might be used to represent a fast fibre-based broadband network.</p>
+The value represents the "network profile" that best matches the connection's latency and bandwidth, rather than the actual mechanisms used for transferring the data. For example, `2g` might be used to represent a slow wifi connection with high latency and low bandwidth, while `4g` might be used to represent a fast fibre-based broadband network.
 
-<p>The hint allows a server to choose what information is sent based on the broad characteristics of the network. For example, a server might choose to send smaller versions of images and other resources on less capable connections. The value might also be used as a starting point for determining what information is sent, which is further refined using information in {{HTTPHeader("RTT")}} and {{HTTPHeader("Downlink")}} hints.</p>
+The hint allows a server to choose what information is sent based on the broad characteristics of the network. For example, a server might choose to send smaller versions of images and other resources on less capable connections. The value might also be used as a starting point for determining what information is sent, which is further refined using information in {{HTTPHeader("RTT")}} and {{HTTPHeader("Downlink")}} hints.
 
-<div class="notecard note">
-  <p><strong>Note:</strong> A server that specifies {{HTTPHeader("ECT")}} in {{HTTPHeader("Accept-CH")}} may also specify it in {{HTTPHeader("Vary")}} to indicate that responses should be cached for different ECT values.</p>
-</div>
+> **Note:** A server that specifies {{HTTPHeader("ECT")}} in {{HTTPHeader("Accept-CH")}} may also specify it in {{HTTPHeader("Vary")}} to indicate that responses should be cached for different ECT values.
 
-<h2 id="Syntax">Syntax</h2>
+## Syntax
 
-<pre>ECT: &lt;value&gt;</pre>
+    ECT: <value>
 
-<h2 id="Directives">Directives</h2>
+## Directives
 
-<dl>
- <dt>&lt;value&gt;</dt>
- <dd>A value indicating {{Glossary("effective connection type")}}. This is one of: <code>slow-2g</code>, <code>2g</code>, <code>3g</code>, or <code>4g</code>.</dd>
-</dl>
+- \<value>
+  - : A value indicating {{Glossary("effective connection type")}}. This is one of: `slow-2g`, `2g`, `3g`, or `4g`.
 
-<h2 id="Examples">Examples</h2>
+## Examples
 
-<p>A server first needs to opt in to receive the <code>ECT</code> header by sending the {{HTTPHeader("Accept-CH")}} response header containing <code>ECT</code>.</p>
+A server first needs to opt in to receive the `ECT` header by sending the {{HTTPHeader("Accept-CH")}} response header containing `ECT`.
 
-<pre>Accept-CH: ECT</pre>
+    Accept-CH: ECT
 
-<p>Then on subsequent requests the client might send an <code>ECT</code> header back:</p>
+Then on subsequent requests the client might send an `ECT` header back:
 
-<pre>ECT: 2g</pre>
+    ECT: 2g
 
-<h2 id="Specifications">Specifications</h2>
+## Specifications
 
-<p>{{Specifications}}</p>
+{{Specifications}}
 
-<h2 id="Browser_compatibility">Browser compatibility</h2>
+## Browser compatibility
 
-<p>{{Compat}}</p>
+{{Compat}}
 
+## See also
 
-<h2 id="See_also">See also</h2>
+- [Adapting to Users with Client Hints](https://developers.google.com/web/fundamentals/performance/optimizing-content-efficiency/client-hints) (developer.google.com)
+- Network client hints
 
-<ul>
-  <li><a href="https://developers.google.com/web/fundamentals/performance/optimizing-content-efficiency/client-hints">Adapting to Users with Client Hints</a> (developer.google.com)</li>
- <li>Network client hints
-  <ul>
-    <li>{{HTTPHeader("Downlink")}}</li>
-    <li>{{HTTPHeader("RTT")}}</li>
-    <li>{{HTTPHeader("Save-Data")}}</li>
-   </ul>
- </li>
- <li>{{HTTPHeader("Accept-CH")}}</li>
- <li><a href="/en-US/docs/Web/HTTP/Caching#varying_responses">HTTP Caching > Varying responses</a> and {{HTTPHeader("Vary")}}</li>
- <li>{{domxref("NetworkInformation.effectiveType")}}</li>
-</ul>
+  - {{HTTPHeader("Downlink")}}
+  - {{HTTPHeader("RTT")}}
+  - {{HTTPHeader("Save-Data")}}
+
+- {{HTTPHeader("Accept-CH")}}
+- [HTTP Caching > Varying responses](/en-US/docs/Web/HTTP/Caching#varying_responses) and {{HTTPHeader("Vary")}}
+- {{domxref("NetworkInformation.effectiveType")}}
diff --git a/files/en-us/web/http/headers/etag/index.md b/files/en-us/web/http/headers/etag/index.md
index 3b361ca1bccb754..6e9bdbd813bdf54 100644
--- a/files/en-us/web/http/headers/etag/index.md
+++ b/files/en-us/web/http/headers/etag/index.md
@@ -8,19 +8,19 @@ tags:
   - header
 browser-compat: http.headers.ETag
 ---
-<div>{{HTTPSidebar}}</div>
+{{HTTPSidebar}}
 
-<p>The <strong><code>ETag</code></strong> HTTP response header is an identifier for a
-  specific version of a resource. It lets caches be more efficient and save bandwidth, as
-  a web server does not need to resend a full response if the content has not changed.
-  Additionally, etags help prevent simultaneous updates of a resource from overwriting
-  each other (<a href="#avoiding_mid-air_collisions">"mid-air collisions"</a>).</p>
+The **`ETag`** HTTP response header is an identifier for a
+specific version of a resource. It lets caches be more efficient and save bandwidth, as
+a web server does not need to resend a full response if the content has not changed.
+Additionally, etags help prevent simultaneous updates of a resource from overwriting
+each other (["mid-air collisions"](#avoiding_mid-air_collisions)).
 
-<p>If the resource at a given URL changes, a new <code>Etag</code> value <em>must</em> be
-  generated. A comparison of them can determine whether two representations of a resource
-  are the same. Etags are therefore similar to fingerprints, and might also be used for
-  tracking purposes by some servers. They might also be set to persist indefinitely by a
-  tracking server.</p>
+If the resource at a given URL changes, a new `Etag` value _must_ be
+generated. A comparison of them can determine whether two representations of a resource
+are the same. Etags are therefore similar to fingerprints, and might also be used for
+tracking purposes by some servers. They might also be set to persist indefinitely by a
+tracking server.
 
 <table class="properties">
   <tbody>
@@ -35,90 +35,83 @@ browser-compat: http.headers.ETag
   </tbody>
 </table>
 
-<h2 id="Syntax">Syntax</h2>
+## Syntax
 
-<pre class="brush: html">ETag: W/"&lt;etag_value&gt;"
-ETag: "&lt;etag_value&gt;"
-</pre>
+```html
+ETag: W/"<etag_value>"
+ETag: "<etag_value>"
+```
 
-<h2 id="Directives">Directives</h2>
+## Directives
 
-<dl>
-  <dt><code>W/</code> {{optional_inline}}</dt>
-  <dd><code>'W/'</code> (case-sensitive) indicates that a <a
-      href="/en-US/docs/Web/HTTP/Conditional_requests#weak_validation">weak validator</a>
+- `W/` {{optional_inline}}
+  - : `'W/'` (case-sensitive) indicates that a [weak validator](/en-US/docs/Web/HTTP/Conditional_requests#weak_validation)
     is used. Weak etags are easy to generate, but are far less useful for comparisons.
     Strong validators are ideal for comparisons but can be very difficult to generate
-    efficiently. Weak <code>ETag</code> values of two representations of the same
+    efficiently. Weak `ETag` values of two representations of the same
     resources might be semantically equivalent, but not byte-for-byte identical. This
-    means weak etags prevent caching when <a
-      href="/en-US/docs/Web/HTTP/Headers/Accept-Ranges">byte range requests</a> are used,
-    but strong etags mean range requests can still be cached.</dd>
-  <dt>"&lt;etag_value&gt;"</dt>
-  <dd>Entity tag uniquely representing the requested resource. They are a string of ASCII
-    characters placed between double quotes, like <code>"675af34563dc-tr34"</code>. The
-    method by which <code>ETag</code> values are generated is not specified. Often, a hash
+    means weak etags prevent caching when [byte range requests](/en-US/docs/Web/HTTP/Headers/Accept-Ranges) are used,
+    but strong etags mean range requests can still be cached.
+- "\<etag_value>"
+  - : Entity tag uniquely representing the requested resource. They are a string of ASCII
+    characters placed between double quotes, like `"675af34563dc-tr34"`. The
+    method by which `ETag` values are generated is not specified. Often, a hash
     of the content, a hash of the last modification timestamp, or just a revision number
-    is used. For example, MDN uses a hexadecimal hash of the wiki article content.</dd>
-</dl>
+    is used. For example, MDN uses a hexadecimal hash of the wiki article content.
 
-<h2 id="Examples">Examples</h2>
+## Examples
 
-<pre>ETag: "33a64df551425fcc55e4d42a148795d9f25f89d4"
-ETag: W/"0815"</pre>
+    ETag: "33a64df551425fcc55e4d42a148795d9f25f89d4"
+    ETag: W/"0815"
 
-<h3 id="Avoiding_mid-air_collisions">Avoiding mid-air collisions</h3>
+### Avoiding mid-air collisions
 
-<p>With the help of the <code>ETag</code> and the {{HTTPHeader("If-Match")}} headers, you
-  can detect mid-air edit collisions.</p>
+With the help of the `ETag` and the {{HTTPHeader("If-Match")}} headers, you
+can detect mid-air edit collisions.
 
-<p>For example, when editing a wiki, the current wiki content may be hashed
-  and put into an <code>Etag</code> header in the response:</p>
+For example, when editing a wiki, the current wiki content may be hashed
+and put into an `Etag` header in the response:
 
-<pre>ETag: "33a64df551425fcc55e4d42a148795d9f25f89d4"</pre>
+    ETag: "33a64df551425fcc55e4d42a148795d9f25f89d4"
 
-<p>When saving changes to a wiki page (posting data), the {{HTTPMethod("POST")}} request
-  will contain the {{HTTPHeader("If-Match")}} header containing the <code>ETag</code>
-  values to check freshness against.</p>
+When saving changes to a wiki page (posting data), the {{HTTPMethod("POST")}} request
+will contain the {{HTTPHeader("If-Match")}} header containing the `ETag`
+values to check freshness against.
 
-<pre>If-Match: "33a64df551425fcc55e4d42a148795d9f25f89d4"</pre>
+    If-Match: "33a64df551425fcc55e4d42a148795d9f25f89d4"
 
-<p>If the hashes don't match, it means that the document has been edited in-between and a
-  {{HTTPStatus("412")}} <code>Precondition Failed</code> error is thrown.</p>
+If the hashes don't match, it means that the document has been edited in-between and a
+{{HTTPStatus("412")}} `Precondition Failed` error is thrown.
 
-<h3 id="Caching_of_unchanged_resources">Caching of unchanged resources</h3>
+### Caching of unchanged resources
 
-<p>Another typical use of the <code>ETag</code> header is to cache resources that are
-  unchanged. If a user visits a given URL again (that has an <code>ETag</code> set), and
-  it is <em>stale</em> (too old to be considered usable), the client will send the value
-  of its <code>ETag</code> along in an {{HTTPHeader("If-None-Match")}} header field:</p>
+Another typical use of the `ETag` header is to cache resources that are
+unchanged. If a user visits a given URL again (that has an `ETag` set), and
+it is _stale_ (too old to be considered usable), the client will send the value
+of its `ETag` along in an {{HTTPHeader("If-None-Match")}} header field:
 
-<pre>If-None-Match: "33a64df551425fcc55e4d42a148795d9f25f89d4"</pre>
+    If-None-Match: "33a64df551425fcc55e4d42a148795d9f25f89d4"
 
-<p>The server compares the client's <code>ETag</code> (sent with
-  <code>If-None-Match</code>) with the <code>ETag</code> for its current version of the
-  resource, and if both values match (that is, the resource has not changed), the server
-  sends back a {{HTTPStatus("304")}} <code>Not Modified</code> status, without a body,
-  which tells the client that the cached version of the response is still good to use
-  (<em>fresh</em>).</p>
+The server compares the client's `ETag` (sent with
+`If-None-Match`) with the `ETag` for its current version of the
+resource, and if both values match (that is, the resource has not changed), the server
+sends back a {{HTTPStatus("304")}} `Not Modified` status, without a body,
+which tells the client that the cached version of the response is still good to use
+(_fresh_).
 
-<h2 id="Specifications">Specifications</h2>
+## Specifications
 
 {{Specifications}}
 
-<h2 id="Browser_compatibility">Browser compatibility</h2>
+## Browser compatibility
 
-<p>{{Compat}}</p>
+{{Compat}}
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
-  <li>{{HTTPHeader("If-Match")}}</li>
-  <li>{{HTTPHeader("If-None-Match")}}</li>
-  <li>{{HTTPStatus("304")}}<code> Not Modified</code></li>
-  <li>{{HTTPStatus("412")}}<code> Precondition Failed</code></li>
-  <li>
-    <p><a href="https://www.w3.org/1999/04/Editing/">W3C Note: Editing the Web – Detecting
-        the Lost Update Problem Using Unreserved Checkout</a></p>
-  </li>
-</ul>
+- {{HTTPHeader("If-Match")}}
+- {{HTTPHeader("If-None-Match")}}
+- {{HTTPStatus("304")}}` Not Modified`
+- {{HTTPStatus("412")}}` Precondition Failed`
+- [W3C Note: Editing the Web – Detecting
+  the Lost Update Problem Using Unreserved Checkout](https://www.w3.org/1999/04/Editing/)
diff --git a/files/en-us/web/http/headers/expect-ct/index.md b/files/en-us/web/http/headers/expect-ct/index.md
index bddba55da11032d..d5cb81b278e644f 100644
--- a/files/en-us/web/http/headers/expect-ct/index.md
+++ b/files/en-us/web/http/headers/expect-ct/index.md
@@ -7,101 +7,81 @@ tags:
   - header
 browser-compat: http.headers.Expect-CT
 ---
-<p>{{HTTPSidebar}}</p>
+{{HTTPSidebar}}
 
-<p>The <code>Expect-CT</code> header lets sites opt in to reporting and/or enforcement of <a href="/en-US/docs/Web/Security/Certificate_Transparency">Certificate Transparency</a> requirements, to prevent the use of misissued certificates for that site from going unnoticed.</p>
+The `Expect-CT` header lets sites opt in to reporting and/or enforcement of [Certificate Transparency](/en-US/docs/Web/Security/Certificate_Transparency) requirements, to prevent the use of misissued certificates for that site from going unnoticed.
 
-<p>CT requirements can be satisfied via any one of the following mechanisms:</p>
+CT requirements can be satisfied via any one of the following mechanisms:
 
-<ul>
- <li>X.509v3 certificate extension to allow embedding of signed certificate timestamps issued by individual logs</li>
- <li>A TLS extension of type <code>signed_certificate_timestamp</code> sent during the handshake</li>
- <li>Supporting OCSP stapling (that is, the <code>status_request</code> TLS extension) and providing a <code>SignedCertificateTimestampList</code></li>
-</ul>
+- X.509v3 certificate extension to allow embedding of signed certificate timestamps issued by individual logs
+- A TLS extension of type `signed_certificate_timestamp` sent during the handshake
+- Supporting OCSP stapling (that is, the `status_request` TLS extension) and providing a `SignedCertificateTimestampList`
 
-<div class="notecard note">
-  <p><strong>Note:</strong> When a site enables the <code>Expect-CT</code> header, they are requesting that the browser check that any certificate for that site appears in <strong><a href="https://www.certificate-transparency.org/known-logs">public CT logs</a></strong>.</p>
-</div>
+> **Note:** When a site enables the `Expect-CT` header, they are requesting that the browser check that any certificate for that site appears in **[public CT logs](https://www.certificate-transparency.org/known-logs)**.
 
-<div class="notecard note">
-  <p><strong>Note:</strong> Browsers <strong>ignore</strong> the <code>Expect-CT</code> header over HTTP; the header only has effect on HTTPS connections.</p>
-</div>
+> **Note:** Browsers **ignore** the `Expect-CT` header over HTTP; the header only has effect on HTTPS connections.
 
-<div class="notecard note">
-<p><strong>Note:</strong> The <code>Expect-CT</code> will likely become obsolete in June 2021. Since May 2018 new certificates are expected to support SCTs by default. Certificates before March 2018 were allowed to have a lifetime of 39 months, those will all be expired in June 2021.</p>
-</div>
+> **Note:** The `Expect-CT` will likely become obsolete in June 2021. Since May 2018 new certificates are expected to support SCTs by default. Certificates before March 2018 were allowed to have a lifetime of 39 months, those will all be expired in June 2021.
 
 <table class="properties">
- <tbody>
-  <tr>
-   <th scope="row">Header type</th>
-   <td>{{Glossary("Response header")}}</td>
-  </tr>
-  <tr>
-   <th scope="row">{{Glossary("Forbidden header name")}}</th>
-   <td>yes</td>
-  </tr>
- </tbody>
+  <tbody>
+    <tr>
+      <th scope="row">Header type</th>
+      <td>{{Glossary("Response header")}}</td>
+    </tr>
+    <tr>
+      <th scope="row">{{Glossary("Forbidden header name")}}</th>
+      <td>yes</td>
+    </tr>
+  </tbody>
 </table>
 
-<h2 id="Syntax">Syntax</h2>
+## Syntax
 
-<pre>Expect-CT: report-uri="&lt;uri&gt;",
-           enforce,
-           max-age=&lt;age&gt;</pre>
+    Expect-CT: report-uri="<uri>",
+               enforce,
+               max-age=<age>
 
-<h2 id="Directives"> Directives</h2>
+##  Directives
 
-<dl>
- <dt><code>max-age</code></dt>
- <dd>
- <p>The number of seconds after reception of the <code>Expect-CT</code> header field during which the user agent should regard the host of the received message as a known <code>Expect-CT</code> host.</p>
+- `max-age`
 
- <p>If a cache receives a value greater than it can represent, or if any of its subsequent calculations overflows, the cache will consider this value to be either 2,147,483,648 (2^31) or the greatest positive integer it can represent.</p>
- </dd>
- <dt><code>report-uri="&lt;uri&gt;"</code> {{optional_inline}}</dt>
- <dd>
- <p>The URI where the user agent should report <code>Expect-CT</code> failures.</p>
- When present with the <code>enforce</code> directive, the configuration is referred to as an "enforce-and-report" configuration, signalling to the user agent both that compliance to the Certificate Transparency policy should be enforced <em>and</em> that violations should be reported.</dd>
- <dt><code>enforce</code> {{optional_inline}}</dt>
- <dd>
- <p>Signals to the user agent that compliance with the Certificate Transparency policy should be enforced (rather than only reporting compliance) and that the user agent should refuse future connections that violate its Certificate Transparency policy.</p>
+  - : The number of seconds after reception of the `Expect-CT` header field during which the user agent should regard the host of the received message as a known `Expect-CT` host.
 
- <p>When both the <code>enforce</code> directive and the <code>report-uri</code> directive are present, the configuration is referred to as an "enforce-and-report" configuration, signalling to the user agent both that compliance to the Certificate Transparency policy should be enforced and that violations should be reported.</p>
- </dd>
-</dl>
+    If a cache receives a value greater than it can represent, or if any of its subsequent calculations overflows, the cache will consider this value to be either 2,147,483,648 (2^31) or the greatest positive integer it can represent.
 
-<h2 id="Example">Example</h2>
+- `report-uri="<uri>"` {{optional_inline}}
 
-<p>The following example specifies enforcement of Certificate Transparency for 24 hours and reports violations to <code>foo.example</code>.</p>
+  - : The URI where the user agent should report `Expect-CT` failures.
 
-<pre>Expect-CT: max-age=86400, enforce, report-uri="https://foo.example/report"</pre>
+    When present with the `enforce` directive, the configuration is referred to as an "enforce-and-report" configuration, signalling to the user agent both that compliance to the Certificate Transparency policy should be enforced _and_ that violations should be reported.
 
-<h2 id="Notes">Notes</h2>
+- `enforce` {{optional_inline}}
 
-<p>Root CAs manually added to the trust store override and suppress <code>Expect-CT</code> reports/enforcement.</p>
+  - : Signals to the user agent that compliance with the Certificate Transparency policy should be enforced (rather than only reporting compliance) and that the user agent should refuse future connections that violate its Certificate Transparency policy.
 
-<p>Browsers will not remember an <code>Expect-CT</code> policy, unless the site has 'proven' it can serve a certificate satisfying the certificate transparency requirements. Browsers implement their own trust model regarding which CT logs are considered trusted for the certificate to have been logged to.</p>
+    When both the `enforce` directive and the `report-uri` directive are present, the configuration is referred to as an "enforce-and-report" configuration, signalling to the user agent both that compliance to the Certificate Transparency policy should be enforced and that violations should be reported.
 
-<p>Builds of Chrome are designed to stop enforcing the <code>Expect-CT</code> policy 10 weeks after the installation's build date.</p>
+## Example
 
-<h2 id="Specifications">Specifications</h2>
+The following example specifies enforcement of Certificate Transparency for 24 hours and reports violations to `foo.example`.
 
-<table class="standard-table">
- <thead>
-  <tr>
-   <th scope="col">Specification</th>
-   <th scope="col">Title</th>
-  </tr>
- </thead>
- <tbody>
-  <tr>
-   <td><a href="https://datatracker.ietf.org/doc/html/draft-ietf-httpbis-expect-ct-08">Internet Draft</a></td>
-   <td>Expect-CT Extension for HTTP</td>
-  </tr>
- </tbody>
-</table>
+    Expect-CT: max-age=86400, enforce, report-uri="https://foo.example/report"
+
+## Notes
+
+Root CAs manually added to the trust store override and suppress `Expect-CT` reports/enforcement.
+
+Browsers will not remember an `Expect-CT` policy, unless the site has 'proven' it can serve a certificate satisfying the certificate transparency requirements. Browsers implement their own trust model regarding which CT logs are considered trusted for the certificate to have been logged to.
+
+Builds of Chrome are designed to stop enforcing the `Expect-CT` policy 10 weeks after the installation's build date.
+
+## Specifications
+
+| Specification                                                                           | Title                        |
+| --------------------------------------------------------------------------------------- | ---------------------------- |
+| [Internet Draft](https://datatracker.ietf.org/doc/html/draft-ietf-httpbis-expect-ct-08) | Expect-CT Extension for HTTP |
 
-<h2 id="Browser_compatibility">Browser compatibility</h2>
+## Browser compatibility
 
-<p>{{Compat}}</p>
+{{Compat}}
diff --git a/files/en-us/web/http/headers/expect/index.md b/files/en-us/web/http/headers/expect/index.md
index a776dcf923e6355..b29c40331a6e3d1 100644
--- a/files/en-us/web/http/headers/expect/index.md
+++ b/files/en-us/web/http/headers/expect/index.md
@@ -2,32 +2,30 @@
 title: Expect
 slug: Web/HTTP/Headers/Expect
 tags:
-- HTTP
-- HTTP Header
-- Reference
-- Request header
+  - HTTP
+  - HTTP Header
+  - Reference
+  - Request header
 browser-compat: http.headers.Expect
 ---
-<div>{{HTTPSidebar}}</div>
+{{HTTPSidebar}}
 
-<p>The <strong><code>Expect</code></strong> HTTP request header indicates expectations
-  that need to be fulfilled by the server in order to properly handle the request.</p>
+The **`Expect`** HTTP request header indicates expectations
+that need to be fulfilled by the server in order to properly handle the request.
 
-<p>The only expectation defined in the specification is <code>Expect: 100-continue</code>,
-  to which the server shall respond with:</p>
+The only expectation defined in the specification is `Expect: 100-continue`,
+to which the server shall respond with:
 
-<ul>
-  <li>{{HTTPStatus("100")}} if the information contained in the header is sufficient to
-    cause an immediate success,</li>
-  <li>{{HTTPStatus("417")}} (Expectation Failed) if it cannot meet the expectation; or any
-    other 4xx status otherwise.</li>
-</ul>
+- {{HTTPStatus("100")}} if the information contained in the header is sufficient to
+  cause an immediate success,
+- {{HTTPStatus("417")}} (Expectation Failed) if it cannot meet the expectation; or any
+  other 4xx status otherwise.
 
-<p>For example, the server may reject a request if its {{HTTPHeader("Content-Length")}} is
-  too large.</p>
+For example, the server may reject a request if its {{HTTPHeader("Content-Length")}} is
+too large.
 
-<p>No common browsers send the <code>Expect</code> header, but some other clients such as
-  cURL do so by default.</p>
+No common browsers send the `Expect` header, but some other clients such as
+cURL do so by default.
 
 <table class="properties">
   <tbody>
@@ -42,52 +40,48 @@ browser-compat: http.headers.Expect
   </tbody>
 </table>
 
-<h2 id="Syntax">Syntax</h2>
+## Syntax
 
-<p>No other expectations except "100-continue" are specified currently.</p>
+No other expectations except "100-continue" are specified currently.
 
-<pre class="brush: html">Expect: 100-continue
-</pre>
+```html
+Expect: 100-continue
+```
 
-<h2 id="Directives">Directives</h2>
+## Directives
 
-<dl>
-  <dt>100-continue</dt>
-  <dd>Informs recipients that the client is about to send a (presumably large) message
+- 100-continue
+  - : Informs recipients that the client is about to send a (presumably large) message
     body in this request and wishes to receive a {{HTTPStatus("100")}} (Continue) interim
-    response.</dd>
-</dl>
+    response.
 
-<h2 id="Examples">Examples</h2>
+## Examples
 
-<h3 id="Large_message_body">Large message body</h3>
+### Large message body
 
-<p>A client sends a request with a Expect header and waits for the server to respond
-  before sending the message body.</p>
+A client sends a request with a Expect header and waits for the server to respond
+before sending the message body.
 
-<pre>PUT /somewhere/fun HTTP/1.1
-Host: origin.example.com
-Content-Type: video/h264
-Content-Length: 1234567890987
-Expect: 100-continue
-</pre>
+    PUT /somewhere/fun HTTP/1.1
+    Host: origin.example.com
+    Content-Type: video/h264
+    Content-Length: 1234567890987
+    Expect: 100-continue
 
-<p>The server now checks the request headers and may respond with a {{HTTPStatus("100")}}
-  (Continue) response to instruct the client to go ahead and send the message body, or it
-  will send a {{HTTPStatus("417")}} (Expectation Failed) status if any of the expectations
-  cannot be met.</p>
+The server now checks the request headers and may respond with a {{HTTPStatus("100")}}
+(Continue) response to instruct the client to go ahead and send the message body, or it
+will send a {{HTTPStatus("417")}} (Expectation Failed) status if any of the expectations
+cannot be met.
 
-<h2 id="Specifications">Specifications</h2>
+## Specifications
 
 {{Specifications}}
 
-<h2 id="Browser_compatibility">Browser compatibility</h2>
+## Browser compatibility
 
-<p>{{Compat}}</p>
+{{Compat}}
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
-  <li>{{HTTPStatus("417")}}<code> Expectation Failed</code></li>
-  <li>{{HTTPStatus("100")}}<code> Continue</code></li>
-</ul>
+- {{HTTPStatus("417")}}` Expectation Failed`
+- {{HTTPStatus("100")}}` Continue`
diff --git a/files/en-us/web/http/headers/expires/index.md b/files/en-us/web/http/headers/expires/index.md
index c2d991d762949f1..8be7c6b18c1ed25 100644
--- a/files/en-us/web/http/headers/expires/index.md
+++ b/files/en-us/web/http/headers/expires/index.md
@@ -2,25 +2,23 @@
 title: Expires
 slug: Web/HTTP/Headers/Expires
 tags:
-- Caching
-- HTTP
-- Response
-- header
+  - Caching
+  - HTTP
+  - Response
+  - header
 browser-compat: http.headers.Expires
 ---
-<div>{{HTTPSidebar}}</div>
+{{HTTPSidebar}}
 
-<p>The <code><strong>Expires</strong></code> header contains the date/time after which the
-  response is considered stale.</p>
+The **`Expires`** header contains the date/time after which the
+response is considered stale.
 
-<p>Invalid dates, like the value 0, represent a date in the past and mean that the
-  resource is already expired.</p>
+Invalid dates, like the value 0, represent a date in the past and mean that the
+resource is already expired.
 
-<div class="notecard note">
-  <p><strong>Note:</strong> If there is a {{HTTPHeader("Cache-Control")}} header
-    with the <code>max-age</code> or <code>s-maxage</code> directive in the response,
-    the <code>Expires</code> header is ignored.</p>
-</div>
+> **Note:** If there is a {{HTTPHeader("Cache-Control")}} header
+> with the `max-age` or `s-maxage` directive in the response,
+> the `Expires` header is ignored.
 
 <table class="properties">
   <tbody>
@@ -33,41 +31,38 @@ browser-compat: http.headers.Expires
       <td>no</td>
     </tr>
     <tr>
-      <th scope="row">{{Glossary("CORS-safelisted response header")}}</th>
+      <th scope="row">
+        {{Glossary("CORS-safelisted response header")}}
+      </th>
       <td>yes</td>
     </tr>
   </tbody>
 </table>
 
-<h2 id="Syntax">Syntax</h2>
+## Syntax
 
-<pre class="brush: html">Expires: &lt;http-date&gt;
-</pre>
+```html
+Expires: <http-date>
+```
 
-<h2 id="Directives">Directives</h2>
+## Directives
 
-<dl>
-  <dt>&lt;http-date&gt;</dt>
-  <dd>
-    <p>An HTTP-date timestamp.</p>
-  </dd>
-</dl>
+- \<http-date>
+  - : An HTTP-date timestamp.
 
-<h2 id="Examples">Examples</h2>
+## Examples
 
-<pre>Expires: Wed, 21 Oct 2015 07:28:00 GMT</pre>
+    Expires: Wed, 21 Oct 2015 07:28:00 GMT
 
-<h2 id="Specifications">Specifications</h2>
+## Specifications
 
 {{Specifications}}
 
-<h2 id="Browser_compatibility">Browser compatibility</h2>
+## Browser compatibility
 
-<p>{{Compat}}</p>
+{{Compat}}
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
-  <li>{{HTTPHeader("Cache-Control")}}</li>
-  <li>{{HTTPHeader("Age")}}</li>
-</ul>
+- {{HTTPHeader("Cache-Control")}}
+- {{HTTPHeader("Age")}}
diff --git a/files/en-us/web/http/headers/feature-policy/accelerometer/index.md b/files/en-us/web/http/headers/feature-policy/accelerometer/index.md
index 7d3f4597e740ee4..66d3150a0df273b 100644
--- a/files/en-us/web/http/headers/feature-policy/accelerometer/index.md
+++ b/files/en-us/web/http/headers/feature-policy/accelerometer/index.md
@@ -10,36 +10,31 @@ tags:
   - Experimental
 browser-compat: http.headers.Feature-Policy.accelerometer
 ---
-<p>{{HTTPSidebar}} {{SeeCompatTable}}</p>
+{{HTTPSidebar}} {{SeeCompatTable}}
 
-<p>The HTTP {{HTTPHeader('Feature-Policy')}} header <code>accelerometer</code> directive controls whether the current document is allowed to gather information about the acceleration of the device through the {{domxref('Accelerometer')}} interface.</p>
+The HTTP {{HTTPHeader('Feature-Policy')}} header `accelerometer` directive controls whether the current document is allowed to gather information about the acceleration of the device through the {{domxref('Accelerometer')}} interface.
 
-<h2 id="Syntax">Syntax</h2>
+## Syntax
 
-<pre>Feature-Policy: accelerometer &lt;allowlist&gt;;</pre>
+    Feature-Policy: accelerometer <allowlist>;
 
-<dl>
- <dt>&lt;allowlist&gt;</dt>
- <dd>A list of origins for which the feature is allowed. See <a href="/en-US/docs/Web/HTTP/Headers/Feature-Policy#syntax"><code>Feature-Policy</code></a>.</dd>
-</dl>
+- \<allowlist>
+  - : A list of origins for which the feature is allowed. See [`Feature-Policy`](/en-US/docs/Web/HTTP/Headers/Feature-Policy#syntax).
 
-<h2 id="Default_policy">Default policy</h2>
+## Default policy
 
-<p>The default <code>allowlist</code> value for this feature is: <code>'self'</code>.</p>
+The default `allowlist` value for this feature is: `'self'`.
 
-<h2 id="Specifications">Specifications</h2>
+## Specifications
 
-<p>{{Specifications}}</p>
+{{Specifications}}
 
+## Browser compatibility
 
-<h2 id="Browser_compatibility">Browser compatibility</h2>
+{{Compat}}
 
-<p>{{Compat}}</p>
+## See also
 
-<h2 id="See_also">See also</h2>
-
-<ul>
- <li>{{HTTPHeader('Feature-Policy')}} header</li>
- <li><a href="/en-US/docs/Web/HTTP/Feature_Policy">Feature Policy</a></li>
- <li><a href="/en-US/docs/Web/HTTP/Feature_Policy/Using_Feature_Policy">Using Feature Policy</a></li>
-</ul>
+- {{HTTPHeader('Feature-Policy')}} header
+- [Feature Policy](/en-US/docs/Web/HTTP/Feature_Policy)
+- [Using Feature Policy](/en-US/docs/Web/HTTP/Feature_Policy/Using_Feature_Policy)
diff --git a/files/en-us/web/http/headers/feature-policy/ambient-light-sensor/index.md b/files/en-us/web/http/headers/feature-policy/ambient-light-sensor/index.md
index f76e582f3caa353..8d388222474ca26 100644
--- a/files/en-us/web/http/headers/feature-policy/ambient-light-sensor/index.md
+++ b/files/en-us/web/http/headers/feature-policy/ambient-light-sensor/index.md
@@ -8,36 +8,31 @@ tags:
   - Experimental
 browser-compat: http.headers.Feature-Policy.ambient-light-sensor
 ---
-<p>{{HTTPSidebar}} {{SeeCompatTable}}</p>
+{{HTTPSidebar}} {{SeeCompatTable}}
 
-<p>The HTTP {{HTTPHeader('Feature-Policy')}} header <code>ambient-light-sensor</code> directive controls whether the current document is allowed to gather information about the amount of light in the environment around the device through the {{domxref('AmbientLightSensor')}} interface.</p>
+The HTTP {{HTTPHeader('Feature-Policy')}} header `ambient-light-sensor` directive controls whether the current document is allowed to gather information about the amount of light in the environment around the device through the {{domxref('AmbientLightSensor')}} interface.
 
-<h2 id="Syntax">Syntax</h2>
+## Syntax
 
-<pre>Feature-Policy: ambient-light-sensor &lt;allowlist&gt;;</pre>
+    Feature-Policy: ambient-light-sensor <allowlist>;
 
-<dl>
-  <dt>&lt;allowlist&gt;</dt>
-  <dd>A list of origins for which the feature is allowed. See <a href="/en-US/docs/Web/HTTP/Headers/Feature-Policy#syntax"><code>Feature-Policy</code></a>.</dd>
- </dl>
+- \<allowlist>
+  - : A list of origins for which the feature is allowed. See [`Feature-Policy`](/en-US/docs/Web/HTTP/Headers/Feature-Policy#syntax).
 
-<h2 id="Default_policy">Default policy</h2>
+## Default policy
 
-<p>Default allow list for <code>ambient-light-sensor</code> is <code>'self'</code>.</p>
+Default allow list for `ambient-light-sensor` is `'self'`.
 
-<h2 id="Specifications">Specifications</h2>
+## Specifications
 
-<p>{{Specifications}}</p>
+{{Specifications}}
 
+## Browser compatibility
 
-<h2 id="Browser_compatibility">Browser compatibility</h2>
+{{Compat}}
 
-<p>{{Compat}}</p>
+## See also
 
-<h2 id="See_also">See also</h2>
-
-<ul>
- <li>{{HTTPHeader('Feature-Policy')}} header</li>
- <li><a href="/en-US/docs/Web/HTTP/Feature_Policy">Feature Policy</a></li>
- <li><a href="/en-US/docs/Web/HTTP/Feature_Policy/Using_Feature_Policy">Using Feature Policy</a></li>
-</ul>
+- {{HTTPHeader('Feature-Policy')}} header
+- [Feature Policy](/en-US/docs/Web/HTTP/Feature_Policy)
+- [Using Feature Policy](/en-US/docs/Web/HTTP/Feature_Policy/Using_Feature_Policy)
diff --git a/files/en-us/web/http/headers/feature-policy/autoplay/index.md b/files/en-us/web/http/headers/feature-policy/autoplay/index.md
index e9bc60cb5457737..dd0878a70b67895 100644
--- a/files/en-us/web/http/headers/feature-policy/autoplay/index.md
+++ b/files/en-us/web/http/headers/feature-policy/autoplay/index.md
@@ -11,48 +11,42 @@ tags:
   - Experimental
 browser-compat: http.headers.Feature-Policy.autoplay
 ---
-<div>{{HTTPSidebar}} {{SeeCompatTable}}</div>
+{{HTTPSidebar}} {{SeeCompatTable}}
 
-<p>The HTTP {{HTTPHeader("Feature-Policy")}} header
-    <code>autoplay</code> directive controls whether the current document is allowed to
-    autoplay media requested through the {{domxref("HTMLMediaElement")}} interface.
-  When this policy is enabled and there were no user gestures, the {{jsxref("Promise")}}
-  returned by {{domxref("HTMLMediaElement.play()")}} will reject with
-  a {{domxref("DOMException")}}. The {{htmlattrxref("autoplay", "audio")}} attribute on
-  {{HTMLElement("audio")}} and {{HTMLElement("video")}} elements will be ignored.</p>
+The HTTP {{HTTPHeader("Feature-Policy")}} header
+`autoplay` directive controls whether the current document is allowed to
+autoplay media requested through the {{domxref("HTMLMediaElement")}} interface.
+When this policy is enabled and there were no user gestures, the {{jsxref("Promise")}}
+returned by {{domxref("HTMLMediaElement.play()")}} will reject with
+a {{domxref("DOMException")}}. The {{htmlattrxref("autoplay", "audio")}} attribute on
+{{HTMLElement("audio")}} and {{HTMLElement("video")}} elements will be ignored.
 
-<p>For more details on autoplay and autoplay blocking, see the article <a
-    href="/en-US/docs/Web/Media/Autoplay_guide">Autoplay guide for media and Web Audio
-    APIs</a>.</p>
+For more details on autoplay and autoplay blocking, see the article [Autoplay guide for media and Web Audio
+APIs](/en-US/docs/Web/Media/Autoplay_guide).
 
-<h2 id="Syntax">Syntax</h2>
+## Syntax
 
-<pre>Feature-Policy: autoplay &lt;allowlist&gt;;</pre>
+    Feature-Policy: autoplay <allowlist>;
 
-<dl>
-  <dt>&lt;allowlist&gt;</dt>
-  <dd>A list of origins for which the feature is allowed. See <a href="/en-US/docs/Web/HTTP/Headers/Feature-Policy#syntax"><code>Feature-Policy</code></a>.</dd>
- </dl>
+- \<allowlist>
+  - : A list of origins for which the feature is allowed. See [`Feature-Policy`](/en-US/docs/Web/HTTP/Headers/Feature-Policy#syntax).
 
-<h2 id="Default_policy">Default policy</h2>
+## Default policy
 
-<p>The default value in <a
-    href="https://www.chromestatus.com/feature/5100524789563392">Google Chrome</a> is
-  <code>'self'</code>.</p>
+The default value in [Google Chrome](https://www.chromestatus.com/feature/5100524789563392) is
+`'self'`.
 
-<h2 id="Specifications">Specifications</h2>
+## Specifications
 
-<p>{{Specifications}}</p>
+{{Specifications}}
 
-<h2 id="Browser_compatibility">Browser compatibility</h2>
+## Browser compatibility
 
-<p>{{Compat}}</p>
+{{Compat}}
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
-  <li>{{HTTPHeader("Feature-Policy")}} header</li>
-  <li><a href="/en-US/docs/Web/HTTP/Feature_Policy">Feature Policy</a></li>
-  <li><a href="/en-US/docs/Web/HTTP/Feature_Policy/Using_Feature_Policy">Using Feature
-      Policy</a></li>
-</ul>
+- {{HTTPHeader("Feature-Policy")}} header
+- [Feature Policy](/en-US/docs/Web/HTTP/Feature_Policy)
+- [Using Feature
+  Policy](/en-US/docs/Web/HTTP/Feature_Policy/Using_Feature_Policy)
diff --git a/files/en-us/web/http/headers/feature-policy/battery/index.md b/files/en-us/web/http/headers/feature-policy/battery/index.md
index b5df7d9564e7140..47ab34157942260 100644
--- a/files/en-us/web/http/headers/feature-policy/battery/index.md
+++ b/files/en-us/web/http/headers/feature-policy/battery/index.md
@@ -7,40 +7,35 @@ tags:
   - HTTP
   - Experimental
 browser-compat: http.headers.Feature-Policy.battery
-
 ---
-<p>{{HTTPSidebar}}{{SeeCompatTable}}</p>
+{{HTTPSidebar}}{{SeeCompatTable}}
 
-<p>The HTTP {{HTTPHeader("Feature-Policy")}} header <code>battery</code> directive controls whether the current document is allowed to gather information about the battery of the device through the {{DOMxRef("BatteryManager")}} interface obtained via {{DOMxRef("Navigator.getBattery","Navigator.getBattery()")}}.</p>
+The HTTP {{HTTPHeader("Feature-Policy")}} header `battery` directive controls whether the current document is allowed to gather information about the battery of the device through the {{DOMxRef("BatteryManager")}} interface obtained via {{DOMxRef("Navigator.getBattery","Navigator.getBattery()")}}.
 
-<h2 id="Syntax">Syntax</h2>
+## Syntax
 
-<pre>Feature-Policy: battery &lt;allowlist&gt;;</pre>
+    Feature-Policy: battery <allowlist>;
 
-<dl>
-  <dt>&lt;allowlist&gt;</dt>
-  <dd>A list of origins for which the feature is allowed. See <a href="/en-US/docs/Web/HTTP/Headers/Feature-Policy#syntax"><code>Feature-Policy</code></a>.</dd>
- </dl>
+- \<allowlist>
+  - : A list of origins for which the feature is allowed. See [`Feature-Policy`](/en-US/docs/Web/HTTP/Headers/Feature-Policy#syntax).
 
-<h2 id="Default_policy">Default policy</h2>
+## Default policy
 
-<p>Default allow list for <code>battery</code> is <code>'self'</code>.</p>
+Default allow list for `battery` is `'self'`.
 
-<h2 id="Specifications">Specifications</h2>
+## Specifications
 
-<p>{{Specifications}}</p>
+{{Specifications}}
 
-<h2 id="Browser_compatibility">Browser compatibility</h2>
+## Browser compatibility
 
-<p>{{Compat}}</p>
+{{Compat}}
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
- <li>{{HTTPHeader("Feature-Policy")}} header</li>
- <li><a href="/en-US/docs/Web/HTTP/Feature_Policy">Feature Policy</a></li>
- <li><a href="/en-US/docs/Web/HTTP/Feature_Policy/Using_Feature_Policy">Using Feature Policy</a></li>
- <li><a href="/en-US/docs/Web/API/Battery_Status_API">Battery Status API</a></li>
- <li>{{DOMxRef("Navigator.getBattery","Navigator.getBattery()")}}</li>
- <li>{{DOMxRef("BatteryManager")}}</li>
-</ul>
+- {{HTTPHeader("Feature-Policy")}} header
+- [Feature Policy](/en-US/docs/Web/HTTP/Feature_Policy)
+- [Using Feature Policy](/en-US/docs/Web/HTTP/Feature_Policy/Using_Feature_Policy)
+- [Battery Status API](/en-US/docs/Web/API/Battery_Status_API)
+- {{DOMxRef("Navigator.getBattery","Navigator.getBattery()")}}
+- {{DOMxRef("BatteryManager")}}
diff --git a/files/en-us/web/http/headers/feature-policy/camera/index.md b/files/en-us/web/http/headers/feature-policy/camera/index.md
index c3293e1a5b48d4e..09eda44d03276bd 100644
--- a/files/en-us/web/http/headers/feature-policy/camera/index.md
+++ b/files/en-us/web/http/headers/feature-policy/camera/index.md
@@ -11,39 +11,35 @@ tags:
   - Experimental
 browser-compat: http.headers.Feature-Policy.camera
 ---
-<div>{{HTTPSidebar}} {{SeeCompatTable}} </div>
+{{HTTPSidebar}} {{SeeCompatTable}}
 
-<p>The HTTP {{HTTPHeader("Feature-Policy")}} header
-    <code>camera</code> directive controls whether the current document is allowed to use
-    video input devices. When this policy is enabled, the {{jsxref("Promise")}} returned
-    by {{domxref("MediaDevices.getUserMedia()")}} will reject with
-    a <code>NotAllowedError</code> {{domxref("DOMException")}}.</p>
+The HTTP {{HTTPHeader("Feature-Policy")}} header
+`camera` directive controls whether the current document is allowed to use
+video input devices. When this policy is enabled, the {{jsxref("Promise")}} returned
+by {{domxref("MediaDevices.getUserMedia()")}} will reject with
+a `NotAllowedError` {{domxref("DOMException")}}.
 
-<h2 id="Syntax">Syntax</h2>
+## Syntax
 
-<pre>Feature-Policy: camera &lt;allowlist&gt;;</pre>
+    Feature-Policy: camera <allowlist>;
 
-<dl>
-  <dt>&lt;allowlist&gt;</dt>
-  <dd>A list of origins for which the feature is allowed. See <a href="/en-US/docs/Web/HTTP/Headers/Feature-Policy#syntax"><code>Feature-Policy</code></a>.</dd>
- </dl>
+- \<allowlist>
+  - : A list of origins for which the feature is allowed. See [`Feature-Policy`](/en-US/docs/Web/HTTP/Headers/Feature-Policy#syntax).
 
-<h2 id="Default_policy">Default policy</h2>
+## Default policy
 
-<p>Default allow list for <code>camera</code> is <code>'self'</code>.</p>
+Default allow list for `camera` is `'self'`.
 
-<h2 id="Specifications">Specifications</h2>
+## Specifications
 
-<p>{{Specifications}}</p>
+{{Specifications}}
 
-<h2 id="Browser_compatibility">Browser compatibility</h2>
+## Browser compatibility
 
-<p>{{Compat}}</p>
+{{Compat}}
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
-  <li>{{HTTPHeader("Feature-Policy")}} header</li>
-  <li><a href="/en-US/docs/Web/HTTP/Feature_Policy">Feature Policy</a></li>
-  <li><a href="/en-US/docs/Web/HTTP/Feature_Policy/Using_Feature_Policy">Using Feature Policy</a></li>
-</ul>
+- {{HTTPHeader("Feature-Policy")}} header
+- [Feature Policy](/en-US/docs/Web/HTTP/Feature_Policy)
+- [Using Feature Policy](/en-US/docs/Web/HTTP/Feature_Policy/Using_Feature_Policy)
diff --git a/files/en-us/web/http/headers/feature-policy/display-capture/index.md b/files/en-us/web/http/headers/feature-policy/display-capture/index.md
index 06bf052b4125ed6..1ae3384625ffc79 100644
--- a/files/en-us/web/http/headers/feature-policy/display-capture/index.md
+++ b/files/en-us/web/http/headers/feature-policy/display-capture/index.md
@@ -10,40 +10,35 @@ tags:
   - Experimental
 browser-compat: http.headers.Feature-Policy.display-capture
 ---
-<div>{{HTTPSidebar}} {{SeeCompatTable}} </div>
+{{HTTPSidebar}} {{SeeCompatTable}}
 
-<p>The HTTP {{HTTPHeader("Feature-Policy")}} header <code>display-capture</code> directive controls whether or not the document is permitted to use <a href="/en-US/docs/Web/API/Screen_Capture_API">Screen Capture API</a>, that is, {{domxref("MediaDevices.getDisplayMedia", "getDisplayMedia()")}} to capture the screen's contents.</p>
+The HTTP {{HTTPHeader("Feature-Policy")}} header `display-capture` directive controls whether or not the document is permitted to use [Screen Capture API](/en-US/docs/Web/API/Screen_Capture_API), that is, {{domxref("MediaDevices.getDisplayMedia", "getDisplayMedia()")}} to capture the screen's contents.
 
-<p>If <code>display-capture</code> is disabled in a document, the document will not be able to initiate screen capture via {{domxref("MediaDevices.getDisplayMedia", "getDisplayMedia()")}}.</p>
+If `display-capture` is disabled in a document, the document will not be able to initiate screen capture via {{domxref("MediaDevices.getDisplayMedia", "getDisplayMedia()")}}.
 
-<h2 id="Syntax">Syntax</h2>
+## Syntax
 
-<pre>Feature-Policy: display-capture &lt;allowlist&gt;;</pre>
+    Feature-Policy: display-capture <allowlist>;
 
-<dl>
-  <dt>&lt;allowlist&gt;</dt>
-  <dd>A list of origins for which the feature is allowed. See <a href="/en-US/docs/Web/HTTP/Headers/Feature-Policy#syntax"><code>Feature-Policy</code></a>.</dd>
-</dl>
+- \<allowlist>
+  - : A list of origins for which the feature is allowed. See [`Feature-Policy`](/en-US/docs/Web/HTTP/Headers/Feature-Policy#syntax).
 
-<h2 id="Default_policy">Default policy</h2>
+## Default policy
 
-<p>Default allow list for <code>display-capture</code> is <code>'self'</code>.</p>
+Default allow list for `display-capture` is `'self'`.
 
-<h2 id="Specifications">Specifications</h2>
+## Specifications
 
-<p>{{Specifications}}</p>
+{{Specifications}}
 
+## Browser compatibility
 
-<h2 id="Browser_compatibility">Browser compatibility</h2>
+{{Compat}}
 
-<p>{{Compat}}</p>
+## See also
 
-<h2 id="See_also">See also</h2>
-
-<ul>
- <li>{{HTTPHeader("Feature-Policy")}} header</li>
- <li><a href="/en-US/docs/Web/HTTP/Feature_Policy">Feature Policy</a></li>
- <li><a href="/en-US/docs/Web/HTTP/Feature_Policy/Using_Feature_Policy">Using Feature Policy</a></li>
- <li><a href="/en-US/docs/Web/API/Screen_Capture_API">Screen Capture API</a></li>
- <li><a href="/en-US/docs/Web/API/Screen_Capture_API/Using_Screen_Capture">Using the Screen Capture API</a></li>
-</ul>
+- {{HTTPHeader("Feature-Policy")}} header
+- [Feature Policy](/en-US/docs/Web/HTTP/Feature_Policy)
+- [Using Feature Policy](/en-US/docs/Web/HTTP/Feature_Policy/Using_Feature_Policy)
+- [Screen Capture API](/en-US/docs/Web/API/Screen_Capture_API)
+- [Using the Screen Capture API](/en-US/docs/Web/API/Screen_Capture_API/Using_Screen_Capture)
diff --git a/files/en-us/web/http/headers/feature-policy/document-domain/index.md b/files/en-us/web/http/headers/feature-policy/document-domain/index.md
index 140c40b9f803ff1..acceaeb6965b3ec 100644
--- a/files/en-us/web/http/headers/feature-policy/document-domain/index.md
+++ b/files/en-us/web/http/headers/feature-policy/document-domain/index.md
@@ -2,49 +2,45 @@
 title: 'Feature-Policy: document-domain'
 slug: Web/HTTP/Headers/Feature-Policy/document-domain
 tags:
-- Directive
-- Experimental
-- Feature Policy
-- Feature-Policy
-- HTTP
-- Reference
-- document-domain
-- Header
+  - Directive
+  - Experimental
+  - Feature Policy
+  - Feature-Policy
+  - HTTP
+  - Reference
+  - document-domain
+  - Header
 browser-compat: http.headers.Feature-Policy.document-domain
 ---
-<div>{{HTTPSidebar}} {{SeeCompatTable}}</div>
+{{HTTPSidebar}} {{SeeCompatTable}}
 
-<p>The HTTP {{HTTPHeader("Feature-Policy")}} header
-    <code>document-domain</code> directive controls whether the current document is
-    allowed to set {{domxref("document.domain")}}. When this policy is disabled, attempting
-    to set {{domxref("document.domain")}} will fail and cause a <code>SecurityError</code>
-    {{domxref("DOMException")}} to be thrown.</p>
+The HTTP {{HTTPHeader("Feature-Policy")}} header
+`document-domain` directive controls whether the current document is
+allowed to set {{domxref("document.domain")}}. When this policy is disabled, attempting
+to set {{domxref("document.domain")}} will fail and cause a `SecurityError`
+{{domxref("DOMException")}} to be thrown.
 
-<h2 id="Syntax">Syntax</h2>
+## Syntax
 
-<pre>Feature-Policy: document-domain &lt;allowlist&gt;;</pre>
+    Feature-Policy: document-domain <allowlist>;
 
-<dl>
-  <dt>&lt;allowlist&gt;</dt>
-  <dd>A list of origins for which the feature is allowed. See <a href="/en-US/docs/Web/HTTP/Headers/Feature-Policy#syntax"><code>Feature-Policy</code></a>.</dd>
-</dl>
+- \<allowlist>
+  - : A list of origins for which the feature is allowed. See [`Feature-Policy`](/en-US/docs/Web/HTTP/Headers/Feature-Policy#syntax).
 
-<h2 id="Default_policy">Default policy</h2>
+## Default policy
 
-<p>Default allow list for <code>document-domain</code> is <code>*</code>.</p>
+Default allow list for `document-domain` is `*`.
 
-<h2 id="Specifications">Specifications</h2>
+## Specifications
 
-<p>{{Specifications}}</p>
+{{Specifications}}
 
-<h2 id="Browser_compatibility">Browser compatibility</h2>
+## Browser compatibility
 
-<p>{{Compat}}</p>
+{{Compat}}
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
-  <li>{{HTTPHeader("Feature-Policy")}} header</li>
-  <li><a href="/en-US/docs/Web/HTTP/Feature_Policy">Feature Policy</a></li>
-  <li><a href="/en-US/docs/Web/HTTP/Feature_Policy/Using_Feature_Policy">Using Feature Policy</a></li>
-</ul>
+- {{HTTPHeader("Feature-Policy")}} header
+- [Feature Policy](/en-US/docs/Web/HTTP/Feature_Policy)
+- [Using Feature Policy](/en-US/docs/Web/HTTP/Feature_Policy/Using_Feature_Policy)
diff --git a/files/en-us/web/http/headers/feature-policy/encrypted-media/index.md b/files/en-us/web/http/headers/feature-policy/encrypted-media/index.md
index aff353eb7469ede..5d63eff902d1265 100644
--- a/files/en-us/web/http/headers/feature-policy/encrypted-media/index.md
+++ b/files/en-us/web/http/headers/feature-policy/encrypted-media/index.md
@@ -11,35 +11,31 @@ tags:
   - Experimental
 browser-compat: http.headers.Feature-Policy.encrypted-media
 ---
-<p>{{HTTPSidebar}}{{SeeCompatTable}}</p>
+{{HTTPSidebar}}{{SeeCompatTable}}
 
-<p>The HTTP {{HTTPHeader("Feature-Policy")}} header <code>encrypted-media</code> directive controls whether the current document is allowed to use the <a href="/en-US/docs/Web/API/Encrypted_Media_Extensions_API">Encrypted Media Extensions</a> API (EME). When this policy is enabled, the {{jsxref("Promise")}} returned by {{domxref("Navigator.requestMediaKeySystemAccess","Navigator.requestMediaKeySystemAccess()")}} will reject with a {{domxref("DOMException")}}.</p>
+The HTTP {{HTTPHeader("Feature-Policy")}} header `encrypted-media` directive controls whether the current document is allowed to use the [Encrypted Media Extensions](/en-US/docs/Web/API/Encrypted_Media_Extensions_API) API (EME). When this policy is enabled, the {{jsxref("Promise")}} returned by {{domxref("Navigator.requestMediaKeySystemAccess","Navigator.requestMediaKeySystemAccess()")}} will reject with a {{domxref("DOMException")}}.
 
-<h2 id="Syntax">Syntax</h2>
+## Syntax
 
-<pre>Feature-Policy: encrypted-media &lt;allowlist&gt;;</pre>
+    Feature-Policy: encrypted-media <allowlist>;
 
-<dl>
-  <dt>&lt;allowlist&gt;</dt>
-  <dd>A list of origins for which the feature is allowed. See <a href="/en-US/docs/Web/HTTP/Headers/Feature-Policy#syntax"><code>Feature-Policy</code></a>.</dd>
-</dl>
+- \<allowlist>
+  - : A list of origins for which the feature is allowed. See [`Feature-Policy`](/en-US/docs/Web/HTTP/Headers/Feature-Policy#syntax).
 
-<h2 id="Default_policy">Default policy</h2>
+## Default policy
 
-<p>Default allow list for <code>encrypted-media</code> is <code>'self'</code>.</p>
+Default allow list for `encrypted-media` is `'self'`.
 
-<h2 id="Specifications">Specifications</h2>
+## Specifications
 
-<p>{{Specifications}}</p>
+{{Specifications}}
 
-<h2 id="Browser_compatibility">Browser compatibility</h2>
+## Browser compatibility
 
-<p>{{Compat}}</p>
+{{Compat}}
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
- <li>{{HTTPHeader("Feature-Policy")}} header</li>
- <li><a href="/en-US/docs/Web/HTTP/Feature_Policy">Feature Policy</a></li>
- <li><a href="/en-US/docs/Web/HTTP/Feature_Policy/Using_Feature_Policy">Using Feature Policy</a></li>
-</ul>
+- {{HTTPHeader("Feature-Policy")}} header
+- [Feature Policy](/en-US/docs/Web/HTTP/Feature_Policy)
+- [Using Feature Policy](/en-US/docs/Web/HTTP/Feature_Policy/Using_Feature_Policy)
diff --git a/files/en-us/web/http/headers/feature-policy/fullscreen/index.md b/files/en-us/web/http/headers/feature-policy/fullscreen/index.md
index 3937b9005d8bf36..094c7e011dd3cef 100644
--- a/files/en-us/web/http/headers/feature-policy/fullscreen/index.md
+++ b/files/en-us/web/http/headers/feature-policy/fullscreen/index.md
@@ -10,62 +10,61 @@ tags:
   - Experimental
 browser-compat: http.headers.Feature-Policy.fullscreen
 ---
-<div>{{HTTPSidebar}} {{SeeCompatTable}}</div>
+{{HTTPSidebar}} {{SeeCompatTable}}
 
-<p>The HTTP {{HTTPHeader("Feature-Policy")}} header <code>fullscreen</code> directive controls whether the current document is allowed to use {{domxref('Element.requestFullScreen()')}}. When this policy is enabled, the returned {{jsxref('Promise')}} rejects with a {{jsxref('TypeError')}}.</p>
+The HTTP {{HTTPHeader("Feature-Policy")}} header `fullscreen` directive controls whether the current document is allowed to use {{domxref('Element.requestFullScreen()')}}. When this policy is enabled, the returned {{jsxref('Promise')}} rejects with a {{jsxref('TypeError')}}.
 
-<p>By default, top-level documents and their same-origin child frames can request and enter fullscreen mode. This directive allows or prevents cross-origin frames from using fullscreen mode. This includes same-origin frames.</p>
+By default, top-level documents and their same-origin child frames can request and enter fullscreen mode. This directive allows or prevents cross-origin frames from using fullscreen mode. This includes same-origin frames.
 
-<div class="notecard note">
-  <p><strong>Note:</strong> If both this directive (i.e. via the <code>allow</code> attribute) and the <code>allowfullscreen</code> attribute are present on an <code>&lt;iframe&gt;</code> element, this directive takes precedence. There was a bug whereby the <code>fullscreen</code> directive didn't work unless the <code>allowfullscreen</code> attribute was also present, but this has been fixed as of Firefox 80 ({{bug(1608358)}}).</p>
-</div>
+> **Note:** If both this directive (i.e. via the `allow` attribute) and the `allowfullscreen` attribute are present on an `<iframe>` element, this directive takes precedence. There was a bug whereby the `fullscreen` directive didn't work unless the `allowfullscreen` attribute was also present, but this has been fixed as of Firefox 80 ({{bug(1608358)}}).
 
-<h2 id="Syntax">Syntax</h2>
+## Syntax
 
-<pre>Feature-Policy: fullscreen &lt;allowlist&gt;;</pre>
+    Feature-Policy: fullscreen <allowlist>;
 
-<dl>
-  <dt>&lt;allowlist&gt;</dt>
-  <dd>A list of origins for which the feature is allowed. See <a href="/en-US/docs/Web/HTTP/Headers/Feature-Policy#syntax"><code>Feature-Policy</code></a>.</dd>
-</dl>
+- \<allowlist>
+  - : A list of origins for which the feature is allowed. See [`Feature-Policy`](/en-US/docs/Web/HTTP/Headers/Feature-Policy#syntax).
 
-<h2 id="Default_policy">Default policy</h2>
+## Default policy
 
-<p>Default allow list for <code>fullscreen</code> is <code>'self'</code>.</p>
+Default allow list for `fullscreen` is `'self'`.
 
+## Examples
 
-<h2 id="Examples">Examples</h2>
+### General example
 
-<h3 id="General_example">General example</h3>
+SecureCorp Inc. wants to disable the Fullscreen API within all browsing contexts except for its own origin and those whose origin is `https://example.com`. It can do so by delivering the following HTTP response header to define a feature policy:
 
-<p>SecureCorp Inc. wants to disable the Fullscreen API within all browsing contexts except for its own origin and those whose origin is <code>https://example.com</code>. It can do so by delivering the following HTTP response header to define a feature policy:</p>
+```bash
+Feature-Policy: fullscreen 'self' https://example.com
+```
 
-<pre class="brush: bash">Feature-Policy: fullscreen 'self' https://example.com</pre>
+### With an \<iframe> element
 
-<h3 id="With_an_&lt;iframe&gt;_element">With an &lt;iframe&gt; element</h3>
+FastCorp Inc. wants to disable `fullscreen` for all cross-origin child frames, except for a specific \<iframe>. It can do so by delivering the following HTTP response header to define a feature policy:
 
-<p>FastCorp Inc. wants to disable <code>fullscreen</code> for all cross-origin child frames, except for a specific &lt;iframe&gt;. It can do so by delivering the following HTTP response header to define a feature policy:</p>
+```bash
+Feature-Policy: fullscreen 'self'
+```
 
-<pre class="brush: bash">Feature-Policy: fullscreen 'self'</pre>
+Then include an {{HTMLElement('iframe','allow','#Attributes')}} attribute on the `<iframe>` element:
 
-<p>Then include an {{HTMLElement('iframe','allow','#Attributes')}} attribute on the <code>&lt;iframe&gt;</code> element:</p>
+```html
+<iframe src="https://other.com/videoplayer" allow="fullscreen"></iframe>
+```
 
-<pre class="brush: html">&lt;iframe src="https://other.com/videoplayer" allow="fullscreen"&gt;&lt;/iframe&gt;</pre>
+iframe attributes can selectively enable features in certain frames, and not in others, even if those frames contain documents from the same origin.
 
-<p>iframe attributes can selectively enable features in certain frames, and not in others, even if those frames contain documents from the same origin.</p>
+## Specifications
 
-<h2 id="Specifications">Specifications</h2>
+{{Specifications}}
 
-<p>{{Specifications}}</p>
+## Browser compatibility
 
-<h2 id="Browser_compatibility">Browser compatibility</h2>
+{{Compat}}
 
-<p>{{Compat}}</p>
+## See also
 
-<h2 id="See_also">See also</h2>
-
-<ul>
- <li>{{HTTPHeader("Feature-Policy")}} header</li>
- <li><a href="/en-US/docs/Web/HTTP/Feature_Policy">Feature Policy</a></li>
- <li><a href="/en-US/docs/Web/HTTP/Feature_Policy/Using_Feature_Policy">Using Feature Policy</a></li>
-</ul>
+- {{HTTPHeader("Feature-Policy")}} header
+- [Feature Policy](/en-US/docs/Web/HTTP/Feature_Policy)
+- [Using Feature Policy](/en-US/docs/Web/HTTP/Feature_Policy/Using_Feature_Policy)
diff --git a/files/en-us/web/http/headers/feature-policy/gamepad/index.md b/files/en-us/web/http/headers/feature-policy/gamepad/index.md
index f45699693c272b0..a563193fa5991ee 100644
--- a/files/en-us/web/http/headers/feature-policy/gamepad/index.md
+++ b/files/en-us/web/http/headers/feature-policy/gamepad/index.md
@@ -7,63 +7,62 @@ tags:
   - HTTP
   - header
   - Experimental
-
 browser-compat: http.headers.Feature-Policy.gamepad
 ---
-<div>{{HTTPSidebar}} {{SeeCompatTable}}</div>
+{{HTTPSidebar}} {{SeeCompatTable}}
 
-<p>The HTTP {{HTTPHeader("Feature-Policy")}} header <code>gamepad</code> directive controls whether the current document is allowed to use the <a href="/en-US/docs/Web/API/Gamepad_API">Gamepad API</a>.
-  When this policy is disabled, calls to {{domxref('Navigator.getGamepads()')}} will throw a <code>SecurityError</code> {{domxref('DOMException')}}.
-  In addition, the {{event("gamepadconnected")}} and {{event("gamepaddisconnected")}} events will not fire.</p>
+The HTTP {{HTTPHeader("Feature-Policy")}} header `gamepad` directive controls whether the current document is allowed to use the [Gamepad API](/en-US/docs/Web/API/Gamepad_API).
+When this policy is disabled, calls to {{domxref('Navigator.getGamepads()')}} will throw a `SecurityError` {{domxref('DOMException')}}.
+In addition, the {{event("gamepadconnected")}} and {{event("gamepaddisconnected")}} events will not fire.
 
-<h2 id="Syntax">Syntax</h2>
+## Syntax
 
-<pre>Feature-Policy: gamepad &lt;allowlist&gt;;</pre>
+    Feature-Policy: gamepad <allowlist>;
 
-<dl>
-  <dt>&lt;allowlist&gt;</dt>
-  <dd>A list of origins for which the feature is allowed. See <a href="/en-US/docs/Web/HTTP/Headers/Feature-Policy#syntax"><code>Feature-Policy</code></a>.</dd>
-</dl>
+- \<allowlist>
+  - : A list of origins for which the feature is allowed. See [`Feature-Policy`](/en-US/docs/Web/HTTP/Headers/Feature-Policy#syntax).
 
-<h2 id="Default_policy">Default policy</h2>
+## Default policy
 
-<p>Default allow list for <code>gamepad</code> is <code>'self'</code>.</p>
+Default allow list for `gamepad` is `'self'`.
 
-<h2 id="Examples">Examples</h2>
+## Examples
 
-<h3 id="General_example">General example</h3>
+### General example
 
-<p>SecureCorp Inc. wants to disable the Gamepad API within all browsing contexts except for its own origin and those whose origin is <code>https://example.com</code>.
-  It can do so by delivering the following HTTP response header to define a feature policy:</p>
+SecureCorp Inc. wants to disable the Gamepad API within all browsing contexts except for its own origin and those whose origin is `https://example.com`.
+It can do so by delivering the following HTTP response header to define a feature policy:
 
-<pre class="brush: bash">Feature-Policy: gamepad 'self' https://example.com</pre>
+```bash
+Feature-Policy: gamepad 'self' https://example.com
+```
 
-<h3 id="With_an_&lt;iframe&gt;_element">With an &lt;iframe&gt; element</h3>
+### With an \<iframe> element
 
-<p>FastCorp Inc. wants to disable <code>gamepad</code> for all cross-origin child frames, except for a specific &lt;iframe&gt;.
-  It can do so by delivering the following HTTP response header to define a feature policy:</p>
+FastCorp Inc. wants to disable `gamepad` for all cross-origin child frames, except for a specific \<iframe>.
+It can do so by delivering the following HTTP response header to define a feature policy:
 
-<pre class="brush: bash">Feature-Policy: gamepad 'self'</pre>
+```bash
+Feature-Policy: gamepad 'self'
+```
 
-<p>Then include an {{HTMLElement('iframe','allow','#Attributes')}} attribute on the <code>&lt;iframe&gt;</code> element:</p>
+Then include an {{HTMLElement('iframe','allow','#Attributes')}} attribute on the `<iframe>` element:
 
-<pre>&lt;iframe src="https://other.com/game" allow="gamepad"&gt;&lt;/iframe&gt;</pre>
+    <iframe src="https://other.com/game" allow="gamepad"></iframe>
 
-<p>iframe attributes can selectively enable features in certain frames, and not in others, even if those frames contain documents from the same origin.</p>
+iframe attributes can selectively enable features in certain frames, and not in others, even if those frames contain documents from the same origin.
 
-<h2 id="Specifications">Specifications</h2>
+## Specifications
 
-<p>{{Specifications}}</p>
+{{Specifications}}
 
-<h2 id="Browser_compatibility">Browser compatibility</h2>
+## Browser compatibility
 
-<p>{{Compat}}</p>
+{{Compat}}
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
-  <li>{{HTTPHeader("Feature-Policy")}} header</li>
-  <li><a href="/en-US/docs/Web/HTTP/Feature_Policy">Feature Policy</a></li>
-  <li><a href="/en-US/docs/Web/HTTP/Feature_Policy/Using_Feature_Policy">Using Feature
-      Policy</a></li>
-</ul>
+- {{HTTPHeader("Feature-Policy")}} header
+- [Feature Policy](/en-US/docs/Web/HTTP/Feature_Policy)
+- [Using Feature
+  Policy](/en-US/docs/Web/HTTP/Feature_Policy/Using_Feature_Policy)
diff --git a/files/en-us/web/http/headers/feature-policy/geolocation/index.md b/files/en-us/web/http/headers/feature-policy/geolocation/index.md
index 81751f568c738df..3df76c649f3c344 100644
--- a/files/en-us/web/http/headers/feature-policy/geolocation/index.md
+++ b/files/en-us/web/http/headers/feature-policy/geolocation/index.md
@@ -7,76 +7,74 @@ tags:
   - HTTP
   - header
   - Experimental
-
 browser-compat: http.headers.Feature-Policy.geolocation
 ---
-<div>{{HTTPSidebar}} {{SeeCompatTable}}</div>
+{{HTTPSidebar}} {{SeeCompatTable}}
 
-<p>The HTTP {{HTTPHeader("Feature-Policy")}} header
-    <code>geolocation</code> directive controls whether the current document is allowed to
-    use the {{domxref('Geolocation')}} Interface. When this policy is enabled, calls to
-    {{domxref('Geolocation.getCurrentPosition','getCurrentPosition()')}} and
-    {{domxref('Geolocation.watchPosition','watchPosition()')}} will cause those functions'
-    callbacks to be invoked with a {{domxref('GeolocationPositionError')}} code of
-    <code>PERMISSION_DENIED</code>.</p>
+The HTTP {{HTTPHeader("Feature-Policy")}} header
+`geolocation` directive controls whether the current document is allowed to
+use the {{domxref('Geolocation')}} Interface. When this policy is enabled, calls to
+{{domxref('Geolocation.getCurrentPosition','getCurrentPosition()')}} and
+{{domxref('Geolocation.watchPosition','watchPosition()')}} will cause those functions'
+callbacks to be invoked with a {{domxref('GeolocationPositionError')}} code of
+`PERMISSION_DENIED`.
 
-<p>By default, the Geolocation API can be used within top-level documents and their
-  same-origin child frames. This directive allows or prevents cross-origin frames from
-  accessing geolocation. This includes same-origin frames.</p>
+By default, the Geolocation API can be used within top-level documents and their
+same-origin child frames. This directive allows or prevents cross-origin frames from
+accessing geolocation. This includes same-origin frames.
 
-<h2 id="Syntax">Syntax</h2>
+## Syntax
 
-<pre>Feature-Policy: geolocation &lt;allowlist&gt;;</pre>
+    Feature-Policy: geolocation <allowlist>;
 
-<dl>
-  <dt>&lt;allowlist&gt;</dt>
-  <dd>A list of origins for which the feature is allowed. See <a href="/en-US/docs/Web/HTTP/Headers/Feature-Policy#syntax"><code>Feature-Policy</code></a>.</dd>
-</dl>
+- \<allowlist>
+  - : A list of origins for which the feature is allowed. See [`Feature-Policy`](/en-US/docs/Web/HTTP/Headers/Feature-Policy#syntax).
 
-<h2 id="Default_policy">Default policy</h2>
+## Default policy
 
-<p>Default allow list for <code>geolocation</code> is <code>'self'</code>.</p>
+Default allow list for `geolocation` is `'self'`.
 
-<h2 id="Examples">Examples</h2>
+## Examples
 
-<h3 id="General_example">General example</h3>
+### General example
 
-<p>SecureCorp Inc. wants to disable the Geolocation API within all browsing contexts
-  except for its own origin and those whose origin is <code>https://example.com</code>. It
-  can do so by delivering the following HTTP response header to define a feature policy:
-</p>
+SecureCorp Inc. wants to disable the Geolocation API within all browsing contexts
+except for its own origin and those whose origin is `https://example.com`. It
+can do so by delivering the following HTTP response header to define a feature policy:
 
-<pre class="brush: bash">Feature-Policy: geolocation 'self' https://example.com</pre>
+```bash
+Feature-Policy: geolocation 'self' https://example.com
+```
 
-<h3 id="With_an_&lt;iframe&gt;_element">With an &lt;iframe&gt; element</h3>
+### With an \<iframe> element
 
-<p>FastCorp Inc. wants to disable <code>geolocation</code> for all cross-origin child
-  frames, except for a specific &lt;iframe&gt;. It can do so by delivering the following
-  HTTP response header to define a feature policy:</p>
+FastCorp Inc. wants to disable `geolocation` for all cross-origin child
+frames, except for a specific \<iframe>. It can do so by delivering the following
+HTTP response header to define a feature policy:
 
-<pre class="brush: bash">Feature-Policy: geolocation 'self'</pre>
+```bash
+Feature-Policy: geolocation 'self'
+```
 
-<p>Then include an {{HTMLElement('iframe','allow','#Attributes')}} attribute on the
-  <code>&lt;iframe&gt;</code> element:</p>
+Then include an {{HTMLElement('iframe','allow','#Attributes')}} attribute on the
+`<iframe>` element:
 
-<pre>&lt;iframe src="https://other.com/map" allow="geolocation"&gt;&lt;/iframe&gt;</pre>
+    <iframe src="https://other.com/map" allow="geolocation"></iframe>
 
-<p>iframe attributes can selectively enable features in certain frames, and not in others,
-  even if those frames contain documents from the same origin.</p>
+iframe attributes can selectively enable features in certain frames, and not in others,
+even if those frames contain documents from the same origin.
 
-<h2 id="Specifications">Specifications</h2>
+## Specifications
 
-<p>{{Specifications}}</p>
+{{Specifications}}
 
-<h2 id="Browser_compatibility">Browser compatibility</h2>
+## Browser compatibility
 
-<p>{{Compat}}</p>
+{{Compat}}
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
-  <li>{{HTTPHeader("Feature-Policy")}} header</li>
-  <li><a href="/en-US/docs/Web/HTTP/Feature_Policy">Feature Policy</a></li>
-  <li><a href="/en-US/docs/Web/HTTP/Feature_Policy/Using_Feature_Policy">Using Feature
-      Policy</a></li>
-</ul>
+- {{HTTPHeader("Feature-Policy")}} header
+- [Feature Policy](/en-US/docs/Web/HTTP/Feature_Policy)
+- [Using Feature
+  Policy](/en-US/docs/Web/HTTP/Feature_Policy/Using_Feature_Policy)
diff --git a/files/en-us/web/http/headers/feature-policy/gyroscope/index.md b/files/en-us/web/http/headers/feature-policy/gyroscope/index.md
index 08ddf40309fbc6c..51e008fb0dec106 100644
--- a/files/en-us/web/http/headers/feature-policy/gyroscope/index.md
+++ b/files/en-us/web/http/headers/feature-policy/gyroscope/index.md
@@ -9,35 +9,31 @@ tags:
   - Experimental
 browser-compat: http.headers.Feature-Policy.gyroscope
 ---
-<p>{{HTTPSidebar}} {{SeeCompatTable}}</p>
+{{HTTPSidebar}} {{SeeCompatTable}}
 
-<p>The HTTP {{HTTPHeader("Feature-Policy")}} header <code>gyroscope</code> directive controls whether the current document is allowed to gather information about the orientation of the device through the {{domxref("Gyroscope")}} interface.</p>
+The HTTP {{HTTPHeader("Feature-Policy")}} header `gyroscope` directive controls whether the current document is allowed to gather information about the orientation of the device through the {{domxref("Gyroscope")}} interface.
 
-<h2 id="Syntax">Syntax</h2>
+## Syntax
 
-<pre>Feature-Policy: gyroscope &lt;allowlist&gt;;</pre>
+    Feature-Policy: gyroscope <allowlist>;
 
-<dl>
-  <dt>&lt;allowlist&gt;</dt>
-  <dd>A list of origins for which the feature is allowed. See <a href="/en-US/docs/Web/HTTP/Headers/Feature-Policy#syntax"><code>Feature-Policy</code></a>.</dd>
-</dl>
+- \<allowlist>
+  - : A list of origins for which the feature is allowed. See [`Feature-Policy`](/en-US/docs/Web/HTTP/Headers/Feature-Policy#syntax).
 
-<h2 id="Default_policy">Default policy</h2>
+## Default policy
 
-<p>Default allow list for <code>gyroscope</code> is <code>'self'</code>.</p>
+Default allow list for `gyroscope` is `'self'`.
 
-<h2 id="Specifications">Specifications</h2>
+## Specifications
 
-<p>{{Specifications}}</p>
+{{Specifications}}
 
-<h2 id="Browser_compatibility">Browser compatibility</h2>
+## Browser compatibility
 
-<p>{{Compat}}</p>
+{{Compat}}
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
- <li>{{HTTPHeader("Feature-Policy")}} header</li>
- <li><a href="/en-US/docs/Web/HTTP/Feature_Policy">Feature Policy</a></li>
- <li><a href="/en-US/docs/Web/HTTP/Feature_Policy/Using_Feature_Policy">Using Feature Policy</a></li>
-</ul>
+- {{HTTPHeader("Feature-Policy")}} header
+- [Feature Policy](/en-US/docs/Web/HTTP/Feature_Policy)
+- [Using Feature Policy](/en-US/docs/Web/HTTP/Feature_Policy/Using_Feature_Policy)
diff --git a/files/en-us/web/http/headers/feature-policy/index.md b/files/en-us/web/http/headers/feature-policy/index.md
index 02393c6729bd2f3..33037b7b7c20ccf 100644
--- a/files/en-us/web/http/headers/feature-policy/index.md
+++ b/files/en-us/web/http/headers/feature-policy/index.md
@@ -13,165 +13,143 @@ tags:
   - header
 browser-compat: http.headers.Feature-Policy
 ---
-<div>{{HTTPSidebar}} {{SeeCompatTable}}</div>
+{{HTTPSidebar}} {{SeeCompatTable}}
 
-<div class="notecard warning">
-  <p><strong>Warning:</strong> The header has now been renamed to <code>Permissions-Policy</code> in the spec, and this article will eventually be updated to reflect that change.</p>
-</div>
+> **Warning:** The header has now been renamed to `Permissions-Policy` in the spec, and this article will eventually be updated to reflect that change.
 
-<p>The HTTP <strong><code>Feature-Policy</code></strong> header provides a mechanism to allow and deny the use of browser features in its own frame, and in content within any {{HTMLElement("iframe")}} elements in the document.</p>
+The HTTP **`Feature-Policy`** header provides a mechanism to allow and deny the use of browser features in its own frame, and in content within any {{HTMLElement("iframe")}} elements in the document.
 
-<p>For more information, see the main <a href="/en-US/docs/Web/HTTP/Feature_Policy">Feature Policy</a> article.</p>
+For more information, see the main [Feature Policy](/en-US/docs/Web/HTTP/Feature_Policy) article.
 
 <table class="properties">
- <tbody>
-  <tr>
-   <th scope="row">Header type</th>
-   <td>{{Glossary("Response header")}}</td>
-  </tr>
-  <tr>
-   <th scope="row">{{Glossary("Forbidden header name")}}</th>
-   <td>yes</td>
-  </tr>
- </tbody>
+  <tbody>
+    <tr>
+      <th scope="row">Header type</th>
+      <td>{{Glossary("Response header")}}</td>
+    </tr>
+    <tr>
+      <th scope="row">{{Glossary("Forbidden header name")}}</th>
+      <td>yes</td>
+    </tr>
+  </tbody>
 </table>
 
-<h2 id="Syntax">Syntax</h2>
-
-<pre>Feature-Policy: &lt;directive&gt; &lt;allowlist&gt;</pre>
-
-<dl>
- <dt><code>&lt;directive&gt;</code></dt>
- <dd>The Feature Policy directive to apply the <code>allowlist</code> to. See <a href="#directives">Directives</a> below for a list of the permitted directive names.</dd>
- <dt>&lt;allowlist&gt;</dt>
- <dd><p>An <code>allowlist</code> is a list of origins that takes one or more of the following values, separated by spaces:</p>
-
-  <ul>
-   <li><code>*</code>: The feature will be allowed in this document, and all nested browsing contexts (iframes) regardless of their origin.</li>
-   <li><code>'self'</code>: The feature will be allowed in this document, and in all nested browsing contexts (iframes) in the same origin. The feature is not allowed in cross-origin documents in nested browsing contexts.</li>
-   <li><code>'src'</code>: (In an iframe <code>allow</code> attribute only) The feature will be allowed in this iframe, as long as the document loaded into it comes from the same origin as the URL in the iframe's {{HTMLElement('iframe','src','#Attributes')}} attribute.
-    <div class="notecard note">
-      <p><strong>Note:</strong> The <code>'src'</code> origin is used in the iframe <code>allow</code> attribute only, and is the <em>default</em> <code>allowlist</code> value.</p>
-    </div>
-   </li>
-   <li><code>'none'</code>: The feature is disabled in top-level and nested browsing contexts.</li>
-   <li>&lt;origin(s)&gt;: The feature is allowed for specific origins (for example, https://example.com). Origins should be separated by a space.</li>
-  </ul>
-
-  <p>The values <code>*</code> (enable for all origins) or <code>'none'</code> (disable for all origins) may only be used alone, while <code>'self'</code> and <code>'src'</code> may be used with one or more origins.</p>
-  <p>Features have a <em>default</em> allowlist, which is one of: <code>*</code>, <code>'self'</code>, or <code>'none'</code>.</p>
-</dd>
-</dl>
-
-
-
-
-<h2 id="Directives">Directives</h2>
-
-<dl>
- <dt>{{httpheader('Feature-Policy/accelerometer','accelerometer')}}</dt>
- <dd>Controls whether the current document is allowed to gather information about the acceleration of the device through the {{DOMxRef("Accelerometer")}} interface.</dd>
- <dt>{{httpheader('Feature-Policy/ambient-light-sensor','ambient-light-sensor')}}</dt>
- <dd>Controls whether the current document is allowed to gather information about the amount of light in the environment around the device through the {{DOMxRef("AmbientLightSensor")}} interface.</dd>
- <dt>{{httpheader('Feature-Policy/autoplay','autoplay')}}</dt>
- <dd>Controls whether the current document is allowed to autoplay media requested through the {{domxref("HTMLMediaElement")}} interface. When this policy is disabled and there were no user gestures, the {{jsxref("Promise")}} returned by {{domxref("HTMLMediaElement.play()")}} will reject with a {{domxref("DOMException")}}. The autoplay attribute on {{HTMLELement("audio")}} and {{HTMLElement("video")}} elements will be ignored.</dd>
- <dt>{{httpheader('Feature-Policy/battery','battery')}}</dt>
- <dd>Controls whether the use of the <a href="/en-US/docs/Web/API/Battery_Status_API">Battery Status API</a> is allowed. When this policy is disabled, the {{JSxRef("Promise")}} returned by {{DOMxRef("Navigator.getBattery","Navigator.getBattery()")}} will reject with a {{Exception("NotAllowedError")}} {{DOMxRef("DOMException")}}.</dd>
- <dt>{{httpheader('Feature-Policy/camera', 'camera')}}</dt>
- <dd>Controls whether the current document is allowed to use video input devices. When this policy is disabled, the {{jsxref("Promise")}} returned by {{domxref("MediaDevices.getUserMedia", "getUserMedia()")}} will reject with a {{Exception("NotAllowedError")}} {{DOMxRef("DOMException")}}.</dd>
- <dt>{{HTTPHeader('Feature-Policy/display-capture', 'display-capture')}}</dt>
- <dd>Controls whether or not the current document is permitted to use the {{domxref("MediaDevices.getDisplayMedia", "getDisplayMedia()")}} method to capture screen contents. When this policy is disabled, the promise returned by <code>getDisplayMedia()</code> will reject with a {{Exception("NotAllowedError")}} if permission is not obtained to capture the display's contents.</dd>
- <dt>{{httpheader('Feature-Policy/document-domain','document-domain')}}</dt>
- <dd>Controls whether the current document is allowed to set {{domxref("document.domain")}}. When this policy is disabled, attempting to set {{domxref("document.domain")}} will fail and cause a {{Exception("SecurityError")}} {{domxref("DOMException")}} to be thrown.</dd>
- <dt>{{httpheader('Feature-Policy/encrypted-media', 'encrypted-media')}}</dt>
- <dd>Controls whether the current document is allowed to use the <a href="/en-US/docs/Web/API/Encrypted_Media_Extensions_API">Encrypted Media Extensions</a> API (EME). When this policy is disabled, the {{jsxref("Promise")}} returned by {{domxref("Navigator.requestMediaKeySystemAccess()")}} will reject with a {{domxref("DOMException")}}.</dd>
- <dt>{{httpheader('Feature-Policy/execution-while-not-rendered', 'execution-while-not-rendered')}}</dt>
- <dd>Controls whether tasks should execute in frames while they're not being rendered (e.g. if an iframe is <code><a href="/en-US/docs/Web/HTML/Global_attributes/hidden">hidden</a></code> or <code>display: none</code>).</dd>
- <dt>{{httpheader('Feature-Policy/execution-while-out-of-viewport', 'execution-while-out-of-viewport')}}</dt>
- <dd>Controls whether tasks should execute in frames while they're outside of the visible viewport.</dd>
- <dt>{{httpheader('Feature-Policy/fullscreen','fullscreen')}}</dt>
- <dd>Controls whether the current document is allowed to use {{DOMxRef("Element.requestFullScreen()")}}. When this policy is disabled, the returned {{JSxRef("Promise")}} rejects with a {{JSxRef("TypeError")}}.</dd>
- <dt>{{httpheader('Feature-Policy/gamepad','gamepad')}}</dt>
- <dd>Controls whether the current document is allowed to use the <a href="/en-US/docs/Web/API/Gamepad_API">Gamepad API</a>.
-  When this policy is disabled, calls to {{domxref('Navigator.getGamepads()')}} will throw a <code>SecurityError</code> {{domxref('DOMException')}}, and the {{event("gamepadconnected")}} and {{event("gamepaddisconnected")}} events will not fire.</dd>
- <dt>{{httpheader('Feature-Policy/geolocation','geolocation')}}</dt>
- <dd>Controls whether the current document is allowed to use the {{domxref('Geolocation')}} Interface. When this policy is disabled, calls to {{domxref('Geolocation.getCurrentPosition','getCurrentPosition()')}} and {{domxref('Geolocation.watchPosition','watchPosition()')}} will cause those functions' callbacks to be invoked with a {{domxref('GeolocationPositionError')}} code of <code>PERMISSION_DENIED</code>.</dd>
- <dt>{{httpheader('Feature-Policy/gyroscope','gyroscope')}}</dt>
- <dd>Controls whether the current document is allowed to gather information about the orientation of the device through the {{DOMxRef("Gyroscope")}} interface.</dd>
- <dt>{{httpheader('Feature-Policy/layout-animations','layout-animations')}}</dt>
- <dd>Controls whether the current document is allowed to show layout animations.</dd>
- <dt>{{httpheader('Feature-Policy/legacy-image-formats','legacy-image-formats')}}</dt>
- <dd>Controls whether the current document is allowed to display images in legacy formats.</dd>
- <dt>{{httpheader('Feature-Policy/magnetometer','magnetometer')}}</dt>
- <dd>Controls whether the current document is allowed to gather information about the orientation of the device through the {{DOMxRef("Magnetometer")}} interface.</dd>
- <dt>{{httpheader('Feature-Policy/microphone','microphone')}}</dt>
- <dd>Controls whether the current document is allowed to use audio input devices. When this policy is disabled, the {{jsxref("Promise")}} returned by {{domxref("MediaDevices.getUserMedia()")}} will reject with a {{Exception("NotAllowedError")}}.</dd>
- <dt>{{httpheader('Feature-Policy/midi', 'midi')}}</dt>
- <dd>Controls whether the current document is allowed to use the <a href="/en-US/docs/Web/API/Web_MIDI_API">Web MIDI API</a>. When this policy is disabled, the {{jsxref("Promise")}} returned by {{domxref("Navigator.requestMIDIAccess()")}} will reject with a {{domxref("DOMException")}}.</dd>
- <dt>{{httpheader('Feature-Policy/navigation-override','navigation-override')}}</dt>
- <dd>Controls the availability of mechanisms that enables the page author to take control over the behavior of <a href="https://www.w3.org/TR/css-nav/">spatial navigation</a>, or to cancel it outright.</dd>
- <dt>{{httpheader('Feature-Policy/oversized-images','oversized-images')}}</dt>
- <dd>Controls whether the current document is allowed to download and display large images.</dd>
- <dt>{{httpheader('Feature-Policy/payment', 'payment')}}</dt>
- <dd>Controls whether the current document is allowed to use the <a href="/en-US/docs/Web/API/Payment_Request_API">Payment Request API</a>. When this policy is enabled, the {{domxref("PaymentRequest","PaymentRequest()")}} constructor will throw a {{Exception("SecurityError")}} {{domxref("DOMException")}}.</dd>
- <dt>{{httpheader('Feature-Policy/picture-in-picture', 'picture-in-picture')}}</dt>
- <dd>Controls whether the current document is allowed to play a video in a Picture-in-Picture mode via the corresponding API.</dd>
- <dt>{{httpheader("Feature-Policy/publickey-credentials-get", "publickey-credentials-get")}}</dt>
- <dd>Controls whether the current document is allowed to use the <a href="/en-US/docs/Web/API/Web_Authentication_API">Web Authentication API</a> to retrieve already stored public-key credentials, i.e. via {{domxref("CredentialsContainer.get","navigator.credentials.get({publicKey: ..., ...})")}}.</dd>
- <dt>{{httpheader('Feature-Policy/sync-xhr', 'sync-xhr')}}</dt>
- <dd>Controls whether the current document is allowed to make synchronous {{DOMxRef("XMLHttpRequest")}} requests.</dd>
- <dt>{{httpheader('Feature-Policy/unoptimized-images', 'unoptimized-images')}} {{experimental_inline}}{{Non-standard_Inline}}</dt>
- <dd>Controls whether the current document is allowed to download and display unoptimized images.</dd>
- <dt>{{httpheader('Feature-Policy/unsized-media', 'unsized-media')}} {{experimental_inline}}{{Non-standard_Inline}}</dt>
- <dd>Controls whether the current document is allowed to change the size of media elements after the initial layout is complete.</dd>
- <dt>{{httpheader('Feature-Policy/usb', 'usb')}}</dt>
- <dd>Controls whether the current document is allowed to use the <a href="https://wicg.github.io/webusb/">WebUSB API</a>.</dd>
- <dt>{{httpheader('Feature-Policy/vibrate', 'vibrate')}} {{deprecated_inline}}{{experimental_inline}}{{Non-standard_Inline}}</dt>
- <dd>Controls whether the current document is  allowed to trigger device vibrations via {{DOMxRef("Navigator.vibrate","Navigator.vibrate()")}} method of <a href="/en-US/docs/Web/API/Vibration_API">Vibration API</a>.</dd>
- <dt>{{httpheader('Feature-Policy/vr', 'vr')}} {{deprecated_inline}}</dt>
- <dd>Controls whether the current document is allowed to use the <a href="/en-US/docs/Web/API/WebVR_API">WebVR API</a>. When this policy is disabled, the {{jsxref("Promise")}} returned by {{domxref("Navigator.getVRDisplays","Navigator.getVRDisplays()")}} will reject with a {{domxref("DOMException")}}. Keep in mind that the WebVR standard is in the process of being replaced with <a href="/en-US/docs/Web/API/WebXR_Device_API">WebXR</a>.</dd>
- <dt>{{httpheader('Feature-Policy/screen-wake-lock', 'screen-wake-lock')}}</dt>
- <dd>Controls whether the current document is allowed to use <a href="/en-US/docs/Web/API/Screen_Wake_Lock_API">Screen Wake Lock API</a> to indicate that device should not turn off or dim the screen.</dd>
- <dt>{{httpheader("Feature-Policy/web-share", "web-share")}}</dt>
- <dd>Controls whether or not the current document is allowed to use the {{domxref("Navigator.share","Navigator.share()")}} of Web Share API to share text, links, images, and other content to arbitrary destinations of user's choice, e.g. mobile apps.</dd>
- <dt>{{httpheader("Feature-Policy/xr-spatial-tracking", "xr-spatial-tracking")}}</dt>
- <dd>Controls whether or not the current document is allowed to use the <a href="/en-US/docs/Web/API/WebXR_Device_API">WebXR Device API</a> to interact with a WebXR session.</dd>
-</dl>
-
-<h2 id="Example">Example</h2>
-
-<p>SecureCorp Inc. wants to disable Microphone and Geolocation APIs in its application. It can do so by delivering the following HTTP response header to define a feature policy:</p>
-
-<pre>Feature-Policy: microphone 'none'; geolocation 'none'</pre>
-
-<p>By specifying the <code>'none'</code> keyword for the origin list, the specified features will be disabled for all browsing contexts (this includes all iframes), regardless of their origin.</p>
-
-<h2 id="Specifications">Specifications</h2>
-
-<table class="standard-table">
- <thead>
-  <tr>
-   <th scope="col">Specification</th>
-  </tr>
- </thead>
- <tbody>
-  <tr>
-   <td><a href="https://w3c.github.io/webappsec-permissions-policy/#permissions-policy-http-header-field">Permissions Policy</a></td>
-  </tr>
- </tbody>
-</table>
-
-<h2 id="Browser_compatibility">Browser compatibility</h2>
-
-<p>{{Compat}}</p>
-
-<h2 id="See_also">See also</h2>
-
-<ul>
- <li><a href="/en-US/docs/Web/HTTP/Feature_Policy">Feature Policy</a></li>
- <li><a href="/en-US/docs/Web/HTTP/Feature_Policy/Using_Feature_Policy">Using Feature Policy</a></li>
- <li>{{DOMxRef("Document.featurePolicy")}} and {{DOMxRef("FeaturePolicy")}}</li>
- <li><a class="external external-icon" href="https://chrome.google.com/webstore/detail/feature-policy-tester-dev/pchamnkhkeokbpahnocjaeednpbpacop" rel="noopener">Feature-Policy Tester (Chrome Developer Tools extension)</a></li>
- <li>{{HTTPHeader("Content-Security-Policy")}}</li>
- <li>{{HTTPHeader("Referrer-Policy")}}</li>
-</ul>
+## Syntax
+
+    Feature-Policy: <directive> <allowlist>
+
+- `<directive>`
+  - : The Feature Policy directive to apply the `allowlist` to. See [Directives](#directives) below for a list of the permitted directive names.
+- \<allowlist>
+
+  - : An `allowlist` is a list of origins that takes one or more of the following values, separated by spaces:
+
+    - `*`: The feature will be allowed in this document, and all nested browsing contexts (iframes) regardless of their origin.
+    - `'self'`: The feature will be allowed in this document, and in all nested browsing contexts (iframes) in the same origin. The feature is not allowed in cross-origin documents in nested browsing contexts.
+    - `'src'`: (In an iframe `allow` attribute only) The feature will be allowed in this iframe, as long as the document loaded into it comes from the same origin as the URL in the iframe's {{HTMLElement('iframe','src','#Attributes')}} attribute.
+
+      > **Note:** The `'src'` origin is used in the iframe `allow` attribute only, and is the _default_ `allowlist` value.
+
+    - `'none'`: The feature is disabled in top-level and nested browsing contexts.
+    - \<origin(s)>: The feature is allowed for specific origins (for example, https\://example.com). Origins should be separated by a space.
+
+    The values `*` (enable for all origins) or `'none'` (disable for all origins) may only be used alone, while `'self'` and `'src'` may be used with one or more origins.
+
+    Features have a _default_ allowlist, which is one of: `*`, `'self'`, or `'none'`.
+
+## Directives
+
+- {{httpheader('Feature-Policy/accelerometer','accelerometer')}}
+  - : Controls whether the current document is allowed to gather information about the acceleration of the device through the {{DOMxRef("Accelerometer")}} interface.
+- {{httpheader('Feature-Policy/ambient-light-sensor','ambient-light-sensor')}}
+  - : Controls whether the current document is allowed to gather information about the amount of light in the environment around the device through the {{DOMxRef("AmbientLightSensor")}} interface.
+- {{httpheader('Feature-Policy/autoplay','autoplay')}}
+  - : Controls whether the current document is allowed to autoplay media requested through the {{domxref("HTMLMediaElement")}} interface. When this policy is disabled and there were no user gestures, the {{jsxref("Promise")}} returned by {{domxref("HTMLMediaElement.play()")}} will reject with a {{domxref("DOMException")}}. The autoplay attribute on {{HTMLELement("audio")}} and {{HTMLElement("video")}} elements will be ignored.
+- {{httpheader('Feature-Policy/battery','battery')}}
+  - : Controls whether the use of the [Battery Status API](/en-US/docs/Web/API/Battery_Status_API) is allowed. When this policy is disabled, the {{JSxRef("Promise")}} returned by {{DOMxRef("Navigator.getBattery","Navigator.getBattery()")}} will reject with a {{Exception("NotAllowedError")}} {{DOMxRef("DOMException")}}.
+- {{httpheader('Feature-Policy/camera', 'camera')}}
+  - : Controls whether the current document is allowed to use video input devices. When this policy is disabled, the {{jsxref("Promise")}} returned by {{domxref("MediaDevices.getUserMedia", "getUserMedia()")}} will reject with a {{Exception("NotAllowedError")}} {{DOMxRef("DOMException")}}.
+- {{HTTPHeader('Feature-Policy/display-capture', 'display-capture')}}
+  - : Controls whether or not the current document is permitted to use the {{domxref("MediaDevices.getDisplayMedia", "getDisplayMedia()")}} method to capture screen contents. When this policy is disabled, the promise returned by `getDisplayMedia()` will reject with a {{Exception("NotAllowedError")}} if permission is not obtained to capture the display's contents.
+- {{httpheader('Feature-Policy/document-domain','document-domain')}}
+  - : Controls whether the current document is allowed to set {{domxref("document.domain")}}. When this policy is disabled, attempting to set {{domxref("document.domain")}} will fail and cause a {{Exception("SecurityError")}} {{domxref("DOMException")}} to be thrown.
+- {{httpheader('Feature-Policy/encrypted-media', 'encrypted-media')}}
+  - : Controls whether the current document is allowed to use the [Encrypted Media Extensions](/en-US/docs/Web/API/Encrypted_Media_Extensions_API) API (EME). When this policy is disabled, the {{jsxref("Promise")}} returned by {{domxref("Navigator.requestMediaKeySystemAccess()")}} will reject with a {{domxref("DOMException")}}.
+- {{httpheader('Feature-Policy/execution-while-not-rendered', 'execution-while-not-rendered')}}
+  - : Controls whether tasks should execute in frames while they're not being rendered (e.g. if an iframe is [`hidden`](/en-US/docs/Web/HTML/Global_attributes/hidden) or `display: none`).
+- {{httpheader('Feature-Policy/execution-while-out-of-viewport', 'execution-while-out-of-viewport')}}
+  - : Controls whether tasks should execute in frames while they're outside of the visible viewport.
+- {{httpheader('Feature-Policy/fullscreen','fullscreen')}}
+  - : Controls whether the current document is allowed to use {{DOMxRef("Element.requestFullScreen()")}}. When this policy is disabled, the returned {{JSxRef("Promise")}} rejects with a {{JSxRef("TypeError")}}.
+- {{httpheader('Feature-Policy/gamepad','gamepad')}}
+  - : Controls whether the current document is allowed to use the [Gamepad API](/en-US/docs/Web/API/Gamepad_API).
+    When this policy is disabled, calls to {{domxref('Navigator.getGamepads()')}} will throw a `SecurityError` {{domxref('DOMException')}}, and the {{event("gamepadconnected")}} and {{event("gamepaddisconnected")}} events will not fire.
+- {{httpheader('Feature-Policy/geolocation','geolocation')}}
+  - : Controls whether the current document is allowed to use the {{domxref('Geolocation')}} Interface. When this policy is disabled, calls to {{domxref('Geolocation.getCurrentPosition','getCurrentPosition()')}} and {{domxref('Geolocation.watchPosition','watchPosition()')}} will cause those functions' callbacks to be invoked with a {{domxref('GeolocationPositionError')}} code of `PERMISSION_DENIED`.
+- {{httpheader('Feature-Policy/gyroscope','gyroscope')}}
+  - : Controls whether the current document is allowed to gather information about the orientation of the device through the {{DOMxRef("Gyroscope")}} interface.
+- {{httpheader('Feature-Policy/layout-animations','layout-animations')}}
+  - : Controls whether the current document is allowed to show layout animations.
+- {{httpheader('Feature-Policy/legacy-image-formats','legacy-image-formats')}}
+  - : Controls whether the current document is allowed to display images in legacy formats.
+- {{httpheader('Feature-Policy/magnetometer','magnetometer')}}
+  - : Controls whether the current document is allowed to gather information about the orientation of the device through the {{DOMxRef("Magnetometer")}} interface.
+- {{httpheader('Feature-Policy/microphone','microphone')}}
+  - : Controls whether the current document is allowed to use audio input devices. When this policy is disabled, the {{jsxref("Promise")}} returned by {{domxref("MediaDevices.getUserMedia()")}} will reject with a {{Exception("NotAllowedError")}}.
+- {{httpheader('Feature-Policy/midi', 'midi')}}
+  - : Controls whether the current document is allowed to use the [Web MIDI API](/en-US/docs/Web/API/Web_MIDI_API). When this policy is disabled, the {{jsxref("Promise")}} returned by {{domxref("Navigator.requestMIDIAccess()")}} will reject with a {{domxref("DOMException")}}.
+- {{httpheader('Feature-Policy/navigation-override','navigation-override')}}
+  - : Controls the availability of mechanisms that enables the page author to take control over the behavior of [spatial navigation](https://www.w3.org/TR/css-nav/), or to cancel it outright.
+- {{httpheader('Feature-Policy/oversized-images','oversized-images')}}
+  - : Controls whether the current document is allowed to download and display large images.
+- {{httpheader('Feature-Policy/payment', 'payment')}}
+  - : Controls whether the current document is allowed to use the [Payment Request API](/en-US/docs/Web/API/Payment_Request_API). When this policy is enabled, the {{domxref("PaymentRequest","PaymentRequest()")}} constructor will throw a {{Exception("SecurityError")}} {{domxref("DOMException")}}.
+- {{httpheader('Feature-Policy/picture-in-picture', 'picture-in-picture')}}
+  - : Controls whether the current document is allowed to play a video in a Picture-in-Picture mode via the corresponding API.
+- {{httpheader("Feature-Policy/publickey-credentials-get", "publickey-credentials-get")}}
+  - : Controls whether the current document is allowed to use the [Web Authentication API](/en-US/docs/Web/API/Web_Authentication_API) to retrieve already stored public-key credentials, i.e. via {{domxref("CredentialsContainer.get","navigator.credentials.get({publicKey: ..., ...})")}}.
+- {{httpheader('Feature-Policy/sync-xhr', 'sync-xhr')}}
+  - : Controls whether the current document is allowed to make synchronous {{DOMxRef("XMLHttpRequest")}} requests.
+- {{httpheader('Feature-Policy/unoptimized-images', 'unoptimized-images')}} {{experimental_inline}}{{Non-standard_Inline}}
+  - : Controls whether the current document is allowed to download and display unoptimized images.
+- {{httpheader('Feature-Policy/unsized-media', 'unsized-media')}} {{experimental_inline}}{{Non-standard_Inline}}
+  - : Controls whether the current document is allowed to change the size of media elements after the initial layout is complete.
+- {{httpheader('Feature-Policy/usb', 'usb')}}
+  - : Controls whether the current document is allowed to use the [WebUSB API](https://wicg.github.io/webusb/).
+- {{httpheader('Feature-Policy/vibrate', 'vibrate')}} {{deprecated_inline}}{{experimental_inline}}{{Non-standard_Inline}}
+  - : Controls whether the current document is allowed to trigger device vibrations via {{DOMxRef("Navigator.vibrate","Navigator.vibrate()")}} method of [Vibration API](/en-US/docs/Web/API/Vibration_API).
+- {{httpheader('Feature-Policy/vr', 'vr')}} {{deprecated_inline}}
+  - : Controls whether the current document is allowed to use the [WebVR API](/en-US/docs/Web/API/WebVR_API). When this policy is disabled, the {{jsxref("Promise")}} returned by {{domxref("Navigator.getVRDisplays","Navigator.getVRDisplays()")}} will reject with a {{domxref("DOMException")}}. Keep in mind that the WebVR standard is in the process of being replaced with [WebXR](/en-US/docs/Web/API/WebXR_Device_API).
+- {{httpheader('Feature-Policy/screen-wake-lock', 'screen-wake-lock')}}
+  - : Controls whether the current document is allowed to use [Screen Wake Lock API](/en-US/docs/Web/API/Screen_Wake_Lock_API) to indicate that device should not turn off or dim the screen.
+- {{httpheader("Feature-Policy/web-share", "web-share")}}
+  - : Controls whether or not the current document is allowed to use the {{domxref("Navigator.share","Navigator.share()")}} of Web Share API to share text, links, images, and other content to arbitrary destinations of user's choice, e.g. mobile apps.
+- {{httpheader("Feature-Policy/xr-spatial-tracking", "xr-spatial-tracking")}}
+  - : Controls whether or not the current document is allowed to use the [WebXR Device API](/en-US/docs/Web/API/WebXR_Device_API) to interact with a WebXR session.
+
+## Example
+
+SecureCorp Inc. wants to disable Microphone and Geolocation APIs in its application. It can do so by delivering the following HTTP response header to define a feature policy:
+
+    Feature-Policy: microphone 'none'; geolocation 'none'
+
+By specifying the `'none'` keyword for the origin list, the specified features will be disabled for all browsing contexts (this includes all iframes), regardless of their origin.
+
+## Specifications
+
+| Specification                                                                                                  |
+| -------------------------------------------------------------------------------------------------------------- |
+| [Permissions Policy](https://w3c.github.io/webappsec-permissions-policy/#permissions-policy-http-header-field) |
+
+## Browser compatibility
+
+{{Compat}}
+
+## See also
+
+- [Feature Policy](/en-US/docs/Web/HTTP/Feature_Policy)
+- [Using Feature Policy](/en-US/docs/Web/HTTP/Feature_Policy/Using_Feature_Policy)
+- {{DOMxRef("Document.featurePolicy")}} and {{DOMxRef("FeaturePolicy")}}
+- [Feature-Policy Tester (Chrome Developer Tools extension)](https://chrome.google.com/webstore/detail/feature-policy-tester-dev/pchamnkhkeokbpahnocjaeednpbpacop)
+- {{HTTPHeader("Content-Security-Policy")}}
+- {{HTTPHeader("Referrer-Policy")}}
diff --git a/files/en-us/web/http/headers/feature-policy/layout-animations/index.md b/files/en-us/web/http/headers/feature-policy/layout-animations/index.md
index 4974d5eb546682b..f42b6add04512c3 100644
--- a/files/en-us/web/http/headers/feature-policy/layout-animations/index.md
+++ b/files/en-us/web/http/headers/feature-policy/layout-animations/index.md
@@ -11,31 +11,27 @@ tags:
   - Non-standard
 browser-compat: http.headers.Feature-Policy.layout-animations
 ---
-<p>{{HTTPSidebar}} {{SeeCompatTable}}{{Non-standard_header}}</p>
+{{HTTPSidebar}} {{SeeCompatTable}}{{Non-standard_header}}
 
-<p>The HTTP {{HTTPHeader("Feature-Policy")}} header <code>layout-animations</code> directive controls whether the current document is allowed to show layout animations.</p>
+The HTTP {{HTTPHeader("Feature-Policy")}} header `layout-animations` directive controls whether the current document is allowed to show layout animations.
 
-<h2 id="Syntax">Syntax</h2>
+## Syntax
 
-<pre>Feature-Policy: layout-animations &lt;allowlist&gt;;</pre>
+    Feature-Policy: layout-animations <allowlist>;
 
-<dl>
-  <dt>&lt;allowlist&gt;</dt>
-  <dd>A list of origins for which the feature is allowed. See <a href="/en-US/docs/Web/HTTP/Headers/Feature-Policy#syntax"><code>Feature-Policy</code></a>.</dd>
-</dl>
+- \<allowlist>
+  - : A list of origins for which the feature is allowed. See [`Feature-Policy`](/en-US/docs/Web/HTTP/Headers/Feature-Policy#syntax).
 
-<h2 id="Default_policy">Default policy</h2>
+## Default policy
 
-<p>Default allow list for <code>layout-animations</code> is <code>'self'</code>.</p>
+Default allow list for `layout-animations` is `'self'`.
 
-<h2 id="Browser_compatibility">Browser compatibility</h2>
+## Browser compatibility
 
-<p>{{Compat}}</p>
+{{Compat}}
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
- <li>{{HTTPHeader("Feature-Policy")}} header</li>
- <li><a href="/en-US/docs/Web/HTTP/Feature_Policy">Feature Policy</a></li>
- <li><a href="/en-US/docs/Web/HTTP/Feature_Policy/Using_Feature_Policy">Using Feature Policy</a></li>
-</ul>
+- {{HTTPHeader("Feature-Policy")}} header
+- [Feature Policy](/en-US/docs/Web/HTTP/Feature_Policy)
+- [Using Feature Policy](/en-US/docs/Web/HTTP/Feature_Policy/Using_Feature_Policy)
diff --git a/files/en-us/web/http/headers/feature-policy/legacy-image-formats/index.md b/files/en-us/web/http/headers/feature-policy/legacy-image-formats/index.md
index 20c8297a97ac762..2d2eab69542bf9e 100644
--- a/files/en-us/web/http/headers/feature-policy/legacy-image-formats/index.md
+++ b/files/en-us/web/http/headers/feature-policy/legacy-image-formats/index.md
@@ -11,31 +11,27 @@ tags:
   - Non-standard
 browser-compat: http.headers.Feature-Policy.legacy-image-formats
 ---
-<p>{{HTTPSidebar}}{{SeeCompatTable}}{{Non-standard_header}}</p>
+{{HTTPSidebar}}{{SeeCompatTable}}{{Non-standard_header}}
 
-<p>The HTTP {{HTTPHeader("Feature-Policy")}} header <code>legacy-image-formats</code> directive controls whether the current document is allowed to display images in legacy formats.</p>
+The HTTP {{HTTPHeader("Feature-Policy")}} header `legacy-image-formats` directive controls whether the current document is allowed to display images in legacy formats.
 
-<h2 id="Syntax">Syntax</h2>
+## Syntax
 
-<pre>Feature-Policy: legacy-image-formats &lt;allowlist&gt;;</pre>
+    Feature-Policy: legacy-image-formats <allowlist>;
 
-<dl>
-  <dt>&lt;allowlist&gt;</dt>
-  <dd>A list of origins for which the feature is allowed. See <a href="/en-US/docs/Web/HTTP/Headers/Feature-Policy#syntax"><code>Feature-Policy</code></a>.</dd>
-</dl>
+- \<allowlist>
+  - : A list of origins for which the feature is allowed. See [`Feature-Policy`](/en-US/docs/Web/HTTP/Headers/Feature-Policy#syntax).
 
-<h2 id="Default_policy">Default policy</h2>
+## Default policy
 
-<p>Default allow list for <code>legacy-image-formats</code> is <code>'self'</code>.</p>
+Default allow list for `legacy-image-formats` is `'self'`.
 
-<h2 id="Browser_compatibility">Browser compatibility</h2>
+## Browser compatibility
 
-<p>{{Compat}}</p>
+{{Compat}}
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
- <li>{{HTTPHeader("Feature-Policy")}} header</li>
- <li><a href="/en-US/docs/Web/HTTP/Feature_Policy">Feature Policy</a></li>
- <li><a href="/en-US/docs/Web/HTTP/Feature_Policy/Using_Feature_Policy">Using Feature Policy</a></li>
-</ul>
+- {{HTTPHeader("Feature-Policy")}} header
+- [Feature Policy](/en-US/docs/Web/HTTP/Feature_Policy)
+- [Using Feature Policy](/en-US/docs/Web/HTTP/Feature_Policy/Using_Feature_Policy)
diff --git a/files/en-us/web/http/headers/feature-policy/magnetometer/index.md b/files/en-us/web/http/headers/feature-policy/magnetometer/index.md
index 07700baa9488c74..3c747de4a1fde6b 100644
--- a/files/en-us/web/http/headers/feature-policy/magnetometer/index.md
+++ b/files/en-us/web/http/headers/feature-policy/magnetometer/index.md
@@ -10,36 +10,31 @@ tags:
   - Experimental
 browser-compat: http.headers.Feature-Policy.magnetometer
 ---
-<p>{{HTTPSidebar}} {{SeeCompatTable}}</p>
+{{HTTPSidebar}} {{SeeCompatTable}}
 
-<p>The HTTP {{HTTPHeader("Feature-Policy")}} header <code>magnetometer</code> directive controls whether the current document is allowed to gather information about the orientation of the device through the {{domxref("Magnetometer")}} interface.</p>
+The HTTP {{HTTPHeader("Feature-Policy")}} header `magnetometer` directive controls whether the current document is allowed to gather information about the orientation of the device through the {{domxref("Magnetometer")}} interface.
 
-<h2 id="Syntax">Syntax</h2>
+## Syntax
 
-<pre>Feature-Policy: magnetometer &lt;allowlist&gt;;</pre>
+    Feature-Policy: magnetometer <allowlist>;
 
-<dl>
-  <dt>&lt;allowlist&gt;</dt>
-  <dd>A list of origins for which the feature is allowed. See <a href="/en-US/docs/Web/HTTP/Headers/Feature-Policy#syntax"><code>Feature-Policy</code></a>.</dd>
-</dl>
+- \<allowlist>
+  - : A list of origins for which the feature is allowed. See [`Feature-Policy`](/en-US/docs/Web/HTTP/Headers/Feature-Policy#syntax).
 
-<h2 id="Default_policy">Default policy</h2>
+## Default policy
 
-<p>Default allow list for <code>magnetometer</code> is <code>'self'</code>.</p>
+Default allow list for `magnetometer` is `'self'`.
 
+## Specifications
 
-<h2 id="Specifications">Specifications</h2>
+{{Specifications}}
 
-<p>{{Specifications}}</p>
+## Browser compatibility
 
-<h2 id="Browser_compatibility">Browser compatibility</h2>
+{{Compat}}
 
-<p>{{Compat}}</p>
+## See also
 
-<h2 id="See_also">See also</h2>
-
-<ul>
- <li>{{HTTPHeader("Feature-Policy")}} header</li>
- <li><a href="/en-US/docs/Web/HTTP/Feature_Policy">Feature Policy</a></li>
- <li><a href="/en-US/docs/Web/HTTP/Feature_Policy/Using_Feature_Policy">Using Feature Policy</a></li>
-</ul>
+- {{HTTPHeader("Feature-Policy")}} header
+- [Feature Policy](/en-US/docs/Web/HTTP/Feature_Policy)
+- [Using Feature Policy](/en-US/docs/Web/HTTP/Feature_Policy/Using_Feature_Policy)
diff --git a/files/en-us/web/http/headers/feature-policy/microphone/index.md b/files/en-us/web/http/headers/feature-policy/microphone/index.md
index e3fb1a3993b7541..f3dbfa8d1d3dc8b 100644
--- a/files/en-us/web/http/headers/feature-policy/microphone/index.md
+++ b/files/en-us/web/http/headers/feature-policy/microphone/index.md
@@ -2,49 +2,44 @@
 title: 'Feature-Policy: microphone'
 slug: Web/HTTP/Headers/Feature-Policy/microphone
 tags:
-- Feature Policy
-- Feature-Policy
-- HTTP
-- header
-- microphone
-- Experimental
+  - Feature Policy
+  - Feature-Policy
+  - HTTP
+  - header
+  - microphone
+  - Experimental
 browser-compat: http.headers.Feature-Policy.microphone
 ---
-<div>{{HTTPSidebar}} {{SeeCompatTable}}</div>
+{{HTTPSidebar}} {{SeeCompatTable}}
 
-<p>The HTTP {{HTTPHeader("Feature-Policy")}} header
-    <code>microphone</code> directive controls whether the current document is allowed to
-    use audio input devices. When this policy is enabled, the {{jsxref("Promise")}}
-    returned by {{domxref("MediaDevices.getUserMedia()")}} will reject with a
-    <code>NotAllowedError</code>.</p>
+The HTTP {{HTTPHeader("Feature-Policy")}} header
+`microphone` directive controls whether the current document is allowed to
+use audio input devices. When this policy is enabled, the {{jsxref("Promise")}}
+returned by {{domxref("MediaDevices.getUserMedia()")}} will reject with a
+`NotAllowedError`.
 
-<h2 id="Syntax">Syntax</h2>
+## Syntax
 
-<pre>Feature-Policy: microphone &lt;allowlist&gt;;</pre>
+    Feature-Policy: microphone <allowlist>;
 
-<dl>
-  <dt>&lt;allowlist&gt;</dt>
-  <dd>A list of origins for which the feature is allowed. See <a href="/en-US/docs/Web/HTTP/Headers/Feature-Policy#syntax"><code>Feature-Policy</code></a>.</dd>
-</dl>
+- \<allowlist>
+  - : A list of origins for which the feature is allowed. See [`Feature-Policy`](/en-US/docs/Web/HTTP/Headers/Feature-Policy#syntax).
 
-<h2 id="Default_policy">Default policy</h2>
+## Default policy
 
-<p>Default allow list for <code>microphone</code> is <code>'self'</code>.</p>
+Default allow list for `microphone` is `'self'`.
 
+## Specifications
 
-<h2 id="Specifications">Specifications</h2>
+{{Specifications}}
 
-<p>{{Specifications}}</p>
+## Browser compatibility
 
-<h2 id="Browser_compatibility">Browser compatibility</h2>
+{{Compat}}
 
-<p>{{Compat}}</p>
+## See also
 
-<h2 id="See_also">See also</h2>
-
-<ul>
-  <li>{{HTTPHeader("Feature-Policy")}} header</li>
-  <li><a href="/en-US/docs/Web/HTTP/Feature_Policy">Feature Policy</a></li>
-  <li><a href="/en-US/docs/Web/HTTP/Feature_Policy/Using_Feature_Policy">Using Feature
-      Policy</a></li>
-</ul>
+- {{HTTPHeader("Feature-Policy")}} header
+- [Feature Policy](/en-US/docs/Web/HTTP/Feature_Policy)
+- [Using Feature
+  Policy](/en-US/docs/Web/HTTP/Feature_Policy/Using_Feature_Policy)
diff --git a/files/en-us/web/http/headers/feature-policy/midi/index.md b/files/en-us/web/http/headers/feature-policy/midi/index.md
index 605e2e10cffadfa..dcd1ab225abcfe8 100644
--- a/files/en-us/web/http/headers/feature-policy/midi/index.md
+++ b/files/en-us/web/http/headers/feature-policy/midi/index.md
@@ -11,35 +11,31 @@ tags:
   - Experimental
 browser-compat: http.headers.Feature-Policy.midi
 ---
-<p>{{HTTPSidebar}}{{SeeCompatTable}}</p>
+{{HTTPSidebar}}{{SeeCompatTable}}
 
-<p>The HTTP {{HTTPHeader("Feature-Policy")}} header <code>midi</code> directive controls whether the current document is allowed to use the <a href="/en-US/docs/Web/API/Web_MIDI_API">Web MIDI API</a>. When this policy is enabled, the {{jsxref("Promise")}} returned by {{domxref("Navigator.requestMIDIAccess()")}} will reject with a <code>DOMException</code>.</p>
+The HTTP {{HTTPHeader("Feature-Policy")}} header `midi` directive controls whether the current document is allowed to use the [Web MIDI API](/en-US/docs/Web/API/Web_MIDI_API). When this policy is enabled, the {{jsxref("Promise")}} returned by {{domxref("Navigator.requestMIDIAccess()")}} will reject with a `DOMException`.
 
-<h2 id="Syntax">Syntax</h2>
+## Syntax
 
-<pre>Feature-Policy: midi &lt;allowlist&gt;;</pre>
+    Feature-Policy: midi <allowlist>;
 
-<dl>
-  <dt>&lt;allowlist&gt;</dt>
-  <dd>A list of origins for which the feature is allowed. See <a href="/en-US/docs/Web/HTTP/Headers/Feature-Policy#syntax"><code>Feature-Policy</code></a>.</dd>
-</dl>
+- \<allowlist>
+  - : A list of origins for which the feature is allowed. See [`Feature-Policy`](/en-US/docs/Web/HTTP/Headers/Feature-Policy#syntax).
 
-<h2 id="Default_policy">Default policy</h2>
+## Default policy
 
-<p>The allow list is <code>'self'</code>.</p>
+The allow list is `'self'`.
 
-<h2 id="Specifications">Specifications</h2>
+## Specifications
 
-<p>{{Specifications}}</p>
+{{Specifications}}
 
-<h2 id="Browser_compatibility">Browser compatibility</h2>
+## Browser compatibility
 
-<p>{{Compat}}</p>
+{{Compat}}
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
- <li>{{HTTPHeader("Feature-Policy")}} header</li>
- <li><a href="/en-US/docs/Web/HTTP/Feature_Policy">Feature Policy</a></li>
- <li><a href="/en-US/docs/Web/HTTP/Feature_Policy/Using_Feature_Policy">Using Feature Policy</a></li>
-</ul>
+- {{HTTPHeader("Feature-Policy")}} header
+- [Feature Policy](/en-US/docs/Web/HTTP/Feature_Policy)
+- [Using Feature Policy](/en-US/docs/Web/HTTP/Feature_Policy/Using_Feature_Policy)
diff --git a/files/en-us/web/http/headers/feature-policy/oversized-images/index.md b/files/en-us/web/http/headers/feature-policy/oversized-images/index.md
index 313104cc93bec2e..d79cf9e5142e5c0 100644
--- a/files/en-us/web/http/headers/feature-policy/oversized-images/index.md
+++ b/files/en-us/web/http/headers/feature-policy/oversized-images/index.md
@@ -10,31 +10,27 @@ tags:
   - Non-standard
 browser-compat: http.headers.Feature-Policy.oversized-images
 ---
-<p>{{HTTPSidebar}} {{SeeCompatTable}}{{Non-standard_header}}</p>
+{{HTTPSidebar}} {{SeeCompatTable}}{{Non-standard_header}}
 
-<p>The HTTP {{HTTPHeader("Feature-Policy")}} header <code>oversized-images</code> directive controls whether the current document is allowed to download and display large images.</p>
+The HTTP {{HTTPHeader("Feature-Policy")}} header `oversized-images` directive controls whether the current document is allowed to download and display large images.
 
-<h2 id="Syntax">Syntax</h2>
+## Syntax
 
-<pre>Feature-Policy: oversized-images &lt;allowlist&gt;;</pre>
+    Feature-Policy: oversized-images <allowlist>;
 
-<dl>
-  <dt>&lt;allowlist&gt;</dt>
-  <dd>A list of origins for which the feature is allowed. See <a href="/en-US/docs/Web/HTTP/Headers/Feature-Policy#syntax"><code>Feature-Policy</code></a>.</dd>
-</dl>
+- \<allowlist>
+  - : A list of origins for which the feature is allowed. See [`Feature-Policy`](/en-US/docs/Web/HTTP/Headers/Feature-Policy#syntax).
 
-<h2 id="Default_value">Default value</h2>
+## Default value
 
-<p>The default value is <code>'*'</code>.</p>
+The default value is `'*'`.
 
-<h2 id="Browser_compatibility">Browser compatibility</h2>
+## Browser compatibility
 
-<p>{{Compat}}</p>
+{{Compat}}
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
- <li>{{HTTPHeader("Feature-Policy")}} header</li>
- <li><a href="/en-US/docs/Web/HTTP/Feature_Policy">Feature Policy</a></li>
- <li><a href="/en-US/docs/Web/HTTP/Feature_Policy/Using_Feature_Policy">Using Feature Policy</a></li>
-</ul>
+- {{HTTPHeader("Feature-Policy")}} header
+- [Feature Policy](/en-US/docs/Web/HTTP/Feature_Policy)
+- [Using Feature Policy](/en-US/docs/Web/HTTP/Feature_Policy/Using_Feature_Policy)
diff --git a/files/en-us/web/http/headers/feature-policy/payment/index.md b/files/en-us/web/http/headers/feature-policy/payment/index.md
index 3870b9f98a4250f..b89ce3d29a3c869 100644
--- a/files/en-us/web/http/headers/feature-policy/payment/index.md
+++ b/files/en-us/web/http/headers/feature-policy/payment/index.md
@@ -12,55 +12,34 @@ tags:
   - Experimental
 browser-compat: http.headers.Feature-Policy.payment
 ---
-<div>{{HTTPSidebar}} {{SeeCompatTable}}</div>
+{{HTTPSidebar}} {{SeeCompatTable}}
 
-<p>The HTTP {{HTTPHeader("Feature-Policy")}} header field's <code>payment</code> directive controls whether the current document is allowed to use the <a href="/en-US/docs/Web/API/Payment_Request_API">Payment Request API</a>. When this policy is disabled, the {{DOMxRef("PaymentRequest()")}} constructor will throw a {{exception("SyntaxError")}}.</p>
+The HTTP {{HTTPHeader("Feature-Policy")}} header field's `payment` directive controls whether the current document is allowed to use the [Payment Request API](/en-US/docs/Web/API/Payment_Request_API). When this policy is disabled, the {{DOMxRef("PaymentRequest()")}} constructor will throw a {{exception("SyntaxError")}}.
 
-<h2 id="Syntax">Syntax</h2>
+## Syntax
 
-<pre>Feature-Policy: payment &lt;allowlist&gt;;</pre>
+    Feature-Policy: payment <allowlist>;
 
-<dl>
-  <dt>&lt;allowlist&gt;</dt>
-  <dd>A list of origins for which the feature is allowed. See <a href="/en-US/docs/Web/HTTP/Headers/Feature-Policy#syntax"><code>Feature-Policy</code></a>.</dd>
-</dl>
+- \<allowlist>
+  - : A list of origins for which the feature is allowed. See [`Feature-Policy`](/en-US/docs/Web/HTTP/Headers/Feature-Policy#syntax).
 
-<h2 id="Default_policy">Default policy</h2>
+## Default policy
 
-<p>The <code>payment</code> feature's default allowlist value is <code>'self'</code>.</p>
+The `payment` feature's default allowlist value is `'self'`.
 
-<h2 id="Specifications">Specifications</h2>
+## Specifications
 
-<table class="standard-table">
- <thead>
-  <tr>
-   <th scope="col">Specification</th>
-   <th scope="col">Status</th>
-   <th scope="col">Comment</th>
-  </tr>
- </thead>
- <tbody>
-  <tr>
-   <td>{{SpecName('Payment')}}</td>
-   <td>{{Spec2('Payment')}}</td>
-   <td>See <a href="https://w3c.github.io/payment-request/#feature-policy">Section 16. Feature Policy integration</a>.</td>
-  </tr>
-  <tr>
-   <td>{{SpecName('Feature Policy')}}</td>
-   <td>{{Spec2('Feature Policy')}}</td>
-   <td>Initial definition.</td>
-  </tr>
- </tbody>
-</table>
+| Specification                            | Status                               | Comment                                                                                              |
+| ---------------------------------------- | ------------------------------------ | ---------------------------------------------------------------------------------------------------- |
+| {{SpecName('Payment')}}         | {{Spec2('Payment')}}         | See [Section 16. Feature Policy integration](https://w3c.github.io/payment-request/#feature-policy). |
+| {{SpecName('Feature Policy')}} | {{Spec2('Feature Policy')}} | Initial definition.                                                                                  |
 
-<h2 id="Browser_compatibility">Browser compatibility</h2>
+## Browser compatibility
 
-<p>{{Compat}}</p>
+{{Compat}}
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
- <li>{{HTTPHeader("Feature-Policy")}} header field</li>
- <li><a href="/en-US/docs/Web/HTTP/Feature_Policy">Feature Policy</a></li>
- <li><a href="/en-US/docs/Web/HTTP/Feature_Policy/Using_Feature_Policy">Using Feature Policy</a></li>
-</ul>
+- {{HTTPHeader("Feature-Policy")}} header field
+- [Feature Policy](/en-US/docs/Web/HTTP/Feature_Policy)
+- [Using Feature Policy](/en-US/docs/Web/HTTP/Feature_Policy/Using_Feature_Policy)
diff --git a/files/en-us/web/http/headers/feature-policy/picture-in-picture/index.md b/files/en-us/web/http/headers/feature-policy/picture-in-picture/index.md
index 54e62d4cae4876d..7d271064d683da4 100644
--- a/files/en-us/web/http/headers/feature-policy/picture-in-picture/index.md
+++ b/files/en-us/web/http/headers/feature-policy/picture-in-picture/index.md
@@ -10,50 +10,33 @@ tags:
   - Experimental
 browser-compat: http.headers.Feature-Policy.picture-in-picture
 ---
-<p>{{HTTPSidebar}} {{SeeCompatTable}}</p>
+{{HTTPSidebar}} {{SeeCompatTable}}
 
-<p>The HTTP {{HTTPHeader("Feature-Policy")}} header <code>picture-in-picture</code> directive controls whether the current document is allowed to play a video in a Picture-in-Picture mode via the corresponding API.</p>
+The HTTP {{HTTPHeader("Feature-Policy")}} header `picture-in-picture` directive controls whether the current document is allowed to play a video in a Picture-in-Picture mode via the corresponding API.
 
-<h2 id="Syntax">Syntax</h2>
+## Syntax
 
-<pre>Feature-Policy: picture-in-picture &lt;allowlist&gt;;</pre>
+    Feature-Policy: picture-in-picture <allowlist>;
 
-<dl>
-  <dt>&lt;allowlist&gt;</dt>
-  <dd>A list of origins for which the feature is allowed. See <a href="/en-US/docs/Web/HTTP/Headers/Feature-Policy#syntax"><code>Feature-Policy</code></a>.</dd>
-</dl>
+- \<allowlist>
+  - : A list of origins for which the feature is allowed. See [`Feature-Policy`](/en-US/docs/Web/HTTP/Headers/Feature-Policy#syntax).
 
-<h2 id="Default_policy">Default policy</h2>
+## Default policy
 
-<p>As of June 2019, the <a href="https://wicg.github.io/picture-in-picture/#feature-policy">spec draft</a> and <a href="https://bugs.chromium.org/p/chromium/issues/detail?id=806249#c17">Google Chrome</a> set default allow list to <code>*</code>.</p>
+As of June 2019, the [spec draft](https://wicg.github.io/picture-in-picture/#feature-policy) and [Google Chrome](https://bugs.chromium.org/p/chromium/issues/detail?id=806249#c17) set default allow list to `*`.
 
-<h2 id="Specifications">Specifications</h2>
+## Specifications
 
-<table class="standard-table">
- <thead>
-  <tr>
-   <th scope="col">Specification</th>
-   <th scope="col">Status</th>
-   <th scope="col">Comment</th>
-  </tr>
- </thead>
- <tbody>
-  <tr>
-   <td>{{SpecName('Feature Policy')}}</td>
-   <td>{{Spec2('Feature Policy')}}</td>
-   <td>Initial definition.</td>
-  </tr>
- </tbody>
-</table>
+| Specification                            | Status                               | Comment             |
+| ---------------------------------------- | ------------------------------------ | ------------------- |
+| {{SpecName('Feature Policy')}} | {{Spec2('Feature Policy')}} | Initial definition. |
 
-<h2 id="Browser_compatibility">Browser compatibility</h2>
+## Browser compatibility
 
-<p>{{Compat}}</p>
+{{Compat}}
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
- <li>{{HTTPHeader("Feature-Policy")}} header</li>
- <li><a href="/en-US/docs/Web/HTTP/Feature_Policy">Feature Policy</a></li>
- <li><a href="/en-US/docs/Web/HTTP/Feature_Policy/Using_Feature_Policy">Using Feature Policy</a></li>
-</ul>
+- {{HTTPHeader("Feature-Policy")}} header
+- [Feature Policy](/en-US/docs/Web/HTTP/Feature_Policy)
+- [Using Feature Policy](/en-US/docs/Web/HTTP/Feature_Policy/Using_Feature_Policy)
diff --git a/files/en-us/web/http/headers/feature-policy/publickey-credentials-get/index.md b/files/en-us/web/http/headers/feature-policy/publickey-credentials-get/index.md
index c084fb09860fa65..fc94b180e55feeb 100644
--- a/files/en-us/web/http/headers/feature-policy/publickey-credentials-get/index.md
+++ b/files/en-us/web/http/headers/feature-policy/publickey-credentials-get/index.md
@@ -10,39 +10,35 @@ tags:
   - Experimental
 browser-compat: http.headers.Feature-Policy.publickey-credentials-get
 ---
-<div>{{HTTPSidebar}} {{SeeCompatTable}}</div>
+{{HTTPSidebar}} {{SeeCompatTable}}
 
-<p>The HTTP {{HTTPHeader("Feature-Policy")}} header <code>publickey-credentials-get</code> directive controls whether the current document is allowed to access the <a href="/en-US/docs/Web/API/Web_Authentication_API">Web Authentication API</a> to retrieve public-key credentials; i.e, via {{DOMxRef("CredentialsContainer.get", "navigator.credentials.get({publicKey: ..., ...})")}}.</p>
+The HTTP {{HTTPHeader("Feature-Policy")}} header `publickey-credentials-get` directive controls whether the current document is allowed to access the [Web Authentication API](/en-US/docs/Web/API/Web_Authentication_API) to retrieve public-key credentials; i.e, via {{DOMxRef("CredentialsContainer.get", "navigator.credentials.get({publicKey: ..., ...})")}}.
 
-<p>When this policy is enabled, any attempt to query public key credentials will result in an error.</p>
+When this policy is enabled, any attempt to query public key credentials will result in an error.
 
-<h2 id="Syntax">Syntax</h2>
+## Syntax
 
-<pre>Feature-Policy: publickey-credentials-get &lt;allowlist&gt;;</pre>
+    Feature-Policy: publickey-credentials-get <allowlist>;
 
-<dl>
-  <dt>&lt;allowlist&gt;</dt>
-  <dd>A list of origins for which the feature is allowed. See <a href="/en-US/docs/Web/HTTP/Headers/Feature-Policy#syntax"><code>Feature-Policy</code></a>.</dd>
-</dl>
+- \<allowlist>
+  - : A list of origins for which the feature is allowed. See [`Feature-Policy`](/en-US/docs/Web/HTTP/Headers/Feature-Policy#syntax).
 
-<h2 id="Default_policy">Default policy</h2>
+## Default policy
 
-<p>The default allowlist is <code>'self'</code>.</p>
+The default allowlist is `'self'`.
 
-<h2 id="Specifications">Specifications</h2>
+## Specifications
 
-<p>{{Specifications}}</p>
+{{Specifications}}
 
-<h2 id="Browser_compatibility">Browser compatibility</h2>
+## Browser compatibility
 
-<p>{{Compat}}</p>
+{{Compat}}
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
- <li>{{HTTPHeader("Feature-Policy")}} header</li>
- <li><a href="/en-US/docs/Web/HTTP/Feature_Policy">Feature Policy</a></li>
- <li><a href="/en-US/docs/Web/HTTP/Feature_Policy/Using_Feature_Policy">Using Feature Policy</a></li>
- <li><a href="/en-US/docs/Web/API/Web_Authentication_API">Web Authentication API</a></li>
- <li>{{DOMxRef("PublicKeyCredential")}} interface</li>
-</ul>
+- {{HTTPHeader("Feature-Policy")}} header
+- [Feature Policy](/en-US/docs/Web/HTTP/Feature_Policy)
+- [Using Feature Policy](/en-US/docs/Web/HTTP/Feature_Policy/Using_Feature_Policy)
+- [Web Authentication API](/en-US/docs/Web/API/Web_Authentication_API)
+- {{DOMxRef("PublicKeyCredential")}} interface
diff --git a/files/en-us/web/http/headers/feature-policy/screen-wake-lock/index.md b/files/en-us/web/http/headers/feature-policy/screen-wake-lock/index.md
index 8c1394d74700b56..cad64577b71c29f 100644
--- a/files/en-us/web/http/headers/feature-policy/screen-wake-lock/index.md
+++ b/files/en-us/web/http/headers/feature-policy/screen-wake-lock/index.md
@@ -11,61 +11,38 @@ tags:
   - Experimental
 browser-compat: http.headers.Feature-Policy.screen-wake-lock
 ---
-<p>{{HTTPSidebar}} {{SeeCompatTable}}</p>
+{{HTTPSidebar}} {{SeeCompatTable}}
 
-<p>The HTTP {{HTTPHeader("Feature-Policy")}} header <strong><code>screen-wake-lock</code></strong> directive controls whether the current document is allowed to use <a href="/en-US/docs/Web/API/Screen_Wake_Lock_API">Screen Wake Lock API</a> to indicate that device should not dim or turn off the screen.</p>
+The HTTP {{HTTPHeader("Feature-Policy")}} header **`screen-wake-lock`** directive controls whether the current document is allowed to use [Screen Wake Lock API](/en-US/docs/Web/API/Screen_Wake_Lock_API) to indicate that device should not dim or turn off the screen.
 
-<div class="notecard note">
-  <p><strong>Note:</strong> In earlier specification drafts this directive was called <code>wake-lock</code>")}}.</p>
-</div>
+> **Note:** In earlier specification drafts this directive was called `wake-lock`")}}.
 
-<h2 id="Syntax">Syntax</h2>
+## Syntax
 
-<pre>Feature-Policy: screen-wake-lock &lt;allowlist&gt;;</pre>
+    Feature-Policy: screen-wake-lock <allowlist>;
 
-<dl>
-  <dt>&lt;allowlist&gt;</dt>
-  <dd>A list of origins for which the feature is allowed. See <a href="/en-US/docs/Web/HTTP/Headers/Feature-Policy#syntax"><code>Feature-Policy</code></a>.</dd>
-</dl>
+- \<allowlist>
+  - : A list of origins for which the feature is allowed. See [`Feature-Policy`](/en-US/docs/Web/HTTP/Headers/Feature-Policy#syntax).
 
-<h2 id="Default_policy">Default policy</h2>
+## Default policy
 
-<p>Default allow list for <code>screen-wake-lock</code> is <code>'self'</code>.</p>
+Default allow list for `screen-wake-lock` is `'self'`.
 
-<h2 id="Specifications">Specifications</h2>
+## Specifications
 
-<table class="standard-table">
- <thead>
-  <tr>
-   <th scope="col">Specification</th>
-   <th scope="col">Status</th>
-   <th scope="col">Comment</th>
-  </tr>
- </thead>
- <tbody>
-  <tr>
-   <td>{{SpecName('Feature Policy')}}</td>
-   <td>{{Spec2('Feature Policy')}}</td>
-   <td>Initial definition.</td>
-  </tr>
-  <tr>
-   <td><a href="https://w3c.github.io/screen-wake-lock/#the-screen-wake-lock-powerful-feature">Screen Wake Lock API</a></td>
-   <td>Editor's Draft</td>
-   <td>Initial definition of <code>screen-wake-lock</code> feature directive.</td>
-  </tr>
- </tbody>
-</table>
+| Specification                                                                                         | Status                               | Comment                                                     |
+| ----------------------------------------------------------------------------------------------------- | ------------------------------------ | ----------------------------------------------------------- |
+| {{SpecName('Feature Policy')}}                                                              | {{Spec2('Feature Policy')}} | Initial definition.                                         |
+| [Screen Wake Lock API](https://w3c.github.io/screen-wake-lock/#the-screen-wake-lock-powerful-feature) | Editor's Draft                       | Initial definition of `screen-wake-lock` feature directive. |
 
-<h2 id="Browser_compatibility">Browser compatibility</h2>
+## Browser compatibility
 
-<p>{{Compat}}</p>
+{{Compat}}
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
- <li><a href="/en-US/docs/Web/API/Screen_Wake_Lock_API">Screen Wake Lock API</a></li>
- <li>{{HTTPHeader('Feature-Policy')}} header</li>
- <li><a href="/en-US/docs/Web/HTTP/Feature_Policy">Feature Policy</a></li>
- <li><a href="/en-US/docs/Web/HTTP/Feature_Policy/Using_Feature_Policy">Using Feature Policy</a></li>
- <li><a href="https://www.w3.org/TR/wake-lock/#wake-locks">Default value of the allow list</a></li>
-</ul>
+- [Screen Wake Lock API](/en-US/docs/Web/API/Screen_Wake_Lock_API)
+- {{HTTPHeader('Feature-Policy')}} header
+- [Feature Policy](/en-US/docs/Web/HTTP/Feature_Policy)
+- [Using Feature Policy](/en-US/docs/Web/HTTP/Feature_Policy/Using_Feature_Policy)
+- [Default value of the allow list](https://www.w3.org/TR/wake-lock/#wake-locks)
diff --git a/files/en-us/web/http/headers/feature-policy/sync-xhr/index.md b/files/en-us/web/http/headers/feature-policy/sync-xhr/index.md
index 9bac4b62427a063..f7a57f80127b6e1 100644
--- a/files/en-us/web/http/headers/feature-policy/sync-xhr/index.md
+++ b/files/en-us/web/http/headers/feature-policy/sync-xhr/index.md
@@ -11,30 +11,26 @@ tags:
   - Experimental
 browser-compat: http.headers.Feature-Policy.sync-xhr
 ---
-<p>{{HTTPSidebar}} {{SeeCompatTable}}</p>
+{{HTTPSidebar}} {{SeeCompatTable}}
 
-<p>The HTTP {{HTTPHeader("Feature-Policy")}} header <code>sync-xhr</code> directive controls whether the current document is allowed to make synchronous {{domxref("XMLHttpRequest")}} requests.</p>
+The HTTP {{HTTPHeader("Feature-Policy")}} header `sync-xhr` directive controls whether the current document is allowed to make synchronous {{domxref("XMLHttpRequest")}} requests.
 
-<h2 id="Syntax">Syntax</h2>
+## Syntax
 
-<pre>Feature-Policy: sync-xhr &lt;allowlist&gt;;</pre>
+    Feature-Policy: sync-xhr <allowlist>;
 
-<dl>
-  <dt>&lt;allowlist&gt;</dt>
-  <dd>A list of origins for which the feature is allowed. See <a href="/en-US/docs/Web/HTTP/Headers/Feature-Policy#syntax"><code>Feature-Policy</code></a>.</dd>
-</dl>
+- \<allowlist>
+  - : A list of origins for which the feature is allowed. See [`Feature-Policy`](/en-US/docs/Web/HTTP/Headers/Feature-Policy#syntax).
 
-<h2 id="Default_policy">Default policy</h2>
+## Default policy
 
-<p>By default the policy is set to <code>*</code>, which means synchronous requests are allowed in all frames.</p>
+By default the policy is set to `*`, which means synchronous requests are allowed in all frames.
 
-<h2 id="Browser_compatibility">Browser compatibility</h2>
+## Browser compatibility
 
-<p>{{Compat}}</p>
+{{Compat}}
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
- <li><a href="/en-US/docs/Web/HTTP/Feature_Policy">Feature Policy</a></li>
- <li><a href="/en-US/docs/Web/HTTP/Feature_Policy/Using_Feature_Policy">Using Feature Policy</a></li>
-</ul>
+- [Feature Policy](/en-US/docs/Web/HTTP/Feature_Policy)
+- [Using Feature Policy](/en-US/docs/Web/HTTP/Feature_Policy/Using_Feature_Policy)
diff --git a/files/en-us/web/http/headers/feature-policy/unoptimized-images/index.md b/files/en-us/web/http/headers/feature-policy/unoptimized-images/index.md
index e78fd678ba5d938..b42cfccf6e229b4 100644
--- a/files/en-us/web/http/headers/feature-policy/unoptimized-images/index.md
+++ b/files/en-us/web/http/headers/feature-policy/unoptimized-images/index.md
@@ -11,31 +11,27 @@ tags:
   - Non-standard
 browser-compat: http.headers.Feature-Policy.unoptimized-images
 ---
-<p>{{HTTPSidebar}}{{SeeCompatTable}}{{Non-standard_header}}</p>
+{{HTTPSidebar}}{{SeeCompatTable}}{{Non-standard_header}}
 
-<p>The HTTP {{HTTPHeader("Feature-Policy")}} header <code>unoptimized-images</code> directive controls whether the current document is allowed to download and display unoptimized images.</p>
+The HTTP {{HTTPHeader("Feature-Policy")}} header `unoptimized-images` directive controls whether the current document is allowed to download and display unoptimized images.
 
-<h2 id="Syntax">Syntax</h2>
+## Syntax
 
-<pre>Feature-Policy: unoptimized-images &lt;allowlist&gt;;</pre>
+    Feature-Policy: unoptimized-images <allowlist>;
 
-<dl>
-  <dt>&lt;allowlist&gt;</dt>
-  <dd>A list of origins for which the feature is allowed. See <a href="/en-US/docs/Web/HTTP/Headers/Feature-Policy#syntax"><code>Feature-Policy</code></a>.</dd>
-</dl>
+- \<allowlist>
+  - : A list of origins for which the feature is allowed. See [`Feature-Policy`](/en-US/docs/Web/HTTP/Headers/Feature-Policy#syntax).
 
-<h2 id="Default_policy">Default policy</h2>
+## Default policy
 
-<p>Default allow list for <code>unoptimized-images</code> is <code>'self'</code>.</p>
+Default allow list for `unoptimized-images` is `'self'`.
 
-<h2 id="Browser_compatibility">Browser compatibility</h2>
+## Browser compatibility
 
-<p>{{Compat}}</p>
+{{Compat}}
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
- <li>{{HTTPHeader("Feature-Policy")}} header</li>
- <li><a href="/en-US/docs/Web/HTTP/Feature_Policy">Feature Policy</a></li>
- <li><a href="/en-US/docs/Web/HTTP/Feature_Policy/Using_Feature_Policy">Using Feature Policy</a></li>
-</ul>
+- {{HTTPHeader("Feature-Policy")}} header
+- [Feature Policy](/en-US/docs/Web/HTTP/Feature_Policy)
+- [Using Feature Policy](/en-US/docs/Web/HTTP/Feature_Policy/Using_Feature_Policy)
diff --git a/files/en-us/web/http/headers/feature-policy/unsized-media/index.md b/files/en-us/web/http/headers/feature-policy/unsized-media/index.md
index 77413131c491964..70767872d4a25cb 100644
--- a/files/en-us/web/http/headers/feature-policy/unsized-media/index.md
+++ b/files/en-us/web/http/headers/feature-policy/unsized-media/index.md
@@ -10,34 +10,30 @@ tags:
   - Non-standard
 browser-compat: http.headers.Feature-Policy.unsized-media
 ---
-<p>{{HTTPSidebar}} {{SeeCompatTable}}{{Non-standard_header}}</p>
+{{HTTPSidebar}} {{SeeCompatTable}}{{Non-standard_header}}
 
-<p>The HTTP {{HTTPHeader('Feature-Policy')}} header <code>unsized-media</code> directive controls whether the current document is allowed to change the size of media elements after the initial layout is complete.</p>
+The HTTP {{HTTPHeader('Feature-Policy')}} header `unsized-media` directive controls whether the current document is allowed to change the size of media elements after the initial layout is complete.
 
-<p>This restriction solves "layout instability" problem caused by providing default dimensions for images whose size is not specified in advance so that image doesn't change size after loading.</p>
+This restriction solves "layout instability" problem caused by providing default dimensions for images whose size is not specified in advance so that image doesn't change size after loading.
 
-<h2 id="Syntax">Syntax</h2>
+## Syntax
 
-<pre>Feature-Policy: unsized-media &lt;allowlist&gt;;</pre>
+    Feature-Policy: unsized-media <allowlist>;
 
-<dl>
-  <dt>&lt;allowlist&gt;</dt>
-  <dd>A list of origins for which the feature is allowed. See <a href="/en-US/docs/Web/HTTP/Headers/Feature-Policy#syntax"><code>Feature-Policy</code></a>.</dd>
-</dl>
+- \<allowlist>
+  - : A list of origins for which the feature is allowed. See [`Feature-Policy`](/en-US/docs/Web/HTTP/Headers/Feature-Policy#syntax).
 
-<h2 id="Default_value">Default value</h2>
+## Default value
 
-<p>The default value for unsized-media is <code>'*'</code>, that is unsized media elements are allowed for all origins by default. The page will re-flow every time an image with unknown dimensions is loaded.</p>
+The default value for unsized-media is `'*'`, that is unsized media elements are allowed for all origins by default. The page will re-flow every time an image with unknown dimensions is loaded.
 
-<h2 id="Browser_compatibility">Browser compatibility</h2>
+## Browser compatibility
 
-<p>{{Compat}}</p>
+{{Compat}}
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
- <li>{{HTTPHeader('Feature-Policy')}} header</li>
- <li><a href="/en-US/docs/Web/HTTP/Feature_Policy">Feature Policy</a></li>
- <li><a href="/en-US/docs/Web/HTTP/Feature_Policy/Using_Feature_Policy">Using Feature Policy</a></li>
- <li><a href="https://github.com/w3c/webappsec-feature-policy/blob/master/policies/unsized-media.md">Proposal</a></li>
-</ul>
+- {{HTTPHeader('Feature-Policy')}} header
+- [Feature Policy](/en-US/docs/Web/HTTP/Feature_Policy)
+- [Using Feature Policy](/en-US/docs/Web/HTTP/Feature_Policy/Using_Feature_Policy)
+- [Proposal](https://github.com/w3c/webappsec-feature-policy/blob/master/policies/unsized-media.md)
diff --git a/files/en-us/web/http/headers/feature-policy/usb/index.md b/files/en-us/web/http/headers/feature-policy/usb/index.md
index 8134e6d62b898d2..9c2db489f6e52c7 100644
--- a/files/en-us/web/http/headers/feature-policy/usb/index.md
+++ b/files/en-us/web/http/headers/feature-policy/usb/index.md
@@ -11,35 +11,31 @@ tags:
   - Experimental
 browser-compat: http.headers.Feature-Policy.usb
 ---
-<p>{{HTTPSidebar}} {{SeeCompatTable}}</p>
+{{HTTPSidebar}} {{SeeCompatTable}}
 
-<p>The HTTP {{HTTPHeader("Feature-Policy")}} header <code>usb</code> directive controls whether the current document is allowed to use the WebUSB API.</p>
+The HTTP {{HTTPHeader("Feature-Policy")}} header `usb` directive controls whether the current document is allowed to use the WebUSB API.
 
-<h2 id="Syntax">Syntax</h2>
+## Syntax
 
-<pre>Feature-Policy: usb &lt;allowlist&gt;;</pre>
+    Feature-Policy: usb <allowlist>;
 
-<dl>
-  <dt>&lt;allowlist&gt;</dt>
-  <dd>A list of origins for which the feature is allowed. See <a href="/en-US/docs/Web/HTTP/Headers/Feature-Policy#syntax"><code>Feature-Policy</code></a>.</dd>
-</dl>
+- \<allowlist>
+  - : A list of origins for which the feature is allowed. See [`Feature-Policy`](/en-US/docs/Web/HTTP/Headers/Feature-Policy#syntax).
 
-<h2 id="Default_policy">Default policy</h2>
+## Default policy
 
-<p>The default value is <code>'self'</code>.</p>
+The default value is `'self'`.
 
-<h2 id="Specifications">Specifications</h2>
+## Specifications
 
 {{Specifications}}
 
-<h2 id="Browser_compatibility">Browser compatibility</h2>
+## Browser compatibility
 
-<p>{{Compat}}</p>
+{{Compat}}
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
- <li>{{HTTPHeader('Feature-Policy')}} header</li>
- <li><a href="/en-US/docs/Web/HTTP/Feature_Policy">Feature Policy</a></li>
- <li><a href="/en-US/docs/Web/HTTP/Feature_Policy/Using_Feature_Policy">Using Feature Policy</a></li>
-</ul>
+- {{HTTPHeader('Feature-Policy')}} header
+- [Feature Policy](/en-US/docs/Web/HTTP/Feature_Policy)
+- [Using Feature Policy](/en-US/docs/Web/HTTP/Feature_Policy/Using_Feature_Policy)
diff --git a/files/en-us/web/http/headers/feature-policy/vibrate/index.md b/files/en-us/web/http/headers/feature-policy/vibrate/index.md
index 8c2200ca7f3bff9..35232f3e54e9f09 100644
--- a/files/en-us/web/http/headers/feature-policy/vibrate/index.md
+++ b/files/en-us/web/http/headers/feature-policy/vibrate/index.md
@@ -12,52 +12,35 @@ tags:
   - Non-standard
 browser-compat: http.headers.Feature-Policy.vibrate
 ---
-<p>{{HTTPSidebar}} {{Deprecated_Header}}</p>
+{{HTTPSidebar}} {{Deprecated_Header}}
 
-<p>The HTTP {{HTTPHeader("Feature-Policy")}} header <code>vibrate</code> {{deprecated_inline}} directive controls whether the current document is allowed to trigger device vibrations via {{DOMxRef("Navigator.vibrate","Navigator.vibrate()")}} method of <a href="/en-US/docs/Web/API/Vibration_API">Vibration API</a>.</p>
+The HTTP {{HTTPHeader("Feature-Policy")}} header `vibrate` {{deprecated_inline}} directive controls whether the current document is allowed to trigger device vibrations via {{DOMxRef("Navigator.vibrate","Navigator.vibrate()")}} method of [Vibration API](/en-US/docs/Web/API/Vibration_API).
 
-<h2 id="Syntax">Syntax</h2>
+## Syntax
 
-<pre>Feature-Policy: vibrate &lt;allowlist&gt;;</pre>
+    Feature-Policy: vibrate <allowlist>;
 
-<dl>
-  <dt>&lt;allowlist&gt;</dt>
-  <dd>A list of origins for which the feature is allowed. See <a href="/en-US/docs/Web/HTTP/Headers/Feature-Policy#syntax"><code>Feature-Policy</code></a>.</dd>
-</dl>
+- \<allowlist>
+  - : A list of origins for which the feature is allowed. See [`Feature-Policy`](/en-US/docs/Web/HTTP/Headers/Feature-Policy#syntax).
 
-<h2 id="Default_policy">Default policy</h2>
+## Default policy
 
-<p>Default allow list for <code>vibrate</code> is <code>'self'</code>.</p>
+Default allow list for `vibrate` is `'self'`.
 
-<h2 id="Specifications">Specifications</h2>
+## Specifications
 
-<table class="standard-table">
- <thead>
-  <tr>
-   <th scope="col">Specification</th>
-   <th scope="col">Status</th>
-   <th scope="col">Comment</th>
-  </tr>
- </thead>
- <tbody>
-  <tr>
-   <td>{{SpecName('Feature Policy')}}</td>
-   <td>{{Spec2('Feature Policy')}}</td>
-   <td>Initial definition.</td>
-  </tr>
- </tbody>
-</table>
+| Specification                            | Status                               | Comment             |
+| ---------------------------------------- | ------------------------------------ | ------------------- |
+| {{SpecName('Feature Policy')}} | {{Spec2('Feature Policy')}} | Initial definition. |
 
-<h2 id="Browser_compatibility">Browser compatibility</h2>
+## Browser compatibility
 
-<p>{{Compat}}</p>
+{{Compat}}
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
- <li>{{HTTPHeader("Feature-Policy")}} header</li>
- <li><a href="/en-US/docs/Web/HTTP/Feature_Policy">Feature Policy</a></li>
- <li><a href="/en-US/docs/Web/HTTP/Feature_Policy/Using_Feature_Policy">Using Feature Policy</a></li>
- <li><a href="/en-US/docs/Web/API/Vibration_API">Vibration API</a></li>
- <li>{{DOMxRef("Navigator.vibrate","Navigator.vibrate()")}}</li>
-</ul>
+- {{HTTPHeader("Feature-Policy")}} header
+- [Feature Policy](/en-US/docs/Web/HTTP/Feature_Policy)
+- [Using Feature Policy](/en-US/docs/Web/HTTP/Feature_Policy/Using_Feature_Policy)
+- [Vibration API](/en-US/docs/Web/API/Vibration_API)
+- {{DOMxRef("Navigator.vibrate","Navigator.vibrate()")}}
diff --git a/files/en-us/web/http/headers/feature-policy/vr/index.md b/files/en-us/web/http/headers/feature-policy/vr/index.md
index b977fc87e084392..cf725450e783e8f 100644
--- a/files/en-us/web/http/headers/feature-policy/vr/index.md
+++ b/files/en-us/web/http/headers/feature-policy/vr/index.md
@@ -11,62 +11,39 @@ tags:
   - Experimental
 browser-compat: http.headers.Feature-Policy.vr
 ---
-<div>{{HTTPSidebar}} {{SeeCompatTable}}</div>
+{{HTTPSidebar}} {{SeeCompatTable}}
 
-<div class="notecard warning">
-  <p><strong>Warning:</strong> The <a href="/en-US/docs/Web/API/WebVR_API">WebVR API</a> has been replaced with the <a href="/en-US/docs/Web/API/WebXR_Device_API">WebXR Device API</a>
-  and is currently being removed from the web platform.
-  Use the feature identifier {{HTTPHeader("Feature-Policy/xr-spatial-tracking","xr-spatial-tracking")}} for WebXR Device API instead.</p>
-</div>
+> **Warning:** The [WebVR API](/en-US/docs/Web/API/WebVR_API) has been replaced with the [WebXR Device API](/en-US/docs/Web/API/WebXR_Device_API)
+> and is currently being removed from the web platform.
+> Use the feature identifier {{HTTPHeader("Feature-Policy/xr-spatial-tracking","xr-spatial-tracking")}} for WebXR Device API instead.
 
-<p>The HTTP {{HTTPHeader("Feature-Policy")}} header <code>vr</code> directive controls whether the current document is allowed to use the <a href="/en-US/docs/Web/API/WebVR_API">WebVR API</a>. When this policy is enabled, the {{JSxRef("Promise")}} returned by {{DOMxRef("Navigator.getVRDisplays","Navigator.getVRDisplays()")}} will reject with a {{DOMxRef("DOMException")}}.</p>
+The HTTP {{HTTPHeader("Feature-Policy")}} header `vr` directive controls whether the current document is allowed to use the [WebVR API](/en-US/docs/Web/API/WebVR_API). When this policy is enabled, the {{JSxRef("Promise")}} returned by {{DOMxRef("Navigator.getVRDisplays","Navigator.getVRDisplays()")}} will reject with a {{DOMxRef("DOMException")}}.
 
-<h2 id="Syntax">Syntax</h2>
+## Syntax
 
-<pre>Feature-Policy: vr &lt;allowlist&gt;;</pre>
+    Feature-Policy: vr <allowlist>;
 
-<dl>
-  <dt>&lt;allowlist&gt;</dt>
-  <dd>A list of origins for which the feature is allowed. See <a href="/en-US/docs/Web/HTTP/Headers/Feature-Policy#syntax"><code>Feature-Policy</code></a>.</dd>
-</dl>
+- \<allowlist>
+  - : A list of origins for which the feature is allowed. See [`Feature-Policy`](/en-US/docs/Web/HTTP/Headers/Feature-Policy#syntax).
 
-<h2 id="Default_policy">Default policy</h2>
+## Default policy
 
-<p>The default allowlist is <code>'self'</code>.</p>
+The default allowlist is `'self'`.
 
-<h2 id="Specifications">Specifications</h2>
+## Specifications
 
-<table class="standard-table">
- <thead>
-  <tr>
-   <th scope="col">Specification</th>
-   <th scope="col">Status</th>
-   <th scope="col">Comment</th>
-  </tr>
- </thead>
- <tbody>
-  <tr>
-   <td>{{SpecName("Feature Policy")}}</td>
-   <td>{{Spec2("Feature Policy")}}</td>
-   <td>Initial definition.</td>
-  </tr>
-  <tr>
-   <td>{{SpecName("WebVR 1.1")}}</td>
-   <td>{{Spec2("WebVR 1.1")}}</td>
-   <td></td>
-  </tr>
- </tbody>
-</table>
+| Specification                            | Status                               | Comment             |
+| ---------------------------------------- | ------------------------------------ | ------------------- |
+| {{SpecName("Feature Policy")}} | {{Spec2("Feature Policy")}} | Initial definition. |
+| {{SpecName("WebVR 1.1")}}         | {{Spec2("WebVR 1.1")}}         |                     |
 
-<h2 id="Browser_compatibility">Browser compatibility</h2>
+## Browser compatibility
 
-<p>{{Compat}}</p>
+{{Compat}}
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
- <li>{{HTTPHeader("Feature-Policy/xr-spatial-tracking","Feature-Policy: xr-spatial-tracking")}}</li>
- <li>{{HTTPHeader("Feature-Policy")}} header</li>
- <li><a href="/en-US/docs/Web/HTTP/Feature_Policy">Feature Policy</a></li>
- <li><a href="/en-US/docs/Web/HTTP/Feature_Policy/Using_Feature_Policy">Using Feature Policy</a></li>
-</ul>
+- {{HTTPHeader("Feature-Policy/xr-spatial-tracking","Feature-Policy: xr-spatial-tracking")}}
+- {{HTTPHeader("Feature-Policy")}} header
+- [Feature Policy](/en-US/docs/Web/HTTP/Feature_Policy)
+- [Using Feature Policy](/en-US/docs/Web/HTTP/Feature_Policy/Using_Feature_Policy)
diff --git a/files/en-us/web/http/headers/feature-policy/web-share/index.md b/files/en-us/web/http/headers/feature-policy/web-share/index.md
index 7c3185bac79d9d4..e740ebe77ede035 100644
--- a/files/en-us/web/http/headers/feature-policy/web-share/index.md
+++ b/files/en-us/web/http/headers/feature-policy/web-share/index.md
@@ -8,37 +8,33 @@ tags:
   - Experimental
 browser-compat: http.headers.Feature-Policy.web-share
 ---
-<p>{{HTTPSidebar}} {{SeeCompatTable}}</p>
+{{HTTPSidebar}} {{SeeCompatTable}}
 
-<p>The HTTP {{HTTPHeader('Feature-Policy')}} header <code>web-share</code> directive controls whether the current document is allowed to use the {{domxref("Navigator.share","Navigator.share()")}} method of the Web Share API to share text, links, images, and other content to arbitrary destinations of the user's choice.</p>
+The HTTP {{HTTPHeader('Feature-Policy')}} header `web-share` directive controls whether the current document is allowed to use the {{domxref("Navigator.share","Navigator.share()")}} method of the Web Share API to share text, links, images, and other content to arbitrary destinations of the user's choice.
 
-<h2 id="Syntax">Syntax</h2>
+## Syntax
 
-<pre>Feature-Policy: web-share &lt;allowlist&gt;;</pre>
+    Feature-Policy: web-share <allowlist>;
 
-<dl>
-  <dt>&lt;allowlist&gt;</dt>
-  <dd>A list of origins for which the feature is allowed. See <a href="/en-US/docs/Web/HTTP/Headers/Feature-Policy#syntax"><code>Feature-Policy</code></a>.</dd>
-</dl>
+- \<allowlist>
+  - : A list of origins for which the feature is allowed. See [`Feature-Policy`](/en-US/docs/Web/HTTP/Headers/Feature-Policy#syntax).
 
-<h2 id="Default_policy">Default policy</h2>
+## Default policy
 
-<p>The default value is <code>'self'</code>.</p>
+The default value is `'self'`.
 
-<h2 id="Specifications">Specifications</h2>
+## Specifications
 
-<p>{{Specifications}}</p>
+{{Specifications}}
 
-<h2 id="Browser_compatibility">Browser compatibility</h2>
+## Browser compatibility
 
-<p>{{Compat}}</p>
+{{Compat}}
 
-<p>Browser implementation is being discussed in <a href="https://github.com/w3c/web-share/issues/169">https://github.com/w3c/web-share/issues/169</a>.</p>
+Browser implementation is being discussed in <https://github.com/w3c/web-share/issues/169>.
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
- <li>{{HTTPHeader('Feature-Policy')}} header</li>
- <li><a href="/en-US/docs/Web/HTTP/Feature_Policy">Feature Policy</a></li>
- <li><a href="/en-US/docs/Web/HTTP/Feature_Policy/Using_Feature_Policy">Using Feature Policy</a></li>
-</ul>
+- {{HTTPHeader('Feature-Policy')}} header
+- [Feature Policy](/en-US/docs/Web/HTTP/Feature_Policy)
+- [Using Feature Policy](/en-US/docs/Web/HTTP/Feature_Policy/Using_Feature_Policy)
diff --git a/files/en-us/web/http/headers/feature-policy/xr-spatial-tracking/index.md b/files/en-us/web/http/headers/feature-policy/xr-spatial-tracking/index.md
index 5a6f8b24533c5af..ef8589865de5a47 100644
--- a/files/en-us/web/http/headers/feature-policy/xr-spatial-tracking/index.md
+++ b/files/en-us/web/http/headers/feature-policy/xr-spatial-tracking/index.md
@@ -11,37 +11,33 @@ tags:
   - Experimental
 browser-compat: http.headers.Feature-Policy.xr-spatial-tracking
 ---
-<div>{{HTTPSidebar}}{{Draft}}{{SeeCompatTable}}</div>
+{{HTTPSidebar}}{{Draft}}{{SeeCompatTable}}
 
-<p>The HTTP {{HTTPHeader("Feature-Policy")}} header <code>xr-spatial-tracking</code> directive controls whether the current document is allowed to use the <a href="/en-US/docs/Web/API/WebXR_Device_API">WebXR Device API</a>. This policy controls whether {{DOMxRef("XRSystem/requestSession","navigator.xr.requestSession()")}} can return {{DOMxRef("XRSession")}} that requires spatial tracking and whether user agent can indicate support for sessions supporting spatial tracking via {{DOMxRef("XRSystem/isSessionSupported","navigator.xr.isSessionSupported()")}} and {{Event("devicechange")}} event on {{DOMxRef("Navigator.xr","navigator.xr")}} object.</p>
+The HTTP {{HTTPHeader("Feature-Policy")}} header `xr-spatial-tracking` directive controls whether the current document is allowed to use the [WebXR Device API](/en-US/docs/Web/API/WebXR_Device_API). This policy controls whether {{DOMxRef("XRSystem/requestSession","navigator.xr.requestSession()")}} can return {{DOMxRef("XRSession")}} that requires spatial tracking and whether user agent can indicate support for sessions supporting spatial tracking via {{DOMxRef("XRSystem/isSessionSupported","navigator.xr.isSessionSupported()")}} and {{Event("devicechange")}} event on {{DOMxRef("Navigator.xr","navigator.xr")}} object.
 
-<h2 id="Syntax">Syntax</h2>
+## Syntax
 
-<pre>Feature-Policy: xr-spatial-tracking &lt;allowlist&gt;;</pre>
+    Feature-Policy: xr-spatial-tracking <allowlist>;
 
-<dl>
-  <dt>&lt;allowlist&gt;</dt>
-  <dd>A list of origins for which the feature is allowed. See <a href="/en-US/docs/Web/HTTP/Headers/Feature-Policy#syntax"><code>Feature-Policy</code></a>.</dd>
- </dl>
+- \<allowlist>
+  - : A list of origins for which the feature is allowed. See [`Feature-Policy`](/en-US/docs/Web/HTTP/Headers/Feature-Policy#syntax).
 
-<h2 id="Default_policy">Default policy</h2>
+## Default policy
 
-<p>The default allowlist is <code>'self'</code>.</p>
+The default allowlist is `'self'`.
 
-<h2 id="Specifications">Specifications</h2>
+## Specifications
 
-<p>{{Specifications}}</p>
+{{Specifications}}
 
-<h2 id="Browser_compatibility">Browser compatibility</h2>
+## Browser compatibility
 
-<p>{{Compat}}</p>
+{{Compat}}
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
- <li><a href="/en-US/docs/Web/API/WebXR_Device_API">WebXR Device API</a></li>
- <li>{{DOMxRef("XRSystem/requestSession","navigator.xr.requestSession()")}}, and {{DOMxRef("XRSystem/isSessionSupported","navigator.xr.isSessionSupported()")}} and {{Event("devicechange")}} event on {{DOMxRef("Navigator.xr","navigator.xr")}}</li>
- <li>{{HTTPHeader("Feature-Policy")}} header</li>
- <li><a href="/en-US/docs/Web/HTTP/Feature_Policy">Feature Policy</a></li>
- <li><a href="/en-US/docs/Web/HTTP/Feature_Policy/Using_Feature_Policy">Using Feature Policy</a></li>
-</ul>
+- [WebXR Device API](/en-US/docs/Web/API/WebXR_Device_API)
+- {{DOMxRef("XRSystem/requestSession","navigator.xr.requestSession()")}}, and {{DOMxRef("XRSystem/isSessionSupported","navigator.xr.isSessionSupported()")}} and {{Event("devicechange")}} event on {{DOMxRef("Navigator.xr","navigator.xr")}}
+- {{HTTPHeader("Feature-Policy")}} header
+- [Feature Policy](/en-US/docs/Web/HTTP/Feature_Policy)
+- [Using Feature Policy](/en-US/docs/Web/HTTP/Feature_Policy/Using_Feature_Policy)
diff --git a/files/en-us/web/http/headers/feature-policy/xr/index.md b/files/en-us/web/http/headers/feature-policy/xr/index.md
index 529d794a46d8291..cddf9e58c3f9154 100644
--- a/files/en-us/web/http/headers/feature-policy/xr/index.md
+++ b/files/en-us/web/http/headers/feature-policy/xr/index.md
@@ -4,8 +4,7 @@ slug: Web/HTTP/Headers/Feature-Policy/xr
 tags:
   - Deprecated
   - Experimental
-
 ---
-<p>{{HTTPSidebar}} {{Deprecated_Header}}</p>
+{{HTTPSidebar}} {{Deprecated_Header}}
 
-<p>This Feature Policy directive was at one point defined as <code>xr</code> (but implemented in Chrome as {{httpheader("Feature-Policy/vr", "vr")}}), use {{httpheader("Feature-Policy/xr-spatial-tracking", "xr-spatial-tracking")}} instead.</p>
+This Feature Policy directive was at one point defined as `xr` (but implemented in Chrome as {{httpheader("Feature-Policy/vr", "vr")}}), use {{httpheader("Feature-Policy/xr-spatial-tracking", "xr-spatial-tracking")}} instead.
diff --git a/files/en-us/web/http/headers/forwarded/index.md b/files/en-us/web/http/headers/forwarded/index.md
index c337c4febf52679..58e34072ef57662 100644
--- a/files/en-us/web/http/headers/forwarded/index.md
+++ b/files/en-us/web/http/headers/forwarded/index.md
@@ -9,95 +9,88 @@ tags:
   - header
 browser-compat: http.headers.Forwarded
 ---
-<div>{{HTTPSidebar}}</div>
+{{HTTPSidebar}}
 
-<p>The <strong><code>Forwarded</code></strong> header contains information from the <a href="/en-US/docs/Web/HTTP/Proxy_servers_and_tunneling">reverse proxy servers</a> that is altered or lost when a proxy is involved in the path of the request.</p>
+The **`Forwarded`** header contains information from the [reverse proxy servers](/en-US/docs/Web/HTTP/Proxy_servers_and_tunneling) that is altered or lost when a proxy is involved in the path of the request.
 
-<p>The alternative and de-facto standard versions of this header are the {{HTTPHeader("X-Forwarded-For")}}, {{HTTPHeader("X-Forwarded-Host")}} and {{HTTPHeader("X-Forwarded-Proto")}} headers.</p>
+The alternative and de-facto standard versions of this header are the {{HTTPHeader("X-Forwarded-For")}}, {{HTTPHeader("X-Forwarded-Host")}} and {{HTTPHeader("X-Forwarded-Proto")}} headers.
 
-<p>This header is used for debugging, statistics, and generating location-dependent content and by design it exposes privacy sensitive information, such as the IP address of the client. Therefore the user's privacy must be kept in mind when deploying this header.</p>
+This header is used for debugging, statistics, and generating location-dependent content and by design it exposes privacy sensitive information, such as the IP address of the client. Therefore the user's privacy must be kept in mind when deploying this header.
 
 <table class="properties">
- <tbody>
-  <tr>
-   <th scope="row">Header type</th>
-   <td>{{Glossary("Request header")}}</td>
-  </tr>
-  <tr>
-   <th scope="row">{{Glossary("Forbidden header name")}}</th>
-   <td>no</td>
-  </tr>
- </tbody>
+  <tbody>
+    <tr>
+      <th scope="row">Header type</th>
+      <td>{{Glossary("Request header")}}</td>
+    </tr>
+    <tr>
+      <th scope="row">{{Glossary("Forbidden header name")}}</th>
+      <td>no</td>
+    </tr>
+  </tbody>
 </table>
 
-<h2 id="Syntax">Syntax</h2>
+## Syntax
 
-<pre class="brush: html">Forwarded: by=&lt;identifier&gt;;for=&lt;identifier&gt;;host=&lt;host&gt;;proto=&lt;http|https&gt;
-</pre>
+```html
+Forwarded: by=<identifier>;for=<identifier>;host=<host>;proto=<http|https>
+```
 
-<h2 id="Directives">Directives</h2>
+## Directives
 
-<dl>
- <dt>&lt;identifier&gt;</dt>
- <dd>An identifier disclosing the information that is altered or lost when using a proxy. This can be either:
- <ul>
-  <li>an IP address (v4 or v6, optionally with a port, and ipv6 quoted and enclosed in square brackets),</li>
-  <li>an obfuscated identifier (such as "_hidden" or "_secret"),</li>
-  <li>or "unknown" when the preceding entity is not known (and you still want to indicate that forwarding of the request was made).</li>
- </ul>
- </dd>
- <dt>by=&lt;identifier&gt;</dt>
- <dd>The interface where the request came in to the proxy server.</dd>
- <dt>for=&lt;identifier&gt;</dt>
- <dd>The client that initiated the request and subsequent proxies in a chain of proxies.</dd>
- <dt>host=&lt;host&gt;</dt>
- <dd>The {{HTTPHeader("Host")}} request header field as received by the proxy.</dd>
- <dt>proto=&lt;http|https&gt;</dt>
- <dd>
- <p>Indicates which protocol was used to make the request (typically "http" or "https").</p>
- </dd>
-</dl>
+- \<identifier>
 
-<h2 id="Examples">Examples</h2>
+  - : An identifier disclosing the information that is altered or lost when using a proxy. This can be either:
 
-<h3 id="Using_the_Forwarded_header">Using the <code>Forwarded</code> header</h3>
+    - an IP address (v4 or v6, optionally with a port, and ipv6 quoted and enclosed in square brackets),
+    - an obfuscated identifier (such as "\_hidden" or "\_secret"),
+    - or "unknown" when the preceding entity is not known (and you still want to indicate that forwarding of the request was made).
 
-<pre>Forwarded: for="_mdn"
+- by=\<identifier>
+  - : The interface where the request came in to the proxy server.
+- for=\<identifier>
+  - : The client that initiated the request and subsequent proxies in a chain of proxies.
+- host=\<host>
+  - : The {{HTTPHeader("Host")}} request header field as received by the proxy.
+- proto=\<http|https>
+  - : Indicates which protocol was used to make the request (typically "http" or "https").
 
-# case insensitive
-Forwarded: For="[2001:db8:cafe::17]:4711"
+## Examples
 
-# separated by semicolon
-Forwarded: for=192.0.2.60;proto=http;by=203.0.113.43
+### Using the `Forwarded` header
 
-# multiple values can be appended using a comma
-Forwarded: for=192.0.2.43, for=198.51.100.17
-</pre>
+    Forwarded: for="_mdn"
 
-<h3 id="Transitioning_from_X-Forwarded-For_to_Forwarded">Transitioning from <code>X-Forwarded-For</code> to <code>Forwarded</code></h3>
+    # case insensitive
+    Forwarded: For="[2001:db8:cafe::17]:4711"
 
-<p>If your application, server, or proxy supports the standardized <code>Forwarded</code> header, the {{HTTPHeader("X-Forwarded-For")}} header can be replaced. Note that IPv6 address are quoted and enclosed in square brackets in <code>Forwarded</code>.</p>
+    # separated by semicolon
+    Forwarded: for=192.0.2.60;proto=http;by=203.0.113.43
 
-<pre>X-Forwarded-For: 123.34.567.89
-Forwarded: for=123.34.567.89
+    # multiple values can be appended using a comma
+    Forwarded: for=192.0.2.43, for=198.51.100.17
 
-X-Forwarded-For: 192.0.2.43, "[2001:db8:cafe::17]"
-Forwarded: for=192.0.2.43, for="[2001:db8:cafe::17]"
-</pre>
+### Transitioning from `X-Forwarded-For` to `Forwarded`
 
-<h2 id="Specifications">Specifications</h2>
+If your application, server, or proxy supports the standardized `Forwarded` header, the {{HTTPHeader("X-Forwarded-For")}} header can be replaced. Note that IPv6 address are quoted and enclosed in square brackets in `Forwarded`.
+
+    X-Forwarded-For: 123.34.567.89
+    Forwarded: for=123.34.567.89
+
+    X-Forwarded-For: 192.0.2.43, "[2001:db8:cafe::17]"
+    Forwarded: for=192.0.2.43, for="[2001:db8:cafe::17]"
+
+## Specifications
 
 {{Specifications}}
 
-<h2 id="Browser_compatibility">Browser compatibility</h2>
+## Browser compatibility
 
-<p>{{Compat}}</p>
+{{Compat}}
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
- <li>{{HTTPHeader("X-Forwarded-For")}}</li>
- <li>{{HTTPHeader("X-Forwarded-Host")}}</li>
- <li>{{HTTPHeader("X-Forwarded-Proto")}}</li>
- <li>{{HTTPHeader("Via")}} – provides information about the proxy itself, not about the client connecting to it.</li>
-</ul>
+- {{HTTPHeader("X-Forwarded-For")}}
+- {{HTTPHeader("X-Forwarded-Host")}}
+- {{HTTPHeader("X-Forwarded-Proto")}}
+- {{HTTPHeader("Via")}} – provides information about the proxy itself, not about the client connecting to it.
diff --git a/files/en-us/web/http/headers/from/index.md b/files/en-us/web/http/headers/from/index.md
index df4f2d4d4b76eba..4628109ce3f65fb 100644
--- a/files/en-us/web/http/headers/from/index.md
+++ b/files/en-us/web/http/headers/from/index.md
@@ -2,25 +2,21 @@
 title: From
 slug: Web/HTTP/Headers/From
 tags:
-- HTTP
-- Reference
-- header
+  - HTTP
+  - Reference
+  - header
 browser-compat: http.headers.From
 ---
-<div>{{HTTPSidebar}}</div>
+{{HTTPSidebar}}
 
-<p>The <code><strong>From</strong></code> request header contains an Internet email
-  address for a human user who controls the requesting user agent.</p>
+The **`From`** request header contains an Internet email
+address for a human user who controls the requesting user agent.
 
-<p>If you are running a robotic user agent (e.g. a crawler), the <code>From</code> header
-  should be sent, so you can be contacted if problems occur on servers, such as if the
-  robot is sending excessive, unwanted, or invalid requests.</p>
+If you are running a robotic user agent (e.g. a crawler), the `From` header
+should be sent, so you can be contacted if problems occur on servers, such as if the
+robot is sending excessive, unwanted, or invalid requests.
 
-<div class="notecard warning">
-  <p>
-    <strong>Warning:</strong> You shouldn't use the <code>From</code> header for access control or authentication.
-  </p>
-</div>
+> **Warning:** You shouldn't use the `From` header for access control or authentication.
 
 <table class="properties">
   <tbody>
@@ -35,32 +31,29 @@ browser-compat: http.headers.From
   </tbody>
 </table>
 
-<h2 id="Syntax">Syntax</h2>
+## Syntax
 
-<pre class="brush: html">From: &lt;email&gt;
-</pre>
+```html
+From: <email>
+```
 
-<h2 id="Directives">Directives</h2>
+## Directives
 
-<dl>
-  <dt>&lt;email&gt;</dt>
-  <dd>A machine-usable email address.</dd>
-</dl>
+- \<email>
+  - : A machine-usable email address.
 
-<h2 id="Examples">Examples</h2>
+## Examples
 
-<pre>From: webmaster@example.org</pre>
+    From: webmaster@example.org
 
-<h2 id="Specifications">Specifications</h2>
+## Specifications
 
 {{Specifications}}
 
-<h2 id="Browser_compatibility">Browser compatibility</h2>
+## Browser compatibility
 
-<p>{{Compat}}</p>
+{{Compat}}
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
-  <li>{{HTTPHeader("Host")}}</li>
-</ul>
+- {{HTTPHeader("Host")}}
diff --git a/files/en-us/web/http/headers/host/index.md b/files/en-us/web/http/headers/host/index.md
index d03233c185c642f..299f62dbc7795b0 100644
--- a/files/en-us/web/http/headers/host/index.md
+++ b/files/en-us/web/http/headers/host/index.md
@@ -2,22 +2,22 @@
 title: Host
 slug: Web/HTTP/Headers/Host
 tags:
-- HTTP
-- Reference
-- header
+  - HTTP
+  - Reference
+  - header
 browser-compat: http.headers.Host
 ---
-<div>{{HTTPSidebar}}</div>
+{{HTTPSidebar}}
 
-<p>The <code><strong>Host</strong></code> request header specifies the host and port
-  number of the server to which the request is being sent.</p>
+The **`Host`** request header specifies the host and port
+number of the server to which the request is being sent.
 
-<p>If no port is included, the default port for the service requested (e.g.,
-  <code>443</code> for an HTTPS URL, and <code>80</code> for an HTTP URL) is implied.</p>
+If no port is included, the default port for the service requested (e.g.,
+`443` for an HTTPS URL, and `80` for an HTTP URL) is implied.
 
-<p>A <code>Host</code> header field must be sent in all HTTP/1.1 request messages. A
-  {{HTTPStatus("400")}} (Bad Request) status code may be sent to any HTTP/1.1 request
-  message that lacks a <code>Host</code> header field or that contains more than one.</p>
+A `Host` header field must be sent in all HTTP/1.1 request messages. A
+{{HTTPStatus("400")}} (Bad Request) status code may be sent to any HTTP/1.1 request
+message that lacks a `Host` header field or that contains more than one.
 
 <table class="properties">
   <tbody>
@@ -32,35 +32,32 @@ browser-compat: http.headers.Host
   </tbody>
 </table>
 
-<h2 id="Syntax">Syntax</h2>
+## Syntax
 
-<pre class="brush: html">Host: &lt;host&gt;:&lt;port&gt;
-</pre>
+```html
+Host: <host>:<port>
+```
 
-<h2 id="Directives">Directives</h2>
+## Directives
 
-<dl>
-  <dt>&lt;host&gt;</dt>
-  <dd>the domain name of the server (for virtual hosting).</dd>
-  <dt>&lt;port&gt; {{optional_inline}}</dt>
-  <dd>TCP port number on which the server is listening.</dd>
-</dl>
+- \<host>
+  - : the domain name of the server (for virtual hosting).
+- \<port> {{optional_inline}}
+  - : TCP port number on which the server is listening.
 
-<h2 id="Examples">Examples</h2>
+## Examples
 
-<pre>Host: developer.mozilla.org</pre>
+    Host: developer.mozilla.org
 
-<h2 id="Specifications">Specifications</h2>
+## Specifications
 
 {{Specifications}}
 
-<h2 id="Browser_compatibility">Browser compatibility</h2>
+## Browser compatibility
 
-<p>{{Compat}}</p>
+{{Compat}}
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
-  <li>{{HTTPStatus("400")}}</li>
-  <li>{{HTMLElement("base")}}</li>
-</ul>
+- {{HTTPStatus("400")}}
+- {{HTMLElement("base")}}
diff --git a/files/en-us/web/http/headers/if-match/index.md b/files/en-us/web/http/headers/if-match/index.md
index 09cac4823e3d97d..08774efe5a83580 100644
--- a/files/en-us/web/http/headers/if-match/index.md
+++ b/files/en-us/web/http/headers/if-match/index.md
@@ -2,41 +2,38 @@
 title: If-Match
 slug: Web/HTTP/Headers/If-Match
 tags:
-- Conditional Requests
-- HTTP
-- HTTP Header
-- Reference
-- Request header
+  - Conditional Requests
+  - HTTP
+  - HTTP Header
+  - Reference
+  - Request header
 browser-compat: http.headers.If-Match
 ---
-<div>{{HTTPSidebar}}</div>
-
-<p>The <strong><code>If-Match</code></strong> HTTP request header makes the request
-  conditional. For {{HTTPMethod("GET")}} and {{HTTPMethod("HEAD")}} methods, the server
-  will send back the requested resource only if it matches one of the listed
-  <code>ETags</code>. For {{HTTPMethod("PUT")}} and other non-safe methods, it will only
-  upload the resource in this case.</p>
-
-<p>The comparison with the stored {{HTTPHeader("ETag")}} uses the <em>strong comparison
-    algorithm</em>, meaning two files are considered identical byte to byte only. If a
-  listed <code>ETag</code> has the <code>W/</code> prefix indicating a weak entity tag, it
-  will never match under this comparison algorithm.</p>
-
-<p>There are two common use cases:</p>
-
-<ul>
-  <li>For {{HTTPMethod("GET")}} and {{HTTPMethod("HEAD")}} methods, used in combination
-    with a {{HTTPHeader("Range")}} header, it can guarantee that the new ranges requested
-    comes from the same resource than the previous one. If it doesn't match, then a
-    {{HTTPStatus("416")}} (Range Not Satisfiable) response is returned.</li>
-  <li>For other methods, and in particular for {{HTTPMethod("PUT")}},
-    <code>If-Match</code> can be used to prevent the <a
-      href="https://www.w3.org/1999/04/Editing/#3.1">lost update problem</a>. It can check
-    if the modification of a resource that the user wants to upload will not override
-    another change that has been done since the original resource was fetched. If the
-    request cannot be fulfilled, the {{HTTPStatus("412")}} (Precondition Failed) response
-    is returned.</li>
-</ul>
+{{HTTPSidebar}}
+
+The **`If-Match`** HTTP request header makes the request
+conditional. For {{HTTPMethod("GET")}} and {{HTTPMethod("HEAD")}} methods, the server
+will send back the requested resource only if it matches one of the listed
+`ETags`. For {{HTTPMethod("PUT")}} and other non-safe methods, it will only
+upload the resource in this case.
+
+The comparison with the stored {{HTTPHeader("ETag")}} uses the _strong comparison
+algorithm_, meaning two files are considered identical byte to byte only. If a
+listed `ETag` has the `W/` prefix indicating a weak entity tag, it
+will never match under this comparison algorithm.
+
+There are two common use cases:
+
+- For {{HTTPMethod("GET")}} and {{HTTPMethod("HEAD")}} methods, used in combination
+  with a {{HTTPHeader("Range")}} header, it can guarantee that the new ranges requested
+  comes from the same resource than the previous one. If it doesn't match, then a
+  {{HTTPStatus("416")}} (Range Not Satisfiable) response is returned.
+- For other methods, and in particular for {{HTTPMethod("PUT")}},
+  `If-Match` can be used to prevent the [lost update problem](https://www.w3.org/1999/04/Editing/#3.1). It can check
+  if the modification of a resource that the user wants to upload will not override
+  another change that has been done since the original resource was fetched. If the
+  request cannot be fulfilled, the {{HTTPStatus("412")}} (Precondition Failed) response
+  is returned.
 
 <table class="properties">
   <tbody>
@@ -51,49 +48,45 @@ browser-compat: http.headers.If-Match
   </tbody>
 </table>
 
-<h2 id="Syntax">Syntax</h2>
+## Syntax
 
-<pre class="brush: html">If-Match: &lt;etag_value&gt;
-If-Match: &lt;etag_value&gt;, &lt;etag_value&gt;, …
-</pre>
+```html
+If-Match: <etag_value>
+If-Match: <etag_value>, <etag_value>, …
+```
 
-<h2 id="Directives">Directives</h2>
+## Directives
 
-<dl>
-  <dt>&lt;etag_value&gt;</dt>
-  <dd>Entity tags uniquely representing the requested resources. They are a string of
-    ASCII characters placed between double quotes (like <code>"675af34563dc-tr34"</code>).
-    They may be prefixed by <code>W/</code> to indicate that they are "weak", i.e. that
+- \<etag_value>
+  - : Entity tags uniquely representing the requested resources. They are a string of
+    ASCII characters placed between double quotes (like `"675af34563dc-tr34"`).
+    They may be prefixed by `W/` to indicate that they are "weak", i.e. that
     they represent the resource semantically, but not byte-for-byte. However, in an
-    <strong><code>If-Match</code></strong> header, weak entity tags will never match.</dd>
-  <dt><code>*</code></dt>
-  <dd>The asterisk is a special value representing any resource.</dd>
-</dl>
+    **`If-Match`** header, weak entity tags will never match.
+- `*`
+  - : The asterisk is a special value representing any resource.
 
-<h2 id="Examples">Examples</h2>
+## Examples
 
-<pre>If-Match: "bfc13a64729c4290ef5b2c2730249c88ca92d82d"
+    If-Match: "bfc13a64729c4290ef5b2c2730249c88ca92d82d"
 
-If-Match: "67ab43", "54ed21", "7892dd"
+    If-Match: "67ab43", "54ed21", "7892dd"
 
-If-Match: *
-</pre>
+    If-Match: *
 
-<h2 id="Specifications">Specifications</h2>
+## Specifications
 
 {{Specifications}}
 
-<h2 id="Browser_compatibility">Browser compatibility</h2>
+## Browser compatibility
 
-<p>{{Compat}}</p>
+{{Compat}}
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
-  <li>{{HTTPHeader("ETag")}}</li>
-  <li>{{HTTPHeader("If-Unmodified-Since")}}</li>
-  <li>{{HTTPHeader("If-Modified-Since")}}</li>
-  <li>{{HTTPHeader("If-None-Match")}}</li>
-  <li>{{HTTPStatus("416")}}<code> Range Not Satisfiable</code></li>
-  <li>{{HTTPStatus("412")}}<code> Precondition Failed</code></li>
-</ul>
+- {{HTTPHeader("ETag")}}
+- {{HTTPHeader("If-Unmodified-Since")}}
+- {{HTTPHeader("If-Modified-Since")}}
+- {{HTTPHeader("If-None-Match")}}
+- {{HTTPStatus("416")}}` Range Not Satisfiable`
+- {{HTTPStatus("412")}}` Precondition Failed`
diff --git a/files/en-us/web/http/headers/if-modified-since/index.md b/files/en-us/web/http/headers/if-modified-since/index.md
index aa9afbfa9af3522..221489264ff5b24 100644
--- a/files/en-us/web/http/headers/if-modified-since/index.md
+++ b/files/en-us/web/http/headers/if-modified-since/index.md
@@ -2,29 +2,29 @@
 title: If-Modified-Since
 slug: Web/HTTP/Headers/If-Modified-Since
 tags:
-- Conditional Requests
-- HTTP
-- HTTP Header
-- Reference
-- Request header
+  - Conditional Requests
+  - HTTP
+  - HTTP Header
+  - Reference
+  - Request header
 browser-compat: http.headers.If-Modified-Since
 ---
-<div>{{HTTPSidebar}}</div>
+{{HTTPSidebar}}
 
-<p>The <strong><code>If-Modified-Since</code></strong> request HTTP header makes the
-  request conditional: the server will send back the requested resource, with a
-  {{HTTPStatus("200")}} status, only if it has been last modified after the given date. If
-  the resource has not been modified since, the response will be a {{HTTPStatus("304")}}
-  without any body; the {{HTTPHeader("Last-Modified")}} response header of a previous
-  request will contain the date of last modification. Unlike
-  {{HTTPHeader("If-Unmodified-Since")}}, <code>If-Modified-Since</code> can only be used
-  with a {{HTTPMethod("GET")}} or {{HTTPMethod("HEAD")}}.</p>
+The **`If-Modified-Since`** request HTTP header makes the
+request conditional: the server will send back the requested resource, with a
+{{HTTPStatus("200")}} status, only if it has been last modified after the given date. If
+the resource has not been modified since, the response will be a {{HTTPStatus("304")}}
+without any body; the {{HTTPHeader("Last-Modified")}} response header of a previous
+request will contain the date of last modification. Unlike
+{{HTTPHeader("If-Unmodified-Since")}}, `If-Modified-Since` can only be used
+with a {{HTTPMethod("GET")}} or {{HTTPMethod("HEAD")}}.
 
-<p>When used in combination with {{HTTPHeader("If-None-Match")}}, it is ignored, unless
-  the server doesn't support <code>If-None-Match</code>.</p>
+When used in combination with {{HTTPHeader("If-None-Match")}}, it is ignored, unless
+the server doesn't support `If-None-Match`.
 
-<p>The most common use case is to update a cached entity that has no associated
-  {{HTTPHeader("ETag")}}.</p>
+The most common use case is to update a cached entity that has no associated
+{{HTTPHeader("ETag")}}.
 
 <table class="properties">
   <tbody>
@@ -39,55 +39,48 @@ browser-compat: http.headers.If-Modified-Since
   </tbody>
 </table>
 
-<h2 id="Syntax">Syntax</h2>
-
-<pre class="brush: html">If-Modified-Since: &lt;day-name&gt;, &lt;day&gt; &lt;month&gt; &lt;year&gt; &lt;hour&gt;:&lt;minute&gt;:&lt;second&gt; GMT
-</pre>
-
-<h2 id="Directives">Directives</h2>
-
-<dl>
-  <dt>&lt;day-name&gt;</dt>
-  <dd>One of "Mon", "Tue", "Wed", "Thu", "Fri", "Sat", or "Sun" (case-sensitive).</dd>
-  <dt>&lt;day&gt;</dt>
-  <dd>2 digit day number, e.g. "04" or "23".</dd>
-  <dt>&lt;month&gt;</dt>
-  <dd>One of "Jan", "Feb", "Mar", "Apr", "May", "Jun", "Jul", "Aug", "Sep", "Oct", "Nov",
-    "Dec" (case sensitive).</dd>
-  <dt>&lt;year&gt;</dt>
-  <dd>4 digit year number, e.g. "1990" or "2016".</dd>
-  <dt>&lt;hour&gt;</dt>
-  <dd>2 digit hour number, e.g. "09" or "23".</dd>
-  <dt>&lt;minute&gt;</dt>
-  <dd>2 digit minute number, e.g. "04" or "59".</dd>
-  <dt>&lt;second&gt;</dt>
-  <dd>2 digit second number, e.g. "04" or "59".</dd>
-  <dt><code>GMT</code></dt>
-  <dd>
-    <p>Greenwich Mean Time. HTTP dates are always expressed in GMT, never in local time.
-    </p>
-  </dd>
-</dl>
-
-<h2 id="Examples">Examples</h2>
-
-<pre>If-Modified-Since: Wed, 21 Oct 2015 07:28:00 GMT
-</pre>
-
-<h2 id="Specifications">Specifications</h2>
+## Syntax
+
+```html
+If-Modified-Since: <day-name>, <day> <month> <year> <hour>:<minute>:<second> GMT
+```
+
+## Directives
+
+- \<day-name>
+  - : One of "Mon", "Tue", "Wed", "Thu", "Fri", "Sat", or "Sun" (case-sensitive).
+- \<day>
+  - : 2 digit day number, e.g. "04" or "23".
+- \<month>
+  - : One of "Jan", "Feb", "Mar", "Apr", "May", "Jun", "Jul", "Aug", "Sep", "Oct", "Nov",
+    "Dec" (case sensitive).
+- \<year>
+  - : 4 digit year number, e.g. "1990" or "2016".
+- \<hour>
+  - : 2 digit hour number, e.g. "09" or "23".
+- \<minute>
+  - : 2 digit minute number, e.g. "04" or "59".
+- \<second>
+  - : 2 digit second number, e.g. "04" or "59".
+- `GMT`
+  - : Greenwich Mean Time. HTTP dates are always expressed in GMT, never in local time.
+
+## Examples
+
+    If-Modified-Since: Wed, 21 Oct 2015 07:28:00 GMT
+
+## Specifications
 
 {{Specifications}}
 
-<h2 id="Browser_compatibility">Browser compatibility</h2>
+## Browser compatibility
 
-<p>{{Compat}}</p>
+{{Compat}}
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
-  <li>{{HTTPHeader("ETag")}}</li>
-  <li>{{HTTPHeader("If-Unmodified-since")}}</li>
-  <li>{{HTTPHeader("If-Match")}}</li>
-  <li>{{HTTPHeader("If-None-Match")}}</li>
-  <li>{{HTTPStatus("304")}}<code> Not Modified</code></li>
-</ul>
+- {{HTTPHeader("ETag")}}
+- {{HTTPHeader("If-Unmodified-since")}}
+- {{HTTPHeader("If-Match")}}
+- {{HTTPHeader("If-None-Match")}}
+- {{HTTPStatus("304")}}` Not Modified`
diff --git a/files/en-us/web/http/headers/if-none-match/index.md b/files/en-us/web/http/headers/if-none-match/index.md
index d7266057cdc22c2..bdef9f56a31e8b1 100644
--- a/files/en-us/web/http/headers/if-none-match/index.md
+++ b/files/en-us/web/http/headers/if-none-match/index.md
@@ -9,75 +9,70 @@ tags:
   - Request header
 browser-compat: http.headers.If-None-Match
 ---
-<div>{{HTTPSidebar}}</div>
+{{HTTPSidebar}}
 
-<p>The <strong><code>If-None-Match</code></strong> HTTP request header makes the request conditional. For {{HTTPMethod("GET")}} and {{HTTPMethod("HEAD")}} methods, the server will send back the requested resource, with a {{HTTPStatus("200")}} status, only if it doesn't have an {{HTTPHeader("ETag")}} matching the given ones. For other methods, the request will be processed only if the eventually existing resource's {{HTTPHeader("ETag")}} doesn't match any of the values listed.</p>
+The **`If-None-Match`** HTTP request header makes the request conditional. For {{HTTPMethod("GET")}} and {{HTTPMethod("HEAD")}} methods, the server will send back the requested resource, with a {{HTTPStatus("200")}} status, only if it doesn't have an {{HTTPHeader("ETag")}} matching the given ones. For other methods, the request will be processed only if the eventually existing resource's {{HTTPHeader("ETag")}} doesn't match any of the values listed.
 
-<p>When the condition fails for {{HTTPMethod("GET")}} and {{HTTPMethod("HEAD")}} methods, then the server must return HTTP status code 304 (Not Modified). For methods that apply server-side changes, the status code 412 (Precondition Failed) is used. Note that the server generating a 304 response MUST generate any of the following header fields that would have been sent in a 200 (OK) response to the same request: Cache-Control, Content-Location, Date, ETag, Expires, and Vary.</p>
+When the condition fails for {{HTTPMethod("GET")}} and {{HTTPMethod("HEAD")}} methods, then the server must return HTTP status code 304 (Not Modified). For methods that apply server-side changes, the status code 412 (Precondition Failed) is used. Note that the server generating a 304 response MUST generate any of the following header fields that would have been sent in a 200 (OK) response to the same request: Cache-Control, Content-Location, Date, ETag, Expires, and Vary.
 
-<p>The comparison with the stored {{HTTPHeader("ETag")}} uses the <em>weak comparison algorithm</em>, meaning two files are considered identical if the content is equivalent — they don't have to be identical byte for byte. For example, two pages that differ by the date of generation in the footer would still be considered as identical.</p>
+The comparison with the stored {{HTTPHeader("ETag")}} uses the _weak comparison algorithm_, meaning two files are considered identical if the content is equivalent — they don't have to be identical byte for byte. For example, two pages that differ by the date of generation in the footer would still be considered as identical.
 
-<p>When used in combination with {{HTTPHeader("If-Modified-Since")}}, <strong><code>If-None-Match</code></strong> has precedence (if the server supports it).</p>
+When used in combination with {{HTTPHeader("If-Modified-Since")}}, **`If-None-Match`** has precedence (if the server supports it).
 
-<p>There are two common use cases:</p>
+There are two common use cases:
 
-<ul>
- <li>For {{HTTPMethod("GET")}} and {{HTTPMethod("HEAD")}} methods, to update a cached entity that has an associated {{HTTPHeader("ETag")}}.</li>
- <li>For other methods, and in particular for {{HTTPMethod("PUT")}}, <code>If-None-Match</code> used with the <code>*</code> value can be used to save a file not known to exist, guaranteeing that another upload didn't happen before, losing the data of the previous put; this problem is a variation of the <a href="https://www.w3.org/1999/04/Editing/#3.1">lost update problem</a>.</li>
-</ul>
+- For {{HTTPMethod("GET")}} and {{HTTPMethod("HEAD")}} methods, to update a cached entity that has an associated {{HTTPHeader("ETag")}}.
+- For other methods, and in particular for {{HTTPMethod("PUT")}}, `If-None-Match` used with the `*` value can be used to save a file not known to exist, guaranteeing that another upload didn't happen before, losing the data of the previous put; this problem is a variation of the [lost update problem](https://www.w3.org/1999/04/Editing/#3.1).
 
 <table class="properties">
- <tbody>
-  <tr>
-   <th scope="row">Header type</th>
-   <td>{{Glossary("Request header")}}</td>
-  </tr>
-  <tr>
-   <th scope="row">{{Glossary("Forbidden header name")}}</th>
-   <td>no</td>
-  </tr>
- </tbody>
+  <tbody>
+    <tr>
+      <th scope="row">Header type</th>
+      <td>{{Glossary("Request header")}}</td>
+    </tr>
+    <tr>
+      <th scope="row">{{Glossary("Forbidden header name")}}</th>
+      <td>no</td>
+    </tr>
+  </tbody>
 </table>
 
-<h2 id="Syntax">Syntax</h2>
+## Syntax
 
-<pre class="brush: html">If-None-Match: "&lt;etag_value&gt;"
-If-None-Match: "&lt;etag_value&gt;", "&lt;etag_value&gt;", …
-If-None-Match: *</pre>
+```html
+If-None-Match: "<etag_value>"
+If-None-Match: "<etag_value>", "<etag_value>", …
+If-None-Match: *
+```
 
-<h2 id="Directives">Directives</h2>
+## Directives
 
-<dl>
- <dt>&lt;etag_value&gt;</dt>
- <dd>Entity tags uniquely representing the requested resources. They are a string of ASCII characters placed between double quotes (Like <code>"675af34563dc-tr34"</code>) and may be prefixed by <code>W/</code> to indicate that the weak comparison algorithm should be used (This is useless with <code>If-None-Match</code> as it only uses that algorithm).</dd>
- <dt><code>*</code></dt>
- <dd>The asterisk is a special value representing any resource. They are only useful when uploading a resource, usually with {{HTTPMethod("PUT")}}, to check if another resource with the identity has already been uploaded before.</dd>
-</dl>
+- \<etag_value>
+  - : Entity tags uniquely representing the requested resources. They are a string of ASCII characters placed between double quotes (Like `"675af34563dc-tr34"`) and may be prefixed by `W/` to indicate that the weak comparison algorithm should be used (This is useless with `If-None-Match` as it only uses that algorithm).
+- `*`
+  - : The asterisk is a special value representing any resource. They are only useful when uploading a resource, usually with {{HTTPMethod("PUT")}}, to check if another resource with the identity has already been uploaded before.
 
-<h2 id="Examples">Examples</h2>
+## Examples
 
-<pre>If-None-Match: "bfc13a64729c4290ef5b2c2730249c88ca92d82d"
+    If-None-Match: "bfc13a64729c4290ef5b2c2730249c88ca92d82d"
 
-If-None-Match: W/"67ab43", "54ed21", "7892dd"
+    If-None-Match: W/"67ab43", "54ed21", "7892dd"
 
-If-None-Match: *
-</pre>
+    If-None-Match: *
 
-<h2 id="Specifications">Specifications</h2>
+## Specifications
 
 {{Specifications}}
 
-<h2 id="Browser_compatibility">Browser compatibility</h2>
+## Browser compatibility
 
-<p>{{Compat}}</p>
+{{Compat}}
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
- <li>{{HTTPHeader("ETag")}}</li>
- <li>{{HTTPHeader("If-Unmodified-Since")}}</li>
- <li>{{HTTPHeader("If-Modified-Since")}}</li>
- <li>{{HTTPHeader("If-Match")}}</li>
- <li>{{HTTPStatus("304")}}<code> Not Modified</code></li>
- <li>{{HTTPStatus("412")}}<code> Precondition Failed</code></li>
-</ul>
+- {{HTTPHeader("ETag")}}
+- {{HTTPHeader("If-Unmodified-Since")}}
+- {{HTTPHeader("If-Modified-Since")}}
+- {{HTTPHeader("If-Match")}}
+- {{HTTPStatus("304")}}` Not Modified`
+- {{HTTPStatus("412")}}` Precondition Failed`
diff --git a/files/en-us/web/http/headers/if-range/index.md b/files/en-us/web/http/headers/if-range/index.md
index cde5ba791431f09..3405a39e1fd2350 100644
--- a/files/en-us/web/http/headers/if-range/index.md
+++ b/files/en-us/web/http/headers/if-range/index.md
@@ -2,27 +2,27 @@
 title: If-Range
 slug: Web/HTTP/Headers/If-Range
 tags:
-- Condtional Requests
-- HTTP
-- HTTP Header
-- Range Requests
-- Reference
-- Request header
+  - Condtional Requests
+  - HTTP
+  - HTTP Header
+  - Range Requests
+  - Reference
+  - Request header
 browser-compat: http.headers.If-Range
 ---
-<div>{{HTTPSidebar}}</div>
+{{HTTPSidebar}}
 
-<p>The <strong><code>If-Range</code></strong> HTTP request header makes a range request
-  conditional: if the condition is fulfilled, the range request will be issued and the
-  server sends back a {{HTTPStatus("206")}} <code>Partial Content</code> answer with the
-  appropriate body. If the condition is not fulfilled, the full resource is sent back,
-  with a {{HTTPStatus("200")}} <code>OK</code> status.</p>
+The **`If-Range`** HTTP request header makes a range request
+conditional: if the condition is fulfilled, the range request will be issued and the
+server sends back a {{HTTPStatus("206")}} `Partial Content` answer with the
+appropriate body. If the condition is not fulfilled, the full resource is sent back,
+with a {{HTTPStatus("200")}} `OK` status.
 
-<p>This header can be used either with a {{HTTPHeader("Last-Modified")}} validator, or
-  with an {{HTTPHeader("ETag")}}, but not with both.</p>
+This header can be used either with a {{HTTPHeader("Last-Modified")}} validator, or
+with an {{HTTPHeader("ETag")}}, but not with both.
 
-<p>The most common use case is to resume a download, to guarantee that the stored resource
-  has not been modified since the last fragment has been received.</p>
+The most common use case is to resume a download, to guarantee that the stored resource
+has not been modified since the last fragment has been received.
 
 <table class="properties">
   <tbody>
@@ -37,64 +37,57 @@ browser-compat: http.headers.If-Range
   </tbody>
 </table>
 
-<h2 id="Syntax">Syntax</h2>
-
-<pre class="brush: html">If-Range: &lt;day-name&gt;, &lt;day&gt; &lt;month&gt; &lt;year&gt; &lt;hour&gt;:&lt;minute&gt;:&lt;second&gt; GMT
-If-Range: &lt;etag&gt;</pre>
-
-<h2 id="Directives">Directives</h2>
-
-<dl>
-  <dt>&lt;etag&gt;</dt>
-  <dd>An entity tag uniquely representing the requested resource. It is a string of ASCII
-    characters placed between double quotes (Like <code>"675af34563dc-tr34"</code>) and
-    may be prefixed by <code>W/</code> to indicate that the weak comparison algorithm
-    should be used.</dd>
-  <dt>&lt;day-name&gt;</dt>
-  <dd>One of "Mon", "Tue", "Wed", "Thu", "Fri", "Sat", or "Sun" (case-sensitive).</dd>
-  <dt>&lt;day&gt;</dt>
-  <dd>2 digit day number, e.g. "04" or "23".</dd>
-  <dt>&lt;month&gt;</dt>
-  <dd>One of "Jan", "Feb", "Mar", "Apr", "May", "Jun", "Jul", "Aug", "Sep", "Oct", "Nov",
-    "Dec" (case sensitive).</dd>
-  <dt>&lt;year&gt;</dt>
-  <dd>4 digit year number, e.g. "1990" or "2016".</dd>
-  <dt>&lt;hour&gt;</dt>
-  <dd>2 digit hour number, e.g. "09" or "23".</dd>
-  <dt>&lt;minute&gt;</dt>
-  <dd>2 digit minute number, e.g. "04" or "59".</dd>
-  <dt>&lt;second&gt;</dt>
-  <dd>2 digit second number, e.g. "04" or "59".</dd>
-  <dt><code>GMT</code></dt>
-  <dd>
-    <p>Greenwich Mean Time. HTTP dates are always expressed in GMT, never in local time.
-    </p>
-  </dd>
-</dl>
-
-<h2 id="Examples">Examples</h2>
-
-<pre>If-Range: Wed, 21 Oct 2015 07:28:00 GMT
-</pre>
-
-<h2 id="Specifications">Specifications</h2>
+## Syntax
+
+```html
+If-Range: <day-name>, <day> <month> <year> <hour>:<minute>:<second> GMT
+If-Range: <etag>
+```
+
+## Directives
+
+- \<etag>
+  - : An entity tag uniquely representing the requested resource. It is a string of ASCII
+    characters placed between double quotes (Like `"675af34563dc-tr34"`) and
+    may be prefixed by `W/` to indicate that the weak comparison algorithm
+    should be used.
+- \<day-name>
+  - : One of "Mon", "Tue", "Wed", "Thu", "Fri", "Sat", or "Sun" (case-sensitive).
+- \<day>
+  - : 2 digit day number, e.g. "04" or "23".
+- \<month>
+  - : One of "Jan", "Feb", "Mar", "Apr", "May", "Jun", "Jul", "Aug", "Sep", "Oct", "Nov",
+    "Dec" (case sensitive).
+- \<year>
+  - : 4 digit year number, e.g. "1990" or "2016".
+- \<hour>
+  - : 2 digit hour number, e.g. "09" or "23".
+- \<minute>
+  - : 2 digit minute number, e.g. "04" or "59".
+- \<second>
+  - : 2 digit second number, e.g. "04" or "59".
+- `GMT`
+  - : Greenwich Mean Time. HTTP dates are always expressed in GMT, never in local time.
+
+## Examples
+
+    If-Range: Wed, 21 Oct 2015 07:28:00 GMT
+
+## Specifications
 
 {{Specifications}}
 
-<h2 id="Browser_compatibility">Browser compatibility</h2>
+## Browser compatibility
 
-<p>{{Compat}}</p>
+{{Compat}}
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
-  <li>{{HTTPHeader("ETag")}}</li>
-  <li>{{HTTPHeader("Last-Modified")}}</li>
-  <li>{{HTTPHeader("If-Modified-Since")}}</li>
-  <li>{{HTTPHeader("If-Unmodified-Since")}}</li>
-  <li>{{HTTPHeader("If-Match")}}</li>
-  <li>{{HTTPHeader("If-None-Match")}}</li>
-  <li>{{HTTPStatus("206")}}<code> Partial Content</code></li>
-  <li><a href="/en-US/docs/Web/HTTP/Conditional_requests">HTTP Conditional Requests</a>
-  </li>
-</ul>
+- {{HTTPHeader("ETag")}}
+- {{HTTPHeader("Last-Modified")}}
+- {{HTTPHeader("If-Modified-Since")}}
+- {{HTTPHeader("If-Unmodified-Since")}}
+- {{HTTPHeader("If-Match")}}
+- {{HTTPHeader("If-None-Match")}}
+- {{HTTPStatus("206")}}` Partial Content`
+- [HTTP Conditional Requests](/en-US/docs/Web/HTTP/Conditional_requests)
diff --git a/files/en-us/web/http/headers/if-unmodified-since/index.md b/files/en-us/web/http/headers/if-unmodified-since/index.md
index 78415d9bb52577e..9fb66f9076cef6c 100644
--- a/files/en-us/web/http/headers/if-unmodified-since/index.md
+++ b/files/en-us/web/http/headers/if-unmodified-since/index.md
@@ -2,33 +2,29 @@
 title: If-Unmodified-Since
 slug: Web/HTTP/Headers/If-Unmodified-Since
 tags:
-- HTTP
-- HTTP Header
-- Reference
-- Request header
+  - HTTP
+  - HTTP Header
+  - Reference
+  - Request header
 browser-compat: http.headers.If-Unmodified-Since
 ---
-<div>{{HTTPSidebar}}</div>
-
-<p>The <strong><code>If-Unmodified-Since</code></strong> request HTTP header makes the
-  request conditional: the server will send back the requested resource, or accept it in
-  the case of a {{HTTPMethod("POST")}} or another non-{{Glossary("Safe/HTTP", "safe")}} method, only if
-  it has not been last modified after the given date. If the resource has been modified
-  after the given date, the response will be a {{HTTPStatus("412")}} (Precondition Failed)
-  error.</p>
-
-<p>There are two common use cases:</p>
-
-<ul>
-  <li>In conjunction with non-{{Glossary("Safe/HTTP", "safe")}} methods, like {{HTTPMethod("POST")}},
-    it can be used to implement an <a
-      href="https://en.wikipedia.org/wiki/Optimistic_concurrency_control">optimistic
-      concurrency control</a>, like done by some wikis: editions are rejected if the
-    stored document has been modified since the original has been retrieved.</li>
-  <li>In conjunction with a range request with a {{HTTPHeader("If-Range")}} header, it can
-    be used to ensure that the new fragment requested comes from an unmodified document.
-  </li>
-</ul>
+{{HTTPSidebar}}
+
+The **`If-Unmodified-Since`** request HTTP header makes the
+request conditional: the server will send back the requested resource, or accept it in
+the case of a {{HTTPMethod("POST")}} or another non-{{Glossary("Safe/HTTP", "safe")}} method, only if
+it has not been last modified after the given date. If the resource has been modified
+after the given date, the response will be a {{HTTPStatus("412")}} (Precondition Failed)
+error.
+
+There are two common use cases:
+
+- In conjunction with non-{{Glossary("Safe/HTTP", "safe")}} methods, like {{HTTPMethod("POST")}},
+  it can be used to implement an [optimistic
+  concurrency control](https://en.wikipedia.org/wiki/Optimistic_concurrency_control), like done by some wikis: editions are rejected if the
+  stored document has been modified since the original has been retrieved.
+- In conjunction with a range request with a {{HTTPHeader("If-Range")}} header, it can
+  be used to ensure that the new fragment requested comes from an unmodified document.
 
 <table class="properties">
   <tbody>
@@ -43,56 +39,49 @@ browser-compat: http.headers.If-Unmodified-Since
   </tbody>
 </table>
 
-<h2 id="Syntax">Syntax</h2>
-
-<pre class="brush: html">If-Unmodified-Since: &lt;day-name&gt;, &lt;day&gt; &lt;month&gt; &lt;year&gt; &lt;hour&gt;:&lt;minute&gt;:&lt;second&gt; GMT
-</pre>
-
-<h2 id="Directives">Directives</h2>
-
-<dl>
-  <dt>&lt;day-name&gt;</dt>
-  <dd>One of "Mon", "Tue", "Wed", "Thu", "Fri", "Sat", or "Sun" (case-sensitive).</dd>
-  <dt>&lt;day&gt;</dt>
-  <dd>2 digit day number, e.g. "04" or "23".</dd>
-  <dt>&lt;month&gt;</dt>
-  <dd>One of "Jan", "Feb", "Mar", "Apr", "May", "Jun", "Jul", "Aug", "Sep", "Oct", "Nov",
-    "Dec" (case sensitive).</dd>
-  <dt>&lt;year&gt;</dt>
-  <dd>4 digit year number, e.g. "1990" or "2016".</dd>
-  <dt>&lt;hour&gt;</dt>
-  <dd>2 digit hour number, e.g. "09" or "23".</dd>
-  <dt>&lt;minute&gt;</dt>
-  <dd>2 digit minute number, e.g. "04" or "59".</dd>
-  <dt>&lt;second&gt;</dt>
-  <dd>2 digit second number, e.g. "04" or "59".</dd>
-  <dt><code>GMT</code></dt>
-  <dd>
-    <p>Greenwich Mean Time. HTTP dates are always expressed in GMT, never in local time.
-    </p>
-  </dd>
-</dl>
-
-<h2 id="Examples">Examples</h2>
-
-<pre>If-Unmodified-Since: Wed, 21 Oct 2015 07:28:00 GMT
-</pre>
-
-<h2 id="Specifications">Specifications</h2>
+## Syntax
+
+```html
+If-Unmodified-Since: <day-name>, <day> <month> <year> <hour>:<minute>:<second> GMT
+```
+
+## Directives
+
+- \<day-name>
+  - : One of "Mon", "Tue", "Wed", "Thu", "Fri", "Sat", or "Sun" (case-sensitive).
+- \<day>
+  - : 2 digit day number, e.g. "04" or "23".
+- \<month>
+  - : One of "Jan", "Feb", "Mar", "Apr", "May", "Jun", "Jul", "Aug", "Sep", "Oct", "Nov",
+    "Dec" (case sensitive).
+- \<year>
+  - : 4 digit year number, e.g. "1990" or "2016".
+- \<hour>
+  - : 2 digit hour number, e.g. "09" or "23".
+- \<minute>
+  - : 2 digit minute number, e.g. "04" or "59".
+- \<second>
+  - : 2 digit second number, e.g. "04" or "59".
+- `GMT`
+  - : Greenwich Mean Time. HTTP dates are always expressed in GMT, never in local time.
+
+## Examples
+
+    If-Unmodified-Since: Wed, 21 Oct 2015 07:28:00 GMT
+
+## Specifications
 
 {{Specifications}}
 
-<h2 id="Browser_compatibility">Browser compatibility</h2>
+## Browser compatibility
 
-<p>{{Compat}}</p>
+{{Compat}}
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
-  <li>{{HTTPHeader("Last-Modified")}}</li>
-  <li>{{HTTPHeader("If-Modified-Since")}}</li>
-  <li>{{HTTPHeader("If-Match")}}</li>
-  <li>{{HTTPHeader("If-None-Match")}}</li>
-  <li>{{HTTPHeader("If-Range")}}</li>
-  <li>{{HTTPStatus("412")}}<code> Precondition Failed</code></li>
-</ul>
+- {{HTTPHeader("Last-Modified")}}
+- {{HTTPHeader("If-Modified-Since")}}
+- {{HTTPHeader("If-Match")}}
+- {{HTTPHeader("If-None-Match")}}
+- {{HTTPHeader("If-Range")}}
+- {{HTTPStatus("412")}}` Precondition Failed`
diff --git a/files/en-us/web/http/headers/index.md b/files/en-us/web/http/headers/index.md
index 054a239b50b4126..3a2f5ea36733e6b 100644
--- a/files/en-us/web/http/headers/index.md
+++ b/files/en-us/web/http/headers/index.md
@@ -9,447 +9,390 @@ tags:
   - Overview
   - Reference
 ---
-<div>{{HTTPSidebar}}</div>
-
-<p><strong>HTTP headers</strong> let the client and the server pass additional information with an HTTP request or response. An HTTP header consists of its case-insensitive name followed by a colon (<code>:</code>), then by its value. {{Glossary("Whitespace")}} before the value is ignored.</p>
-
-<p>Custom proprietary headers have historically been used with an <code>X-</code> prefix, but this convention was deprecated in June 2012 because of the inconveniences it caused when nonstandard fields became standard in <a href="https://datatracker.ietf.org/doc/html/rfc6648">RFC 6648</a>; others are listed in an <a href="https://www.iana.org/assignments/message-headers/perm-headers.html">IANA registry</a>, whose original content was defined in <a href="https://datatracker.ietf.org/doc/html/rfc4229">RFC 4229</a>. IANA also maintains a <a href="https://www.iana.org/assignments/message-headers/prov-headers.html">registry of proposed new HTTP headers</a>.</p>
-
-<p>Headers can be grouped according to their contexts:</p>
-
-<ul>
- <li>{{Glossary("Request header", "Request headers")}} contain more information about the resource to be fetched, or about the client requesting the resource.</li>
- <li>{{Glossary("Response header", "Response headers")}} hold additional information about the response, like its location or about the server providing it.</li>
- <li>{{Glossary("Representation header", "Representation headers")}} contain information about the body of the resource, like its <a href="/en-US/docs/Web/HTTP/Basics_of_HTTP/MIME_types">MIME type</a>, or encoding/compression applied.</li>
- <li>{{Glossary("Payload header","Payload headers")}} contain representation-independent information about payload data, including content length and the encoding used for transport.</li>
-</ul>
-
-<p>Headers can also be grouped according to how {{Glossary("Proxy_server", "proxies")}} handle them:</p>
-
-<ul>
- <li>{{ httpheader("Connection") }}</li>
- <li>{{ httpheader("Keep-Alive") }}</li>
- <li>{{ httpheader("Proxy-Authenticate") }}</li>
- <li>{{ httpheader("Proxy-Authorization") }}</li>
- <li>{{ httpheader("TE") }}</li>
- <li>{{ httpheader("Trailer") }}</li>
- <li>{{ httpheader("Transfer-Encoding") }}</li>
- <li>{{ httpheader("Upgrade") }} (see also <a href="/en-US/docs/Web/HTTP/Protocol_upgrade_mechanism">Protocol upgrade mechanism</a>).</li>
-</ul>
-
-<dl>
- <dt id="e2e">End-to-end headers</dt>
- <dd>These headers <em>must</em> be transmitted to the final recipient of the message: the server for a request, or the client for a response. Intermediate proxies must retransmit these headers unmodified and caches must store them.</dd>
- <dt id="hbh">Hop-by-hop headers</dt>
- <dd>These headers are meaningful only for a single transport-level connection, and <em>must not</em> be retransmitted by proxies or cached. Note that only hop-by-hop headers may be set using the {{httpheader("Connection")}} header.</dd>
-</dl>
-
-<h2 id="Authentication">Authentication</h2>
-
-<dl>
- <dt>{{HTTPHeader("WWW-Authenticate")}}</dt>
- <dd>Defines the authentication method that should be used to access a resource.</dd>
- <dt>{{HTTPHeader("Authorization")}}</dt>
- <dd>Contains the credentials to authenticate a user-agent with a server.</dd>
- <dt>{{HTTPHeader("Proxy-Authenticate")}}</dt>
- <dd>Defines the authentication method that should be used to access a resource behind a proxy server.</dd>
- <dt>{{HTTPHeader("Proxy-Authorization")}}</dt>
- <dd>Contains the credentials to authenticate a user agent with a proxy server.</dd>
-</dl>
-
-<h2 id="Caching">Caching</h2>
-
-<dl>
- <dt>{{HTTPHeader("Age")}}</dt>
- <dd>The time, in seconds, that the object has been in a proxy cache.</dd>
- <dt>{{HTTPHeader("Cache-Control")}}</dt>
- <dd>Directives for caching mechanisms in both requests and responses.</dd>
- <dt>{{HTTPHeader("Clear-Site-Data")}}</dt>
- <dd>Clears browsing data (e.g. cookies, storage, cache) associated with the requesting website.</dd>
- <dt>{{HTTPHeader("Expires")}}</dt>
- <dd>The date/time after which the response is considered stale.</dd>
- <dt>{{HTTPHeader("Pragma")}}</dt>
- <dd>Implementation-specific header that may have various effects anywhere along the request-response chain. Used for backwards compatibility with HTTP/1.0 caches where the <code>Cache-Control</code> header is not yet present.</dd>
- <dt>{{HTTPHeader("Warning")}}</dt>
- <dd>General warning information about possible problems.</dd>
-</dl>
-
-<h2 id="Client_hints">Client hints</h2>
-
-<p>HTTP {{Glossary("Client_hints", "Client hints")}} are a set of request headers that provide useful information about the client such as device type and network conditions, and allow servers to optimize what is served for those conditions.</p>
-
-<p>Servers proactively requests the client hint headers they are interested in from the client using {{HTTPHeader("Accept-CH")}}. The client may then choose to include the requested headers in subsequent requests.</p>
-
-<dl>
- <dt>{{HTTPHeader("Accept-CH")}} {{experimental_inline}}</dt>
- <dd>Servers can advertise support for Client Hints using the <code>Accept-CH</code> header field or an equivalent HTML <code>&lt;meta&gt;</code> element with <a href="/en-US/docs/Web/HTML/Element/meta#attr-http-equiv"><code>http-equi</code>v</a> attribute.</dd>
- <dt>{{HTTPHeader("Accept-CH-Lifetime")}} {{experimental_inline}} {{deprecated_inline}}</dt>
- <dd>Servers can ask the client to remember the set of Client Hints that the server supports for a specified period of time, to enable delivery of Client Hints on subsequent requests to the server’s origin.</dd>
-</dl>
-
-<p>The different categories of client hints are listed below.</p>
-
-<h3 id="device_client_hints">Device client hints</h3>
-
-<dl>
-  <dt>{{HTTPHeader("Content-DPR")}} {{deprecated_inline}}{{experimental_inline}}</dt>
-  <dd>Response header used to confirm the image device to pixel ratio in requests where the {{HTTPHeader("DPR")}} client hint was used to select an image resource.</dd>
-  <dt>{{HTTPHeader("Device-Memory")}} {{deprecated_inline}}{{experimental_inline}}</dt>
-  <dd>Approximate amount of available client RAM memory. This is part of the <a href="/en-US/docs/Web/API/Device_Memory_API">Device Memory API</a>.</dd>
-  <dt>{{HTTPHeader("DPR")}} {{deprecated_inline}}{{experimental_inline}}</dt>
-  <dd>Client device pixel ratio (DPR), which is the number of physical device pixels corresponding to every CSS pixel.</dd>
-  <dt>{{HTTPHeader("Viewport-Width")}} {{deprecated_inline}}{{experimental_inline}}</dt>
-  <dd>A number that indicates the layout viewport width in CSS pixels. The provided pixel value is a number rounded to the smallest following integer (i.e. ceiling value).</dd>
-  <dt>{{HTTPHeader("Width")}} {{deprecated_inline}}{{experimental_inline}}</dt>
-  <dd>The <code>Width</code> request header field is a number that indicates the desired resource width in physical pixels (i.e. intrinsic size of an image).</dd>
- </dl>
-
-
-<h3 id="network_client_hints">Network client hints</h3>
-
-<p>Network client hints allow a server to choose what information is sent based on the user choice and network bandwidth and latency.</p>
-
-<dl>
-  <dt>{{HTTPHeader("Downlink")}}</dt>
-  <dd>Approximate bandwidth of the client's connection to the server, in Mbps. This is part of the <a href="/en-US/docs/Web/API/Network_Information_API">Network Information API</a>.</dd>
-  <dt>{{HTTPHeader("ECT")}}</dt>
-  <dd>The {{Glossary("effective connection type")}} ("network profile") that best matches the connection's latency and bandwidth. This is part of the <a href="/en-US/docs/Web/API/Network_Information_API">Network Information API</a>.</dd>
-  <dt>{{HTTPHeader("RTT")}}</dt>
-  <dd>Application layer round trip time (RTT) in miliseconds, which includes the server processing time. This is part of the <a href="/en-US/docs/Web/API/Network_Information_API">Network Information API</a>.</dd>
-  <dt>{{HTTPHeader("Save-Data")}} {{experimental_inline}}</dt>
-  <dd>A boolean that indicates the user agent's preference for reduced data usage.</dd>
- </dl>
-
-<h2 id="Conditionals">Conditionals</h2>
-
-<dl>
- <dt>{{HTTPHeader("Last-Modified")}}</dt>
- <dd>The last modification date of the resource, used to compare several versions of the same resource. It is less accurate than {{HTTPHeader("ETag")}}, but easier to calculate in some environments. Conditional requests using {{HTTPHeader("If-Modified-Since")}} and {{HTTPHeader("If-Unmodified-Since")}} use this value to change the behavior of the request.</dd>
- <dt>{{HTTPHeader("ETag")}}</dt>
- <dd>A unique string identifying the version of the resource. Conditional requests using {{HTTPHeader("If-Match")}} and {{HTTPHeader("If-None-Match")}} use this value to change the behavior of the request.</dd>
- <dt>{{HTTPHeader("If-Match")}}</dt>
- <dd>Makes the request conditional, and applies the method only if the stored resource matches one of the given ETags.</dd>
- <dt>{{HTTPHeader("If-None-Match")}}</dt>
- <dd>Makes the request conditional, and applies the method only if the stored resource <em>doesn't</em> match any of the given ETags. This is used to update caches (for safe requests), or to prevent to upload a new resource when one already exists.</dd>
- <dt>{{HTTPHeader("If-Modified-Since")}}</dt>
- <dd>Makes the request conditional, and expects the resource to be transmitted only if it has been modified after the given date. This is used to transmit data only when the cache is out of date.</dd>
- <dt>{{HTTPHeader("If-Unmodified-Since")}}</dt>
- <dd>Makes the request conditional, and expects the resource to be transmitted only if it has not been modified after the given date. This ensures the coherence of a new fragment of a specific range with previous ones, or to implement an optimistic concurrency control system when modifying existing documents.</dd>
- <dt>{{HTTPHeader("Vary")}}</dt>
- <dd>Determines how to match request headers to decide whether a cached response can be used rather than requesting a fresh one from the origin server.</dd>
-</dl>
-
-<h2 id="Connection_management">Connection management</h2>
-
-<dl>
- <dt>{{HTTPHeader("Connection")}}</dt>
- <dd>Controls whether the network connection stays open after the current transaction finishes.</dd>
- <dt>{{HTTPHeader("Keep-Alive")}}</dt>
- <dd>Controls how long a persistent connection should stay open.</dd>
-</dl>
-
-
-<h2 id="Content_negotiation">Content negotiation</h2>
-
-<p><a href="/en-US/docs/Web/HTTP/Content_negotiation">Content negotiation</a> headers.</p>
-<dl>
- <dt>{{HTTPHeader("Accept")}}</dt>
- <dd>Informs the server about the {{Glossary("MIME_type", "types")}} of data that can be sent back.</dd>
- <dt>{{HTTPHeader("Accept-Encoding")}}</dt>
- <dd>The encoding algorithm, usually a <a href="/en-US/docs/Web/HTTP/Compression">compression algorithm</a>, that can be used on the resource sent back.</dd>
- <dt>{{HTTPHeader("Accept-Language")}}</dt>
- <dd>Informs the server about the human language the server is expected to send back. This is a hint and is not necessarily under the full control of the user: the server should always pay attention not to override an explicit user choice (like selecting a language from a dropdown).</dd>
-</dl>
-
-<h2 id="Controls">Controls</h2>
-
-<dl>
- <dt>{{HTTPHeader("Expect")}}</dt>
- <dd>Indicates expectations that need to be fulfilled by the server to properly handle the request.</dd>
- <dt>{{HTTPHeader("Max-Forwards")}}</dt>
- <dd>TBD</dd>
-</dl>
-
-<h2 id="Cookies">Cookies</h2>
-
-<dl>
- <dt>{{HTTPHeader("Cookie")}}</dt>
- <dd>Contains stored <a href="/en-US/docs/Web/HTTP/Cookies">HTTP cookies</a> previously sent by the server with the {{HTTPHeader("Set-Cookie")}} header.</dd>
- <dt>{{HTTPHeader("Set-Cookie")}}</dt>
- <dd>Send cookies from the server to the user-agent.</dd>
- <dt>{{HTTPHeader("Cookie2")}} {{deprecated_inline}}</dt>
- <dd>Contains an HTTP cookie previously sent by the server with the {{HTTPHeader("Set-Cookie2")}} header, but has been <strong>obsoleted</strong>. Use {{HTTPHeader("Cookie")}} instead.</dd>
- <dt>{{HTTPHeader("Set-Cookie2")}} {{deprecated_inline}}</dt>
- <dd>Sends cookies from the server to the user-agent, but has been <strong>obsoleted</strong>. Use {{HTTPHeader("Set-Cookie")}} instead.</dd>
-</dl>
-
-<h2 id="CORS">CORS</h2>
-
-<p><em>Learn more about CORS <a href="CORS">here</a>.</em></p>
-
-<dl>
- <dt>{{HTTPHeader("Access-Control-Allow-Origin")}}</dt>
- <dd>Indicates whether the response can be shared.</dd>
- <dt>{{HTTPHeader("Access-Control-Allow-Credentials")}}</dt>
- <dd>Indicates whether the response to the request can be exposed when the credentials flag is true.</dd>
- <dt>{{HTTPHeader("Access-Control-Allow-Headers")}}</dt>
- <dd>Used in response to a {{Glossary("Preflight_request", "preflight request")}} to indicate which HTTP headers can be used when making the actual request.</dd>
- <dt>{{HTTPHeader("Access-Control-Allow-Methods")}}</dt>
- <dd>Specifies the methods allowed when accessing the resource in response to a preflight request.</dd>
- <dt>{{HTTPHeader("Access-Control-Expose-Headers")}}</dt>
- <dd>Indicates which headers can be exposed as part of the response by listing their names.</dd>
- <dt>{{HTTPHeader("Access-Control-Max-Age")}}</dt>
- <dd>Indicates how long the results of a preflight request can be cached.</dd>
- <dt>{{HTTPHeader("Access-Control-Request-Headers")}}</dt>
- <dd>Used when issuing a preflight request to let the server know which HTTP headers will be used when the actual request is made.</dd>
- <dt>{{HTTPHeader("Access-Control-Request-Method")}}</dt>
- <dd>Used when issuing a preflight request to let the server know which <a href="/en-US/docs/Web/HTTP/Methods">HTTP method</a> will be used when the actual request is made.</dd>
- <dt>{{HTTPHeader("Origin")}}</dt>
- <dd>Indicates where a fetch originates from.</dd>
- <dt>{{HTTPHeader("Timing-Allow-Origin")}}</dt>
- <dd>Specifies origins that are allowed to see values of attributes retrieved via features of the <a href="/en-US/docs/Web/API/Resource_Timing_API">Resource Timing API</a>, which would otherwise be reported as zero due to cross-origin restrictions.</dd>
-</dl>
-
-<h2 id="Downloads">Downloads</h2>
-
-<dl>
- <dt>{{HTTPHeader("Content-Disposition")}}</dt>
- <dd>Indicates if the resource transmitted should be displayed inline (default behavior without the header), or if it should be handled like a download and the browser should present a “Save As” dialog.</dd>
-</dl>
-
-<h2 id="Message_body_information">Message body information</h2>
-
-<dl>
- <dt>{{HTTPHeader("Content-Length")}}</dt>
- <dd>The size of the resource, in decimal number of bytes.</dd>
- <dt>{{HTTPHeader("Content-Type")}}</dt>
- <dd>Indicates the media type of the resource.</dd>
- <dt>{{HTTPHeader("Content-Encoding")}}</dt>
- <dd>Used to specify the compression algorithm.</dd>
- <dt>{{HTTPHeader("Content-Language")}}</dt>
- <dd>Describes the human language(s) intended for the audience, so that it allows a user to differentiate according to the users' own preferred language.</dd>
- <dt>{{HTTPHeader("Content-Location")}}</dt>
- <dd>Indicates an alternate location for the returned data.</dd>
-</dl>
-
-<h2 id="Proxies">Proxies</h2>
-
-<dl>
- <dt>{{HTTPHeader("Forwarded")}}</dt>
- <dd>Contains information from the client-facing side of proxy servers that is altered or lost when a proxy is involved in the path of the request.</dd>
- <dt>{{HTTPHeader("X-Forwarded-For")}} {{non-standard_inline}}</dt>
- <dd>Identifies the originating IP addresses of a client connecting to a web server through an HTTP proxy or a load balancer.</dd>
- <dt>{{HTTPHeader("X-Forwarded-Host")}} {{non-standard_inline}}</dt>
- <dd>Identifies the original host requested that a client used to connect to your proxy or load balancer.</dd>
- <dt>{{HTTPHeader("X-Forwarded-Proto")}} {{non-standard_inline}}</dt>
- <dd>Identifies the protocol (HTTP or HTTPS) that a client used to connect to your proxy or load balancer.</dd>
- <dt>{{HTTPHeader("Via")}}</dt>
- <dd>Added by proxies, both forward and reverse proxies, and can appear in the request headers and the response headers.</dd>
-</dl>
-
-<h2 id="Redirects">Redirects</h2>
-
-<dl>
- <dt>{{HTTPHeader("Location")}}</dt>
- <dd>Indicates the URL to redirect a page to.</dd>
-</dl>
-
-<h2 id="Request_context">Request context</h2>
-
-<dl>
- <dt>{{HTTPHeader("From")}}</dt>
- <dd>Contains an Internet email address for a human user who controls the requesting user agent.</dd>
- <dt>{{HTTPHeader("Host")}}</dt>
- <dd>Specifies the domain name of the server (for virtual hosting), and (optionally) the TCP port number on which the server is listening.</dd>
- <dt>{{HTTPHeader("Referer")}}</dt>
- <dd>The address of the previous web page from which a link to the currently requested page was followed.</dd>
- <dt>{{HTTPHeader("Referrer-Policy")}}</dt>
- <dd>Governs which referrer information sent in the {{HTTPHeader("Referer")}} header should be included with requests made.</dd>
- <dt>{{HTTPHeader("User-Agent")}}</dt>
- <dd>Contains a characteristic string that allows the network protocol peers to identify the application type, operating system, software vendor or software version of the requesting software user agent. See also the <a href="/en-US/docs/Web/HTTP/Headers/User-Agent/Firefox">Firefox user agent string reference</a>.</dd>
-</dl>
-
-<h2 id="Response_context">Response context</h2>
-
-<dl>
- <dt>{{HTTPHeader("Allow")}}</dt>
- <dd>Lists the set of HTTP request methods supported by a resource.</dd>
- <dt>{{HTTPHeader("Server")}}</dt>
- <dd>Contains information about the software used by the origin server to handle the request.</dd>
-</dl>
-
-<h2 id="Range_requests">Range requests</h2>
-
-<dl>
- <dt>{{HTTPHeader("Accept-Ranges")}}</dt>
- <dd>Indicates if the server supports range requests, and if so in which unit the range can be expressed.</dd>
- <dt>{{HTTPHeader("Range")}}</dt>
- <dd>Indicates the part of a document that the server should return.</dd>
- <dt>{{HTTPHeader("If-Range")}}</dt>
- <dd>Creates a conditional range request that is only fulfilled if the given etag or date matches the remote resource. Used to prevent downloading two ranges from incompatible version of the resource.</dd>
- <dt>{{HTTPHeader("Content-Range")}}</dt>
- <dd>Indicates where in a full body message a partial message belongs.</dd>
-</dl>
-
-<h2 id="Security">Security</h2>
-
-<dl>
- <dt>{{HTTPHeader("Cross-Origin-Embedder-Policy")}} (COEP)</dt>
- <dd>Allows a server to declare an embedder policy for a given document.</dd>
- <dt>{{HTTPHeader("Cross-Origin-Opener-Policy")}} (COOP)</dt>
- <dd>Prevents other domains from opening/controlling a window.</dd>
- <dt>{{HTTPHeader("Cross-Origin-Resource-Policy")}} (CORP)</dt>
- <dd>Prevents other domains from reading the response of the resources to which this header is applied.</dd>
- <dt>{{HTTPHeader("Content-Security-Policy")}} ({{Glossary("CSP")}})</dt>
- <dd>Controls resources the user agent is allowed to load for a given page.</dd>
- <dt>{{HTTPHeader("Content-Security-Policy-Report-Only")}}</dt>
- <dd>Allows web developers to experiment with policies by monitoring, but not enforcing, their effects. These violation reports consist of {{Glossary("JSON")}} documents sent via an HTTP <code>POST</code> request to the specified URI.</dd>
- <dt>{{HTTPHeader("Expect-CT")}}</dt>
- <dd>Allows sites to opt in to reporting and/or enforcement of Certificate Transparency requirements, which prevents the use of misissued certificates for that site from going unnoticed. When a site enables the Expect-CT header, they are requesting that Chrome check that any certificate for that site appears in public CT logs.</dd>
- <dt>{{HTTPHeader("Feature-Policy")}}</dt>
- <dd>Provides a mechanism to allow and deny the use of browser features in its own frame, and in iframes that it embeds.</dd>
- <dt>{{HTTPHeader("Origin-Isolation")}} {{experimental_inline}}</dt>
- <dd>Provides a mechanism to allow web applications to isolate their origins.</dd>
- <dt>{{HTTPHeader("Strict-Transport-Security")}} ({{Glossary("HSTS")}})</dt>
- <dd>Force communication using HTTPS instead of HTTP.</dd>
- <dt>{{HTTPHeader("Upgrade-Insecure-Requests")}}</dt>
- <dd>Sends a signal to the server expressing the client’s preference for an encrypted and authenticated response, and that it can successfully handle the {{CSP("upgrade-insecure-requests")}} directive.</dd>
- <dt>{{HTTPHeader("X-Content-Type-Options")}}</dt>
- <dd>Disables MIME sniffing and forces browser to use the type given in {{HTTPHeader("Content-Type")}}.</dd>
- <dt>{{HTTPHeader("X-Download-Options")}}</dt>
- <dd>The <code><a href="https://docs.microsoft.com/en-us/previous-versions/windows/internet-explorer/ie-developer/compatibility/jj542450(v=vs.85)?#the-noopen-directive">X-Download-Options</a></code> HTTP header indicates that the browser (Internet Explorer) should not display the option to "Open" a file that has been downloaded from an application, to prevent phishing attacks as the file otherwise would gain access to execute in the context of the application. (Note: related <a href="https://developer.microsoft.com/en-us/microsoft-edge/platform/issues/18488178/">MS Edge bug</a>).</dd>
- <dt>{{HTTPHeader("X-Frame-Options")}} (XFO)</dt>
- <dd>Indicates whether a browser should be allowed to render a page in a {{HTMLElement("frame")}}, {{HTMLElement("iframe")}}, {{HTMLElement("embed")}} or {{HTMLElement("object")}}.</dd>
- <dt>{{HTTPHeader("X-Permitted-Cross-Domain-Policies")}}</dt>
- <dd>Specifies if a cross-domain policy file (<code>crossdomain.xml</code>) is allowed. The file may define a policy to grant clients, such as Adobe's Flash Player (now obsolete), Adobe Acrobat, Microsoft Silverlight (now obsolete), or Apache Flex, permission to handle data across domains that would otherwise be restricted due to the <a href="/en-US/docs/Web/Security/Same-origin_policy">Same-Origin Policy</a>. See the <a href="https://www.adobe.com/devnet/articles/crossdomain_policy_file_spec.html">Cross-domain Policy File Specification</a> for more information.</dd>
- <dt>{{HTTPHeader("X-Powered-By")}}</dt>
- <dd>May be set by hosting environments or other frameworks and contains information about them while not providing any usefulness to the application or its visitors. Unset this header to avoid exposing potential vulnerabilities.</dd>
- <dt>{{HTTPHeader("X-XSS-Protection")}}</dt>
- <dd>Enables cross-site scripting filtering.</dd>
-</dl>
-
-<h3 id="HTTP_Public_Key_Pinning_GlossaryHPKP">HTTP Public Key Pinning (HPKP)</h3>
-
-<p>{{Glossary("HPKP", "HTTP Public Key Pinning")}} has been deprecated and removed in favor of Certificate Transparency and {{HTTPHeader("Expect-CT")}}.</p>
-
-<dl>
- <dt>{{HTTPHeader("Public-Key-Pins")}}</dt>
- <dd>Associates a specific cryptographic public key with a certain web server to decrease the risk of {{Glossary("MITM")}} attacks with forged certificates.</dd>
- <dt>{{HTTPHeader("Public-Key-Pins-Report-Only")}}</dt>
- <dd>Sends reports to the report-uri specified in the header and does still allow clients to connect to the server even if the pinning is violated.</dd>
-</dl>
-
-<h3 id="Fetch_metadata_request_headers">Fetch metadata request headers</h3>
-
-<p>{{Glossary("Fetch metadata request header", "Fetch metadata request headers")}} provides information about the context from which the request originated. This allows a server to make decisions about whether a request should be allowed based on where the request came from and how the resource will be used.</p>
-
-<dl>
- <dt>{{HTTPHeader("Sec-Fetch-Site")}}</dt>
- <dd>It is a request header that indicates the relationship between a request initiator's origin and its target's origin. It is a Structured Header whose value is a token with possible values <code>cross-site</code>, <code>same-origin</code>, <code>same-site</code>, and <code>none</code>.</dd>
- <dt>{{HTTPHeader("Sec-Fetch-Mode")}}</dt>
- <dd>It is a request header that indicates the request's mode to a server. It is a Structured Header whose value is a token with possible values <code>cors</code>, <code>navigate</code>, <code>no-cors</code>, <code>same-origin</code>, and <code>websocket</code>.</dd>
- <dt>{{HTTPHeader("Sec-Fetch-User")}}</dt>
- <dd>It is a request header that indicates whether or not a navigation request was triggered by user activation. It is a Structured Header whose value is a boolean so possible values are <code>?0</code> for false and <code>?1</code> for true.</dd>
- <dt>{{HTTPHeader("Sec-Fetch-Dest")}}</dt>
- <dd>It is a request header that indicates the request's destination to a server. It is a Structured Header whose value is a token with possible values <code>audio</code>, <code>audioworklet</code>, <code>document</code>, <code>embed</code>, <code>empty</code>, <code>font</code>, <code>image</code>, <code>manifest</code>, <code>object</code>, <code>paintworklet</code>, <code>report</code>, <code>script</code>, <code>serviceworker</code>, <code>sharedworker</code>, <code>style</code>, <code>track</code>, <code>video</code>, <code>worker</code>, and <code>xslt</code>.</dd>
-</dl>
-
-<h2 id="Server-sent_events">Server-sent events</h2>
-
-<dl>
- <dt>{{HTTPHeader("Last-Event-ID")}}</dt>
- <dd>TBD</dd>
- <dt>{{HTTPHeader("NEL")}} {{experimental_inline}}</dt>
- <dd>Defines a mechanism that enables developers to declare a network error reporting policy.</dd>
- <dt>{{HTTPHeader("Ping-From")}}</dt>
- <dd>TBD</dd>
- <dt>{{HTTPHeader("Ping-To")}}</dt>
- <dd>TBD</dd>
- <dt>{{HTTPHeader("Report-To")}}</dt>
- <dd>Used to specify a server endpoint for the browser to send warning and error reports to.</dd>
-</dl>
-
-<h2 id="Transfer_coding">Transfer coding</h2>
-
-<dl>
- <dt>{{HTTPHeader("Transfer-Encoding")}}</dt>
- <dd>Specifies the form of encoding used to safely transfer the resource to the user.</dd>
- <dt>{{HTTPHeader("TE")}}</dt>
- <dd>Specifies the transfer encodings the user agent is willing to accept.</dd>
- <dt>{{HTTPHeader("Trailer")}}</dt>
- <dd>Allows the sender to include additional fields at the end of chunked message.</dd>
-</dl>
-
-<h2 id="WebSockets">WebSockets</h2>
-
-<dl>
- <dt>{{HTTPHeader("Sec-WebSocket-Key")}}</dt>
- <dd>TBD</dd>
- <dt>{{HTTPHeader("Sec-WebSocket-Extensions")}}</dt>
- <dd>TBD</dd>
- <dt>{{HTTPHeader("Sec-WebSocket-Accept")}}</dt>
- <dd>TBD</dd>
- <dt>{{HTTPHeader("Sec-WebSocket-Protocol")}}</dt>
- <dd>TBD</dd>
- <dt>{{HTTPHeader("Sec-WebSocket-Version")}}</dt>
- <dd>TBD</dd>
-</dl>
-
-<h2 id="Other">Other</h2>
-
-<dl>
- <dt>{{HTTPHeader("Accept-Push-Policy")}} {{experimental_inline}}</dt>
- <dd>A client can express the desired push policy for a request by sending an <code><a href="https://datatracker.ietf.org/doc/html/draft-ruellan-http-accept-push-policy-00#section-3.1">Accept-Push-Policy</a></code> header field in the request.</dd>
- <dt>{{HTTPHeader("Accept-Signature")}} {{experimental_inline}}</dt>
- <dd>A client can send the <code><a href="https://wicg.github.io/webpackage/draft-yasskin-http-origin-signed-responses.html#rfc.section.3.7">Accept-Signature</a></code> header field to indicate intention to take advantage of any available signatures and to indicate what kinds of signatures it supports.</dd>
- <dt>{{HTTPHeader("Alt-Svc")}}</dt>
- <dd>Used to list alternate ways to reach this service.</dd>
- <dt>{{HTTPHeader("Date")}}</dt>
- <dd>Contains the date and time at which the message was originated.</dd>
- <dt>{{HTTPHeader("Early-Data")}} {{experimental_inline}}</dt>
- <dd>Indicates that the request has been conveyed in TLS early data.</dd>
- <dt>{{HTTPHeader("Large-Allocation")}}</dt>
- <dd>Tells the browser that the page being loaded is going to want to perform a large allocation.</dd>
- <dt>{{HTTPHeader("Link")}}</dt>
- <dd>The <code><a href="https://datatracker.ietf.org/doc/html/rfc5988#section-5">Link</a></code> entity-header field provides a means for serialising one or more links in HTTP headers. It is semantically equivalent to the HTML {{HTMLElement("link")}} element.</dd>
- <dt>{{HTTPHeader("Push-Policy")}} {{experimental_inline}}</dt>
- <dd>A <code><a href="https://datatracker.ietf.org/doc/html/draft-ruellan-http-accept-push-policy-00#section-3.2">Push-Policy</a></code> defines the server behavior regarding push when processing a request.</dd>
- <dt>{{HTTPHeader("Retry-After")}}</dt>
- <dd>Indicates how long the user agent should wait before making a follow-up request.</dd>
- <dt>{{HTTPHeader("Signature")}} {{experimental_inline}}</dt>
- <dd>The <code><a href="https://wicg.github.io/webpackage/draft-yasskin-http-origin-signed-responses.html#rfc.section.3.1">Signature</a></code> header field conveys a list of signatures for an exchange, each one accompanied by information about how to determine the authority of and refresh that signature.</dd>
- <dt>{{HTTPHeader("Signed-Headers")}} {{experimental_inline}}</dt>
- <dd>The <code><a href="https://wicg.github.io/webpackage/draft-yasskin-http-origin-signed-responses.html#rfc.section.5.1.2">Signed-Headers</a></code> header field identifies an ordered list of response header fields to include in a signature.</dd>
- <dt>{{HTTPHeader("Server-Timing")}}</dt>
- <dd>Communicates one or more metrics and descriptions for the given request-response cycle.</dd>
- <dt>{{HTTPHeader("Service-Worker-Allowed")}}</dt>
- <dd>Used to remove the <a href="https://w3c.github.io/ServiceWorker/#path-restriction">path restriction</a> by including this header <a href="https://w3c.github.io/ServiceWorker/#service-worker-script-response">in the response of the Service Worker script</a>.</dd>
- <dt>{{HTTPHeader("SourceMap")}}</dt>
- <dd>Links generated code to a <a href="/en-US/docs/Tools/Debugger/How_to/Use_a_source_map">source map</a>.</dd>
- <dt>{{HTTPHeader("Upgrade")}}</dt>
- <dd>The relevant RFC document for the <a href="https://datatracker.ietf.org/doc/html/rfc7230#section-6.7">Upgrade header field is RFC 7230, section 6.7</a>. The standard establishes rules for upgrading or changing to a different protocol on the current client, server, transport protocol connection. For example, this header standard allows a client to change from HTTP 1.1 to HTTP 2.0, assuming the server decides to acknowledge and implement the Upgrade header field. Neither party is required to accept the terms specified in the Upgrade header field. It can be used in both client and server headers. If the Upgrade header field is specified, then the sender MUST also send the Connection header field with the upgrade option specified. For details on the Connection header field <a href="https://datatracker.ietf.org/doc/html/rfc7230#section-6.1">please see section 6.1 of the aforementioned RFC</a>.</dd>
- <dt>{{HTTPHeader("X-DNS-Prefetch-Control")}}</dt>
- <dd>Controls DNS prefetching, a feature by which browsers proactively perform domain name resolution on both links that the user may choose to follow as well as URLs for items referenced by the document, including images, CSS, JavaScript, and so forth.</dd>
- <dt>{{HTTPHeader("X-Firefox-Spdy")}} {{deprecated_inline}} {{non-standard_inline}}</dt>
- <dd>TBD</dd>
- <dt>{{HTTPHeader("X-Pingback")}} {{non-standard_inline}}</dt>
- <dd>TBD</dd>
- <dt>{{HTTPHeader("X-Requested-With")}}</dt>
- <dd>TBD</dd>
- <dt>{{HTTPHeader("X-Robots-Tag")}}{{non-standard_inline}}</dt>
- <dd>The <code><a href="https://developers.google.com/search/reference/robots_meta_tag#xrobotstag">X-Robots-Tag</a></code> HTTP header is used to indicate how a web page is to be indexed within public search engine results. The header is effectively equivalent to <code>&lt;meta name="robots" content="..."&gt;</code>.</dd>
- <dt>{{HTTPHeader("X-UA-Compatible")}} {{non-standard_inline}}</dt>
- <dd>Used by Internet Explorer to signal which document mode to use.</dd>
-</dl>
-
-<h2 id="Contributing">Contributing</h2>
-
-<p>You can help by <a href="/en-US/docs/MDN/Contribute/Howto/Document_an_HTTP_header">writing new entries</a> or improving the existing ones.</p>
-
-<h2 id="See_also">See also</h2>
-
-<ul>
- <li><a href="https://en.wikipedia.org/wiki/List_of_HTTP_header_fields">Wikipedia page on List of HTTP headers</a></li>
- <li><a href="https://www.iana.org/assignments/message-headers/perm-headers.html">IANA registry</a></li>
- <li><a href="https://httpwg.org/specs/">HTTP Working Group</a></li>
-</ul>
+{{HTTPSidebar}}
+
+**HTTP headers** let the client and the server pass additional information with an HTTP request or response. An HTTP header consists of its case-insensitive name followed by a colon (`:`), then by its value. {{Glossary("Whitespace")}} before the value is ignored.
+
+Custom proprietary headers have historically been used with an `X-` prefix, but this convention was deprecated in June 2012 because of the inconveniences it caused when nonstandard fields became standard in [RFC 6648](https://datatracker.ietf.org/doc/html/rfc6648); others are listed in an [IANA registry](https://www.iana.org/assignments/message-headers/perm-headers.html), whose original content was defined in [RFC 4229](https://datatracker.ietf.org/doc/html/rfc4229). IANA also maintains a [registry of proposed new HTTP headers](https://www.iana.org/assignments/message-headers/prov-headers.html).
+
+Headers can be grouped according to their contexts:
+
+- {{Glossary("Request header", "Request headers")}} contain more information about the resource to be fetched, or about the client requesting the resource.
+- {{Glossary("Response header", "Response headers")}} hold additional information about the response, like its location or about the server providing it.
+- {{Glossary("Representation header", "Representation headers")}} contain information about the body of the resource, like its [MIME type](/en-US/docs/Web/HTTP/Basics_of_HTTP/MIME_types), or encoding/compression applied.
+- {{Glossary("Payload header","Payload headers")}} contain representation-independent information about payload data, including content length and the encoding used for transport.
+
+Headers can also be grouped according to how {{Glossary("Proxy_server", "proxies")}} handle them:
+
+- {{ httpheader("Connection") }}
+- {{ httpheader("Keep-Alive") }}
+- {{ httpheader("Proxy-Authenticate") }}
+- {{ httpheader("Proxy-Authorization") }}
+- {{ httpheader("TE") }}
+- {{ httpheader("Trailer") }}
+- {{ httpheader("Transfer-Encoding") }}
+- {{ httpheader("Upgrade") }} (see also [Protocol upgrade mechanism](/en-US/docs/Web/HTTP/Protocol_upgrade_mechanism)).
+
+<!---->
+
+- End-to-end headers
+  - : These headers _must_ be transmitted to the final recipient of the message: the server for a request, or the client for a response. Intermediate proxies must retransmit these headers unmodified and caches must store them.
+- Hop-by-hop headers
+  - : These headers are meaningful only for a single transport-level connection, and _must not_ be retransmitted by proxies or cached. Note that only hop-by-hop headers may be set using the {{httpheader("Connection")}} header.
+
+## Authentication
+
+- {{HTTPHeader("WWW-Authenticate")}}
+  - : Defines the authentication method that should be used to access a resource.
+- {{HTTPHeader("Authorization")}}
+  - : Contains the credentials to authenticate a user-agent with a server.
+- {{HTTPHeader("Proxy-Authenticate")}}
+  - : Defines the authentication method that should be used to access a resource behind a proxy server.
+- {{HTTPHeader("Proxy-Authorization")}}
+  - : Contains the credentials to authenticate a user agent with a proxy server.
+
+## Caching
+
+- {{HTTPHeader("Age")}}
+  - : The time, in seconds, that the object has been in a proxy cache.
+- {{HTTPHeader("Cache-Control")}}
+  - : Directives for caching mechanisms in both requests and responses.
+- {{HTTPHeader("Clear-Site-Data")}}
+  - : Clears browsing data (e.g. cookies, storage, cache) associated with the requesting website.
+- {{HTTPHeader("Expires")}}
+  - : The date/time after which the response is considered stale.
+- {{HTTPHeader("Pragma")}}
+  - : Implementation-specific header that may have various effects anywhere along the request-response chain. Used for backwards compatibility with HTTP/1.0 caches where the `Cache-Control` header is not yet present.
+- {{HTTPHeader("Warning")}}
+  - : General warning information about possible problems.
+
+## Client hints
+
+HTTP {{Glossary("Client_hints", "Client hints")}} are a set of request headers that provide useful information about the client such as device type and network conditions, and allow servers to optimize what is served for those conditions.
+
+Servers proactively requests the client hint headers they are interested in from the client using {{HTTPHeader("Accept-CH")}}. The client may then choose to include the requested headers in subsequent requests.
+
+- {{HTTPHeader("Accept-CH")}} {{experimental_inline}}
+  - : Servers can advertise support for Client Hints using the `Accept-CH` header field or an equivalent HTML `<meta>` element with [`http-equi`v](/en-US/docs/Web/HTML/Element/meta#attr-http-equiv) attribute.
+- {{HTTPHeader("Accept-CH-Lifetime")}} {{experimental_inline}} {{deprecated_inline}}
+  - : Servers can ask the client to remember the set of Client Hints that the server supports for a specified period of time, to enable delivery of Client Hints on subsequent requests to the server’s origin.
+
+The different categories of client hints are listed below.
+
+### Device client hints
+
+- {{HTTPHeader("Content-DPR")}} {{deprecated_inline}}{{experimental_inline}}
+  - : Response header used to confirm the image device to pixel ratio in requests where the {{HTTPHeader("DPR")}} client hint was used to select an image resource.
+- {{HTTPHeader("Device-Memory")}} {{deprecated_inline}}{{experimental_inline}}
+  - : Approximate amount of available client RAM memory. This is part of the [Device Memory API](/en-US/docs/Web/API/Device_Memory_API).
+- {{HTTPHeader("DPR")}} {{deprecated_inline}}{{experimental_inline}}
+  - : Client device pixel ratio (DPR), which is the number of physical device pixels corresponding to every CSS pixel.
+- {{HTTPHeader("Viewport-Width")}} {{deprecated_inline}}{{experimental_inline}}
+  - : A number that indicates the layout viewport width in CSS pixels. The provided pixel value is a number rounded to the smallest following integer (i.e. ceiling value).
+- {{HTTPHeader("Width")}} {{deprecated_inline}}{{experimental_inline}}
+  - : The `Width` request header field is a number that indicates the desired resource width in physical pixels (i.e. intrinsic size of an image).
+
+### Network client hints
+
+Network client hints allow a server to choose what information is sent based on the user choice and network bandwidth and latency.
+
+- {{HTTPHeader("Downlink")}}
+  - : Approximate bandwidth of the client's connection to the server, in Mbps. This is part of the [Network Information API](/en-US/docs/Web/API/Network_Information_API).
+- {{HTTPHeader("ECT")}}
+  - : The {{Glossary("effective connection type")}} ("network profile") that best matches the connection's latency and bandwidth. This is part of the [Network Information API](/en-US/docs/Web/API/Network_Information_API).
+- {{HTTPHeader("RTT")}}
+  - : Application layer round trip time (RTT) in miliseconds, which includes the server processing time. This is part of the [Network Information API](/en-US/docs/Web/API/Network_Information_API).
+- {{HTTPHeader("Save-Data")}} {{experimental_inline}}
+  - : A boolean that indicates the user agent's preference for reduced data usage.
+
+## Conditionals
+
+- {{HTTPHeader("Last-Modified")}}
+  - : The last modification date of the resource, used to compare several versions of the same resource. It is less accurate than {{HTTPHeader("ETag")}}, but easier to calculate in some environments. Conditional requests using {{HTTPHeader("If-Modified-Since")}} and {{HTTPHeader("If-Unmodified-Since")}} use this value to change the behavior of the request.
+- {{HTTPHeader("ETag")}}
+  - : A unique string identifying the version of the resource. Conditional requests using {{HTTPHeader("If-Match")}} and {{HTTPHeader("If-None-Match")}} use this value to change the behavior of the request.
+- {{HTTPHeader("If-Match")}}
+  - : Makes the request conditional, and applies the method only if the stored resource matches one of the given ETags.
+- {{HTTPHeader("If-None-Match")}}
+  - : Makes the request conditional, and applies the method only if the stored resource _doesn't_ match any of the given ETags. This is used to update caches (for safe requests), or to prevent to upload a new resource when one already exists.
+- {{HTTPHeader("If-Modified-Since")}}
+  - : Makes the request conditional, and expects the resource to be transmitted only if it has been modified after the given date. This is used to transmit data only when the cache is out of date.
+- {{HTTPHeader("If-Unmodified-Since")}}
+  - : Makes the request conditional, and expects the resource to be transmitted only if it has not been modified after the given date. This ensures the coherence of a new fragment of a specific range with previous ones, or to implement an optimistic concurrency control system when modifying existing documents.
+- {{HTTPHeader("Vary")}}
+  - : Determines how to match request headers to decide whether a cached response can be used rather than requesting a fresh one from the origin server.
+
+## Connection management
+
+- {{HTTPHeader("Connection")}}
+  - : Controls whether the network connection stays open after the current transaction finishes.
+- {{HTTPHeader("Keep-Alive")}}
+  - : Controls how long a persistent connection should stay open.
+
+## Content negotiation
+
+[Content negotiation](/en-US/docs/Web/HTTP/Content_negotiation) headers.
+
+- {{HTTPHeader("Accept")}}
+  - : Informs the server about the {{Glossary("MIME_type", "types")}} of data that can be sent back.
+- {{HTTPHeader("Accept-Encoding")}}
+  - : The encoding algorithm, usually a [compression algorithm](/en-US/docs/Web/HTTP/Compression), that can be used on the resource sent back.
+- {{HTTPHeader("Accept-Language")}}
+  - : Informs the server about the human language the server is expected to send back. This is a hint and is not necessarily under the full control of the user: the server should always pay attention not to override an explicit user choice (like selecting a language from a dropdown).
+
+## Controls
+
+- {{HTTPHeader("Expect")}}
+  - : Indicates expectations that need to be fulfilled by the server to properly handle the request.
+- {{HTTPHeader("Max-Forwards")}}
+  - : TBD
+
+## Cookies
+
+- {{HTTPHeader("Cookie")}}
+  - : Contains stored [HTTP cookies](/en-US/docs/Web/HTTP/Cookies) previously sent by the server with the {{HTTPHeader("Set-Cookie")}} header.
+- {{HTTPHeader("Set-Cookie")}}
+  - : Send cookies from the server to the user-agent.
+- {{HTTPHeader("Cookie2")}} {{deprecated_inline}}
+  - : Contains an HTTP cookie previously sent by the server with the {{HTTPHeader("Set-Cookie2")}} header, but has been **obsoleted**. Use {{HTTPHeader("Cookie")}} instead.
+- {{HTTPHeader("Set-Cookie2")}} {{deprecated_inline}}
+  - : Sends cookies from the server to the user-agent, but has been **obsoleted**. Use {{HTTPHeader("Set-Cookie")}} instead.
+
+## CORS
+
+_Learn more about CORS [here](CORS)._
+
+- {{HTTPHeader("Access-Control-Allow-Origin")}}
+  - : Indicates whether the response can be shared.
+- {{HTTPHeader("Access-Control-Allow-Credentials")}}
+  - : Indicates whether the response to the request can be exposed when the credentials flag is true.
+- {{HTTPHeader("Access-Control-Allow-Headers")}}
+  - : Used in response to a {{Glossary("Preflight_request", "preflight request")}} to indicate which HTTP headers can be used when making the actual request.
+- {{HTTPHeader("Access-Control-Allow-Methods")}}
+  - : Specifies the methods allowed when accessing the resource in response to a preflight request.
+- {{HTTPHeader("Access-Control-Expose-Headers")}}
+  - : Indicates which headers can be exposed as part of the response by listing their names.
+- {{HTTPHeader("Access-Control-Max-Age")}}
+  - : Indicates how long the results of a preflight request can be cached.
+- {{HTTPHeader("Access-Control-Request-Headers")}}
+  - : Used when issuing a preflight request to let the server know which HTTP headers will be used when the actual request is made.
+- {{HTTPHeader("Access-Control-Request-Method")}}
+  - : Used when issuing a preflight request to let the server know which [HTTP method](/en-US/docs/Web/HTTP/Methods) will be used when the actual request is made.
+- {{HTTPHeader("Origin")}}
+  - : Indicates where a fetch originates from.
+- {{HTTPHeader("Timing-Allow-Origin")}}
+  - : Specifies origins that are allowed to see values of attributes retrieved via features of the [Resource Timing API](/en-US/docs/Web/API/Resource_Timing_API), which would otherwise be reported as zero due to cross-origin restrictions.
+
+## Downloads
+
+- {{HTTPHeader("Content-Disposition")}}
+  - : Indicates if the resource transmitted should be displayed inline (default behavior without the header), or if it should be handled like a download and the browser should present a “Save As” dialog.
+
+## Message body information
+
+- {{HTTPHeader("Content-Length")}}
+  - : The size of the resource, in decimal number of bytes.
+- {{HTTPHeader("Content-Type")}}
+  - : Indicates the media type of the resource.
+- {{HTTPHeader("Content-Encoding")}}
+  - : Used to specify the compression algorithm.
+- {{HTTPHeader("Content-Language")}}
+  - : Describes the human language(s) intended for the audience, so that it allows a user to differentiate according to the users' own preferred language.
+- {{HTTPHeader("Content-Location")}}
+  - : Indicates an alternate location for the returned data.
+
+## Proxies
+
+- {{HTTPHeader("Forwarded")}}
+  - : Contains information from the client-facing side of proxy servers that is altered or lost when a proxy is involved in the path of the request.
+- {{HTTPHeader("X-Forwarded-For")}} {{non-standard_inline}}
+  - : Identifies the originating IP addresses of a client connecting to a web server through an HTTP proxy or a load balancer.
+- {{HTTPHeader("X-Forwarded-Host")}} {{non-standard_inline}}
+  - : Identifies the original host requested that a client used to connect to your proxy or load balancer.
+- {{HTTPHeader("X-Forwarded-Proto")}} {{non-standard_inline}}
+  - : Identifies the protocol (HTTP or HTTPS) that a client used to connect to your proxy or load balancer.
+- {{HTTPHeader("Via")}}
+  - : Added by proxies, both forward and reverse proxies, and can appear in the request headers and the response headers.
+
+## Redirects
+
+- {{HTTPHeader("Location")}}
+  - : Indicates the URL to redirect a page to.
+
+## Request context
+
+- {{HTTPHeader("From")}}
+  - : Contains an Internet email address for a human user who controls the requesting user agent.
+- {{HTTPHeader("Host")}}
+  - : Specifies the domain name of the server (for virtual hosting), and (optionally) the TCP port number on which the server is listening.
+- {{HTTPHeader("Referer")}}
+  - : The address of the previous web page from which a link to the currently requested page was followed.
+- {{HTTPHeader("Referrer-Policy")}}
+  - : Governs which referrer information sent in the {{HTTPHeader("Referer")}} header should be included with requests made.
+- {{HTTPHeader("User-Agent")}}
+  - : Contains a characteristic string that allows the network protocol peers to identify the application type, operating system, software vendor or software version of the requesting software user agent. See also the [Firefox user agent string reference](/en-US/docs/Web/HTTP/Headers/User-Agent/Firefox).
+
+## Response context
+
+- {{HTTPHeader("Allow")}}
+  - : Lists the set of HTTP request methods supported by a resource.
+- {{HTTPHeader("Server")}}
+  - : Contains information about the software used by the origin server to handle the request.
+
+## Range requests
+
+- {{HTTPHeader("Accept-Ranges")}}
+  - : Indicates if the server supports range requests, and if so in which unit the range can be expressed.
+- {{HTTPHeader("Range")}}
+  - : Indicates the part of a document that the server should return.
+- {{HTTPHeader("If-Range")}}
+  - : Creates a conditional range request that is only fulfilled if the given etag or date matches the remote resource. Used to prevent downloading two ranges from incompatible version of the resource.
+- {{HTTPHeader("Content-Range")}}
+  - : Indicates where in a full body message a partial message belongs.
+
+## Security
+
+- {{HTTPHeader("Cross-Origin-Embedder-Policy")}} (COEP)
+  - : Allows a server to declare an embedder policy for a given document.
+- {{HTTPHeader("Cross-Origin-Opener-Policy")}} (COOP)
+  - : Prevents other domains from opening/controlling a window.
+- {{HTTPHeader("Cross-Origin-Resource-Policy")}} (CORP)
+  - : Prevents other domains from reading the response of the resources to which this header is applied.
+- {{HTTPHeader("Content-Security-Policy")}} ({{Glossary("CSP")}})
+  - : Controls resources the user agent is allowed to load for a given page.
+- {{HTTPHeader("Content-Security-Policy-Report-Only")}}
+  - : Allows web developers to experiment with policies by monitoring, but not enforcing, their effects. These violation reports consist of {{Glossary("JSON")}} documents sent via an HTTP `POST` request to the specified URI.
+- {{HTTPHeader("Expect-CT")}}
+  - : Allows sites to opt in to reporting and/or enforcement of Certificate Transparency requirements, which prevents the use of misissued certificates for that site from going unnoticed. When a site enables the Expect-CT header, they are requesting that Chrome check that any certificate for that site appears in public CT logs.
+- {{HTTPHeader("Feature-Policy")}}
+  - : Provides a mechanism to allow and deny the use of browser features in its own frame, and in iframes that it embeds.
+- {{HTTPHeader("Origin-Isolation")}} {{experimental_inline}}
+  - : Provides a mechanism to allow web applications to isolate their origins.
+- {{HTTPHeader("Strict-Transport-Security")}} ({{Glossary("HSTS")}})
+  - : Force communication using HTTPS instead of HTTP.
+- {{HTTPHeader("Upgrade-Insecure-Requests")}}
+  - : Sends a signal to the server expressing the client’s preference for an encrypted and authenticated response, and that it can successfully handle the {{CSP("upgrade-insecure-requests")}} directive.
+- {{HTTPHeader("X-Content-Type-Options")}}
+  - : Disables MIME sniffing and forces browser to use the type given in {{HTTPHeader("Content-Type")}}.
+- {{HTTPHeader("X-Download-Options")}}
+  - : The [`X-Download-Options`](<https://docs.microsoft.com/en-us/previous-versions/windows/internet-explorer/ie-developer/compatibility/jj542450(v=vs.85)?#the-noopen-directive>) HTTP header indicates that the browser (Internet Explorer) should not display the option to "Open" a file that has been downloaded from an application, to prevent phishing attacks as the file otherwise would gain access to execute in the context of the application. (Note: related [MS Edge bug](https://developer.microsoft.com/en-us/microsoft-edge/platform/issues/18488178/)).
+- {{HTTPHeader("X-Frame-Options")}} (XFO)
+  - : Indicates whether a browser should be allowed to render a page in a {{HTMLElement("frame")}}, {{HTMLElement("iframe")}}, {{HTMLElement("embed")}} or {{HTMLElement("object")}}.
+- {{HTTPHeader("X-Permitted-Cross-Domain-Policies")}}
+  - : Specifies if a cross-domain policy file (`crossdomain.xml`) is allowed. The file may define a policy to grant clients, such as Adobe's Flash Player (now obsolete), Adobe Acrobat, Microsoft Silverlight (now obsolete), or Apache Flex, permission to handle data across domains that would otherwise be restricted due to the [Same-Origin Policy](/en-US/docs/Web/Security/Same-origin_policy). See the [Cross-domain Policy File Specification](https://www.adobe.com/devnet/articles/crossdomain_policy_file_spec.html) for more information.
+- {{HTTPHeader("X-Powered-By")}}
+  - : May be set by hosting environments or other frameworks and contains information about them while not providing any usefulness to the application or its visitors. Unset this header to avoid exposing potential vulnerabilities.
+- {{HTTPHeader("X-XSS-Protection")}}
+  - : Enables cross-site scripting filtering.
+
+### HTTP Public Key Pinning (HPKP)
+
+{{Glossary("HPKP", "HTTP Public Key Pinning")}} has been deprecated and removed in favor of Certificate Transparency and {{HTTPHeader("Expect-CT")}}.
+
+- {{HTTPHeader("Public-Key-Pins")}}
+  - : Associates a specific cryptographic public key with a certain web server to decrease the risk of {{Glossary("MITM")}} attacks with forged certificates.
+- {{HTTPHeader("Public-Key-Pins-Report-Only")}}
+  - : Sends reports to the report-uri specified in the header and does still allow clients to connect to the server even if the pinning is violated.
+
+### Fetch metadata request headers
+
+{{Glossary("Fetch metadata request header", "Fetch metadata request headers")}} provides information about the context from which the request originated. This allows a server to make decisions about whether a request should be allowed based on where the request came from and how the resource will be used.
+
+- {{HTTPHeader("Sec-Fetch-Site")}}
+  - : It is a request header that indicates the relationship between a request initiator's origin and its target's origin. It is a Structured Header whose value is a token with possible values `cross-site`, `same-origin`, `same-site`, and `none`.
+- {{HTTPHeader("Sec-Fetch-Mode")}}
+  - : It is a request header that indicates the request's mode to a server. It is a Structured Header whose value is a token with possible values `cors`, `navigate`, `no-cors`, `same-origin`, and `websocket`.
+- {{HTTPHeader("Sec-Fetch-User")}}
+  - : It is a request header that indicates whether or not a navigation request was triggered by user activation. It is a Structured Header whose value is a boolean so possible values are `?0` for false and `?1` for true.
+- {{HTTPHeader("Sec-Fetch-Dest")}}
+  - : It is a request header that indicates the request's destination to a server. It is a Structured Header whose value is a token with possible values `audio`, `audioworklet`, `document`, `embed`, `empty`, `font`, `image`, `manifest`, `object`, `paintworklet`, `report`, `script`, `serviceworker`, `sharedworker`, `style`, `track`, `video`, `worker`, and `xslt`.
+
+## Server-sent events
+
+- {{HTTPHeader("Last-Event-ID")}}
+  - : TBD
+- {{HTTPHeader("NEL")}} {{experimental_inline}}
+  - : Defines a mechanism that enables developers to declare a network error reporting policy.
+- {{HTTPHeader("Ping-From")}}
+  - : TBD
+- {{HTTPHeader("Ping-To")}}
+  - : TBD
+- {{HTTPHeader("Report-To")}}
+  - : Used to specify a server endpoint for the browser to send warning and error reports to.
+
+## Transfer coding
+
+- {{HTTPHeader("Transfer-Encoding")}}
+  - : Specifies the form of encoding used to safely transfer the resource to the user.
+- {{HTTPHeader("TE")}}
+  - : Specifies the transfer encodings the user agent is willing to accept.
+- {{HTTPHeader("Trailer")}}
+  - : Allows the sender to include additional fields at the end of chunked message.
+
+## WebSockets
+
+- {{HTTPHeader("Sec-WebSocket-Key")}}
+  - : TBD
+- {{HTTPHeader("Sec-WebSocket-Extensions")}}
+  - : TBD
+- {{HTTPHeader("Sec-WebSocket-Accept")}}
+  - : TBD
+- {{HTTPHeader("Sec-WebSocket-Protocol")}}
+  - : TBD
+- {{HTTPHeader("Sec-WebSocket-Version")}}
+  - : TBD
+
+## Other
+
+- {{HTTPHeader("Accept-Push-Policy")}} {{experimental_inline}}
+  - : A client can express the desired push policy for a request by sending an [`Accept-Push-Policy`](https://datatracker.ietf.org/doc/html/draft-ruellan-http-accept-push-policy-00#section-3.1) header field in the request.
+- {{HTTPHeader("Accept-Signature")}} {{experimental_inline}}
+  - : A client can send the [`Accept-Signature`](https://wicg.github.io/webpackage/draft-yasskin-http-origin-signed-responses.html#rfc.section.3.7) header field to indicate intention to take advantage of any available signatures and to indicate what kinds of signatures it supports.
+- {{HTTPHeader("Alt-Svc")}}
+  - : Used to list alternate ways to reach this service.
+- {{HTTPHeader("Date")}}
+  - : Contains the date and time at which the message was originated.
+- {{HTTPHeader("Early-Data")}} {{experimental_inline}}
+  - : Indicates that the request has been conveyed in TLS early data.
+- {{HTTPHeader("Large-Allocation")}}
+  - : Tells the browser that the page being loaded is going to want to perform a large allocation.
+- {{HTTPHeader("Link")}}
+  - : The [`Link`](https://datatracker.ietf.org/doc/html/rfc5988#section-5) entity-header field provides a means for serialising one or more links in HTTP headers. It is semantically equivalent to the HTML {{HTMLElement("link")}} element.
+- {{HTTPHeader("Push-Policy")}} {{experimental_inline}}
+  - : A [`Push-Policy`](https://datatracker.ietf.org/doc/html/draft-ruellan-http-accept-push-policy-00#section-3.2) defines the server behavior regarding push when processing a request.
+- {{HTTPHeader("Retry-After")}}
+  - : Indicates how long the user agent should wait before making a follow-up request.
+- {{HTTPHeader("Signature")}} {{experimental_inline}}
+  - : The [`Signature`](https://wicg.github.io/webpackage/draft-yasskin-http-origin-signed-responses.html#rfc.section.3.1) header field conveys a list of signatures for an exchange, each one accompanied by information about how to determine the authority of and refresh that signature.
+- {{HTTPHeader("Signed-Headers")}} {{experimental_inline}}
+  - : The [`Signed-Headers`](https://wicg.github.io/webpackage/draft-yasskin-http-origin-signed-responses.html#rfc.section.5.1.2) header field identifies an ordered list of response header fields to include in a signature.
+- {{HTTPHeader("Server-Timing")}}
+  - : Communicates one or more metrics and descriptions for the given request-response cycle.
+- {{HTTPHeader("Service-Worker-Allowed")}}
+  - : Used to remove the [path restriction](https://w3c.github.io/ServiceWorker/#path-restriction) by including this header [in the response of the Service Worker script](https://w3c.github.io/ServiceWorker/#service-worker-script-response).
+- {{HTTPHeader("SourceMap")}}
+  - : Links generated code to a [source map](/en-US/docs/Tools/Debugger/How_to/Use_a_source_map).
+- {{HTTPHeader("Upgrade")}}
+  - : The relevant RFC document for the [Upgrade header field is RFC 7230, section 6.7](https://datatracker.ietf.org/doc/html/rfc7230#section-6.7). The standard establishes rules for upgrading or changing to a different protocol on the current client, server, transport protocol connection. For example, this header standard allows a client to change from HTTP 1.1 to HTTP 2.0, assuming the server decides to acknowledge and implement the Upgrade header field. Neither party is required to accept the terms specified in the Upgrade header field. It can be used in both client and server headers. If the Upgrade header field is specified, then the sender MUST also send the Connection header field with the upgrade option specified. For details on the Connection header field [please see section 6.1 of the aforementioned RFC](https://datatracker.ietf.org/doc/html/rfc7230#section-6.1).
+- {{HTTPHeader("X-DNS-Prefetch-Control")}}
+  - : Controls DNS prefetching, a feature by which browsers proactively perform domain name resolution on both links that the user may choose to follow as well as URLs for items referenced by the document, including images, CSS, JavaScript, and so forth.
+- {{HTTPHeader("X-Firefox-Spdy")}} {{deprecated_inline}} {{non-standard_inline}}
+  - : TBD
+- {{HTTPHeader("X-Pingback")}} {{non-standard_inline}}
+  - : TBD
+- {{HTTPHeader("X-Requested-With")}}
+  - : TBD
+- {{HTTPHeader("X-Robots-Tag")}}{{non-standard_inline}}
+  - : The [`X-Robots-Tag`](https://developers.google.com/search/reference/robots_meta_tag#xrobotstag) HTTP header is used to indicate how a web page is to be indexed within public search engine results. The header is effectively equivalent to `<meta name="robots" content="...">`.
+- {{HTTPHeader("X-UA-Compatible")}} {{non-standard_inline}}
+  - : Used by Internet Explorer to signal which document mode to use.
+
+## Contributing
+
+You can help by [writing new entries](/en-US/docs/MDN/Contribute/Howto/Document_an_HTTP_header) or improving the existing ones.
+
+## See also
+
+- [Wikipedia page on List of HTTP headers](https://en.wikipedia.org/wiki/List_of_HTTP_header_fields)
+- [IANA registry](https://www.iana.org/assignments/message-headers/perm-headers.html)
+- [HTTP Working Group](https://httpwg.org/specs/)
diff --git a/files/en-us/web/http/headers/keep-alive/index.md b/files/en-us/web/http/headers/keep-alive/index.md
index a4087bf4466ec8a..7bed22ca0b9d491 100644
--- a/files/en-us/web/http/headers/keep-alive/index.md
+++ b/files/en-us/web/http/headers/keep-alive/index.md
@@ -9,74 +9,70 @@ tags:
   - Reference
 browser-compat: http.headers.Keep-Alive
 ---
-<div>{{HTTPSidebar}}</div>
+{{HTTPSidebar}}
 
-<p>The <strong><code>Keep-Alive</code></strong> general header allows the sender to hint about how the connection may be used to set a timeout and a maximum amount of requests.</p>
+The **`Keep-Alive`** general header allows the sender to hint about how the connection may be used to set a timeout and a maximum amount of requests.
 
-<div class="notecard note">
-  <p><strong>Note:</strong> The {{HTTPHeader("Connection")}} header needs to be set to "keep-alive" for this header to have any meaning.</p>
-</div>
+> **Note:** The {{HTTPHeader("Connection")}} header needs to be set to "keep-alive" for this header to have any meaning.
 
-<div class="notecard warning">
-  <p><strong>Warning:</strong> Connection-specific header fields such as {{HTTPHeader("Connection")}} and {{HTTPHeader("Keep-Alive")}} are <a href="https://datatracker.ietf.org/doc/html/rfc7540#section-8.1.2.2">prohibited in HTTP/2</a>. Chrome and Firefox ignore them in HTTP/2 responses, but Safari conforms to the HTTP/2 spec requirements and won't load any response which contains them.</p>
-</div>
+> **Warning:** Connection-specific header fields such as {{HTTPHeader("Connection")}} and {{HTTPHeader("Keep-Alive")}} are [prohibited in HTTP/2](https://datatracker.ietf.org/doc/html/rfc7540#section-8.1.2.2). Chrome and Firefox ignore them in HTTP/2 responses, but Safari conforms to the HTTP/2 spec requirements and won't load any response which contains them.
 
 <table class="properties">
- <tbody>
-  <tr>
-   <th scope="row">Header type</th>
-   <td>{{Glossary("Request header")}}, {{Glossary("Response header")}}</td>
-  </tr>
-  <tr>
-   <th scope="row">{{Glossary("Forbidden header name")}}</th>
-   <td>yes</td>
-  </tr>
- </tbody>
+  <tbody>
+    <tr>
+      <th scope="row">Header type</th>
+      <td>
+        {{Glossary("Request header")}},
+        {{Glossary("Response header")}}
+      </td>
+    </tr>
+    <tr>
+      <th scope="row">{{Glossary("Forbidden header name")}}</th>
+      <td>yes</td>
+    </tr>
+  </tbody>
 </table>
 
-<h2 id="Syntax">Syntax</h2>
+## Syntax
 
-<pre class="brush: html">Keep-Alive: <var>parameters</var></pre>
+```html
+Keep-Alive: parameters
+```
 
-<h2 id="Directives">Directives</h2>
+## Directives
 
-<dl>
- <dt><code><var>parameters</var></code></dt>
- <dd>A comma-separated list of parameters, each consisting of an identifier and a value separated by the equal sign (<code>'='</code>). The following identifiers are possible:
- <ul>
-  <li><code>timeout</code>: An integer representing the time in seconds that the host will allow an idle connection to remain open before it is closed. A connection is idle if no data is sent or received by a host. A host may keep an idle connection open for longer than <code>timeout</code> seconds, but the host should attempt to retain a connection for at least <code>timeout</code> seconds.</li>
-  <li><code>max</code>: indicating the maximum number of requests that can be sent on this connection before closing it. Unless <code>0</code>, this value is ignored for non-pipelined connections as another request will be sent in the next response. An HTTP pipeline can use it to limit the pipelining.</li>
- </ul>
- </dd>
-</dl>
+- `parameters`
 
-<h2 id="Examples">Examples</h2>
+  - : A comma-separated list of parameters, each consisting of an identifier and a value separated by the equal sign (`'='`). The following identifiers are possible:
 
-<p>A response containing a <code>Keep-Alive</code> header:</p>
+    - `timeout`: An integer representing the time in seconds that the host will allow an idle connection to remain open before it is closed. A connection is idle if no data is sent or received by a host. A host may keep an idle connection open for longer than `timeout` seconds, but the host should attempt to retain a connection for at least `timeout` seconds.
+    - `max`: indicating the maximum number of requests that can be sent on this connection before closing it. Unless `0`, this value is ignored for non-pipelined connections as another request will be sent in the next response. An HTTP pipeline can use it to limit the pipelining.
 
-<pre>HTTP/1.1 200 OK
-<strong>Connection: Keep-Alive</strong>
-Content-Encoding: gzip
-Content-Type: text/html; charset=utf-8
-Date: Thu, 11 Aug 2016 15:23:13 GMT
-<strong>Keep-Alive: timeout=5, max=1000</strong>
-Last-Modified: Mon, 25 Jul 2016 04:32:39 GMT
-Server: Apache
+## Examples
 
-(body)</pre>
+A response containing a `Keep-Alive` header:
 
-<h2 id="Specifications">Specifications</h2>
+    HTTP/1.1 200 OK
+    Connection: Keep-Alive
+    Content-Encoding: gzip
+    Content-Type: text/html; charset=utf-8
+    Date: Thu, 11 Aug 2016 15:23:13 GMT
+    Keep-Alive: timeout=5, max=1000
+    Last-Modified: Mon, 25 Jul 2016 04:32:39 GMT
+    Server: Apache
+
+    (body)
+
+## Specifications
 
 {{Specifications}}
 
-<h2 id="Browser_compatibility">Browser compatibility</h2>
+## Browser compatibility
 
-<p>{{Compat}}</p>
+{{Compat}}
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
- <li>{{HTTPHeader("Connection")}}</li>
- <li><a href="/en-US/docs/Web/HTTP/Connection_management_in_HTTP_1.x">Connection management in HTTP/1.x</a></li>
- <li><a href="https://datatracker.ietf.org/doc/html/draft-thomson-hybi-http-timeout-03#section-2">Keep-Alive Header</a> IETF Internet Draft</li>
-</ul>
+- {{HTTPHeader("Connection")}}
+- [Connection management in HTTP/1.x](/en-US/docs/Web/HTTP/Connection_management_in_HTTP_1.x)
+- [Keep-Alive Header](https://datatracker.ietf.org/doc/html/draft-thomson-hybi-http-timeout-03#section-2) IETF Internet Draft
diff --git a/files/en-us/web/http/headers/large-allocation/index.md b/files/en-us/web/http/headers/large-allocation/index.md
index aad7e7d8b26abc0..5efd6ba83cca979 100644
--- a/files/en-us/web/http/headers/large-allocation/index.md
+++ b/files/en-us/web/http/headers/large-allocation/index.md
@@ -10,19 +10,18 @@ tags:
   - header
 browser-compat: http.headers.Large-Allocation
 ---
-<div>{{HTTPSidebar}}</div>
+{{HTTPSidebar}}
 
-<p>The non-standard <strong><code>Large-Allocation</code></strong> response header tells
-  the browser that the page being loaded is going to want to perform a large allocation.
-  It is currently only implemented in Firefox, but is harmless to send to every browser.
-</p>
+The non-standard **`Large-Allocation`** response header tells
+the browser that the page being loaded is going to want to perform a large allocation.
+It is currently only implemented in Firefox, but is harmless to send to every browser.
 
-<p><a href="/en-US/docs/WebAssembly">WebAssembly</a> or asm.js applications can use large
-  contiguous blocks of allocated memory. For complex games, for example, these allocations
-  can be quite large, sometimes as large as 1GB. The <code>Large-Allocation</code> tells
-  the browser that the web content in the to-be-loaded page is going to want to perform a
-  large contiguous memory allocation and the browser can react to this header by starting
-  a dedicated process for the to-be-loaded document, for example.</p>
+[WebAssembly](/en-US/docs/WebAssembly) or asm.js applications can use large
+contiguous blocks of allocated memory. For complex games, for example, these allocations
+can be quite large, sometimes as large as 1GB. The `Large-Allocation` tells
+the browser that the web content in the to-be-loaded page is going to want to perform a
+large contiguous memory allocation and the browser can react to this header by starting
+a dedicated process for the to-be-loaded document, for example.
 
 <table class="properties">
   <tbody>
@@ -37,96 +36,86 @@ browser-compat: http.headers.Large-Allocation
   </tbody>
 </table>
 
-<h2 id="Syntax">Syntax</h2>
+## Syntax
 
-<pre class="brush: html">Large-Allocation: 0
-Large-Allocation: &lt;megabytes&gt;
-</pre>
+```html
+Large-Allocation: 0
+Large-Allocation: <megabytes>
+```
 
-<h2 id="Directives">Directives</h2>
+## Directives
 
-<dl>
-  <dt><code>0</code></dt>
-  <dd>0 is a special value which represents uncertainty as to what the size of the
-    allocation is.</dd>
-  <dt><code>&lt;megabytes&gt;</code></dt>
-  <dd>The expected size of the allocation to be performed, in megabytes.</dd>
-</dl>
+- `0`
+  - : 0 is a special value which represents uncertainty as to what the size of the
+    allocation is.
+- `<megabytes>`
+  - : The expected size of the allocation to be performed, in megabytes.
 
-<h2 id="Examples">Examples</h2>
+## Examples
 
-<pre>Large-Allocation: 0
-Large-Allocation: 500
-</pre>
+    Large-Allocation: 0
+    Large-Allocation: 500
 
-<h2 id="Troubleshooting_errors">Troubleshooting errors</h2>
+## Troubleshooting errors
 
-<p>The <code>Large-Allocation</code> header throws warnings or error messages when used
-  incorrectly. You'll encounter them in the <a href="/en-US/docs/Tools/Web_Console">web
-    console</a>.</p>
+The `Large-Allocation` header throws warnings or error messages when used
+incorrectly. You'll encounter them in the [web
+console](/en-US/docs/Tools/Web_Console).
 
-<dl>
-  <dt>This page was loaded in a new process due to a <code>Large-Allocation</code> header.
-  </dt>
-  <dd>This message means that the browser saw the <code>Large-Allocation</code> header,
+- This page was loaded in a new process due to a `Large-Allocation` header.
+  - : This message means that the browser saw the `Large-Allocation` header,
     and was able to reload the page into a new process which should have more available
-    contiguous memory.</dd>
-  <dt>A <code>Large-Allocation</code> header was ignored due to the load being triggered
-    by a non-GET request.</dt>
-  <dd>When a {{HTTPMethod("POST")}} request is used to load a document, that load cannot
+    contiguous memory.
+- A `Large-Allocation` header was ignored due to the load being triggered
+  by a non-GET request.
+  - : When a {{HTTPMethod("POST")}} request is used to load a document, that load cannot
     currently be redirected into a new process. This error is displayed when loading a
-    document with a <code>Large-Allocation</code> header with a non-GET HTTP method. This
+    document with a `Large-Allocation` header with a non-GET HTTP method. This
     could be caused due to the document being loaded by a form submission, for example.
-  </dd>
-  <dt>A <code>Large-Allocation</code> header was ignored due to the presence of windows
-    which have a reference to this browsing context through the frame hierarchy or
-    {{domxref("window.opener")}}.</dt>
-  <dd>
-    <p>This error means that the document was not loaded at the top level of an
-      user-opened or noopener-opened tab or window. It can occur in these situations:</p>
-
-    <ul>
-      <li>The document with the <code>Large-Allocation</code> header was loaded in an
-        {{HTMLElement("iframe")}}. Firefox cannot move an iframe into a new process
-        currently, so the document must load in the current process.</li>
-      <li>The document with the <code>Large-Allocation</code> header was loaded in a
-        window which was opened by {{domxref("window.open()")}},
-        <code>&lt;a target="_blank"&gt;</code> or other similar methods without
-        <code>rel="noopener"</code> or the <code>"noopener"</code> feature being set.
-        These windows must remain in the same process as their opener, as they can
-        communicate, meaning that we cannot allow them to switch processes.</li>
-      <li>The document with the <code>Large-Allocation header</code> has opened another
-        window with {{domxref("window.open()")}}, <code>&lt;a target="_blank"&gt;</code>
-        or other similar methods without <code>rel="noopener"</code> or the
-        <code>"noopener"</code> feature being set. This is for the same reason as above,
-        namely that they can communicate and thus we cannot allow them to switch
-        processes.</li>
-    </ul>
-  </dd>
-  <dt>This page would be loaded in a new process due to a <code>Large-Allocation</code>
-    header, however <code>Large-Allocation</code> process creation is disabled on
-    non-Win32 platforms.</dt>
-  <dd>Firefox currently only supports the <code>Large-Allocation</code> header in our
+- A `Large-Allocation` header was ignored due to the presence of windows
+  which have a reference to this browsing context through the frame hierarchy or
+  {{domxref("window.opener")}}.
+
+  - : This error means that the document was not loaded at the top level of an
+    user-opened or noopener-opened tab or window. It can occur in these situations:
+
+    - The document with the `Large-Allocation` header was loaded in an
+      {{HTMLElement("iframe")}}. Firefox cannot move an iframe into a new process
+      currently, so the document must load in the current process.
+    - The document with the `Large-Allocation` header was loaded in a
+      window which was opened by {{domxref("window.open()")}},
+      `<a target="_blank">` or other similar methods without
+      `rel="noopener"` or the `"noopener"` feature being set.
+      These windows must remain in the same process as their opener, as they can
+      communicate, meaning that we cannot allow them to switch processes.
+    - The document with the `Large-Allocation header` has opened another
+      window with {{domxref("window.open()")}}, `<a target="_blank">`
+      or other similar methods without `rel="noopener"` or the
+      `"noopener"` feature being set. This is for the same reason as above,
+      namely that they can communicate and thus we cannot allow them to switch
+      processes.
+
+- This page would be loaded in a new process due to a `Large-Allocation`
+  header, however `Large-Allocation` process creation is disabled on
+  non-Win32 platforms.
+
+  - : Firefox currently only supports the `Large-Allocation` header in our
     32-bit Windows builds, as memory fragmentation is not an issue in 64-bit builds. If
     you are running a non-win32 version of Firefox, this error will appear. This check can
     be disabled with the "dom.largeAllocation.
-    <p>forceEnable" boolean preferece in about:config.</p>
-  </dd>
-</dl>
 
-<h2 id="Specifications">Specifications</h2>
+    forceEnable" boolean preferece in about:config.
 
-<p>Not part of any current specifications. An explainer of the ideas behind this header
-  can be found in <a
-    href="https://gist.github.com/mystor/5739e222e398efc6c29108be55eb6fe3">this
-    document</a>.</p>
+## Specifications
 
-<h2 id="Browser_compatibility">Browser compatibility</h2>
+Not part of any current specifications. An explainer of the ideas behind this header
+can be found in [this
+document](https://gist.github.com/mystor/5739e222e398efc6c29108be55eb6fe3).
 
-<p>{{Compat}}</p>
+## Browser compatibility
 
-<h2 id="See_also">See also</h2>
+{{Compat}}
 
-<ul>
-  <li><a href="/en-US/docs/WebAssembly">WebAssembly</a></li>
-</ul>
+## See also
+
+- [WebAssembly](/en-US/docs/WebAssembly)
diff --git a/files/en-us/web/http/headers/last-modified/index.md b/files/en-us/web/http/headers/last-modified/index.md
index 20571df647c5515..9001eadaf4851c0 100644
--- a/files/en-us/web/http/headers/last-modified/index.md
+++ b/files/en-us/web/http/headers/last-modified/index.md
@@ -2,20 +2,20 @@
 title: Last-Modified
 slug: Web/HTTP/Headers/Last-Modified
 tags:
-- HTTP
-- HTTP Header
-- Reference
-- Response Header
+  - HTTP
+  - HTTP Header
+  - Reference
+  - Response Header
 browser-compat: http.headers.Last-Modified
 ---
-<div>{{HTTPSidebar}}</div>
+{{HTTPSidebar}}
 
-<p>The <strong><code>Last-Modified</code></strong> response HTTP header contains the date
-  and time at which the origin server believes the resource was last modified. It is used
-  as a validator to determine if a resource received or stored is the same. Less accurate
-  than an {{HTTPHeader("ETag")}} header, it is a fallback mechanism. Conditional requests
-  containing {{HTTPHeader("If-Modified-Since")}} or {{HTTPHeader("If-Unmodified-Since")}}
-  headers make use of this field.</p>
+The **`Last-Modified`** response HTTP header contains the date
+and time at which the origin server believes the resource was last modified. It is used
+as a validator to determine if a resource received or stored is the same. Less accurate
+than an {{HTTPHeader("ETag")}} header, it is a fallback mechanism. Conditional requests
+containing {{HTTPHeader("If-Modified-Since")}} or {{HTTPHeader("If-Unmodified-Since")}}
+headers make use of this field.
 
 <table class="properties">
   <tbody>
@@ -28,59 +28,54 @@ browser-compat: http.headers.Last-Modified
       <td>no</td>
     </tr>
     <tr>
-      <th scope="row">{{Glossary("CORS-safelisted response header")}}</th>
+      <th scope="row">
+        {{Glossary("CORS-safelisted response header")}}
+      </th>
       <td>yes</td>
     </tr>
   </tbody>
 </table>
 
-<h2 id="Syntax">Syntax</h2>
+## Syntax
 
-<pre class="brush: html">Last-Modified: &lt;day-name&gt;, &lt;day&gt; &lt;month&gt; &lt;year&gt; &lt;hour&gt;:&lt;minute&gt;:&lt;second&gt; GMT
-</pre>
+```html
+Last-Modified: <day-name>, <day> <month> <year> <hour>:<minute>:<second> GMT
+```
 
-<h2 id="Directives">Directives</h2>
+## Directives
 
-<dl>
-  <dt>&lt;day-name&gt;</dt>
-  <dd>One of "Mon", "Tue", "Wed", "Thu", "Fri", "Sat", or "Sun" (case-sensitive).</dd>
-  <dt>&lt;day&gt;</dt>
-  <dd>2 digit day number, e.g. "04" or "23".</dd>
-  <dt>&lt;month&gt;</dt>
-  <dd>One of "Jan", "Feb", "Mar", "Apr", "May", "Jun", "Jul", "Aug", "Sep", "Oct", "Nov",
-    "Dec" (case sensitive).</dd>
-  <dt>&lt;year&gt;</dt>
-  <dd>4 digit year number, e.g. "1990" or "2016".</dd>
-  <dt>&lt;hour&gt;</dt>
-  <dd>2 digit hour number, e.g. "09" or "23".</dd>
-  <dt>&lt;minute&gt;</dt>
-  <dd>2 digit minute number, e.g. "04" or "59".</dd>
-  <dt>&lt;second&gt;</dt>
-  <dd>2 digit second number, e.g. "04" or "59".</dd>
-  <dt><code>GMT</code></dt>
-  <dd>
-    <p>Greenwich Mean Time. HTTP dates are always expressed in GMT, never in local time.
-    </p>
-  </dd>
-</dl>
+- \<day-name>
+  - : One of "Mon", "Tue", "Wed", "Thu", "Fri", "Sat", or "Sun" (case-sensitive).
+- \<day>
+  - : 2 digit day number, e.g. "04" or "23".
+- \<month>
+  - : One of "Jan", "Feb", "Mar", "Apr", "May", "Jun", "Jul", "Aug", "Sep", "Oct", "Nov",
+    "Dec" (case sensitive).
+- \<year>
+  - : 4 digit year number, e.g. "1990" or "2016".
+- \<hour>
+  - : 2 digit hour number, e.g. "09" or "23".
+- \<minute>
+  - : 2 digit minute number, e.g. "04" or "59".
+- \<second>
+  - : 2 digit second number, e.g. "04" or "59".
+- `GMT`
+  - : Greenwich Mean Time. HTTP dates are always expressed in GMT, never in local time.
 
-<h2 id="Examples">Examples</h2>
+## Examples
 
-<pre>Last-Modified: Wed, 21 Oct 2015 07:28:00 GMT
-</pre>
+    Last-Modified: Wed, 21 Oct 2015 07:28:00 GMT
 
-<h2 id="Specifications">Specifications</h2>
+## Specifications
 
 {{Specifications}}
 
-<h2 id="Browser_compatibility">Browser compatibility</h2>
+## Browser compatibility
 
-<p>{{Compat}}</p>
+{{Compat}}
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
-  <li>{{HTTPHeader("If-Modified-Since")}}</li>
-  <li>{{HTTPHeader("If-Unmodified-Since")}}</li>
-  <li>{{HTTPHeader("Etag")}}</li>
-</ul>
+- {{HTTPHeader("If-Modified-Since")}}
+- {{HTTPHeader("If-Unmodified-Since")}}
+- {{HTTPHeader("Etag")}}
diff --git a/files/en-us/web/http/headers/link/index.md b/files/en-us/web/http/headers/link/index.md
index 4cd05ff43299182..66e81b6db920734 100644
--- a/files/en-us/web/http/headers/link/index.md
+++ b/files/en-us/web/http/headers/link/index.md
@@ -12,47 +12,49 @@ tags:
   - Reference
 browser-compat: http.headers.Link
 ---
-<div>{{HTTPSidebar}}</div>
+{{HTTPSidebar}}
 
-<p>The HTTP <strong><code>Link</code></strong> entity-header field provides a means for serialising one or more links in HTTP headers. It is semantically equivalent to the HTML {{HTMLElement("link")}} element.</p>
+The HTTP **`Link`** entity-header field provides a means for serialising one or more links in HTTP headers. It is semantically equivalent to the HTML {{HTMLElement("link")}} element.
 
-<h2 id="Syntax">Syntax</h2>
+## Syntax
 
-<pre class="brush: html">Link: &lt; <var>uri-reference</var> &gt;; <var>param1</var>=<var>value1</var>; <var>param2</var>="<var>value2</var>"</pre>
+```html
+Link: < uri-reference >; param1=value1; param2="value2"
+```
 
-<dl>
- <dt><code>&lt;uri-reference&gt;</code></dt>
- <dd>The URI reference, must be enclosed between <code>&lt;</code> and <code>&gt;</code>.</dd>
-</dl>
+- `<uri-reference>`
+  - : The URI reference, must be enclosed between `<` and `>`.
 
-<h3 id="Parameters">Parameters</h3>
+### Parameters
 
-<p>The link header contains parameters, which are separated with <code>;</code> and are equivalent to attributes of the {{HTMLElement("link")}} element.</p>
+The link header contains parameters, which are separated with `;` and are equivalent to attributes of the {{HTMLElement("link")}} element.
 
-<h2 id="Examples">Examples</h2>
+## Examples
 
-<p>The URI (absolute or relative) must be enclosed between <code>&lt;</code> and <code>&gt;</code>:</p>
+The URI (absolute or relative) must be enclosed between `<` and `>`:
 
-<pre class="example-good">Link: &lt;https://example.com&gt;; rel="preconnect"</pre>
+```plain example-good
+Link: <https://example.com>; rel="preconnect"
+```
 
-<pre class="example-bad">Link: https://bad.example; rel="preconnect"</pre>
+```plain example-bad
+Link: https://bad.example; rel="preconnect"
+```
 
-<h3 id="Specifying_multiple_links">Specifying multiple links</h3>
+### Specifying multiple links
 
-<p>You can specify multiple links separated by commas, for example:</p>
+You can specify multiple links separated by commas, for example:
 
-<pre>Link: &lt;https://one.example.com&gt;; rel="preconnect", &lt;https://two.example.com&gt;; rel="preconnect", &lt;https://three.example.com&gt;; rel="preconnect"</pre>
+    Link: <https://one.example.com>; rel="preconnect", <https://two.example.com>; rel="preconnect", <https://three.example.com>; rel="preconnect"
 
-<h2 id="Specifications">Specifications</h2>
+## Specifications
 
 {{Specifications}}
 
-<h2 id="Browser_compatibility">Browser compatibility</h2>
+## Browser compatibility
 
-<p>{{Compat}}</p>
+{{Compat}}
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
- <li>{{HTTPStatus(103, "103 Early Hints")}}</li>
-</ul>
+- {{HTTPStatus(103, "103 Early Hints")}}
diff --git a/files/en-us/web/http/headers/location/index.md b/files/en-us/web/http/headers/location/index.md
index 40d9c2a440d1451..1f5dd6cc39bce50 100644
--- a/files/en-us/web/http/headers/location/index.md
+++ b/files/en-us/web/http/headers/location/index.md
@@ -2,44 +2,41 @@
 title: Location
 slug: Web/HTTP/Headers/Location
 tags:
-- HTTP
-- HTTP Header
-- Reference
-- Response Header
+  - HTTP
+  - HTTP Header
+  - Reference
+  - Response Header
 browser-compat: http.headers.Location
 ---
-<div>{{HTTPSidebar}}</div>
-
-<p>The <strong><code>Location</code></strong> response header indicates the URL to
-  redirect a page to. It only provides a meaning when served with a
-  <code>3xx</code> (redirection) or <code>201</code> (created) status response.</p>
-
-<p>In cases of redirection, the HTTP method used to make the new request to fetch the page
-  pointed to by <code>Location</code> depends of the original method and of the kind of
-  redirection:</p>
-
-<ul>
-  <li>If {{HTTPStatus("303")}} (See Also) responses always lead to the use of a
-    {{HTTPMethod("GET")}} method, {{HTTPStatus("307")}} (Temporary Redirect) and
-    {{HTTPStatus("308")}} (Permanent Redirect) don't change the method used in the
-    original request;</li>
-  <li>{{HTTPStatus("301")}} (Moved Permanently) and {{HTTPStatus("302")}} (Found) doesn't
-    change the method most of the time, though older user-agents may (so you basically
-    don't know).</li>
-</ul>
-
-<p>All responses with one of these status codes send a <code>Location</code> header.</p>
-
-<p>In cases of resource creation, it indicates the URL to the newly created resource.</p>
-
-<p><code>Location</code> and {{HTTPHeader("Content-Location")}} are different:
-  <code>Location</code> indicates the target of a redirection (or the URL of a newly
-  created resource), while {{HTTPHeader("Content-Location")}} indicates the direct URL to
-  use to access the resource when <a
-    href="/en-US/docs/Web/HTTP/Content_negotiation">content negotiation</a> happened,
-  without the need of further content negotiation. <code>Location</code> is a header
-  associated with the response, while {{HTTPHeader("Content-Location")}} is associated
-  with the entity returned.</p>
+{{HTTPSidebar}}
+
+The **`Location`** response header indicates the URL to
+redirect a page to. It only provides a meaning when served with a
+`3xx` (redirection) or `201` (created) status response.
+
+In cases of redirection, the HTTP method used to make the new request to fetch the page
+pointed to by `Location` depends of the original method and of the kind of
+redirection:
+
+- If {{HTTPStatus("303")}} (See Also) responses always lead to the use of a
+  {{HTTPMethod("GET")}} method, {{HTTPStatus("307")}} (Temporary Redirect) and
+  {{HTTPStatus("308")}} (Permanent Redirect) don't change the method used in the
+  original request;
+- {{HTTPStatus("301")}} (Moved Permanently) and {{HTTPStatus("302")}} (Found) doesn't
+  change the method most of the time, though older user-agents may (so you basically
+  don't know).
+
+All responses with one of these status codes send a `Location` header.
+
+In cases of resource creation, it indicates the URL to the newly created resource.
+
+`Location` and {{HTTPHeader("Content-Location")}} are different:
+`Location` indicates the target of a redirection (or the URL of a newly
+created resource), while {{HTTPHeader("Content-Location")}} indicates the direct URL to
+use to access the resource when [content negotiation](/en-US/docs/Web/HTTP/Content_negotiation) happened,
+without the need of further content negotiation. `Location` is a header
+associated with the response, while {{HTTPHeader("Content-Location")}} is associated
+with the entity returned.
 
 <table class="properties">
   <tbody>
@@ -54,35 +51,32 @@ browser-compat: http.headers.Location
   </tbody>
 </table>
 
-<h2 id="Syntax">Syntax</h2>
+## Syntax
 
-<pre class="brush: html">Location: &lt;url&gt;
-</pre>
+```html
+Location: <url>
+```
 
-<h2 id="Directives">Directives</h2>
+## Directives
 
-<dl>
-  <dt>&lt;url&gt;</dt>
-  <dd>A relative (to the request URL) or absolute URL.</dd>
-</dl>
+- \<url>
+  - : A relative (to the request URL) or absolute URL.
 
-<h2 id="Examples">Examples</h2>
+## Examples
 
-<pre>Location: /index.html</pre>
+    Location: /index.html
 
-<h2 id="Specifications">Specifications</h2>
+## Specifications
 
 {{Specifications}}
 
-<h2 id="Browser_compatibility">Browser compatibility</h2>
+## Browser compatibility
 
-<p>{{Compat}}</p>
+{{Compat}}
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
-  <li>{{HTTPHeader("Content-Location")}}</li>
-  <li>Status of responses including a <code>Location</code> header: {{HTTPStatus("201")}},
-    {{HTTPStatus("301")}}, {{HTTPStatus("302")}}, {{HTTPStatus("303")}},
-    {{HTTPStatus("307")}}, {{HTTPStatus("308")}}.</li>
-</ul>
+- {{HTTPHeader("Content-Location")}}
+- Status of responses including a `Location` header: {{HTTPStatus("201")}},
+  {{HTTPStatus("301")}}, {{HTTPStatus("302")}}, {{HTTPStatus("303")}},
+  {{HTTPStatus("307")}}, {{HTTPStatus("308")}}.
diff --git a/files/en-us/web/http/headers/nel/index.md b/files/en-us/web/http/headers/nel/index.md
index aecc6e5fe7da161..f31fb90de91f9b7 100644
--- a/files/en-us/web/http/headers/nel/index.md
+++ b/files/en-us/web/http/headers/nel/index.md
@@ -10,36 +10,35 @@ tags:
   - header
 browser-compat: http.headers.NEL
 ---
-<div>{{HTTPSidebar}}</div>
+{{HTTPSidebar}}
 
-<p>The HTTP <strong><code>NEL</code></strong> response header is used to configure network request logging.</p>
+The HTTP **`NEL`** response header is used to configure network request logging.
 
 <table class="properties">
- <tbody>
-  <tr>
-   <th scope="row">Header type</th>
-   <td>{{Glossary("Response header")}}</td>
-  </tr>
-  <tr>
-   <th scope="row">{{Glossary("Forbidden header name")}}</th>
-   <td>no</td>
-  </tr>
- </tbody>
+  <tbody>
+    <tr>
+      <th scope="row">Header type</th>
+      <td>{{Glossary("Response header")}}</td>
+    </tr>
+    <tr>
+      <th scope="row">{{Glossary("Forbidden header name")}}</th>
+      <td>no</td>
+    </tr>
+  </tbody>
 </table>
 
-<h2 id="Syntax">Syntax</h2>
+## Syntax
 
-<pre class="brush: html">NEL: { "report_to": "name_of_reporting_group", "max_age": 12345, "include_subdomains": false, "success_fraction": 0.0, "failure_fraction": 1.0 }
-</pre>
+```html
+NEL: { "report_to": "name_of_reporting_group", "max_age": 12345, "include_subdomains": false, "success_fraction": 0.0, "failure_fraction": 1.0 }
+```
 
 {{Specifications}}
 
-<h2 id="Browser_compatibility">Browser compatibility</h2>
+## Browser compatibility
 
-<p>{{Compat}}</p>
+{{Compat}}
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
- <li><a href="/en-US/docs/Web/HTTP/Network_Error_Logging">Network Error Logging (NEL) explainer</a></li>
-</ul>
+- [Network Error Logging (NEL) explainer](/en-US/docs/Web/HTTP/Network_Error_Logging)
diff --git a/files/en-us/web/http/headers/origin/index.md b/files/en-us/web/http/headers/origin/index.md
index 1461593c1bc78d0..dd347a4fea3aa01 100644
--- a/files/en-us/web/http/headers/origin/index.md
+++ b/files/en-us/web/http/headers/origin/index.md
@@ -9,66 +9,61 @@ tags:
   - origin
 browser-compat: http.headers.Origin
 ---
-<div>{{HTTPSidebar}}</div>
+{{HTTPSidebar}}
 
-<p>The <strong><code>Origin</code></strong> request header indicates where a request originates from. It doesn't include any path information. It is similar to the {{HTTPHeader("Referer")}} header, but, unlike that header, it doesn't disclose the whole path.</p>
+The **`Origin`** request header indicates where a request originates from. It doesn't include any path information. It is similar to the {{HTTPHeader("Referer")}} header, but, unlike that header, it doesn't disclose the whole path.
 
-<div class="notecard note">
-  <p><strong>Note:</strong> Basically, browsers add the {{httpheader("Origin")}} request header to:</p>
-  <ul>
-    <li>all {{Glossary("CORS", "cross origin")}} requests.</li>
-    <li><a href="/en-US/docs/Web/Security/Same-origin_policy">same-origin</a> requests except for {{HTTPMethod("GET")}} or {{HTTPMethod("HEAD")}} requests (i.e. they are added to same-origin {{HTTPMethod("POST")}}, {{HTTPMethod("OPTIONS")}}, {{HTTPMethod("PUT")}}, {{HTTPMethod("PATCH")}}, and {{HTTPMethod("DELETE")}} requests).</li>
-  </ul>
-  <p>There are some exceptions to the above rules; for example if a cross-origin {{HTTPMethod("GET")}} or {{HTTPMethod("HEAD")}} request is made in <a href="/en-US/docs/Web/API/Request/mode#value">no-cors mode</a> the <code>Origin</code> header will not be added.</p>
-</div>
+> **Note:** Basically, browsers add the {{httpheader("Origin")}} request header to:
+>
+> - all {{Glossary("CORS", "cross origin")}} requests.
+> - [same-origin](/en-US/docs/Web/Security/Same-origin_policy) requests except for {{HTTPMethod("GET")}} or {{HTTPMethod("HEAD")}} requests (i.e. they are added to same-origin {{HTTPMethod("POST")}}, {{HTTPMethod("OPTIONS")}}, {{HTTPMethod("PUT")}}, {{HTTPMethod("PATCH")}}, and {{HTTPMethod("DELETE")}} requests).
+>
+> There are some exceptions to the above rules; for example if a cross-origin {{HTTPMethod("GET")}} or {{HTTPMethod("HEAD")}} request is made in [no-cors mode](/en-US/docs/Web/API/Request/mode#value) the `Origin` header will not be added.
 
 <table class="properties">
- <tbody>
-  <tr>
-   <th scope="row">Header type</th>
-   <td>{{Glossary("Request header")}}</td>
-  </tr>
-  <tr>
-   <th scope="row">{{Glossary("Forbidden header name")}}</th>
-   <td>yes</td>
-  </tr>
- </tbody>
+  <tbody>
+    <tr>
+      <th scope="row">Header type</th>
+      <td>{{Glossary("Request header")}}</td>
+    </tr>
+    <tr>
+      <th scope="row">{{Glossary("Forbidden header name")}}</th>
+      <td>yes</td>
+    </tr>
+  </tbody>
 </table>
 
-<h2 id="Syntax">Syntax</h2>
+## Syntax
 
-<pre class="brush: html">Origin: null
-Origin: &lt;scheme&gt; "://" &lt;hostname&gt; [ ":" &lt;port&gt; ]
-</pre>
+```html
+Origin: null
+Origin: <scheme> "://" <hostname> [ ":" <port> ]
+```
 
-<h2 id="Directives">Directives</h2>
+## Directives
 
-<dl>
- <dt>&lt;scheme&gt;</dt>
- <dd>The protocol that is used. Usually it is the HTTP protocol or its secured version, HTTPS.</dd>
- <dt>&lt;hostname&gt;</dt>
- <dd>The domain name of the server (for virtual hosting) or the IP.</dd>
- <dt>&lt;port&gt; {{optional_inline}}</dt>
- <dd>TCP port number on which the server is listening. If no port is given, the default port for the service requested (e.g., "80" for an HTTP URL) is implied.</dd>
-</dl>
+- \<scheme>
+  - : The protocol that is used. Usually it is the HTTP protocol or its secured version, HTTPS.
+- \<hostname>
+  - : The domain name of the server (for virtual hosting) or the IP.
+- \<port> {{optional_inline}}
+  - : TCP port number on which the server is listening. If no port is given, the default port for the service requested (e.g., "80" for an HTTP URL) is implied.
 
-<h2 id="Examples">Examples</h2>
+## Examples
 
-<pre>Origin: https://developer.mozilla.org</pre>
+    Origin: https://developer.mozilla.org
 
-<h2 id="Specifications">Specifications</h2>
+## Specifications
 
 {{Specifications}}
 
-<h2 id="Browser_compatibility">Browser compatibility</h2>
+## Browser compatibility
 
-<div>{{Compat}}</div>
+{{Compat}}
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
- <li>{{HTTPHeader("Host")}}</li>
- <li>{{HTTPHeader("Referer")}}</li>
- <li><a href="/en-US/docs/Web/Security/Same-origin_policy">Same-origin policy</a></li>
- <li>Stack Overflow: <a href="https://stackoverflow.com/a/42242802/">When do browsers send the Origin header? When do browsers set the origin to null?</a></li>
-</ul>
+- {{HTTPHeader("Host")}}
+- {{HTTPHeader("Referer")}}
+- [Same-origin policy](/en-US/docs/Web/Security/Same-origin_policy)
+- Stack Overflow: [When do browsers send the Origin header? When do browsers set the origin to null?](https://stackoverflow.com/a/42242802/)
diff --git a/files/en-us/web/http/headers/pragma/index.md b/files/en-us/web/http/headers/pragma/index.md
index 6d4fe57d758da1a..0c19623f0cc7af4 100644
--- a/files/en-us/web/http/headers/pragma/index.md
+++ b/files/en-us/web/http/headers/pragma/index.md
@@ -10,69 +10,68 @@ tags:
   - Response header
 browser-compat: http.headers.Pragma
 ---
-<div>{{HTTPSidebar}}</div>
+{{HTTPSidebar}}
 
-<p>The <code><strong>Pragma</strong></code> HTTP/1.0 general header is an
-  implementation-specific header that may have various effects along the request-response
-  chain. It is used for backwards compatibility with HTTP/1.0 caches where the
-  {{HTTPHeader("Cache-Control")}} HTTP/1.1 header is not yet present.</p>
+The **`Pragma`** HTTP/1.0 general header is an
+implementation-specific header that may have various effects along the request-response
+chain. It is used for backwards compatibility with HTTP/1.0 caches where the
+{{HTTPHeader("Cache-Control")}} HTTP/1.1 header is not yet present.
 
-<div class="notecard note">
-  <p><strong>Note:</strong> <code>Pragma</code> is not specified for HTTP responses and is
-    therefore not a reliable replacement for the general HTTP/1.1
-    <code>Cache-Control</code> header, although it does behave the same as
-    <code>Cache-Control: no-cache</code>, if the <code>Cache-Control</code> header field
-    is omitted in a request. Use <code>Pragma</code> only for backwards compatibility with
-    HTTP/1.0 clients.</p>
-</div>
+> **Note:** `Pragma` is not specified for HTTP responses and is
+> therefore not a reliable replacement for the general HTTP/1.1
+> `Cache-Control` header, although it does behave the same as
+> `Cache-Control: no-cache`, if the `Cache-Control` header field
+> is omitted in a request. Use `Pragma` only for backwards compatibility with
+> HTTP/1.0 clients.
 
 <table class="properties">
   <tbody>
     <tr>
       <th scope="row">Header type</th>
-      <td>{{Glossary("Request header")}}, {{Glossary("Response header")}} (response behavior is not specified and thus implementation-specific).</td>
+      <td>
+        {{Glossary("Request header")}},
+        {{Glossary("Response header")}} (response behavior is not
+        specified and thus implementation-specific).
+      </td>
     </tr>
     <tr>
       <th scope="row">{{Glossary("Forbidden header name")}}</th>
       <td>no</td>
     </tr>
     <tr>
-      <th scope="row">{{Glossary("CORS-safelisted response header")}}</th>
+      <th scope="row">
+        {{Glossary("CORS-safelisted response header")}}
+      </th>
       <td>yes</td>
     </tr>
   </tbody>
 </table>
 
-<h2 id="Syntax">Syntax</h2>
+## Syntax
 
-<pre class="brush: html">Pragma: no-cache
-</pre>
+```html
+Pragma: no-cache
+```
 
-<h2 id="Directives">Directives</h2>
+## Directives
 
-<dl>
-  <dt>no-cache</dt>
-  <dd>
-    <p>Same as <code>Cache-Control: no-cache</code>. Forces caches to submit the request
-      to the origin server for validation before releasing a cached copy.</p>
-  </dd>
-</dl>
+- no-cache
+  - : Same as `Cache-Control: no-cache`. Forces caches to submit the request
+    to the origin server for validation before releasing a cached copy.
 
-<h2 id="Examples">Examples</h2>
+## Examples
 
-<pre>Pragma: no-cache</pre>
+    Pragma: no-cache
 
-<h2 id="Specifications">Specifications</h2>
+## Specifications
 
 {{Specifications}}
 
-<h2 id="Browser_compatibility">Browser compatibility</h2>
+## Browser compatibility
 
-<p>{{Compat}}</p>
+{{Compat}}
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
-  <li>{{HTTPHeader("Cache-Control")}}</li>
-  <li>{{HTTPHeader("Expires")}}</li>
-</ul>
+- {{HTTPHeader("Cache-Control")}}
+- {{HTTPHeader("Expires")}}
diff --git a/files/en-us/web/http/headers/proxy-authenticate/index.md b/files/en-us/web/http/headers/proxy-authenticate/index.md
index c1c9e7ce0027fe8..7cbe06ef71380f3 100644
--- a/files/en-us/web/http/headers/proxy-authenticate/index.md
+++ b/files/en-us/web/http/headers/proxy-authenticate/index.md
@@ -9,15 +9,15 @@ tags:
   - Response Header
 browser-compat: http.headers.Proxy-Authenticate
 ---
-<div>{{HTTPSidebar}}</div>
+{{HTTPSidebar}}
 
-<p>The HTTP <strong><code>Proxy-Authenticate</code></strong> response header defines the
-  authentication method that should be used to gain access to a resource behind a
-  {{Glossary("proxy server")}}. It authenticates the request to the proxy server, allowing
-  it to transmit the request further.</p>
+The HTTP **`Proxy-Authenticate`** response header defines the
+authentication method that should be used to gain access to a resource behind a
+{{Glossary("proxy server")}}. It authenticates the request to the proxy server, allowing
+it to transmit the request further.
 
-<p>The <code>Proxy-Authenticate</code> header is sent along with a {{HTTPStatus("407")}}
-  <code>Proxy Authentication Required</code>.</p>
+The `Proxy-Authenticate` header is sent along with a {{HTTPStatus("407")}}
+`Proxy Authentication Required`.
 
 <table class="properties">
   <tbody>
@@ -32,47 +32,41 @@ browser-compat: http.headers.Proxy-Authenticate
   </tbody>
 </table>
 
-<h2 id="Syntax">Syntax</h2>
+## Syntax
 
-<pre class="brush: html">Proxy-Authenticate: &lt;type&gt; realm=&lt;realm&gt;
-</pre>
+```html
+Proxy-Authenticate: <type> realm=<realm>
+```
 
-<h2 id="Directives">Directives</h2>
+## Directives
 
-<dl>
-  <dt>&lt;type&gt;</dt>
-  <dd><a href="/en-US/docs/Web/HTTP/Authentication#authentication_schemes">Authentication
-      type</a>. A common type is <a
-      href="/en-US/docs/Web/HTTP/Authentication#basic_authentication_scheme">"Basic"</a>.
-    IANA maintains a <a
-      href="https://www.iana.org/assignments/http-authschemes/http-authschemes.xhtml">list
-      of authentication schemes</a>.</dd>
-  <dt>realm=&lt;realm&gt;</dt>
-  <dd>A description of the protected area, the realm. If no realm is specified, clients
-    often display a formatted host name instead.</dd>
-</dl>
+- \<type>
+  - : [Authentication
+    type](/en-US/docs/Web/HTTP/Authentication#authentication_schemes). A common type is ["Basic"](/en-US/docs/Web/HTTP/Authentication#basic_authentication_scheme).
+    IANA maintains a [list
+    of authentication schemes](https://www.iana.org/assignments/http-authschemes/http-authschemes.xhtml).
+- realm=\<realm>
+  - : A description of the protected area, the realm. If no realm is specified, clients
+    often display a formatted host name instead.
 
-<h2 id="Examples">Examples</h2>
+## Examples
 
-<pre>Proxy-Authenticate: Basic
+    Proxy-Authenticate: Basic
 
-Proxy-Authenticate: Basic realm="Access to the internal site"
-</pre>
+    Proxy-Authenticate: Basic realm="Access to the internal site"
 
-<h2 id="Specifications">Specifications</h2>
+## Specifications
 
 {{Specifications}}
 
-<h2 id="Browser_compatibility">Browser compatibility</h2>
+## Browser compatibility
 
-<p>{{Compat}}</p>
+{{Compat}}
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
-  <li><a href="/en-US/docs/Web/HTTP/Authentication">HTTP authentication</a></li>
-  <li>{{HTTPHeader("Authorization")}}</li>
-  <li>{{HTTPHeader("Proxy-Authorization")}}</li>
-  <li>{{HTTPHeader("WWW-Authenticate")}}</li>
-  <li>{{HTTPStatus("401")}}, {{HTTPStatus("403")}}, {{HTTPStatus("407")}}</li>
-</ul>
+- [HTTP authentication](/en-US/docs/Web/HTTP/Authentication)
+- {{HTTPHeader("Authorization")}}
+- {{HTTPHeader("Proxy-Authorization")}}
+- {{HTTPHeader("WWW-Authenticate")}}
+- {{HTTPStatus("401")}}, {{HTTPStatus("403")}}, {{HTTPStatus("407")}}
diff --git a/files/en-us/web/http/headers/proxy-authorization/index.md b/files/en-us/web/http/headers/proxy-authorization/index.md
index 68c2f137ae19417..09769a67b6d719d 100644
--- a/files/en-us/web/http/headers/proxy-authorization/index.md
+++ b/files/en-us/web/http/headers/proxy-authorization/index.md
@@ -8,12 +8,12 @@ tags:
   - Request header
   - header
 ---
-<div>{{HTTPSidebar}}</div>
+{{HTTPSidebar}}
 
-<p>The HTTP <strong><code>Proxy-Authorization</code></strong> request header contains the
-  credentials to authenticate a user agent to a proxy server, usually after the server has
-  responded with a {{HTTPStatus("407")}} <code>Proxy Authentication Required</code> status
-  and the {{HTTPHeader("Proxy-Authenticate")}} header.</p>
+The HTTP **`Proxy-Authorization`** request header contains the
+credentials to authenticate a user agent to a proxy server, usually after the server has
+responded with a {{HTTPStatus("407")}} `Proxy Authentication Required` status
+and the {{HTTPHeader("Proxy-Authenticate")}} header.
 
 <table class="properties">
   <tbody>
@@ -28,55 +28,45 @@ tags:
   </tbody>
 </table>
 
-<h2 id="Syntax">Syntax</h2>
+## Syntax
 
-<pre
-  class="brush: html">Proxy-Authorization: &lt;type&gt; &lt;credentials&gt;</pre>
+```html
+Proxy-Authorization: <type> <credentials>
+```
 
-<h2 id="Directives">Directives</h2>
+## Directives
 
-<dl>
-  <dt>&lt;type&gt;</dt>
-  <dd><a href="/en-US/docs/Web/HTTP/Authentication#authentication_schemes">Authentication
-      type</a>. A common type is <a
-      href="/en-US/docs/Web/HTTP/Authentication#basic_authentication_scheme">"Basic"</a>.
-    See also the <a
-      href="https://www.iana.org/assignments/http-authschemes/http-authschemes.xhtml">IANA
-      registry of Authentication schemes</a>.</dd>
-  <dt>&lt;credentials&gt;</dt>
-  <dd>The credentials are constructed like this:
-    <ul>
-      <li>The username and the password are combined with a colon
-        (<code>aladdin:opensesame</code>).</li>
-      <li>The resulting string is <a
-          href="/en-US/docs/Glossary/Base64">base64</a>
-        encoded (<code>YWxhZGRpbjpvcGVuc2VzYW1l</code>).</li>
-    </ul>
+- \<type>
+  - : [Authentication
+    type](/en-US/docs/Web/HTTP/Authentication#authentication_schemes). A common type is ["Basic"](/en-US/docs/Web/HTTP/Authentication#basic_authentication_scheme).
+    See also the [IANA
+    registry of Authentication schemes](https://www.iana.org/assignments/http-authschemes/http-authschemes.xhtml).
+- \<credentials>
 
-    <div class="notecard note">
-      <p><strong>Note:</strong> Base64 encoding does not mean encryption or hashing! This
-        method is equally secure as sending the credentials in clear text (base64 is a
-        reversible encoding). Prefer to use HTTPS in conjunction with Basic
-        Authentication.</p>
-    </div>
-  </dd>
-</dl>
+  - : The credentials are constructed like this:
 
-<h2 id="Examples">Examples</h2>
+    - The username and the password are combined with a colon
+      (`aladdin:opensesame`).
+    - The resulting string is [base64](/en-US/docs/Glossary/Base64)
+      encoded (`YWxhZGRpbjpvcGVuc2VzYW1l`).
 
-<pre>Proxy-Authorization: Basic YWxhZGRpbjpvcGVuc2VzYW1l
-</pre>
+    > **Note:** Base64 encoding does not mean encryption or hashing! This
+    > method is equally secure as sending the credentials in clear text (base64 is a
+    > reversible encoding). Prefer to use HTTPS in conjunction with Basic
+    > Authentication.
 
-<h2 id="Specifications">Specifications</h2>
+## Examples
+
+    Proxy-Authorization: Basic YWxhZGRpbjpvcGVuc2VzYW1l
+
+## Specifications
 
 {{Specifications}}
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
-  <li><a href="/en-US/docs/Web/HTTP/Authentication">HTTP authentication</a></li>
-  <li>{{HTTPHeader("Proxy-Authenticate")}}</li>
-  <li>{{HTTPHeader("WWW-Authenticate")}}</li>
-  <li>{{HTTPHeader("Authorization")}}</li>
-  <li>{{HTTPStatus("401")}}, {{HTTPStatus("403")}}, {{HTTPStatus("407")}}</li>
-</ul>
+- [HTTP authentication](/en-US/docs/Web/HTTP/Authentication)
+- {{HTTPHeader("Proxy-Authenticate")}}
+- {{HTTPHeader("WWW-Authenticate")}}
+- {{HTTPHeader("Authorization")}}
+- {{HTTPStatus("401")}}, {{HTTPStatus("403")}}, {{HTTPStatus("407")}}
diff --git a/files/en-us/web/http/headers/public-key-pins-report-only/index.md b/files/en-us/web/http/headers/public-key-pins-report-only/index.md
index 13b78d81475ba6d..061308cd1fba957 100644
--- a/files/en-us/web/http/headers/public-key-pins-report-only/index.md
+++ b/files/en-us/web/http/headers/public-key-pins-report-only/index.md
@@ -2,35 +2,30 @@
 title: Public-Key-Pins-Report-Only
 slug: Web/HTTP/Headers/Public-Key-Pins-Report-Only
 tags:
-- Deprecated
-- HPKP
-- HTTP
-- Deprecated
-- Security
-- header
+  - Deprecated
+  - HPKP
+  - HTTP
+  - Deprecated
+  - Security
+  - header
 browser-compat: http.headers.Public-Key-Pins-Report-Only
 ---
-<p>{{HTTPSidebar}}{{deprecated_header}}</p>
-
-<div class="notecard note">
-  <p>
-    <strong>Note:</strong> Public Key Pinning mechanism was deprecated in favor of
-    <a href="/en-US/docs/Web/Security/Certificate_Transparency">Certificate Transparency</a>
-    and {{HTTPHeader("Expect-CT")}} header.
-  </p>
-</div>
-
-<p>The HTTP <code><strong>Public-Key-Pins-Report-Only</strong></code> response header was
-  used to send reports of pinning violation to the <code>report-uri</code> specified in
-  the header but, unlike {{HTTPHeader("Public-Key-Pins")}} still allows browsers to
-  connect to the server if the pinning is violated. The header is silently ignored in
-  modern browsers as support for HPKP has been removed. Use <a
-    href="/en-US/docs/Web/Security/Certificate_Transparency">Certificate Transparency</a>
-  and the {{HTTPHeader("Expect-CT")}} header instead.</p>
-
-<p>For more information, see the {{HTTPHeader("Public-Key-Pins")}} header reference page
-  and the <a href="/en-US/docs/Web/HTTP/Public_Key_Pinning">HTTP Public Key Pinning</a>
-  article.</p>
+{{HTTPSidebar}}{{deprecated_header}}
+
+> **Note:** Public Key Pinning mechanism was deprecated in favor of
+> [Certificate Transparency](/en-US/docs/Web/Security/Certificate_Transparency)
+> and {{HTTPHeader("Expect-CT")}} header.
+
+The HTTP **`Public-Key-Pins-Report-Only`** response header was
+used to send reports of pinning violation to the `report-uri` specified in
+the header but, unlike {{HTTPHeader("Public-Key-Pins")}} still allows browsers to
+connect to the server if the pinning is violated. The header is silently ignored in
+modern browsers as support for HPKP has been removed. Use [Certificate Transparency](/en-US/docs/Web/Security/Certificate_Transparency)
+and the {{HTTPHeader("Expect-CT")}} header instead.
+
+For more information, see the {{HTTPHeader("Public-Key-Pins")}} header reference page
+and the [HTTP Public Key Pinning](/en-US/docs/Web/HTTP/Public_Key_Pinning)
+article.
 
 <table class="properties">
   <tbody>
@@ -45,59 +40,57 @@ browser-compat: http.headers.Public-Key-Pins-Report-Only
   </tbody>
 </table>
 
-<h2 id="Syntax">Syntax</h2>
+## Syntax
 
-<pre class="brush: html">Public-Key-Pins-Report-Only: pin-sha256="&lt;pin-value&gt;";
-                             max-age=&lt;expire-time&gt;;
+```html
+Public-Key-Pins-Report-Only: pin-sha256="<pin-value>";
+                             max-age=<expire-time>;
                              includeSubDomains;
-                             report-uri="&lt;uri&gt;"</pre>
+                             report-uri="<uri>"
+```
 
-<h2 id="Directives">Directives</h2>
+## Directives
 
-<dl>
-  <dt><code>pin-sha256="&lt;pin-value&gt;"</code></dt>
-  <dd>The quoted string is the Base64 encoded Subject Public Key Information
+- `pin-sha256="<pin-value>"`
+  - : The quoted string is the Base64 encoded Subject Public Key Information
     ({{Glossary("SPKI")}}) fingerprint. It is possible to specify multiple pins for
     different public keys. Some browsers might allow other hashing algorithms than SHA-256
-    in the future.</dd>
-  <dt>max-age=&lt;expire-time&gt;</dt>
-  <dd>This directive is meaningless for the Public-Key-Pins-Report-Only header, it will be
-    ignored by user agents and the header will not be cached.</dd>
-  <dt><code>includeSubDomains </code>{{optional_inline}}</dt>
-  <dd>If this optional parameter is specified, this rule applies to all of the site's
-    subdomains as well.</dd>
-  <dt><code>report-uri="&lt;uri&gt;"</code></dt>
-  <dd>Pin validation failures are reported to the given URL. This directive should be used
-    with this header, otherwise this header will be a no-op.</dd>
-</dl>
-
-<h2 id="Example">Example</h2>
-
-<pre>Public-Key-Pins-Report-Only:
-  pin-sha256="cUPcTAZWKaASuYWhhneDttWpY3oBAkE3h2+soZS7sWs=";
-  pin-sha256="M8HztCzM3elUxkcjR2S5P4hhyBNf6lHkmjAHKhpGPWE=";
-  includeSubDomains;
-  report-uri="https://www.example.org/hpkp-report"</pre>
-
-<p>In this example,
-  <strong>pin-sha256="cUPcTAZWKaASuYWhhneDttWpY3oBAkE3h2+soZS7sWs="</strong> pins the
-  server's public key used in production. The second pin declaration
-  <strong>pin-sha256="M8HztCzM3elUxkcjR2S5P4hhyBNf6lHkmjAHKhpGPWE="</strong> also pins the
-  backup key. This key pinning is also valid for all subdomains, which is told by the
-  <strong>includeSubDomains</strong> declaration. Finally,
-  <strong>report-uri="https://www.example.org/hpkp-report"</strong> explains where to
-  report pin validation failures.</p>
-
-<h2 id="Specifications">Specifications</h2>
+    in the future.
+- max-age=\<expire-time>
+  - : This directive is meaningless for the Public-Key-Pins-Report-Only header, it will be
+    ignored by user agents and the header will not be cached.
+- `includeSubDomains `{{optional_inline}}
+  - : If this optional parameter is specified, this rule applies to all of the site's
+    subdomains as well.
+- `report-uri="<uri>"`
+  - : Pin validation failures are reported to the given URL. This directive should be used
+    with this header, otherwise this header will be a no-op.
+
+## Example
+
+    Public-Key-Pins-Report-Only:
+      pin-sha256="cUPcTAZWKaASuYWhhneDttWpY3oBAkE3h2+soZS7sWs=";
+      pin-sha256="M8HztCzM3elUxkcjR2S5P4hhyBNf6lHkmjAHKhpGPWE=";
+      includeSubDomains;
+      report-uri="https://www.example.org/hpkp-report"
+
+In this example,
+**pin-sha256="cUPcTAZWKaASuYWhhneDttWpY3oBAkE3h2+soZS7sWs="** pins the
+server's public key used in production. The second pin declaration
+**pin-sha256="M8HztCzM3elUxkcjR2S5P4hhyBNf6lHkmjAHKhpGPWE="** also pins the
+backup key. This key pinning is also valid for all subdomains, which is told by the
+**includeSubDomains** declaration. Finally,
+**report-uri="https\://www\.example.org/hpkp-report"** explains where to
+report pin validation failures.
+
+## Specifications
 
 {{Specifications}}
 
-<h2 id="Browser_compatibility">Browser compatibility</h2>
+## Browser compatibility
 
-<p>{{Compat}}</p>
+{{Compat}}
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
-  <li>{{HTTPHeader("Public-Key-Pins")}}</li>
-</ul>
+- {{HTTPHeader("Public-Key-Pins")}}
diff --git a/files/en-us/web/http/headers/public-key-pins/index.md b/files/en-us/web/http/headers/public-key-pins/index.md
index 8762e0abc96fb62..04ce2160452d5c3 100644
--- a/files/en-us/web/http/headers/public-key-pins/index.md
+++ b/files/en-us/web/http/headers/public-key-pins/index.md
@@ -2,34 +2,29 @@
 title: Public-Key-Pins
 slug: Web/HTTP/Headers/Public-Key-Pins
 tags:
-- Deprecated
-- HPKP
-- HTTP
-- Deprecated
-- Reference
-- Security
-- header
+  - Deprecated
+  - HPKP
+  - HTTP
+  - Deprecated
+  - Reference
+  - Security
+  - header
 browser-compat: http.headers.Public-Key-Pins
 ---
-<div>{{HTTPSidebar}}{{deprecated_header}}</div>
-
-<div class="notecard note">
-  <p>
-    <strong>Note:</strong> Public Key Pinning mechanism was deprecated
-    in favor of <a href="/en-US/docs/Web/Security/Certificate_Transparency">Certificate Transparency</a>
-    and {{HTTPHeader("Expect-CT")}} header.
-  </p>
-</div>
-
-<p>The HTTP <code><strong>Public-Key-Pins</strong></code> response header used to
-  associate a specific cryptographic public {{Glossary("key")}} with a certain web server
-  to decrease the risk of {{Glossary("MITM")}} attacks with forged certificates, however,
-  it has been removed from modern browsers and is no longer supported. Use <a
-    href="/en-US/docs/Web/Security/Certificate_Transparency">Certificate
-    Transparency</a> and {{HTTPHeader("Expect-CT")}} header instead.</p>
-
-<p>For more information, see the <a href="/en-US/docs/Web/HTTP/Public_Key_Pinning">HTTP
-    Public Key Pinning</a> article.</p>
+{{HTTPSidebar}}{{deprecated_header}}
+
+> **Note:** Public Key Pinning mechanism was deprecated
+> in favor of [Certificate Transparency](/en-US/docs/Web/Security/Certificate_Transparency)
+> and {{HTTPHeader("Expect-CT")}} header.
+
+The HTTP **`Public-Key-Pins`** response header used to
+associate a specific cryptographic public {{Glossary("key")}} with a certain web server
+to decrease the risk of {{Glossary("MITM")}} attacks with forged certificates, however,
+it has been removed from modern browsers and is no longer supported. Use [Certificate
+Transparency](/en-US/docs/Web/Security/Certificate_Transparency) and {{HTTPHeader("Expect-CT")}} header instead.
+
+For more information, see the [HTTP
+Public Key Pinning](/en-US/docs/Web/HTTP/Public_Key_Pinning) article.
 
 <table class="properties">
   <tbody>
@@ -44,70 +39,64 @@ browser-compat: http.headers.Public-Key-Pins
   </tbody>
 </table>
 
-<h2 id="Syntax">Syntax</h2>
+## Syntax
 
-<pre class="brush: html">Public-Key-Pins: pin-sha256="&lt;pin-value&gt;";
-                 max-age=&lt;expire-time&gt;;
+```html
+Public-Key-Pins: pin-sha256="<pin-value>";
+                 max-age=<expire-time>;
                  includeSubDomains;
-                 report-uri="&lt;uri&gt;"</pre>
+                 report-uri="<uri>"
+```
 
-<h2 id="Directives">Directives</h2>
+## Directives
 
-<dl>
-  <dt><code>pin-sha256="&lt;pin-value&gt;"</code></dt>
-  <dd>The quoted string is the Base64 encoded Subject Public Key Information
+- `pin-sha256="<pin-value>"`
+  - : The quoted string is the Base64 encoded Subject Public Key Information
     ({{Glossary("SPKI")}}) fingerprint. It is possible to specify multiple pins for
     different public keys. Some browsers might allow other hashing algorithms than SHA-256
-    in the future.</dd>
-  <dt><code>max-age=&lt;expire-time&gt;</code></dt>
-  <dd>The time, in seconds, that the browser should remember that this site is only to be
-    accessed using one of the defined keys.</dd>
-  <dt><code>includeSubDomains </code>{{optional_inline}}</dt>
-  <dd>If this optional parameter is specified, this rule applies to all of the site's
-    subdomains as well.</dd>
-  <dt><code>report-uri="&lt;uri&gt;"</code> {{optional_inline}}</dt>
-  <dd>If this optional parameter is specified, pin validation failures are reported to the
-    given URL.</dd>
-</dl>
-
-<h2 id="Example">Example</h2>
-
-<div class="notecard warning">
-  <p>
-    <strong>Warning:</strong> HPKP has the potential to lock out users for a long time
-    if used incorrectly!
-    The use of backup certificates and/or pinning the CA certificate is recommended.
-  </p>
-</div>
-
-<pre>Public-Key-Pins:
-  pin-sha256="cUPcTAZWKaASuYWhhneDttWpY3oBAkE3h2+soZS7sWs=";
-  pin-sha256="M8HztCzM3elUxkcjR2S5P4hhyBNf6lHkmjAHKhpGPWE=";
-  max-age=5184000; includeSubDomains;
-  report-uri="https://www.example.org/hpkp-report"</pre>
-
-<p>In this example,
-  <strong>pin-sha256="cUPcTAZWKaASuYWhhneDttWpY3oBAkE3h2+soZS7sWs="</strong> pins the
-  server's public key used in production. The second pin declaration
-  <strong>pin-sha256="M8HztCzM3elUxkcjR2S5P4hhyBNf6lHkmjAHKhpGPWE="</strong> also pins the
-  backup key. <strong>max-age=5184000</strong> tells the client to store this information
-  for two months, which is a reasonable time limit according to the IETF RFC. This key
-  pinning is also valid for all subdomains, which is told by the
-  <strong>includeSubDomains</strong> declaration. Finally,
-  <strong>report-uri="https://www.example.org/hpkp-report"</strong> explains where to
-  report pin validation failures.</p>
-
-<h2 id="Specifications">Specifications</h2>
+    in the future.
+- `max-age=<expire-time>`
+  - : The time, in seconds, that the browser should remember that this site is only to be
+    accessed using one of the defined keys.
+- `includeSubDomains `{{optional_inline}}
+  - : If this optional parameter is specified, this rule applies to all of the site's
+    subdomains as well.
+- `report-uri="<uri>"` {{optional_inline}}
+  - : If this optional parameter is specified, pin validation failures are reported to the
+    given URL.
+
+## Example
+
+> **Warning:** HPKP has the potential to lock out users for a long time
+> if used incorrectly!
+> The use of backup certificates and/or pinning the CA certificate is recommended.
+
+    Public-Key-Pins:
+      pin-sha256="cUPcTAZWKaASuYWhhneDttWpY3oBAkE3h2+soZS7sWs=";
+      pin-sha256="M8HztCzM3elUxkcjR2S5P4hhyBNf6lHkmjAHKhpGPWE=";
+      max-age=5184000; includeSubDomains;
+      report-uri="https://www.example.org/hpkp-report"
+
+In this example,
+**pin-sha256="cUPcTAZWKaASuYWhhneDttWpY3oBAkE3h2+soZS7sWs="** pins the
+server's public key used in production. The second pin declaration
+**pin-sha256="M8HztCzM3elUxkcjR2S5P4hhyBNf6lHkmjAHKhpGPWE="** also pins the
+backup key. **max-age=5184000** tells the client to store this information
+for two months, which is a reasonable time limit according to the IETF RFC. This key
+pinning is also valid for all subdomains, which is told by the
+**includeSubDomains** declaration. Finally,
+**report-uri="https\://www\.example.org/hpkp-report"** explains where to
+report pin validation failures.
+
+## Specifications
 
 {{Specifications}}
 
-<h2 id="Browser_compatibility">Browser compatibility</h2>
+## Browser compatibility
 
-<p>{{Compat}}</p>
+{{Compat}}
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
-  <li>{{HTTPHeader("Public-Key-Pins-Report-Only")}}</li>
-  <li>{{HTTPHeader("Expect-CT")}}</li>
-</ul>
+- {{HTTPHeader("Public-Key-Pins-Report-Only")}}
+- {{HTTPHeader("Expect-CT")}}
diff --git a/files/en-us/web/http/headers/range/index.md b/files/en-us/web/http/headers/range/index.md
index f2a1dbce9f586f6..b020b61530039c1 100644
--- a/files/en-us/web/http/headers/range/index.md
+++ b/files/en-us/web/http/headers/range/index.md
@@ -9,70 +9,66 @@ tags:
   - Request header
 browser-compat: http.headers.Range
 ---
-<p>{{HTTPSidebar}}</p>
+{{HTTPSidebar}}
 
-<p>The <strong><code>Range</code></strong> HTTP request header indicates the part of a document that the server should return. Several parts can be requested with one <code>Range</code> header at once, and the server may send back these ranges in a multipart document. If the server sends back ranges, it uses the {{HTTPStatus("206")}}<code> Partial Content</code> for the response. If the ranges are invalid, the server returns the {{HTTPStatus("416")}}<code> Range Not Satisfiable</code> error. The server can also ignore the <code>Range</code> header and return the whole document with a {{HTTPStatus("200")}} status code.</p>
+The **`Range`** HTTP request header indicates the part of a document that the server should return. Several parts can be requested with one `Range` header at once, and the server may send back these ranges in a multipart document. If the server sends back ranges, it uses the {{HTTPStatus("206")}}` Partial Content` for the response. If the ranges are invalid, the server returns the {{HTTPStatus("416")}}` Range Not Satisfiable` error. The server can also ignore the `Range` header and return the whole document with a {{HTTPStatus("200")}} status code.
 
 <table class="properties">
- <tbody>
-  <tr>
-   <th scope="row">Header type</th>
-   <td>{{Glossary("Request header")}}</td>
-  </tr>
-  <tr>
-   <th scope="row">{{Glossary("Forbidden header name")}}</th>
-   <td>no</td>
-  </tr>
- </tbody>
+  <tbody>
+    <tr>
+      <th scope="row">Header type</th>
+      <td>{{Glossary("Request header")}}</td>
+    </tr>
+    <tr>
+      <th scope="row">{{Glossary("Forbidden header name")}}</th>
+      <td>no</td>
+    </tr>
+  </tbody>
 </table>
 
-<h2 id="Syntax">Syntax</h2>
+## Syntax
 
-<pre class="brush: html">Range: &lt;unit&gt;=&lt;range-start&gt;-
-Range: &lt;unit&gt;=&lt;range-start&gt;-&lt;range-end&gt;
-Range: &lt;unit&gt;=&lt;range-start&gt;-&lt;range-end&gt;, &lt;range-start&gt;-&lt;range-end&gt;
-Range: &lt;unit&gt;=&lt;range-start&gt;-&lt;range-end&gt;, &lt;range-start&gt;-&lt;range-end&gt;, &lt;range-start&gt;-&lt;range-end&gt;
-Range: &lt;unit&gt;=-&lt;suffix-length&gt;</pre>
+```html
+Range: <unit>=<range-start>-
+Range: <unit>=<range-start>-<range-end>
+Range: <unit>=<range-start>-<range-end>, <range-start>-<range-end>
+Range: <unit>=<range-start>-<range-end>, <range-start>-<range-end>, <range-start>-<range-end>
+Range: <unit>=-<suffix-length>
+```
 
-<h2 id="Directives">Directives</h2>
+## Directives
 
-<dl>
- <dt>&lt;unit&gt;</dt>
- <dd>The unit in which ranges are specified. This is usually <code>bytes</code>.</dd>
- <dt>&lt;range-start&gt;</dt>
- <dd>An integer in the given unit indicating the beginning of the request range.</dd>
- <dt>&lt;range-end&gt;</dt>
- <dd>An integer in the given unit indicating the end of the requested range. This value is optional and, if omitted, the end of the document is taken as the end of the range.</dd>
- <dt>&lt;suffix-length&gt;</dt>
- <dd>An integer in the given unit indicating the number of units at the end of the file to return.</dd>
-</dl>
+- \<unit>
+  - : The unit in which ranges are specified. This is usually `bytes`.
+- \<range-start>
+  - : An integer in the given unit indicating the beginning of the request range.
+- \<range-end>
+  - : An integer in the given unit indicating the end of the requested range. This value is optional and, if omitted, the end of the document is taken as the end of the range.
+- \<suffix-length>
+  - : An integer in the given unit indicating the number of units at the end of the file to return.
 
-<h2 id="Examples">Examples</h2>
+## Examples
 
-<p>Requesting three ranges from the file.</p>
+Requesting three ranges from the file.
 
-<pre>Range: bytes=200-1000, 2000-6576, 19000-
-</pre>
+    Range: bytes=200-1000, 2000-6576, 19000-
 
-<p>Requesting the first 500 and last 500 bytes of the file. The request may be rejected by the server if the ranges overlap.</p>
+Requesting the first 500 and last 500 bytes of the file. The request may be rejected by the server if the ranges overlap.
 
-<pre>Range: bytes=0-499, -500
-</pre>
+    Range: bytes=0-499, -500
 
-<h2 id="Specifications">Specifications</h2>
+## Specifications
 
 {{Specifications}}
 
-<h2 id="Browser_compatibility">Browser compatibility</h2>
+## Browser compatibility
 
-<p>{{Compat}}</p>
+{{Compat}}
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
- <li>{{HTTPHeader("If-Range")}}</li>
- <li>{{HTTPHeader("Content-Range")}}</li>
- <li>{{HTTPHeader("Content-Type")}}</li>
- <li>{{HTTPStatus("206")}}<code> Partial Content</code></li>
- <li>{{HTTPStatus("416")}}<code> Range Not Satisfiable</code></li>
-</ul>
+- {{HTTPHeader("If-Range")}}
+- {{HTTPHeader("Content-Range")}}
+- {{HTTPHeader("Content-Type")}}
+- {{HTTPStatus("206")}}` Partial Content`
+- {{HTTPStatus("416")}}` Range Not Satisfiable`
diff --git a/files/en-us/web/http/headers/referer/index.md b/files/en-us/web/http/headers/referer/index.md
index 91808f927123c37..4f7ee0bcb7fcf95 100644
--- a/files/en-us/web/http/headers/referer/index.md
+++ b/files/en-us/web/http/headers/referer/index.md
@@ -9,66 +9,58 @@ tags:
   - referrer
 browser-compat: http.headers.Referer
 ---
-<div>{{HTTPSidebar}}</div>
+{{HTTPSidebar}}
 
-<p>The <code><strong>Referer</strong></code> HTTP request header contains an absolute or partial address of the page making the request. When following a link, this would be the address of the page containing the link. When making resource requests to another domain, this would be the address of the page using the resource. The <code>Referer</code> header allows servers to identify where people are visiting them from, which can then be used for analytics, logging, optimized caching, and more.</p>
+The **`Referer`** HTTP request header contains an absolute or partial address of the page making the request. When following a link, this would be the address of the page containing the link. When making resource requests to another domain, this would be the address of the page using the resource. The `Referer` header allows servers to identify where people are visiting them from, which can then be used for analytics, logging, optimized caching, and more.
 
-<p>The <code>Referer</code> header may not contain URL fragments (i.e. "#section") or "username:password" information. It can potentially contain an <em>origin</em>, <em>path</em>, and <em>querystring</em>. What is sent, if anything, depends on the <em>referrer policy</em> for the request. See {{HTTPHeader("Referrer-Policy")}} for <a href="/en-US/docs/Web/HTTP/Headers/Referrer-Policy#directives">information</a> and <a href="/en-US/docs/Web/HTTP/Headers/Referrer-Policy#examples">examples</a>.
+The `Referer` header may not contain URL fragments (i.e. "#section") or "username:password" information. It can potentially contain an _origin_, _path_, and _querystring_. What is sent, if anything, depends on the _referrer policy_ for the request. See {{HTTPHeader("Referrer-Policy")}} for [information](/en-US/docs/Web/HTTP/Headers/Referrer-Policy#directives) and [examples](/en-US/docs/Web/HTTP/Headers/Referrer-Policy#examples).
 
-<div class="notecard note">
-  <p><strong>Note:</strong> The header name "referer" is actually a misspelling of the word "referrer". See {{interwiki("wikipedia", "HTTP_referer", "HTTP referer on Wikipedia")}} for more details.</p>
-</div>
+> **Note:** The header name "referer" is actually a misspelling of the word "referrer". See {{interwiki("wikipedia", "HTTP_referer", "HTTP referer on Wikipedia")}} for more details.
 
-<div class="notecard warning">
-  <p><strong>Warning:</strong> Although this header has many innocent uses it can have undesirable consequences for user security and privacy. See <a href="/en-US/docs/Web/Security/Referer_header:_privacy_and_security_concerns">Referer header: privacy and security concerns</a> for more information and mitigations.</p>
-</div>
+> **Warning:** Although this header has many innocent uses it can have undesirable consequences for user security and privacy. See [Referer header: privacy and security concerns](/en-US/docs/Web/Security/Referer_header:_privacy_and_security_concerns) for more information and mitigations.
 
 <table class="properties">
- <tbody>
-  <tr>
-   <th scope="row">Header type</th>
-   <td>{{Glossary("Request header")}}</td>
-  </tr>
-  <tr>
-   <th scope="row">{{Glossary("Forbidden header name")}}</th>
-   <td>yes</td>
-  </tr>
- </tbody>
+  <tbody>
+    <tr>
+      <th scope="row">Header type</th>
+      <td>{{Glossary("Request header")}}</td>
+    </tr>
+    <tr>
+      <th scope="row">{{Glossary("Forbidden header name")}}</th>
+      <td>yes</td>
+    </tr>
+  </tbody>
 </table>
 
-<h2 id="Syntax">Syntax</h2>
+## Syntax
 
-<pre class="brush: html">Referer: &lt;url&gt;
-</pre>
+```html
+Referer: <url>
+```
 
-<h2 id="Directives">Directives</h2>
+## Directives
 
-<dl>
- <dt>&lt;url&gt;</dt>
- <dd>An absolute or partial address of the web page making the request. URL fragments (i.e. "#section") and userinfo (i.e. "username:password" in "https://username:password@example.com/foo/bar/") are not included. Origin, path, and querystring may be included, depending on the <a href="/en-US/docs/Web/HTTP/Headers/Referrer-Policy#directives">referrer policy</a>.</dd>
-</dl>
+- \<url>
+  - : An absolute or partial address of the web page making the request. URL fragments (i.e. "#section") and userinfo (i.e. "username:password" in "https\://username:password\@example.com/foo/bar/") are not included. Origin, path, and querystring may be included, depending on the [referrer policy](/en-US/docs/Web/HTTP/Headers/Referrer-Policy#directives).
 
-<h2 id="Examples">Examples</h2>
+## Examples
 
-<pre>Referer: https://developer.mozilla.org/en-US/docs/Web/JavaScript
-Referer: https://example.com/page?q=123
-Referer: https://example.com/
-</pre>
+    Referer: https://developer.mozilla.org/en-US/docs/Web/JavaScript
+    Referer: https://example.com/page?q=123
+    Referer: https://example.com/
 
-<h2 id="Specifications">Specifications</h2>
+## Specifications
 
 {{Specifications}}
 
-<h2 id="Browser_compatibility">Browser compatibility</h2>
+## Browser compatibility
 
-<p>{{Compat}}</p>
+{{Compat}}
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
-  <li>{{interwiki("wikipedia", "HTTP_referer", "HTTP referer on Wikipedia")}}</li>
-  <li><a href="/en-US/docs/Web/API/Fetch_API">Fetch</a>: {{domxref("Request.referrerPolicy")}}</li>
-  <li>The obsolete {{HTTPHeader("Content-Security-Policy")}} {{HTTPHeader("Content-Security-Policy/referrer", "referrer")}} {{deprecated_inline}} directive.</li>
-  <li><a href="/en-US/docs/Web/Security/Same-origin_policy">Same-origin policy</a></li>
-  <li><a href="https://blog.mozilla.org/security/2015/01/21/meta-referrer/">Tighter Control Over Your Referrers – Mozilla Security Blog</a></li>
- </ul>
+- {{interwiki("wikipedia", "HTTP_referer", "HTTP referer on Wikipedia")}}
+- [Fetch](/en-US/docs/Web/API/Fetch_API): {{domxref("Request.referrerPolicy")}}
+- The obsolete {{HTTPHeader("Content-Security-Policy")}} {{HTTPHeader("Content-Security-Policy/referrer", "referrer")}} {{deprecated_inline}} directive.
+- [Same-origin policy](/en-US/docs/Web/Security/Same-origin_policy)
+- [Tighter Control Over Your Referrers – Mozilla Security Blog](https://blog.mozilla.org/security/2015/01/21/meta-referrer/)
diff --git a/files/en-us/web/http/headers/referrer-policy/index.md b/files/en-us/web/http/headers/referrer-policy/index.md
index c55cee68241aa3a..68636d6b1bfb976 100644
--- a/files/en-us/web/http/headers/referrer-policy/index.md
+++ b/files/en-us/web/http/headers/referrer-policy/index.md
@@ -12,26 +12,27 @@ tags:
   - referrer
 browser-compat: http.headers.Referrer-Policy
 ---
-<div>{{HTTPSidebar}}</div>
+{{HTTPSidebar}}
 
-<p>The <strong><code>Referrer-Policy</code></strong> {{glossary("HTTP header")}} controls how much <a href="/en-US/docs/Web/Security/Referer_header:_privacy_and_security_concerns">referrer information</a> (sent via the {{HTTPHeader("Referer")}} header) should be included with requests. Aside from the HTTP header, you can <a href="#integration_with_html">set this policy in HTML</a>.</p>
+The **`Referrer-Policy`** {{glossary("HTTP header")}} controls how much [referrer information](/en-US/docs/Web/Security/Referer_header:_privacy_and_security_concerns) (sent via the {{HTTPHeader("Referer")}} header) should be included with requests. Aside from the HTTP header, you can [set this policy in HTML](#integration_with_html).
 
 <table class="properties">
- <tbody>
-  <tr>
-   <th scope="row">Header type</th>
-   <td>{{Glossary("Response header")}}</td>
-  </tr>
-  <tr>
-   <th scope="row">{{Glossary("Forbidden header name")}}</th>
-   <td>no</td>
-  </tr>
- </tbody>
+  <tbody>
+    <tr>
+      <th scope="row">Header type</th>
+      <td>{{Glossary("Response header")}}</td>
+    </tr>
+    <tr>
+      <th scope="row">{{Glossary("Forbidden header name")}}</th>
+      <td>no</td>
+    </tr>
+  </tbody>
 </table>
 
-<h2 id="Syntax">Syntax</h2>
+## Syntax
 
-<pre class="brush: html">Referrer-Policy: no-referrer
+```html
+Referrer-Policy: no-referrer
 Referrer-Policy: no-referrer-when-downgrade
 Referrer-Policy: origin
 Referrer-Policy: origin-when-cross-origin
@@ -39,270 +40,159 @@ Referrer-Policy: same-origin
 Referrer-Policy: strict-origin
 Referrer-Policy: strict-origin-when-cross-origin
 Referrer-Policy: unsafe-url
-</pre>
-
-<div class="notecard note">
-  <p><strong>Note:</strong> The original header name {{HTTPHeader("Referer")}} is a misspelling of the word "referrer". The <code>Referrer-Policy</code> header does not share this misspelling.</p>
-</div>
-
-<h2 id="Directives">Directives</h2>
-
-<dl>
- <dt><code>no-referrer</code></dt>
- <dd>The {{HTTPHeader("Referer")}} header will be omitted entirely. No referrer information is sent along with requests.</dd>
- <dt><code>no-referrer-when-downgrade</code></dt>
- <dd>Send the {{glossary("origin")}}, path, and querystring in {{HTTPHeader("Referer")}} when the protocol security level stays the same or improves (HTTP→HTTP, HTTP→HTTPS, HTTPS→HTTPS). Don't send the {{HTTPHeader("Referer")}} header for requests to less secure destinations (HTTPS→HTTP, HTTPS→file).
- </dd>
- <dt><code>origin</code></dt>
- <dd>Send the {{glossary("origin")}} (only) in the {{HTTPHeader("Referer")}} header.<br>
- For example, a document at <code>https://example.com/page.html</code> will send the referrer <code>https://example.com/</code>.</dd>
- <dt><code>origin-when-cross-origin</code></dt>
- <dd>Send the {{glossary("origin")}}, path, and query string when performing a {{glossary("Same-origin_policy", "same-origin")}} request to the same protocol level. Send origin (only) for cross origin requests and requests to less secure destinations.</dd>
- <dt><code>same-origin</code></dt>
- <dd>Send the {{glossary("origin")}}, path, and query string for {{glossary("Same-origin_policy", "same-origin")}} requests. Don't send the {{HTTPHeader("Referer")}} header for cross-origin requests.</dd>
- <dt><code>strict-origin</code></dt>
- <dd>Send the origin (only) when the protocol security level stays the same (HTTPS→HTTPS). Don't send the {{HTTPHeader("Referer")}} header to less secure destinations (HTTPS→HTTP).</dd>
- <dt><code>strict-origin-when-cross-origin</code> (default)</dt>
- <dd>Send the origin, path, and querystring when performing a same-origin request. For cross-origin requests send the origin (only) when the protocol security level stays same (HTTPS→HTTPS). Don't send the {{HTTPHeader("Referer")}} header to less secure destinations (HTTPS→HTTP).
-
-  <div class="notecard note">
-    <p><strong>Note:</strong> This is the default policy if no policy is specified, or if the provided value is invalid (see spec revision <a href="https://github.com/whatwg/fetch/pull/1066">November 2020</a>). Previously the default was <code>no-referrer-when-downgrade</code>.    </p>
-  </div>
- </dd>
- <dt><code>unsafe-url</code></dt>
- <dd>Send the origin, path, and query string when performing any request, regardless of security.
- <div class="notecard warning">
-   <p><strong>Warning:</strong> This policy will leak potentially-private information from HTTPS resource URLs to insecure origins. Carefully consider the impact of this setting.</p>
- </div>
- </dd>
-</dl>
-
-<h2 id="Integration_with_HTML">Integration with HTML</h2>
-
-<p>You can also set referrer policies inside HTML. For example, you can set the referrer policy for the entire document with a {{HTMLElement("meta")}} element with a <a href="/en-US/docs/Web/HTML/Element/meta#attr-name">name</a> of <code>referrer</code>:</p>
-
-<pre class="brush: html">&lt;meta name="referrer" content="origin"&gt;</pre>
-
-<p>Or set it for individual requests with the <code>referrerpolicy</code> attribute on {{HTMLElement("a")}}, {{HTMLElement("area")}}, {{HTMLElement("img")}}, {{HTMLElement("iframe")}}, {{HTMLElement("script")}}, or {{HTMLElement("link")}} elements:</p>
-
-<pre class="brush: html">&lt;a href="http://example.com" referrerpolicy="origin"&gt;</pre>
-
-<p>Alternatively, a <code>noreferrer</code> <a href="/en-US/docs/Web/HTML/Link_types">link relation</a> on an <code>a</code>, <code>area</code>, or <code>link</code> element can be set:</p>
-
-<pre class="brush: html">&lt;a href="http://example.com" rel="noreferrer"&gt;</pre>
-
-<div class="notecard warning">
-  <p><strong>Warning:</strong> As seen above, the <code>noreferrer</code> link relation is written without a dash — <code>noreferrer</code>. When the referrer policy is specified for the entire document with a {{HTMLElement("meta")}} element, it's written <em>with</em> a dash: <code>&lt;meta name="referrer" content="no-referrer"&gt;</code>.</p>
-</div>
-
-<h2 id="Integration_with_CSS">Integration with CSS</h2>
-
-<p>CSS can fetch resources referenced from stylesheets. These resources follow a referrer policy as well:</p>
-
-<ul>
- <li>External CSS stylesheets use the default policy (<code>strict-origin-when-cross-origin</code>), unless it's overwritten via a <code>Referrer-Policy</code> HTTP header on the CSS stylesheet's response.</li>
- <li>For {{HTMLElement("style")}} elements or <a href="/en-US/docs/Web/API/HTMLElement/style"><code>style</code> attributes</a>, the owner document's referrer policy is used.</li>
-</ul>
-
-<h2 id="Examples">Examples</h2>
-
-<h3><code>no-referrer</code></h3>
-<table>
-  <tr>
-    <th>From document</th>
-    <th>Navigation to</th>
-    <th>Referrer used</th>
-  </tr>
-  <tr>
-    <td>https://example.com/page</td>
-    <td><em>anywhere</em></td>
-    <td><em>(no referrer)</em></td>
-  </tr>
-</table>
+```
 
-<h3><code>no-referrer-when-downgrade</code></h3>
-<table>
-  <tr>
-    <th>From document</th>
-    <th>Navigation to</th>
-    <th>Referrer used</th>
-  </tr>
-  <tr>
-    <td>https://example.com/page</td>
-    <td>https://example.com/otherpage</td>
-    <td>https://example.com/page</td>
-  </tr>
-  <tr>
-    <td>https://example.com/page</td>
-    <td>https://mozilla.org</td>
-    <td>https://example.com/page</td>
-  </tr>
-  <tr>
-    <td>https://example.com/page</td>
-    <td><strong>http</strong>://example.com</td>
-    <td><em>(no referrer)</em></td>
-  </tr>
-</table>
+> **Note:** The original header name {{HTTPHeader("Referer")}} is a misspelling of the word "referrer". The `Referrer-Policy` header does not share this misspelling.
 
-<h3><code>origin</code></h3>
-<table>
-  <tr>
-    <th>From document</th>
-    <th>Navigation to</th>
-    <th>Referrer used</th>
-  </tr>
-  <tr>
-    <td>https://example.com/page</td>
-    <td><em>anywhere</em></td>
-    <td>https://example.com/</td>
-  </tr>
-</table>
+## Directives
 
-<h3><code>origin-when-cross-origin</code></h3>
-<table>
-  <tr>
-    <th>From document</th>
-    <th>Navigation to</th>
-    <th>Referrer used</th>
-  </tr>
-  <tr>
-    <td>https://example.com/page</td>
-    <td>https://example.com/otherpage</td>
-    <td>https://example.com/page</td>
-  </tr>
-  <tr>
-    <td>https://example.com/page</td>
-    <td>https://mozilla.org</td>
-    <td>https://example.com/</td>
-  </tr>
-  <tr>
-    <td>https://example.com/page</td>
-    <td><strong>http</strong>://example.com/page</td>
-    <td>https://example.com/</td>
-  </tr>
-</table>
+- `no-referrer`
+  - : The {{HTTPHeader("Referer")}} header will be omitted entirely. No referrer information is sent along with requests.
+- `no-referrer-when-downgrade`
+  - : Send the {{glossary("origin")}}, path, and querystring in {{HTTPHeader("Referer")}} when the protocol security level stays the same or improves (HTTP→HTTP, HTTP→HTTPS, HTTPS→HTTPS). Don't send the {{HTTPHeader("Referer")}} header for requests to less secure destinations (HTTPS→HTTP, HTTPS→file).
+- `origin`
+  - : Send the {{glossary("origin")}} (only) in the {{HTTPHeader("Referer")}} header.
+    For example, a document at `https://example.com/page.html` will send the referrer `https://example.com/`.
+- `origin-when-cross-origin`
+  - : Send the {{glossary("origin")}}, path, and query string when performing a {{glossary("Same-origin_policy", "same-origin")}} request to the same protocol level. Send origin (only) for cross origin requests and requests to less secure destinations.
+- `same-origin`
+  - : Send the {{glossary("origin")}}, path, and query string for {{glossary("Same-origin_policy", "same-origin")}} requests. Don't send the {{HTTPHeader("Referer")}} header for cross-origin requests.
+- `strict-origin`
+  - : Send the origin (only) when the protocol security level stays the same (HTTPS→HTTPS). Don't send the {{HTTPHeader("Referer")}} header to less secure destinations (HTTPS→HTTP).
+- `strict-origin-when-cross-origin` (default)
 
-<h3>><code>same-origin</code></h3>
-<table>
-  <tr>
-    <th>From document</th>
-    <th>Navigation to</th>
-    <th>Referrer used</th>
-  </tr>
-  <tr>
-    <td>https://example.com/page</td>
-    <td>https://example.com/otherpage</td>
-    <td>https://example.com/page</td>
-  </tr>
-  <tr>
-    <td>https://example.com/page</td>
-    <td>https://mozilla.org</td>
-    <td><em>(no referrer)</em></td>
-  </tr>
-</table>
+  - : Send the origin, path, and querystring when performing a same-origin request. For cross-origin requests send the origin (only) when the protocol security level stays same (HTTPS→HTTPS). Don't send the {{HTTPHeader("Referer")}} header to less secure destinations (HTTPS→HTTP).
 
-<h3><code>strict-origin</code></h3>
-<table>
-  <tr>
-    <th>From document</th>
-    <th>Navigation to</th>
-    <th>Referrer used</th>
-  </tr>
-  <tr>
-    <td>https://example.com/page</td>
-    <td>https://mozilla.org</td>
-    <td>https://example.com/</td>
-  </tr>
-  <tr>
-    <td>https://example.com/page</td>
-    <td><strong>http</strong>://example.com</td>
-    <td><em>(no referrer)</em></td>
-  </tr>
-  <tr>
-    <td><strong>http</strong>://example.com/page</td>
-    <td><em>anywhere</em></td>
-    <td>http://example.com/</td>
-  </tr>
-</table>
+    > **Note:** This is the default policy if no policy is specified, or if the provided value is invalid (see spec revision [November 2020](https://github.com/whatwg/fetch/pull/1066)). Previously the default was `no-referrer-when-downgrade`.
 
-<h3><code>strict-origin-when-cross-origin</code></h3>
-<table>
-  <tr>
-    <th>From document</th>
-    <th>Navigation to</th>
-    <th>Referrer used</th>
-  </tr>
-  <tr>
-    <td>https://example.com/page</td>
-    <td>https://example.com/otherpage</td>
-    <td>https://example.com/page</td>
-  </tr>
-  <tr>
-    <td>https://example.com/page</td>
-    <td>https://mozilla.org</td>
-    <td>https://example.com/</td>
-  </tr>
-  <tr>
-    <td>https://example.com/page</td>
-    <td><strong>http</strong>://example.com</td>
-    <td><em>(no referrer)</em></td>
-  </tr>
-</table>
+- `unsafe-url`
 
-<h3><code>unsafe-url</code></h3>
-<table>
-  <tr>
-    <th>From document</th>
-    <th>Navigation to</th>
-    <th>Referrer used</th>
-  </tr>
-  <tr>
-    <td>https://example.com/page?q=123</td>
-    <td><em>anywhere</em></td>
-    <td>https://example.com/page?q=123</td>
-  </tr>
-</table>
+  - : Send the origin, path, and query string when performing any request, regardless of security.
+
+    > **Warning:** This policy will leak potentially-private information from HTTPS resource URLs to insecure origins. Carefully consider the impact of this setting.
+
+## Integration with HTML
+
+You can also set referrer policies inside HTML. For example, you can set the referrer policy for the entire document with a {{HTMLElement("meta")}} element with a [name](/en-US/docs/Web/HTML/Element/meta#attr-name) of `referrer`:
+
+```html
+<meta name="referrer" content="origin">
+```
+
+Or set it for individual requests with the `referrerpolicy` attribute on {{HTMLElement("a")}}, {{HTMLElement("area")}}, {{HTMLElement("img")}}, {{HTMLElement("iframe")}}, {{HTMLElement("script")}}, or {{HTMLElement("link")}} elements:
+
+```html
+<a href="http://example.com" referrerpolicy="origin">
+```
+
+Alternatively, a `noreferrer` [link relation](/en-US/docs/Web/HTML/Link_types) on an `a`, `area`, or `link` element can be set:
+
+```html
+<a href="http://example.com" rel="noreferrer">
+```
+
+> **Warning:** As seen above, the `noreferrer` link relation is written without a dash — `noreferrer`. When the referrer policy is specified for the entire document with a {{HTMLElement("meta")}} element, it's written _with_ a dash: `<meta name="referrer" content="no-referrer">`.
+
+## Integration with CSS
+
+CSS can fetch resources referenced from stylesheets. These resources follow a referrer policy as well:
+
+- External CSS stylesheets use the default policy (`strict-origin-when-cross-origin`), unless it's overwritten via a `Referrer-Policy` HTTP header on the CSS stylesheet's response.
+- For {{HTMLElement("style")}} elements or [`style` attributes](/en-US/docs/Web/API/HTMLElement/style), the owner document's referrer policy is used.
+
+## Examples
+
+### `no-referrer`
+
+| From document            | Navigation to | Referrer used   |
+| ------------------------ | ------------- | --------------- |
+| https://example.com/page | _anywhere_    | _(no referrer)_ |
+
+### `no-referrer-when-downgrade`
+
+| From document            | Navigation to                 | Referrer used            |
+| ------------------------ | ----------------------------- | ------------------------ |
+| https://example.com/page | https://example.com/otherpage | https://example.com/page |
+| https://example.com/page | https://mozilla.org           | https://example.com/page |
+| https://example.com/page | **http**://example.com        | _(no referrer)_          |
+
+### `origin`
+
+| From document            | Navigation to | Referrer used        |
+| ------------------------ | ------------- | -------------------- |
+| https://example.com/page | _anywhere_    | https://example.com/ |
+
+### `origin-when-cross-origin`
+
+| From document            | Navigation to                 | Referrer used            |
+| ------------------------ | ----------------------------- | ------------------------ |
+| https://example.com/page | https://example.com/otherpage | https://example.com/page |
+| https://example.com/page | https://mozilla.org           | https://example.com/     |
+| https://example.com/page | **http**://example.com/page   | https://example.com/     |
+
+### >`same-origin`
+
+| From document            | Navigation to                 | Referrer used            |
+| ------------------------ | ----------------------------- | ------------------------ |
+| https://example.com/page | https://example.com/otherpage | https://example.com/page |
+| https://example.com/page | https://mozilla.org           | _(no referrer)_          |
+
+### `strict-origin`
+
+| From document               | Navigation to          | Referrer used        |
+| --------------------------- | ---------------------- | -------------------- |
+| https://example.com/page    | https://mozilla.org    | https://example.com/ |
+| https://example.com/page    | **http**://example.com | _(no referrer)_      |
+| **http**://example.com/page | _anywhere_             | http://example.com/  |
+
+### `strict-origin-when-cross-origin`
+
+| From document            | Navigation to                 | Referrer used            |
+| ------------------------ | ----------------------------- | ------------------------ |
+| https://example.com/page | https://example.com/otherpage | https://example.com/page |
+| https://example.com/page | https://mozilla.org           | https://example.com/     |
+| https://example.com/page | **http**://example.com        | _(no referrer)_          |
+
+### `unsafe-url`
+
+| From document                  | Navigation to | Referrer used                  |
+| ------------------------------ | ------------- | ------------------------------ |
+| https://example.com/page?q=123 | _anywhere_    | https://example.com/page?q=123 |
+
+### Specifying a fallback policy
+
+If you want to specify a fallback policy in any case the desired policy hasn't got wide enough browser support, use a comma-separated list with the desired policy specified last:
 
-<h3 id="Specifying_a_fallback_policy">Specifying a fallback policy</h3>
+    Referrer-Policy: no-referrer, strict-origin-when-cross-origin
 
-<p>If you want to specify a fallback policy in any case the desired policy hasn't got wide enough browser support, use a comma-separated list with the desired policy specified last:</p>
+In the above scenario, `no-referrer` will only be used if `strict-origin-when-cross-origin` is not supported by the browser.
 
-<pre>Referrer-Policy: no-referrer, strict-origin-when-cross-origin</pre>
+> **Note:** Specifying multiple values is only supported in the `Referrer-Policy` HTTP header, and not in the `referrerpolicy` attribute.
 
-<p>In the above scenario, <code>no-referrer</code> will only be used if <code>strict-origin-when-cross-origin</code> is not supported by the browser.</p>
+## Browser-specific preferences/settings
 
-<div class="notecard note">
-  <p><strong>Note:</strong> Specifying multiple values is only supported in the <code>Referrer-Policy</code> HTTP header, and not in the <code>referrerpolicy</code> attribute.</p>
-</div>
+### Firefox preferences
 
-<h2 id="Browser-specific_preferencessettings">Browser-specific preferences/settings</h2>
-<h3 id="Firefox_preferences">Firefox preferences</h3>
+Firefox preferences can be used to configure the _default_ referrer policy. The preference names are version specific:
 
-<p>Firefox preferences can be used to configure the <em>default</em> referrer policy. The preference names are version specific:</p>
-<ul>
-  <li>Firefox version 59 and later: <code>network.http.referer.defaultPolicy</code> (and <code>network.http.referer.defaultPolicy.pbmode</code> for private networks)</li>
-  <li>Firefox versions 53 to 58: <code>network.http.referer.userControlPolicy</code></li>
-</ul>
-<p>All of these settings take the same set of values: <code>0 = no-referrer</code>, <code>1 = same-origin</code>, <code>2 = strict-origin-when-cross-origin</code>, <code>3 = no-referrer-when-downgrade</code>.</p>
+- Firefox version 59 and later: `network.http.referer.defaultPolicy` (and `network.http.referer.defaultPolicy.pbmode` for private networks)
+- Firefox versions 53 to 58: `network.http.referer.userControlPolicy`
 
+All of these settings take the same set of values: `0 = no-referrer`, `1 = same-origin`, `2 = strict-origin-when-cross-origin`, `3 = no-referrer-when-downgrade`.
 
-<h2 id="Specifications">Specifications</h2>
+## Specifications
 
 {{Specifications}}
 
-<h2 id="Browser_compatibility">Browser compatibility</h2>
+## Browser compatibility
 
-<p>{{Compat}}</p>
+{{Compat}}
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
- <li><a href="/en-US/docs/Web/Security/Referer_header:_privacy_and_security_concerns">Web security > Referer header: privacy and security concerns</a></li>
- <li>{{interwiki("wikipedia", "HTTP_referer", "HTTP referer on Wikipedia")}}</li>
- <li>When using <a href="/en-US/docs/Web/API/Fetch_API">Fetch</a>: {{domxref("Request.referrerPolicy")}}</li>
- <li>The obsolete {{HTTPHeader("Content-Security-Policy")}}'s {{HTTPHeader("Content-Security-Policy/referrer", "referrer")}} {{deprecated_inline}} directive.</li>
- <li><a href="/en-US/docs/Web/Security/Same-origin_policy">Same-origin policy</a></li>
- <li>
-  <p><a href="https://blog.mozilla.org/security/2015/01/21/meta-referrer/">Tighter Control Over Your Referrers – Mozilla Security Blog</a></p>
- </li>
-</ul>
+- [Web security > Referer header: privacy and security concerns](/en-US/docs/Web/Security/Referer_header:_privacy_and_security_concerns)
+- {{interwiki("wikipedia", "HTTP_referer", "HTTP referer on Wikipedia")}}
+- When using [Fetch](/en-US/docs/Web/API/Fetch_API): {{domxref("Request.referrerPolicy")}}
+- The obsolete {{HTTPHeader("Content-Security-Policy")}}'s {{HTTPHeader("Content-Security-Policy/referrer", "referrer")}} {{deprecated_inline}} directive.
+- [Same-origin policy](/en-US/docs/Web/Security/Same-origin_policy)
+- [Tighter Control Over Your Referrers – Mozilla Security Blog](https://blog.mozilla.org/security/2015/01/21/meta-referrer/)
diff --git a/files/en-us/web/http/headers/retry-after/index.md b/files/en-us/web/http/headers/retry-after/index.md
index 4832e3f70c00988..e4ada5166056eea 100644
--- a/files/en-us/web/http/headers/retry-after/index.md
+++ b/files/en-us/web/http/headers/retry-after/index.md
@@ -2,28 +2,26 @@
 title: Retry-After
 slug: Web/HTTP/Headers/Retry-After
 tags:
-- HTTP
-- Reference
-- Response
-- Response Header
-- header
+  - HTTP
+  - Reference
+  - Response
+  - Response Header
+  - header
 browser-compat: http.headers.Retry-After
 ---
-<div>{{HTTPSidebar}}</div>
-
-<p>The <strong><code>Retry-After</code></strong> response HTTP header indicates how long
-  the user agent should wait before making a follow-up request. There are three main cases
-  this header is used:</p>
-
-<ul>
-  <li>When sent with a {{HTTPStatus(503)}} (Service Unavailable) response, this indicates
-    how long the service is expected to be unavailable.</li>
-  <li>When sent with a {{HTTPStatus(429)}} (Too Many Requests) response, this indicates
-    how long to wait before making a new request.</li>
-  <li>When sent with a redirect response, such as {{HTTPStatus(301)}} (Moved Permanently),
-    this indicates the minimum time that the user agent is asked to wait before issuing
-    the redirected request.</li>
-</ul>
+{{HTTPSidebar}}
+
+The **`Retry-After`** response HTTP header indicates how long
+the user agent should wait before making a follow-up request. There are three main cases
+this header is used:
+
+- When sent with a {{HTTPStatus(503)}} (Service Unavailable) response, this indicates
+  how long the service is expected to be unavailable.
+- When sent with a {{HTTPStatus(429)}} (Too Many Requests) response, this indicates
+  how long to wait before making a new request.
+- When sent with a redirect response, such as {{HTTPStatus(301)}} (Moved Permanently),
+  this indicates the minimum time that the user agent is asked to wait before issuing
+  the redirected request.
 
 <table class="properties">
   <tbody>
@@ -38,51 +36,46 @@ browser-compat: http.headers.Retry-After
   </tbody>
 </table>
 
-<h2 id="Syntax">Syntax</h2>
+## Syntax
 
-<pre class="brush: html">Retry-After: &lt;http-date&gt;
-Retry-After: &lt;delay-seconds&gt;
-</pre>
+```html
+Retry-After: <http-date>
+Retry-After: <delay-seconds>
+```
 
-<h2 id="Directives">Directives</h2>
+## Directives
 
-<dl>
-  <dt>&lt;http-date&gt;</dt>
-  <dd>A date after which to retry. See the {{HTTPHeader("Date")}} header for more details
-    on the HTTP date format.</dd>
-  <dt>&lt;delay-seconds&gt;</dt>
-  <dd>A non-negative decimal integer indicating the seconds to delay after the response is
-    received.</dd>
-</dl>
+- \<http-date>
+  - : A date after which to retry. See the {{HTTPHeader("Date")}} header for more details
+    on the HTTP date format.
+- \<delay-seconds>
+  - : A non-negative decimal integer indicating the seconds to delay after the response is
+    received.
 
-<h2 id="Examples">Examples</h2>
+## Examples
 
-<h3 id="Dealing_with_scheduled_downtime">Dealing with scheduled downtime</h3>
+### Dealing with scheduled downtime
 
-<p>Support for the <code>Retry-After</code> header on both clients and servers is still
-  inconsistent. However, some crawlers and spiders, like the Googlebot, honor the
-  <code>Retry-After</code> header. It is useful to send it along with a
-  {{HTTPStatus(503)}} (Service Unavailable) response, so that search engines will keep
-  indexing your site when the downtime is over.</p>
+Support for the `Retry-After` header on both clients and servers is still
+inconsistent. However, some crawlers and spiders, like the Googlebot, honor the
+`Retry-After` header. It is useful to send it along with a
+{{HTTPStatus(503)}} (Service Unavailable) response, so that search engines will keep
+indexing your site when the downtime is over.
 
-<pre>Retry-After: Wed, 21 Oct 2015 07:28:00 GMT
-Retry-After: 120
-</pre>
+    Retry-After: Wed, 21 Oct 2015 07:28:00 GMT
+    Retry-After: 120
 
-<h2 id="Specifications">Specifications</h2>
+## Specifications
 
 {{Specifications}}
 
-<h2 id="Browser_compatibility">Browser compatibility</h2>
+## Browser compatibility
 
-<p>{{Compat}}</p>
+{{Compat}}
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
-  <li><a
-      href="https://webmasters.googleblog.com/2011/01/how-to-deal-with-planned-site-downtime.html">Google
-      Webmaster blog: How to deal with planned site downtime</a></li>
-  <li>{{HTTPStatus(503)}} (Service Unavailable)</li>
-  <li>{{HTTPStatus(301)}} (Moved Permanently)</li>
-</ul>
+- [Google
+  Webmaster blog: How to deal with planned site downtime](https://webmasters.googleblog.com/2011/01/how-to-deal-with-planned-site-downtime.html)
+- {{HTTPStatus(503)}} (Service Unavailable)
+- {{HTTPStatus(301)}} (Moved Permanently)
diff --git a/files/en-us/web/http/headers/rtt/index.md b/files/en-us/web/http/headers/rtt/index.md
index 7c99a18c7e0c47d..3fb9209949cecc0 100644
--- a/files/en-us/web/http/headers/rtt/index.md
+++ b/files/en-us/web/http/headers/rtt/index.md
@@ -11,73 +11,68 @@ tags:
   - Experimental
 browser-compat: http.headers.rtt
 ---
-<div>{{HTTPSidebar}} {{SeeCompatTable}}</div>
+{{HTTPSidebar}} {{SeeCompatTable}}
 
-<p>The <strong><code>RTT</code></strong> {{Glossary("Client hints","network client hint")}} request header field provides the approximate round trip time on the application layer, in milliseconds. The RTT hint, unlike transport layer RTT, includes server processing time.</p>
+The **`RTT`** {{Glossary("Client hints","network client hint")}} request header field provides the approximate round trip time on the application layer, in milliseconds. The RTT hint, unlike transport layer RTT, includes server processing time.
 
 <table class="properties">
   <tbody>
-   <tr>
-    <th scope="row">Header type</th>
-    <td>{{Glossary("Request header")}}, {{Glossary("Client hints","Client hint")}}</td>
-   </tr>
-   <tr>
-    <th scope="row">{{Glossary("Forbidden header name")}}</th>
-    <td>no</td>
-   </tr>
+    <tr>
+      <th scope="row">Header type</th>
+      <td>
+        {{Glossary("Request header")}},
+        {{Glossary("Client hints","Client hint")}}
+      </td>
+    </tr>
+    <tr>
+      <th scope="row">{{Glossary("Forbidden header name")}}</th>
+      <td>no</td>
+    </tr>
   </tbody>
- </table>
+</table>
 
-<p>The RTT value is rounded to the nearest 25 milliseconds to prevent fingerprinting; There are many other mechanisms an attacker might use to obtain similar round-trip information.</p>
+The RTT value is rounded to the nearest 25 milliseconds to prevent fingerprinting; There are many other mechanisms an attacker might use to obtain similar round-trip information.
 
-<p>The hint allows a server to choose what information is sent based on the network responsiveness/latency. For example, it might choose to send fewer resources.</p>
+The hint allows a server to choose what information is sent based on the network responsiveness/latency. For example, it might choose to send fewer resources.
 
-<div class="notecard note">
-  <p><strong>Note:</strong> The {{HTTPHeader("Vary")}} header is used in responses to indicate that a different resource is sent for every different value of the header (see <a href="/en-US/docs/Web/HTTP/Caching#varying_responses">HTTP Caching > Varying responses</a>). Even if {{HTTPHeader("RTT")}} is used to configure what resources are sent consider omitting it in the {{HTTPHeader("Vary")}} header  — it is likely to change often, which effectively makes the resource uncachable.</p>
-</div>
+> **Note:** The {{HTTPHeader("Vary")}} header is used in responses to indicate that a different resource is sent for every different value of the header (see [HTTP Caching > Varying responses](/en-US/docs/Web/HTTP/Caching#varying_responses)). Even if {{HTTPHeader("RTT")}} is used to configure what resources are sent consider omitting it in the {{HTTPHeader("Vary")}} header — it is likely to change often, which effectively makes the resource uncachable.
 
-<h2 id="Syntax">Syntax</h2>
+## Syntax
 
-<pre>RTT: &lt;number&gt;</pre>
+    RTT: <number>
 
-<h2 id="Directives">Directives</h2>
+## Directives
 
-<dl>
- <dt>&lt;number&gt;</dt>
- <dd>The approximate round trip time in milliseconds, rounded to the nearest 25 milliseconds.</dd>
-</dl>
+- \<number>
+  - : The approximate round trip time in milliseconds, rounded to the nearest 25 milliseconds.
 
-<h2 id="Examples">Examples</h2>
+## Examples
 
-<p>A server first needs to opt in to receive the <code>RTT</code> header by sending the {{HTTPHeader("Accept-CH")}} response header containing <code>RTT</code>.</p>
+A server first needs to opt in to receive the `RTT` header by sending the {{HTTPHeader("Accept-CH")}} response header containing `RTT`.
 
-<pre>Accept-CH: RTT</pre>
+    Accept-CH: RTT
 
-<p>Then on subsequent requests the client might send an <code>RTT</code> header back:</p>
+Then on subsequent requests the client might send an `RTT` header back:
 
-<pre>RTT: 125</pre>
+    RTT: 125
 
-<h2 id="Specifications">Specifications</h2>
+## Specifications
 
-<p>{{Specifications}}</p>
+{{Specifications}}
 
-<h2 id="Browser_compatibility">Browser compatibility</h2>
+## Browser compatibility
 
-<p>{{Compat}}</p>
+{{Compat}}
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
-  <li><a href="https://developers.google.com/web/fundamentals/performance/optimizing-content-efficiency/client-hints">Adapting to Users with Client Hints</a> (developer.google.com)</li>
- <li>Network client hints
-  <ul>
-    <li>{{HTTPHeader("Downlink")}}</li>
-    <li>{{HTTPHeader("ECT")}}</li>
-    <li>{{HTTPHeader("Save-Data")}}</li>
-   </ul>
- </li>
- <li>{{HTTPHeader("Accept-CH")}}</li>
- <li><a href="/en-US/docs/Web/HTTP/Caching#varying_responses">HTTP Caching > Varying responses</a> and {{HTTPHeader("Vary")}}</li>
- <li>{{domxref("NetworkInformation.effectiveType")}}</li>
-</ul>
+- [Adapting to Users with Client Hints](https://developers.google.com/web/fundamentals/performance/optimizing-content-efficiency/client-hints) (developer.google.com)
+- Network client hints
 
+  - {{HTTPHeader("Downlink")}}
+  - {{HTTPHeader("ECT")}}
+  - {{HTTPHeader("Save-Data")}}
+
+- {{HTTPHeader("Accept-CH")}}
+- [HTTP Caching > Varying responses](/en-US/docs/Web/HTTP/Caching#varying_responses) and {{HTTPHeader("Vary")}}
+- {{domxref("NetworkInformation.effectiveType")}}
diff --git a/files/en-us/web/http/headers/save-data/index.md b/files/en-us/web/http/headers/save-data/index.md
index 4ae32ed3cdab1bf..47155d7de8a9152 100644
--- a/files/en-us/web/http/headers/save-data/index.md
+++ b/files/en-us/web/http/headers/save-data/index.md
@@ -10,121 +10,114 @@ tags:
   - Request header
 browser-compat: http.headers.Save-Data
 ---
-<p>{{HTTPSidebar}}</p>
+{{HTTPSidebar}}
 
-<p>The <strong><code>Save-Data</code></strong> {{Glossary("Client hints","network client hint")}} request header field is a boolean which indicates the client's preference for reduced data usage. This could be for reasons such as high transfer costs, slow connection speeds, etc.</p>
+The **`Save-Data`** {{Glossary("Client hints","network client hint")}} request header field is a boolean which indicates the client's preference for reduced data usage. This could be for reasons such as high transfer costs, slow connection speeds, etc.
 
-  <table class="properties">
-    <tbody>
-     <tr>
+<table class="properties">
+  <tbody>
+    <tr>
       <th scope="row">Header type</th>
-      <td>{{Glossary("Request header")}}, {{Glossary("Client hints","Client hint")}}</td>
-     </tr>
-     <tr>
+      <td>
+        {{Glossary("Request header")}},
+        {{Glossary("Client hints","Client hint")}}
+      </td>
+    </tr>
+    <tr>
       <th scope="row">{{Glossary("Forbidden header name")}}</th>
       <td>no</td>
-     </tr>
-     <tr>
-      <th scope="row">{{Glossary("CORS-safelisted response header")}}</th>
+    </tr>
+    <tr>
+      <th scope="row">
+        {{Glossary("CORS-safelisted response header")}}
+      </th>
       <td>no</td>
-     </tr>
-    </tbody>
-   </table>
+    </tr>
+  </tbody>
+</table>
 
-<p>A value of <code>On</code> indicates explicit user opt-in into a reduced data usage
-  mode on the client, and when communicated to origins allows them to deliver alternative
-  content to reduce the data downloaded such as smaller image and video resources,
-  different markup and styling, disabled polling and automatic updates, and so on.</p>
+A value of `On` indicates explicit user opt-in into a reduced data usage
+mode on the client, and when communicated to origins allows them to deliver alternative
+content to reduce the data downloaded such as smaller image and video resources,
+different markup and styling, disabled polling and automatic updates, and so on.
 
-<div class="notecard note">
-  <p><strong>Note:</strong> Disabling HTTP/2 Server Push ({{RFC("7540", "Server Push",
-    "8.2")}}) might be desirable too for reducing data downloads.</p>
-</div>
+> **Note:** Disabling HTTP/2 Server Push ({{RFC("7540", "Server Push",
+    "8.2")}}) might be desirable too for reducing data downloads.
 
-<div class="notecard note">
-  <p><strong>Note:</strong> The <strong><code>Save-Data</code></strong> {{Glossary("Client hints","network client hint")}} should be used to reduce data set to the client irrespective of the values of other client client hints that indicate network capability, like {{HTTPHeader("Downlink")}} and {{HTTPHeader("RTT")}}.</p>
-</div>
+> **Note:** The **`Save-Data`** {{Glossary("Client hints","network client hint")}} should be used to reduce data set to the client irrespective of the values of other client client hints that indicate network capability, like {{HTTPHeader("Downlink")}} and {{HTTPHeader("RTT")}}.
 
-<h2 id="Syntax">Syntax</h2>
+## Syntax
 
-<pre>Save-Data: &lt;sd-token&gt;</pre>
+    Save-Data: <sd-token>
 
-<h2 id="Directives">Directives</h2>
+## Directives
 
-<dl>
-  <dt><code>&lt;sd-token&gt;</code></dt>
-  <dd>A value indicating whether the client wants to opt in to reduced data
-    usage mode. <code>on</code> indicates yes, while <code>off</code> (the default)
-    indicates no.</dd>
-</dl>
+- `<sd-token>`
+  - : A value indicating whether the client wants to opt in to reduced data
+    usage mode. `on` indicates yes, while `off` (the default)
+    indicates no.
 
-<h2 id="Examples">Examples</h2>
+## Examples
 
-<p>The {{HTTPHeader("Vary")}} header ensures that the content is cached properly (for
-  instance ensuring that the user is not served a lower-quality image from the cache when
-  <code>Save-Data</code> header is no longer present [<em>e.g.</em> after having switched
-  from cellular to Wi-Fi]).</p>
+The {{HTTPHeader("Vary")}} header ensures that the content is cached properly (for
+instance ensuring that the user is not served a lower-quality image from the cache when
+`Save-Data` header is no longer present \[_e.g._ after having switched
+from cellular to Wi-Fi]).
 
-<h3 id="With_Save-Data_on">With <code>Save-Data: on</code></h3>
+### With `Save-Data: on`
 
-<p>Request:</p>
+Request:
 
-<pre>GET /image.jpg HTTP/1.0
-Host: example.com
-Save-Data: on</pre>
+    GET /image.jpg HTTP/1.0
+    Host: example.com
+    Save-Data: on
 
-<p>Response:</p>
+Response:
 
-<pre>HTTP/1.0 200 OK
-Content-Length: 102832
-Vary: Accept-Encoding, Save-Data
-Cache-Control: public, max-age=31536000
-Content-Type: image/jpeg
+    HTTP/1.0 200 OK
+    Content-Length: 102832
+    Vary: Accept-Encoding, Save-Data
+    Cache-Control: public, max-age=31536000
+    Content-Type: image/jpeg
 
-[...]
-</pre>
+    [...]
 
-<h3 id="Without_Save-Data">Without <code>Save-Data</code></h3>
+### Without `Save-Data`
 
-<p>Request:</p>
+Request:
 
-<pre>GET /image.jpg HTTP/1.0
-Host: example.com
-</pre>
+    GET /image.jpg HTTP/1.0
+    Host: example.com
 
-<p>Response:</p>
+Response:
 
-<pre>HTTP/1.0 200 OK
-Content-Length: 481770
-Vary: Accept-Encoding, Save-Data
-Cache-Control: public, max-age=31536000
-Content-Type: image/jpeg
+    HTTP/1.0 200 OK
+    Content-Length: 481770
+    Vary: Accept-Encoding, Save-Data
+    Cache-Control: public, max-age=31536000
+    Content-Type: image/jpeg
 
-[...]
-</pre>
+    [...]
 
-<h2 id="Specifications">Specifications</h2>
+## Specifications
 
-<p>{{Specifications}}</p>
+{{Specifications}}
 
-<h2 id="Browser_compatibility">Browser compatibility</h2>
+## Browser compatibility
 
-<p>{{Compat}}</p>
+{{Compat}}
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
-  <li><a href="https://css-tricks.com/help-users-save-data/">Help Your Users `Save-Data` - CSS Tricks</a></li>
-  <li><a href="https://developers.google.com/web/fundamentals/performance/optimizing-content-efficiency/save-data/">Delivering Fast and Light Applications with Save-Data - Google Developers</a></li>
-  <li>{{HTTPHeader("Vary")}} header which indicate that the content served varies by <code>Save-Data</code> (see <a href="/en-US/docs/Web/HTTP/Caching#varying_responses">HTTP Caching > Varying responses</a>)</li>
-  <li>CSS @media feature <code><a href="/en-US/docs/Web/CSS/@media/prefers-reduced-data">prefers-reduced-data</a></code> {{experimental_inline}}</li>
-  <li><a href="https://developers.google.com/web/fundamentals/performance/optimizing-content-efficiency/client-hints">Adapting to Users with Client Hints</a> (developer.google.com)</li>
-    <li>Network client hints
-      <ul>
-       <li>{{HTTPHeader("Downlink")}}</li>
-       <li>{{HTTPHeader("RTT")}}</li>
-       <li>{{HTTPHeader("ECT")}}</li>
-      </ul>
-  </li>
-  <li>{{domxref("NetworkInformation.saveData")}}</li>
-</ul>
+- [Help Your Users \`Save-Data\` - CSS Tricks](https://css-tricks.com/help-users-save-data/)
+- [Delivering Fast and Light Applications with Save-Data - Google Developers](https://developers.google.com/web/fundamentals/performance/optimizing-content-efficiency/save-data/)
+- {{HTTPHeader("Vary")}} header which indicate that the content served varies by `Save-Data` (see [HTTP Caching > Varying responses](/en-US/docs/Web/HTTP/Caching#varying_responses))
+- CSS @media feature [`prefers-reduced-data`](/en-US/docs/Web/CSS/@media/prefers-reduced-data) {{experimental_inline}}
+- [Adapting to Users with Client Hints](https://developers.google.com/web/fundamentals/performance/optimizing-content-efficiency/client-hints) (developer.google.com)
+- Network client hints
+
+  - {{HTTPHeader("Downlink")}}
+  - {{HTTPHeader("RTT")}}
+  - {{HTTPHeader("ECT")}}
+
+- {{domxref("NetworkInformation.saveData")}}
diff --git a/files/en-us/web/http/headers/sec-fetch-dest/index.md b/files/en-us/web/http/headers/sec-fetch-dest/index.md
index 5f1dfe2dd28d307..64dcb502a9bede4 100644
--- a/files/en-us/web/http/headers/sec-fetch-dest/index.md
+++ b/files/en-us/web/http/headers/sec-fetch-dest/index.md
@@ -10,135 +10,127 @@ tags:
   - Request header
 browser-compat: http.headers.Sec-Fetch-Dest
 ---
-<p>{{HTTPSidebar}}</p>
+{{HTTPSidebar}}
 
-<p>The <strong><code>Sec-Fetch-Dest</code></strong> {{Glossary("Fetch metadata request header", "fetch metadata request header")}} indicates the request's <em>destination</em>. That is the initiator of the original fetch request, which is where (and how) the fetched data will be used.</p>
+The **`Sec-Fetch-Dest`** {{Glossary("Fetch metadata request header", "fetch metadata request header")}} indicates the request's _destination_. That is the initiator of the original fetch request, which is where (and how) the fetched data will be used.
 
-<p>This allows servers determine whether to service a request based on whether it is appropriate for how it is <em>expected</em> to be used. For example, a request with an <code>audio</code> destination should request audio data, not some other type of resource (for example, a document that includes senstive user information).</p>
+This allows servers determine whether to service a request based on whether it is appropriate for how it is _expected_ to be used. For example, a request with an `audio` destination should request audio data, not some other type of resource (for example, a document that includes senstive user information).
 
 <table class="properties">
-	<tbody>
-		<tr>
-			<th scope="row">Header type</th>
-			<td>{{Glossary("Fetch Metadata Request Header")}}</td>
-		</tr>
-		<tr>
-			<th scope="row">{{Glossary("Forbidden header name")}}</th>
-			<td>yes (prefix <code>Sec-</code>)</td>
-		</tr>
-		<tr>
-			<th scope="row">{{Glossary("CORS-safelisted request header")}}</th>
-			<td>no</td>
-		</tr>
-	</tbody>
+  <tbody>
+    <tr>
+      <th scope="row">Header type</th>
+      <td>{{Glossary("Fetch Metadata Request Header")}}</td>
+    </tr>
+    <tr>
+      <th scope="row">{{Glossary("Forbidden header name")}}</th>
+      <td>yes (prefix <code>Sec-</code>)</td>
+    </tr>
+    <tr>
+      <th scope="row">
+        {{Glossary("CORS-safelisted request header")}}
+      </th>
+      <td>no</td>
+    </tr>
+  </tbody>
 </table>
 
-<h2 id="Syntax">Syntax</h2>
-
-<pre>Sec-Fetch-Dest: audio
-Sec-Fetch-Dest: audioworklet
-Sec-Fetch-Dest: document
-Sec-Fetch-Dest: embed
-Sec-Fetch-Dest: empty
-Sec-Fetch-Dest: font
-Sec-Fetch-Dest: frame
-Sec-Fetch-Dest: iframe
-Sec-Fetch-Dest: image
-Sec-Fetch-Dest: manifest
-Sec-Fetch-Dest: object
-Sec-Fetch-Dest: paintworklet
-Sec-Fetch-Dest: report
-Sec-Fetch-Dest: script
-Sec-Fetch-Dest: serviceworker
-Sec-Fetch-Dest: sharedworker
-Sec-Fetch-Dest: style
-Sec-Fetch-Dest: track
-Sec-Fetch-Dest: video
-Sec-Fetch-Dest: worker
-Sec-Fetch-Dest: xslt
-</pre>
-
-<p>Servers should ignore this header if it contains any other value.</p>
-
-<h2 id="Directives">Directives</h2>
-
-<div class="notecard note">
-	<p><strong>Note:</strong> These directives correspond to the values returned by {{domxref("Request.destination")}}).</p>
-</div>
-
-<dl>
-	<dt><code>audio</code></dt>
-	<dd>The destination is audio data. This might originate from an HTML {{HTMLElement("audio")}} tag.</dd>
-	<dt><code>audioworklet</code></dt>
-	<dd>The destination is data being fetched for use by an audio worklet. This might originate from a call to {{domxref("Worklet.addModule()", "audioWorklet.addModule()")}}.</dd>
-	<dt><code>document</code></dt>
-	<dd>The destination is a document (HTML or XML), and the request is the result of a user-initiated top-level navigation (e.g. resulting from a user clicking a link).</dd>
-	<dt><code>embed</code></dt>
-	<dd>The destination is embedded content. This might originate from an HTML {{HTMLElement("embed")}} tag.</dd>
-	<dt><code>empty</code></dt>
-	<dd>The destination is the empty string. This is used for destinations that do not have their own value. For example <code>fetch()</code>, {{domxref("navigator.sendBeacon()")}}, {{domxref("EventSource")}}, {{domxref("XMLHttpRequest")}}, {{domxref("WebSocket")}}, etc.</dd>
-	<dt><code>font</code></dt>
-	<dd>The destination is a font. This might originate from CSS {{cssxref("@font-face")}}.</dd>
-	<dt><code>frame</code></dt>
-	<dd>The destination is a frame. This might originate from an HTML {{HTMLElement("frame")}} tag.</dd>
-	<dt><code>iframe</code></dt>
-	<dd>The destination is an iframe. This might originate from an HTML {{HTMLElement("iframe")}} tag.</dd>
-	<dt><code>image</code></dt>
-	<dd>The destination is an image. This might originate from an HTML {{HTMLElement("image")}}, SVG {{SVGElement("image")}}, CSS {{cssxref("background-image")}}, CSS {{cssxref("cursor")}}, CSS {{cssxref("list-style-image")}}, etc.</dd>
-	<dt><code>manifest</code></dt>
-	<dd>The destination is a manifest. This might originate from an HTML <a href="/en-US/docs/Web/HTML/Link_types/manifest">&lt;link rel=manifest&gt;</a>).</dd>
-	<dt><code>object</code></dt>
-	<dd>The destination is an object. This might originate from an HTML {{HTMLElement("object")}} tag.</dd>
-	<dt><code>paintworklet</code></dt>
-	<dd>The destination is a paint worklet. This might originate from a call to {{domxref('Worklet.addModule', 'CSS.PaintWorklet.addModule()')}}.</dd>
-	<dt><code>report</code></dt>
-	<dd>The destination is a report (for example, a content security policy report).</dd>
-	<dt><code>script</code></dt>
-	<dd>The destination is a script. This might originate from an HTML {{HTMLElement("script")}} tag or a call to {{domxref("WorkerGlobalScope.importScripts()")}}.</dd>
-	<dt><code>serviceworker</code></dt>
-	<dd>The destination is a service worker. This might originate from a call to {{domxref("ServiceWorkerContainer.register","navigator.serviceWorker.register()")}}.</dd>
-	<dt><code>sharedworker</code></dt>
-	<dd>The destination is a shared worker. This might originate from a {{domxref("SharedWorker")}}.</dd>
-	<dt><code>style</code></dt>
-	<dd>The destination is a style. This might originate from an HTML {{HTMLElement("link","&lt;link rel=stylesheet&gt;")}} or a CSS {{cssxref("@import")}}.</dd>
-	<dt><code>track</code></dt>
-	<dd>The destination is an HTML text track. This might originate from an HTML {{HTMLElement("track")}} tag.</dd>
-	<dt><code>video</code></dt>
-	<dd>The destination is video data. This might originate from an HTML {{HTMLElement("video")}} tag.</dd>
-	<dt><code>worker</code></dt>
-	<dd>The destination is a {{domxref("Worker")}}.</dd>
-	<dt><code>xslt</code></dt>
-	<dd>The destination is an XLST transform.</dd>
-</dl>
-
-
-<h2 id="Examples">Examples</h2>
-
-<p>A cross-site request generated by an {{HTMLElement("img")}} element would result in a request with the following HTTP request headers (note that the destination is <code>image</code>):</p>
-
-<pre>Sec-Fetch-Dest: image
-Sec-Fetch-Mode: no-cors
-Sec-Fetch-Site: cross-site
-</pre>
-
-<h2 id="Specifications">Specifications</h2>
-
-<p>{{Specifications}}</p>
-
-<h2 id="Browser_compatibility">Browser compatibility</h2>
-
-<p>{{Compat}}</p>
-
-<h2 id="See_also">See also</h2>
-
-<ul>
-	<li>Related headers
-	 <ul>
-		 <li>{{HTTPHeader("Sec-Fetch-Mode")}}</li>
-		 <li>{{HTTPHeader("Sec-Fetch-Site")}}</li>
-		 <li>{{HTTPHeader("Sec-Fetch-User")}}</li>
-	  </ul>
-	</li>
-	<li><a href="https://web.dev/fetch-metadata/">Protect your resources from web attacks with Fetch Metadata</a> (web.dev)</li>
-	<li><a href="https://secmetadata.appspot.com/">Fetch Metadata Request Headers playground</a> (secmetadata.appspot.com)</li>
-   </ul>
+## Syntax
+
+    Sec-Fetch-Dest: audio
+    Sec-Fetch-Dest: audioworklet
+    Sec-Fetch-Dest: document
+    Sec-Fetch-Dest: embed
+    Sec-Fetch-Dest: empty
+    Sec-Fetch-Dest: font
+    Sec-Fetch-Dest: frame
+    Sec-Fetch-Dest: iframe
+    Sec-Fetch-Dest: image
+    Sec-Fetch-Dest: manifest
+    Sec-Fetch-Dest: object
+    Sec-Fetch-Dest: paintworklet
+    Sec-Fetch-Dest: report
+    Sec-Fetch-Dest: script
+    Sec-Fetch-Dest: serviceworker
+    Sec-Fetch-Dest: sharedworker
+    Sec-Fetch-Dest: style
+    Sec-Fetch-Dest: track
+    Sec-Fetch-Dest: video
+    Sec-Fetch-Dest: worker
+    Sec-Fetch-Dest: xslt
+
+Servers should ignore this header if it contains any other value.
+
+## Directives
+
+> **Note:** These directives correspond to the values returned by {{domxref("Request.destination")}}).
+
+- `audio`
+  - : The destination is audio data. This might originate from an HTML {{HTMLElement("audio")}} tag.
+- `audioworklet`
+  - : The destination is data being fetched for use by an audio worklet. This might originate from a call to {{domxref("Worklet.addModule()", "audioWorklet.addModule()")}}.
+- `document`
+  - : The destination is a document (HTML or XML), and the request is the result of a user-initiated top-level navigation (e.g. resulting from a user clicking a link).
+- `embed`
+  - : The destination is embedded content. This might originate from an HTML {{HTMLElement("embed")}} tag.
+- `empty`
+  - : The destination is the empty string. This is used for destinations that do not have their own value. For example `fetch()`, {{domxref("navigator.sendBeacon()")}}, {{domxref("EventSource")}}, {{domxref("XMLHttpRequest")}}, {{domxref("WebSocket")}}, etc.
+- `font`
+  - : The destination is a font. This might originate from CSS {{cssxref("@font-face")}}.
+- `frame`
+  - : The destination is a frame. This might originate from an HTML {{HTMLElement("frame")}} tag.
+- `iframe`
+  - : The destination is an iframe. This might originate from an HTML {{HTMLElement("iframe")}} tag.
+- `image`
+  - : The destination is an image. This might originate from an HTML {{HTMLElement("image")}}, SVG {{SVGElement("image")}}, CSS {{cssxref("background-image")}}, CSS {{cssxref("cursor")}}, CSS {{cssxref("list-style-image")}}, etc.
+- `manifest`
+  - : The destination is a manifest. This might originate from an HTML [\<link rel=manifest>](/en-US/docs/Web/HTML/Link_types/manifest)).
+- `object`
+  - : The destination is an object. This might originate from an HTML {{HTMLElement("object")}} tag.
+- `paintworklet`
+  - : The destination is a paint worklet. This might originate from a call to {{domxref('Worklet.addModule', 'CSS.PaintWorklet.addModule()')}}.
+- `report`
+  - : The destination is a report (for example, a content security policy report).
+- `script`
+  - : The destination is a script. This might originate from an HTML {{HTMLElement("script")}} tag or a call to {{domxref("WorkerGlobalScope.importScripts()")}}.
+- `serviceworker`
+  - : The destination is a service worker. This might originate from a call to {{domxref("ServiceWorkerContainer.register","navigator.serviceWorker.register()")}}.
+- `sharedworker`
+  - : The destination is a shared worker. This might originate from a {{domxref("SharedWorker")}}.
+- `style`
+  - : The destination is a style. This might originate from an HTML {{HTMLElement("link","&lt;link rel=stylesheet&gt;")}} or a CSS {{cssxref("@import")}}.
+- `track`
+  - : The destination is an HTML text track. This might originate from an HTML {{HTMLElement("track")}} tag.
+- `video`
+  - : The destination is video data. This might originate from an HTML {{HTMLElement("video")}} tag.
+- `worker`
+  - : The destination is a {{domxref("Worker")}}.
+- `xslt`
+  - : The destination is an XLST transform.
+
+## Examples
+
+A cross-site request generated by an {{HTMLElement("img")}} element would result in a request with the following HTTP request headers (note that the destination is `image`):
+
+    Sec-Fetch-Dest: image
+    Sec-Fetch-Mode: no-cors
+    Sec-Fetch-Site: cross-site
+
+## Specifications
+
+{{Specifications}}
+
+## Browser compatibility
+
+{{Compat}}
+
+## See also
+
+- Related headers
+
+  - {{HTTPHeader("Sec-Fetch-Mode")}}
+  - {{HTTPHeader("Sec-Fetch-Site")}}
+  - {{HTTPHeader("Sec-Fetch-User")}}
+
+- [Protect your resources from web attacks with Fetch Metadata](https://web.dev/fetch-metadata/) (web.dev)
+- [Fetch Metadata Request Headers playground](https://secmetadata.appspot.com/) (secmetadata.appspot.com)
diff --git a/files/en-us/web/http/headers/sec-fetch-mode/index.md b/files/en-us/web/http/headers/sec-fetch-mode/index.md
index 92a5eb97388ae43..30a852494c687d2 100644
--- a/files/en-us/web/http/headers/sec-fetch-mode/index.md
+++ b/files/en-us/web/http/headers/sec-fetch-mode/index.md
@@ -10,96 +10,86 @@ tags:
   - Request header
 browser-compat: http.headers.Sec-Fetch-Mode
 ---
-<div>{{HTTPSidebar}}</div>
+{{HTTPSidebar}}
 
-<p>The <strong><code>Sec-Fetch-Mode</code></strong> {{Glossary("Fetch metadata request header", "fetch metadata request header")}} indicates the <a href="/en-US/docs/Web/API/Request/mode">mode</a> of the request.</p>
+The **`Sec-Fetch-Mode`** {{Glossary("Fetch metadata request header", "fetch metadata request header")}} indicates the [mode](/en-US/docs/Web/API/Request/mode) of the request.
 
-<p>Broadly speaking, this allows a server to distinguish between: requests originating from a user navigating between HTML pages, and requests to load images and other resources. For example, this header would contain <code>navigate</code> for top level navigation requests, while <code>no-cors</code> is used for loading an image.</p>
+Broadly speaking, this allows a server to distinguish between: requests originating from a user navigating between HTML pages, and requests to load images and other resources. For example, this header would contain `navigate` for top level navigation requests, while `no-cors` is used for loading an image.
 
 <table class="properties">
- <tbody>
-  <tr>
-   <th scope="row">Header type</th>
-   <td>{{Glossary("Fetch Metadata Request Header")}}</td>
-  </tr>
-  <tr>
-   <th scope="row">{{Glossary("Forbidden header name")}}</th>
-   <td>yes (prefix <code>Sec-</code>)</td>
-  </tr>
-  <tr>
-   <th scope="row">{{Glossary("CORS-safelisted request header")}}</th>
-   <td>no</td>
-  </tr>
- </tbody>
+  <tbody>
+    <tr>
+      <th scope="row">Header type</th>
+      <td>{{Glossary("Fetch Metadata Request Header")}}</td>
+    </tr>
+    <tr>
+      <th scope="row">{{Glossary("Forbidden header name")}}</th>
+      <td>yes (prefix <code>Sec-</code>)</td>
+    </tr>
+    <tr>
+      <th scope="row">
+        {{Glossary("CORS-safelisted request header")}}
+      </th>
+      <td>no</td>
+    </tr>
+  </tbody>
 </table>
 
-<h2 id="Syntax">Syntax</h2>
+## Syntax
 
-<pre>Sec-Fetch-Mode: cors
-Sec-Fetch-Mode: navigate
-Sec-Fetch-Mode: no-cors
-Sec-Fetch-Mode: same-origin
-Sec-Fetch-Mode: websocket
-</pre>
+    Sec-Fetch-Mode: cors
+    Sec-Fetch-Mode: navigate
+    Sec-Fetch-Mode: no-cors
+    Sec-Fetch-Mode: same-origin
+    Sec-Fetch-Mode: websocket
 
-<p>Servers should ignore this header if it contains any other value.</p>
+Servers should ignore this header if it contains any other value.
 
+## Directives
 
-<h2 id="Directives">Directives</h2>
+> **Note:** These directives correspond to the values in [`Request.mode`](/en-US/docs/Web/API/Request/mode#value).
 
-<div class="notecard note">
-  <p><strong>Note:</strong> These directives correspond to the values in <a href="/en-US/docs/Web/API/Request/mode#value"><code>Request.mode</code></a>.</p>
-</div>
+- `cors`
+  - : The request is a [CORS protocol](/en-US/docs/Web/HTTP/CORS) request.
+- `navigate`
+  - : The request is initiated by navigation between HTML documents.
+- `no-cors`
+  - : The request is a no-cors request (see [`Request.mode`](/en-US/docs/Web/API/Request/mode#value)).
+- `same-origin`
+  - : The request is made from the same origin as the resource that is being requested.
+- `websocket`
+  - : The request is being made to establish a [WebSocket](/en-US/docs/Web/API/WebSockets_API) connection.
 
-<dl>
- <dt><code>cors</code></dt>
- <dd>The request is a <a href="/en-US/docs/Web/HTTP/CORS">CORS protocol</a> request.</dd>
- <dt><code>navigate</code></dt>
- <dd>The request is initiated by navigation between HTML documents.</dd>
- <dt><code>no-cors</code></dt>
- <dd>The request is a no-cors request (see <a href="/en-US/docs/Web/API/Request/mode#value"><code>Request.mode</code></a>).</dd>
- <dt><code>same-origin</code></dt>
- <dd>The request is made from the same origin as the resource that is being requested.</dd>
- <dt><code>websocket</code></dt>
- <dd>The request is being made to establish a <a href="/en-US/docs/Web/API/WebSockets_API">WebSocket</a> connection.</dd>
-</dl>
+## Examples
 
+If a user clicks on a page link to another page on the same origin, the resulting request would have the following headers (note that the mode is `navigate`):
 
-<h2 id="Examples">Examples</h2>
+    Sec-Fetch-Dest: document
+    Sec-Fetch-Mode: navigate
+    Sec-Fetch-Site: same-origin
+    Sec-Fetch-User: ?1
 
-<p>If a user clicks on a page link to another page on the same origin, the resulting request would have the following headers (note that the mode is <code>navigate</code>):</p>
+A cross-site request generated by an {{HTMLElement("img")}} element would result in a request with the following HTTP request headers (note that the mode is `no-cors`):
 
-<pre>Sec-Fetch-Dest: document
-Sec-Fetch-Mode: navigate
-Sec-Fetch-Site: same-origin
-Sec-Fetch-User: ?1
-</pre>
+    Sec-Fetch-Dest: image
+    Sec-Fetch-Mode: no-cors
+    Sec-Fetch-Site: cross-site
 
-<p>A cross-site request generated by an {{HTMLElement("img")}} element would result in a request with the following HTTP request headers (note that the mode is <code>no-cors</code>):</p>
+## Specifications
 
-<pre>Sec-Fetch-Dest: image
-Sec-Fetch-Mode: no-cors
-Sec-Fetch-Site: cross-site
-</pre>
+{{Specifications}}
 
-<h2 id="Specifications">Specifications</h2>
+## Browser compatibility
 
-<p>{{Specifications}}</p>
+{{Compat}}
 
-<h2 id="Browser_compatibility">Browser compatibility</h2>
+## See also
 
-<p>{{Compat}}</p>
+- Related headers
 
-<h2 id="See_also">See also</h2>
+  - {{HTTPHeader("Sec-Fetch-Dest")}}
+  - {{HTTPHeader("Sec-Fetch-Site")}}
+  - {{HTTPHeader("Sec-Fetch-User")}}
 
-<ul>
-  <li>Related headers
-   <ul>
-    <li>{{HTTPHeader("Sec-Fetch-Dest")}}</li>
-    <li>{{HTTPHeader("Sec-Fetch-Site")}}</li>
-    <li>{{HTTPHeader("Sec-Fetch-User")}}</li>
-    </ul>
-  </li>
-  <li><a href="https://web.dev/fetch-metadata/">Protect your resources from web attacks with Fetch Metadata</a> (web.dev)</li>
-  <li><a href="https://secmetadata.appspot.com/">Fetch Metadata Request Headers playground</a> (secmetadata.appspot.com)</li>
- </ul>
+- [Protect your resources from web attacks with Fetch Metadata](https://web.dev/fetch-metadata/) (web.dev)
+- [Fetch Metadata Request Headers playground](https://secmetadata.appspot.com/) (secmetadata.appspot.com)
diff --git a/files/en-us/web/http/headers/sec-fetch-site/index.md b/files/en-us/web/http/headers/sec-fetch-site/index.md
index 92443d9c0dbdae8..0851a9d822b577a 100644
--- a/files/en-us/web/http/headers/sec-fetch-site/index.md
+++ b/files/en-us/web/http/headers/sec-fetch-site/index.md
@@ -10,89 +10,83 @@ tags:
   - Request header
 browser-compat: http.headers.Sec-Fetch-Site
 ---
-<p>{{HTTPSidebar}}</p>
+{{HTTPSidebar}}
 
-<p>The <strong><code>Sec-Fetch-Site</code></strong> {{Glossary("Fetch metadata request header", "fetch metadata request header")}} indicates the relationship between a request initiator's origin and the origin of the requested resource.</p>
+The **`Sec-Fetch-Site`** {{Glossary("Fetch metadata request header", "fetch metadata request header")}} indicates the relationship between a request initiator's origin and the origin of the requested resource.
 
-<p>In other words, this header tells a server whether a request for a resource is coming from the same origin, the same site, a different site, or is a "user initiated" request. The server can then use this information to decide if the request should be allowed.</p>
+In other words, this header tells a server whether a request for a resource is coming from the same origin, the same site, a different site, or is a "user initiated" request. The server can then use this information to decide if the request should be allowed.
 
-<p>Same-origin requests would usually be allowed by default, but what happens for requests from other origins may further depend on what resource is being requested, or information in other {{Glossary("Fetch metadata request header","Fetch metadata request headers")}}. By default, requests that are not accepted should be rejected with a {{HTTPStatus("403")}} response code.</p>
+Same-origin requests would usually be allowed by default, but what happens for requests from other origins may further depend on what resource is being requested, or information in other {{Glossary("Fetch metadata request header","Fetch metadata request headers")}}. By default, requests that are not accepted should be rejected with a {{HTTPStatus("403")}} response code.
 
 <table class="properties">
- <tbody>
-  <tr>
-   <th scope="row">Header type</th>
-   <td>{{Glossary("Fetch Metadata Request Header")}}</td>
-  </tr>
-  <tr>
-   <th scope="row">{{Glossary("Forbidden header name")}}</th>
-   <td>yes (prefix <code>Sec-</code>)</td>
-  </tr>
-   <th scope="row">{{Glossary("CORS-safelisted request header")}}</th>
-   <td>no</td>
-  </tr>
- </tbody>
+  <tbody>
+    <tr>
+      <th scope="row">Header type</th>
+      <td>{{Glossary("Fetch Metadata Request Header")}}</td>
+    </tr>
+    <tr>
+      <th scope="row">{{Glossary("Forbidden header name")}}</th>
+      <td>yes (prefix <code>Sec-</code>)</td>
+    </tr>
+    <tr>
+      <th scope="row">
+        {{Glossary("CORS-safelisted request header")}}
+      </th>
+      <td>no</td>
+    </tr>
+  </tbody>
 </table>
 
-<h2 id="Syntax">Syntax</h2>
+## Syntax
 
-<pre>Sec-Fetch-Site: cross-site
-Sec-Fetch-Site: same-origin
-Sec-Fetch-Site: same-site
-Sec-Fetch-Site: none
-</pre>
+    Sec-Fetch-Site: cross-site
+    Sec-Fetch-Site: same-origin
+    Sec-Fetch-Site: same-site
+    Sec-Fetch-Site: none
 
-<h2 id="Directives">Directives</h2>
+## Directives
 
-<dl>
-  <dt><code>cross-site</code></dt>
-  <dd>The request initiator and the server hosting the resource have a different site (i.e. a request by "potentially-evil.com" for a resource at "example.com").</dd>
-  <dt><code>same-origin</code></dt>
-  <dd>The request initiator and the server hosting the resource have the same {{Glossary("origin")}} (same scheme, host and port).</dd>
-  <dt><code>same-site</code></dt>
-  <dd>The request initiator and the server hosting the resource have the same scheme, domain and/or subdomain, but not necessarily the same port.</dd>
-  <dt><code>none</code></dt>
-  <dd>This request is a user-originated operation. For example: entering a URL into the address bar, opening a bookmark, or dragging-and-dropping a file into the browser window.</dd>
- </dl>
+- `cross-site`
+  - : The request initiator and the server hosting the resource have a different site (i.e. a request by "potentially-evil.com" for a resource at "example.com").
+- `same-origin`
+  - : The request initiator and the server hosting the resource have the same {{Glossary("origin")}} (same scheme, host and port).
+- `same-site`
+  - : The request initiator and the server hosting the resource have the same scheme, domain and/or subdomain, but not necessarily the same port.
+- `none`
+  - : This request is a user-originated operation. For example: entering a URL into the address bar, opening a bookmark, or dragging-and-dropping a file into the browser window.
 
+## Examples
 
- <h2 id="Examples">Examples</h2>
+A fetch request to `https://mysite.example/foo.json` originating from a web page on `https://mysite.example` (with the same port) is a same-origin request.
+The browser will generate the `Sec-Fetch-Site: same-origin` header as shown below, and the server will typically allow the request:
 
- <p>A fetch request to <code>https://mysite.example/foo.json</code> originating from a web page on <code>https://mysite.example</code> (with the same port) is a same-origin request.
-The browser will generate the <code>Sec-Fetch-Site: same-origin</code> header as shown below, and the server will typically allow the request:</p>
+    GET /foo.json
+    Sec-Fetch-Dest: empty
+    Sec-Fetch-Mode: cors
+    Sec-Fetch-Site: same-origin
 
- <pre>GET /foo.json
-Sec-Fetch-Dest: empty
-Sec-Fetch-Mode: cors
-Sec-Fetch-Site: same-origin
-</pre>
+A fetch request to the same URL from another site, for example `potentially-evil.com`, causes the browser to generate a different header (e.g. `Sec-Fetch-Site: cross-site`), which the server can choose to accept or reject:
 
-<p>A fetch request to the same URL from another site, for example <code>potentially-evil.com</code>, causes the browser to generate a different header (e.g. <code>Sec-Fetch-Site: cross-site</code>), which the server can choose to accept or reject:</p>
+    GET /foo.json
+    Sec-Fetch-Dest: empty
+    Sec-Fetch-Mode: cors
+    Sec-Fetch-Site: cross-site
 
-<pre>GET /foo.json
-Sec-Fetch-Dest: empty
-Sec-Fetch-Mode: cors
-Sec-Fetch-Site: cross-site
-</pre>
+## Specifications
 
-<h2 id="Specifications">Specifications</h2>
+{{Specifications}}
 
-<p>{{Specifications}}</p>
+## Browser compatibility
 
-<h2 id="Browser_compatibility">Browser compatibility</h2>
+{{Compat}}
 
-<p>{{Compat}}</p>
+## See also
 
-<h2 id="See_also">See also</h2>
+- Related headers
 
-<ul>
- <li>Related headers
-  <ul>
-    <li>{{HTTPHeader("Sec-Fetch-Mode")}}</li>
-    <li>{{HTTPHeader("Sec-Fetch-User")}}</li>
-    <li>{{HTTPHeader("Sec-Fetch-Dest")}}</li>
-   </ul>
- </li>
- <li><a href="https://web.dev/fetch-metadata/">Protect your resources from web attacks with Fetch Metadata</a> (web.dev)</li>
- <li><a href="https://secmetadata.appspot.com/">Fetch Metadata Request Headers playground</a> (secmetadata.appspot.com)</li>
-</ul>
+  - {{HTTPHeader("Sec-Fetch-Mode")}}
+  - {{HTTPHeader("Sec-Fetch-User")}}
+  - {{HTTPHeader("Sec-Fetch-Dest")}}
+
+- [Protect your resources from web attacks with Fetch Metadata](https://web.dev/fetch-metadata/) (web.dev)
+- [Fetch Metadata Request Headers playground](https://secmetadata.appspot.com/) (secmetadata.appspot.com)
diff --git a/files/en-us/web/http/headers/sec-fetch-user/index.md b/files/en-us/web/http/headers/sec-fetch-user/index.md
index a17a60777e26ffe..321085f17952da7 100644
--- a/files/en-us/web/http/headers/sec-fetch-user/index.md
+++ b/files/en-us/web/http/headers/sec-fetch-user/index.md
@@ -10,66 +10,63 @@ tags:
   - Request header
 browser-compat: http.headers.Sec-Fetch-User
 ---
-<p>{{HTTPSidebar}}</p>
+{{HTTPSidebar}}
 
-<p>The <strong><code>Sec-Fetch-User</code></strong> {{Glossary("Fetch metadata request header", "fetch metadata request header")}} is only sent for requests initiated by user activation, and its value will always be <code>?1</code>.</p>
+The **`Sec-Fetch-User`** {{Glossary("Fetch metadata request header", "fetch metadata request header")}} is only sent for requests initiated by user activation, and its value will always be `?1`.
 
-<p>A server can use this header to identify whether a navigation request from a document, iframe, etc., was originated by the user.</p>
+A server can use this header to identify whether a navigation request from a document, iframe, etc., was originated by the user.
 
 <table class="properties">
- <tbody>
-  <tr>
-   <th scope="row">Header type</th>
-   <td>{{Glossary("Fetch Metadata Request Header")}}</td>
-  </tr>
-  <tr>
-   <th scope="row">{{Glossary("Forbidden header name")}}</th>
-   <td>yes (prefix <code>Sec-</code>)</td>
-  </tr>
-  <tr>
-   <th scope="row">{{Glossary("CORS-safelisted request header")}}</th>
-   <td>no</td>
-  </tr>
- </tbody>
+  <tbody>
+    <tr>
+      <th scope="row">Header type</th>
+      <td>{{Glossary("Fetch Metadata Request Header")}}</td>
+    </tr>
+    <tr>
+      <th scope="row">{{Glossary("Forbidden header name")}}</th>
+      <td>yes (prefix <code>Sec-</code>)</td>
+    </tr>
+    <tr>
+      <th scope="row">
+        {{Glossary("CORS-safelisted request header")}}
+      </th>
+      <td>no</td>
+    </tr>
+  </tbody>
 </table>
 
-<h2 id="Syntax">Syntax</h2>
+## Syntax
 
-<pre>Sec-Fetch-User: ?1
-</pre>
+    Sec-Fetch-User: ?1
 
-<h2 id="Directives">Directives</h2>
+## Directives
 
-<p>The value will always be <code>?1</code>. When a request is triggered by something other than a user activation, the spec requires browsers to omit the header completely.</p>
+The value will always be `?1`. When a request is triggered by something other than a user activation, the spec requires browsers to omit the header completely.
 
-<h2 id="Examples">Examples</h2>
+## Examples
 
-<p>If a user clicks on a page link to another page on the same origin, the resulting request would have the following headers:</p>
+If a user clicks on a page link to another page on the same origin, the resulting request would have the following headers:
 
-<pre>Sec-Fetch-Dest: document
-Sec-Fetch-Mode: navigate
-Sec-Fetch-Site: same-origin
-Sec-Fetch-User: ?1
-</pre>
+    Sec-Fetch-Dest: document
+    Sec-Fetch-Mode: navigate
+    Sec-Fetch-Site: same-origin
+    Sec-Fetch-User: ?1
 
-<h2 id="Specifications">Specifications</h2>
+## Specifications
 
-<p>{{Specifications}}</p>
+{{Specifications}}
 
-<h2 id="Browser_compatibility">Browser compatibility</h2>
+## Browser compatibility
 
-<p>{{Compat}}</p>
+{{Compat}}
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
-  <li>Related headers
-   <ul>
-    <li>{{HTTPHeader("Sec-Fetch-Dest")}}</li>
-    <li>{{HTTPHeader("Sec-Fetch-Mode")}}</li>
-    <li>{{HTTPHeader("Sec-Fetch-Site")}}</li>
-    </ul>
-  </li>
-  <li><a href="https://web.dev/fetch-metadata/">Protect your resources from web attacks with Fetch Metadata</a> (web.dev)</li>
-  <li><a href="https://secmetadata.appspot.com/">Fetch Metadata Request Headers playground</a> (secmetadata.appspot.com)</li>
- </ul>
+- Related headers
+
+  - {{HTTPHeader("Sec-Fetch-Dest")}}
+  - {{HTTPHeader("Sec-Fetch-Mode")}}
+  - {{HTTPHeader("Sec-Fetch-Site")}}
+
+- [Protect your resources from web attacks with Fetch Metadata](https://web.dev/fetch-metadata/) (web.dev)
+- [Fetch Metadata Request Headers playground](https://secmetadata.appspot.com/) (secmetadata.appspot.com)
diff --git a/files/en-us/web/http/headers/sec-websocket-accept/index.md b/files/en-us/web/http/headers/sec-websocket-accept/index.md
index e0857f07f2490f1..0021cad81444209 100644
--- a/files/en-us/web/http/headers/sec-websocket-accept/index.md
+++ b/files/en-us/web/http/headers/sec-websocket-accept/index.md
@@ -12,12 +12,11 @@ tags:
   - header
 browser-compat: http.headers.Sec-WebSocket-Accept
 ---
-<div>{{HTTPSidebar}}{{Draft}}</div>
+{{HTTPSidebar}}{{Draft}}
 
-<p>The <strong>Sec-WebSocket-Accept</strong> header is used in the websocket opening
-  handshake. It would appear in the response headers. That is, this is header is sent from
-  server to client to inform that server is willing to initiate a websocket connection.
-</p>
+The **Sec-WebSocket-Accept** header is used in the websocket opening
+handshake. It would appear in the response headers. That is, this is header is sent from
+server to client to inform that server is willing to initiate a websocket connection.
 
 <table class="properties">
   <tbody>
@@ -32,37 +31,32 @@ browser-compat: http.headers.Sec-WebSocket-Accept
   </tbody>
 </table>
 
-<h2 id="Syntax">Syntax</h2>
+## Syntax
 
-<pre class="brush: html">Sec-WebSocket-Accept: &lt;hashed key&gt;</pre>
+```html
+Sec-WebSocket-Accept: <hashed key>
+```
 
-<h2 id="Directives">Directives</h2>
+## Directives
 
-<dl>
-  <dt>&lt;hashed key&gt;</dt>
-  <dd>
-    <p>The server takes the value of the Sec-WebSocket-Key sent in the handshake request,
-      appends <code>258EAFA5-E914-47DA-95CA-C5AB0DC85B11</code>, takes SHA-1 of the new
-      value, and is then <a
-        href="/en-US/docs/Glossary/Base64">base64</a>
-      encoded.</p>
-  </dd>
-</dl>
+- \<hashed key>
+  - : The server takes the value of the Sec-WebSocket-Key sent in the handshake request,
+    appends `258EAFA5-E914-47DA-95CA-C5AB0DC85B11`, takes SHA-1 of the new
+    value, and is then [base64](/en-US/docs/Glossary/Base64)
+    encoded.
 
-<h2 id="Examples">Examples</h2>
+## Examples
 
-<pre>Sec-WebSocket-Accept: s3pPLMBiTxaQ9kYGzzhZRbK+xOo=</pre>
+    Sec-WebSocket-Accept: s3pPLMBiTxaQ9kYGzzhZRbK+xOo=
 
-<h2 id="Specifications">Specifications</h2>
+## Specifications
 
 {{Specifications}}
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
-  <li>{{HTTPHeader("Sec-WebSocket-Key")}}</li>
-</ul>
+- {{HTTPHeader("Sec-WebSocket-Key")}}
 
-<h2 id="Browser_compatibility">Browser compatibility</h2>
+## Browser compatibility
 
-<p>{{Compat}}</p>
+{{Compat}}
diff --git a/files/en-us/web/http/headers/server-timing/index.md b/files/en-us/web/http/headers/server-timing/index.md
index d281e2161432545..0cac37dc6284165 100644
--- a/files/en-us/web/http/headers/server-timing/index.md
+++ b/files/en-us/web/http/headers/server-timing/index.md
@@ -8,65 +8,62 @@ tags:
   - header
 browser-compat: http.headers.Server-Timing
 ---
-<p>{{HTTPSidebar}}</p>
+{{HTTPSidebar}}
 
-<p>The <strong><code>Server-Timing</code></strong> header communicates one or more metrics and descriptions for a given request-response cycle. It is used to surface any backend server timing metrics (e.g. database read/write, CPU time, file system access, etc.) in the developer tools in the user's browser or in the {{domxref("PerformanceServerTiming")}} interface.</p>
+The **`Server-Timing`** header communicates one or more metrics and descriptions for a given request-response cycle. It is used to surface any backend server timing metrics (e.g. database read/write, CPU time, file system access, etc.) in the developer tools in the user's browser or in the {{domxref("PerformanceServerTiming")}} interface.
 
 <table class="properties">
- <tbody>
-  <tr>
-   <th scope="row">Header type</th>
-   <td>{{Glossary("Response header")}}</td>
-  </tr>
-  <tr>
-   <th scope="row">{{Glossary("Forbidden header name")}}</th>
-   <td>no</td>
-  </tr>
- </tbody>
+  <tbody>
+    <tr>
+      <th scope="row">Header type</th>
+      <td>{{Glossary("Response header")}}</td>
+    </tr>
+    <tr>
+      <th scope="row">{{Glossary("Forbidden header name")}}</th>
+      <td>no</td>
+    </tr>
+  </tbody>
 </table>
 
-<h2 id="Syntax">Syntax</h2>
+## Syntax
 
-<p>The syntax of the <code>Server-Timing</code> header allows you to communicate metrics in different ways: server metric name only, metric with value, metric with value and description, and metric with description.</p>
+The syntax of the `Server-Timing` header allows you to communicate metrics in different ways: server metric name only, metric with value, metric with value and description, and metric with description.
 
-<p>The specification advices that names and descriptions should be kept as short as possible (use abbreviations and omit optional values where possible) to minimize the HTTP overhead.</p>
+The specification advices that names and descriptions should be kept as short as possible (use abbreviations and omit optional values where possible) to minimize the HTTP overhead.
 
-<pre>// Single metric without value
-Server-Timing: missedCache
+    // Single metric without value
+    Server-Timing: missedCache
 
-// Single metric with value
-Server-Timing: cpu;dur=2.4
+    // Single metric with value
+    Server-Timing: cpu;dur=2.4
 
-// Single metric with description and value
-Server-Timing: cache;desc="Cache Read";dur=23.2
+    // Single metric with description and value
+    Server-Timing: cache;desc="Cache Read";dur=23.2
 
-// Two metrics with value
-Server-Timing: db;dur=53, app;dur=47.2
+    // Two metrics with value
+    Server-Timing: db;dur=53, app;dur=47.2
 
-// Server-Timing as trailer
-Trailer: Server-Timing
---- response body ---
-Server-Timing: total;dur=123.4
-</pre>
+    // Server-Timing as trailer
+    Trailer: Server-Timing
+    --- response body ---
+    Server-Timing: total;dur=123.4
 
-<h2 id="Privacy_and_security">Privacy and security</h2>
+## Privacy and security
 
-<p>The <code>Server-Timing</code> header may expose potentially sensitive application and infrastructure information. Consider to control which metrics are returned when and to whom on the server side. For example, you could only show metrics to authenticated users and nothing to the public.</p>
+The `Server-Timing` header may expose potentially sensitive application and infrastructure information. Consider to control which metrics are returned when and to whom on the server side. For example, you could only show metrics to authenticated users and nothing to the public.
 
-<h2 id="PerformanceServerTiming_interface">PerformanceServerTiming interface</h2>
+## PerformanceServerTiming interface
 
-<p>In addition to having <code>Server-Timing</code> header metrics appear in the developer tools of the browser, the {{domxref("PerformanceServerTiming")}} interface enables tools to automatically collect and process metrics from JavaScript. This interface is restricted to the same origin, but you can use the {{HTTPHeader("Timing-Allow-Origin")}} header to specify the domains that are allowed to access the server metrics. The interface is only available in secure contexts (HTTPS) in some browsers.</p>
+In addition to having `Server-Timing` header metrics appear in the developer tools of the browser, the {{domxref("PerformanceServerTiming")}} interface enables tools to automatically collect and process metrics from JavaScript. This interface is restricted to the same origin, but you can use the {{HTTPHeader("Timing-Allow-Origin")}} header to specify the domains that are allowed to access the server metrics. The interface is only available in secure contexts (HTTPS) in some browsers.
 
-<h2 id="Specifications">Specifications</h2>
+## Specifications
 
 {{Specifications}}
 
-<h2 id="Browser_compatibility">Browser compatibility</h2>
+## Browser compatibility
 
-<p>{{Compat}}</p>
+{{Compat}}
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
- <li>{{domxref("PerformanceServerTiming")}}</li>
-</ul>
+- {{domxref("PerformanceServerTiming")}}
diff --git a/files/en-us/web/http/headers/server/index.md b/files/en-us/web/http/headers/server/index.md
index e5f9b37cafdaba7..487f98ca5d312c9 100644
--- a/files/en-us/web/http/headers/server/index.md
+++ b/files/en-us/web/http/headers/server/index.md
@@ -2,21 +2,19 @@
 title: Server
 slug: Web/HTTP/Headers/Server
 tags:
-- HTTP
-- Reference
-- header
+  - HTTP
+  - Reference
+  - header
 browser-compat: http.headers.Server
 ---
-<div>{{HTTPSidebar}}</div>
+{{HTTPSidebar}}
 
-<p>The <code><strong>Server</strong></code> header describes the
-    software used by the origin server that handled the request — that is, the server that
-    generated the response.</p>
+The **`Server`** header describes the
+software used by the origin server that handled the request — that is, the server that
+generated the response.
 
-<div class="notecard warning">
-  <p><strong>Warning:</strong> Avoid overly-detailed <code>Server</code> values, as they can reveal information that
-    might make it (slightly) easier for attackers to exploit known security holes.</p>
-</div>
+> **Warning:** Avoid overly-detailed `Server` values, as they can reveal information that
+> might make it (slightly) easier for attackers to exploit known security holes.
 
 <table class="properties">
   <tbody>
@@ -31,41 +29,36 @@ browser-compat: http.headers.Server
   </tbody>
 </table>
 
-<h2 id="Syntax">Syntax</h2>
+## Syntax
 
-<pre class="brush: html">Server: &lt;product&gt;
-</pre>
+```html
+Server: <product>
+```
 
-<h2 id="Directives">Directives</h2>
+## Directives
 
-<dl>
-  <dt><code>&lt;product&gt;</code></dt>
-  <dd>
-    <p>The name of the software or product that handled the request. Usually in a format
-      similar to {{HTTPHeader('User-Agent')}}.</p>
-  </dd>
-</dl>
+- `<product>`
+  - : The name of the software or product that handled the request. Usually in a format
+    similar to {{HTTPHeader('User-Agent')}}.
 
-<p>How much detail to include is an interesting balance to strike; exposing the OS version
-  is probably a bad idea, as mentioned in the earlier warning about overly-detailed
-  values. However, exposed Apache versions helped browsers work around a bug those
-  versions had with {{HTTPHeader('Content-Encoding')}} combined with
-  {{HTTPHeader('Range')}}.</p>
+How much detail to include is an interesting balance to strike; exposing the OS version
+is probably a bad idea, as mentioned in the earlier warning about overly-detailed
+values. However, exposed Apache versions helped browsers work around a bug those
+versions had with {{HTTPHeader('Content-Encoding')}} combined with
+{{HTTPHeader('Range')}}.
 
-<h2 id="Examples">Examples</h2>
+## Examples
 
-<pre>Server: Apache/2.4.1 (Unix)</pre>
+    Server: Apache/2.4.1 (Unix)
 
-<h2 id="Specifications">Specifications</h2>
+## Specifications
 
 {{Specifications}}
 
-<h2 id="Browser_compatibility">Browser compatibility</h2>
+## Browser compatibility
 
-<p>{{Compat}}</p>
+{{Compat}}
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
-  <li>{{HTTPHeader("Allow")}}</li>
-</ul>
+- {{HTTPHeader("Allow")}}
diff --git a/files/en-us/web/http/headers/set-cookie/index.md b/files/en-us/web/http/headers/set-cookie/index.md
index c8861f0f2bb2d30..93762426aae4c57 100644
--- a/files/en-us/web/http/headers/set-cookie/index.md
+++ b/files/en-us/web/http/headers/set-cookie/index.md
@@ -10,261 +10,227 @@ tags:
   - samesite
 browser-compat: http.headers.Set-Cookie
 ---
-<div>{{HTTPSidebar}}</div>
+{{HTTPSidebar}}
 
-<p>The <strong><code>Set-Cookie</code></strong> HTTP response header is used to send a cookie from the server to the user agent, so the user agent can send it back to the server later. To send multiple cookies, multiple <strong><code>Set-Cookie</code></strong> headers should be sent in the same response.</p>
+The **`Set-Cookie`** HTTP response header is used to send a cookie from the server to the user agent, so the user agent can send it back to the server later. To send multiple cookies, multiple **`Set-Cookie`** headers should be sent in the same response.
 
-<div class="notecard warning">
-  <p><strong>Warning:</strong> Browsers block frontend JavaScript code from accessing the <code>Set Cookie</code> header, as required by the Fetch spec, which defines <code>Set-Cookie</code> as a <a href="https://fetch.spec.whatwg.org/#forbidden-response-header-name">forbidden response-header name</a> that <a href="https://fetch.spec.whatwg.org/#ref-for-forbidden-response-header-name%E2%91%A0">must be filtered out</a> from any response exposed to frontend code.</p>
-</div>
+> **Warning:** Browsers block frontend JavaScript code from accessing the `Set Cookie` header, as required by the Fetch spec, which defines `Set-Cookie` as a [forbidden response-header name](https://fetch.spec.whatwg.org/#forbidden-response-header-name) that [must be filtered out](https://fetch.spec.whatwg.org/#ref-for-forbidden-response-header-name%E2%91%A0) from any response exposed to frontend code.
 
-<p>For more information, see the guide on <a href="/en-US/docs/Web/HTTP/Cookies">Using HTTP cookies</a>.</p>
+For more information, see the guide on [Using HTTP cookies](/en-US/docs/Web/HTTP/Cookies).
 
 <table class="properties">
- <tbody>
-  <tr>
-   <th scope="row">Header type</th>
-   <td>{{Glossary("Response header")}}</td>
-  </tr>
-  <tr>
-   <th scope="row">{{Glossary("Forbidden header name")}}</th>
-   <td>no</td>
-  </tr>
-  <tr>
-   <th scope="row"><a href="https://fetch.spec.whatwg.org/#forbidden-response-header-name">Forbidden response-header name</a></th>
-   <td>yes</td>
-  </tr>
- </tbody>
+  <tbody>
+    <tr>
+      <th scope="row">Header type</th>
+      <td>{{Glossary("Response header")}}</td>
+    </tr>
+    <tr>
+      <th scope="row">{{Glossary("Forbidden header name")}}</th>
+      <td>no</td>
+    </tr>
+    <tr>
+      <th scope="row">
+        <a href="https://fetch.spec.whatwg.org/#forbidden-response-header-name"
+          >Forbidden response-header name</a
+        >
+      </th>
+      <td>yes</td>
+    </tr>
+  </tbody>
 </table>
 
-<h2 id="Syntax">Syntax</h2>
+## Syntax
 
-<pre class="brush: html">Set-Cookie: &lt;cookie-name&gt;=&lt;cookie-value&gt;
-Set-Cookie: &lt;cookie-name&gt;=&lt;cookie-value&gt;; Expires=&lt;date&gt;
-Set-Cookie: &lt;cookie-name&gt;=&lt;cookie-value&gt;; Max-Age=&lt;number&gt;
-Set-Cookie: &lt;cookie-name&gt;=&lt;cookie-value&gt;; Domain=&lt;domain-value&gt;
-Set-Cookie: &lt;cookie-name&gt;=&lt;cookie-value&gt;; Path=&lt;path-value&gt;
-Set-Cookie: &lt;cookie-name&gt;=&lt;cookie-value&gt;; Secure
-Set-Cookie: &lt;cookie-name&gt;=&lt;cookie-value&gt;; HttpOnly
+```html
+Set-Cookie: <cookie-name>=<cookie-value>
+Set-Cookie: <cookie-name>=<cookie-value>; Expires=<date>
+Set-Cookie: <cookie-name>=<cookie-value>; Max-Age=<number>
+Set-Cookie: <cookie-name>=<cookie-value>; Domain=<domain-value>
+Set-Cookie: <cookie-name>=<cookie-value>; Path=<path-value>
+Set-Cookie: <cookie-name>=<cookie-value>; Secure
+Set-Cookie: <cookie-name>=<cookie-value>; HttpOnly
 
-Set-Cookie: &lt;cookie-name&gt;=&lt;cookie-value&gt;; SameSite=Strict
-Set-Cookie: &lt;cookie-name&gt;=&lt;cookie-value&gt;; SameSite=Lax
-Set-Cookie: &lt;cookie-name&gt;=&lt;cookie-value&gt;; SameSite=None; Secure
+Set-Cookie: <cookie-name>=<cookie-value>; SameSite=Strict
+Set-Cookie: <cookie-name>=<cookie-value>; SameSite=Lax
+Set-Cookie: <cookie-name>=<cookie-value>; SameSite=None; Secure
 
 // Multiple attributes are also possible, for example:
-Set-Cookie: &lt;cookie-name&gt;=&lt;cookie-value&gt;; Domain=&lt;domain-value&gt;; Secure; HttpOnly
-</pre>
-
-<h2 id="Attributes">Attributes</h2>
-
-<dl>
-  <dt><code>&lt;cookie-name&gt;=&lt;cookie-value&gt;</code></dt>
-  <dd>
-    <p>A cookie begins with a name-value pair.</p>
-    <p>
-      A <code>&lt;cookie-name&gt;</code> can be any US-ASCII characters,
-      except control characters, spaces, or tabs.
-      It also must not contain a separator character like the following: <code>( ) &lt; &gt; @ , ; : \ " / [ ] ? = { }</code>.
-    </p>
-    <p>
-      A <code>&lt;cookie-value&gt;</code> can optionally be wrapped in double quotes
-      and include any US-ASCII characters excluding control characters, {{glossary("Whitespace")}}, double quotes, comma, semicolon, and backslash.
-    </p>
-    <p>
-      <strong>Encoding</strong>: Many implementations perform URL encoding on cookie values,
-      however it is not required per the RFC specification.
-      It does help satisfying the requirements
-      about which characters are allowed for &lt;cookie-value&gt; though.
-    </p>
-    <div class="notecard note">
-      <p><strong>Note:</strong> Some <code>>&lt;cookie-name&gt;</code> have a specific semantic:</p>
-      <p>
-        <strong><code>__Secure-</code> prefix</strong>:
-        Cookies names starting with<code> __Secure-</code>
-        (dash is part of the prefix)
-        must be set with the <code>secure</code> flag from a secure page (HTTPS).
-      </p>
-      <p>
-        <strong><code>__Host-</code> prefix</strong>: Cookies with names starting with <code>__Host-</code> must be set with the <code>secure</code> flag, must be from a secure page (HTTPS), must not have a domain specified (and therefore aren't sent to subdomains) and the path must be <code>/</code>.
-      </p>
-    </div>
-  </dd>
-
-  <dt><code>Expires=&lt;date&gt;</code> {{optional_inline}}</dt>
-  <dd>
-    <p>
-      The maximum lifetime of the cookie as an HTTP-date timestamp.
-      See {{HTTPHeader("Date")}} for the required formatting.
-    </p>
-
-    <p>
-      If unspecified, the cookie becomes a <strong>session cookie</strong>.
-      A session finishes when the client shuts down,
-      and session cookies will be removed.
-    </p>
-
-    <div class="notecard warning">
-      <p><strong>Warning:</strong> Many web browsers have a <em>session restore</em> feature that will save all tabs and restore them next time the browser is used. Session cookies will also be restored, as if the browser was never closed.</p>
-    </div>
-
-    <p>When an <code>Expires</code> date is set, the deadline is relative to the <em>client</em> the cookie is being set on, not the server.</p>
-  </dd>
-
-  <dt><code>Max-Age=&lt;number&gt; </code>{{optional_inline}}</dt>
-  <dd>Number of seconds until the cookie expires. A zero or negative number will expire the cookie immediately. If both <code>Expires</code> and <code>Max-Age</code> are set, <code>Max-Age</code> has precedence.</dd>
-
-  <dt><code>Domain=&lt;domain-value&gt;</code> {{optional_inline}}</dt>
-  <dd>
-    <p>Host to which the cookie will be sent.</p>
-    <p>
-      If omitted, defaults to the host of the current document URL,
-      not including subdomains.
-    </p>
-    <p>
-      Contrary to earlier specifications,
-      leading dots in domain names (<code>.example.com</code>) are ignored.
-    </p>
-    <p>
-      Multiple host/domain values are <em>not</em> allowed,
-      but if a domain <em>is</em> specified, t
-      hen subdomains are always included.
-    </p>
-  </dd>
-
-  <dt><code>Path=&lt;path-value&gt;</code> {{optional_inline}}</dt>
-  <dd>
-    <p>
-      A path that must exist in the requested URL,
-      or the browser won't send the <code>Cookie</code> header.
-    </p>
-    <p>
-      The forward slash (<code>/</code>) character is interpreted as a directory separator,
-      and subdirectories will be matched as well:
-      for <code>Path=/docs</code>, <code>/docs</code>, <code>/docs/Web/</code>, and <code>/docs/Web/HTTP</code> will all match.
-    </p>
-
-  <dt id="Secure"><code>Secure</code> {{optional_inline}}</dt>
-  <dd>Cookie is only sent to the server when a request is made with the <code>https:</code> scheme (except on localhost), and therefore is more resistent to <a href="/en-US/docs/Glossary/MitM">man-in-the-middle</a> attacks.
-    <div class="notecard note">
-      <p><strong>Note:</strong> Do not assume that <code>Secure</code> prevents all access to sensitive information in cookies (session keys, login details, etc.). Cookies with this attribute can still be read/modified with access to the client's hard disk, or from JavaScript if the <code>HttpOnly</code> cookie attribute is not set.</p>
-      <p>Insecure sites (<code>http:</code>) can't set cookies with the <code>Secure</code> attribute (since Chrome 52 and Firefox 52). For Firefox, the <code>https:</code> requirements are ignored when the <code>Secure</code> attribute is set by localhost (since Firefox 75).</p>
-    </div>
-  </dd>
-
-  <dt id="HttpOnly"><code>HttpOnly</code> {{optional_inline}}</dt>
-  <dd>Forbids JavaScript from accessing the cookie, for example, through the {{domxref("Document.cookie")}} property. Note that a cookie that has been created with HttpOnly will still be sent with JavaScript-initiated requests, e.g. when calling {{domxref("XMLHttpRequest.send()")}} or {{domxref("WindowOrWorkerGlobalScope.fetch")}}. This mitigates attacks against cross-site scripting ({{Glossary("Cross-site_scripting", "XSS")}}).</dd>
-
-  <dt id="SameSite"><code>SameSite=&lt;samesite-value&gt;</code> {{optional_inline}}</dt>
-  <dd>
-    <p>
-      Controls whether a cookie is sent with cross-origin requests,
-      providing some protection against cross-site request forgery attacks ({{Glossary("CSRF")}}).
-    </p>
-    <div class="notecard note">
-      <p><strong>Note:</strong> Standards related to the <a href="/en-US/docs/Web/HTTP/Headers/Set-Cookie/SameSite">SameSite Cookies</a> recently changed such that:</p>
-      <ol>
-        <li>The cookie-sending behavior if <code>SameSite</code> is not specified is <code>SameSite=Lax</code>. Previously the default was that cookies were sent for all requests.</li>
-        <li>Cookies with <code>SameSite=None</code> must now<br>
-        also specify the <code>Secure</code> attribute (i.e. they require a secure context).</li>
-      </ol>
-      <p>The options below covers the new behavior. See the <a href="/en-US/docs/Web/HTTP/Headers/Set-Cookie/SameSite#browser_compatibility">Browser compatibility</a> table for information about specific browser implementation (rows: "<code>SameSite</code>: Defaults to <code>Lax</code>" and "<code>SameSite</code>: Secure context required").</p>
-    </div>
-    <p>Inline options are: <code>Strict</code>, <code>Lax</code>, and <code>None</code>.</p>
-    <p>
-      <code>Strict</code> means that the browser sends the cookie only for same-site requests,
-      that is, requests originating from the same site that set the cookie.
-      If the request originated from a different URL than the current one,
-      no cookies with the <code>SameSite=Strict</code> attribute are sent.
-    </p>
-    <p>
-      <code>Lax</code>means that the cookie is not sent on cross-site requests,
-      such as calls to load images or frames,
-      but is sent when a user is navigating to the origin site from an external site
-      (e.g., if following a link).
-      This is the default behavior
-      if the <code>SameSite</code> attribute is not specified.
-    </p>
-    <p>
-      Finally, <code>None</code> means that the browser sends the cookie with both cross-site and same-site requests.
-      The <code>Secure</code> attribute must also be set when <code>SameSite=None</code>!
-    </p>
-  </dd>
-</dl>
-
-<h2 id="Examples">Examples</h2>
-
-<h3 id="Session_cookie">Session cookie</h3>
-
-<p><strong>Session cookies</strong> are removed when the client shuts down. Cookies are session cookies if they don't specify the <code>Expires</code> or <code>Max-Age</code> attributes.</p>
-
-<pre>Set-Cookie: sessionId=38afes7a8</pre>
-
-<h3 id="Permanent_cookie">Permanent cookie</h3>
-
-<p>Instead of expiring when the client is closed, <strong>permanent cookies</strong> expire at a specific date (<code>Expires</code>) or after a specific length of time (<code>Max-Age</code>).</p>
-
-<pre>Set-Cookie: id=a3fWa; Expires=Wed, 21 Oct 2015 07:28:00 GMT
-</pre>
-
-<pre>Set-Cookie: id=a3fWa; Max-Age=2592000</pre>
-
-<h3 id="Invalid_domains">Invalid domains</h3>
-
-<p>A cookie for a domain that does not include the server that set it <a href="https://datatracker.ietf.org/doc/html/rfc6265#section-4.1.2.3">should be rejected by the user agent</a>.</p>
-
-<p>The following cookie will be rejected if set by a server hosted on <code>originalcompany.com</code>:</p>
-
-<pre>Set-Cookie: qwerty=219ffwef9w0f; Domain=somecompany.co.uk</pre>
-
-<p>A cookie for a sub domain of the serving domain will be rejected.</p>
-
-<p>The following cookie will be rejected if set by a server hosted on <code>example.com</code>:</p>
-
-<pre>Set-Cookie: sessionId=e8bb43229de9; Domain=foo.example.com</pre>
-
-<h3 id="Cookie_prefixes">Cookie prefixes</h3>
-
-<p>Cookies names prefixed with <code>__Secure-</code> or <code>__Host-</code> can be used only if they are set with the <code>secure</code> attribute from a secure (HTTPS) origin.</p>
-
-<p>In addition, cookies with the <code>__Host-</code> prefix must have a path of <code>/</code> (meaning any path at the host) and must not have a <code>Domain</code> attribute.</p>
-
-<div class="notecard warning">
-  <p><strong>Warning:</strong> For clients that don't implement cookie prefixes, you cannot count on these additional assurances, and prefixed cookies will always be accepted.</p>
-</div>
-
-<pre>// Both accepted when from a secure origin (HTTPS)
-Set-Cookie: __Secure-ID=123; Secure; Domain=example.com
-Set-Cookie: __Host-ID=123; Secure; Path=/
+Set-Cookie: <cookie-name>=<cookie-value>; Domain=<domain-value>; Secure; HttpOnly
+```
 
-// Rejected due to missing Secure attribute
-Set-Cookie: __Secure-id=1
+## Attributes
 
-// Rejected due to the missing Path=/ attribute
-Set-Cookie: __Host-id=1; Secure
+- `<cookie-name>=<cookie-value>`
 
-// Rejected due to setting a Domain
-Set-Cookie: __Host-id=1; Secure; Path=/; Domain=example.com
-</pre>
+  - : A cookie begins with a name-value pair.
 
-<h2 id="Specifications">Specifications</h2>
+    A `<cookie-name>` can be any US-ASCII characters,
+    except control characters, spaces, or tabs.
+    It also must not contain a separator character like the following: `( ) < > @ , ; : \ " / [ ] ? = { }`.
+
+    A `<cookie-value>` can optionally be wrapped in double quotes
+    and include any US-ASCII characters excluding control characters, {{glossary("Whitespace")}}, double quotes, comma, semicolon, and backslash.
+
+    **Encoding**: Many implementations perform URL encoding on cookie values,
+    however it is not required per the RFC specification.
+    It does help satisfying the requirements
+    about which characters are allowed for \<cookie-value> though.
+
+    > **Note:** Some `><cookie-name>` have a specific semantic:
+    >
+    > **`__Secure-` prefix**:
+    > Cookies names starting with` __Secure-`
+    > (dash is part of the prefix)
+    > must be set with the `secure` flag from a secure page (HTTPS).
+    >
+    > **`__Host-` prefix**: Cookies with names starting with `__Host-` must be set with the `secure` flag, must be from a secure page (HTTPS), must not have a domain specified (and therefore aren't sent to subdomains) and the path must be `/`.
+
+- `Expires=<date>` {{optional_inline}}
+
+  - : The maximum lifetime of the cookie as an HTTP-date timestamp.
+    See {{HTTPHeader("Date")}} for the required formatting.
+
+    If unspecified, the cookie becomes a **session cookie**.
+    A session finishes when the client shuts down,
+    and session cookies will be removed.
+
+    > **Warning:** Many web browsers have a _session restore_ feature that will save all tabs and restore them next time the browser is used. Session cookies will also be restored, as if the browser was never closed.
+
+    When an `Expires` date is set, the deadline is relative to the _client_ the cookie is being set on, not the server.
+
+- `Max-Age=<number> `{{optional_inline}}
+  - : Number of seconds until the cookie expires. A zero or negative number will expire the cookie immediately. If both `Expires` and `Max-Age` are set, `Max-Age` has precedence.
+- `Domain=<domain-value>` {{optional_inline}}
+
+  - : Host to which the cookie will be sent.
+
+    If omitted, defaults to the host of the current document URL,
+    not including subdomains.
+
+    Contrary to earlier specifications,
+    leading dots in domain names (`.example.com`) are ignored.
+
+    Multiple host/domain values are _not_ allowed,
+    but if a domain _is_ specified, t
+    hen subdomains are always included.
+
+- `Path=<path-value>` {{optional_inline}}
+
+  - : A path that must exist in the requested URL,
+    or the browser won't send the `Cookie` header.
+
+    The forward slash (`/`) character is interpreted as a directory separator,
+    and subdirectories will be matched as well:
+    for `Path=/docs`, `/docs`, `/docs/Web/`, and `/docs/Web/HTTP` will all match.
+
+- `Secure` {{optional_inline}}
+
+  - : Cookie is only sent to the server when a request is made with the `https:` scheme (except on localhost), and therefore is more resistent to [man-in-the-middle](/en-US/docs/Glossary/MitM) attacks.
+
+    > **Note:** Do not assume that `Secure` prevents all access to sensitive information in cookies (session keys, login details, etc.). Cookies with this attribute can still be read/modified with access to the client's hard disk, or from JavaScript if the `HttpOnly` cookie attribute is not set.
+    >
+    > Insecure sites (`http:`) can't set cookies with the `Secure` attribute (since Chrome 52 and Firefox 52). For Firefox, the `https:` requirements are ignored when the `Secure` attribute is set by localhost (since Firefox 75).
+
+- `HttpOnly` {{optional_inline}}
+  - : Forbids JavaScript from accessing the cookie, for example, through the {{domxref("Document.cookie")}} property. Note that a cookie that has been created with HttpOnly will still be sent with JavaScript-initiated requests, e.g. when calling {{domxref("XMLHttpRequest.send()")}} or {{domxref("WindowOrWorkerGlobalScope.fetch")}}. This mitigates attacks against cross-site scripting ({{Glossary("Cross-site_scripting", "XSS")}}).
+- `SameSite=<samesite-value>` {{optional_inline}}
+
+  - : Controls whether a cookie is sent with cross-origin requests,
+    providing some protection against cross-site request forgery attacks ({{Glossary("CSRF")}}).
+
+    > **Note:** Standards related to the [SameSite Cookies](/en-US/docs/Web/HTTP/Headers/Set-Cookie/SameSite) recently changed such that:
+    >
+    > 1.  The cookie-sending behavior if `SameSite` is not specified is `SameSite=Lax`. Previously the default was that cookies were sent for all requests.
+    > 2.  Cookies with `SameSite=None` must now
+    >     also specify the `Secure` attribute (i.e. they require a secure context).
+    >
+    > The options below covers the new behavior. See the [Browser compatibility](/en-US/docs/Web/HTTP/Headers/Set-Cookie/SameSite#browser_compatibility) table for information about specific browser implementation (rows: "`SameSite`: Defaults to `Lax`" and "`SameSite`: Secure context required").
+
+    Inline options are: `Strict`, `Lax`, and `None`.
+
+    `Strict` means that the browser sends the cookie only for same-site requests,
+    that is, requests originating from the same site that set the cookie.
+    If the request originated from a different URL than the current one,
+    no cookies with the `SameSite=Strict` attribute are sent.
+
+    `Lax`means that the cookie is not sent on cross-site requests,
+    such as calls to load images or frames,
+    but is sent when a user is navigating to the origin site from an external site
+    (e.g., if following a link).
+    This is the default behavior
+    if the `SameSite` attribute is not specified.
+
+    Finally, `None` means that the browser sends the cookie with both cross-site and same-site requests.
+    The `Secure` attribute must also be set when `SameSite=None`!
+
+## Examples
+
+### Session cookie
+
+**Session cookies** are removed when the client shuts down. Cookies are session cookies if they don't specify the `Expires` or `Max-Age` attributes.
+
+    Set-Cookie: sessionId=38afes7a8
+
+### Permanent cookie
+
+Instead of expiring when the client is closed, **permanent cookies** expire at a specific date (`Expires`) or after a specific length of time (`Max-Age`).
+
+    Set-Cookie: id=a3fWa; Expires=Wed, 21 Oct 2015 07:28:00 GMT
+
+<!---->
+
+    Set-Cookie: id=a3fWa; Max-Age=2592000
+
+### Invalid domains
+
+A cookie for a domain that does not include the server that set it [should be rejected by the user agent](https://datatracker.ietf.org/doc/html/rfc6265#section-4.1.2.3).
+
+The following cookie will be rejected if set by a server hosted on `originalcompany.com`:
+
+    Set-Cookie: qwerty=219ffwef9w0f; Domain=somecompany.co.uk
+
+A cookie for a sub domain of the serving domain will be rejected.
+
+The following cookie will be rejected if set by a server hosted on `example.com`:
+
+    Set-Cookie: sessionId=e8bb43229de9; Domain=foo.example.com
+
+### Cookie prefixes
+
+Cookies names prefixed with `__Secure-` or `__Host-` can be used only if they are set with the `secure` attribute from a secure (HTTPS) origin.
+
+In addition, cookies with the `__Host-` prefix must have a path of `/` (meaning any path at the host) and must not have a `Domain` attribute.
+
+> **Warning:** For clients that don't implement cookie prefixes, you cannot count on these additional assurances, and prefixed cookies will always be accepted.
+
+    // Both accepted when from a secure origin (HTTPS)
+    Set-Cookie: __Secure-ID=123; Secure; Domain=example.com
+    Set-Cookie: __Host-ID=123; Secure; Path=/
+
+    // Rejected due to missing Secure attribute
+    Set-Cookie: __Secure-id=1
+
+    // Rejected due to the missing Path=/ attribute
+    Set-Cookie: __Host-id=1; Secure
+
+    // Rejected due to setting a Domain
+    Set-Cookie: __Host-id=1; Secure; Path=/; Domain=example.com
+
+## Specifications
 
 {{Specifications}}
 
-<h2 id="Browser_compatibility">Browser compatibility</h2>
+## Browser compatibility
 
-<p>{{Compat}}</p>
+{{Compat}}
 
-<h2 id="Compatibility_notes">Compatibility notes</h2>
+## Compatibility notes
 
-<ul>
- <li>Starting with Chrome 52 and Firefox 52, insecure sites (<code>http:</code>) can't set cookies with the <code>Secure</code> attribute anymore.</li>
-</ul>
+- Starting with Chrome 52 and Firefox 52, insecure sites (`http:`) can't set cookies with the `Secure` attribute anymore.
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
- <li><a href="/en-US/docs/Web/HTTP/Cookies">HTTP cookies</a></li>
- <li>{{HTTPHeader("Cookie")}}</li>
- <li>{{domxref("Document.cookie")}}</li>
- <li><a href="/en-US/docs/Web/HTTP/Headers/Set-Cookie/SameSite">SameSite cookies</a></li>
-</ul>
+- [HTTP cookies](/en-US/docs/Web/HTTP/Cookies)
+- {{HTTPHeader("Cookie")}}
+- {{domxref("Document.cookie")}}
+- [SameSite cookies](/en-US/docs/Web/HTTP/Headers/Set-Cookie/SameSite)
diff --git a/files/en-us/web/http/headers/set-cookie/samesite/index.md b/files/en-us/web/http/headers/set-cookie/samesite/index.md
index 48c2056bbc25a2d..676e92c282fcedf 100644
--- a/files/en-us/web/http/headers/set-cookie/samesite/index.md
+++ b/files/en-us/web/http/headers/set-cookie/samesite/index.md
@@ -8,129 +8,115 @@ tags:
   - samesite
 browser-compat: http.headers.Set-Cookie.SameSite
 ---
-<div>{{HTTPSidebar}}</div>
+{{HTTPSidebar}}
 
-<p>The <strong><code>SameSite</code></strong> attribute of the {{HTTPHeader("Set-Cookie")}} HTTP response header allows you to declare if your cookie should be restricted to a <a href="/en-US/docs/Web/HTTP/Cookies#third-party_cookies">first-party</a> or same-site context.</p>
+The **`SameSite`** attribute of the {{HTTPHeader("Set-Cookie")}} HTTP response header allows you to declare if your cookie should be restricted to a [first-party](/en-US/docs/Web/HTTP/Cookies#third-party_cookies) or same-site context.
 
-<div class="notecard note">
-  <p><strong>Note:</strong> Standards related to the Cookie <code>SameSite</code> attribute recently changed such that:</p>
-  <ul>
-    <li>The cookie-sending behavior if <code>SameSite</code> is not specified is <code>SameSite=Lax</code>. Previously the default was that cookies were sent for all requests.</li>
-  <li>Cookies with <code>SameSite=None</code> must now also specify the <code>Secure</code> attribute (they require a secure context/HTTPS).</li>
-  </ul>
+> **Note:** Standards related to the Cookie `SameSite` attribute recently changed such that:
+>
+> - The cookie-sending behavior if `SameSite` is not specified is `SameSite=Lax`. Previously the default was that cookies were sent for all requests.
+> - Cookies with `SameSite=None` must now also specify the `Secure` attribute (they require a secure context/HTTPS).
+>
+> This article documents the new standard. See [Browser Compatibility](#browser_compatibility) below for information about specific versions where the behavior changed.
 
-  <p>This article documents the new standard. See <a href="#browser_compatibility">Browser Compatibility</a> below for information about specific versions where the behavior changed.</p>
-</div>
+## Values
 
-<h2 id="Values">Values</h2>
+The `SameSite` attribute accepts three values:
 
-<p>The <code>SameSite</code> attribute accepts three values:</p>
+### `Lax`
 
-<h3 id="Lax"><code>Lax</code></h3>
+Cookies are not sent on normal cross-site subrequests (for example to load images or frames into a third party site), but are sent when a user is _navigating to_ the origin site (i.e., when following a link).
 
-<p>Cookies are not sent on normal cross-site subrequests (for example to load images or frames into a third party site), but are sent when a user is <em>navigating to</em> the origin site (i.e., when following a link).</p>
+This is the default cookie value if `SameSite` has not been explicitly specified in recent browser versions (see the "SameSite: Defaults to Lax" feature in the Browser Compatibility).
 
-<p>This is the default cookie value if <code>SameSite</code> has not been explicitly specified in recent browser versions (see the "SameSite: Defaults to Lax" feature in the Browser Compatibility).</p>
+> **Note:** `Lax` replaced `None` as the default value in order to ensure that users have reasonably robust defense against some classes of cross-site request forgery ({{Glossary("CSRF")}}) attacks.
 
-<div class="notecard note">
-  <p><strong>Note:</strong> <code>Lax</code> replaced <code>None</code> as the default value in order to ensure that users have reasonably robust defense against some classes of cross-site request forgery ({{Glossary("CSRF")}}) attacks.</p>
-</div>
+### `Strict`
 
-<h3 id="Strict"><code>Strict</code></h3>
+Cookies will only be sent in a first-party context and not be sent along with requests initiated by third party websites.
 
-<p>Cookies will only be sent in a first-party context and not be sent along with requests initiated by third party websites.</p>
+### `None`
 
-<h3 id="None"><code>None</code></h3>
+Cookies will be sent in all contexts, i.e. in responses to both first-party and cross-origin requests. If `SameSite=None` is set, the cookie [`Secure`](/en-US/docs/Web/HTTP/Headers/Set-Cookie#secure) attribute must also be set (or the cookie will be blocked).
 
-<p>Cookies will be sent in all contexts, i.e. in responses to both first-party and cross-origin requests. If <code>SameSite=None</code> is set, the cookie <a href="/en-US/docs/Web/HTTP/Headers/Set-Cookie#secure"><code>Secure</code></a> attribute must also be set (or the cookie will be blocked).</p>
+## Fixing common warnings
 
-<h2 id="Fixing_common_warnings">Fixing common warnings</h2>
+### `SameSite=None` requires `Secure`
 
-<h3 id="SameSiteNone_requires_Secure"><code>SameSite=None</code> requires <code>Secure</code></h3>
+Warnings like the ones below might appear in your console:
 
-<p>Warnings like the ones below might appear in your console:</p>
+```html
+Cookie “myCookie” rejected because it has the “SameSite=None” attribute but is missing the “secure” attribute.
 
-<pre class="brush: html">Cookie “<em>myCookie</em>” rejected because it has the “SameSite=None” attribute but is missing the “secure” attribute.
+This Set-Cookie was blocked because it had the "SameSite=None" attribute but did not have the "Secure" attribute, which is required in order to use "SameSite=None".
+```
 
-This Set-Cookie was blocked because it had the "SameSite=None" attribute but did not have the "Secure" attribute, which is required in order to use "SameSite=None".</pre>
+The warning appears because any cookie that requests `SameSite=None` but is not marked `Secure` will be rejected.
 
-<p>The warning appears because any cookie that requests <code>SameSite=None</code> but is not marked <code>Secure</code> will be rejected.</p>
+```plain example-bad
+Set-Cookie: flavor=choco; SameSite=None
+```
 
-<pre class="example-bad">Set-Cookie: flavor=choco; SameSite=None</pre>
+To fix this, you will have to add the `Secure` attribute to your `SameSite=None` cookies.
 
-<p>To fix this, you will have to add the <code>Secure</code> attribute to your <code>SameSite=None</code> cookies.</p>
+```plain example-good
+Set-Cookie: flavor=choco; SameSite=None; Secure
+```
 
-<pre class="example-good">Set-Cookie: flavor=choco; SameSite=None; <strong>Secure</strong></pre>
+A [`Secure`](#secure) cookie is only sent to the server with an encrypted request over the HTTPS protocol. Note that insecure sites (`http:`) can't set cookies with the `Secure` directive.
 
-<p>A <a href="#secure"><code>Secure</code></a> cookie is only sent to the server with an encrypted request over the HTTPS protocol. Note that insecure sites (<code>http:</code>) can't set cookies with the <code>Secure</code> directive.</p>
+> **Note:** On older browser versions you might get a warning that the cookie will be blocked in future. For example:
+>
+> Cookie `myCookie` will be soon rejected
+> because it has the `SameSite` attribute set to `None`
+> or an invalid value, without the `secure` attribute.
 
-<div class="notecard note">
-  <p><strong>Note:</strong> On older browser versions you might get a warning that the cookie will be blocked in future. For example:</p>
-  <p>
-    Cookie <code>myCookie</code> will be soon rejected
-    because it has the <code>SameSite</code> attribute set to <code>None</code>
-    or an invalid value, without the <code>secure</code> attribute.
-  </p>
-</div>
+### Cookies without `SameSite` default to `SameSite=Lax`
 
-<h3 id="Cookies_without_SameSite_default_to_SameSiteLax">Cookies without <code>SameSite</code> default to <code>SameSite=Lax</code></h3>
+Recent versions of modern browsers provide a more secure default for `SameSite` to your cookies and so the following message might appear in your console:
 
-<p>Recent versions of modern browsers provide a more secure default for <code>SameSite</code> to your cookies and so the following message might appear in your console:</p>
+```html
+Cookie “myCookie” has “SameSite” policy set to “Lax” because it is missing a “SameSite” attribute, and “SameSite=Lax” is the default value for this attribute.
+```
 
-<pre class="brush: html">Cookie “<em>myCookie</em>” has “SameSite” policy set to “Lax” because it is missing a “SameSite” attribute, and “SameSite=Lax” is the default value for this attribute.
-</pre>
+The warning appears because the `SameSite` policy for a cookie was not explicitly specified:
 
-<p>The warning appears because the <code>SameSite</code> policy for a cookie was not explicitly specified:</p>
+```plain example-bad
+Set-Cookie: flavor=choco
+```
 
-<pre class="example-bad">Set-Cookie: flavor=choco</pre>
+You should explicitly communicate the intended `SameSite` policy for your cookie (rather than relying on browsers to apply `SameSite=Lax` automatically). This will also improve the experience across browsers as not all of them default to `Lax` yet.
 
-<p>You should explicitly communicate the intended <code>SameSite</code> policy for your cookie (rather than relying on browsers to apply <code>SameSite=Lax</code> automatically). This will also improve the experience across browsers as not all of them default to <code>Lax</code> yet.</p>
+```plain example-good
+Set-Cookie: flavor=choco; SameSite=Lax
+```
 
-<pre class="example-good">Set-Cookie: flavor=choco; <strong>SameSite=Lax</strong></pre>
+## Example:
 
-<h2 id="Example">Example:</h2>
+    RewriteEngine on
+    RewriteBase "/"
+    RewriteCond "%{HTTP_HOST}"       "^example\.org$" [NC]
+    RewriteRule "^(.*)"              "https://www.example.org/index.html" [R=301,L,QSA]
+    RewriteRule "^(.*)\.ht$"         "index.php?nav=$1 [NC,L,QSA,CO=RewriteRule;01;https://www.example.org;30/;SameSite=None;Secure]
+    RewriteRule "^(.*)\.htm$"        "index.php?nav=$1 [NC,L,QSA,CO=RewriteRule;02;https://www.example.org;30/;SameSite=None;Secure]
+    RewriteRule "^(.*)\.html$"       "index.php?nav=$1 [NC,L,QSA,CO=RewriteRule;03;https://www.example.org;30/;SameSite=None;Secure]
+    [...]
+    RewriteRule "^admin/(.*)\.html$" "admin/index.php?nav=$1 [NC,L,QSA,CO=RewriteRule;09;https://www.example.org:30/;SameSite=Strict;Secure]
 
-<pre>RewriteEngine on
-RewriteBase "/"
-RewriteCond "%{HTTP_HOST}"       "^example\.org$" [NC]
-RewriteRule "^(.*)"              "https://www.example.org/index.html" [R=301,L,QSA]
-RewriteRule "^(.*)\.ht$"         "index.php?nav=$1 [NC,L,QSA,CO=RewriteRule;01;https://www.example.org;30/;SameSite=None;Secure]
-RewriteRule "^(.*)\.htm$"        "index.php?nav=$1 [NC,L,QSA,CO=RewriteRule;02;https://www.example.org;30/;SameSite=None;Secure]
-RewriteRule "^(.*)\.html$"       "index.php?nav=$1 [NC,L,QSA,CO=RewriteRule;03;https://www.example.org;30/;SameSite=None;Secure]
-[...]
-RewriteRule "^admin/(.*)\.html$" "admin/index.php?nav=$1 [NC,L,QSA,CO=RewriteRule;09;https://www.example.org:30/;SameSite=Strict;Secure]
-</pre>
+## Specifications
 
-<h2 id="Specifications">Specifications</h2>
+| Specification                                                                                              | Title                                                         |
+| ---------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------- |
+| {{RFC("6265", "Set-Cookie", "4.1")}}                                                           | HTTP State Management Mechanism                               |
+| [draft-ietf-httpbis-rfc6265bis-05](https://datatracker.ietf.org/doc/html/draft-ietf-httpbis-rfc6265bis-05) | Cookie Prefixes, Same-Site Cookies, and Strict Secure Cookies |
 
-<table class="standard-table">
- <thead>
-  <tr>
-   <th scope="col">Specification</th>
-   <th scope="col">Title</th>
-  </tr>
- </thead>
- <tbody>
-  <tr>
-   <td>{{RFC("6265", "Set-Cookie", "4.1")}}</td>
-   <td>HTTP State Management Mechanism</td>
-  </tr>
-  <tr>
-   <td><a href="https://datatracker.ietf.org/doc/html/draft-ietf-httpbis-rfc6265bis-05">draft-ietf-httpbis-rfc6265bis-05</a></td>
-   <td>Cookie Prefixes, Same-Site Cookies, and Strict Secure Cookies</td>
-  </tr>
- </tbody>
-</table>
+## Browser compatibility
 
-<h2 id="Browser_compatibility">Browser compatibility</h2>
+{{Compat}}
 
-<p>{{Compat}}</p>
+## See also
 
-<h2 id="See_also">See also</h2>
-
-<ul>
- <li><a href="/en-US/docs/Web/HTTP/Cookies">HTTP cookies</a></li>
- <li>{{HTTPHeader("Cookie")}}</li>
- <li>{{domxref("Document.cookie")}}</li>
- <li><a href="https://web.dev/samesite-cookies-explained/">Samesite cookies explained</a> (web.dev blog)</li>
-</ul>
+- [HTTP cookies](/en-US/docs/Web/HTTP/Cookies)
+- {{HTTPHeader("Cookie")}}
+- {{domxref("Document.cookie")}}
+- [Samesite cookies explained](https://web.dev/samesite-cookies-explained/) (web.dev blog)
diff --git a/files/en-us/web/http/headers/set-cookie2/index.md b/files/en-us/web/http/headers/set-cookie2/index.md
index 2f144e8ec599d8d..9411f2cf04b352b 100644
--- a/files/en-us/web/http/headers/set-cookie2/index.md
+++ b/files/en-us/web/http/headers/set-cookie2/index.md
@@ -2,18 +2,18 @@
 title: Set-Cookie2
 slug: Web/HTTP/Headers/Set-Cookie2
 tags:
-- Cookies
-- HTTP
-- Deprecated
-- Reference
-- header
+  - Cookies
+  - HTTP
+  - Deprecated
+  - Reference
+  - header
 browser-compat: http.headers.Set-Cookie2
 ---
-<div>{{HTTPSidebar}} {{deprecated_header}}</div>
+{{HTTPSidebar}} {{deprecated_header}}
 
-<p>The obsolete <strong><code>Set-Cookie2</code></strong> HTTP response header used to
-  send cookies from the server to the user agent, but has been deprecated by the
-  specification. Use {{HTTPHeader("Set-Cookie")}} instead.</p>
+The obsolete **`Set-Cookie2`** HTTP response header used to
+send cookies from the server to the user agent, but has been deprecated by the
+specification. Use {{HTTPHeader("Set-Cookie")}} instead.
 
 <table class="properties">
   <tbody>
@@ -28,49 +28,38 @@ browser-compat: http.headers.Set-Cookie2
   </tbody>
 </table>
 
-<h2 id="Syntax">Syntax</h2>
+## Syntax
 
-<pre class="brush: html">Set-Cookie2: &lt;cookie-name&gt;=&lt;cookie-value&gt;
-Set-Cookie2: &lt;cookie-name&gt;=&lt;cookie-value&gt;; Comment=&lt;value&gt;
-Set-Cookie2: &lt;cookie-name&gt;=&lt;cookie-value&gt;; CommentURL=&lt;http-url&gt;
-Set-Cookie2: &lt;cookie-name&gt;=&lt;cookie-value&gt;; Discard
-Set-Cookie2: &lt;cookie-name&gt;=&lt;cookie-value&gt;; Domain=&lt;domain-value&gt;
-Set-Cookie2: &lt;cookie-name&gt;=&lt;cookie-value&gt;; Max-Age=&lt;non-zero-digit&gt;
-Set-Cookie2: &lt;cookie-name&gt;=&lt;cookie-value&gt;; Path=&lt;path-value&gt;
-Set-Cookie2: &lt;cookie-name&gt;=&lt;cookie-value&gt;; Port=&lt;port-number&gt;
-Set-Cookie2: &lt;cookie-name&gt;=&lt;cookie-value&gt;; Secure
-Set-Cookie2: &lt;cookie-name&gt;=&lt;cookie-value&gt;; Version=&lt;version-number&gt;
+```html
+Set-Cookie2: <cookie-name>=<cookie-value>
+Set-Cookie2: <cookie-name>=<cookie-value>; Comment=<value>
+Set-Cookie2: <cookie-name>=<cookie-value>; CommentURL=<http-url>
+Set-Cookie2: <cookie-name>=<cookie-value>; Discard
+Set-Cookie2: <cookie-name>=<cookie-value>; Domain=<domain-value>
+Set-Cookie2: <cookie-name>=<cookie-value>; Max-Age=<non-zero-digit>
+Set-Cookie2: <cookie-name>=<cookie-value>; Path=<path-value>
+Set-Cookie2: <cookie-name>=<cookie-value>; Port=<port-number>
+Set-Cookie2: <cookie-name>=<cookie-value>; Secure
+Set-Cookie2: <cookie-name>=<cookie-value>; Version=<version-number>
 
 // Multiple directives are also possible, for example:
-Set-Cookie2: &lt;cookie-name&gt;=&lt;cookie-value&gt;; Domain=&lt;domain-value&gt;; Secure
+Set-Cookie2: <cookie-name>=<cookie-value>; Domain=<domain-value>; Secure
 
 // Multiple cookies are separated by a comma
-Set-Cookie2: &lt;cookie-name&gt;=&lt;cookie-value&gt;, &lt;cookie-name&gt;=&lt;cookie-value&gt;, ...
-</pre>
+Set-Cookie2: <cookie-name>=<cookie-value>, <cookie-name>=<cookie-value>, ...
+```
 
-<h2 id="Specifications">Specifications</h2>
+## Specifications
 
-<table class="standard-table">
-  <tbody>
-    <tr>
-      <th scope="col">Specification</th>
-      <th scope="col">Title</th>
-    </tr>
-    <tr>
-      <td>{{RFC("2965", "Set-Cookie2")}}</td>
-      <td>Historic specification of HTTP State Management Mechanism, obsoleted
-        by {{RFC("6265")}}</td>
-    </tr>
-  </tbody>
-</table>
+| Specification                            | Title                                                                                        |
+| ---------------------------------------- | -------------------------------------------------------------------------------------------- |
+| {{RFC("2965", "Set-Cookie2")}} | Historic specification of HTTP State Management Mechanism, obsoleted by {{RFC("6265")}} |
 
-<h2 id="Browser_compatibility">Browser compatibility</h2>
+## Browser compatibility
 
-<p>{{Compat}}</p>
+{{Compat}}
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
-  <li>{{HTTPHeader("Set-Cookie")}}</li>
-  <li>{{domxref("Document.cookie")}}</li>
-</ul>
+- {{HTTPHeader("Set-Cookie")}}
+- {{domxref("Document.cookie")}}
diff --git a/files/en-us/web/http/headers/sourcemap/index.md b/files/en-us/web/http/headers/sourcemap/index.md
index 4acd42bd1d4ea4c..c0a8eeaec127965 100644
--- a/files/en-us/web/http/headers/sourcemap/index.md
+++ b/files/en-us/web/http/headers/sourcemap/index.md
@@ -9,61 +9,49 @@ tags:
   - header
 browser-compat: http.headers.SourceMap
 ---
-<div>{{HTTPSidebar}}</div>
+{{HTTPSidebar}}
 
-<p>The <strong><code>SourceMap</code></strong> <a href="/en-US/docs/Web/HTTP">HTTP</a> response header links generated code to a <a href="/en-US/docs/Tools/Debugger/How_to/Use_a_source_map">source map</a>, enabling the browser to reconstruct the original source and present the reconstructed original in the debugger.</p>
+The **`SourceMap`** [HTTP](/en-US/docs/Web/HTTP) response header links generated code to a [source map](/en-US/docs/Tools/Debugger/How_to/Use_a_source_map), enabling the browser to reconstruct the original source and present the reconstructed original in the debugger.
 
 <table class="properties">
-	<tbody>
-		<tr>
-			<th scope="row">Header type</th>
-			<td>{{Glossary("Response header")}}</td>
-		</tr>
-		<tr>
-			<th scope="row">{{Glossary("Forbidden header name")}}</th>
-			<td>no</td>
-		</tr>
-	</tbody>
+  <tbody>
+    <tr>
+      <th scope="row">Header type</th>
+      <td>{{Glossary("Response header")}}</td>
+    </tr>
+    <tr>
+      <th scope="row">{{Glossary("Forbidden header name")}}</th>
+      <td>no</td>
+    </tr>
+  </tbody>
 </table>
 
-<h2 id="Syntax">Syntax</h2>
+## Syntax
 
-<pre class="brush: html">SourceMap: &lt;url&gt;
-X-SourceMap: &lt;url&gt; (deprecated)
-</pre>
+```html
+SourceMap: <url>
+X-SourceMap: <url> (deprecated)
+```
 
-<h3 id="Directives">Directives</h3>
+### Directives
 
-<dl>
-	<dt><code>&lt;url&gt;</code></dt>
-	<dd>A relative (to the request URL) or absolute URL pointing to a source map file.</dd>
-</dl>
+- `<url>`
+  - : A relative (to the request URL) or absolute URL pointing to a source map file.
 
-<h2 id="Examples">Examples</h2>
+## Examples
 
-<pre>SourceMap: /path/to/file.js.map</pre>
+    SourceMap: /path/to/file.js.map
 
-<h2 id="Specifications">Specifications</h2>
+## Specifications
 
-<table class="standard-table">
-	<tbody>
-		<tr>
-			<th scope="col">Specification</th>
-			<th scope="col">Title</th>
-		</tr>
-		<tr>
-			<td><a href="https://sourcemaps.info/spec.html">Draft document</a></td>
-			<td>Source Map Revision 3 Proposal</td>
-		</tr>
-	</tbody>
-</table>
+| Specification                                       | Title                          |
+| --------------------------------------------------- | ------------------------------ |
+| [Draft document](https://sourcemaps.info/spec.html) | Source Map Revision 3 Proposal |
 
-<h2 id="Browser_compatibility">Browser compatibility</h2>
+## Browser compatibility
 
-<p>{{Compat}}</p>
+{{Compat}}
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
-	<li><a href="/en-US/docs/Tools/Debugger/How_to/Use_a_source_map">Firefox Developer Tools: using a source map</a></li>
-</ul>
+- [Firefox Developer Tools: using a source map](/en-US/docs/Tools/Debugger/How_to/Use_a_source_map)
diff --git a/files/en-us/web/http/headers/strict-transport-security/index.md b/files/en-us/web/http/headers/strict-transport-security/index.md
index 5ca4149a1dc04da..40f1803e32fe696 100644
--- a/files/en-us/web/http/headers/strict-transport-security/index.md
+++ b/files/en-us/web/http/headers/strict-transport-security/index.md
@@ -2,18 +2,18 @@
 title: Strict-Transport-Security
 slug: Web/HTTP/Headers/Strict-Transport-Security
 tags:
-- HSTS
-- HTTP
-- HTTPS
-- Security
-- header
+  - HSTS
+  - HTTP
+  - HTTPS
+  - Security
+  - header
 browser-compat: http.headers.Strict-Transport-Security
 ---
-<div>{{HTTPSidebar}}</div>
+{{HTTPSidebar}}
 
-<p>The <strong>HTTP <code>Strict-Transport-Security</code></strong> response header (often
-  abbreviated as {{Glossary("HSTS")}}) lets a web site tell browsers that it should only
-  be accessed using HTTPS, instead of using HTTP.</p>
+The **HTTP `Strict-Transport-Security`** response header (often
+abbreviated as {{Glossary("HSTS")}}) lets a web site tell browsers that it should only
+be accessed using HTTPS, instead of using HTTP.
 
 <table class="properties">
   <tbody>
@@ -28,135 +28,121 @@ browser-compat: http.headers.Strict-Transport-Security
   </tbody>
 </table>
 
-<h2 id="Syntax">Syntax</h2>
-
-<pre class="brush: html">Strict-Transport-Security: max-age=&lt;expire-time&gt;
-Strict-Transport-Security: max-age=&lt;expire-time&gt;; includeSubDomains
-Strict-Transport-Security: max-age=&lt;expire-time&gt;; preload
-</pre>
-
-<h2 id="Directives">Directives</h2>
-
-<dl>
-  <dt><code>max-age=&lt;expire-time&gt;</code></dt>
-  <dd>The time, in seconds, that the browser should remember that a site is only to be
-    accessed using HTTPS.</dd>
-  <dt><code>includeSubDomains</code> {{optional_inline}}</dt>
-  <dd>If this optional parameter is specified, this rule applies to all of the site's
-    subdomains as well.</dd>
-  <dt><code>preload</code> {{optional_inline}}</dt>
-  <dd>See {{anch("Preloading Strict Transport Security")}} for details. Not part of the
-    specification.</dd>
-</dl>
-
-<h2 id="Description">Description</h2>
-
-<p>If a website accepts a connection through HTTP and redirects to HTTPS, visitors may
-  initially communicate with the non-encrypted version of the site before being
-  redirected, if, for example, the visitor types http://www.foo.com/ or even just foo.com.
-  This creates an opportunity for a man-in-the-middle attack. The redirect could be
-  exploited to direct visitors to a malicious site instead of the secure version of the
-  original site.</p>
-
-<p>The HTTP Strict Transport Security header informs the browser that it should never load
-  a site using HTTP and should automatically convert all attempts to access the site using
-  HTTP to HTTPS requests instead.</p>
-
-<div class="notecard note">
-  <p><strong>Note:</strong> The <code>Strict-Transport-Security</code> header
-  is <strong>ignored</strong> by the browser when your site is accessed using HTTP; this
-  is because an attacker may intercept HTTP connections and inject the header or remove
-  it. When your site is accessed over HTTPS with no certificate errors, the browser knows
-  your site is HTTPS capable and will honor the <code>Strict-Transport-Security</code>
-  header.</p>
-</div>
-
-<h3 id="An_example_scenario">An example scenario</h3>
-
-<p>You log into a free WiFi access point at an airport and start surfing the web, visiting
-  your online banking service to check your balance and pay a couple of bills.
-  Unfortunately, the access point you're using is actually a hacker's laptop, and they're
-  intercepting your original HTTP request and redirecting you to a clone of your bank's
-  site instead of the real thing. Now your private data is exposed to the hacker.</p>
-
-<p>Strict Transport Security resolves this problem; as long as you've accessed your bank's
-  web site once using HTTPS, and the bank's web site uses Strict Transport Security, your
-  browser will know to automatically use only HTTPS, which prevents hackers from
-  performing this sort of man-in-the-middle attack.</p>
-
-<h3 id="How_the_browser_handles_it">How the browser handles it</h3>
-
-<p>The first time your site is accessed using HTTPS and it returns the
-  <code>Strict-Transport-Security</code> header, the browser records this information, so
-  that future attempts to load the site using HTTP will automatically use HTTPS instead.
-</p>
-
-<p>When the expiration time specified by the Strict-Transport-Security header elapses, the
-  next attempt to load the site via HTTP will proceed as normal instead of automatically
-  using HTTPS.</p>
-
-<p>Whenever the Strict-Transport-Security header is delivered to the browser, it will
-  update the expiration time for that site, so sites can refresh this information and
-  prevent the timeout from expiring. Should it be necessary to disable Strict Transport
-  Security, setting the max-age to 0 (over a https connection) will immediately expire the
-  <code>Strict-Transport-Security</code> header, allowing access via http.</p>
-
-<h2 id="Preloading_Strict_Transport_Security">Preloading Strict Transport Security</h2>
-
-<p>Google maintains <a href="https://hstspreload.org/">an HSTS preload service</a>. By
-  following the guidelines and successfully submitting your domain, browsers will never
-  connect to your domain using an insecure connection. While the service is hosted by
-  Google, all browsers have stated an intent to use (or actually started using) the
-  preload list. However, it is not part of the HSTS specification and should not be
-  treated as official.</p>
-
-<ul>
-  <li>Information regarding the HSTS preload list in Chrome : <a
-      href="https://www.chromium.org/hsts">https://www.chromium.org/hsts</a></li>
-  <li>Consultation of the Firefox HSTS preload list : <a
-      href="https://hg.mozilla.org/mozilla-central/raw-file/tip/security/manager/ssl/nsSTSPreloadList.inc">nsSTSPreloadList.inc</a>
-  </li>
-</ul>
-
-<h2 id="Examples">Examples</h2>
-
-<p>All present and future subdomains will be HTTPS for a max-age of 1 year. This blocks
-  access to pages or sub domains that can only be served over HTTP.</p>
-
-<pre>Strict-Transport-Security: max-age=31536000; includeSubDomains</pre>
-
-<p>In the following example, <code>max-age</code> is set to 2 years, raised from what was
-  a former limit <code>max-age</code> of 1 year. Note that 1 year is acceptable for a
-  domain to be included in browsers' HSTS preload lists. 2 years is, however, the
-  recommended goal as a website's final HSTS configuration as explained on <a
-    href="https://hstspreload.org">https://hstspreload.org</a>. It also suffixed with
-  <code>preload</code> which is necessary for inclusion in most major web browsers' HSTS
-  preload lists, e.g. Chromium, Edge, &amp; Firefox.</p>
-
-<pre>Strict-Transport-Security: max-age=63072000; includeSubDomains; preload</pre>
-
-<h2 id="Specifications">Specifications</h2>
+## Syntax
+
+```html
+Strict-Transport-Security: max-age=<expire-time>
+Strict-Transport-Security: max-age=<expire-time>; includeSubDomains
+Strict-Transport-Security: max-age=<expire-time>; preload
+```
+
+## Directives
+
+- `max-age=<expire-time>`
+  - : The time, in seconds, that the browser should remember that a site is only to be
+    accessed using HTTPS.
+- `includeSubDomains` {{optional_inline}}
+  - : If this optional parameter is specified, this rule applies to all of the site's
+    subdomains as well.
+- `preload` {{optional_inline}}
+  - : See {{anch("Preloading Strict Transport Security")}} for details. Not part of the
+    specification.
+
+## Description
+
+If a website accepts a connection through HTTP and redirects to HTTPS, visitors may
+initially communicate with the non-encrypted version of the site before being
+redirected, if, for example, the visitor types http\://www\.foo.com/ or even just foo.com.
+This creates an opportunity for a man-in-the-middle attack. The redirect could be
+exploited to direct visitors to a malicious site instead of the secure version of the
+original site.
+
+The HTTP Strict Transport Security header informs the browser that it should never load
+a site using HTTP and should automatically convert all attempts to access the site using
+HTTP to HTTPS requests instead.
+
+> **Note:** The `Strict-Transport-Security` header
+> is **ignored** by the browser when your site is accessed using HTTP; this
+> is because an attacker may intercept HTTP connections and inject the header or remove
+> it. When your site is accessed over HTTPS with no certificate errors, the browser knows
+> your site is HTTPS capable and will honor the `Strict-Transport-Security`
+> header.
+
+### An example scenario
+
+You log into a free WiFi access point at an airport and start surfing the web, visiting
+your online banking service to check your balance and pay a couple of bills.
+Unfortunately, the access point you're using is actually a hacker's laptop, and they're
+intercepting your original HTTP request and redirecting you to a clone of your bank's
+site instead of the real thing. Now your private data is exposed to the hacker.
+
+Strict Transport Security resolves this problem; as long as you've accessed your bank's
+web site once using HTTPS, and the bank's web site uses Strict Transport Security, your
+browser will know to automatically use only HTTPS, which prevents hackers from
+performing this sort of man-in-the-middle attack.
+
+### How the browser handles it
+
+The first time your site is accessed using HTTPS and it returns the
+`Strict-Transport-Security` header, the browser records this information, so
+that future attempts to load the site using HTTP will automatically use HTTPS instead.
+
+When the expiration time specified by the Strict-Transport-Security header elapses, the
+next attempt to load the site via HTTP will proceed as normal instead of automatically
+using HTTPS.
+
+Whenever the Strict-Transport-Security header is delivered to the browser, it will
+update the expiration time for that site, so sites can refresh this information and
+prevent the timeout from expiring. Should it be necessary to disable Strict Transport
+Security, setting the max-age to 0 (over a https connection) will immediately expire the
+`Strict-Transport-Security` header, allowing access via http.
+
+## Preloading Strict Transport Security
+
+Google maintains [an HSTS preload service](https://hstspreload.org/). By
+following the guidelines and successfully submitting your domain, browsers will never
+connect to your domain using an insecure connection. While the service is hosted by
+Google, all browsers have stated an intent to use (or actually started using) the
+preload list. However, it is not part of the HSTS specification and should not be
+treated as official.
+
+- Information regarding the HSTS preload list in Chrome : <https://www.chromium.org/hsts>
+- Consultation of the Firefox HSTS preload list : [nsSTSPreloadList.inc](https://hg.mozilla.org/mozilla-central/raw-file/tip/security/manager/ssl/nsSTSPreloadList.inc)
+
+## Examples
+
+All present and future subdomains will be HTTPS for a max-age of 1 year. This blocks
+access to pages or sub domains that can only be served over HTTP.
+
+    Strict-Transport-Security: max-age=31536000; includeSubDomains
+
+In the following example, `max-age` is set to 2 years, raised from what was
+a former limit `max-age` of 1 year. Note that 1 year is acceptable for a
+domain to be included in browsers' HSTS preload lists. 2 years is, however, the
+recommended goal as a website's final HSTS configuration as explained on <https://hstspreload.org>. It also suffixed with
+`preload` which is necessary for inclusion in most major web browsers' HSTS
+preload lists, e.g. Chromium, Edge, & Firefox.
+
+    Strict-Transport-Security: max-age=63072000; includeSubDomains; preload
+
+## Specifications
 
 {{Specifications}}
 
-<h2 id="Browser_compatibility">Browser compatibility</h2>
-
-<p>{{Compat}}</p>
-
-<h2 id="See_also">See also</h2>
-
-<ul>
-  <li>Blog post: <a       href="https://blog.sidstamm.com/2010/08/http-strict-transport-security-has.html">HTTP
-      Strict Transport Security has landed!</a></li>
-  <li>Blog post: <a       href="https://hacks.mozilla.org/2010/08/firefox-4-http-strict-transport-security-force-https/">HTTP
-      Strict Transport Security (force HTTPS)</a></li>
-  <li>OWASP Article: <a
-      href="https://cheatsheetseries.owasp.org/cheatsheets/HTTP_Strict_Transport_Security_Cheat_Sheet.html">HTTP
-      Strict Transport Security</a></li>
-  <li>Wikipedia: {{interwiki("wikipedia", "HTTP Strict Transport Security")}}</li>
-  <li>Browser test site: <a href="https://projects.dm.id.lv/Public-Key-Pins_test">HSTS and
-      HPKP test</a></li>
-  <li><a
-      href="/en-US/docs/Web/Security/Secure_Contexts/features_restricted_to_secure_contexts">Features
-      restricted to secure contexts</a></li>
-</ul>
+## Browser compatibility
+
+{{Compat}}
+
+## See also
+
+- Blog post: [HTTP
+  Strict Transport Security has landed!](https://blog.sidstamm.com/2010/08/http-strict-transport-security-has.html)
+- Blog post: [HTTP
+  Strict Transport Security (force HTTPS)](https://hacks.mozilla.org/2010/08/firefox-4-http-strict-transport-security-force-https/)
+- OWASP Article: [HTTP
+  Strict Transport Security](https://cheatsheetseries.owasp.org/cheatsheets/HTTP_Strict_Transport_Security_Cheat_Sheet.html)
+- Wikipedia: {{interwiki("wikipedia", "HTTP Strict Transport Security")}}
+- Browser test site: [HSTS and
+  HPKP test](https://projects.dm.id.lv/Public-Key-Pins_test)
+- [Features
+  restricted to secure contexts](/en-US/docs/Web/Security/Secure_Contexts/features_restricted_to_secure_contexts)
diff --git a/files/en-us/web/http/headers/te/index.md b/files/en-us/web/http/headers/te/index.md
index 2af55bd820ee527..27fa8dbde73c5da 100644
--- a/files/en-us/web/http/headers/te/index.md
+++ b/files/en-us/web/http/headers/te/index.md
@@ -2,28 +2,26 @@
 title: TE
 slug: Web/HTTP/Headers/TE
 tags:
-- HTTP
-- Reference
-- header
+  - HTTP
+  - Reference
+  - header
 browser-compat: http.headers.TE
 ---
-<div>{{HTTPSidebar}}</div>
+{{HTTPSidebar}}
 
-<p>The <code><strong>TE</strong></code> request header specifies the transfer encodings
-  the user agent is willing to accept. (you could informally call it
-  <em><code>Accept-Transfer-Encoding</code></em>, which would be more intuitive).</p>
+The **`TE`** request header specifies the transfer encodings
+the user agent is willing to accept. (you could informally call it
+_`Accept-Transfer-Encoding`_, which would be more intuitive).
 
-<div class="notecard note">
-  <p><strong>Note:</strong> <a href="https://datatracker.ietf.org/doc/html/rfc7540#section-8.1.2.2">In HTTP/2,
-    the <code>TE</code> header field is only accepted
-    if the <code>trailers</code> value is set.</a></p>
-</div>
+> **Note:** [In HTTP/2,
+> the `TE` header field is only accepted
+> if the `trailers` value is set.](https://datatracker.ietf.org/doc/html/rfc7540#section-8.1.2.2)
 
-<p>See also the {{HTTPHeader("Transfer-Encoding")}} response header for more details on
-  transfer encodings. Note that <code>chunked</code> is always acceptable for HTTP/1.1
-  recipients and you don't have to specify <code>"chunked"</code> using the
-  <code>TE</code> header. However, it is useful for setting if the client is accepting
-  trailer fields in a chunked transfer coding using the "trailers" value.</p>
+See also the {{HTTPHeader("Transfer-Encoding")}} response header for more details on
+transfer encodings. Note that `chunked` is always acceptable for HTTP/1.1
+recipients and you don't have to specify `"chunked"` using the
+`TE` header. However, it is useful for setting if the client is accepting
+trailer fields in a chunked transfer coding using the "trailers" value.
 
 <table class="properties">
   <tbody>
@@ -38,55 +36,48 @@ browser-compat: http.headers.TE
   </tbody>
 </table>
 
-<h2 id="Syntax">Syntax</h2>
+## Syntax
 
-<pre class="brush: html">TE: compress
+```html
+TE: compress
 TE: deflate
 TE: gzip
 TE: trailers
 
 // Multiple directives, weighted with the {{glossary("quality values", "quality value")}} syntax:
 TE: trailers, deflate;q=0.5
-</pre>
+```
 
-<h2 id="Directives">Directives</h2>
+## Directives
 
-<dl>
-  <dt><code>compress</code></dt>
-  <dd>A format using the <a       href="https://en.wikipedia.org/wiki/LZW">Lempel-Ziv-Welch</a> (LZW) algorithm is
-    accepted as a transfer coding name.</dd>
-  <dt><code>deflate</code></dt>
-  <dd>Using the <a href="https://en.wikipedia.org/wiki/Zlib">zlib</a>
-    structure is accepted as a transfer coding name.</dd>
-  <dt><code>gzip</code></dt>
-  <dd>A format using the <a       href="https://en.wikipedia.org/wiki/LZ77_and_LZ78#LZ77">Lempel-Ziv coding</a>
-    (LZ77), with a 32-bit CRC is accepted as a transfer coding name.</dd>
-  <dt><code>trailers</code></dt>
-  <dd>Indicates that the client is willing to accept trailer fields in a chunked transfer
-    coding.</dd>
-  <dt><code>q</code></dt>
-  <dd>
-    <p>When multiple transfer codings are acceptable, the <code>q</code> parameter of the
-      <a href="/en-US/docs/Glossary/Quality_values">quality value</a> syntax can rank
-      codings by preference.</p>
-  </dd>
-</dl>
+- `compress`
+  - : A format using the [Lempel-Ziv-Welch](https://en.wikipedia.org/wiki/LZW) (LZW) algorithm is
+    accepted as a transfer coding name.
+- `deflate`
+  - : Using the [zlib](https://en.wikipedia.org/wiki/Zlib)
+    structure is accepted as a transfer coding name.
+- `gzip`
+  - : A format using the [Lempel-Ziv coding](https://en.wikipedia.org/wiki/LZ77_and_LZ78#LZ77)
+    (LZ77), with a 32-bit CRC is accepted as a transfer coding name.
+- `trailers`
+  - : Indicates that the client is willing to accept trailer fields in a chunked transfer
+    coding.
+- `q`
+  - : When multiple transfer codings are acceptable, the `q` parameter of the
+    [quality value](/en-US/docs/Glossary/Quality_values) syntax can rank
+    codings by preference.
 
-<h2 id="Specifications">Specifications</h2>
+## Specifications
 
 {{Specifications}}
 
-<h2 id="Browser_compatibility">Browser compatibility</h2>
+## Browser compatibility
 
-<p>{{Compat}}</p>
+{{Compat}}
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
-  <li>{{HTTPHeader("Transfer-Encoding")}}</li>
-  <li>{{HTTPHeader("Trailer")}}</li>
-  <li>
-    <p><a href="https://en.wikipedia.org/wiki/Chunked_transfer_encoding">Chunked transfer
-        encoding</a></p>
-  </li>
-</ul>
+- {{HTTPHeader("Transfer-Encoding")}}
+- {{HTTPHeader("Trailer")}}
+- [Chunked transfer
+  encoding](https://en.wikipedia.org/wiki/Chunked_transfer_encoding)
diff --git a/files/en-us/web/http/headers/timing-allow-origin/index.md b/files/en-us/web/http/headers/timing-allow-origin/index.md
index c3eaaec11f2ec7a..035b52f80ee0a38 100644
--- a/files/en-us/web/http/headers/timing-allow-origin/index.md
+++ b/files/en-us/web/http/headers/timing-allow-origin/index.md
@@ -9,60 +9,57 @@ tags:
   - header
 browser-compat: http.headers.Timing-Allow-Origin
 ---
-<div>{{HTTPSidebar}}</div>
+{{HTTPSidebar}}
 
-<p>The <strong><code>Timing-Allow-Origin</code></strong> response header specifies origins that are allowed to see values of attributes retrieved via features of the <a href="/en-US/docs/Web/API/Resource_Timing_API">Resource Timing API</a>, which would otherwise be reported as zero due to cross-origin restrictions.</p>
+The **`Timing-Allow-Origin`** response header specifies origins that are allowed to see values of attributes retrieved via features of the [Resource Timing API](/en-US/docs/Web/API/Resource_Timing_API), which would otherwise be reported as zero due to cross-origin restrictions.
 
 <table class="properties">
- <tbody>
-  <tr>
-   <th scope="row">Header type</th>
-   <td>{{Glossary("Response header")}}</td>
-  </tr>
-  <tr>
-   <th scope="row">{{Glossary("Forbidden header name")}}</th>
-   <td>no</td>
-  </tr>
- </tbody>
+  <tbody>
+    <tr>
+      <th scope="row">Header type</th>
+      <td>{{Glossary("Response header")}}</td>
+    </tr>
+    <tr>
+      <th scope="row">{{Glossary("Forbidden header name")}}</th>
+      <td>no</td>
+    </tr>
+  </tbody>
 </table>
 
-<h2 id="Syntax">Syntax</h2>
+## Syntax
 
-<pre class="brush: html">Timing-Allow-Origin: *
-Timing-Allow-Origin: &lt;origin&gt;[, &lt;origin&gt;]*
-</pre>
+```html
+Timing-Allow-Origin: *
+Timing-Allow-Origin: <origin>[, <origin>]*
+```
 
-<h2 id="Directives">Directives</h2>
+## Directives
 
-<dl>
- <dt><code>*</code></dt>
- <dd>The server may specify "*" as a wildcard, thereby allowing any origin to see timing resources.</dd>
- <dt><code>&lt;origin&gt;</code></dt>
- <dd>Specifies a URI that may see the timing resources. You can specify multiple origins, separated by commas.</dd>
-</dl>
+- `*`
+  - : The server may specify "\*" as a wildcard, thereby allowing any origin to see timing resources.
+- `<origin>`
+  - : Specifies a URI that may see the timing resources. You can specify multiple origins, separated by commas.
 
-<h2 id="Examples">Examples</h2>
+## Examples
 
-<p>To allow any resource to see timing resources:</p>
+To allow any resource to see timing resources:
 
-<pre>Timing-Allow-Origin: *</pre>
+    Timing-Allow-Origin: *
 
-<p>To allow <code>https://developer.mozilla.org</code> to see timing resources, you can specify:</p>
+To allow `https://developer.mozilla.org` to see timing resources, you can specify:
 
-<pre>Timing-Allow-Origin: https://developer.mozilla.org</pre>
+    Timing-Allow-Origin: https://developer.mozilla.org
 
-<h2 id="Specifications">Specifications</h2>
+## Specifications
 
 {{Specifications}}
 
-<h2 id="Browser_compatibility">Browser compatibility</h2>
+## Browser compatibility
 
-<p>{{Compat}}</p>
+{{Compat}}
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
- <li><a href="/en-US/docs/Web/API/Resource_Timing_API">Resource Timing API</a></li>
- <li><a href="/en-US/docs/Web/API/Resource_Timing_API/Using_the_Resource_Timing_API">Using the Resource Timing API</a></li>
- <li>{{HTTPHeader("Vary")}}</li>
-</ul>
+- [Resource Timing API](/en-US/docs/Web/API/Resource_Timing_API)
+- [Using the Resource Timing API](/en-US/docs/Web/API/Resource_Timing_API/Using_the_Resource_Timing_API)
+- {{HTTPHeader("Vary")}}
diff --git a/files/en-us/web/http/headers/tk/index.md b/files/en-us/web/http/headers/tk/index.md
index 6bd7253b3989d77..fddf3fa984d6425 100644
--- a/files/en-us/web/http/headers/tk/index.md
+++ b/files/en-us/web/http/headers/tk/index.md
@@ -2,18 +2,18 @@
 title: Tk
 slug: Web/HTTP/Headers/Tk
 tags:
-- DNT
-- HTTP
-- Reference
-- Response
-- header
-- tracking
+  - DNT
+  - HTTP
+  - Reference
+  - Response
+  - header
+  - tracking
 browser-compat: http.headers.Tk
 ---
-<div>{{HTTPSidebar}}{{Deprecated_header}}</div>
+{{HTTPSidebar}}{{Deprecated_header}}
 
-<p>The <strong><code>Tk</code></strong> response header indicates the tracking status that
-  applied to the corresponding request.</p>
+The **`Tk`** response header indicates the tracking status that
+applied to the corresponding request.
 
 <table class="properties">
   <tbody>
@@ -28,9 +28,10 @@ browser-compat: http.headers.Tk
   </tbody>
 </table>
 
-<h2 id="Syntax">Syntax</h2>
+## Syntax
 
-<pre class="brush: html">Tk: !  (under construction)
+```html
+Tk: !  (under construction)
 Tk: ?  (dynamic)
 Tk: G  (gateway or multiple parties)
 Tk: N  (not tracking)
@@ -39,58 +40,53 @@ Tk: C  (tracking with consent)
 Tk: P  (potential consent)
 Tk: D  (disregarding DNT)
 Tk: U  (updated)
-</pre>
+```
 
-<h3 id="Directives">Directives</h3>
+### Directives
 
-<dl>
-  <dt>!</dt>
-  <dd>Under construction. The origin server is currently testing its communication of
-    tracking status.</dd>
-  <dt>?</dt>
-  <dd>Dynamic. The origin server needs more information to determine tracking status.</dd>
-  <dt>G</dt>
-  <dd>Gateway or multiple parties. The server is acting as a gateway to an exchange
-    involving multiple parties.</dd>
-  <dt>N</dt>
-  <dd>Not tracking.</dd>
-  <dt>T</dt>
-  <dd>Tracking.</dd>
-  <dt>C</dt>
-  <dd>Tracking with consent. The origin server believes it has received prior consent for
-    tracking this user, user agent, or device.</dd>
-  <dt>P</dt>
-  <dd>Potential consent. The origin server does not know, in real-time, whether it has
+- !
+  - : Under construction. The origin server is currently testing its communication of
+    tracking status.
+- ?
+  - : Dynamic. The origin server needs more information to determine tracking status.
+- G
+  - : Gateway or multiple parties. The server is acting as a gateway to an exchange
+    involving multiple parties.
+- N
+  - : Not tracking.
+- T
+  - : Tracking.
+- C
+  - : Tracking with consent. The origin server believes it has received prior consent for
+    tracking this user, user agent, or device.
+- P
+  - : Potential consent. The origin server does not know, in real-time, whether it has
     received prior consent for tracking this user, user agent, or device, but promises not
-    to use or share any <code>DNT:1</code> data until such consent has been determined,
+    to use or share any `DNT:1` data until such consent has been determined,
     and further promises to delete or permanently de-identify within 48 hours any
-    <code>DNT:1</code> data received for which such consent has not been received.</dd>
-  <dt>D</dt>
-  <dd>Disregarding DNT. The origin server is unable or unwilling to respect a tracking
-    preference received from the requesting user agent.</dd>
-  <dt>U</dt>
-  <dd>Updated. The request resulted in a potential change to the tracking status
-    applicable to this user, user agent, or device.</dd>
-</dl>
+    `DNT:1` data received for which such consent has not been received.
+- D
+  - : Disregarding DNT. The origin server is unable or unwilling to respect a tracking
+    preference received from the requesting user agent.
+- U
+  - : Updated. The request resulted in a potential change to the tracking status
+    applicable to this user, user agent, or device.
 
-<h2 id="Examples">Examples</h2>
+## Examples
 
-<p>A <code>Tk</code> header for a resource that claims not to be tracking would look like:
-</p>
+A `Tk` header for a resource that claims not to be tracking would look like:
 
-<pre>Tk: N</pre>
+    Tk: N
 
-<h2 id="Specifications">Specifications</h2>
+## Specifications
 
 {{Specifications}}
 
-<h2 id="Browser_compatibility">Browser compatibility</h2>
+## Browser compatibility
 
-<p>{{Compat}}</p>
+{{Compat}}
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
-  <li>{{HTTPHeader("DNT")}} header</li>
-  <li>{{domxref("Navigator.doNotTrack")}}</li>
-</ul>
+- {{HTTPHeader("DNT")}} header
+- {{domxref("Navigator.doNotTrack")}}
diff --git a/files/en-us/web/http/headers/trailer/index.md b/files/en-us/web/http/headers/trailer/index.md
index 5e2a616fb1586f1..8712310f804538a 100644
--- a/files/en-us/web/http/headers/trailer/index.md
+++ b/files/en-us/web/http/headers/trailer/index.md
@@ -9,23 +9,25 @@ tags:
   - Payload header
 browser-compat: http.headers.Trailer
 ---
-<div>{{HTTPSidebar}}</div>
+{{HTTPSidebar}}
 
-<p>The <strong>Trailer</strong> response header allows the sender to include additional
-  fields at the end of chunked messages in order to supply metadata that might be
-  dynamically generated while the message body is sent, such as a message integrity check,
-  digital signature, or post-processing status.</p>
+The **Trailer** response header allows the sender to include additional
+fields at the end of chunked messages in order to supply metadata that might be
+dynamically generated while the message body is sent, such as a message integrity check,
+digital signature, or post-processing status.
 
-<div class="notecard note">
-  <p><strong>Note:</strong> The {{HTTPHeader("TE")}} request header needs to be set to "trailers" to allow
-    trailer fields.</p>
-</div>
+> **Note:** The {{HTTPHeader("TE")}} request header needs to be set to "trailers" to allow
+> trailer fields.
 
 <table class="properties">
   <tbody>
     <tr>
       <th scope="row">Header type</th>
-      <td>{{Glossary("Request header")}}, {{Glossary("Response header")}}, {{Glossary("Payload header")}}</td>
+      <td>
+        {{Glossary("Request header")}},
+        {{Glossary("Response header")}},
+        {{Glossary("Payload header")}}
+      </td>
     </tr>
     <tr>
       <th scope="row">{{Glossary("Forbidden header name")}}</th>
@@ -34,69 +36,62 @@ browser-compat: http.headers.Trailer
   </tbody>
 </table>
 
-<h2 id="Syntax">Syntax</h2>
-
-<pre class="brush: html">Trailer: header-names</pre>
-
-<h2 id="Directives">Directives</h2>
-
-<dl>
-  <dt><code>header-names</code></dt>
-  <dd>HTTP header fields which will be present in the trailer part of chunked messages.
-    These header fields are <strong>disallowed</strong>:
-    <ul>
-      <li>message framing headers (e.g., {{HTTPHeader("Transfer-Encoding")}} and
-        {{HTTPHeader("Content-Length")}}),</li>
-      <li>routing headers (e.g., {{HTTPHeader("Host")}}),</li>
-      <li>request modifiers (e.g., controls and conditionals, like
-        {{HTTPHeader("Cache-Control")}}, {{HTTPHeader("Max-Forwards")}}, or
-        {{HTTPHeader("TE")}}), </li>
-      <li>authentication headers (e.g., {{HTTPHeader("Authorization")}} or
-        {{HTTPHeader("Set-Cookie")}}),</li>
-      <li>or {{HTTPHeader("Content-Encoding")}}, {{HTTPHeader("Content-Type")}},
-        {{HTTPHeader("Content-Range")}}, and <code>Trailer</code> itself.</li>
-    </ul>
-  </dd>
-</dl>
-
-<h2 id="Examples">Examples</h2>
-
-<h3 id="Chunked_transfer_encoding_using_a_trailing_header">Chunked transfer encoding using
-  a trailing header</h3>
-
-<p>In this example, the {{HTTPHeader("Expires")}} header is used at the end of the chunked
-  message and serves as a trailing header.</p>
-
-<pre>HTTP/1.1 200 OK
-Content-Type: text/plain
-Transfer-Encoding: chunked
-Trailer: Expires
-
-7\r\n
-Mozilla\r\n
-9\r\n
-Developer\r\n
-7\r\n
-Network\r\n
-0\r\n
-Expires: Wed, 21 Oct 2015 07:28:00 GMT\r\n
-\r\n
-</pre>
-
-<h2 id="Specifications">Specifications</h2>
+## Syntax
+
+```html
+Trailer: header-names
+```
+
+## Directives
+
+- `header-names`
+
+  - : HTTP header fields which will be present in the trailer part of chunked messages.
+    These header fields are **disallowed**:
+
+    - message framing headers (e.g., {{HTTPHeader("Transfer-Encoding")}} and
+      {{HTTPHeader("Content-Length")}}),
+    - routing headers (e.g., {{HTTPHeader("Host")}}),
+    - request modifiers (e.g., controls and conditionals, like
+      {{HTTPHeader("Cache-Control")}}, {{HTTPHeader("Max-Forwards")}}, or
+      {{HTTPHeader("TE")}}),
+    - authentication headers (e.g., {{HTTPHeader("Authorization")}} or
+      {{HTTPHeader("Set-Cookie")}}),
+    - or {{HTTPHeader("Content-Encoding")}}, {{HTTPHeader("Content-Type")}},
+      {{HTTPHeader("Content-Range")}}, and `Trailer` itself.
+
+## Examples
+
+### Chunked transfer encoding using a trailing header
+
+In this example, the {{HTTPHeader("Expires")}} header is used at the end of the chunked
+message and serves as a trailing header.
+
+    HTTP/1.1 200 OK
+    Content-Type: text/plain
+    Transfer-Encoding: chunked
+    Trailer: Expires
+
+    7\r\n
+    Mozilla\r\n
+    9\r\n
+    Developer\r\n
+    7\r\n
+    Network\r\n
+    0\r\n
+    Expires: Wed, 21 Oct 2015 07:28:00 GMT\r\n
+    \r\n
+
+## Specifications
 
 {{Specifications}}
 
-<h2 id="Browser_compatibility">Browser compatibility</h2>
+## Browser compatibility
 
-<p>{{Compat}}</p>
+{{Compat}}
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
-  <li>{{HTTPHeader("Transfer-Encoding")}}</li>
-  <li>{{HTTPHeader("TE")}}</li>
-  <li>
-    <p><a href="https://en.wikipedia.org/wiki/Chunked_transfer_encoding">Chunked transfer encoding</a></p>
-  </li>
-</ul>
+- {{HTTPHeader("Transfer-Encoding")}}
+- {{HTTPHeader("TE")}}
+- [Chunked transfer encoding](https://en.wikipedia.org/wiki/Chunked_transfer_encoding)
diff --git a/files/en-us/web/http/headers/transfer-encoding/index.md b/files/en-us/web/http/headers/transfer-encoding/index.md
index 904eb0e70ff519c..c10ea945742e659 100644
--- a/files/en-us/web/http/headers/transfer-encoding/index.md
+++ b/files/en-us/web/http/headers/transfer-encoding/index.md
@@ -10,34 +10,35 @@ tags:
   - Payload header
 browser-compat: http.headers.Transfer-Encoding
 ---
-<div>{{HTTPSidebar}}</div>
+{{HTTPSidebar}}
 
-<p>The <strong><code>Transfer-Encoding</code></strong> header specifies the form of
-  encoding used to safely transfer the {{Glossary("Payload body","payload body")}} to the
-  user.</p>
+The **`Transfer-Encoding`** header specifies the form of
+encoding used to safely transfer the {{Glossary("Payload body","payload body")}} to the
+user.
 
-<div class="notecard note">
-  <p><strong>Note:</strong> <a href="https://wikipedia.org/wiki/HTTP/2">HTTP/2</a> doesn't support
-    HTTP 1.1's chunked transfer encoding mechanism, as it provides its own, more efficient,
-    mechanisms for data streaming.</p>
-</div>
+> **Note:** [HTTP/2](https://wikipedia.org/wiki/HTTP/2) doesn't support
+> HTTP 1.1's chunked transfer encoding mechanism, as it provides its own, more efficient,
+> mechanisms for data streaming.
 
-<p><code>Transfer-Encoding</code> is a <a
-    href="/en-US/docs/Web/HTTP/Headers#hbh">hop-by-hop header</a>, that is applied to a
-  message between two nodes, not to a resource itself. Each segment of a multi-node
-  connection can use different <code>Transfer-Encoding</code> values. If you want to
-  compress data over the whole connection, use the end-to-end
-  {{HTTPHeader("Content-Encoding")}} header instead.</p>
+`Transfer-Encoding` is a [hop-by-hop header](/en-US/docs/Web/HTTP/Headers#hbh), that is applied to a
+message between two nodes, not to a resource itself. Each segment of a multi-node
+connection can use different `Transfer-Encoding` values. If you want to
+compress data over the whole connection, use the end-to-end
+{{HTTPHeader("Content-Encoding")}} header instead.
 
-<p>When present on a response to a {{HTTPMethod("HEAD")}} request that has no body, it
-  indicates the value that would have applied to the corresponding {{HTTPMethod("GET")}}
-  message.</p>
+When present on a response to a {{HTTPMethod("HEAD")}} request that has no body, it
+indicates the value that would have applied to the corresponding {{HTTPMethod("GET")}}
+message.
 
 <table class="properties">
   <tbody>
     <tr>
       <th scope="row">Header type</th>
-      <td>{{Glossary("Request header")}}, {{Glossary("Response header")}}, {{Glossary("Payload header")}}</td>
+      <td>
+        {{Glossary("Request header")}},
+        {{Glossary("Response header")}},
+        {{Glossary("Payload header")}}
+      </td>
     </tr>
     <tr>
       <th scope="row">{{Glossary("Forbidden header name")}}</th>
@@ -46,90 +47,85 @@ browser-compat: http.headers.Transfer-Encoding
   </tbody>
 </table>
 
-<h2 id="Syntax">Syntax</h2>
+## Syntax
 
-<pre class="brush: html">Transfer-Encoding: chunked
+```html
+Transfer-Encoding: chunked
 Transfer-Encoding: compress
 Transfer-Encoding: deflate
 Transfer-Encoding: gzip
 Transfer-Encoding: identity
 
-<em>// Several values can be listed, separated by a comma</em>
-Transfer-Encoding: gzip, chunked</pre>
+// Several values can be listed, separated by a comma
+Transfer-Encoding: gzip, chunked
+```
 
-<h2 id="Directives">Directives</h2>
+## Directives
 
-<dl>
-  <dt><code>chunked</code></dt>
-  <dd>Data is sent in a series of chunks. The {{HTTPHeader("Content-Length")}} header is
+- `chunked`
+  - : Data is sent in a series of chunks. The {{HTTPHeader("Content-Length")}} header is
     omitted in this case and at the beginning of each chunk you need to add the length of
-    the current chunk in hexadecimal format, followed by '<code>\r\n</code>' and then the
-    chunk itself, followed by another '<code>\r\n</code>'. The terminating chunk is a
+    the current chunk in hexadecimal format, followed by '`\r\n`' and then the
+    chunk itself, followed by another '`\r\n`'. The terminating chunk is a
     regular chunk, with the exception that its length is zero. It is followed by the
-    trailer, which consists of a (possibly empty) sequence of header fields. </dd>
-  <dt><code>compress</code></dt>
-  <dd>A format using the <a href="https://en.wikipedia.org/wiki/LZW">Lempel-Ziv-Welch</a> (LZW) algorithm. The
-    value name was taken from the UNIX <em>compress</em> program, which implemented this
-    algorithm.<br>
+    trailer, which consists of a (possibly empty) sequence of header fields.
+- `compress`
+  - : A format using the [Lempel-Ziv-Welch](https://en.wikipedia.org/wiki/LZW) (LZW) algorithm. The
+    value name was taken from the UNIX _compress_ program, which implemented this
+    algorithm.
     Like the compress program, which has disappeared from most UNIX distributions, this
     content-encoding is used by almost no browsers today, partly because of a patent issue
-    (which expired in 2003).</dd>
-  <dt><code>deflate</code></dt>
-  <dd>Using the <a href="https://en.wikipedia.org/wiki/Zlib">zlib</a>
-    structure (defined in <a href="https://datatracker.ietf.org/doc/html/rfc1950">RFC 1950</a>), with the <a
-      href="https://en.wikipedia.org/wiki/DEFLATE"><em>deflate</em></a>
-    compression algorithm (defined in <a href="https://datatracker.ietf.org/doc/html/rfc1952">RFC 1951</a>).</dd>
-  <dt><code>gzip</code></dt>
-  <dd>A format using the <a       href="https://en.wikipedia.org/wiki/LZ77_and_LZ78#LZ77">Lempel-Ziv coding</a>
-    (LZ77), with a 32-bit CRC. This is originally the format of the UNIX <em>gzip</em>
+    (which expired in 2003).
+- `deflate`
+  - : Using the [zlib](https://en.wikipedia.org/wiki/Zlib)
+    structure (defined in [RFC 1950](https://datatracker.ietf.org/doc/html/rfc1950)), with the [_deflate_](https://en.wikipedia.org/wiki/DEFLATE)
+    compression algorithm (defined in [RFC 1951](https://datatracker.ietf.org/doc/html/rfc1952)).
+- `gzip`
+  - : A format using the [Lempel-Ziv coding](https://en.wikipedia.org/wiki/LZ77_and_LZ78#LZ77)
+    (LZ77), with a 32-bit CRC. This is originally the format of the UNIX _gzip_
     program. The HTTP/1.1 standard also recommends that the servers supporting this
-    content-encoding should recognize <code>x-gzip</code> as an alias, for compatibility
-    purposes.</dd>
-  <dt><code>identity</code></dt>
-  <dd>Indicates the identity function (i.e. no compression, nor modification). This token,
-    except if explicitly specified, is always deemed acceptable.</dd>
-</dl>
+    content-encoding should recognize `x-gzip` as an alias, for compatibility
+    purposes.
+- `identity`
+  - : Indicates the identity function (i.e. no compression, nor modification). This token,
+    except if explicitly specified, is always deemed acceptable.
 
-<h2 id="Examples">Examples</h2>
+## Examples
 
-<h3 id="Chunked_encoding">Chunked encoding</h3>
+### Chunked encoding
 
-<p>Chunked encoding is useful when larger amounts of data are sent to the client and the
-  total size of the response may not be known until the request has been fully processed.
-  For example, when generating a large HTML table resulting from a database query or when
-  transmitting large images. A chunked response looks like this:</p>
+Chunked encoding is useful when larger amounts of data are sent to the client and the
+total size of the response may not be known until the request has been fully processed.
+For example, when generating a large HTML table resulting from a database query or when
+transmitting large images. A chunked response looks like this:
 
-<pre>HTTP/1.1 200 OK
-Content-Type: text/plain
-Transfer-Encoding: chunked
+    HTTP/1.1 200 OK
+    Content-Type: text/plain
+    Transfer-Encoding: chunked
 
-7\r\n
-Mozilla\r\n
-9\r\n
-Developer\r\n
-7\r\n
-Network\r\n
-0\r\n
-\r\n</pre>
+    7\r\n
+    Mozilla\r\n
+    9\r\n
+    Developer\r\n
+    7\r\n
+    Network\r\n
+    0\r\n
+    \r\n
 
-<h2 id="Specifications">Specifications</h2>
+## Specifications
 
 {{Specifications}}
 
-<h2 id="Browser_compatibility">Browser compatibility</h2>
+## Browser compatibility
 
-<p>{{Compat}}</p>
+{{Compat}}
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
-  <li>{{HTTPHeader("Accept-Encoding")}}</li>
-  <li>{{HTTPHeader("Content-Encoding")}}</li>
-  <li>{{HTTPHeader("Content-Length")}}</li>
-  <li>Header fields that regulate the use of trailers: {{HTTPHeader("TE")}} (requests) and
-    {{HTTPHeader("Trailer")}} (responses).</li>
-  <li>
-    <p><a href="https://en.wikipedia.org/wiki/Chunked_transfer_encoding">Chunked transfer
-        encoding</a></p>
-  </li>
-</ul>
+- {{HTTPHeader("Accept-Encoding")}}
+- {{HTTPHeader("Content-Encoding")}}
+- {{HTTPHeader("Content-Length")}}
+- Header fields that regulate the use of trailers: {{HTTPHeader("TE")}} (requests) and
+  {{HTTPHeader("Trailer")}} (responses).
+- [Chunked transfer
+  encoding](https://en.wikipedia.org/wiki/Chunked_transfer_encoding)
diff --git a/files/en-us/web/http/headers/upgrade-insecure-requests/index.md b/files/en-us/web/http/headers/upgrade-insecure-requests/index.md
index a3232528fd4cacc..37f16634aceedf7 100644
--- a/files/en-us/web/http/headers/upgrade-insecure-requests/index.md
+++ b/files/en-us/web/http/headers/upgrade-insecure-requests/index.md
@@ -8,51 +8,51 @@ tags:
   - header
 browser-compat: http.headers.Upgrade-Insecure-Requests
 ---
-<div>{{HTTPSidebar}}</div>
+{{HTTPSidebar}}
 
-<p>The HTTP <strong><code>Upgrade-Insecure-Requests</code></strong> request header sends a signal to the server expressing the client’s preference for an encrypted and authenticated response, and that it can successfully handle the {{CSP("upgrade-insecure-requests")}} <a href="/en-US/docs/Web/HTTP/CSP">CSP</a> directive.</p>
+The HTTP **`Upgrade-Insecure-Requests`** request header sends a signal to the server expressing the client’s preference for an encrypted and authenticated response, and that it can successfully handle the {{CSP("upgrade-insecure-requests")}} [CSP](/en-US/docs/Web/HTTP/CSP) directive.
 
 <table class="properties">
- <tbody>
-  <tr>
-   <th scope="row">Header type</th>
-   <td>{{Glossary("Request header")}}</td>
-  </tr>
-  <tr>
-   <th scope="row">{{Glossary("Forbidden header name")}}</th>
-   <td>no</td>
-  </tr>
- </tbody>
+  <tbody>
+    <tr>
+      <th scope="row">Header type</th>
+      <td>{{Glossary("Request header")}}</td>
+    </tr>
+    <tr>
+      <th scope="row">{{Glossary("Forbidden header name")}}</th>
+      <td>no</td>
+    </tr>
+  </tbody>
 </table>
 
-<h2 id="Syntax">Syntax</h2>
+## Syntax
 
-<pre class="brush: html">Upgrade-Insecure-Requests: 1</pre>
+```html
+Upgrade-Insecure-Requests: 1
+```
 
-<h2 id="Examples">Examples</h2>
+## Examples
 
-<p>A client's request signals to the server that it supports the upgrade mechanisms of {{CSP("upgrade-insecure-requests")}}:</p>
+A client's request signals to the server that it supports the upgrade mechanisms of {{CSP("upgrade-insecure-requests")}}:
 
-<pre>GET / HTTP/1.1
-Host: example.com
-Upgrade-Insecure-Requests: 1</pre>
+    GET / HTTP/1.1
+    Host: example.com
+    Upgrade-Insecure-Requests: 1
 
-<p>The server can now redirect to a secure version of the site. A {{HTTPHeader("Vary")}} header can be used so that the site isn't served by caches to clients that don’t support the upgrade mechanism.</p>
+The server can now redirect to a secure version of the site. A {{HTTPHeader("Vary")}} header can be used so that the site isn't served by caches to clients that don’t support the upgrade mechanism.
 
-<pre>Location: https://example.com/
-Vary: Upgrade-Insecure-Requests</pre>
+    Location: https://example.com/
+    Vary: Upgrade-Insecure-Requests
 
-<h2 id="Specifications">Specifications</h2>
+## Specifications
 
 {{Specifications}}
 
-<h2 id="Browser_compatibility">Browser compatibility</h2>
+## Browser compatibility
 
-<p>{{Compat}}</p>
+{{Compat}}
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
- <li>{{HTTPHeader("Content-Security-Policy")}}</li>
- <li>CSP {{CSP("upgrade-insecure-requests")}} directive</li>
-</ul>
+- {{HTTPHeader("Content-Security-Policy")}}
+- CSP {{CSP("upgrade-insecure-requests")}} directive
diff --git a/files/en-us/web/http/headers/upgrade/index.md b/files/en-us/web/http/headers/upgrade/index.md
index aff0c375b74eff5..a2c28aed398e203 100644
--- a/files/en-us/web/http/headers/upgrade/index.md
+++ b/files/en-us/web/http/headers/upgrade/index.md
@@ -9,107 +9,96 @@ tags:
   - Upgrade
 browser-compat: http.headers.Upgrade
 ---
-<p>{{HTTPSidebar}}</p>
+{{HTTPSidebar}}
 
-<p>The HTTP 1.1 (only) <code>Upgrade</code> header can be used to upgrade an already established client/server connection to a different protocol (over the same transport protocol). For example, it can be used by a client to upgrade a connection from HTTP 1.1 to HTTP 2.0, or an HTTP or HTTPS connection into a WebSocket.</p>
+The HTTP 1.1 (only) `Upgrade` header can be used to upgrade an already established client/server connection to a different protocol (over the same transport protocol). For example, it can be used by a client to upgrade a connection from HTTP 1.1 to HTTP 2.0, or an HTTP or HTTPS connection into a WebSocket.
 
-<div class="notecard warning">
-  <p><strong>Warning:</strong> HTTP/2 explicitly disallows the use of this mechanism/header; it is specific to HTTP/1.1.</p>
-</div>
+> **Warning:** HTTP/2 explicitly disallows the use of this mechanism/header; it is specific to HTTP/1.1.
 
 <table class="properties">
-	<tbody>
-		<tr>
-			<th scope="row">Header type</th>
-			<td>{{Glossary("Request header")}}, {{Glossary("Response header")}}</td>
-		</tr>
-		<tr>
-			<th scope="row">{{Glossary("Forbidden header name")}}</th>
-			<td>yes</td>
-		</tr>
-	</tbody>
+  <tbody>
+    <tr>
+      <th scope="row">Header type</th>
+      <td>
+        {{Glossary("Request header")}},
+        {{Glossary("Response header")}}
+      </td>
+    </tr>
+    <tr>
+      <th scope="row">{{Glossary("Forbidden header name")}}</th>
+      <td>yes</td>
+    </tr>
+  </tbody>
 </table>
 
-<h2 id="Overview">Overview</h2>
+## Overview
 
-<p>The <code>Upgrade</code> header field may be used by clients to invite a server to switch to one (or more) of the listed protocols, in descending preference order.</p>
+The `Upgrade` header field may be used by clients to invite a server to switch to one (or more) of the listed protocols, in descending preference order.
 
-<p>For example, the client might send a <code>GET</code> request as shown, listing the preferred protocols to switch to (in this case "example/1" and "foo/2"):</p>
+For example, the client might send a `GET` request as shown, listing the preferred protocols to switch to (in this case "example/1" and "foo/2"):
 
-<pre>GET /index.html HTTP/1.1
-Host: www.example.com
-Connection: upgrade
-Upgrade: example/1, foo/2</pre>
+    GET /index.html HTTP/1.1
+    Host: www.example.com
+    Connection: upgrade
+    Upgrade: example/1, foo/2
 
-<div class="notecard note">
-  <p><strong>Note:</strong> <code>Connection: upgrade</code> must be set whenever <code>Upgrade</code> is sent.</p>
-</div>
+> **Note:** `Connection: upgrade` must be set whenever `Upgrade` is sent.
 
-<p>The server can choose to ignore the request, for any reason, in which case it should just respond as though the <code>Upgrade</code> header had not been sent (for example, with a  {{HTTPStatus(200, "200 OK")}}).</p>
+The server can choose to ignore the request, for any reason, in which case it should just respond as though the `Upgrade` header had not been sent (for example, with a  {{HTTPStatus(200, "200 OK")}}).
 
-<p>If the server decides to upgrade the connection, it must:</p>
+If the server decides to upgrade the connection, it must:
 
-<ol>
-	<li>Send back a {{HTTPStatus(101, "101 Switching Protocols")}} response status with an <code>Upgrade</code> header that specifies the protocol(s) being switched to. For example:
+1.  Send back a {{HTTPStatus(101, "101 Switching Protocols")}} response status with an `Upgrade` header that specifies the protocol(s) being switched to. For example:
 
-	<pre><code>HTTP/1.1 101 Switching Protocols
-Upgrade: foo/2
-Connection: Upgrade</code></pre>
-	</li>
-	<li>Send a response to the original request <em>using the new protocol</em> (the server may only switch to a protocol with which it can complete the original request).</li>
-</ol>
+        HTTP/1.1 101 Switching Protocols
+        Upgrade: foo/2
+        Connection: Upgrade
 
-<p>A server may also send the header as part of a {{HTTPStatus("426")}} <code>Upgrade Required</code> response, to indicate that the server won't perform the request using the current protocol, but might do so if the protocol is changed. The client can then request a protocol change using the process above.</p>
+2.  Send a response to the original request *using the new protocol* (the server may only switch to a protocol with which it can complete the original request).
 
-<p>More detail and examples are provided in the topic <a href="/en-US/docs/Web/HTTP/Protocol_upgrade_mechanism">Protocol upgrade mechanism</a>.</p>
+A server may also send the header as part of a {{HTTPStatus("426")}} `Upgrade Required` response, to indicate that the server won't perform the request using the current protocol, but might do so if the protocol is changed. The client can then request a protocol change using the process above.
 
-<h2 id="Syntax">Syntax</h2>
+More detail and examples are provided in the topic [Protocol upgrade mechanism](/en-US/docs/Web/HTTP/Protocol_upgrade_mechanism).
 
-<pre>Connection: upgrade
-Upgrade: <em>protocol_name</em>[<strong>/</strong><em>protocol_version</em>]
-</pre>
+## Syntax
 
-<p>Notes:</p>
+    Connection: upgrade
+    Upgrade: protocol_name[/protocol_version]
 
-<ul>
-	<li>The {{HTTPHeader("Connection")}} header with type <code>upgrade</code> must <em>always</em> be sent with the <code>Upgrade</code> header (as shown above).</li>
-	<li>Protocols are listed, comma-separated, in order of descending preference. Protocol version is optional. For example:
-	<pre>  Connection: upgrade
-  Upgrade: a_protocol/1, example ,another_protocol/2.2
-</pre>
-	</li>
-</ul>
+Notes:
 
-<h2 id="Directives">Directives</h2>
+- The {{HTTPHeader("Connection")}} header with type `upgrade` must _always_ be sent with the `Upgrade` header (as shown above).
+- Protocols are listed, comma-separated, in order of descending preference. Protocol version is optional. For example:
 
-<dl>
-	<dt>any comma-separated list protocol names (each with optional protocol version)</dt>
-	<dd>One or more protocol names with optional version ("/" separated). The protocols are listed in order of descending preference.</dd>
-</dl>
+        Connection: upgrade
+        Upgrade: a_protocol/1, example ,another_protocol/2.2
 
-<h2 id="Examples">Examples</h2>
+## Directives
 
-<pre>Connection: upgrade
-Upgrade: HTTP/2.0, SHTTP/1.3, IRC/6.9, RTA/x11
-</pre>
+- any comma-separated list protocol names (each with optional protocol version)
+  - : One or more protocol names with optional version ("/" separated). The protocols are listed in order of descending preference.
 
-<pre>Connection: Upgrade
-Upgrade: websocket
-</pre>
+## Examples
 
-<h2 id="Specifications">Specifications</h2>
+    Connection: upgrade
+    Upgrade: HTTP/2.0, SHTTP/1.3, IRC/6.9, RTA/x11
+
+<!---->
+
+    Connection: Upgrade
+    Upgrade: websocket
+
+## Specifications
 
 {{Specifications}}
 
-<h2 id="Browser_compatibility">Browser compatibility</h2>
+## Browser compatibility
 
-<p>{{Compat}}</p>
+{{Compat}}
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
-	<li><a href="/en-US/docs/Web/HTTP/Protocol_upgrade_mechanism">Protocol upgrade mechanism</a></li>
-	<li>{{HTTPStatus("101")}} <code>Switching Protocol</code></li>
-	<li>{{HTTPStatus("426")}} <code>Upgrade Required</code></li>
-	<li>{{HTTPHeader("Connection")}}</li>
-</ul>
+- [Protocol upgrade mechanism](/en-US/docs/Web/HTTP/Protocol_upgrade_mechanism)
+- {{HTTPStatus("101")}} `Switching Protocol`
+- {{HTTPStatus("426")}} `Upgrade Required`
+- {{HTTPHeader("Connection")}}
diff --git a/files/en-us/web/http/headers/user-agent/firefox/index.md b/files/en-us/web/http/headers/user-agent/firefox/index.md
index f23d5f768cf4ed3..3227da3eac231c9 100644
--- a/files/en-us/web/http/headers/user-agent/firefox/index.md
+++ b/files/en-us/web/http/headers/user-agent/firefox/index.md
@@ -9,459 +9,227 @@ tags:
   - Gecko 2.0
   - Guide
 ---
-<div>{{HTTPSidebar}}</div>
-
-<p>This document describes the user agent string used in Firefox 4 and later and applications based on Gecko 2.0 and later. For a breakdown of changes to the string in Gecko 2.0, see <a href="https://hacks.mozilla.org/2010/09/final-user-agent-string-for-firefox-4/">Final User Agent string for Firefox 4</a> (blog post). See also this document on <a href="/en-US/docs/Web/HTTP/Browser_detection_using_the_user_agent">user agent sniffing</a> and this <a href="https://hacks.mozilla.org/2013/09/user-agent-detection-history-and-checklist/">Hacks blog post</a>.</p>
-
-<h2 id="General_form">General form</h2>
-
-<p>The UA string of Firefox itself is broken down into four components:</p>
-
-<p><code>Mozilla/5.0 (<var>platform</var>; rv:<var>geckoversion</var>) Gecko/<var>geckotrail</var> Firefox/<var>firefoxversion</var></code></p>
-
-<ul>
- <li><code>Mozilla/5.0</code> is the general token that says the browser is Mozilla compatible, and is common to almost every browser today.</li>
- <li>
-  <p><code><var>platform</var></code> describes the native platform the browser is running on (e.g. Windows, Mac, Linux or Android), and whether or not it's a mobile phone. Firefox OS phones say "<code>Mobile</code>"; the web is the platform. Note that <code><var>platform</var></code> can consist of multiple "; "-separated tokens. See below for further details and examples.</p>
-
-  <div class="notecard note">
-    <p><strong>Note:</strong> Though fixed in Firefox 69, previous 32-bit versions of Firefox running on 64-bit processors would report that the system is using a 32-bit CPU.</p>
-  </div>
- </li>
- <li><code>rv:<var>geckoversion</var></code> indicates the release version of Gecko (such as "<code>17.0</code>"). In recent browsers, <code><var>geckoversion</var></code> is the same as <code><var>firefoxversion</var></code>.</li>
- <li><code>Gecko/<var>geckotrail</var></code> indicates that the browser is based on Gecko.</li>
- <li>On Desktop, <code><var>geckotrail</var></code> is the fixed string "<code>20100101</code>"</li>
- <li><code>Firefox/<var>firefoxversion</var></code> indicates the browser is Firefox, and provides the version (such as "<code>17.0</code>").</li>
- <li>From Firefox 10 on mobile, <code><var>geckotrail</var></code> is the same as <code><var>firefoxversion</var></code>.</li>
-</ul>
-
-<div class="notecard note">
-  <p><strong>Note:</strong> The recommended way of sniffing for Gecko-based browsers (if you <em>have to</em> sniff for the browser engine instead of using feature detection) is by the presence of the "<code>Gecko</code>" and "<code>rv:</code>" strings, since some other browsers include a "<code>like Gecko</code>" token.</p>
-</div>
-
-<p>For other products based on Gecko, the string can take one of two forms, where the tokens have the same meaning except those noted below:</p>
-
-<p><code>Mozilla/5.0 (<var>platform</var>; rv:<var>geckoversion</var>) Gecko/<var>geckotrail</var> <var>appname</var>/<var>appversion</var></code><br>
- <code>Mozilla/5.0 (<var>platform</var>; rv:<var>geckoversion</var>) Gecko/<var>geckotrail</var> Firefox/<var>firefoxversion</var> <var>appname</var>/<var>appversion</var></code></p>
-
-<ul>
- <li><code><var>appname</var>/<var>appversion</var></code> indicates the application name and version. For instance, this could be "<code>Camino/2.1.1</code>", or "<code>SeaMonkey/2.7.1</code>".</li>
- <li>
-  <p><code>Firefox/<var>firefoxversion</var></code> is an optional compatibility token that some Gecko-based browsers may choose to incorporate, to achieve maximum compatibility with websites that expect Firefox. <code><var>firefoxversion</var></code> will generally represent the equivalent Firefox release corresponding to the given Gecko version. Some Gecko-based browsers may not opt into using this token; for this reason, sniffers should be looking for Gecko — not Firefox! Whether this token appears is controlled by the <em>"general.useragent.compatMode.firefox"</em> boolean pref.</p>
- </li>
-</ul>
-
-<h2 id="Mobile_and_Tablet_indicators">Mobile and Tablet indicators</h2>
-
-<div class="notecard note">
-  <p><strong>Note:</strong> Only from Firefox 11 to 68.</p>
-</div>
-
-<p>The <code><var>platform</var></code> part of the UA string indicates if Firefox is running on a phone-sized or tablet device. When Firefox runs on a device that has the phone form factor, there is a <code>Mobile;</code> token in the <code><var>platform</var></code> part of the UA string. When Firefox runs on a tablet device, there is a <code>Tablet;</code> token in the <code><var>platform</var></code> part of the UA string instead. For example:</p>
-
-<pre>Mozilla/5.0 (Android 4.4; <strong>Mobile</strong>; rv:41.0) Gecko/41.0 Firefox/41.0
-Mozilla/5.0 (Android 4.4; <strong>Tablet</strong>; rv:41.0) Gecko/41.0 Firefox/41.0</pre>
-
-<div class="notecard note">
-  <p><strong>Note:</strong> The version numbers are not relevant. Avoid inferring materials based on these.</p>
-</div>
-
-<p>The preferred way to target content to a device form factor is to use CSS Media Queries. However, if you use UA sniffing to target content to a device form factor, please look for <strong>Mobi</strong> (to include Opera Mobile, which uses "Mobi") for the phone form factor and do <strong>not</strong> assume any correlation between "Android" and the device form factor. This way, your code will work if/when Firefox ships on other phone/tablet operating systems or Android is used for laptops. Also, please use touch detection to find touch devices rather than looking for "Mobi" or "Tablet", since there may be touch devices which are not tablets.</p>
-
-<div class="notecard note">
-  <p><strong>Note:</strong> Firefox OS devices identify themselves without any operating system indication; for example: "Mozilla/5.0 (Mobile; rv:15.0) Gecko/15.0 Firefox/15.0". The web is the platform.</p>
-</div>
-
-<h2 id="Windows">Windows</h2>
-
-<p>Windows user agents have the following variations, where <em>x.y</em> is the Windows NT version (for instance, Windows NT 6.1).</p>
-
-<table>
- <thead>
-  <tr>
-   <th>Windows version</th>
-   <th>Gecko user agent string</th>
-  </tr>
- </thead>
- <tbody>
-  <tr>
-   <td>Windows NT on x86 or aarch64 CPU</td>
-   <td>Mozilla/5.0 (Windows NT <em>x</em>.<em>y</em>; rv:10.0) Gecko/20100101 Firefox/10.0</td>
-  </tr>
-  <tr>
-   <td>Windows NT on x64 CPU</td>
-   <td>Mozilla/5.0 (Windows NT <em>x</em>.<em>y</em>; Win64; x64; rv:10.0) Gecko/20100101 Firefox/10.0</td>
-  </tr>
- </tbody>
-</table>
-
-<h2 id="Macintosh">Macintosh</h2>
-
-<p>Here, <em>x.y</em> is the version of Mac OS X (for instance, Mac OS X 10.15). Starting in Firefox 87, Firefox caps the reported Mac OS X version number to 10.15, so macOS 11.0 Big Sur and later will be reported as "10.15" in the User-Agent string.</p>
-
-<p>Note that <a href="https://support.mozilla.org/kb/firefox-no-longer-works-mac-os-10-4-or-powerpc">Firefox no longer officially supports Mac OS X on PowerPC</a>.</p>
-
-<table>
- <thead>
-  <tr>
-   <th>Mac OS X version</th>
-   <th>Gecko user agent string</th>
-  </tr>
- </thead>
- <tbody>
-  <tr>
-   <td>Mac OS X on x86, x86_64, or aarch64</td>
-   <td>Mozilla/5.0 (Macintosh; Intel Mac OS X <em>x.y</em>; rv:10.0) Gecko/20100101 Firefox/10.0</td>
-  </tr>
-  <tr>
-   <td>Mac OS X on PowerPC</td>
-   <td>Mozilla/5.0 (Macintosh; PPC Mac OS X <em>x.y</em>; rv:10.0) Gecko/20100101 Firefox/10.0</td>
-  </tr>
- </tbody>
-</table>
-
-<h2 id="Linux">Linux</h2>
-
-<p>Linux is a more diverse platform. Your distribution of Linux might include an extension that changes your user-agent. A few common examples are given below.</p>
-
-<table>
- <thead>
-  <tr>
-   <th>Linux version</th>
-   <th>Gecko user agent string</th>
-  </tr>
- </thead>
- <tbody>
-  <tr>
-   <td>Linux desktop on i686 CPU</td>
-   <td>Mozilla/5.0 (X11; Linux i686; rv:10.0) Gecko/20100101 Firefox/10.0</td>
-  </tr>
-  <tr>
-   <td>Linux desktop on x86_64 CPU</td>
-   <td>Mozilla/5.0 (X11; Linux x86_64; rv:10.0) Gecko/20100101 Firefox/10.0</td>
-  </tr>
-  <tr>
-   <td>Nokia N900 Linux mobile, on the Fennec browser</td>
-   <td>Mozilla/5.0 (Maemo; Linux armv7l; rv:10.0) Gecko/20100101 Firefox/10.0 Fennec/10.0</td>
-  </tr>
- </tbody>
-</table>
-
-<h2 id="Android_version_40_and_below">Android (version 40 and below)</h2>
-
-<table>
- <thead>
-  <tr>
-   <th>Form factor</th>
-   <th>Gecko user agent string</th>
-  </tr>
- </thead>
- <tbody>
-  <tr>
-   <td>Phone</td>
-   <td>Mozilla/5.0 (Android; Mobile; rv:40.0) Gecko/40.0 Firefox/40.0</td>
-  </tr>
-  <tr>
-   <td>Tablet</td>
-   <td>Mozilla/5.0 (Android; Tablet; rv:40.0) Gecko/40.0 Firefox/40.0</td>
-  </tr>
- </tbody>
-</table>
-
-<h2 id="Android_version_41_and_above">Android (version 41 and above)</h2>
-
-<p>Beginning in version 41, Firefox for Android will contain the Android version as part of the <var>platform</var> token. For increased interoperability, if the browser is running on a version below 4 it will report 4.4. Android versions 4 and above will report the version accurately. Note that the same Gecko—with the same capabilities—is shipped to all versions of Android.</p>
-
-<table>
- <thead>
-  <tr>
-   <th>Form factor</th>
-   <th>Gecko user agent string</th>
-  </tr>
- </thead>
- <tbody>
-  <tr>
-   <td>Phone</td>
-   <td>Mozilla/5.0 (Android 4.4; Mobile; rv:41.0) Gecko/41.0 Firefox/41.0</td>
-  </tr>
-  <tr>
-   <td>Tablet</td>
-   <td>Mozilla/5.0 (Android 4.4; Tablet; rv:41.0) Gecko/41.0 Firefox/41.0</td>
-  </tr>
- </tbody>
-</table>
-
-<h2 id="Focus_for_Android">Focus for Android</h2>
-
-<p>From version 1, Focus is powered by Android WebView and uses the following user agent string format:</p>
-
-<pre>Mozilla/5.0 (Linux; &lt;Android Version&gt; &lt;Build Tag etc.&gt;) AppleWebKit/&lt;WebKit Rev&gt; (KHTML, like Gecko) Version/4.0 Focus/&lt;focusversion&gt; Chrome/&lt;Chrome Rev&gt; Mobile Safari/&lt;WebKit Rev&gt;</pre>
-
-<p>Tablet versions on WebView mirror mobile, but do not contain a <code>Mobile</code> token.</p>
-
-<p>Starting in Version 6, users can opt into using a GeckoView-based Focus for Android with a hidden preference: it uses a GeckoView UA string to advertise Gecko compatibility.</p>
-
-<table>
- <tbody>
-  <tr>
-   <th>Focus Version (Rendering Engine)</th>
-   <th>User Agent string</th>
-  </tr>
-  <tr>
-   <td>1.0 (WebView Mobile)</td>
-   <td>Mozilla/5.0 (Linux; Android 7.0) AppleWebKit/537.36 (KHTML, like Gecko) Version/4.0 Focus/1.0 Chrome/59.0.3029.83 Mobile Safari/537.36</td>
-  </tr>
-  <tr>
-   <td>1.0 (WebView Tablet)</td>
-   <td>Mozilla/5.0 (Linux; Android 7.0) AppleWebKit/537.36 (KHTML, like Gecko) Version/4.0 Focus/1.0 Chrome/59.0.3029.83 Safari/537.36</td>
-  </tr>
-  <tr>
-   <td>6.0 (GeckoView)</td>
-   <td>Mozilla/5.0 (Android 7.0; Mobile; rv:62.0) Gecko/62.0 Firefox/62.0</td>
-  </tr>
- </tbody>
-</table>
-
-<h2 id="Klar_for_Android">Klar for Android</h2>
-
-<p>Since version 4.1, Klar for Android uses the same UA string as <a href="#focus_for_android">Focus for Android</a>. Before version 4.1, it sent a <var>Klar/&lt;version&gt;</var> <var>product/version</var> token.</p>
-
-<table>
- <thead>
-  <tr>
-   <th>Klar Version (Rendering Engine)</th>
-   <th>User Agent string</th>
-  </tr>
- </thead>
- <tbody>
-  <tr>
-   <td>1.0 (WebView)</td>
-   <td>Mozilla/5.0 (Linux; Android 7.0) AppleWebKit/537.36 (KHTML, like Gecko) Version/4.0 Klar/1.0 Chrome/58.0.3029.83 Mobile Safari/537.36</td>
-  </tr>
-  <tr>
-   <td>4.1+ (WebView)</td>
-   <td>Mozilla/5.0 (Linux; Android 7.0) AppleWebKit/537.36 (KHTML, like Gecko) Version/4.0 Focus/4.1 Chrome/62.0.3029.83 Mobile Safari/537.36</td>
-  </tr>
-  <tr>
-   <td>6.0+ (GeckoView)</td>
-   <td>Mozilla/5.0 (Android 7.0; Mobile; rv:62.0) Gecko/62.0 Firefox/62.0</td>
-  </tr>
- </tbody>
-</table>
-
-<h2 id="Focus_for_iOS">Focus for iOS</h2>
-
-<p>Version 7 of Focus for iOS uses a user agent string with the following format:</p>
-
-<pre>Mozilla/5.0 (iPhone; CPU iPhone OS 12_1 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) FxiOS/7.0.4 Mobile/16B91 Safari/605.1.15</pre>
-
-<p>Note: this user agent was retrieved from an iPhone XR simulator and may be different on device.</p>
-
-<h2 id="Firefox_for_Fire_TV">Firefox for Fire TV</h2>
-
-<p>Version 3 (and probably earlier) of Firefox for Fire TV use a user agent string with the following format:</p>
-
-<pre>Mozilla/5.0 (Linux; &lt;Android version&gt;) AppleWebKit/537.36 (KHTML, like Gecko) Version/4.0 Focus/&lt;firefoxversion&gt; Chrome/&lt;Chrome Rev&gt; Safari/&lt;WebKit Rev&gt;</pre>
-
-<table>
-  <tr>
-   <th>Firefox TV version</th>
-   <th>User Agent string</th>
-  </tr>
-  <tr>
-   <td>v3.0</td>
-   <td>Mozilla/5.0 (Linux; Android 7.1.2) AppleWebKit/537.36 (KHTML, like Gecko) Version/4.0 Focus/3.0 Chrome/59.0.3017.125 Safari/537.36</td>
-  </tr>
-</table>
-
-<h2 id="Firefox_for_Echo_Show">Firefox for Echo Show</h2>
-
-<p>From version 1.1, Firefox for Echo Show uses a user agent string with the following format:</p>
-
-<pre>Mozilla/5.0 (Linux; &lt;Android version&gt;) AppleWebKit/537.36 (KHTML, like Gecko) Version/4.0 Focus/&lt;firefoxversion&gt; Chrome/&lt;Chrome Rev&gt; Safari/&lt;WebKit Rev&gt;
-</pre>
-
-<table>
-  <tr>
-   <th>Firefox for Echo Show version</th>
-   <th>User agent string</th>
-  </tr>
-  <tr>
-   <td>v1.1</td>
-   <td>Mozilla/5.0 (Linux; Android 5.1.1) AppleWebKit/537.36 (KHTML, like Gecko) Version/4.0 Focus/1.1 Chrome/59.0.3017.125 Safari/537.36</td>
-  </tr>
-</table>
-
-<h2 id="Firefox_OS">Firefox OS</h2>
-
-<table>
-  <tr>
-   <th>Form factor</th>
-   <th>Gecko user agent string</th>
-  </tr>
-  <tr>
-   <td>Phone</td>
-   <td>Mozilla/5.0 (Mobile; rv:26.0) Gecko/26.0 Firefox/26.0</td>
-  </tr>
-  <tr>
-   <td>Tablet</td>
-   <td>Mozilla/5.0 (Tablet; rv:26.0) Gecko/26.0 Firefox/26.0</td>
-  </tr>
-  <tr>
-   <td>TV</td>
-   <td>Mozilla/5.0 (TV; rv:44.0) Gecko/44.0 Firefox/44.0</td>
-  </tr>
-  <tr>
-   <td>Device-specific</td>
-   <td>Mozilla/5.0 (Mobile; <em><strong>nnnn;</strong></em> rv:26.0) Gecko/26.0 Firefox/26.0</td>
-  </tr>
-</table>
-
-<h3 id="Device-specific_user_agent_strings">Device-specific user agent strings</h3>
-
-<p>Although it is <strong>strongly discouraged</strong> by Mozilla, some handset manufacturers unfortunately include a token in their device's UA string that represents their device id. If this is the case, the Firefox OS UA string will look like the device-specific string in the table above, where <em><strong>nnnn;</strong></em> is the manufacturer's code for the device (see <a href="https://wiki.mozilla.org/B2G/User_Agent/Device_Model_Inclusion_Requirements">Guidelines</a>). Some of them we have noticed are of the form "<strong>NexusOne;</strong>", "<strong>ZTEOpen;</strong>", or "<strong>Open C;</strong>" (note that putting space is also discouraged). We provide this information to assist with your UA detection logic, but Mozilla discourages the detection of a device id in UA strings.</p>
-
-<p>Here is a JavaScript regular expression that will detect all mobile devices, including devices with a device id in their UA string:</p>
-
-<pre>/mobi/i</pre>
-
-<p>The <code>i</code> makes it case-insensitive, and <code>mobi</code> matches all mobile browsers.</p>
-
-<h3 id="Firefox_OS_version_number">Firefox OS version number</h3>
-
-<p>While the version number for Firefox OS is not included in the UA string, it is possible to infer version information from the Gecko version number present in the UA string.</p>
-
-<table>
- <thead>
-  <tr>
-   <th>Firefox OS version number</th>
-   <th>Gecko version number</th>
-  </tr>
- </thead>
- <tbody>
-  <tr>
-   <td>1.0.1</td>
-   <td>18.0</td>
-  </tr>
-  <tr>
-   <td>1.1</td>
-   <td>18.1</td>
-  </tr>
-  <tr>
-   <td>1.2</td>
-   <td>26.0</td>
-  </tr>
-  <tr>
-   <td>1.3</td>
-   <td>28.0</td>
-  </tr>
-  <tr>
-   <td>1.4</td>
-   <td>30.0</td>
-  </tr>
-  <tr>
-   <td>2.0</td>
-   <td>32.0</td>
-  </tr>
-  <tr>
-   <td>2.1</td>
-   <td>34.0</td>
-  </tr>
-  <tr>
-   <td>2.2</td>
-   <td>37</td>
-  </tr>
-  <tr>
-   <td>2.5</td>
-   <td>44</td>
-  </tr>
- </tbody>
-</table>
-
-<div class="notecard note">
-  <p><strong>Note:</strong> It's easy to find the correspondences by looking at the <a href="https://hg.mozilla.org/releases">Mercurial repository names</a>: repositories starting by <code>mozilla-b2g</code> are the release repositories for Firefox OS, and have both Firefox OS and Gecko versions in their names.</p>
-</div>
-
-<p>Firefox OS has a four-digit version number: <code>X.X.X.Y</code>. The first two digits are owned by the Mozilla product team and denote versions with new features (eg: v1.1, 1.2, etc). The third digit is incremented with regular version tags (about every 6 weeks) for security updates, and the fourth is owned by the OEM.</p>
-
-<h2 id="Firefox_for_iOS">Firefox for iOS</h2>
-
-<p>Firefox for iOS uses the default Mobile Safari UA string, with an additional <strong>FxiOS/&lt;version&gt;</strong> token, similar to how <a href="https://developer.chrome.com/multidevice/user-agent#chrome_for_ios_user_agent">Chrome for iOS identifies itself</a>.</p>
-
-<table>
- <thead>
-  <tr>
-   <th>Form factor</th>
-   <th>Firefox for iOS user agent string</th>
-  </tr>
- </thead>
- <tbody>
-  <tr>
-   <td>iPod</td>
-   <td>Mozilla/5.0 (iPod touch; CPU iPhone OS 8_3 like Mac OS X) AppleWebKit/600.1.4 (KHTML, like Gecko) <strong>FxiOS/1.0</strong> Mobile/12F69 Safari/600.1.4</td>
-  </tr>
-  <tr>
-   <td>iPhone</td>
-   <td>Mozilla/5.0 (iPhone; CPU iPhone OS 8_3 like Mac OS X) AppleWebKit/600.1.4 (KHTML, like Gecko) <strong>FxiOS/1.0</strong> Mobile/12F69 Safari/600.1.4</td>
-  </tr>
-  <tr>
-   <td>iPad</td>
-   <td>Mozilla/5.0 (iPad; CPU iPhone OS 8_3 like Mac OS X) AppleWebKit/600.1.4 (KHTML, like Gecko) <strong>FxiOS/1.0</strong> Mobile/12F69 Safari/600.1.4</td>
-  </tr>
- </tbody>
-</table>
-
-<h2 id="Firefox_Web_Runtime">Firefox Web Runtime</h2>
-
-<p>The Web Runtime uses the same user agent string as desktop Firefox.</p>
-
-<h2 id="Other_Gecko-based_browsers">Other Gecko-based browsers</h2>
-
-<p>These are some sample UA strings from other Gecko-based browsers on various platforms. Note that many of these have not yet been released on Gecko 2.0!</p>
-
-<table>
- <thead>
-  <tr>
-   <th>Browser</th>
-   <th>Gecko user agent string</th>
-  </tr>
- </thead>
- <tbody>
-  <tr>
-   <td>Firefox for Maemo (Nokia N900)</td>
-   <td>Mozilla/5.0 (Maemo; Linux armv7l; rv:10.0.1) Gecko/20100101 Firefox/10.0.1 Fennec/10.0.1</td>
-  </tr>
-  <tr>
-   <td>Camino on Mac</td>
-   <td>Mozilla/5.0 (Macintosh; Intel Mac OS X 10.5; rv:2.0.1) Gecko/20100101 Firefox/4.0.1 Camino/2.2.1</td>
-  </tr>
-  <tr>
-   <td>SeaMonkey on Windows</td>
-   <td>Mozilla/5.0 (Windows NT 5.2; rv:10.0.1) Gecko/20100101 Firefox/10.0.1 SeaMonkey/2.7.1</td>
-  </tr>
-  <tr>
-   <td>SeaMonkey on Mac</td>
-   <td>Mozilla/5.0 (Macintosh; Intel Mac OS X 10.5; rv:10.0.1) Gecko/20100101 Firefox/10.0.1 SeaMonkey/2.7.1</td>
-  </tr>
-  <tr>
-   <td>SeaMonkey on Linux</td>
-   <td>Mozilla/5.0 (X11; Linux i686; rv:10.0.1) Gecko/20100101 Firefox/10.0.1 SeaMonkey/2.7.1</td>
-  </tr>
- </tbody>
-</table>
-
-<h2 id="Implementation_notes_for_applications_vendors_and_extensions">Implementation notes for applications, vendors, and extensions</h2>
-
-<p>Prior to Firefox 4 and Gecko 2.0, it was possible for extensions to add user agent parts through the <code>general.useragent.extra.<em>identifier</em></code> preferences. But that has not been possible since {{ Bug(581008) }}.</p>
-
-<p>In the past, specific plug-ins, add-ons or extensions added user agent parts to notify sites they were installed. The recommended way to do this, if it's absolutely necessary (remember that it slows down every request) is to <a href="/en-US/docs/Setting_HTTP_request_headers">set a custom HTTP header</a>.</p>
-
-<h2 id="See_also">See also</h2>
-
-<ul>
- <li><a href="https://lawrencemandel.com/2012/07/27/decision-made-firefox-os-user-agent-string/">Firefox OS User Agent String</a> (blog post w/<a href="https://bugzilla.mozilla.org/show_bug.cgi?id=777710">bug 777710</a> reference)</li>
- <li><a href="https://hacks.mozilla.org/2010/09/final-user-agent-string-for-firefox-4/">Final User Agent string for Firefox 4</a> (blog post)</li>
- <li>Recommendations on <a href="/en-US/docs/Browser_Detection_and_Cross_Browser_Support">sniffing the UA string for cross-browser support</a></li>
- <li><a href="/en-US/docs/Web/API/Window/navigator" rel="internal">window.navigator.userAgent</a></li>
- <li><a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1169772">Add Android version to Fennec UA String (bug 1169772)</a></li>
-</ul>
+{{HTTPSidebar}}
+
+This document describes the user agent string used in Firefox 4 and later and applications based on Gecko 2.0 and later. For a breakdown of changes to the string in Gecko 2.0, see [Final User Agent string for Firefox 4](https://hacks.mozilla.org/2010/09/final-user-agent-string-for-firefox-4/) (blog post). See also this document on [user agent sniffing](/en-US/docs/Web/HTTP/Browser_detection_using_the_user_agent) and this [Hacks blog post](https://hacks.mozilla.org/2013/09/user-agent-detection-history-and-checklist/).
+
+## General form
+
+The UA string of Firefox itself is broken down into four components:
+
+`Mozilla/5.0 (platform; rv:geckoversion) Gecko/geckotrail Firefox/firefoxversion`
+
+- `Mozilla/5.0` is the general token that says the browser is Mozilla compatible, and is common to almost every browser today.
+- `platform` describes the native platform the browser is running on (e.g. Windows, Mac, Linux or Android), and whether or not it's a mobile phone. Firefox OS phones say "`Mobile`"; the web is the platform. Note that `platform` can consist of multiple "; "-separated tokens. See below for further details and examples.
+
+  > **Note:** Though fixed in Firefox 69, previous 32-bit versions of Firefox running on 64-bit processors would report that the system is using a 32-bit CPU.
+
+- `rv:geckoversion` indicates the release version of Gecko (such as "`17.0`"). In recent browsers, `geckoversion` is the same as `firefoxversion`.
+- `Gecko/geckotrail` indicates that the browser is based on Gecko.
+- On Desktop, `geckotrail` is the fixed string "`20100101`"
+- `Firefox/firefoxversion` indicates the browser is Firefox, and provides the version (such as "`17.0`").
+- From Firefox 10 on mobile, `geckotrail` is the same as `firefoxversion`.
+
+> **Note:** The recommended way of sniffing for Gecko-based browsers (if you _have to_ sniff for the browser engine instead of using feature detection) is by the presence of the "`Gecko`" and "`rv:`" strings, since some other browsers include a "`like Gecko`" token.
+
+For other products based on Gecko, the string can take one of two forms, where the tokens have the same meaning except those noted below:
+
+`Mozilla/5.0 (platform; rv:geckoversion) Gecko/geckotrail appname/appversion`
+`Mozilla/5.0 (platform; rv:geckoversion) Gecko/geckotrail Firefox/firefoxversion appname/appversion`
+
+- `appname/appversion` indicates the application name and version. For instance, this could be "`Camino/2.1.1`", or "`SeaMonkey/2.7.1`".
+- `Firefox/firefoxversion` is an optional compatibility token that some Gecko-based browsers may choose to incorporate, to achieve maximum compatibility with websites that expect Firefox. `firefoxversion` will generally represent the equivalent Firefox release corresponding to the given Gecko version. Some Gecko-based browsers may not opt into using this token; for this reason, sniffers should be looking for Gecko — not Firefox! Whether this token appears is controlled by the _"general.useragent.compatMode.firefox"_ boolean pref.
+
+## Mobile and Tablet indicators
+
+> **Note:** Only from Firefox 11 to 68.
+
+The `platform` part of the UA string indicates if Firefox is running on a phone-sized or tablet device. When Firefox runs on a device that has the phone form factor, there is a `Mobile;` token in the `platform` part of the UA string. When Firefox runs on a tablet device, there is a `Tablet;` token in the `platform` part of the UA string instead. For example:
+
+    Mozilla/5.0 (Android 4.4; Mobile; rv:41.0) Gecko/41.0 Firefox/41.0
+    Mozilla/5.0 (Android 4.4; Tablet; rv:41.0) Gecko/41.0 Firefox/41.0
+
+> **Note:** The version numbers are not relevant. Avoid inferring materials based on these.
+
+The preferred way to target content to a device form factor is to use CSS Media Queries. However, if you use UA sniffing to target content to a device form factor, please look for **Mobi** (to include Opera Mobile, which uses "Mobi") for the phone form factor and do **not** assume any correlation between "Android" and the device form factor. This way, your code will work if/when Firefox ships on other phone/tablet operating systems or Android is used for laptops. Also, please use touch detection to find touch devices rather than looking for "Mobi" or "Tablet", since there may be touch devices which are not tablets.
+
+> **Note:** Firefox OS devices identify themselves without any operating system indication; for example: "Mozilla/5.0 (Mobile; rv:15.0) Gecko/15.0 Firefox/15.0". The web is the platform.
+
+## Windows
+
+Windows user agents have the following variations, where _x.y_ is the Windows NT version (for instance, Windows NT 6.1).
+
+| Windows version                  | Gecko user agent string                                                           |
+| -------------------------------- | --------------------------------------------------------------------------------- |
+| Windows NT on x86 or aarch64 CPU | Mozilla/5.0 (Windows NT _x_._y_; rv:10.0) Gecko/20100101 Firefox/10.0             |
+| Windows NT on x64 CPU            | Mozilla/5.0 (Windows NT _x_._y_; Win64; x64; rv:10.0) Gecko/20100101 Firefox/10.0 |
+
+## Macintosh
+
+Here, _x.y_ is the version of Mac OS X (for instance, Mac OS X 10.15). Starting in Firefox 87, Firefox caps the reported Mac OS X version number to 10.15, so macOS 11.0 Big Sur and later will be reported as "10.15" in the User-Agent string.
+
+Note that [Firefox no longer officially supports Mac OS X on PowerPC](https://support.mozilla.org/kb/firefox-no-longer-works-mac-os-10-4-or-powerpc).
+
+| Mac OS X version                    | Gecko user agent string                                                            |
+| ----------------------------------- | ---------------------------------------------------------------------------------- |
+| Mac OS X on x86, x86_64, or aarch64 | Mozilla/5.0 (Macintosh; Intel Mac OS X _x.y_; rv:10.0) Gecko/20100101 Firefox/10.0 |
+| Mac OS X on PowerPC                 | Mozilla/5.0 (Macintosh; PPC Mac OS X _x.y_; rv:10.0) Gecko/20100101 Firefox/10.0   |
+
+## Linux
+
+Linux is a more diverse platform. Your distribution of Linux might include an extension that changes your user-agent. A few common examples are given below.
+
+| Linux version                                  | Gecko user agent string                                                            |
+| ---------------------------------------------- | ---------------------------------------------------------------------------------- |
+| Linux desktop on i686 CPU                      | Mozilla/5.0 (X11; Linux i686; rv:10.0) Gecko/20100101 Firefox/10.0                 |
+| Linux desktop on x86_64 CPU                    | Mozilla/5.0 (X11; Linux x86_64; rv:10.0) Gecko/20100101 Firefox/10.0               |
+| Nokia N900 Linux mobile, on the Fennec browser | Mozilla/5.0 (Maemo; Linux armv7l; rv:10.0) Gecko/20100101 Firefox/10.0 Fennec/10.0 |
+
+## Android (version 40 and below)
+
+| Form factor | Gecko user agent string                                        |
+| ----------- | -------------------------------------------------------------- |
+| Phone       | Mozilla/5.0 (Android; Mobile; rv:40.0) Gecko/40.0 Firefox/40.0 |
+| Tablet      | Mozilla/5.0 (Android; Tablet; rv:40.0) Gecko/40.0 Firefox/40.0 |
+
+## Android (version 41 and above)
+
+Beginning in version 41, Firefox for Android will contain the Android version as part of the _platform_ token. For increased interoperability, if the browser is running on a version below 4 it will report 4.4. Android versions 4 and above will report the version accurately. Note that the same Gecko—with the same capabilities—is shipped to all versions of Android.
+
+| Form factor | Gecko user agent string                                            |
+| ----------- | ------------------------------------------------------------------ |
+| Phone       | Mozilla/5.0 (Android 4.4; Mobile; rv:41.0) Gecko/41.0 Firefox/41.0 |
+| Tablet      | Mozilla/5.0 (Android 4.4; Tablet; rv:41.0) Gecko/41.0 Firefox/41.0 |
+
+## Focus for Android
+
+From version 1, Focus is powered by Android WebView and uses the following user agent string format:
+
+    Mozilla/5.0 (Linux; <Android Version> <Build Tag etc.>) AppleWebKit/<WebKit Rev> (KHTML, like Gecko) Version/4.0 Focus/<focusversion> Chrome/<Chrome Rev> Mobile Safari/<WebKit Rev>
+
+Tablet versions on WebView mirror mobile, but do not contain a `Mobile` token.
+
+Starting in Version 6, users can opt into using a GeckoView-based Focus for Android with a hidden preference: it uses a GeckoView UA string to advertise Gecko compatibility.
+
+| Focus Version (Rendering Engine) | User Agent string                                                                                                                      |
+| -------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------- |
+| 1.0 (WebView Mobile)             | Mozilla/5.0 (Linux; Android 7.0) AppleWebKit/537.36 (KHTML, like Gecko) Version/4.0 Focus/1.0 Chrome/59.0.3029.83 Mobile Safari/537.36 |
+| 1.0 (WebView Tablet)             | Mozilla/5.0 (Linux; Android 7.0) AppleWebKit/537.36 (KHTML, like Gecko) Version/4.0 Focus/1.0 Chrome/59.0.3029.83 Safari/537.36        |
+| 6.0 (GeckoView)                  | Mozilla/5.0 (Android 7.0; Mobile; rv:62.0) Gecko/62.0 Firefox/62.0                                                                     |
+
+## Klar for Android
+
+Since version 4.1, Klar for Android uses the same UA string as [Focus for Android](#focus_for_android). Before version 4.1, it sent a _Klar/\<version>_ _product/version_ token.
+
+| Klar Version (Rendering Engine) | User Agent string                                                                                                                      |
+| ------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------- |
+| 1.0 (WebView)                   | Mozilla/5.0 (Linux; Android 7.0) AppleWebKit/537.36 (KHTML, like Gecko) Version/4.0 Klar/1.0 Chrome/58.0.3029.83 Mobile Safari/537.36  |
+| 4.1+ (WebView)                  | Mozilla/5.0 (Linux; Android 7.0) AppleWebKit/537.36 (KHTML, like Gecko) Version/4.0 Focus/4.1 Chrome/62.0.3029.83 Mobile Safari/537.36 |
+| 6.0+ (GeckoView)                | Mozilla/5.0 (Android 7.0; Mobile; rv:62.0) Gecko/62.0 Firefox/62.0                                                                     |
+
+## Focus for iOS
+
+Version 7 of Focus for iOS uses a user agent string with the following format:
+
+    Mozilla/5.0 (iPhone; CPU iPhone OS 12_1 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) FxiOS/7.0.4 Mobile/16B91 Safari/605.1.15
+
+Note: this user agent was retrieved from an iPhone XR simulator and may be different on device.
+
+## Firefox for Fire TV
+
+Version 3 (and probably earlier) of Firefox for Fire TV use a user agent string with the following format:
+
+    Mozilla/5.0 (Linux; <Android version>) AppleWebKit/537.36 (KHTML, like Gecko) Version/4.0 Focus/<firefoxversion> Chrome/<Chrome Rev> Safari/<WebKit Rev>
+
+| Firefox TV version | User Agent string                                                                                                                  |
+| ------------------ | ---------------------------------------------------------------------------------------------------------------------------------- |
+| v3.0               | Mozilla/5.0 (Linux; Android 7.1.2) AppleWebKit/537.36 (KHTML, like Gecko) Version/4.0 Focus/3.0 Chrome/59.0.3017.125 Safari/537.36 |
+
+## Firefox for Echo Show
+
+From version 1.1, Firefox for Echo Show uses a user agent string with the following format:
+
+    Mozilla/5.0 (Linux; <Android version>) AppleWebKit/537.36 (KHTML, like Gecko) Version/4.0 Focus/<firefoxversion> Chrome/<Chrome Rev> Safari/<WebKit Rev>
+
+| Firefox for Echo Show version | User agent string                                                                                                                  |
+| ----------------------------- | ---------------------------------------------------------------------------------------------------------------------------------- |
+| v1.1                          | Mozilla/5.0 (Linux; Android 5.1.1) AppleWebKit/537.36 (KHTML, like Gecko) Version/4.0 Focus/1.1 Chrome/59.0.3017.125 Safari/537.36 |
+
+## Firefox OS
+
+| Form factor     | Gecko user agent string                                           |
+| --------------- | ----------------------------------------------------------------- |
+| Phone           | Mozilla/5.0 (Mobile; rv:26.0) Gecko/26.0 Firefox/26.0             |
+| Tablet          | Mozilla/5.0 (Tablet; rv:26.0) Gecko/26.0 Firefox/26.0             |
+| TV              | Mozilla/5.0 (TV; rv:44.0) Gecko/44.0 Firefox/44.0                 |
+| Device-specific | Mozilla/5.0 (Mobile; **_nnnn;_** rv:26.0) Gecko/26.0 Firefox/26.0 |
+
+### Device-specific user agent strings
+
+Although it is **strongly discouraged** by Mozilla, some handset manufacturers unfortunately include a token in their device's UA string that represents their device id. If this is the case, the Firefox OS UA string will look like the device-specific string in the table above, where **_nnnn;_** is the manufacturer's code for the device (see [Guidelines](https://wiki.mozilla.org/B2G/User_Agent/Device_Model_Inclusion_Requirements)). Some of them we have noticed are of the form "**NexusOne;**", "**ZTEOpen;**", or "**Open C;**" (note that putting space is also discouraged). We provide this information to assist with your UA detection logic, but Mozilla discourages the detection of a device id in UA strings.
+
+Here is a JavaScript regular expression that will detect all mobile devices, including devices with a device id in their UA string:
+
+    /mobi/i
+
+The `i` makes it case-insensitive, and `mobi` matches all mobile browsers.
+
+### Firefox OS version number
+
+While the version number for Firefox OS is not included in the UA string, it is possible to infer version information from the Gecko version number present in the UA string.
+
+| Firefox OS version number | Gecko version number |
+| ------------------------- | -------------------- |
+| 1.0.1                     | 18.0                 |
+| 1.1                       | 18.1                 |
+| 1.2                       | 26.0                 |
+| 1.3                       | 28.0                 |
+| 1.4                       | 30.0                 |
+| 2.0                       | 32.0                 |
+| 2.1                       | 34.0                 |
+| 2.2                       | 37                   |
+| 2.5                       | 44                   |
+
+> **Note:** It's easy to find the correspondences by looking at the [Mercurial repository names](https://hg.mozilla.org/releases): repositories starting by `mozilla-b2g` are the release repositories for Firefox OS, and have both Firefox OS and Gecko versions in their names.
+
+Firefox OS has a four-digit version number: `X.X.X.Y`. The first two digits are owned by the Mozilla product team and denote versions with new features (eg: v1.1, 1.2, etc). The third digit is incremented with regular version tags (about every 6 weeks) for security updates, and the fourth is owned by the OEM.
+
+## Firefox for iOS
+
+Firefox for iOS uses the default Mobile Safari UA string, with an additional **FxiOS/\<version>** token, similar to how [Chrome for iOS identifies itself](https://developer.chrome.com/multidevice/user-agent#chrome_for_ios_user_agent).
+
+| Form factor | Firefox for iOS user agent string                                                                                                           |
+| ----------- | ------------------------------------------------------------------------------------------------------------------------------------------- |
+| iPod        | Mozilla/5.0 (iPod touch; CPU iPhone OS 8_3 like Mac OS X) AppleWebKit/600.1.4 (KHTML, like Gecko) **FxiOS/1.0** Mobile/12F69 Safari/600.1.4 |
+| iPhone      | Mozilla/5.0 (iPhone; CPU iPhone OS 8_3 like Mac OS X) AppleWebKit/600.1.4 (KHTML, like Gecko) **FxiOS/1.0** Mobile/12F69 Safari/600.1.4     |
+| iPad        | Mozilla/5.0 (iPad; CPU iPhone OS 8_3 like Mac OS X) AppleWebKit/600.1.4 (KHTML, like Gecko) **FxiOS/1.0** Mobile/12F69 Safari/600.1.4       |
+
+## Firefox Web Runtime
+
+The Web Runtime uses the same user agent string as desktop Firefox.
+
+## Other Gecko-based browsers
+
+These are some sample UA strings from other Gecko-based browsers on various platforms. Note that many of these have not yet been released on Gecko 2.0!
+
+| Browser                        | Gecko user agent string                                                                               |
+| ------------------------------ | ----------------------------------------------------------------------------------------------------- |
+| Firefox for Maemo (Nokia N900) | Mozilla/5.0 (Maemo; Linux armv7l; rv:10.0.1) Gecko/20100101 Firefox/10.0.1 Fennec/10.0.1              |
+| Camino on Mac                  | Mozilla/5.0 (Macintosh; Intel Mac OS X 10.5; rv:2.0.1) Gecko/20100101 Firefox/4.0.1 Camino/2.2.1      |
+| SeaMonkey on Windows           | Mozilla/5.0 (Windows NT 5.2; rv:10.0.1) Gecko/20100101 Firefox/10.0.1 SeaMonkey/2.7.1                 |
+| SeaMonkey on Mac               | Mozilla/5.0 (Macintosh; Intel Mac OS X 10.5; rv:10.0.1) Gecko/20100101 Firefox/10.0.1 SeaMonkey/2.7.1 |
+| SeaMonkey on Linux             | Mozilla/5.0 (X11; Linux i686; rv:10.0.1) Gecko/20100101 Firefox/10.0.1 SeaMonkey/2.7.1                |
+
+## Implementation notes for applications, vendors, and extensions
+
+Prior to Firefox 4 and Gecko 2.0, it was possible for extensions to add user agent parts through the `general.useragent.extra.identifier` preferences. But that has not been possible since {{ Bug(581008) }}.
+
+In the past, specific plug-ins, add-ons or extensions added user agent parts to notify sites they were installed. The recommended way to do this, if it's absolutely necessary (remember that it slows down every request) is to [set a custom HTTP header](/en-US/docs/Setting_HTTP_request_headers).
+
+## See also
+
+- [Firefox OS User Agent String](https://lawrencemandel.com/2012/07/27/decision-made-firefox-os-user-agent-string/) (blog post w/[bug 777710](https://bugzilla.mozilla.org/show_bug.cgi?id=777710) reference)
+- [Final User Agent string for Firefox 4](https://hacks.mozilla.org/2010/09/final-user-agent-string-for-firefox-4/) (blog post)
+- Recommendations on [sniffing the UA string for cross-browser support](/en-US/docs/Browser_Detection_and_Cross_Browser_Support)
+- [window.navigator.userAgent](/en-US/docs/Web/API/Window/navigator)
+- [Add Android version to Fennec UA String (bug 1169772)](https://bugzilla.mozilla.org/show_bug.cgi?id=1169772)
diff --git a/files/en-us/web/http/headers/user-agent/index.md b/files/en-us/web/http/headers/user-agent/index.md
index 1c258da07aef7ac..9452f5ce9a790f5 100644
--- a/files/en-us/web/http/headers/user-agent/index.md
+++ b/files/en-us/web/http/headers/user-agent/index.md
@@ -8,139 +8,136 @@ tags:
   - User-agent
 browser-compat: http.headers.User-Agent
 ---
-<div>{{HTTPSidebar}}</div>
+{{HTTPSidebar}}
 
-<p>The <strong>User-Agent</strong> {{Glossary("request header")}} is a characteristic string that lets servers and network peers identify the application, operating system, vendor, and/or version of the requesting {{Glossary("user agent")}}.</p>
+The **User-Agent** {{Glossary("request header")}} is a characteristic string that lets servers and network peers identify the application, operating system, vendor, and/or version of the requesting {{Glossary("user agent")}}.
 
-<div class="notecard warning">
-  <p><strong>Warning:</strong> Please read <a href="/en-US/docs/Web/HTTP/Browser_detection_using_the_user_agent">Browser detection using the user agent</a> for why serving different Web pages or services to different browsers is usually a bad idea.</p>
-</div>
+> **Warning:** Please read [Browser detection using the user agent](/en-US/docs/Web/HTTP/Browser_detection_using_the_user_agent) for why serving different Web pages or services to different browsers is usually a bad idea.
 
 <table class="properties">
- <tbody>
-  <tr>
-   <th scope="row">Header type</th>
-   <td>{{Glossary("Request header")}}</td>
-  </tr>
-  <tr>
-   <th scope="row">{{Glossary("Forbidden header name")}}</th>
-   <td>no</td>
-  </tr>
- </tbody>
+  <tbody>
+    <tr>
+      <th scope="row">Header type</th>
+      <td>{{Glossary("Request header")}}</td>
+    </tr>
+    <tr>
+      <th scope="row">{{Glossary("Forbidden header name")}}</th>
+      <td>no</td>
+    </tr>
+  </tbody>
 </table>
 
-<h2 id="Syntax">Syntax</h2>
+## Syntax
 
-<pre class="brush: html">User-Agent: &lt;product&gt; / &lt;product-version&gt; &lt;comment&gt;</pre>
+```html
+User-Agent: <product> / <product-version> <comment>
+```
 
-<p>Common format for web browsers:</p>
+Common format for web browsers:
 
-<pre class="brush: html">User-Agent: Mozilla/5.0 (&lt;system-information&gt;) &lt;platform&gt; (&lt;platform-details&gt;) &lt;extensions&gt;</pre>
+```html
+User-Agent: Mozilla/5.0 (<system-information>) <platform> (<platform-details>) <extensions>
+```
 
-<h3 id="Directives">Directives</h3>
+### Directives
 
-<dl>
- <dt><code>&lt;product&gt;</code></dt>
- <dd>A product identifier — its name or development codename.</dd>
- <dt><code>&lt;product-version&gt;</code></dt>
- <dd>Version number of the product.</dd>
- <dt><code>&lt;comment&gt;</code></dt>
- <dd>Zero or more comments containing more details; sub-product information, for example.</dd>
-</dl>
+- `<product>`
+  - : A product identifier — its name or development codename.
+- `<product-version>`
+  - : Version number of the product.
+- `<comment>`
+  - : Zero or more comments containing more details; sub-product information, for example.
 
-<h2 id="Firefox_UA_string">Firefox UA string</h2>
+## Firefox UA string
 
-<p>For more on Firefox- and Gecko-based user agent strings, see the <a href="/en-US/docs/Web/HTTP/Headers/User-Agent/Firefox">Firefox user agent string reference</a>. The UA string of Firefox is broken down into 4 components:</p>
+For more on Firefox- and Gecko-based user agent strings, see the [Firefox user agent string reference](/en-US/docs/Web/HTTP/Headers/User-Agent/Firefox). The UA string of Firefox is broken down into 4 components:
 
-<pre>Mozilla/5.0 (<strong><em>platform</em></strong>; rv:<strong><em>geckoversion</em></strong>) Gecko/<strong><em>geckotrail</em></strong> Firefox/<strong><em>firefoxversion</em></strong></pre>
+    Mozilla/5.0 (platform; rv:geckoversion) Gecko/geckotrail Firefox/firefoxversion
 
-<ol>
- <li><code>Mozilla/5.0</code> is the general token that says the browser is Mozilla-compatible. For historical reasons, almost every browser today sends it.</li>
- <li><strong><em>platform</em></strong> describes the native platform the browser is running on (Windows, Mac, Linux, Android, etc.), and if it's a mobile phone. {{Glossary("Firefox OS")}} phones say <code>Mobile</code> — the web is the platform. Note that <strong><em>platform</em></strong> can consist of multiple "<code>; </code>"-separated tokens. See below for further details and examples.</li>
- <li><strong>rv:<em>geckoversion</em></strong> indicates the release version of Gecko (such as "<em>17.0</em>"). In recent browsers, <strong><em>geckoversion</em></strong> is the same as <strong><em>firefoxversion</em></strong>.</li>
- <li><strong><em>Gecko/geckotrail</em></strong> indicates that the browser is based on Gecko. (On Desktop, <em><strong>geckotrail</strong></em> is always the fixed string <code>20100101</code>.)</li>
- <li><em><strong>Firefox/firefoxversion</strong></em> indicates the browser is Firefox, and provides the version (such as "<em>17.0"</em>).</li>
-</ol>
+1.  `Mozilla/5.0` is the general token that says the browser is Mozilla-compatible. For historical reasons, almost every browser today sends it.
+2.  **_platform_** describes the native platform the browser is running on (Windows, Mac, Linux, Android, etc.), and if it's a mobile phone. {{Glossary("Firefox OS")}} phones say `Mobile` — the web is the platform. Note that **_platform_** can consist of multiple "`; `"-separated tokens. See below for further details and examples.
+3.  **rv:_geckoversion_** indicates the release version of Gecko (such as "_17.0_"). In recent browsers, **_geckoversion_** is the same as **_firefoxversion_**.
+4.  **_Gecko/geckotrail_** indicates that the browser is based on Gecko. (On Desktop, **_geckotrail_** is always the fixed string `20100101`.)
+5.  **_Firefox/firefoxversion_** indicates the browser is Firefox, and provides the version (such as "_17.0"_).
 
-<h3>Examples</h3>
+### Examples
 
-<pre>Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:47.0) Gecko/20100101 Firefox/47.0
-Mozilla/5.0 (Macintosh; Intel Mac OS X <em>x.y</em>; rv:42.0) Gecko/20100101 Firefox/42.0
-</pre>
+    Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:47.0) Gecko/20100101 Firefox/47.0
+    Mozilla/5.0 (Macintosh; Intel Mac OS X x.y; rv:42.0) Gecko/20100101 Firefox/42.0
 
-<h2 id="Chrome_UA_string">Chrome UA string</h2>
+## Chrome UA string
 
-<p>The Chrome (or Chromium/Blink-based engines) user agent string is similar to Firefox’s. For compatibility, it adds strings like <code>KHTML, like Gecko</code> and <code>Safari</code>.</p>
+The Chrome (or Chromium/Blink-based engines) user agent string is similar to Firefox’s. For compatibility, it adds strings like `KHTML, like Gecko` and `Safari`.
 
-<h3>Examples</h3>
+### Examples
 
-<pre>Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2704.103 Safari/537.36</pre>
+    Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2704.103 Safari/537.36
 
-<h2 id="Opera_UA_string">Opera UA string</h2>
+## Opera UA string
 
-<p>The Opera browser is also based on the Blink engine, which is why it almost looks the same, but adds <code>"OPR/&lt;version&gt;"</code>.</p>
+The Opera browser is also based on the Blink engine, which is why it almost looks the same, but adds `"OPR/<version>"`.
 
-<h3>Examples</h3>
+### Examples
 
-<pre>Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2704.106 Safari/537.36 OPR/38.0.2220.41</pre>
+    Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2704.106 Safari/537.36 OPR/38.0.2220.41
 
-<p>Older, Presto-based Opera releases used:</p>
+Older, Presto-based Opera releases used:
 
-<pre>Opera/9.80 (Macintosh; Intel Mac OS X; U; en) Presto/2.2.15 Version/10.00
-Opera/9.60 (Windows NT 6.0; U; en) Presto/2.1.1</pre>
+    Opera/9.80 (Macintosh; Intel Mac OS X; U; en) Presto/2.2.15 Version/10.00
+    Opera/9.60 (Windows NT 6.0; U; en) Presto/2.1.1
 
-<h2 id="Edge_UA_string">Microsoft Edge UA string</h2>
+## Microsoft Edge UA string
 
-<p>The Edge browser is also based on the Blink engine.</p>
+The Edge browser is also based on the Blink engine.
 
-<h3>Examples</h3>
+### Examples
 
-<pre>Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/91.0.4472.124 Safari/537.36 Edg/91.0.864.59</pre>
+    Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/91.0.4472.124 Safari/537.36 Edg/91.0.864.59
 
-<h2 id="Safari_UA_string">Safari UA string</h2>
+## Safari UA string
 
-<p>In this example, the user agent string is mobile Safari’s version. It contains the word <code>"Mobile"</code>.</p>
+In this example, the user agent string is mobile Safari’s version. It contains the word `"Mobile"`.
 
-<h3>Examples</h3>
+### Examples
 
-<pre>Mozilla/5.0 (iPhone; CPU iPhone OS 13_5_1 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/13.1.1 Mobile/15E148 Safari/604.1</pre>
+    Mozilla/5.0 (iPhone; CPU iPhone OS 13_5_1 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/13.1.1 Mobile/15E148 Safari/604.1
 
-<h2 id="Internet_Explorer_UA_string">Internet Explorer UA string</h2>
+## Internet Explorer UA string
 
-<h3>Examples</h3>
+### Examples
 
-<pre>Mozilla/5.0 (compatible; MSIE 9.0; Windows Phone OS 7.5; Trident/5.0; IEMobile/9.0)</pre>
+    Mozilla/5.0 (compatible; MSIE 9.0; Windows Phone OS 7.5; Trident/5.0; IEMobile/9.0)
 
-<h2 id="Crawler_and_bot_UA_strings">Crawler and bot UA strings</h2>
+## Crawler and bot UA strings
 
-<h3>Examples</h3>
+### Examples
 
-<pre>Mozilla/5.0 (compatible; Googlebot/2.1; +http://www.google.com/bot.html)</pre>
+    Mozilla/5.0 (compatible; Googlebot/2.1; +http://www.google.com/bot.html)
 
-<pre>Mozilla/5.0 (compatible; YandexAccessibilityBot/3.0; +http://yandex.com/bots)</pre>
+<!---->
 
-<h2 id="Library_and_net_tool_UA_strings">Library and net tool UA strings</h2>
+    Mozilla/5.0 (compatible; YandexAccessibilityBot/3.0; +http://yandex.com/bots)
 
-<h3>Examples</h3>
+## Library and net tool UA strings
 
-<pre>curl/7.64.1</pre>
+### Examples
 
-<pre>PostmanRuntime/7.26.5</pre>
+    curl/7.64.1
 
-<h2 id="Specifications">Specifications</h2>
+<!---->
+
+    PostmanRuntime/7.26.5
+
+## Specifications
 
 {{Specifications}}
 
-<h2 id="Browser_compatibility">Browser compatibility</h2>
+## Browser compatibility
 
-<p>{{Compat}}</p>
+{{Compat}}
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
- <li><a href="https://hacks.mozilla.org/2013/09/user-agent-detection-history-and-checklist/">User-Agent detection, history and checklist</a></li>
- <li><a href="/en-US/docs/Web/HTTP/Headers/User-Agent/Firefox">Firefox user agent string reference</a></li>
- <li>
-  <p><a href="/en-US/docs/Web/HTTP/Browser_detection_using_the_user_agent">Browser detection using the user agent</a></p>
- </li>
-</ul>
+- [User-Agent detection, history and checklist](https://hacks.mozilla.org/2013/09/user-agent-detection-history-and-checklist/)
+- [Firefox user agent string reference](/en-US/docs/Web/HTTP/Headers/User-Agent/Firefox)
+- [Browser detection using the user agent](/en-US/docs/Web/HTTP/Browser_detection_using_the_user_agent)
diff --git a/files/en-us/web/http/headers/vary/index.md b/files/en-us/web/http/headers/vary/index.md
index 8cd63b387c19fec..fde1be63997e947 100644
--- a/files/en-us/web/http/headers/vary/index.md
+++ b/files/en-us/web/http/headers/vary/index.md
@@ -9,17 +9,16 @@ tags:
   - header
 browser-compat: http.headers.Vary
 ---
-<div>{{HTTPSidebar}}</div>
+{{HTTPSidebar}}
 
-<p>The <strong><code>Vary</code></strong> HTTP response header determines how to match
-  future request headers to decide whether a cached response can be used rather than
-  requesting a fresh one from the origin server. It is used by the server to indicate
-  which headers it used when selecting a representation of a resource in a <a
-    href="/en-US/docs/Web/HTTP/Content_negotiation">content negotiation</a> algorithm.</p>
+The **`Vary`** HTTP response header determines how to match
+future request headers to decide whether a cached response can be used rather than
+requesting a fresh one from the origin server. It is used by the server to indicate
+which headers it used when selecting a representation of a resource in a [content negotiation](/en-US/docs/Web/HTTP/Content_negotiation) algorithm.
 
-<p>The <code>Vary</code> header should be set on a {{HTTPStatus("304")}}
-  <code>Not Modified</code> response exactly like it would have been set on an equivalent
-  {{HTTPStatus("200")}} <code>OK</code> response.</p>
+The `Vary` header should be set on a {{HTTPStatus("304")}}
+`Not Modified` response exactly like it would have been set on an equivalent
+{{HTTPStatus("200")}} `OK` response.
 
 <table class="properties">
   <tbody>
@@ -34,63 +33,55 @@ browser-compat: http.headers.Vary
   </tbody>
 </table>
 
-<h2 id="Syntax">Syntax</h2>
+## Syntax
 
-<pre class="brush: html">Vary: *
-Vary: &lt;header-name&gt;, &lt;header-name&gt;, ...
-</pre>
+```html
+Vary: *
+Vary: <header-name>, <header-name>, ...
+```
 
-<h2 id="Directives">Directives</h2>
+## Directives
 
-<dl>
-  <dt>*</dt>
-  <dd>Each request for a URL is supposed to be treated as a unique and uncacheable
+- \*
+  - : Each request for a URL is supposed to be treated as a unique and uncacheable
     request. A better way to indicate this is to use {{HTTPHeader("Cache-Control")}}:
-    <code>no-store</code>, which is clearer to read and also signals that the object
-    shouldn't be stored ever.</dd>
-  <dt>&lt;header-name&gt;</dt>
-  <dd>A comma-separated list of header names to take into account when deciding whether or
-    not a cached response can be used.</dd>
-</dl>
+    `no-store`, which is clearer to read and also signals that the object
+    shouldn't be stored ever.
+- \<header-name>
+  - : A comma-separated list of header names to take into account when deciding whether or
+    not a cached response can be used.
 
-<h2 id="Examples">Examples</h2>
+## Examples
 
-<h3 id="Dynamic_serving">Dynamic serving</h3>
+### Dynamic serving
 
-<p>When using the <code>Vary: User-Agent</code> header, caching servers should consider
-  the user agent when deciding whether to serve the page from cache. For example, if you
-  are serving different content to mobile users, it can help you to avoid that a cache may
-  mistakenly serve a desktop version of your site to your mobile users. It can help Google
-  and other search engines to discover the mobile version of a page, and might also tell
-  them that no <a href="https://en.wikipedia.org/wiki/Cloaking">Cloaking</a> is intended.
-</p>
+When using the `Vary: User-Agent` header, caching servers should consider
+the user agent when deciding whether to serve the page from cache. For example, if you
+are serving different content to mobile users, it can help you to avoid that a cache may
+mistakenly serve a desktop version of your site to your mobile users. It can help Google
+and other search engines to discover the mobile version of a page, and might also tell
+them that no [Cloaking](https://en.wikipedia.org/wiki/Cloaking) is intended.
 
-<pre>Vary: User-Agent</pre>
+    Vary: User-Agent
 
-<h2 id="Specifications">Specifications</h2>
+## Specifications
 
 {{Specifications}}
 
-<h2 id="Browser_compatibility">Browser compatibility</h2>
+## Browser compatibility
 
-<p>{{Compat}}</p>
+{{Compat}}
 
-<h2 id="Compatibility_notes">Compatibility notes</h2>
+## Compatibility notes
 
-<ul>
-  <li><a
-      href="https://blogs.msdn.microsoft.com/ieinternals/2009/06/17/vary-with-care/">Vary
-      with care – Vary header problems in IE6-9</a></li>
-</ul>
+- [Vary
+  with care – Vary header problems in IE6-9](https://blogs.msdn.microsoft.com/ieinternals/2009/06/17/vary-with-care/)
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
-  <li><a
-      href="https://www.smashingmagazine.com/2017/11/understanding-vary-header/">Understanding
-      The Vary Header - Smashing Magazine</a></li>
-  <li><a href="https://www.fastly.com/blog/best-practices-for-using-the-vary-header">Best
-      Practices for Using the Vary Header – fastly.com</a></li>
-  <li><a href="/en-US/docs/Web/HTTP/Content_negotiation">Content
-      negotiation</a></li>
-</ul>
+- [Understanding
+  The Vary Header - Smashing Magazine](https://www.smashingmagazine.com/2017/11/understanding-vary-header/)
+- [Best
+  Practices for Using the Vary Header – fastly.com](https://www.fastly.com/blog/best-practices-for-using-the-vary-header)
+- [Content
+  negotiation](/en-US/docs/Web/HTTP/Content_negotiation)
diff --git a/files/en-us/web/http/headers/via/index.md b/files/en-us/web/http/headers/via/index.md
index e89e6a0b42b1ed9..61f26567302ecdb 100644
--- a/files/en-us/web/http/headers/via/index.md
+++ b/files/en-us/web/http/headers/via/index.md
@@ -9,18 +9,21 @@ tags:
   - Reference
 browser-compat: http.headers.Via
 ---
-<div>{{HTTPSidebar}}</div>
+{{HTTPSidebar}}
 
-<p>The <code><strong>Via</strong></code> general header is added by proxies, both forward
-  and reverse proxies, and can appear in the request headers and the response headers. It
-  is used for tracking message forwards, avoiding request loops, and identifying the
-  protocol capabilities of senders along the request/response chain.</p>
+The **`Via`** general header is added by proxies, both forward
+and reverse proxies, and can appear in the request headers and the response headers. It
+is used for tracking message forwards, avoiding request loops, and identifying the
+protocol capabilities of senders along the request/response chain.
 
 <table class="properties">
   <tbody>
     <tr>
       <th scope="row">Header type</th>
-      <td>{{Glossary("Request header")}}, {{Glossary("Response header")}}</td>
+      <td>
+        {{Glossary("Request header")}},
+        {{Glossary("Response header")}}
+      </td>
     </tr>
     <tr>
       <th scope="row">{{Glossary("Forbidden header name")}}</th>
@@ -29,44 +32,40 @@ browser-compat: http.headers.Via
   </tbody>
 </table>
 
-<h2 id="Syntax">Syntax</h2>
+## Syntax
 
-<pre class="brush: html">Via: [ &lt;protocol-name&gt; "/" ] &lt;protocol-version&gt; &lt;host&gt; [ ":" &lt;port&gt; ]
+```html
+Via: [ <protocol-name> "/" ] <protocol-version> <host> [ ":" <port> ]
 or
-Via: [ &lt;protocol-name&gt; "/" ] &lt;protocol-version&gt; &lt;pseudonym&gt;
-</pre>
+Via: [ <protocol-name> "/" ] <protocol-version> <pseudonym>
+```
 
-<h2 id="Directives">Directives</h2>
+## Directives
 
-<dl>
-  <dt>&lt;protocol-name&gt;</dt>
-  <dd>Optional. The name of the protocol used, such as "HTTP".</dd>
-  <dt>&lt;protocol-version&gt;</dt>
-  <dd>The version of the protocol used, such as "1.1".</dd>
-  <dt>&lt;host&gt; and &lt;port&gt;</dt>
-  <dd>Public proxy URL and port.</dd>
-  <dt>&lt;pseudonym&gt;</dt>
-  <dd>Name/alias of an internal proxy.</dd>
-</dl>
+- \<protocol-name>
+  - : Optional. The name of the protocol used, such as "HTTP".
+- \<protocol-version>
+  - : The version of the protocol used, such as "1.1".
+- \<host> and \<port>
+  - : Public proxy URL and port.
+- \<pseudonym>
+  - : Name/alias of an internal proxy.
 
-<h2 id="Examples">Examples</h2>
+## Examples
 
-<pre>Via: 1.1 vegur
-Via: HTTP/1.1 GWA
-Via: 1.0 fred, 1.1 p.example.net
-</pre>
+    Via: 1.1 vegur
+    Via: HTTP/1.1 GWA
+    Via: 1.0 fred, 1.1 p.example.net
 
-<h2 id="Specifications">Specifications</h2>
+## Specifications
 
 {{Specifications}}
 
-<h2 id="Browser_compatibility">Browser compatibility</h2>
+## Browser compatibility
 
-<p>{{Compat}}</p>
+{{Compat}}
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
-  <li>{{HTTPHeader("X-Forwarded-For")}}</li>
-  <li><a href="https://github.com/heroku/vegur">Heroku's proxy library Vegur</a></li>
-</ul>
+- {{HTTPHeader("X-Forwarded-For")}}
+- [Heroku's proxy library Vegur](https://github.com/heroku/vegur)
diff --git a/files/en-us/web/http/headers/viewport-width/index.md b/files/en-us/web/http/headers/viewport-width/index.md
index 23b6267c9e90a86..5d70bec287ba39d 100644
--- a/files/en-us/web/http/headers/viewport-width/index.md
+++ b/files/en-us/web/http/headers/viewport-width/index.md
@@ -12,74 +12,69 @@ tags:
   - Exerimental
 browser-compat: http.headers.Viewport-Width
 ---
-<div>{{HTTPSidebar}} {{deprecated_header}}{{securecontext_header}}</div>
+{{HTTPSidebar}} {{deprecated_header}}{{securecontext_header}}
 
-<p>The <strong><code>Viewport-Width</code></strong> <a href="/en-US/docs/Glossary/Client_hints">device client hint</a> request header provides the client's layout viewport width in {{Glossary("CSS pixel","CSS pixels")}}. The value is rounded up to the smallest following integer (i.e. ceiling value).</p>
+The **`Viewport-Width`** [device client hint](/en-US/docs/Glossary/Client_hints) request header provides the client's layout viewport width in {{Glossary("CSS pixel","CSS pixels")}}. The value is rounded up to the smallest following integer (i.e. ceiling value).
 
 <table class="properties">
   <tbody>
-   <tr>
-    <th scope="row">Header type</th>
-    <td>{{Glossary("Request header")}}, {{Glossary("Client hints","Client hint")}}</td>
-   </tr>
-   <tr>
-    <th scope="row">{{Glossary("Forbidden header name")}}</th>
-    <td>no</td>
-   </tr>
+    <tr>
+      <th scope="row">Header type</th>
+      <td>
+        {{Glossary("Request header")}},
+        {{Glossary("Client hints","Client hint")}}
+      </td>
+    </tr>
+    <tr>
+      <th scope="row">{{Glossary("Forbidden header name")}}</th>
+      <td>no</td>
+    </tr>
   </tbody>
- </table>
+</table>
 
-<p>The hint can be used with other screen-specific hints to deliver images optimized for a specific screen size, or to omit resources that are not needed for a particular screen width.</p>
+The hint can be used with other screen-specific hints to deliver images optimized for a specific screen size, or to omit resources that are not needed for a particular screen width.
 
-<p>If the <code>Viewport-Width</code> header appears more than once in a message the last occurrence is used.</p>
+If the `Viewport-Width` header appears more than once in a message the last occurrence is used.
 
-<div class="notecard note">
-  <p><strong>Note:</strong></p>
-    <ul>
-      <li>Client Hints are accessible only on secure origins (via TLS).</li>
-      <li>A server has to opt in to receive the <code>Viewport-Width</code> header from the client, by sending the {{HTTPHeader("Accept-CH")}} response header.</li>
-      <li>Servers that opt in to the <code>Viewport-Width</code> client hint will typically also specify it in the {{HTTPHeader("Vary")}} header. This informs caches that the server may send different responses based on the header value in a request.</li>
-      <li><code>Viewport-Width</code> was removed from the original client hints specification in <a href="https://datatracker.ietf.org/doc/html/draft-ietf-httpbis-client-hints-07">draft-ietf-httpbis-client-hints-07</a>. The proposed replacement is <a href="https://wicg.github.io/responsive-image-client-hints/#sec-ch-viewport-width"><code>Sec-CH-Viewport-Width</code></a> (Responsive Image Client Hints).</li>
-    </ul>
-</div>
+> **Note:**
+>
+> - Client Hints are accessible only on secure origins (via TLS).
+> - A server has to opt in to receive the `Viewport-Width` header from the client, by sending the {{HTTPHeader("Accept-CH")}} response header.
+> - Servers that opt in to the `Viewport-Width` client hint will typically also specify it in the {{HTTPHeader("Vary")}} header. This informs caches that the server may send different responses based on the header value in a request.
+> - `Viewport-Width` was removed from the original client hints specification in [draft-ietf-httpbis-client-hints-07](https://datatracker.ietf.org/doc/html/draft-ietf-httpbis-client-hints-07). The proposed replacement is [`Sec-CH-Viewport-Width`](https://wicg.github.io/responsive-image-client-hints/#sec-ch-viewport-width) (Responsive Image Client Hints).
 
-<h2 id="Syntax">Syntax</h2>
+## Syntax
 
-<pre>Viewport-Width: &lt;number&gt;</pre>
+    Viewport-Width: <number>
 
-<h2 id="Directives">Directives</h2>
+## Directives
 
-<dl>
- <dt><code> &lt;number&gt;</code></dt>
- <dd>The width of the user's viewport in {{Glossary("CSS pixel","CSS pixels")}}, rounded up to the nearest integer.</dd>
-</dl>
+- `<number>`
+  - : The width of the user's viewport in {{Glossary("CSS pixel","CSS pixels")}}, rounded up to the nearest integer.
 
-<h2 id="Examples">Examples</h2>
+## Examples
 
-<p>A server must first opt in to receive the <code>Viewport-Width</code> header by sending the response header {{HTTPHeader("Accept-CH")}} containing the directive <code>Viewport-Width</code>.</p>
+A server must first opt in to receive the `Viewport-Width` header by sending the response header {{HTTPHeader("Accept-CH")}} containing the directive `Viewport-Width`.
 
-<pre>Accept-CH: Viewport-Width</pre>
+    Accept-CH: Viewport-Width
 
-<p>Then on subsequent requests the client might send <code>Viewport-Width</code> header back:</p>
+Then on subsequent requests the client might send `Viewport-Width` header back:
 
-<pre>Viewport-Width: 320</pre>
+    Viewport-Width: 320
 
-<h2 id="Browser_compatibility">Browser compatibility</h2>
+## Browser compatibility
 
-<p>{{Compat}}</p>
+{{Compat}}
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
-  <li><a href="https://developers.google.com/web/fundamentals/performance/optimizing-content-efficiency/client-hints">Adapting to Users with Client Hints</a> (developer.google.com)</li>
- <li>Device client hints
-  <ul>
-    <li>{{HTTPHeader("Content-DPR")}}</li>
-    <li>{{HTTPHeader("Device-Memory")}}</li>
-    <li>{{HTTPHeader("DPR")}}</li>
-    <li>{{HTTPHeader("Width")}}</li>
-   </ul>
- </li>
- <li>{{HTTPHeader("Accept-CH")}}</li>
- <li><a href="/en-US/docs/Web/HTTP/Caching#varying_responses">HTTP Caching > Varying responses</a> and {{HTTPHeader("Vary")}}</li>
-</ul>
+- [Adapting to Users with Client Hints](https://developers.google.com/web/fundamentals/performance/optimizing-content-efficiency/client-hints) (developer.google.com)
+- Device client hints
+
+  - {{HTTPHeader("Content-DPR")}}
+  - {{HTTPHeader("Device-Memory")}}
+  - {{HTTPHeader("DPR")}}
+  - {{HTTPHeader("Width")}}
+
+- {{HTTPHeader("Accept-CH")}}
+- [HTTP Caching > Varying responses](/en-US/docs/Web/HTTP/Caching#varying_responses) and {{HTTPHeader("Vary")}}
diff --git a/files/en-us/web/http/headers/want-digest/index.md b/files/en-us/web/http/headers/want-digest/index.md
index 14c7a1dfa78a866..de16d9af1884247 100644
--- a/files/en-us/web/http/headers/want-digest/index.md
+++ b/files/en-us/web/http/headers/want-digest/index.md
@@ -8,37 +8,37 @@ tags:
   - Response header
 browser-compat: http.headers.Want-Digest
 ---
-<div>{{HTTPSidebar}}</div>
+{{HTTPSidebar}}
 
-<p>The <code><strong>Want-Digest</strong></code> HTTP header is primarily used in a HTTP
-  request, to ask the responder to provide a {{Glossary("digest")}} of the requested
-  resource using the <code><a href="/en-US/docs/Web/HTTP/Headers/Digest">Digest</a></code>
-  response header.</p>
+The **`Want-Digest`** HTTP header is primarily used in a HTTP
+request, to ask the responder to provide a {{Glossary("digest")}} of the requested
+resource using the [`Digest`](/en-US/docs/Web/HTTP/Headers/Digest)
+response header.
 
-<p>The header contains identifiers for one or more digest algorithms that the sender
-  wishes the responder to use to create the digest. The sender may use <a
-    href="/en-US/docs/Glossary/Quality_values">quality values</a> to indicate its
-  preference ordering among the choices it offers.</p>
+The header contains identifiers for one or more digest algorithms that the sender
+wishes the responder to use to create the digest. The sender may use [quality values](/en-US/docs/Glossary/Quality_values) to indicate its
+preference ordering among the choices it offers.
 
-<p>If <code>Want-Digest</code> does not include any digest algorithms that the server
-  supports, the server may respond with:</p>
+If `Want-Digest` does not include any digest algorithms that the server
+supports, the server may respond with:
 
-<ul>
-  <li>a digest calculated using a different digest algorithm, or</li>
-  <li>a <code><a href="/en-US/docs/Web/HTTP/Status/400">400 Bad Request</a></code> error,
-    and include another <code>Want-Digest</code> header with that response, listing the
-    algorithms that it does support.</li>
-</ul>
+- a digest calculated using a different digest algorithm, or
+- a [`400 Bad Request`](/en-US/docs/Web/HTTP/Status/400) error,
+  and include another `Want-Digest` header with that response, listing the
+  algorithms that it does support.
 
-<p>See the page for the
-  <code><a href="/en-US/docs/Web/HTTP/Headers/Digest">Digest</a></code> header for more
-  information.</p>
+See the page for the
+[`Digest`](/en-US/docs/Web/HTTP/Headers/Digest) header for more
+information.
 
 <table class="properties">
   <tbody>
     <tr>
       <th scope="row">Header type</th>
-      <td>{{Glossary("Request header")}}, {{Glossary("Response header")}}</td>
+      <td>
+        {{Glossary("Request header")}},
+        {{Glossary("Response header")}}
+      </td>
     </tr>
     <tr>
       <th scope="row">{{Glossary("Forbidden header name")}}</th>
@@ -47,104 +47,94 @@ browser-compat: http.headers.Want-Digest
   </tbody>
 </table>
 
-<h2 id="Syntax">Syntax</h2>
+## Syntax
 
-<pre
-  class="brush: html">Want-Digest: &lt;digest-algorithm&gt;
+```html
+Want-Digest: <digest-algorithm>
 
 // Multiple algorithms, weighted with the quality value syntax:
-Want-Digest: &lt;digest-algorithm&gt;&lt;q-value&gt;,&lt;digest-algorithm&gt;&lt;q-value&gt;</pre>
+Want-Digest: <digest-algorithm><q-value>,<digest-algorithm><q-value>
+```
 
-<h2 id="Directives">Directives</h2>
+## Directives
 
-<dl>
-  <dt><code>&lt;digest-algorithm&gt;</code></dt>
-  <dd>Supported digest algorithms are defined in <a
-      href="https://datatracker.ietf.org/doc/html/rfc3230">RFC 3230</a> and <a
-      href="https://datatracker.ietf.org/doc/html/rfc5843">RFC 5843</a>, and include
-    <code>SHA-256</code> and <code>SHA-512</code>. Some of the supported algorithms,
-    including <code>unixsum</code> and <code>MD5</code> are subject to collisions and are
-    thus not suitable for applications in which collision-resistance is important.</dd>
-  <dt><code>&lt;q-value&gt;</code></dt>
-  <dd>The <a href="/en-US/docs/Glossary/Quality_values">quality value</a> to apply to that
-    option.</dd>
-</dl>
+- `<digest-algorithm>`
+  - : Supported digest algorithms are defined in [RFC 3230](https://datatracker.ietf.org/doc/html/rfc3230) and [RFC 5843](https://datatracker.ietf.org/doc/html/rfc5843), and include
+    `SHA-256` and `SHA-512`. Some of the supported algorithms,
+    including `unixsum` and `MD5` are subject to collisions and are
+    thus not suitable for applications in which collision-resistance is important.
+- `<q-value>`
+  - : The [quality value](/en-US/docs/Glossary/Quality_values) to apply to that
+    option.
 
-<h2 id="Examples">Examples</h2>
+## Examples
 
-<pre class="brush: html">Want-Digest: sha-256
-Want-Digest: SHA-512;q=0.3, sha-256;q=1, md5;q=0</pre>
+```html
+Want-Digest: sha-256
+Want-Digest: SHA-512;q=0.3, sha-256;q=1, md5;q=0
+```
 
-<h3 id="Basic_operation">Basic operation</h3>
+### Basic operation
 
-<p>The sender provides a list of digests which it is prepared to accept, and the server
-  uses one of them:</p>
+The sender provides a list of digests which it is prepared to accept, and the server
+uses one of them:
 
-<pre>Request:
+    Request:
 
-  GET /item
-  Want-Digest: sha-256;q=0.3, sha;q=1
+      GET /item
+      Want-Digest: sha-256;q=0.3, sha;q=1
 
-Response:
+    Response:
 
-  HTTP/1.1 200 Ok
-  Digest: sha-256=X48E9qOokqqrvdts8nOJRJN3OWDUoyWxBf7kbu9DBPE=</pre>
+      HTTP/1.1 200 Ok
+      Digest: sha-256=X48E9qOokqqrvdts8nOJRJN3OWDUoyWxBf7kbu9DBPE=
 
-<h3 id="Unsupported_digests">Unsupported digests</h3>
+### Unsupported digests
 
-<p>The server does not support any of the requested digest algorithms, so uses a different
-  algorithm:</p>
+The server does not support any of the requested digest algorithms, so uses a different
+algorithm:
 
-<pre>Request:
+    Request:
 
-  GET /item
-  Want-Digest: sha;q=1
+      GET /item
+      Want-Digest: sha;q=1
 
-Response:
+    Response:
 
-  HTTP/1.1 200 Ok
-  Digest: sha-256=X48E9qOokqqrvdts8nOJRJN3OWDUoyWxBf7kbu9DBPE=</pre>
+      HTTP/1.1 200 Ok
+      Digest: sha-256=X48E9qOokqqrvdts8nOJRJN3OWDUoyWxBf7kbu9DBPE=
 
-<p>The server does not support any of the requested digest algorithms, so responds with a
-  400 error and includes another <code>Want-Digest</code> header, listing the algorithms
-  that it does support:</p>
+The server does not support any of the requested digest algorithms, so responds with a
+400 error and includes another `Want-Digest` header, listing the algorithms
+that it does support:
 
-<pre>Request:
+    Request:
 
-  GET /item
-  Want-Digest: sha;q=1
+      GET /item
+      Want-Digest: sha;q=1
 
-Response:
+    Response:
 
-  HTTP/1.1 400 Bad Request
-  Want-Digest: sha-256, sha-512</pre>
+      HTTP/1.1 400 Bad Request
+      Want-Digest: sha-256, sha-512
 
-<h2 id="Specifications">Specifications</h2>
+## Specifications
 
-<table>
-  <tr>
-    <th>Specification</th>
-  </tr>
-  <tr>
-    <td><a href="https://datatracker.ietf.org/doc/draft-ietf-httpbis-digest-headers">draft-ietf-httpbis-digest-headers-latest</a></td>
-  </tr>
-</table>
+| Specification                                                                                                  |
+| -------------------------------------------------------------------------------------------------------------- |
+| [draft-ietf-httpbis-digest-headers-latest](https://datatracker.ietf.org/doc/draft-ietf-httpbis-digest-headers) |
 
-<p>
-  This header was originally defined in <a href="https://datatracker.ietf.org/doc/html/rfc3230">RFC 3230</a>,
-  but the definition of "selected representation"
-  in <a href="https://www.rfc-editor.org/info/rfc7231">RFC 7231</a>
-  made the original definition inconsistent with current HTTP specifications.
-  When released, The "Resource Digests for HTTP" draft therefore will obsolete RFC 3230
-  and will update the standard to be consistent.
-</p>
+This header was originally defined in [RFC 3230](https://datatracker.ietf.org/doc/html/rfc3230),
+but the definition of "selected representation"
+in [RFC 7231](https://www.rfc-editor.org/info/rfc7231)
+made the original definition inconsistent with current HTTP specifications.
+When released, The "Resource Digests for HTTP" draft therefore will obsolete RFC 3230
+and will update the standard to be consistent.
 
-<h2 id="Browser_compatibility">Browser compatibility</h2>
+## Browser compatibility
 
-<p>{{Compat}}</p>
+{{Compat}}
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
-  <li>{{HTTPHeader("Digest")}}</li>
-</ul>
+- {{HTTPHeader("Digest")}}
diff --git a/files/en-us/web/http/headers/warning/index.md b/files/en-us/web/http/headers/warning/index.md
index 709fb96ab8da730..87c06889c74ada1 100644
--- a/files/en-us/web/http/headers/warning/index.md
+++ b/files/en-us/web/http/headers/warning/index.md
@@ -9,29 +9,29 @@ tags:
   - Reference
 browser-compat: http.headers.Warning
 ---
-<div>{{HTTPSidebar}}</div>
+{{HTTPSidebar}}
 
-<div class="notecard note">
-  <p><strong>Note:</strong> The <code>Warning</code> header is soon to be deprecated; see
-    <a href="https://github.com/httpwg/http-core/issues/139">Warning
-      (https://github.com/httpwg/http-core/issues/139)</a> and <a
-      href="https://github.com/whatwg/fetch/issues/913">Warning: header &amp;
-      stale-while-revalidate (https://github.com/whatwg/fetch/issues/913)</a> for more
-    details.</p>
-</div>
+> **Note:** The `Warning` header is soon to be deprecated; see
+> [Warning
+> (https://github.com/httpwg/http-core/issues/139)](https://github.com/httpwg/http-core/issues/139) and [Warning: header &
+> stale-while-revalidate (https://github.com/whatwg/fetch/issues/913)](https://github.com/whatwg/fetch/issues/913) for more
+> details.
 
-<p>The <strong><code>Warning</code></strong> general HTTP header contains information
-  about possible problems with the status of the message. More than one
-  <code>Warning</code> header may appear in a response.</p>
+The **`Warning`** general HTTP header contains information
+about possible problems with the status of the message. More than one
+`Warning` header may appear in a response.
 
-<p><code>Warning</code> header fields can in general be applied to any message, however
-  some warn-codes are specific to caches and can only be applied to response messages.</p>
+`Warning` header fields can in general be applied to any message, however
+some warn-codes are specific to caches and can only be applied to response messages.
 
 <table class="properties">
   <tbody>
     <tr>
       <th scope="row">Header type</th>
-      <td>{{Glossary("Request header")}}, {{Glossary("Response header")}}</td>
+      <td>
+        {{Glossary("Request header")}},
+        {{Glossary("Response header")}}
+      </td>
     </tr>
     <tr>
       <th scope="row">{{Glossary("Forbidden header name")}}</th>
@@ -40,116 +40,66 @@ browser-compat: http.headers.Warning
   </tbody>
 </table>
 
-<h2 id="Syntax">Syntax</h2>
+## Syntax
 
-<pre class="brush: html">Warning: &lt;warn-code&gt; &lt;warn-agent&gt; &lt;warn-text&gt; [&lt;warn-date&gt;]
-</pre>
+```html
+Warning: <warn-code> <warn-agent> <warn-text> [<warn-date>]
+```
 
-<h2 id="Directives">Directives</h2>
+## Directives
 
-<dl>
-  <dt>&lt;warn-code&gt;</dt>
-  <dd>A three-digit warning number. The first digit indicates whether the
-    <code>Warning</code> is required to be deleted from a stored response after
+- \<warn-code>
+
+  - : A three-digit warning number. The first digit indicates whether the
+    `Warning` is required to be deleted from a stored response after
     validation.
-    <ul>
-      <li><code>1xx</code> warn-codes describe the freshness or validation status of the
-        response and will be deleted by a cache after deletion.</li>
-      <li>
-        <p><code>2xx</code> warn-codes describe some aspect of the representation that is
-          not rectified by a validation and won't be deleted by a cache after validation
-          unless a full response is sent.</p>
-      </li>
-    </ul>
-  </dd>
-  <dt>&lt;warn-agent&gt;</dt>
-  <dd>
-    <p>The name or pseudonym of the server or software adding the <code>Warning</code>
-      header (might be "-" when the agent is unknown).</p>
-  </dd>
-  <dt>&lt;warn-text&gt;</dt>
-  <dd>Advisory text describing the error.</dd>
-  <dt>&lt;warn-date&gt;</dt>
-  <dd>Optional. If more than one <code>Warning</code> header is sent, include a date that
-    matches the {{HTTPHeader("Date")}} header.</dd>
-</dl>
-
-<h2 id="Warning_codes">Warning codes</h2>
-
-<p>The <a
-    href="https://www.iana.org/assignments/http-warn-codes/http-warn-codes.xhtml">HTTP Warn
-    Codes registry at iana.org</a> defines the namespace for warn codes.</p>
-
-<table class="standard-table">
-  <thead>
-    <tr>
-      <th scope="col">Code</th>
-      <th scope="col">Text</th>
-      <th scope="col">Description</th>
-    </tr>
-  </thead>
-  <tbody>
-    <tr>
-      <td>110</td>
-      <td>Response is Stale</td>
-      <td>A response provided by a cache is stale (the expiration time set for it has
-        passed).</td>
-    </tr>
-    <tr>
-      <td>111</td>
-      <td>Revalidation Failed</td>
-      <td>An attempt to validate the response failed, due to an inability to reach the
-        server.</td>
-    </tr>
-    <tr>
-      <td>112</td>
-      <td>Disconnected Operation</td>
-      <td>The cache is disconnected from the rest of the network.</td>
-    </tr>
-    <tr>
-      <td>113</td>
-      <td>Heuristic Expiration</td>
-      <td>Sent If a cache heuristically chose a freshness lifetime greater than 24 hours
-        and the response's age is greater than 24 hours.</td>
-    </tr>
-    <tr>
-      <td>199</td>
-      <td>Miscellaneous Warning</td>
-      <td>Arbitrary, non-specific warning</td>
-    </tr>
-    <tr>
-      <td>214</td>
-      <td>Transformation Applied</td>
-      <td>Added by a proxy if it applies any transformation to the representation, such as
-        changing the content-coding, media-type or the like.</td>
-    </tr>
-    <tr>
-      <td>299</td>
-      <td>Miscellaneous Persistent Warning</td>
-      <td>Same as 199, but indicating a persistent warning</td>
-    </tr>
-  </tbody>
-</table>
 
-<h2 id="Examples">Examples</h2>
+    - `1xx` warn-codes describe the freshness or validation status of the
+      response and will be deleted by a cache after deletion.
+    - `2xx` warn-codes describe some aspect of the representation that is
+      not rectified by a validation and won't be deleted by a cache after validation
+      unless a full response is sent.
+
+- \<warn-agent>
+  - : The name or pseudonym of the server or software adding the `Warning`
+    header (might be "-" when the agent is unknown).
+- \<warn-text>
+  - : Advisory text describing the error.
+- \<warn-date>
+  - : Optional. If more than one `Warning` header is sent, include a date that
+    matches the {{HTTPHeader("Date")}} header.
+
+## Warning codes
+
+The [HTTP Warn
+Codes registry at iana.org](https://www.iana.org/assignments/http-warn-codes/http-warn-codes.xhtml) defines the namespace for warn codes.
+
+| Code | Text                             | Description                                                                                                                           |
+| ---- | -------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------- |
+| 110  | Response is Stale                | A response provided by a cache is stale (the expiration time set for it has passed).                                                  |
+| 111  | Revalidation Failed              | An attempt to validate the response failed, due to an inability to reach the server.                                                  |
+| 112  | Disconnected Operation           | The cache is disconnected from the rest of the network.                                                                               |
+| 113  | Heuristic Expiration             | Sent If a cache heuristically chose a freshness lifetime greater than 24 hours and the response's age is greater than 24 hours.       |
+| 199  | Miscellaneous Warning            | Arbitrary, non-specific warning                                                                                                       |
+| 214  | Transformation Applied           | Added by a proxy if it applies any transformation to the representation, such as changing the content-coding, media-type or the like. |
+| 299  | Miscellaneous Persistent Warning | Same as 199, but indicating a persistent warning                                                                                      |
+
+## Examples
 
-<pre>Warning: 110 anderson/1.3.37 "Response is stale"
+    Warning: 110 anderson/1.3.37 "Response is stale"
 
-Date: Wed, 21 Oct 2015 07:28:00 GMT
-Warning: 112 - "cache down" "Wed, 21 Oct 2015 07:28:00 GMT"
-</pre>
+    Date: Wed, 21 Oct 2015 07:28:00 GMT
+    Warning: 112 - "cache down" "Wed, 21 Oct 2015 07:28:00 GMT"
 
-<h2 id="Specifications">Specifications</h2>
+## Specifications
 
 {{Specifications}}
 
-<h2 id="Browser_compatibility">Browser compatibility</h2>
+## Browser compatibility
 
-<p>{{Compat}}</p>
+{{Compat}}
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
-  <li>{{HTTPHeader("Date")}}</li>
-  <li><a href="/en-US/docs/Web/HTTP/Status">HTTP response status codes</a></li>
-</ul>
+- {{HTTPHeader("Date")}}
+- [HTTP response status codes](/en-US/docs/Web/HTTP/Status)
diff --git a/files/en-us/web/http/headers/width/index.md b/files/en-us/web/http/headers/width/index.md
index 46a50f8ac625009..e07e15052802b82 100644
--- a/files/en-us/web/http/headers/width/index.md
+++ b/files/en-us/web/http/headers/width/index.md
@@ -12,77 +12,71 @@ tags:
   - Deprecated
 browser-compat: http.headers.Width
 ---
-<div>{{HTTPSidebar}} {{deprecated_header}}{{securecontext_header}}</div>
+{{HTTPSidebar}} {{deprecated_header}}{{securecontext_header}}
 
-<p>The <strong><code>Width</code></strong> {{Glossary("Client hints","device client hint")}} request header field indicates the desired resource width in physical pixels — the intrinsic size of an image. The provided pixel value is a number rounded to the smallest following integer (i.e. ceiling value).</p>
+The **`Width`** {{Glossary("Client hints","device client hint")}} request header field indicates the desired resource width in physical pixels — the intrinsic size of an image. The provided pixel value is a number rounded to the smallest following integer (i.e. ceiling value).
 
 <table class="properties">
   <tbody>
-   <tr>
-    <th scope="row">Header type</th>
-    <td>{{Glossary("Request header")}}, {{Glossary("Client hints","Client hint")}}</td>
-   </tr>
-   <tr>
-    <th scope="row">{{Glossary("Forbidden header name")}}</th>
-    <td>no</td>
-   </tr>
+    <tr>
+      <th scope="row">Header type</th>
+      <td>
+        {{Glossary("Request header")}},
+        {{Glossary("Client hints","Client hint")}}
+      </td>
+    </tr>
+    <tr>
+      <th scope="row">{{Glossary("Forbidden header name")}}</th>
+      <td>no</td>
+    </tr>
   </tbody>
- </table>
+</table>
 
-<p>The hint is particularly useful because it allows the client to request a resource that is optimal for both the screen and the layout: taking into account both the density-corrected width of the screen and the image's extrinsic size within the layout.</p>
+The hint is particularly useful because it allows the client to request a resource that is optimal for both the screen and the layout: taking into account both the density-corrected width of the screen and the image's extrinsic size within the layout.
 
-<p>If the desired resource width is not known at the time of the request or the resource does not have a display width, the <code>Width</code> header field can be omitted.</p>
+If the desired resource width is not known at the time of the request or the resource does not have a display width, the `Width` header field can be omitted.
 
-<p>If the <code>Width</code> header appears more than once in a message the last occurrence is used.</p>
+If the `Width` header appears more than once in a message the last occurrence is used.
 
-<div class="notecard note">
-  <p><strong>Note:</strong></p>
-    <ul>
-      <li>Client Hints are accessible only on secure origins (via TLS).</li>
-      <li>A server has to opt in to receive the <code>Width</code> header from the client, by sending the {{HTTPHeader("Accept-CH")}} response header.</li>
-      <li>Servers that opt in to the <code>Width</code> client hint will typically also specify it in the {{HTTPHeader("Vary")}} header. This informs caches that the server may send different responses based on the header value in a request.</li>
-      <li><code>Width</code> was removed from the client hints specification in <a href="https://datatracker.ietf.org/doc/html/draft-ietf-httpbis-client-hints-07">draft-ietf-httpbis-client-hints-07</a>. The proposed replacement is <a href="https://wicg.github.io/responsive-image-client-hints/#sec-ch-width"><code>Sec-CH-Width</code></a> (Responsive Image Client Hints).</li>
-    </ul>
-</div>
+> **Note:**
+>
+> - Client Hints are accessible only on secure origins (via TLS).
+> - A server has to opt in to receive the `Width` header from the client, by sending the {{HTTPHeader("Accept-CH")}} response header.
+> - Servers that opt in to the `Width` client hint will typically also specify it in the {{HTTPHeader("Vary")}} header. This informs caches that the server may send different responses based on the header value in a request.
+> - `Width` was removed from the client hints specification in [draft-ietf-httpbis-client-hints-07](https://datatracker.ietf.org/doc/html/draft-ietf-httpbis-client-hints-07). The proposed replacement is [`Sec-CH-Width`](https://wicg.github.io/responsive-image-client-hints/#sec-ch-width) (Responsive Image Client Hints).
 
-<h2 id="Syntax">Syntax</h2>
+## Syntax
 
-<pre>Width: &lt;number&gt;</pre>
+    Width: <number>
 
-<h2 id="Directives">Directives</h2>
+## Directives
 
-<dl>
- <dt><code> &lt;number&gt;</code></dt>
- <dd>The width of the resource in physical pixels, rounded up to the nearest integer.</dd>
-</dl>
+- `<number>`
+  - : The width of the resource in physical pixels, rounded up to the nearest integer.
 
+## Examples
 
-<h2 id="Examples">Examples</h2>
+The server first needs to opt in to receive the `Width` header by sending the response headers {{HTTPHeader("Accept-CH")}} containing `Width`.
 
-<p>The server first needs to opt in to receive the <code>Width</code> header by sending the response headers {{HTTPHeader("Accept-CH")}} containing <code>Width</code>.</p>
+    Accept-CH: Width
 
-<pre>Accept-CH: Width</pre>
+Then on subsequent requests the client might send `Width` header back:
 
-<p>Then on subsequent requests the client might send <code>Width</code> header back:</p>
+    Width: 1920
 
-<pre>Width: 1920</pre>
+## Browser compatibility
 
-<h2 id="Browser_compatibility">Browser compatibility</h2>
+{{Compat}}
 
-<p>{{Compat}}</p>
+## See also
 
-<h2 id="See_also">See also</h2>
+- [Adapting to Users with Client Hints](https://developers.google.com/web/fundamentals/performance/optimizing-content-efficiency/client-hints) (developer.google.com)
+- Device client hints
 
-<ul>
-  <li><a href="https://developers.google.com/web/fundamentals/performance/optimizing-content-efficiency/client-hints">Adapting to Users with Client Hints</a> (developer.google.com)</li>
- <li>Device client hints
-  <ul>
-    <li>{{HTTPHeader("Content-DPR")}}</li>
-    <li>{{HTTPHeader("Device-Memory")}}</li>
-    <li>{{HTTPHeader("DPR")}}</li>
-    <li>{{HTTPHeader("Viewport-Width")}}</li>
-   </ul>
- </li>
- <li>{{HTTPHeader("Accept-CH")}}</li>
- <li><a href="/en-US/docs/Web/HTTP/Caching#varying_responses">HTTP Caching > Varying responses</a> and {{HTTPHeader("Vary")}}</li>
-</ul>
+  - {{HTTPHeader("Content-DPR")}}
+  - {{HTTPHeader("Device-Memory")}}
+  - {{HTTPHeader("DPR")}}
+  - {{HTTPHeader("Viewport-Width")}}
+
+- {{HTTPHeader("Accept-CH")}}
+- [HTTP Caching > Varying responses](/en-US/docs/Web/HTTP/Caching#varying_responses) and {{HTTPHeader("Vary")}}
diff --git a/files/en-us/web/http/headers/www-authenticate/index.md b/files/en-us/web/http/headers/www-authenticate/index.md
index d94b017c3426e4d..c3251a52367939f 100644
--- a/files/en-us/web/http/headers/www-authenticate/index.md
+++ b/files/en-us/web/http/headers/www-authenticate/index.md
@@ -9,64 +9,60 @@ tags:
   - header
 browser-compat: http.headers.WWW-Authenticate
 ---
-<div>{{HTTPSidebar}}</div>
+{{HTTPSidebar}}
 
-<p>The HTTP <strong><code>WWW-Authenticate</code></strong> response header defines the authentication method that should be used to gain access to a resource.</p>
+The HTTP **`WWW-Authenticate`** response header defines the authentication method that should be used to gain access to a resource.
 
-<p>The <code>WWW-Authenticate</code> header is sent along with a {{HTTPStatus("401")}} <code>Unauthorized</code> response.</p>
+The `WWW-Authenticate` header is sent along with a {{HTTPStatus("401")}} `Unauthorized` response.
 
 <table class="properties">
-	<tbody>
-		<tr>
-			<th scope="row">Header type</th>
-			<td>{{Glossary("Response header")}}</td>
-		</tr>
-		<tr>
-			<th scope="row">{{Glossary("Forbidden header name")}}</th>
-			<td>no</td>
-		</tr>
-	</tbody>
+  <tbody>
+    <tr>
+      <th scope="row">Header type</th>
+      <td>{{Glossary("Response header")}}</td>
+    </tr>
+    <tr>
+      <th scope="row">{{Glossary("Forbidden header name")}}</th>
+      <td>no</td>
+    </tr>
+  </tbody>
 </table>
 
-<h2 id="Syntax">Syntax</h2>
+## Syntax
 
-<pre class="brush: html">WWW-Authenticate: &lt;type&gt; realm=&lt;realm&gt;[, charset="UTF-8"]
-</pre>
+```html
+WWW-Authenticate: <type> realm=<realm>[, charset="UTF-8"]
+```
 
-<h2 id="Directives">Directives</h2>
+## Directives
 
-<dl>
-	<dt>&lt;type&gt;</dt>
-	<dd><a href="/en-US/docs/Web/HTTP/Authentication#authentication_schemes">Authentication type</a>. A common type is <a href="/en-US/docs/Web/HTTP/Authentication#basic_authentication_scheme">"Basic"</a>. IANA maintains a <a href="https://www.iana.org/assignments/http-authschemes/http-authschemes.xhtml">list of Authentication schemes</a>.</dd>
-	<dt>realm=&lt;realm&gt;</dt>
-	<dd>A description of the protected area. If no realm is specified, clients often display a formatted hostname instead.</dd>
-	<dt>charset=&lt;charset&gt;</dt>
-	<dd>Tells the client the server's preferred encoding scheme when submitting a username and password. The only allowed value is the case insensitive string "UTF-8". This does not relate to the encoding of the realm string.</dd>
-</dl>
+- \<type>
+  - : [Authentication type](/en-US/docs/Web/HTTP/Authentication#authentication_schemes). A common type is ["Basic"](/en-US/docs/Web/HTTP/Authentication#basic_authentication_scheme). IANA maintains a [list of Authentication schemes](https://www.iana.org/assignments/http-authschemes/http-authschemes.xhtml).
+- realm=\<realm>
+  - : A description of the protected area. If no realm is specified, clients often display a formatted hostname instead.
+- charset=\<charset>
+  - : Tells the client the server's preferred encoding scheme when submitting a username and password. The only allowed value is the case insensitive string "UTF-8". This does not relate to the encoding of the realm string.
 
-<h2 id="Examples">Examples</h2>
+## Examples
 
-<p>Typically, a server response contains a <code>WWW-Authenticate</code> header that looks like this:</p>
+Typically, a server response contains a `WWW-Authenticate` header that looks like this:
 
-<pre>WWW-Authenticate: Basic realm="Access to the staging site", charset="UTF-8"
-</pre>
+    WWW-Authenticate: Basic realm="Access to the staging site", charset="UTF-8"
 
-<p>See also <a href="/en-US/docs/Web/HTTP/Authentication">HTTP authentication</a> for examples on how to configure Apache or nginx servers to password protect your site with HTTP basic authentication.</p>
+See also [HTTP authentication](/en-US/docs/Web/HTTP/Authentication) for examples on how to configure Apache or nginx servers to password protect your site with HTTP basic authentication.
 
-<h2 id="Specifications">Specifications</h2>
+## Specifications
 
 {{Specifications}}
 
-<h2 id="Browser_compatibility">Browser compatibility</h2>
+## Browser compatibility
 
-<p>{{Compat}}</p>
+{{Compat}}
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
-	<li><a href="/en-US/docs/Web/HTTP/Authentication">HTTP authentication</a></li>
-	<li>{{HTTPHeader("Authorization")}}</li>
-	<li>{{HTTPHeader("Proxy-Authorization")}}</li>
-	<li>{{HTTPHeader("Proxy-Authenticate")}}</li>
-	<li>{{HTTPStatus("401")}}, {{HTTPStatus("403")}}, {{HTTPStatus("407")}}</li>
-</ul>
+- [HTTP authentication](/en-US/docs/Web/HTTP/Authentication)
+- {{HTTPHeader("Authorization")}}
+- {{HTTPHeader("Proxy-Authorization")}}
+- {{HTTPHeader("Proxy-Authenticate")}}
+- {{HTTPStatus("401")}}, {{HTTPStatus("403")}}, {{HTTPStatus("407")}}
diff --git a/files/en-us/web/http/headers/x-content-type-options/index.md b/files/en-us/web/http/headers/x-content-type-options/index.md
index ceaed505a5dba5e..fe767860bbd4235 100644
--- a/files/en-us/web/http/headers/x-content-type-options/index.md
+++ b/files/en-us/web/http/headers/x-content-type-options/index.md
@@ -8,37 +8,33 @@ tags:
   - Response Header
 browser-compat: http.headers.X-Content-Type-Options
 ---
-<div>{{HTTPSidebar}}</div>
-
-<p>The <code><strong>X-Content-Type-Options</strong></code> response HTTP header is a
-  marker used by the server to indicate that the <a
-    href="/en-US/docs/Web/HTTP/Basics_of_HTTP/MIME_types">MIME types</a> advertised in the
-  {{HTTPHeader("Content-Type")}} headers should not be changed and be followed. This is a
-  way to opt out of <a
-    href="/en-US/docs/Web/HTTP/Basics_of_HTTP/MIME_types#mime_sniffing">MIME type
-    sniffing</a>, or, in other words, to say that the MIME types are deliberately
-  configured.</p>
-
-<p>This header was introduced by Microsoft in IE 8 as a way for webmasters to block
-  content sniffing that was happening and could transform non-executable MIME types into
-  executable MIME types. Since then, other browsers have introduced it, even if their MIME
-  sniffing algorithms were less aggressive.</p>
-
-<p>Starting with Firefox 72, the opting out of MIME sniffing is also applied to top-level
-  documents if a {{HTTPHeader("Content-type")}} is provided. This can cause HTML web pages
-  to be downloaded instead of being rendered when they are served with a MIME type other
-  than <code>text/html</code>. Make sure to set both headers correctly.</p>
-
-<p>Site security testers usually expect this header to be set.</p>
-
-<div class="notecard note">
-  <p><strong>Note:</strong> <code>X-Content-Type-Options</code> only apply
-    <a href="https://fetch.spec.whatwg.org/#should-response-to-request-be-blocked-due-to-nosniff?">request-blocking due to <code>nosniff</code></a>
-    for <a href="https://fetch.spec.whatwg.org/#concept-request-destination">request destinations</a> of "<code>script</code>"
-    and "<code>style</code>". However, it also
-    <a href="https://chromium.googlesource.com/chromium/src/+/master/services/network/cross_origin_read_blocking_explainer.md#determining-whether-a-response-is-corb_protected">enables Cross-Origin Read Blocking (CORB)</a>
-    protection for HTML, TXT, JSON and XML files (excluding SVG <code>image/svg+xml</code>).</p>
-</div>
+{{HTTPSidebar}}
+
+The **`X-Content-Type-Options`** response HTTP header is a
+marker used by the server to indicate that the [MIME types](/en-US/docs/Web/HTTP/Basics_of_HTTP/MIME_types) advertised in the
+{{HTTPHeader("Content-Type")}} headers should not be changed and be followed. This is a
+way to opt out of [MIME type
+sniffing](/en-US/docs/Web/HTTP/Basics_of_HTTP/MIME_types#mime_sniffing), or, in other words, to say that the MIME types are deliberately
+configured.
+
+This header was introduced by Microsoft in IE 8 as a way for webmasters to block
+content sniffing that was happening and could transform non-executable MIME types into
+executable MIME types. Since then, other browsers have introduced it, even if their MIME
+sniffing algorithms were less aggressive.
+
+Starting with Firefox 72, the opting out of MIME sniffing is also applied to top-level
+documents if a {{HTTPHeader("Content-type")}} is provided. This can cause HTML web pages
+to be downloaded instead of being rendered when they are served with a MIME type other
+than `text/html`. Make sure to set both headers correctly.
+
+Site security testers usually expect this header to be set.
+
+> **Note:** `X-Content-Type-Options` only apply
+> [request-blocking due to `nosniff`](https://fetch.spec.whatwg.org/#should-response-to-request-be-blocked-due-to-nosniff?)
+> for [request destinations](https://fetch.spec.whatwg.org/#concept-request-destination) of "`script`"
+> and "`style`". However, it also
+> [enables Cross-Origin Read Blocking (CORB)](https://chromium.googlesource.com/chromium/src/+/master/services/network/cross_origin_read_blocking_explainer.md#determining-whether-a-response-is-corb_protected)
+> protection for HTML, TXT, JSON and XML files (excluding SVG `image/svg+xml`).
 
 <table class="properties">
   <tbody>
@@ -53,51 +49,41 @@ browser-compat: http.headers.X-Content-Type-Options
   </tbody>
 </table>
 
-<h2 id="Syntax">Syntax</h2>
+## Syntax
 
-<pre class="brush: html">X-Content-Type-Options: nosniff
-</pre>
+```html
+X-Content-Type-Options: nosniff
+```
 
-<h2 id="Directives">Directives</h2>
+## Directives
 
-<dl>
-  <dt><code>nosniff</code></dt>
-  <dd>Blocks a request if the request destination is of type
-    <code>style</code> and the MIME type is not <code>text/css</code>,
-    or of type <code>script</code> and the MIME type is not a <a href="https://html.spec.whatwg.org/multipage/scripting.html#javascript-mime-type">JavaScript MIME type</a>.
-  </dd>
-</dl>
+- `nosniff`
+  - : Blocks a request if the request destination is of type
+    `style` and the MIME type is not `text/css`,
+    or of type `script` and the MIME type is not a [JavaScript MIME type](https://html.spec.whatwg.org/multipage/scripting.html#javascript-mime-type).
 
-<h2 id="Specifications">Specifications</h2>
+## Specifications
 
 {{Specifications}}
 
-<h2 id="Browser_compatibility">Browser compatibility</h2>
-
-<p>{{Compat}}</p>
-
-<h3 id="Browser_specific_notes">Browser specific notes</h3>
-
-<ul>
-  <li>Firefox 72 enables <code>X-Content-Type-Options: nosniff</code> for top-level
-    documents</li>
-</ul>
-
-<h2 id="See_also">See also</h2>
-
-<ul>
-  <li>{{HTTPHeader("Content-Type")}}</li>
-  <li>The <a
-      href="https://blogs.msdn.microsoft.com/ie/2008/09/02/ie8-security-part-vi-beta-2-update/">original
-      definition</a> of X-Content-Type-Options by Microsoft.</li>
-  <li>The <a href="https://observatory.mozilla.org/">Mozilla Observatory</a> tool testing
-    the configuration (including this header) of Web sites for safety and security</li>
-  <li><a
-      href="https://blog.mozilla.org/security/2016/08/26/mitigating-mime-confusion-attacks-in-firefox/">Mitigating
-      MIME Confusion Attacks in Firefox</a></li>
-  <li><a href="https://fetch.spec.whatwg.org/#corb">Cross-Origin Read Blocking (CORB)</a>
-  </li>
-  <li><a
-      href="https://chromium.googlesource.com/chromium/src/+/master/services/network/cross_origin_read_blocking_explainer.md">Google
-      Docs CORB explainer</a></li>
-</ul>
+## Browser compatibility
+
+{{Compat}}
+
+### Browser specific notes
+
+- Firefox 72 enables `X-Content-Type-Options: nosniff` for top-level
+  documents
+
+## See also
+
+- {{HTTPHeader("Content-Type")}}
+- The [original
+  definition](https://blogs.msdn.microsoft.com/ie/2008/09/02/ie8-security-part-vi-beta-2-update/) of X-Content-Type-Options by Microsoft.
+- The [Mozilla Observatory](https://observatory.mozilla.org/) tool testing
+  the configuration (including this header) of Web sites for safety and security
+- [Mitigating
+  MIME Confusion Attacks in Firefox](https://blog.mozilla.org/security/2016/08/26/mitigating-mime-confusion-attacks-in-firefox/)
+- [Cross-Origin Read Blocking (CORB)](https://fetch.spec.whatwg.org/#corb)
+- [Google
+  Docs CORB explainer](https://chromium.googlesource.com/chromium/src/+/master/services/network/cross_origin_read_blocking_explainer.md)
diff --git a/files/en-us/web/http/headers/x-dns-prefetch-control/index.md b/files/en-us/web/http/headers/x-dns-prefetch-control/index.md
index 4cce7c1fff7d584..622d7d981a30c9c 100644
--- a/files/en-us/web/http/headers/x-dns-prefetch-control/index.md
+++ b/files/en-us/web/http/headers/x-dns-prefetch-control/index.md
@@ -2,22 +2,22 @@
 title: X-DNS-Prefetch-Control
 slug: Web/HTTP/Headers/X-DNS-Prefetch-Control
 tags:
-- DNS
-- HTTP
-- X-DNS-Prefetch-Control
-- header
+  - DNS
+  - HTTP
+  - X-DNS-Prefetch-Control
+  - header
 browser-compat: http.headers.X-DNS-Prefetch-Control
 ---
-<div>{{HTTPSidebar}}</div>
+{{HTTPSidebar}}
 
-<p>The <strong><code>X-DNS-Prefetch-Control</code></strong> HTTP response header controls
-  DNS prefetching, a feature by which browsers proactively perform domain name resolution
-  on both links that the user may choose to follow as well as URLs for items referenced by
-  the document, including images, CSS, JavaScript, and so forth.</p>
+The **`X-DNS-Prefetch-Control`** HTTP response header controls
+DNS prefetching, a feature by which browsers proactively perform domain name resolution
+on both links that the user may choose to follow as well as URLs for items referenced by
+the document, including images, CSS, JavaScript, and so forth.
 
-<p>This prefetching is performed in the background, so that the {{glossary("DNS")}} is
-  likely to have been resolved by the time the referenced items are needed. This reduces
-  latency when the user clicks a link.</p>
+This prefetching is performed in the background, so that the {{glossary("DNS")}} is
+likely to have been resolved by the time the referenced items are needed. This reduces
+latency when the user clicks a link.
 
 <table class="properties">
   <tbody>
@@ -32,95 +32,94 @@ browser-compat: http.headers.X-DNS-Prefetch-Control
   </tbody>
 </table>
 
-<h2 id="Syntax">Syntax</h2>
+## Syntax
 
-<pre class="brush: html">X-DNS-Prefetch-Control: on
+```html
+X-DNS-Prefetch-Control: on
 X-DNS-Prefetch-Control: off
-</pre>
+```
 
-<h3 id="Directives">Directives</h3>
+### Directives
 
-<dl>
-  <dt>on</dt>
-  <dd>Enables DNS prefetching. This is what browsers do, if they support the feature, when
-    this header is not present</dd>
-  <dt>off</dt>
-  <dd>Disables DNS prefetching. This is useful if you don't control the link on the pages,
-    or know that you don't want to leak information to these domains.</dd>
-</dl>
+- on
+  - : Enables DNS prefetching. This is what browsers do, if they support the feature, when
+    this header is not present
+- off
+  - : Disables DNS prefetching. This is useful if you don't control the link on the pages,
+    or know that you don't want to leak information to these domains.
 
-<h2 id="Description">Description</h2>
+## Description
 
-<p>DNS requests are very small in terms of bandwidth, but latency can be quite high,
-  especially on mobile networks. By speculatively prefetching DNS results, latency can be
-  reduced significantly at certain times, such as when the user clicks the link. In some
-  cases, latency can be reduced by a second.</p>
+DNS requests are very small in terms of bandwidth, but latency can be quite high,
+especially on mobile networks. By speculatively prefetching DNS results, latency can be
+reduced significantly at certain times, such as when the user clicks the link. In some
+cases, latency can be reduced by a second.
 
-<p>The implementation of this prefetching in some browsers allows domain name resolution
-  to occur in parallel with (instead of in serial with) the fetching of actual page
-  content. By doing this, the high-latency domain name resolution process doesn't cause
-  any delay while fetching content.</p>
+The implementation of this prefetching in some browsers allows domain name resolution
+to occur in parallel with (instead of in serial with) the fetching of actual page
+content. By doing this, the high-latency domain name resolution process doesn't cause
+any delay while fetching content.
 
-<p>Page load times – especially on mobile networks – can be measurably improved in this
-  way. If the domain names for images can be resolved in advance of the images being
-  requested, pages that load many images can see an improvement of 5% or more in the time
-  of loading images.</p>
+Page load times – especially on mobile networks – can be measurably improved in this
+way. If the domain names for images can be resolved in advance of the images being
+requested, pages that load many images can see an improvement of 5% or more in the time
+of loading images.
 
-<h3 id="Configuring_prefetching_in_the_browser">Configuring prefetching in the browser
-</h3>
+### Configuring prefetching in the browser
 
-<p>In general, you don't need to do anything to manage prefetching. However, the user may
-  wish to disable prefetching. On Firefox, this can be done by setting the
-  <code>network.dns.disablePrefetch</code> preference to <code>true</code>.</p>
+In general, you don't need to do anything to manage prefetching. However, the user may
+wish to disable prefetching. On Firefox, this can be done by setting the
+`network.dns.disablePrefetch` preference to `true`.
 
-<p>Also, by default, prefetching of embedded link hostnames is not performed on documents
-  loaded over {{glossary("HTTPS")}}. On Firefox, this can be changed by setting the
-  <code>network.dns.disablePrefetchFromHTTPS</code> preference to <code>false</code>.</p>
+Also, by default, prefetching of embedded link hostnames is not performed on documents
+loaded over {{glossary("HTTPS")}}. On Firefox, this can be changed by setting the
+`network.dns.disablePrefetchFromHTTPS` preference to `false`.
 
-<h2 id="Examples">Examples</h2>
+## Examples
 
-<h3 id="Turning_on_and_off_prefetching">Turning on and off prefetching</h3>
+### Turning on and off prefetching
 
-<p>You can either send the <code>X-DNS-Prefetch-Control</code> header server-side, or from
-  individual documents, using the {{ htmlattrxref("http-equiv", "meta") }} attribute on
-  the {{ HTMLElement("meta") }} element, like this:</p>
+You can either send the `X-DNS-Prefetch-Control` header server-side, or from
+individual documents, using the {{ htmlattrxref("http-equiv", "meta") }} attribute on
+the {{ HTMLElement("meta") }} element, like this:
 
-<pre class="brush: html">&lt;meta http-equiv="x-dns-prefetch-control" content="off"&gt;
-</pre>
+```html
+<meta http-equiv="x-dns-prefetch-control" content="off">
+```
 
-<p>You can reverse this setting by setting <code>content</code> to "<code>on</code>".</p>
+You can reverse this setting by setting `content` to "`on`".
 
-<h3 id="Forcing_lookup_of_specific_hostnames">Forcing lookup of specific hostnames</h3>
+### Forcing lookup of specific hostnames
 
-<p>You can force the lookup of specific hostnames without providing specific anchors using
-  that hostname by using the {{ htmlattrxref("rel","link") }} attribute on the {{
-  HTMLElement("link") }} element with a <a href="/en-US/docs/Web/HTML/Link_types">link
-    type</a> of <code>dns-prefetch</code>:</p>
+You can force the lookup of specific hostnames without providing specific anchors using
+that hostname by using the {{ htmlattrxref("rel","link") }} attribute on the {{
+  HTMLElement("link") }} element with a [link
+type](/en-US/docs/Web/HTML/Link_types) of `dns-prefetch`:
 
-<pre class="brush: html">&lt;link rel="dns-prefetch" href="https://www.mozilla.org/contribute/"&gt;
-</pre>
+```html
+<link rel="dns-prefetch" href="https://www.mozilla.org/contribute/">
+```
 
-<p>In this example, the domain name <code>www.mozilla.org/contribute</code> will be pre-resolved.</p>
+In this example, the domain name `www.mozilla.org/contribute` will be pre-resolved.
 
-<p>Similarly, the link element can be used to resolve hostnames without providing a
-  complete URL, but only, by preceding the hostname with two slashes:</p>
+Similarly, the link element can be used to resolve hostnames without providing a
+complete URL, but only, by preceding the hostname with two slashes:
 
-<pre class="brush: html">&lt;link rel="dns-prefetch" href="//www.mozilla.org/contribute/"&gt;
-</pre>
+```html
+<link rel="dns-prefetch" href="//www.mozilla.org/contribute/">
+```
 
-<p>Forced prefetching of hostnames might be useful, for example, on the homepage of a site
-  to force pre-resolution of domain names that are referenced frequently throughout the
-  site even though they are not used on the home page itself. This will improve the
-  overall performance of site even though the performance of the home page may not be
-  affected.</p>
+Forced prefetching of hostnames might be useful, for example, on the homepage of a site
+to force pre-resolution of domain names that are referenced frequently throughout the
+site even though they are not used on the home page itself. This will improve the
+overall performance of site even though the performance of the home page may not be
+affected.
 
-<h2 id="Browser_compatibility">Browser compatibility</h2>
+## Browser compatibility
 
-<p>{{Compat}}</p>
+{{Compat}}
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
-  <li><a href="https://bitsup.blogspot.com/2008/11/dns-prefetching-for-firefox.html">DNS Prefetching for Firefox (blog post)</a></li>
-  <li><a href="https://dev.chromium.org/developers/design-documents/dns-prefetching">Google Chrome handles DNS prefetching control</a></li>
-</ul>
+- [DNS Prefetching for Firefox (blog post)](https://bitsup.blogspot.com/2008/11/dns-prefetching-for-firefox.html)
+- [Google Chrome handles DNS prefetching control](https://dev.chromium.org/developers/design-documents/dns-prefetching)
diff --git a/files/en-us/web/http/headers/x-forwarded-for/index.md b/files/en-us/web/http/headers/x-forwarded-for/index.md
index 42d7e09d52e3c41..e716071f899dc4c 100644
--- a/files/en-us/web/http/headers/x-forwarded-for/index.md
+++ b/files/en-us/web/http/headers/x-forwarded-for/index.md
@@ -2,33 +2,32 @@
 title: X-Forwarded-For
 slug: Web/HTTP/Headers/X-Forwarded-For
 tags:
-- HTTP
-- HTTP Header
-- Non-standard
-- Reference
-- Request header
-- header
+  - HTTP
+  - HTTP Header
+  - Non-standard
+  - Reference
+  - Request header
+  - header
 browser-compat: http.headers.X-Forwarded-For
 ---
-<div>{{HTTPSidebar}}</div>
+{{HTTPSidebar}}
 
-<p>The <strong><code>X-Forwarded-For</code></strong> (XFF) header is a de-facto standard
-  header for identifying the originating IP address of a client connecting to a web server
-  through an HTTP proxy or a load balancer. When traffic is intercepted between clients
-  and servers, server access logs contain the IP address of the proxy or load balancer
-  only. To see the original IP address of the client, the <code>X-Forwarded-For</code>
-  request header is used.</p>
+The **`X-Forwarded-For`** (XFF) header is a de-facto standard
+header for identifying the originating IP address of a client connecting to a web server
+through an HTTP proxy or a load balancer. When traffic is intercepted between clients
+and servers, server access logs contain the IP address of the proxy or load balancer
+only. To see the original IP address of the client, the `X-Forwarded-For`
+request header is used.
 
-<p>This header is used for debugging, statistics, and generating location-dependent
-  content and by design it exposes privacy sensitive information, such as the IP address
-  of the client. Therefore the user's privacy must be kept in mind when deploying this
-  header.</p>
+This header is used for debugging, statistics, and generating location-dependent
+content and by design it exposes privacy sensitive information, such as the IP address
+of the client. Therefore the user's privacy must be kept in mind when deploying this
+header.
 
-<p>A standardized version of this header is the HTTP {{HTTPHeader("Forwarded")}} header.
-</p>
+A standardized version of this header is the HTTP {{HTTPHeader("Forwarded")}} header.
 
-<p><code>X-Forwarded-For</code> is also an email-header indicating that an email-message
-  was forwarded from another account.</p>
+`X-Forwarded-For` is also an email-header indicating that an email-message
+was forwarded from another account.
 
 <table class="properties">
   <tbody>
@@ -43,51 +42,46 @@ browser-compat: http.headers.X-Forwarded-For
   </tbody>
 </table>
 
-<h2 id="Syntax">Syntax</h2>
+## Syntax
 
-<pre class="brush: html">X-Forwarded-For: &lt;client&gt;, &lt;proxy1&gt;, &lt;proxy2&gt;
-</pre>
+```html
+X-Forwarded-For: <client>, <proxy1>, <proxy2>
+```
 
-<h2 id="Directives">Directives</h2>
+## Directives
 
-<dl>
-  <dt>&lt;client&gt;</dt>
-  <dd>The client IP address</dd>
-  <dt>&lt;proxy1&gt;, &lt;proxy2&gt;</dt>
-  <dd>If a request goes through multiple proxies, the IP addresses of each successive
+- \<client>
+  - : The client IP address
+- \<proxy1>, \<proxy2>
+  - : If a request goes through multiple proxies, the IP addresses of each successive
     proxy is listed. This means, the right-most IP address is the IP address of the most
     recent proxy and the left-most IP address is the IP address of the originating client.
-  </dd>
-</dl>
 
-<h2 id="Examples">Examples</h2>
+## Examples
 
-<pre>X-Forwarded-For: 2001:db8:85a3:8d3:1319:8a2e:370:7348
+    X-Forwarded-For: 2001:db8:85a3:8d3:1319:8a2e:370:7348
 
-X-Forwarded-For: 203.0.113.195
+    X-Forwarded-For: 203.0.113.195
 
-X-Forwarded-For: 203.0.113.195, 70.41.3.18, 150.172.238.178
-</pre>
+    X-Forwarded-For: 203.0.113.195, 70.41.3.18, 150.172.238.178
 
-<p>Other non-standard forms:</p>
+Other non-standard forms:
 
-<pre># Used for some Google services
-X-ProxyUser-Ip: 203.0.113.19</pre>
+    # Used for some Google services
+    X-ProxyUser-Ip: 203.0.113.19
 
-<h2 id="Specifications">Specifications</h2>
+## Specifications
 
-<p>Not part of any current specification. The standardized version of this header is
-  {{HTTPHeader("Forwarded")}}.</p>
+Not part of any current specification. The standardized version of this header is
+{{HTTPHeader("Forwarded")}}.
 
-<h2 id="Browser_compatibility">Browser compatibility</h2>
+## Browser compatibility
 
-<p>{{Compat}}</p>
+{{Compat}}
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
-  <li>{{HTTPHeader("Forwarded")}}</li>
-  <li>{{HTTPHeader("X-Forwarded-Host")}}</li>
-  <li>{{HTTPHeader("X-Forwarded-Proto")}}</li>
-  <li>{{HTTPHeader("Via")}}</li>
-</ul>
+- {{HTTPHeader("Forwarded")}}
+- {{HTTPHeader("X-Forwarded-Host")}}
+- {{HTTPHeader("X-Forwarded-Proto")}}
+- {{HTTPHeader("Via")}}
diff --git a/files/en-us/web/http/headers/x-forwarded-host/index.md b/files/en-us/web/http/headers/x-forwarded-host/index.md
index 30e5fe043bbf079..b79ca66e5c3c696 100644
--- a/files/en-us/web/http/headers/x-forwarded-host/index.md
+++ b/files/en-us/web/http/headers/x-forwarded-host/index.md
@@ -2,31 +2,30 @@
 title: X-Forwarded-Host
 slug: Web/HTTP/Headers/X-Forwarded-Host
 tags:
-- HTTP
-- HTTP Header
-- Non-standard
-- Reference
-- Request header
-- header
+  - HTTP
+  - HTTP Header
+  - Non-standard
+  - Reference
+  - Request header
+  - header
 browser-compat: http.headers.X-Forwarded-Host
 ---
-<div>{{HTTPSidebar}}</div>
+{{HTTPSidebar}}
 
-<p>The <strong><code>X-Forwarded-Host</code></strong> (XFH) header is a de-facto standard
-  header for identifying the original host requested by the client in the
-  {{HTTPHeader("Host")}} HTTP request header.</p>
+The **`X-Forwarded-Host`** (XFH) header is a de-facto standard
+header for identifying the original host requested by the client in the
+{{HTTPHeader("Host")}} HTTP request header.
 
-<p>Host names and ports of reverse proxies (load balancers, CDNs) may differ from the
-  origin server handling the request, in that case the <code>X-Forwarded-Host</code>
-  header is useful to determine which Host was originally used.</p>
+Host names and ports of reverse proxies (load balancers, CDNs) may differ from the
+origin server handling the request, in that case the `X-Forwarded-Host`
+header is useful to determine which Host was originally used.
 
-<p>This header is used for debugging, statistics, and generating location-dependent
-  content and by design it exposes privacy sensitive information, such as the IP address
-  of the client. Therefore the user's privacy must be kept in mind when deploying this
-  header.</p>
+This header is used for debugging, statistics, and generating location-dependent
+content and by design it exposes privacy sensitive information, such as the IP address
+of the client. Therefore the user's privacy must be kept in mind when deploying this
+header.
 
-<p>A standardized version of this header is the HTTP {{HTTPHeader("Forwarded")}} header.
-</p>
+A standardized version of this header is the HTTP {{HTTPHeader("Forwarded")}} header.
 
 <table class="properties">
   <tbody>
@@ -41,37 +40,33 @@ browser-compat: http.headers.X-Forwarded-Host
   </tbody>
 </table>
 
-<h2 id="Syntax">Syntax</h2>
+## Syntax
 
-<pre class="brush: html">X-Forwarded-Host: &lt;host&gt;
-</pre>
+```html
+X-Forwarded-Host: <host>
+```
 
-<h2 id="Directives">Directives</h2>
+## Directives
 
-<dl>
-  <dt>&lt;host&gt;</dt>
-  <dd>The domain name of the forwarded server.</dd>
-</dl>
+- \<host>
+  - : The domain name of the forwarded server.
 
-<h2 id="Examples">Examples</h2>
+## Examples
 
-<pre>X-Forwarded-Host: id42.example-cdn.com
-</pre>
+    X-Forwarded-Host: id42.example-cdn.com
 
-<h2 id="Specifications">Specifications</h2>
+## Specifications
 
-<p>Not part of any current specification. The standardized version of this header is
-  {{HTTPHeader("Forwarded")}}.</p>
+Not part of any current specification. The standardized version of this header is
+{{HTTPHeader("Forwarded")}}.
 
-<h2 id="Browser_compatibility">Browser compatibility</h2>
+## Browser compatibility
 
-<p>{{Compat}}</p>
+{{Compat}}
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
-  <li>{{HTTPHeader("Host")}}</li>
-  <li>{{HTTPHeader("Forwarded")}}</li>
-  <li>{{HTTPHeader("X-Forwarded-For")}}</li>
-  <li>{{HTTPHeader("X-Forwarded-Proto")}}</li>
-</ul>
+- {{HTTPHeader("Host")}}
+- {{HTTPHeader("Forwarded")}}
+- {{HTTPHeader("X-Forwarded-For")}}
+- {{HTTPHeader("X-Forwarded-Proto")}}
diff --git a/files/en-us/web/http/headers/x-forwarded-proto/index.md b/files/en-us/web/http/headers/x-forwarded-proto/index.md
index ff36ac9b1779db5..b1c66eddd3dc19e 100644
--- a/files/en-us/web/http/headers/x-forwarded-proto/index.md
+++ b/files/en-us/web/http/headers/x-forwarded-proto/index.md
@@ -2,25 +2,24 @@
 title: X-Forwarded-Proto
 slug: Web/HTTP/Headers/X-Forwarded-Proto
 tags:
-- HTTP
-- HTTP Header
-- Non-standard
-- Reference
-- Request header
-- header
+  - HTTP
+  - HTTP Header
+  - Non-standard
+  - Reference
+  - Request header
+  - header
 browser-compat: http.headers.X-Forwarded-Proto
 ---
-<div>{{HTTPSidebar}}</div>
+{{HTTPSidebar}}
 
-<p>The <strong><code>X-Forwarded-Proto</code></strong> (XFP) header is a de-facto standard
-  header for identifying the protocol (HTTP or HTTPS) that a client used to connect to
-  your proxy or load balancer. Your server access logs contain the protocol used between
-  the server and the load balancer, but not the protocol used between the client and the
-  load balancer. To determine the protocol used between the client and the load balancer,
-  the <code>X-Forwarded-Proto</code> request header can be used.</p>
+The **`X-Forwarded-Proto`** (XFP) header is a de-facto standard
+header for identifying the protocol (HTTP or HTTPS) that a client used to connect to
+your proxy or load balancer. Your server access logs contain the protocol used between
+the server and the load balancer, but not the protocol used between the client and the
+load balancer. To determine the protocol used between the client and the load balancer,
+the `X-Forwarded-Proto` request header can be used.
 
-<p>A standardized version of this header is the HTTP {{HTTPHeader("Forwarded")}} header.
-</p>
+A standardized version of this header is the HTTP {{HTTPHeader("Forwarded")}} header.
 
 <table class="properties">
   <tbody>
@@ -35,45 +34,41 @@ browser-compat: http.headers.X-Forwarded-Proto
   </tbody>
 </table>
 
-<h2 id="Syntax">Syntax</h2>
+## Syntax
 
-<pre class="brush: html">X-Forwarded-Proto: &lt;protocol&gt;
-</pre>
+```html
+X-Forwarded-Proto: <protocol>
+```
 
-<h2 id="Directives">Directives</h2>
+## Directives
 
-<dl>
-  <dt>&lt;protocol&gt;</dt>
-  <dd>The forwarded protocol (http or https).</dd>
-</dl>
+- \<protocol>
+  - : The forwarded protocol (http or https).
 
-<h2 id="Examples">Examples</h2>
+## Examples
 
-<pre>X-Forwarded-Proto: https</pre>
+    X-Forwarded-Proto: https
 
-<p>Other non-standard forms:</p>
+Other non-standard forms:
 
-<pre># Microsoft
-Front-End-Https: on
+    # Microsoft
+    Front-End-Https: on
 
-X-Forwarded-Protocol: https
-X-Forwarded-Ssl: on
-X-Url-Scheme: https
-</pre>
+    X-Forwarded-Protocol: https
+    X-Forwarded-Ssl: on
+    X-Url-Scheme: https
 
-<h2 id="Specifications">Specifications</h2>
+## Specifications
 
-<p>Not part of any current specification. The standardized version of this header is
-  {{HTTPHeader("Forwarded")}}.</p>
+Not part of any current specification. The standardized version of this header is
+{{HTTPHeader("Forwarded")}}.
 
-<h2 id="Browser_compatibility">Browser compatibility</h2>
+## Browser compatibility
 
-<p>{{Compat}}</p>
+{{Compat}}
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
-  <li>{{HTTPHeader("Forwarded")}}</li>
-  <li>{{HTTPHeader("X-Forwarded-For")}}</li>
-  <li>{{HTTPHeader("X-Forwarded-Host")}}</li>
-</ul>
+- {{HTTPHeader("Forwarded")}}
+- {{HTTPHeader("X-Forwarded-For")}}
+- {{HTTPHeader("X-Forwarded-Host")}}
diff --git a/files/en-us/web/http/headers/x-frame-options/index.md b/files/en-us/web/http/headers/x-frame-options/index.md
index 7422c9d9e3d55b7..4039cdd84063c8f 100644
--- a/files/en-us/web/http/headers/x-frame-options/index.md
+++ b/files/en-us/web/http/headers/x-frame-options/index.md
@@ -10,134 +10,123 @@ tags:
   - nginx
 browser-compat: http.headers.X-Frame-Options
 ---
-<div>{{HTTPSidebar}}</div>
+{{HTTPSidebar}}
 
-<p>The <strong><code>X-Frame-Options</code></strong> <a href="/en-US/docs/Web/HTTP">HTTP</a> response header can be used to indicate whether or not a browser should be allowed to render a page in a {{HTMLElement("frame")}}, {{HTMLElement("iframe")}}, {{HTMLElement("embed")}} or {{HTMLElement("object")}}. Sites can use this to avoid <a href="/en-US/docs/Web/Security/Types_of_attacks#click-jacking">click-jacking</a> attacks, by ensuring that their content is not embedded into other sites.</p>
+The **`X-Frame-Options`** [HTTP](/en-US/docs/Web/HTTP) response header can be used to indicate whether or not a browser should be allowed to render a page in a {{HTMLElement("frame")}}, {{HTMLElement("iframe")}}, {{HTMLElement("embed")}} or {{HTMLElement("object")}}. Sites can use this to avoid [click-jacking](/en-US/docs/Web/Security/Types_of_attacks#click-jacking) attacks, by ensuring that their content is not embedded into other sites.
 
-<p>The added security is provided only if the user accessing the document is using a browser that supports <code>X-Frame-Options</code>.</p>
+The added security is provided only if the user accessing the document is using a browser that supports `X-Frame-Options`.
 
-<div class="notecard note">
-  <p><strong>Note:</strong> The {{HTTPHeader("Content-Security-Policy")}} HTTP header has a {{HTTPHeader("Content-Security-Policy/frame-ancestors", "frame-ancestors")}} directive which <a href="https://www.w3.org/TR/CSP2/#frame-ancestors-and-frame-options">obsoletes</a> this header for supporting browsers.</p>
-</div>
+> **Note:** The {{HTTPHeader("Content-Security-Policy")}} HTTP header has a {{HTTPHeader("Content-Security-Policy/frame-ancestors", "frame-ancestors")}} directive which [obsoletes](https://www.w3.org/TR/CSP2/#frame-ancestors-and-frame-options) this header for supporting browsers.
 
 <table class="properties">
- <tbody>
-  <tr>
-   <th scope="row">Header type</th>
-   <td>{{Glossary("Response header")}}</td>
-  </tr>
-  <tr>
-   <th scope="row">{{Glossary("Forbidden header name")}}</th>
-   <td>no</td>
-  </tr>
- </tbody>
+  <tbody>
+    <tr>
+      <th scope="row">Header type</th>
+      <td>{{Glossary("Response header")}}</td>
+    </tr>
+    <tr>
+      <th scope="row">{{Glossary("Forbidden header name")}}</th>
+      <td>no</td>
+    </tr>
+  </tbody>
 </table>
 
-<h2 id="Syntax">Syntax</h2>
+## Syntax
 
-<p>There are two possible directives for <code>X-Frame-Options</code>:</p>
+There are two possible directives for `X-Frame-Options`:
 
-<pre class="brush: html">X-Frame-Options: DENY
+```html
+X-Frame-Options: DENY
 X-Frame-Options: SAMEORIGIN
-</pre>
+```
 
-<h3 id="Directives">Directives</h3>
+### Directives
 
-<p>If you specify <code>DENY</code>, not only will attempts to load the page in a frame fail when loaded from other sites, attempts to do so will fail when loaded from the same site. On the other hand, if you specify <code>SAMEORIGIN</code>, you can still use the page in a frame as long as the site including it in a frame is the same as the one serving the page.</p>
+If you specify `DENY`, not only will attempts to load the page in a frame fail when loaded from other sites, attempts to do so will fail when loaded from the same site. On the other hand, if you specify `SAMEORIGIN`, you can still use the page in a frame as long as the site including it in a frame is the same as the one serving the page.
 
-<dl>
- <dt><code>DENY</code></dt>
- <dd>The page cannot be displayed in a frame, regardless of the site attempting to do so.</dd>
- <dt><code>SAMEORIGIN</code></dt>
- <dd>The page can only be displayed in a frame on the same origin as the page itself. The spec leaves it up to browser vendors to decide whether this option applies to the top level, the parent, or the whole chain, although it is argued that the option is not very useful unless all ancestors are also in the same origin (see {{bug(725490)}}). Also see {{anch("Browser compatibility")}} for support details.</dd>
- <dt><code>ALLOW-FROM <em>uri</em></code> {{deprecated_inline}}</dt>
- <dd>This is an obsolete directive that no longer works in modern browsers. Don't use it. In supporting legacy browsers, a page can be displayed in a frame only on the specified origin <em>uri</em>. Note that in the legacy Firefox implementation this still suffered from the same problem as <code>SAMEORIGIN</code> did — it doesn't check the frame ancestors to see if they are in the same origin. The {{HTTPHeader("Content-Security-Policy")}} HTTP header has a {{HTTPHeader("Content-Security-Policy/frame-ancestors", "frame-ancestors")}} directive which you can use instead.</dd>
-</dl>
+- `DENY`
+  - : The page cannot be displayed in a frame, regardless of the site attempting to do so.
+- `SAMEORIGIN`
+  - : The page can only be displayed in a frame on the same origin as the page itself. The spec leaves it up to browser vendors to decide whether this option applies to the top level, the parent, or the whole chain, although it is argued that the option is not very useful unless all ancestors are also in the same origin (see {{bug(725490)}}). Also see {{anch("Browser compatibility")}} for support details.
+- `ALLOW-FROM uri` {{deprecated_inline}}
+  - : This is an obsolete directive that no longer works in modern browsers. Don't use it. In supporting legacy browsers, a page can be displayed in a frame only on the specified origin _uri_. Note that in the legacy Firefox implementation this still suffered from the same problem as `SAMEORIGIN` did — it doesn't check the frame ancestors to see if they are in the same origin. The {{HTTPHeader("Content-Security-Policy")}} HTTP header has a {{HTTPHeader("Content-Security-Policy/frame-ancestors", "frame-ancestors")}} directive which you can use instead.
 
-<h2 id="Examples">Examples</h2>
+## Examples
 
-<div class="notecard note">
-  <p><strong>Note:</strong> Setting X-Frame-Options inside the {{HTMLElement("meta")}} element is useless! For instance, <code>&lt;meta http-equiv="X-Frame-Options" content="deny"&gt;</code> has no effect. Do not use it! <code>X-Frame-Options</code> works only by setting through the HTTP header, as in the examples below.</p>
-</div>
+> **Note:** Setting X-Frame-Options inside the {{HTMLElement("meta")}} element is useless! For instance, `<meta http-equiv="X-Frame-Options" content="deny">` has no effect. Do not use it! `X-Frame-Options` works only by setting through the HTTP header, as in the examples below.
 
-<h3 id="Configuring_Apache">Configuring Apache</h3>
+### Configuring Apache
 
-<p>To configure Apache to send the <code>X-Frame-Options</code> header for all pages, add this to your site's configuration:</p>
+To configure Apache to send the `X-Frame-Options` header for all pages, add this to your site's configuration:
 
-<pre>Header always set X-Frame-Options "SAMEORIGIN"
-</pre>
+    Header always set X-Frame-Options "SAMEORIGIN"
 
-<p>To configure Apache to set the <code>X-Frame-Options</code> DENY, add this to your site's configuration:</p>
+To configure Apache to set the `X-Frame-Options` DENY, add this to your site's configuration:
 
-<pre>Header set X-Frame-Options "DENY"
-</pre>
+    Header set X-Frame-Options "DENY"
 
-<h3 id="Configuring_nginx">Configuring nginx</h3>
+### Configuring nginx
 
-<p>To configure nginx to send the <code>X-Frame-Options</code> header, add this either to your http, server or location configuration:</p>
+To configure nginx to send the `X-Frame-Options` header, add this either to your http, server or location configuration:
 
-<pre>add_header X-Frame-Options SAMEORIGIN always;
-</pre>
+    add_header X-Frame-Options SAMEORIGIN always;
 
-<h3 id="Configuring_IIS">Configuring IIS</h3>
+### Configuring IIS
 
-<p>To configure IIS to send the <code>X-Frame-Options</code> header, add this to your site's <code>Web.config</code> file:</p>
+To configure IIS to send the `X-Frame-Options` header, add this to your site's `Web.config` file:
 
-<pre>&lt;system.webServer&gt;
-  ...
+    <system.webServer>
+      ...
 
-  &lt;httpProtocol&gt;
-    &lt;customHeaders&gt;
-      &lt;add name="X-Frame-Options" value="SAMEORIGIN" /&gt;
-    &lt;/customHeaders&gt;
-  &lt;/httpProtocol&gt;
+      <httpProtocol>
+        <customHeaders>
+          <add name="X-Frame-Options" value="SAMEORIGIN" />
+        </customHeaders>
+      </httpProtocol>
 
-  ...
-&lt;/system.webServer&gt;
-</pre>
+      ...
+    </system.webServer>
 
-<p>Or see this <a href="https://support.office.com/en-us/article/Mitigating-framesniffing-with-the-X-Frame-Options-header-1911411b-b51e-49fd-9441-e8301dcdcd79">Microsoft support article on setting this configuration using the IIS Manager</a> user interface.</p>
+Or see this [Microsoft support article on setting this configuration using the IIS Manager](https://support.office.com/en-us/article/Mitigating-framesniffing-with-the-X-Frame-Options-header-1911411b-b51e-49fd-9441-e8301dcdcd79) user interface.
 
-<h3 id="Configuring_HAProxy">Configuring HAProxy</h3>
+### Configuring HAProxy
 
-<p>To configure HAProxy to send the <code>X-Frame-Options</code> header, add this to your front-end, listen, or backend configuration:</p>
+To configure HAProxy to send the `X-Frame-Options` header, add this to your front-end, listen, or backend configuration:
 
-<pre>rspadd X-Frame-Options:\ SAMEORIGIN
-</pre>
+    rspadd X-Frame-Options:\ SAMEORIGIN
 
-<p>Alternatively, in newer versions:</p>
+Alternatively, in newer versions:
 
-<pre>http-response set-header X-Frame-Options SAMEORIGIN
-</pre>
+    http-response set-header X-Frame-Options SAMEORIGIN
 
-<h3 id="Configuring_Express">Configuring Express</h3>
+### Configuring Express
 
-<p>To configure Express to send the <code>X-Frame-Options</code> header, you can use <a href="https://helmetjs.github.io/">helmet</a> which uses <a href="https://helmetjs.github.io/docs/frameguard/">frameguard</a> to set the header. Add this to your server configuration:</p>
+To configure Express to send the `X-Frame-Options` header, you can use [helmet](https://helmetjs.github.io/) which uses [frameguard](https://helmetjs.github.io/docs/frameguard/) to set the header. Add this to your server configuration:
 
-<pre class="brush: js">const helmet = require('helmet');
+```js
+const helmet = require('helmet');
 const app = express();
 app.use(helmet.frameguard({ action: 'SAMEORIGIN' }));
-</pre>
+```
 
-<p>Alternatively, you can use frameguard directly:</p>
+Alternatively, you can use frameguard directly:
 
-<pre class="brush: js">const frameguard = require('frameguard')
+```js
+const frameguard = require('frameguard')
 app.use(frameguard({ action: 'SAMEORIGIN' }))
-</pre>
+```
 
-<h2 id="Specifications">Specifications</h2>
+## Specifications
 
 {{Specifications}}
 
-<h2 id="Browser_compatibility">Browser compatibility</h2>
+## Browser compatibility
 
-<p>{{Compat}}</p>
+{{Compat}}
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
- <li>{{HTTPHeader("Content-Security-Policy")}} directive {{HTTPHeader("Content-Security-Policy/frame-ancestors", "frame-ancestors")}}</li>
- <li><a href="https://datatracker.ietf.org/doc/html/rfc7034">HTTP Header Field X-Frame-Options - RFC 7034</a></li>
- <li><a href="https://docs.microsoft.com/en-us/archive/blogs/ie/ie8-security-part-vii-clickjacking-defenses">ClickJacking Defenses - IEBlog</a></li>
- <li><a href="https://docs.microsoft.com/en-us/archive/blogs/ieinternals/combating-clickjacking-with-x-frame-options">Combating ClickJacking with X-Frame-Options - IEInternals</a></li>
-</ul>
+- {{HTTPHeader("Content-Security-Policy")}} directive {{HTTPHeader("Content-Security-Policy/frame-ancestors", "frame-ancestors")}}
+- [HTTP Header Field X-Frame-Options - RFC 7034](https://datatracker.ietf.org/doc/html/rfc7034)
+- [ClickJacking Defenses - IEBlog](https://docs.microsoft.com/en-us/archive/blogs/ie/ie8-security-part-vii-clickjacking-defenses)
+- [Combating ClickJacking with X-Frame-Options - IEInternals](https://docs.microsoft.com/en-us/archive/blogs/ieinternals/combating-clickjacking-with-x-frame-options)
diff --git a/files/en-us/web/http/headers/x-xss-protection/index.md b/files/en-us/web/http/headers/x-xss-protection/index.md
index 6dd11007e2e6b3c..98430f9562e238c 100644
--- a/files/en-us/web/http/headers/x-xss-protection/index.md
+++ b/files/en-us/web/http/headers/x-xss-protection/index.md
@@ -9,87 +9,86 @@ tags:
   - header
 browser-compat: http.headers.X-XSS-Protection
 ---
-<div>{{HTTPSidebar}}</div>
+{{HTTPSidebar}}
 
-<p>The HTTP <strong><code>X-XSS-Protection</code></strong> response header is a feature of Internet Explorer, Chrome and Safari that stops pages from loading when they detect reflected cross-site scripting ({{Glossary("Cross-site_scripting", "XSS")}}) attacks. Although these protections are largely unnecessary in modern browsers when sites implement a strong {{HTTPHeader("Content-Security-Policy")}} that disables the use of inline JavaScript (<code>'unsafe-inline'</code>), they can still provide protections for users of older web browsers that don't yet support {{Glossary("CSP")}}.</p>
+The HTTP **`X-XSS-Protection`** response header is a feature of Internet Explorer, Chrome and Safari that stops pages from loading when they detect reflected cross-site scripting ({{Glossary("Cross-site_scripting", "XSS")}}) attacks. Although these protections are largely unnecessary in modern browsers when sites implement a strong {{HTTPHeader("Content-Security-Policy")}} that disables the use of inline JavaScript (`'unsafe-inline'`), they can still provide protections for users of older web browsers that don't yet support {{Glossary("CSP")}}.
 
-<div class="notecard note">
-  <p><strong>Note:</strong> </p>
-  <ul>
-    <li>Chrome has <a href="https://www.chromestatus.com/feature/5021976655560704">removed their XSS Auditor</a></li>
-    <li>Firefox has not, and <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=528661">will not implement <code>X-XSS-Protection</code></a></li>
-    <li>Edge has <a href="https://blogs.windows.com/windowsexperience/2018/07/25/announcing-windows-10-insider-preview-build-17723-and-build-18204/">retired their XSS filter</a></li>
-  </ul>
-  <p>This means that if you do not need to support legacy browsers, it is recommended that you use <code><a href="/en-US/docs/Web/HTTP/Headers/Content-Security-Policy">Content-Security-Policy</a></code> without allowing <code>unsafe-inline</code> scripts instead.</p>
-</div>
+> **Note:**
+>
+> - Chrome has [removed their XSS Auditor](https://www.chromestatus.com/feature/5021976655560704)
+> - Firefox has not, and [will not implement `X-XSS-Protection`](https://bugzilla.mozilla.org/show_bug.cgi?id=528661)
+> - Edge has [retired their XSS filter](https://blogs.windows.com/windowsexperience/2018/07/25/announcing-windows-10-insider-preview-build-17723-and-build-18204/)
+>
+> This means that if you do not need to support legacy browsers, it is recommended that you use [`Content-Security-Policy`](/en-US/docs/Web/HTTP/Headers/Content-Security-Policy) without allowing `unsafe-inline` scripts instead.
 
 <table class="properties">
- <tbody>
-  <tr>
-   <th scope="row">Header type</th>
-   <td>{{Glossary("Response header")}}</td>
-  </tr>
-  <tr>
-   <th scope="row">{{Glossary("Forbidden header name")}}</th>
-   <td>no</td>
-  </tr>
- </tbody>
+  <tbody>
+    <tr>
+      <th scope="row">Header type</th>
+      <td>{{Glossary("Response header")}}</td>
+    </tr>
+    <tr>
+      <th scope="row">{{Glossary("Forbidden header name")}}</th>
+      <td>no</td>
+    </tr>
+  </tbody>
 </table>
 
-<h2 id="Syntax">Syntax</h2>
+## Syntax
 
-<pre class="brush: html">X-XSS-Protection: 0
+```html
+X-XSS-Protection: 0
 X-XSS-Protection: 1
 X-XSS-Protection: 1; mode=block
-X-XSS-Protection: 1; report=&lt;reporting-uri&gt;
-</pre>
+X-XSS-Protection: 1; report=<reporting-uri>
+```
 
-<dl>
- <dt>0</dt>
- <dd>Disables XSS filtering.</dd>
- <dt>1</dt>
- <dd>Enables XSS filtering (usually default in browsers). If a cross-site scripting attack is detected, the browser will sanitize the page (remove the unsafe parts).</dd>
- <dt>1; mode=block</dt>
- <dd>Enables XSS filtering. Rather than sanitizing the page, the browser will prevent rendering of the page if an attack is detected.</dd>
- <dt>1; report=&lt;reporting-URI&gt; (Chromium only)</dt>
- <dd>Enables XSS filtering. If a cross-site scripting attack is detected, the browser will sanitize the page and report the violation. This uses the functionality of the CSP {{CSP("report-uri")}} directive to send a report.</dd>
-</dl>
+- 0
+  - : Disables XSS filtering.
+- 1
+  - : Enables XSS filtering (usually default in browsers). If a cross-site scripting attack is detected, the browser will sanitize the page (remove the unsafe parts).
+- 1; mode=block
+  - : Enables XSS filtering. Rather than sanitizing the page, the browser will prevent rendering of the page if an attack is detected.
+- 1; report=\<reporting-URI> (Chromium only)
+  - : Enables XSS filtering. If a cross-site scripting attack is detected, the browser will sanitize the page and report the violation. This uses the functionality of the CSP {{CSP("report-uri")}} directive to send a report.
 
-<h2 id="Example">Example</h2>
+## Example
 
-<p>Block pages from loading when they detect reflected XSS attacks:</p>
+Block pages from loading when they detect reflected XSS attacks:
 
-<pre class="brush: bash">X-XSS-Protection: 1; mode=block</pre>
+```bash
+X-XSS-Protection: 1; mode=block
+```
 
-<p>PHP</p>
+PHP
 
-<pre>header("X-XSS-Protection: 1; mode=block");</pre>
+    header("X-XSS-Protection: 1; mode=block");
 
-<p>Apache (.htaccess)</p>
+Apache (.htaccess)
 
-<pre class="brush: bash">&lt;IfModule mod_headers.c&gt;
+```bash
+<IfModule mod_headers.c>
   Header set X-XSS-Protection "1; mode=block"
-&lt;/IfModule&gt;</pre>
+</IfModule>
+```
 
-<p>Nginx</p>
+Nginx
 
-<pre class="brush: bash">add_header "X-XSS-Protection" "1; mode=block";</pre>
+```bash
+add_header "X-XSS-Protection" "1; mode=block";
+```
 
-<h2 id="Specifications">Specifications</h2>
+## Specifications
 
-<p>Not part of any specifications or drafts.</p>
+Not part of any specifications or drafts.
 
-<h2 id="Browser_compatibility">Browser compatibility</h2>
+## Browser compatibility
 
-<p>{{Compat}}</p>
+{{Compat}}
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
- <li>{{HTTPHeader("Content-Security-Policy")}}</li>
- <li><a href="https://blogs.msdn.microsoft.com/ieinternals/2011/01/31/controlling-the-xss-filter/">Controlling the XSS Filter – Microsoft</a></li>
- <li><a href="https://www.virtuesecurity.com/blog/understanding-xss-auditor/">Understanding XSS Auditor – Virtue Security</a></li>
- <li>
-  <p><a href="https://blog.innerht.ml/the-misunderstood-x-xss-protection/">The misunderstood X-XSS-Protection – blog.innerht.ml</a></p>
- </li>
-</ul>
+- {{HTTPHeader("Content-Security-Policy")}}
+- [Controlling the XSS Filter – Microsoft](https://blogs.msdn.microsoft.com/ieinternals/2011/01/31/controlling-the-xss-filter/)
+- [Understanding XSS Auditor – Virtue Security](https://www.virtuesecurity.com/blog/understanding-xss-auditor/)
+- [The misunderstood X-XSS-Protection – blog.innerht.ml](https://blog.innerht.ml/the-misunderstood-x-xss-protection/)
diff --git a/files/en-us/web/http/index.md b/files/en-us/web/http/index.md
index 16ab8e672993625..978a835a4814cf4 100644
--- a/files/en-us/web/http/index.md
+++ b/files/en-us/web/http/index.md
@@ -10,63 +10,55 @@ tags:
   - Web Development
   - l10n:priority
 ---
-<div>{{HTTPSidebar}}</div>
+{{HTTPSidebar}}
 
-<p class="summary"><strong><dfn>Hypertext Transfer Protocol (HTTP)</dfn></strong> is an <a href="https://en.wikipedia.org/wiki/Application_Layer">application-layer</a> protocol for transmitting hypermedia documents, such as HTML. It was designed for communication between web browsers and web servers, but it can also be used for other purposes. HTTP follows a classical <a href="https://en.wikipedia.org/wiki/Client%E2%80%93server_model">client-server model</a>, with a client opening a connection to make a request, then waiting until it receives a response. HTTP is a <a href="https://en.wikipedia.org/wiki/Stateless_protocol">stateless protocol</a>, meaning that the server does not keep any data (state) between two requests.</p>
+**_Hypertext Transfer Protocol (HTTP)_** is an [application-layer](https://en.wikipedia.org/wiki/Application_Layer) protocol for transmitting hypermedia documents, such as HTML. It was designed for communication between web browsers and web servers, but it can also be used for other purposes. HTTP follows a classical [client-server model](https://en.wikipedia.org/wiki/Client%E2%80%93server_model), with a client opening a connection to make a request, then waiting until it receives a response. HTTP is a [stateless protocol](https://en.wikipedia.org/wiki/Stateless_protocol), meaning that the server does not keep any data (state) between two requests.
 
-<h2 id="Tutorials">Tutorials</h2>
+## Tutorials
 
-<p>Learn how to use HTTP with guides and tutorials.</p>
+Learn how to use HTTP with guides and tutorials.
 
-<dl>
- <dt><a href="/en-US/docs/Web/HTTP/Overview">Overview of HTTP</a></dt>
- <dd>The basic features of the client-server protocol: what it can do and its intended uses.</dd>
- <dt><a href="/en-US/docs/Web/HTTP/Caching">HTTP Cache</a></dt>
- <dd>Caching is very important for fast Web sites. This article describes different methods of caching and how to use HTTP Headers to control them.</dd>
- <dt><a href="/en-US/docs/Web/HTTP/Cookies">HTTP Cookies</a></dt>
- <dd>How cookies work is defined by <a href="https://datatracker.ietf.org/doc/html/rfc6265">RFC 6265</a>. When serving an HTTP request, a server can send a <code>Set-Cookie</code> HTTP header with the response. The client then returns the cookie's value with every request to the same server in the form of a <code>Cookie</code> request header. The cookie can also be set to expire on a certain date, or restricted to a specific domain and path.</dd>
- <dt><a href="/en-US/docs/Web/HTTP/CORS">Cross-Origin Resource Sharing (CORS)</a></dt>
- <dd><strong>Cross-site HTTP requests</strong> are HTTP requests for resources from a <strong>different domain</strong> than the domain of the resource making the request. For instance, an HTML page from Domain A (<code>http://domaina.example/</code>) makes a request for an image on Domain B (<code>http://domainb.foo/image.jpg</code>) via the <code>img</code> element. Web pages today very commonly load cross-site resources, including CSS stylesheets, images, scripts, and other resources. CORS allows web developers to control how their site reacts to cross-site requests.</dd>
- <dt><a href="/en-US/docs/Web/HTTP/Basics_of_HTTP/Evolution_of_HTTP">Evolution of HTTP</a></dt>
- <dd>A brief description of the changes between the early versions of HTTP, to the modern HTTP/2, the emergent HTTP/3 and beyond.</dd>
- <dt><a href="https://wiki.mozilla.org/Security/Guidelines/Web_Security">Mozilla web security guidelines</a></dt>
- <dd>A collection of tips to help operational teams with creating secure web applications.</dd>
- <dt><a href="/en-US/docs/Web/HTTP/Messages">HTTP Messages</a></dt>
- <dd>Describes the type and structure of the different kind of messages of HTTP/1.x and HTTP/2.</dd>
- <dt><a href="/en-US/docs/Web/HTTP/Session">A typical HTTP session</a></dt>
- <dd>Shows and explains the flow of a usual HTTP session.</dd>
- <dt><a href="/en-US/docs/Web/HTTP/Connection_management_in_HTTP_1.x">Connection management in HTTP/1.x</a></dt>
- <dd>Describes the three connection management models available in HTTP/1.x, their strengths, and their weaknesses.</dd>
-</dl>
+- [Overview of HTTP](/en-US/docs/Web/HTTP/Overview)
+  - : The basic features of the client-server protocol: what it can do and its intended uses.
+- [HTTP Cache](/en-US/docs/Web/HTTP/Caching)
+  - : Caching is very important for fast Web sites. This article describes different methods of caching and how to use HTTP Headers to control them.
+- [HTTP Cookies](/en-US/docs/Web/HTTP/Cookies)
+  - : How cookies work is defined by [RFC 6265](https://datatracker.ietf.org/doc/html/rfc6265). When serving an HTTP request, a server can send a `Set-Cookie` HTTP header with the response. The client then returns the cookie's value with every request to the same server in the form of a `Cookie` request header. The cookie can also be set to expire on a certain date, or restricted to a specific domain and path.
+- [Cross-Origin Resource Sharing (CORS)](/en-US/docs/Web/HTTP/CORS)
+  - : **Cross-site HTTP requests** are HTTP requests for resources from a **different domain** than the domain of the resource making the request. For instance, an HTML page from Domain A (`http://domaina.example/`) makes a request for an image on Domain B (`http://domainb.foo/image.jpg`) via the `img` element. Web pages today very commonly load cross-site resources, including CSS stylesheets, images, scripts, and other resources. CORS allows web developers to control how their site reacts to cross-site requests.
+- [Evolution of HTTP](/en-US/docs/Web/HTTP/Basics_of_HTTP/Evolution_of_HTTP)
+  - : A brief description of the changes between the early versions of HTTP, to the modern HTTP/2, the emergent HTTP/3 and beyond.
+- [Mozilla web security guidelines](https://wiki.mozilla.org/Security/Guidelines/Web_Security)
+  - : A collection of tips to help operational teams with creating secure web applications.
+- [HTTP Messages](/en-US/docs/Web/HTTP/Messages)
+  - : Describes the type and structure of the different kind of messages of HTTP/1.x and HTTP/2.
+- [A typical HTTP session](/en-US/docs/Web/HTTP/Session)
+  - : Shows and explains the flow of a usual HTTP session.
+- [Connection management in HTTP/1.x](/en-US/docs/Web/HTTP/Connection_management_in_HTTP_1.x)
+  - : Describes the three connection management models available in HTTP/1.x, their strengths, and their weaknesses.
 
-<h2 id="Reference">Reference</h2>
+## Reference
 
-<p>Browse through detailed HTTP reference documentation.</p>
+Browse through detailed HTTP reference documentation.
 
-<dl>
- <dt><a href="/en-US/docs/Web/HTTP/Headers">HTTP Headers</a></dt>
- <dd>HTTP message headers are used to describe a resource, or the behavior of the server or the client. Header fields are kept in an <a href="https://www.iana.org/assignments/message-headers/message-headers.xhtml#perm-headers">IANA registry</a>. IANA also maintains a <a href="https://www.iana.org/assignments/message-headers/message-headers.xhtml#prov-headers">registry of proposed new HTTP message headers</a>.</dd>
- <dt><a href="/en-US/docs/Web/HTTP/Methods">HTTP Request Methods</a></dt>
- <dd>The different operations that can be done with HTTP: {{HTTPMethod("GET")}}, {{HTTPMethod("POST")}}, and also less common requests like {{HTTPMethod("OPTIONS")}}, {{HTTPMethod("DELETE")}}, or {{HTTPMethod("TRACE")}}.</dd>
- <dt><a href="/en-US/docs/Web/HTTP/Status">HTTP Status Response Codes</a></dt>
- <dd>HTTP response codes indicate whether a specific HTTP request has been successfully completed. Responses are grouped in five classes: informational responses, successful responses, redirections, client errors, and servers errors.</dd>
- <dt><a href="/en-US/docs/Web/HTTP/Headers/Content-Security-Policy">CSP directives</a></dt>
- <dd>The {{HTTPHeader("Content-Security-Policy")}} response header fields allows web site administrators to control resources the user agent is allowed to load for a given page. With a few exceptions, policies mostly involve specifying server origins and script endpoints.</dd>
-</dl>
+- [HTTP Headers](/en-US/docs/Web/HTTP/Headers)
+  - : HTTP message headers are used to describe a resource, or the behavior of the server or the client. Header fields are kept in an [IANA registry](https://www.iana.org/assignments/message-headers/message-headers.xhtml#perm-headers). IANA also maintains a [registry of proposed new HTTP message headers](https://www.iana.org/assignments/message-headers/message-headers.xhtml#prov-headers).
+- [HTTP Request Methods](/en-US/docs/Web/HTTP/Methods)
+  - : The different operations that can be done with HTTP: {{HTTPMethod("GET")}}, {{HTTPMethod("POST")}}, and also less common requests like {{HTTPMethod("OPTIONS")}}, {{HTTPMethod("DELETE")}}, or {{HTTPMethod("TRACE")}}.
+- [HTTP Status Response Codes](/en-US/docs/Web/HTTP/Status)
+  - : HTTP response codes indicate whether a specific HTTP request has been successfully completed. Responses are grouped in five classes: informational responses, successful responses, redirections, client errors, and servers errors.
+- [CSP directives](/en-US/docs/Web/HTTP/Headers/Content-Security-Policy)
+  - : The {{HTTPHeader("Content-Security-Policy")}} response header fields allows web site administrators to control resources the user agent is allowed to load for a given page. With a few exceptions, policies mostly involve specifying server origins and script endpoints.
 
-<h2 id="Tools_resources">Tools &amp; resources</h2>
+## Tools & resources
 
-<p>Helpful tools and resources for understanding and debugging HTTP.</p>
+Helpful tools and resources for understanding and debugging HTTP.
 
-<dl>
- <dt><a href="/en-US/docs/Tools">Firefox Developer Tools</a></dt>
- <dd><a href="/en-US/docs/Tools/Network_Monitor">Network monitor</a></dd>
- <dt><a href="https://observatory.mozilla.org/">Mozilla Observatory</a></dt>
- <dd>
- <p>A project designed to help developers, system administrators, and security professionals configure their sites safely and securely.</p>
- </dd>
- <dt><a href="https://redbot.org/">RedBot</a></dt>
- <dd>Tools to check your cache-related headers</dd>
- <dt><a href="https://www.html5rocks.com/en/tutorials/internals/howbrowserswork/">How Browsers Work</a></dt>
- <dd>A very comprehensive article on browser internals and request flow through HTTP protocol. A MUST-READ for any web developer.</dd>
-</dl>
+- [Firefox Developer Tools](/en-US/docs/Tools)
+  - : [Network monitor](/en-US/docs/Tools/Network_Monitor)
+- [Mozilla Observatory](https://observatory.mozilla.org/)
+  - : A project designed to help developers, system administrators, and security professionals configure their sites safely and securely.
+- [RedBot](https://redbot.org/)
+  - : Tools to check your cache-related headers
+- [How Browsers Work](https://www.html5rocks.com/en/tutorials/internals/howbrowserswork/)
+  - : A very comprehensive article on browser internals and request flow through HTTP protocol. A MUST-READ for any web developer.
diff --git a/files/en-us/web/http/index/index.md b/files/en-us/web/http/index/index.md
index 61291d6d7e2aaa8..884c79a1f44ee50 100644
--- a/files/en-us/web/http/index/index.md
+++ b/files/en-us/web/http/index/index.md
@@ -5,8 +5,8 @@ tags:
   - HTTP
   - Index
 ---
-<div>{{HTTPSidebar}}</div>
+{{HTTPSidebar}}
 
-<p>This page lists all MDN HTTP pages along with their summary and tags.</p>
+This page lists all MDN HTTP pages along with their summary and tags.
 
-<p>{{Index("/en-US/docs/Web/HTTP")}}</p>
+{{Index("/en-US/docs/Web/HTTP")}}
diff --git a/files/en-us/web/http/link_prefetching_faq/index.md b/files/en-us/web/http/link_prefetching_faq/index.md
index a350cbe1f8fd8f2..e31a7366a628c40 100644
--- a/files/en-us/web/http/link_prefetching_faq/index.md
+++ b/files/en-us/web/http/link_prefetching_faq/index.md
@@ -11,114 +11,108 @@ tags:
   - Prefetch
   - Web Development
 ---
-<h3 id="What_is_link_prefetching.3F">What is link prefetching?</h3>
+### What is link prefetching?
 
-<p>Link prefetching is a browser mechanism, which utilizes browser idle time to download or <em>prefetch</em> documents that the user might visit in the near future. A web page provides a set of prefetching hints to the browser, and after the browser is finished loading the page, it begins silently prefetching specified documents and stores them in its cache. When the user visits one of the prefetched documents, it can be served up quickly out of the browser's cache.</p>
+Link prefetching is a browser mechanism, which utilizes browser idle time to download or _prefetch_ documents that the user might visit in the near future. A web page provides a set of prefetching hints to the browser, and after the browser is finished loading the page, it begins silently prefetching specified documents and stores them in its cache. When the user visits one of the prefetched documents, it can be served up quickly out of the browser's cache.
 
-<h3 id="Does_prefetching_work_with_HTTPS">Does prefetching work with HTTPS?</h3>
+### Does prefetching work with HTTPS?
 
-<p>Starting in Gecko 1.9.1 (Firefox 3.5), HTTPS content can be prefetched.</p>
+Starting in Gecko 1.9.1 (Firefox 3.5), HTTPS content can be prefetched.
 
-<h3 id="What_are_the_prefetching_hints.3F">What are the prefetching hints?</h3>
+### What are the prefetching hints?
 
-<p>The browser looks for either an HTML {{ HTMLElement("link") }} or an <a href="/en-US/docs/Web/HTTP/Headers" title="HTTP headers">HTTP <code>Link:</code> header</a> with a relation type of either <code>next</code> or <code>prefetch</code>. An example using the <code>link</code> tag follows:</p>
+The browser looks for either an HTML {{ HTMLElement("link") }} or an [HTTP `Link:` header](/en-US/docs/Web/HTTP/Headers "HTTP headers") with a relation type of either `next` or `prefetch`. An example using the `link` tag follows:
 
-<pre class="eval">&lt;link rel="prefetch" href="/images/big.jpeg"&gt;
-</pre>
+    <link rel="prefetch" href="/images/big.jpeg">
 
-<p>The same prefetching hint using an HTTP <code>Link:</code> header:</p>
+The same prefetching hint using an HTTP `Link:` header:
 
-<pre class="eval">Link: &lt;/images/big.jpeg&gt;; rel=prefetch
-</pre>
+    Link: </images/big.jpeg>; rel=prefetch
 
-<p>The format for the <code>Link:</code> header is described in <a href="https://datatracker.ietf.org/doc/html/rfc5988">RFC 5988</a> section 5.</p>
+The format for the `Link:` header is described in [RFC 5988](https://datatracker.ietf.org/doc/html/rfc5988) section 5.
 
-<p>The browser observes all of these hints and queues up each unique request to be prefetched when the browser is idle. There can be multiple hints per page, as it might make sense to prefetch multiple documents. For example, the next document might contain several large images.</p>
+The browser observes all of these hints and queues up each unique request to be prefetched when the browser is idle. There can be multiple hints per page, as it might make sense to prefetch multiple documents. For example, the next document might contain several large images.
 
-<p>Some more examples follow:</p>
+Some more examples follow:
 
-<pre class="eval">&lt;link rel="prefetch alternate stylesheet" title="Designed for Mozilla" href="mozspecific.css"&gt;
-&lt;link rel="next" href="2.html"&gt;
-</pre>
+    <link rel="prefetch alternate stylesheet" title="Designed for Mozilla" href="mozspecific.css">
+    <link rel="next" href="2.html">
 
-<h3 id="Are_anchor_.28.3Ca.3E.29_tags_prefetched.3F">Are anchor (&lt;a&gt;) tags prefetched?</h3>
+### Are anchor (\<a>) tags prefetched?
 
-<p>No, only <code>&lt;link&gt;</code> tags with a relation type of <code>next</code> or <code>prefetch</code> are prefetched. However, if there is sufficient interest, we may expand link prefetching support to include prefetching &lt;a&gt; tags, which include a relation type of <code>next</code> or <code>prefetch</code> in the future. Doing so would probably help content providers avoid the problem of stale prefetching links.</p>
+No, only `<link>` tags with a relation type of `next` or `prefetch` are prefetched. However, if there is sufficient interest, we may expand link prefetching support to include prefetching \<a> tags, which include a relation type of `next` or `prefetch` in the future. Doing so would probably help content providers avoid the problem of stale prefetching links.
 
-<h3 id="Is_link_prefetching_standards_compliant.3F">Is link prefetching standards compliant?</h3>
+### Is link prefetching standards compliant?
 
-<p>Yes, link prefetching as outlined in this document does not violate any existing web standards. In fact, the HTML 4.01 specification explicitly allows for the definition of new link relation types (<a href="https://www.w3.org/TR/html4/types.html#type-links">see Section 6.12: Link types</a>). However, the exact mechanism employed by Mozilla is not yet standardized. An Internet-Draft is in the works.</p>
+Yes, link prefetching as outlined in this document does not violate any existing web standards. In fact, the HTML 4.01 specification explicitly allows for the definition of new link relation types ([see Section 6.12: Link types](https://www.w3.org/TR/html4/types.html#type-links)). However, the exact mechanism employed by Mozilla is not yet standardized. An Internet-Draft is in the works.
 
-<p>Standardization of this technique is part of the scope of HTML 5, see the current working draft, <a href="https://www.whatwg.org/specs/web-apps/current-work/#link-type-prefetch">section §5.11.3.13. Link type "prefetch"</a> .</p>
+Standardization of this technique is part of the scope of HTML 5, see the current working draft, [section §5.11.3.13. Link type "prefetch"](https://www.whatwg.org/specs/web-apps/current-work/#link-type-prefetch) .
 
-<h3 id="How_is_browser_idle_time_determined.3F">How is browser idle time determined?</h3>
+### How is browser idle time determined?
 
-<p>In the current implementation (Mozilla 1.2), idle time is determined using the <code>nsIWebProgressListener</code> API. We attach a listener to the toplevel <code>nsIWebProgress</code> object ("@mozilla.org/docloaderservice;1"). From this, we receive document start &amp; stop notifications, and we approximate idle time as the period between the last document stop and the next document start. The last document stop notification occurs roughly when the onLoad handler would fire for the toplevel document. This is when we kick off prefetch requests. If a subframe contains prefetching hints, prefetching will not begin until the top-most frame and all its "child" frames finish loading.</p>
+In the current implementation (Mozilla 1.2), idle time is determined using the `nsIWebProgressListener` API. We attach a listener to the toplevel `nsIWebProgress` object ("@mozilla.org/docloaderservice;1"). From this, we receive document start & stop notifications, and we approximate idle time as the period between the last document stop and the next document start. The last document stop notification occurs roughly when the onLoad handler would fire for the toplevel document. This is when we kick off prefetch requests. If a subframe contains prefetching hints, prefetching will not begin until the top-most frame and all its "child" frames finish loading.
 
-<h3 id="What_happens_if_I_click_on_a_link_while_something_is_being_prefetched.3F">What happens if I click on a link while something is being prefetched?</h3>
+### What happens if I click on a link while something is being prefetched?
 
-<p>When the user clicks on a link, or initiates any kind of page load, link prefetching will stop and any prefetch hints will be discarded. If a prefetched document is partially downloaded, then the partial document will still be stored in the cache provided the server sent an "Accept-Ranges: bytes" response header. This header is typically generated by webservers when serving up static content. When the user visits a prefetched document for real, the remaining portion of the document will be fetched using a HTTP byte-range request.</p>
+When the user clicks on a link, or initiates any kind of page load, link prefetching will stop and any prefetch hints will be discarded. If a prefetched document is partially downloaded, then the partial document will still be stored in the cache provided the server sent an "Accept-Ranges: bytes" response header. This header is typically generated by webservers when serving up static content. When the user visits a prefetched document for real, the remaining portion of the document will be fetched using a HTTP byte-range request.
 
-<h3 id="What_if_I.27m_downloading_something_in_the_background.3F_Will_link_prefetching_compete_for_bandwidth.3F">What if I'm downloading something in the background? Will link prefetching compete for bandwidth?</h3>
+### What if I'm downloading something in the background? Will link prefetching compete for bandwidth?
 
-<p>Yes and no. If you are downloading something using Mozilla, link prefetching will be delayed until any background downloads complete. For example, if you load a bookmark group (which opens several tabs), any prefetch requests initiated by one of the bookmarked pages will not begin until all of the tabs finish loading. If you are using another application which uses the network, link prefetching in Mozilla may compete for bandwidth with the other application. This is a problem that we hope to address in the future by leveraging operating system services to monitor network idle time.</p>
+Yes and no. If you are downloading something using Mozilla, link prefetching will be delayed until any background downloads complete. For example, if you load a bookmark group (which opens several tabs), any prefetch requests initiated by one of the bookmarked pages will not begin until all of the tabs finish loading. If you are using another application which uses the network, link prefetching in Mozilla may compete for bandwidth with the other application. This is a problem that we hope to address in the future by leveraging operating system services to monitor network idle time.
 
-<h3 id="Are_there_any_restrictions_on_what_is_prefetched.3F">Are there any restrictions on what is prefetched?</h3>
+### Are there any restrictions on what is prefetched?
 
-<p>Yes, only <code>http://</code> (and, starting in {{ Gecko("1.9.1") }} <code>https://</code>) URLs can be prefetched. Other protocols (such as FTP) do not provide rich enough support for client side caching.</p>
+Yes, only `http://` (and, starting in {{ Gecko("1.9.1") }} `https://`) URLs can be prefetched. Other protocols (such as FTP) do not provide rich enough support for client side caching.
 
-<h3 id="Will_Mozilla_prefetch_documents_from_a_different_host.3F">Will Mozilla prefetch documents from a different host?</h3>
+### Will Mozilla prefetch documents from a different host?
 
-<p>Yes. There is no same-origin restriction for link prefetching. Limiting prefetching to only URLs from the same server would not offer any increased browser security.</p>
+Yes. There is no same-origin restriction for link prefetching. Limiting prefetching to only URLs from the same server would not offer any increased browser security.
 
-<h3 id="Do_prefetched_requests_contain_a_Referer:_header.3F">Do prefetched requests contain a Referer: header?</h3>
+### Do prefetched requests contain a Referer: header?
 
-<p>Yes, prefetched requests include a HTTP <code>Referer:</code> header indicating the document from which the prefetching hint was extracted.</p>
+Yes, prefetched requests include a HTTP `Referer:` header indicating the document from which the prefetching hint was extracted.
 
-<p>This may impact referrer tracking that is commonly used on many sites. For this reason, link prefetching may not be appropriate for all content. However, it is possible to instruct Mozilla to validate a prefetched document when the user follows a href to the prefetched document by specifying the <code>Cache-control: must-revalidate</code> HTTP response header. This header enables caching, but requires an <code>If-Modified-Since</code> or <code>If-None-Match</code> validation request before the serving the document out of the browser's cache.</p>
+This may impact referrer tracking that is commonly used on many sites. For this reason, link prefetching may not be appropriate for all content. However, it is possible to instruct Mozilla to validate a prefetched document when the user follows a href to the prefetched document by specifying the `Cache-control: must-revalidate` HTTP response header. This header enables caching, but requires an `If-Modified-Since` or `If-None-Match` validation request before the serving the document out of the browser's cache.
 
-<h3 id="As_a_server_admin.2C_can_I_distinguish_prefetch_requests_from_normal_requests.3F">As a server admin, can I distinguish prefetch requests from normal requests?</h3>
+### As a server admin, can I distinguish prefetch requests from normal requests?
 
-<p>Yes, we send the following header along with each prefetch request:</p>
+Yes, we send the following header along with each prefetch request:
 
-<pre>X-moz: prefetch</pre>
+    X-moz: prefetch
 
-<p>Of course, this request header is not at all standardized, and it may change in future Mozilla releases. Chrome uses "X-Purpose: prefetch" or "Purpose: prefetch" <a href="https://bugs.webkit.org/show_bug.cgi?id=46529">header</a>.</p>
+Of course, this request header is not at all standardized, and it may change in future Mozilla releases. Chrome uses "X-Purpose: prefetch" or "Purpose: prefetch" [header](https://bugs.webkit.org/show_bug.cgi?id=46529).
 
-<h3 id="Is_there_a_preference_to_disable_link_prefetching.3F">Is there a preference to disable link prefetching?</h3>
+### Is there a preference to disable link prefetching?
 
-<p>Yes, there is a hidden preference that you can set to disable link prefetching. Add this line to your prefs.js file located in your profile directory (or make the appropriate change via <code>about:config</code>:</p>
+Yes, there is a hidden preference that you can set to disable link prefetching. Add this line to your prefs.js file located in your profile directory (or make the appropriate change via `about:config`:
 
-<pre class="eval">user_pref("network.prefetch-next", false);
-</pre>
+    user_pref("network.prefetch-next", false);
 
-<p>However, the theory is that if link prefetching needs to be disabled then there must be something wrong with the implementation. We would rather improve the implementation if it does not work correctly, than expect users to locate and tweak some obscure preference.</p>
+However, the theory is that if link prefetching needs to be disabled then there must be something wrong with the implementation. We would rather improve the implementation if it does not work correctly, than expect users to locate and tweak some obscure preference.
 
-<h3 id="What_about_folks_who_pay-per-byte_for_network_bandwidth.3F">What about folks who pay-per-byte for network bandwidth?</h3>
+### What about folks who pay-per-byte for network bandwidth?
 
-<p>Basically, there are two ways of looking at this issue: websites can already cause things to be silently downloaded using JS/DOM hacks. Prefetching is a browser feature; users should be able to disable it easily.</p>
+Basically, there are two ways of looking at this issue: websites can already cause things to be silently downloaded using JS/DOM hacks. Prefetching is a browser feature; users should be able to disable it easily.
 
-<p>It is important that websites adopt <code>&lt;link&gt;</code> tag based prefetching instead of trying to roll-in silent downloading using various JS/DOM hacks. The <code>&lt;link&gt;</code> tag gives the browser the ability to know what sites are up to, and we can use this information to better prioritize document prefetching. The user preference to disable <code>&lt;link&gt;</code> tag prefetching may encourage websites to stick with JS/DOM hacks, and that would not be good for users. This is one reason why prefetching is enabled by default.</p>
+It is important that websites adopt `<link>` tag based prefetching instead of trying to roll-in silent downloading using various JS/DOM hacks. The `<link>` tag gives the browser the ability to know what sites are up to, and we can use this information to better prioritize document prefetching. The user preference to disable `<link>` tag prefetching may encourage websites to stick with JS/DOM hacks, and that would not be good for users. This is one reason why prefetching is enabled by default.
 
-<h3 id="Which_browsers_support_link_prefetching.3F">Which browsers support link prefetching?</h3>
+### Which browsers support link prefetching?
 
-<p>Browsers based on Mozilla 1.2 (or later) as well as browsers based on Mozilla 1.0.2 (or later) support prefetching. This includes Firefox and Netscape 7.01+. Camino builds as of March 2003 are based on Mozilla 1.0.1, and therefore do not support prefetching. <a href="https://gemal.dk/browserspy/prefetch.php">Test</a> your browser to see if it supports Link Prefetching.</p>
+Browsers based on Mozilla 1.2 (or later) as well as browsers based on Mozilla 1.0.2 (or later) support prefetching. This includes Firefox and Netscape 7.01+. Camino builds as of March 2003 are based on Mozilla 1.0.1, and therefore do not support prefetching. [Test](https://gemal.dk/browserspy/prefetch.php) your browser to see if it supports Link Prefetching.
 
-<h3 id="Privacy_implications">Privacy implications</h3>
+### Privacy implications
 
-<p>Along with the referral and URL-following implications already mentioned above, prefetching will generally cause the cookies of the prefetched site to be accessed. (For example, if you google amazon, the google results page will prefetch <code>www.amazon.com</code>, causing amazon cookies to be sent back and forth. You can block 3rd party cookies in Firefox, see <a href="https://support.mozilla.com/en-US/kb/Disabling%20third%20party%20cookies">Disabling third party cookies</a>.)</p>
+Along with the referral and URL-following implications already mentioned above, prefetching will generally cause the cookies of the prefetched site to be accessed. (For example, if you google amazon, the google results page will prefetch `www.amazon.com`, causing amazon cookies to be sent back and forth. You can block 3rd party cookies in Firefox, see [Disabling third party cookies](https://support.mozilla.com/en-US/kb/Disabling%20third%20party%20cookies).)
 
-<h3 id="What_about....3F">What about...?</h3>
+### What about...?
 
-<p>If you have any questions or comments about link prefetching, please feel free to send them my way :-)</p>
+If you have any questions or comments about link prefetching, please feel free to send them my way :-)
 
-<h4 id="See_also">See also</h4>
+#### See also
 
-<p><a href="https://www.edochan.com/programming/pf.htm">Prefetching Hints</a></p>
+[Prefetching Hints](https://www.edochan.com/programming/pf.htm)
 
-<h2 id="Original_Document_Information">Original Document Information</h2>
+## Original Document Information
 
-<ul>
- <li>Author(s): Darin Fisher (darin at meer dot net)</li>
- <li>Last Updated Date: Updated: March 3, 2003</li>
-</ul>
+- Author(s): Darin Fisher (darin at meer dot net)
+- Last Updated Date: Updated: March 3, 2003
diff --git a/files/en-us/web/http/messages/index.md b/files/en-us/web/http/messages/index.md
index 090ab2fe1941808..e8c31e020bb8203 100644
--- a/files/en-us/web/http/messages/index.md
+++ b/files/en-us/web/http/messages/index.md
@@ -6,138 +6,118 @@ tags:
   - HTTP
   - WebMechanics
 ---
-<div>{{HTTPSidebar}}</div>
+{{HTTPSidebar}}
 
-<p class="summary">HTTP messages are how data is exchanged between a server and a client. There are two types of messages: <em>requests</em> sent by the client to trigger an action on the server, and <em>responses</em>, the answer from the server.</p>
+HTTP messages are how data is exchanged between a server and a client. There are two types of messages: _requests_ sent by the client to trigger an action on the server, and _responses_, the answer from the server.
 
-<p>HTTP messages are composed of textual information encoded in ASCII, and span over multiple lines. In HTTP/1.1, and earlier versions of the protocol, these messages were openly sent across the connection. In HTTP/2, the once human-readable message is now divided up into HTTP frames, providing optimization and performance improvements.</p>
+HTTP messages are composed of textual information encoded in ASCII, and span over multiple lines. In HTTP/1.1, and earlier versions of the protocol, these messages were openly sent across the connection. In HTTP/2, the once human-readable message is now divided up into HTTP frames, providing optimization and performance improvements.
 
-<p>Web developers, or webmasters, rarely craft these textual HTTP messages themselves: software, a Web browser, proxy, or Web server, perform this action. They provide HTTP messages through config files (for proxies or servers), APIs (for browsers), or other interfaces.</p>
+Web developers, or webmasters, rarely craft these textual HTTP messages themselves: software, a Web browser, proxy, or Web server, perform this action. They provide HTTP messages through config files (for proxies or servers), APIs (for browsers), or other interfaces.
 
-<p><img alt="From a user-, script-, or server- generated event, an HTTP/1.x msg is generated, and if HTTP/2 is in use, it is binary framed into an HTTP/2 stream, then sent." src="httpmsg2.png"></p>
+![From a user-, script-, or server- generated event, an HTTP/1.x msg is generated, and if HTTP/2 is in use, it is binary framed into an HTTP/2 stream, then sent.](httpmsg2.png)
 
-<p>The HTTP/2 binary framing mechanism has been designed to not require any alteration of the APIs or config files applied: it is broadly transparent to the user.</p>
+The HTTP/2 binary framing mechanism has been designed to not require any alteration of the APIs or config files applied: it is broadly transparent to the user.
 
-<p>HTTP requests, and responses, share similar structure and are composed of:</p>
+HTTP requests, and responses, share similar structure and are composed of:
 
-<ol>
- <li>A <em>start-line</em> describing the requests to be implemented, or its status of whether successful or a failure. This start-line is always a single line.</li>
- <li>An optional set of <em>HTTP headers</em> specifying the request, or describing the body included in the message.</li>
- <li>A blank line indicating all meta-information for the request has been sent.</li>
- <li>An optional <em>body</em> containing data associated with the request (like content of an HTML form), or the document associated with a response. The presence of the body and its size is specified by the start-line and HTTP headers.</li>
-</ol>
+1.  A _start-line_ describing the requests to be implemented, or its status of whether successful or a failure. This start-line is always a single line.
+2.  An optional set of _HTTP headers_ specifying the request, or describing the body included in the message.
+3.  A blank line indicating all meta-information for the request has been sent.
+4.  An optional _body_ containing data associated with the request (like content of an HTML form), or the document associated with a response. The presence of the body and its size is specified by the start-line and HTTP headers.
 
-<p>The start-line and HTTP headers of the HTTP message are collectively known as the <em>head</em> of the requests, whereas its payload is known as the <em>body</em>.</p>
+The start-line and HTTP headers of the HTTP message are collectively known as the _head_ of the requests, whereas its payload is known as the _body_.
 
-<p><img alt="Requests and responses share a common structure in HTTP" src="httpmsgstructure2.png"></p>
+![Requests and responses share a common structure in HTTP](httpmsgstructure2.png)
 
-<h2 id="HTTP_Requests">HTTP Requests</h2>
+## HTTP Requests
 
-<h3 id="Start_line">Start line</h3>
+### Start line
 
-<p>HTTP requests are messages sent by the client to initiate an action on the server. Their <em>start-line</em> contain three elements:</p>
+HTTP requests are messages sent by the client to initiate an action on the server. Their _start-line_ contain three elements:
 
-<ol>
- <li>An <em><a href="/en-US/docs/Web/HTTP/Methods">HTTP method</a></em>, a verb (like {{HTTPMethod("GET")}}, {{HTTPMethod("PUT")}} or {{HTTPMethod("POST")}}) or a noun (like {{HTTPMethod("HEAD")}} or {{HTTPMethod("OPTIONS")}}), that describes the action to be performed. For example, <code>GET</code> indicates that a resource should be fetched or <code>POST</code> means that data is pushed to the server (creating or modifying a resource, or generating a temporary document to send back).</li>
- <li>The <em>request target</em>, usually a {{glossary("URL")}}, or the absolute path of the protocol, port, and domain are usually characterized by the request context. The format of this request target varies between different HTTP methods. It can be
-  <ul>
-   <li>An absolute path, ultimately followed by a <code>'?'</code> and query string. This is the most common form, known as the <em>origin form</em>, and is used with <code>GET</code>, <code>POST</code>, <code>HEAD</code>, and <code>OPTIONS</code> methods.<br>
-    <code>POST / HTTP/1.1<br>
-    GET /background.png HTTP/1.0<br>
-    HEAD /test.html?query=alibaba HTTP/1.1<br>
-    OPTIONS /anypage.html HTTP/1.0</code></li>
-   <li>A complete URL, known as the <em>absolute form</em>, is mostly used with <code>GET</code> when connected to a proxy.<br>
-    <code>GET https://developer.mozilla.org/en-US/docs/Web/HTTP/Messages HTTP/1.1</code></li>
-   <li>The authority component of a URL, consisting of the domain name and optionally the port (prefixed by a <code>':'</code>), is called the <em>authority form</em>. It is only used with <code>CONNECT</code> when setting up an HTTP tunnel.<br>
-    <code>CONNECT developer.mozilla.org:80 HTTP/1.1</code></li>
-   <li>The <em>asterisk form</em>, a simple asterisk (<code>'*'</code>) is used with <code>OPTIONS</code>, representing the server as a whole.<br>
-    <code>OPTIONS * HTTP/1.1</code></li>
-  </ul>
- </li>
- <li>The <em>HTTP version</em>, which defines the structure of the remaining message, acting as an indicator of the expected version to use for the response.</li>
-</ol>
+1.  An _[HTTP method](/en-US/docs/Web/HTTP/Methods)_, a verb (like {{HTTPMethod("GET")}}, {{HTTPMethod("PUT")}} or {{HTTPMethod("POST")}}) or a noun (like {{HTTPMethod("HEAD")}} or {{HTTPMethod("OPTIONS")}}), that describes the action to be performed. For example, `GET` indicates that a resource should be fetched or `POST` means that data is pushed to the server (creating or modifying a resource, or generating a temporary document to send back).
+2.  The _request target_, usually a {{glossary("URL")}}, or the absolute path of the protocol, port, and domain are usually characterized by the request context. The format of this request target varies between different HTTP methods. It can be
 
-<h3 id="Headers">Headers</h3>
+    - An absolute path, ultimately followed by a `'?'` and query string. This is the most common form, known as the _origin form_, and is used with `GET`, `POST`, `HEAD`, and `OPTIONS` methods.
+      `POST / HTTP/1.1 GET /background.png HTTP/1.0 HEAD /test.html?query=alibaba HTTP/1.1 OPTIONS /anypage.html HTTP/1.0`
+    - A complete URL, known as the _absolute form_, is mostly used with `GET` when connected to a proxy.
+      `GET https://developer.mozilla.org/en-US/docs/Web/HTTP/Messages HTTP/1.1`
+    - The authority component of a URL, consisting of the domain name and optionally the port (prefixed by a `':'`), is called the _authority form_. It is only used with `CONNECT` when setting up an HTTP tunnel.
+      `CONNECT developer.mozilla.org:80 HTTP/1.1`
+    - The _asterisk form_, a simple asterisk (`'*'`) is used with `OPTIONS`, representing the server as a whole.
+      `OPTIONS * HTTP/1.1`
 
-<p><a href="/en-US/docs/Web/HTTP/Headers">HTTP headers</a> from a request follow the same basic structure of an HTTP header: a case-insensitive string followed by a colon (<code>':'</code>) and a value whose structure depends upon the header. The whole header, including the value, consist of one single line, which can be quite long.</p>
+3.  The _HTTP version_, which defines the structure of the remaining message, acting as an indicator of the expected version to use for the response.
 
-<p>Many different headers can appear in requests. They can be divided in several groups:</p>
+### Headers
 
-<ul>
- <li>{{glossary("General header", "General headers")}}, like {{HTTPHeader("Via")}}, apply to the message as a whole.</li> 
- <li>{{glossary("Request header", "Request headers")}}, like {{HTTPHeader("User-Agent")}} or {{HTTPHeader("Accept")}}, modify the request by specifying it further (like {{HTTPHeader("Accept-Language")}}), by giving context (like {{HTTPHeader("Referer")}}), or by conditionally restricting it (like {{HTTPHeader("If-None")}}).</li>
- <li>{{glossary("Representation header", "Representation headers")}} like {{HTTPHeader("Content-Type")}} that describe the original format of the message data and any encoding applied (only present if the message has a body).</li>
-</ul>
+[HTTP headers](/en-US/docs/Web/HTTP/Headers) from a request follow the same basic structure of an HTTP header: a case-insensitive string followed by a colon (`':'`) and a value whose structure depends upon the header. The whole header, including the value, consist of one single line, which can be quite long.
 
-<p><img alt="Example of headers in an HTTP request" src="http_request_headers3.png"></p>
+Many different headers can appear in requests. They can be divided in several groups:
 
-<h3 id="Body">Body</h3>
+- {{glossary("General header", "General headers")}}, like {{HTTPHeader("Via")}}, apply to the message as a whole.
+- {{glossary("Request header", "Request headers")}}, like {{HTTPHeader("User-Agent")}} or {{HTTPHeader("Accept")}}, modify the request by specifying it further (like {{HTTPHeader("Accept-Language")}}), by giving context (like {{HTTPHeader("Referer")}}), or by conditionally restricting it (like {{HTTPHeader("If-None")}}).
+- {{glossary("Representation header", "Representation headers")}} like {{HTTPHeader("Content-Type")}} that describe the original format of the message data and any encoding applied (only present if the message has a body).
 
-<p>The final part of the request is its body. Not all requests have one: requests fetching resources, like <code>GET</code>, <code>HEAD</code>, <code>DELETE</code>, or <code>OPTIONS</code>, usually don't need one. Some requests send data to the server in order to update it: as often the case with <code>POST</code> requests (containing HTML form data).</p>
+![Example of headers in an HTTP request](http_request_headers3.png)
 
-<p>Bodies can be broadly divided into two categories:</p>
+### Body
 
-<ul>
- <li>Single-resource bodies, consisting of one single file, defined by the two headers: {{HTTPHeader("Content-Type")}} and {{HTTPHeader("Content-Length")}}.</li>
- <li><a href="/en-US/docs/Web/HTTP/Basics_of_HTTP/MIME_types#multipartform-data">Multiple-resource bodies</a>, consisting of a multipart body, each containing a different bit of information. This is typically associated with <a href="/en-US/docs/Learn/Forms">HTML Forms</a>.</li>
-</ul>
+The final part of the request is its body. Not all requests have one: requests fetching resources, like `GET`, `HEAD`, `DELETE`, or `OPTIONS`, usually don't need one. Some requests send data to the server in order to update it: as often the case with `POST` requests (containing HTML form data).
 
-<h2 id="HTTP_Responses">HTTP Responses</h2>
+Bodies can be broadly divided into two categories:
 
-<h3 id="Status_line">Status line</h3>
+- Single-resource bodies, consisting of one single file, defined by the two headers: {{HTTPHeader("Content-Type")}} and {{HTTPHeader("Content-Length")}}.
+- [Multiple-resource bodies](/en-US/docs/Web/HTTP/Basics_of_HTTP/MIME_types#multipartform-data), consisting of a multipart body, each containing a different bit of information. This is typically associated with [HTML Forms](/en-US/docs/Learn/Forms).
 
-<p>The start line of an HTTP response, called the <em>status line</em>, contains the following information:</p>
+## HTTP Responses
 
-<ol>
- <li>The <em>protocol version</em>, usually <code>HTTP/1.1</code>.</li>
- <li>A <em>status code</em>, indicating success or failure of the request. Common status codes are {{HTTPStatus("200")}}, {{HTTPStatus("404")}}, or {{HTTPStatus("302")}}</li>
- <li>A <em>status text</em>. A brief, purely informational, textual description of the status code to help a human understand the HTTP message.</li>
-</ol>
+### Status line
 
-<p>A typical status line looks like: <code>HTTP/1.1 404 Not Found</code>.</p>
+The start line of an HTTP response, called the _status line_, contains the following information:
 
-<h3 id="Headers_2">Headers</h3>
+1.  The _protocol version_, usually `HTTP/1.1`.
+2.  A _status code_, indicating success or failure of the request. Common status codes are {{HTTPStatus("200")}}, {{HTTPStatus("404")}}, or {{HTTPStatus("302")}}
+3.  A _status text_. A brief, purely informational, textual description of the status code to help a human understand the HTTP message.
 
-<p><a href="/en-US/docs/Web/HTTP/Headers">HTTP headers</a> for responses follow the same structure as any other header: a case-insensitive string followed by a colon (<code>':'</code>) and a value whose structure depends upon the type of the header. The whole header, including its value, presents as a single line.</p>
+A typical status line looks like: `HTTP/1.1 404 Not Found`.
 
-<p>Many different headers can appear in responses. These can be divided into several groups:</p>
+### Headers
 
-<ul>
- <li>{{glossary("General header", "General headers")}}, like {{HTTPHeader("Via")}}, apply to the whole message.</li> 
- <li>{{glossary("Response header", "Response headers")}}, like {{HTTPHeader("Vary")}} and {{HTTPHeader("Accept-Ranges")}}, give additional information about the server which doesn't fit in the status line.</li>  
- <li>{{glossary("Representation header", "Representation headers")}} like {{HTTPHeader("Content-Type")}} that describe the original format of the message data and any encoding applied (only present if the message has a body).</li>
-</ul>
+[HTTP headers](/en-US/docs/Web/HTTP/Headers) for responses follow the same structure as any other header: a case-insensitive string followed by a colon (`':'`) and a value whose structure depends upon the type of the header. The whole header, including its value, presents as a single line.
 
-<p><img alt="Example of headers in an HTTP response" src="http_response_headers3.png"></p>
+Many different headers can appear in responses. These can be divided into several groups:
 
-<h3 id="Body_2">Body</h3>
+- {{glossary("General header", "General headers")}}, like {{HTTPHeader("Via")}}, apply to the whole message.
+- {{glossary("Response header", "Response headers")}}, like {{HTTPHeader("Vary")}} and {{HTTPHeader("Accept-Ranges")}}, give additional information about the server which doesn't fit in the status line.
+- {{glossary("Representation header", "Representation headers")}} like {{HTTPHeader("Content-Type")}} that describe the original format of the message data and any encoding applied (only present if the message has a body).
 
-<p>The last part of a response is the body. Not all responses have one: responses with a status code that sufficiently answers the request without the need for corresponding payload (like {{HTTPStatus("201")}} <strong><code>Created</code></strong> or {{HTTPStatus("204")}} <strong><code>No Content</code></strong>) usually don't.</p>
+![Example of headers in an HTTP response](http_response_headers3.png)
 
-<p>Bodies can be broadly divided into three categories:</p>
+### Body
 
-<ul>
- <li>Single-resource bodies, consisting of a single file of known length, defined by the two headers: {{HTTPHeader("Content-Type")}} and {{HTTPHeader("Content-Length")}}.</li>
- <li>Single-resource bodies, consisting of a single file of unknown length, encoded by chunks with {{HTTPHeader("Transfer-Encoding")}} set to <code>chunked</code>.</li>
- <li><a href="/en-US/docs/Web/HTTP/Basics_of_HTTP/MIME_types#multipartform-data">Multiple-resource bodies</a>, consisting of a multipart body, each containing a different section of information. These are relatively rare.</li>
-</ul>
+The last part of a response is the body. Not all responses have one: responses with a status code that sufficiently answers the request without the need for corresponding payload (like {{HTTPStatus("201")}} **`Created`** or {{HTTPStatus("204")}} **`No Content`**) usually don't.
 
-<h2 id="HTTP2_Frames">HTTP/2 Frames</h2>
+Bodies can be broadly divided into three categories:
 
-<p>HTTP/1.x messages have a few drawbacks for performance:</p>
+- Single-resource bodies, consisting of a single file of known length, defined by the two headers: {{HTTPHeader("Content-Type")}} and {{HTTPHeader("Content-Length")}}.
+- Single-resource bodies, consisting of a single file of unknown length, encoded by chunks with {{HTTPHeader("Transfer-Encoding")}} set to `chunked`.
+- [Multiple-resource bodies](/en-US/docs/Web/HTTP/Basics_of_HTTP/MIME_types#multipartform-data), consisting of a multipart body, each containing a different section of information. These are relatively rare.
 
-<ul>
- <li>Headers, unlike bodies, are uncompressed.</li>
- <li>Headers are often very similar from one message to the next one, yet still repeated across connections.</li>
- <li>No multiplexing can be done. Several connections need opening on the same server: and warm TCP connections are more efficient than cold ones.</li>
-</ul>
+## HTTP/2 Frames
 
-<p>HTTP/2 introduces an extra step: it divides HTTP/1.x messages into frames which are embedded in a stream. Data and header frames are separated, this allows header compression. Several streams can be combined together, a process called <em>multiplexing</em>, allowing more efficient use of underlying TCP connections.</p>
+HTTP/1.x messages have a few drawbacks for performance:
 
-<p><img alt="HTTP/2 modify the HTTP message to divide them in frames (part of a single stream), allowing for more optimization." src="binary_framing2.png"></p>
+- Headers, unlike bodies, are uncompressed.
+- Headers are often very similar from one message to the next one, yet still repeated across connections.
+- No multiplexing can be done. Several connections need opening on the same server: and warm TCP connections are more efficient than cold ones.
 
-<p>HTTP frames are now transparent to Web developers. This is an additional step in HTTP/2, between HTTP/1.1 messages and the underlying transport protocol. No changes are needed in the APIs used by Web developers to utilize HTTP frames; when available in both the browser and the server, HTTP/2 is switched on and used.</p>
+HTTP/2 introduces an extra step: it divides HTTP/1.x messages into frames which are embedded in a stream. Data and header frames are separated, this allows header compression. Several streams can be combined together, a process called _multiplexing_, allowing more efficient use of underlying TCP connections.
 
-<h2 id="Conclusion">Conclusion</h2>
+![HTTP/2 modify the HTTP message to divide them in frames (part of a single stream), allowing for more optimization.](binary_framing2.png)
 
-<p>HTTP messages are the key in using HTTP; their structure is simple, and they are highly extensible. The HTTP/2 framing mechanism adds a new intermediate layer between the HTTP/1.x syntax and the underlying transport protocol, without fundamentally modifying it: building upon proven mechanisms.</p>
+HTTP frames are now transparent to Web developers. This is an additional step in HTTP/2, between HTTP/1.1 messages and the underlying transport protocol. No changes are needed in the APIs used by Web developers to utilize HTTP frames; when available in both the browser and the server, HTTP/2 is switched on and used.
+
+## Conclusion
+
+HTTP messages are the key in using HTTP; their structure is simple, and they are highly extensible. The HTTP/2 framing mechanism adds a new intermediate layer between the HTTP/1.x syntax and the underlying transport protocol, without fundamentally modifying it: building upon proven mechanisms.
diff --git a/files/en-us/web/http/methods/connect/index.md b/files/en-us/web/http/methods/connect/index.md
index e6a31a1e0d6f5a7..840faee8fa0cfdb 100644
--- a/files/en-us/web/http/methods/connect/index.md
+++ b/files/en-us/web/http/methods/connect/index.md
@@ -7,22 +7,20 @@ tags:
   - Request method
 browser-compat: http.methods.CONNECT
 ---
-<div>{{HTTPSidebar}}</div>
+{{HTTPSidebar}}
 
-<p>The <strong>HTTP <code>CONNECT</code> method</strong> starts two-way communications
-  with the requested resource. It can be used to open a tunnel.</p>
+The **HTTP `CONNECT` method** starts two-way communications
+with the requested resource. It can be used to open a tunnel.
 
-<p>For example, the <code>CONNECT</code> method can be used to access websites that use
-  {{Glossary("SSL")}} ({{Glossary("HTTPS")}}). The client asks an HTTP {{Glossary("Proxy
-  server")}} to tunnel the <a
-    href="/en-US/docs/Glossary/Transmission_Control_Protocol_(TCP)">TCP</a> connection to
-  the desired destination. The server then proceeds to make the connection on behalf of
-  the client. Once the connection has been established by the server, the
-  {{Glossary("Proxy server")}} continues to proxy the <a
-    href="/en-US/docs/Glossary/Transmission_Control_Protocol_(TCP)">TCP</a> stream to and
-  from the client.</p>
+For example, the `CONNECT` method can be used to access websites that use
+{{Glossary("SSL")}} ({{Glossary("HTTPS")}}). The client asks an HTTP {{Glossary("Proxy
+  server")}} to tunnel the [TCP](</en-US/docs/Glossary/Transmission_Control_Protocol_(TCP)>) connection to
+the desired destination. The server then proceeds to make the connection on behalf of
+the client. Once the connection has been established by the server, the
+{{Glossary("Proxy server")}} continues to proxy the [TCP](</en-US/docs/Glossary/Transmission_Control_Protocol_(TCP)>) stream to and
+from the client.
 
-<p><code>CONNECT</code> is a hop-by-hop method.</p>
+`CONNECT` is a hop-by-hop method.
 
 <table class="properties">
   <tbody>
@@ -47,38 +45,38 @@ browser-compat: http.methods.CONNECT
       <td>No</td>
     </tr>
     <tr>
-      <th scope="row">Allowed in <a href="/en-US/docs/Learn/Forms">HTML forms</a>
+      <th scope="row">
+        Allowed in <a href="/en-US/docs/Learn/Forms">HTML forms</a>
       </th>
       <td>No</td>
     </tr>
   </tbody>
 </table>
 
-<h2 id="Syntax">Syntax</h2>
+## Syntax
 
-<pre class="brush: html">CONNECT www.example.com:443 HTTP/1.1
-</pre>
+```html
+CONNECT www.example.com:443 HTTP/1.1
+```
 
-<h2 id="Example">Example</h2>
+## Example
 
-<p>Some proxy servers might need authority to create a tunnel. See also the
-  {{HTTPHeader("Proxy-Authorization")}} header.</p>
+Some proxy servers might need authority to create a tunnel. See also the
+{{HTTPHeader("Proxy-Authorization")}} header.
 
-<pre>CONNECT server.example.com:80 HTTP/1.1
-Host: server.example.com:80
-Proxy-Authorization: basic aGVsbG86d29ybGQ=</pre>
+    CONNECT server.example.com:80 HTTP/1.1
+    Host: server.example.com:80
+    Proxy-Authorization: basic aGVsbG86d29ybGQ=
 
-<h2 id="Specifications">Specifications</h2>
+## Specifications
 
 {{Specifications}}
 
-<h2 id="Browser_compatibility">Browser compatibility</h2>
+## Browser compatibility
 
-<p>{{Compat}}</p>
+{{Compat}}
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
-  <li>{{Glossary("Proxy server")}}</li>
-  <li>{{HTTPHeader("Proxy-Authorization")}}</li>
-</ul>
+- {{Glossary("Proxy server")}}
+- {{HTTPHeader("Proxy-Authorization")}}
diff --git a/files/en-us/web/http/methods/delete/index.md b/files/en-us/web/http/methods/delete/index.md
index 0c1699b9e295000..562b5552e4baeef 100644
--- a/files/en-us/web/http/methods/delete/index.md
+++ b/files/en-us/web/http/methods/delete/index.md
@@ -7,10 +7,10 @@ tags:
   - Request method
 browser-compat: http.methods.DELETE
 ---
-<div>{{HTTPSidebar}}</div>
+{{HTTPSidebar}}
 
-<p>The <strong>HTTP <code>DELETE</code> request method</strong> deletes the specified
-  resource.</p>
+The **HTTP `DELETE` request method** deletes the specified
+resource.
 
 <table class="properties">
   <tbody>
@@ -35,60 +35,58 @@ browser-compat: http.methods.DELETE
       <td>No</td>
     </tr>
     <tr>
-      <th scope="row">Allowed in <a href="/en-US/docs/Learn/Forms">HTML forms</a>
+      <th scope="row">
+        Allowed in <a href="/en-US/docs/Learn/Forms">HTML forms</a>
       </th>
       <td>No</td>
     </tr>
   </tbody>
 </table>
 
-<h2 id="Syntax">Syntax</h2>
+## Syntax
 
-<pre class="brush: html">DELETE /file.html HTTP/1.1
-</pre>
+```html
+DELETE /file.html HTTP/1.1
+```
 
-<h2 id="Example">Example</h2>
+## Example
 
-<h3 id="Request">Request</h3>
+### Request
 
-<pre>DELETE /file.html HTTP/1.1
-Host: example.com
-</pre>
+    DELETE /file.html HTTP/1.1
+    Host: example.com
 
-<h3 id="Responses">Responses</h3>
+### Responses
 
-<p>If a <code>DELETE</code> method is successfully applied, there are several response
-  status codes possible:</p>
+If a `DELETE` method is successfully applied, there are several response
+status codes possible:
 
-<ul>
-  <li>A {{HTTPStatus("202")}} (<code>Accepted</code>) status code if the action will
-    likely succeed but has not yet been enacted.</li>
-  <li>A {{HTTPStatus("204")}} (<code>No Content</code>) status code if the action has been
-    enacted and no further information is to be supplied.</li>
-  <li>A {{HTTPStatus("200")}} (<code>OK</code>) status code if the action has been enacted
-    and the response message includes a representation describing the status.</li>
-</ul>
+- A {{HTTPStatus("202")}} (`Accepted`) status code if the action will
+  likely succeed but has not yet been enacted.
+- A {{HTTPStatus("204")}} (`No Content`) status code if the action has been
+  enacted and no further information is to be supplied.
+- A {{HTTPStatus("200")}} (`OK`) status code if the action has been enacted
+  and the response message includes a representation describing the status.
 
-<pre>HTTP/1.1 200 OK
-Date: Wed, 21 Oct 2015 07:28:00 GMT
+<!---->
 
-&lt;html&gt;
-  &lt;body&gt;
-    &lt;h1&gt;File deleted.&lt;/h1&gt;
-  &lt;/body&gt;
-&lt;/html&gt;</pre>
+    HTTP/1.1 200 OK
+    Date: Wed, 21 Oct 2015 07:28:00 GMT
 
-<h2 id="Specifications">Specifications</h2>
+    <html>
+      <body>
+        <h1>File deleted.</h1>
+      </body>
+    </html>
+
+## Specifications
 
 {{Specifications}}
 
-<h2 id="Browser_compatibility">Browser compatibility</h2>
+## Browser compatibility
 
-<p>{{Compat}}</p>
+{{Compat}}
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
-  <li>HTTP status: {{HTTPStatus("200")}}, {{HTTPStatus("202")}}, {{HTTPStatus("204")}}
-  </li>
-</ul>
+- HTTP status: {{HTTPStatus("200")}}, {{HTTPStatus("202")}}, {{HTTPStatus("204")}}
diff --git a/files/en-us/web/http/methods/get/index.md b/files/en-us/web/http/methods/get/index.md
index 08869dd90657195..57595de0ec3d730 100644
--- a/files/en-us/web/http/methods/get/index.md
+++ b/files/en-us/web/http/methods/get/index.md
@@ -7,13 +7,11 @@ tags:
   - Request method
 browser-compat: http.methods.GET
 ---
-<p>{{HTTPSidebar}}</p>
+{{HTTPSidebar}}
 
-<p>The <strong>HTTP <code>GET</code> method</strong> requests a representation of the specified resource. Requests using <code>GET</code> should only be used to request data (they shouldn't include data).</p>
+The **HTTP `GET` method** requests a representation of the specified resource. Requests using `GET` should only be used to request data (they shouldn't include data).
 
-<div class="notecard note">
-  <p><strong>Note:</strong> Sending body/payload in a <code>GET</code> request may cause some existing implementations to reject the request — while not prohibited by the specification, the semantics are undefined. It is better to just avoid sending payloads in <code>GET</code> requests.</p>
-</div>
+> **Note:** Sending body/payload in a `GET` request may cause some existing implementations to reject the request — while not prohibited by the specification, the semantics are undefined. It is better to just avoid sending payloads in `GET` requests.
 
 <table class="properties">
   <tbody>
@@ -44,23 +42,22 @@ browser-compat: http.methods.GET
   </tbody>
 </table>
 
-<h2 id="Syntax">Syntax</h2>
+## Syntax
 
-<pre class="brush: html">GET /index.html
-</pre>
+```html
+GET /index.html
+```
 
-<h2 id="Specifications">Specifications</h2>
+## Specifications
 
 {{Specifications}}
 
-<h2 id="Browser_compatibility">Browser compatibility</h2>
+## Browser compatibility
 
-<p>{{Compat}}</p>
+{{Compat}}
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
- <li><a href="/en-US/docs/Web/HTTP/Headers">HTTP Headers</a></li>
- <li>{{HTTPHeader("Range")}}</li>
- <li>{{HTTPMethod("POST")}}</li>
-</ul>
+- [HTTP Headers](/en-US/docs/Web/HTTP/Headers)
+- {{HTTPHeader("Range")}}
+- {{HTTPMethod("POST")}}
diff --git a/files/en-us/web/http/methods/head/index.md b/files/en-us/web/http/methods/head/index.md
index 4139d67b49e2323..f4c42fbf6049286 100644
--- a/files/en-us/web/http/methods/head/index.md
+++ b/files/en-us/web/http/methods/head/index.md
@@ -7,15 +7,13 @@ tags:
   - Request method
 browser-compat: http.methods.HEAD
 ---
-<div>{{HTTPSidebar}}</div>
+{{HTTPSidebar}}
 
-<p>The <strong>HTTP <code>HEAD</code> method</strong> requests the <a href="/en-US/docs/Web/HTTP/Headers">headers</a> that would be returned if the <code>HEAD</code> request's URL was instead requested with the HTTP {{HTTPMethod("GET")}} method. For example, if a URL might produce a large download, a <code>HEAD</code> request could read its {{HTTPHeader("Content-Length")}} header to check the filesize without actually downloading the file.</p>
+The **HTTP `HEAD` method** requests the [headers](/en-US/docs/Web/HTTP/Headers) that would be returned if the `HEAD` request's URL was instead requested with the HTTP {{HTTPMethod("GET")}} method. For example, if a URL might produce a large download, a `HEAD` request could read its {{HTTPHeader("Content-Length")}} header to check the filesize without actually downloading the file.
 
-<div class="notecard warning">
-  <p><strong>Warning:</strong> A response to a <code>HEAD</code> method <em>should not</em> have a body. If it has one anyway, that body <strong>must be</strong> ignored: any {{glossary("Representation header", "representation headers")}} that might describe the erroneous body are instead assumed to describe the response which a similar <code>GET</code> request would have received.</p>
-</div>
+> **Warning:** A response to a `HEAD` method _should not_ have a body. If it has one anyway, that body **must be** ignored: any {{glossary("Representation header", "representation headers")}} that might describe the erroneous body are instead assumed to describe the response which a similar `GET` request would have received.
 
-<p>If the response to a <code>HEAD</code> request shows that a cached URL response is now outdated, the cached copy is invalidated even if no <code>GET</code> request was made.</p>
+If the response to a `HEAD` request shows that a cached URL response is now outdated, the cached copy is invalidated even if no `GET` request was made.
 
 <table class="properties">
   <tbody>
@@ -40,27 +38,28 @@ browser-compat: http.methods.HEAD
       <td>Yes</td>
     </tr>
     <tr>
-      <th scope="row">Allowed in <a href="/en-US/docs/Learn/Forms">HTML forms</a></th>
+      <th scope="row">
+        Allowed in <a href="/en-US/docs/Learn/Forms">HTML forms</a>
+      </th>
       <td>No</td>
     </tr>
   </tbody>
 </table>
 
-<h2 id="Syntax">Syntax</h2>
+## Syntax
 
-<pre class="brush: html">HEAD /index.html
-</pre>
+```html
+HEAD /index.html
+```
 
-<h2 id="Specifications">Specifications</h2>
+## Specifications
 
 {{Specifications}}
 
-<h2 id="Browser_compatibility">Browser compatibility</h2>
+## Browser compatibility
 
-<p>{{Compat}}</p>
+{{Compat}}
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
- <li>{{HTTPMethod("GET")}}</li>
-</ul>
+- {{HTTPMethod("GET")}}
diff --git a/files/en-us/web/http/methods/index.md b/files/en-us/web/http/methods/index.md
index d558bde85ad998e..7e1f7dc599573ab 100644
--- a/files/en-us/web/http/methods/index.md
+++ b/files/en-us/web/http/methods/index.md
@@ -7,61 +7,40 @@ tags:
   - Reference
 browser-compat: http.methods
 ---
-<div>{{HTTPSidebar}}</div>
-
-<p>HTTP defines a set of <strong>request methods</strong> to indicate the desired action to be performed for a given resource. Although they can also be nouns, these request methods are sometimes referred to as <em>HTTP verbs</em>. Each of them implements a different semantic, but some common features are shared by a group of them: e.g. a request method can be {{glossary("Safe/HTTP", "safe")}}, {{glossary("idempotent")}}, or {{glossary("cacheable")}}.</p>
-
-<dl>
- <dt><code><a href="/en-US/docs/Web/HTTP/Methods/GET">GET</a></code></dt>
- <dd>The <code>GET</code> method requests a representation of the specified resource. Requests using <code>GET</code> should only retrieve data.</dd>
- <dt><code><a href="/en-US/docs/Web/HTTP/Methods/HEAD">HEAD</a></code></dt>
- <dd>The <code>HEAD</code> method asks for a response identical to that of a <code>GET</code> request, but without the response body.</dd>
- <dt><code><a href="/en-US/docs/Web/HTTP/Methods/POST">POST</a></code></dt>
- <dd>The <code>POST</code> method is used to submit an entity to the specified resource, often causing a change in state or side effects on the server.</dd>
- <dt><code><a href="/en-US/docs/Web/HTTP/Methods/PUT">PUT</a></code></dt>
- <dd>The <code>PUT</code> method replaces all current representations of the target resource with the request payload.</dd>
- <dt><code><a href="/en-US/docs/Web/HTTP/Methods/DELETE">DELETE</a></code></dt>
- <dd>The <code>DELETE</code> method deletes the specified resource.</dd>
- <dt><code><a href="/en-US/docs/Web/HTTP/Methods/CONNECT">CONNECT</a></code></dt>
- <dd>The <code>CONNECT</code> method establishes a tunnel to the server identified by the target resource.</dd>
- <dt><code><a href="/en-US/docs/Web/HTTP/Methods/OPTIONS">OPTIONS</a></code></dt>
- <dd>The <code>OPTIONS</code> method is used to describe the communication options for the target resource.</dd>
- <dt><code><a href="/en-US/docs/Web/HTTP/Methods/TRACE">TRACE</a></code></dt>
- <dd>The <code>TRACE</code> method performs a message loop-back test along the path to the target resource.</dd>
- <dt><code><a href="/en-US/docs/Web/HTTP/Methods/PATCH">PATCH</a></code></dt>
- <dd>The <code>PATCH</code> method is used to apply partial modifications to a resource.</dd>
-</dl>
-
-<h2 id="Specifications">Specifications</h2>
-
-<table class="standard-table">
- <thead>
-  <tr>
-   <th scope="col">Specification</th>
-   <th scope="col">Title</th>
-   <th scope="col">Comment</th>
-  </tr>
- </thead>
- <tbody>
-  <tr>
-   <td>{{RFC("7231", "Request methods", "4")}}</td>
-   <td>Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content</td>
-   <td>Specifies GET, HEAD, POST, PUT, DELETE, CONNECT, OPTIONS, TRACE.</td>
-  </tr>
-  <tr>
-   <td>{{RFC("5789", "Patch method", "2")}}</td>
-   <td>PATCH Method for HTTP</td>
-   <td>Specifies PATCH.</td>
-  </tr>
- </tbody>
-</table>
-
-<h2 id="Browser_compatibility">Browser compatibility</h2>
-
-<p>{{Compat}}</p>
-
-<h2 id="See_also">See also</h2>
-
-<ul>
- <li><a href="/en-US/docs/Web/HTTP/Headers">HTTP headers</a></li>
-</ul>
+{{HTTPSidebar}}
+
+HTTP defines a set of **request methods** to indicate the desired action to be performed for a given resource. Although they can also be nouns, these request methods are sometimes referred to as _HTTP verbs_. Each of them implements a different semantic, but some common features are shared by a group of them: e.g. a request method can be {{glossary("Safe/HTTP", "safe")}}, {{glossary("idempotent")}}, or {{glossary("cacheable")}}.
+
+- [`GET`](/en-US/docs/Web/HTTP/Methods/GET)
+  - : The `GET` method requests a representation of the specified resource. Requests using `GET` should only retrieve data.
+- [`HEAD`](/en-US/docs/Web/HTTP/Methods/HEAD)
+  - : The `HEAD` method asks for a response identical to that of a `GET` request, but without the response body.
+- [`POST`](/en-US/docs/Web/HTTP/Methods/POST)
+  - : The `POST` method is used to submit an entity to the specified resource, often causing a change in state or side effects on the server.
+- [`PUT`](/en-US/docs/Web/HTTP/Methods/PUT)
+  - : The `PUT` method replaces all current representations of the target resource with the request payload.
+- [`DELETE`](/en-US/docs/Web/HTTP/Methods/DELETE)
+  - : The `DELETE` method deletes the specified resource.
+- [`CONNECT`](/en-US/docs/Web/HTTP/Methods/CONNECT)
+  - : The `CONNECT` method establishes a tunnel to the server identified by the target resource.
+- [`OPTIONS`](/en-US/docs/Web/HTTP/Methods/OPTIONS)
+  - : The `OPTIONS` method is used to describe the communication options for the target resource.
+- [`TRACE`](/en-US/docs/Web/HTTP/Methods/TRACE)
+  - : The `TRACE` method performs a message loop-back test along the path to the target resource.
+- [`PATCH`](/en-US/docs/Web/HTTP/Methods/PATCH)
+  - : The `PATCH` method is used to apply partial modifications to a resource.
+
+## Specifications
+
+| Specification                                        | Title                                                         | Comment                                                          |
+| ---------------------------------------------------- | ------------------------------------------------------------- | ---------------------------------------------------------------- |
+| {{RFC("7231", "Request methods", "4")}} | Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content | Specifies GET, HEAD, POST, PUT, DELETE, CONNECT, OPTIONS, TRACE. |
+| {{RFC("5789", "Patch method", "2")}}     | PATCH Method for HTTP                                         | Specifies PATCH.                                                 |
+
+## Browser compatibility
+
+{{Compat}}
+
+## See also
+
+- [HTTP headers](/en-US/docs/Web/HTTP/Headers)
diff --git a/files/en-us/web/http/methods/options/index.md b/files/en-us/web/http/methods/options/index.md
index dfac4688be15593..0ba14514819d1d5 100644
--- a/files/en-us/web/http/methods/options/index.md
+++ b/files/en-us/web/http/methods/options/index.md
@@ -7,9 +7,9 @@ tags:
   - Request method
 browser-compat: http.methods.OPTIONS
 ---
-<div>{{HTTPSidebar}}</div>
+{{HTTPSidebar}}
 
-<p>The <strong>HTTP <code>OPTIONS</code> method</strong> requests permitted communication options for a given URL or server. A client can specify a URL with this method, or an asterisk (<code>*</code>) to refer to the entire server.</p>
+The **HTTP `OPTIONS` method** requests permitted communication options for a given URL or server. A client can specify a URL with this method, or an asterisk (`*`) to refer to the entire server.
 
 <table class="properties">
   <tbody>
@@ -40,83 +40,83 @@ browser-compat: http.methods.OPTIONS
   </tbody>
 </table>
 
-<h2 id="Syntax">Syntax</h2>
+## Syntax
 
-<pre class="brush: html">OPTIONS /index.html HTTP/1.1
+```html
+OPTIONS /index.html HTTP/1.1
 OPTIONS * HTTP/1.1
-</pre>
-
-<h2 id="Examples">Examples</h2>
-
-<h3 id="Identifying_allowed_request_methods">Identifying allowed request methods</h3>
-
-<p>To find out which request methods a server supports, one can use the <code>curl</code> command-line program to issue an <code>OPTIONS</code> request:</p>
-
-<pre class="brush: bash">curl -X OPTIONS https://example.org -i</pre>
-
-<p>The response then contains an {{HTTPHeader("Allow")}} header that holds the allowed methods:</p>
-
-<pre>HTTP/1.1 204 No Content
-<mark>Allow: OPTIONS, GET, HEAD, POST</mark>
-Cache-Control: max-age=604800
-Date: Thu, 13 Oct 2016 11:45:00 GMT
-Server: EOS (lax004/2813)
-</pre>
-
-<h3 id="Preflighted_requests_in_CORS">Preflighted requests in CORS</h3>
-
-<p>In <a href="/en-US/docs/Web/HTTP/CORS">CORS</a>, a <a href="/en-US/docs/Glossary/Preflight_request">preflight request</a> is sent with the <code>OPTIONS</code> method so that the server can respond if it is acceptable to send the request. In this example, we will request permission for these parameters:</p>
-
-<ul>
- <li>The {{HTTPHeader("Access-Control-Request-Method")}} header sent in the preflight request tells the server that when the actual request is sent, it will have a {{HTTPMethod("POST")}} request method.</li>
- <li>The {{HTTPHeader("Access-Control-Request-Headers")}} header tells the server that when the actual request is sent, it will have the <code>X-PINGOTHER</code> and <code>Content-Type</code> headers.</li>
-</ul>
-
-<pre>OPTIONS /resources/post-here/ HTTP/1.1
-Host: bar.example
-Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
-Accept-Language: en-us,en;q=0.5
-Accept-Encoding: gzip,deflate
-Connection: keep-alive
-Origin: https://foo.example
-<mark>Access-Control-Request-Method: POST
-Access-Control-Request-Headers: X-PINGOTHER, Content-Type</mark></pre>
-
-<p>The server now can respond if it will accept a request under these circumstances. In this example, the server response says that:</p>
-
-<dl>
- <dt>{{HTTPHeader("Access-Control-Allow-Origin")}}</dt>
- <dd>The <code>https://foo.example</code> origin is permitted to request the <code>bar.example/resources/post-here/</code> URL via the following:</dd>
- <dt>{{HTTPHeader("Access-Control-Allow-Methods")}}</dt>
- <dd>{{HTTPMethod("POST")}}, {{HTTPMethod("GET")}}, and <code>OPTIONS</code> are permitted methods for the URL. (This header is similar to the {{HTTPHeader("Allow")}} response header, but used only for <a href="/en-US/docs/Web/HTTP/CORS">CORS</a>.)</dd>
- <dt>{{HTTPHeader("Access-Control-Allow-Headers")}}</dt>
- <dd>Any script inspecting the response is permitted to read the values of the <code>X-PINGOTHER</code> and <code>Content-Type</code> headers.</dd>
- <dt>{{HTTPHeader("Access-Control-Max-Age")}}</dt>
- <dd>The above permissions may be cached for 86,400 seconds (1 day).</dd>
-</dl>
-
-<pre>HTTP/1.1 204 No Content
-Date: Mon, 01 Dec 2008 01:15:39 GMT
-Server: Apache/2.0.61 (Unix)
-<mark>Access-Control-Allow-Origin: https://foo.example
-Access-Control-Allow-Methods: POST, GET, OPTIONS
-Access-Control-Allow-Headers: X-PINGOTHER, Content-Type
-Access-Control-Max-Age: 86400</mark>
-Vary: Accept-Encoding, Origin
-Keep-Alive: timeout=2, max=100
-Connection: Keep-Alive</pre>
-
-<h2 id="Specifications">Specifications</h2>
+```
+
+## Examples
+
+### Identifying allowed request methods
+
+To find out which request methods a server supports, one can use the `curl` command-line program to issue an `OPTIONS` request:
+
+```bash
+curl -X OPTIONS https://example.org -i
+```
+
+The response then contains an {{HTTPHeader("Allow")}} header that holds the allowed methods:
+
+    HTTP/1.1 204 No Content
+    Allow: OPTIONS, GET, HEAD, POST
+    Cache-Control: max-age=604800
+    Date: Thu, 13 Oct 2016 11:45:00 GMT
+    Server: EOS (lax004/2813)
+
+### Preflighted requests in CORS
+
+In [CORS](/en-US/docs/Web/HTTP/CORS), a [preflight request](/en-US/docs/Glossary/Preflight_request) is sent with the `OPTIONS` method so that the server can respond if it is acceptable to send the request. In this example, we will request permission for these parameters:
+
+- The {{HTTPHeader("Access-Control-Request-Method")}} header sent in the preflight request tells the server that when the actual request is sent, it will have a {{HTTPMethod("POST")}} request method.
+- The {{HTTPHeader("Access-Control-Request-Headers")}} header tells the server that when the actual request is sent, it will have the `X-PINGOTHER` and `Content-Type` headers.
+
+<!---->
+
+    OPTIONS /resources/post-here/ HTTP/1.1
+    Host: bar.example
+    Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
+    Accept-Language: en-us,en;q=0.5
+    Accept-Encoding: gzip,deflate
+    Connection: keep-alive
+    Origin: https://foo.example
+    Access-Control-Request-Method: POST
+    Access-Control-Request-Headers: X-PINGOTHER, Content-Type
+
+The server now can respond if it will accept a request under these circumstances. In this example, the server response says that:
+
+- {{HTTPHeader("Access-Control-Allow-Origin")}}
+  - : The `https://foo.example` origin is permitted to request the `bar.example/resources/post-here/` URL via the following:
+- {{HTTPHeader("Access-Control-Allow-Methods")}}
+  - : {{HTTPMethod("POST")}}, {{HTTPMethod("GET")}}, and `OPTIONS` are permitted methods for the URL. (This header is similar to the {{HTTPHeader("Allow")}} response header, but used only for [CORS](/en-US/docs/Web/HTTP/CORS).)
+- {{HTTPHeader("Access-Control-Allow-Headers")}}
+  - : Any script inspecting the response is permitted to read the values of the `X-PINGOTHER` and `Content-Type` headers.
+- {{HTTPHeader("Access-Control-Max-Age")}}
+  - : The above permissions may be cached for 86,400 seconds (1 day).
+
+<!---->
+
+    HTTP/1.1 204 No Content
+    Date: Mon, 01 Dec 2008 01:15:39 GMT
+    Server: Apache/2.0.61 (Unix)
+    Access-Control-Allow-Origin: https://foo.example
+    Access-Control-Allow-Methods: POST, GET, OPTIONS
+    Access-Control-Allow-Headers: X-PINGOTHER, Content-Type
+    Access-Control-Max-Age: 86400
+    Vary: Accept-Encoding, Origin
+    Keep-Alive: timeout=2, max=100
+    Connection: Keep-Alive
+
+## Specifications
 
 {{Specifications}}
 
-<h2 id="Browser_compatibility">Browser compatibility</h2>
+## Browser compatibility
 
-<p>{{Compat}}</p>
+{{Compat}}
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
- <li>{{HTTPHeader("Allow")}} header</li>
- <li><a href="/en-US/docs/Web/HTTP/CORS">CORS</a></li>
-</ul>
+- {{HTTPHeader("Allow")}} header
+- [CORS](/en-US/docs/Web/HTTP/CORS)
diff --git a/files/en-us/web/http/methods/patch/index.md b/files/en-us/web/http/methods/patch/index.md
index 91e47c8e8de821e..bef08960d5e2b68 100644
--- a/files/en-us/web/http/methods/patch/index.md
+++ b/files/en-us/web/http/methods/patch/index.md
@@ -6,21 +6,21 @@ tags:
   - Reference
   - Request method
 ---
-<div>{{HTTPSidebar}}</div>
+{{HTTPSidebar}}
 
-<p>The <strong>HTTP <code>PATCH</code> request method</strong> applies partial modifications to a resource.</p>
+The **HTTP `PATCH` request method** applies partial modifications to a resource.
 
-<p><code>PATCH</code> is somewhat analogous to the "update" concept found in {{Glossary("CRUD")}} (in general, HTTP is different than {{Glossary("CRUD")}}, and the two should not be confused).</p>
+`PATCH` is somewhat analogous to the "update" concept found in {{Glossary("CRUD")}} (in general, HTTP is different than {{Glossary("CRUD")}}, and the two should not be confused).
 
-<p>A <code>PATCH</code> request is considered a set of instructions on how to modify a resource. Contrast this with {{HTTPMethod("PUT")}}; which is a complete representation of a resource.</p>
+A `PATCH` request is considered a set of instructions on how to modify a resource. Contrast this with {{HTTPMethod("PUT")}}; which is a complete representation of a resource.
 
-<p>A <code>PATCH</code> is not necessarily idempotent, although it can be. Contrast this with {{HTTPMethod("PUT")}}; which is always idempotent. The word "idempotent" means that any number of repeated, identical requests will leave the resource in the same state. For example if an auto-incrementing counter field is an integral part of the resource, then a {{HTTPMethod("PUT")}} will naturally overwrite it (since it overwrites everything), but not necessarily so for <code>PATCH</code>.</p>
+A `PATCH` is not necessarily idempotent, although it can be. Contrast this with {{HTTPMethod("PUT")}}; which is always idempotent. The word "idempotent" means that any number of repeated, identical requests will leave the resource in the same state. For example if an auto-incrementing counter field is an integral part of the resource, then a {{HTTPMethod("PUT")}} will naturally overwrite it (since it overwrites everything), but not necessarily so for `PATCH`.
 
-<p><code>PATCH</code> (like {{HTTPMethod("POST")}}) <em>may</em> have side-effects on other resources.</p>
+`PATCH` (like {{HTTPMethod("POST")}}) _may_ have side-effects on other resources.
 
-<p>To find out whether a server supports <code>PATCH</code>, a server can advertise its support by adding it to the list in the {{HTTPHeader("Allow")}} or {{HTTPHeader("Access-Control-Allow-Methods")}} (for <a href="/en-US/docs/Web/HTTP/CORS">CORS</a>) response headers.</p>
+To find out whether a server supports `PATCH`, a server can advertise its support by adding it to the list in the {{HTTPHeader("Allow")}} or {{HTTPHeader("Access-Control-Allow-Methods")}} (for [CORS](/en-US/docs/Web/HTTP/CORS)) response headers.
 
-<p>Another (implicit) indication that <code>PATCH</code> is allowed, is the presence of the {{HTTPHeader("Accept-Patch")}} header, which specifies the patch document formats accepted by the server.</p>
+Another (implicit) indication that `PATCH` is allowed, is the presence of the {{HTTPHeader("Accept-Patch")}} header, which specifies the patch document formats accepted by the server.
 
 <table class="properties">
   <tbody>
@@ -45,60 +45,50 @@ tags:
       <td>No</td>
     </tr>
     <tr>
-      <th scope="row">Allowed in <a href="/en-US/docs/Learn/Forms">HTML forms</a></th>
+      <th scope="row">
+        Allowed in <a href="/en-US/docs/Learn/Forms">HTML forms</a>
+      </th>
       <td>No</td>
     </tr>
   </tbody>
 </table>
 
-<h2 id="Syntax">Syntax</h2>
+## Syntax
 
-<pre class="brush: html">PATCH /file.txt HTTP/1.1
-</pre>
+```html
+PATCH /file.txt HTTP/1.1
+```
 
-<h2 id="Example">Example</h2>
+## Example
 
-<h3 id="Request">Request</h3>
+### Request
 
-<pre>PATCH /file.txt HTTP/1.1
-Host: www.example.com
-Content-Type: application/example
-If-Match: "e0023aa4e"
-Content-Length: 100
+    PATCH /file.txt HTTP/1.1
+    Host: www.example.com
+    Content-Type: application/example
+    If-Match: "e0023aa4e"
+    Content-Length: 100
 
-[description of changes]</pre>
+    [description of changes]
 
-<h3 id="Response">Response</h3>
+### Response
 
-<p>A successful response is indicated by any <a href="https://datatracker.ietf.org/doc/html/rfc7231#section-6.3">2xx</a> status code.</p>
+A successful response is indicated by any [2xx](https://datatracker.ietf.org/doc/html/rfc7231#section-6.3) status code.
 
-<p>In the example below a {{HTTPStatus("204")}} response code is used, because the response does not carry a payload body. A {{HTTPStatus("200")}} response could have contained a payload body.</p>
+In the example below a {{HTTPStatus("204")}} response code is used, because the response does not carry a payload body. A {{HTTPStatus("200")}} response could have contained a payload body.
 
-<pre>HTTP/1.1 204 No Content
-Content-Location: /file.txt
-ETag: "e0023aa4f"</pre>
+    HTTP/1.1 204 No Content
+    Content-Location: /file.txt
+    ETag: "e0023aa4f"
 
-<h2 id="Specifications">Specifications</h2>
+## Specifications
 
-<table class="standard-table">
- <thead>
-  <tr>
-   <th scope="col">Specification</th>
-   <th scope="col">Title</th>
-  </tr>
- </thead>
- <tbody>
-  <tr>
-   <td>{{RFC("5789", "PATCH")}}</td>
-   <td>PATCH Method for HTTP</td>
-  </tr>
- </tbody>
-</table>
+| Specification                    | Title                 |
+| -------------------------------- | --------------------- |
+| {{RFC("5789", "PATCH")}} | PATCH Method for HTTP |
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
- <li>{{HTTPStatus("204")}}</li>
- <li>{{HTTPHeader("Allow")}}, {{HTTPHeader("Access-Control-Allow-Methods")}}</li>
- <li>{{HTTPHeader("Accept-Patch")}} – specifies the patch document formats accepted by the server.</li>
-</ul>
+- {{HTTPStatus("204")}}
+- {{HTTPHeader("Allow")}}, {{HTTPHeader("Access-Control-Allow-Methods")}}
+- {{HTTPHeader("Accept-Patch")}} – specifies the patch document formats accepted by the server.
diff --git a/files/en-us/web/http/methods/post/index.md b/files/en-us/web/http/methods/post/index.md
index e9155a94b1e1dd9..6b6351ee5a91f76 100644
--- a/files/en-us/web/http/methods/post/index.md
+++ b/files/en-us/web/http/methods/post/index.md
@@ -7,29 +7,25 @@ tags:
   - Request method
 browser-compat: http.methods.POST
 ---
-<p>{{HTTPSidebar}}</p>
+{{HTTPSidebar}}
 
-<p>The <strong>HTTP <code>POST</code> method</strong> sends data to the server. The type of the body of the request is indicated by the {{HTTPHeader("Content-Type")}} header.</p>
+The **HTTP `POST` method** sends data to the server. The type of the body of the request is indicated by the {{HTTPHeader("Content-Type")}} header.
 
-<p>The difference between {{HTTPMethod("PUT")}} and <code>POST</code> is that <code>PUT</code> is idempotent: calling it once or several times successively has the same effect (that is no <em>side</em> effect), where successive identical <code>POST</code> may have additional effects, like passing an order several times.</p>
+The difference between {{HTTPMethod("PUT")}} and `POST` is that `PUT` is idempotent: calling it once or several times successively has the same effect (that is no _side_ effect), where successive identical `POST` may have additional effects, like passing an order several times.
 
-<p>A <code>POST</code> request is typically sent via an <a href="/en-US/docs/Learn/Forms">HTML form</a> and results in a change on the server. In this case, the content type is selected by putting the adequate string in the {{htmlattrxref("enctype", "form")}} attribute of the {{HTMLElement("form")}} element or the {{htmlattrxref("formenctype", "input")}} attribute of the {{HTMLElement("input") }} or {{HTMLElement("button")}} elements:</p>
+A `POST` request is typically sent via an [HTML form](/en-US/docs/Learn/Forms) and results in a change on the server. In this case, the content type is selected by putting the adequate string in the {{htmlattrxref("enctype", "form")}} attribute of the {{HTMLElement("form")}} element or the {{htmlattrxref("formenctype", "input")}} attribute of the {{HTMLElement("input") }} or {{HTMLElement("button")}} elements:
 
-<ul>
- <li><code>application/x-www-form-urlencoded</code>: the keys and values are encoded in key-value tuples separated by <code>'&amp;'</code>, with a <code>'='</code> between the key and the value. Non-alphanumeric characters in both keys and values are {{glossary("percent-encoding", "percent encoded")}}: this is the reason why this type is not suitable to use with binary data (use <code>multipart/form-data</code> instead)</li>
- <li><code>multipart/form-data</code>: each value is sent as a block of data ("body part"), with a user agent-defined delimiter ("boundary") separating each part. The keys are given in the <code>Content-Disposition</code> header of each part.</li>
- <li><code>text/plain</code></li>
-</ul>
+- `application/x-www-form-urlencoded`: the keys and values are encoded in key-value tuples separated by `'&'`, with a `'='` between the key and the value. Non-alphanumeric characters in both keys and values are {{glossary("percent-encoding", "percent encoded")}}: this is the reason why this type is not suitable to use with binary data (use `multipart/form-data` instead)
+- `multipart/form-data`: each value is sent as a block of data ("body part"), with a user agent-defined delimiter ("boundary") separating each part. The keys are given in the `Content-Disposition` header of each part.
+- `text/plain`
 
-<p>When the <code>POST</code> request is sent via a method other than an HTML form — like via an {{domxref("XMLHttpRequest")}} — the body can take any type. As described in the HTTP 1.1 specification, <code>POST</code> is designed to allow a uniform method to cover the following functions:</p>
+When the `POST` request is sent via a method other than an HTML form — like via an {{domxref("XMLHttpRequest")}} — the body can take any type. As described in the HTTP 1.1 specification, `POST` is designed to allow a uniform method to cover the following functions:
 
-<ul>
- <li>Annotation of existing resources</li>
- <li>Posting a message to a bulletin board, newsgroup, mailing list, or similar group of articles;</li>
- <li>Adding a new user through a signup modal;</li>
- <li>Providing a block of data, such as the result of submitting a form, to a data-handling process;</li>
- <li>Extending a database through an append operation.</li>
-</ul>
+- Annotation of existing resources
+- Posting a message to a bulletin board, newsgroup, mailing list, or similar group of articles;
+- Adding a new user through a signup modal;
+- Providing a block of data, such as the result of submitting a form, to a data-handling process;
+- Extending a database through an append operation.
 
 <table class="properties">
   <tbody>
@@ -54,57 +50,57 @@ browser-compat: http.methods.POST
       <td>Only if freshness information is included</td>
     </tr>
     <tr>
-      <th scope="row">Allowed in <a href="/en-US/docs/Learn/Forms">HTML forms</a></th>
+      <th scope="row">
+        Allowed in <a href="/en-US/docs/Learn/Forms">HTML forms</a>
+      </th>
       <td>Yes</td>
     </tr>
   </tbody>
 </table>
 
-<h2 id="Syntax">Syntax</h2>
+## Syntax
 
-<pre class="brush: html">POST /test
-</pre>
+```html
+POST /test
+```
 
-<h2 id="Example">Example</h2>
+## Example
 
-<p>A simple form using the default <code>application/x-www-form-urlencoded</code> content type:</p>
+A simple form using the default `application/x-www-form-urlencoded` content type:
 
-<pre>POST /test HTTP/1.1
-Host: foo.example
-Content-Type: application/x-www-form-urlencoded
-Content-Length: 27
+    POST /test HTTP/1.1
+    Host: foo.example
+    Content-Type: application/x-www-form-urlencoded
+    Content-Length: 27
 
-field1=value1&amp;field2=value2</pre>
+    field1=value1&field2=value2
 
-<p>A form using the <code>multipart/form-data</code> content type:</p>
+A form using the `multipart/form-data` content type:
 
-<pre>POST /test HTTP/1.1
-Host: foo.example
-Content-Type: multipart/form-data;boundary="boundary"
+    POST /test HTTP/1.1
+    Host: foo.example
+    Content-Type: multipart/form-data;boundary="boundary"
 
---boundary
-Content-Disposition: form-data; name="field1"
+    --boundary
+    Content-Disposition: form-data; name="field1"
 
-value1
---boundary
-Content-Disposition: form-data; name="field2"; filename="example.txt"
+    value1
+    --boundary
+    Content-Disposition: form-data; name="field2"; filename="example.txt"
 
-value2
---boundary--
-</pre>
+    value2
+    --boundary--
 
-<h2 id="Specifications">Specifications</h2>
+## Specifications
 
 {{Specifications}}
 
-<h2 id="Browser_compatibility">Browser compatibility</h2>
+## Browser compatibility
 
-<p>{{Compat}}</p>
+{{Compat}}
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
- <li>{{HTTPHeader("Content-Type")}}</li>
- <li>{{HTTPHeader("Content-Disposition")}}</li>
- <li>{{HTTPMethod("GET")}}</li>
-</ul>
+- {{HTTPHeader("Content-Type")}}
+- {{HTTPHeader("Content-Disposition")}}
+- {{HTTPMethod("GET")}}
diff --git a/files/en-us/web/http/methods/put/index.md b/files/en-us/web/http/methods/put/index.md
index 457e7861b585030..b1b5e8febbf3987 100644
--- a/files/en-us/web/http/methods/put/index.md
+++ b/files/en-us/web/http/methods/put/index.md
@@ -7,11 +7,11 @@ tags:
   - Request method
 browser-compat: http.methods.PUT
 ---
-<div>{{HTTPSidebar}}</div>
+{{HTTPSidebar}}
 
-<p>The <strong>HTTP <code>PUT</code> request method</strong> creates a new resource or replaces a representation of the target resource with the request payload.</p>
+The **HTTP `PUT` request method** creates a new resource or replaces a representation of the target resource with the request payload.
 
-<p>The difference between <code>PUT</code> and {{HTTPMethod("POST")}} is that <code>PUT</code> is idempotent: calling it once or several times successively has the same effect (that is no <em>side</em> effect), whereas successive identical {{HTTPMethod("POST")}} requests may have additional effects, akin to placing an order several times.</p>
+The difference between `PUT` and {{HTTPMethod("POST")}} is that `PUT` is idempotent: calling it once or several times successively has the same effect (that is no _side_ effect), whereas successive identical {{HTTPMethod("POST")}} requests may have additional effects, akin to placing an order several times.
 
 <table class="properties">
   <tbody>
@@ -36,52 +36,52 @@ browser-compat: http.methods.PUT
       <td>No</td>
     </tr>
     <tr>
-      <th scope="row">Allowed in <a href="/en-US/docs/Learn/Forms">HTML forms</a></th>
+      <th scope="row">
+        Allowed in <a href="/en-US/docs/Learn/Forms">HTML forms</a>
+      </th>
       <td>No</td>
     </tr>
   </tbody>
 </table>
 
-<h2 id="Syntax">Syntax</h2>
+## Syntax
 
-<pre class="brush: html">PUT /new.html HTTP/1.1
-</pre>
+```html
+PUT /new.html HTTP/1.1
+```
 
-<h2 id="Example">Example</h2>
+## Example
 
-<h3 id="Request">Request</h3>
+### Request
 
-<pre>PUT /new.html HTTP/1.1
-Host: example.com
-Content-type: text/html
-Content-length: 16
+    PUT /new.html HTTP/1.1
+    Host: example.com
+    Content-type: text/html
+    Content-length: 16
 
-&lt;p&gt;New File&lt;/p&gt;</pre>
+    <p>New File</p>
 
-<h3 id="Responses">Responses</h3>
+### Responses
 
-<p>If the target resource does not have a current representation and the <code>PUT</code> request successfully creates one, then the origin server must inform the user agent by sending a {{HTTPStatus("201")}} (<code>Created</code>) response.</p>
+If the target resource does not have a current representation and the `PUT` request successfully creates one, then the origin server must inform the user agent by sending a {{HTTPStatus("201")}} (`Created`) response.
 
-<pre>HTTP/1.1 201 Created
-Content-Location: /new.html</pre>
+    HTTP/1.1 201 Created
+    Content-Location: /new.html
 
-<p>If the target resource does have a current representation and that representation is successfully modified in accordance with the state of the enclosed representation, then the origin server must send either a {{HTTPStatus("200")}} (<code>OK</code>) or a {{HTTPStatus("204")}} (<code>No Content</code>) response to indicate successful completion of the request.</p>
+If the target resource does have a current representation and that representation is successfully modified in accordance with the state of the enclosed representation, then the origin server must send either a {{HTTPStatus("200")}} (`OK`) or a {{HTTPStatus("204")}} (`No Content`) response to indicate successful completion of the request.
 
-<pre>HTTP/1.1 204 No Content
-Content-Location: /existing.html
-</pre>
+    HTTP/1.1 204 No Content
+    Content-Location: /existing.html
 
-<h2 id="Specifications">Specifications</h2>
+## Specifications
 
 {{Specifications}}
 
-<h2 id="Browser_compatibility">Browser compatibility</h2>
+## Browser compatibility
 
-<p>{{Compat}}</p>
+{{Compat}}
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
- <li>{{HTTPStatus("201")}}</li>
- <li>{{HTTPStatus("204")}}</li>
-</ul>
+- {{HTTPStatus("201")}}
+- {{HTTPStatus("204")}}
diff --git a/files/en-us/web/http/methods/trace/index.md b/files/en-us/web/http/methods/trace/index.md
index ca9cfc1c9f2dcdf..0af4762aa7cec53 100644
--- a/files/en-us/web/http/methods/trace/index.md
+++ b/files/en-us/web/http/methods/trace/index.md
@@ -7,11 +7,11 @@ tags:
   - Request method
 browser-compat: http.methods.TRACE
 ---
-<div>{{HTTPSidebar}}</div>
+{{HTTPSidebar}}
 
-<p>The <strong>HTTP <code>TRACE</code> method</strong> performs a message loop-back test along the path to the target resource, providing a useful debugging mechanism.</p>
+The **HTTP `TRACE` method** performs a message loop-back test along the path to the target resource, providing a useful debugging mechanism.
 
-<p>The final recipient of the request should reflect the message received, excluding some fields described below, back to the client as the message body of a {{HTTPStatus("200")}} (<code>OK</code>) response with a {{HTTPHeader("Content-Type")}} of <code>message/http</code>. The final recipient is either the origin server or the first server to receive a {{HTTPHeader("Max-Forwards")}} value of 0 in the request.</p>
+The final recipient of the request should reflect the message received, excluding some fields described below, back to the client as the message body of a {{HTTPStatus("200")}} (`OK`) response with a {{HTTPHeader("Content-Type")}} of `message/http`. The final recipient is either the origin server or the first server to receive a {{HTTPHeader("Max-Forwards")}} value of 0 in the request.
 
 <table class="properties">
   <tbody>
@@ -42,21 +42,20 @@ browser-compat: http.methods.TRACE
   </tbody>
 </table>
 
-<h2 id="Syntax">Syntax</h2>
+## Syntax
 
-<pre class="brush: html">TRACE /index.html
-</pre>
+```html
+TRACE /index.html
+```
 
-<h2 id="Specifications">Specifications</h2>
+## Specifications
 
 {{Specifications}}
 
-<h2 id="Browser_compatibility">Browser compatibility</h2>
+## Browser compatibility
 
-<p>{{Compat}}</p>
+{{Compat}}
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
- <li><a href="/en-US/docs/Web/HTTP/Methods">HTTP methods</a></li>
-</ul>
+- [HTTP methods](/en-US/docs/Web/HTTP/Methods)
diff --git a/files/en-us/web/http/network_error_logging/index.md b/files/en-us/web/http/network_error_logging/index.md
index 07506305e68144b..cfb427df7fbe8bc 100644
--- a/files/en-us/web/http/network_error_logging/index.md
+++ b/files/en-us/web/http/network_error_logging/index.md
@@ -7,55 +7,50 @@ tags:
   - Network Error Logging
   - Reference
 ---
-<div>{{HTTPSidebar}}{{SeeCompatTable}}</div>
+{{HTTPSidebar}}{{SeeCompatTable}}
 
-<p>Network Error Logging is a mechanism that can be configured via the {{HTTPHeader("NEL")}} HTTP <em><a href="/en-US/docs/Glossary/Response_header">response header</a></em>. This experimental header allows web sites and applications to opt-in to receive reports about failed (and, if desired, successful) network fetches from supporting browsers.</p>
+Network Error Logging is a mechanism that can be configured via the {{HTTPHeader("NEL")}} HTTP _[response header](/en-US/docs/Glossary/Response_header)_. This experimental header allows web sites and applications to opt-in to receive reports about failed (and, if desired, successful) network fetches from supporting browsers.
 
-<p>Reports are sent to a reporting group defined within a {{HTTPHeader("Report-To")}} header.</p>
+Reports are sent to a reporting group defined within a {{HTTPHeader("Report-To")}} header.
 
-<h2 id="Usage">Usage</h2>
+## Usage
 
-<p>Web applications opt in to this behavior with the NEL header, which is a <em><a href="/en-US/docs/Glossary/Response_header">JSON-encoded</a></em> object:</p>
+Web applications opt in to this behavior with the NEL header, which is a _[JSON-encoded](/en-US/docs/Glossary/Response_header)_ object:
 
-<pre><a href="https://www.w3.org/TR/network-error-logging/#nel-response-header">NEL</a>: { "<a href="https://www.w3.org/TR/network-error-logging/#the-report_to-member">report_to</a>": "nel",
-       "<a href="https://www.w3.org/TR/network-error-logging/#the-max_age-member">max_age</a>": 31556952 }
-</pre>
+    NEL: { "report_to": "nel",
+           "max_age": 31556952 }
 
-<p>An origin considered secure by the browser is required.</p>
+An origin considered secure by the browser is required.
 
-<p>The following object keys can be specified in the NEL header:</p>
+The following object keys can be specified in the NEL header:
 
-<dl>
- <dt>report_to</dt>
- <dd>
- <p>The <a href="/en-US/docs/Web/API/Reporting_API">reporting API</a> group to send network error reports to (see below).</p>
- </dd>
- <dt>max_age</dt>
- <dd>Specifies the lifetime of the policy, in seconds (in a similar way to e.g. HSTS policies are time-restricted). The referenced reporting group should have a lifetime at least as long as the NEL policy.</dd>
- <dt>include_subdomains</dt>
- <dd>If true, the policy applies to all subdomains under the origin that the policy header is set. The reporting group should also be set to include subdomains, if this option is to be enabled.</dd>
- <dt>success_fraction</dt>
- <dd>Floating point value between 0 and 1 which specifies the proportion of <strong>successful</strong> network requests to report. Defaults to 0, so that no successful network requests will be reported if the key is not present in the JSON payload.</dd>
- <dt>failure_fraction</dt>
- <dd>Floating point value between 0 and 1 which specifies the proportion of <strong>failed</strong> network requests to report. Defaults to 1, so that all failed network requests will be reported if the key is not present in the JSON payload.</dd>
-</dl>
+- report_to
+  - : The [reporting API](/en-US/docs/Web/API/Reporting_API) group to send network error reports to (see below).
+- max_age
+  - : Specifies the lifetime of the policy, in seconds (in a similar way to e.g. HSTS policies are time-restricted). The referenced reporting group should have a lifetime at least as long as the NEL policy.
+- include_subdomains
+  - : If true, the policy applies to all subdomains under the origin that the policy header is set. The reporting group should also be set to include subdomains, if this option is to be enabled.
+- success_fraction
+  - : Floating point value between 0 and 1 which specifies the proportion of **successful** network requests to report. Defaults to 0, so that no successful network requests will be reported if the key is not present in the JSON payload.
+- failure_fraction
+  - : Floating point value between 0 and 1 which specifies the proportion of **failed** network requests to report. Defaults to 1, so that all failed network requests will be reported if the key is not present in the JSON payload.
 
-<p>The reporting group referenced above is defined in the usual manner within the {{HTTPHeader("Report-To")}} header, for example:</p>
+The reporting group referenced above is defined in the usual manner within the {{HTTPHeader("Report-To")}} header, for example:
 
-<pre><a href="https://wicg.github.io/reporting/#report-to" id="ref-for-report-to①">Report-To</a>: { "<a href="https://wicg.github.io/reporting/#group" id="ref-for-group①">group</a>": "nel",
-             "<a href="https://wicg.github.io/reporting/#max-age" id="ref-for-max-age①">max_age</a>": 31556952,
-             "<a href="https://wicg.github.io/reporting/#endpoints" id="ref-for-endpoints②">endpoints</a>": [
-               { "<a href="https://wicg.github.io/reporting/#url" id="ref-for-url②">url</a>": "https://example.com/csp-reports" }
-             ] }
-</pre>
+    Report-To: { "group": "nel",
+                 "max_age": 31556952,
+                 "endpoints": [
+                   { "url": "https://example.com/csp-reports" }
+                 ] }
 
-<h2 id="Error_reports">Error reports</h2>
+## Error reports
 
-<p>In these examples, the entire reporting API payload is shown. The top-level <strong><code>"body"</code></strong> key contains the network error report.</p>
+In these examples, the entire reporting API payload is shown. The top-level **`"body"`** key contains the network error report.
 
-<h3 id="HTTP_400_Bad_Request_response">HTTP 400 (Bad Request) response</h3>
+### HTTP 400 (Bad Request) response
 
-<pre class="brush: js">{
+```js
+{
   "age": 20,
   "type": "network-error",
   "url": "https://example.com/previous-page",
@@ -72,13 +67,14 @@ tags:
     "url": "https://example.com/bad-request"
   }
 }
-</pre>
+```
 
-<h3 id="DNS_name_not_resolved">DNS name not resolved</h3>
+### DNS name not resolved
 
-<p>Note that the phase is set to <code>dns</code> in this report and no <code>server_ip</code> is available to include.</p>
+Note that the phase is set to `dns` in this report and no `server_ip` is available to include.
 
-<pre class="brush: js">{
+```js
+{
   "age": 20,
   "type": "network-error",
   "url": "https://example.com/previous-page",
@@ -95,60 +91,51 @@ tags:
     "url": "https://example-host.com/"
   }
 }
-</pre>
-
-<p>The type of the network error may be one of the following pre-defined values from the specification, but browsers can add and send their own error types:</p>
-
-<dl>
- <dt><code>dns.unreachable</code></dt>
- <dd>The user's DNS server is unreachable</dd>
- <dt><code>dns.name_not_resolved</code></dt>
- <dd>The user's DNS server responded but was unable to resolve an IP address for the requested URI.</dd>
- <dt><code>dns.failed</code></dt>
- <dd>Request to the DNS server failed due to reasons not covered by previous errors (e.g. SERVFAIL)</dd>
- <dt><code>dns.address_changed</code></dt>
- <dd>For security reasons, if the server IP address that delivered the original report is different to the current server IP address at time of error generation, the report data will be downgraded to only include information about this problem and the type set to <code>dns.address_changed</code>.</dd>
- <dt><code>tcp.timed_out</code></dt>
- <dd>TCP connection to the server timed out</dd>
- <dt><code>tcp.closed</code></dt>
- <dd>The TCP connection was closed by the server</dd>
- <dt><code>tcp.reset</code></dt>
- <dd>The TCP connection was reset</dd>
- <dt><code>tcp.refused</code></dt>
- <dd>The TCP connection was refused by the server</dd>
- <dt><code>tcp.aborted</code></dt>
- <dd>The TCP connection was aborted</dd>
- <dt><code>tcp.address_invalid</code></dt>
- <dd>The IP address is invalid</dd>
- <dt><code>tcp.address_unreachable</code></dt>
- <dd>The IP address is unreachable</dd>
- <dt><code>tcp.failed</code></dt>
- <dd>The TCP connection failed due to reasons not covered by previous errors</dd>
- <dt><code>http.error</code></dt>
- <dd>The user agent successfully received a response, but it had a <a href="https://datatracker.ietf.org/doc/html/rfc7231#section-6.5">4xx</a> or <a href="https://datatracker.ietf.org/doc/html/rfc7231#section-6.6">5xx</a> status code</dd>
- <dt><code>http.protocol.error</code></dt>
- <dd>The connection was aborted due to an HTTP protocol error</dd>
- <dt><code>http.response.invalid</code></dt>
- <dd>Response is empty, has a content-length mismatch, has improper encoding, and/or other conditions that prevent user agent from processing the response</dd>
- <dt><code>http.response.redirect_loop</code></dt>
- <dd>The request was aborted due to a detected redirect loop</dd>
- <dt><code>http.failed</code></dt>
- <dd>The connection failed due to errors in HTTP protocol not covered by previous errors</dd>
-</dl>
-
-<h2 id="Specifications">Specifications</h2>
-
-<table class="standard-table">
- <tbody>
-  <tr>
-   <th scope="col">Specification</th>
-  </tr>
-  <tr>
-   <td><a href="https://w3c.github.io/network-error-logging/#introduction">Network Error Logging</a></td>
-  </tr>
- </tbody>
-</table>
-
-<h2 id="Browser_compatibility">Browser compatibility</h2>
-
-<p>{{Compat("http.headers.NEL")}}</p>
+```
+
+The type of the network error may be one of the following pre-defined values from the specification, but browsers can add and send their own error types:
+
+- `dns.unreachable`
+  - : The user's DNS server is unreachable
+- `dns.name_not_resolved`
+  - : The user's DNS server responded but was unable to resolve an IP address for the requested URI.
+- `dns.failed`
+  - : Request to the DNS server failed due to reasons not covered by previous errors (e.g. SERVFAIL)
+- `dns.address_changed`
+  - : For security reasons, if the server IP address that delivered the original report is different to the current server IP address at time of error generation, the report data will be downgraded to only include information about this problem and the type set to `dns.address_changed`.
+- `tcp.timed_out`
+  - : TCP connection to the server timed out
+- `tcp.closed`
+  - : The TCP connection was closed by the server
+- `tcp.reset`
+  - : The TCP connection was reset
+- `tcp.refused`
+  - : The TCP connection was refused by the server
+- `tcp.aborted`
+  - : The TCP connection was aborted
+- `tcp.address_invalid`
+  - : The IP address is invalid
+- `tcp.address_unreachable`
+  - : The IP address is unreachable
+- `tcp.failed`
+  - : The TCP connection failed due to reasons not covered by previous errors
+- `http.error`
+  - : The user agent successfully received a response, but it had a [4xx](https://datatracker.ietf.org/doc/html/rfc7231#section-6.5) or [5xx](https://datatracker.ietf.org/doc/html/rfc7231#section-6.6) status code
+- `http.protocol.error`
+  - : The connection was aborted due to an HTTP protocol error
+- `http.response.invalid`
+  - : Response is empty, has a content-length mismatch, has improper encoding, and/or other conditions that prevent user agent from processing the response
+- `http.response.redirect_loop`
+  - : The request was aborted due to a detected redirect loop
+- `http.failed`
+  - : The connection failed due to errors in HTTP protocol not covered by previous errors
+
+## Specifications
+
+| Specification                                                                      |
+| ---------------------------------------------------------------------------------- |
+| [Network Error Logging](https://w3c.github.io/network-error-logging/#introduction) |
+
+## Browser compatibility
+
+{{Compat("http.headers.NEL")}}
diff --git a/files/en-us/web/http/overview/index.md b/files/en-us/web/http/overview/index.md
index 5493ccba1b339c2..81da186c24a4c8f 100644
--- a/files/en-us/web/http/overview/index.md
+++ b/files/en-us/web/http/overview/index.md
@@ -8,171 +8,163 @@ tags:
   - WebMechanics
   - l10n:priority
 ---
-<div>{{HTTPSidebar}}</div>
+{{HTTPSidebar}}
 
-<p class="summary"><strong>HTTP</strong> is a {{Glossary("protocol")}} which allows the fetching of resources, such as HTML documents. It is the foundation of any data exchange on the Web and it is a client-server protocol, which means requests are initiated by the recipient, usually the Web browser. A complete document is reconstructed from the different sub-documents fetched, for instance text, layout description, images, videos, scripts, and more.</p>
+**HTTP** is a {{Glossary("protocol")}} which allows the fetching of resources, such as HTML documents. It is the foundation of any data exchange on the Web and it is a client-server protocol, which means requests are initiated by the recipient, usually the Web browser. A complete document is reconstructed from the different sub-documents fetched, for instance text, layout description, images, videos, scripts, and more.
 
-<p><img alt="A Web document is the composition of different resources" src="fetching_a_page.png"></p>
+![A Web document is the composition of different resources](fetching_a_page.png)
 
-<p>Clients and servers communicate by exchanging individual messages (as opposed to a stream of data). The messages sent by the client, usually a Web browser, are called <em>requests</em> and the messages sent by the server as an answer are called <em>responses</em>.</p>
+Clients and servers communicate by exchanging individual messages (as opposed to a stream of data). The messages sent by the client, usually a Web browser, are called _requests_ and the messages sent by the server as an answer are called _responses_.
 
-<p><img alt="HTTP as an application layer protocol, on top of TCP (transport layer) and IP (network layer) and below the presentation layer." src="http-layers.png">Designed in the early 1990s, HTTP is an extensible protocol which has evolved over time. It is an application layer protocol that is sent over {{Glossary("TCP")}}, or over a {{Glossary("TLS")}}-encrypted TCP connection, though any reliable transport protocol could theoretically be used. Due to its extensibility, it is used to not only fetch hypertext documents, but also images and videos or to post content to servers, like with HTML form results. HTTP can also be used to fetch parts of documents to update Web pages on demand.</p>
+![HTTP as an application layer protocol, on top of TCP (transport layer) and IP (network layer) and below the presentation layer.](http-layers.png)Designed in the early 1990s, HTTP is an extensible protocol which has evolved over time. It is an application layer protocol that is sent over {{Glossary("TCP")}}, or over a {{Glossary("TLS")}}-encrypted TCP connection, though any reliable transport protocol could theoretically be used. Due to its extensibility, it is used to not only fetch hypertext documents, but also images and videos or to post content to servers, like with HTML form results. HTTP can also be used to fetch parts of documents to update Web pages on demand.
 
-<h2 id="Components_of_HTTP-based_systems">Components of HTTP-based systems</h2>
+## Components of HTTP-based systems
 
-<p>HTTP is a client-server protocol: requests are sent by one entity, the user-agent (or a proxy on behalf of it). Most of the time the user-agent is a Web browser, but it can be anything, for example a robot that crawls the Web to populate and maintain a search engine index.</p>
+HTTP is a client-server protocol: requests are sent by one entity, the user-agent (or a proxy on behalf of it). Most of the time the user-agent is a Web browser, but it can be anything, for example a robot that crawls the Web to populate and maintain a search engine index.
 
-<p>Each individual request is sent to a server, which handles it and provides an answer, called the <em>response</em>. Between the client and the server there are numerous entities, collectively called {{Glossary("Proxy_server", "proxies")}}, which perform different operations and act as gateways or {{Glossary("Cache", "caches")}}, for example.</p>
+Each individual request is sent to a server, which handles it and provides an answer, called the _response_. Between the client and the server there are numerous entities, collectively called {{Glossary("Proxy_server", "proxies")}}, which perform different operations and act as gateways or {{Glossary("Cache", "caches")}}, for example.
 
-<p><img alt="Client server chain" src="client-server-chain.png"></p>
+![Client server chain](client-server-chain.png)
 
-<p>In reality, there are more computers between a browser and the server handling the request: there are routers, modems, and more. Thanks to the layered design of the Web, these are hidden in the network and transport layers. HTTP is on top, at the application layer. Although important to diagnose network problems, the underlying layers are mostly irrelevant to the description of HTTP.</p>
+In reality, there are more computers between a browser and the server handling the request: there are routers, modems, and more. Thanks to the layered design of the Web, these are hidden in the network and transport layers. HTTP is on top, at the application layer. Although important to diagnose network problems, the underlying layers are mostly irrelevant to the description of HTTP.
 
-<h3 id="Client_the_user-agent">Client: the user-agent</h3>
+### Client: the user-agent
 
-<p>The <em>user-agent</em> is any tool that acts on the behalf of the user. This role is primarily performed by the Web browser; other possibilities are programs used by engineers and Web developers to debug their applications.</p>
+The _user-agent_ is any tool that acts on the behalf of the user. This role is primarily performed by the Web browser; other possibilities are programs used by engineers and Web developers to debug their applications.
 
-<p>The browser is <strong>always</strong> the entity initiating the request. It is never the server (though some mechanisms have been added over the years to simulate server-initiated messages).</p>
+The browser is **always** the entity initiating the request. It is never the server (though some mechanisms have been added over the years to simulate server-initiated messages).
 
-<p>To present a Web page, the browser sends an original request to fetch the HTML document that represents the page. It then parses this file, making additional requests corresponding to execution scripts, layout information (CSS) to display, and sub-resources contained within the page (usually images and videos). The Web browser then mixes these resources to present to the user a complete document, the Web page. Scripts executed by the browser can fetch more resources in later phases and the browser updates the Web page accordingly.</p>
+To present a Web page, the browser sends an original request to fetch the HTML document that represents the page. It then parses this file, making additional requests corresponding to execution scripts, layout information (CSS) to display, and sub-resources contained within the page (usually images and videos). The Web browser then mixes these resources to present to the user a complete document, the Web page. Scripts executed by the browser can fetch more resources in later phases and the browser updates the Web page accordingly.
 
-<p>A Web page is a hypertext document. This means some parts of displayed text are links which can be activated (usually by a click of the mouse) to fetch a new Web page, allowing the user to direct their user-agent and navigate through the Web. The browser translates these directions in HTTP requests, and further interprets the HTTP responses to present the user with a clear response.</p>
+A Web page is a hypertext document. This means some parts of displayed text are links which can be activated (usually by a click of the mouse) to fetch a new Web page, allowing the user to direct their user-agent and navigate through the Web. The browser translates these directions in HTTP requests, and further interprets the HTTP responses to present the user with a clear response.
 
-<h3 id="The_Web_server">The Web server</h3>
+### The Web server
 
-<p>On the opposite side of the communication channel, is the server, which <em>serves</em> the document as requested by the client. A server appears as only a single machine virtually: this is because it may actually be a collection of servers, sharing the load (load balancing) or a complex piece of software interrogating other computers (like cache, a DB server, or e-commerce servers), totally or partially generating the document on demand.</p>
+On the opposite side of the communication channel, is the server, which _serves_ the document as requested by the client. A server appears as only a single machine virtually: this is because it may actually be a collection of servers, sharing the load (load balancing) or a complex piece of software interrogating other computers (like cache, a DB server, or e-commerce servers), totally or partially generating the document on demand.
 
-<p>A server is not necessarily a single machine, but several server software instances can be hosted on the same machine. With HTTP/1.1 and the {{HTTPHeader("Host")}} header, they may even share the same IP address.</p>
+A server is not necessarily a single machine, but several server software instances can be hosted on the same machine. With HTTP/1.1 and the {{HTTPHeader("Host")}} header, they may even share the same IP address.
 
-<h3 id="Proxies">Proxies</h3>
+### Proxies
 
-<p>Between the Web browser and the server, numerous computers and machines relay the HTTP messages. Due to the layered structure of the Web stack, most of these operate at the transport, network or physical levels, becoming transparent at the HTTP layer and potentially making a significant impact on performance. Those operating at the application layers are generally called <strong>proxies</strong>. These can be transparent, forwarding on the requests they receive without altering them in any way, or non-transparent, in which case they will change the request in some way before passing it along to the server. Proxies may perform numerous functions:</p>
+Between the Web browser and the server, numerous computers and machines relay the HTTP messages. Due to the layered structure of the Web stack, most of these operate at the transport, network or physical levels, becoming transparent at the HTTP layer and potentially making a significant impact on performance. Those operating at the application layers are generally called **proxies**. These can be transparent, forwarding on the requests they receive without altering them in any way, or non-transparent, in which case they will change the request in some way before passing it along to the server. Proxies may perform numerous functions:
 
-<ul>
- <li>caching (the cache can be public or private, like the browser cache)</li>
- <li>filtering (like an antivirus scan or parental controls)</li>
- <li>load balancing (to allow multiple servers to serve the different requests)</li>
- <li>authentication (to control access to different resources)</li>
- <li>logging (allowing the storage of historical information)</li>
-</ul>
+- caching (the cache can be public or private, like the browser cache)
+- filtering (like an antivirus scan or parental controls)
+- load balancing (to allow multiple servers to serve the different requests)
+- authentication (to control access to different resources)
+- logging (allowing the storage of historical information)
 
-<h2 id="Basic_aspects_of_HTTP">Basic aspects of HTTP</h2>
+## Basic aspects of HTTP
 
-<h3 id="HTTP_is_simple">HTTP is simple</h3>
+### HTTP is simple
 
-<p>HTTP is generally designed to be simple and human readable, even with the added complexity introduced in HTTP/2 by encapsulating HTTP messages into frames. HTTP messages can be read and understood by humans, providing easier testing for developers, and reduced complexity for newcomers.</p>
+HTTP is generally designed to be simple and human readable, even with the added complexity introduced in HTTP/2 by encapsulating HTTP messages into frames. HTTP messages can be read and understood by humans, providing easier testing for developers, and reduced complexity for newcomers.
 
-<h3 id="HTTP_is_extensible">HTTP is extensible</h3>
+### HTTP is extensible
 
-<p>Introduced in HTTP/1.0, <a href="/en-US/docs/Web/HTTP/Headers">HTTP headers</a> make this protocol easy to extend and experiment with. New functionality can even be introduced by a simple agreement between a client and a server about a new header's semantics.</p>
+Introduced in HTTP/1.0, [HTTP headers](/en-US/docs/Web/HTTP/Headers) make this protocol easy to extend and experiment with. New functionality can even be introduced by a simple agreement between a client and a server about a new header's semantics.
 
-<h3 id="HTTP_is_stateless_but_not_sessionless">HTTP is stateless, but not sessionless</h3>
+### HTTP is stateless, but not sessionless
 
-<p>HTTP is stateless: there is no link between two requests being successively carried out on the same connection. This immediately has the prospect of being problematic for users attempting to interact with certain pages coherently, for example, using e-commerce shopping baskets. But while the core of HTTP itself is stateless, HTTP cookies allow the use of stateful sessions. Using header extensibility, HTTP Cookies are added to the workflow, allowing session creation on each HTTP request to share the same context, or the same state.</p>
+HTTP is stateless: there is no link between two requests being successively carried out on the same connection. This immediately has the prospect of being problematic for users attempting to interact with certain pages coherently, for example, using e-commerce shopping baskets. But while the core of HTTP itself is stateless, HTTP cookies allow the use of stateful sessions. Using header extensibility, HTTP Cookies are added to the workflow, allowing session creation on each HTTP request to share the same context, or the same state.
 
-<h3 id="HTTP_and_connections">HTTP and connections</h3>
+### HTTP and connections
 
-<p>A connection is controlled at the transport layer, and therefore fundamentally out of scope for HTTP. Though HTTP doesn't require the underlying transport protocol to be connection-based; only requiring it to be <em>reliable</em>, or not lose messages (so at minimum presenting an error). Among the two most common transport protocols on the Internet, TCP is reliable and UDP isn't. HTTP therefore relies on the TCP standard, which is connection-based.</p>
+A connection is controlled at the transport layer, and therefore fundamentally out of scope for HTTP. Though HTTP doesn't require the underlying transport protocol to be connection-based; only requiring it to be _reliable_, or not lose messages (so at minimum presenting an error). Among the two most common transport protocols on the Internet, TCP is reliable and UDP isn't. HTTP therefore relies on the TCP standard, which is connection-based.
 
-<p>Before a client and server can exchange an HTTP request/response pair, they must establish a TCP connection, a process which requires several round-trips. The default behavior of HTTP/1.0 is to open a separate TCP connection for each HTTP request/response pair. This is less efficient than sharing a single TCP connection when multiple requests are sent in close succession.</p>
+Before a client and server can exchange an HTTP request/response pair, they must establish a TCP connection, a process which requires several round-trips. The default behavior of HTTP/1.0 is to open a separate TCP connection for each HTTP request/response pair. This is less efficient than sharing a single TCP connection when multiple requests are sent in close succession.
 
-<p>In order to mitigate this flaw, HTTP/1.1 introduced <em>pipelining</em> (which proved difficult to implement) and <em>persistent connections</em>: the underlying TCP connection can be partially controlled using the {{HTTPHeader("Connection")}} header. HTTP/2 went a step further by multiplexing messages over a single connection, helping keep the connection warm and more efficient.</p>
+In order to mitigate this flaw, HTTP/1.1 introduced _pipelining_ (which proved difficult to implement) and _persistent connections_: the underlying TCP connection can be partially controlled using the {{HTTPHeader("Connection")}} header. HTTP/2 went a step further by multiplexing messages over a single connection, helping keep the connection warm and more efficient.
 
-<p>Experiments are in progress to design a better transport protocol more suited to HTTP. For example, Google is experimenting with <a href="https://en.wikipedia.org/wiki/QUIC">QUIC</a> which builds on UDP to provide a more reliable and efficient transport protocol.</p>
+Experiments are in progress to design a better transport protocol more suited to HTTP. For example, Google is experimenting with [QUIC](https://en.wikipedia.org/wiki/QUIC) which builds on UDP to provide a more reliable and efficient transport protocol.
 
-<h2 id="What_can_be_controlled_by_HTTP">What can be controlled by HTTP</h2>
+## What can be controlled by HTTP
 
-<p>This extensible nature of HTTP has, over time, allowed for more control and functionality of the Web. Cache or authentication methods were functions handled early in HTTP history. The ability to relax the <em>origin constraint</em>, by contrast, has only been added in the 2010s.</p>
+This extensible nature of HTTP has, over time, allowed for more control and functionality of the Web. Cache or authentication methods were functions handled early in HTTP history. The ability to relax the _origin constraint_, by contrast, has only been added in the 2010s.
 
-<p>Here is a list of common features controllable with HTTP.</p>
+Here is a list of common features controllable with HTTP.
 
-<ul>
- <li><em><a href="/en-US/docs/Web/HTTP/Caching">Caching</a></em><br>
-  How documents are cached can be controlled by HTTP. The server can instruct proxies and clients, about what to cache and for how long. The client can instruct intermediate cache proxies to ignore the stored document.</li>
- <li><em>Relaxing the origin constraint</em><br>
-  To prevent snooping and other privacy invasions, Web browsers enforce strict separation between Web sites. Only pages from the <strong>same origin</strong> can access all the information of a Web page. Though such constraint is a burden to the server, HTTP headers can relax this strict separation on the server side, allowing a document to become a patchwork of information sourced from different domains; there could even be security-related reasons to do so.</li>
- <li><em>Authentication</em><br>
-  Some pages may be protected so that only specific users can access them. Basic authentication may be provided by HTTP, either using the {{HTTPHeader("WWW-Authenticate")}} and similar headers, or by setting a specific session using <a href="/en-US/docs/Web/HTTP/Cookies">HTTP cookies</a>.</li>
- <li><em><a href="/en-US/docs/Web/HTTP/Proxy_servers_and_tunneling">Proxy and tunneling</a></em><br>
-  Servers or clients are often located on intranets and hide their true IP address from other computers. HTTP requests then go through proxies to cross this network barrier. Not all proxies are HTTP proxies. The SOCKS protocol, for example, operates at a lower level. Other protocols, like ftp, can be handled by these proxies.</li>
- <li><em>Sessions</em><br>
-  Using HTTP cookies allows you to link requests with the state of the server. This creates sessions, despite basic HTTP being a state-less protocol. This is useful not only for e-commerce shopping baskets, but also for any site allowing user configuration of the output.</li>
-</ul>
+- _[Caching](/en-US/docs/Web/HTTP/Caching)_
+  How documents are cached can be controlled by HTTP. The server can instruct proxies and clients, about what to cache and for how long. The client can instruct intermediate cache proxies to ignore the stored document.
+- _Relaxing the origin constraint_
+  To prevent snooping and other privacy invasions, Web browsers enforce strict separation between Web sites. Only pages from the **same origin** can access all the information of a Web page. Though such constraint is a burden to the server, HTTP headers can relax this strict separation on the server side, allowing a document to become a patchwork of information sourced from different domains; there could even be security-related reasons to do so.
+- _Authentication_
+  Some pages may be protected so that only specific users can access them. Basic authentication may be provided by HTTP, either using the {{HTTPHeader("WWW-Authenticate")}} and similar headers, or by setting a specific session using [HTTP cookies](/en-US/docs/Web/HTTP/Cookies).
+- _[Proxy and tunneling](/en-US/docs/Web/HTTP/Proxy_servers_and_tunneling)_
+  Servers or clients are often located on intranets and hide their true IP address from other computers. HTTP requests then go through proxies to cross this network barrier. Not all proxies are HTTP proxies. The SOCKS protocol, for example, operates at a lower level. Other protocols, like ftp, can be handled by these proxies.
+- _Sessions_
+  Using HTTP cookies allows you to link requests with the state of the server. This creates sessions, despite basic HTTP being a state-less protocol. This is useful not only for e-commerce shopping baskets, but also for any site allowing user configuration of the output.
 
-<h2 id="HTTP_flow">HTTP flow</h2>
+## HTTP flow
 
-<p>When a client wants to communicate with a server, either the final server or an intermediate proxy, it performs the following steps:</p>
+When a client wants to communicate with a server, either the final server or an intermediate proxy, it performs the following steps:
 
-<ol>
- <li>Open a TCP connection: The TCP connection is used to send a request, or several, and receive an answer. The client may open a new connection, reuse an existing connection, or open several TCP connections to the servers.</li>
- <li>Send an HTTP message: HTTP messages (before HTTP/2) are human-readable. With HTTP/2, these simple messages are encapsulated in frames, making them impossible to read directly, but the principle remains the same. For example:
-  <pre>GET / HTTP/1.1
-Host: developer.mozilla.org
-Accept-Language: fr</pre>
- </li>
- <li>Read the response sent by the server, such as:
-  <pre>HTTP/1.1 200 OK
-Date: Sat, 09 Oct 2010 14:28:02 GMT
-Server: Apache
-Last-Modified: Tue, 01 Dec 2009 20:18:22 GMT
-ETag: "51142bc1-7449-479b075b2891b"
-Accept-Ranges: bytes
-Content-Length: 29769
-Content-Type: text/html
+1.  Open a TCP connection: The TCP connection is used to send a request, or several, and receive an answer. The client may open a new connection, reuse an existing connection, or open several TCP connections to the servers.
+2.  Send an HTTP message: HTTP messages (before HTTP/2) are human-readable. With HTTP/2, these simple messages are encapsulated in frames, making them impossible to read directly, but the principle remains the same. For example:
 
-&lt;!DOCTYPE html... (here comes the 29769 bytes of the requested web page)</pre>
- </li>
- <li>Close or reuse the connection for further requests.</li>
-</ol>
+        GET / HTTP/1.1
+        Host: developer.mozilla.org
+        Accept-Language: fr
 
-<p>If HTTP pipelining is activated, several requests can be sent without waiting for the first response to be fully received. HTTP pipelining has proven difficult to implement in existing networks, where old pieces of software coexist with modern versions. HTTP pipelining has been superseded in HTTP/2 with more robust multiplexing requests within a frame.</p>
+3.  Read the response sent by the server, such as:
 
-<h2 id="HTTP_Messages">HTTP Messages</h2>
+        HTTP/1.1 200 OK
+        Date: Sat, 09 Oct 2010 14:28:02 GMT
+        Server: Apache
+        Last-Modified: Tue, 01 Dec 2009 20:18:22 GMT
+        ETag: "51142bc1-7449-479b075b2891b"
+        Accept-Ranges: bytes
+        Content-Length: 29769
+        Content-Type: text/html
 
-<p>HTTP messages, as defined in HTTP/1.1 and earlier, are human-readable. In HTTP/2, these messages are embedded into a binary structure, a <em>frame</em>, allowing optimizations like compression of headers and multiplexing. Even if only part of the original HTTP message is sent in this version of HTTP, the semantics of each message is unchanged and the client reconstitutes (virtually) the original HTTP/1.1 request. It is therefore useful to comprehend HTTP/2 messages in the HTTP/1.1 format.</p>
+        <!DOCTYPE html... (here comes the 29769 bytes of the requested web page)
 
-<p>There are two types of HTTP messages, requests and responses, each with its own format.</p>
+4.  Close or reuse the connection for further requests.
 
-<h3 id="Requests">Requests</h3>
+If HTTP pipelining is activated, several requests can be sent without waiting for the first response to be fully received. HTTP pipelining has proven difficult to implement in existing networks, where old pieces of software coexist with modern versions. HTTP pipelining has been superseded in HTTP/2 with more robust multiplexing requests within a frame.
 
-<p>An example HTTP request:</p>
+## HTTP Messages
 
-<p><img alt="A basic HTTP request" src="http_request.png"></p>
+HTTP messages, as defined in HTTP/1.1 and earlier, are human-readable. In HTTP/2, these messages are embedded into a binary structure, a _frame_, allowing optimizations like compression of headers and multiplexing. Even if only part of the original HTTP message is sent in this version of HTTP, the semantics of each message is unchanged and the client reconstitutes (virtually) the original HTTP/1.1 request. It is therefore useful to comprehend HTTP/2 messages in the HTTP/1.1 format.
 
-<p>Requests consists of the following elements:</p>
+There are two types of HTTP messages, requests and responses, each with its own format.
 
-<ul>
- <li>An HTTP <a href="/en-US/docs/Web/HTTP/Methods">method</a>, usually a verb like {{HTTPMethod("GET")}}, {{HTTPMethod("POST")}} or a noun like {{HTTPMethod("OPTIONS")}} or {{HTTPMethod("HEAD")}} that defines the operation the client wants to perform. Typically, a client wants to fetch a resource (using <code>GET</code>) or post the value of an <a href="/en-US/docs/Learn/Forms">HTML form</a> (using <code>POST</code>), though more operations may be needed in other cases.</li>
- <li>The path of the resource to fetch; the URL of the resource stripped from elements that are obvious from the context, for example without the {{Glossary("protocol")}} (<code>http://</code>), the {{Glossary("domain")}} (here, <code>developer.mozilla.org</code>), or the TCP {{Glossary("port")}} (here, <code>80</code>).</li>
- <li>The version of the HTTP protocol.</li>
- <li>Optional <a href="/en-US/docs/Web/HTTP/Headers">headers</a> that convey additional information for the servers.</li>
- <li>Or a body, for some methods like <code>POST</code>, similar to those in responses, which contain the resource sent.</li>
-</ul>
+### Requests
 
-<h3 id="Responses">Responses</h3>
+An example HTTP request:
 
-<p>An example response:</p>
+![A basic HTTP request](http_request.png)
 
-<p><img alt="" src="http_response.png"></p>
+Requests consists of the following elements:
 
-<p>Responses consist of the following elements:</p>
+- An HTTP [method](/en-US/docs/Web/HTTP/Methods), usually a verb like {{HTTPMethod("GET")}}, {{HTTPMethod("POST")}} or a noun like {{HTTPMethod("OPTIONS")}} or {{HTTPMethod("HEAD")}} that defines the operation the client wants to perform. Typically, a client wants to fetch a resource (using `GET`) or post the value of an [HTML form](/en-US/docs/Learn/Forms) (using `POST`), though more operations may be needed in other cases.
+- The path of the resource to fetch; the URL of the resource stripped from elements that are obvious from the context, for example without the {{Glossary("protocol")}} (`http://`), the {{Glossary("domain")}} (here, `developer.mozilla.org`), or the TCP {{Glossary("port")}} (here, `80`).
+- The version of the HTTP protocol.
+- Optional [headers](/en-US/docs/Web/HTTP/Headers) that convey additional information for the servers.
+- Or a body, for some methods like `POST`, similar to those in responses, which contain the resource sent.
 
-<ul>
- <li>The version of the HTTP protocol they follow.</li>
- <li>A <a href="/en-US/docs/Web/HTTP/Status">status code</a>, indicating if the request was successful, or not, and why.</li>
- <li>A status message, a non-authoritative short description of the status code.</li>
- <li>HTTP <a href="/en-US/docs/Web/HTTP/Headers">headers</a>, like those for requests.</li>
- <li>Optionally, a body containing the fetched resource.</li>
-</ul>
+### Responses
 
-<h2 id="APIs_based_on_HTTP">APIs based on HTTP</h2>
+An example response:
 
-<p>The most commonly used API based on HTTP is the {{domxref("XMLHttpRequest")}} API, which can be used to exchange data between a {{Glossary("user agent")}} and a server. The modern {{domxref("Fetch API")}} provides the same features with a more powerful and flexible feature set.</p>
+![](http_response.png)
 
-<p>Another API, <a href="/en-US/docs/Web/API/Server-sent_events">server-sent events</a>, is a one-way service that allows a server to send events to the client, using HTTP as a transport mechanism. Using the {{domxref("EventSource")}} interface, the client opens a connection and establishes event handlers. The client browser automatically converts the messages that arrive on the HTTP stream into appropriate {{domxref("Event")}} objects, delivering them to the event handlers that have been registered for the events' {{domxref("Event.type", "type")}} if known, or to the {{domxref("EventSource.onmessage", "onmessage")}} event handler if no type-specific event handler was established.</p>
+Responses consist of the following elements:
 
-<h2 id="Conclusion">Conclusion</h2>
+- The version of the HTTP protocol they follow.
+- A [status code](/en-US/docs/Web/HTTP/Status), indicating if the request was successful, or not, and why.
+- A status message, a non-authoritative short description of the status code.
+- HTTP [headers](/en-US/docs/Web/HTTP/Headers), like those for requests.
+- Optionally, a body containing the fetched resource.
 
-<p>HTTP is an extensible protocol that is easy to use. The client-server structure, combined with the ability to add headers, allows HTTP to advance along with the extended capabilities of the Web.</p>
+## APIs based on HTTP
 
-<p>Though HTTP/2 adds some complexity, by embedding HTTP messages in frames to improve performance, the basic structure of messages has stayed the same since HTTP/1.0. Session flow remains simple, allowing it to be investigated, and debugged with a simple <a href="/en-US/docs/Tools/Network_Monitor">HTTP message monitor</a>.</p>
+The most commonly used API based on HTTP is the {{domxref("XMLHttpRequest")}} API, which can be used to exchange data between a {{Glossary("user agent")}} and a server. The modern {{domxref("Fetch API")}} provides the same features with a more powerful and flexible feature set.
+
+Another API, [server-sent events](/en-US/docs/Web/API/Server-sent_events), is a one-way service that allows a server to send events to the client, using HTTP as a transport mechanism. Using the {{domxref("EventSource")}} interface, the client opens a connection and establishes event handlers. The client browser automatically converts the messages that arrive on the HTTP stream into appropriate {{domxref("Event")}} objects, delivering them to the event handlers that have been registered for the events' {{domxref("Event.type", "type")}} if known, or to the {{domxref("EventSource.onmessage", "onmessage")}} event handler if no type-specific event handler was established.
+
+## Conclusion
+
+HTTP is an extensible protocol that is easy to use. The client-server structure, combined with the ability to add headers, allows HTTP to advance along with the extended capabilities of the Web.
+
+Though HTTP/2 adds some complexity, by embedding HTTP messages in frames to improve performance, the basic structure of messages has stayed the same since HTTP/1.0. Session flow remains simple, allowing it to be investigated, and debugged with a simple [HTTP message monitor](/en-US/docs/Tools/Network_Monitor).
diff --git a/files/en-us/web/http/protocol_upgrade_mechanism/index.md b/files/en-us/web/http/protocol_upgrade_mechanism/index.md
index d27b05dd4933436..66b7b9034de7076 100644
--- a/files/en-us/web/http/protocol_upgrade_mechanism/index.md
+++ b/files/en-us/web/http/protocol_upgrade_mechanism/index.md
@@ -11,146 +11,144 @@ tags:
   - WebSocket
   - WebSockets
 ---
-<div>{{HTTPSidebar}}</div>
+{{HTTPSidebar}}
 
-<p>The <a href="/en-US/docs/Web/HTTP">HTTP/1.1 protocol</a> provides a special mechanism that can be used to upgrade an already established connection to a different protocol, using the {{HTTPHeader("Upgrade")}} header field.</p>
+The [HTTP/1.1 protocol](/en-US/docs/Web/HTTP) provides a special mechanism that can be used to upgrade an already established connection to a different protocol, using the {{HTTPHeader("Upgrade")}} header field.
 
-<p>This mechanism is optional; it cannot be used to insist on a protocol change. Implementations can choose not to take advantage of an upgrade even if they support the new protocol, and in practice, this mechanism is used mostly to bootstrap a WebSockets connection.</p>
+This mechanism is optional; it cannot be used to insist on a protocol change. Implementations can choose not to take advantage of an upgrade even if they support the new protocol, and in practice, this mechanism is used mostly to bootstrap a WebSockets connection.
 
-<p>Note also that HTTP/2 explicitly disallows the use of this mechanism; it is specific to HTTP/1.1.</p>
+Note also that HTTP/2 explicitly disallows the use of this mechanism; it is specific to HTTP/1.1.
 
-<h2 id="Upgrading_HTTP1.1_Connections">Upgrading HTTP/1.1 Connections</h2>
+## Upgrading HTTP/1.1 Connections
 
-<p>The {{HTTPHeader("Upgrade")}} header field is used by clients to invite the server to switch to one of the listed protocols, in descending preference order.</p>
+The {{HTTPHeader("Upgrade")}} header field is used by clients to invite the server to switch to one of the listed protocols, in descending preference order.
 
-<p>Because <code>Upgrade</code> is a hop-by-hop header, it also needs to be listed in the {{HTTPHeader("Connection")}} header field. This means that a typical request that includes Upgrade would look something like:</p>
+Because `Upgrade` is a hop-by-hop header, it also needs to be listed in the {{HTTPHeader("Connection")}} header field. This means that a typical request that includes Upgrade would look something like:
 
-<pre class="brush: html">GET /index.html HTTP/1.1
+```html
+GET /index.html HTTP/1.1
 Host: www.example.com
 Connection: upgrade
-Upgrade: example/1, foo/2</pre>
+Upgrade: example/1, foo/2
+```
 
-<p>Other headers may be required depending on the requested protocol; for example, <a href="/en-US/docs/Web/API/WebSocket">WebSocket</a> upgrades allow additional headers to configure details about the WebSocket connection as well as to offer a degree of security in opening the connection. See {{anch("Upgrading to a WebSocket connection")}} for more details.</p>
+Other headers may be required depending on the requested protocol; for example, [WebSocket](/en-US/docs/Web/API/WebSocket) upgrades allow additional headers to configure details about the WebSocket connection as well as to offer a degree of security in opening the connection. See {{anch("Upgrading to a WebSocket connection")}} for more details.
 
-<p>If the server decides to upgrade the connection, it sends back a {{HTTPStatus(101, "101 Switching Protocols")}} response status with an Upgrade header that specifies the protocol(s) being switched to. If it does not (or cannot) upgrade the connection, it ignores the <code>Upgrade</code> header and sends back a regular response (for example, a {{HTTPStatus(200, "200 OK")}}).</p>
+If the server decides to upgrade the connection, it sends back a {{HTTPStatus(101, "101 Switching Protocols")}} response status with an Upgrade header that specifies the protocol(s) being switched to. If it does not (or cannot) upgrade the connection, it ignores the `Upgrade` header and sends back a regular response (for example, a {{HTTPStatus(200, "200 OK")}}).
 
-<p>Right after sending the <code>101</code> status code, the server can begin speaking the new protocol, performing any additional protocol-specific handshakes as necessary. Effectively, the connection becomes a two-way pipe as soon as the upgraded response is complete, and the request that initiated the upgrade can be completed over the new protocol.</p>
+Right after sending the `101` status code, the server can begin speaking the new protocol, performing any additional protocol-specific handshakes as necessary. Effectively, the connection becomes a two-way pipe as soon as the upgraded response is complete, and the request that initiated the upgrade can be completed over the new protocol.
 
-<h2 id="Common_uses_for_this_mechanism">Common uses for this mechanism</h2>
+## Common uses for this mechanism
 
-<p>Here we look at the most common use cases for the {{HTTPHeader("Upgrade")}} header.</p>
+Here we look at the most common use cases for the {{HTTPHeader("Upgrade")}} header.
 
-<h3 id="Upgrading_to_a_WebSocket_connection">Upgrading to a WebSocket connection</h3>
+### Upgrading to a WebSocket connection
 
-<p>By far, the most common use case for upgrading an HTTP connection is to use WebSockets, which are always implemented by upgrading an HTTP or HTTPS connection. Keep in mind that if you're opening a new connection using the <a href="/en-US/docs/Web/API/WebSocket">WebSocket API</a>, or any library that does WebSockets, most or all of this is done for you. For example, opening a WebSocket connection is as simple as:</p>
+By far, the most common use case for upgrading an HTTP connection is to use WebSockets, which are always implemented by upgrading an HTTP or HTTPS connection. Keep in mind that if you're opening a new connection using the [WebSocket API](/en-US/docs/Web/API/WebSocket), or any library that does WebSockets, most or all of this is done for you. For example, opening a WebSocket connection is as simple as:
 
-<pre class="brush: js">webSocket = new WebSocket("ws://destination.server.ext", "optionalProtocol");</pre>
+```js
+webSocket = new WebSocket("ws://destination.server.ext", "optionalProtocol");
+```
 
-<p>The {{domxref("WebSocket.WebSocket", "WebSocket()")}} constructor does all the work of creating an initial HTTP/1.1 connection then handling the handshaking and upgrade process for you.</p>
+The {{domxref("WebSocket.WebSocket", "WebSocket()")}} constructor does all the work of creating an initial HTTP/1.1 connection then handling the handshaking and upgrade process for you.
 
-<div class="notecard note">
-  <p><strong>Note:</strong> You can also use the <code>"wss://"</code> URL scheme to open a secure WebSocket connection.</p>
-</div>
+> **Note:** You can also use the `"wss://"` URL scheme to open a secure WebSocket connection.
 
-<p>If you need to create a WebSocket connection from scratch, you'll have to handle the handshaking process yourself. After creating the initial HTTP/1.1 session, you need to request the upgrade by adding to a standard request the {{HTTPHeader("Upgrade")}} and {{HTTPHeader("Connection")}} headers, as follows:</p>
+If you need to create a WebSocket connection from scratch, you'll have to handle the handshaking process yourself. After creating the initial HTTP/1.1 session, you need to request the upgrade by adding to a standard request the {{HTTPHeader("Upgrade")}} and {{HTTPHeader("Connection")}} headers, as follows:
 
-<pre>Connection: Upgrade
-Upgrade: websocket</pre>
+    Connection: Upgrade
+    Upgrade: websocket
 
-<h3 id="WebSocket-specific_headers">WebSocket-specific headers</h3>
+### WebSocket-specific headers
 
-<p>The following headers are involved in the WebSocket upgrade process. Other than the {{HTTPHeader("Upgrade")}} and {{HTTPHeader("Connection")}} headers, the rest are generally optional or handled for you by the browser and server when they're talking to each other.</p>
+The following headers are involved in the WebSocket upgrade process. Other than the {{HTTPHeader("Upgrade")}} and {{HTTPHeader("Connection")}} headers, the rest are generally optional or handled for you by the browser and server when they're talking to each other.
 
-<h4 id="HTTPHeaderSec-WebSocket-Extensions">{{HTTPHeader("Sec-WebSocket-Extensions")}}</h4>
+#### {{HTTPHeader("Sec-WebSocket-Extensions")}}
 
-<p>Specifies one or more protocol-level WebSocket extensions to ask the server to use. Using more than one <code>Sec-WebSocket-Extension</code> header in a request is permitted; the result is the same as if you included all of the listed extensions in one such header.</p>
+Specifies one or more protocol-level WebSocket extensions to ask the server to use. Using more than one `Sec-WebSocket-Extension` header in a request is permitted; the result is the same as if you included all of the listed extensions in one such header.
 
-<pre class="brush: html">Sec-WebSocket-Extensions: <var>extensions</var></pre>
+```html
+Sec-WebSocket-Extensions: extensions
+```
 
-<dl>
- <dt><code><var>extensions</var></code></dt>
- <dd>A comma-separated list of extensions to request (or agree to support). These should be selected from the <a href="https://www.iana.org/assignments/websocket/websocket.xml#extension-name">IANA WebSocket Extension Name Registry</a>. Extensions which take parameters do so by using semicolon delineation.</dd>
-</dl>
+- `extensions`
+  - : A comma-separated list of extensions to request (or agree to support). These should be selected from the [IANA WebSocket Extension Name Registry](https://www.iana.org/assignments/websocket/websocket.xml#extension-name). Extensions which take parameters do so by using semicolon delineation.
 
-<p>For example:</p>
+For example:
 
-<pre>Sec-WebSocket-Extensions: superspeed, colormode; depth=16</pre>
+    Sec-WebSocket-Extensions: superspeed, colormode; depth=16
 
-<h4 id="HTTPHeaderSec-WebSocket-Key">{{HTTPHeader("Sec-WebSocket-Key")}}</h4>
+#### {{HTTPHeader("Sec-WebSocket-Key")}}
 
-<p>Provides information to the server which is needed in order to confirm that the client is entitled to request an upgrade to WebSocket. This header can be used when insecure (HTTP) clients wish to upgrade, in order to offer some degree of protection against abuse. The value of the key is computed using an algorithm defined in the WebSocket specification, so this <em>does not provide security</em>. Instead, it helps to prevent non-WebSocket clients from inadvertently, or through misuse, requesting a WebSocket connection. In essence, then, this key confirms that "Yes, I really mean to open a WebSocket connection."</p>
+Provides information to the server which is needed in order to confirm that the client is entitled to request an upgrade to WebSocket. This header can be used when insecure (HTTP) clients wish to upgrade, in order to offer some degree of protection against abuse. The value of the key is computed using an algorithm defined in the WebSocket specification, so this _does not provide security_. Instead, it helps to prevent non-WebSocket clients from inadvertently, or through misuse, requesting a WebSocket connection. In essence, then, this key confirms that "Yes, I really mean to open a WebSocket connection."
 
-<p>This header is automatically added by clients that choose to use it; it cannot be added using the {{domxref("XMLHttpRequest.setRequestHeader()")}} method.</p>
+This header is automatically added by clients that choose to use it; it cannot be added using the {{domxref("XMLHttpRequest.setRequestHeader()")}} method.
 
-<pre class="brush: html">Sec-WebSocket-Key: <var>key</var></pre>
+```html
+Sec-WebSocket-Key: key
+```
 
-<dl>
- <dt><code><var>key</var></code></dt>
- <dd>The key for this request to upgrade. The client adds this if it wishes to do so, and the server will include in the response a key of its own, which the client will validate before delivering the upgrade response to you.</dd>
-</dl>
+- `key`
+  - : The key for this request to upgrade. The client adds this if it wishes to do so, and the server will include in the response a key of its own, which the client will validate before delivering the upgrade response to you.
 
-<p>The server's response's {{HTTPHeader("Sec-WebSocket-Accept")}} header will have a value computed based upon the specified <code><var>key</var></code>.</p>
+The server's response's {{HTTPHeader("Sec-WebSocket-Accept")}} header will have a value computed based upon the specified `key`.
 
-<h4 id="HTTPHeaderSec-WebSocket-Protocol">{{HTTPHeader("Sec-WebSocket-Protocol")}}</h4>
+#### {{HTTPHeader("Sec-WebSocket-Protocol")}}
 
-<p>The <code>Sec-WebSocket-Protocol</code> header specifies one or more WebSocket protocols that you wish to use, in order of preference. The first one that is supported by the server will be selected and returned by the server in a <code>Sec-WebSocket-Protocol</code> header included in the response. You can use this more than once in the header, as well; the result is the same as if you used a comma-delineated list of subprotocol identifiers in a single header.</p>
+The `Sec-WebSocket-Protocol` header specifies one or more WebSocket protocols that you wish to use, in order of preference. The first one that is supported by the server will be selected and returned by the server in a `Sec-WebSocket-Protocol` header included in the response. You can use this more than once in the header, as well; the result is the same as if you used a comma-delineated list of subprotocol identifiers in a single header.
 
-<pre class="brush: html">Sec-WebSocket-Protocol: <var>subprotocols</var></pre>
+```html
+Sec-WebSocket-Protocol: subprotocols
+```
 
-<dl>
- <dt><code><var>subprotocols</var></code></dt>
- <dd>A comma-separated list of subprotocol names, in the order of preference. The subprotocols may be selected from the <a href="https://www.iana.org/assignments/websocket/websocket.xml#subprotocol-name">IANA WebSocket Subprotocol Name Registry</a> or may be a custom name jointly understood by the client and the server.</dd>
-</dl>
+- `subprotocols`
+  - : A comma-separated list of subprotocol names, in the order of preference. The subprotocols may be selected from the [IANA WebSocket Subprotocol Name Registry](https://www.iana.org/assignments/websocket/websocket.xml#subprotocol-name) or may be a custom name jointly understood by the client and the server.
 
-<h4 id="HTTPHeaderSec-WebSocket-Version">{{HTTPHeader("Sec-WebSocket-Version")}}</h4>
+#### {{HTTPHeader("Sec-WebSocket-Version")}}
 
-<h5 id="Request_header">Request header</h5>
+##### Request header
 
-<p>Specifies the WebSocket protocol version the client wishes to use, so the server can confirm whether or not that version is supported on its end.</p>
+Specifies the WebSocket protocol version the client wishes to use, so the server can confirm whether or not that version is supported on its end.
 
-<pre class="brush: html">Sec-WebSocket-Version: <var>version</var></pre>
+```html
+Sec-WebSocket-Version: version
+```
 
-<dl>
- <dt><code><var>version</var></code></dt>
- <dd>The WebSocket protocol version the client wishes to use when communicating with the server. This number should be the most recent version possible listed in the <a href="https://www.iana.org/assignments/websocket/websocket.xml#version-number">IANA WebSocket Version Number Registry</a>. The most recent final version of the WebSocket protocol is version 13.</dd>
-</dl>
+- `version`
+  - : The WebSocket protocol version the client wishes to use when communicating with the server. This number should be the most recent version possible listed in the [IANA WebSocket Version Number Registry](https://www.iana.org/assignments/websocket/websocket.xml#version-number). The most recent final version of the WebSocket protocol is version 13.
 
-<h5 id="Response_header">Response header</h5>
+##### Response header
 
-<p>If the server can't communicate using the specified version of the WebSocket protocol, it will respond with an error (such as 426 Upgrade Required) that includes in its headers a <code>Sec-WebSocket-Version</code> header with a comma-separated list of the supported protocol versions. If the server does support the requested protocol version, no <code>Sec-WebSocket-Version</code> header is included in the response.</p>
+If the server can't communicate using the specified version of the WebSocket protocol, it will respond with an error (such as 426 Upgrade Required) that includes in its headers a `Sec-WebSocket-Version` header with a comma-separated list of the supported protocol versions. If the server does support the requested protocol version, no `Sec-WebSocket-Version` header is included in the response.
 
-<pre class="brush: html">Sec-WebSocket-Version: <var>supportedVersions</var></pre>
+```html
+Sec-WebSocket-Version: supportedVersions
+```
 
-<dl>
- <dt><code><var>supportedVersions</var></code></dt>
- <dd>A comma-delineated list of the WebSocket protocol versions supported by the server.</dd>
-</dl>
+- `supportedVersions`
+  - : A comma-delineated list of the WebSocket protocol versions supported by the server.
 
-<h3 id="Response-only_headers">Response-only headers</h3>
+### Response-only headers
 
-<p>The response from the server may include these.</p>
+The response from the server may include these.
 
-<h4 id="HTTPHeaderSec-WebSocket-Accept">{{HTTPHeader("Sec-WebSocket-Accept")}}</h4>
+#### {{HTTPHeader("Sec-WebSocket-Accept")}}
 
-<p>Included in the response message from the server during the opening handshake process when the server is willing to initiate a WebSocket connection. It will appear no more than once in the response headers.</p>
+Included in the response message from the server during the opening handshake process when the server is willing to initiate a WebSocket connection. It will appear no more than once in the response headers.
 
-<pre class="brush: html">Sec-WebSocket-Accept: <var>hash</var></pre>
+```html
+Sec-WebSocket-Accept: hash
+```
 
-<dl>
- <dt><code><var>hash</var></code></dt>
- <dd>If a {{HTTPHeader("Sec-WebSocket-Key")}} header was provided, the value of this header is computed by taking the value of the key, concatenating the string "258EAFA5-E914-47DA-95CA-C5AB0DC85B11" to it, taking the {{interwiki("wikipedia", "SHA-1")}} hash of that concatenated string, resulting in a 20-byte value. That value is then <a href="/en-US/docs/Glossary/Base64">base64</a> encoded to obtain the value of this property.</dd>
-</dl>
+- `hash`
+  - : If a {{HTTPHeader("Sec-WebSocket-Key")}} header was provided, the value of this header is computed by taking the value of the key, concatenating the string "258EAFA5-E914-47DA-95CA-C5AB0DC85B11" to it, taking the {{interwiki("wikipedia", "SHA-1")}} hash of that concatenated string, resulting in a 20-byte value. That value is then [base64](/en-US/docs/Glossary/Base64) encoded to obtain the value of this property.
 
-<h2 id="References">References</h2>
+## References
 
-<ul>
- <li><a href="/en-US/docs/Web/API/WebSocket">WebSocket API</a></li>
- <li><a href="/en-US/docs/Web/HTTP">HTTP</a></li>
- <li>Specifications and RFCs:
-  <ul>
-   <li>{{RFC(7230)}}</li>
-   <li>{{RFC(6455)}}</li>
-   <li>{{RFC(7540)}}</li>
-  </ul>
- </li>
-</ul>
+- [WebSocket API](/en-US/docs/Web/API/WebSocket)
+- [HTTP](/en-US/docs/Web/HTTP)
+- Specifications and RFCs:
+
+  - {{RFC(7230)}}
+  - {{RFC(6455)}}
+  - {{RFC(7540)}}
diff --git a/files/en-us/web/http/proxy_servers_and_tunneling/index.md b/files/en-us/web/http/proxy_servers_and_tunneling/index.md
index f3d065783189435..d46430f190f5b5c 100644
--- a/files/en-us/web/http/proxy_servers_and_tunneling/index.md
+++ b/files/en-us/web/http/proxy_servers_and_tunneling/index.md
@@ -7,91 +7,87 @@ tags:
   - Proxies
   - Proxy
 ---
-<div>{{HTTPSidebar}}</div>
+{{HTTPSidebar}}
 
-<p class="summary">When navigating through different networks of the Internet, proxy servers and HTTP tunnels are facilitating access to content on the World Wide Web. A proxy can be on the user's local computer, or anywhere between the user's computer and a destination server on the Internet. This page outlines some basics about proxies and introduces a few configuration options.</p>
+When navigating through different networks of the Internet, proxy servers and HTTP tunnels are facilitating access to content on the World Wide Web. A proxy can be on the user's local computer, or anywhere between the user's computer and a destination server on the Internet. This page outlines some basics about proxies and introduces a few configuration options.
 
-<p>There are two types of proxies: <strong>forward proxies</strong> (or tunnel, or gateway) and <strong>reverse proxies</strong> (used to control and protect access to a server for load-balancing, authentication, decryption or caching).</p>
+There are two types of proxies: **forward proxies** (or tunnel, or gateway) and **reverse proxies** (used to control and protect access to a server for load-balancing, authentication, decryption or caching).
 
-<h2 id="Forward_proxies">Forward proxies</h2>
+## Forward proxies
 
-<p>A forward proxy, or gateway, or just "proxy" provides proxy services to a client or a group of clients. There are likely hundreds of thousands of open forward proxies on the Internet. They store and forward Internet services (like the DNS, or web pages) to reduce and control the bandwidth used by the group.</p>
+A forward proxy, or gateway, or just "proxy" provides proxy services to a client or a group of clients. There are likely hundreds of thousands of open forward proxies on the Internet. They store and forward Internet services (like the DNS, or web pages) to reduce and control the bandwidth used by the group.
 
-<p>Forward proxies can also be anonymous proxies and allow users to hide their IP address while browsing the Web or using other Internet services. <a href="https://www.torproject.org/">TOR</a> (The Onion Router), routes internet traffic through multiple proxies for anonymity.</p>
+Forward proxies can also be anonymous proxies and allow users to hide their IP address while browsing the Web or using other Internet services. [TOR](https://www.torproject.org/) (The Onion Router), routes internet traffic through multiple proxies for anonymity.
 
-<h2 id="Reverse_proxies">Reverse proxies</h2>
+## Reverse proxies
 
-<p>As the name implies, a reverse proxy does the opposite of what a forward proxy does: A forward proxy acts on behalf of clients (or requesting hosts). Forward proxies can hide the identities of clients whereas reverse proxies can hide the identities of servers. Reverse proxies have several use cases, a few are:</p>
+As the name implies, a reverse proxy does the opposite of what a forward proxy does: A forward proxy acts on behalf of clients (or requesting hosts). Forward proxies can hide the identities of clients whereas reverse proxies can hide the identities of servers. Reverse proxies have several use cases, a few are:
 
-<ul>
- <li>Load balancing: distribute the load to several web servers,</li>
- <li>Cache static content: offload the web servers by caching static content like pictures,</li>
- <li>Compression: compress and optimize content to speed up load time.</li>
-</ul>
+- Load balancing: distribute the load to several web servers,
+- Cache static content: offload the web servers by caching static content like pictures,
+- Compression: compress and optimize content to speed up load time.
 
-<h2 id="Forwarding_client_information_through_proxies">Forwarding client information through proxies</h2>
+## Forwarding client information through proxies
 
-<p>Proxies can make requests appear as if they originated from the proxy's IP address. This can be useful if a proxy is used to provide client anonymity, but in other cases information from the original request is lost. The IP address of the original client is often used for debugging, statistics, or generating location-dependent content. A common way to disclose this information is by using the following HTTP headers:</p>
+Proxies can make requests appear as if they originated from the proxy's IP address. This can be useful if a proxy is used to provide client anonymity, but in other cases information from the original request is lost. The IP address of the original client is often used for debugging, statistics, or generating location-dependent content. A common way to disclose this information is by using the following HTTP headers:
 
-<p>The standardized header:</p>
+The standardized header:
 
-<dl>
- <dt>{{HTTPHeader("Forwarded")}}</dt>
- <dd>Contains information from the client-facing side of proxy servers that is altered or lost when a proxy is involved in the path of the request.</dd>
-</dl>
+- {{HTTPHeader("Forwarded")}}
+  - : Contains information from the client-facing side of proxy servers that is altered or lost when a proxy is involved in the path of the request.
 
-<p>Or the de-facto standard versions:</p>
+Or the de-facto standard versions:
 
-<dl>
- <dt>{{HTTPHeader("X-Forwarded-For")}} {{non-standard_inline}}</dt>
- <dd>Identifies the originating IP addresses of a client connecting to a web server through an HTTP proxy or a load balancer.</dd>
- <dt>{{HTTPHeader("X-Forwarded-Host")}} {{non-standard_inline}}</dt>
- <dd>Identifies the original host requested that a client used to connect to your proxy or load balancer.</dd>
- <dt>{{HTTPHeader("X-Forwarded-Proto")}} {{non-standard_inline}}</dt>
- <dd>identifies the protocol (HTTP or HTTPS) that a client used to connect to your proxy or load balancer.</dd>
-</dl>
+- {{HTTPHeader("X-Forwarded-For")}} {{non-standard_inline}}
+  - : Identifies the originating IP addresses of a client connecting to a web server through an HTTP proxy or a load balancer.
+- {{HTTPHeader("X-Forwarded-Host")}} {{non-standard_inline}}
+  - : Identifies the original host requested that a client used to connect to your proxy or load balancer.
+- {{HTTPHeader("X-Forwarded-Proto")}} {{non-standard_inline}}
+  - : identifies the protocol (HTTP or HTTPS) that a client used to connect to your proxy or load balancer.
 
-<p>To provide information about the proxy itself (not about the client connecting to it), the <code>Via</code> header can be used.</p>
+To provide information about the proxy itself (not about the client connecting to it), the `Via` header can be used.
 
-<dl>
- <dt>{{HTTPHeader("Via")}}</dt>
- <dd>Added by proxies, both forward and reverse proxies, and can appear in the request headers and the response headers.</dd>
-</dl>
+- {{HTTPHeader("Via")}}
+  - : Added by proxies, both forward and reverse proxies, and can appear in the request headers and the response headers.
 
-<h2 id="HTTP_tunneling">HTTP tunneling</h2>
+## HTTP tunneling
 
-<p>Tunneling transmits private network data and protocol information through public network by encapsulating the data. HTTP tunneling is using a protocol of higher level (HTTP) to transport a lower level protocol (TCP).</p>
+Tunneling transmits private network data and protocol information through public network by encapsulating the data. HTTP tunneling is using a protocol of higher level (HTTP) to transport a lower level protocol (TCP).
 
-<p>The HTTP protocol specifies a request method called {{HTTPMethod("CONNECT")}}. It starts two-way communications with the requested resource and can be used to open a tunnel. This is how a client behind an HTTP proxy can access websites using SSL (i.e. HTTPS, port 443). Note, however, that not all proxy servers support the <code>CONNECT</code> method or limit it to port 443 only.</p>
+The HTTP protocol specifies a request method called {{HTTPMethod("CONNECT")}}. It starts two-way communications with the requested resource and can be used to open a tunnel. This is how a client behind an HTTP proxy can access websites using SSL (i.e. HTTPS, port 443). Note, however, that not all proxy servers support the `CONNECT` method or limit it to port 443 only.
 
-<p>See also the <a href="https://en.wikipedia.org/wiki/HTTP_tunnel">HTTP tunnel article on Wikipedia</a>.</p>
+See also the [HTTP tunnel article on Wikipedia](https://en.wikipedia.org/wiki/HTTP_tunnel).
 
-<h2 id="Proxy_Auto-Configuration_PAC">Proxy Auto-Configuration (PAC)</h2>
+## Proxy Auto-Configuration (PAC)
 
-<p>A <a href="/en-US/docs/Web/HTTP/Proxy_servers_and_tunneling/Proxy_Auto-Configuration_PAC_file">Proxy Auto-Configuration (PAC)</a> file is a <a href="/en-US/docs/Web/JavaScript">JavaScript</a> function that determines whether web browser requests (HTTP, HTTPS, and FTP) go directly to the destination or are forwarded to a web proxy server. The JavaScript function contained in the PAC file defines the function:</p>
+A [Proxy Auto-Configuration (PAC)](/en-US/docs/Web/HTTP/Proxy_servers_and_tunneling/Proxy_Auto-Configuration_PAC_file) file is a [JavaScript](/en-US/docs/Web/JavaScript) function that determines whether web browser requests (HTTP, HTTPS, and FTP) go directly to the destination or are forwarded to a web proxy server. The JavaScript function contained in the PAC file defines the function:
 
-<p>The auto-config file should be saved to a file with a <code>.pac</code> filename extension:</p>
+The auto-config file should be saved to a file with a `.pac` filename extension:
 
-<pre class="brush: html">proxy.pac</pre>
+```html
+proxy.pac
+```
 
-<p>And the MIME type set to:</p>
+And the MIME type set to:
 
-<pre class="brush: html">application/x-ns-proxy-autoconfig</pre>
+```html
+application/x-ns-proxy-autoconfig
+```
 
-<p>The file consists of a function called <code>FindProxyForURL</code>. The example below will work in an environment where the internal DNS server is set up so that it can only resolve internal host names, and the goal is to use a proxy only for hosts that aren't resolvable:</p>
+The file consists of a function called `FindProxyForURL`. The example below will work in an environment where the internal DNS server is set up so that it can only resolve internal host names, and the goal is to use a proxy only for hosts that aren't resolvable:
 
-<pre class="brush: js">function FindProxyForURL(url, host) {
+```js
+function FindProxyForURL(url, host) {
   if (isResolvable(host))
     return "DIRECT";
   else
     return "PROXY proxy.mydomain.com:8080";
-}</pre>
+}
+```
 
-<p>See <a href="/en-US/docs/Web/HTTP/Proxy_servers_and_tunneling/Proxy_Auto-Configuration_PAC_file">Proxy Auto-Configuration (PAC)</a> for more examples.</p>
+See [Proxy Auto-Configuration (PAC)](/en-US/docs/Web/HTTP/Proxy_servers_and_tunneling/Proxy_Auto-Configuration_PAC_file) for more examples.
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
- <li>{{HTTPMethod("CONNECT")}}</li>
- <li><a href="https://en.wikipedia.org/wiki/Proxy_server">Proxy server on Wikipedia</a></li>
-</ul>
+- {{HTTPMethod("CONNECT")}}
+- [Proxy server on Wikipedia](https://en.wikipedia.org/wiki/Proxy_server)
diff --git a/files/en-us/web/http/proxy_servers_and_tunneling/proxy_auto-configuration_pac_file/index.md b/files/en-us/web/http/proxy_servers_and_tunneling/proxy_auto-configuration_pac_file/index.md
index 0f75409bc61c965..a041c51eb72e6ef 100644
--- a/files/en-us/web/http/proxy_servers_and_tunneling/proxy_auto-configuration_pac_file/index.md
+++ b/files/en-us/web/http/proxy_servers_and_tunneling/proxy_auto-configuration_pac_file/index.md
@@ -7,471 +7,461 @@ tags:
   - PAC
   - Proxy
 ---
-<div>{{HTTPSidebar}}</div>
+{{HTTPSidebar}}
 
-<p>A <strong>Proxy Auto-Configuration (PAC)</strong> file is a JavaScript function that determines whether web browser requests (HTTP, HTTPS, and FTP) go directly to the destination or are forwarded to a web proxy server. The JavaScript function contained in the PAC file defines the function:</p>
+A **Proxy Auto-Configuration (PAC)** file is a JavaScript function that determines whether web browser requests (HTTP, HTTPS, and FTP) go directly to the destination or are forwarded to a web proxy server. The JavaScript function contained in the PAC file defines the function:
 
-<pre class="brush: js">function FindProxyForURL(url, host) {
+```js
+function FindProxyForURL(url, host) {
   // ...
-}</pre>
+}
+```
+
+## Syntax
+
+```js
+function FindProxyForURL(url, host)
+```
+
+### Parameters
+
+- `url`
+  - : The URL being accessed. The path and query components of `https://` URLs are stripped. In Chrome (versions 52 to 73), you can disable this by setting `PacHttpsUrlStrippingEnabled` to `false` in policy or by launching with the `--unsafe-pac-url` command-line flag (in Chrome 74, only the flag works, and from 75 onward, there is no way to disable path-stripping; as of Chrome 81, path-stripping does not apply to HTTP URLs, but there is interest in changing this behavior to match HTTPS); in Firefox, the preference is `network.proxy.autoconfig_url.include_path`.
+- `host`
+  - : The hostname extracted from the URL. This is only for convenience; it is the same string as between `://` and the first `:` or `/` after that. The port number is not included in this parameter. It can be extracted from the URL when necessary.
+
+## Description
+
+Returns a string describing the configuration. The format of this string is defined in **return value format** below.
+
+### Return value format
+
+- The JavaScript function returns a single string
+- If the string is null, no proxies should be used
+- The string can contain any number of the following building blocks, separated by a semicolon:
+
+<!---->
+
+- `DIRECT`
+  - : Connections should be made directly, without any proxies
+- `PROXY host:port`
+  - : The specified proxy should be used
+- `SOCKS host:port`
+  - : The specified SOCKS server should be used
+
+Recent versions of Firefox support as well:
+
+- `HTTP host:port`
+  - : The specified proxy should be used
+- `HTTPS host:port`
+  - : The specified HTTPS proxy should be used
+- `SOCKS4 host:port`, `SOCKS5 host:port`
+  - : The specified SOCKS server (with the specified SOCK version) should be used
+
+If there are multiple semicolon-separated settings, the left-most setting will be used, until Firefox fails to establish the connection to the proxy. In that case, the next value will be used, etc.
+
+The browser will automatically retry a previously unresponsive proxy after 30 minutes. Additional attempts will continue beginning at one hour, always adding 30 minutes to the elapsed time between attempts.
+
+If all proxies are down, and there was no DIRECT option specified, the browser will ask if proxies should be temporarily ignored, and direct connections attempted. After 20 minutes, the browser will ask if proxies should be retried, asking again after an additional 40 minutes. Queries will continue, always adding 20 minutes to the elapsed time between queries.
+
+#### Examples
+
+- `PROXY w3proxy.netscape.com:8080; PROXY mozilla.netscape.com:8081`
+  - : Primary proxy is w3proxy:8080; if that goes down start using mozilla:8081 until the primary proxy comes up again.
+- `PROXY w3proxy.netscape.com:8080; PROXY mozilla.netscape.com:8081; DIRECT`
+  - : Same as above, but if both proxies go down, automatically start making direct connections. (In the first example above, Netscape will ask user confirmation about making direct connections; in this case, there is no user intervention.)
+- `PROXY w3proxy.netscape.com:8080; SOCKS socks:1080`
+  - : Use SOCKS if the primary proxy goes down.
+
+The auto-config file should be saved to a file with a .pac filename extension:
+
+```html
+proxy.pac
+```
+
+And the MIME type should be set to:
+
+```html
+application/x-ns-proxy-autoconfig
+```
+
+Next, you should configure your server to map the .pac filename extension to the MIME type.
+
+> **Note:**
+>
+> - The JavaScript function should always be saved to a file by itself but not be embedded in a HTML file or any other file.
+> - The examples at the end of this document are complete. There is no additional syntax needed to save it into a file and use it. (Of course, the JavaScripts must be edited to reflect your site's domain name and/or subnets.)
+
+## Predefined functions and environment
+
+These functions can be used in building the PAC file:
+
+- Hostname based conditions
+
+  - [`isPlainHostName()`](#isplainhostname)
+  - [`dnsDomainIs()`](#dnsdomainis)
+  - [`localHostOrDomainIs()`](#localhostordomainis)
+  - [`isResolvable()`](#isresolvable)
+  - [`isInNet()`](#isinnet)
+
+- Related utility functions
+
+  - [`dnsResolve()`](#dnsresolve)
+  - [`convert_addr()`](#convert_addr)
+  - [`myIpAddress()`](#myipaddress)
+  - [`dnsDomainLevels()`](#dnsdomainlevels)
+
+- URL/hostname based conditions
+
+  - [`shExpMatch()`](#shexpmatch)
+
+- Time based conditions
+
+  - [`weekdayRange()`](#weekdayrange)
+  - [`dateRange()`](#daterange)
+  - [`timeRange()`](#timerange)
+
+- Logging utility
 
-<h2 id="Syntax">Syntax</h2>
-
-<pre class="brush: js">function FindProxyForURL(<var>url</var>, <var>host</var>)</pre>
-
-<h3 id="Parameters">Parameters</h3>
-
-<dl>
- <dt><code><var>url</var></code></dt>
- <dd>The URL being accessed. The path and query components of <code>https://</code> URLs are stripped. In Chrome (versions 52 to 73), you can disable this by setting <code>PacHttpsUrlStrippingEnabled</code> to <code>false</code> in policy or by launching with the <code>--unsafe-pac-url</code> command-line flag (in Chrome 74, only the flag works, and from 75 onward, there is no way to disable path-stripping; as of Chrome 81, path-stripping does not apply to HTTP URLs, but there is interest in changing this behavior to match HTTPS); in Firefox, the preference is <code>network.proxy.autoconfig_url.include_path</code>.</dd>
- <dt><code><var>host</var></code></dt>
- <dd>The hostname extracted from the URL. This is only for convenience; it is the same string as between <code>://</code> and the first <code>:</code> or <code>/</code> after that. The port number is not included in this parameter. It can be extracted from the URL when necessary.</dd>
-</dl>
-
-<h2 id="Description">Description</h2>
-
-<p>Returns a string describing the configuration. The format of this string is defined in <strong>return value format</strong> below.</p>
-
-<h3 id="Return_value_format">Return value format</h3>
-
-<ul>
- <li>The JavaScript function returns a single string</li>
- <li>If the string is null, no proxies should be used</li>
- <li>The string can contain any number of the following building blocks, separated by a semicolon:</li>
-</ul>
-
-<dl>
- <dt><code>DIRECT</code></dt>
- <dd>Connections should be made directly, without any proxies</dd>
- <dt><code>PROXY <em>host:port</em></code></dt>
- <dd>The specified proxy should be used</dd>
- <dt><code>SOCKS <em>host:port</em></code></dt>
- <dd>The specified SOCKS server should be used</dd>
-</dl>
-
-<p>Recent versions of Firefox support as well:</p>
-
-<dl>
- <dt><code>HTTP <em>host:port</em></code></dt>
- <dd>The specified proxy should be used</dd>
- <dt><code>HTTPS <em>host:port</em></code></dt>
- <dd>The specified HTTPS proxy should be used</dd>
- <dt><code>SOCKS4 <em>host:port</em></code>, <code>SOCKS5 <em>host:port</em></code></dt>
- <dd>The specified SOCKS server (with the specified SOCK version) should be used</dd>
-</dl>
-
-<p>If there are multiple semicolon-separated settings, the left-most setting will be used, until Firefox fails to establish the connection to the proxy. In that case, the next value will be used, etc.</p>
-
-<p>The browser will automatically retry a previously unresponsive proxy after 30 minutes. Additional attempts will continue beginning at one hour, always adding 30 minutes to the elapsed time between attempts.</p>
-
-<p>If all proxies are down, and there was no DIRECT option specified, the browser will ask if proxies should be temporarily ignored, and direct connections attempted. After 20 minutes, the browser will ask if proxies should be retried, asking again after an additional 40 minutes. Queries will continue, always adding 20 minutes to the elapsed time between queries.</p>
-
-<h4 id="Examples">Examples</h4>
-
-<dl>
- <dt><code>PROXY w3proxy.netscape.com:8080; PROXY mozilla.netscape.com:8081</code></dt>
- <dd>Primary proxy is w3proxy:8080; if that goes down start using mozilla:8081 until the primary proxy comes up again.</dd>
- <dt><code>PROXY w3proxy.netscape.com:8080; PROXY mozilla.netscape.com:8081; DIRECT</code></dt>
- <dd>Same as above, but if both proxies go down, automatically start making direct connections. (In the first example above, Netscape will ask user confirmation about making direct connections; in this case, there is no user intervention.)</dd>
- <dt><code>PROXY w3proxy.netscape.com:8080; SOCKS socks:1080</code></dt>
- <dd>Use SOCKS if the primary proxy goes down.</dd>
-</dl>
-
-<p>The auto-config file should be saved to a file with a .pac filename extension:</p>
-
-<pre class="brush: html">proxy.pac</pre>
-
-<p>And the MIME type should be set to:</p>
-
-<pre class="brush: html">application/x-ns-proxy-autoconfig</pre>
-
-<p>Next, you should configure your server to map the .pac filename extension to the MIME type.</p>
-
-<div class="notecard note">
-  <p><strong>Note:</strong></p>
-<ul>
- <li>The JavaScript function should always be saved to a file by itself but not be embedded in a HTML file or any other file.</li>
- <li>The examples at the end of this document are complete. There is no additional syntax needed to save it into a file and use it. (Of course, the JavaScripts must be edited to reflect your site's domain name and/or subnets.)</li>
-</ul>
-</div>
-
-<h2 id="Predefined_functions_and_environment">Predefined functions and environment</h2>
-
-<p>These functions can be used in building the PAC file:</p>
-
-<ul>
- <li>Hostname based conditions
-  <ul>
-   <li><code><a href="#isplainhostname">isPlainHostName()</a></code></li>
-   <li><code><a href="#dnsdomainis">dnsDomainIs()</a></code></li>
-   <li><code><a href="#localhostordomainis">localHostOrDomainIs()</a></code></li>
-   <li><code><a href="#isresolvable">isResolvable()</a></code></li>
-   <li><code><a href="#isinnet">isInNet()</a></code></li>
-  </ul>
- </li>
- <li>Related utility functions
-  <ul>
-   <li><code><a href="#dnsresolve">dnsResolve()</a></code></li>
-   <li><code><a href="#convert_addr">convert_addr()</a></code></li>
-   <li><code><a href="#myipaddress">myIpAddress()</a></code></li>
-   <li><code><a href="#dnsdomainlevels">dnsDomainLevels()</a></code></li>
-  </ul>
- </li>
- <li>URL/hostname based conditions
-  <ul>
-   <li><code><a href="#shexpmatch">shExpMatch()</a></code></li>
-  </ul>
- </li>
- <li>Time based conditions
-  <ul>
-   <li><code><a href="#weekdayrange">weekdayRange()</a></code></li>
-   <li><code><a href="#daterange">dateRange()</a></code></li>
-   <li><code><a href="#timerange">timeRange()</a></code></li>
-  </ul>
- </li>
- <li>Logging utility
-  <ul>
-   <li><code><a href="#alert">alert()</a></code></li>
-  </ul>
- </li>
- <li>There was one associative array (object) already defined, because at the time JavaScript code was unable to define it by itself:
-  <ul>
-   <li><code>ProxyConfig.bindings</code> {{deprecated_inline}}</li>
-  </ul>
- </li>
-</ul>
-
-<div class="notecard note">
-  <p><strong>Note:</strong> pactester (part of the <a href="https://github.com/pacparser/pacparser">pacparser </a>package) was used to test the following syntax examples.</p>
-  <ul>
-    <li>The PAC file is named <code>proxy.pac</code></li>
-    <li>Command line: <code>pactester -p ~/pacparser-master/tests/proxy.pac -u http://www.mozilla.org</code> (passes the <code>host</code> parameter <code>www.mozilla.org</code> and the <code>url</code> parameter <code>http://www.mozilla.org</code>)</li>
-  </ul>
-</div>
-
-<h3 id="isPlainHostName">isPlainHostName()</h3>
-
-<h4 id="Syntax_2">Syntax</h4>
-
-<pre class="brush: js">isPlainHostName(<var>host</var>)</pre>
-
-<h4 id="Parameters_2">Parameters</h4>
-
-<dl>
- <dt>host</dt>
- <dd>The hostname from the URL (excluding port number).</dd>
-</dl>
-
-<h4 id="Description_2">Description</h4>
-
-<p>True if and only if there is no domain name in the hostname (no dots).</p>
-
-<h4 id="Examples_2">Examples</h4>
-
-<pre class="brush: js">isPlainHostName("www.mozilla.org") // false
+  - [`alert()`](#alert)
+
+- There was one associative array (object) already defined, because at the time JavaScript code was unable to define it by itself:
+
+  - `ProxyConfig.bindings` {{deprecated_inline}}
+
+> **Note:** pactester (part of the [pacparser ](https://github.com/pacparser/pacparser)package) was used to test the following syntax examples.
+>
+> - The PAC file is named `proxy.pac`
+> - Command line: `pactester -p ~/pacparser-master/tests/proxy.pac -u http://www.mozilla.org` (passes the `host` parameter `www.mozilla.org` and the `url` parameter `http://www.mozilla.org`)
+
+### isPlainHostName()
+
+#### Syntax
+
+```js
+isPlainHostName(host)
+```
+
+#### Parameters
+
+- host
+  - : The hostname from the URL (excluding port number).
+
+#### Description
+
+True if and only if there is no domain name in the hostname (no dots).
+
+#### Examples
+
+```js
+isPlainHostName("www.mozilla.org") // false
 isPlainHostName("www") // true
-</pre>
+```
 
-<h3 id="dnsDomainIs"><code>dnsDomainIs()</code></h3>
+### `dnsDomainIs()`
 
-<h4 id="Syntax_3">Syntax</h4>
+#### Syntax
 
-<pre class="brush: js">dnsDomainIs(<var>host</var>, <var>domain</var>)</pre>
+```js
+dnsDomainIs(host, domain)
+```
 
-<h4 id="Parameters_3">Parameters</h4>
+#### Parameters
 
-<dl>
- <dt>host</dt>
- <dd>Is the hostname from the URL.</dd>
- <dt>domain</dt>
- <dd>Is the domain name to test the hostname against.</dd>
-</dl>
+- host
+  - : Is the hostname from the URL.
+- domain
+  - : Is the domain name to test the hostname against.
 
-<h4 id="Description_3">Description</h4>
+#### Description
 
-<p>Returns true if and only if the domain of hostname matches.</p>
+Returns true if and only if the domain of hostname matches.
 
-<h4 id="Examples_3">Examples</h4>
+#### Examples
 
-<pre class="brush: js">dnsDomainIs("www.mozilla.org", ".mozilla.org") // true
+```js
+dnsDomainIs("www.mozilla.org", ".mozilla.org") // true
 dnsDomainIs("www", ".mozilla.org") // false
-</pre>
+```
 
-<h3 id="localHostOrDomainIs">localHostOrDomainIs()</h3>
+### localHostOrDomainIs()
 
-<h4 id="Syntax_4">Syntax</h4>
+#### Syntax
 
-<pre class="brush: js">localHostOrDomainIs(<var>host</var>, <var>hostdom</var>)</pre>
+```js
+localHostOrDomainIs(host, hostdom)
+```
 
-<h4 id="Parameters_4">Parameters</h4>
+#### Parameters
 
-<dl>
- <dt>host</dt>
- <dd>The hostname from the URL.</dd>
- <dt>hostdom</dt>
- <dd>Fully qualified hostname to match against.</dd>
-</dl>
+- host
+  - : The hostname from the URL.
+- hostdom
+  - : Fully qualified hostname to match against.
 
-<h4 id="Description_4">Description</h4>
+#### Description
 
-<p>Is true if the hostname matches <em>exactly</em> the specified hostname, or if there is no domain name part in the hostname, but the unqualified hostname matches.</p>
+Is true if the hostname matches _exactly_ the specified hostname, or if there is no domain name part in the hostname, but the unqualified hostname matches.
 
-<h4 id="Examples_4">Examples</h4>
+#### Examples
 
-<pre class="brush: js">localHostOrDomainIs("www.mozilla.org" , "www.mozilla.org") // true (exact match)
+```js
+localHostOrDomainIs("www.mozilla.org" , "www.mozilla.org") // true (exact match)
 localHostOrDomainIs("www"             , "www.mozilla.org") // true (hostname match, domain not specified)
 localHostOrDomainIs("www.google.com"  , "www.mozilla.org") // false (domain name mismatch)
-localHostOrDomainIs("home.mozilla.org", "www.mozilla.org") // false (hostname mismatch)</pre>
+localHostOrDomainIs("home.mozilla.org", "www.mozilla.org") // false (hostname mismatch)
+```
 
-<h3 id="isResolvable">isResolvable()</h3>
+### isResolvable()
 
-<h4 id="Syntax_5">Syntax</h4>
+#### Syntax
 
-<pre class="brush: js">isResolvable(<var>host</var>)</pre>
+```js
+isResolvable(host)
+```
 
-<h4 id="Parameters_5">Parameters</h4>
+#### Parameters
 
-<dl>
- <dt>host</dt>
- <dd>is the hostname from the URL.</dd>
-</dl>
+- host
+  - : is the hostname from the URL.
 
-<p>Tries to resolve the hostname. Returns true if succeeds.</p>
+Tries to resolve the hostname. Returns true if succeeds.
 
-<h4 id="Examples_5">Examples:</h4>
+#### Examples:
 
-<pre class="brush: js">isResolvable("www.mozilla.org") // true
-</pre>
+```js
+isResolvable("www.mozilla.org") // true
+```
 
-<h3 id="isInNet">isInNet()</h3>
+### isInNet()
 
-<h4 id="Syntax_6">Syntax</h4>
+#### Syntax
 
-<pre class="brush: js">isInNet(<var>host</var>, <var>pattern</var>, <var>mask</var>)</pre>
+```js
+isInNet(host, pattern, mask)
+```
 
-<h4 id="Parameters_6">Parameters</h4>
+#### Parameters
 
-<dl>
- <dt>host</dt>
- <dd>a DNS hostname, or IP address. If a hostname is passed, it will be resolved into an IP address by this function.</dd>
- <dt>pattern</dt>
- <dd>an IP address pattern in the dot-separated format.</dd>
- <dt>mask</dt>
- <dd>mask for the IP address pattern informing which parts of the IP address should be matched against. 0 means ignore, 255 means match.</dd>
-</dl>
+- host
+  - : a DNS hostname, or IP address. If a hostname is passed, it will be resolved into an IP address by this function.
+- pattern
+  - : an IP address pattern in the dot-separated format.
+- mask
+  - : mask for the IP address pattern informing which parts of the IP address should be matched against. 0 means ignore, 255 means match.
 
-<p>True if and only if the IP address of the host matches the specified IP address pattern.</p>
+True if and only if the IP address of the host matches the specified IP address pattern.
 
-<p>Pattern and mask specification is done the same way as for SOCKS configuration.</p>
+Pattern and mask specification is done the same way as for SOCKS configuration.
 
-<h4 id="Examples_6">Examples:</h4>
+#### Examples:
 
-<pre class="brush: js">function alert_eval(str) { alert(str + ' is ' + eval(str)) }
+```js
+function alert_eval(str) { alert(str + ' is ' + eval(str)) }
 function FindProxyForURL(url, host) {
   alert_eval('isInNet(host, "63.245.213.24", "255.255.255.255")')
   // "PAC-alert: isInNet(host, "63.245.213.24", "255.255.255.255") is true"
 }
-</pre>
+```
 
-<h3 id="dnsResolve">dnsResolve()</h3>
+### dnsResolve()
 
-<pre class="brush: js">dnsResolve(<em>host</em>)</pre>
+```js
+dnsResolve(host)
+```
 
-<h4 id="Parameters_7">Parameters</h4>
+#### Parameters
 
-<dl>
- <dt>host</dt>
- <dd>hostname to resolve.</dd>
-</dl>
+- host
+  - : hostname to resolve.
 
-<p>Resolves the given DNS hostname into an IP address, and returns it in the dot-separated format as a string.</p>
+Resolves the given DNS hostname into an IP address, and returns it in the dot-separated format as a string.
 
-<h4 id="Example">Example</h4>
+#### Example
 
-<pre class="brush: js">dnsResolve("www.mozilla.org"); // returns the string "104.16.41.2"</pre>
+```js
+dnsResolve("www.mozilla.org"); // returns the string "104.16.41.2"
+```
 
-<h3 id="convert_addr">convert_addr()</h3>
+### convert_addr()
 
-<h4 id="Syntax_7">Syntax</h4>
+#### Syntax
 
-<pre class="brush: js">convert_addr(ipaddr)</pre>
+```js
+convert_addr(ipaddr)
+```
 
-<h4 id="Parameters_8">Parameters</h4>
+#### Parameters
 
-<dl>
- <dt>ipaddr</dt>
- <dd>Any dotted address such as an IP address or mask.</dd>
-</dl>
+- ipaddr
+  - : Any dotted address such as an IP address or mask.
 
-<p>Concatenates the four dot-separated bytes into one 4-byte word and converts it to decimal.</p>
+Concatenates the four dot-separated bytes into one 4-byte word and converts it to decimal.
 
-<h4 id="Example_2">Example</h4>
+#### Example
 
-<pre class="brush: js">convert_addr("104.16.41.2"); // returns the decimal number 1745889538</pre>
+```js
+convert_addr("104.16.41.2"); // returns the decimal number 1745889538
+```
 
-<h3 id="myIpAddress">myIpAddress()</h3>
+### myIpAddress()
 
-<h4 id="Syntax_8">Syntax</h4>
+#### Syntax
 
-<pre class="brush: js">myIpAddress()</pre>
+```js
+myIpAddress()
+```
 
-<h4 id="Parameters_9">Parameters</h4>
+#### Parameters
 
-<p><strong>(none)</strong></p>
+**(none)**
 
-<p>Returns the server IP address of the machine Firefox is running on, as a string in the dot-separated integer format.</p>
+Returns the server IP address of the machine Firefox is running on, as a string in the dot-separated integer format.
 
-<div class="notecard warning">
-  <p><strong>Warning:</strong> myIpAddress() returns the same IP address as the server address returned by <strong><code>nslookup localhost</code></strong> on a Linux machine. It does not return the public IP address.</p>
-</div>
+> **Warning:** myIpAddress() returns the same IP address as the server address returned by **`nslookup localhost`** on a Linux machine. It does not return the public IP address.
 
-<h4 id="Example_3">Example</h4>
+#### Example
 
-<pre class="brush: js">myIpAddress() //returns the string "127.0.1.1" if you were running Firefox on that localhost</pre>
+```js
+myIpAddress() //returns the string "127.0.1.1" if you were running Firefox on that localhost
+```
 
-<h3 id="dnsDomainLevels">dnsDomainLevels()</h3>
+### dnsDomainLevels()
 
-<h4 id="Syntax_9">Syntax</h4>
+#### Syntax
 
-<pre class="brush: js">dnsDomainLevels(<var>host</var>)</pre>
+```js
+dnsDomainLevels(host)
+```
 
-<h4 id="Parameters_10">Parameters</h4>
+#### Parameters
 
-<dl>
- <dt>host</dt>
- <dd>is the hostname from the URL.</dd>
-</dl>
+- host
+  - : is the hostname from the URL.
 
-<p>Returns the number (integer) of DNS domain levels (number of dots) in the hostname.</p>
+Returns the number (integer) of DNS domain levels (number of dots) in the hostname.
 
-<h4 id="Examples_7">Examples:</h4>
+#### Examples:
 
-<pre class="brush: js">dnsDomainLevels("www");             // 0
+```js
+dnsDomainLevels("www");             // 0
 dnsDomainLevels("mozilla.org");     // 1
 dnsDomainLevels("www.mozilla.org"); // 2
-</pre>
+```
 
-<h3 id="shExpMatch">shExpMatch()</h3>
+### shExpMatch()
 
-<h4 id="Syntax_10">Syntax</h4>
+#### Syntax
 
-<pre class="brush: js">shExpMatch(<var>str</var>, <var>shexp</var>)</pre>
+```js
+shExpMatch(str, shexp)
+```
 
-<h4 id="Parameters_11">Parameters</h4>
+#### Parameters
 
-<dl>
- <dt>str</dt>
- <dd>is any string to compare (e.g. the URL, or the hostname).</dd>
- <dt>shexp</dt>
- <dd>is a shell expression to compare against.</dd>
-</dl>
+- str
+  - : is any string to compare (e.g. the URL, or the hostname).
+- shexp
+  - : is a shell expression to compare against.
 
-<p>Returns <code>true</code> if the string matches the specified shell glob expression.</p>
+Returns `true` if the string matches the specified shell glob expression.
 
-<p>Support for particular glob expression syntax varies across browsers:
-  <code>*</code> (match any number of characters) and <code>?</code> (match one character) are always supported,
-  while <code>[characters]</code> and <code>[^characters]</code> are additionally supported by some implementations (including Firefox).</p>
+Support for particular glob expression syntax varies across browsers:
+`*` (match any number of characters) and `?` (match one character) are always supported,
+while `[characters]` and `[^characters]` are additionally supported by some implementations (including Firefox).
 
-<div class="notecard note">
-  <p><strong>Note:</strong> If supported by the client, JavaScript regular expressions typically provide a more powerful and consistent way to pattern-match URLs (and other strings).</p>
-</div>
+> **Note:** If supported by the client, JavaScript regular expressions typically provide a more powerful and consistent way to pattern-match URLs (and other strings).
 
+#### Examples
 
-<h4 id="Examples_8">Examples</h4>
+```js
+shExpMatch("http://home.netscape.com/people/ari/index.html", "*/ari/*"); // returns true
+shExpMatch("http://home.netscape.com/people/montulli/index.html", "*/ari/*"); // returns false
+```
 
-<pre class="brush: js">shExpMatch("http://home.netscape.com/people/ari/index.html", "*/ari/*"); // returns true
-shExpMatch("http://home.netscape.com/people/montulli/index.html", "*/ari/*"); // returns false</pre>
+### weekdayRange()
 
-<h3 id="weekdayRange">weekdayRange()</h3>
+#### Syntax
 
-<h4 id="Syntax_11">Syntax</h4>
+```js
+weekdayRange(wd1, wd2, [gmt])
+```
 
-<pre class="brush: js">weekdayRange(<var>wd1</var>, <var>wd2</var>, [<var>gmt</var>])</pre>
+> **Note:** (Before Firefox 49) wd1 must be less than wd2 if you want the function to evaluate these parameters as a range. See the warning below.
 
-<div class="notecard note">
-  <p><strong>Note:</strong> (Before Firefox 49) wd1 must be less than wd2 if you want the function to evaluate these parameters as a range. See the warning below.</p>
-</div>
+#### Parameters
 
-<h4 id="Parameters_12">Parameters</h4>
+- wd1 and wd2
+  - : One of the ordered weekday strings: `"SUN"`, `"MON"`, `"TUE"`, `"WED"`, `"THU"`, `"FRI"`, `"SAT"`
+- gmt
+  - : Is either the string "GMT" or is left out.
 
-<dl>
- <dt>wd1 and wd2</dt>
- <dd>One of the ordered weekday strings: <code>"SUN"</code>, <code>"MON"</code>, <code>"TUE"</code>, <code>"WED"</code>, <code>"THU"</code>, <code>"FRI"</code>, <code>"SAT"</code>
- <dt>gmt</dt>
- <dd>Is either the string "GMT" or is left out.</dd>
-</dl>
+Only the first parameter is mandatory. Either the second, the third, or both may be left out.
 
-<p>Only the first parameter is mandatory. Either the second, the third, or both may be left out.</p>
+If only one parameter is present, the function returns a value of true on the weekday that the parameter represents. If the string "GMT" is specified as a second parameter, times are taken to be in GMT. Otherwise, they are assumed to be in the local timezone.
 
-<p>If only one parameter is present, the function returns a value of true on the weekday that the parameter represents. If the string "GMT" is specified as a second parameter, times are taken to be in GMT. Otherwise, they are assumed to be in the local timezone.</p>
+If both **wd1** and **wd1** are defined, the condition is true if the current weekday is in between those two _ordered_ weekdays. Bounds are inclusive, _but the bounds are ordered_. If the "GMT" parameter is specified, times are taken to be in GMT. Otherwise, the local timezone is used.
 
-<p>If both <strong>wd1</strong> and <strong>wd1</strong> are defined, the condition is true if the current weekday is in between those two <em>ordered</em> weekdays. Bounds are inclusive, <em>but the bounds are ordered</em>. If the "GMT" parameter is specified, times are taken to be in GMT. Otherwise, the local timezone is used.</p>
+> **Warning:** _The order of the days matters_.
+> Before Firefox 49, `weekdayRange("SUN", "SAT")` will always evaluate to `true`.
+> Now `weekdayRange("WED", "SUN")` will only evaluate to `true`
+> if the current day is Wednesday or Sunday.
 
-<div class="notecard warning">
-  <p>
-    <strong>Warning:</strong> <em>The order of the days matters</em>.
-    Before Firefox 49, <code>weekdayRange("<em>SUN", "SAT"</em>)</code> will always evaluate to <code>true</code>.
-    Now <code>weekdayRange("<em>WED", "SUN"</em>)</code> will only evaluate to <code>true</code>
-    if the current day is Wednesday or Sunday.
-  </p>
-</div>
+#### Examples
 
-<h4 id="Examples_9">Examples</h4>
-
-<pre class="brush: js">weekdayRange("MON", "FRI");        // returns true Monday through Friday (local timezone)
+```js
+weekdayRange("MON", "FRI");        // returns true Monday through Friday (local timezone)
 weekdayRange("MON", "FRI", "GMT"); // returns true Monday through Friday (GMT timezone)
 weekdayRange("SAT");               // returns true on Saturdays local time
 weekdayRange("SAT", "GMT");        // returns true on Saturdays GMT time
-weekdayRange("FRI", "MON");        // returns true Friday and Monday only (note, order does matter!)</pre>
+weekdayRange("FRI", "MON");        // returns true Friday and Monday only (note, order does matter!)
+```
 
-<h3 id="dateRange">dateRange()</h3>
+### dateRange()
 
-<h4 id="Syntax_12">Syntax</h4>
+#### Syntax
 
-<pre class="brush: js">dateRange(&lt;day&gt; | &lt;month&gt; | &lt;year&gt;, [gmt])  // ambiguity is resolved by assuming year is greater than 31
-dateRange(&lt;day1&gt;, &lt;day2&gt;, [gmt])
-dateRange(&lt;month1&gt;, &lt;month2&gt;, [gmt])
-dateRange(&lt;year1&gt;, &lt;year2&gt;, [gmt])
-dateRange(&lt;day1&gt;, &lt;month1&gt;, &lt;day2&gt;, &lt;month2&gt;, [gmt])
-dateRange(&lt;month1&gt;, &lt;year1&gt;, &lt;month2&gt;, &lt;year2&gt;, [gmt])
-dateRange(&lt;day1&gt;, &lt;month1&gt;, &lt;year1&gt;, &lt;day2&gt;, &lt;month2&gt;, &lt;year2&gt;, [gmt])</pre>
+```js
+dateRange(<day> | <month> | <year>, [gmt])  // ambiguity is resolved by assuming year is greater than 31
+dateRange(<day1>, <day2>, [gmt])
+dateRange(<month1>, <month2>, [gmt])
+dateRange(<year1>, <year2>, [gmt])
+dateRange(<day1>, <month1>, <day2>, <month2>, [gmt])
+dateRange(<month1>, <year1>, <month2>, <year2>, [gmt])
+dateRange(<day1>, <month1>, <year1>, <day2>, <month2>, <year2>, [gmt])
+```
 
-<div class="notecard note">
-  <p><strong>Note:</strong> (Before Firefox 49) day1 must be less than day2, month1 must be less than month2, and year1 must be less than year2 if you want the function to evaluate these parameters as a range. See the warning below.</p>
-</div>
+> **Note:** (Before Firefox 49) day1 must be less than day2, month1 must be less than month2, and year1 must be less than year2 if you want the function to evaluate these parameters as a range. See the warning below.
 
-<h4 id="Parameters_13">Parameters</h4>
+#### Parameters
 
-<dl>
- <dt>day</dt>
- <dd>Is the ordered day of the month between 1 and 31 (as an integer).</dd>
-</dl>
+- day
+  - : Is the ordered day of the month between 1 and 31 (as an integer).
 
-<pre class="brush: html">1|2|3|4|5|6|7|8|9|10|11|12|13|14|15|16|17|18|19|20|21|22|23|24|25|26|27|28|29|30|31</pre>
+```html
+1|2|3|4|5|6|7|8|9|10|11|12|13|14|15|16|17|18|19|20|21|22|23|24|25|26|27|28|29|30|31
+```
 
-<dl>
- <dt>month</dt>
- <dd>Is one of the ordered month strings below.</dd>
-</dl>
+- month
+  - : Is one of the ordered month strings below.
 
-<pre class="brush: html">"JAN"|"FEB"|"MAR"|"APR"|"MAY"|"JUN"|"JUL"|"AUG"|"SEP"|"OCT"|"NOV"|"DEC"</pre>
+```html
+"JAN"|"FEB"|"MAR"|"APR"|"MAY"|"JUN"|"JUL"|"AUG"|"SEP"|"OCT"|"NOV"|"DEC"
+```
 
-<dl>
- <dt>year</dt>
- <dd>Is the ordered full year integer number. For example, 2016 (<strong>not</strong> 16).</dd>
- <dt>gmt</dt>
- <dd>Is either the string "GMT", which makes time comparison occur in GMT timezone, or is left out. If left unspecified, times are taken to be in the local timezone.</dd>
-</dl>
+- year
+  - : Is the ordered full year integer number. For example, 2016 (**not** 16).
+- gmt
+  - : Is either the string "GMT", which makes time comparison occur in GMT timezone, or is left out. If left unspecified, times are taken to be in the local timezone.
 
-<p>If only a single value is specified (from each category: day, month, year), the function returns a true value only on days that match that specification. If both values are specified, the result is true between those times, including bounds, <em>but the bounds are ordered</em>.</p>
+If only a single value is specified (from each category: day, month, year), the function returns a true value only on days that match that specification. If both values are specified, the result is true between those times, including bounds, _but the bounds are ordered_.
 
-<div class="notecard warning">
-  <p><strong>Warning:</strong> <strong>The order of the days, months, and years matter</strong>; Before Firefox 49, <code>dateRange("<em>JAN", "DEC"</em>)</code> will always evaluate to <code>true</code>. Now <code>dateRange("<em>DEC", "JAN"</em>)</code> will only evaluate true if the current month is December or January.</p>
-</div>
+> **Warning:** **The order of the days, months, and years matter**; Before Firefox 49, `dateRange("JAN", "DEC")` will always evaluate to `true`. Now `dateRange("DEC", "JAN")` will only evaluate true if the current month is December or January.
 
-<h4 id="Examples_10">Examples</h4>
+#### Examples
 
-<pre class="brush: js">dateRange(1);            // returns true on the first day of each month, local timezone
+```js
+dateRange(1);            // returns true on the first day of each month, local timezone
 dateRange(1, "GMT")      // returns true on the first day of each month, GMT timezone
 dateRange(1, 15);        // returns true on the first half of each month
 dateRange(24, "DEC");    // returns true on 24th of December each year
@@ -492,131 +482,131 @@ dateRange(1995);
 // returns true during the entire year of 1995
 
 dateRange(1995, 1997);
-// returns true from beginning of year 1995 until the end of year 1997</pre>
+// returns true from beginning of year 1995 until the end of year 1997
+```
 
-<h3 id="timeRange">timeRange()</h3>
+### timeRange()
 
-<h4 id="Syntax_13">Syntax</h4>
+#### Syntax
 
-<pre class="brush: html">// The full range of expansions is analogous to dateRange.
-timeRange(&lt;hour1&gt;, &lt;min1&gt;, &lt;sec1&gt;, &lt;hour2&gt;, &lt;min2&gt;, &lt;sec2&gt;, [gmt])</pre>
+```html
+// The full range of expansions is analogous to dateRange.
+timeRange(<hour1>, <min1>, <sec1>, <hour2>, <min2>, <sec2>, [gmt])
+```
 
-<div class="notecard note">
-  <p><strong>Note:</strong> (Before Firefox 49) the category hour1, min1, sec1 must be less than the category hour2, min2, sec2 if you want the function to evaluate these parameters as a range. See the warning below.</p>
-</div>
+> **Note:** (Before Firefox 49) the category hour1, min1, sec1 must be less than the category hour2, min2, sec2 if you want the function to evaluate these parameters as a range. See the warning below.
 
-<h4 id="Parameters_14">Parameters</h4>
+#### Parameters
 
-<dl>
- <dt>hour</dt>
- <dd>Is the hour from 0 to 23. (0 is midnight, 23 is 11 pm.)</dd>
- <dt>min</dt>
- <dd>Minutes from 0 to 59.</dd>
- <dt>sec</dt>
- <dd>Seconds from 0 to 59.</dd>
- <dt>gmt</dt>
- <dd>Either the string "GMT" for GMT timezone, or not specified, for local timezone.</dd>
-</dl>
+- hour
+  - : Is the hour from 0 to 23. (0 is midnight, 23 is 11 pm.)
+- min
+  - : Minutes from 0 to 59.
+- sec
+  - : Seconds from 0 to 59.
+- gmt
+  - : Either the string "GMT" for GMT timezone, or not specified, for local timezone.
 
-<p>If only a single value is specified (from each category: hour, minute, second), the function returns a true value only at times that match that specification. If both values are specified, the result is true between those times, including bounds, <em>but the bounds are ordered</em>.</p>
+If only a single value is specified (from each category: hour, minute, second), the function returns a true value only at times that match that specification. If both values are specified, the result is true between those times, including bounds, _but the bounds are ordered_.
 
-<div class="notecard warning">
-  <p><strong>Warning:</strong> <strong>The order of the hour, minute, second matter</strong>; Before Firefox 49, <code>timeRange(<em>0, 23</em>)</code> will always evaluate to true. Now <code>timeRange(<em>23, 0</em>)</code> will only evaluate true if the current hour is 23:00 or midnight.</p>
-</div>
+> **Warning:** **The order of the hour, minute, second matter**; Before Firefox 49, `timeRange(0, 23)` will always evaluate to true. Now `timeRange(23, 0)` will only evaluate true if the current hour is 23:00 or midnight.
 
-<h4 id="Examples_11">Examples</h4>
+#### Examples
 
-<pre class="brush: js">timerange(12);                // returns true from noon to 1pm
+```js
+timerange(12);                // returns true from noon to 1pm
 timerange(12, 13);            // returns true from noon to 1pm
 timerange(12, "GMT");         // returns true from noon to 1pm, in GMT timezone
 timerange(9, 17);             // returns true from 9am to 5pm
 timerange(8, 30, 17, 00);     // returns true from 8:30am to 5:00pm
-timerange(0, 0, 0, 0, 0, 30); // returns true between midnight and 30 seconds past midnight</pre>
+timerange(0, 0, 0, 0, 0, 30); // returns true between midnight and 30 seconds past midnight
+```
 
-<h3 id="alert">alert()</h3>
+### alert()
 
-<h4 id="Syntax_14">Syntax</h4>
+#### Syntax
 
-<pre class="brush: html">
+```html
 alert(message)
-</pre>
+```
 
-<h4 id="Parameters_15">Parameters</h4>
+#### Parameters
 
-<dl>
- <dt>message</dt>
- <dd>The string to log</dd>
-</dl>
+- message
+  - : The string to log
 
-<p>Logs the message in the browser console.</p>
+Logs the message in the browser console.
 
-<h4 id="Examples_12">Examples</h4>
+#### Examples
 
-<pre class="brush: js">alert(host + " = " + dnsResolve(host));            // logs the host name and its IP address
-alert("Error: shouldn't reach this clause.");      // log a simple message</pre>
+```js
+alert(host + " = " + dnsResolve(host));            // logs the host name and its IP address
+alert("Error: shouldn't reach this clause.");      // log a simple message
+```
 
-<h2 id="Example_1">Example 1</h2>
+## Example 1
 
-<h3 id="Use_proxy_for_everything_except_local_hosts">Use proxy for everything except local hosts</h3>
+### Use proxy for everything except local hosts
 
-<div class="notecard note">
-  <p><strong>Note:</strong> Since all of the examples that follow are very specific, they have not been tested.</p>
-</div>
+> **Note:** Since all of the examples that follow are very specific, they have not been tested.
 
-<p>All hosts which aren't fully qualified, or the ones that are in local domain, will be connected to directly. Everything else will go through <code>w3proxy.mozilla.org:8080</code>. If the proxy goes down, connections become direct automatically:</p>
+All hosts which aren't fully qualified, or the ones that are in local domain, will be connected to directly. Everything else will go through `w3proxy.mozilla.org:8080`. If the proxy goes down, connections become direct automatically:
 
-<pre class="brush: js">function FindProxyForURL(url, host) {
+```js
+function FindProxyForURL(url, host) {
   if (isPlainHostName(host) || dnsDomainIs(host, ".mozilla.org")) {
     return "DIRECT";
   } else {
     return "PROXY w3proxy.mozilla.org:8080; DIRECT";
   }
-}</pre>
+}
+```
 
-<div class="notecard note">
-  <p><strong>Note:</strong> This is the simplest and most efficient autoconfig file for cases where there's only one proxy.</p>
-</div>
+> **Note:** This is the simplest and most efficient autoconfig file for cases where there's only one proxy.
 
-<h2 id="Example_2_2">Example 2</h2>
+## Example 2
 
-<h3 id="As_above_but_use_proxy_for_local_servers_which_are_outside_the_firewall">As above, but use proxy for local servers which are outside the firewall</h3>
+### As above, but use proxy for local servers which are outside the firewall
 
-<p>If there are hosts (such as the main Web server) that belong to the local domain but are outside the firewall and are only reachable through the proxy server, those exceptions can be handled using the <code>localHostOrDomainIs()</code> function:</p>
+If there are hosts (such as the main Web server) that belong to the local domain but are outside the firewall and are only reachable through the proxy server, those exceptions can be handled using the `localHostOrDomainIs()` function:
 
-<pre class="brush: js">function FindProxyForURL(url, host) {
+```js
+function FindProxyForURL(url, host) {
   if (
-    (isPlainHostName(host) || dnsDomainIs(host, ".mozilla.org")) &amp;&amp;
-    !localHostOrDomainIs(host, "www.mozilla.org") &amp;&amp;
+    (isPlainHostName(host) || dnsDomainIs(host, ".mozilla.org")) &&
+    !localHostOrDomainIs(host, "www.mozilla.org") &&
     !localHostOrDomainIs(host, "merchant.mozilla.org")
   ) {
     return "DIRECT";
   } else {
     return "PROXY w3proxy.mozilla.org:8080; DIRECT";
   }
-}</pre>
+}
+```
 
-<p>The above example will use the proxy for everything except local hosts in the mozilla.org domain, with the further exception that hosts <code>www.mozilla.org</code> and <code>merchant.mozilla.org</code> will go through the proxy.</p>
+The above example will use the proxy for everything except local hosts in the mozilla.org domain, with the further exception that hosts `www.mozilla.org` and `merchant.mozilla.org` will go through the proxy.
 
-<div class="notecard note">
-  <p><strong>Note:</strong> The order of the above exceptions for efficiency: <code>localHostOrDomainIs()</code> functions only get executed for URLs that are in local domain, not for every URL. Be careful to note the parentheses around the <em>or</em> expression before the <em>and</em> expression to achieve the above-mentioned efficient behavior.</p>
-</div>
+> **Note:** The order of the above exceptions for efficiency: `localHostOrDomainIs()` functions only get executed for URLs that are in local domain, not for every URL. Be careful to note the parentheses around the _or_ expression before the _and_ expression to achieve the above-mentioned efficient behavior.
 
-<h2 id="Example_3_2">Example 3</h2>
+## Example 3
 
-<h3 id="Use_proxy_only_if_cannot_resolve_host">Use proxy only if cannot resolve host</h3>
+### Use proxy only if cannot resolve host
 
-<p>This example will work in an environment where the internal DNS server is set up so that it can only resolve internal host names, and the goal is to use a proxy only for hosts that aren't resolvable:</p>
+This example will work in an environment where the internal DNS server is set up so that it can only resolve internal host names, and the goal is to use a proxy only for hosts that aren't resolvable:
 
-<pre class="brush: js">function FindProxyForURL(url, host) {
+```js
+function FindProxyForURL(url, host) {
   if (isResolvable(host))
     return "DIRECT";
   else
     return "PROXY proxy.mydomain.com:8080";
-}</pre>
+}
+```
 
-<p>The above requires consulting the DNS every time; it can be grouped intelligently with other rules so that DNS is consulted only if other rules do not yield a result:</p>
+The above requires consulting the DNS every time; it can be grouped intelligently with other rules so that DNS is consulted only if other rules do not yield a result:
 
-<pre class="brush: js">function FindProxyForURL(url, host) {
+```js
+function FindProxyForURL(url, host) {
   if (
     isPlainHostName(host) ||
     dnsDomainIs(host, ".mydomain.com") ||
@@ -626,24 +616,28 @@ alert("Error: shouldn't reach this clause.");      // log a simple message</pre>
   } else {
     return "PROXY proxy.mydomain.com:8080";
   }
-}</pre>
+}
+```
 
-<h2 id="Example_4">Example 4</h2>
+## Example 4
 
-<h3 id="Subnet_based_decisions">Subnet based decisions</h3>
+### Subnet based decisions
 
-<p>In this example all of the hosts in a given subnet are connected-to directly, others are connected through the proxy:</p>
+In this example all of the hosts in a given subnet are connected-to directly, others are connected through the proxy:
 
-<pre class="brush: js">function FindProxyForURL(url, host) {
+```js
+function FindProxyForURL(url, host) {
   if (isInNet(host, "198.95.0.0", "255.255.0.0"))
     return "DIRECT";
   else
     return "PROXY proxy.mydomain.com:8080";
-}</pre>
+}
+```
 
-<p>Again, use of the DNS server in the above can be minimized by adding redundant rules in the beginning:</p>
+Again, use of the DNS server in the above can be minimized by adding redundant rules in the beginning:
 
-<pre class="brush: js">function FindProxyForURL(url, host) {
+```js
+function FindProxyForURL(url, host) {
   if (
     isPlainHostName(host) ||
     dnsDomainIs(host, ".mydomain.com") ||
@@ -653,42 +647,26 @@ alert("Error: shouldn't reach this clause.");      // log a simple message</pre>
   } else {
     return "PROXY proxy.mydomain.com:8080";
   }
-}</pre>
-
-<h2 id="Example_5">Example 5</h2>
-
-<h3 id="Load_balancingrouting_based_on_URL_patterns">Load balancing/routing based on URL patterns</h3>
-
-<p>This example is more sophisticated. There are four (4) proxy servers; one of them is a hot stand-by for all of the other ones, so if any of the remaining three goes down the fourth one will take over. Furthermore, the three remaining proxy servers share the load based on URL patterns, which makes their caching more effective (there is only one copy of any document on the three servers - as opposed to one copy on each of them). The load is distributed like this:</p>
-
-<table>
- <tbody>
-  <tr>
-   <th>Proxy</th>
-   <th>Purpose</th>
-  </tr>
-  <tr>
-   <td>#1</td>
-   <td>.com domain</td>
-  </tr>
-  <tr>
-   <td>#2</td>
-   <td>.edu domain</td>
-  </tr>
-  <tr>
-   <td>#3</td>
-   <td>all other domains</td>
-  </tr>
-  <tr>
-   <td>#4</td>
-   <td>hot stand-by</td>
-  </tr>
- </tbody>
-</table>
-
-<p>All local accesses are desired to be direct. All proxy servers run on the port 8080 (they don't need to, you can just change your port but remember to modify your configuations on both side). Note how strings can be concatenated with the <code><strong>+</strong></code> operator in JavaScript.</p>
-
-<pre class="brush: js">function FindProxyForURL(url, host) {
+}
+```
+
+## Example 5
+
+### Load balancing/routing based on URL patterns
+
+This example is more sophisticated. There are four (4) proxy servers; one of them is a hot stand-by for all of the other ones, so if any of the remaining three goes down the fourth one will take over. Furthermore, the three remaining proxy servers share the load based on URL patterns, which makes their caching more effective (there is only one copy of any document on the three servers - as opposed to one copy on each of them). The load is distributed like this:
+
+| Proxy | Purpose           |
+| ----- | ----------------- |
+| #1    | .com domain       |
+| #2    | .edu domain       |
+| #3    | all other domains |
+| #4    | hot stand-by      |
+
+All local accesses are desired to be direct. All proxy servers run on the port 8080 (they don't need to, you can just change your port but remember to modify your configuations on both side). Note how strings can be concatenated with the **`+`** operator in JavaScript.
+
+```js
+function FindProxyForURL(url, host) {
 
   if (isPlainHostName(host) || dnsDomainIs(host, ".mydomain.com"))
     return "DIRECT";
@@ -704,15 +682,17 @@ alert("Error: shouldn't reach this clause.");      // log a simple message</pre>
   else
     return "PROXY proxy3.mydomain.com:8080; " +
            "PROXY proxy4.mydomain.com:8080";
-}</pre>
+}
+```
 
-<h2 id="Example_6">Example 6</h2>
+## Example 6
 
-<h3 id="Setting_a_proxy_for_a_specific_protocol">Setting a proxy for a specific protocol</h3>
+### Setting a proxy for a specific protocol
 
-<p>Most of the standard JavaScript functionality is available for use in the <code>FindProxyForURL()</code> function. As an example, to set different proxies based on the protocol the {{jsxref("String.prototype.startsWith()", "startsWith()")}} function can be used:</p>
+Most of the standard JavaScript functionality is available for use in the `FindProxyForURL()` function. As an example, to set different proxies based on the protocol the {{jsxref("String.prototype.startsWith()", "startsWith()")}} function can be used:
 
-<pre class="brush: js">function FindProxyForURL(url, host) {
+```js
+function FindProxyForURL(url, host) {
 
   if (url.startsWith("http:"))
     return "PROXY http-proxy.mydomain.com:8080";
@@ -729,29 +709,29 @@ alert("Error: shouldn't reach this clause.");      // log a simple message</pre>
   else
     return "DIRECT";
 
-}</pre>
+}
+```
 
-<div class="notecard note">
-  <p><strong>Note:</strong> The same can be accomplished using the <code><a href="#shexpmatch">shExpMatch()</a></code> function described earlier.</p>
-</div>
+> **Note:** The same can be accomplished using the [`shExpMatch()`](#shexpmatch) function described earlier.
 
-<p>For example:</p>
+For example:
 
-<pre class="brush: js">// ...
+```js
+// ...
 if (shExpMatch(url, "http:*")) {
   return "PROXY http-proxy.mydomain.com:8080";
 }
-// ...</pre>
+// ...
+```
 
-<div class="notecard note">
-  <p><strong>Note:</strong> The autoconfig file can be output by a CGI script. This is useful, for example, when making the autoconfig file act differently based on the client IP address (the <code>REMOTE_ADDR</code> environment variable in CGI).</p>
-  <p>Usage of <code>isInNet()</code>, <code>isResolvable()</code> and <code>dnsResolve()</code> functions should be carefully considered, as they require the DNS server to be consulted. All the other autoconfig-related functions are mere string-matching functions that don't require the use of a DNS server. If a proxy is used, the proxy will perform its DNS lookup which would double the impact on the DNS server. Most of the time these functions are not necessary to achieve the desired result.</p>
-</div>
+> **Note:** The autoconfig file can be output by a CGI script. This is useful, for example, when making the autoconfig file act differently based on the client IP address (the `REMOTE_ADDR` environment variable in CGI).
+>
+> Usage of `isInNet()`, `isResolvable()` and `dnsResolve()` functions should be carefully considered, as they require the DNS server to be consulted. All the other autoconfig-related functions are mere string-matching functions that don't require the use of a DNS server. If a proxy is used, the proxy will perform its DNS lookup which would double the impact on the DNS server. Most of the time these functions are not necessary to achieve the desired result.
 
-<h2 id="History_and_implementation">History and implementation</h2>
+## History and implementation
 
-<p>Proxy auto-config was introduced into Netscape Navigator 2.0 in the late 1990s, at the same time when JavaScript was introduced. Open-sourcing Netscape eventually lead to Firefox itself.</p>
+Proxy auto-config was introduced into Netscape Navigator 2.0 in the late 1990s, at the same time when JavaScript was introduced. Open-sourcing Netscape eventually lead to Firefox itself.
 
-<p>The most "original" implementation of PAC and its JavaScript libraries is, therefore, <code>nsProxyAutoConfig.js</code> found in early versions of Firefox. These utilities are found in many other open-source systems including <a href="https://cs.chromium.org/chromium/src/services/proxy_resolver/pac_js_library.h">Chromium</a>. Firefox later integrated the file into <code><a href="https://dxr.mozilla.org/mozilla-central/source/netwerk/base/ProxyAutoConfig.cpp">ProxyAutoConfig.cpp</a></code> as a C++ string literal. To extract it into its own file, it suffices to copy the chunk into JavaScript with a <code>console.log</code> directive to print it.</p>
+The most "original" implementation of PAC and its JavaScript libraries is, therefore, `nsProxyAutoConfig.js` found in early versions of Firefox. These utilities are found in many other open-source systems including [Chromium](https://cs.chromium.org/chromium/src/services/proxy_resolver/pac_js_library.h). Firefox later integrated the file into [`ProxyAutoConfig.cpp`](https://dxr.mozilla.org/mozilla-central/source/netwerk/base/ProxyAutoConfig.cpp) as a C++ string literal. To extract it into its own file, it suffices to copy the chunk into JavaScript with a `console.log` directive to print it.
 
-<p>Microsoft in general made its own implementation. There used to be <a href="https://en.wikipedia.org/wiki/Proxy_auto-config#Old_Microsoft_problems">some problems with their libraries</a>, but most are resolved by now. They have defined <a href="https://docs.microsoft.com/en-us/windows/win32/winhttp/ipv6-extensions-to-navigator-auto-config-file-format">some new "Ex" suffixed functions</a> around the address handling parts to support IPv6. The feature is supported by Chromium, but not yet by Firefox (<a href="https://bugzilla.mozilla.org/show_bug.cgi?id=558253">bugzilla #558253</a>).</p>
+Microsoft in general made its own implementation. There used to be [some problems with their libraries](https://en.wikipedia.org/wiki/Proxy_auto-config#Old_Microsoft_problems), but most are resolved by now. They have defined [some new "Ex" suffixed functions](https://docs.microsoft.com/en-us/windows/win32/winhttp/ipv6-extensions-to-navigator-auto-config-file-format) around the address handling parts to support IPv6. The feature is supported by Chromium, but not yet by Firefox ([bugzilla #558253](https://bugzilla.mozilla.org/show_bug.cgi?id=558253)).
diff --git a/files/en-us/web/http/public_key_pinning/index.md b/files/en-us/web/http/public_key_pinning/index.md
index a94f099507f4f1a..58792dbf4cc2630 100644
--- a/files/en-us/web/http/public_key_pinning/index.md
+++ b/files/en-us/web/http/public_key_pinning/index.md
@@ -9,156 +9,134 @@ tags:
   - Deprecated
   - Security
 ---
-<p>{{HTTPSidebar}}{{deprecated_header}}</p>
+{{HTTPSidebar}}{{deprecated_header}}
 
-<div class="notecard note">
-  <p><strong>Note:</strong> Public Key Pinning mechanism was deprecated in favor of <a href="/en-US/docs/Web/Security/Certificate_Transparency">Certificate Transparency</a> and {{HTTPHeader("Expect-CT")}} header.</p>
-</div>
+> **Note:** Public Key Pinning mechanism was deprecated in favor of [Certificate Transparency](/en-US/docs/Web/Security/Certificate_Transparency) and {{HTTPHeader("Expect-CT")}} header.
 
-<p class="summary"><strong>HTTP Public Key Pinning</strong> ({{Glossary("HPKP")}}) was a security feature that used to tell a web client to associate a specific cryptographic public key with a certain web server to decrease the risk of {{Glossary("MITM")}} attacks with forged certificates. It has been removed in modern browsers and is no longer supported.</p>
+**HTTP Public Key Pinning** ({{Glossary("HPKP")}}) was a security feature that used to tell a web client to associate a specific cryptographic public key with a certain web server to decrease the risk of {{Glossary("MITM")}} attacks with forged certificates. It has been removed in modern browsers and is no longer supported.
 
-<p>To ensure the authenticity of a server's public key used in {{Glossary("TLS")}} sessions, this public key is wrapped into a X.509 certificate which is usually signed by a certificate authority ({{Glossary("Certificate_authority", "CA")}}). Web clients such as browsers trust a lot of these CAs, which can all create certificates for arbitrary domain names. If an attacker is able to compromise a single CA, they can perform MITM attacks on various TLS connections. HPKP can circumvent this threat for the {{Glossary("HTTPS")}} protocol by telling the client which public key belongs to a certain web server.</p>
+To ensure the authenticity of a server's public key used in {{Glossary("TLS")}} sessions, this public key is wrapped into a X.509 certificate which is usually signed by a certificate authority ({{Glossary("Certificate_authority", "CA")}}). Web clients such as browsers trust a lot of these CAs, which can all create certificates for arbitrary domain names. If an attacker is able to compromise a single CA, they can perform MITM attacks on various TLS connections. HPKP can circumvent this threat for the {{Glossary("HTTPS")}} protocol by telling the client which public key belongs to a certain web server.
 
-<p>HPKP is a <em>Trust on First Use</em> ({{Glossary("TOFU")}}) technique. The first time a web server tells a client via a special HTTP header which public keys belong to it, the client stores this information for a given period of time. When the client visits the server again, it expects at least one certificate in the certificate chain to contain a public key whose fingerprint is already known via HPKP. If the server delivers an unknown public key, the client should present a warning to the user.</p>
+HPKP is a _Trust on First Use_ ({{Glossary("TOFU")}}) technique. The first time a web server tells a client via a special HTTP header which public keys belong to it, the client stores this information for a given period of time. When the client visits the server again, it expects at least one certificate in the certificate chain to contain a public key whose fingerprint is already known via HPKP. If the server delivers an unknown public key, the client should present a warning to the user.
 
-<div class="notecard note">
-  <p><strong>Note:</strong> Firefox and Chrome <strong>disable pin validation</strong> for pinned hosts whose validated certificate chain terminates at a <strong>user-defined trust anchor</strong> (rather than a built-in trust anchor). This means that for users who imported custom root certificates all pinning violations are ignored.</p>
-</div>
+> **Note:** Firefox and Chrome **disable pin validation** for pinned hosts whose validated certificate chain terminates at a **user-defined trust anchor** (rather than a built-in trust anchor). This means that for users who imported custom root certificates all pinning violations are ignored.
 
-<h2 id="Enabling_HPKP">Enabling HPKP</h2>
+## Enabling HPKP
 
-<p>To enable this feature for your site, you need to return the {{HTTPHeader("Public-Key-Pins")}} HTTP header when your site is accessed over HTTPS:</p>
+To enable this feature for your site, you need to return the {{HTTPHeader("Public-Key-Pins")}} HTTP header when your site is accessed over HTTPS:
 
-<pre>Public-Key-Pins: pin-sha256="base64=="; max-age=<em>expireTime</em> [; includeSubDomains][; report-uri="<em>reportURI"</em>]</pre>
+    Public-Key-Pins: pin-sha256="base64=="; max-age=expireTime [; includeSubDomains][; report-uri="reportURI"]
 
-<dl>
- <dt><code>pin-sha256</code></dt>
- <dd>The quoted string is the Base64 encoded <em>Subject Public Key Information</em> ({{Glossary("SPKI")}}) fingerprint. It is possible to specify multiple pins for different public keys. Some browsers might allow other hashing algorithms than SHA-256 in the future. See below on how to extract this information out of a certificate or key file.</dd>
- <dt><code>max-age</code></dt>
- <dd>The time, in seconds, that the browser should remember that this site is only to be accessed using one of the defined keys.</dd>
- <dt><code>includeSubDomains</code> {{optional_inline}}</dt>
- <dd>If this optional parameter is specified, this rule applies to all of the site's subdomains as well.</dd>
- <dt><code>report-uri</code> {{optional_inline}}</dt>
- <dd>If this optional parameter is specified, pin validation failures are reported to the given URL.</dd>
-</dl>
+- `pin-sha256`
+  - : The quoted string is the Base64 encoded _Subject Public Key Information_ ({{Glossary("SPKI")}}) fingerprint. It is possible to specify multiple pins for different public keys. Some browsers might allow other hashing algorithms than SHA-256 in the future. See below on how to extract this information out of a certificate or key file.
+- `max-age`
+  - : The time, in seconds, that the browser should remember that this site is only to be accessed using one of the defined keys.
+- `includeSubDomains` {{optional_inline}}
+  - : If this optional parameter is specified, this rule applies to all of the site's subdomains as well.
+- `report-uri` {{optional_inline}}
+  - : If this optional parameter is specified, pin validation failures are reported to the given URL.
 
-<div class="notecard note">
-  <p><strong>Note:</strong> The current specification requires including a second pin for a backup key which isn't yet used in production. This allows for changing the server's public key without breaking accessibility for clients that have already noted the pins. This is important for example when the former key gets compromised.</p>
-</div>
+> **Note:** The current specification requires including a second pin for a backup key which isn't yet used in production. This allows for changing the server's public key without breaking accessibility for clients that have already noted the pins. This is important for example when the former key gets compromised.
 
-<h3 id="Extracting_the_Base64_encoded_public_key_information">Extracting the Base64 encoded public key information</h3>
+### Extracting the Base64 encoded public key information
 
-<div class="notecard note">
-  <p><strong>Note:</strong> While the example below shows how to set a pin on a server certificate, it is recommended to place the pin on the intermediate certificate of the CA that issued the server certificate, to ease certificates renewals and rotations.</p>
-</div>
+> **Note:** While the example below shows how to set a pin on a server certificate, it is recommended to place the pin on the intermediate certificate of the CA that issued the server certificate, to ease certificates renewals and rotations.
 
-<p>First you need to extract the public key information from your certificate or key file and encode them using Base64.</p>
+First you need to extract the public key information from your certificate or key file and encode them using Base64.
 
-<p>The following commands will help you extract the Base64 encoded information from a key file, a certificate signing request, or a certificate.</p>
+The following commands will help you extract the Base64 encoded information from a key file, a certificate signing request, or a certificate.
 
-<pre>openssl rsa -in my-rsa-key-file.key -outform der -pubout | openssl dgst -sha256 -binary | openssl enc -base64</pre>
+    openssl rsa -in my-rsa-key-file.key -outform der -pubout | openssl dgst -sha256 -binary | openssl enc -base64
 
-<pre>openssl ec -in my-ecc-key-file.key -outform der -pubout | openssl dgst -sha256 -binary | openssl enc -base64</pre>
+<!---->
 
-<pre>openssl req -in my-signing-request.csr -pubkey -noout | openssl pkey -pubin -outform der | openssl dgst -sha256 -binary | openssl enc -base64</pre>
+    openssl ec -in my-ecc-key-file.key -outform der -pubout | openssl dgst -sha256 -binary | openssl enc -base64
 
-<pre>openssl x509 -in my-certificate.crt -pubkey -noout | openssl pkey -pubin -outform der | openssl dgst -sha256 -binary | openssl enc -base64</pre>
+<!---->
 
-<p>The following command will extract the Base64 encoded information for a website.</p>
+    openssl req -in my-signing-request.csr -pubkey -noout | openssl pkey -pubin -outform der | openssl dgst -sha256 -binary | openssl enc -base64
 
-<pre>openssl s_client -servername www.example.com -connect www.example.com:443 | openssl x509 -pubkey -noout | openssl pkey -pubin -outform der | openssl dgst -sha256 -binary | openssl enc -base64</pre>
+<!---->
 
-<h3 id="Example_HPKP_Header">Example HPKP Header</h3>
+    openssl x509 -in my-certificate.crt -pubkey -noout | openssl pkey -pubin -outform der | openssl dgst -sha256 -binary | openssl enc -base64
 
-<pre>Public-Key-Pins:
-  pin-sha256="cUPcTAZWKaASuYWhhneDttWpY3oBAkE3h2+soZS7sWs=";
-  pin-sha256="M8HztCzM3elUxkcjR2S5P4hhyBNf6lHkmjAHKhpGPWE=";
-  max-age=5184000; includeSubDomains;
-  report-uri="<em>https://www.example.org/hpkp-report"</em></pre>
+The following command will extract the Base64 encoded information for a website.
 
-<p>In this example, <strong>pin-sha256="cUPcTAZWKaASuYWhhneDttWpY3oBAkE3h2+soZS7sWs="</strong> pins the server's public key used in production. The second pin declaration <strong>pin-sha256="M8HztCzM3elUxkcjR2S5P4hhyBNf6lHkmjAHKhpGPWE="</strong> also pins the backup key. <strong>max-age=5184000</strong> tells the client to store this information for two months, which is a reasonable time limit according to the IETF RFC. This key pinning is also valid for all subdomains, which is told by the <strong>includeSubDomains</strong> declaration. Finally, <strong>report-uri="https://www.example.net/hpkp-report"</strong> explains where to report pin validation failures.</p>
+    openssl s_client -servername www.example.com -connect www.example.com:443 | openssl x509 -pubkey -noout | openssl pkey -pubin -outform der | openssl dgst -sha256 -binary | openssl enc -base64
 
-<h3 id="Report-Only_header">Report-Only header</h3>
+### Example HPKP Header
 
-<p>Instead of using a {{HTTPHeader("Public-Key-Pins")}} header you can also use a {{HTTPHeader("Public-Key-Pins-Report-Only")}} header. This header only sends reports to the <code>report-uri</code> specified in the header and does still allow browsers to connect to the webserver even if the pinning is violated.</p>
+    Public-Key-Pins:
+      pin-sha256="cUPcTAZWKaASuYWhhneDttWpY3oBAkE3h2+soZS7sWs=";
+      pin-sha256="M8HztCzM3elUxkcjR2S5P4hhyBNf6lHkmjAHKhpGPWE=";
+      max-age=5184000; includeSubDomains;
+      report-uri="https://www.example.org/hpkp-report"
 
-<h3 id="Setting_up_your_webserver_to_include_the_HPKP_header">Setting up your webserver to include the HPKP header</h3>
+In this example, **pin-sha256="cUPcTAZWKaASuYWhhneDttWpY3oBAkE3h2+soZS7sWs="** pins the server's public key used in production. The second pin declaration **pin-sha256="M8HztCzM3elUxkcjR2S5P4hhyBNf6lHkmjAHKhpGPWE="** also pins the backup key. **max-age=5184000** tells the client to store this information for two months, which is a reasonable time limit according to the IETF RFC. This key pinning is also valid for all subdomains, which is told by the **includeSubDomains** declaration. Finally, **report-uri="https\://www\.example.net/hpkp-report"** explains where to report pin validation failures.
 
-<p>The concrete steps necessary to deliver the HPKP header depend on the web server you use.</p>
+### Report-Only header
 
-<div class="notecard note">
-  <p><strong>Note:</strong> These examples use a max-age of two months and include all subdomains. It is advised to verify that this setup will work for your server.</p>
-</div>
+Instead of using a {{HTTPHeader("Public-Key-Pins")}} header you can also use a {{HTTPHeader("Public-Key-Pins-Report-Only")}} header. This header only sends reports to the `report-uri` specified in the header and does still allow browsers to connect to the webserver even if the pinning is violated.
 
-<div class="notecard warning">
-  <p><strong>Warning:</strong> HPKP has the potential to lock out users for a long time if used incorrectly! The use of backup certificates and/or pinning the CA certificate is recommended.</p>
-</div>
+### Setting up your webserver to include the HPKP header
 
-<h4 id="Apache">Apache</h4>
+The concrete steps necessary to deliver the HPKP header depend on the web server you use.
 
-<p>Adding a line similar to the following to your webserver's config will enable HPKP on your Apache. This requires <code>mod_headers</code> enabled.</p>
+> **Note:** These examples use a max-age of two months and include all subdomains. It is advised to verify that this setup will work for your server.
 
-<pre>Header always set Public-Key-Pins "pin-sha256=\"base64+primary==\"; pin-sha256=\"base64+backup==\"; max-age=5184000; includeSubDomains"</pre>
+> **Warning:** HPKP has the potential to lock out users for a long time if used incorrectly! The use of backup certificates and/or pinning the CA certificate is recommended.
 
-<h4 id="Nginx">Nginx</h4>
+#### Apache
 
-<p>Adding the following line and inserting the appropriate <code>pin-sha256="..."</code> values will enable HPKP on your nginx. This requires the <code>ngx_http_headers_module.</code></p>
+Adding a line similar to the following to your webserver's config will enable HPKP on your Apache. This requires `mod_headers` enabled.
 
-<pre>add_header Public-Key-Pins 'pin-sha256="base64+primary=="; pin-sha256="base64+backup=="; max-age=5184000; includeSubDomains' always;</pre>
+    Header always set Public-Key-Pins "pin-sha256=\"base64+primary==\"; pin-sha256=\"base64+backup==\"; max-age=5184000; includeSubDomains"
 
-<h4 id="Lighttpd">Lighttpd</h4>
+#### Nginx
 
-<p>The following line with your relevant key information (pin-sha256="..." fields) will enable HPKP on lighttpd.</p>
+Adding the following line and inserting the appropriate `pin-sha256="..."` values will enable HPKP on your nginx. This requires the `ngx_http_headers_module.`
 
-<pre>setenv.add-response-header  = ( "Public-Key-Pins" =&gt; "pin-sha256=\"base64+primary==\"; pin-sha256=\"base64+backup==\"; max-age=5184000; includeSubDomains")</pre>
+    add_header Public-Key-Pins 'pin-sha256="base64+primary=="; pin-sha256="base64+backup=="; max-age=5184000; includeSubDomains' always;
 
-<p><strong>Note:</strong> This requires the <code>mod_setenv</code> server.module loaded which can be included by the following if not already loaded.</p>
+#### Lighttpd
 
-<pre>server.modules += ( "mod_setenv" )</pre>
+The following line with your relevant key information (pin-sha256="..." fields) will enable HPKP on lighttpd.
 
-<h4 id="IIS">IIS</h4>
+    setenv.add-response-header  = ( "Public-Key-Pins" => "pin-sha256=\"base64+primary==\"; pin-sha256=\"base64+backup==\"; max-age=5184000; includeSubDomains")
 
-<p>Add the following line to the Web.config file to send the <code>Public-Key-Pins</code> header:</p>
+**Note:** This requires the `mod_setenv` server.module loaded which can be included by the following if not already loaded.
 
-<pre>&lt;system.webServer&gt;
-  ...
+    server.modules += ( "mod_setenv" )
 
-  &lt;httpProtocol&gt;
-    &lt;customHeaders&gt;
-      &lt;add name="Public-Key-Pins" value="pin-sha256=&amp;quot;base64+primary==&amp;quot;; pin-sha256=&amp;quot;base64+backup==&amp;quot;; max-age=5184000; includeSubDomains" /&gt;
-    &lt;/customHeaders&gt;
-  &lt;/httpProtocol&gt;
+#### IIS
 
-  ...
-&lt;/system.webServer&gt;
-</pre>
+Add the following line to the Web.config file to send the `Public-Key-Pins` header:
 
-<h2 id="Specifications">Specifications</h2>
+    <system.webServer>
+      ...
 
-<table class="standard-table">
- <thead>
-  <tr>
-   <th scope="col">Specification</th>
-   <th scope="col">Title</th>
-  </tr>
- </thead>
- <tbody>
-  <tr>
-   <td>{{RFC("7469", "Public-Key-Pins", "2.1")}}</td>
-   <td>Public Key Pinning Extension for HTTP</td>
-  </tr>
- </tbody>
-</table>
+      <httpProtocol>
+        <customHeaders>
+          <add name="Public-Key-Pins" value="pin-sha256=&quot;base64+primary==&quot;; pin-sha256=&quot;base64+backup==&quot;; max-age=5184000; includeSubDomains" />
+        </customHeaders>
+      </httpProtocol>
 
-<h2 id="Browser_compatibility">Browser compatibility</h2>
+      ...
+    </system.webServer>
 
-<p>{{Compat("http.headers.Public-Key-Pins")}}</p>
+## Specifications
 
-<h2 id="See_also">See also</h2>
+| Specification                                            | Title                                 |
+| -------------------------------------------------------- | ------------------------------------- |
+| {{RFC("7469", "Public-Key-Pins", "2.1")}} | Public Key Pinning Extension for HTTP |
 
-<ul>
- <li>{{HTTPHeader("Public-Key-Pins")}}</li>
- <li>{{HTTPHeader("Public-Key-Pins-Report-Only")}}</li>
- <li>Browser test site: <a href="https://projects.dm.id.lv/Public-Key-Pins_test">HSTS and HPKP test</a></li>
- <li>{{HTTPHeader("Expect-CT")}}</li>
-</ul>
+## Browser compatibility
+
+{{Compat("http.headers.Public-Key-Pins")}}
+
+## See also
+
+- {{HTTPHeader("Public-Key-Pins")}}
+- {{HTTPHeader("Public-Key-Pins-Report-Only")}}
+- Browser test site: [HSTS and HPKP test](https://projects.dm.id.lv/Public-Key-Pins_test)
+- {{HTTPHeader("Expect-CT")}}
diff --git a/files/en-us/web/http/range_requests/index.md b/files/en-us/web/http/range_requests/index.md
index ef17d43ae195535..34accaa3db68caf 100644
--- a/files/en-us/web/http/range_requests/index.md
+++ b/files/en-us/web/http/range_requests/index.md
@@ -6,113 +6,106 @@ tags:
   - HTTP
   - HTTP range requests
 ---
-<div>{{HTTPSidebar}}</div>
+{{HTTPSidebar}}
 
-<p class="summary">HTTP range requests allow to send only a portion of an HTTP message from a server to a client. Partial requests are useful for large media or downloading files with pause and resume functions, for example.</p>
+HTTP range requests allow to send only a portion of an HTTP message from a server to a client. Partial requests are useful for large media or downloading files with pause and resume functions, for example.
 
-<h2 id="Checking_if_a_server_supports_partial_requests">Checking if a server supports partial requests</h2>
+## Checking if a server supports partial requests
 
-<p>If the {{HTTPHeader("Accept-Ranges")}} is present in HTTP responses (and its value isn't "<code>none</code>"), the server supports range requests. You can check this by issuing a {{HTTPMethod("HEAD")}} request with cURL, for example.</p>
+If the {{HTTPHeader("Accept-Ranges")}} is present in HTTP responses (and its value isn't "`none`"), the server supports range requests. You can check this by issuing a {{HTTPMethod("HEAD")}} request with cURL, for example.
 
-<pre>curl -I http://i.imgur.com/z4d4kWk.jpg
+    curl -I http://i.imgur.com/z4d4kWk.jpg
 
-HTTP/1.1 200 OK
-...
-Accept-Ranges: bytes
-Content-Length: 146515
-</pre>
+    HTTP/1.1 200 OK
+    ...
+    Accept-Ranges: bytes
+    Content-Length: 146515
 
-<p>In this response, <code>Accept-Ranges: bytes</code> indicates that bytes can be used as unit to define a range. Here the {{HTTPHeader("Content-Length")}} header is also useful as it indicates the full size of the image to retrieve.</p>
+In this response, `Accept-Ranges: bytes` indicates that bytes can be used as unit to define a range. Here the {{HTTPHeader("Content-Length")}} header is also useful as it indicates the full size of the image to retrieve.
 
-<p>If sites omit the <code>Accept-Ranges</code> header, they likely don't support partial requests. Some sites also explicitly send "<code>none</code>" as a value, indicating no support. In some apps, download managers disable their pause buttons in that case.</p>
+If sites omit the `Accept-Ranges` header, they likely don't support partial requests. Some sites also explicitly send "`none`" as a value, indicating no support. In some apps, download managers disable their pause buttons in that case.
 
-<pre>curl -I https://www.youtube.com/watch?v=EwTZ2xpQwpA
+    curl -I https://www.youtube.com/watch?v=EwTZ2xpQwpA
 
-HTTP/1.1 200 OK
-...
-Accept-Ranges: none
-</pre>
+    HTTP/1.1 200 OK
+    ...
+    Accept-Ranges: none
 
-<h2 id="Requesting_a_specific_range_from_a_server">Requesting a specific range from a server</h2>
+## Requesting a specific range from a server
 
-<p>If the server supports range requests, you can issue such a request by using the {{HTTPHeader("Range")}} header. It indicates the part(s) of a document that the server should return.</p>
+If the server supports range requests, you can issue such a request by using the {{HTTPHeader("Range")}} header. It indicates the part(s) of a document that the server should return.
 
-<h3 id="Single_part_ranges">Single part ranges</h3>
+### Single part ranges
 
-<p>We can request a single range from a resource. Again, we can test a request by using cURL. The "<code>-H</code>" option will append a header line to the request, which in this case is the <code>Range</code> header requesting the first 1024 bytes.</p>
+We can request a single range from a resource. Again, we can test a request by using cURL. The "`-H`" option will append a header line to the request, which in this case is the `Range` header requesting the first 1024 bytes.
 
-<pre>curl http://i.imgur.com/z4d4kWk.jpg -i -H "Range: bytes=0-1023"</pre>
+    curl http://i.imgur.com/z4d4kWk.jpg -i -H "Range: bytes=0-1023"
 
-<p>The issued request looks like this:</p>
+The issued request looks like this:
 
-<pre>GET /z4d4kWk.jpg HTTP/1.1
-Host: i.imgur.com
-Range: bytes=0-1023</pre>
+    GET /z4d4kWk.jpg HTTP/1.1
+    Host: i.imgur.com
+    Range: bytes=0-1023
 
-<p>The server responses with the {{HTTPStatus("206")}} <code>Partial Content</code> status:</p>
+The server responses with the {{HTTPStatus("206")}} `Partial Content` status:
 
-<pre>HTTP/1.1 206 Partial Content
-Content-Range: bytes 0-1023/146515
-Content-Length: 1024
-...
-(binary content)
-</pre>
+    HTTP/1.1 206 Partial Content
+    Content-Range: bytes 0-1023/146515
+    Content-Length: 1024
+    ...
+    (binary content)
 
-<p>The {{HTTPHeader("Content-Length")}} header now indicates the size of the requested range (and not the full size of the image). The {{HTTPHeader("Content-Range")}} response header indicates where in the full resource this partial message belongs.</p>
+The {{HTTPHeader("Content-Length")}} header now indicates the size of the requested range (and not the full size of the image). The {{HTTPHeader("Content-Range")}} response header indicates where in the full resource this partial message belongs.
 
-<h3 id="Multipart_ranges">Multipart ranges</h3>
+### Multipart ranges
 
-<p>The {{HTTPHeader("Range")}} header also allows you to get multiple ranges at once in a multipart document. The ranges are separated by a comma.</p>
+The {{HTTPHeader("Range")}} header also allows you to get multiple ranges at once in a multipart document. The ranges are separated by a comma.
 
-<pre>curl http://www.example.com -i -H "Range: bytes=0-50, 100-150"</pre>
+    curl http://www.example.com -i -H "Range: bytes=0-50, 100-150"
 
-<p>The server responses with the {{HTTPStatus("206")}} <code>Partial Content</code> status and a {{HTTPHeader("Content-Type")}}<code>: multipart/byteranges; boundary=3d6b6a416f9b5</code> header, indicating that a multipart byterange follows. Each part contains its own <code>Content-Type</code> and <code>Content-Range</code> fields and the required boundary parameter specifies the boundary string used to separate each body-part.</p>
+The server responses with the {{HTTPStatus("206")}} `Partial Content` status and a {{HTTPHeader("Content-Type")}}`: multipart/byteranges; boundary=3d6b6a416f9b5` header, indicating that a multipart byterange follows. Each part contains its own `Content-Type` and `Content-Range` fields and the required boundary parameter specifies the boundary string used to separate each body-part.
 
-<pre>HTTP/1.1 206 Partial Content
-Content-Type: multipart/byteranges; boundary=3d6b6a416f9b5
-Content-Length: 282
+    HTTP/1.1 206 Partial Content
+    Content-Type: multipart/byteranges; boundary=3d6b6a416f9b5
+    Content-Length: 282
 
---3d6b6a416f9b5
-Content-Type: text/html
-Content-Range: bytes 0-50/1270
+    --3d6b6a416f9b5
+    Content-Type: text/html
+    Content-Range: bytes 0-50/1270
 
-&lt;!doctype html&gt;
-&lt;html&gt;
-&lt;head&gt;
-    &lt;title&gt;Example Do
---3d6b6a416f9b5
-Content-Type: text/html
-Content-Range: bytes 100-150/1270
+    <!doctype html>
+    <html>
+    <head>
+        <title>Example Do
+    --3d6b6a416f9b5
+    Content-Type: text/html
+    Content-Range: bytes 100-150/1270
 
-eta http-equiv="Content-type" content="text/html; c
---3d6b6a416f9b5--</pre>
+    eta http-equiv="Content-type" content="text/html; c
+    --3d6b6a416f9b5--
 
-<h3 id="Conditional_range_requests">Conditional range requests</h3>
+### Conditional range requests
 
-<p>When resuming to request more parts of a resource, you need to guarantee that the stored resource has not been modified since the last fragment has been received.</p>
+When resuming to request more parts of a resource, you need to guarantee that the stored resource has not been modified since the last fragment has been received.
 
-<p>The {{HTTPHeader("If-Range")}} HTTP request header makes a range request conditional: if the condition is fulfilled, the range request will be issued and the server sends back a {{HTTPStatus("206")}} <code>Partial Content</code> answer with the appropriate body. If the condition is not fulfilled, the full resource is sent back, with a {{HTTPStatus("200")}} <code>OK</code> status. This header can be used either with a {{HTTPHeader("Last-Modified")}} validator, or with an {{HTTPHeader("ETag")}}, but not with both.</p>
+The {{HTTPHeader("If-Range")}} HTTP request header makes a range request conditional: if the condition is fulfilled, the range request will be issued and the server sends back a {{HTTPStatus("206")}} `Partial Content` answer with the appropriate body. If the condition is not fulfilled, the full resource is sent back, with a {{HTTPStatus("200")}} `OK` status. This header can be used either with a {{HTTPHeader("Last-Modified")}} validator, or with an {{HTTPHeader("ETag")}}, but not with both.
 
-<pre>If-Range: Wed, 21 Oct 2015 07:28:00 GMT </pre>
+    If-Range: Wed, 21 Oct 2015 07:28:00 GMT
 
-<h2 id="Partial_request_responses">Partial request responses</h2>
+## Partial request responses
 
-<p>There are three relevant statuses, when working with range requests:</p>
+There are three relevant statuses, when working with range requests:
 
-<ul>
-	<li>In case of a successful range request, the {{HTTPStatus("206")}} <code>Partial Content</code> status is sent back from a server.</li>
-	<li>In case of a range request that is out of bounds (none of the range values overlap the extent of the resource, i.e first-byte-pos of all ranges is greater than the resource length), the server responds with a {{HTTPStatus("416")}} <code>Requested Range Not Satisfiable</code> status.</li>
-	<li>In case of no support of range requests, the {{HTTPStatus("200")}} <code>OK</code> status is sent back from a server.</li>
-</ul>
+- In case of a successful range request, the {{HTTPStatus("206")}} `Partial Content` status is sent back from a server.
+- In case of a range request that is out of bounds (none of the range values overlap the extent of the resource, i.e first-byte-pos of all ranges is greater than the resource length), the server responds with a {{HTTPStatus("416")}} `Requested Range Not Satisfiable` status.
+- In case of no support of range requests, the {{HTTPStatus("200")}} `OK` status is sent back from a server.
 
-<h2 id="Comparison_to_chunked_Transfer-Encoding">Comparison to chunked <code>Transfer-Encoding</code></h2>
+## Comparison to chunked `Transfer-Encoding`
 
-<p>The {{HTTPHeader("Transfer-Encoding")}} header allows chunked encoding, which is useful when larger amounts of data are sent to the client and the total size of the response is not known until the request has been fully processed. The server sends data to the client straight away without buffering the response or determining the exact length, which leads to improved latency. Range requests and chunking are compatible and can be used with or without each other.</p>
+The {{HTTPHeader("Transfer-Encoding")}} header allows chunked encoding, which is useful when larger amounts of data are sent to the client and the total size of the response is not known until the request has been fully processed. The server sends data to the client straight away without buffering the response or determining the exact length, which leads to improved latency. Range requests and chunking are compatible and can be used with or without each other.
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
-	<li>Related status codes {{HTTPStatus("200")}}, {{HTTPStatus("206")}}, {{HTTPStatus("416")}}.</li>
-	<li>Related headers: {{HTTPHeader("Accept-Ranges")}}, {{HTTPHeader("Range")}}, {{HTTPHeader("Content-Range")}}, {{HTTPHeader("If-Range")}}, {{HTTPHeader("Transfer-Encoding")}}.</li>
-	<li><a href="https://blogs.msdn.microsoft.com/ieinternals/2011/06/03/download-resumption-in-internet-explorer/">Download resumption in Internet Explorer</a></li>
-</ul>
+- Related status codes {{HTTPStatus("200")}}, {{HTTPStatus("206")}}, {{HTTPStatus("416")}}.
+- Related headers: {{HTTPHeader("Accept-Ranges")}}, {{HTTPHeader("Range")}}, {{HTTPHeader("Content-Range")}}, {{HTTPHeader("If-Range")}}, {{HTTPHeader("Transfer-Encoding")}}.
+- [Download resumption in Internet Explorer](https://blogs.msdn.microsoft.com/ieinternals/2011/06/03/download-resumption-in-internet-explorer/)
diff --git a/files/en-us/web/http/redirections/index.md b/files/en-us/web/http/redirections/index.md
index a5515dfd51dadd2..3fcd95c5ade2fc1 100644
--- a/files/en-us/web/http/redirections/index.md
+++ b/files/en-us/web/http/redirections/index.md
@@ -6,282 +6,201 @@ tags:
   - HTTP
   - redirects
 ---
-<div>{{HTTPSidebar}}</div>
-
-<p class="summary"><strong>URL redirection</strong>, also known as <em>URL forwarding</em>, is a technique to give more than one URL address to a page, a form, or a whole Web site/application. HTTP has a special kind of response, called a <strong><em>HTTP redirect</em></strong>, for this operation.</p>
-
-<p>Redirects accomplish numerous goals:</p>
-
-<ul>
- <li>Temporary redirects during site maintenance or downtime</li>
- <li>Permanent redirects to preserve existing links/bookmarks after changing the site's URLs, progress pages when uploading a file, etc.</li>
-</ul>
-
-<h2 id="Principle">Principle</h2>
-
-<p>In HTTP, redirection is triggered by a server sending a special <em>redirect</em> response to a request. Redirect responses have <a href="/en-US/docs/Web/HTTP/Status">status codes</a> that start with <code>3</code>, and a {{ httpheader("Location") }} header holding the URL to redirect to.</p>
-
-<p>When browsers receive a redirect, they immediately load the new URL provided in the <code>Location</code> header. Besides the small performance hit of an additional round-trip, users rarely notice the redirection.</p>
-
-<p><img alt="" src="httpredirect.png"></p>
-
-<p>There are several types of redirects, sorted into three categories:</p>
-
-<ol>
- <li><a href="#permanent_redirections">Permanent redirections</a></li>
- <li><a href="#temporary_redirections">Temporary redirections</a></li>
- <li><a href="#special_redirections">Special redirections</a></li>
-</ol>
-
-<h3 id="Permanent_redirections">Permanent redirections</h3>
-
-<p>These redirections are meant to last forever. They imply that the original URL should no longer be used, and replaced with the new one.Search engine robots, RSS readers, and other crawlers will update the original URL for the resource.</p>
-
-<table>
- <thead>
-  <tr>
-   <th>Code</th>
-   <th>Text</th>
-   <th>Method handling</th>
-   <th>Typical use case</th>
-  </tr>
- </thead>
- <tbody>
-  <tr>
-   <td><code>301</code></td>
-   <td><code>Moved Permanently</code></td>
-   <td>{{HTTPMethod("GET")}} methods unchanged.<br>
-    Others may or may not be changed to {{HTTPMethod("GET")}}. [1]</td>
-   <td>Reorganization of a Web site.</td>
-  </tr>
-  <tr>
-   <td><code>308</code></td>
-   <td><code>Permanent Redirect</code></td>
-   <td>Method and body not changed.</td>
-   <td>Reorganization of a Web site, with non-GET links/operations.</td>
-  </tr>
- </tbody>
-</table>
-
-<p>[1] The specification did not intend to allow method changes, but there are existing user agents that do change their method. {{HTTPStatus("308")}} was created to remove the ambiguity of the behavior when using non-<code>GET</code> methods.</p>
-
-<h3 id="Temporary_redirections">Temporary redirections</h3>
-
-<p>Sometimes the requested resource can't be accessed from its canonical location, but it can be accessed from another place. In this case, a temporary redirect can be used.</p>
-
-<p>Search engine robots and other crawlers don't memorize the new, temporary URL. Temporary redirections are also used when creating, updating, or deleting resources, to show temporary progress pages.</p>
-
-<table>
- <thead>
-  <tr>
-   <th>Code</th>
-   <th>Text</th>
-   <th>Method handling</th>
-   <th>Typical use case</th>
-  </tr>
- </thead>
- <tbody>
-  <tr>
-   <td><code>302</code></td>
-   <td><code>Found</code></td>
-   <td>{{HTTPMethod("GET")}} methods unchanged.<br>
-    Others may or may not be changed to {{HTTPMethod("GET")}}. [2]</td>
-   <td>The Web page is temporarily unavailable for unforeseen reasons.</td>
-  </tr>
-  <tr>
-   <td><code>303</code></td>
-   <td><code>See Other</code></td>
-   <td>{{HTTPMethod("GET")}} methods unchanged.<br>
-    Others <em>changed</em> to <code>GET</code> (body lost).</td>
-   <td>Used to redirect after a {{HTTPMethod("PUT")}} or a {{HTTPMethod("POST")}}, so that refreshing the result page doesn't re-trigger the operation.</td>
-  </tr>
-  <tr>
-   <td><code>307</code></td>
-   <td><code>Temporary Redirect</code></td>
-   <td>Method and body not changed</td>
-   <td>The Web page is temporarily unavailable for unforeseen reasons. Better than <code>302</code> when non-<code>GET</code> operations are available on the site.</td>
-  </tr>
- </tbody>
-</table>
-
-<p>[2] The specification did not intend to allow method changes, but there are existing user agents that do change their method. {{HTTPStatus("307")}} was created to remove the ambiguity of the behavior when using non-<code>GET</code> methods.</p>
-
-<h3 id="Special_redirections">Special redirections</h3>
+{{HTTPSidebar}}
 
-<p>{{HTTPStatus("304")}} (Not Modified) redirects a page to the locally cached copy (that was stale), and {{HTTPStatus("300")}} (Multiple Choice) is a manual redirection: the body, presented by the browser as a Web page, lists the possible redirections and the user clicks on one to select it.</p>
+**URL redirection**, also known as _URL forwarding_, is a technique to give more than one URL address to a page, a form, or a whole Web site/application. HTTP has a special kind of response, called a **_HTTP redirect_**, for this operation.
 
-<table>
- <thead>
-  <tr>
-   <th>Code</th>
-   <th>Text</th>
-   <th>Typical use case</th>
-  </tr>
- </thead>
- <tbody>
-  <tr>
-   <td><code>300</code></td>
-   <td><code>Multiple Choice</code></td>
-   <td>Not many: the choices are listed in an HTML page in the body. Machine-readable choices are encouraged to be sent as {{HTTPHeader("Link")}} headers with <code>rel=alternate</code>.</td>
-  </tr>
-  <tr>
-   <td><code>304</code></td>
-   <td><code>Not Modified</code></td>
-   <td>Sent for revalidated conditional requests. Indicates that the cached response is still fresh and can be used.</td>
-  </tr>
- </tbody>
-</table>
+Redirects accomplish numerous goals:
 
-<h2 id="Alternative_way_of_specifying_redirections">Alternative way of specifying redirections</h2>
+- Temporary redirects during site maintenance or downtime
+- Permanent redirects to preserve existing links/bookmarks after changing the site's URLs, progress pages when uploading a file, etc.
 
-<p>HTTP redirects aren't the only way to define redirections. There are two others:</p>
+## Principle
 
-<ol>
- <li>HTML redirections with the {{HTMLElement("meta")}} element</li>
- <li>JavaScript redirections via the <a href="/en-US/docs/Web/API/Document_Object_Model">DOM</a></li>
-</ol>
+In HTTP, redirection is triggered by a server sending a special _redirect_ response to a request. Redirect responses have [status codes](/en-US/docs/Web/HTTP/Status) that start with `3`, and a {{ httpheader("Location") }} header holding the URL to redirect to.
 
-<h3 id="HTML_redirections">HTML redirections</h3>
+When browsers receive a redirect, they immediately load the new URL provided in the `Location` header. Besides the small performance hit of an additional round-trip, users rarely notice the redirection.
 
-<p>HTTP redirects are the best way to create redirections, but sometimes you don't have control over the server. In that case, try a {{HTMLElement("meta")}} element with its {{htmlattrxref("http-equiv", "meta")}} attribute set to <code>Refresh</code> in the {{HTMLElement("head")}} of the page. When displaying the page, the browser will go to the indicated URL.</p>
+![](httpredirect.png)
 
-<pre class="brush: html">&lt;head&gt;
-  &lt;meta http-equiv="Refresh" content="0; URL=https://example.com/"&gt;
-&lt;/head&gt;
-</pre>
+There are several types of redirects, sorted into three categories:
 
-<p>The {{htmlattrxref("content")}} attribute should start with a number indicating how many seconds the browser should wait before redirecting to the given URL. Always set it to <code>0</code> for accessibility compliance.</p>
+1.  [Permanent redirections](#permanent_redirections)
+2.  [Temporary redirections](#temporary_redirections)
+3.  [Special redirections](#special_redirections)
 
-<p>Obviously, this method only works with HTML, and cannot be used for images or other types of content.</p>
+### Permanent redirections
 
-<h3 id="JavaScript_redirections">JavaScript redirections</h3>
+These redirections are meant to last forever. They imply that the original URL should no longer be used, and replaced with the new one.Search engine robots, RSS readers, and other crawlers will update the original URL for the resource.
 
-<p>Redirections in JavaScript are performed by setting a URL string to the {{domxref("window.location")}} property, loading the new page:</p>
+| Code  | Text                 | Method handling                                                                                                       | Typical use case                                             |
+| ----- | -------------------- | --------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------ |
+| `301` | `Moved Permanently`  | {{HTTPMethod("GET")}} methods unchanged. Others may or may not be changed to {{HTTPMethod("GET")}}. [1] | Reorganization of a Web site.                                |
+| `308` | `Permanent Redirect` | Method and body not changed.                                                                                          | Reorganization of a Web site, with non-GET links/operations. |
 
-<pre class="brush: js">window.location = "https://example.com/";</pre>
+\[1] The specification did not intend to allow method changes, but there are existing user agents that do change their method. {{HTTPStatus("308")}} was created to remove the ambiguity of the behavior when using non-`GET` methods.
 
-<p>Like HTML redirections, this can't work on all resources, and obviously, this will only work on clients that execute JavaScript. On the other hand, there are more possibilities: for example, you can trigger the redirect only if some conditions are met.</p>
+### Temporary redirections
 
-<h3 id="Order_of_precedence">Order of precedence</h3>
+Sometimes the requested resource can't be accessed from its canonical location, but it can be accessed from another place. In this case, a temporary redirect can be used.
 
-<p>With three ways to trigger redirections, several ways can be used at the same time. But which is applied first?</p>
+Search engine robots and other crawlers don't memorize the new, temporary URL. Temporary redirections are also used when creating, updating, or deleting resources, to show temporary progress pages.
 
-<ol>
- <li>HTTP redirects always execute first — they exist when there is not even a transmitted page.</li>
- <li>HTML redirects ({{HTMLElement("meta")}}) execute if there weren't any HTTP redirects.</li>
- <li>JavaScript redirects execute last, and only if JavaScript is enabled.</li>
-</ol>
+| Code  | Text                 | Method handling                                                                                                       | Typical use case                                                                                                                                              |
+| ----- | -------------------- | --------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `302` | `Found`              | {{HTTPMethod("GET")}} methods unchanged. Others may or may not be changed to {{HTTPMethod("GET")}}. [2] | The Web page is temporarily unavailable for unforeseen reasons.                                                                                               |
+| `303` | `See Other`          | {{HTTPMethod("GET")}} methods unchanged. Others _changed_ to `GET` (body lost).                                | Used to redirect after a {{HTTPMethod("PUT")}} or a {{HTTPMethod("POST")}}, so that refreshing the result page doesn't re-trigger the operation. |
+| `307` | `Temporary Redirect` | Method and body not changed                                                                                           | The Web page is temporarily unavailable for unforeseen reasons. Better than `302` when non-`GET` operations are available on the site.                        |
 
-<p>When possible, use HTTP redirects and don't add {{HTMLElement("meta")}} element redirects. If someone changes the HTTP redirects but forgets to change the HTML redirects, the redirects will no longer be identical, which could cause an infinite loop or other nightmares.</p>
+\[2] The specification did not intend to allow method changes, but there are existing user agents that do change their method. {{HTTPStatus("307")}} was created to remove the ambiguity of the behavior when using non-`GET` methods.
 
-<h2 id="Use_cases">Use cases</h2>
+### Special redirections
 
-<p>There are numerous use cases for redirects, but as performance is impacted with every redirect, their use should be kept to a minimum.</p>
+{{HTTPStatus("304")}} (Not Modified) redirects a page to the locally cached copy (that was stale), and {{HTTPStatus("300")}} (Multiple Choice) is a manual redirection: the body, presented by the browser as a Web page, lists the possible redirections and the user clicks on one to select it.
 
-<h3 id="Domain_aliasing">Domain aliasing</h3>
+| Code  | Text              | Typical use case                                                                                                                                                               |
+| ----- | ----------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| `300` | `Multiple Choice` | Not many: the choices are listed in an HTML page in the body. Machine-readable choices are encouraged to be sent as {{HTTPHeader("Link")}} headers with `rel=alternate`. |
+| `304` | `Not Modified`    | Sent for revalidated conditional requests. Indicates that the cached response is still fresh and can be used.                                                                  |
 
-<p>Ideally, there is one location, and therefore one URL, for each resource. But there are reasons for alternative names for a resource:</p>
+## Alternative way of specifying redirections
 
-<dl>
- <dt>Expanding the reach of your site</dt>
- <dd>A common case is when a site resides at <code>www.example.com</code>, but accessing it from <code>example.com</code> should also work. Redirections for <code>example.com</code> to <code>www.example.com</code> are thus set up. You might also redirect from common synonyms or frequent typos of your domains.</dd>
- <dt>Moving to a new domain</dt>
- <dd>For example, your company was renamed, but you want existing links or bookmarks to still find you under the new name.</dd>
- <dt>Forcing <a href="/en-US/docs/Glossary/https">HTTPS</a></dt>
- <dd>Requests to the <code>http://</code> version of your site will redirect to the <code>https://</code> version of your site.</dd>
-</dl>
+HTTP redirects aren't the only way to define redirections. There are two others:
 
-<h3 id="Keeping_links_alive">Keeping links alive</h3>
+1.  HTML redirections with the {{HTMLElement("meta")}} element
+2.  JavaScript redirections via the [DOM](/en-US/docs/Web/API/Document_Object_Model)
 
-<p>When you restructure Web sites, URLs change. Even if you update your site's links to match the new URLs, you have no control over the URLs used by external resources.</p>
+### HTML redirections
 
-<p>You don't want to break these links, as they bring valuable users and help your SEO, so you set up redirects from the old URLs to the new ones.</p>
+HTTP redirects are the best way to create redirections, but sometimes you don't have control over the server. In that case, try a {{HTMLElement("meta")}} element with its {{htmlattrxref("http-equiv", "meta")}} attribute set to `Refresh` in the {{HTMLElement("head")}} of the page. When displaying the page, the browser will go to the indicated URL.
 
-<div class="notecard note">
-  <p><strong>Note:</strong> This technique does work for internal links, but try to avoid having internal redirects. A redirect has a significant performance cost (as an extra HTTP request occurs). If you can avoid it by correcting internal links, you should fix those links instead.</p>
-</div>
+```html
+<head>
+  <meta http-equiv="Refresh" content="0; URL=https://example.com/">
+</head>
+```
 
-<h3 id="Temporary_responses_to_unsafe_requests">Temporary responses to unsafe requests</h3>
+The {{htmlattrxref("content")}} attribute should start with a number indicating how many seconds the browser should wait before redirecting to the given URL. Always set it to `0` for accessibility compliance.
 
-<p>{{Glossary("Safe/HTTP", "Unsafe")}} requests modify the state of the server and the user shouldn't resend them unintentionally.</p>
+Obviously, this method only works with HTML, and cannot be used for images or other types of content.
 
-<p>Typically, you don't want your users to resend {{HTTPMethod("PUT")}}, {{HTTPMethod("POST")}} or {{HTTPMethod("DELETE")}} requests. If you serve the response as the result of this request, a simple press of the reload button will resend the request (possibly after a confirmation message).</p>
+### JavaScript redirections
 
-<p>In this case, the server can send back a {{HTTPStatus("303")}} (See Other) response for a URL that will contain the right information. If the reload button is pressed, only that page is redisplayed, without replaying the unsafe requests.</p>
+Redirections in JavaScript are performed by setting a URL string to the {{domxref("window.location")}} property, loading the new page:
 
-<h3 id="Temporary_responses_to_long_requests">Temporary responses to long requests</h3>
+```js
+window.location = "https://example.com/";
+```
 
-<p>Some requests may need more time on the server, like {{HTTPHeader("DELETE")}} requests that are scheduled for later processing. In this case, the response is a {{HTTPStatus("303")}} (See Other) redirect that links to a page indicating that the action has been scheduled, and eventually informs about its progress, or allows to cancel it.</p>
+Like HTML redirections, this can't work on all resources, and obviously, this will only work on clients that execute JavaScript. On the other hand, there are more possibilities: for example, you can trigger the redirect only if some conditions are met.
 
-<h2 id="Configuring_redirects_in_common_servers">Configuring redirects in common servers</h2>
+### Order of precedence
 
-<h3 id="Apache">Apache</h3>
+With three ways to trigger redirections, several ways can be used at the same time. But which is applied first?
 
-<p>Redirects can be set either in the server config file or in the <code>.htaccess</code> of each directory.</p>
+1.  HTTP redirects always execute first — they exist when there is not even a transmitted page.
+2.  HTML redirects ({{HTMLElement("meta")}}) execute if there weren't any HTTP redirects.
+3.  JavaScript redirects execute last, and only if JavaScript is enabled.
 
-<p>The <code><a href="https://httpd.apache.org/docs/current/mod/mod_alias.html">mod_alias</a></code> module has <code>Redirect</code> and <code>RedirectMatch</code> directives that set up {{HTTPStatus("302")}} redirects by default:</p>
+When possible, use HTTP redirects and don't add {{HTMLElement("meta")}} element redirects. If someone changes the HTTP redirects but forgets to change the HTML redirects, the redirects will no longer be identical, which could cause an infinite loop or other nightmares.
 
-<pre>&lt;VirtualHost *:443&gt;
-	ServerName example.com
-	Redirect / https://www.example.com
-&lt;/VirtualHost&gt;
-</pre>
+## Use cases
 
-<p>The URL <code>https://example.com/</code> will be redirected to <code>https://www.example.com/</code>, as will any files or directories under it (<code>https://example.com/some-page</code> will be redirected to <code>https://www.example.com/some-page</code>)</p>
+There are numerous use cases for redirects, but as performance is impacted with every redirect, their use should be kept to a minimum.
 
-<p><code>RedirectMatch</code> does the same, but takes a {{glossary("regular expression")}} to define a collection of affected URLs:</p>
+### Domain aliasing
 
-<pre>RedirectMatch ^/images/(.*)$ https://images.example.com/$1</pre>
+Ideally, there is one location, and therefore one URL, for each resource. But there are reasons for alternative names for a resource:
 
-<p>All documents in the <code>images/</code> directory will redirect to a different domain.</p>
+- Expanding the reach of your site
+  - : A common case is when a site resides at `www.example.com`, but accessing it from `example.com` should also work. Redirections for `example.com` to `www.example.com` are thus set up. You might also redirect from common synonyms or frequent typos of your domains.
+- Moving to a new domain
+  - : For example, your company was renamed, but you want existing links or bookmarks to still find you under the new name.
+- Forcing [HTTPS](/en-US/docs/Glossary/https)
+  - : Requests to the `http://` version of your site will redirect to the `https://` version of your site.
 
-<p>If you don't want a temporary redirect, an extra parameter (either the HTTP status code to use or the <code>permanent</code> keyword) can be used to set up a different redirect:</p>
+### Keeping links alive
 
-<pre>Redirect permanent / https://www.example.com
-# …acts the same as:
-Redirect 301 / https://www.example.com
-</pre>
+When you restructure Web sites, URLs change. Even if you update your site's links to match the new URLs, you have no control over the URLs used by external resources.
 
-<p>The <code><a href="https://httpd.apache.org/docs/current/mod/mod_rewrite.html">mod_rewrite</a></code> module can also create redirects. It is more flexible, but a bit more complex.</p>
+You don't want to break these links, as they bring valuable users and help your SEO, so you set up redirects from the old URLs to the new ones.
 
-<h3 id="Nginx">Nginx</h3>
+> **Note:** This technique does work for internal links, but try to avoid having internal redirects. A redirect has a significant performance cost (as an extra HTTP request occurs). If you can avoid it by correcting internal links, you should fix those links instead.
 
-<p>In Nginx, you create a specific server block for the content you want to redirect:</p>
+### Temporary responses to unsafe requests
 
-<pre>server {
-	listen 80;
-	server_name example.com;
-	return 301 $scheme://www.example.com$request_uri;
-}</pre>
+{{Glossary("Safe/HTTP", "Unsafe")}} requests modify the state of the server and the user shouldn't resend them unintentionally.
 
-<p>To apply a redirect to a directory or only certain pages, use the <code>rewrite</code> directive:</p>
+Typically, you don't want your users to resend {{HTTPMethod("PUT")}}, {{HTTPMethod("POST")}} or {{HTTPMethod("DELETE")}} requests. If you serve the response as the result of this request, a simple press of the reload button will resend the request (possibly after a confirmation message).
 
-<pre>rewrite ^/images/(.*)$ https://images.example.com/$1 redirect;
-rewrite ^/images/(.*)$ https://images.example.com/$1 permanent;
-</pre>
+In this case, the server can send back a {{HTTPStatus("303")}} (See Other) response for a URL that will contain the right information. If the reload button is pressed, only that page is redisplayed, without replaying the unsafe requests.
 
-<h3 id="IIS">IIS</h3>
+### Temporary responses to long requests
 
-<p>In IIS, you use the <code><a href="https://www.iis.net/configreference/system.webserver/httpredirect">&lt;httpRedirect&gt;</a></code> element to configure redirections.</p>
+Some requests may need more time on the server, like {{HTTPHeader("DELETE")}} requests that are scheduled for later processing. In this case, the response is a {{HTTPStatus("303")}} (See Other) redirect that links to a page indicating that the action has been scheduled, and eventually informs about its progress, or allows to cancel it.
 
-<h2 id="Redirection_loops">Redirection loops</h2>
+## Configuring redirects in common servers
 
-<p>Redirection loops happen when additional redirections follow the one that has already been followed. In other words, there is a loop that will never be finished and no page will ever be found.</p>
+### Apache
 
-<p>Most of the time this is a server problem, and if the server can detect it, it will send back a {{HTTPStatus("500")}} <code>Internal Server Error</code>. If you encounter such an error soon after modifying a server configuration, this is likely a redirection loop.</p>
+Redirects can be set either in the server config file or in the `.htaccess` of each directory.
 
-<p>Sometimes, the server won't detect it: a redirection loop can spread over several servers which each don't have the full picture. In this case, browsers will detect it and display an error message. Firefox displays:</p>
+The [`mod_alias`](https://httpd.apache.org/docs/current/mod/mod_alias.html) module has `Redirect` and `RedirectMatch` directives that set up {{HTTPStatus("302")}} redirects by default:
 
-<blockquote>
-<p>Firefox has detected that the server is redirecting the request for this address in a way that will never complete.</p>
-</blockquote>
+    <VirtualHost *:443>
+    	ServerName example.com
+    	Redirect / https://www.example.com
+    </VirtualHost>
 
-<p>…while Chrome displays:</p>
+The URL `https://example.com/` will be redirected to `https://www.example.com/`, as will any files or directories under it (`https://example.com/some-page` will be redirected to `https://www.example.com/some-page`)
 
-<blockquote>
-<p>This Webpage has a redirect loop</p>
-</blockquote>
+`RedirectMatch` does the same, but takes a {{glossary("regular expression")}} to define a collection of affected URLs:
 
-<p>In both cases, the user can't do much (unless a corruption is happening on their side, like a mismatch of cache or cookies).</p>
+    RedirectMatch ^/images/(.*)$ https://images.example.com/$1
 
-<p>It is important to avoid redirection loops, as they completely break the user experience.</p>
+All documents in the `images/` directory will redirect to a different domain.
+
+If you don't want a temporary redirect, an extra parameter (either the HTTP status code to use or the `permanent` keyword) can be used to set up a different redirect:
+
+    Redirect permanent / https://www.example.com
+    # …acts the same as:
+    Redirect 301 / https://www.example.com
+
+The [`mod_rewrite`](https://httpd.apache.org/docs/current/mod/mod_rewrite.html) module can also create redirects. It is more flexible, but a bit more complex.
+
+### Nginx
+
+In Nginx, you create a specific server block for the content you want to redirect:
+
+    server {
+    	listen 80;
+    	server_name example.com;
+    	return 301 $scheme://www.example.com$request_uri;
+    }
+
+To apply a redirect to a directory or only certain pages, use the `rewrite` directive:
+
+    rewrite ^/images/(.*)$ https://images.example.com/$1 redirect;
+    rewrite ^/images/(.*)$ https://images.example.com/$1 permanent;
+
+### IIS
+
+In IIS, you use the [`<httpRedirect>`](https://www.iis.net/configreference/system.webserver/httpredirect) element to configure redirections.
+
+## Redirection loops
+
+Redirection loops happen when additional redirections follow the one that has already been followed. In other words, there is a loop that will never be finished and no page will ever be found.
+
+Most of the time this is a server problem, and if the server can detect it, it will send back a {{HTTPStatus("500")}} `Internal Server Error`. If you encounter such an error soon after modifying a server configuration, this is likely a redirection loop.
+
+Sometimes, the server won't detect it: a redirection loop can spread over several servers which each don't have the full picture. In this case, browsers will detect it and display an error message. Firefox displays:
+
+> Firefox has detected that the server is redirecting the request for this address in a way that will never complete.
+
+…while Chrome displays:
+
+> This Webpage has a redirect loop
+
+In both cases, the user can't do much (unless a corruption is happening on their side, like a mismatch of cache or cookies).
+
+It is important to avoid redirection loops, as they completely break the user experience.
diff --git a/files/en-us/web/http/resources_and_specifications/index.md b/files/en-us/web/http/resources_and_specifications/index.md
index 427dfd8cafe348b..bfa77995ff1c14f 100644
--- a/files/en-us/web/http/resources_and_specifications/index.md
+++ b/files/en-us/web/http/resources_and_specifications/index.md
@@ -5,258 +5,55 @@ tags:
   - Guide
   - HTTP
 ---
-<div>{{HTTPSidebar}}</div>
+{{HTTPSidebar}}
 
-<p>HTTP was first specified in the early 1990s. Designed with extensibility in mind, it has seen numerous additions over the years; this lead to its specification being scattered through numerous specification documents (in the midst of experimental abandoned extensions). This page lists relevant resources about HTTP.</p>
+HTTP was first specified in the early 1990s. Designed with extensibility in mind, it has seen numerous additions over the years; this lead to its specification being scattered through numerous specification documents (in the midst of experimental abandoned extensions). This page lists relevant resources about HTTP.
 
-<table class="standard-table">
- <thead>
-  <tr>
-   <th scope="col">Specification</th>
-   <th scope="col">Title</th>
-   <th scope="col">Status</th>
-  </tr>
- </thead>
- <tbody>
-  <tr>
-   <td>{{rfc(7230)}}</td>
-   <td>Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing</td>
-   <td>Proposed Standard</td>
-  </tr>
-  <tr>
-   <td>{{rfc(7231)}}</td>
-   <td>Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content</td>
-   <td>Proposed Standard</td>
-  </tr>
-  <tr>
-   <td>{{rfc(7232)}}</td>
-   <td>Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests</td>
-   <td>Proposed Standard</td>
-  </tr>
-  <tr>
-   <td>{{rfc(7233)}}</td>
-   <td>Hypertext Transfer Protocol (HTTP/1.1): Range Requests</td>
-   <td>Proposed Standard</td>
-  </tr>
-  <tr>
-   <td>{{rfc(7234)}}</td>
-   <td>Hypertext Transfer Protocol (HTTP/1.1): Caching</td>
-   <td>Proposed Standard</td>
-  </tr>
-  <tr>
-   <td>{{rfc(5861)}}</td>
-   <td>HTTP Cache-Control Extensions for Stale Content</td>
-   <td>Informational</td>
-  </tr>
-  <tr>
-   <td>{{rfc(8246)}}</td>
-   <td>HTTP Immutable Responses</td>
-   <td>Proposed Standard</td>
-  </tr>
-  <tr>
-   <td>{{rfc(7235)}}</td>
-   <td>Hypertext Transfer Protocol (HTTP/1.1): Authentication</td>
-   <td>Proposed Standard</td>
-  </tr>
-  <tr>
-   <td>{{rfc(6265)}}</td>
-   <td>HTTP State Management Mechanism<br>
-    <em>Defines Cookies</em></td>
-   <td>Proposed Standard</td>
-  </tr>
-  <tr>
-   <td><a href="https://datatracker.ietf.org/doc/html/draft-ietf-httpbis-cookie-prefixes-00">Draft spec</a></td>
-   <td>Cookie Prefixes</td>
-   <td>IETF Draft</td>
-  </tr>
-  <tr>
-   <td><a href="https://datatracker.ietf.org/doc/html/draft-ietf-httpbis-cookie-same-site-00">Draft spec</a></td>
-   <td>Same-Site Cookies</td>
-   <td>IETF Draft</td>
-  </tr>
-  <tr>
-   <td><a href="https://datatracker.ietf.org/doc/html/draft-ietf-httpbis-cookie-alone-01">Draft spec</a></td>
-   <td>Deprecate modification of 'secure' cookies from non-secure origins</td>
-   <td>IETF Draft</td>
-  </tr>
-  <tr>
-   <td>{{rfc(2145)}}</td>
-   <td>Use and Interpretation of HTTP Version Numbers</td>
-   <td>Informational</td>
-  </tr>
-  <tr>
-   <td>{{rfc(6585)}}</td>
-   <td>Additional HTTP Status Codes</td>
-   <td>Proposed Standard</td>
-  </tr>
-  <tr>
-   <td>{{rfc(7538)}}</td>
-   <td>The Hypertext Transfer Protocol Status Code 308 (Permanent Redirect)</td>
-   <td>Proposed Standard</td>
-  </tr>
-  <tr>
-   <td>{{rfc(7725)}}</td>
-   <td>An HTTP Status Code to Report Legal Obstacles</td>
-   <td>On the standard track</td>
-  </tr>
-  <tr>
-   <td>{{rfc(2397)}}</td>
-   <td>The "data" URL scheme</td>
-   <td>Proposed Standard</td>
-  </tr>
-  <tr>
-   <td>{{rfc(3986)}}</td>
-   <td>Uniform Resource Identifier (URI): Generic Syntax</td>
-   <td>Internet Standard</td>
-  </tr>
-  <tr>
-   <td>{{rfc(5988)}}</td>
-   <td>Web Linking<br>
-    <em>Defines the {{HTTPHeader("Link")}} header</em></td>
-   <td>Proposed Standard</td>
-  </tr>
-  <tr>
-   <td><a href="https://tools.ietf.org/id/draft-thomson-hybi-http-timeout-01.html">Experimental spec</a></td>
-   <td>Hypertext Transfer Protocol (HTTP) Keep-Alive Header</td>
-   <td>Informational (Expired)</td>
-  </tr>
-  <tr>
-   <td><a href="http://httpwg.org/http-extensions/client-hints.html">Draft spec</a></td>
-   <td>HTTP Client Hints</td>
-   <td>IETF Draft</td>
-  </tr>
-  <tr>
-   <td>{{rfc(7578)}}</td>
-   <td>Returning Values from Forms: multipart/form-data</td>
-   <td>Proposed Standard</td>
-  </tr>
-  <tr>
-   <td>{{rfc(6266)}}</td>
-   <td>Use of the Content-Disposition Header Field in the Hypertext Transfer Protocol (HTTP)</td>
-   <td>Proposed Standard</td>
-  </tr>
-  <tr>
-   <td>{{rfc(2183)}}</td>
-   <td>Communicating Presentation Information in Internet Messages: The Content-Disposition Header Field<br>
-    <em>Only a subset of syntax of the {{HTTPHeader("Content-Disposition")}} header can be used in the context of HTTP messages.</em></td>
-   <td>Proposed Standard</td>
-  </tr>
-  <tr>
-   <td>{{rfc(7239)}}</td>
-   <td>Forwarded HTTP Extension</td>
-   <td>Proposed Standard</td>
-  </tr>
-  <tr>
-   <td>{{rfc(6455)}}</td>
-   <td>The WebSocket Protocol</td>
-   <td>Proposed Standard</td>
-  </tr>
-  <tr>
-   <td>{{rfc(5246)}}</td>
-   <td>The Transport Layer Security (TLS) Protocol Version 1.2<br>
-    <em>This specification has been modified by subsequent RFCs, but these modifications have no effect on the HTTP protocol.</em></td>
-   <td>Proposed Standard</td>
-  </tr>
-  <tr>
-   <td>{{rfc(8446)}}</td>
-   <td>The Transport Layer Security (TLS) Protocol Version 1.3<br>
-    <em>Supersedes TLS 1.2.</em></td>
-   <td>Proposed Standard</td>
-  </tr>
-  <tr>
-   <td>{{rfc(2817)}}</td>
-   <td>Upgrading to TLS Within HTTP/1.1</td>
-   <td>Proposed Standard</td>
-  </tr>
-  <tr>
-   <td>{{rfc(7540)}}</td>
-   <td>Hypertext Transfer Protocol Version 2 (HTTP/2)</td>
-   <td>Proposed Standard</td>
-  </tr>
-  <tr>
-   <td>{{rfc(7541)}}</td>
-   <td>HPACK: Header Compression for HTTP/2</td>
-   <td>On the standard track</td>
-  </tr>
-  <tr>
-   <td>{{rfc(7838)}}</td>
-   <td>HTTP Alternative Services</td>
-   <td>On the standard track</td>
-  </tr>
-  <tr>
-   <td>{{rfc(7301)}}</td>
-   <td>Transport Layer Security (TLS) Application-Layer Protocol Negotiation Extension<br>
-    <em>Used to negotiate HTTP/2 at the transport to save an extra request/response round trip.</em></td>
-   <td>Proposed Standard</td>
-  </tr>
-  <tr>
-   <td>{{rfc(6454)}}</td>
-   <td>The Web Origin Concept</td>
-   <td>Proposed Standard</td>
-  </tr>
-  <tr>
-   <td>{{SpecName('Fetch', '#cors-protocol', 'CORS')}}</td>
-   <td>Cross-Origin Resource Sharing</td>
-   <td>{{Spec2("Fetch")}}</td>
-  </tr>
-  <tr>
-   <td>{{rfc(7034)}}</td>
-   <td>HTTP Header Field X-Frame-Options</td>
-   <td>Informational</td>
-  </tr>
-  <tr>
-   <td>{{rfc(6797)}}</td>
-   <td>HTTP Strict Transport Security (HSTS)</td>
-   <td>Proposed Standard</td>
-  </tr>
-  <tr>
-   <td>{{SpecName("Upgrade Insecure Requests")}}</td>
-   <td>Upgrade Insecure Requests</td>
-   <td>{{Spec2("Upgrade Insecure Requests")}}</td>
-  </tr>
-  <tr>
-   <td>{{SpecName("CSP 1.0")}}</td>
-   <td>Content Security Policy 1.0<br>
-    <em>CSP 1.1 and CSP 3.0 doesn't extend the HTTP standard</em></td>
-   <td>{{Spec2("CSP 1.0")}}</td>
-  </tr>
-  <tr>
-   <td><a href="https://msdn.microsoft.com/en-us/library/jj676915(v=vs.85).aspx">Microsoft document</a></td>
-   <td>Specifying legacy document modes*<br>
-    <em>Defines X-UA-Compatible</em></td>
-   <td>Note</td>
-  </tr>
-  <tr>
-   <td>{{rfc(5689)}}</td>
-   <td>HTTP Extensions for Web Distributed Authoring and Versioning (WebDAV)<br>
-    <em>These extensions of the Web, as well as CardDAV and CalDAV, are out-of-scope for HTTP on the Web. Modern APIs for application are defines using the RESTful pattern nowadays.</em></td>
-   <td>Proposed Standard</td>
-  </tr>
-  <tr>
-   <td>{{rfc(2324)}}</td>
-   <td>Hyper Text Coffee Pot Control Protocol (HTCPCP/1.0)</td>
-   <td>April 1st joke spec</td>
-  </tr>
-  <tr>
-   <td>{{rfc(7168)}}</td>
-   <td>The Hyper Text Coffee Pot Control Protocol for Tea Efflux Appliances (HTCPCP-TEA)</td>
-   <td>April 1st joke spec</td>
-  </tr>
-  <tr>
-   <td>{{SpecName("HTML WHATWG")}}</td>
-   <td>HTML<br>
-    <em>Defines extensions of HTTP for Server-Sent Events</em></td>
-   <td>{{Spec2("HTML WHATWG")}}</td>
-  </tr>
-  <tr>
-   <td><a href="https://wicg.github.io/reporting/">Reporting API</a></td>
-   <td><code>Report-To</code> header</td>
-   <td>Draft</td>
-  </tr>
-  <tr>
-   <td><a href="https://datatracker.ietf.org/doc/html/draft-ietf-httpbis-expect-ct-01">Draft spec</a></td>
-   <td>Expect-CT Extension for HTTP</td>
-   <td>IETF Draft</td>
-  </tr>
- </tbody>
-</table>
+| Specification                                                                              | Title                                                                                                                                                                                                                                                 | Status                                               |
+| ------------------------------------------------------------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------- |
+| {{rfc(7230)}}                                                                           | Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing                                                                                                                                                                                    | Proposed Standard                                    |
+| {{rfc(7231)}}                                                                           | Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content                                                                                                                                                                                         | Proposed Standard                                    |
+| {{rfc(7232)}}                                                                           | Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests                                                                                                                                                                                          | Proposed Standard                                    |
+| {{rfc(7233)}}                                                                           | Hypertext Transfer Protocol (HTTP/1.1): Range Requests                                                                                                                                                                                                | Proposed Standard                                    |
+| {{rfc(7234)}}                                                                           | Hypertext Transfer Protocol (HTTP/1.1): Caching                                                                                                                                                                                                       | Proposed Standard                                    |
+| {{rfc(5861)}}                                                                           | HTTP Cache-Control Extensions for Stale Content                                                                                                                                                                                                       | Informational                                        |
+| {{rfc(8246)}}                                                                           | HTTP Immutable Responses                                                                                                                                                                                                                              | Proposed Standard                                    |
+| {{rfc(7235)}}                                                                           | Hypertext Transfer Protocol (HTTP/1.1): Authentication                                                                                                                                                                                                | Proposed Standard                                    |
+| {{rfc(6265)}}                                                                           | HTTP State Management Mechanism _Defines Cookies_                                                                                                                                                                                                     | Proposed Standard                                    |
+| [Draft spec](https://datatracker.ietf.org/doc/html/draft-ietf-httpbis-cookie-prefixes-00)  | Cookie Prefixes                                                                                                                                                                                                                                       | IETF Draft                                           |
+| [Draft spec](https://datatracker.ietf.org/doc/html/draft-ietf-httpbis-cookie-same-site-00) | Same-Site Cookies                                                                                                                                                                                                                                     | IETF Draft                                           |
+| [Draft spec](https://datatracker.ietf.org/doc/html/draft-ietf-httpbis-cookie-alone-01)     | Deprecate modification of 'secure' cookies from non-secure origins                                                                                                                                                                                    | IETF Draft                                           |
+| {{rfc(2145)}}                                                                           | Use and Interpretation of HTTP Version Numbers                                                                                                                                                                                                        | Informational                                        |
+| {{rfc(6585)}}                                                                           | Additional HTTP Status Codes                                                                                                                                                                                                                          | Proposed Standard                                    |
+| {{rfc(7538)}}                                                                           | The Hypertext Transfer Protocol Status Code 308 (Permanent Redirect)                                                                                                                                                                                  | Proposed Standard                                    |
+| {{rfc(7725)}}                                                                           | An HTTP Status Code to Report Legal Obstacles                                                                                                                                                                                                         | On the standard track                                |
+| {{rfc(2397)}}                                                                           | The "data" URL scheme                                                                                                                                                                                                                                 | Proposed Standard                                    |
+| {{rfc(3986)}}                                                                           | Uniform Resource Identifier (URI): Generic Syntax                                                                                                                                                                                                     | Internet Standard                                    |
+| {{rfc(5988)}}                                                                           | Web Linking _Defines the {{HTTPHeader("Link")}} header_                                                                                                                                                                                         | Proposed Standard                                    |
+| [Experimental spec](https://tools.ietf.org/id/draft-thomson-hybi-http-timeout-01.html)     | Hypertext Transfer Protocol (HTTP) Keep-Alive Header                                                                                                                                                                                                  | Informational (Expired)                              |
+| [Draft spec](http://httpwg.org/http-extensions/client-hints.html)                          | HTTP Client Hints                                                                                                                                                                                                                                     | IETF Draft                                           |
+| {{rfc(7578)}}                                                                           | Returning Values from Forms: multipart/form-data                                                                                                                                                                                                      | Proposed Standard                                    |
+| {{rfc(6266)}}                                                                           | Use of the Content-Disposition Header Field in the Hypertext Transfer Protocol (HTTP)                                                                                                                                                                 | Proposed Standard                                    |
+| {{rfc(2183)}}                                                                           | Communicating Presentation Information in Internet Messages: The Content-Disposition Header Field _Only a subset of syntax of the {{HTTPHeader("Content-Disposition")}} header can be used in the context of HTTP messages._               | Proposed Standard                                    |
+| {{rfc(7239)}}                                                                           | Forwarded HTTP Extension                                                                                                                                                                                                                              | Proposed Standard                                    |
+| {{rfc(6455)}}                                                                           | The WebSocket Protocol                                                                                                                                                                                                                                | Proposed Standard                                    |
+| {{rfc(5246)}}                                                                           | The Transport Layer Security (TLS) Protocol Version 1.2 _This specification has been modified by subsequent RFCs, but these modifications have no effect on the HTTP protocol._                                                                       | Proposed Standard                                    |
+| {{rfc(8446)}}                                                                           | The Transport Layer Security (TLS) Protocol Version 1.3 _Supersedes TLS 1.2._                                                                                                                                                                         | Proposed Standard                                    |
+| {{rfc(2817)}}                                                                           | Upgrading to TLS Within HTTP/1.1                                                                                                                                                                                                                      | Proposed Standard                                    |
+| {{rfc(7540)}}                                                                           | Hypertext Transfer Protocol Version 2 (HTTP/2)                                                                                                                                                                                                        | Proposed Standard                                    |
+| {{rfc(7541)}}                                                                           | HPACK: Header Compression for HTTP/2                                                                                                                                                                                                                  | On the standard track                                |
+| {{rfc(7838)}}                                                                           | HTTP Alternative Services                                                                                                                                                                                                                             | On the standard track                                |
+| {{rfc(7301)}}                                                                           | Transport Layer Security (TLS) Application-Layer Protocol Negotiation Extension _Used to negotiate HTTP/2 at the transport to save an extra request/response round trip._                                                                             | Proposed Standard                                    |
+| {{rfc(6454)}}                                                                           | The Web Origin Concept                                                                                                                                                                                                                                | Proposed Standard                                    |
+| {{SpecName('Fetch', '#cors-protocol', 'CORS')}}                           | Cross-Origin Resource Sharing                                                                                                                                                                                                                         | {{Spec2("Fetch")}}                             |
+| {{rfc(7034)}}                                                                           | HTTP Header Field X-Frame-Options                                                                                                                                                                                                                     | Informational                                        |
+| {{rfc(6797)}}                                                                           | HTTP Strict Transport Security (HSTS)                                                                                                                                                                                                                 | Proposed Standard                                    |
+| {{SpecName("Upgrade Insecure Requests")}}                                   | Upgrade Insecure Requests                                                                                                                                                                                                                             | {{Spec2("Upgrade Insecure Requests")}} |
+| {{SpecName("CSP 1.0")}}                                                           | Content Security Policy 1.0 _CSP 1.1 and CSP 3.0 doesn't extend the HTTP standard_                                                                                                                                                                    | {{Spec2("CSP 1.0")}}                         |
+| [Microsoft document](<https://msdn.microsoft.com/en-us/library/jj676915(v=vs.85).aspx>)    | Specifying legacy document modes\* _Defines X-UA-Compatible_                                                                                                                                                                                          | Note                                                 |
+| {{rfc(5689)}}                                                                           | HTTP Extensions for Web Distributed Authoring and Versioning (WebDAV) _These extensions of the Web, as well as CardDAV and CalDAV, are out-of-scope for HTTP on the Web. Modern APIs for application are defines using the RESTful pattern nowadays._ | Proposed Standard                                    |
+| {{rfc(2324)}}                                                                           | Hyper Text Coffee Pot Control Protocol (HTCPCP/1.0)                                                                                                                                                                                                   | April 1st joke spec                                  |
+| {{rfc(7168)}}                                                                           | The Hyper Text Coffee Pot Control Protocol for Tea Efflux Appliances (HTCPCP-TEA)                                                                                                                                                                     | April 1st joke spec                                  |
+| {{SpecName("HTML WHATWG")}}                                                       | HTML _Defines extensions of HTTP for Server-Sent Events_                                                                                                                                                                                              | {{Spec2("HTML WHATWG")}}                     |
+| [Reporting API](https://wicg.github.io/reporting/)                                         | `Report-To` header                                                                                                                                                                                                                                    | Draft                                                |
+| [Draft spec](https://datatracker.ietf.org/doc/html/draft-ietf-httpbis-expect-ct-01)        | Expect-CT Extension for HTTP                                                                                                                                                                                                                          | IETF Draft                                           |
diff --git a/files/en-us/web/http/resources_and_uris/index.md b/files/en-us/web/http/resources_and_uris/index.md
index 6f9ecb64545351a..8db1c4c19a54d70 100644
--- a/files/en-us/web/http/resources_and_uris/index.md
+++ b/files/en-us/web/http/resources_and_uris/index.md
@@ -12,19 +12,17 @@ tags:
   - URL
   - resources
 ---
-<div>{{HTTPSidebar}}</div>
+{{HTTPSidebar}}
 
-<p>HTTP allows a browser, or another {{Glossary("user agent")}}, to communicate with different <em>resources</em> on the Internet: to do this the browser needs both the <em>identity</em> and the <em>location</em> of the resources. These two bits of information are described by a {{glossary("URI")}}.</p>
+HTTP allows a browser, or another {{Glossary("user agent")}}, to communicate with different _resources_ on the Internet: to do this the browser needs both the _identity_ and the _location_ of the resources. These two bits of information are described by a {{glossary("URI")}}.
 
-<dl>
- <dt><a href="/en-US/docs/Web/HTTP/Basics_of_HTTP/Identifying_resources_on_the_Web">Identifying resources on the Web</a></dt>
- <dd>URIs and how to access resources on the Web.</dd>
- <dt><a href="/en-US/docs/Web/HTTP/Basics_of_HTTP/Data_URIs">Data URIs</a></dt>
- <dd>A specific kind of URIs, data URIs, embed the resource itself inside the identifier.</dd>
- <dt><a href="/en-US/docs/Web/HTTP/Basics_of_HTTP/Choosing_between_www_and_non-www_URLs">Choosing between www and non-www URLs</a></dt>
- <dd>Advice on using a www-prefixed domain or not, this article explains the consequences of the choice as well as how to make it.</dd>
- <dt><a href="/en-US/docs/Web/HTTP/Basics_of_HTTP/MIME_types">MIME Types</a></dt>
- <dd>MIME media types define what kind of document a specific resource is. This article presents both the syntax and the most useful MIME types for use on the Web.</dd>
- <dt><a href="/en-US/docs/Web/HTTP/Basics_of_HTTP/MIME_types/Common_types">Common MIME types</a></dt>
- <dd>List of common MIME types useful for Web developers.</dd>
-</dl>
+- [Identifying resources on the Web](/en-US/docs/Web/HTTP/Basics_of_HTTP/Identifying_resources_on_the_Web)
+  - : URIs and how to access resources on the Web.
+- [Data URIs](/en-US/docs/Web/HTTP/Basics_of_HTTP/Data_URIs)
+  - : A specific kind of URIs, data URIs, embed the resource itself inside the identifier.
+- [Choosing between www and non-www URLs](/en-US/docs/Web/HTTP/Basics_of_HTTP/Choosing_between_www_and_non-www_URLs)
+  - : Advice on using a www-prefixed domain or not, this article explains the consequences of the choice as well as how to make it.
+- [MIME Types](/en-US/docs/Web/HTTP/Basics_of_HTTP/MIME_types)
+  - : MIME media types define what kind of document a specific resource is. This article presents both the syntax and the most useful MIME types for use on the Web.
+- [Common MIME types](/en-US/docs/Web/HTTP/Basics_of_HTTP/MIME_types/Common_types)
+  - : List of common MIME types useful for Web developers.
diff --git a/files/en-us/web/http/session/index.md b/files/en-us/web/http/session/index.md
index e56efab0d929864..a85ea89139813bd 100644
--- a/files/en-us/web/http/session/index.md
+++ b/files/en-us/web/http/session/index.md
@@ -4,168 +4,148 @@ slug: Web/HTTP/Session
 tags:
   - HTTP
 ---
-<div>{{HTTPSidebar}}</div>
+{{HTTPSidebar}}
 
-<p>In client-server protocols, like HTTP, sessions consist of three phases:</p>
+In client-server protocols, like HTTP, sessions consist of three phases:
 
-<ol>
- <li>The client establishes a TCP connection (or the appropriate connection if the transport layer is not TCP).</li>
- <li>The client sends its request, and waits for the answer.</li>
- <li>The server processes the request, sending back its answer, providing a status code and appropriate data.</li>
-</ol>
+1.  The client establishes a TCP connection (or the appropriate connection if the transport layer is not TCP).
+2.  The client sends its request, and waits for the answer.
+3.  The server processes the request, sending back its answer, providing a status code and appropriate data.
 
-<p>As of HTTP/1.1, the connection is no longer closed after completing the third phase, and the client is now granted a further request: this means the second and third phases can now be performed any number of times.</p>
+As of HTTP/1.1, the connection is no longer closed after completing the third phase, and the client is now granted a further request: this means the second and third phases can now be performed any number of times.
 
-<h2 id="Establishing_a_connection">Establishing a connection</h2>
+## Establishing a connection
 
-<p>In client-server protocols, it is the client which establishes the connection. Opening a connection in HTTP means initiating a connection in the underlying transport layer, usually this is TCP.</p>
+In client-server protocols, it is the client which establishes the connection. Opening a connection in HTTP means initiating a connection in the underlying transport layer, usually this is TCP.
 
-<p>With TCP the default port, for an HTTP server on a computer, is port 80. Other ports can also be used, like 8000 or 8080. The URL of a page to fetch contains both the domain name, and the port number, though the latter can be omitted if it is 80. See <a href="/en-US/docs/Web/HTTP/Basics_of_HTTP/Identifying_resources_on_the_Web">Identifying resources on the Web</a> for more details.</p>
+With TCP the default port, for an HTTP server on a computer, is port 80. Other ports can also be used, like 8000 or 8080. The URL of a page to fetch contains both the domain name, and the port number, though the latter can be omitted if it is 80. See [Identifying resources on the Web](/en-US/docs/Web/HTTP/Basics_of_HTTP/Identifying_resources_on_the_Web) for more details.
 
-<div class="notecard note">
-  <p><strong>Note:</strong> The client-server model does not allow the server to send data to the client without an explicit request for it. To work around this problem, web developers use several techniques: ping the server periodically via the {{domxref("XMLHTTPRequest")}}, {{domxref("WindowOrWorkerGlobalScope.fetch")}} APIs, using the <a href="/en-US/docs/Web/API/WebSockets_API">WebSockets API</a>, or similar protocols.</p>
-</div>
-
-<h2 id="Sending_a_client_request">Sending a client request</h2>
-
-<p>Once the connection is established, the user-agent can send the request (a user-agent is typically a web browser, but can be anything else, a crawler, for example). A client request consists of text directives, separated by CRLF (carriage return, followed by line feed), divided into three blocks:</p>
+> **Note:** The client-server model does not allow the server to send data to the client without an explicit request for it. To work around this problem, web developers use several techniques: ping the server periodically via the {{domxref("XMLHTTPRequest")}}, {{domxref("WindowOrWorkerGlobalScope.fetch")}} APIs, using the [WebSockets API](/en-US/docs/Web/API/WebSockets_API), or similar protocols.
 
-<ol>
- <li>The first line contains a request method followed by its parameters:
-  <ul>
-   <li>the path of the document, i.e. an absolute URL without the protocol or domain name</li>
-   <li>the HTTP protocol version</li>
-  </ul>
- </li>
- <li>Subsequent lines represent an HTTP header, giving the server information about what type of data is appropriate (e.g., what language, what MIME types), or other data altering its behavior (e.g., not sending an answer if it is already cached). These HTTP headers form a block which ends with an empty line.</li>
- <li>The final block is an optional data block, which may contain further data mainly used by the POST method.</li>
-</ol>
-
-<h3 id="Example_requests">Example requests</h3>
-
-<p>Fetching the root page of developer.mozilla.org, (<code>https://developer.mozilla.org/</code>), and telling the server that the user-agent would prefer the page in French, if possible:</p>
-
-<pre>GET / HTTP/1.1
-Host: developer.mozilla.org
-Accept-Language: fr
-</pre>
-
-<p>Observe that final empty line, this separates the data block from the header block. As there is no <code>Content-Length</code> provided in an HTTP header, this data block is presented empty, marking the end of the headers, allowing the server to process the request the moment it receives this empty line.</p>
-
-<p>For example, sending the result of a form:</p>
-
-<pre>POST /contact_form.php HTTP/1.1
-Host: developer.mozilla.org
-Content-Length: 64
-Content-Type: application/x-www-form-urlencoded
-
-name=Joe%20User&amp;request=Send%20me%20one%20of%20your%20catalogue
-</pre>
-
-<h3 id="Request_methods">Request methods</h3>
-
-<p>HTTP defines a set of <a href="/en-US/docs/Web/HTTP/Methods">request methods</a> indicating the desired action to be performed upon a resource. Although they can also be nouns, these requests methods are sometimes referred as HTTP verbs. The most common requests are <code>GET</code> and <code>POST</code>:</p>
-
-<ul>
- <li>The {{HTTPMethod("GET")}} method requests a data representation of the specified resource. Requests using <code>GET</code> should only retrieve data.</li>
- <li>The {{HTTPMethod("POST")}} method sends data to a server so it may change its state. This is the method often used for <a href="/en-US/docs/Learn/Forms">HTML Forms</a>.</li>
-</ul>
-
-<h2 id="Structure_of_a_server_response">Structure of a server response</h2>
-
-<p>After the connected agent has sent its request, the web server processes it, and ultimately returns a response. Similar to a client request, a server response is formed of text directives, separated by CRLF, though divided into three blocks:</p>
-
-<ol>
- <li>The first line, the <em>status line</em>, consists of an acknowledgment of the HTTP version used, followed by a response status code (and its brief meaning in human-readable text).</li>
- <li>Subsequent lines represent specific HTTP headers, giving the client information about the data sent (e.g. type, data size, compression algorithm used, hints about caching). Similarly to the block of HTTP headers for a client request, these HTTP headers form a block ending with an empty line.</li>
- <li>The final block is a data block, which contains the optional data.</li>
-</ol>
-
-<h3 id="Example_responses">Example responses</h3>
-
-<p>Successful web page response:</p>
-
-<pre>HTTP/1.1 200 OK
-Content-Type: text/html; charset=utf-8
-Content-Length: 55743
-Connection: keep-alive
-Cache-Control: s-maxage=300, public, max-age=0
-Content-Language: en-US
-Date: Thu, 06 Dec 2018 17:37:18 GMT
-ETag: "2e77ad1dc6ab0b53a2996dfd4653c1c3"
-Server: meinheld/0.6.1
-Strict-Transport-Security: max-age=63072000
-X-Content-Type-Options: nosniff
-X-Frame-Options: DENY
-X-XSS-Protection: 1; mode=block
-Vary: Accept-Encoding,Cookie
-Age: 7
-
-&lt;!DOCTYPE html&gt;
-&lt;html lang="en"&gt;
-&lt;head&gt;
-  &lt;meta charset="utf-8"&gt;
-  &lt;title&gt;A simple webpage&lt;/title&gt;
-&lt;/head&gt;
-&lt;body&gt;
-  &lt;h1&gt;Simple HTML5 webpage&lt;/h1&gt;
-  &lt;p&gt;Hello, world!&lt;/p&gt;
-&lt;/body&gt;
-&lt;/html&gt;
-</pre>
-
-<p>Notification that the requested resource has permanently moved:</p>
-
-<pre>HTTP/1.1 301 Moved Permanently
-Server: Apache/2.4.37 (Red Hat)
-Content-Type: text/html; charset=utf-8
-Date: Thu, 06 Dec 2018 17:33:08 GMT
-Location: <a class="linkification-ext" href="../../../../" title="Linkification: https://developer.mozilla.org/">https://developer.mozilla.org/</a> <strong><em>(this is the new link to the resource; it is expected that the user-agent will fetch it)</em></strong>
-Keep-Alive: timeout=15, max=98
-Accept-Ranges: bytes
-Via: Moz-Cache-zlb05
-Connection: Keep-Alive
-Content-Length: 325 <em>(<strong>the content contains a default page to display if the user-agent is not able to follow the link)</strong></em>
-
-&lt;!DOCTYPE html... <strong><em>(contains a site-customized page helping the user to find the missing resource)</em></strong>
-</pre>
-
-<p>Notification that the requested resource doesn't exist:</p>
-
-<pre>HTTP/1.1 404 Not Found
-Content-Type: text/html; charset=utf-8
-Content-Length: 38217
-Connection: keep-alive
-Cache-Control: no-cache, no-store, must-revalidate, max-age=0
-Content-Language: en-US
-Date: Thu, 06 Dec 2018 17:35:13 GMT
-Expires: Thu, 06 Dec 2018 17:35:13 GMT
-Server: meinheld/0.6.1
-Strict-Transport-Security: max-age=63072000
-X-Content-Type-Options: nosniff
-X-Frame-Options: DENY
-X-XSS-Protection: 1; mode=block
-Vary: Accept-Encoding,Cookie
-X-Cache: Error from cloudfront
-
-&lt;!DOCTYPE html... <strong><em>(contains a site-customized page helping the user to find the missing resource)</em></strong>
-</pre>
-
-<h3 id="Response_status_codes">Response status codes</h3>
-
-<p><a href="/en-US/docs/Web/HTTP/Status">HTTP response status codes</a> indicate if a specific HTTP request has been successfully completed. Responses are grouped into five classes: informational responses, successful responses, redirects, client errors, and servers errors.</p>
-
-<ul>
- <li>{{HTTPStatus(200)}}: OK. The request has succeeded.</li>
- <li>{{HTTPStatus(301)}}: Moved Permanently. This response code means that the URI of requested resource has been changed.</li>
- <li>{{HTTPStatus(404)}}: Not Found. The server cannot find the requested resource.</li>
-</ul>
-
-<h2 id="See_also">See also</h2>
-
-<ul>
- <li><a href="/en-US/docs/Web/HTTP/Basics_of_HTTP/Identifying_resources_on_the_Web">Identifying resources on the Web</a></li>
- <li><a href="/en-US/docs/Web/HTTP/Headers">HTTP headers</a></li>
- <li><a href="/en-US/docs/Web/HTTP/Methods">HTTP request methods</a></li>
- <li><a href="/en-US/docs/Web/HTTP/Status">HTTP response status codes </a></li>
-</ul>
+## Sending a client request
+
+Once the connection is established, the user-agent can send the request (a user-agent is typically a web browser, but can be anything else, a crawler, for example). A client request consists of text directives, separated by CRLF (carriage return, followed by line feed), divided into three blocks:
+
+1.  The first line contains a request method followed by its parameters:
+
+    - the path of the document, i.e. an absolute URL without the protocol or domain name
+    - the HTTP protocol version
+
+2.  Subsequent lines represent an HTTP header, giving the server information about what type of data is appropriate (e.g., what language, what MIME types), or other data altering its behavior (e.g., not sending an answer if it is already cached). These HTTP headers form a block which ends with an empty line.
+3.  The final block is an optional data block, which may contain further data mainly used by the POST method.
+
+### Example requests
+
+Fetching the root page of developer.mozilla.org, (`https://developer.mozilla.org/`), and telling the server that the user-agent would prefer the page in French, if possible:
+
+    GET / HTTP/1.1
+    Host: developer.mozilla.org
+    Accept-Language: fr
+
+Observe that final empty line, this separates the data block from the header block. As there is no `Content-Length` provided in an HTTP header, this data block is presented empty, marking the end of the headers, allowing the server to process the request the moment it receives this empty line.
+
+For example, sending the result of a form:
+
+    POST /contact_form.php HTTP/1.1
+    Host: developer.mozilla.org
+    Content-Length: 64
+    Content-Type: application/x-www-form-urlencoded
+
+    name=Joe%20User&request=Send%20me%20one%20of%20your%20catalogue
+
+### Request methods
+
+HTTP defines a set of [request methods](/en-US/docs/Web/HTTP/Methods) indicating the desired action to be performed upon a resource. Although they can also be nouns, these requests methods are sometimes referred as HTTP verbs. The most common requests are `GET` and `POST`:
+
+- The {{HTTPMethod("GET")}} method requests a data representation of the specified resource. Requests using `GET` should only retrieve data.
+- The {{HTTPMethod("POST")}} method sends data to a server so it may change its state. This is the method often used for [HTML Forms](/en-US/docs/Learn/Forms).
+
+## Structure of a server response
+
+After the connected agent has sent its request, the web server processes it, and ultimately returns a response. Similar to a client request, a server response is formed of text directives, separated by CRLF, though divided into three blocks:
+
+1.  The first line, the _status line_, consists of an acknowledgment of the HTTP version used, followed by a response status code (and its brief meaning in human-readable text).
+2.  Subsequent lines represent specific HTTP headers, giving the client information about the data sent (e.g. type, data size, compression algorithm used, hints about caching). Similarly to the block of HTTP headers for a client request, these HTTP headers form a block ending with an empty line.
+3.  The final block is a data block, which contains the optional data.
+
+### Example responses
+
+Successful web page response:
+
+    HTTP/1.1 200 OK
+    Content-Type: text/html; charset=utf-8
+    Content-Length: 55743
+    Connection: keep-alive
+    Cache-Control: s-maxage=300, public, max-age=0
+    Content-Language: en-US
+    Date: Thu, 06 Dec 2018 17:37:18 GMT
+    ETag: "2e77ad1dc6ab0b53a2996dfd4653c1c3"
+    Server: meinheld/0.6.1
+    Strict-Transport-Security: max-age=63072000
+    X-Content-Type-Options: nosniff
+    X-Frame-Options: DENY
+    X-XSS-Protection: 1; mode=block
+    Vary: Accept-Encoding,Cookie
+    Age: 7
+
+    <!DOCTYPE html>
+    <html lang="en">
+    <head>
+      <meta charset="utf-8">
+      <title>A simple webpage</title>
+    </head>
+    <body>
+      <h1>Simple HTML5 webpage</h1>
+      <p>Hello, world!</p>
+    </body>
+    </html>
+
+Notification that the requested resource has permanently moved:
+
+    HTTP/1.1 301 Moved Permanently
+    Server: Apache/2.4.37 (Red Hat)
+    Content-Type: text/html; charset=utf-8
+    Date: Thu, 06 Dec 2018 17:33:08 GMT
+    Location: https://developer.mozilla.org/ (this is the new link to the resource; it is expected that the user-agent will fetch it)
+    Keep-Alive: timeout=15, max=98
+    Accept-Ranges: bytes
+    Via: Moz-Cache-zlb05
+    Connection: Keep-Alive
+    Content-Length: 325 (the content contains a default page to display if the user-agent is not able to follow the link)
+
+    <!DOCTYPE html... (contains a site-customized page helping the user to find the missing resource)
+
+Notification that the requested resource doesn't exist:
+
+    HTTP/1.1 404 Not Found
+    Content-Type: text/html; charset=utf-8
+    Content-Length: 38217
+    Connection: keep-alive
+    Cache-Control: no-cache, no-store, must-revalidate, max-age=0
+    Content-Language: en-US
+    Date: Thu, 06 Dec 2018 17:35:13 GMT
+    Expires: Thu, 06 Dec 2018 17:35:13 GMT
+    Server: meinheld/0.6.1
+    Strict-Transport-Security: max-age=63072000
+    X-Content-Type-Options: nosniff
+    X-Frame-Options: DENY
+    X-XSS-Protection: 1; mode=block
+    Vary: Accept-Encoding,Cookie
+    X-Cache: Error from cloudfront
+
+    <!DOCTYPE html... (contains a site-customized page helping the user to find the missing resource)
+
+### Response status codes
+
+[HTTP response status codes](/en-US/docs/Web/HTTP/Status) indicate if a specific HTTP request has been successfully completed. Responses are grouped into five classes: informational responses, successful responses, redirects, client errors, and servers errors.
+
+- {{HTTPStatus(200)}}: OK. The request has succeeded.
+- {{HTTPStatus(301)}}: Moved Permanently. This response code means that the URI of requested resource has been changed.
+- {{HTTPStatus(404)}}: Not Found. The server cannot find the requested resource.
+
+## See also
+
+- [Identifying resources on the Web](/en-US/docs/Web/HTTP/Basics_of_HTTP/Identifying_resources_on_the_Web)
+- [HTTP headers](/en-US/docs/Web/HTTP/Headers)
+- [HTTP request methods](/en-US/docs/Web/HTTP/Methods)
+- [HTTP response status codes](/en-US/docs/Web/HTTP/Status)
diff --git a/files/en-us/web/http/status/100/index.md b/files/en-us/web/http/status/100/index.md
index 5a924260414c970..5c20d851b707be7 100644
--- a/files/en-us/web/http/status/100/index.md
+++ b/files/en-us/web/http/status/100/index.md
@@ -2,37 +2,36 @@
 title: 100 Continue
 slug: Web/HTTP/Status/100
 tags:
-- HTTP
-- Informational
-- Status code
+  - HTTP
+  - Informational
+  - Status code
 browser-compat: http.status.100
 ---
-<div>{{HTTPSidebar}}</div>
+{{HTTPSidebar}}
 
-<p>The HTTP <strong><code>100 Continue</code></strong> informational status response code
-  indicates that everything so far is OK and that the client should continue with the
-  request or ignore it if it is already finished.</p>
+The HTTP **`100 Continue`** informational status response code
+indicates that everything so far is OK and that the client should continue with the
+request or ignore it if it is already finished.
 
-<p>To have a server check the request's headers, a client must send
-  {{HTTPHeader("Expect")}}<code>: 100-continue</code> as a header in its initial request
-  and receive a <code>100 Continue</code> status code in response before sending the body.
-</p>
+To have a server check the request's headers, a client must send
+{{HTTPHeader("Expect")}}`: 100-continue` as a header in its initial request
+and receive a `100 Continue` status code in response before sending the body.
 
-<h2 id="Status">Status</h2>
+## Status
 
-<pre class="brush: html">100 Continue</pre>
+```html
+100 Continue
+```
 
-<h2 id="Specifications">Specifications</h2>
+## Specifications
 
 {{Specifications}}
 
-<h2 id="Browser_compatibility">Browser compatibility</h2>
+## Browser compatibility
 
-<p>{{Compat}}</p>
+{{Compat}}
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
-  <li>{{HTTPHeader("Expect")}}</li>
-  <li>{{HTTPStatus(417)}}</li>
-</ul>
+- {{HTTPHeader("Expect")}}
+- {{HTTPStatus(417)}}
diff --git a/files/en-us/web/http/status/101/index.md b/files/en-us/web/http/status/101/index.md
index 8364c89dcdaf98c..60bbe5e4f242fc1 100644
--- a/files/en-us/web/http/status/101/index.md
+++ b/files/en-us/web/http/status/101/index.md
@@ -2,57 +2,47 @@
 title: 101 Switching Protocols
 slug: Web/HTTP/Status/101
 tags:
-- HTTP
-- HTTP Status Code
-- Informational
-- Reference
-- WebSockets
+  - HTTP
+  - HTTP Status Code
+  - Informational
+  - Reference
+  - WebSockets
 ---
-<div>{{HTTPSidebar}}</div>
-
-<p>The HTTP <code><strong>101 Switching Protocols</strong></code> response code indicates
-  the protocol the server is switching to as requested by a client which sent the message
-  including the {{HTTPHeader("Upgrade")}} request header.</p>
-
-<p>The server includes in this response an {{HTTPHeader("Upgrade")}} response header to
-  indicate the protocol it switched to. The process is described in detail in the article
-  <a href="/en-US/docs/Web/HTTP/Protocol_upgrade_mechanism">Protocol upgrade
-    mechanism</a>.</p>
-
-<h2 id="Status">Status</h2>
-
-<pre class="brush: html">101 Switching Protocols</pre>
-
-<h2 id="Examples">Examples</h2>
-
-<p>Switching protocols might be used with <a
-    href="/en-US/docs/Web/API/WebSockets_API">WebSockets</a>.</p>
-
-<pre>HTTP/1.1 101 Switching Protocols
-Upgrade: websocket
-Connection: Upgrade</pre>
-
-<h2 id="Specifications">Specifications</h2>
-
-<table class="standard-table">
-  <tbody>
-    <tr>
-      <th scope="col">Specification</th>
-      <th scope="col">Title</th>
-    </tr>
-    <tr>
-      <td>{{RFC("7231", "101 Switching Protocol" , "6.2.2")}}</td>
-      <td>Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content</td>
-    </tr>
-  </tbody>
-</table>
-
-<h2 id="See_also">See also</h2>
-
-<ul>
-  <li><a href="/en-US/docs/Web/HTTP/Protocol_upgrade_mechanism">Protocol upgrade
-      mechanism</a></li>
-  <li><a href="/en-US/docs/Web/API/WebSockets_API">WebSockets</a></li>
-  <li>{{HTTPHeader("Upgrade")}}</li>
-  <li>{{HTTPStatus("426")}} <code>Upgrade Required</code></li>
-</ul>
+{{HTTPSidebar}}
+
+The HTTP **`101 Switching Protocols`** response code indicates
+the protocol the server is switching to as requested by a client which sent the message
+including the {{HTTPHeader("Upgrade")}} request header.
+
+The server includes in this response an {{HTTPHeader("Upgrade")}} response header to
+indicate the protocol it switched to. The process is described in detail in the article
+[Protocol upgrade
+mechanism](/en-US/docs/Web/HTTP/Protocol_upgrade_mechanism).
+
+## Status
+
+```html
+101 Switching Protocols
+```
+
+## Examples
+
+Switching protocols might be used with [WebSockets](/en-US/docs/Web/API/WebSockets_API).
+
+    HTTP/1.1 101 Switching Protocols
+    Upgrade: websocket
+    Connection: Upgrade
+
+## Specifications
+
+| Specification                                                        | Title                                                         |
+| -------------------------------------------------------------------- | ------------------------------------------------------------- |
+| {{RFC("7231", "101 Switching Protocol" , "6.2.2")}} | Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content |
+
+## See also
+
+- [Protocol upgrade
+  mechanism](/en-US/docs/Web/HTTP/Protocol_upgrade_mechanism)
+- [WebSockets](/en-US/docs/Web/API/WebSockets_API)
+- {{HTTPHeader("Upgrade")}}
+- {{HTTPStatus("426")}} `Upgrade Required`
diff --git a/files/en-us/web/http/status/103/index.md b/files/en-us/web/http/status/103/index.md
index 057cc54b7f11748..d967596a0224722 100644
--- a/files/en-us/web/http/status/103/index.md
+++ b/files/en-us/web/http/status/103/index.md
@@ -2,50 +2,36 @@
 title: 103 Early Hints
 slug: Web/HTTP/Status/103
 tags:
-- Draft
-- HTTP
-- Informational
-- NeedsCompatTable
-- NeedsContent
-- Status code
+  - Draft
+  - HTTP
+  - Informational
+  - NeedsCompatTable
+  - NeedsContent
+  - Status code
 browser-compat: http.status.103
 ---
-<p>{{HTTPSidebar}}{{Draft}}</p>
+{{HTTPSidebar}}{{Draft}}
 
-<p>The HTTP <strong><code>103 Early Hints</code></strong> information response status code
-  is primarily intended to be used with the {{HTTPHeader("Link")}} header to allow the
-  user agent to start preloading resources while the server is still preparing a response.
-</p>
+The HTTP **`103 Early Hints`** information response status code
+is primarily intended to be used with the {{HTTPHeader("Link")}} header to allow the
+user agent to start preloading resources while the server is still preparing a response.
 
-<h2 id="Syntax">Syntax</h2>
+## Syntax
 
-<pre class="brush: html">103 Early Hints</pre>
+```html
+103 Early Hints
+```
 
-<h2 id="Specifications">Specifications</h2>
+## Specifications
 
-<table class="standard-table">
-  <thead>
-    <tr>
-      <th scope="col">Specification</th>
-      <th scope="col">Status</th>
-      <th scope="col">Comments</th>
-    </tr>
-  </thead>
-  <tbody>
-    <tr>
-      <td>{{RFC(8297, "103 Early Hints")}}</td>
-      <td>IETF RFC</td>
-      <td>Initial definition</td>
-    </tr>
-  </tbody>
-</table>
+| Specification                                | Status   | Comments           |
+| -------------------------------------------- | -------- | ------------------ |
+| {{RFC(8297, "103 Early Hints")}} | IETF RFC | Initial definition |
 
-<h2 id="Browser_compatibility">Browser compatibility</h2>
+## Browser compatibility
 
-<p>{{Compat}}</p>
+{{Compat}}
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
-  <li>{{HTTPHeader("Link")}}</li>
-</ul>
+- {{HTTPHeader("Link")}}
diff --git a/files/en-us/web/http/status/200/index.md b/files/en-us/web/http/status/200/index.md
index 8f5e3c24a720cdb..f335e36adf5c4d4 100644
--- a/files/en-us/web/http/status/200/index.md
+++ b/files/en-us/web/http/status/200/index.md
@@ -7,35 +7,33 @@ tags:
   - Success
 browser-compat: http.status.200
 ---
-<div>{{HTTPSidebar}}</div>
+{{HTTPSidebar}}
 
-<p>The HTTP <strong><code>200 OK</code></strong> success status response code indicates that the request has succeeded. A 200 response is cacheable by default.</p>
+The HTTP **`200 OK`** success status response code indicates that the request has succeeded. A 200 response is cacheable by default.
 
-<p>The meaning of a success depends on the HTTP request method:</p>
+The meaning of a success depends on the HTTP request method:
 
-<ul>
- <li>{{HTTPMethod("GET")}}: The resource has been fetched and is transmitted in the message body.</li>
- <li>{{HTTPMethod("HEAD")}}: The representation headers are included in the response without any message body </li>
- <li>{{HTTPMethod("POST")}}: The resource describing the result of the action is transmitted in the message body</li>
- <li>{{HTTPMethod("TRACE")}}: The message body contains the request message as received by the server.</li>
-</ul>
+- {{HTTPMethod("GET")}}: The resource has been fetched and is transmitted in the message body.
+- {{HTTPMethod("HEAD")}}: The representation headers are included in the response without any message body
+- {{HTTPMethod("POST")}}: The resource describing the result of the action is transmitted in the message body
+- {{HTTPMethod("TRACE")}}: The message body contains the request message as received by the server.
 
-<p>The successful result of a {{HTTPMethod("PUT")}} or a {{HTTPMethod("DELETE")}} is often not a <code>200</code> <code>OK</code> but a {{HTTPStatus("204")}} <code>No Content</code> (or a {{HTTPStatus("201")}} <code>Created</code> when the resource is uploaded for the first time).</p>
+The successful result of a {{HTTPMethod("PUT")}} or a {{HTTPMethod("DELETE")}} is often not a `200` `OK` but a {{HTTPStatus("204")}} `No Content` (or a {{HTTPStatus("201")}} `Created` when the resource is uploaded for the first time).
 
-<h2 id="Status">Status</h2>
+## Status
 
-<pre class="brush: html">200 OK</pre>
+```html
+200 OK
+```
 
-<h2 id="Specifications">Specifications</h2>
+## Specifications
 
 {{Specifications}}
 
-<h2 id="Browser_compatibility">Browser compatibility</h2>
+## Browser compatibility
 
-<p>{{Compat}}</p>
+{{Compat}}
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
- <li><a href="/en-US/docs/Web/HTTP/Methods">HTTP request methods</a></li>
-</ul>
+- [HTTP request methods](/en-US/docs/Web/HTTP/Methods)
diff --git a/files/en-us/web/http/status/201/index.md b/files/en-us/web/http/status/201/index.md
index fc391bfb8442e2f..67d8006721146c4 100644
--- a/files/en-us/web/http/status/201/index.md
+++ b/files/en-us/web/http/status/201/index.md
@@ -2,37 +2,37 @@
 title: 201 Created
 slug: Web/HTTP/Status/201
 tags:
-- HTTP
-- Reference
-- Status code
-- Success
+  - HTTP
+  - Reference
+  - Status code
+  - Success
 browser-compat: http.status.201
 ---
-<div>{{HTTPSidebar}}</div>
+{{HTTPSidebar}}
 
-<p>The HTTP <strong><code>201 Created</code></strong> success status response code
-  indicates that the request has succeeded and has led to the creation of a resource. The
-  new resource is effectively created before this response is sent back and the new
-  resource is returned in the body of the message, its location being either the URL of
-  the request, or the content of the {{HTTPHeader("Location")}} header.</p>
+The HTTP **`201 Created`** success status response code
+indicates that the request has succeeded and has led to the creation of a resource. The
+new resource is effectively created before this response is sent back and the new
+resource is returned in the body of the message, its location being either the URL of
+the request, or the content of the {{HTTPHeader("Location")}} header.
 
-<p>The common use case of this status code is as the result of a {{HTTPMethod("POST")}}
-  request.</p>
+The common use case of this status code is as the result of a {{HTTPMethod("POST")}}
+request.
 
-<h2 id="Status">Status</h2>
+## Status
 
-<pre class="brush: html">201 Created</pre>
+```html
+201 Created
+```
 
-<h2 id="Specifications">Specifications</h2>
+## Specifications
 
 {{Specifications}}
 
-<h2 id="Browser_compatibility">Browser compatibility</h2>
+## Browser compatibility
 
-<p>{{Compat}}</p>
+{{Compat}}
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
-  <li><a href="/en-US/docs/Web/HTTP/Methods">HTTP request methods</a></li>
-</ul>
+- [HTTP request methods](/en-US/docs/Web/HTTP/Methods)
diff --git a/files/en-us/web/http/status/202/index.md b/files/en-us/web/http/status/202/index.md
index 2aaaaedc8284196..82f9f4ecbf3d886 100644
--- a/files/en-us/web/http/status/202/index.md
+++ b/files/en-us/web/http/status/202/index.md
@@ -2,45 +2,35 @@
 title: 202 Accepted
 slug: Web/HTTP/Status/202
 tags:
-- HTTP
-- Reference
-- Status code
-- Success response
+  - HTTP
+  - Reference
+  - Status code
+  - Success response
 ---
-<div>{{HTTPSidebar}}</div>
-
-<p>The HyperText Transfer Protocol (HTTP) <code><strong>202 Accepted</strong></code>
-  response status code indicates that the request has been accepted for processing, but
-  the processing has not been completed; in fact, processing may not have started yet. The
-  request might or might not eventually be acted upon, as it might be disallowed when
-  processing actually takes place.</p>
-
-<p>202 is non-committal, meaning that there is no way for the HTTP to later send an
-  asynchronous response indicating the outcome of processing the request. It is intended
-  for cases where another process or server handles the request, or for batch processing.
-</p>
-
-<h2 id="Status">Status</h2>
-
-<pre class="brush: html">202 Accepted</pre>
-
-<h2 id="Specifications">Specifications</h2>
-
-<table class="standard-table">
-  <tbody>
-    <tr>
-      <th scope="col">Specification</th>
-      <th scope="col">Title</th>
-    </tr>
-    <tr>
-      <td>{{RFC("7231", "202 Accepted" , "6.3.3")}}</td>
-      <td>Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content</td>
-    </tr>
-  </tbody>
-</table>
-
-<h2 id="See_also">See also</h2>
-
-<ul>
-  <li>{{HTTPHeader("Accept")}}</li>
-</ul>
+{{HTTPSidebar}}
+
+The HyperText Transfer Protocol (HTTP) **`202 Accepted`**
+response status code indicates that the request has been accepted for processing, but
+the processing has not been completed; in fact, processing may not have started yet. The
+request might or might not eventually be acted upon, as it might be disallowed when
+processing actually takes place.
+
+202 is non-committal, meaning that there is no way for the HTTP to later send an
+asynchronous response indicating the outcome of processing the request. It is intended
+for cases where another process or server handles the request, or for batch processing.
+
+## Status
+
+```html
+202 Accepted
+```
+
+## Specifications
+
+| Specification                                            | Title                                                         |
+| -------------------------------------------------------- | ------------------------------------------------------------- |
+| {{RFC("7231", "202 Accepted" , "6.3.3")}} | Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content |
+
+## See also
+
+- {{HTTPHeader("Accept")}}
diff --git a/files/en-us/web/http/status/203/index.md b/files/en-us/web/http/status/203/index.md
index 45a5ac65c9c3c25..f1dd064d47615ad 100644
--- a/files/en-us/web/http/status/203/index.md
+++ b/files/en-us/web/http/status/203/index.md
@@ -8,44 +8,33 @@ tags:
   - Status code
   - Successful response
 ---
-<div>{{HTTPSidebar}}</div>
-
-<p>The HTTP <strong><code>203 Non-Authoritative Information</code></strong> response
-  status indicates that the request was successful but the enclosed payload has been
-  modified by a transforming {{Glossary("Proxy server", "proxy")}} from that of the origin
-  server's {{HTTPStatus("200")}} (<code>OK</code>) response .</p>
-
-<p>The <code>203</code> response is similar to the value
-  <code><a href="/en-US/docs/Web/HTTP/Headers/Warning#warning_codes">214</a></code>,
-  meaning <code>Transformation Applied</code>, of the {{HTTPHeader("Warning")}} header
-  code, which has the additional advantage of being applicable to responses with any
-  status code.</p>
-
-<h2 id="Status">Status</h2>
-
-<pre class="brush: html">203 Non-Authoritative Information</pre>
-
-<h2 id="Specifications">Specifications</h2>
-
-<table class="standard-table">
-  <thead>
-    <tr>
-      <th scope="col">Specification</th>
-      <th scope="col">Title</th>
-    </tr>
-  </thead>
-  <tbody>
-    <tr>
-      <td>{{RFC("7231", "203 Non-Authoritative Information" , "6.3.4")}}</td>
-      <td>Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content</td>
-    </tr>
-  </tbody>
-</table>
-
-<h2 id="See_also">See also</h2>
-
-<ul>
-  <li>{{HTTPStatus("200")}}</li>
-  <li>{{Glossary("Proxy server")}}</li>
-  <li>{{HTTPHeader("Warning")}}</li>
-</ul>
+{{HTTPSidebar}}
+
+The HTTP **`203 Non-Authoritative Information`** response
+status indicates that the request was successful but the enclosed payload has been
+modified by a transforming {{Glossary("Proxy server", "proxy")}} from that of the origin
+server's {{HTTPStatus("200")}} (`OK`) response .
+
+The `203` response is similar to the value
+[`214`](/en-US/docs/Web/HTTP/Headers/Warning#warning_codes),
+meaning `Transformation Applied`, of the {{HTTPHeader("Warning")}} header
+code, which has the additional advantage of being applicable to responses with any
+status code.
+
+## Status
+
+```html
+203 Non-Authoritative Information
+```
+
+## Specifications
+
+| Specification                                                                        | Title                                                         |
+| ------------------------------------------------------------------------------------ | ------------------------------------------------------------- |
+| {{RFC("7231", "203 Non-Authoritative Information" , "6.3.4")}} | Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content |
+
+## See also
+
+- {{HTTPStatus("200")}}
+- {{Glossary("Proxy server")}}
+- {{HTTPHeader("Warning")}}
diff --git a/files/en-us/web/http/status/204/index.md b/files/en-us/web/http/status/204/index.md
index b9779bd94dc2afe..3c0cdee6cf7acfe 100644
--- a/files/en-us/web/http/status/204/index.md
+++ b/files/en-us/web/http/status/204/index.md
@@ -2,56 +2,51 @@
 title: 204 No Content
 slug: Web/HTTP/Status/204
 tags:
-- HTTP
-- Reference
-- Status code
-- Success
+  - HTTP
+  - Reference
+  - Status code
+  - Success
 browser-compat: http.status.204
 ---
-<div>{{HTTPSidebar}}</div>
+{{HTTPSidebar}}
 
-<p>The HTTP <strong><code>204 No Content</code></strong> success status response code
-  indicates that a request has succeeded, but that the client doesn't need to navigate away
-  from its current page.</p>
+The HTTP **`204 No Content`** success status response code
+indicates that a request has succeeded, but that the client doesn't need to navigate away
+from its current page.
 
-<p>This might be used, for example, when implementing "save and continue editing" functionality for a wiki site.
-  In this case a {{HTTPMethod("PUT")}} request would be used to save the page, and the <code>204 No Content</code> response
-  would be sent to indicate that the editor should not be replaced by some other page.</p>
+This might be used, for example, when implementing "save and continue editing" functionality for a wiki site.
+In this case a {{HTTPMethod("PUT")}} request would be used to save the page, and the `204 No Content` response
+would be sent to indicate that the editor should not be replaced by some other page.
 
-<p>A 204 response is cacheable by default (an {{HTTPHeader("ETag")}} header is included in such a response).</p>
+A 204 response is cacheable by default (an {{HTTPHeader("ETag")}} header is included in such a response).
 
+## Status
 
-<h2 id="Status">Status</h2>
+```html
+204 No Content
+```
 
-<pre class="brush: html">204 No Content</pre>
-
-<h2 id="Specifications">Specifications</h2>
+## Specifications
 
 {{Specifications}}
 
-<h2 id="Browser_compatibility">Browser compatibility</h2>
+## Browser compatibility
+
+{{Compat}}
 
-<p>{{Compat}}</p>
+## Compatibility notes
 
-<h2 id="Compatibility_notes">Compatibility notes</h2>
+- Although this status code is intended to describe a response with no body, servers
+  may erroneously include data following the headers. The protocol allows user agents to
+  vary in how they process such responses ([discussion regarding this
+  specification text can be found here](https://github.com/httpwg/http11bis/issues/26)). This is observable in persistent
+  connections, where the invalid body may include a distinct response to a subsequent
+  request.
 
-<ul>
-  <li>Although this status code is intended to describe a response with no body, servers
-    may erroneously include data following the headers. The protocol allows user agents to
-    vary in how they process such responses (<a
-      href="https://github.com/httpwg/http11bis/issues/26">discussion regarding this
-      specification text can be found here</a>). This is observable in persistent
-    connections, where the invalid body may include a distinct response to a subsequent
-    request.<br>
-    <br>
-    Apple Safari rejects any such data. Google Chrome and Microsoft Edge discard up to
-    four invalid bytes preceding a valid response. Firefox tolerates in excess of a
-    kilobyte of invalid data preceding a valid response.
-  </li>
-</ul>
+  Apple Safari rejects any such data. Google Chrome and Microsoft Edge discard up to
+  four invalid bytes preceding a valid response. Firefox tolerates in excess of a
+  kilobyte of invalid data preceding a valid response.
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
-  <li><a href="/en-US/docs/Web/HTTP/Methods">HTTP request methods</a></li>
-</ul>
+- [HTTP request methods](/en-US/docs/Web/HTTP/Methods)
diff --git a/files/en-us/web/http/status/205/index.md b/files/en-us/web/http/status/205/index.md
index 965c2110d7baf5b..05f3adc5d297d74 100644
--- a/files/en-us/web/http/status/205/index.md
+++ b/files/en-us/web/http/status/205/index.md
@@ -2,46 +2,35 @@
 title: 205 Reset Content
 slug: Web/HTTP/Status/205
 tags:
-- HTTP
-- HTTP Status Code
-- Reference
-- Status code
+  - HTTP
+  - HTTP Status Code
+  - Reference
+  - Status code
 ---
-<div>{{HTTPSidebar}}</div>
+{{HTTPSidebar}}
 
-<p>The HTTP <strong><code>205 Reset Content</code></strong> response status tells the
-  client to reset the document view, so for example to clear the content of a form, reset
-  a canvas state, or to refresh the UI.</p>
+The HTTP **`205 Reset Content`** response status tells the
+client to reset the document view, so for example to clear the content of a form, reset
+a canvas state, or to refresh the UI.
 
-<h2 id="Status">Status</h2>
+## Status
 
-<pre class="brush: html">205 Reset Content</pre>
+```html
+205 Reset Content
+```
 
-<h2 id="Specifications">Specifications</h2>
+## Specifications
 
-<table class="standard-table">
-  <tbody>
-    <tr>
-      <th scope="col">Specification</th>
-      <th scope="col">Title</th>
-    </tr>
-    <tr>
-      <td>{{RFC("7231", "205 Reset Content" , "6.3.6")}}</td>
-      <td>Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content</td>
-    </tr>
-  </tbody>
-</table>
+| Specification                                                | Title                                                         |
+| ------------------------------------------------------------ | ------------------------------------------------------------- |
+| {{RFC("7231", "205 Reset Content" , "6.3.6")}} | Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content |
 
-<h2 id="Compatibility_Notes">Compatibility Notes</h2>
+## Compatibility Notes
 
-<ul>
-  <li>Browser behavior differs if this response erroneously includes a body on persistent
-    connections See <a href="/en-US/docs/Web/HTTP/Status/204">204 No Content</a> for more
-    detail.</li>
-</ul>
+- Browser behavior differs if this response erroneously includes a body on persistent
+  connections See [204 No Content](/en-US/docs/Web/HTTP/Status/204) for more
+  detail.
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
-  <li>{{HTTPStatus(204)}} No Content</li>
-</ul>
+- {{HTTPStatus(204)}} No Content
diff --git a/files/en-us/web/http/status/206/index.md b/files/en-us/web/http/status/206/index.md
index 5de6f1ea458a374..37c87f8e1e4fcec 100644
--- a/files/en-us/web/http/status/206/index.md
+++ b/files/en-us/web/http/status/206/index.md
@@ -2,75 +2,75 @@
 title: 206 Partial Content
 slug: Web/HTTP/Status/206
 tags:
-- HTTP
-- HTTP Status
-- Range Requests
-- Success
+  - HTTP
+  - HTTP Status
+  - Range Requests
+  - Success
 browser-compat: http.status.206
 ---
-<div>{{HTTPSidebar}}</div>
+{{HTTPSidebar}}
 
-<p>The HTTP <strong><code>206 Partial Content</code></strong> success status response code
-  indicates that the request has succeeded and the body contains the requested ranges
-  of data, as described in the {{HTTPHeader("Range")}} header of the request.</p>
+The HTTP **`206 Partial Content`** success status response code
+indicates that the request has succeeded and the body contains the requested ranges
+of data, as described in the {{HTTPHeader("Range")}} header of the request.
 
-<p>If there is only one range, the {{HTTPHeader("Content-Type")}} of the whole response is
-  set to the type of the document, and a {{HTTPHeader("Content-Range")}} is provided.</p>
+If there is only one range, the {{HTTPHeader("Content-Type")}} of the whole response is
+set to the type of the document, and a {{HTTPHeader("Content-Range")}} is provided.
 
-<p>If several ranges are sent back, the {{HTTPHeader("Content-Type")}} is set to
-  <code>multipart/byteranges</code> and each fragment covers one range, with
-  {{HTTPHeader("Content-Range")}} and {{HTTPHeader("Content-Type")}} describing it.</p>
+If several ranges are sent back, the {{HTTPHeader("Content-Type")}} is set to
+`multipart/byteranges` and each fragment covers one range, with
+{{HTTPHeader("Content-Range")}} and {{HTTPHeader("Content-Type")}} describing it.
 
-<h2 id="Status">Status</h2>
+## Status
 
-<pre class="brush: html">206 Partial Content</pre>
+```html
+206 Partial Content
+```
 
-<h2 id="Examples">Examples</h2>
+## Examples
 
-<p>A response containing one single range:</p>
+A response containing one single range:
 
-<pre>HTTP/1.1 206 Partial Content
-Date: Wed, 15 Nov 2015 06:25:24 GMT
-Last-Modified: Wed, 15 Nov 2015 04:58:08 GMT
-Content-Range: bytes 21010-47021/47022
-Content-Length: 26012
-Content-Type: image/gif
+    HTTP/1.1 206 Partial Content
+    Date: Wed, 15 Nov 2015 06:25:24 GMT
+    Last-Modified: Wed, 15 Nov 2015 04:58:08 GMT
+    Content-Range: bytes 21010-47021/47022
+    Content-Length: 26012
+    Content-Type: image/gif
 
-... 26012 bytes of partial image data ...</pre>
+    ... 26012 bytes of partial image data ...
 
-<p>A response containing several ranges:</p>
+A response containing several ranges:
 
-<pre>HTTP/1.1 206 Partial Content
-Date: Wed, 15 Nov 2015 06:25:24 GMT
-Last-Modified: Wed, 15 Nov 2015 04:58:08 GMT
-Content-Length: 1741
-Content-Type: multipart/byteranges; boundary=String_separator
+    HTTP/1.1 206 Partial Content
+    Date: Wed, 15 Nov 2015 06:25:24 GMT
+    Last-Modified: Wed, 15 Nov 2015 04:58:08 GMT
+    Content-Length: 1741
+    Content-Type: multipart/byteranges; boundary=String_separator
 
---String_separator
-Content-Type: application/pdf
-Content-Range: bytes 234-639/8000
+    --String_separator
+    Content-Type: application/pdf
+    Content-Range: bytes 234-639/8000
 
-...the first range...
---String_separator
-Content-Type: application/pdf
-Content-Range: bytes 4590-7999/8000
+    ...the first range...
+    --String_separator
+    Content-Type: application/pdf
+    Content-Range: bytes 4590-7999/8000
 
-...the second range
---String_separator--</pre>
+    ...the second range
+    --String_separator--
 
-<h2 id="Specifications">Specifications</h2>
+## Specifications
 
 {{Specifications}}
 
-<h2 id="Browser_compatibility">Browser compatibility</h2>
+## Browser compatibility
 
-<p>{{Compat}}</p>
+{{Compat}}
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
-  <li>{{HTTPHeader("If-Range")}}</li>
-  <li>{{HTTPHeader("Range")}}</li>
-  <li>{{HTTPHeader("Content-Range")}}</li>
-  <li>{{HTTPHeader("Content-Type")}}</li>
-</ul>
+- {{HTTPHeader("If-Range")}}
+- {{HTTPHeader("Range")}}
+- {{HTTPHeader("Content-Range")}}
+- {{HTTPHeader("Content-Type")}}
diff --git a/files/en-us/web/http/status/300/index.md b/files/en-us/web/http/status/300/index.md
index a94e076d2cbbdc3..f7b5c7bf18135b6 100644
--- a/files/en-us/web/http/status/300/index.md
+++ b/files/en-us/web/http/status/300/index.md
@@ -2,45 +2,35 @@
 title: 300 Multiple Choices
 slug: Web/HTTP/Status/300
 tags:
-- HTTP
-- HTTP Status Code
-- Reference
-- Status code
+  - HTTP
+  - HTTP Status Code
+  - Reference
+  - Status code
 ---
-<div>{{HTTPSidebar}}</div>
-
-<p>The HTTP <code><strong>300 Multiple Choices</strong></code> redirect status response
-	code indicates that the request has more than one possible responses. The user-agent
-	or the user should choose one of them. As there is no standardized way of choosing one
-	of the responses, this response code is very rarely used.</p>
-
-<p>If the server has a preferred choice, it should generate a {{HTTPHeader("Location")}}
-	header.</p>
-
-<h2 id="Status">Status</h2>
-
-<pre class="brush: html">300 Multiple Choices
-</pre>
-
-<h2 id="Specifications">Specifications</h2>
-
-<table class="standard-table">
-	<tbody>
-		<tr>
-			<th scope="col">Specification</th>
-			<th scope="col">Title</th>
-		</tr>
-		<tr>
-			<td>{{RFC("7231", "300 Multiple Choices" , "6.4.1")}}</td>
-			<td>Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content</td>
-		</tr>
-	</tbody>
-</table>
-
-<h2 id="See_also">See also</h2>
-
-<ul>
-	<li>{{HTTPStatus("301")}} <code>Moved Permanently</code></li>
-	<li>{{HTTPStatus("302")}} <code>Found</code>, the temporary redirect</li>
-	<li>{{HTTPStatus("308")}} <code>Permanent Redirect</code></li>
-</ul>
+{{HTTPSidebar}}
+
+The HTTP **`300 Multiple Choices`** redirect status response
+code indicates that the request has more than one possible responses. The user-agent
+or the user should choose one of them. As there is no standardized way of choosing one
+of the responses, this response code is very rarely used.
+
+If the server has a preferred choice, it should generate a {{HTTPHeader("Location")}}
+header.
+
+## Status
+
+```html
+300 Multiple Choices
+```
+
+## Specifications
+
+| Specification                                                    | Title                                                         |
+| ---------------------------------------------------------------- | ------------------------------------------------------------- |
+| {{RFC("7231", "300 Multiple Choices" , "6.4.1")}} | Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content |
+
+## See also
+
+- {{HTTPStatus("301")}} `Moved Permanently`
+- {{HTTPStatus("302")}} `Found`, the temporary redirect
+- {{HTTPStatus("308")}} `Permanent Redirect`
diff --git a/files/en-us/web/http/status/301/index.md b/files/en-us/web/http/status/301/index.md
index 6083150a161a5d7..6a1fc04a3e8738f 100644
--- a/files/en-us/web/http/status/301/index.md
+++ b/files/en-us/web/http/status/301/index.md
@@ -8,39 +8,39 @@ tags:
   - Status code
 browser-compat: http.status.301
 ---
-<div>{{HTTPSidebar}}</div>
+{{HTTPSidebar}}
 
-<p>The HyperText Transfer Protocol (HTTP) <code><strong>301 Moved Permanently</strong></code> redirect status response code indicates that the resource requested has been definitively moved to the URL given by the {{HTTPHeader("Location")}} headers. A browser redirects to this page and search engines update their links to the resource (in 'SEO-speak', it is said that the 'link-juice' is sent to the new URL).</p>
+The HyperText Transfer Protocol (HTTP) **`301 Moved Permanently`** redirect status response code indicates that the resource requested has been definitively moved to the URL given by the {{HTTPHeader("Location")}} headers. A browser redirects to this page and search engines update their links to the resource (in 'SEO-speak', it is said that the 'link-juice' is sent to the new URL).
 
-<p>Even if the specification requires the method (and the body) not to be altered when the redirection is performed, not all user-agents align with it - you can still find this type of bugged software out there. It is therefore recommended to use the <code>301</code> code only as a response for {{HTTPMethod("GET")}} or {{HTTPMethod("HEAD")}} methods and to use the {{HTTPStatus("308", "308 Permanent Redirect")}} for {{HTTPMethod("POST")}} methods instead, as the method change is explicitly prohibited with this status.</p>
+Even if the specification requires the method (and the body) not to be altered when the redirection is performed, not all user-agents align with it - you can still find this type of bugged software out there. It is therefore recommended to use the `301` code only as a response for {{HTTPMethod("GET")}} or {{HTTPMethod("HEAD")}} methods and to use the {{HTTPStatus("308", "308 Permanent Redirect")}} for {{HTTPMethod("POST")}} methods instead, as the method change is explicitly prohibited with this status.
 
-<h2 id="Status">Status</h2>
+## Status
 
-<pre class="brush: html">301 Moved Permanently</pre>
+```html
+301 Moved Permanently
+```
 
-<h2 id="Example">Example</h2>
+## Example
 
-<h3 id="Client_request">Client request</h3>
+### Client request
 
-<pre>GET /index.php HTTP/1.1
-Host: www.example.org</pre>
+    GET /index.php HTTP/1.1
+    Host: www.example.org
 
-<h3 id="Server_response">Server response</h3>
+### Server response
 
-<pre>HTTP/1.1 301 Moved Permanently
-Location: http://www.example.org/index.asp</pre>
+    HTTP/1.1 301 Moved Permanently
+    Location: http://www.example.org/index.asp
 
-<h2 id="Specifications">Specifications</h2>
+## Specifications
 
 {{Specifications}}
 
-<h2 id="Browser_compatibility">Browser compatibility</h2>
+## Browser compatibility
 
-<p>{{Compat}}</p>
+{{Compat}}
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
- <li>{{HTTPStatus("308", "308 Permanent Redirect")}}</li>
- <li>{{HTTPStatus("302", "302 Found")}}, the temporary redirect</li>
-</ul>
+- {{HTTPStatus("308", "308 Permanent Redirect")}}
+- {{HTTPStatus("302", "302 Found")}}, the temporary redirect
diff --git a/files/en-us/web/http/status/302/index.md b/files/en-us/web/http/status/302/index.md
index 6ddd28ed7e58914..f53102f6edfd68d 100644
--- a/files/en-us/web/http/status/302/index.md
+++ b/files/en-us/web/http/status/302/index.md
@@ -2,50 +2,50 @@
 title: 302 Found
 slug: Web/HTTP/Status/302
 tags:
-- HTTP
-- HTTP Status Code
-- Reference
-- redirects
+  - HTTP
+  - HTTP Status Code
+  - Reference
+  - redirects
 browser-compat: http.status.302
 ---
-<div>{{HTTPSidebar}}</div>
+{{HTTPSidebar}}
 
-<p>The HyperText Transfer Protocol (HTTP) <code><strong>302 Found</strong></code> redirect
-  status response code indicates that the resource requested has been temporarily moved to
-  the URL given by the {{HTTPHeader("Location")}} header. A browser redirects to this page
-  but search engines don't update their links to the resource (in 'SEO-speak', it is said
-  that the 'link-juice' is not sent to the new URL).</p>
+The HyperText Transfer Protocol (HTTP) **`302 Found`** redirect
+status response code indicates that the resource requested has been temporarily moved to
+the URL given by the {{HTTPHeader("Location")}} header. A browser redirects to this page
+but search engines don't update their links to the resource (in 'SEO-speak', it is said
+that the 'link-juice' is not sent to the new URL).
 
-<p>Even if the specification requires the method (and the body) not to be altered when the
-  redirection is performed, not all user-agents conform here - you can still find this
-  type of bugged software out there. It is therefore recommended to set the
-  <code>302</code> code only as a response for {{HTTPMethod("GET")}} or
-  {{HTTPMethod("HEAD")}} methods and to use {{HTTPStatus("307", "307 Temporary
-  Redirect")}} instead, as the method change is explicitly prohibited in that case.</p>
+Even if the specification requires the method (and the body) not to be altered when the
+redirection is performed, not all user-agents conform here - you can still find this
+type of bugged software out there. It is therefore recommended to set the
+`302` code only as a response for {{HTTPMethod("GET")}} or
+{{HTTPMethod("HEAD")}} methods and to use {{HTTPStatus("307", "307 Temporary
+  Redirect")}} instead, as the method change is explicitly prohibited in that case.
 
-<p>In the cases where you want the method used to be changed to {{HTTPMethod("GET")}}, use
-  {{HTTPStatus("303", "303 See Other")}} instead. This is useful when you want to give a
-  response to a {{HTTPMethod("PUT")}} method that is not the uploaded resource but a
-  confirmation message such as: 'you successfully uploaded XYZ'.</p>
+In the cases where you want the method used to be changed to {{HTTPMethod("GET")}}, use
+{{HTTPStatus("303", "303 See Other")}} instead. This is useful when you want to give a
+response to a {{HTTPMethod("PUT")}} method that is not the uploaded resource but a
+confirmation message such as: 'you successfully uploaded XYZ'.
 
-<h2 id="Status">Status</h2>
+## Status
 
-<pre class="brush: html">302 Found</pre>
+```html
+302 Found
+```
 
-<h2 id="Specifications">Specifications</h2>
+## Specifications
 
 {{Specifications}}
 
-<h2 id="Browser_compatibility">Browser compatibility</h2>
+## Browser compatibility
 
-<p>{{Compat}}</p>
+{{Compat}}
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
-  <li>{{HTTPStatus("307", "307 Temporary Redirect")}}, the equivalent of this status code
-    where the method used never changes.</li>
-  <li>{{HTTPStatus("303", "303 See Other")}}, a temporary redirect that changes the method
-    used to {{HTTPMethod("GET")}}.</li>
-  <li>{{HTTPStatus("301", "301 Moved Permanently")}}, the permanent redirect.</li>
-</ul>
+- {{HTTPStatus("307", "307 Temporary Redirect")}}, the equivalent of this status code
+  where the method used never changes.
+- {{HTTPStatus("303", "303 See Other")}}, a temporary redirect that changes the method
+  used to {{HTTPMethod("GET")}}.
+- {{HTTPStatus("301", "301 Moved Permanently")}}, the permanent redirect.
diff --git a/files/en-us/web/http/status/303/index.md b/files/en-us/web/http/status/303/index.md
index 6c24aff0e049081..eefcc689781510a 100644
--- a/files/en-us/web/http/status/303/index.md
+++ b/files/en-us/web/http/status/303/index.md
@@ -2,37 +2,37 @@
 title: 303 See Other
 slug: Web/HTTP/Status/303
 tags:
-- HTTP
-- HTTP Status Code
-- Reference
-- redirects
+  - HTTP
+  - HTTP Status Code
+  - Reference
+  - redirects
 browser-compat: http.status.303
 ---
-<p>{{HTTPSidebar}}</p>
+{{HTTPSidebar}}
 
-<p>The HyperText Transfer Protocol (HTTP) <code><strong>303 See Other</strong></code>
-  redirect status response code indicates that the redirects don't link to the newly
-  uploaded resources, but to another page (such as a confirmation page or an upload
-  progress page). This response code is usually sent back as a result of
-  {{HTTPMethod("PUT")}} or {{HTTPMethod("POST")}}. The method used to display this
-  redirected page is always {{HTTPMethod("GET")}}.</p>
+The HyperText Transfer Protocol (HTTP) **`303 See Other`**
+redirect status response code indicates that the redirects don't link to the newly
+uploaded resources, but to another page (such as a confirmation page or an upload
+progress page). This response code is usually sent back as a result of
+{{HTTPMethod("PUT")}} or {{HTTPMethod("POST")}}. The method used to display this
+redirected page is always {{HTTPMethod("GET")}}.
 
-<h2 id="Status">Status</h2>
+## Status
 
-<pre class="brush: html">303 See Other</pre>
+```html
+303 See Other
+```
 
-<h2 id="Specifications">Specifications</h2>
+## Specifications
 
 {{Specifications}}
 
-<h2 id="Browser_compatibility">Browser compatibility</h2>
+## Browser compatibility
 
-<p>{{Compat}}</p>
+{{Compat}}
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
-  <li>{{HTTPStatus("302", "302 Found")}}, the temporary redirect</li>
-  <li>{{HTTPStatus("307", "307 Temporary Redirect")}}, the equivalent of this status code
-    where the method used never changes.</li>
-</ul>
+- {{HTTPStatus("302", "302 Found")}}, the temporary redirect
+- {{HTTPStatus("307", "307 Temporary Redirect")}}, the equivalent of this status code
+  where the method used never changes.
diff --git a/files/en-us/web/http/status/304/index.md b/files/en-us/web/http/status/304/index.md
index aa1b2d7c584c5ed..214f6ca11bb51be 100644
--- a/files/en-us/web/http/status/304/index.md
+++ b/files/en-us/web/http/status/304/index.md
@@ -2,55 +2,51 @@
 title: 304 Not Modified
 slug: Web/HTTP/Status/304
 tags:
-- HTTP
-- Redirection
-- Reference
-- Status code
+  - HTTP
+  - Redirection
+  - Reference
+  - Status code
 browser-compat: http.status.304
 ---
-<div>{{HTTPSidebar}}</div>
+{{HTTPSidebar}}
 
-<p>The HTTP <code><strong>304 Not Modified</strong></code> client redirection response
-  code indicates that there is no need to retransmit the requested resources. It is an
-  implicit redirection to a cached resource. This happens when the request method is
-  {{glossary("Safe/HTTP", "safe")}}, like a {{HTTPMethod("GET")}} or a {{HTTPMethod("HEAD")}} request,
-  or when the request is conditional and uses a {{HTTPHeader("If-None-Match")}} or a
-  {{HTTPHeader("If-Modified-Since")}} header.</p>
+The HTTP **`304 Not Modified`** client redirection response
+code indicates that there is no need to retransmit the requested resources. It is an
+implicit redirection to a cached resource. This happens when the request method is
+{{glossary("Safe/HTTP", "safe")}}, like a {{HTTPMethod("GET")}} or a {{HTTPMethod("HEAD")}} request,
+or when the request is conditional and uses a {{HTTPHeader("If-None-Match")}} or a
+{{HTTPHeader("If-Modified-Since")}} header.
 
-<p>The equivalent {{HTTPStatus("200")}} <code>OK</code> response would have included the
-  headers {{HTTPHeader("Cache-Control")}}, {{HTTPHeader("Content-Location")}},
-  {{HTTPHeader("Date")}}, {{HTTPHeader("ETag")}}, {{HTTPHeader("Expires")}}, and
-  {{HTTPHeader("Vary")}}.</p>
+The equivalent {{HTTPStatus("200")}} `OK` response would have included the
+headers {{HTTPHeader("Cache-Control")}}, {{HTTPHeader("Content-Location")}},
+{{HTTPHeader("Date")}}, {{HTTPHeader("ETag")}}, {{HTTPHeader("Expires")}}, and
+{{HTTPHeader("Vary")}}.
 
-<div class="notecard note">
-  <p><strong>Note:</strong> Many <a href="/en-US/docs/Tools/Network_Monitor">developer tools' network panels</a>
-    of browsers create extraneous requests leading to <code>304</code> responses, so that
-    access to the local cache is visible to developers.</p>
-</div>
+> **Note:** Many [developer tools' network panels](/en-US/docs/Tools/Network_Monitor)
+> of browsers create extraneous requests leading to `304` responses, so that
+> access to the local cache is visible to developers.
 
-<h2 id="Status">Status</h2>
+## Status
 
-<pre class="brush: html">304 Not Modified</pre>
+```html
+304 Not Modified
+```
 
-<h2 id="Specifications">Specifications</h2>
+## Specifications
 
 {{Specifications}}
 
-<h2 id="Browser_compatibility">Browser compatibility</h2>
+## Browser compatibility
 
-<p>{{Compat}}</p>
+{{Compat}}
 
-<h2 id="Compatibility_Notes">Compatibility Notes</h2>
+## Compatibility Notes
 
-<ul>
-  <li>Browser behavior differs if this response erroneously includes a body on persistent
-    connections See <a href="/en-US/docs/Web/HTTP/Status/204">204 No Content</a> for more
-    detail.</li>
-</ul>
+- Browser behavior differs if this response erroneously includes a body on persistent
+  connections See [204 No Content](/en-US/docs/Web/HTTP/Status/204) for more
+  detail.
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
-  <li>{{HTTPHeader("If-Modified-Since")}}</li>
-  <li>{{HTTPHeader("If-None-Match")}}</li>
-</ul>
+- {{HTTPHeader("If-Modified-Since")}}
+- {{HTTPHeader("If-None-Match")}}
diff --git a/files/en-us/web/http/status/307/index.md b/files/en-us/web/http/status/307/index.md
index 4cc645468799281..d2cf2b2116562a9 100644
--- a/files/en-us/web/http/status/307/index.md
+++ b/files/en-us/web/http/status/307/index.md
@@ -2,52 +2,50 @@
 title: 307 Temporary Redirect
 slug: Web/HTTP/Status/307
 tags:
-- HTTP
-- HTTP Status Code
-- Reference
-- redirects
+  - HTTP
+  - HTTP Status Code
+  - Reference
+  - redirects
 browser-compat: http.status.307
 ---
-<div>{{HTTPSidebar}}</div>
+{{HTTPSidebar}}
 
-<p>{{Glossary("HTTP")}} <code><strong>307 Temporary Redirect</strong></code> redirect
-  status response code indicates that the resource requested has been temporarily moved to
-  the URL given by the {{HTTPHeader("Location")}} headers.</p>
+{{Glossary("HTTP")}} **`307 Temporary Redirect`** redirect
+status response code indicates that the resource requested has been temporarily moved to
+the URL given by the {{HTTPHeader("Location")}} headers.
 
-<p>The method and the body of the original request are reused to perform the redirected
-  request. In the cases where you want the method used to be changed to
-  {{HTTPMethod("GET")}}, use {{HTTPStatus("303", "303 See Other")}} instead. This is
-  useful when you want to give an answer to a {{HTTPMethod("PUT")}} method that is not the
-  uploaded resources, but a confirmation message (like "You successfully uploaded XYZ").
-</p>
+The method and the body of the original request are reused to perform the redirected
+request. In the cases where you want the method used to be changed to
+{{HTTPMethod("GET")}}, use {{HTTPStatus("303", "303 See Other")}} instead. This is
+useful when you want to give an answer to a {{HTTPMethod("PUT")}} method that is not the
+uploaded resources, but a confirmation message (like "You successfully uploaded XYZ").
 
-<p>The only difference between <code>307</code> and {{HTTPStatus("302")}} is that
-  <code>307</code> guarantees that the method and the body will not be changed when the
-  redirected request is made. With <code>302</code>, some old clients were incorrectly
-  changing the method to {{HTTPMethod("GET")}}: the behavior with non-<code>GET</code>
-  methods and <code>302</code> is then unpredictable on the Web, whereas the behavior with
-  <code>307</code> is predictable. For <code>GET</code> requests, their behavior is
-  identical.</p>
+The only difference between `307` and {{HTTPStatus("302")}} is that
+`307` guarantees that the method and the body will not be changed when the
+redirected request is made. With `302`, some old clients were incorrectly
+changing the method to {{HTTPMethod("GET")}}: the behavior with non-`GET`
+methods and `302` is then unpredictable on the Web, whereas the behavior with
+`307` is predictable. For `GET` requests, their behavior is
+identical.
 
-<h2 id="Status">Status</h2>
+## Status
 
-<pre class="brush: html">307 Temporary Redirect
-</pre>
+```html
+307 Temporary Redirect
+```
 
-<h2 id="Specifications">Specifications</h2>
+## Specifications
 
 {{Specifications}}
 
-<h2 id="Browser_compatibility">Browser compatibility</h2>
+## Browser compatibility
 
-<p>{{Compat}}</p>
+{{Compat}}
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
-  <li>{{HTTPStatus("302", "302 Found")}}, the equivalent of this status code, but that may
-    change the method used when it is not a {{HTTPMethod("GET")}}.</li>
-  <li>{{HTTPStatus("303", "303 See Other")}}, a temporary redirect that changes the method
-    used to {{HTTPMethod("GET")}}.</li>
-  <li>{{HTTPStatus("301", "301 Moved Permanently")}}, a permanent redirect</li>
-</ul>
+- {{HTTPStatus("302", "302 Found")}}, the equivalent of this status code, but that may
+  change the method used when it is not a {{HTTPMethod("GET")}}.
+- {{HTTPStatus("303", "303 See Other")}}, a temporary redirect that changes the method
+  used to {{HTTPMethod("GET")}}.
+- {{HTTPStatus("301", "301 Moved Permanently")}}, a permanent redirect
diff --git a/files/en-us/web/http/status/308/index.md b/files/en-us/web/http/status/308/index.md
index ff8982206a08152..5a31962a44124d7 100644
--- a/files/en-us/web/http/status/308/index.md
+++ b/files/en-us/web/http/status/308/index.md
@@ -2,48 +2,44 @@
 title: 308 Permanent Redirect
 slug: Web/HTTP/Status/308
 tags:
-- HTTP
-- HTTP Status Code
-- Reference
-- redirects
+  - HTTP
+  - HTTP Status Code
+  - Reference
+  - redirects
 browser-compat: http.status.308
 ---
-<div>{{HTTPSidebar}}</div>
+{{HTTPSidebar}}
 
-<p>The HyperText Transfer Protocol (HTTP)
-  <code><strong>308 Permanent Redirect</strong></code> redirect status response code
-  indicates that the resource requested has been definitively moved to the URL given by
-  the {{HTTPHeader("Location")}} headers. A browser redirects to this page and search
-  engines update their links to the resource (in 'SEO-speak', it is said that the
-  'link-juice' is sent to the new URL).</p>
+The HyperText Transfer Protocol (HTTP)
+**`308 Permanent Redirect`** redirect status response code
+indicates that the resource requested has been definitively moved to the URL given by
+the {{HTTPHeader("Location")}} headers. A browser redirects to this page and search
+engines update their links to the resource (in 'SEO-speak', it is said that the
+'link-juice' is sent to the new URL).
 
-<p>The request method and the body will not be altered, whereas {{HTTPStatus("301")}} may
-  incorrectly sometimes be changed to a {{HTTPMethod("GET")}} method.</p>
+The request method and the body will not be altered, whereas {{HTTPStatus("301")}} may
+incorrectly sometimes be changed to a {{HTTPMethod("GET")}} method.
 
-<div class="notecard note">
-  <p><strong>Note:</strong> Some Web applications may use the
-    <code>308 Permanent Redirect</code> in a non-standard way and for other purposes. For
-    example, Google Drive uses a <code>308 Resume Incomplete</code> response to indicate
-    to the client when an incomplete upload stalled. (See <a
-        href="https://developers.google.com/drive/v3/web/manage-uploads#resumable">Perform a resumable download</a> on Google Drive documentation.)
-  </p>
-</div>
+> **Note:** Some Web applications may use the
+> `308 Permanent Redirect` in a non-standard way and for other purposes. For
+> example, Google Drive uses a `308 Resume Incomplete` response to indicate
+> to the client when an incomplete upload stalled. (See [Perform a resumable download](https://developers.google.com/drive/v3/web/manage-uploads#resumable) on Google Drive documentation.)
 
-<h2 id="Status">Status</h2>
+## Status
 
-<pre class="brush: html">308 Permanent Redirect</pre>
+```html
+308 Permanent Redirect
+```
 
-<h2 id="Specifications">Specifications</h2>
+## Specifications
 
 {{Specifications}}
 
-<h2 id="Browser_compatibility">Browser compatibility</h2>
+## Browser compatibility
 
-<p>{{Compat}}</p>
+{{Compat}}
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
-  <li>{{HTTPStatus("301", "301 Moved Permanently")}}</li>
-  <li>{{HTTPStatus("302", "302 Found")}}, the temporary redirect</li>
-</ul>
+- {{HTTPStatus("301", "301 Moved Permanently")}}
+- {{HTTPStatus("302", "302 Found")}}, the temporary redirect
diff --git a/files/en-us/web/http/status/400/index.md b/files/en-us/web/http/status/400/index.md
index ee3c9dd622dce61..c9ee4119fa3ec2a 100644
--- a/files/en-us/web/http/status/400/index.md
+++ b/files/en-us/web/http/status/400/index.md
@@ -8,37 +8,24 @@ tags:
   - Reference
   - Status code
 ---
-<div>{{HTTPSidebar}}</div>
+{{HTTPSidebar}}
 
-<p>The HyperText Transfer Protocol (HTTP) <code><strong>400 Bad Request</strong></code> response status code indicates that the server cannot or will not process the request due to something that is perceived to be a client error (e.g., malformed request syntax, invalid request message framing, or deceptive request routing).</p>
+The HyperText Transfer Protocol (HTTP) **`400 Bad Request`** response status code indicates that the server cannot or will not process the request due to something that is perceived to be a client error (e.g., malformed request syntax, invalid request message framing, or deceptive request routing).
 
-<div class="notecard warning">
-  <p><strong>Warning:</strong> The client should not repeat this request without modification.</p>
-</div>
+> **Warning:** The client should not repeat this request without modification.
 
-<h2 id="Status">Status</h2>
+## Status
 
-<pre class="brush: html">400 Bad Request </pre>
+```html
+400 Bad Request 
+```
 
-<h2 id="Specifications">Specifications</h2>
+## Specifications
 
-<table class="standard-table">
- <thead>
-  <tr>
-   <th scope="col">Specification</th>
-   <th scope="col">Title</th>
-  </tr>
- </thead>
- <tbody>
-  <tr>
-   <td>{{RFC("7231", "400 Bad Request" , "6.5.1")}}</td>
-   <td>Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content</td>
-  </tr>
- </tbody>
-</table>
+| Specification                                                | Title                                                         |
+| ------------------------------------------------------------ | ------------------------------------------------------------- |
+| {{RFC("7231", "400 Bad Request" , "6.5.1")}} | Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content |
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
- <li><a href="https://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html" rel="noopener">HTTP/1.1: Status Code Definitions</a></li>
-</ul>
+- [HTTP/1.1: Status Code Definitions](https://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html)
diff --git a/files/en-us/web/http/status/401/index.md b/files/en-us/web/http/status/401/index.md
index 40d094a9602e028..e50ff2b02e8d64b 100644
--- a/files/en-us/web/http/status/401/index.md
+++ b/files/en-us/web/http/status/401/index.md
@@ -2,49 +2,49 @@
 title: 401 Unauthorized
 slug: Web/HTTP/Status/401
 tags:
-- Client error
-- HTTP
-- Reference
-- Status code
+  - Client error
+  - HTTP
+  - Reference
+  - Status code
 browser-compat: http.status.401
 ---
-<div>{{HTTPSidebar}}</div>
+{{HTTPSidebar}}
 
-<p>The HTTP <strong><code>401 Unauthorized</code></strong> client error status response
-  code indicates that the request has not been applied because it lacks valid
-  authentication credentials for the target resource.</p>
+The HTTP **`401 Unauthorized`** client error status response
+code indicates that the request has not been applied because it lacks valid
+authentication credentials for the target resource.
 
-<p>This status is sent with a {{HTTPHeader("WWW-Authenticate")}} header that contains
-  information on how to authorize correctly.</p>
+This status is sent with a {{HTTPHeader("WWW-Authenticate")}} header that contains
+information on how to authorize correctly.
 
-<p>This status is similar to {{HTTPStatus("403")}}, but in this case, authentication is
-  possible.</p>
+This status is similar to {{HTTPStatus("403")}}, but in this case, authentication is
+possible.
 
-<h2 id="Status">Status</h2>
+## Status
 
-<pre class="brush: html">401 Unauthorized</pre>
+```html
+401 Unauthorized
+```
 
-<h2 id="Example_response">Example response</h2>
+## Example response
 
-<pre>HTTP/1.1 401 Unauthorized
-Date: Wed, 21 Oct 2015 07:28:00 GMT
-WWW-Authenticate: Basic realm="Access to staging site"</pre>
+    HTTP/1.1 401 Unauthorized
+    Date: Wed, 21 Oct 2015 07:28:00 GMT
+    WWW-Authenticate: Basic realm="Access to staging site"
 
-<h2 id="Specifications">Specifications</h2>
+## Specifications
 
 {{Specifications}}
 
-<h2 id="Browser_compatibility">Browser compatibility</h2>
+## Browser compatibility
 
-<p>{{Compat}}</p>
+{{Compat}}
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
-  <li><a href="/en-US/docs/Web/HTTP/Authentication">HTTP authentication</a></li>
-  <li>{{HTTPHeader("WWW-Authenticate")}}</li>
-  <li>{{HTTPHeader("Authorization")}}</li>
-  <li>{{HTTPHeader("Proxy-Authorization")}}</li>
-  <li>{{HTTPHeader("Proxy-Authenticate")}}</li>
-  <li>{{HTTPStatus("403")}}, {{HTTPStatus("407")}}</li>
-</ul>
+- [HTTP authentication](/en-US/docs/Web/HTTP/Authentication)
+- {{HTTPHeader("WWW-Authenticate")}}
+- {{HTTPHeader("Authorization")}}
+- {{HTTPHeader("Proxy-Authorization")}}
+- {{HTTPHeader("Proxy-Authenticate")}}
+- {{HTTPStatus("403")}}, {{HTTPStatus("407")}}
diff --git a/files/en-us/web/http/status/402/index.md b/files/en-us/web/http/status/402/index.md
index c40d14504930269..b01f1b42702cbc8 100644
--- a/files/en-us/web/http/status/402/index.md
+++ b/files/en-us/web/http/status/402/index.md
@@ -8,45 +8,35 @@ tags:
   - Status code
 browser-compat: http.status.402
 ---
-<p>{{HTTPSidebar}}{{SeeCompatTable}}</p>
+{{HTTPSidebar}}{{SeeCompatTable}}
 
-<p>The HTTP <strong><code>402 Payment Required</code></strong> is a nonstandard client error status response code that is reserved for future use.</p>
+The HTTP **`402 Payment Required`** is a nonstandard client error status response code that is reserved for future use.
 
-<p>Sometimes, this code indicates that the request can not be processed until the client makes a payment. Originally it was created to enable digital cash or (micro) payment systems and would indicate that the requested content is not available until the client makes a payment. However, no standard use convention exists and different entities use it in different contexts.</p>
+Sometimes, this code indicates that the request can not be processed until the client makes a payment. Originally it was created to enable digital cash or (micro) payment systems and would indicate that the requested content is not available until the client makes a payment. However, no standard use convention exists and different entities use it in different contexts.
 
-<h2 id="Status">Status</h2>
+## Status
 
-<pre class="brush: html">402 Payment Required</pre>
+```html
+402 Payment Required
+```
 
-<h2 id="Example_response">Example response</h2>
+## Example response
 
-<pre class="brush: bash">HTTP/1.1 402 Payment Required
+```bash
+HTTP/1.1 402 Payment Required
 Date: Wed, 21 Oct 2015 07:28:00 GMT
-</pre>
-
-<h2 id="Specifications">Specifications</h2>
-
-<table class="standard-table">
- <thead>
-  <tr>
-   <th scope="col">Specification</th>
-   <th scope="col">Title</th>
-  </tr>
- </thead>
- <tbody>
-  <tr>
-   <td>{{RFC("7231", "402 Payment Required" , "6.5.2")}}</td>
-   <td>HTTP/1.1: Semantics and Content</td>
-  </tr>
- </tbody>
-</table>
-
-<h2 id="Browser_compatibility">Browser compatibility</h2>
-
-<p>{{Compat}}</p>
-
-<h2 id="See_also">See also</h2>
-
-<ul>
- <li><a href="/en-US/docs/Web/HTTP/Authentication">HTTP authentication</a></li>
-</ul>
+```
+
+## Specifications
+
+| Specification                                                    | Title                           |
+| ---------------------------------------------------------------- | ------------------------------- |
+| {{RFC("7231", "402 Payment Required" , "6.5.2")}} | HTTP/1.1: Semantics and Content |
+
+## Browser compatibility
+
+{{Compat}}
+
+## See also
+
+- [HTTP authentication](/en-US/docs/Web/HTTP/Authentication)
diff --git a/files/en-us/web/http/status/403/index.md b/files/en-us/web/http/status/403/index.md
index 48a7000f46e38d8..d39281f6a7c8f10 100644
--- a/files/en-us/web/http/status/403/index.md
+++ b/files/en-us/web/http/status/403/index.md
@@ -8,33 +8,32 @@ tags:
   - Status code
 browser-compat: http.status.403
 ---
-<div>{{HTTPSidebar}}</div>
+{{HTTPSidebar}}
 
-<p>The HTTP <strong><code>403 Forbidden</code></strong> client error status response code indicates that the server understood the request but refuses to authorize it.</p>
+The HTTP **`403 Forbidden`** client error status response code indicates that the server understood the request but refuses to authorize it.
 
-<p>This status is similar to {{HTTPStatus("401")}}, but in this case, re-authenticating will make no difference. The access is permanently forbidden and tied to the application logic, such as insufficient rights to a resource.</p>
+This status is similar to {{HTTPStatus("401")}}, but in this case, re-authenticating will make no difference. The access is permanently forbidden and tied to the application logic, such as insufficient rights to a resource.
 
-<h2 id="Status">Status</h2>
+## Status
 
-<pre class="brush: html">403 Forbidden</pre>
+```html
+403 Forbidden
+```
 
-<h2 id="Example_response">Example response</h2>
+## Example response
 
-<pre>HTTP/1.1 403 Forbidden
-Date: Wed, 21 Oct 2015 07:28:00 GMT
-</pre>
+    HTTP/1.1 403 Forbidden
+    Date: Wed, 21 Oct 2015 07:28:00 GMT
 
-<h2 id="Specifications">Specifications</h2>
+## Specifications
 
 {{Specifications}}
 
-<h2 id="Browser_compatibility">Browser compatibility</h2>
+## Browser compatibility
 
-<p>{{Compat}}</p>
+{{Compat}}
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
- <li>{{HTTPStatus("401")}}</li>
- <li><a href="https://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html" rel="noopener">HTTP/1.1: Status Code Definitions</a></li>
-</ul>
+- {{HTTPStatus("401")}}
+- [HTTP/1.1: Status Code Definitions](https://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html)
diff --git a/files/en-us/web/http/status/404/index.md b/files/en-us/web/http/status/404/index.md
index 27f41439af08ee9..f759173cae7b734 100644
--- a/files/en-us/web/http/status/404/index.md
+++ b/files/en-us/web/http/status/404/index.md
@@ -8,41 +8,39 @@ tags:
   - Status code
 browser-compat: http.status.404
 ---
-<div>{{HTTPSidebar}}</div>
+{{HTTPSidebar}}
 
-<p>The HTTP <code><strong>404 Not Found</strong></code> client error response code indicates that the server can't find the requested resource. Links that lead to a 404 page are often called broken or dead links and can be subject to <a href="https://en.wikipedia.org/wiki/Link_rot">link rot</a>.</p>
+The HTTP **`404 Not Found`** client error response code indicates that the server can't find the requested resource. Links that lead to a 404 page are often called broken or dead links and can be subject to [link rot](https://en.wikipedia.org/wiki/Link_rot).
 
-<p>A 404 status code does not indicate whether the resource is temporarily or permanently missing. But if a resource is permanently removed, a {{HTTPStatus("410")}} (Gone) should be used instead of a 404 status.</p>
+A 404 status code does not indicate whether the resource is temporarily or permanently missing. But if a resource is permanently removed, a {{HTTPStatus("410")}} (Gone) should be used instead of a 404 status.
 
-<h2 id="Status">Status</h2>
+## Status
 
-<pre class="brush: html">404 Not Found</pre>
+```html
+404 Not Found
+```
 
-<h2 id="Custom_error_pages">Custom error pages</h2>
+## Custom error pages
 
-<p>Many web sites customize the look of a 404 page to be more helpful to the user and provide guidance on what to do next. Apache servers can be configured using an <code>.htaccess</code> file and a code snippet like the following example.</p>
+Many web sites customize the look of a 404 page to be more helpful to the user and provide guidance on what to do next. Apache servers can be configured using an `.htaccess` file and a code snippet like the following example.
 
-<pre class="brush: bash">ErrorDocument 404 /notfound.html</pre>
+```bash
+ErrorDocument 404 /notfound.html
+```
 
-<p>For an example of a custom 404 page, see <a href="/en-US/404">MDN's 404 page</a>.</p>
+For an example of a custom 404 page, see [MDN's 404 page](/en-US/404).
 
-<div class="notecard note">
-  <p><strong>Note:</strong> Custom design is a good thing, in moderation. Feel free to make your 404 page humorous and human, but don't confuse your users.</p>
-</div>
+> **Note:** Custom design is a good thing, in moderation. Feel free to make your 404 page humorous and human, but don't confuse your users.
 
-<h2 id="Specifications">Specifications</h2>
+## Specifications
 
 {{Specifications}}
 
-<h2 id="Browser_compatibility">Browser compatibility</h2>
+## Browser compatibility
 
-<p>{{Compat}}</p>
+{{Compat}}
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
- <li>{{HTTPStatus("410")}}</li>
- <li>
-  <p>{{interwiki("wikipedia", "HTTP_404", "Wikipedia: HTTP 404")}}</p>
- </li>
-</ul>
+- {{HTTPStatus("410")}}
+- {{interwiki("wikipedia", "HTTP_404", "Wikipedia: HTTP 404")}}
diff --git a/files/en-us/web/http/status/405/index.md b/files/en-us/web/http/status/405/index.md
index 96c45359e9fad80..fe8473305771523 100644
--- a/files/en-us/web/http/status/405/index.md
+++ b/files/en-us/web/http/status/405/index.md
@@ -8,38 +8,27 @@ tags:
   - Reference
   - Status code
 ---
-<div>{{HTTPSidebar}}</div>
+{{HTTPSidebar}}
 
-<p>The HyperText Transfer Protocol (HTTP) <code><strong>405 Method Not Allowed</strong></code> response status code indicates that the request method is known by the server but is not supported by the target resource.</p>
+The HyperText Transfer Protocol (HTTP) **`405 Method Not Allowed`** response status code indicates that the request method is known by the server but is not supported by the target resource.
 
-<p>The server <strong>must</strong> generate an <strong><code>Allow</code></strong> header field in a 405 response containing a list of the target resource's currently supported methods.</p>
+The server **must** generate an **`Allow`** header field in a 405 response containing a list of the target resource's currently supported methods.
 
-<h2 id="Status">Status</h2>
+## Status
 
-<pre class="brush: html">405 Method Not Allowed</pre>
+```html
+405 Method Not Allowed
+```
 
-<h2 id="Specifications">Specifications</h2>
+## Specifications
 
-<table class="standard-table">
- <thead>
-  <tr>
-   <th scope="col">Specification</th>
-   <th scope="col">Title</th>
-  </tr>
- </thead>
- <tbody>
-  <tr>
-   <td>{{RFC("7231", "405 Method Not Allowed" , "6.5.5")}}</td>
-   <td>Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content</td>
-  </tr>
- </tbody>
-</table>
+| Specification                                                        | Title                                                         |
+| -------------------------------------------------------------------- | ------------------------------------------------------------- |
+| {{RFC("7231", "405 Method Not Allowed" , "6.5.5")}} | Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content |
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
- <li>{{HTTPHeader("Allow")}}</li>
- <li><a href="https://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html" rel="noopener">HTTP/1.1: Status Code Definitions</a></li>
- <li><a href="https://kinsta.com/blog/405-method-not-allowed-error/">How to Fix 405 Method Not Allowed</a></li>
- <li><a href="https://docs.microsoft.com/en-us/aspnet/web-api/overview/testing-and-debugging/troubleshooting-http-405-errors-after-publishing-web-api-applications">Troubleshooting HTTP 405</a></li>
-</ul>
+- {{HTTPHeader("Allow")}}
+- [HTTP/1.1: Status Code Definitions](https://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html)
+- [How to Fix 405 Method Not Allowed](https://kinsta.com/blog/405-method-not-allowed-error/)
+- [Troubleshooting HTTP 405](https://docs.microsoft.com/en-us/aspnet/web-api/overview/testing-and-debugging/troubleshooting-http-405-errors-after-publishing-web-api-applications)
diff --git a/files/en-us/web/http/status/406/index.md b/files/en-us/web/http/status/406/index.md
index baf3fdfb87266ef..308015f6f08e924 100644
--- a/files/en-us/web/http/status/406/index.md
+++ b/files/en-us/web/http/status/406/index.md
@@ -2,53 +2,50 @@
 title: 406 Not Acceptable
 slug: Web/HTTP/Status/406
 tags:
-- HTTP
-- Reference
-- Status code
+  - HTTP
+  - Reference
+  - Status code
 browser-compat: http.status.406
 ---
-<div>{{HTTPSidebar}}</div>
+{{HTTPSidebar}}
 
-<p>The HyperText Transfer Protocol (HTTP) <code><strong>406 Not Acceptable</strong></code>
-  client error response code indicates that the server cannot produce a response matching
-  the list of acceptable values defined in the request's proactive <a
-    href="/en-US/docs/Web/HTTP/Content_negotiation">content negotiation</a> headers, and
-  that the server is unwilling to supply a default representation.</p>
+The HyperText Transfer Protocol (HTTP) **`406 Not Acceptable`**
+client error response code indicates that the server cannot produce a response matching
+the list of acceptable values defined in the request's proactive [content negotiation](/en-US/docs/Web/HTTP/Content_negotiation) headers, and
+that the server is unwilling to supply a default representation.
 
-<p>Proactive content negotiation headers include:</p>
+Proactive content negotiation headers include:
 
-<ul>
-  <li>{{HTTPHeader("Accept")}}</li>
-  <li>{{HTTPHeader("Accept-Encoding")}}</li>
-  <li>{{HTTPHeader("Accept-Language")}}</li>
-</ul>
+- {{HTTPHeader("Accept")}}
+- {{HTTPHeader("Accept-Encoding")}}
+- {{HTTPHeader("Accept-Language")}}
 
-<p>In practice, this error is very rarely used. Instead of responding using this error
-  code, which would be cryptic for the end user and difficult to fix, servers ignore the
-  relevant header and serve an actual page to the user. It is assumed that even if the
-  user won't be completely happy, they will prefer this to an error code.</p>
+In practice, this error is very rarely used. Instead of responding using this error
+code, which would be cryptic for the end user and difficult to fix, servers ignore the
+relevant header and serve an actual page to the user. It is assumed that even if the
+user won't be completely happy, they will prefer this to an error code.
 
-<p>If a server returns such an error status, the body of the message should contain the
-  list of the available representations of the resources, allowing the user to choose
-  among them.</p>
+If a server returns such an error status, the body of the message should contain the
+list of the available representations of the resources, allowing the user to choose
+among them.
 
-<h2 id="Status">Status</h2>
+## Status
 
-<pre class="brush: html">406 Not Acceptable</pre>
+```html
+406 Not Acceptable
+```
 
-<h2 id="Specifications">Specifications</h2>
+## Specifications
 
 {{Specifications}}
 
-<h2 id="Browser_compatibility">Browser compatibility</h2>
+## Browser compatibility
 
-<p>{{Compat}}</p>
+{{Compat}}
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
-  <li>{{HTTPHeader("Accept")}}</li>
-  <li>{{HTTPHeader("Accept-Encoding")}}</li>
-  <li>{{HTTPHeader("Accept-Language")}}</li>
-  <li>HTTP <a href="/en-US/docs/Web/HTTP/Content_negotiation">content negotiation</a></li>
-</ul>
+- {{HTTPHeader("Accept")}}
+- {{HTTPHeader("Accept-Encoding")}}
+- {{HTTPHeader("Accept-Language")}}
+- HTTP [content negotiation](/en-US/docs/Web/HTTP/Content_negotiation)
diff --git a/files/en-us/web/http/status/407/index.md b/files/en-us/web/http/status/407/index.md
index 80159ee5676d857..f4e7f895dd01b96 100644
--- a/files/en-us/web/http/status/407/index.md
+++ b/files/en-us/web/http/status/407/index.md
@@ -2,47 +2,47 @@
 title: 407 Proxy Authentication Required
 slug: Web/HTTP/Status/407
 tags:
-- Client error
-- HTTP
-- Reference
-- Status code
+  - Client error
+  - HTTP
+  - Reference
+  - Status code
 browser-compat: http.status.407
 ---
-<div>{{HTTPSidebar}}</div>
+{{HTTPSidebar}}
 
-<p>The HTTP <strong><code>407 Proxy Authentication Required </code></strong> client error
-  status response code indicates that the request has not been applied because it lacks
-  valid authentication credentials for a {{Glossary("proxy server")}} that is between the
-  browser and the server that can access the requested resource.</p>
+The HTTP **`407 Proxy Authentication Required `**client error
+status response code indicates that the request has not been applied because it lacks
+valid authentication credentials for a {{Glossary("proxy server")}} that is between the
+browser and the server that can access the requested resource.
 
-<p>This status is sent with a {{HTTPHeader("Proxy-Authenticate")}} header that contains
-  information on how to authorize correctly.</p>
+This status is sent with a {{HTTPHeader("Proxy-Authenticate")}} header that contains
+information on how to authorize correctly.
 
-<h2 id="Status">Status</h2>
+## Status
 
-<pre class="brush: html">407 Proxy Authentication Required </pre>
+```html
+407 Proxy Authentication Required 
+```
 
-<h2 id="Example_response">Example response</h2>
+## Example response
 
-<pre>HTTP/1.1 407 Proxy Authentication Required
-Date: Wed, 21 Oct 2015 07:28:00 GMT
-Proxy-Authenticate: Basic realm="Access to internal site"</pre>
+    HTTP/1.1 407 Proxy Authentication Required
+    Date: Wed, 21 Oct 2015 07:28:00 GMT
+    Proxy-Authenticate: Basic realm="Access to internal site"
 
-<h2 id="Specifications">Specifications</h2>
+## Specifications
 
 {{Specifications}}
 
-<h2 id="Browser_compatibility">Browser compatibility</h2>
+## Browser compatibility
 
-<p>{{Compat}}</p>
+{{Compat}}
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
-  <li><a href="/en-US/docs/Web/HTTP/Authentication">HTTP authentication</a></li>
-  <li>{{HTTPHeader("WWW-Authenticate")}}</li>
-  <li>{{HTTPHeader("Authorization")}}</li>
-  <li>{{HTTPHeader("Proxy-Authorization")}}</li>
-  <li>{{HTTPHeader("Proxy-Authenticate")}}</li>
-  <li>{{HTTPStatus("401")}}, {{HTTPStatus("403")}}</li>
-</ul>
+- [HTTP authentication](/en-US/docs/Web/HTTP/Authentication)
+- {{HTTPHeader("WWW-Authenticate")}}
+- {{HTTPHeader("Authorization")}}
+- {{HTTPHeader("Proxy-Authorization")}}
+- {{HTTPHeader("Proxy-Authenticate")}}
+- {{HTTPStatus("401")}}, {{HTTPStatus("403")}}
diff --git a/files/en-us/web/http/status/408/index.md b/files/en-us/web/http/status/408/index.md
index 178a3d676e4afe0..73f6c2b4008a634 100644
--- a/files/en-us/web/http/status/408/index.md
+++ b/files/en-us/web/http/status/408/index.md
@@ -2,53 +2,42 @@
 title: 408 Request Timeout
 slug: Web/HTTP/Status/408
 tags:
-- Client error
-- HTTP
-- HTTP Status Code
-- Reference
-- Status code
+  - Client error
+  - HTTP
+  - HTTP Status Code
+  - Reference
+  - Status code
 ---
-<div>{{HTTPSidebar}}</div>
-
-<p>The HyperText Transfer Protocol (HTTP)
-  <code><strong>408 Request Timeout</strong></code> response status code means that the
-  server would like to shut down this unused connection. It is sent on an idle connection
-  by some servers, <em>even without any previous request by the client</em>.</p>
-
-<p>A server should send the "close" {{HTTPHeader("Connection")}} header field in the
-  response, since <code>408</code> implies that the server has decided to close the
-  connection rather than continue waiting.</p>
-
-<p>This response is used much more since some browsers, like Chrome, Firefox 27+, and IE9,
-  use HTTP pre-connection mechanisms to speed up surfing.</p>
-
-<div class="notecard note">
-  <p><strong>Note:</strong> some servers merely shut down the connection without sending
-    this message.</p>
-</div>
-
-<h2 id="Status">Status</h2>
-
-<pre class="brush: html">408 Request Timeout</pre>
-
-<h2 id="Specifications">Specifications</h2>
-
-<table class="standard-table">
-  <tbody>
-    <tr>
-      <th scope="col">Specification</th>
-      <th scope="col">Title</th>
-    </tr>
-    <tr>
-      <td>{{RFC("7231", "408 Request Timeout" , "6.5.7")}}</td>
-      <td>Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content</td>
-    </tr>
-  </tbody>
-</table>
-
-<h2 id="See_also">See also</h2>
-
-<ul>
-  <li>{{HTTPHeader("Connection")}}</li>
-  <li>{{HTTPHeader("X-DNS-Prefetch-Control")}}</li>
-</ul>
+{{HTTPSidebar}}
+
+The HyperText Transfer Protocol (HTTP)
+**`408 Request Timeout`** response status code means that the
+server would like to shut down this unused connection. It is sent on an idle connection
+by some servers, _even without any previous request by the client_.
+
+A server should send the "close" {{HTTPHeader("Connection")}} header field in the
+response, since `408` implies that the server has decided to close the
+connection rather than continue waiting.
+
+This response is used much more since some browsers, like Chrome, Firefox 27+, and IE9,
+use HTTP pre-connection mechanisms to speed up surfing.
+
+> **Note:** some servers merely shut down the connection without sending
+> this message.
+
+## Status
+
+```html
+408 Request Timeout
+```
+
+## Specifications
+
+| Specification                                                    | Title                                                         |
+| ---------------------------------------------------------------- | ------------------------------------------------------------- |
+| {{RFC("7231", "408 Request Timeout" , "6.5.7")}} | Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content |
+
+## See also
+
+- {{HTTPHeader("Connection")}}
+- {{HTTPHeader("X-DNS-Prefetch-Control")}}
diff --git a/files/en-us/web/http/status/409/index.md b/files/en-us/web/http/status/409/index.md
index 7addb68defa49c1..c90babe56a61a91 100644
--- a/files/en-us/web/http/status/409/index.md
+++ b/files/en-us/web/http/status/409/index.md
@@ -8,26 +8,26 @@ tags:
   - Reference
 browser-compat: http.status.409
 ---
-<div>{{HTTPSidebar}}</div>
+{{HTTPSidebar}}
 
-<p>The HTTP <code><strong>409 Conflict</strong></code> response status code indicates a request conflict with current state of the target resource.</p>
+The HTTP **`409 Conflict`** response status code indicates a request conflict with current state of the target resource.
 
-<p>Conflicts are most likely to occur in response to a {{HTTPMethod("PUT")}} request. For example, you may get a 409 response when uploading a file which is older than the one already on the server resulting in a version control conflict.</p>
+Conflicts are most likely to occur in response to a {{HTTPMethod("PUT")}} request. For example, you may get a 409 response when uploading a file which is older than the one already on the server resulting in a version control conflict.
 
-<h2 id="Status">Status</h2>
+## Status
 
-<pre class="brush: html">409 Conflict</pre>
+```html
+409 Conflict
+```
 
-<h2 id="Specifications">Specifications</h2>
+## Specifications
 
 {{Specifications}}
 
-<h2 id="Browser_compatibility">Browser compatibility</h2>
+## Browser compatibility
 
-<p>{{Compat}}</p>
+{{Compat}}
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
- <li>{{HTTPMethod("PUT")}}</li>
-</ul>
+- {{HTTPMethod("PUT")}}
diff --git a/files/en-us/web/http/status/410/index.md b/files/en-us/web/http/status/410/index.md
index 2453a2ffeccaab2..fdd589b811ba7a2 100644
--- a/files/en-us/web/http/status/410/index.md
+++ b/files/en-us/web/http/status/410/index.md
@@ -8,31 +8,29 @@ tags:
   - Status code
 browser-compat: http.status.410
 ---
-<div>{{HTTPSidebar}}</div>
+{{HTTPSidebar}}
 
-<p>The HyperText Transfer Protocol (HTTP) <code><strong>410 Gone</strong></code> client error response 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.</p>
+The HyperText Transfer Protocol (HTTP) **`410 Gone`** client error response 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.
 
-<p>If you don't know whether this condition is temporary or permanent, a {{HTTPStatus(404)}} status code should be used instead.</p>
+If you don't know whether this condition is temporary or permanent, a {{HTTPStatus(404)}} status code should be used instead.
 
-<div class="notecard note">
-  <p><strong>Note:</strong> A 410 response is cacheable by default.</p>
-</div>
+> **Note:** A 410 response is cacheable by default.
 
-<h2 id="Status">Status</h2>
+## Status
 
-<pre class="brush: html">410 Gone</pre>
+```html
+410 Gone
+```
 
-<h2 id="Specifications">Specifications</h2>
+## Specifications
 
 {{Specifications}}
 
-<h2 id="Browser_compatibility">Browser compatibility</h2>
+## Browser compatibility
 
-<p>{{Compat}}</p>
+{{Compat}}
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
-	<li>{{HTTPStatus(404)}}</li>
-	<li><a href="https://www.exai.com/blog/410-gone-client-error">410 gone</a></li>
-</ul>
+- {{HTTPStatus(404)}}
+- [410 gone](https://www.exai.com/blog/410-gone-client-error)
diff --git a/files/en-us/web/http/status/411/index.md b/files/en-us/web/http/status/411/index.md
index fe6bf00ea562d9a..1833ce15fe1decd 100644
--- a/files/en-us/web/http/status/411/index.md
+++ b/files/en-us/web/http/status/411/index.md
@@ -2,48 +2,37 @@
 title: 411 Length Required
 slug: Web/HTTP/Status/411
 tags:
-- Client error
-- HTTP
-- HTTP Status Code
-- Reference
-- Status code
+  - Client error
+  - HTTP
+  - HTTP Status Code
+  - Reference
+  - Status code
 ---
-<div>{{HTTPSidebar}}</div>
-
-<p>The HyperText Transfer Protocol (HTTP)
-  <code><strong>411 Length Required</strong></code> client error response code indicates
-  that the server refuses to accept the request without a defined
-  {{HTTPHeader("Content-Length")}} header.</p>
-
-<div class="notecard note">
-  <p><strong>Note:</strong> by specification, when sending data in a series of chunks, the
-    <code>Content-Length</code> header is omitted and at the beginning of each chunk you
-    need to add the length of the current chunk in hexadecimal format. See
-    {{HTTPHeader("Transfer-Encoding")}} for more details.</p>
-</div>
-
-<h2 id="Status">Status</h2>
-
-<pre class="brush: html">411 Length Required</pre>
-
-<h2 id="Specifications">Specifications</h2>
-
-<table class="standard-table">
-  <tbody>
-    <tr>
-      <th scope="col">Specification</th>
-      <th scope="col">Title</th>
-    </tr>
-    <tr>
-      <td>{{RFC("7231", "411 Length Required" , "6.5.10")}}</td>
-      <td>Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content</td>
-    </tr>
-  </tbody>
-</table>
-
-<h2 id="See_also">See also</h2>
-
-<ul>
-  <li>{{HTTPHeader("Content-Length")}}</li>
-  <li>{{HTTPHeader("Transfer-Encoding")}}</li>
-</ul>
+{{HTTPSidebar}}
+
+The HyperText Transfer Protocol (HTTP)
+**`411 Length Required`** client error response code indicates
+that the server refuses to accept the request without a defined
+{{HTTPHeader("Content-Length")}} header.
+
+> **Note:** by specification, when sending data in a series of chunks, the
+> `Content-Length` header is omitted and at the beginning of each chunk you
+> need to add the length of the current chunk in hexadecimal format. See
+> {{HTTPHeader("Transfer-Encoding")}} for more details.
+
+## Status
+
+```html
+411 Length Required
+```
+
+## Specifications
+
+| Specification                                                    | Title                                                         |
+| ---------------------------------------------------------------- | ------------------------------------------------------------- |
+| {{RFC("7231", "411 Length Required" , "6.5.10")}} | Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content |
+
+## See also
+
+- {{HTTPHeader("Content-Length")}}
+- {{HTTPHeader("Transfer-Encoding")}}
diff --git a/files/en-us/web/http/status/412/index.md b/files/en-us/web/http/status/412/index.md
index 6565b9a9cc3fa3c..923ac96cec02bf0 100644
--- a/files/en-us/web/http/status/412/index.md
+++ b/files/en-us/web/http/status/412/index.md
@@ -2,68 +2,66 @@
 title: 412 Precondition Failed
 slug: Web/HTTP/Status/412
 tags:
-- Error
-- HTTP
-- Reference
-- Status code
+  - Error
+  - HTTP
+  - Reference
+  - Status code
 browser-compat: http.status.412
 ---
-<div>{{HTTPSidebar}}</div>
+{{HTTPSidebar}}
 
-<p>The HyperText Transfer Protocol (HTTP)
-  <code><strong>412 Precondition Failed</strong></code> client error response code
-  indicates that access to the target resource has been denied. This happens with
-  conditional requests on methods other than {{HTTPMethod("GET")}} or
-  {{HTTPMethod("HEAD")}} when the condition defined by the
-  {{HTTPHeader("If-Unmodified-Since")}} or {{HTTPHeader("If-None-Match")}} headers is not
-  fulfilled. In that case, the request, usually an upload or a modification of a resource,
-  cannot be made and this error response is sent back.</p>
+The HyperText Transfer Protocol (HTTP)
+**`412 Precondition Failed`** client error response code
+indicates that access to the target resource has been denied. This happens with
+conditional requests on methods other than {{HTTPMethod("GET")}} or
+{{HTTPMethod("HEAD")}} when the condition defined by the
+{{HTTPHeader("If-Unmodified-Since")}} or {{HTTPHeader("If-None-Match")}} headers is not
+fulfilled. In that case, the request, usually an upload or a modification of a resource,
+cannot be made and this error response is sent back.
 
-<h2 id="Status">Status</h2>
+## Status
 
-<pre class="brush: html">412 Precondition Failed</pre>
+```html
+412 Precondition Failed
+```
 
-<h2 id="Examples">Examples</h2>
+## Examples
 
-<pre><code>ETag: "33a64df551425fcc55e4d42a148795d9f25f89d4"
-ETag: W/"0815"</code></pre>
+    ETag: "33a64df551425fcc55e4d42a148795d9f25f89d4"
+    ETag: W/"0815"
 
-<h3 id="Avoiding_mid-air_collisions">Avoiding mid-air collisions</h3>
+### Avoiding mid-air collisions
 
-<p>With the help of the <code>ETag</code> and the {{HTTPHeader("If-Match")}} headers, you
-  can detect mid-air edit collisions.</p>
+With the help of the `ETag` and the {{HTTPHeader("If-Match")}} headers, you
+can detect mid-air edit collisions.
 
-<p>For example, when editing MDN, the current wiki content is hashed and put into an
-  <code>Etag</code> in the response:</p>
+For example, when editing MDN, the current wiki content is hashed and put into an
+`Etag` in the response:
 
-<pre><code>ETag: "33a64df551425fcc55e4d42a148795d9f25f89d4"</code></pre>
+    ETag: "33a64df551425fcc55e4d42a148795d9f25f89d4"
 
-<p>When saving changes to a wiki page (posting data), the {{HTTPMethod("POST")}} request
-  will contain the {{HTTPHeader("If-Match")}} header containing the <code>ETag</code>
-  values to check freshness against.</p>
+When saving changes to a wiki page (posting data), the {{HTTPMethod("POST")}} request
+will contain the {{HTTPHeader("If-Match")}} header containing the `ETag`
+values to check freshness against.
 
-<pre><code>If-Match: "33a64df551425fcc55e4d42a148795d9f25f89d4"</code></pre>
+    If-Match: "33a64df551425fcc55e4d42a148795d9f25f89d4"
 
-<p>If the hashes don't match, it means that the document has been edited in-between and a
-  {{HTTPStatus("412")}} <code>Precondition Failed</code> error is thrown.</p>
+If the hashes don't match, it means that the document has been edited in-between and a
+{{HTTPStatus("412")}} `Precondition Failed` error is thrown.
 
-<h2 id="Specifications">Specifications</h2>
+## Specifications
 
 {{Specifications}}
 
-<h2 id="Browser_compatibility">Browser compatibility</h2>
+## Browser compatibility
 
-<p>The information below has been pulled from MDN's GitHub (<a
-    href="https://github.com/mdn/browser-compat-data">https://github.com/mdn/browser-compat-data</a>).
-</p>
+The information below has been pulled from MDN's GitHub (<https://github.com/mdn/browser-compat-data>).
 
-<p>{{Compat}}</p>
+{{Compat}}
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
-  <li>{{HTTPStatus("304")}}</li>
-  <li>{{HTTPHeader("If-Unmodified-Since")}}</li>
-  <li>{{HTTPHeader("If-None-Match")}}</li>
-  <li>{{HTTPStatus("428")}}</li>
-</ul>
+- {{HTTPStatus("304")}}
+- {{HTTPHeader("If-Unmodified-Since")}}
+- {{HTTPHeader("If-None-Match")}}
+- {{HTTPStatus("428")}}
diff --git a/files/en-us/web/http/status/413/index.md b/files/en-us/web/http/status/413/index.md
index de0d33fe5414922..4f36cf2570b7d46 100644
--- a/files/en-us/web/http/status/413/index.md
+++ b/files/en-us/web/http/status/413/index.md
@@ -8,34 +8,23 @@ tags:
   - Reference
   - Status code
 ---
-<div>{{HTTPSidebar}}</div>
+{{HTTPSidebar}}
 
-<p>The HTTP <code><strong>413 Payload Too Large</strong></code> response status code indicates that the request entity is larger than limits defined by server; the server might close the connection or return a {{HTTPHeader("Retry-After")}} header field.</p>
+The HTTP **`413 Payload Too Large`** response status code indicates that the request entity is larger than limits defined by server; the server might close the connection or return a {{HTTPHeader("Retry-After")}} header field.
 
-<h2 id="Status">Status</h2>
+## Status
 
-<pre class="brush: html">413 Payload Too Large</pre>
+```html
+413 Payload Too Large
+```
 
-<h2 id="Specifications">Specifications</h2>
+## Specifications
 
-<table class="standard-table">
- <thead>
-  <tr>
-   <th scope="col">Specification</th>
-   <th scope="col">Title</th>
-  </tr>
- </thead>
- <tbody>
-  <tr>
-   <td>{{RFC("7231", "413 Payload Too Large" , "6.5.11")}}</td>
-   <td>Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content</td>
-  </tr>
- </tbody>
-</table>
+| Specification                                                        | Title                                                         |
+| -------------------------------------------------------------------- | ------------------------------------------------------------- |
+| {{RFC("7231", "413 Payload Too Large" , "6.5.11")}} | Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content |
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
- <li>{{HTTPHeader("Connection")}}</li>
- <li>{{HTTPHeader("Retry-After")}}</li>
-</ul>
+- {{HTTPHeader("Connection")}}
+- {{HTTPHeader("Retry-After")}}
diff --git a/files/en-us/web/http/status/414/index.md b/files/en-us/web/http/status/414/index.md
index 16b77674d2d58ea..475d378228ebb8f 100644
--- a/files/en-us/web/http/status/414/index.md
+++ b/files/en-us/web/http/status/414/index.md
@@ -2,49 +2,37 @@
 title: 414 URI Too Long
 slug: Web/HTTP/Status/414
 tags:
-- Client error
-- HTTP
-- Reference
-- Status code
+  - Client error
+  - HTTP
+  - Reference
+  - Status code
 ---
-<div>{{HTTPSidebar}}</div>
-
-<p>The HTTP <code><strong>414 URI Too Long</strong></code> response status code indicates
-  that the URI requested by the client is longer than the server is willing to interpret.
-</p>
-
-<p>There are a few rare conditions when this might occur:</p>
-
-<ul>
-  <li>when a client has improperly converted a {{HTTPMethod("POST")}} request to a
-    {{HTTPMethod("GET")}} request with long query information,</li>
-  <li>when the client has descended into a loop of redirection (for example, a redirected
-    URI prefix that points to a suffix of itself),</li>
-  <li>or when the server is under attack by a client attempting to exploit potential
-    security holes.</li>
-</ul>
-
-<h2 id="Status">Status</h2>
-
-<pre class="brush: html">414 URI Too Long</pre>
-
-<h2 id="Specifications">Specifications</h2>
-
-<table class="standard-table">
-  <tbody>
-    <tr>
-      <th scope="col">Specification</th>
-      <th scope="col">Title</th>
-    </tr>
-    <tr>
-      <td>{{RFC("7231", "414 URI Too Long" , "6.5.12")}}</td>
-      <td>Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content</td>
-    </tr>
-  </tbody>
-</table>
-
-<h2 id="See_also">See also</h2>
-
-<ul>
-  <li>{{Glossary("URI")}}</li>
-</ul>
+{{HTTPSidebar}}
+
+The HTTP **`414 URI Too Long`** response status code indicates
+that the URI requested by the client is longer than the server is willing to interpret.
+
+There are a few rare conditions when this might occur:
+
+- when a client has improperly converted a {{HTTPMethod("POST")}} request to a
+  {{HTTPMethod("GET")}} request with long query information,
+- when the client has descended into a loop of redirection (for example, a redirected
+  URI prefix that points to a suffix of itself),
+- or when the server is under attack by a client attempting to exploit potential
+  security holes.
+
+## Status
+
+```html
+414 URI Too Long
+```
+
+## Specifications
+
+| Specification                                                | Title                                                         |
+| ------------------------------------------------------------ | ------------------------------------------------------------- |
+| {{RFC("7231", "414 URI Too Long" , "6.5.12")}} | Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content |
+
+## See also
+
+- {{Glossary("URI")}}
diff --git a/files/en-us/web/http/status/415/index.md b/files/en-us/web/http/status/415/index.md
index 57c75e5fb3bbe26..364d3f3092b127a 100644
--- a/files/en-us/web/http/status/415/index.md
+++ b/files/en-us/web/http/status/415/index.md
@@ -2,45 +2,36 @@
 title: 415 Unsupported Media Type
 slug: Web/HTTP/Status/415
 tags:
-- Client error
-- HTTP
-- HTTP Status Code
-- Reference
-- Status code
+  - Client error
+  - HTTP
+  - HTTP Status Code
+  - Reference
+  - Status code
 ---
-<div>{{HTTPSidebar}}</div>
-
-<p>The HTTP <code><strong>415 Unsupported Media Type</strong></code> client error response
-  code indicates that the server refuses to accept the request because the payload format
-  is in an unsupported format.</p>
-
-<p>The format problem might be due to the request's indicated
-  {{HTTPHeader("Content-Type")}} or {{HTTPHeader("Content-Encoding")}}, or as a result of
-  inspecting the data directly.</p>
-
-<h2 id="Status">Status</h2>
-
-<pre class="brush: html">415 Unsupported Media Type</pre>
-
-<h2 id="Specifications">Specifications</h2>
-
-<table class="standard-table">
-  <tbody>
-    <tr>
-      <th scope="col">Specification</th>
-      <th scope="col">Title</th>
-    </tr>
-    <tr>
-      <td>{{RFC("7231", "415 Unsupported Media Type" , "6.5.13")}}</td>
-      <td>Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content</td>
-    </tr>
-  </tbody>
-</table>
-
-<h2 id="See_also">See also</h2>
-
-<ul>
-  <li>{{HTTPHeader("Content-Type")}}</li>
-  <li>{{HTTPHeader("Content-Encoding")}}</li>
-  <li>{{HTTPHeader("Accept")}}</li>
-</ul>
+{{HTTPSidebar}}
+
+The HTTP **`415 Unsupported Media Type`** client error response
+code indicates that the server refuses to accept the request because the payload format
+is in an unsupported format.
+
+The format problem might be due to the request's indicated
+{{HTTPHeader("Content-Type")}} or {{HTTPHeader("Content-Encoding")}}, or as a result of
+inspecting the data directly.
+
+## Status
+
+```html
+415 Unsupported Media Type
+```
+
+## Specifications
+
+| Specification                                                                | Title                                                         |
+| ---------------------------------------------------------------------------- | ------------------------------------------------------------- |
+| {{RFC("7231", "415 Unsupported Media Type" , "6.5.13")}} | Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content |
+
+## See also
+
+- {{HTTPHeader("Content-Type")}}
+- {{HTTPHeader("Content-Encoding")}}
+- {{HTTPHeader("Accept")}}
diff --git a/files/en-us/web/http/status/416/index.md b/files/en-us/web/http/status/416/index.md
index 3c0106db85c6b3a..beb404de4cafd23 100644
--- a/files/en-us/web/http/status/416/index.md
+++ b/files/en-us/web/http/status/416/index.md
@@ -7,30 +7,30 @@ tags:
   - Status code
 browser-compat: http.status.416
 ---
-<div>{{HTTPSidebar}}</div>
+{{HTTPSidebar}}
 
-<p>The HyperText Transfer Protocol (HTTP) <code><strong>416 Range Not Satisfiable</strong></code> error response code indicates that a server cannot serve the requested ranges. The most likely reason is that the document doesn't contain such ranges, or that the {{HTTPHeader("Range")}} header value, though syntactically correct, doesn't make sense.</p>
+The HyperText Transfer Protocol (HTTP) **`416 Range Not Satisfiable`** error response code indicates that a server cannot serve the requested ranges. The most likely reason is that the document doesn't contain such ranges, or that the {{HTTPHeader("Range")}} header value, though syntactically correct, doesn't make sense.
 
-<p>The <code>416</code> response message contains a {{HTTPHeader("Content-Range")}} indicating an unsatisfied range (that is a <code>'*'</code>) followed by a <code>'/'</code> and the current length of the resource. E.g. <code>Content-Range: bytes */12777</code></p>
+The `416` response message contains a {{HTTPHeader("Content-Range")}} indicating an unsatisfied range (that is a `'*'`) followed by a `'/'` and the current length of the resource. E.g. `Content-Range: bytes */12777`
 
-<p>Faced with this error, browsers usually either abort the operation (for example, a download will be considered as non-resumable) or ask for the whole document again.</p>
+Faced with this error, browsers usually either abort the operation (for example, a download will be considered as non-resumable) or ask for the whole document again.
 
-<h2 id="Status">Status</h2>
+## Status
 
-<pre class="brush: html">416 Range Not Satisfiable</pre>
+```html
+416 Range Not Satisfiable
+```
 
-<h2 id="Specifications">Specifications</h2>
+## Specifications
 
 {{Specifications}}
 
-<h2 id="Browser_compatibility">Browser compatibility</h2>
+## Browser compatibility
 
-<p>{{Compat}}</p>
+{{Compat}}
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
- <li>{{HTTPStatus(206)}} <code>Partial Content</code></li>
- <li>{{HTTPHeader("Content-Range")}}</li>
- <li>{{HTTPHeader("Range")}}</li>
-</ul>
+- {{HTTPStatus(206)}} `Partial Content`
+- {{HTTPHeader("Content-Range")}}
+- {{HTTPHeader("Range")}}
diff --git a/files/en-us/web/http/status/417/index.md b/files/en-us/web/http/status/417/index.md
index 9a7f88fe4fe85d7..183ec68f8c0fb55 100644
--- a/files/en-us/web/http/status/417/index.md
+++ b/files/en-us/web/http/status/417/index.md
@@ -2,41 +2,32 @@
 title: 417 Expectation Failed
 slug: Web/HTTP/Status/417
 tags:
-- Client error
-- HTTP
-- HTTP Status Code
-- Reference
-- Status code
+  - Client error
+  - HTTP
+  - HTTP Status Code
+  - Reference
+  - Status code
 ---
-<div>{{HTTPSidebar}}</div>
+{{HTTPSidebar}}
 
-<p>The HTTP <strong><code>417 Expectation Failed</code></strong> client error response
-  code indicates that the expectation given in the request's {{HTTPHeader("Expect")}}
-  header could not be met.</p>
+The HTTP **`417 Expectation Failed`** client error response
+code indicates that the expectation given in the request's {{HTTPHeader("Expect")}}
+header could not be met.
 
-<p>See the {{HTTPHeader("Expect")}} header for more details.</p>
+See the {{HTTPHeader("Expect")}} header for more details.
 
-<h2 id="Status">Status</h2>
+## Status
 
-<pre class="brush: html">417 Expectation Failed</pre>
+```html
+417 Expectation Failed
+```
 
-<h2 id="Specifications">Specifications</h2>
+## Specifications
 
-<table class="standard-table">
-  <tbody>
-    <tr>
-      <th scope="col">Specification</th>
-      <th scope="col">Title</th>
-    </tr>
-    <tr>
-      <td>{{RFC("7231", "417 Expectation Failed" , "6.5.14")}}</td>
-      <td>Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content</td>
-    </tr>
-  </tbody>
-</table>
+| Specification                                                        | Title                                                         |
+| -------------------------------------------------------------------- | ------------------------------------------------------------- |
+| {{RFC("7231", "417 Expectation Failed" , "6.5.14")}} | Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content |
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
-  <li>{{HTTPHeader("Expect")}}</li>
-</ul>
+- {{HTTPHeader("Expect")}}
diff --git a/files/en-us/web/http/status/418/index.md b/files/en-us/web/http/status/418/index.md
index f33efb0c1f3301e..82991f7aa780a73 100644
--- a/files/en-us/web/http/status/418/index.md
+++ b/files/en-us/web/http/status/418/index.md
@@ -7,43 +7,29 @@ tags:
   - Reference
 browser-compat: http.status.418
 ---
-<p>{{HTTPSidebar}}</p>
+{{HTTPSidebar}}
 
-<p>The HTTP <strong><code>418 I'm a teapot</code></strong> client error response code indicates that the server refuses to brew coffee because it is, permanently, a teapot. A combined coffee/tea pot that is temporarily out of coffee should instead return 503. This error is a reference to Hyper Text Coffee Pot Control Protocol defined in April Fools' jokes in 1998 and 2014.</p>
+The HTTP **`418 I'm a teapot`** client error response code indicates that the server refuses to brew coffee because it is, permanently, a teapot. A combined coffee/tea pot that is temporarily out of coffee should instead return 503. This error is a reference to Hyper Text Coffee Pot Control Protocol defined in April Fools' jokes in 1998 and 2014.
 
-<p>Some websites use this response for requests they do not wish to handle, such as automated queries.</p>
+Some websites use this response for requests they do not wish to handle, such as automated queries.
 
-<h2 id="Status">Status</h2>
+## Status
 
-<pre class="brush: html">418 I'm a teapot</pre>
+```html
+418 I'm a teapot
+```
 
-<h2 id="Specifications">Specifications</h2>
+## Specifications
 
-<table class="standard-table">
- <thead>
-  <tr>
-   <th scope="col">Specification</th>
-   <th scope="col">Title</th>
-  </tr>
- </thead>
- <tbody>
-  <tr>
-   <td>{{RFC("2324", "418 I'm a teapot" , "2.3.2")}}</td>
-   <td>Hyper Text Coffee Pot Control Protocol (HTCPCP/1.0): Semantics and Content</td>
-  </tr>
-  <tr>
-   <td>{{RFC("7168", "418 I'm a teapot" , "2.3.3")}}</td>
-   <td>The Hyper Text Coffee Pot Control Protocol for Tea Efflux Appliances (HTCPCP-TEA): Response Codes</td>
-  </tr>
- </tbody>
-</table>
+| Specification                                                | Title                                                                                             |
+| ------------------------------------------------------------ | ------------------------------------------------------------------------------------------------- |
+| {{RFC("2324", "418 I'm a teapot" , "2.3.2")}} | Hyper Text Coffee Pot Control Protocol (HTCPCP/1.0): Semantics and Content                        |
+| {{RFC("7168", "418 I'm a teapot" , "2.3.3")}} | The Hyper Text Coffee Pot Control Protocol for Tea Efflux Appliances (HTCPCP-TEA): Response Codes |
 
-<h2 id="Browser_compatibility">Browser compatibility</h2>
+## Browser compatibility
 
-<p>{{Compat}}</p>
+{{Compat}}
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
- <li>{{interwiki("wikipedia", "Hyper Text Coffee Pot Control Protocol", "Wikipedia: Hyper Text Coffee Pot Control Protocol")}}</li>
-</ul>
+- {{interwiki("wikipedia", "Hyper Text Coffee Pot Control Protocol", "Wikipedia: Hyper Text Coffee Pot Control Protocol")}}
diff --git a/files/en-us/web/http/status/422/index.md b/files/en-us/web/http/status/422/index.md
index 2e221e1757f4d8f..0cc57e8308cc00c 100644
--- a/files/en-us/web/http/status/422/index.md
+++ b/files/en-us/web/http/status/422/index.md
@@ -2,42 +2,30 @@
 title: 422 Unprocessable Entity
 slug: Web/HTTP/Status/422
 tags:
-- Client error
-- HTTP
-- HTTP Status Code
-- Reference
-- Status code
-- WebDAV
+  - Client error
+  - HTTP
+  - HTTP Status Code
+  - Reference
+  - Status code
+  - WebDAV
 ---
-<p>{{HTTPSidebar}}</p>
+{{HTTPSidebar}}
 
-<p>The HyperText Transfer Protocol (HTTP)
-  <code><strong>422 Unprocessable Entity</strong></code> response status code indicates
-  that the server understands the content type of the request entity, and the syntax of
-  the request entity is correct, but it was unable to process the contained instructions.
-</p>
+The HyperText Transfer Protocol (HTTP)
+**`422 Unprocessable Entity`** response status code indicates
+that the server understands the content type of the request entity, and the syntax of
+the request entity is correct, but it was unable to process the contained instructions.
 
-<div class="notecard warning">
-  <p><strong>Warning:</strong> The client should not repeat this request without modification.</p>
-</div>
+> **Warning:** The client should not repeat this request without modification.
 
-<h2 id="Status">Status</h2>
+## Status
 
-<pre class="brush: html">422 Unprocessable Entity</pre>
+```html
+422 Unprocessable Entity
+```
 
-<h2 id="Specifications">Specifications</h2>
+## Specifications
 
-<table class="standard-table">
-  <thead>
-    <tr>
-      <th scope="col">Specification</th>
-      <th scope="col">Title</th>
-    </tr>
-  </thead>
-  <tbody>
-    <tr>
-      <td>{{RFC("4918", "422 Unprocessable Entity" , "11.2")}}</td>
-      <td>HTTP Extensions for Web Distributed Authoring and Versioning (WebDAV)</td>
-    </tr>
-  </tbody>
-</table>
+| Specification                                                        | Title                                                                 |
+| -------------------------------------------------------------------- | --------------------------------------------------------------------- |
+| {{RFC("4918", "422 Unprocessable Entity" , "11.2")}} | HTTP Extensions for Web Distributed Authoring and Versioning (WebDAV) |
diff --git a/files/en-us/web/http/status/425/index.md b/files/en-us/web/http/status/425/index.md
index 7d121c4b368e3c0..45f9b5e29d141bd 100644
--- a/files/en-us/web/http/status/425/index.md
+++ b/files/en-us/web/http/status/425/index.md
@@ -2,26 +2,28 @@
 title: 425 Too Early
 slug: Web/HTTP/Status/425
 tags:
-- Browser
-- Client error
-- HTTP
-- Status code
+  - Browser
+  - Client error
+  - HTTP
+  - Status code
 browser-compat: http.status.425
 ---
-<div>{{SeeCompatTable}}{{HTTPSidebar}}</div>
+{{SeeCompatTable}}{{HTTPSidebar}}
 
-<p>The HyperText Transfer Protocol (HTTP) <code><strong>425 Too Early</strong></code>
-  response status code indicates that the server is unwilling to risk processing a request
-  that might be replayed, which creates the potential for a replay attack.</p>
+The HyperText Transfer Protocol (HTTP) **`425 Too Early`**
+response status code indicates that the server is unwilling to risk processing a request
+that might be replayed, which creates the potential for a replay attack.
 
-<h2 id="Status">Status</h2>
+## Status
 
-<pre class="brush: html">425 Too Early</pre>
+```html
+425 Too Early
+```
 
-<h2 id="Specifications">Specifications</h2>
+## Specifications
 
 {{Specifications}}
 
-<h2 id="Browser_compatibility">Browser compatibility</h2>
+## Browser compatibility
 
-<p>{{Compat}}</p>
+{{Compat}}
diff --git a/files/en-us/web/http/status/426/index.md b/files/en-us/web/http/status/426/index.md
index f17315323e3347e..13479ed92a19607 100644
--- a/files/en-us/web/http/status/426/index.md
+++ b/files/en-us/web/http/status/426/index.md
@@ -2,55 +2,44 @@
 title: 426 Upgrade Required
 slug: Web/HTTP/Status/426
 tags:
-- Client error
-- HTTP
-- HTTP Status Code
-- Reference
-- Status code
+  - Client error
+  - HTTP
+  - HTTP Status Code
+  - Reference
+  - Status code
 ---
-<div>{{HTTPSidebar}}</div>
+{{HTTPSidebar}}
 
-<p>The HTTP <code><strong>426 Upgrade Required</strong></code> client error response code
-  indicates that the server refuses to perform the request using the current protocol but
-  might be willing to do so after the client upgrades to a different protocol.</p>
+The HTTP **`426 Upgrade Required`** client error response code
+indicates that the server refuses to perform the request using the current protocol but
+might be willing to do so after the client upgrades to a different protocol.
 
-<p>The server sends an {{HTTPHeader("Upgrade")}} header with this response to indicate the
-  required protocol(s).</p>
+The server sends an {{HTTPHeader("Upgrade")}} header with this response to indicate the
+required protocol(s).
 
-<h2 id="Status">Status</h2>
+## Status
 
-<pre class="brush: html">426 Upgrade Required</pre>
+```html
+426 Upgrade Required
+```
 
-<h2 id="Examples">Examples</h2>
+## Examples
 
-<pre>HTTP/1.1 426 Upgrade Required
-Upgrade: HTTP/2.0
-Connection: Upgrade
-Content-Length: 53
-Content-Type: text/plain
+    HTTP/1.1 426 Upgrade Required
+    Upgrade: HTTP/2.0
+    Connection: Upgrade
+    Content-Length: 53
+    Content-Type: text/plain
 
-This service requires use of the HTTP/2.0 protocol</pre>
+    This service requires use of the HTTP/2.0 protocol
 
-<h2 id="Specifications">Specifications</h2>
+## Specifications
 
-<table class="standard-table">
-  <thead>
-    <tr>
-      <th scope="col">Specification</th>
-      <th scope="col">Title</th>
-    </tr>
-  </thead>
-  <tbody>
-    <tr>
-      <td>{{RFC("7231", "426 Upgrade Required" , "6.5.15")}}</td>
-      <td>Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content</td>
-    </tr>
-  </tbody>
-</table>
+| Specification                                                        | Title                                                         |
+| -------------------------------------------------------------------- | ------------------------------------------------------------- |
+| {{RFC("7231", "426 Upgrade Required" , "6.5.15")}} | Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content |
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
-  <li>{{HTTPHeader("Upgrade")}}</li>
-  <li>{{HTTPStatus("101")}} <code>Switching Protocol</code></li>
-</ul>
+- {{HTTPHeader("Upgrade")}}
+- {{HTTPStatus("101")}} `Switching Protocol`
diff --git a/files/en-us/web/http/status/428/index.md b/files/en-us/web/http/status/428/index.md
index 19c7e97d22d9e1e..0e9cd6b9cb3275e 100644
--- a/files/en-us/web/http/status/428/index.md
+++ b/files/en-us/web/http/status/428/index.md
@@ -2,48 +2,37 @@
 title: 428 Precondition Required
 slug: Web/HTTP/Status/428
 tags:
-- Client error
-- HTTP
-- HTTP Status Code
-- Reference
-- Status code
+  - Client error
+  - HTTP
+  - HTTP Status Code
+  - Reference
+  - Status code
 ---
-<div>{{HTTPSidebar}}</div>
+{{HTTPSidebar}}
 
-<p>The HTTP <code><strong>428 Precondition Required</strong></code> response status code
-  indicates that the server requires the request to be <a
-    href="/en-US/docs/Web/HTTP/Conditional_requests">conditional</a>.</p>
+The HTTP **`428 Precondition Required`** response status code
+indicates that the server requires the request to be [conditional](/en-US/docs/Web/HTTP/Conditional_requests).
 
-<p>Typically, this means that a required precondition header, such
-  as {{HTTPHeader("If-Match")}}, <strong>is missing</strong>.</p>
+Typically, this means that a required precondition header, such
+as {{HTTPHeader("If-Match")}}, **is missing**.
 
-<p>When a precondition header is <strong>not matching</strong> the server side state, the
-  response should be {{HTTPStatus(412)}} <code>Precondition Failed</code>.</p>
+When a precondition header is **not matching** the server side state, the
+response should be {{HTTPStatus(412)}} `Precondition Failed`.
 
-<h2 id="Status">Status</h2>
+## Status
 
-<pre class="brush: html">428 Precondition Required</pre>
+```html
+428 Precondition Required
+```
 
-<h2 id="Specifications">Specifications</h2>
+## Specifications
 
-<table class="standard-table">
-  <tbody>
-    <tr>
-      <th scope="col">Specification</th>
-      <th scope="col">Title</th>
-    </tr>
-    <tr>
-      <td>{{RFC("6585", "428 Precondition Required" , "3")}}</td>
-      <td>Additional HTTP Status Codes</td>
-    </tr>
-  </tbody>
-</table>
+| Specification                                                        | Title                        |
+| -------------------------------------------------------------------- | ---------------------------- |
+| {{RFC("6585", "428 Precondition Required" , "3")}} | Additional HTTP Status Codes |
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
-  <li><a href="/en-US/docs/Web/HTTP/Conditional_requests">HTTP conditional requests</a>
-  </li>
-  <li>{{HTTPHeader("If-Match")}}</li>
-  <li>{{HTTPStatus(412)}}</li>
-</ul>
+- [HTTP conditional requests](/en-US/docs/Web/HTTP/Conditional_requests)
+- {{HTTPHeader("If-Match")}}
+- {{HTTPStatus(412)}}
diff --git a/files/en-us/web/http/status/429/index.md b/files/en-us/web/http/status/429/index.md
index a770385042397f7..22e7a34ec496c3e 100644
--- a/files/en-us/web/http/status/429/index.md
+++ b/files/en-us/web/http/status/429/index.md
@@ -8,43 +8,32 @@ tags:
   - Reference
   - Status code
 ---
-<div>{{HTTPSidebar}}</div>
+{{HTTPSidebar}}
 
-<p>The HTTP <code><strong>429 Too Many Requests</strong></code> response status code indicates the user has sent too many requests in a given amount of time ("rate limiting").</p>
+The HTTP **`429 Too Many Requests`** response status code indicates the user has sent too many requests in a given amount of time ("rate limiting").
 
-<p>A {{HTTPHeader("Retry-After")}} header might be included to this response indicating how long to wait before making a new request.</p>
+A {{HTTPHeader("Retry-After")}} header might be included to this response indicating how long to wait before making a new request.
 
-<h2 id="Status">Status</h2>
+## Status
 
-<pre class="brush: html">429 Too Many Requests</pre>
+```html
+429 Too Many Requests
+```
 
-<h2 id="Example">Example</h2>
+## Example
 
-<pre>HTTP/1.1 429 Too Many Requests
-Content-Type: text/html
-Retry-After: 3600</pre>
+    HTTP/1.1 429 Too Many Requests
+    Content-Type: text/html
+    Retry-After: 3600
 
-<h2 id="Specifications">Specifications</h2>
+## Specifications
 
-<table class="standard-table">
- <thead>
-  <tr>
-   <th scope="col">Specification</th>
-   <th scope="col">Title</th>
-  </tr>
- </thead>
- <tbody>
-  <tr>
-   <td>{{RFC("6585", "429 Too Many Requests" , "4")}}</td>
-   <td>Additional HTTP Status Codes</td>
-  </tr>
- </tbody>
-</table>
+| Specification                                                | Title                        |
+| ------------------------------------------------------------ | ---------------------------- |
+| {{RFC("6585", "429 Too Many Requests" , "4")}} | Additional HTTP Status Codes |
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
- <li>{{HTTPHeader("Retry-After")}}</li>
- <li><a href="https://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html" rel="noopener">HTTP/1.1: Status Code Definitions</a></li>
- <li>Python solution: <a href="https://stackoverflow.com/questions/22786068/how-to-avoid-http-error-429-too-many-requests-python">How to avoid HTTP error 429 python</a></li>
-</ul>
+- {{HTTPHeader("Retry-After")}}
+- [HTTP/1.1: Status Code Definitions](https://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html)
+- Python solution: [How to avoid HTTP error 429 python](https://stackoverflow.com/questions/22786068/how-to-avoid-http-error-429-too-many-requests-python)
diff --git a/files/en-us/web/http/status/431/index.md b/files/en-us/web/http/status/431/index.md
index 6caed69ce9230c8..20867db3cf5e6dc 100644
--- a/files/en-us/web/http/status/431/index.md
+++ b/files/en-us/web/http/status/431/index.md
@@ -2,59 +2,44 @@
 title: 431 Request Header Fields Too Large
 slug: Web/HTTP/Status/431
 tags:
-- Client error
-- HTTP
-- HTTP Status Code
-- Reference
-- Status code
+  - Client error
+  - HTTP
+  - HTTP Status Code
+  - Reference
+  - Status code
 ---
-<div>{{HTTPSidebar}}</div>
-
-<p>
-  The HTTP <code><strong>431 Request Header Fields Too Large</strong></code> response status code
-  indicates that the server refuses to process the request because the request's
-  <a href="/en-US/docs/Web/HTTP/Headers">HTTP headers</a> are too long.
-  The request <em>may</em> be resubmitted after reducing the size of the request headers.
-</p>
-
-<p>431 can be used when the <strong>total size</strong> of request headers is too large,
-  or when a <strong>single</strong> header field is too large. To help those running into
-  this error, indicate which of the two is the problem in the response body — ideally,
-  also include which headers are too large. This lets users attempt to fix the problem,
-  such as by clearing their cookies.</p>
-
-<p>Servers will often produce this status if:</p>
-
-<ul>
-  <li>The {{ httpheader("Referer") }} URL is too long</li>
-  <li>There are too many <a href="/en-US/docs/Web/HTTP/Cookies">Cookies</a> sent in the
-    request</li>
-</ul>
-
-<h2 id="Status">Status</h2>
-
-<pre class="brush: html">431 Request Header Fields Too Large</pre>
-
-<h2 id="Specifications">Specifications</h2>
-
-<table class="standard-table">
-  <thead>
-    <tr>
-      <th scope="col">Specification</th>
-      <th scope="col">Title</th>
-    </tr>
-  </thead>
-  <tbody>
-    <tr>
-      <td>{{RFC("6585", "431 Request Header Fields Too Large" , "5")}}</td>
-      <td>Additional HTTP Status Codes</td>
-    </tr>
-  </tbody>
-</table>
-
-<h2 id="See_also">See also</h2>
-
-<ul>
-  <li>{{HTTPStatus(414, "414 URI Too Long")}}</li>
-  <li>{{Glossary("Request header")}}</li>
-</ul>
+{{HTTPSidebar}}
+
+The HTTP **`431 Request Header Fields Too Large`** response status code
+indicates that the server refuses to process the request because the request's
+[HTTP headers](/en-US/docs/Web/HTTP/Headers) are too long.
+The request _may_ be resubmitted after reducing the size of the request headers.
+
+431 can be used when the **total size** of request headers is too large,
+or when a **single** header field is too large. To help those running into
+this error, indicate which of the two is the problem in the response body — ideally,
+also include which headers are too large. This lets users attempt to fix the problem,
+such as by clearing their cookies.
+
+Servers will often produce this status if:
+
+- The {{ httpheader("Referer") }} URL is too long
+- There are too many [Cookies](/en-US/docs/Web/HTTP/Cookies) sent in the
+  request
+
+## Status
+
+```html
+431 Request Header Fields Too Large
+```
+
+## Specifications
+
+| Specification                                                                    | Title                        |
+| -------------------------------------------------------------------------------- | ---------------------------- |
+| {{RFC("6585", "431 Request Header Fields Too Large" , "5")}} | Additional HTTP Status Codes |
+
+## See also
+
+- {{HTTPStatus(414, "414 URI Too Long")}}
+- {{Glossary("Request header")}}
diff --git a/files/en-us/web/http/status/451/index.md b/files/en-us/web/http/status/451/index.md
index ef815bab017620d..64c56dff1871a47 100644
--- a/files/en-us/web/http/status/451/index.md
+++ b/files/en-us/web/http/status/451/index.md
@@ -8,48 +8,50 @@ tags:
   - Status code
 browser-compat: http.status.451
 ---
-<p>{{HTTPSidebar}}</p>
+{{HTTPSidebar}}
 
-<p>The HyperText Transfer Protocol (HTTP) <code><strong>451 Unavailable For Legal Reasons</strong></code> client error response code indicates that the user requested a resource that is not available due to legal reasons, such as a web page for which a legal action has been issued.</p>
+The HyperText Transfer Protocol (HTTP) **`451 Unavailable For Legal Reasons`** client error response code indicates that the user requested a resource that is not available due to legal reasons, such as a web page for which a legal action has been issued.
 
-<h2 id="Status">Status</h2>
+## Status
 
-<pre class="brush: html">451 Unavailable For Legal Reasons</pre>
+```html
+451 Unavailable For Legal Reasons
+```
 
-<h2 id="Example">Example</h2>
+## Example
 
-<p>This example response is taken from the IETF RFC (see below) and contains a reference to {{interwiki("wikipedia", "Monty_Python's_Life_of_Brian", "Monty Python's Life of Brian")}}.</p>
+This example response is taken from the IETF RFC (see below) and contains a reference to {{interwiki("wikipedia", "Monty_Python's_Life_of_Brian", "Monty Python's Life of Brian")}}.
 
-<p><strong>Note:</strong> the {{HTTPHeader("Link")}} header might also contain a <code>rel="blocked-by"</code> relation identifying the entity and implementing blockage, not any other entity mandating it.</p>
+**Note:** the {{HTTPHeader("Link")}} header might also contain a `rel="blocked-by"` relation identifying the entity and implementing blockage, not any other entity mandating it.
 
-<p>Any attempt to identify the entity ultimately responsible for the resource being unavailable belongs in the response body, not in the <code>rel="blocked-by"</code> link. This includes the name of the person or organization that made a legal demand resulting in the content's removal.</p>
+Any attempt to identify the entity ultimately responsible for the resource being unavailable belongs in the response body, not in the `rel="blocked-by"` link. This includes the name of the person or organization that made a legal demand resulting in the content's removal.
 
-<pre>HTTP/1.1 451 Unavailable For Legal Reasons
-Link: &lt;https://spqr.example.org/legislatione&gt;; rel="blocked-by"
-Content-Type: text/html</pre>
+    HTTP/1.1 451 Unavailable For Legal Reasons
+    Link: <https://spqr.example.org/legislatione>; rel="blocked-by"
+    Content-Type: text/html
 
-<pre>&lt;html&gt;
-      &lt;head&gt;&lt;title&gt;Unavailable For Legal Reasons&lt;/title&gt;&lt;/head&gt;
-      &lt;body&gt;
-            &lt;h1&gt;Unavailable For Legal Reasons&lt;/h1&gt;
-            &lt;p&gt;This request may not be serviced in the Roman Province
-            of Judea due to the Lex Julia Majestatis, which disallows
-            access to resources hosted on servers deemed to be
-            operated by the People's Front of Judea.&lt;/p&gt;
-     &lt;/body&gt;
-&lt;/html&gt;</pre>
+<!---->
 
-<h2 id="Specifications">Specifications</h2>
+    <html>
+          <head><title>Unavailable For Legal Reasons</title></head>
+          <body>
+                <h1>Unavailable For Legal Reasons</h1>
+                <p>This request may not be serviced in the Roman Province
+                of Judea due to the Lex Julia Majestatis, which disallows
+                access to resources hosted on servers deemed to be
+                operated by the People's Front of Judea.</p>
+         </body>
+    </html>
+
+## Specifications
 
 {{Specifications}}
 
-<h2 id="Browser_compatibility">Browser compatibility</h2>
+## Browser compatibility
 
-<p>{{Compat}}</p>
+{{Compat}}
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
- <li>{{interwiki("wikipedia", "HTTP_451", "Wikipedia: HTTP 451")}}</li>
- <li>{{interwiki("wikipedia", "Fahrenheit_451", "Wikipedia: Fahrenheit 451")}} (which gave this status code its number)</li>
-</ul>
+- {{interwiki("wikipedia", "HTTP_451", "Wikipedia: HTTP 451")}}
+- {{interwiki("wikipedia", "Fahrenheit_451", "Wikipedia: Fahrenheit 451")}} (which gave this status code its number)
diff --git a/files/en-us/web/http/status/500/index.md b/files/en-us/web/http/status/500/index.md
index b76c01fa9601ea6..b8b869c678e3dbe 100644
--- a/files/en-us/web/http/status/500/index.md
+++ b/files/en-us/web/http/status/500/index.md
@@ -7,26 +7,26 @@ tags:
   - Status code
 browser-compat: http.status.500
 ---
-<div>{{HTTPSidebar}}</div>
+{{HTTPSidebar}}
 
-<p>The HyperText Transfer Protocol (HTTP) <code><strong>500 Internal Server Error</strong></code> server error response code indicates that the server encountered an unexpected condition that prevented it from fulfilling the request.</p>
+The HyperText Transfer Protocol (HTTP) **`500 Internal Server Error`** server error response code indicates that the server encountered an unexpected condition that prevented it from fulfilling the request.
 
-<p>This error response is a generic "catch-all" response. Usually, this indicates the server cannot find a better 5xx error code to response. Sometimes, server administrators log error responses like the 500 status code with more details about the request to prevent the error from happening again in the future.</p>
+This error response is a generic "catch-all" response. Usually, this indicates the server cannot find a better 5xx error code to response. Sometimes, server administrators log error responses like the 500 status code with more details about the request to prevent the error from happening again in the future.
 
-<h2 id="Status">Status</h2>
+## Status
 
-<pre class="brush: html">500 Internal Server Error</pre>
+```html
+500 Internal Server Error
+```
 
-<h2 id="Specifications">Specifications</h2>
+## Specifications
 
 {{Specifications}}
 
-<h2 id="Browser_compatibility">Browser compatibility</h2>
+## Browser compatibility
 
-<p>{{Compat}}</p>
+{{Compat}}
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
- <li><a href="https://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html" rel="noopener">HTTP/1.1: Status Code Definitions</a></li>
-</ul>
+- [HTTP/1.1: Status Code Definitions](https://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html)
diff --git a/files/en-us/web/http/status/501/index.md b/files/en-us/web/http/status/501/index.md
index a689f70b75c6bb7..c626c1cb515b85c 100644
--- a/files/en-us/web/http/status/501/index.md
+++ b/files/en-us/web/http/status/501/index.md
@@ -7,32 +7,31 @@ tags:
   - Status code
 browser-compat: http.status.501
 ---
-<div>{{HTTPSidebar}}</div>
+{{HTTPSidebar}}
 
-<p>The HyperText Transfer Protocol (HTTP) <code><strong>501 Not Implemented</strong></code> server error response code means that <strong>the server does not support the functionality required to fulfill the request</strong>.</p>
+The HyperText Transfer Protocol (HTTP) **`501 Not Implemented`** server error response code means that **the server does not support the functionality required to fulfill the request**.
 
-<p>This status can also send a {{HTTPHeader("Retry-After")}} header, telling the requester when to check back to see if the functionality is supported by then.</p>
+This status can also send a {{HTTPHeader("Retry-After")}} header, telling the requester when to check back to see if the functionality is supported by then.
 
-<p><code>501</code> is the appropriate response when the server does not recognize the request method and is incapable of supporting it for any resource. The only methods that servers are required to support (and therefore that must not return <code>501</code>) are {{HTTPMethod("GET")}} and {{HTTPMethod("HEAD")}}.</p>
+`501` is the appropriate response when the server does not recognize the request method and is incapable of supporting it for any resource. The only methods that servers are required to support (and therefore that must not return `501`) are {{HTTPMethod("GET")}} and {{HTTPMethod("HEAD")}}.
 
-<p>If the server <em>does</em> recognize the method, but intentionally does not support it, the appropriate response is {{HTTPStatus(405, "405 Method Not Allowed")}}.</p>
+If the server _does_ recognize the method, but intentionally does not support it, the appropriate response is {{HTTPStatus(405, "405 Method Not Allowed")}}.
 
-<div class="notecard note">
-  <p><strong>Note:</strong> </p>
-  <ul>
-    <li>A 501 error is not something you can fix, but requires a fix by the web server you are trying to access.</li>
-    <li>A 501 response is cacheable by default; that is, unless caching headers instruct otherwise.</li>
-  </ul>
-</div>
+> **Note:**
+>
+> - A 501 error is not something you can fix, but requires a fix by the web server you are trying to access.
+> - A 501 response is cacheable by default; that is, unless caching headers instruct otherwise.
 
-<h2 id="Status">Status</h2>
+## Status
 
-<pre class="brush: html">501 Not Implemented</pre>
+```html
+501 Not Implemented
+```
 
-<h2 id="Specifications">Specifications</h2>
+## Specifications
 
 {{Specifications}}
 
-<h2 id="Browser_compatibility">Browser compatibility</h2>
+## Browser compatibility
 
-<p>{{Compat}}</p>
+{{Compat}}
diff --git a/files/en-us/web/http/status/502/index.md b/files/en-us/web/http/status/502/index.md
index a36a4037704275c..b1abbbcbf20c7a4 100644
--- a/files/en-us/web/http/status/502/index.md
+++ b/files/en-us/web/http/status/502/index.md
@@ -7,30 +7,27 @@ tags:
   - Status code
 browser-compat: http.status.502
 ---
-<div>{{HTTPSidebar}}</div>
+{{HTTPSidebar}}
 
-<p>The HyperText Transfer Protocol (HTTP) <code><strong>502 Bad Gateway</strong></code> server error response code indicates that the server, while acting as a gateway or proxy, received an invalid response from the upstream server.</p>
+The HyperText Transfer Protocol (HTTP) **`502 Bad Gateway`** server error response code indicates that the server, while acting as a gateway or proxy, received an invalid response from the upstream server.
 
-<div class="norecard note">
-  <p><strong>Note:</strong> A {{interwiki("wikipedia", "Gateway_(telecommunications)", "Gateway")}} might refer to different things in networking and a 502 error is usually not something you can fix, but requires a fix by the web server or the proxies you are trying to get access through.</p>
-</div>
+> **Note:** A {{interwiki("wikipedia", "Gateway_(telecommunications)", "Gateway")}} might refer to different things in networking and a 502 error is usually not something you can fix, but requires a fix by the web server or the proxies you are trying to get access through.
 
-<h2 id="Status">Status</h2>
+## Status
 
-<pre class="brush: html">502 Bad Gateway
-</pre>
+```html
+502 Bad Gateway
+```
 
-<h2 id="Specifications">Specifications</h2>
+## Specifications
 
 {{Specifications}}
 
-<h2 id="Browser_compatibility">Browser compatibility</h2>
+## Browser compatibility
 
-<p>{{Compat}}</p>
+{{Compat}}
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
- <li>{{HTTPStatus(504)}}</li>
- <li><a href="https://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html" rel="noopener">HTTP/1.1: Status Code Definitions</a></li>
-</ul>
+- {{HTTPStatus(504)}}
+- [HTTP/1.1: Status Code Definitions](https://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html)
diff --git a/files/en-us/web/http/status/503/index.md b/files/en-us/web/http/status/503/index.md
index 0d780962f87d3f9..d664b9ebfdade08 100644
--- a/files/en-us/web/http/status/503/index.md
+++ b/files/en-us/web/http/status/503/index.md
@@ -8,33 +8,31 @@ tags:
   - Status code
 browser-compat: http.status.503
 ---
-<div>{{HTTPSidebar}}</div>
+{{HTTPSidebar}}
 
-<p>The HyperText Transfer Protocol (HTTP) <code><strong>503 Service Unavailable</strong></code> server error response code indicates that the server is not ready to handle the request.</p>
+The HyperText Transfer Protocol (HTTP) **`503 Service Unavailable`** server error response code indicates that the server is not ready to handle the request.
 
-<p>Common causes are a server that is down for maintenance or that is overloaded. This response should be used for temporary conditions and the {{HTTPHeader("Retry-After")}} HTTP header should, if possible, contain the estimated time for the recovery of the service.</p>
+Common causes are a server that is down for maintenance or that is overloaded. This response should be used for temporary conditions and the {{HTTPHeader("Retry-After")}} HTTP header should, if possible, contain the estimated time for the recovery of the service.
 
-<div class="notecard note">
-  <p><strong>Note:</strong> together with this response, a user-friendly page explaining the problem should be sent.</p>
-</div>
+> **Note:** together with this response, a user-friendly page explaining the problem should be sent.
 
-<p>Caching-related headers that are sent along with this response should be taken care of, as a 503 status is often a temporary condition and responses shouldn't usually be cached.</p>
+Caching-related headers that are sent along with this response should be taken care of, as a 503 status is often a temporary condition and responses shouldn't usually be cached.
 
-<h2 id="Status">Status</h2>
+## Status
 
-<pre class="brush: html">503 Service Unavailable</pre>
+```html
+503 Service Unavailable
+```
 
-<h2 id="Specifications">Specifications</h2>
+## Specifications
 
 {{Specifications}}
 
-<h2 id="Browser_compatibility">Browser compatibility</h2>
+## Browser compatibility
 
-<p>{{Compat}}</p>
+{{Compat}}
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
- <li>{{HTTPHeader("Retry-After")}}</li>
- <li><a href="https://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html">HTTP/1.1: Status Code Definitions</a></li>
-</ul>
+- {{HTTPHeader("Retry-After")}}
+- [HTTP/1.1: Status Code Definitions](https://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html)
diff --git a/files/en-us/web/http/status/504/index.md b/files/en-us/web/http/status/504/index.md
index f2ed612bb14cff7..3b92fb543f1f9cc 100644
--- a/files/en-us/web/http/status/504/index.md
+++ b/files/en-us/web/http/status/504/index.md
@@ -7,29 +7,27 @@ tags:
   - Status code
 browser-compat: http.status.504
 ---
-<div>{{HTTPSidebar}}</div>
+{{HTTPSidebar}}
 
-<p>The HyperText Transfer Protocol (HTTP) <code><strong>504 Gateway Timeout</strong></code> server error response code indicates that the server, while acting as a gateway or proxy, did not get a response in time from the upstream server that it needed in order to complete the request.</p>
+The HyperText Transfer Protocol (HTTP) **`504 Gateway Timeout`** server error response code indicates that the server, while acting as a gateway or proxy, did not get a response in time from the upstream server that it needed in order to complete the request.
 
-<div class="notecard note">
-<p><strong>Note:</strong> A {{interwiki("wikipedia", "Gateway_(telecommunications)", "Gateway")}} might refer to different things in networking and a 504 error is usually not something you can fix, but requires a fix by the web server or the proxies you are trying to get access through.</p>
-</div>
+> **Note:** A {{interwiki("wikipedia", "Gateway_(telecommunications)", "Gateway")}} might refer to different things in networking and a 504 error is usually not something you can fix, but requires a fix by the web server or the proxies you are trying to get access through.
 
-<h2 id="Status">Status</h2>
+## Status
 
-<pre class="brush: html">504 Gateway Timeout</pre>
+```html
+504 Gateway Timeout
+```
 
-<h2 id="Specifications">Specifications</h2>
+## Specifications
 
 {{Specifications}}
 
-<h2 id="Browser_compatibility">Browser compatibility</h2>
+## Browser compatibility
 
-<p>{{Compat}}</p>
+{{Compat}}
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
- <li><a href="https://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html" rel="noopener">HTTP/1.1: Status Code Definitions</a></li>
- <li>{{HTTPStatus(502)}}</li>
-</ul>
+- [HTTP/1.1: Status Code Definitions](https://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html)
+- {{HTTPStatus(502)}}
diff --git a/files/en-us/web/http/status/505/index.md b/files/en-us/web/http/status/505/index.md
index 3a873387d9b7c15..8e7043e9bc2995f 100644
--- a/files/en-us/web/http/status/505/index.md
+++ b/files/en-us/web/http/status/505/index.md
@@ -2,38 +2,29 @@
 title: 505 HTTP Version Not Supported
 slug: Web/HTTP/Status/505
 tags:
-- HTTP
-- Reference
-- Server error
-- Status code
+  - HTTP
+  - Reference
+  - Server error
+  - Status code
 ---
-<div>{{HTTPSidebar}}</div>
+{{HTTPSidebar}}
 
-<p>The HyperText Transfer Protocol (HTTP)
-  <code><strong>505 HTTP Version Not Supported</strong></code> response status code
-  indicates that the HTTP version used in the request is not supported by the server.</p>
+The HyperText Transfer Protocol (HTTP)
+**`505 HTTP Version Not Supported`** response status code
+indicates that the HTTP version used in the request is not supported by the server.
 
-<h2 id="Status">Status</h2>
+## Status
 
-<pre class="brush: html">505 HTTP Version Not Supported</pre>
+```html
+505 HTTP Version Not Supported
+```
 
-<h2 id="Specifications">Specifications</h2>
+## Specifications
 
-<table class="standard-table">
-  <tbody>
-    <tr>
-      <th scope="col">Specification</th>
-      <th scope="col">Title</th>
-    </tr>
-    <tr>
-      <td>{{RFC("7231", "505 HTTP Version Not Supported" , "6.6.6")}}</td>
-      <td>Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content</td>
-    </tr>
-  </tbody>
-</table>
+| Specification                                                                    | Title                                                         |
+| -------------------------------------------------------------------------------- | ------------------------------------------------------------- |
+| {{RFC("7231", "505 HTTP Version Not Supported" , "6.6.6")}} | Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content |
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
-  <li>{{HTTPHeader("Upgrade")}}</li>
-</ul>
+- {{HTTPHeader("Upgrade")}}
diff --git a/files/en-us/web/http/status/506/index.md b/files/en-us/web/http/status/506/index.md
index 8e40fb025b57673..b36478e3018494e 100644
--- a/files/en-us/web/http/status/506/index.md
+++ b/files/en-us/web/http/status/506/index.md
@@ -6,29 +6,20 @@ tags:
   - Server error
   - Status code
 ---
-<div>{{HTTPSidebar}}</div>
+{{HTTPSidebar}}
 
-<p>The HyperText Transfer Protocol (HTTP) <code><strong>506 Variant Also Negotiates</strong></code> response status code may be given in the context of Transparent Content Negotiation (see <a href="https://datatracker.ietf.org/doc/html/rfc2295">RFC 2295</a>). This protocol enables a client to retrieve the best variant of a given resource, where the server supports multiple variants.</p>
+The HyperText Transfer Protocol (HTTP) **`506 Variant Also Negotiates`** response status code may be given in the context of Transparent Content Negotiation (see [RFC 2295](https://datatracker.ietf.org/doc/html/rfc2295)). This protocol enables a client to retrieve the best variant of a given resource, where the server supports multiple variants.
 
-<p>The <code><strong>Variant Also Negotiates</strong></code> status code indicates an internal server configuration error in which the chosen variant is itself configured to engage in content negotiation, so is not a proper negotiation endpoint.</p>
+The **`Variant Also Negotiates`** status code indicates an internal server configuration error in which the chosen variant is itself configured to engage in content negotiation, so is not a proper negotiation endpoint.
 
-<h2 id="Status">Status</h2>
+## Status
 
-<pre class="brush: html">506 Variant Also Negotiates</pre>
+```html
+506 Variant Also Negotiates
+```
 
-<h2 id="Specifications">Specifications</h2>
+## Specifications
 
-<table class="standard-table">
- <thead>
-  <tr>
-   <th scope="col">Specification</th>
-   <th scope="col">Title</th>
-  </tr>
- </thead>
- <tbody>
-  <tr>
-   <td>{{RFC("2295", "506 Variant Also Negotiates" , "8.1")}}</td>
-   <td>Transparent Content Negotiation in HTTP</td>
-  </tr>
- </tbody>
-</table>
+| Specification                                                            | Title                                   |
+| ------------------------------------------------------------------------ | --------------------------------------- |
+| {{RFC("2295", "506 Variant Also Negotiates" , "8.1")}} | Transparent Content Negotiation in HTTP |
diff --git a/files/en-us/web/http/status/507/index.md b/files/en-us/web/http/status/507/index.md
index 14ce8ee0c50a6ad..952fe820cd2a617 100644
--- a/files/en-us/web/http/status/507/index.md
+++ b/files/en-us/web/http/status/507/index.md
@@ -6,29 +6,20 @@ tags:
   - Server error
   - Status code
 ---
-<div>{{HTTPSidebar}}</div>
+{{HTTPSidebar}}
 
-<p>The HyperText Transfer Protocol (HTTP) <code><strong>507 Insufficient Storage</strong></code> response status code may be given in the context of the Web Distributed Authoring and Versioning (WebDAV) protocol (see <a href="https://datatracker.ietf.org/doc/html/rfc4918">RFC 4918</a>).</p>
+The HyperText Transfer Protocol (HTTP) **`507 Insufficient Storage`** response status code may be given in the context of the Web Distributed Authoring and Versioning (WebDAV) protocol (see [RFC 4918](https://datatracker.ietf.org/doc/html/rfc4918)).
 
-<p>It indicates that a method could not be performed because the server cannot store the representation needed to successfully complete the request.</p>
+It indicates that a method could not be performed because the server cannot store the representation needed to successfully complete the request.
 
-<h2 id="Status">Status</h2>
+## Status
 
-<pre class="brush: html">507 Insufficient Storage</pre>
+```html
+507 Insufficient Storage
+```
 
-<h2 id="Specifications">Specifications</h2>
+## Specifications
 
-<table class="standard-table">
- <thead>
-  <tr>
-   <th scope="col">Specification</th>
-   <th scope="col">Title</th>
-  </tr>
- </thead>
- <tbody>
-  <tr>
-   <td>{{RFC("4918", "507 Insufficient Storage" , "11.5")}}</td>
-   <td>Web Distributed Authoring and Versioning</td>
-  </tr>
- </tbody>
-</table>
+| Specification                                                        | Title                                    |
+| -------------------------------------------------------------------- | ---------------------------------------- |
+| {{RFC("4918", "507 Insufficient Storage" , "11.5")}} | Web Distributed Authoring and Versioning |
diff --git a/files/en-us/web/http/status/508/index.md b/files/en-us/web/http/status/508/index.md
index 379d852bcd7cb63..ea234e5f7477f37 100644
--- a/files/en-us/web/http/status/508/index.md
+++ b/files/en-us/web/http/status/508/index.md
@@ -2,38 +2,29 @@
 title: 508 Loop Detected
 slug: Web/HTTP/Status/508
 tags:
-- '508'
-- HTTP
-- Server error
-- Status code
+  - '508'
+  - HTTP
+  - Server error
+  - Status code
 ---
-<div>{{HTTPSidebar}}</div>
+{{HTTPSidebar}}
 
-<p>The HyperText Transfer Protocol (HTTP) <code><strong>508 Loop Detected</strong></code>
-  response status code may be given in the context of the Web Distributed Authoring and
-  Versioning (WebDAV) protocol.</p>
+The HyperText Transfer Protocol (HTTP) **`508 Loop Detected`**
+response status code may be given in the context of the Web Distributed Authoring and
+Versioning (WebDAV) protocol.
 
-<p>It indicates that the server terminated an operation because it encountered an infinite
-  loop while processing a request with "Depth: infinity". This status indicates that the
-  entire operation failed.</p>
+It indicates that the server terminated an operation because it encountered an infinite
+loop while processing a request with "Depth: infinity". This status indicates that the
+entire operation failed.
 
-<h2 id="Status">Status</h2>
+## Status
 
-<pre class="brush: html">508 Loop Detected</pre>
+```html
+508 Loop Detected
+```
 
-<h2 id="Specifications">Specifications</h2>
+## Specifications
 
-<table class="standard-table">
-  <thead>
-    <tr>
-      <th scope="col">Specification</th>
-      <th scope="col">Title</th>
-    </tr>
-  </thead>
-  <tbody>
-    <tr>
-      <td>{{RFC("5842", "508 Loop Detected" , "7.2")}}</td>
-      <td>Web Distributed Authoring and Versioning</td>
-    </tr>
-  </tbody>
-</table>
+| Specification                                                | Title                                    |
+| ------------------------------------------------------------ | ---------------------------------------- |
+| {{RFC("5842", "508 Loop Detected" , "7.2")}} | Web Distributed Authoring and Versioning |
diff --git a/files/en-us/web/http/status/510/index.md b/files/en-us/web/http/status/510/index.md
index cfd5a5abd18286c..14ebc3c6228b178 100644
--- a/files/en-us/web/http/status/510/index.md
+++ b/files/en-us/web/http/status/510/index.md
@@ -2,36 +2,29 @@
 title: 510 Not Extended
 slug: Web/HTTP/Status/510
 tags:
-- HTTP
-- Server error
-- Status code
+  - HTTP
+  - Server error
+  - Status code
 ---
-<div>{{HTTPSidebar}}</div>
+{{HTTPSidebar}}
 
-<p>The HyperText Transfer Protocol (HTTP)  <code><strong>510 Not Extended</strong></code>
-  response status code is sent in the context of the HTTP Extension Framework, defined in
-  <a href="https://datatracker.ietf.org/doc/html/rfc2774">RFC 2774</a>.</p>
+The HyperText Transfer Protocol (HTTP)  **`510 Not Extended`**
+response status code is sent in the context of the HTTP Extension Framework, defined in
+[RFC 2774](https://datatracker.ietf.org/doc/html/rfc2774).
 
-<p>In that specification a client may send a request that contains an extension
-  declaration, that describes the extension to be used. If the server receives such a
-  request, but any described extensions are not supported for the request, then the server
-  responds with the 510 status code.</p>
+In that specification a client may send a request that contains an extension
+declaration, that describes the extension to be used. If the server receives such a
+request, but any described extensions are not supported for the request, then the server
+responds with the 510 status code.
 
-<h2 id="Status">Status</h2>
+## Status
 
-<pre class="brush: html">510 Not Extended</pre>
+```html
+510 Not Extended
+```
 
-<h2 id="Specifications">Specifications</h2>
+## Specifications
 
-<table class="standard-table">
-  <tbody>
-    <tr>
-      <th scope="col">Specification</th>
-      <th scope="col">Title</th>
-    </tr>
-    <tr>
-      <td>{{RFC("2774", "510 Not Extended" , "7")}}</td>
-      <td>An HTTP Extension Framework</td>
-    </tr>
-  </tbody>
-</table>
+| Specification                                            | Title                       |
+| -------------------------------------------------------- | --------------------------- |
+| {{RFC("2774", "510 Not Extended" , "7")}} | An HTTP Extension Framework |
diff --git a/files/en-us/web/http/status/511/index.md b/files/en-us/web/http/status/511/index.md
index 7595ca01c43719d..4c2637f5b4272a0 100644
--- a/files/en-us/web/http/status/511/index.md
+++ b/files/en-us/web/http/status/511/index.md
@@ -2,46 +2,37 @@
 title: 511 Network Authentication Required
 slug: Web/HTTP/Status/511
 tags:
-- HTTP
-- HTTP Status Code
-- Reference
-- Server error
-- Status code
+  - HTTP
+  - HTTP Status Code
+  - Reference
+  - Server error
+  - Status code
 ---
-<div>{{HTTPSidebar}}</div>
+{{HTTPSidebar}}
 
-<p>The HTTP <code><strong>511 Network Authentication Required</strong></code> response
-  status code indicates that the client needs to authenticate to gain network access.</p>
+The HTTP **`511 Network Authentication Required`** response
+status code indicates that the client needs to authenticate to gain network access.
 
-<p>This status is not generated by origin servers, but by intercepting proxies that
-  control access to the network.</p>
+This status is not generated by origin servers, but by intercepting proxies that
+control access to the network.
 
-<p>Network operators sometimes require some authentication, acceptance of terms, or other
-  user interaction before granting access (for example in an internet café or at an
-  airport). They often identify clients who have not done so using their Media Access
-  Control ({{Glossary("MAC")}}) addresses.</p>
+Network operators sometimes require some authentication, acceptance of terms, or other
+user interaction before granting access (for example in an internet café or at an
+airport). They often identify clients who have not done so using their Media Access
+Control ({{Glossary("MAC")}}) addresses.
 
-<h2 id="Status">Status</h2>
+## Status
 
-<pre class="brush: html">511 Network Authentication Required</pre>
+```html
+511 Network Authentication Required
+```
 
-<h2 id="Specifications">Specifications</h2>
+## Specifications
 
-<table class="standard-table">
-  <tbody>
-    <tr>
-      <th scope="col">Specification</th>
-      <th scope="col">Title</th>
-    </tr>
-    <tr>
-      <td>{{RFC("6585", "511 Network Authentication Required" , "6")}}</td>
-      <td>Additional HTTP Status Codes</td>
-    </tr>
-  </tbody>
-</table>
+| Specification                                                                    | Title                        |
+| -------------------------------------------------------------------------------- | ---------------------------- |
+| {{RFC("6585", "511 Network Authentication Required" , "6")}} | Additional HTTP Status Codes |
 
-<h2 id="See_also">See also</h2>
+## See also
 
-<ul>
-  <li>{{Glossary("Proxy server")}}</li>
-</ul>
+- {{Glossary("Proxy server")}}
diff --git a/files/en-us/web/http/status/index.md b/files/en-us/web/http/status/index.md
index 319b13aab3c3abf..19969445a7e25fe 100644
--- a/files/en-us/web/http/status/index.md
+++ b/files/en-us/web/http/status/index.md
@@ -9,189 +9,173 @@ tags:
   - Status code
   - Web
 ---
-<div>{{HTTPSidebar}}</div>
-
-<p class="summary">HTTP response status codes indicate whether a specific <a href="/en-US/docs/Web/HTTP">HTTP</a> request has been successfully completed. Responses are grouped in five classes:</p>
-
-<ol>
- <li><a href="#information_responses">Informational responses</a> (<code>100</code>–<code>199</code>)</li>
- <li><a href="#successful_responses">Successful responses</a> (<code>200</code>–<code>299</code>)</li>
- <li><a href="#redirection_messages">Redirects</a> (<code>300</code>–<code>399</code>)</li>
- <li><a href="#client_error_responses">Client errors</a> (<code>400</code>–<code>499</code>)</li>
- <li><a href="#server_error_responses">Server errors</a> (<code>500</code>–<code>599</code>)</li>
-</ol>
-
-<p>The below status codes are defined by <a href="https://datatracker.ietf.org/doc/html/rfc2616#section-10">section 10 of RFC 2616</a>. You can find an updated specification in <a href="https://datatracker.ietf.org/doc/html/rfc7231#section-6.5.1">RFC 7231</a>.</p>
-
-<div class="notecard note">
-  <p><strong>Note:</strong> If you receive a response that is not in this list, it is a non-standard response, possibly custom to the server's software.</p>
-</div>
-
-<h2 id="Information_responses">Information responses</h2>
-
-<dl>
- <dt>{{HTTPStatus(100, "100 Continue")}}</dt>
- <dd>This interim response indicates that everything so far is OK and that the client should continue the request, or ignore the response if the request is already finished.</dd>
- <dt>{{HTTPStatus(101, "101 Switching Protocol")}}</dt>
- <dd>This code is sent in response to an {{HTTPHeader("Upgrade")}} request header from the client, and indicates the protocol the server is switching to.</dd>
- <dt>{{HTTPStatus(102, "102 Processing")}} ({{Glossary("WebDAV")}})</dt>
- <dd>This code indicates that the server has received and is processing the request, but no response is available yet.</dd>
- <dt>{{HTTPStatus(103, "103 Early Hints")}}</dt>
- <dd>This status code is primarily intended to be used with the {{HTTPHeader("Link")}} header, letting the user agent start <a href="/en-US/docs/Web/HTML/Link_types/preload">preloading</a> resources while the server prepares a response.</dd>
-</dl>
-
-<h2 id="Successful_responses">Successful responses</h2>
-
-<dl>
- <dt>{{HTTPStatus(200, "200 OK")}}</dt>
- <dd>The request has succeeded. The meaning of the success depends on the HTTP method:
- <ul>
-  <li><code>GET</code>: The resource has been fetched and is transmitted in the message body.</li>
-  <li><code>HEAD</code>: The representation headers are included in the response without any message body.</li>
-  <li><code>PUT</code> or <code>POST</code>: The resource describing the result of the action is transmitted in the message body.</li>
-  <li><code>TRACE</code>: The message body contains the request message as received by the server.</li>
- </ul>
- </dd>
- <dt>{{HTTPStatus(201, "201 Created")}}</dt>
- <dd>The request has succeeded and a new resource has been created as a result. This is typically the response sent after <code>POST</code> requests, or some <code>PUT</code> requests.</dd>
- <dt>{{HTTPStatus(202, "202 Accepted")}}</dt>
- <dd>The request has been received but not yet acted upon. It is noncommittal, since there is no way in HTTP to later send an asynchronous response indicating the outcome of the request. It is intended for cases where another process or server handles the request, or for batch processing.</dd>
- <dt>{{HTTPStatus(203, "203 Non-Authoritative Information")}}</dt>
- <dd>This response code means the returned meta-information is not exactly the same as is available from the origin server, but is collected from a local or a third-party copy. This is mostly used for mirrors or backups of another resource. Except for that specific case, the "200 OK" response is preferred to this status.</dd>
- <dt>{{HTTPStatus(204, "204 No Content")}}</dt>
- <dd>There is no content to send for this request, but the headers may be useful. The user-agent may update its cached headers for this resource with the new ones.</dd>
- <dt>{{HTTPStatus(205, "205 Reset Content")}}</dt>
- <dd>Tells the user-agent to reset the document which sent this request.</dd>
- <dt>{{HTTPStatus(206, "206 Partial Content")}}</dt>
- <dd>This response code is used when the {{HTTPHeader("Range")}} header is sent from the client to request only part of a resource.</dd>
- <dt>{{HTTPStatus(207, "207 Multi-Status")}} ({{Glossary("WebDAV")}})</dt>
- <dd>Conveys information about multiple resources, for situations where multiple status codes might be appropriate.</dd>
- <dt>{{HTTPStatus(208, "208 Already Reported")}} ({{Glossary("WebDAV")}})</dt>
- <dd>Used inside a <code>&lt;dav:propstat&gt;</code> response element to avoid repeatedly enumerating the internal members of multiple bindings to the same collection.</dd>
- <dt>{{HTTPStatus(226, "226 IM Used")}} (<a href="https://datatracker.ietf.org/doc/html/rfc3229">HTTP Delta encoding</a>)</dt>
- <dd>The server has fulfilled a <code>GET</code> request for the resource, and the response is a representation of the result of one or more instance-manipulations applied to the current instance.</dd>
-</dl>
-
-<h2 id="Redirection_messages">Redirection messages</h2>
-
-<dl>
- <dt>{{HTTPStatus(300, "300 Multiple Choice")}}</dt>
- <dd>The request has more than one possible response. The user-agent or user should choose one of them. (There is no standardized way of choosing one of the responses, but HTML links to the possibilities are recommended so the user can pick.)</dd>
- <dt>{{HTTPStatus(301, "301 Moved Permanently")}}</dt>
- <dd>The URL of the requested resource has been changed permanently. The new URL is given in the response.</dd>
- <dt>{{HTTPStatus(302, "302 Found")}}</dt>
- <dd>This response code means that the URI of requested resource has been changed <em>temporarily</em>. Further changes in the URI might be made in the future. Therefore, this same URI should be used by the client in future requests.</dd>
- <dt>{{HTTPStatus(303, "303 See Other")}}</dt>
- <dd>The server sent this response to direct the client to get the requested resource at another URI with a GET request.</dd>
- <dt>{{HTTPStatus(304, "304 Not Modified")}}</dt>
- <dd>This is used for caching purposes. It tells the client that the response has not been modified, so the client can continue to use the same cached version of the response.</dd>
- <dt><code>305 Use Proxy</code> {{deprecated_inline}}</dt>
- <dd>Defined in a previous version of the HTTP specification to indicate that a requested response must be accessed by a proxy. It has been deprecated due to security concerns regarding in-band configuration of a proxy.</dd>
- <dt><code>306 unused</code></dt>
- <dd>This response code is no longer used; it is just reserved. It was used in a previous version of the HTTP/1.1 specification.</dd>
- <dt>{{HTTPStatus(307, "307 Temporary Redirect")}}</dt>
- <dd>The server sends this response to direct the client to get the requested resource at another URI with same method that was used in the prior request. This has the same semantics as the <code>302 Found</code> HTTP response code, with the exception that the user agent <em>must not</em> change the HTTP method used: If a <code>POST</code> was used in the first request, a <code>POST</code> must be used in the second request.</dd>
- <dt>{{HTTPStatus(308, "308 Permanent Redirect")}}</dt>
- <dd>This means that the resource is now permanently located at another URI, specified by the <code>Location:</code> HTTP Response header. This has the same semantics as the <code>301 Moved Permanently</code> HTTP response code, with the exception that the user agent <em>must not</em> change the HTTP method used: If a <code>POST</code> was used in the first request, a <code>POST</code> must be used in the second request.</dd>
-</dl>
-
-<h2 id="Client_error_responses">Client error responses</h2>
-
-<dl>
- <dt>{{HTTPStatus(400, "400 Bad Request")}}</dt>
- <dd>The server could not understand the request due to invalid syntax.</dd>
- <dt>{{HTTPStatus(401, "401 Unauthorized")}}</dt>
- <dd>Although the HTTP standard specifies "unauthorized", semantically this response means "unauthenticated". That is, the client must authenticate itself to get the requested response.</dd>
- <dt>{{HTTPStatus(402, "402 Payment Required")}} {{experimental_inline}}</dt>
- <dd>This response code is reserved for future use. The initial aim for creating this code was using it for digital payment systems, however this status code is used very rarely and no standard convention exists.</dd>
- <dt>{{HTTPStatus(403, "403 Forbidden")}}</dt>
- <dd>The client does not have access rights to the content; that is, it is unauthorized, so the server is refusing to give the requested resource. Unlike 401, the client's identity is known to the server.</dd>
- <dt>{{HTTPStatus(404, "404 Not Found")}}</dt>
- <dd>The server can not find the requested resource. In the browser, this means the URL is not recognized. In an API, this can also mean that the endpoint is valid but the resource itself does not exist. Servers may also send this response instead of 403 to hide the existence of a resource from an unauthorized client. This response code is probably the most famous one due to its frequent occurrence on the web.</dd>
- <dt>{{HTTPStatus(405, "405 Method Not Allowed")}}</dt>
- <dd>The request method is known by the server but is not supported by the target resource. For example, an API may forbid DELETE-ing a resource.</dd>
- <dt>{{HTTPStatus(406, "406 Not Acceptable")}}</dt>
- <dd>This response is sent when the web server, after performing <a href="/en-US/docs/Web/HTTP/Content_negotiation#server-driven_negotiation">server-driven content negotiation</a>, doesn't find any content that conforms to the criteria given by the user agent.</dd>
- <dt>{{HTTPStatus(407, "407 Proxy Authentication Required")}}</dt>
- <dd>This is similar to 401 but authentication is needed to be done by a proxy.</dd>
- <dt>{{HTTPStatus(408, "408 Request Timeout")}}</dt>
- <dd>This response is sent on an idle connection by some servers, even without any previous request by the client. It means that the server would like to shut down this unused connection. This response is used much more since some browsers, like Chrome, Firefox 27+, or IE9, use HTTP pre-connection mechanisms to speed up surfing. Also note that some servers merely shut down the connection without sending this message.</dd>
- <dt>{{HTTPStatus(409, "409 Conflict")}}</dt>
- <dd>This response is sent when a request conflicts with the current state of the server.</dd>
- <dt>{{HTTPStatus(410, "410 Gone")}}</dt>
- <dd>This response is sent when the requested content has been permanently deleted from server, with no forwarding address. Clients are expected to remove their caches and links to the resource. The HTTP specification intends this status code to be used for "limited-time, promotional services". APIs should not feel compelled to indicate resources that have been deleted with this status code.</dd>
- <dt>{{HTTPStatus(411, "411 Length Required")}}</dt>
- <dd>Server rejected the request because the <code>Content-Length</code> header field is not defined and the server requires it.</dd>
- <dt>{{HTTPStatus(412, "412 Precondition Failed")}}</dt>
- <dd>The client has indicated preconditions in its headers which the server does not meet.</dd>
- <dt>{{HTTPStatus(413, "413 Payload Too Large")}}</dt>
- <dd>Request entity is larger than limits defined by server; the server might close the connection or return an <code>Retry-After</code> header field.</dd>
- <dt>{{HTTPStatus(414, "414 URI Too Long")}}</dt>
- <dd>The URI requested by the client is longer than the server is willing to interpret.</dd>
- <dt>{{HTTPStatus(415, "415 Unsupported Media Type")}}</dt>
- <dd>The media format of the requested data is not supported by the server, so the server is rejecting the request.</dd>
- <dt>{{HTTPStatus(416, "416 Range Not Satisfiable")}}</dt>
- <dd>The range specified by the <code>Range</code> header field in the request can't be fulfilled; it's possible that the range is outside the size of the target URI's data.</dd>
- <dt>{{HTTPStatus(417, "417 Expectation Failed")}}</dt>
- <dd>This response code means the expectation indicated by the <code>Expect</code> request header field can't be met by the server.</dd>
- <dt>{{HTTPStatus(418, "418 I'm a teapot")}}</dt>
- <dd>The server refuses the attempt to brew coffee with a teapot.</dd>
- <dt>{{HTTPStatus(421, "421 Misdirected Request")}}</dt>
- <dd>The request was directed at a server that is not able to produce a response. This can be sent by a server that is not configured to produce responses for the combination of scheme and authority that are included in the request URI.</dd>
- <dt>{{HTTPStatus(422, "422 Unprocessable Entity")}} ({{Glossary("WebDAV")}})</dt>
- <dd>The request was well-formed but was unable to be followed due to semantic errors.</dd>
- <dt>{{HTTPStatus(423, "423 Locked")}} ({{Glossary("WebDAV")}})</dt>
- <dd>The resource that is being accessed is locked.</dd>
- <dt>{{HTTPStatus(424, "424 Failed Dependency")}} ({{Glossary("WebDAV")}})</dt>
- <dd>The request failed due to failure of a previous request.</dd>
- <dt>{{HTTPStatus(425, "425 Too Early")}} {{experimental_inline}}</dt>
- <dd>Indicates that the server is unwilling to risk processing a request that might be replayed.</dd>
- <dt>{{HTTPStatus(426, "426 Upgrade Required")}}</dt>
- <dd>The server refuses to perform the request using the current protocol but might be willing to do so after the client upgrades to a different protocol. The server sends an {{HTTPHeader("Upgrade")}} header in a 426 response to indicate the required protocol(s).</dd>
- <dt>{{HTTPStatus(428, "428 Precondition Required")}}</dt>
- <dd>The origin server requires the request to be conditional. This response is intended to prevent the 'lost update' problem, where a client GETs a resource's state, modifies it, and PUTs it back to the server, when meanwhile a third party has modified the state on the server, leading to a conflict.</dd>
- <dt>{{HTTPStatus(429, "429 Too Many Requests")}}</dt>
- <dd>The user has sent too many requests in a given amount of time ("rate limiting").</dd>
- <dt>{{HTTPStatus(431, "431 Request Header Fields Too Large")}}</dt>
- <dd>The server is unwilling to process the request because its header fields are too large. The request may be resubmitted after reducing the size of the request header fields.</dd>
- <dt>{{HTTPStatus(451, "451 Unavailable For Legal Reasons")}}</dt>
- <dd>The user-agent requested a resource that cannot legally be provided, such as a web page censored by a government.</dd>
-</dl>
-
-<h2 id="Server_error_responses">Server error responses</h2>
-
-<dl>
- <dt>{{HTTPStatus(500, "500 Internal Server Error")}}</dt>
- <dd>The server has encountered a situation it doesn't know how to handle.</dd>
- <dt>{{HTTPStatus(501, "501 Not Implemented")}}</dt>
- <dd>The request method is not supported by the server and cannot be handled. The only methods that servers are required to support (and therefore that must not return this code) are <code>GET</code> and <code>HEAD</code>.</dd>
- <dt>{{HTTPStatus(502, "502 Bad Gateway")}}</dt>
- <dd>This error response means that the server, while working as a gateway to get a response needed to handle the request, got an invalid response.</dd>
- <dt>{{HTTPStatus(503, "503 Service Unavailable")}}</dt>
- <dd>The server is not ready to handle the request. Common causes are a server that is down for maintenance or that is overloaded. Note that together with this response, a user-friendly page explaining the problem should be sent. This response should be used for temporary conditions and the <code>Retry-After:</code> HTTP header should, if possible, contain the estimated time before the recovery of the service. The webmaster must also take care about the caching-related headers that are sent along with this response, as these temporary condition responses should usually not be cached.</dd>
- <dt>{{HTTPStatus(504, "504 Gateway Timeout")}}</dt>
- <dd>This error response is given when the server is acting as a gateway and cannot get a response in time.</dd>
- <dt>{{HTTPStatus(505, "505 HTTP Version Not Supported")}}</dt>
- <dd>The HTTP version used in the request is not supported by the server.</dd>
- <dt>{{HTTPStatus(506, "506 Variant Also Negotiates")}}</dt>
- <dd>The server has an internal configuration error: the chosen variant resource is configured to engage in transparent content negotiation itself, and is therefore not a proper end point in the negotiation process.</dd>
- <dt>{{HTTPStatus(507, "507 Insufficient Storage")}} ({{Glossary("WebDAV")}})</dt>
- <dd>The method could not be performed on the resource because the server is unable to store the representation needed to successfully complete the request.</dd>
- <dt>{{HTTPStatus(508, "508 Loop Detected")}} ({{Glossary("WebDAV")}})</dt>
- <dd>The server detected an infinite loop while processing the request.</dd>
- <dt>{{HTTPStatus(510, "510 Not Extended")}}</dt>
- <dd>Further extensions to the request are required for the server to fulfill it.</dd>
- <dt>{{HTTPStatus(511, "511 Network Authentication Required")}}</dt>
- <dd>The 511 status code indicates that the client needs to authenticate to gain network access.</dd>
-</dl>
-
-<h2 id="Browser_compatibility">Browser compatibility</h2>
-
-<p>{{Compat("http.status")}}</p>
-
-<h2 id="See_also">See also</h2>
-
-<ul>
- <li><a href="https://en.wikipedia.org/wiki/List_of_HTTP_status_codes">List of HTTP status codes on Wikipedia</a></li>
- <li><a href="https://www.iana.org/assignments/http-status-codes/http-status-codes.xhtml">IANA official registry of HTTP status codes </a></li>
-</ul>
+{{HTTPSidebar}}
+
+HTTP response status codes indicate whether a specific [HTTP](/en-US/docs/Web/HTTP) request has been successfully completed. Responses are grouped in five classes:
+
+1.  [Informational responses](#information_responses) (`100`–`199`)
+2.  [Successful responses](#successful_responses) (`200`–`299`)
+3.  [Redirects](#redirection_messages) (`300`–`399`)
+4.  [Client errors](#client_error_responses) (`400`–`499`)
+5.  [Server errors](#server_error_responses) (`500`–`599`)
+
+The below status codes are defined by [section 10 of RFC 2616](https://datatracker.ietf.org/doc/html/rfc2616#section-10). You can find an updated specification in [RFC 7231](https://datatracker.ietf.org/doc/html/rfc7231#section-6.5.1).
+
+> **Note:** If you receive a response that is not in this list, it is a non-standard response, possibly custom to the server's software.
+
+## Information responses
+
+- {{HTTPStatus(100, "100 Continue")}}
+  - : This interim response indicates that everything so far is OK and that the client should continue the request, or ignore the response if the request is already finished.
+- {{HTTPStatus(101, "101 Switching Protocol")}}
+  - : This code is sent in response to an {{HTTPHeader("Upgrade")}} request header from the client, and indicates the protocol the server is switching to.
+- {{HTTPStatus(102, "102 Processing")}} ({{Glossary("WebDAV")}})
+  - : This code indicates that the server has received and is processing the request, but no response is available yet.
+- {{HTTPStatus(103, "103 Early Hints")}}
+  - : This status code is primarily intended to be used with the {{HTTPHeader("Link")}} header, letting the user agent start [preloading](/en-US/docs/Web/HTML/Link_types/preload) resources while the server prepares a response.
+
+## Successful responses
+
+- {{HTTPStatus(200, "200 OK")}}
+
+  - : The request has succeeded. The meaning of the success depends on the HTTP method:
+
+    - `GET`: The resource has been fetched and is transmitted in the message body.
+    - `HEAD`: The representation headers are included in the response without any message body.
+    - `PUT` or `POST`: The resource describing the result of the action is transmitted in the message body.
+    - `TRACE`: The message body contains the request message as received by the server.
+
+- {{HTTPStatus(201, "201 Created")}}
+  - : The request has succeeded and a new resource has been created as a result. This is typically the response sent after `POST` requests, or some `PUT` requests.
+- {{HTTPStatus(202, "202 Accepted")}}
+  - : The request has been received but not yet acted upon. It is noncommittal, since there is no way in HTTP to later send an asynchronous response indicating the outcome of the request. It is intended for cases where another process or server handles the request, or for batch processing.
+- {{HTTPStatus(203, "203 Non-Authoritative Information")}}
+  - : This response code means the returned meta-information is not exactly the same as is available from the origin server, but is collected from a local or a third-party copy. This is mostly used for mirrors or backups of another resource. Except for that specific case, the "200 OK" response is preferred to this status.
+- {{HTTPStatus(204, "204 No Content")}}
+  - : There is no content to send for this request, but the headers may be useful. The user-agent may update its cached headers for this resource with the new ones.
+- {{HTTPStatus(205, "205 Reset Content")}}
+  - : Tells the user-agent to reset the document which sent this request.
+- {{HTTPStatus(206, "206 Partial Content")}}
+  - : This response code is used when the {{HTTPHeader("Range")}} header is sent from the client to request only part of a resource.
+- {{HTTPStatus(207, "207 Multi-Status")}} ({{Glossary("WebDAV")}})
+  - : Conveys information about multiple resources, for situations where multiple status codes might be appropriate.
+- {{HTTPStatus(208, "208 Already Reported")}} ({{Glossary("WebDAV")}})
+  - : Used inside a `<dav:propstat>` response element to avoid repeatedly enumerating the internal members of multiple bindings to the same collection.
+- {{HTTPStatus(226, "226 IM Used")}} ([HTTP Delta encoding](https://datatracker.ietf.org/doc/html/rfc3229))
+  - : The server has fulfilled a `GET` request for the resource, and the response is a representation of the result of one or more instance-manipulations applied to the current instance.
+
+## Redirection messages
+
+- {{HTTPStatus(300, "300 Multiple Choice")}}
+  - : The request has more than one possible response. The user-agent or user should choose one of them. (There is no standardized way of choosing one of the responses, but HTML links to the possibilities are recommended so the user can pick.)
+- {{HTTPStatus(301, "301 Moved Permanently")}}
+  - : The URL of the requested resource has been changed permanently. The new URL is given in the response.
+- {{HTTPStatus(302, "302 Found")}}
+  - : This response code means that the URI of requested resource has been changed _temporarily_. Further changes in the URI might be made in the future. Therefore, this same URI should be used by the client in future requests.
+- {{HTTPStatus(303, "303 See Other")}}
+  - : The server sent this response to direct the client to get the requested resource at another URI with a GET request.
+- {{HTTPStatus(304, "304 Not Modified")}}
+  - : This is used for caching purposes. It tells the client that the response has not been modified, so the client can continue to use the same cached version of the response.
+- `305 Use Proxy` {{deprecated_inline}}
+  - : Defined in a previous version of the HTTP specification to indicate that a requested response must be accessed by a proxy. It has been deprecated due to security concerns regarding in-band configuration of a proxy.
+- `306 unused`
+  - : This response code is no longer used; it is just reserved. It was used in a previous version of the HTTP/1.1 specification.
+- {{HTTPStatus(307, "307 Temporary Redirect")}}
+  - : The server sends this response to direct the client to get the requested resource at another URI with same method that was used in the prior request. This has the same semantics as the `302 Found` HTTP response code, with the exception that the user agent _must not_ change the HTTP method used: If a `POST` was used in the first request, a `POST` must be used in the second request.
+- {{HTTPStatus(308, "308 Permanent Redirect")}}
+  - : This means that the resource is now permanently located at another URI, specified by the `Location:` HTTP Response header. This has the same semantics as the `301 Moved Permanently` HTTP response code, with the exception that the user agent _must not_ change the HTTP method used: If a `POST` was used in the first request, a `POST` must be used in the second request.
+
+## Client error responses
+
+- {{HTTPStatus(400, "400 Bad Request")}}
+  - : The server could not understand the request due to invalid syntax.
+- {{HTTPStatus(401, "401 Unauthorized")}}
+  - : Although the HTTP standard specifies "unauthorized", semantically this response means "unauthenticated". That is, the client must authenticate itself to get the requested response.
+- {{HTTPStatus(402, "402 Payment Required")}} {{experimental_inline}}
+  - : This response code is reserved for future use. The initial aim for creating this code was using it for digital payment systems, however this status code is used very rarely and no standard convention exists.
+- {{HTTPStatus(403, "403 Forbidden")}}
+  - : The client does not have access rights to the content; that is, it is unauthorized, so the server is refusing to give the requested resource. Unlike 401, the client's identity is known to the server.
+- {{HTTPStatus(404, "404 Not Found")}}
+  - : The server can not find the requested resource. In the browser, this means the URL is not recognized. In an API, this can also mean that the endpoint is valid but the resource itself does not exist. Servers may also send this response instead of 403 to hide the existence of a resource from an unauthorized client. This response code is probably the most famous one due to its frequent occurrence on the web.
+- {{HTTPStatus(405, "405 Method Not Allowed")}}
+  - : The request method is known by the server but is not supported by the target resource. For example, an API may forbid DELETE-ing a resource.
+- {{HTTPStatus(406, "406 Not Acceptable")}}
+  - : This response is sent when the web server, after performing [server-driven content negotiation](/en-US/docs/Web/HTTP/Content_negotiation#server-driven_negotiation), doesn't find any content that conforms to the criteria given by the user agent.
+- {{HTTPStatus(407, "407 Proxy Authentication Required")}}
+  - : This is similar to 401 but authentication is needed to be done by a proxy.
+- {{HTTPStatus(408, "408 Request Timeout")}}
+  - : This response is sent on an idle connection by some servers, even without any previous request by the client. It means that the server would like to shut down this unused connection. This response is used much more since some browsers, like Chrome, Firefox 27+, or IE9, use HTTP pre-connection mechanisms to speed up surfing. Also note that some servers merely shut down the connection without sending this message.
+- {{HTTPStatus(409, "409 Conflict")}}
+  - : This response is sent when a request conflicts with the current state of the server.
+- {{HTTPStatus(410, "410 Gone")}}
+  - : This response is sent when the requested content has been permanently deleted from server, with no forwarding address. Clients are expected to remove their caches and links to the resource. The HTTP specification intends this status code to be used for "limited-time, promotional services". APIs should not feel compelled to indicate resources that have been deleted with this status code.
+- {{HTTPStatus(411, "411 Length Required")}}
+  - : Server rejected the request because the `Content-Length` header field is not defined and the server requires it.
+- {{HTTPStatus(412, "412 Precondition Failed")}}
+  - : The client has indicated preconditions in its headers which the server does not meet.
+- {{HTTPStatus(413, "413 Payload Too Large")}}
+  - : Request entity is larger than limits defined by server; the server might close the connection or return an `Retry-After` header field.
+- {{HTTPStatus(414, "414 URI Too Long")}}
+  - : The URI requested by the client is longer than the server is willing to interpret.
+- {{HTTPStatus(415, "415 Unsupported Media Type")}}
+  - : The media format of the requested data is not supported by the server, so the server is rejecting the request.
+- {{HTTPStatus(416, "416 Range Not Satisfiable")}}
+  - : The range specified by the `Range` header field in the request can't be fulfilled; it's possible that the range is outside the size of the target URI's data.
+- {{HTTPStatus(417, "417 Expectation Failed")}}
+  - : This response code means the expectation indicated by the `Expect` request header field can't be met by the server.
+- {{HTTPStatus(418, "418 I'm a teapot")}}
+  - : The server refuses the attempt to brew coffee with a teapot.
+- {{HTTPStatus(421, "421 Misdirected Request")}}
+  - : The request was directed at a server that is not able to produce a response. This can be sent by a server that is not configured to produce responses for the combination of scheme and authority that are included in the request URI.
+- {{HTTPStatus(422, "422 Unprocessable Entity")}} ({{Glossary("WebDAV")}})
+  - : The request was well-formed but was unable to be followed due to semantic errors.
+- {{HTTPStatus(423, "423 Locked")}} ({{Glossary("WebDAV")}})
+  - : The resource that is being accessed is locked.
+- {{HTTPStatus(424, "424 Failed Dependency")}} ({{Glossary("WebDAV")}})
+  - : The request failed due to failure of a previous request.
+- {{HTTPStatus(425, "425 Too Early")}} {{experimental_inline}}
+  - : Indicates that the server is unwilling to risk processing a request that might be replayed.
+- {{HTTPStatus(426, "426 Upgrade Required")}}
+  - : The server refuses to perform the request using the current protocol but might be willing to do so after the client upgrades to a different protocol. The server sends an {{HTTPHeader("Upgrade")}} header in a 426 response to indicate the required protocol(s).
+- {{HTTPStatus(428, "428 Precondition Required")}}
+  - : The origin server requires the request to be conditional. This response is intended to prevent the 'lost update' problem, where a client GETs a resource's state, modifies it, and PUTs it back to the server, when meanwhile a third party has modified the state on the server, leading to a conflict.
+- {{HTTPStatus(429, "429 Too Many Requests")}}
+  - : The user has sent too many requests in a given amount of time ("rate limiting").
+- {{HTTPStatus(431, "431 Request Header Fields Too Large")}}
+  - : The server is unwilling to process the request because its header fields are too large. The request may be resubmitted after reducing the size of the request header fields.
+- {{HTTPStatus(451, "451 Unavailable For Legal Reasons")}}
+  - : The user-agent requested a resource that cannot legally be provided, such as a web page censored by a government.
+
+## Server error responses
+
+- {{HTTPStatus(500, "500 Internal Server Error")}}
+  - : The server has encountered a situation it doesn't know how to handle.
+- {{HTTPStatus(501, "501 Not Implemented")}}
+  - : The request method is not supported by the server and cannot be handled. The only methods that servers are required to support (and therefore that must not return this code) are `GET` and `HEAD`.
+- {{HTTPStatus(502, "502 Bad Gateway")}}
+  - : This error response means that the server, while working as a gateway to get a response needed to handle the request, got an invalid response.
+- {{HTTPStatus(503, "503 Service Unavailable")}}
+  - : The server is not ready to handle the request. Common causes are a server that is down for maintenance or that is overloaded. Note that together with this response, a user-friendly page explaining the problem should be sent. This response should be used for temporary conditions and the `Retry-After:` HTTP header should, if possible, contain the estimated time before the recovery of the service. The webmaster must also take care about the caching-related headers that are sent along with this response, as these temporary condition responses should usually not be cached.
+- {{HTTPStatus(504, "504 Gateway Timeout")}}
+  - : This error response is given when the server is acting as a gateway and cannot get a response in time.
+- {{HTTPStatus(505, "505 HTTP Version Not Supported")}}
+  - : The HTTP version used in the request is not supported by the server.
+- {{HTTPStatus(506, "506 Variant Also Negotiates")}}
+  - : The server has an internal configuration error: the chosen variant resource is configured to engage in transparent content negotiation itself, and is therefore not a proper end point in the negotiation process.
+- {{HTTPStatus(507, "507 Insufficient Storage")}} ({{Glossary("WebDAV")}})
+  - : The method could not be performed on the resource because the server is unable to store the representation needed to successfully complete the request.
+- {{HTTPStatus(508, "508 Loop Detected")}} ({{Glossary("WebDAV")}})
+  - : The server detected an infinite loop while processing the request.
+- {{HTTPStatus(510, "510 Not Extended")}}
+  - : Further extensions to the request are required for the server to fulfill it.
+- {{HTTPStatus(511, "511 Network Authentication Required")}}
+  - : The 511 status code indicates that the client needs to authenticate to gain network access.
+
+## Browser compatibility
+
+{{Compat("http.status")}}
+
+## See also
+
+- [List of HTTP status codes on Wikipedia](https://en.wikipedia.org/wiki/List_of_HTTP_status_codes)
+- [IANA official registry of HTTP status codes](https://www.iana.org/assignments/http-status-codes/http-status-codes.xhtml)

From ca2362f5e24e3d5e91d928ad4f7f2d904c064169 Mon Sep 17 00:00:00 2001
From: "Michael[tm] Smith" <mike@w3.org>
Date: Fri, 13 Aug 2021 02:18:48 +0900
Subject: [PATCH 3/9] Fix some character-styling conversion failures

---
 .../http/headers/content-security-policy/navigate-to/index.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/files/en-us/web/http/headers/content-security-policy/navigate-to/index.md b/files/en-us/web/http/headers/content-security-policy/navigate-to/index.md
index 0e178e413807712..004d3b4c26abda3 100644
--- a/files/en-us/web/http/headers/content-security-policy/navigate-to/index.md
+++ b/files/en-us/web/http/headers/content-security-policy/navigate-to/index.md
@@ -14,11 +14,11 @@ browser-compat: http.headers.csp.Content-Security-Policy.navigate-to
 {{HTTPSidebar}}
 
 The HTTP {{HTTPHeader("Content-Security-Policy")}} (CSP)
-**`navigate`\*\***`-to`** directive
+**`navigate-to`** directive
 restricts the URLs to which a document can initiate navigations by any means including
 {{HTMLElement("form")}} (if {{CSP("form-action")}} is not specified),
 {{HTMLElement("a")}}, {{DOMxRef("window.location")}}, {{DOMxRef("window.open")}}, etc.
-This is an enforcement on what navigations this document initiates **not\*\*
+This is an enforcement on what navigations this document initiates, **not**
 on what this document is allowed to navigate to.
 
 > **Note:** If the {{CSP("form-action")}} directive is present,

From ad861b0e9d5e4210e7efd1b4b629527f2db7488a Mon Sep 17 00:00:00 2001
From: "Michael[tm] Smith" <mike@w3.org>
Date: Fri, 13 Aug 2021 02:49:41 +0900
Subject: [PATCH 4/9] Normalize list spacing

---
 files/en-us/web/http/authentication/index.md  |  6 +++---
 .../index.md                                  |  6 +++---
 files/en-us/web/http/cors/errors/index.md     |  4 ++--
 files/en-us/web/http/cors/index.md            |  4 ++--
 .../web/http/headers/set-cookie/index.md      |  4 ++--
 files/en-us/web/http/headers/upgrade/index.md |  4 ++--
 .../web/http/headers/user-agent/index.md      | 10 +++++-----
 files/en-us/web/http/messages/index.md        | 20 +++++++++----------
 files/en-us/web/http/overview/index.md        |  8 ++++----
 files/en-us/web/http/redirections/index.md    | 16 +++++++--------
 files/en-us/web/http/session/index.md         | 18 ++++++++---------
 files/en-us/web/http/status/index.md          | 10 +++++-----
 12 files changed, 55 insertions(+), 55 deletions(-)

diff --git a/files/en-us/web/http/authentication/index.md b/files/en-us/web/http/authentication/index.md
index 6eb3adb27cad06c..1683831a4718293 100644
--- a/files/en-us/web/http/authentication/index.md
+++ b/files/en-us/web/http/authentication/index.md
@@ -18,9 +18,9 @@ HTTP provides a general framework for access control and authentication. This pa
 
 The challenge and response flow works like this:
 
-1.  The server responds to a client with a {{HTTPStatus("401")}} (Unauthorized) response status and provides information on how to authorize with a {{HTTPHeader("WWW-Authenticate")}} response header containing at least one challenge.
-2.  A client that wants to authenticate itself with the server can then do so by including an {{HTTPHeader("Authorization")}} request header with the credentials.
-3.  Usually a client will present a password prompt to the user and will then issue the request including the correct `Authorization` header.
+1. The server responds to a client with a {{HTTPStatus("401")}} (Unauthorized) response status and provides information on how to authorize with a {{HTTPHeader("WWW-Authenticate")}} response header containing at least one challenge.
+2. A client that wants to authenticate itself with the server can then do so by including an {{HTTPHeader("Authorization")}} request header with the credentials.
+3. Usually a client will present a password prompt to the user and will then issue the request including the correct `Authorization` header.
 
 ![A sequence diagram illustrating HTTP messages between a client and a server lifeline.](httpauth.png "Sequence Diagram of Client-server HTTP Authentication")
 
diff --git a/files/en-us/web/http/basics_of_http/choosing_between_www_and_non-www_urls/index.md b/files/en-us/web/http/basics_of_http/choosing_between_www_and_non-www_urls/index.md
index 8291ad6272a2891..28032714f7eb6a5 100644
--- a/files/en-us/web/http/basics_of_http/choosing_between_www_and_non-www_urls/index.md
+++ b/files/en-us/web/http/basics_of_http/choosing_between_www_and_non-www_urls/index.md
@@ -33,9 +33,9 @@ In this case, you need to configure the server receiving the HTTP requests (whic
 
 Example:
 
-1.  A server receives a request for `http://www.example.org/whaddup` (when the canonical domain is example.org)
-2.  The server answers with a code {{HTTPStatus(301)}} with the header `{{HTTPHeader("Location")}}: http://example.org/whaddup`.
-3.  The client issues a request to the canonical domain: `http://example.org/whatddup`
+1. A server receives a request for `http://www.example.org/whaddup` (when the canonical domain is example.org)
+2. The server answers with a code {{HTTPStatus(301)}} with the header `{{HTTPHeader("Location")}}: http://example.org/whaddup`.
+3. The client issues a request to the canonical domain: `http://example.org/whatddup`
 
 The[ HTML5 boilerplate project](https://github.com/h5bp/html5-boilerplate) has an example on [how to configure an Apache server to redirect one domain to the other](https://github.com/h5bp/html5-boilerplate/blob/7a22a33d4041c479d0962499e853501073811887/.htaccess#L219-L258).
 
diff --git a/files/en-us/web/http/cors/errors/index.md b/files/en-us/web/http/cors/errors/index.md
index b5cbf7342a21eba..64e127f3740b4b0 100644
--- a/files/en-us/web/http/cors/errors/index.md
+++ b/files/en-us/web/http/cors/errors/index.md
@@ -22,8 +22,8 @@ If the CORS configuration isn't setup correctly, the browser console will presen
 
 To understand the underlying issue with the CORS configuration, you need to find out which request is at fault and why. These steps may help you do so:
 
-1.  Navigate to the web site or web app in question and open the [Developer Tools](/en-US/docs/Tools).
-2.  Now try to reproduce the failing transaction and check the [console](/en-US/docs/Tools/Web_Console) if you are seeing a CORS violation error message. It will probably look like this:
+1. Navigate to the web site or web app in question and open the [Developer Tools](/en-US/docs/Tools).
+2. Now try to reproduce the failing transaction and check the [console](/en-US/docs/Tools/Web_Console) if you are seeing a CORS violation error message. It will probably look like this:
 
 ![Firefox console showing CORS error](cors-error2.png)
 
diff --git a/files/en-us/web/http/cors/index.md b/files/en-us/web/http/cors/index.md
index 1edccc762f88e34..8c1afd6e6f3833e 100644
--- a/files/en-us/web/http/cors/index.md
+++ b/files/en-us/web/http/cors/index.md
@@ -255,8 +255,8 @@ Until browsers catch up with the spec, you may be able to work around this limit
 
 If that's not possible, then another way is to:
 
-1.  Make a [simple request](#simple_requests) (using {{domxref("Response.url")}} for the Fetch API, or {{domxref("XMLHttpRequest.responseURL")}}) to determine what URL the real preflighted request would end up at.
-2.  Make another request (the _real_ request) using the URL you obtained from `Response.url` or `XMLHttpRequest.responseURL` in the first step.
+1. Make a [simple request](#simple_requests) (using {{domxref("Response.url")}} for the Fetch API, or {{domxref("XMLHttpRequest.responseURL")}}) to determine what URL the real preflighted request would end up at.
+2. Make another request (the _real_ request) using the URL you obtained from `Response.url` or `XMLHttpRequest.responseURL` in the first step.
 
 However, if the request is one that triggers a preflight due to the presence of the `Authorization` header in the request, you won't be able to work around the limitation using the steps above. And you won't be able to work around it at all unless you have control over the server the request is being made to.
 
diff --git a/files/en-us/web/http/headers/set-cookie/index.md b/files/en-us/web/http/headers/set-cookie/index.md
index 93762426aae4c57..19c859721e10e1a 100644
--- a/files/en-us/web/http/headers/set-cookie/index.md
+++ b/files/en-us/web/http/headers/set-cookie/index.md
@@ -140,8 +140,8 @@ Set-Cookie: <cookie-name>=<cookie-value>; Domain=<domain-value>; Secure; HttpOnl
 
     > **Note:** Standards related to the [SameSite Cookies](/en-US/docs/Web/HTTP/Headers/Set-Cookie/SameSite) recently changed such that:
     >
-    > 1.  The cookie-sending behavior if `SameSite` is not specified is `SameSite=Lax`. Previously the default was that cookies were sent for all requests.
-    > 2.  Cookies with `SameSite=None` must now
+    > 1. The cookie-sending behavior if `SameSite` is not specified is `SameSite=Lax`. Previously the default was that cookies were sent for all requests.
+    > 2. Cookies with `SameSite=None` must now
     >     also specify the `Secure` attribute (i.e. they require a secure context).
     >
     > The options below covers the new behavior. See the [Browser compatibility](/en-US/docs/Web/HTTP/Headers/Set-Cookie/SameSite#browser_compatibility) table for information about specific browser implementation (rows: "`SameSite`: Defaults to `Lax`" and "`SameSite`: Secure context required").
diff --git a/files/en-us/web/http/headers/upgrade/index.md b/files/en-us/web/http/headers/upgrade/index.md
index a2c28aed398e203..d0d2fe513d9df9e 100644
--- a/files/en-us/web/http/headers/upgrade/index.md
+++ b/files/en-us/web/http/headers/upgrade/index.md
@@ -48,13 +48,13 @@ The server can choose to ignore the request, for any reason, in which case it sh
 
 If the server decides to upgrade the connection, it must:
 
-1.  Send back a {{HTTPStatus(101, "101 Switching Protocols")}} response status with an `Upgrade` header that specifies the protocol(s) being switched to. For example:
+1. Send back a {{HTTPStatus(101, "101 Switching Protocols")}} response status with an `Upgrade` header that specifies the protocol(s) being switched to. For example:
 
         HTTP/1.1 101 Switching Protocols
         Upgrade: foo/2
         Connection: Upgrade
 
-2.  Send a response to the original request *using the new protocol* (the server may only switch to a protocol with which it can complete the original request).
+2. Send a response to the original request *using the new protocol* (the server may only switch to a protocol with which it can complete the original request).
 
 A server may also send the header as part of a {{HTTPStatus("426")}} `Upgrade Required` response, to indicate that the server won't perform the request using the current protocol, but might do so if the protocol is changed. The client can then request a protocol change using the process above.
 
diff --git a/files/en-us/web/http/headers/user-agent/index.md b/files/en-us/web/http/headers/user-agent/index.md
index 9452f5ce9a790f5..dc652c6f6009dc2 100644
--- a/files/en-us/web/http/headers/user-agent/index.md
+++ b/files/en-us/web/http/headers/user-agent/index.md
@@ -54,11 +54,11 @@ For more on Firefox- and Gecko-based user agent strings, see the [Firefox user a
 
     Mozilla/5.0 (platform; rv:geckoversion) Gecko/geckotrail Firefox/firefoxversion
 
-1.  `Mozilla/5.0` is the general token that says the browser is Mozilla-compatible. For historical reasons, almost every browser today sends it.
-2.  **_platform_** describes the native platform the browser is running on (Windows, Mac, Linux, Android, etc.), and if it's a mobile phone. {{Glossary("Firefox OS")}} phones say `Mobile` — the web is the platform. Note that **_platform_** can consist of multiple "`; `"-separated tokens. See below for further details and examples.
-3.  **rv:_geckoversion_** indicates the release version of Gecko (such as "_17.0_"). In recent browsers, **_geckoversion_** is the same as **_firefoxversion_**.
-4.  **_Gecko/geckotrail_** indicates that the browser is based on Gecko. (On Desktop, **_geckotrail_** is always the fixed string `20100101`.)
-5.  **_Firefox/firefoxversion_** indicates the browser is Firefox, and provides the version (such as "_17.0"_).
+1. `Mozilla/5.0` is the general token that says the browser is Mozilla-compatible. For historical reasons, almost every browser today sends it.
+2. **_platform_** describes the native platform the browser is running on (Windows, Mac, Linux, Android, etc.), and if it's a mobile phone. {{Glossary("Firefox OS")}} phones say `Mobile` — the web is the platform. Note that **_platform_** can consist of multiple "`;`"-separated tokens. See below for further details and examples.
+3. **rv:_geckoversion_** indicates the release version of Gecko (such as "_17.0_"). In recent browsers, **_geckoversion_** is the same as **_firefoxversion_**.
+4. **_Gecko/geckotrail_** indicates that the browser is based on Gecko. (On Desktop, **_geckotrail_** is always the fixed string `20100101`.)
+5. **_Firefox/firefoxversion_** indicates the browser is Firefox, and provides the version (such as "_17.0"_).
 
 ### Examples
 
diff --git a/files/en-us/web/http/messages/index.md b/files/en-us/web/http/messages/index.md
index e8c31e020bb8203..d0e45124702e90b 100644
--- a/files/en-us/web/http/messages/index.md
+++ b/files/en-us/web/http/messages/index.md
@@ -20,10 +20,10 @@ The HTTP/2 binary framing mechanism has been designed to not require any alterat
 
 HTTP requests, and responses, share similar structure and are composed of:
 
-1.  A _start-line_ describing the requests to be implemented, or its status of whether successful or a failure. This start-line is always a single line.
-2.  An optional set of _HTTP headers_ specifying the request, or describing the body included in the message.
-3.  A blank line indicating all meta-information for the request has been sent.
-4.  An optional _body_ containing data associated with the request (like content of an HTML form), or the document associated with a response. The presence of the body and its size is specified by the start-line and HTTP headers.
+1. A _start-line_ describing the requests to be implemented, or its status of whether successful or a failure. This start-line is always a single line.
+2. An optional set of _HTTP headers_ specifying the request, or describing the body included in the message.
+3. A blank line indicating all meta-information for the request has been sent.
+4. An optional _body_ containing data associated with the request (like content of an HTML form), or the document associated with a response. The presence of the body and its size is specified by the start-line and HTTP headers.
 
 The start-line and HTTP headers of the HTTP message are collectively known as the _head_ of the requests, whereas its payload is known as the _body_.
 
@@ -35,8 +35,8 @@ The start-line and HTTP headers of the HTTP message are collectively known as th
 
 HTTP requests are messages sent by the client to initiate an action on the server. Their _start-line_ contain three elements:
 
-1.  An _[HTTP method](/en-US/docs/Web/HTTP/Methods)_, a verb (like {{HTTPMethod("GET")}}, {{HTTPMethod("PUT")}} or {{HTTPMethod("POST")}}) or a noun (like {{HTTPMethod("HEAD")}} or {{HTTPMethod("OPTIONS")}}), that describes the action to be performed. For example, `GET` indicates that a resource should be fetched or `POST` means that data is pushed to the server (creating or modifying a resource, or generating a temporary document to send back).
-2.  The _request target_, usually a {{glossary("URL")}}, or the absolute path of the protocol, port, and domain are usually characterized by the request context. The format of this request target varies between different HTTP methods. It can be
+1. An _[HTTP method](/en-US/docs/Web/HTTP/Methods)_, a verb (like {{HTTPMethod("GET")}}, {{HTTPMethod("PUT")}} or {{HTTPMethod("POST")}}) or a noun (like {{HTTPMethod("HEAD")}} or {{HTTPMethod("OPTIONS")}}), that describes the action to be performed. For example, `GET` indicates that a resource should be fetched or `POST` means that data is pushed to the server (creating or modifying a resource, or generating a temporary document to send back).
+2. The _request target_, usually a {{glossary("URL")}}, or the absolute path of the protocol, port, and domain are usually characterized by the request context. The format of this request target varies between different HTTP methods. It can be
 
     - An absolute path, ultimately followed by a `'?'` and query string. This is the most common form, known as the _origin form_, and is used with `GET`, `POST`, `HEAD`, and `OPTIONS` methods.
       `POST / HTTP/1.1 GET /background.png HTTP/1.0 HEAD /test.html?query=alibaba HTTP/1.1 OPTIONS /anypage.html HTTP/1.0`
@@ -47,7 +47,7 @@ HTTP requests are messages sent by the client to initiate an action on the serve
     - The _asterisk form_, a simple asterisk (`'*'`) is used with `OPTIONS`, representing the server as a whole.
       `OPTIONS * HTTP/1.1`
 
-3.  The _HTTP version_, which defines the structure of the remaining message, acting as an indicator of the expected version to use for the response.
+3. The _HTTP version_, which defines the structure of the remaining message, acting as an indicator of the expected version to use for the response.
 
 ### Headers
 
@@ -76,9 +76,9 @@ Bodies can be broadly divided into two categories:
 
 The start line of an HTTP response, called the _status line_, contains the following information:
 
-1.  The _protocol version_, usually `HTTP/1.1`.
-2.  A _status code_, indicating success or failure of the request. Common status codes are {{HTTPStatus("200")}}, {{HTTPStatus("404")}}, or {{HTTPStatus("302")}}
-3.  A _status text_. A brief, purely informational, textual description of the status code to help a human understand the HTTP message.
+1. The _protocol version_, usually `HTTP/1.1`.
+2. A _status code_, indicating success or failure of the request. Common status codes are {{HTTPStatus("200")}}, {{HTTPStatus("404")}}, or {{HTTPStatus("302")}}
+3. A _status text_. A brief, purely informational, textual description of the status code to help a human understand the HTTP message.
 
 A typical status line looks like: `HTTP/1.1 404 Not Found`.
 
diff --git a/files/en-us/web/http/overview/index.md b/files/en-us/web/http/overview/index.md
index 81da186c24a4c8f..dbca02c49765fd6 100644
--- a/files/en-us/web/http/overview/index.md
+++ b/files/en-us/web/http/overview/index.md
@@ -99,14 +99,14 @@ Here is a list of common features controllable with HTTP.
 
 When a client wants to communicate with a server, either the final server or an intermediate proxy, it performs the following steps:
 
-1.  Open a TCP connection: The TCP connection is used to send a request, or several, and receive an answer. The client may open a new connection, reuse an existing connection, or open several TCP connections to the servers.
-2.  Send an HTTP message: HTTP messages (before HTTP/2) are human-readable. With HTTP/2, these simple messages are encapsulated in frames, making them impossible to read directly, but the principle remains the same. For example:
+1. Open a TCP connection: The TCP connection is used to send a request, or several, and receive an answer. The client may open a new connection, reuse an existing connection, or open several TCP connections to the servers.
+2. Send an HTTP message: HTTP messages (before HTTP/2) are human-readable. With HTTP/2, these simple messages are encapsulated in frames, making them impossible to read directly, but the principle remains the same. For example:
 
         GET / HTTP/1.1
         Host: developer.mozilla.org
         Accept-Language: fr
 
-3.  Read the response sent by the server, such as:
+3. Read the response sent by the server, such as:
 
         HTTP/1.1 200 OK
         Date: Sat, 09 Oct 2010 14:28:02 GMT
@@ -119,7 +119,7 @@ When a client wants to communicate with a server, either the final server or an
 
         <!DOCTYPE html... (here comes the 29769 bytes of the requested web page)
 
-4.  Close or reuse the connection for further requests.
+4. Close or reuse the connection for further requests.
 
 If HTTP pipelining is activated, several requests can be sent without waiting for the first response to be fully received. HTTP pipelining has proven difficult to implement in existing networks, where old pieces of software coexist with modern versions. HTTP pipelining has been superseded in HTTP/2 with more robust multiplexing requests within a frame.
 
diff --git a/files/en-us/web/http/redirections/index.md b/files/en-us/web/http/redirections/index.md
index 3fcd95c5ade2fc1..cc1d47d76ec83ae 100644
--- a/files/en-us/web/http/redirections/index.md
+++ b/files/en-us/web/http/redirections/index.md
@@ -25,9 +25,9 @@ When browsers receive a redirect, they immediately load the new URL provided in
 
 There are several types of redirects, sorted into three categories:
 
-1.  [Permanent redirections](#permanent_redirections)
-2.  [Temporary redirections](#temporary_redirections)
-3.  [Special redirections](#special_redirections)
+1. [Permanent redirections](#permanent_redirections)
+2. [Temporary redirections](#temporary_redirections)
+3. [Special redirections](#special_redirections)
 
 ### Permanent redirections
 
@@ -67,8 +67,8 @@ Search engine robots and other crawlers don't memorize the new, temporary URL. T
 
 HTTP redirects aren't the only way to define redirections. There are two others:
 
-1.  HTML redirections with the {{HTMLElement("meta")}} element
-2.  JavaScript redirections via the [DOM](/en-US/docs/Web/API/Document_Object_Model)
+1. HTML redirections with the {{HTMLElement("meta")}} element
+2. JavaScript redirections via the [DOM](/en-US/docs/Web/API/Document_Object_Model)
 
 ### HTML redirections
 
@@ -98,9 +98,9 @@ Like HTML redirections, this can't work on all resources, and obviously, this wi
 
 With three ways to trigger redirections, several ways can be used at the same time. But which is applied first?
 
-1.  HTTP redirects always execute first — they exist when there is not even a transmitted page.
-2.  HTML redirects ({{HTMLElement("meta")}}) execute if there weren't any HTTP redirects.
-3.  JavaScript redirects execute last, and only if JavaScript is enabled.
+1. HTTP redirects always execute first — they exist when there is not even a transmitted page.
+2. HTML redirects ({{HTMLElement("meta")}}) execute if there weren't any HTTP redirects.
+3. JavaScript redirects execute last, and only if JavaScript is enabled.
 
 When possible, use HTTP redirects and don't add {{HTMLElement("meta")}} element redirects. If someone changes the HTTP redirects but forgets to change the HTML redirects, the redirects will no longer be identical, which could cause an infinite loop or other nightmares.
 
diff --git a/files/en-us/web/http/session/index.md b/files/en-us/web/http/session/index.md
index a85ea89139813bd..6b904c582998be4 100644
--- a/files/en-us/web/http/session/index.md
+++ b/files/en-us/web/http/session/index.md
@@ -8,9 +8,9 @@ tags:
 
 In client-server protocols, like HTTP, sessions consist of three phases:
 
-1.  The client establishes a TCP connection (or the appropriate connection if the transport layer is not TCP).
-2.  The client sends its request, and waits for the answer.
-3.  The server processes the request, sending back its answer, providing a status code and appropriate data.
+1. The client establishes a TCP connection (or the appropriate connection if the transport layer is not TCP).
+2. The client sends its request, and waits for the answer.
+3. The server processes the request, sending back its answer, providing a status code and appropriate data.
 
 As of HTTP/1.1, the connection is no longer closed after completing the third phase, and the client is now granted a further request: this means the second and third phases can now be performed any number of times.
 
@@ -26,13 +26,13 @@ With TCP the default port, for an HTTP server on a computer, is port 80. Other p
 
 Once the connection is established, the user-agent can send the request (a user-agent is typically a web browser, but can be anything else, a crawler, for example). A client request consists of text directives, separated by CRLF (carriage return, followed by line feed), divided into three blocks:
 
-1.  The first line contains a request method followed by its parameters:
+1. The first line contains a request method followed by its parameters:
 
     - the path of the document, i.e. an absolute URL without the protocol or domain name
     - the HTTP protocol version
 
-2.  Subsequent lines represent an HTTP header, giving the server information about what type of data is appropriate (e.g., what language, what MIME types), or other data altering its behavior (e.g., not sending an answer if it is already cached). These HTTP headers form a block which ends with an empty line.
-3.  The final block is an optional data block, which may contain further data mainly used by the POST method.
+2. Subsequent lines represent an HTTP header, giving the server information about what type of data is appropriate (e.g., what language, what MIME types), or other data altering its behavior (e.g., not sending an answer if it is already cached). These HTTP headers form a block which ends with an empty line.
+3. The final block is an optional data block, which may contain further data mainly used by the POST method.
 
 ### Example requests
 
@@ -64,9 +64,9 @@ HTTP defines a set of [request methods](/en-US/docs/Web/HTTP/Methods) indicating
 
 After the connected agent has sent its request, the web server processes it, and ultimately returns a response. Similar to a client request, a server response is formed of text directives, separated by CRLF, though divided into three blocks:
 
-1.  The first line, the _status line_, consists of an acknowledgment of the HTTP version used, followed by a response status code (and its brief meaning in human-readable text).
-2.  Subsequent lines represent specific HTTP headers, giving the client information about the data sent (e.g. type, data size, compression algorithm used, hints about caching). Similarly to the block of HTTP headers for a client request, these HTTP headers form a block ending with an empty line.
-3.  The final block is a data block, which contains the optional data.
+1. The first line, the _status line_, consists of an acknowledgment of the HTTP version used, followed by a response status code (and its brief meaning in human-readable text).
+2. Subsequent lines represent specific HTTP headers, giving the client information about the data sent (e.g. type, data size, compression algorithm used, hints about caching). Similarly to the block of HTTP headers for a client request, these HTTP headers form a block ending with an empty line.
+3. The final block is a data block, which contains the optional data.
 
 ### Example responses
 
diff --git a/files/en-us/web/http/status/index.md b/files/en-us/web/http/status/index.md
index 19969445a7e25fe..538a76b9873d1f8 100644
--- a/files/en-us/web/http/status/index.md
+++ b/files/en-us/web/http/status/index.md
@@ -13,11 +13,11 @@ tags:
 
 HTTP response status codes indicate whether a specific [HTTP](/en-US/docs/Web/HTTP) request has been successfully completed. Responses are grouped in five classes:
 
-1.  [Informational responses](#information_responses) (`100`–`199`)
-2.  [Successful responses](#successful_responses) (`200`–`299`)
-3.  [Redirects](#redirection_messages) (`300`–`399`)
-4.  [Client errors](#client_error_responses) (`400`–`499`)
-5.  [Server errors](#server_error_responses) (`500`–`599`)
+1. [Informational responses](#information_responses) (`100`–`199`)
+2. [Successful responses](#successful_responses) (`200`–`299`)
+3. [Redirects](#redirection_messages) (`300`–`399`)
+4. [Client errors](#client_error_responses) (`400`–`499`)
+5. [Server errors](#server_error_responses) (`500`–`599`)
 
 The below status codes are defined by [section 10 of RFC 2616](https://datatracker.ietf.org/doc/html/rfc2616#section-10). You can find an updated specification in [RFC 7231](https://datatracker.ietf.org/doc/html/rfc7231#section-6.5.1).
 

From 36adb5353ee063cb0a57a6322a92529969b87c10 Mon Sep 17 00:00:00 2001
From: "Michael[tm] Smith" <mike@w3.org>
Date: Fri, 13 Aug 2021 02:56:00 +0900
Subject: [PATCH 5/9] Fix space-in-wrong-place issues

---
 .../choosing_between_www_and_non-www_urls/index.md            | 2 +-
 .../web/http/basics_of_http/mime_types/common_types/index.md  | 2 +-
 files/en-us/web/http/cookies/index.md                         | 2 +-
 files/en-us/web/http/cors/index.md                            | 2 +-
 .../web/http/headers/public-key-pins-report-only/index.md     | 2 +-
 files/en-us/web/http/headers/public-key-pins/index.md         | 2 +-
 files/en-us/web/http/headers/set-cookie/index.md              | 4 ++--
 .../proxy_auto-configuration_pac_file/index.md                | 2 +-
 files/en-us/web/http/status/407/index.md                      | 2 +-
 9 files changed, 10 insertions(+), 10 deletions(-)

diff --git a/files/en-us/web/http/basics_of_http/choosing_between_www_and_non-www_urls/index.md b/files/en-us/web/http/basics_of_http/choosing_between_www_and_non-www_urls/index.md
index 28032714f7eb6a5..2b19e0098cfbc71 100644
--- a/files/en-us/web/http/basics_of_http/choosing_between_www_and_non-www_urls/index.md
+++ b/files/en-us/web/http/basics_of_http/choosing_between_www_and_non-www_urls/index.md
@@ -37,7 +37,7 @@ Example:
 2. The server answers with a code {{HTTPStatus(301)}} with the header `{{HTTPHeader("Location")}}: http://example.org/whaddup`.
 3. The client issues a request to the canonical domain: `http://example.org/whatddup`
 
-The[ HTML5 boilerplate project](https://github.com/h5bp/html5-boilerplate) has an example on [how to configure an Apache server to redirect one domain to the other](https://github.com/h5bp/html5-boilerplate/blob/7a22a33d4041c479d0962499e853501073811887/.htaccess#L219-L258).
+The [HTML5 boilerplate project](https://github.com/h5bp/html5-boilerplate) has an example on [how to configure an Apache server to redirect one domain to the other](https://github.com/h5bp/html5-boilerplate/blob/7a22a33d4041c479d0962499e853501073811887/.htaccess#L219-L258).
 
 ### Using _`<link rel="canonical">`_
 
diff --git a/files/en-us/web/http/basics_of_http/mime_types/common_types/index.md b/files/en-us/web/http/basics_of_http/mime_types/common_types/index.md
index 6c7ec40b477f93d..db93902d1a5445d 100644
--- a/files/en-us/web/http/basics_of_http/mime_types/common_types/index.md
+++ b/files/en-us/web/http/basics_of_http/mime_types/common_types/index.md
@@ -93,7 +93,7 @@ IANA is the official registry of MIME media types and maintains a [list of all t
 | `.xhtml`       | XHTML                                                                                                  | `application/xhtml+xml`                                                                                                                                                                                                                                                              |
 | `.xls`         | Microsoft Excel                                                                                        | `application/vnd.ms-excel`                                                                                                                                                                                                                                                           |
 | `.xlsx`        | Microsoft Excel (OpenXML)                                                                              | `application/vnd.openxmlformats-officedocument.spreadsheetml.sheet`                                                                                                                                                                                                                  |
-| `.xml`         | `XML`                                                                                                  | `application/xml `if _not_ readable from casual users ([RFC 3023](https://datatracker.ietf.org/doc/html/rfc3023#section-3), section 3) `text/xml` if readable from casual users ([RFC 3023](https://datatracker.ietf.org/doc/html/rfc3023#section-3), section 3)                     |
+| `.xml`         | `XML`                                                                                                  | `application/xml` if _not_ readable from casual users ([RFC 3023](https://datatracker.ietf.org/doc/html/rfc3023#section-3), section 3) `text/xml` if readable from casual users ([RFC 3023](https://datatracker.ietf.org/doc/html/rfc3023#section-3), section 3)                     |
 | `.xul`         | XUL                                                                                                    | `application/vnd.mozilla.xul+xml`                                                                                                                                                                                                                                                    |
 | `.zip`         | ZIP archive                                                                                            | `application/zip`                                                                                                                                                                                                                                                                    |
 | `.3gp`         | [3GPP](https://en.wikipedia.org/wiki/3GP_and_3G2) audio/video container                                | `video/3gpp` `audio/3gpp` if it doesn't contain video                                                                                                                                                                                                                                |
diff --git a/files/en-us/web/http/cookies/index.md b/files/en-us/web/http/cookies/index.md
index d6b9da05dddbb94..882e3179c6bd177 100644
--- a/files/en-us/web/http/cookies/index.md
+++ b/files/en-us/web/http/cookies/index.md
@@ -120,7 +120,7 @@ For example, if `Path=/docs` is set, these paths match:
 
 #### SameSite attribute
 
-The [`SameSite` ](/en-US/docs/Web/HTTP/Headers/Set-Cookie/SameSite)attribute lets servers specify whether/when cookies are sent with cross-site requests (where {{Glossary("Site")}} is defined by the registrable domain), which provides some protection against cross-site request forgery attacks ({{Glossary("CSRF")}}).
+The [`SameSite`](/en-US/docs/Web/HTTP/Headers/Set-Cookie/SameSite) attribute lets servers specify whether/when cookies are sent with cross-site requests (where {{Glossary("Site")}} is defined by the registrable domain), which provides some protection against cross-site request forgery attacks ({{Glossary("CSRF")}}).
 
 It takes three possible values: `Strict`, `Lax`, and `None`. With `Strict`, the cookie is sent only to the same site as the one that originated it; `Lax` is similar, except that cookies are sent when the user _navigates_ to the cookie's origin site, for example, by following a link from an external site; `None` specifies that cookies are sent on both originating and cross-site requests, but *only in secure contexts* (i.e. if `SameSite=None` then the `Secure` attribute must also be set). If no `SameSite` attribute is set then the cookie is treated as `Lax`.
 
diff --git a/files/en-us/web/http/cors/index.md b/files/en-us/web/http/cors/index.md
index 8c1afd6e6f3833e..031b6535f4cae78 100644
--- a/files/en-us/web/http/cors/index.md
+++ b/files/en-us/web/http/cors/index.md
@@ -143,7 +143,7 @@ This pattern of the {{HTTPHeader("Origin")}} and {{HTTPHeader("Access-Control-
 
 ### Preflighted requests
 
-Unlike [_simple requests_ ](#simple_requests), for "preflighted" requests the browser first sends an HTTP request using the {{HTTPMethod("OPTIONS")}} method to the resource on the other origin, in order to determine if the actual request is safe to send. Cross-site requests are preflighted like this since they may have implications to user data.
+Unlike [_simple requests_](#simple_requests), for "preflighted" requests the browser first sends an HTTP request using the {{HTTPMethod("OPTIONS")}} method to the resource on the other origin, in order to determine if the actual request is safe to send. Cross-site requests are preflighted like this since they may have implications to user data.
 
 The following is an example of a request that will be preflighted:
 
diff --git a/files/en-us/web/http/headers/public-key-pins-report-only/index.md b/files/en-us/web/http/headers/public-key-pins-report-only/index.md
index 061308cd1fba957..37a525f4c438a8f 100644
--- a/files/en-us/web/http/headers/public-key-pins-report-only/index.md
+++ b/files/en-us/web/http/headers/public-key-pins-report-only/index.md
@@ -59,7 +59,7 @@ Public-Key-Pins-Report-Only: pin-sha256="<pin-value>";
 - max-age=\<expire-time>
   - : This directive is meaningless for the Public-Key-Pins-Report-Only header, it will be
     ignored by user agents and the header will not be cached.
-- `includeSubDomains `{{optional_inline}}
+- `includeSubDomains` {{optional_inline}}
   - : If this optional parameter is specified, this rule applies to all of the site's
     subdomains as well.
 - `report-uri="<uri>"`
diff --git a/files/en-us/web/http/headers/public-key-pins/index.md b/files/en-us/web/http/headers/public-key-pins/index.md
index 04ce2160452d5c3..49fc6f36f00a9f7 100644
--- a/files/en-us/web/http/headers/public-key-pins/index.md
+++ b/files/en-us/web/http/headers/public-key-pins/index.md
@@ -58,7 +58,7 @@ Public-Key-Pins: pin-sha256="<pin-value>";
 - `max-age=<expire-time>`
   - : The time, in seconds, that the browser should remember that this site is only to be
     accessed using one of the defined keys.
-- `includeSubDomains `{{optional_inline}}
+- `includeSubDomains` {{optional_inline}}
   - : If this optional parameter is specified, this rule applies to all of the site's
     subdomains as well.
 - `report-uri="<uri>"` {{optional_inline}}
diff --git a/files/en-us/web/http/headers/set-cookie/index.md b/files/en-us/web/http/headers/set-cookie/index.md
index 19c859721e10e1a..2a8b1609f1ecf5f 100644
--- a/files/en-us/web/http/headers/set-cookie/index.md
+++ b/files/en-us/web/http/headers/set-cookie/index.md
@@ -79,7 +79,7 @@ Set-Cookie: <cookie-name>=<cookie-value>; Domain=<domain-value>; Secure; HttpOnl
     > **Note:** Some `><cookie-name>` have a specific semantic:
     >
     > **`__Secure-` prefix**:
-    > Cookies names starting with` __Secure-`
+    > Cookies names starting with `__Secure-`
     > (dash is part of the prefix)
     > must be set with the `secure` flag from a secure page (HTTPS).
     >
@@ -98,7 +98,7 @@ Set-Cookie: <cookie-name>=<cookie-value>; Domain=<domain-value>; Secure; HttpOnl
 
     When an `Expires` date is set, the deadline is relative to the _client_ the cookie is being set on, not the server.
 
-- `Max-Age=<number> `{{optional_inline}}
+- `Max-Age=<number>` {{optional_inline}}
   - : Number of seconds until the cookie expires. A zero or negative number will expire the cookie immediately. If both `Expires` and `Max-Age` are set, `Max-Age` has precedence.
 - `Domain=<domain-value>` {{optional_inline}}
 
diff --git a/files/en-us/web/http/proxy_servers_and_tunneling/proxy_auto-configuration_pac_file/index.md b/files/en-us/web/http/proxy_servers_and_tunneling/proxy_auto-configuration_pac_file/index.md
index a041c51eb72e6ef..26b44bc0ba9843d 100644
--- a/files/en-us/web/http/proxy_servers_and_tunneling/proxy_auto-configuration_pac_file/index.md
+++ b/files/en-us/web/http/proxy_servers_and_tunneling/proxy_auto-configuration_pac_file/index.md
@@ -129,7 +129,7 @@ These functions can be used in building the PAC file:
 
   - `ProxyConfig.bindings` {{deprecated_inline}}
 
-> **Note:** pactester (part of the [pacparser ](https://github.com/pacparser/pacparser)package) was used to test the following syntax examples.
+> **Note:** pactester (part of the [pacparser](https://github.com/pacparser/pacparser) package) was used to test the following syntax examples.
 >
 > - The PAC file is named `proxy.pac`
 > - Command line: `pactester -p ~/pacparser-master/tests/proxy.pac -u http://www.mozilla.org` (passes the `host` parameter `www.mozilla.org` and the `url` parameter `http://www.mozilla.org`)
diff --git a/files/en-us/web/http/status/407/index.md b/files/en-us/web/http/status/407/index.md
index f4e7f895dd01b96..e13aecf47b389b3 100644
--- a/files/en-us/web/http/status/407/index.md
+++ b/files/en-us/web/http/status/407/index.md
@@ -10,7 +10,7 @@ browser-compat: http.status.407
 ---
 {{HTTPSidebar}}
 
-The HTTP **`407 Proxy Authentication Required `**client error
+The HTTP **`407 Proxy Authentication Required`** client error
 status response code indicates that the request has not been applied because it lacks
 valid authentication credentials for a {{Glossary("proxy server")}} that is between the
 browser and the server that can access the requested resource.

From 19a8be2c8863ddbc10d6d8767f433445c6a87d20 Mon Sep 17 00:00:00 2001
From: "Michael[tm] Smith" <mike@w3.org>
Date: Fri, 13 Aug 2021 02:58:09 +0900
Subject: [PATCH 6/9] Fix oddly-formatted HTTPStatus macro calls

---
 files/en-us/web/http/basics_of_http/mime_types/index.md   | 2 +-
 files/en-us/web/http/conditional_requests/index.md        | 2 +-
 files/en-us/web/http/headers/etag/index.md                | 7 +++----
 files/en-us/web/http/headers/expect/index.md              | 4 ++--
 files/en-us/web/http/headers/if-match/index.md            | 4 ++--
 files/en-us/web/http/headers/if-modified-since/index.md   | 2 +-
 files/en-us/web/http/headers/if-none-match/index.md       | 4 ++--
 files/en-us/web/http/headers/if-range/index.md            | 2 +-
 files/en-us/web/http/headers/if-unmodified-since/index.md | 2 +-
 files/en-us/web/http/headers/range/index.md               | 6 +++---
 10 files changed, 17 insertions(+), 18 deletions(-)

diff --git a/files/en-us/web/http/basics_of_http/mime_types/index.md b/files/en-us/web/http/basics_of_http/mime_types/index.md
index 089f930113c2c69..910725acf3b3b24 100644
--- a/files/en-us/web/http/basics_of_http/mime_types/index.md
+++ b/files/en-us/web/http/basics_of_http/mime_types/index.md
@@ -361,7 +361,7 @@ will send this message:
 The `multipart/byteranges` MIME type is used to send partial responses to
 the browser.
 
-When the {{HTTPStatus("206")}}` Partial Content` status code is sent, this
+When the {{HTTPStatus("206", "206 Partial Content")}} status code is sent, this
 MIME type indicates that the document is composed of several parts, one for each of the
 requested ranges. Like other multipart types, the {{HTTPHeader("Content-Type")}} uses a
 `boundary` to separate the pieces. Each piece has a
diff --git a/files/en-us/web/http/conditional_requests/index.md b/files/en-us/web/http/conditional_requests/index.md
index e02423768c11579..b795966c3c5222c 100644
--- a/files/en-us/web/http/conditional_requests/index.md
+++ b/files/en-us/web/http/conditional_requests/index.md
@@ -74,7 +74,7 @@ If the resource has not changed, the server sends back a {{HTTPStatus("304")}} `
 
 ![With a stale cache, the conditional request is sent. The server can determine if the resource changed, and, as in this case, decide not to send it again as it is the same.](httpcache2.png)
 
-If the resource has changed, the server just sends back a {{HTTPStatus("200")}}` OK` response, with the new version of the resource, like if the request wasn't conditional and the client uses this new resource (and caches it).
+If the resource has changed, the server just sends back a {{HTTPStatus("200", "200 OK")}} response, with the new version of the resource, like if the request wasn't conditional and the client uses this new resource (and caches it).
 
 ![In the case where the resource was changed, it is sent back as if the request wasn't conditional.](httpcache3.png)
 
diff --git a/files/en-us/web/http/headers/etag/index.md b/files/en-us/web/http/headers/etag/index.md
index 6e9bdbd813bdf54..02d702dfedd3fb9 100644
--- a/files/en-us/web/http/headers/etag/index.md
+++ b/files/en-us/web/http/headers/etag/index.md
@@ -111,7 +111,6 @@ which tells the client that the cached version of the response is still good to
 
 - {{HTTPHeader("If-Match")}}
 - {{HTTPHeader("If-None-Match")}}
-- {{HTTPStatus("304")}}` Not Modified`
-- {{HTTPStatus("412")}}` Precondition Failed`
-- [W3C Note: Editing the Web – Detecting
-  the Lost Update Problem Using Unreserved Checkout](https://www.w3.org/1999/04/Editing/)
+- {{HTTPStatus("304", "304 Not Modified")}}
+- {{HTTPStatus("412", "Precondition Failed")}}
+- [W3C Note: Editing the Web – Detecting the Lost Update Problem Using Unreserved Checkout](https://www.w3.org/1999/04/Editing/)
diff --git a/files/en-us/web/http/headers/expect/index.md b/files/en-us/web/http/headers/expect/index.md
index b29c40331a6e3d1..2dbc95d64467fdc 100644
--- a/files/en-us/web/http/headers/expect/index.md
+++ b/files/en-us/web/http/headers/expect/index.md
@@ -83,5 +83,5 @@ cannot be met.
 
 ## See also
 
-- {{HTTPStatus("417")}}` Expectation Failed`
-- {{HTTPStatus("100")}}` Continue`
+- {{HTTPStatus("417", "417 Expectation Failed")}}
+- {{HTTPStatus("100", "100 Continue")}}
diff --git a/files/en-us/web/http/headers/if-match/index.md b/files/en-us/web/http/headers/if-match/index.md
index 08774efe5a83580..2e4b6b46721260e 100644
--- a/files/en-us/web/http/headers/if-match/index.md
+++ b/files/en-us/web/http/headers/if-match/index.md
@@ -88,5 +88,5 @@ If-Match: <etag_value>, <etag_value>, …
 - {{HTTPHeader("If-Unmodified-Since")}}
 - {{HTTPHeader("If-Modified-Since")}}
 - {{HTTPHeader("If-None-Match")}}
-- {{HTTPStatus("416")}}` Range Not Satisfiable`
-- {{HTTPStatus("412")}}` Precondition Failed`
+- {{HTTPStatus("416", "416 Range Not Satisfiable")}}
+- {{HTTPStatus("412", "412 Precondition Failed")}}
diff --git a/files/en-us/web/http/headers/if-modified-since/index.md b/files/en-us/web/http/headers/if-modified-since/index.md
index 221489264ff5b24..6ba58bb5bdd50c1 100644
--- a/files/en-us/web/http/headers/if-modified-since/index.md
+++ b/files/en-us/web/http/headers/if-modified-since/index.md
@@ -83,4 +83,4 @@ If-Modified-Since: <day-name>, <day> <month> <year> <hour>:<minute>:<second> GMT
 - {{HTTPHeader("If-Unmodified-since")}}
 - {{HTTPHeader("If-Match")}}
 - {{HTTPHeader("If-None-Match")}}
-- {{HTTPStatus("304")}}` Not Modified`
+- {{HTTPStatus("304", "304 Not Modified")}}
diff --git a/files/en-us/web/http/headers/if-none-match/index.md b/files/en-us/web/http/headers/if-none-match/index.md
index bdef9f56a31e8b1..c0d953ca493610d 100644
--- a/files/en-us/web/http/headers/if-none-match/index.md
+++ b/files/en-us/web/http/headers/if-none-match/index.md
@@ -74,5 +74,5 @@ If-None-Match: *
 - {{HTTPHeader("If-Unmodified-Since")}}
 - {{HTTPHeader("If-Modified-Since")}}
 - {{HTTPHeader("If-Match")}}
-- {{HTTPStatus("304")}}` Not Modified`
-- {{HTTPStatus("412")}}` Precondition Failed`
+- {{HTTPStatus("304", "304 Not Modified")}}
+- {{HTTPStatus("412", "412 Precondition Failed")}}
diff --git a/files/en-us/web/http/headers/if-range/index.md b/files/en-us/web/http/headers/if-range/index.md
index 3405a39e1fd2350..065e22add39519e 100644
--- a/files/en-us/web/http/headers/if-range/index.md
+++ b/files/en-us/web/http/headers/if-range/index.md
@@ -89,5 +89,5 @@ If-Range: <etag>
 - {{HTTPHeader("If-Unmodified-Since")}}
 - {{HTTPHeader("If-Match")}}
 - {{HTTPHeader("If-None-Match")}}
-- {{HTTPStatus("206")}}` Partial Content`
+- {{HTTPStatus("206", "206 Partial Content")}}
 - [HTTP Conditional Requests](/en-US/docs/Web/HTTP/Conditional_requests)
diff --git a/files/en-us/web/http/headers/if-unmodified-since/index.md b/files/en-us/web/http/headers/if-unmodified-since/index.md
index 9fb66f9076cef6c..388e4df4f34a034 100644
--- a/files/en-us/web/http/headers/if-unmodified-since/index.md
+++ b/files/en-us/web/http/headers/if-unmodified-since/index.md
@@ -84,4 +84,4 @@ If-Unmodified-Since: <day-name>, <day> <month> <year> <hour>:<minute>:<second> G
 - {{HTTPHeader("If-Match")}}
 - {{HTTPHeader("If-None-Match")}}
 - {{HTTPHeader("If-Range")}}
-- {{HTTPStatus("412")}}` Precondition Failed`
+- {{HTTPStatus("412", "412 Precondition Failed")}}
diff --git a/files/en-us/web/http/headers/range/index.md b/files/en-us/web/http/headers/range/index.md
index b020b61530039c1..ff079235962dc53 100644
--- a/files/en-us/web/http/headers/range/index.md
+++ b/files/en-us/web/http/headers/range/index.md
@@ -11,7 +11,7 @@ browser-compat: http.headers.Range
 ---
 {{HTTPSidebar}}
 
-The **`Range`** HTTP request header indicates the part of a document that the server should return. Several parts can be requested with one `Range` header at once, and the server may send back these ranges in a multipart document. If the server sends back ranges, it uses the {{HTTPStatus("206")}}` Partial Content` for the response. If the ranges are invalid, the server returns the {{HTTPStatus("416")}}` Range Not Satisfiable` error. The server can also ignore the `Range` header and return the whole document with a {{HTTPStatus("200")}} status code.
+The **`Range`** HTTP request header indicates the part of a document that the server should return. Several parts can be requested with one `Range` header at once, and the server may send back these ranges in a multipart document. If the server sends back ranges, it uses the {{HTTPStatus("206", "206 Partial Content")}} for the response. If the ranges are invalid, the server returns the {{HTTPStatus("416", "416 Range Not Satisfiable")}} error. The server can also ignore the `Range` header and return the whole document with a {{HTTPStatus("200")}} status code.
 
 <table class="properties">
   <tbody>
@@ -70,5 +70,5 @@ Requesting the first 500 and last 500 bytes of the file. The request may be reje
 - {{HTTPHeader("If-Range")}}
 - {{HTTPHeader("Content-Range")}}
 - {{HTTPHeader("Content-Type")}}
-- {{HTTPStatus("206")}}` Partial Content`
-- {{HTTPStatus("416")}}` Range Not Satisfiable`
+- {{HTTPStatus("206", "206 Partial Content")}}
+- {{HTTPStatus("416", "416 Range Not Satisfiable")}}

From e28ae3e1c02493b2fa6a2c450766611ed63641be Mon Sep 17 00:00:00 2001
From: "Michael[tm] Smith" <mike@w3.org>
Date: Fri, 13 Aug 2021 02:59:12 +0900
Subject: [PATCH 7/9] Fix a couple miscellaneous issues

---
 files/en-us/web/http/cookies/index.md                         | 2 +-
 files/en-us/web/http/csp/errors/cspviolation/index.md         | 4 ----
 .../proxy_auto-configuration_pac_file/index.md                | 4 +++-
 3 files changed, 4 insertions(+), 6 deletions(-)

diff --git a/files/en-us/web/http/cookies/index.md b/files/en-us/web/http/cookies/index.md
index 882e3179c6bd177..6ddc8eb296466ab 100644
--- a/files/en-us/web/http/cookies/index.md
+++ b/files/en-us/web/http/cookies/index.md
@@ -174,7 +174,7 @@ Please note the security issues in the [Security](#security) section below. Cook
 Ways to mitigate attacks involving cookies:
 
 - Use the `HttpOnly` attribute to prevent access to cookie values via JavaScript.
-- Cookies that are used for sensitive information (such as indicating authentication) should have a short lifetime, with the `SameSite` attribute set to `Strict` or `Lax`. (See [SameSite cookies](#), above.) In [browsers that support SameSite](/en-US/docs/Web/HTTP/Headers/Set-Cookie#browser_compatibility), this has the effect of ensuring that the authentication cookie is not sent with cross-site requests, so such a request is effectively unauthenticated to the application server.
+- Cookies that are used for sensitive information (such as indicating authentication) should have a short lifetime, with the `SameSite` attribute set to `Strict` or `Lax`. (See [SameSite attribute](#samesite_attribute), above.) In [browsers that support SameSite](/en-US/docs/Web/HTTP/Headers/Set-Cookie#browser_compatibility), this has the effect of ensuring that the authentication cookie is not sent with cross-site requests, so such a request is effectively unauthenticated to the application server.
 
 ## Tracking and privacy
 
diff --git a/files/en-us/web/http/csp/errors/cspviolation/index.md b/files/en-us/web/http/csp/errors/cspviolation/index.md
index 39915eeb5827720..79d2fa799d0e2f7 100644
--- a/files/en-us/web/http/csp/errors/cspviolation/index.md
+++ b/files/en-us/web/http/csp/errors/cspviolation/index.md
@@ -47,14 +47,10 @@ with:
 - `uvw`
   - : Text that provides information that may help you resolve the problem, potentially including specific changes you might make to the CSP configuration.
 
-**<<<--- The Chrome information above may be incomplete; we need to investigate that when we resume work on this content --->>>**
-
 ## What went wrong?
 
 This warning message means that due to the existence of a particular CSP directive, a resource wasn't loaded.
 
-**<<<--- add details and suggested fixes --->>>**
-
 ## See also
 
 - [CSP errors and warnings](/en-US/docs/Web/HTTP/CSP/Errors)
diff --git a/files/en-us/web/http/proxy_servers_and_tunneling/proxy_auto-configuration_pac_file/index.md b/files/en-us/web/http/proxy_servers_and_tunneling/proxy_auto-configuration_pac_file/index.md
index 26b44bc0ba9843d..01fe225f0f696b3 100644
--- a/files/en-us/web/http/proxy_servers_and_tunneling/proxy_auto-configuration_pac_file/index.md
+++ b/files/en-us/web/http/proxy_servers_and_tunneling/proxy_auto-configuration_pac_file/index.md
@@ -314,7 +314,9 @@ myIpAddress()
 
 #### Parameters
 
-**(none)**
+(none)
+
+#### Return value
 
 Returns the server IP address of the machine Firefox is running on, as a string in the dot-separated integer format.
 

From 5542fb81a9663a74d69d7408e878fd901b3d7914 Mon Sep 17 00:00:00 2001
From: "Michael[tm] Smith" <mike@w3.org>
Date: Fri, 13 Aug 2021 03:01:46 +0900
Subject: [PATCH 8/9] Fix trailing-punctuation-in-headings

---
 files/en-us/web/http/headers/set-cookie/samesite/index.md   | 2 +-
 .../proxy_auto-configuration_pac_file/index.md              | 6 +++---
 2 files changed, 4 insertions(+), 4 deletions(-)

diff --git a/files/en-us/web/http/headers/set-cookie/samesite/index.md b/files/en-us/web/http/headers/set-cookie/samesite/index.md
index 676e92c282fcedf..54fee20d5659da6 100644
--- a/files/en-us/web/http/headers/set-cookie/samesite/index.md
+++ b/files/en-us/web/http/headers/set-cookie/samesite/index.md
@@ -91,7 +91,7 @@ You should explicitly communicate the intended `SameSite` policy for your cook
 Set-Cookie: flavor=choco; SameSite=Lax
 ```
 
-## Example:
+## Example
 
     RewriteEngine on
     RewriteBase "/"
diff --git a/files/en-us/web/http/proxy_servers_and_tunneling/proxy_auto-configuration_pac_file/index.md b/files/en-us/web/http/proxy_servers_and_tunneling/proxy_auto-configuration_pac_file/index.md
index 01fe225f0f696b3..91df4aeedb5d694 100644
--- a/files/en-us/web/http/proxy_servers_and_tunneling/proxy_auto-configuration_pac_file/index.md
+++ b/files/en-us/web/http/proxy_servers_and_tunneling/proxy_auto-configuration_pac_file/index.md
@@ -227,7 +227,7 @@ isResolvable(host)
 
 Tries to resolve the hostname. Returns true if succeeds.
 
-#### Examples:
+#### Examples
 
 ```js
 isResolvable("www.mozilla.org") // true
@@ -254,7 +254,7 @@ True if and only if the IP address of the host matches the specified IP address
 
 Pattern and mask specification is done the same way as for SOCKS configuration.
 
-#### Examples:
+#### Examples
 
 ```js
 function alert_eval(str) { alert(str + ' is ' + eval(str)) }
@@ -343,7 +343,7 @@ dnsDomainLevels(host)
 
 Returns the number (integer) of DNS domain levels (number of dots) in the hostname.
 
-#### Examples:
+#### Examples
 
 ```js
 dnsDomainLevels("www");             // 0

From ea42eef892934074ad3d41bfa0e79daa426fb141 Mon Sep 17 00:00:00 2001
From: Jean-Yves Perrier <jypenator@gmail.com>
Date: Fri, 13 Aug 2021 13:15:21 +0200
Subject: [PATCH 9/9] Fix triple dots for <pre> in Web/HTTP

---
 files/en-us/web/http/authentication/index.md  |  32 ++-
 .../index.md                                  |   4 +-
 .../http/basics_of_http/data_uris/index.md    |  14 +-
 .../basics_of_http/evolution_of_http/index.md | 134 +++++----
 .../identifying_resources_on_the_web/index.md |  34 ++-
 .../http/basics_of_http/mime_types/index.md   | 100 +++----
 .../basics_of_http/resource_urls/index.md     |  22 +-
 files/en-us/web/http/caching/index.md         |  56 ++--
 .../index.md                                  |  50 ++--
 files/en-us/web/http/cookies/index.md         |  31 +-
 .../corsalloworiginnotmatchingorigin/index.md |  16 +-
 .../cors/errors/corsdidnotsucceed/index.md    |   2 +-
 .../http/cors/errors/corsdisabled/index.md    |   2 +-
 .../corsexternalredirectnotallowed/index.md   |   2 +-
 .../errors/corsinvalidallowheader/index.md    |   4 +-
 .../errors/corsinvalidallowmethod/index.md    |   4 +-
 .../cors/errors/corsmethodnotfound/index.md   |   4 +-
 .../corsmissingallowcredentials/index.md      |   4 +-
 .../index.md                                  |   4 +-
 .../errors/corsmissingalloworigin/index.md    |  18 +-
 .../index.md                                  |   4 +-
 .../corsnotsupportingcredentials/index.md     |   4 +-
 .../errors/corsoriginheadernotadded/index.md  |   4 +-
 .../corspreflightdidnotsucceed/index.md       |   4 +-
 .../cors/errors/corsrequestnothttp/index.md   |   2 +-
 files/en-us/web/http/cors/errors/index.md     |  10 +-
 files/en-us/web/http/cors/index.md            | 270 ++++++++++--------
 .../index.md                                  |   6 +-
 files/en-us/web/http/csp/index.md             |  58 ++--
 .../http/headers/accept-ch-lifetime/index.md  |   8 +-
 .../web/http/headers/accept-encoding/index.md |  10 +-
 .../web/http/headers/accept-patch/index.md    |   4 +-
 .../web/http/headers/accept-post/index.md     |  10 +-
 .../web/http/headers/accept-ranges/index.md   |   6 +-
 files/en-us/web/http/headers/accept/index.md  |  16 +-
 .../access-control-allow-credentials/index.md |   6 +-
 .../access-control-allow-headers/index.md     |  40 ++-
 .../access-control-allow-methods/index.md     |   8 +-
 .../access-control-allow-origin/index.md      |  16 +-
 .../access-control-expose-headers/index.md    |  18 +-
 .../headers/access-control-max-age/index.md   |   6 +-
 .../access-control-request-headers/index.md   |   6 +-
 .../access-control-request-method/index.md    |   6 +-
 files/en-us/web/http/headers/age/index.md     |   6 +-
 files/en-us/web/http/headers/allow/index.md   |   6 +-
 files/en-us/web/http/headers/alt-svc/index.md |  12 +-
 .../web/http/headers/authorization/index.md   |   6 +-
 .../web/http/headers/cache-control/index.md   |  66 +++--
 .../web/http/headers/clear-site-data/index.md |  22 +-
 .../web/http/headers/connection/index.md      |   2 +-
 .../http/headers/content-disposition/index.md |  38 +--
 .../web/http/headers/content-dpr/index.md     |   4 +-
 .../http/headers/content-encoding/index.md    |  10 +-
 .../http/headers/content-language/index.md    |   6 +-
 .../web/http/headers/content-length/index.md  |   2 +-
 .../http/headers/content-location/index.md    |  40 +--
 .../web/http/headers/content-range/index.md   |   6 +-
 .../index.md                                  |  14 +-
 .../content-security-policy/base-uri/index.md |   6 +-
 .../block-all-mixed-content/index.md          |  12 +-
 .../child-src/index.md                        |   4 +-
 .../connect-src/index.md                      |   4 +-
 .../default-src/index.md                      |   6 +-
 .../content-security-policy/font-src/index.md |   4 +-
 .../form-action/index.md                      |   6 +-
 .../frame-ancestors/index.md                  |   4 +-
 .../frame-src/index.md                        |   4 +-
 .../content-security-policy/img-src/index.md  |   4 +-
 .../headers/content-security-policy/index.md  |  40 ++-
 .../manifest-src/index.md                     |   4 +-
 .../media-src/index.md                        |   4 +-
 .../navigate-to/index.md                      |   2 +-
 .../object-src/index.md                       |   4 +-
 .../plugin-types/index.md                     |   6 +-
 .../prefetch-src/index.md                     |   8 +-
 .../content-security-policy/referrer/index.md |   6 +-
 .../report-uri/index.md                       |   8 +-
 .../require-sri-for/index.md                  |   6 +-
 .../require-trusted-types-for/index.md        |  16 +-
 .../content-security-policy/sandbox/index.md  |   4 +-
 .../script-src-attr/index.md                  |   4 +-
 .../script-src/index.md                       |  30 +-
 .../style-src-attr/index.md                   |   8 +-
 .../style-src-elem/index.md                   |   2 +-
 .../style-src/index.md                        |  10 +-
 .../upgrade-insecure-requests/index.md        |  22 +-
 .../worker-src/index.md                       |   7 +-
 .../web/http/headers/content-type/index.md    |  26 +-
 files/en-us/web/http/headers/cookie/index.md  |   6 +-
 files/en-us/web/http/headers/cookie2/index.md |   4 +-
 .../cross-origin-embedder-policy/index.md     |  12 +-
 .../cross-origin-opener-policy/index.md       |  16 +-
 .../cross-origin-resource-policy/index.md     |  12 +-
 files/en-us/web/http/headers/date/index.md    |   6 +-
 .../web/http/headers/device-memory/index.md   |  12 +-
 files/en-us/web/http/headers/digest/index.md  |  12 +-
 files/en-us/web/http/headers/dnt/index.md     |   6 +-
 .../en-us/web/http/headers/downlink/index.md  |  12 +-
 files/en-us/web/http/headers/dpr/index.md     |  16 +-
 .../web/http/headers/early-data/index.md      |  13 +-
 files/en-us/web/http/headers/ect/index.md     |  12 +-
 files/en-us/web/http/headers/etag/index.md    |  20 +-
 .../en-us/web/http/headers/expect-ct/index.md |  12 +-
 files/en-us/web/http/headers/expect/index.md  |  16 +-
 files/en-us/web/http/headers/expires/index.md |   6 +-
 .../feature-policy/accelerometer/index.md     |   4 +-
 .../ambient-light-sensor/index.md             |   4 +-
 .../headers/feature-policy/autoplay/index.md  |   4 +-
 .../headers/feature-policy/battery/index.md   |   4 +-
 .../headers/feature-policy/camera/index.md    |   4 +-
 .../feature-policy/display-capture/index.md   |   4 +-
 .../feature-policy/document-domain/index.md   |   4 +-
 .../feature-policy/encrypted-media/index.md   |   4 +-
 .../feature-policy/fullscreen/index.md        |   8 +-
 .../headers/feature-policy/gamepad/index.md   |  12 +-
 .../feature-policy/geolocation/index.md       |  14 +-
 .../headers/feature-policy/gyroscope/index.md |   4 +-
 .../web/http/headers/feature-policy/index.md  |   8 +-
 .../feature-policy/layout-animations/index.md |   4 +-
 .../legacy-image-formats/index.md             |   4 +-
 .../feature-policy/magnetometer/index.md      |   4 +-
 .../feature-policy/microphone/index.md        |   4 +-
 .../http/headers/feature-policy/midi/index.md |   4 +-
 .../feature-policy/oversized-images/index.md  |   4 +-
 .../headers/feature-policy/payment/index.md   |   4 +-
 .../picture-in-picture/index.md               |   4 +-
 .../publickey-credentials-get/index.md        |   4 +-
 .../feature-policy/screen-wake-lock/index.md  |   4 +-
 .../headers/feature-policy/sync-xhr/index.md  |   4 +-
 .../unoptimized-images/index.md               |   4 +-
 .../feature-policy/unsized-media/index.md     |   4 +-
 .../http/headers/feature-policy/usb/index.md  |   4 +-
 .../headers/feature-policy/vibrate/index.md   |   4 +-
 .../http/headers/feature-policy/vr/index.md   |   4 +-
 .../headers/feature-policy/web-share/index.md |   4 +-
 .../xr-spatial-tracking/index.md              |   4 +-
 .../en-us/web/http/headers/forwarded/index.md |  28 +-
 files/en-us/web/http/headers/from/index.md    |   6 +-
 files/en-us/web/http/headers/host/index.md    |   6 +-
 .../en-us/web/http/headers/if-match/index.md  |   4 +-
 .../http/headers/if-modified-since/index.md   |   6 +-
 .../web/http/headers/if-none-match/index.md   |   4 +-
 .../en-us/web/http/headers/if-range/index.md  |   6 +-
 .../http/headers/if-unmodified-since/index.md |   6 +-
 .../web/http/headers/keep-alive/index.md      |  24 +-
 .../http/headers/large-allocation/index.md    |   8 +-
 .../web/http/headers/last-modified/index.md   |   6 +-
 files/en-us/web/http/headers/link/index.md    |  12 +-
 .../en-us/web/http/headers/location/index.md  |   6 +-
 files/en-us/web/http/headers/nel/index.md     |   2 +-
 files/en-us/web/http/headers/origin/index.md  |   6 +-
 files/en-us/web/http/headers/pragma/index.md  |   6 +-
 .../http/headers/proxy-authenticate/index.md  |   8 +-
 .../http/headers/proxy-authorization/index.md |   6 +-
 .../public-key-pins-report-only/index.md      |  14 +-
 .../web/http/headers/public-key-pins/index.md |  14 +-
 files/en-us/web/http/headers/range/index.md   |  10 +-
 files/en-us/web/http/headers/referer/index.md |  10 +-
 .../web/http/headers/referrer-policy/index.md |   8 +-
 .../web/http/headers/retry-after/index.md     |  11 +-
 files/en-us/web/http/headers/rtt/index.md     |  12 +-
 .../en-us/web/http/headers/save-data/index.md |  45 +--
 .../web/http/headers/sec-fetch-dest/index.md  |  52 ++--
 .../web/http/headers/sec-fetch-mode/index.md  |  30 +-
 .../web/http/headers/sec-fetch-site/index.md  |  30 +-
 .../web/http/headers/sec-fetch-user/index.md  |  14 +-
 .../headers/sec-websocket-accept/index.md     |   6 +-
 .../web/http/headers/server-timing/index.md   |  26 +-
 files/en-us/web/http/headers/server/index.md  |   8 +-
 .../web/http/headers/set-cookie/index.md      |  47 +--
 .../http/headers/set-cookie/samesite/index.md |  36 +--
 .../web/http/headers/set-cookie2/index.md     |   2 +-
 .../en-us/web/http/headers/sourcemap/index.md |   8 +-
 .../strict-transport-security/index.md        |  10 +-
 files/en-us/web/http/headers/te/index.md      |   5 +-
 .../http/headers/timing-allow-origin/index.md |  12 +-
 files/en-us/web/http/headers/tk/index.md      |   6 +-
 files/en-us/web/http/headers/trailer/index.md |  32 ++-
 .../http/headers/transfer-encoding/index.md   |  29 +-
 .../upgrade-insecure-requests/index.md        |  18 +-
 files/en-us/web/http/headers/upgrade/index.md |  46 +--
 .../http/headers/user-agent/firefox/index.md  |  26 +-
 .../web/http/headers/user-agent/index.md      |  68 +++--
 files/en-us/web/http/headers/vary/index.md    |  18 +-
 files/en-us/web/http/headers/via/index.md     |  11 +-
 .../web/http/headers/viewport-width/index.md  |  14 +-
 .../web/http/headers/want-digest/index.md     |  56 ++--
 files/en-us/web/http/headers/warning/index.md |  13 +-
 files/en-us/web/http/headers/width/index.md   |  14 +-
 .../http/headers/www-authenticate/index.md    |   6 +-
 .../headers/x-content-type-options/index.md   |  11 +-
 .../headers/x-dns-prefetch-control/index.md   |   2 +-
 .../web/http/headers/x-forwarded-for/index.md |  16 +-
 .../http/headers/x-forwarded-host/index.md    |   6 +-
 .../http/headers/x-forwarded-proto/index.md   |  18 +-
 .../web/http/headers/x-frame-options/index.md |  42 ++-
 .../http/headers/x-xss-protection/index.md    |  12 +-
 .../web/http/link_prefetching_faq/index.md    |  22 +-
 files/en-us/web/http/methods/connect/index.md |  10 +-
 files/en-us/web/http/methods/delete/index.md  |  28 +-
 files/en-us/web/http/methods/get/index.md     |   2 +-
 files/en-us/web/http/methods/head/index.md    |   2 +-
 files/en-us/web/http/methods/options/index.md |  60 ++--
 files/en-us/web/http/methods/patch/index.md   |  24 +-
 files/en-us/web/http/methods/post/index.md    |  36 +--
 files/en-us/web/http/methods/put/index.md     |  14 +-
 files/en-us/web/http/methods/trace/index.md   |   2 +-
 .../web/http/network_error_logging/index.md   |  19 +-
 files/en-us/web/http/overview/index.md        |  30 +-
 .../http/protocol_upgrade_mechanism/index.md  |  24 +-
 .../web/http/public_key_pinning/index.md      |  72 +++--
 files/en-us/web/http/range_requests/index.md  |  86 +++---
 files/en-us/web/http/redirections/index.md    |  40 ++-
 files/en-us/web/http/session/index.md         | 138 ++++-----
 files/en-us/web/http/status/100/index.md      |   2 +-
 files/en-us/web/http/status/101/index.md      |  10 +-
 files/en-us/web/http/status/103/index.md      |   2 +-
 files/en-us/web/http/status/200/index.md      |   2 +-
 files/en-us/web/http/status/201/index.md      |   2 +-
 files/en-us/web/http/status/202/index.md      |   2 +-
 files/en-us/web/http/status/203/index.md      |   2 +-
 files/en-us/web/http/status/204/index.md      |   2 +-
 files/en-us/web/http/status/205/index.md      |   2 +-
 files/en-us/web/http/status/206/index.md      |   2 +-
 files/en-us/web/http/status/300/index.md      |   2 +-
 files/en-us/web/http/status/301/index.md      |  14 +-
 files/en-us/web/http/status/302/index.md      |   2 +-
 files/en-us/web/http/status/303/index.md      |   2 +-
 files/en-us/web/http/status/304/index.md      |   2 +-
 files/en-us/web/http/status/307/index.md      |   2 +-
 files/en-us/web/http/status/308/index.md      |   2 +-
 files/en-us/web/http/status/400/index.md      |   4 +-
 files/en-us/web/http/status/401/index.md      |  10 +-
 files/en-us/web/http/status/402/index.md      |   4 +-
 files/en-us/web/http/status/403/index.md      |   8 +-
 files/en-us/web/http/status/404/index.md      |   4 +-
 files/en-us/web/http/status/405/index.md      |   2 +-
 files/en-us/web/http/status/406/index.md      |   2 +-
 files/en-us/web/http/status/407/index.md      |  12 +-
 files/en-us/web/http/status/408/index.md      |   2 +-
 files/en-us/web/http/status/409/index.md      |   2 +-
 files/en-us/web/http/status/410/index.md      |   2 +-
 files/en-us/web/http/status/411/index.md      |   2 +-
 files/en-us/web/http/status/412/index.md      |   2 +-
 files/en-us/web/http/status/413/index.md      |   2 +-
 files/en-us/web/http/status/414/index.md      |   2 +-
 files/en-us/web/http/status/415/index.md      |   2 +-
 files/en-us/web/http/status/416/index.md      |   2 +-
 files/en-us/web/http/status/417/index.md      |   2 +-
 files/en-us/web/http/status/418/index.md      |   2 +-
 files/en-us/web/http/status/422/index.md      |   2 +-
 files/en-us/web/http/status/425/index.md      |   2 +-
 files/en-us/web/http/status/426/index.md      |   2 +-
 files/en-us/web/http/status/428/index.md      |   2 +-
 files/en-us/web/http/status/429/index.md      |  10 +-
 files/en-us/web/http/status/431/index.md      |   2 +-
 files/en-us/web/http/status/451/index.md      |   2 +-
 files/en-us/web/http/status/500/index.md      |   2 +-
 files/en-us/web/http/status/501/index.md      |   2 +-
 files/en-us/web/http/status/502/index.md      |   2 +-
 files/en-us/web/http/status/503/index.md      |   2 +-
 files/en-us/web/http/status/504/index.md      |   2 +-
 files/en-us/web/http/status/505/index.md      |   2 +-
 files/en-us/web/http/status/506/index.md      |   2 +-
 files/en-us/web/http/status/507/index.md      |   2 +-
 files/en-us/web/http/status/508/index.md      |   2 +-
 files/en-us/web/http/status/510/index.md      |   2 +-
 files/en-us/web/http/status/511/index.md      |   2 +-
 268 files changed, 2207 insertions(+), 1505 deletions(-)

diff --git a/files/en-us/web/http/authentication/index.md b/files/en-us/web/http/authentication/index.md
index 1683831a4718293..2b1971e5dc0d5b2 100644
--- a/files/en-us/web/http/authentication/index.md
+++ b/files/en-us/web/http/authentication/index.md
@@ -54,7 +54,7 @@ The {{HTTPHeader("WWW-Authenticate")}} and {{HTTPHeader("Proxy-Authenticate")}}
 
 The syntax for these headers is the following:
 
-```html
+```
 WWW-Authenticate: <type> realm=<realm>
 Proxy-Authenticate: <type> realm=<realm>
 ```
@@ -65,7 +65,7 @@ Here, `<type>` is the authentication scheme ("Basic" is the most common scheme a
 
 The {{HTTPHeader("Authorization")}} and {{HTTPHeader("Proxy-Authorization")}} request headers contain the credentials to authenticate a user agent with a (proxy) server. Here, the `<type>` is needed again followed by the credentials, which can be encoded or encrypted depending on which authentication scheme is used.
 
-```html
+```
 Authorization: <type> <credentials>
 Proxy-Authorization: <type> <credentials>
 ```
@@ -103,30 +103,36 @@ To password-protect a directory on an Apache server, you will need a `.htaccess`
 
 The `.htaccess` file typically looks like this:
 
-    AuthType Basic
-    AuthName "Access to the staging site"
-    AuthUserFile /path/to/.htpasswd
-    Require valid-user
+```
+AuthType Basic
+AuthName "Access to the staging site"
+AuthUserFile /path/to/.htpasswd
+Require valid-user
+```
 
 The `.htaccess` file references a `.htpasswd` file in which each line consists of a username and a password separated by a colon (`:`). You cannot see the actual passwords as they are [hashed](https://httpd.apache.org/docs/2.4/misc/password_encryptions.html) (using MD5-based hashing, in this case). Note that you can name your `.htpasswd` file differently if you like, but keep in mind this file shouldn't be accessible to anyone. (Apache is usually configured to prevent access to `.ht*` files).
 
-    aladdin:$apr1$ZjTqBB3f$IF9gdYAGlMrs2fuINjHsz.
-    user2:$apr1$O04r.y2H$/vEkesPhVInBByJUkXitA/
+```
+aladdin:$apr1$ZjTqBB3f$IF9gdYAGlMrs2fuINjHsz.
+user2:$apr1$O04r.y2H$/vEkesPhVInBByJUkXitA/
+```
 
 ### Restricting access with nginx and basic authentication
 
 For nginx, you will need to specify a location that you are going to protect and the `auth_basic` directive that provides the name to the password-protected area. The `auth_basic_user_file` directive then points to a `.htpasswd` file containing the encrypted user credentials, just like in the Apache example above.
 
-    location /status {
-        auth_basic           "Access to the staging site";
-        auth_basic_user_file /etc/apache2/.htpasswd;
-    }
+```
+location /status {
+    auth_basic           "Access to the staging site";
+    auth_basic_user_file /etc/apache2/.htpasswd;
+}
+```
 
 ### Access using credentials in the URL
 
 Many clients also let you avoid the login prompt by using an encoded URL containing the username and the password like this:
 
-```plain example-bad
+```example-bad
 https://username:password@www.example.com/
 ```
 
diff --git a/files/en-us/web/http/basics_of_http/choosing_between_www_and_non-www_urls/index.md b/files/en-us/web/http/basics_of_http/choosing_between_www_and_non-www_urls/index.md
index 2b19e0098cfbc71..1aaae573690977a 100644
--- a/files/en-us/web/http/basics_of_http/choosing_between_www_and_non-www_urls/index.md
+++ b/files/en-us/web/http/basics_of_http/choosing_between_www_and_non-www_urls/index.md
@@ -45,7 +45,9 @@ It is possible to add a special HTML {{HTMLElement("link")}} element to a page t
 
 When adding such a tag, you serve the same content for both domains, telling search engines which URL is canonical. In the previous example, `http://www.example.org/whaddup` would serve the same content as `http://example.org/whaddup`, but with an additional {{htmlelement("link")}} element in the head:
 
-`<link href="http://example.org/whaddup" rel="canonical">`
+```html
+<link href="http://example.org/whaddup" rel="canonical">
+``
 
 Unlike the previous case, browser history will consider non-www and www URLs as independent entries.
 
diff --git a/files/en-us/web/http/basics_of_http/data_uris/index.md b/files/en-us/web/http/basics_of_http/data_uris/index.md
index 73557779563b11e..0d577fce46a1d33 100644
--- a/files/en-us/web/http/basics_of_http/data_uris/index.md
+++ b/files/en-us/web/http/basics_of_http/data_uris/index.md
@@ -68,14 +68,14 @@ base64 a.txt>b.txt
 
 On Windows, [Convert.ToBase64String](https://docs.microsoft.com/en-us/dotnet/api/system.convert.tobase64string?view=net-5.0) from PowerShell can be used to perform the Base64 encoding:
 
-```html
+```bash
 [convert]::ToBase64String([Text.Encoding]::UTF8.GetBytes("hello"))
 # outputs to console: aGVsbG8=
 ```
 
 Alternatively, a GNU/Linux shell (such as [WSL](https://en.wikipedia.org/wiki/Windows_Subsystem_for_Linux)) provides the utility `base64`:
 
-```html
+```bash
 bash$ echo -n hello | base64
 # outputs to console: aGVsbG8=
 ```
@@ -84,11 +84,15 @@ bash$ echo -n hello | base64
 
 This section describes problems that commonly occur when creating and using `data` URLs.
 
-    data:text/html,lots of text...<p><a name%3D"bottom">bottom</a>?arg=val
+```
+data:text/html,lots of text...<p><a name%3D"bottom">bottom</a>?arg=val
+```
 
 This represents an HTML resource whose contents are:
 
-    lots of text...<p><a name="bottom">bottom</a>?arg=val
+```html
+lots of text...<p><a name="bottom">bottom</a>?arg=val
+```
 
 - Syntax
   - : The format for `data` URLs is very simple, but it's easy to forget to put a comma before the "data" segment, or to incorrectly encode the data into base64 format.
@@ -119,5 +123,5 @@ This represents an HTML resource whose contents are:
 - [Percent encoding](/en-US/docs/Glossary/percent-encoding)
 - {{domxref("WindowOrWorkerGlobalScope/atob","atob()")}}
 - {{domxref("WindowOrWorkerGlobalScope/btoa","btoa()")}}
-- [CSS `url()`](</en-US/docs/Web/CSS/url()>)
+- [CSS `url()`](/en-US/docs/Web/CSS/url())
 - [URI](/en-US/docs/Glossary/URI)
diff --git a/files/en-us/web/http/basics_of_http/evolution_of_http/index.md b/files/en-us/web/http/basics_of_http/evolution_of_http/index.md
index 761dd79b290937d..e1e3f02429e96f7 100644
--- a/files/en-us/web/http/basics_of_http/evolution_of_http/index.md
+++ b/files/en-us/web/http/basics_of_http/evolution_of_http/index.md
@@ -28,13 +28,17 @@ The HTTP protocol used in those early phases was very simple, later dubbed HTTP/
 
 The initial version of HTTP had no version number; it has been later called 0.9 to differentiate it from the later versions. HTTP/0.9 is extremely simple: requests consist of a single line and start with the only possible method {{HTTPMethod("GET")}} followed by the path to the resource (not the URL as both the protocol, server, and port are unnecessary once connected to the server).
 
-    GET /mypage.html
+```
+GET /mypage.html
+```
 
 The response is extremely simple too: it only consisted of the file itself.
 
-    <HTML>
-    A very simple HTML page
-    </HTML>
+```html
+<html>
+A very simple HTML page
+</html>
+```
 
 Unlike subsequent evolutions, there were no HTTP headers, meaning that only HTML files could be transmitted, but no other type of documents. There were no status or error codes: in case of a problem, a specific HTML file was sent back with the description of the problem contained in it, for human consumption.
 
@@ -49,28 +53,32 @@ HTTP/0.9 was very limited and both browsers and servers quickly extended it to b
 
 At this point, a typical request and response looked like this:
 
-    GET /mypage.html HTTP/1.0
-    User-Agent: NCSA_Mosaic/2.0 (Windows 3.1)
+```
+GET /mypage.html HTTP/1.0
+User-Agent: NCSA_Mosaic/2.0 (Windows 3.1)
 
-    200 OK
-    Date: Tue, 15 Nov 1994 08:12:31 GMT
-    Server: CERN/3.0 libwww/2.17
-    Content-Type: text/html
-    <HTML>
-    A page with an image
-      <IMG SRC="/myimage.gif">
-    </HTML>
+200 OK
+Date: Tue, 15 Nov 1994 08:12:31 GMT
+Server: CERN/3.0 libwww/2.17
+Content-Type: text/html
+<HTML>
+A page with an image
+  <IMG SRC="/myimage.gif">
+</HTML>
+```
 
 Followed by a second connection and request to fetch the image (followed by a response to that request):
 
-    GET /myimage.gif HTTP/1.0
-    User-Agent: NCSA_Mosaic/2.0 (Windows 3.1)
+```
+  GET /myimage.gif HTTP/1.0
+  User-Agent: NCSA_Mosaic/2.0 (Windows 3.1)
 
-    200 OK
-    Date: Tue, 15 Nov 1994 08:12:32 GMT
-    Server: CERN/3.0 libwww/2.17
-    Content-Type: text/gif
-    (image content)
+  200 OK
+  Date: Tue, 15 Nov 1994 08:12:32 GMT
+  Server: CERN/3.0 libwww/2.17
+  Content-Type: text/gif
+  (image content)
+```
 
 These novelties have not been introduced as concerted effort, but as a try-and-see approach over the 1991-1995 period: a server and a browser added one feature and it saw if it got traction. A lot of interoperability problems were common. In November 1996, in order to solve these annoyances, an informational document describing the common practices has been published, {{RFC(1945)}}. This is the definition of HTTP/1.0 and it is notable that, in the narrow sense of the term, it isn't an official standard.
 
@@ -89,47 +97,49 @@ HTTP/1.1 clarified ambiguities and introduced numerous improvements:
 
 A typical flow of requests, all through one single connection is now looking like this:
 
-    GET /en-US/docs/Glossary/Simple_header HTTP/1.1
-    Host: developer.mozilla.org
-    User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:50.0) Gecko/20100101 Firefox/50.0
-    Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
-    Accept-Language: en-US,en;q=0.5
-    Accept-Encoding: gzip, deflate, br
-    Referer: https://developer.mozilla.org/en-US/docs/Glossary/Simple_header
-
-    200 OK
-    Connection: Keep-Alive
-    Content-Encoding: gzip
-    Content-Type: text/html; charset=utf-8
-    Date: Wed, 20 Jul 2016 10:55:30 GMT
-    Etag: "547fa7e369ef56031dd3bff2ace9fc0832eb251a"
-    Keep-Alive: timeout=5, max=1000
-    Last-Modified: Tue, 19 Jul 2016 00:59:33 GMT
-    Server: Apache
-    Transfer-Encoding: chunked
-    Vary: Cookie, Accept-Encoding
-
-    (content)
-
-    GET /static/img/header-background.png HTTP/1.1
-    Host: developer.mozilla.org
-    User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:50.0) Gecko/20100101 Firefox/50.0
-    Accept: */*
-    Accept-Language: en-US,en;q=0.5
-    Accept-Encoding: gzip, deflate, br
-    Referer: https://developer.mozilla.org/en-US/docs/Glossary/Simple_header
-
-    200 OK
-    Age: 9578461
-    Cache-Control: public, max-age=315360000
-    Connection: keep-alive
-    Content-Length: 3077
-    Content-Type: image/png
-    Date: Thu, 31 Mar 2016 13:34:46 GMT
-    Last-Modified: Wed, 21 Oct 2015 18:27:50 GMT
-    Server: Apache
-
-    (image content of 3077 bytes)
+```
+GET /en-US/docs/Glossary/Simple_header HTTP/1.1
+Host: developer.mozilla.org
+User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:50.0) Gecko/20100101 Firefox/50.0
+Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
+Accept-Language: en-US,en;q=0.5
+Accept-Encoding: gzip, deflate, br
+Referer: https://developer.mozilla.org/en-US/docs/Glossary/Simple_header
+
+200 OK
+Connection: Keep-Alive
+Content-Encoding: gzip
+Content-Type: text/html; charset=utf-8
+Date: Wed, 20 Jul 2016 10:55:30 GMT
+Etag: "547fa7e369ef56031dd3bff2ace9fc0832eb251a"
+Keep-Alive: timeout=5, max=1000
+Last-Modified: Tue, 19 Jul 2016 00:59:33 GMT
+Server: Apache
+Transfer-Encoding: chunked
+Vary: Cookie, Accept-Encoding
+
+(content)
+
+GET /static/img/header-background.png HTTP/1.1
+Host: developer.mozilla.org
+User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:50.0) Gecko/20100101 Firefox/50.0
+Accept: */*
+Accept-Language: en-US,en;q=0.5
+Accept-Encoding: gzip, deflate, br
+Referer: https://developer.mozilla.org/en-US/docs/Glossary/Simple_header
+
+200 OK
+Age: 9578461
+Cache-Control: public, max-age=315360000
+Connection: keep-alive
+Content-Length: 3077
+Content-Type: image/png
+Date: Thu, 31 Mar 2016 13:34:46 GMT
+Last-Modified: Wed, 21 Oct 2015 18:27:50 GMT
+Server: Apache
+
+(image content of 3077 bytes)
+```
 
 HTTP/1.1 was first published as {{rfc(2068)}} in January 1997.
 
diff --git a/files/en-us/web/http/basics_of_http/identifying_resources_on_the_web/index.md b/files/en-us/web/http/basics_of_http/identifying_resources_on_the_web/index.md
index 4f08d9c99833995..1ee1ed9904f0e3c 100644
--- a/files/en-us/web/http/basics_of_http/identifying_resources_on_the_web/index.md
+++ b/files/en-us/web/http/basics_of_http/identifying_resources_on_the_web/index.md
@@ -26,22 +26,28 @@ The target of an HTTP request is called a "resource", whose nature isn't defined
 
 The most common form of URI is the Uniform Resource Locator ({{Glossary("URL")}}), which is known as the _web address_.
 
-    https://developer.mozilla.org
-    https://developer.mozilla.org/en-US/docs/Learn/
-    https://developer.mozilla.org/en-US/search?q=URL
+```
+https://developer.mozilla.org
+https://developer.mozilla.org/en-US/docs/Learn/
+https://developer.mozilla.org/en-US/search?q=URL
+```
 
 Any of those URLs can be typed into your browser's address bar to tell it to load the associated page (resource).
 
 A URL is composed of different parts, some mandatory and others are optional. A more complex example might look like this:
 
-    http://www.example.com:80/path/to/myfile.html?key1=value1&key2=value2#SomewhereInTheDocument
+```
+http://www.example.com:80/path/to/myfile.html?key1=value1&key2=value2#SomewhereInTheDocument
+```
 
 ### URNs
 
-A Uniform Resource Name (URN) is a URI that identifies a resource by name in a particular namespace.
+A Uniform Resource Name (URN) is a URI that identifies a resource by name in a particular namespace.
 
-    urn:isbn:9780141036144
-    urn:ietf:rfc:7230
+```
+urn:isbn:9780141036144
+urn:ietf:rfc:7230
+```
 
 The two URNs correspond to
 
@@ -102,12 +108,14 @@ FTP is still acceptable at the top level (such as typed directly into the browse
 
 ## Examples
 
-    https://developer.mozilla.org/en-US/docs/Learn
-    tel:+1-816-555-1212
-    git@github.com:mdn/browser-compat-data.git
-    ftp://example.org/resource.txt
-    urn:isbn:9780141036144
-    mailto:help@supercyberhelpdesk.info
+```
+https://developer.mozilla.org/en-US/docs/Learn
+tel:+1-816-555-1212
+git@github.com:mdn/browser-compat-data.git
+ftp://example.org/resource.txt
+urn:isbn:9780141036144
+mailto:help@supercyberhelpdesk.info
+```
 
 ## Specifications
 
diff --git a/files/en-us/web/http/basics_of_http/mime_types/index.md b/files/en-us/web/http/basics_of_http/mime_types/index.md
index 910725acf3b3b24..2b3cee70ce4c468 100644
--- a/files/en-us/web/http/basics_of_http/mime_types/index.md
+++ b/files/en-us/web/http/basics_of_http/mime_types/index.md
@@ -41,7 +41,7 @@ The simplest MIME type consists of a _type_ and a _subtype_; these
 are each strings which, when concatenated with a slash (`/`) between them,
 comprise a MIME type. No whitespace is allowed in a MIME type:
 
-```html
+```
 type/subtype
 ```
 
@@ -58,7 +58,7 @@ and a subtype, never just one or the other.
 
 An optional **parameter** can be added to provide additional details:
 
-```html
+```
 type/subtype;parameter=value
 ```
 
@@ -299,7 +299,7 @@ As a multipart document format, it consists of different parts, delimited by a b
 its own HTTP headers, {{HTTPHeader("Content-Disposition")}}, and
 {{HTTPHeader("Content-Type")}} for file uploading fields.
 
-```html
+```
 Content-Type: multipart/form-data; boundary=aBoundaryString
 (other headers associated with the multipart document as a whole)
 
@@ -330,31 +330,33 @@ The following `<form>`:
 
 will send this message:
 
-    POST / HTTP/1.1
-    Host: localhost:8000
-    User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:50.0) Gecko/20100101 Firefox/50.0
-    Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
-    Accept-Language: en-US,en;q=0.5
-    Accept-Encoding: gzip, deflate
-    Connection: keep-alive
-    Upgrade-Insecure-Requests: 1
-    Content-Type: multipart/form-data; boundary=---------------------------8721656041911415653955004498
-    Content-Length: 465
-
-    -----------------------------8721656041911415653955004498
-    Content-Disposition: form-data; name="myTextField"
-
-    Test
-    -----------------------------8721656041911415653955004498
-    Content-Disposition: form-data; name="myCheckBox"
-
-    on
-    -----------------------------8721656041911415653955004498
-    Content-Disposition: form-data; name="myFile"; filename="test.txt"
-    Content-Type: text/plain
-
-    Simple file.
-    -----------------------------8721656041911415653955004498--
+```
+POST / HTTP/1.1
+Host: localhost:8000
+User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:50.0) Gecko/20100101 Firefox/50.0
+Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
+Accept-Language: en-US,en;q=0.5
+Accept-Encoding: gzip, deflate
+Connection: keep-alive
+Upgrade-Insecure-Requests: 1
+Content-Type: multipart/form-data; boundary=---------------------------8721656041911415653955004498
+Content-Length: 465
+
+-----------------------------8721656041911415653955004498
+Content-Disposition: form-data; name="myTextField"
+
+Test
+-----------------------------8721656041911415653955004498
+Content-Disposition: form-data; name="myCheckBox"
+
+on
+-----------------------------8721656041911415653955004498
+Content-Disposition: form-data; name="myFile"; filename="test.txt"
+Content-Type: text/plain
+
+Simple file.
+-----------------------------8721656041911415653955004498--
+```
 
 ### multipart/byteranges
 
@@ -368,26 +370,28 @@ requested ranges. Like other multipart types, the {{HTTPHeader("Content-Type")}}
 {{HTTPHeader("Content-Type")}} header with its actual type and a
 {{HTTPHeader("Content-Range")}} of the range it represents.
 
-    HTTP/1.1 206 Partial Content
-    Accept-Ranges: bytes
-    Content-Type: multipart/byteranges; boundary=3d6b6a416f9b5
-    Content-Length: 385
-
-    --3d6b6a416f9b5
-    Content-Type: text/html
-    Content-Range: bytes 100-200/1270
-
-    eta http-equiv="Content-type" content="text/html; charset=utf-8" />
-        <meta name="vieport" content
-    --3d6b6a416f9b5
-    Content-Type: text/html
-    Content-Range: bytes 300-400/1270
-
-    -color: #f0f0f2;
-            margin: 0;
-            padding: 0;
-            font-family: "Open Sans", "Helvetica
-    --3d6b6a416f9b5--
+```
+HTTP/1.1 206 Partial Content
+Accept-Ranges: bytes
+Content-Type: multipart/byteranges; boundary=3d6b6a416f9b5
+Content-Length: 385
+
+--3d6b6a416f9b5
+Content-Type: text/html
+Content-Range: bytes 100-200/1270
+
+eta http-equiv="Content-type" content="text/html; charset=utf-8" />
+    <meta name="vieport" content
+--3d6b6a416f9b5
+Content-Type: text/html
+Content-Range: bytes 300-400/1270
+
+-color: #f0f0f2;
+        margin: 0;
+        padding: 0;
+        font-family: "Open Sans", "Helvetica
+--3d6b6a416f9b5--
+```
 
 ## Importance of setting the correct MIME type
 
diff --git a/files/en-us/web/http/basics_of_http/resource_urls/index.md b/files/en-us/web/http/basics_of_http/resource_urls/index.md
index e8b23a8efd1b691..73a7b5ec09042ca 100644
--- a/files/en-us/web/http/basics_of_http/resource_urls/index.md
+++ b/files/en-us/web/http/basics_of_http/resource_urls/index.md
@@ -18,18 +18,22 @@ information is available to sites the browser connects to as well.
 Resource URLs are composed of two parts: a prefix (`resource:`), and a URL
 pointing to the resource you want to load:
 
-```html
+```
 resource://<url>
 ```
 
 An example:
 
-    resource://gre/res/svg.css
+```
+resource://gre/res/svg.css
+```
 
 When arrows are found in the resource URL's ('->'), it means that the first file
 loaded the next one:
 
-    resource://<File-loader> -> <File-loaded>
+```
+resource://<File-loader> -> <File-loaded>
+```
 
 Please refer to [Identifying
 resources on the web](/en-US/docs/Web/HTTP/Basics_of_HTTP/Identifying_resources_on_the_Web) for more general details.
@@ -51,7 +55,9 @@ running on the site (you can find the code in <https://browserleaks.com/firefox#
 The file firefox.js passes preference names and values to the pref() function. For
 example:
 
-    http://searchfox.org/mozilla-central/rev/48ea452803907f2575d81021e8678634e8067fc2/browser/app/profile/firefox.js#575
+```
+http://searchfox.org/mozilla-central/rev/48ea452803907f2575d81021e8678634e8067fc2/browser/app/profile/firefox.js#575
+```
 
 Web sites can easily collect Firefox default preferences by overriding this
 `pref()` function and using the script
@@ -67,15 +73,15 @@ In order to fix this problem, Mozilla changed the behavior of loading resource:
 {{bug(863246)}}, which landed in [Firefox 57 (Quantum)](/en-US/docs/Mozilla/Firefox/Releases/57).
 
 In the past, web content was able to access whatever `resource:` URIs were
-desired — not only Firefox’s internal resources, but also extensions’ assets.  Now this
+desired — not only Firefox's internal resources, but also extensions’ assets. Now this
 behavior is prohibited by default.
 
 It is however still necessary for Firefox to load resources in web content under
-certain circumstances.  For example, if you open the view source page (View Page Source
+certain circumstances. For example, if you open the view source page (View Page Source
 or View Selection Source), you will find it requires `viewsource.css` through
-a `resource:` URI.  Resources that have to be exposed to web content have
+a `resource:` URI. Resources that have to be exposed to web content have
 been moved to a new location named `resource://content-accessible/`, which is
-isolated and only contains non-sensitive resources.  In this way we can keep essential
+isolated and only contains non-sensitive resources. In this way we can keep essential
 resources exposed and have most threats eliminated.
 
 > **Note:** It is recommended that web and extension developers don't try
diff --git a/files/en-us/web/http/caching/index.md b/files/en-us/web/http/caching/index.md
index 2dc9d3da2a1dfe0..53cb1a5b2d4215b 100644
--- a/files/en-us/web/http/caching/index.md
+++ b/files/en-us/web/http/caching/index.md
@@ -50,13 +50,17 @@ The {{HTTPHeader("Cache-Control")}} HTTP/1.1 general-header field is used to spe
 
 The cache should not store anything about the client request or server response. A request is sent to the server and a full response is downloaded each and every time.
 
-    Cache-Control: no-store
+```
+Cache-Control: no-store
+```
 
 #### Cache but revalidate
 
 A cache will send the request to the origin server for validation before releasing a cached copy.
 
-    Cache-Control: no-cache
+```
+Cache-Control: no-cache
+```
 
 #### Private and public caches
 
@@ -64,8 +68,10 @@ The "public" directive indicates that the response may be cached by any cache. T
 
 On the other hand, "private" indicates that the response is intended for a single user only and must not be stored by a shared cache. A private browser cache may store the response in this case.
 
-    Cache-Control: private
-    Cache-Control: public
+```
+Cache-Control: private
+Cache-Control: public
+```
 
 #### Expiration
 
@@ -73,13 +79,17 @@ The most important directive here is `max-age=<seconds>`, which is the maximum a
 
 For more details, see also the [Freshness](#freshness) section below.
 
-    Cache-Control: max-age=31536000
+```
+Cache-Control: max-age=31536000
+```
 
 #### Validation
 
 When using the "`must-revalidate`" directive, the cache must verify the status of the stale resources before using it and expired ones should not be used. For more details, see the [Validation](#cache_validation) section below.
 
-    Cache-Control: must-revalidate
+```
+Cache-Control: must-revalidate
+```
 
 ### The `Pragma` header
 
@@ -103,7 +113,9 @@ If an origin server does not explicitly specify freshness (e.g. using {{HTTPHea
 
 In this case look for a {{HTTPHeader("Last-Modified")}} header. If this header is present, then the cache's freshness lifetime is equal to the value of the `Date` header minus the value of the `Last-modified` header divided by 10. The expiration time is computed as follows:
 
-    expirationTime = responseTime + freshnessLifetime - currentAge
+```
+expirationTime = responseTime + freshnessLifetime - currentAge
+```
 
 where `responseTime` is the time at which the response was received according to the browser. For more information see [RFC 7234: Hypertext Transfer Protocol (HTTP/1.1): 4.2.2.  Calculating Heuristic Freshness](https://datatracker.ietf.org/doc/html/rfc7234#section-4.2.2).
 
@@ -143,13 +155,17 @@ When a cache receives a request that has a `Vary` header field, it must not use
 
 ![The Vary header leads cache to use more HTTP headers as key for the cache.](http_vary.png)This feature is commonly used to allow a resource to be cached in uncompressed and (various) compressed forms, and served appropriately to user agents based on the encodings that they support. For example, a server can set `Vary: Accept-Encoding` to ensure that a separate version of a resource is cached for all requests that specify support for a particular set of encodings, e.g. `Accept-Encoding: gzip,deflate,sdch`.
 
-    Vary: Accept-Encoding
+```
+Vary: Accept-Encoding
+```
 
 > **Note:** Use `Vary` with care—it can easily reduce the effectiveness of caching! A caching server should use [normalization](#normalization) to reduce duplicated cache entries and unnecessary requests to the origin server. This is particularly true when using `Vary` with headers and header values that can have many values.
 
 The `Vary` header can also be useful for serving different content to desktop and mobile users, or to allow search engines to discover the mobile version of a page (and perhaps also tell them that no [Cloaking](https://en.wikipedia.org/wiki/Cloaking) is intended). This is usually achieved with the `Vary: User-Agent` header, and works because the {{HTTPHeader("User-Agent")}} header value is different for mobile and desktop clients.
 
-    Vary: User-Agent
+```
+Vary: User-Agent
+```
 
 ### Normalization
 
@@ -159,16 +175,18 @@ For example, by default all of the following result in a separate request to the
 
 To avoid unnecessary requests and duplicated cache entries, caching servers should use **normalization** to pre-process the request and cache only files that are needed. For example, in the case of `Accept-Encoding` you could check for `gzip` and other compression types in the header before doing further processing, and otherwise unset the header. In "pseudo code" this might look like:
 
-    // Normalize Accept-Encoding
-    if (req.http.Accept-Encoding) {
-      if (req.http.Accept-Encoding ~ "gzip") {
-        set req.http.Accept-Encoding = "gzip";
-      }
-      // elsif other encoding types to check
-      else {
-        unset req.http.Accept-Encoding;
-      }
-    }
+```
+// Normalize Accept-Encoding
+if (req.http.Accept-Encoding) {
+  if (req.http.Accept-Encoding ~ "gzip") {
+    set req.http.Accept-Encoding = "gzip";
+  }
+  // elsif other encoding types to check
+  else {
+    unset req.http.Accept-Encoding;
+  }
+}
+```
 
 `User-Agent` has even more variation than `Accept-Encoding`. So if using `Vary: User-Agent` for caching mobile/desktop variants of files you'd similarly check for the presence of `"mobile"` and `"desktop"` in the request `User-Agent` header, and then clear it.
 
diff --git a/files/en-us/web/http/configuring_servers_for_ogg_media/index.md b/files/en-us/web/http/configuring_servers_for_ogg_media/index.md
index ea9d1d65ad3bbc5..4c1617efbe667ac 100644
--- a/files/en-us/web/http/configuring_servers_for_ogg_media/index.md
+++ b/files/en-us/web/http/configuring_servers_for_ogg_media/index.md
@@ -24,9 +24,11 @@ Most servers don't by default serve Ogg media with the correct MIME types, so y
 
 For Apache, you can add the following to your configuration:
 
-    AddType audio/ogg .oga
-    AddType video/ogg .ogv
-    AddType application/ogg .ogg
+```
+AddType audio/ogg .oga
+AddType video/ogg .ogv
+AddType application/ogg .ogg
+```
 
 You can find specific information about possible media file types and the codecs used within them in our comprehensive [guide to media types and formats on the web](/en-US/docs/Web/Media/Formats). In particular, the article on [media container formats](/en-US/docs/Web/Media/Formats/Containers) will be especially helpful when configuring servers to host media properly.
 
@@ -64,7 +66,9 @@ There are two ways Gecko can do this. The best way is to offer an `X-Content-Dur
 
 For example, if the video is 1 minute and 32.6 seconds long, this header would be:
 
-    X-Content-Duration: 92.6
+```
+X-Content-Duration: 92.6
+```
 
 If your server provides the `X-Content-Duration` header when serving Ogg media, Gecko doesn't have to do any extra HTTP requests to seek to the end of the file to calculate its duration. This makes the entire process much more efficient as well as more accurate.
 
@@ -82,24 +86,26 @@ Another probelm with allowing HTTP compression for media streaming: Apache serve
 
 You can use the `oggz-info` tool to get the media duration; this tool is included with the [`oggz-tools`](https://www.xiph.org/oggz/) package. The output from `oggz-info` looks like this:
 
-     $ oggz-info /g/media/bruce_vs_ironman.ogv
-     Content-Duration: 00:01:00.046
-
-     Skeleton: serialno 1976223438
-             4 packets in 3 pages, 1.3 packets/page, 27.508% Ogg overhead
-             Presentation-Time: 0.000
-             Basetime: 0.000
-
-     Theora: serialno 0170995062
-             1790 packets in 1068 pages, 1.7 packets/page, 1.049% Ogg overhead
-             Video-Framerate: 29.983 fps
-             Video-Width: 640
-             Video-Height: 360
-
-     Vorbis: serialno 0708996688
-             4531 packets in 167 pages, 27.1 packets/page, 1.408% Ogg overhead
-             Audio-Samplerate: 44100 Hz
-             Audio-Channels: 2
+```
+$ oggz-info /g/media/bruce_vs_ironman.ogv
+Content-Duration: 00:01:00.046
+
+Skeleton: serialno 1976223438
+        4 packets in 3 pages, 1.3 packets/page, 27.508% Ogg overhead
+        Presentation-Time: 0.000
+        Basetime: 0.000
+
+Theora: serialno 0170995062
+        1790 packets in 1068 pages, 1.7 packets/page, 1.049% Ogg overhead
+        Video-Framerate: 29.983 fps
+        Video-Width: 640
+        Video-Height: 360
+
+Vorbis: serialno 0708996688
+        4531 packets in 167 pages, 27.1 packets/page, 1.408% Ogg overhead
+        Audio-Samplerate: 44100 Hz
+        Audio-Channels: 2
+```
 
 Note that you can't serve up the reported Content-Duration line reported by `oggz-info`, because it's reported in HH:MM:SS format. You'll need to convert it to seconds only, then serve that as your `X-Content-Duration` value. Just parse out the HH, MM, and SS into numbers, then do (HH\*3600)+(MM\*60)+SS to get the value you should report.
 
diff --git a/files/en-us/web/http/cookies/index.md b/files/en-us/web/http/cookies/index.md
index 6ddc8eb296466ab..0ae8e67e5f200b1 100644
--- a/files/en-us/web/http/cookies/index.md
+++ b/files/en-us/web/http/cookies/index.md
@@ -51,18 +51,21 @@ Set-Cookie: <cookie-name>=<cookie-value>
 
 This shows the server sending headers to tell the client to store a pair of cookies:
 
-    HTTP/2.0 200 OK
-    Content-Type: text/html
-    Set-Cookie: yummy_cookie=choco
-    Set-Cookie: tasty_cookie=strawberry
+```
+HTTP/2.0 200 OK
+Content-Type: text/html
+Set-Cookie: yummy_cookie=choco
+Set-Cookie: tasty_cookie=strawberry
 
-    [page content]
+[page content]
+```
 
 Then, with every subsequent request to the server, the browser sends back all previously stored cookies to the server using the {{HTTPHeader("Cookie")}} header.
 
-    GET /sample_page.html HTTP/2.0
-    Host: www.example.org
-    Cookie: yummy_cookie=choco; tasty_cookie=strawberry
+```GET /sample_page.html HTTP/2.0
+Host: www.example.org
+Cookie: yummy_cookie=choco; tasty_cookie=strawberry
+```
 
 > **Note:** Here's how to use the `Set-Cookie` header in various server-side applications:
 >
@@ -80,7 +83,9 @@ The lifetime of a cookie can be defined in two ways:
 
 For example:
 
-    Set-Cookie: id=a3fWa; Expires=Thu, 31 Oct 2021 07:28:00 GMT;
+```
+Set-Cookie: id=a3fWa; Expires=Thu, 31 Oct 2021 07:28:00 GMT;
+```
 
 > **Note:** When an `Expires` date is set, the time and date set is relative to the client the cookie is being set on, not the server.
 
@@ -96,7 +101,9 @@ A cookie with the `HttpOnly` attribute is inaccessible to the JavaScript {{domxr
 
 Here is an example:
 
-    Set-Cookie: id=a3fWa; Expires=Thu, 21 Oct 2021 07:28:00 GMT; Secure; HttpOnly
+```
+Set-Cookie: id=a3fWa; Expires=Thu, 21 Oct 2021 07:28:00 GMT; Secure; HttpOnly
+```
 
 ### Define where cookies are sent
 
@@ -126,7 +133,9 @@ It takes three possible values: `Strict`, `Lax`, and `None`. With `Strict`, the
 
 Here is an example:
 
-    Set-Cookie: mykey=myvalue; SameSite=Strict
+```
+Set-Cookie: mykey=myvalue; SameSite=Strict
+```
 
 > **Note:** Standard related to `SameSite` recently changed (MDN documents the new behavior above). See the cookies [Browser compatibility](/en-US/docs/Web/HTTP/Headers/Set-Cookie/SameSite#browser_compatibility) table for information about how the attribute is handled in specific browser versions:
 >
diff --git a/files/en-us/web/http/cors/errors/corsalloworiginnotmatchingorigin/index.md b/files/en-us/web/http/cors/errors/corsalloworiginnotmatchingorigin/index.md
index ff21cb90ef6e559..7c0e4afbdac03a5 100644
--- a/files/en-us/web/http/cors/errors/corsalloworiginnotmatchingorigin/index.md
+++ b/files/en-us/web/http/cors/errors/corsalloworiginnotmatchingorigin/index.md
@@ -18,18 +18,16 @@ tags:
 
 ## Reason
 
-```html
+```
 Reason: CORS header 'Access-Control-Allow-Origin' does not match 'xyz'
 ```
 
 ## What went wrong?
 
-The origin making the request does not match the origin permitted by the {{HTTPHeader("Access-Control-Allow-Origin")}} header. This error can also occur if the response includes more than one
-`Access-Control-Allow-Origin` header.
+The origin making the request does not match the origin permitted by the {{HTTPHeader("Access-Control-Allow-Origin")}} header. This error can also occur if the response includes more than one `Access-Control-Allow-Origin` header.
 
 If the service your code is accessing uses a CORS request under your control, make
-sure it is configured to include your origin in its
-`Access-Control-Allow-Origin` header. In addition, confirm that only one such header is
+sure it is configured to include your origin in its `Access-Control-Allow-Origin` header. In addition, confirm that only one such header is
 included in responses, and that it includes only a single origin.
 
 For example, in Apache, add a line such as the following to the server's configuration
@@ -39,11 +37,15 @@ configuration is typically found in a `.conf` file (`httpd.conf`
 and `apache.conf` are common names for these), or in an
 `.htaccess` file.
 
-    Header set Access-Control-Allow-Origin 'origin'
+```
+Header set Access-Control-Allow-Origin 'origin'
+```
 
 For Nginx, the command to set up this header is:
 
-    add_header 'Access-Control-Allow-Origin' 'origin'
+```
+add_header 'Access-Control-Allow-Origin' 'origin'
+```
 
 ## See also
 
diff --git a/files/en-us/web/http/cors/errors/corsdidnotsucceed/index.md b/files/en-us/web/http/cors/errors/corsdidnotsucceed/index.md
index dcd7936cb29e19a..f412fe0eaee36bd 100644
--- a/files/en-us/web/http/cors/errors/corsdidnotsucceed/index.md
+++ b/files/en-us/web/http/cors/errors/corsdidnotsucceed/index.md
@@ -18,7 +18,7 @@ tags:
 
 ## Reason
 
-```html
+```
 Reason: CORS request did not succeed
 ```
 
diff --git a/files/en-us/web/http/cors/errors/corsdisabled/index.md b/files/en-us/web/http/cors/errors/corsdisabled/index.md
index 4dfb9f11608b7ad..e412b4e66d634fd 100644
--- a/files/en-us/web/http/cors/errors/corsdisabled/index.md
+++ b/files/en-us/web/http/cors/errors/corsdisabled/index.md
@@ -24,7 +24,7 @@ tags:
 
 ## Reason
 
-```html
+```
 Reason: CORS disabled
 ```
 
diff --git a/files/en-us/web/http/cors/errors/corsexternalredirectnotallowed/index.md b/files/en-us/web/http/cors/errors/corsexternalredirectnotallowed/index.md
index 80d2d22daf8d6b5..be7b138da1f501f 100644
--- a/files/en-us/web/http/cors/errors/corsexternalredirectnotallowed/index.md
+++ b/files/en-us/web/http/cors/errors/corsexternalredirectnotallowed/index.md
@@ -18,7 +18,7 @@ tags:
 
 ## Reason
 
-```html
+```
 Reason: CORS request external redirect not allowed
 ```
 
diff --git a/files/en-us/web/http/cors/errors/corsinvalidallowheader/index.md b/files/en-us/web/http/cors/errors/corsinvalidallowheader/index.md
index f18f17cc9988eb1..f86500997858dc9 100644
--- a/files/en-us/web/http/cors/errors/corsinvalidallowheader/index.md
+++ b/files/en-us/web/http/cors/errors/corsinvalidallowheader/index.md
@@ -18,8 +18,8 @@ tags:
 
 ## Reason
 
-```html
-Reason: invalid token ‘xyz’ in CORS header ‘Access-Control-Allow-Headers’
+```
+Reason: invalid token 'xyz' in CORS header 'Access-Control-Allow-Headers'
 ```
 
 ## What went wrong?
diff --git a/files/en-us/web/http/cors/errors/corsinvalidallowmethod/index.md b/files/en-us/web/http/cors/errors/corsinvalidallowmethod/index.md
index 4e10d3b19dcad9f..e27ed6c6e8f3f71 100644
--- a/files/en-us/web/http/cors/errors/corsinvalidallowmethod/index.md
+++ b/files/en-us/web/http/cors/errors/corsinvalidallowmethod/index.md
@@ -18,8 +18,8 @@ tags:
 
 ## Reason
 
-```html
-Reason: invalid token ‘xyz’ in CORS header ‘Access-Control-Allow-Methods’
+```
+Reason: invalid token 'xyz' in CORS header 'Access-Control-Allow-Methods'
 ```
 
 ## What went wrong?
diff --git a/files/en-us/web/http/cors/errors/corsmethodnotfound/index.md b/files/en-us/web/http/cors/errors/corsmethodnotfound/index.md
index 1717761cdebfb44..dfb87c901f59f42 100644
--- a/files/en-us/web/http/cors/errors/corsmethodnotfound/index.md
+++ b/files/en-us/web/http/cors/errors/corsmethodnotfound/index.md
@@ -18,8 +18,8 @@ tags:
 
 ## Reason
 
-```html
-Reason: Did not find method in CORS header ‘Access-Control-Allow-Methods’
+```
+Reason: Did not find method in CORS header 'Access-Control-Allow-Methods'
 ```
 
 ## What went wrong?
diff --git a/files/en-us/web/http/cors/errors/corsmissingallowcredentials/index.md b/files/en-us/web/http/cors/errors/corsmissingallowcredentials/index.md
index 6f89fe8c4984670..812cf20163db036 100644
--- a/files/en-us/web/http/cors/errors/corsmissingallowcredentials/index.md
+++ b/files/en-us/web/http/cors/errors/corsmissingallowcredentials/index.md
@@ -18,8 +18,8 @@ tags:
 
 ## Reason
 
-```html
-Reason: expected ‘true’ in CORS header ‘Access-Control-Allow-Credentials’
+```
+Reason: expected 'true' in CORS header 'Access-Control-Allow-Credentials'
 ```
 
 ## What went wrong?
diff --git a/files/en-us/web/http/cors/errors/corsmissingallowheaderfrompreflight/index.md b/files/en-us/web/http/cors/errors/corsmissingallowheaderfrompreflight/index.md
index 35324bd84f68cbc..1e42209430616e5 100644
--- a/files/en-us/web/http/cors/errors/corsmissingallowheaderfrompreflight/index.md
+++ b/files/en-us/web/http/cors/errors/corsmissingallowheaderfrompreflight/index.md
@@ -20,8 +20,8 @@ tags:
 
 ## Reason
 
-```html
-Reason: missing token ‘xyz’ in CORS header ‘Access-Control-Allow-Headers’ from CORS preflight channel
+```
+Reason: missing token 'xyz' in CORS header 'Access-Control-Allow-Headers' from CORS preflight channel
 ```
 
 ## What went wrong?
diff --git a/files/en-us/web/http/cors/errors/corsmissingalloworigin/index.md b/files/en-us/web/http/cors/errors/corsmissingalloworigin/index.md
index 71c7911c33b401f..8ffef8dd4b16715 100644
--- a/files/en-us/web/http/cors/errors/corsmissingalloworigin/index.md
+++ b/files/en-us/web/http/cors/errors/corsmissingalloworigin/index.md
@@ -18,7 +18,7 @@ tags:
 
 ## Reason
 
-```html
+```
 Reason: CORS header 'Access-Control-Allow-Origin' missing
 ```
 
@@ -35,7 +35,9 @@ header's value.
 For example, to allow a site at https\://amazing.site to access the resource using CORS,
 the header should be:
 
-    Access-Control-Allow-Origin: https://amazing.site
+```
+Access-Control-Allow-Origin: https://amazing.site
+```
 
 You can also configure a site to allow any site to access it by using the
 `*` wildcard. You should only use this for public APIs. Private APIs should
@@ -44,7 +46,9 @@ addition, the wildcard only works for requests made with the
 {{htmlattrxref("crossorigin")}} attribute set to `anonymous`, and it prevents
 sending credentials like cookies in requests.
 
-    Access-Control-Allow-Origin: *
+```
+Access-Control-Allow-Origin: *
+```
 
 > **Warning:** Using the wildcard to allow all sites to access a private
 > API is a bad idea.
@@ -63,11 +67,15 @@ configuration is typically found in a `.conf` file (`httpd.conf`
 and `apache.conf` are common names for these), or in an
 `.htaccess` file.
 
-    Header set Access-Control-Allow-Origin 'origin-list'
+```
+Header set Access-Control-Allow-Origin 'origin-list'
+```
 
 For Nginx, the command to set up this header is:
 
-    add_header 'Access-Control-Allow-Origin' 'origin-list';
+```
+add_header 'Access-Control-Allow-Origin' 'origin-list';
+```
 
 ## See also
 
diff --git a/files/en-us/web/http/cors/errors/corsmultiplealloworiginnotallowed/index.md b/files/en-us/web/http/cors/errors/corsmultiplealloworiginnotallowed/index.md
index 530d6b73e7b98ca..10df2a15fde3683 100644
--- a/files/en-us/web/http/cors/errors/corsmultiplealloworiginnotallowed/index.md
+++ b/files/en-us/web/http/cors/errors/corsmultiplealloworiginnotallowed/index.md
@@ -18,8 +18,8 @@ tags:
 
 ## Reason
 
-```html
-Reason: Multiple CORS header ‘Access-Control-Allow-Origin’ not allowed
+```
+Reason: Multiple CORS header 'Access-Control-Allow-Origin' not allowed
 ```
 
 ## What went wrong?
diff --git a/files/en-us/web/http/cors/errors/corsnotsupportingcredentials/index.md b/files/en-us/web/http/cors/errors/corsnotsupportingcredentials/index.md
index 835a1fed02fd3fa..f9d3febcb2804ca 100644
--- a/files/en-us/web/http/cors/errors/corsnotsupportingcredentials/index.md
+++ b/files/en-us/web/http/cors/errors/corsnotsupportingcredentials/index.md
@@ -20,8 +20,8 @@ tags:
 
 ## Reason
 
-```html
-Reason: Credential is not supported if the CORS header ‘Access-Control-Allow-Origin’ is ‘*’
+```
+Reason: Credential is not supported if the CORS header 'Access-Control-Allow-Origin' is '*'
 ```
 
 ## What went wrong?
diff --git a/files/en-us/web/http/cors/errors/corsoriginheadernotadded/index.md b/files/en-us/web/http/cors/errors/corsoriginheadernotadded/index.md
index f86ad85b15f6ae9..3416f99f64be374 100644
--- a/files/en-us/web/http/cors/errors/corsoriginheadernotadded/index.md
+++ b/files/en-us/web/http/cors/errors/corsoriginheadernotadded/index.md
@@ -18,8 +18,8 @@ tags:
 
 ## Reason
 
-```html
-Reason: CORS header ‘Origin’ cannot be added
+```
+Reason: CORS header 'Origin' cannot be added
 ```
 
 ## What went wrong?
diff --git a/files/en-us/web/http/cors/errors/corspreflightdidnotsucceed/index.md b/files/en-us/web/http/cors/errors/corspreflightdidnotsucceed/index.md
index aa24b1187925652..c23239369200c26 100644
--- a/files/en-us/web/http/cors/errors/corspreflightdidnotsucceed/index.md
+++ b/files/en-us/web/http/cors/errors/corspreflightdidnotsucceed/index.md
@@ -18,13 +18,13 @@ tags:
 
 ## Reason
 
-```html
+```
 Reason: CORS preflight channel did not succeed
 ```
 
 ## What went wrong?
 
-The {{Glossary("CORS")}} request requires  preflight, preflighting could not be
+The {{Glossary("CORS")}} request requires preflight, preflighting could not be
 performed. There are a couple of reasons why preflighting might fail:
 
 - A cross-site request has previously been performed that already did a preflight, and
diff --git a/files/en-us/web/http/cors/errors/corsrequestnothttp/index.md b/files/en-us/web/http/cors/errors/corsrequestnothttp/index.md
index 3f608973724c1f4..d05def3fdbea140 100644
--- a/files/en-us/web/http/cors/errors/corsrequestnothttp/index.md
+++ b/files/en-us/web/http/cors/errors/corsrequestnothttp/index.md
@@ -18,7 +18,7 @@ tags:
 
 ## Reason
 
-```html
+```
 Reason: CORS request not HTTP
 ```
 
diff --git a/files/en-us/web/http/cors/errors/index.md b/files/en-us/web/http/cors/errors/index.md
index 64e127f3740b4b0..21816e6618b85e4 100644
--- a/files/en-us/web/http/cors/errors/index.md
+++ b/files/en-us/web/http/cors/errors/index.md
@@ -29,15 +29,17 @@ To understand the underlying issue with the CORS configuration, you need to find
 
 The text of the error message will be something similar to the following:
 
-    Cross-Origin Request Blocked: The Same Origin Policy disallows
-    reading the remote resource at https://some-url-here. (Reason:
-    additional information here).
+```
+Cross-Origin Request Blocked: The Same Origin Policy disallows
+reading the remote resource at https://some-url-here. (Reason:
+additional information here).
+````
 
 > **Note:** For security reasons, specifics about what went wrong with a CORS request _are not available to JavaScript code_. All the code knows is that an error occurred. The only way to determine what specifically went wrong is to look at the browser's console for details.
 
 ## CORS error messages
 
-Firefox's console displays messages in its console when requests fail due to CORS. Part of the error text is a "reason" message that provides added insight into what went wrong.  The reason messages are listed below; click the message to open an article explaining the error in more detail and offering possible solutions.
+Firefox's console displays messages in its console when requests fail due to CORS. Part of the error text is a "reason" message that provides added insight into what went wrong. The reason messages are listed below; click the message to open an article explaining the error in more detail and offering possible solutions.
 
 - [Reason: CORS disabled](/en-US/docs/Web/HTTP/CORS/Errors/CORSDisabled)
 - [Reason: CORS request did not succeed](/en-US/docs/Web/HTTP/CORS/Errors/CORSDidNotSucceed)
diff --git a/files/en-us/web/http/cors/index.md b/files/en-us/web/http/cors/index.md
index 031b6535f4cae78..2d69dd383e555fd 100644
--- a/files/en-us/web/http/cors/index.md
+++ b/files/en-us/web/http/cors/index.md
@@ -58,7 +58,7 @@ We present three scenarios that demonstrate how Cross-Origin Resource Sharing wo
 
 ### Simple requests
 
-Some requests don't trigger a {{Glossary("Preflight_request","CORS preflight")}}. Those are called _simple requests_, though the {{SpecName('Fetch')}} spec (which defines CORS) doesn't use that term. A _simple request_ is one that **meets all the following conditions**:
+Some requests don't trigger a {{Glossary("Preflight_request","CORS preflight")}}. Those are called _simple requests_, though the {{SpecName("Fetch")}} spec (which defines CORS) doesn't use that term. A _simple request_ is one that **meets all the following conditions**:
 
 - One of the allowed methods:
 
@@ -107,31 +107,35 @@ This performs a simple exchange between the client and the server, using CORS he
 
 Let's look at what the browser will send to the server in this case, and let's see how the server responds:
 
-    GET /resources/public-data/ HTTP/1.1
-    Host: bar.other
-    User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:71.0) Gecko/20100101 Firefox/71.0
-    Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
-    Accept-Language: en-us,en;q=0.5
-    Accept-Encoding: gzip,deflate
-    Connection: keep-alive
-    Origin: https://foo.example
+```
+GET /resources/public-data/ HTTP/1.1
+Host: bar.other
+User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:71.0) Gecko/20100101 Firefox/71.0
+Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
+Accept-Language: en-us,en;q=0.5
+Accept-Encoding: gzip,deflate
+Connection: keep-alive
+Origin: https://foo.example
+```
 
 The request header of note is {{HTTPHeader("Origin")}}, which shows that the invocation is coming from `https://foo.example`.
 
-    HTTP/1.1 200 OK
-    Date: Mon, 01 Dec 2008 00:23:53 GMT
-    Server: Apache/2
-    Access-Control-Allow-Origin: *
-    Keep-Alive: timeout=2, max=100
-    Connection: Keep-Alive
-    Transfer-Encoding: chunked
-    Content-Type: application/xml
+```
+HTTP/1.1 200 OK
+Date: Mon, 01 Dec 2008 00:23:53 GMT
+Server: Apache/2
+Access-Control-Allow-Origin: *
+Keep-Alive: timeout=2, max=100
+Connection: Keep-Alive
+Transfer-Encoding: chunked
+Content-Type: application/xml
 
-    […XML Data…]
+[…XML Data…]
+```
 
 In response, the server sends back an {{HTTPHeader("Access-Control-Allow-Origin")}} header with `Access-Control-Allow-Origin: *`, which means that the resource can be accessed by **any** origin.
 
-```html
+```
 Access-Control-Allow-Origin: *
 ```
 
@@ -164,41 +168,47 @@ The example above creates an XML body to send with the `POST` request. Also, a n
 
 Let's look at the full exchange between client and server. The first exchange is the _preflight request/response_:
 
-    OPTIONS /doc HTTP/1.1
-    Host: bar.other
-    User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:71.0) Gecko/20100101 Firefox/71.0
-    Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
-    Accept-Language: en-us,en;q=0.5
-    Accept-Encoding: gzip,deflate
-    Connection: keep-alive
-    Origin: https://foo.example
-    Access-Control-Request-Method: POST
-    Access-Control-Request-Headers: X-PINGOTHER, Content-Type
-
-    HTTP/1.1 204 No Content
-    Date: Mon, 01 Dec 2008 01:15:39 GMT
-    Server: Apache/2
-    Access-Control-Allow-Origin: https://foo.example
-    Access-Control-Allow-Methods: POST, GET, OPTIONS
-    Access-Control-Allow-Headers: X-PINGOTHER, Content-Type
-    Access-Control-Max-Age: 86400
-    Vary: Accept-Encoding, Origin
-    Keep-Alive: timeout=2, max=100
-    Connection: Keep-Alive
+```plain
+OPTIONS /doc HTTP/1.1
+Host: bar.other
+User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:71.0) Gecko/20100101 Firefox/71.0
+Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
+Accept-Language: en-us,en;q=0.5
+Accept-Encoding: gzip,deflate
+Connection: keep-alive
+Origin: https://foo.example
+Access-Control-Request-Method: POST
+Access-Control-Request-Headers: X-PINGOTHER, Content-Type
+
+HTTP/1.1 204 No Content
+Date: Mon, 01 Dec 2008 01:15:39 GMT
+Server: Apache/2
+Access-Control-Allow-Origin: https://foo.example
+Access-Control-Allow-Methods: POST, GET, OPTIONS
+Access-Control-Allow-Headers: X-PINGOTHER, Content-Type
+Access-Control-Max-Age: 86400
+Vary: Accept-Encoding, Origin
+Keep-Alive: timeout=2, max=100
+Connection: Keep-Alive
+```
 
 Lines 1 - 10 above represent the preflight request with the {{HTTPMethod("OPTIONS")}} method. The browser determines that it needs to send this based on the request parameters that the JavaScript code snippet above was using, so that the server can respond whether it is acceptable to send the request with the actual request parameters. OPTIONS is an HTTP/1.1 method that is used to determine further information from servers, and is a {{Glossary("Safe/HTTP", "safe")}} method, meaning that it can't be used to change the resource. Note that along with the OPTIONS request, two other request headers are sent (lines 9 and 10 respectively):
 
-    Access-Control-Request-Method: POST
-    Access-Control-Request-Headers: X-PINGOTHER, Content-Type
+```
+Access-Control-Request-Method: POST
+Access-Control-Request-Headers: X-PINGOTHER, Content-Type
+```
 
 The {{HTTPHeader("Access-Control-Request-Method")}} header notifies the server as part of a preflight request that when the actual request is sent, it will be sent with a `POST` request method. The {{HTTPHeader("Access-Control-Request-Headers")}} header notifies the server that when the actual request is sent, it will be sent with a `X-PINGOTHER` and `Content-Type` custom headers. The server now has an opportunity to determine whether it wishes to accept a request under these circumstances.
 
 Lines 13 - 22 above are the response that the server sends back, which indicate that the request method (`POST`) and request headers (`X-PINGOTHER`) are acceptable. In particular, let's look at lines 16-19:
 
-    Access-Control-Allow-Origin: https://foo.example
-    Access-Control-Allow-Methods: POST, GET, OPTIONS
-    Access-Control-Allow-Headers: X-PINGOTHER, Content-Type
-    Access-Control-Max-Age: 86400
+```
+Access-Control-Allow-Origin: https://foo.example
+Access-Control-Allow-Methods: POST, GET, OPTIONS
+Access-Control-Allow-Headers: X-PINGOTHER, Content-Type
+Access-Control-Max-Age: 86400
+```
 
 The server responds with `Access-Control-Allow-Origin: https://foo.example`, restricting access to just the requesting origin domain. It also responds with `Access-Control-Allow-Methods`, which says that `POST` and `GET` are viable methods to query the resource in question (this header is similar to the {{HTTPHeader("Allow")}} response header, but used strictly within the context of access control).
 
@@ -208,43 +218,44 @@ Finally, {{HTTPHeader("Access-Control-Max-Age")}} gives the value in seconds for
 
 Once the preflight request is complete, the real request is sent:
 
-    POST /doc HTTP/1.1
-    Host: bar.other
-    User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:71.0) Gecko/20100101 Firefox/71.0
-    Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
-    Accept-Language: en-us,en;q=0.5
-    Accept-Encoding: gzip,deflate
-    Connection: keep-alive
-    X-PINGOTHER: pingpong
-    Content-Type: text/xml; charset=UTF-8
-    Referer: https://foo.example/examples/preflightInvocation.html
-    Content-Length: 55
-    Origin: https://foo.example
-    Pragma: no-cache
-    Cache-Control: no-cache
-
-    <person><name>Arun</name></person>
-
-    HTTP/1.1 200 OK
-    Date: Mon, 01 Dec 2008 01:15:40 GMT
-    Server: Apache/2
-    Access-Control-Allow-Origin: https://foo.example
-    Vary: Accept-Encoding, Origin
-    Content-Encoding: gzip
-    Content-Length: 235
-    Keep-Alive: timeout=2, max=99
-    Connection: Keep-Alive
-    Content-Type: text/plain
-
-    [Some XML payload]
+```plain
+POST /doc HTTP/1.1
+Host: bar.other
+User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:71.0) Gecko/20100101 Firefox/71.0
+Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
+Accept-Language: en-us,en;q=0.5
+Accept-Encoding: gzip,deflate
+Connection: keep-alive
+X-PINGOTHER: pingpong
+Content-Type: text/xml; charset=UTF-8
+Referer: https://foo.example/examples/preflightInvocation.html
+Content-Length: 55
+Origin: https://foo.example
+Pragma: no-cache
+Cache-Control: no-cache
+
+<person><name>Arun</name></person>
+
+HTTP/1.1 200 OK
+Date: Mon, 01 Dec 2008 01:15:40 GMT
+Server: Apache/2
+Access-Control-Allow-Origin: https://foo.example
+Vary: Accept-Encoding, Origin
+Content-Encoding: gzip
+Content-Length: 235
+Keep-Alive: timeout=2, max=99
+Connection: Keep-Alive
+Content-Type: text/plain
+
+[Some XML payload]
+```
 
 #### Preflighted requests and redirects
 
 Not all browsers currently support following redirects after a preflighted request. If a redirect occurs after a preflighted request, some browsers currently will report an error message such as the following.
 
-> The request was redirected to 'https\://example.com/foo', which is disallowed for cross-origin requests that require preflight
-
-> Request requires preflight, which is disallowed to follow cross-origin redirect
+> The request was redirected to 'https\://example.com/foo', which is disallowed for cross-origin requests that require preflight.
+> Request requires preflight, which is disallowed to follow cross-origin redirect.
 
 The CORS protocol originally required that behavior but [was subsequently changed to no longer require it](https://github.com/whatwg/fetch/commit/0d9a4db8bc02251cc9e391543bb3c1322fb882f2). However, not all browsers have implemented the change, and so still exhibit the behavior that was originally required.
 
@@ -288,33 +299,35 @@ Line 7 shows the flag on {{domxref("XMLHttpRequest")}} that has to be set in ord
 
 Here is a sample exchange between client and server:
 
-    GET /resources/credentialed-content/ HTTP/1.1
-    Host: bar.other
-    User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:71.0) Gecko/20100101 Firefox/71.0
-    Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
-    Accept-Language: en-us,en;q=0.5
-    Accept-Encoding: gzip,deflate
-    Connection: keep-alive
-    Referer: https://foo.example/examples/credential.html
-    Origin: https://foo.example
-    Cookie: pageAccess=2
-
-    HTTP/1.1 200 OK
-    Date: Mon, 01 Dec 2008 01:34:52 GMT
-    Server: Apache/2
-    Access-Control-Allow-Origin: https://foo.example
-    Access-Control-Allow-Credentials: true
-    Cache-Control: no-cache
-    Pragma: no-cache
-    Set-Cookie: pageAccess=3; expires=Wed, 31-Dec-2008 01:34:53 GMT
-    Vary: Accept-Encoding, Origin
-    Content-Encoding: gzip
-    Content-Length: 106
-    Keep-Alive: timeout=2, max=100
-    Connection: Keep-Alive
-    Content-Type: text/plain
-
-    [text/plain payload]
+```plain
+GET /resources/credentialed-content/ HTTP/1.1
+Host: bar.other
+User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:71.0) Gecko/20100101 Firefox/71.0
+Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
+Accept-Language: en-us,en;q=0.5
+Accept-Encoding: gzip,deflate
+Connection: keep-alive
+Referer: https://foo.example/examples/credential.html
+Origin: https://foo.example
+Cookie: pageAccess=2
+
+HTTP/1.1 200 OK
+Date: Mon, 01 Dec 2008 01:34:52 GMT
+Server: Apache/2
+Access-Control-Allow-Origin: https://foo.example
+Access-Control-Allow-Credentials: true
+Cache-Control: no-cache
+Pragma: no-cache
+Set-Cookie: pageAccess=3; expires=Wed, 31-Dec-2008 01:34:53 GMT
+Vary: Accept-Encoding, Origin
+Content-Encoding: gzip
+Content-Length: 106
+Keep-Alive: timeout=2, max=100
+Connection: Keep-Alive
+Content-Type: text/plain
+
+[text/plain payload]
+```
 
 Although line 10 contains the Cookie destined for the content on `https://bar.other`, if bar.other did not respond with an {{HTTPHeader("Access-Control-Allow-Credentials")}}`: true` (line 17) the response would be ignored and not made available to web content.
 
@@ -350,14 +363,18 @@ This section lists the HTTP response headers that servers send back for access c
 
 A returned resource may have one {{HTTPHeader("Access-Control-Allow-Origin")}} header, with the following syntax:
 
-    Access-Control-Allow-Origin: <origin> | *
+```
+Access-Control-Allow-Origin: <origin> | *
+```
 
 `Access-Control-Allow-Origin` specifies either a single origin, which tells browsers to allow that origin to access the resource; or else — for requests **without** credentials — the "`*`" wildcard, to tell browsers to allow any origin to access the resource.
 
 For example, to allow code from the origin `https://mozilla.org` to access the resource, you can specify:
 
-    Access-Control-Allow-Origin: https://mozilla.org
-    Vary: Origin
+```
+Access-Control-Allow-Origin: https://mozilla.org
+Vary: Origin
+```
 
 If the server specifies a single origin (that may dynamically change based on the requesting origin as part of a allowlist) rather than the "`*`" wildcard, then the server should also include `Origin` in the {{HTTPHeader("Vary")}} response header — to indicate to clients that server responses will differ based on the value of the {{HTTPHeader("Origin")}} request header.
 
@@ -365,19 +382,24 @@ If the server specifies a single origin (that may dynamically change based on th
 
 The {{HTTPHeader("Access-Control-Expose-Headers")}} header adds the specified headers to the allowlist that JavaScript (such as {{domxref("XMLHttpRequest.getResponseHeader()","getResponseHeader()")}}) in browsers is allowed to access.
 
-    Access-Control-Expose-Headers: <header-name>[, <header-name>]*
+```
+Access-Control-Expose-Headers: <header-name>[, <header-name>]*
+```
 
 For example, the following:
 
-    Access-Control-Expose-Headers: X-My-Custom-Header, X-Another-Custom-Header
+```
+Access-Control-Expose-Headers: X-My-Custom-Header, X-Another-Custom-Header
+```
 
 …would allow the `X-My-Custom-Header` and `X-Another-Custom-Header` headers to be exposed to the browser.
 
 ### Access-Control-Max-Age
 
 The {{HTTPHeader("Access-Control-Max-Age")}} header indicates how long the results of a preflight request can be cached. For an example of a preflight request, see the above examples.
-
-    Access-Control-Max-Age: <delta-seconds>
+```
+Access-Control-Max-Age: <delta-seconds>
+```
 
 The `delta-seconds` parameter indicates the number of seconds the results can be cached.
 
@@ -385,7 +407,9 @@ The `delta-seconds` parameter indicates the number of seconds the results can be
 
 The {{HTTPHeader("Access-Control-Allow-Credentials")}} header indicates whether or not the response to the request can be exposed when the `credentials` flag is true. When used as part of a response to a preflight request, this indicates whether or not the actual request can be made using credentials. Note that simple `GET` requests are not preflighted, and so if a request is made for a resource with credentials, if this header is not returned with the resource, the response is ignored by the browser and not returned to web content.
 
-    Access-Control-Allow-Credentials: true
+```
+Access-Control-Allow-Credentials: true
+```
 
 [Credentialed requests](#requests_with_credentials) are discussed above.
 
@@ -393,7 +417,9 @@ The {{HTTPHeader("Access-Control-Allow-Credentials")}} header indicates whether
 
 The {{HTTPHeader("Access-Control-Allow-Methods")}} header specifies the method or methods allowed when accessing the resource. This is used in response to a preflight request. The conditions under which a request is preflighted are discussed above.
 
-    Access-Control-Allow-Methods: <method>[, <method>]*
+```
+Access-Control-Allow-Methods: <method>[, <method>]*
+```
 
 An example of a {{Glossary("preflight request")}} is given above, including an example which sends this header to the browser.
 
@@ -401,7 +427,9 @@ An example of a {{Glossary("preflight request")}} is given above, including an e
 
 The {{HTTPHeader("Access-Control-Allow-Headers")}} header is used in response to a {{Glossary("preflight request")}} to indicate which HTTP headers can be used when making the actual request. This header is the server side response to the browser's {{HTTPHeader("Access-Control-Request-Headers")}} header.
 
-    Access-Control-Allow-Headers: <header-name>[, <header-name>]*
+```
+Access-Control-Allow-Headers: <header-name>[, <header-name>]*
+```
 
 ## The HTTP request headers
 
@@ -411,7 +439,9 @@ This section lists headers that clients may use when issuing HTTP requests in or
 
 The {{HTTPHeader("Origin")}} header indicates the origin of the cross-site access request or preflight request.
 
-    Origin: <origin>
+```
+Origin: <origin>
+```
 
 The origin is a URL indicating the server from which the request initiated. It does not include any path information, but only the server name.
 
@@ -423,7 +453,9 @@ Note that in any access control request, the {{HTTPHeader("Origin")}} header is
 
 The {{HTTPHeader("Access-Control-Request-Method")}} is used when issuing a preflight request to let the server know what HTTP method will be used when the actual request is made.
 
-    Access-Control-Request-Method: <method>
+```
+Access-Control-Request-Method: <method>
+```
 
 Examples of this usage can be [found above.](#preflighted_requests)
 
@@ -431,7 +463,9 @@ Examples of this usage can be [found above.](#preflighted_requests)
 
 The {{HTTPHeader("Access-Control-Request-Headers")}} header is used when issuing a preflight request to let the server know what HTTP headers will be used when the actual request is made (such as with {{domxref("XMLHttpRequest.setRequestHeader()","setRequestHeader()")}}). This browser side header will be answered by the complementary server side header of {{HTTPHeader("Access-Control-Allow-Headers")}}.
 
-    Access-Control-Request-Headers: <field-name>[, <field-name>]*
+```
+Access-Control-Request-Headers: <field-name>[, <field-name>]*
+```
 
 Examples of this usage can be [found above](#preflighted_requests).
 
diff --git a/files/en-us/web/http/cross-origin_resource_policy_(corp)/index.md b/files/en-us/web/http/cross-origin_resource_policy_(corp)/index.md
index 4cc3f1d8d0fcda7..6a36f1437eed145 100644
--- a/files/en-us/web/http/cross-origin_resource_policy_(corp)/index.md
+++ b/files/en-us/web/http/cross-origin_resource_policy_(corp)/index.md
@@ -43,9 +43,9 @@ Web applications set a Cross-Origin Resource Policy via the {{HTTPHeader("Cross-
 - `cross-origin`
   - : Requests from any _{{Glossary("origin")}}_ (both same-site and cross-site) can read the resource.
 
-<!---->
-
-    Cross-Origin-Resource-Policy: same-site | same-origin | cross-origin
+```
+Cross-Origin-Resource-Policy: same-site | same-origin | cross-origin
+```
 
 During a cross-origin resource policy check, if the header is set, the browser will deny `no-cors` requests issued from a different origin/site.
 
diff --git a/files/en-us/web/http/csp/index.md b/files/en-us/web/http/csp/index.md
index bd71a9859ddefb7..b7faf5300ac4483 100644
--- a/files/en-us/web/http/csp/index.md
+++ b/files/en-us/web/http/csp/index.md
@@ -11,19 +11,17 @@ tags:
 ---
 {{HTTPSidebar}}
 
-**Content Security Policy** ({{Glossary("CSP")}}) is an
-added layer of security that helps to detect and mitigate certain types of attacks,
-including Cross Site Scripting ({{Glossary("Cross-site_scripting", "XSS")}}) and data injection attacks. These
-attacks are used for everything from data theft to site defacement to distribution of
-malware.
+**Content Security Policy** ({{Glossary("CSP")}}) is an added layer of security
+that helps to detect and mitigate certain types of attacks,
+including Cross Site Scripting ({{Glossary("Cross-site_scripting", "XSS")}}) and data injection attacks.
+These attacks are used for everything from data theft to site defacement to distribution of malware.
 
 CSP is designed to be fully backward compatible (except CSP version 2 where there are
 some explicitly-mentioned inconsistencies in backward compatibility; more details [here](https://www.w3.org/TR/CSP2) section 1.1). Browsers that don't support
 it still work with servers that implement it, and vice-versa: browsers that don't
 support CSP ignore it, functioning as usual, defaulting to the standard same-origin
 policy for web content. If the site doesn't offer the CSP header, browsers likewise use
-the standard [same-origin
-policy](/en-US/docs/Web/Security/Same-origin_policy).
+the standard [same-origin policy](/en-US/docs/Web/Security/Same-origin_policy).
 
 To enable CSP, you need to configure your web server to return the
 {{HTTPHeader("Content-Security-Policy")}} HTTP header. (Sometimes you may see mentions
@@ -32,7 +30,11 @@ you don't need to specify it anymore.)
 
 Alternatively, the {{HTMLElement("meta")}} element can be used to configure a policy,
 for example:
-`<meta http-equiv="Content-Security-Policy" content="default-src 'self'; img-src https://*; child-src 'none';">`
+
+```html
+<meta http-equiv="Content-Security-Policy"
+      content="default-src 'self'; img-src https://*; child-src 'none';">
+```
 
 ## Threats
 
@@ -79,7 +81,7 @@ construct such headers properly, and provides examples.
 You can use the {{HTTPHeader("Content-Security-Policy")}} HTTP header to specify your
 policy, like this:
 
-```html
+```
 Content-Security-Policy: policy
 ```
 
@@ -110,7 +112,7 @@ This section provides examples of some common security policy scenarios.
 A web site administrator wants all content to come from the site's own origin (this
 excludes subdomains.)
 
-```html
+```
 Content-Security-Policy: default-src 'self'
 ```
 
@@ -119,7 +121,7 @@ Content-Security-Policy: default-src 'self'
 A web site administrator wants to allow content from a trusted domain and all its
 subdomains (it doesn't have to be the same domain that the CSP is set on.)
 
-```html
+```
 Content-Security-Policy: default-src 'self' trusted.com *.trusted.com
 ```
 
@@ -129,7 +131,7 @@ A web site administrator wants to allow users of a web application to include im
 from any origin in their own content, but to restrict audio or video media to trusted
 providers, and all scripts only to a specific server that hosts trusted code.
 
-```html
+```
 Content-Security-Policy: default-src 'self'; img-src *; media-src media1.com media2.com; script-src userscripts.example.com
 ```
 
@@ -147,7 +149,7 @@ A web site administrator for an online banking site wants to ensure that all its
 content is loaded using TLS, in order to prevent attackers from eavesdropping on
 requests.
 
-```html
+```
 Content-Security-Policy: default-src https://onlinebanking.jumbobank.com
 ```
 
@@ -159,7 +161,7 @@ through the single origin onlinebanking.jumbobank.com.
 A web site administrator of a web mail site wants to allow HTML in email, as well as
 images loaded from anywhere, but not JavaScript or other potentially dangerous content.
 
-```html
+```
 Content-Security-Policy: default-src 'self' *.mailsite.com; img-src *
 ```
 
@@ -176,8 +178,8 @@ header can be used to test a future revision to a policy without actually deploy
 You can use the {{HTTPHeader("Content-Security-Policy-Report-Only")}} HTTP header to
 specify your policy, like this:
 
-```html
-Content-Security-Policy-Report-Only: policy 
+```
+Content-Security-Policy-Report-Only: policy
 ```
 
 If both a {{HTTPHeader("Content-Security-Policy-Report-Only")}} header and a
@@ -192,7 +194,7 @@ By default, violation reports aren't sent. To enable violation reporting, you ne
 specify the {{CSP("report-uri")}} policy directive, providing at least one URI to which
 to deliver the reports:
 
-```html
+```
 Content-Security-Policy: default-src 'self'; report-uri http://reportcollector.example.com/collector.cgi
 ```
 
@@ -235,7 +237,7 @@ Let's consider a page located at `http://example.com/signup.html`. It uses
 the following policy, disallowing everything but stylesheets from
 `cdn.example.com`.
 
-```html
+```
 Content-Security-Policy: default-src 'none'; style-src cdn.example.com; report-uri /_/csp-reports
 ```
 
@@ -260,15 +262,17 @@ Can you spot the mistake? Stylesheets are allowed to be loaded only from
 following violation report as a POST request to
 `http://example.com/_/csp-reports`, when the document is visited:
 
-    {
-      "csp-report": {
-        "document-uri": "http://example.com/signup.html",
-        "referrer": "",
-        "blocked-uri": "http://example.com/css/style.css",
-        "violated-directive": "style-src cdn.example.com",
-        "original-policy": "default-src 'none'; style-src cdn.example.com; report-uri /_/csp-reports"
-      }
-    }
+```js
+{
+  "csp-report": {
+    "document-uri": "http://example.com/signup.html",
+    "referrer": "",
+    "blocked-uri": "http://example.com/css/style.css",
+    "violated-directive": "style-src cdn.example.com",
+    "original-policy": "default-src 'none'; style-src cdn.example.com; report-uri /_/csp-reports"
+  }
+}
+```
 
 As you can see, the report includes the full path to the violating resource in
 `blocked-uri`. This is not always the case. For example, if the
diff --git a/files/en-us/web/http/headers/accept-ch-lifetime/index.md b/files/en-us/web/http/headers/accept-ch-lifetime/index.md
index 82eb46c587d33d0..8a4926ee0467170 100644
--- a/files/en-us/web/http/headers/accept-ch-lifetime/index.md
+++ b/files/en-us/web/http/headers/accept-ch-lifetime/index.md
@@ -45,14 +45,16 @@ include in subsequent requests.
 
 ## Syntax
 
-```html
+```
 Accept-CH-Lifetime: <age>
 ```
 
 ## Examples
 
-    Accept-CH: Viewport-Width
-    Accept-CH-Lifetime: 86400
+```
+Accept-CH: Viewport-Width
+Accept-CH-Lifetime: 86400
+```
 
 ## Browser compatibility
 
diff --git a/files/en-us/web/http/headers/accept-encoding/index.md b/files/en-us/web/http/headers/accept-encoding/index.md
index 4c8b4d155a9efe1..c3c0e57980f4874 100644
--- a/files/en-us/web/http/headers/accept-encoding/index.md
+++ b/files/en-us/web/http/headers/accept-encoding/index.md
@@ -40,7 +40,7 @@ As long as the `identity` value, meaning no encoding, is not explicitly forbidde
 
 ## Syntax
 
-```html
+```
 Accept-Encoding: gzip
 Accept-Encoding: compress
 Accept-Encoding: deflate
@@ -71,11 +71,13 @@ Accept-Encoding: deflate, gzip;q=1.0, *;q=0.5
 
 ## Examples
 
-    Accept-Encoding: gzip
+```
+Accept-Encoding: gzip
 
-    Accept-Encoding: gzip, compress, br
+Accept-Encoding: gzip, compress, br
 
-    Accept-Encoding: br;q=1.0, gzip;q=0.8, *;q=0.1
+Accept-Encoding: br;q=1.0, gzip;q=0.8, *;q=0.1
+```
 
 ## Specifications
 
diff --git a/files/en-us/web/http/headers/accept-patch/index.md b/files/en-us/web/http/headers/accept-patch/index.md
index 231e2a0eac7a14f..4a59f44b91b8266 100644
--- a/files/en-us/web/http/headers/accept-patch/index.md
+++ b/files/en-us/web/http/headers/accept-patch/index.md
@@ -33,7 +33,7 @@ A server receiving a PATCH request with an unsupported media type could reply wi
 
 ## Syntax
 
-```html
+```
 Accept-Patch: application/example, text/example
 Accept-Patch: text/example;charset=utf-8
 Accept-Patch: application/merge-patch+json
@@ -45,7 +45,7 @@ None
 
 ## Examples
 
-```html
+```
 Accept-Patch: application/example, text/example
 
 Accept-Patch: text/example;charset=utf-8
diff --git a/files/en-us/web/http/headers/accept-post/index.md b/files/en-us/web/http/headers/accept-post/index.md
index ab7eb00b85c7c7f..bddbff43e555456 100644
--- a/files/en-us/web/http/headers/accept-post/index.md
+++ b/files/en-us/web/http/headers/accept-post/index.md
@@ -32,9 +32,11 @@ For example, a server receiving a `POST` request with an unsupported media type
 
 ## Syntax
 
-    Accept: <MIME_type>/<MIME_subtype>
-    Accept: <MIME_type>/*
-    Accept: */*
+```
+Accept: <MIME_type>/<MIME_subtype>
+Accept: <MIME_type>/*
+Accept: */*
+```
 
 > **Note:** The `Accept-Post` header specifies a media range in the same way as {{HTTPHeader("Accept-Language")}}, except that it has no notion of preference (i.e. "accept-params" or "q" arguments are not significant).
 
@@ -44,7 +46,7 @@ None.
 
 ## Examples
 
-```html
+```
 Accept-Post: application/example, text/example
 Accept-Post: image/webp
 Accept-Post: */*
diff --git a/files/en-us/web/http/headers/accept-ranges/index.md b/files/en-us/web/http/headers/accept-ranges/index.md
index 4e61fe856ca3b8a..4c6783422b0a6d6 100644
--- a/files/en-us/web/http/headers/accept-ranges/index.md
+++ b/files/en-us/web/http/headers/accept-ranges/index.md
@@ -33,7 +33,7 @@ _resume_ an interrupted download, rather than to start it from the start again.
 
 ## Syntax
 
-```html
+```
 Accept-Ranges: <range-unit>
 Accept-Ranges: none
 ```
@@ -52,7 +52,9 @@ Accept-Ranges: none
 
 ## Examples
 
-    Accept-Ranges: bytes
+```
+Accept-Ranges: bytes
+```
 
 ## Specifications
 
diff --git a/files/en-us/web/http/headers/accept/index.md b/files/en-us/web/http/headers/accept/index.md
index 19f5acdacd42dcc..3763506a078202d 100644
--- a/files/en-us/web/http/headers/accept/index.md
+++ b/files/en-us/web/http/headers/accept/index.md
@@ -37,7 +37,7 @@ The **`Accept`** request HTTP header advertises which content types, expressed a
 
 ## Syntax
 
-```html
+```
 Accept: <MIME_type>/<MIME_subtype>
 Accept: <MIME_type>/*
 Accept: */*
@@ -59,15 +59,17 @@ Accept: text/html, application/xhtml+xml, application/xml;q=0.9, image/webp, */*
 
 ## Examples
 
-    Accept: text/html
+```
+Accept: text/html
 
-    Accept: image/*
+Accept: image/*
 
-    // General default
-    Accept: */*
+// General default
+Accept: */*
 
-    // Default for navigation requests
-    Accept: text/html, application/xhtml+xml, application/xml;q=0.9, */*;q=0.8
+// Default for navigation requests
+Accept: text/html, application/xhtml+xml, application/xml;q=0.9, */*;q=0.8
+```
 
 ## Specifications
 
diff --git a/files/en-us/web/http/headers/access-control-allow-credentials/index.md b/files/en-us/web/http/headers/access-control-allow-credentials/index.md
index 1674480ddd7f6ec..a2c560bbf5b9d5c 100644
--- a/files/en-us/web/http/headers/access-control-allow-credentials/index.md
+++ b/files/en-us/web/http/headers/access-control-allow-credentials/index.md
@@ -52,7 +52,7 @@ in to including credentials.
 
 ## Syntax
 
-```html
+```
 Access-Control-Allow-Credentials: true
 ```
 
@@ -67,7 +67,9 @@ Access-Control-Allow-Credentials: true
 
 Allow credentials:
 
-    Access-Control-Allow-Credentials: true
+```
+Access-Control-Allow-Credentials: true
+```
 
 Using [XHR](/en-US/docs/Web/API/XMLHttpRequest) with credentials:
 
diff --git a/files/en-us/web/http/headers/access-control-allow-headers/index.md b/files/en-us/web/http/headers/access-control-allow-headers/index.md
index 31c0a912a1b86a8..af8b0984014d91c 100644
--- a/files/en-us/web/http/headers/access-control-allow-headers/index.md
+++ b/files/en-us/web/http/headers/access-control-allow-headers/index.md
@@ -32,7 +32,7 @@ This header is required if the request has an {{HTTPHeader("Access-Control-Reque
 
 ## Syntax
 
-```html
+```
 Access-Control-Allow-Headers: [<header-name>[, <header-name>]*]
 Access-Control-Allow-Headers: *
 ```
@@ -50,19 +50,25 @@ Access-Control-Allow-Headers: *
 
 Here's an example of what an `Access-Control-Allow-Headers` header might look like. It indicates that a custom header named `X-Custom-Header` is supported by CORS requests to the server (in addition to the {{glossary("CORS-safelisted_request_header", "CORS-safelisted request headers")}}).
 
-    Access-Control-Allow-Headers: X-Custom-Header
+```
+Access-Control-Allow-Headers: X-Custom-Header
+```
 
 ### Multiple headers
 
 This example shows `Access-Control-Allow-Headers` when it specifies support for multiple headers.
 
-    Access-Control-Allow-Headers: X-Custom-Header, Upgrade-Insecure-Requests
+```
+Access-Control-Allow-Headers: X-Custom-Header, Upgrade-Insecure-Requests
+```
 
 ### Bypassing additional restrictions
 
 Although {{glossary("CORS-safelisted_request_header", "CORS-safelisted request headers")}} are always allowed and don't usually need to be listed in `Access-Control-Allow-Headers`, listing them anyway will circumvent the [additional restrictions](/en-US/docs/Glossary/CORS-safelisted_request_header#additional_restrictions) that apply.
 
-    Access-Control-Allow-Headers: Accept
+```
+Access-Control-Allow-Headers: Accept
+```
 
 ### Example preflight request
 
@@ -74,22 +80,26 @@ First, the request. The preflight request is an {{HTTPMethod("OPTIONS")}} reque
 
 The preflight request below tells the server that we want to send a CORS `GET` request that has the headers listed in {{HTTPHeader("Access-Control-Request-Headers")}} ({{HTTPHeader("Content-Type")}} and `x-requested-with`).
 
-    OPTIONS /resource/foo
-    Access-Control-Request-Method: GET
-    Access-Control-Request-Headers: Content-Type, x-requested-with
-    Origin: https://foo.bar.org
+```
+OPTIONS /resource/foo
+Access-Control-Request-Method: GET
+Access-Control-Request-Headers: Content-Type, x-requested-with
+Origin: https://foo.bar.org
+```
 
 #### Response
 
 If the CORS request indicated by the preflight request is authorized, the server will respond to the preflight request with a message that indicates the allowed origin, methods and headers. Below we see that {{HTTPHeader("Access-Control-Allow-Headers")}} includes the headers that were requested.
 
-    HTTP/1.1 200 OK
-    Content-Length: 0
-    Connection: keep-alive
-    Access-Control-Allow-Origin: https://foo.bar.org
-    Access-Control-Allow-Methods: POST, GET, OPTIONS, DELETE
-    Access-Control-Allow-Headers: Content-Type, x-requested-with
-    Access-Control-Max-Age: 86400
+```
+HTTP/1.1 200 OK
+Content-Length: 0
+Connection: keep-alive
+Access-Control-Allow-Origin: https://foo.bar.org
+Access-Control-Allow-Methods: POST, GET, OPTIONS, DELETE
+Access-Control-Allow-Headers: Content-Type, x-requested-with
+Access-Control-Max-Age: 86400
+```
 
 If the requested method isn't supported, the server will respond with an error.
 
diff --git a/files/en-us/web/http/headers/access-control-allow-methods/index.md b/files/en-us/web/http/headers/access-control-allow-methods/index.md
index c7f620205f77ff8..c5a672583fa29e7 100644
--- a/files/en-us/web/http/headers/access-control-allow-methods/index.md
+++ b/files/en-us/web/http/headers/access-control-allow-methods/index.md
@@ -29,7 +29,7 @@ specifies the method or methods allowed when accessing the resource in response
 
 ## Syntax
 
-```html
+```
 Access-Control-Allow-Methods: <method>, <method>, ...
 Access-Control-Allow-Methods: *
 ```
@@ -47,8 +47,10 @@ Access-Control-Allow-Methods: *
 
 ## Examples
 
-    Access-Control-Allow-Methods: POST, GET, OPTIONS
-    Access-Control-Allow-Methods: *
+```
+Access-Control-Allow-Methods: POST, GET, OPTIONS
+Access-Control-Allow-Methods: *
+```
 
 ## Specifications
 
diff --git a/files/en-us/web/http/headers/access-control-allow-origin/index.md b/files/en-us/web/http/headers/access-control-allow-origin/index.md
index ad74641282489a9..b8be1ebd97548b1 100644
--- a/files/en-us/web/http/headers/access-control-allow-origin/index.md
+++ b/files/en-us/web/http/headers/access-control-allow-origin/index.md
@@ -35,7 +35,7 @@ The **`Access-Control-Allow-Origin`** response header indicates whether the resp
 
 ## Syntax
 
-```html
+```
 Access-Control-Allow-Origin: *
 Access-Control-Allow-Origin: <origin>
 Access-Control-Allow-Origin: null
@@ -57,11 +57,15 @@ Access-Control-Allow-Origin: null
 
 A response that tells the browser to allow code from any origin to access a resource will include the following:
 
-    Access-Control-Allow-Origin: *
+```
+Access-Control-Allow-Origin: *
+```
 
 A response that tells the browser to allow requesting code from the origin `https://developer.mozilla.org` to access a resource will include the following:
 
-    Access-Control-Allow-Origin: https://developer.mozilla.org
+```
+Access-Control-Allow-Origin: https://developer.mozilla.org
+```
 
 Limiting the possible `Access-Control-Allow-Origin` values to a set of allowed origins requires code on the server side to check the value of the {{HTTPHeader("Origin")}} request header, compare that to a list of allowed origins, and then if the {{HTTPHeader("Origin")}} value is in the list, to set the `Access-Control-Allow-Origin` value to the same value as the {{HTTPHeader("Origin")}} value.
 
@@ -69,8 +73,10 @@ Limiting the possible `Access-Control-Allow-Origin` values to a set of allowed o
 
 If the server sends a response with an `Access-Control-Allow-Origin` value that is an explicit origin (rather than the "`*`" wildcard), then the response should also include a {{HTTPHeader("Vary")}} response header with the value `Origin` — to indicate to browsers that server responses can differ based on the value of the `Origin` request header.
 
-    Access-Control-Allow-Origin: https://developer.mozilla.org
-    Vary: Origin
+```
+Access-Control-Allow-Origin: https://developer.mozilla.org
+Vary: Origin
+```
 
 ## Specifications
 
diff --git a/files/en-us/web/http/headers/access-control-expose-headers/index.md b/files/en-us/web/http/headers/access-control-expose-headers/index.md
index b722dab1b290075..ae459064af19e4b 100644
--- a/files/en-us/web/http/headers/access-control-expose-headers/index.md
+++ b/files/en-us/web/http/headers/access-control-expose-headers/index.md
@@ -29,7 +29,7 @@ Only the {{Glossary("CORS-safelisted response header", "CORS-safelisted response
 
 ## Syntax
 
-```html
+```
 Access-Control-Expose-Headers: [<header-name>[, <header-name>]*]
 Access-Control-Expose-Headers: *
 ```
@@ -46,19 +46,27 @@ Access-Control-Expose-Headers: *
 
 The {{Glossary("CORS-safelisted response header", "CORS-safelisted response headers")}} are: {{HTTPHeader("Cache-Control")}}, {{HTTPHeader("Content-Language")}}, {{HTTPHeader("Content-Length")}}, {{HTTPHeader("Content-Type")}}, {{HTTPHeader("Expires")}}, {{HTTPHeader("Last-Modified")}}, {{HTTPHeader("Pragma")}}. To expose a non-CORS-safelisted response header, you can specify:
 
-    Access-Control-Expose-Headers: Content-Encoding
+```
+Access-Control-Expose-Headers: Content-Encoding
+```
 
 To additionally expose a custom header, like `X-Kuma-Revision`, you can specify multiple headers separated by a comma:
 
-    Access-Control-Expose-Headers: Content-Encoding, X-Kuma-Revision
+```
+Access-Control-Expose-Headers: Content-Encoding, X-Kuma-Revision
+```
 
 For requests without credentials, a server can also respond with a wildcard value:
 
-    Access-Control-Expose-Headers: *
+```
+Access-Control-Expose-Headers: *
+```
 
 However, this won't wildcard the {{HTTPHeader("Authorization")}} header, so if you need to expose that, you will need to list it explicitly:
 
-    Access-Control-Expose-Headers: *, Authorization
+```
+Access-Control-Expose-Headers: *, Authorization
+```
 
 ## Specifications
 
diff --git a/files/en-us/web/http/headers/access-control-max-age/index.md b/files/en-us/web/http/headers/access-control-max-age/index.md
index 041652984632041..9e1c427edfbe490 100644
--- a/files/en-us/web/http/headers/access-control-max-age/index.md
+++ b/files/en-us/web/http/headers/access-control-max-age/index.md
@@ -27,7 +27,7 @@ The **`Access-Control-Max-Age`** response header indicates how long the results
 
 ## Syntax
 
-```html
+```
 Access-Control-Max-Age: <delta-seconds>
 ```
 
@@ -45,7 +45,9 @@ Access-Control-Max-Age: <delta-seconds>
 
 Cache results of a preflight request for 10 minutes:
 
-    Access-Control-Max-Age: 600
+```
+Access-Control-Max-Age: 600
+```
 
 ## Specifications
 
diff --git a/files/en-us/web/http/headers/access-control-request-headers/index.md b/files/en-us/web/http/headers/access-control-request-headers/index.md
index 3ab9dfc53b559d0..cdcbe833f6c990b 100644
--- a/files/en-us/web/http/headers/access-control-request-headers/index.md
+++ b/files/en-us/web/http/headers/access-control-request-headers/index.md
@@ -27,7 +27,7 @@ The **`Access-Control-Request-Headers`** request header is used by browsers when
 
 ## Syntax
 
-```html
+```
 Access-Control-Request-Headers: <header-name>, <header-name>, ...
 ```
 
@@ -38,7 +38,9 @@ Access-Control-Request-Headers: <header-name>, <header-name>, ...
 
 ## Examples
 
-    Access-Control-Request-Headers: X-PINGOTHER, Content-Type
+```
+Access-Control-Request-Headers: X-PINGOTHER, Content-Type
+```
 
 ## Specifications
 
diff --git a/files/en-us/web/http/headers/access-control-request-method/index.md b/files/en-us/web/http/headers/access-control-request-method/index.md
index 2d7d92ed54bb51a..1845ddfbfff65c3 100644
--- a/files/en-us/web/http/headers/access-control-request-method/index.md
+++ b/files/en-us/web/http/headers/access-control-request-method/index.md
@@ -31,7 +31,7 @@ actual request is made. This header is necessary as the preflight request is alw
 
 ## Syntax
 
-```html
+```
 Access-Control-Request-Method: <method>
 ```
 
@@ -43,7 +43,9 @@ Access-Control-Request-Method: <method>
 
 ## Examples
 
-    Access-Control-Request-Method: POST
+```
+Access-Control-Request-Method: POST
+```
 
 ## Specifications
 
diff --git a/files/en-us/web/http/headers/age/index.md b/files/en-us/web/http/headers/age/index.md
index ea16135e240f7f3..089384009560f72 100644
--- a/files/en-us/web/http/headers/age/index.md
+++ b/files/en-us/web/http/headers/age/index.md
@@ -33,7 +33,7 @@ header included in the HTTP response.
 
 ## Syntax
 
-```html
+```
 Age: <delta-seconds>
 ```
 
@@ -45,7 +45,9 @@ Age: <delta-seconds>
 
 ## Examples
 
-    Age: 24
+```
+Age: 24
+```
 
 ## Specifications
 
diff --git a/files/en-us/web/http/headers/allow/index.md b/files/en-us/web/http/headers/allow/index.md
index f52086fa2a4057e..f0ce64e269832da 100644
--- a/files/en-us/web/http/headers/allow/index.md
+++ b/files/en-us/web/http/headers/allow/index.md
@@ -28,7 +28,7 @@ This header must be sent if the server responds with a {{HTTPStatus("405")}} `Me
 
 ## Syntax
 
-```html
+```
 Allow: <http-methods>
 ```
 
@@ -39,7 +39,9 @@ Allow: <http-methods>
 
 ## Examples
 
-    Allow: GET, POST, HEAD
+```
+Allow: GET, POST, HEAD
+```
 
 ## Specifications
 
diff --git a/files/en-us/web/http/headers/alt-svc/index.md b/files/en-us/web/http/headers/alt-svc/index.md
index 8d0ca5313bb0543..392ef532f3ca0fa 100644
--- a/files/en-us/web/http/headers/alt-svc/index.md
+++ b/files/en-us/web/http/headers/alt-svc/index.md
@@ -14,7 +14,7 @@ The {{HTTPHeader("Alt-Svc")}} HTTP header allows a server to indicate that a par
 
 ## Syntax
 
-```html
+```
 Alt-Svc: clear
 Alt-Svc: <protocol-id>=<alt-authority>; ma=<max-age>
 Alt-Svc: <protocol-id>=<alt-authority>; ma=<max-age>; persist=1
@@ -45,10 +45,12 @@ as separator. In that case, early entries are considered more preferable.
 
 ## Example
 
-    Alt-Svc: h2=":443"; ma=2592000;
-    Alt-Svc: h2=":443"; ma=2592000; persist=1
-    Alt-Svc: h2="alt.example.com:443", h2=":443"
-    Alt-Svc: h3-25=":443"; ma=3600, h2=":443"; ma=3600
+```
+Alt-Svc: h2=":443"; ma=2592000;
+Alt-Svc: h2=":443"; ma=2592000; persist=1
+Alt-Svc: h2="alt.example.com:443", h2=":443"
+Alt-Svc: h3-25=":443"; ma=3600, h2=":443"; ma=3600
+```
 
 ## Specifications
 
diff --git a/files/en-us/web/http/headers/authorization/index.md b/files/en-us/web/http/headers/authorization/index.md
index dc8cb2850ce23b9..4beb6605db8be01 100644
--- a/files/en-us/web/http/headers/authorization/index.md
+++ b/files/en-us/web/http/headers/authorization/index.md
@@ -30,7 +30,7 @@ necessarily, after the server has responded with a {{HTTPStatus("401")}}
 
 ## Syntax
 
-```html
+```
 Authorization: <type> <credentials>
 ```
 
@@ -60,7 +60,9 @@ Authorization: <type> <credentials>
 
 ## Examples
 
-    Authorization: Basic YWxhZGRpbjpvcGVuc2VzYW1l
+```
+Authorization: Basic YWxhZGRpbjpvcGVuc2VzYW1l
+```
 
 See also [HTTP authentication](/en-US/docs/Web/HTTP/Authentication) for
 examples on how to configure Apache or nginx servers to password protect your site with
diff --git a/files/en-us/web/http/headers/cache-control/index.md b/files/en-us/web/http/headers/cache-control/index.md
index 45b6f8f155d3cfe..b616d47a568f04e 100644
--- a/files/en-us/web/http/headers/cache-control/index.md
+++ b/files/en-us/web/http/headers/cache-control/index.md
@@ -48,35 +48,41 @@ Caching directives have the following rules to be valid:
 
 Standard `Cache-Control` directives that can be used by the client in an HTTP request.
 
-    Cache-Control: max-age=<seconds>
-    Cache-Control: max-stale[=<seconds>]
-    Cache-Control: min-fresh=<seconds>
-    Cache-Control: no-cache
-    Cache-Control: no-store
-    Cache-Control: no-transform
-    Cache-Control: only-if-cached
+```
+Cache-Control: max-age=<seconds>
+Cache-Control: max-stale[=<seconds>]
+Cache-Control: min-fresh=<seconds>
+Cache-Control: no-cache
+Cache-Control: no-store
+Cache-Control: no-transform
+Cache-Control: only-if-cached
+```
 
 ### Cache response directives
 
 Standard `Cache-Control` directives that can be used by the server in an HTTP response.
 
-    Cache-Control: must-revalidate
-    Cache-Control: no-cache
-    Cache-Control: no-store
-    Cache-Control: no-transform
-    Cache-Control: public
-    Cache-Control: private
-    Cache-Control: proxy-revalidate
-    Cache-Control: max-age=<seconds>
-    Cache-Control: s-maxage=<seconds>
+```
+Cache-Control: must-revalidate
+Cache-Control: no-cache
+Cache-Control: no-store
+Cache-Control: no-transform
+Cache-Control: public
+Cache-Control: private
+Cache-Control: proxy-revalidate
+Cache-Control: max-age=<seconds>
+Cache-Control: s-maxage=<seconds>
+```
 
 ### Extension Cache-Control directives
 
 Extension `Cache-Control` directives are not part of the core HTTP caching standards document. Check the [compatibility table](#browser_compatibility) for their support; user-agents that don't recognize them should ignore them.
 
-    Cache-Control: immutable
-    Cache-Control: stale-while-revalidate=<seconds>
-    Cache-Control: stale-if-error=<seconds>
+```
+Cache-Control: immutable
+Cache-Control: stale-while-revalidate=<seconds>
+Cache-Control: stale-if-error=<seconds>
+```
 
 ## Directives
 
@@ -138,7 +144,7 @@ Cache-Control: no-store
 > but it will not prevent the cache from responding with a non-stale resource that was cached as the result of an earlier request.
 > Setting `max-age=0` as well forces the cache to revalidate (clears the cache).
 >
->     Cache-Control: no-store, max-age=0
+> `Cache-Control: no-store, max-age=0`
 
 On the opposite, this is a bad way to achieve this:
 
@@ -150,22 +156,26 @@ Cache-Control: private,no-cache,no-store,max-age=0,must-revalidate,pre-check=0,p
 
 For the files in the application that will not change, you can usually add aggressive caching by sending the response header below. This includes static files that are served by the application such as images, CSS files and JavaScript files, for example. In addition, see also the `Expires` header.
 
-    Cache-Control: public, max-age=604800, immutable
+```
+Cache-Control: public, max-age=604800, immutable
+```
 
 ### Requiring revalidation
 
-`no-cache` and `max-age=0, must-revalidate` indicates same meaning.
+`no-cache` and `max-age=0, must-revalidate` have the same meaning.
 Clients can cache a resource but must revalidate each time before using it. This means HTTP request occurs each time though, it can skip downloading HTTP body if the content is valid.
 
-    Cache-Control: no-cache
-
-<!---->
+```
+Cache-Control: no-cache
 
-    Cache-Control: max-age=0, must-revalidate
+Cache-Control: max-age=0, must-revalidate
+```
 
-**Note**: Following may serve stale resource if server is down or lose connectivity.
+**Note**: The following header may serve a stale resource, if server is down or loses connectivity.
 
-    Cache-Control: max-age=0
+```
+Cache-Control: max-age=0
+```
 
 ## Specifications
 
diff --git a/files/en-us/web/http/headers/clear-site-data/index.md b/files/en-us/web/http/headers/clear-site-data/index.md
index 30315bf5c1560e9..42ae0b2ee837247 100644
--- a/files/en-us/web/http/headers/clear-site-data/index.md
+++ b/files/en-us/web/http/headers/clear-site-data/index.md
@@ -30,14 +30,16 @@ The **`Clear-Site-Data`** header clears browsing data (cookies, storage, cache)
 
 The `Clear-Site-Data` header accepts one or more directives. If all types of data should be cleared, the wildcard directive (`"*"`) can be used.
 
-    // Single directive
-    Clear-Site-Data: "cache"
+```
+// Single directive
+Clear-Site-Data: "cache"
 
-    // Multiple directives (comma separated)
-    Clear-Site-Data: "cache", "cookies"
+// Multiple directives (comma separated)
+Clear-Site-Data: "cache", "cookies"
 
-    // Wild card
-    Clear-Site-Data: "*"
+// Wild card
+Clear-Site-Data: "*"
+```
 
 ## Directives
 
@@ -71,13 +73,17 @@ The `Clear-Site-Data` header accepts one or more directives. If all types of dat
 
 If a user signs out of your website or service, you might want to remove locally stored data. You can achieve that by adding the `Clear-Site-Data` header when sending the page confirming that logging out from the site has been accomplished successfully (https\://example.com/logout, for example):
 
-    Clear-Site-Data: "cache", "cookies", "storage", "executionContexts"
+```
+Clear-Site-Data: "cache", "cookies", "storage", "executionContexts"
+```
 
 ### Clearing cookies
 
 If this header is delivered with the response at https\://example.com/clear-cookies, all cookies on the same domain https\://example.com and any subdomains (like https\://stage.example.com, etc), will be cleared out.
 
-    Clear-Site-Data: "cookies"
+```
+Clear-Site-Data: "cookies"
+```
 
 ## Specifications
 
diff --git a/files/en-us/web/http/headers/connection/index.md b/files/en-us/web/http/headers/connection/index.md
index 55ab377bf1e4017..71d73bb375f3324 100644
--- a/files/en-us/web/http/headers/connection/index.md
+++ b/files/en-us/web/http/headers/connection/index.md
@@ -49,7 +49,7 @@ further. Standard hop-by-hop headers are also required to be listed.
 
 ## Syntax
 
-```html
+```
 Connection: keep-alive
 Connection: close
 ```
diff --git a/files/en-us/web/http/headers/content-disposition/index.md b/files/en-us/web/http/headers/content-disposition/index.md
index 713f0513f95bf84..310229c54391526 100644
--- a/files/en-us/web/http/headers/content-disposition/index.md
+++ b/files/en-us/web/http/headers/content-disposition/index.md
@@ -40,7 +40,7 @@ The `Content-Disposition` header is defined in the larger context of MIME messag
 
 The first parameter in the HTTP context is either `inline` (default value, indicating it can be displayed inside the Web page, or as the Web page) or `attachment` (indicating it should be downloaded; most browsers presenting a 'Save as' dialog, prefilled with the value of the `filename` parameters if present).
 
-```html
+```
 Content-Disposition: inline
 Content-Disposition: attachment
 Content-Disposition: attachment; filename="filename.jpg"
@@ -52,7 +52,7 @@ Content-Disposition: attachment; filename="filename.jpg"
 
 A `multipart/form-data` body requires a `Content-Disposition` header to provide information for each subpart of the form (e.g. for every form field and any files that are part of field data). The first directive is always `form-data`, and the header _must_ also include a `name` parameter to identify the relevant field. Additional directives are case-insensitive and have arguments that use quoted-string syntax after the `'='` sign. Multiple parameters are separated by a semi-colon (`';'`).
 
-```html
+```
 Content-Disposition: form-data; name="fieldName"
 Content-Disposition: form-data; name="fieldName"; filename="filename.jpg"
 ```
@@ -83,30 +83,34 @@ Content-Disposition: form-data; name="fieldName"; filename="filename.jpg"
 
 A response triggering the "Save As" dialog:
 
-    200 OK
-    Content-Type: text/html; charset=utf-8
-    Content-Disposition: attachment; filename="cool.html"
-    Content-Length: 21
+```
+200 OK
+Content-Type: text/html; charset=utf-8
+Content-Disposition: attachment; filename="cool.html"
+Content-Length: 21
 
-    <HTML>Save me!</HTML>
+<HTML>Save me!</HTML>
+```
 
 This simple HTML file will be saved as a regular download rather than displayed in the browser. Most browsers will propose to save it under the `cool.html` filename (by default).
 
 An example of an HTML form posted using the `multipart/form-data` format that makes use of the `Content-Disposition` header:
 
-    POST /test.html HTTP/1.1
-    Host: example.org
-    Content-Type: multipart/form-data;boundary="boundary"
+```
+POST /test.html HTTP/1.1
+Host: example.org
+Content-Type: multipart/form-data;boundary="boundary"
 
-    --boundary
-    Content-Disposition: form-data; name="field1"
+--boundary
+Content-Disposition: form-data; name="field1"
 
-    value1
-    --boundary
-    Content-Disposition: form-data; name="field2"; filename="example.txt"
+value1
+--boundary
+Content-Disposition: form-data; name="field2"; filename="example.txt"
 
-    value2
-    --boundary--
+value2
+--boundary--
+```
 
 ## Specifications
 
diff --git a/files/en-us/web/http/headers/content-dpr/index.md b/files/en-us/web/http/headers/content-dpr/index.md
index d4a1e01ffa410fb..5d340d0bfdfc202 100644
--- a/files/en-us/web/http/headers/content-dpr/index.md
+++ b/files/en-us/web/http/headers/content-dpr/index.md
@@ -48,7 +48,9 @@ If the `Content-DPR` header appears more than once in a message the last occurre
 
 ## Syntax
 
-    Content-DPR: <number>
+```
+Content-DPR: <number>
+```
 
 ## Directives
 
diff --git a/files/en-us/web/http/headers/content-encoding/index.md b/files/en-us/web/http/headers/content-encoding/index.md
index a8b9ec635abdc5b..d7bb35293b2685c 100644
--- a/files/en-us/web/http/headers/content-encoding/index.md
+++ b/files/en-us/web/http/headers/content-encoding/index.md
@@ -32,7 +32,7 @@ Servers are encouraged to compress data as much as possible, and should use cont
 
 ## Syntax
 
-```html
+```
 Content-Encoding: gzip
 Content-Encoding: compress
 Content-Encoding: deflate
@@ -72,12 +72,16 @@ On the client side, you can advertise a list of compression schemes that will be
 along in an HTTP request. The {{HTTPHeader("Accept-Encoding")}} header is used for
 negotiating content encoding.
 
-    Accept-Encoding: gzip, deflate
+```
+Accept-Encoding: gzip, deflate
+```
 
 The server responds with the scheme used, indicated by the
 `Content-Encoding` response header.
 
-    Content-Encoding: gzip
+```
+Content-Encoding: gzip
+```
 
 Note that the server is not obligated to use any compression method. Compression highly
 depends on server settings and used server modules.
diff --git a/files/en-us/web/http/headers/content-language/index.md b/files/en-us/web/http/headers/content-language/index.md
index b0adb5c3a172f3c..4d2193b2d3eb2d5 100644
--- a/files/en-us/web/http/headers/content-language/index.md
+++ b/files/en-us/web/http/headers/content-language/index.md
@@ -46,7 +46,7 @@ If no `Content-Language` is specified, the default is that the content is intend
 
 ## Syntax
 
-```html
+```
 Content-Language: de-DE
 Content-Language: en-US
 Content-Language: de-DE, en-CA
@@ -80,7 +80,9 @@ Do **not** use this meta element like this for stating a document language:
 
 The `Content-Language` header is used to specify the **intended audience of the page**, and can indicate that this is more than one language.
 
-    Content-Language: de, en
+```
+Content-Language: de, en
+```
 
 ## Specifications
 
diff --git a/files/en-us/web/http/headers/content-length/index.md b/files/en-us/web/http/headers/content-length/index.md
index af0cc616e46b80f..b7b3212bb02c012 100644
--- a/files/en-us/web/http/headers/content-length/index.md
+++ b/files/en-us/web/http/headers/content-length/index.md
@@ -40,7 +40,7 @@ The **`Content-Length`** header indicates the size of the message body, in byte
 
 ## Syntax
 
-```html
+```
 Content-Length: <length>
 ```
 
diff --git a/files/en-us/web/http/headers/content-location/index.md b/files/en-us/web/http/headers/content-location/index.md
index 979e1e5958a653f..f283585802081e8 100644
--- a/files/en-us/web/http/headers/content-location/index.md
+++ b/files/en-us/web/http/headers/content-location/index.md
@@ -36,7 +36,7 @@ data returned. This distinction may seem abstract without [examples](#examples).
 
 ## Syntax
 
-```html
+```
 Content-Location: <url>
 ```
 
@@ -78,22 +78,26 @@ as {{HTTPHeader("Accept-Language")}}.
 
 Say you're creating a new blog post through a site's API:
 
-    PUT /new/post
-    Host: example.com
-    Content-Type: text/markdown
+```
+PUT /new/post
+Host: example.com
+Content-Type: text/markdown
 
-    # My first blog post!
+# My first blog post!
 
-    I made this through `example.com`'s API. I hope it worked.
+I made this through `example.com`'s API. I hope it worked.
+```
 
 The site returns a generic success message confirming the post was published. The
 server specifies _where_ the new post is with `Content-Location`:
 
-    HTTP/1.1 201 Created
-    Content-Type: text/plain; charset=utf-8
-    Content-Location: /my-first-blog-post
+```
+HTTP/1.1 201 Created
+Content-Type: text/plain; charset=utf-8
+Content-Location: /my-first-blog-post
 
-    ✅ Success!
+✅ Success!
+```
 
 ### Indicating the URL of a transaction's result
 
@@ -123,16 +127,18 @@ When the form is submitted, the site generates a receipt for the transaction. Th
 server could use `Content-Location` to indicate that receipt's URL for future
 access.
 
-    HTTP/1.1 200 OK
-    Content-Type: text/html; charset=utf-8
-    Content-Location: /my-receipts/38
+```
+HTTP/1.1 200 OK
+Content-Type: text/html; charset=utf-8
+Content-Location: /my-receipts/38
 
-    <!doctype html>
-    (Lots of HTML…)
+<!doctype html>
+(Lots of HTML…)
 
-    <p>You sent $38.00 to ExampleUser.</p>
+<p>You sent $38.00 to ExampleUser.</p>
 
-    (Lots more HTML…)
+(Lots more HTML…)
+```
 
 ## Specifications
 
diff --git a/files/en-us/web/http/headers/content-range/index.md b/files/en-us/web/http/headers/content-range/index.md
index 38df63077b12218..cce1417cb6d00d8 100644
--- a/files/en-us/web/http/headers/content-range/index.md
+++ b/files/en-us/web/http/headers/content-range/index.md
@@ -40,7 +40,7 @@ a full body message a partial message belongs.
 
 ## Syntax
 
-```html
+```
 Content-Range: <unit> <range-start>-<range-end>/<size>
 Content-Range: <unit> <range-start>-<range-end>/*
 Content-Range: <unit> */<size>
@@ -59,7 +59,9 @@ Content-Range: <unit> */<size>
 
 ## Examples
 
-    Content-Range: bytes 200-1000/67589
+```
+Content-Range: bytes 200-1000/67589
+```
 
 ## Specifications
 
diff --git a/files/en-us/web/http/headers/content-security-policy-report-only/index.md b/files/en-us/web/http/headers/content-security-policy-report-only/index.md
index e96c37fca7ef1db..d78e844effa6369 100644
--- a/files/en-us/web/http/headers/content-security-policy-report-only/index.md
+++ b/files/en-us/web/http/headers/content-security-policy-report-only/index.md
@@ -37,7 +37,7 @@ For more information, see also this article on [Content Security Policy (CSP)](/
 
 ## Syntax
 
-```html
+```
 Content-Security-Policy-Report-Only: <policy-directive>; <policy-directive>
 ```
 
@@ -51,11 +51,15 @@ The CSP {{CSP("report-uri")}} directive should be used with this header, otherwi
 
 This header reports violations that would have occurred. You can use this to iteratively work on your content security policy. You observe how your site behaves, watching for violation reports, or [malware redirects](https://secure.wphackedhelp.com/blog/wordpress-malware-redirect-hack-cleanup/), then choose the desired policy enforced by the {{HTTPHeader("Content-Security-Policy")}} header.
 
-    Content-Security-Policy-Report-Only: default-src https:; report-uri /csp-violation-report-endpoint/
+```
+Content-Security-Policy-Report-Only: default-src https:; report-uri /csp-violation-report-endpoint/
+```
 
 If you still want to receive reporting, but also want to enforce a policy, use the {{HTTPHeader("Content-Security-Policy")}} header with the {{CSP("report-uri")}} directive.
 
-    Content-Security-Policy: default-src https:; report-uri /csp-violation-report-endpoint/
+```
+Content-Security-Policy: default-src https:; report-uri /csp-violation-report-endpoint/
+```
 
 ## Violation report syntax
 
@@ -84,7 +88,9 @@ The report JSON object contains the following data:
 
 Let's consider a page located at `http://example.com/signup.html`. It uses the following policy, disallowing everything but stylesheets from `cdn.example.com`.
 
-    Content-Security-Policy-Report-Only: default-src 'none'; style-src cdn.example.com; report-uri /_/csp-reports
+```
+Content-Security-Policy-Report-Only: default-src 'none'; style-src cdn.example.com; report-uri /_/csp-reports
+```
 
 The HTML of `signup.html` looks like this:
 
diff --git a/files/en-us/web/http/headers/content-security-policy/base-uri/index.md b/files/en-us/web/http/headers/content-security-policy/base-uri/index.md
index 7f1b5806a46e46e..c7b83f6fb8cd392 100644
--- a/files/en-us/web/http/headers/content-security-policy/base-uri/index.md
+++ b/files/en-us/web/http/headers/content-security-policy/base-uri/index.md
@@ -34,7 +34,7 @@ The HTTP {{HTTPHeader("Content-Security-Policy")}} **`base-uri`** directive rest
 
 One or more*sources* can be allowed for the base-uri policy:
 
-```html
+```
 Content-Security-Policy: base-uri <source>;
 Content-Security-Policy: base-uri <source> <source>;
 ```
@@ -55,7 +55,7 @@ While this directive uses the same arguments as other CSP directives, some of th
 
 ### Apache configuration
 
-```bash
+```html
 <IfModule mod_headers.c>
 Header set Content-Security-Policy "base-uri 'self'";
 </IfModule>
@@ -63,7 +63,7 @@ Header set Content-Security-Policy "base-uri 'self'";
 
 ### Nginx configuration
 
-```bash
+```
 add_header Content-Security-Policy "base-uri 'self';"
 ```
 
diff --git a/files/en-us/web/http/headers/content-security-policy/block-all-mixed-content/index.md b/files/en-us/web/http/headers/content-security-policy/block-all-mixed-content/index.md
index 5b206e397857637..c7a2e33768ce4cc 100644
--- a/files/en-us/web/http/headers/content-security-policy/block-all-mixed-content/index.md
+++ b/files/en-us/web/http/headers/content-security-policy/block-all-mixed-content/index.md
@@ -22,19 +22,23 @@ All [mixed content](/en-US/docs/Web/Security/Mixed_content) resource requests ar
 
 ## Syntax
 
-```html
+```
 Content-Security-Policy: block-all-mixed-content;
 ```
 
 ## Examples
 
-    Content-Security-Policy: block-all-mixed-content;
+```
+Content-Security-Policy: block-all-mixed-content;
 
-    <meta http-equiv="Content-Security-Policy" content="block-all-mixed-content">
+<meta http-equiv="Content-Security-Policy" content="block-all-mixed-content">
+```
 
 To disallow http assets on a more granular level, you can also set individual directives to `https:`. For example, to disallow nonsecure HTTP images:
 
-    Content-Security-Policy: img-src https:
+```
+Content-Security-Policy: img-src https:
+```
 
 ## Specifications
 
diff --git a/files/en-us/web/http/headers/content-security-policy/child-src/index.md b/files/en-us/web/http/headers/content-security-policy/child-src/index.md
index 9e4ae7e06964d3f..30531d6d114e00c 100644
--- a/files/en-us/web/http/headers/content-security-policy/child-src/index.md
+++ b/files/en-us/web/http/headers/content-security-policy/child-src/index.md
@@ -45,7 +45,7 @@ network errors by the user agent.
 
 One or more sources can be allowed for the child-src policy:
 
-```html
+```
 Content-Security-Policy: child-src <source>;
 Content-Security-Policy: child-src <source> <source>;
 ```
@@ -60,7 +60,7 @@ Content-Security-Policy: child-src <source> <source>;
 
 Given this CSP header:
 
-```bash
+```
 Content-Security-Policy: child-src https://example.com/
 ```
 
diff --git a/files/en-us/web/http/headers/content-security-policy/connect-src/index.md b/files/en-us/web/http/headers/content-security-policy/connect-src/index.md
index 73d70aee977242d..02b57dc48d2f06c 100644
--- a/files/en-us/web/http/headers/content-security-policy/connect-src/index.md
+++ b/files/en-us/web/http/headers/content-security-policy/connect-src/index.md
@@ -52,7 +52,7 @@ loaded using script interfaces. The APIs that are restricted are:
 
 One or more sources can be allowed for the connect-src policy:
 
-```html
+```
 Content-Security-Policy: connect-src <source>;
 Content-Security-Policy: connect-src <source> <source>;
 ```
@@ -68,7 +68,7 @@ Content-Security-Policy: connect-src <source> <source>;
 
 Given this CSP header:
 
-```bash
+```
 Content-Security-Policy: connect-src https://example.com/
 ```
 
diff --git a/files/en-us/web/http/headers/content-security-policy/default-src/index.md b/files/en-us/web/http/headers/content-security-policy/default-src/index.md
index 5fe31de924def41..71b31cf105aa8f3 100644
--- a/files/en-us/web/http/headers/content-security-policy/default-src/index.md
+++ b/files/en-us/web/http/headers/content-security-policy/default-src/index.md
@@ -51,7 +51,7 @@ The HTTP {{HTTPHeader("Content-Security-Policy")}} (CSP) **`default-src`** direc
 
 One or more sources can be allowed for the `default-src` policy:
 
-```html
+```
 Content-Security-Policy: default-src <source>;
 Content-Security-Policy: default-src <source> <source>;
 ```
@@ -108,13 +108,13 @@ Content-Security-Policy: default-src <source> <source>;
 
 If there are other directives specified, `default-src` does not influence them. The following header:
 
-```bash
+```
 Content-Security-Policy: default-src 'self'; script-src https://example.com
 ```
 
 is the same as:
 
-```bash
+```
 Content-Security-Policy: connect-src 'self';
                          font-src 'self';
                          frame-src 'self';
diff --git a/files/en-us/web/http/headers/content-security-policy/font-src/index.md b/files/en-us/web/http/headers/content-security-policy/font-src/index.md
index ab7eb11fc2ba71c..22d4ac020085b4f 100644
--- a/files/en-us/web/http/headers/content-security-policy/font-src/index.md
+++ b/files/en-us/web/http/headers/content-security-policy/font-src/index.md
@@ -42,7 +42,7 @@ valid sources for fonts loaded using {{cssxref("@font-face")}}.
 
 One or more sources can be allowed for the `font-src` policy:
 
-```html
+```
 Content-Security-Policy: font-src <source>;
 Content-Security-Policy: font-src <source> <source>;
 ```
@@ -57,7 +57,7 @@ Content-Security-Policy: font-src <source> <source>;
 
 Given this CSP header:
 
-```bash
+```
 Content-Security-Policy: font-src https://example.com/
 ```
 
diff --git a/files/en-us/web/http/headers/content-security-policy/form-action/index.md b/files/en-us/web/http/headers/content-security-policy/form-action/index.md
index 19bbddc89b204f2..20f85dcfbbf2ac5 100644
--- a/files/en-us/web/http/headers/content-security-policy/form-action/index.md
+++ b/files/en-us/web/http/headers/content-security-policy/form-action/index.md
@@ -39,7 +39,7 @@ The HTTP {{HTTPHeader("Content-Security-Policy")}} (CSP) **`form`\*\***`-action`
 
 One or more sources can be set for the `form-action` policy:
 
-```html
+```
 Content-Security-Policy: form-action <source>;
 Content-Security-Policy: form-action <source> <source>;
 ```
@@ -58,7 +58,7 @@ Content-Security-Policy: form-action <source> <source>;
 
 ### Apache configuration
 
-```bash
+```html
 <IfModule mod_headers.c>
 Header set Content-Security-Policy "form-action 'none';"
 </IfModule>
@@ -66,7 +66,7 @@ Header set Content-Security-Policy "form-action 'none';"
 
 ### Nginx configuration
 
-```bash
+```
 add_header Content-Security-Policy "form-action 'none';"
 ```
 
diff --git a/files/en-us/web/http/headers/content-security-policy/frame-ancestors/index.md b/files/en-us/web/http/headers/content-security-policy/frame-ancestors/index.md
index 643ac0e0d907234..80cdcd86d07e6ac 100644
--- a/files/en-us/web/http/headers/content-security-policy/frame-ancestors/index.md
+++ b/files/en-us/web/http/headers/content-security-policy/frame-ancestors/index.md
@@ -45,7 +45,7 @@ Setting this directive to `'none'` is similar to {{HTTPHeader("X-Frame-Options")
 
 One or more sources can be set for the `frame-ancestors` policy:
 
-```html
+```
 Content-Security-Policy: frame-ancestors <source>;
 Content-Security-Policy: frame-ancestors <source> <source>;
 ```
@@ -83,7 +83,7 @@ Content-Security-Policy: frame-ancestors <source> <source>;
 
 ## Examples
 
-```bash
+```
 Content-Security-Policy: frame-ancestors 'none';
 
 Content-Security-Policy: frame-ancestors 'self' https://www.example.org;
diff --git a/files/en-us/web/http/headers/content-security-policy/frame-src/index.md b/files/en-us/web/http/headers/content-security-policy/frame-src/index.md
index befed4c47ed3301..bcbf328c3120cf2 100644
--- a/files/en-us/web/http/headers/content-security-policy/frame-src/index.md
+++ b/files/en-us/web/http/headers/content-security-policy/frame-src/index.md
@@ -45,7 +45,7 @@ browsing contexts loading using elements such as {{HTMLElement("frame")}} and
 
 One or more sources can be allowed for the `frame-src` policy:
 
-```html
+```
 Content-Security-Policy: frame-src <source>;
 Content-Security-Policy: frame-src <source> <source>;
 ```
@@ -60,7 +60,7 @@ Content-Security-Policy: frame-src <source> <source>;
 
 Given this CSP header:
 
-```bash
+```
 Content-Security-Policy: frame-src https://example.com/
 ```
 
diff --git a/files/en-us/web/http/headers/content-security-policy/img-src/index.md b/files/en-us/web/http/headers/content-security-policy/img-src/index.md
index 2507f4c0accc6ba..acdbd8f59ac4466 100644
--- a/files/en-us/web/http/headers/content-security-policy/img-src/index.md
+++ b/files/en-us/web/http/headers/content-security-policy/img-src/index.md
@@ -43,7 +43,7 @@ favicons.
 
 One or more sources can be allowed for the `img-src` policy:
 
-```html
+```
 Content-Security-Policy: img-src <source>;
 Content-Security-Policy: img-src <source> <source>;
 ```
@@ -58,7 +58,7 @@ Content-Security-Policy: img-src <source> <source>;
 
 Given this CSP header:
 
-```bash
+```
 Content-Security-Policy: img-src https://example.com/
 ```
 
diff --git a/files/en-us/web/http/headers/content-security-policy/index.md b/files/en-us/web/http/headers/content-security-policy/index.md
index e4f2489cd2a5f96..45306cf7b4ae17e 100644
--- a/files/en-us/web/http/headers/content-security-policy/index.md
+++ b/files/en-us/web/http/headers/content-security-policy/index.md
@@ -35,7 +35,7 @@ For more information, see the introductory article on [Content Security Policy (
 
 ## Syntax
 
-```html
+```
 Content-Security-Policy: <policy-directive>; <policy-directive>
 ```
 
@@ -256,31 +256,43 @@ restrict_ the capabilities of the protected resource, which means that there wil
 be no connection allowed and, as the strictest policy, `connect-src 'none'`
 is enforced.
 
-    Content-Security-Policy: default-src 'self' http://example.com;
-                             connect-src 'none';
-    Content-Security-Policy: connect-src http://example.com/;
-                             script-src http://example.com/
+```
+Content-Security-Policy: default-src 'self' http://example.com;
+                          connect-src 'none';
+Content-Security-Policy: connect-src http://example.com/;
+                          script-src http://example.com/
+```
 
 ## Examples
 
 Example: Disable unsafe inline/eval, only allow loading of resources (images, fonts,
 scripts, etc.) over https:
 
-    // header
-    Content-Security-Policy: default-src https:
+### Using the HTTP header
 
-    // meta tag
-    <meta http-equiv="Content-Security-Policy" content="default-src https:">
+```
+Content-Security-Policy: default-src https:
+```
+
+### Using the HTML meta element
+
+```
+<meta http-equiv="Content-Security-Policy" content="default-src https:">
+```
 
 Example: Pre-existing site that uses too much inline code to fix but wants to ensure
 resources are loaded only over HTTPS and to disable plugins:
 
-    Content-Security-Policy: default-src https: 'unsafe-eval' 'unsafe-inline'; object-src 'none'
+```
+Content-Security-Policy: default-src https: 'unsafe-eval' 'unsafe-inline'; object-src 'none'
+```
 
 Example: Do not implement the above policy yet; instead just report violations that
 would have occurred:
 
-    Content-Security-Policy-Report-Only: default-src https:; report-uri /csp-violation-report-endpoint/
+```
+Content-Security-Policy-Report-Only: default-src https:; report-uri /csp-violation-report-endpoint/
+```
 
 See [Mozilla
 Web Security Guidelines](https://infosec.mozilla.org/guidelines/web_security#Examples_5) for more examples.
@@ -297,9 +309,7 @@ Web Security Guidelines](https://infosec.mozilla.org/guidelines/web_security#Exa
 
 - {{HTTPHeader("Content-Security-Policy-Report-Only")}}
 - [Learn about: Content Security Policy](/en-US/docs/Web/HTTP/CSP)
-- [Content
-  Security in WebExtensions](/en-US/docs/Mozilla/Add-ons/WebExtensions/Content_Security_Policy)
-- [Adopting a strict
-  policy](https://csp.withgoogle.com/docs/strict-csp.html)
+- [Content Security in WebExtensions](/en-US/docs/Mozilla/Add-ons/WebExtensions/Content_Security_Policy)
+- [Adopting a strict policy](https://csp.withgoogle.com/docs/strict-csp.html)
 - [CSP Evaluator](https://github.com/google/csp-evaluator) - Evaluate your
   Content Security Policy
diff --git a/files/en-us/web/http/headers/content-security-policy/manifest-src/index.md b/files/en-us/web/http/headers/content-security-policy/manifest-src/index.md
index ec83d757718b069..202fe39d49fcbc7 100644
--- a/files/en-us/web/http/headers/content-security-policy/manifest-src/index.md
+++ b/files/en-us/web/http/headers/content-security-policy/manifest-src/index.md
@@ -44,7 +44,7 @@ to the resource.
 
 One or more sources can be allowed for the `manifest-src` policy:
 
-```html
+```
 Content-Security-Policy: manifest-src <source>;
 Content-Security-Policy: manifest-src <source> <source>;
 ```
@@ -59,7 +59,7 @@ Content-Security-Policy: manifest-src <source> <source>;
 
 Given this CSP header:
 
-```bash
+```
 Content-Security-Policy: manifest-src https://example.com/
 ```
 
diff --git a/files/en-us/web/http/headers/content-security-policy/media-src/index.md b/files/en-us/web/http/headers/content-security-policy/media-src/index.md
index 32f61a51db97c24..66c7050616f612a 100644
--- a/files/en-us/web/http/headers/content-security-policy/media-src/index.md
+++ b/files/en-us/web/http/headers/content-security-policy/media-src/index.md
@@ -43,7 +43,7 @@ media using the {{HTMLElement("audio")}} and {{HTMLElement("video")}} elements.
 
 One or more sources can be allowed for the `media-src` policy:
 
-```html
+```
 Content-Security-Policy: media-src <source>;
 Content-Security-Policy: media-src <source> <source>;
 ```
@@ -58,7 +58,7 @@ Content-Security-Policy: media-src <source> <source>;
 
 Given this CSP header:
 
-```bash
+```
 Content-Security-Policy: media-src https://example.com/
 ```
 
diff --git a/files/en-us/web/http/headers/content-security-policy/navigate-to/index.md b/files/en-us/web/http/headers/content-security-policy/navigate-to/index.md
index 004d3b4c26abda3..22d2649973f9166 100644
--- a/files/en-us/web/http/headers/content-security-policy/navigate-to/index.md
+++ b/files/en-us/web/http/headers/content-security-policy/navigate-to/index.md
@@ -46,7 +46,7 @@ on what this document is allowed to navigate to.
 
 One or more sources can be set for the `navigate-to` policy:
 
-```html
+```
 Content-Security-Policy: navigate-to <source>;
 Content-Security-Policy: navigate-to <source> <source>;
 ```
diff --git a/files/en-us/web/http/headers/content-security-policy/object-src/index.md b/files/en-us/web/http/headers/content-security-policy/object-src/index.md
index 3336fcfe5bce12a..1baf4c43a6cd847 100644
--- a/files/en-us/web/http/headers/content-security-policy/object-src/index.md
+++ b/files/en-us/web/http/headers/content-security-policy/object-src/index.md
@@ -53,7 +53,7 @@ To set allowed types for {{HTMLElement("object")}}, {{HTMLElement("embed")}}, an
 
 One or more sources can be allowed for the object-src policy:
 
-```html
+```
 Content-Security-Policy: object-src <source>;
 Content-Security-Policy: object-src <source> <source>;
 ```
@@ -68,7 +68,7 @@ Content-Security-Policy: object-src <source> <source>;
 
 Given this CSP header:
 
-```bash
+```
 Content-Security-Policy: object-src https://example.com/
 ```
 
diff --git a/files/en-us/web/http/headers/content-security-policy/plugin-types/index.md b/files/en-us/web/http/headers/content-security-policy/plugin-types/index.md
index 4d328ca785bc47f..ff368008a61aaca 100644
--- a/files/en-us/web/http/headers/content-security-policy/plugin-types/index.md
+++ b/files/en-us/web/http/headers/content-security-policy/plugin-types/index.md
@@ -49,7 +49,7 @@ Instantiation of an {{HTMLElement("embed")}}, {{HTMLElement("object")}} or
 One or more [MIME types](/en-US/docs/Web/HTTP/Basics_of_HTTP/MIME_types) can
 be set for the `plugin-types` policy:
 
-```html
+```
 Content-Security-Policy: plugin-types <type>/<subtype>;
 Content-Security-Policy: plugin-types <type>/<subtype> <type>/<subtype>;
 ```
@@ -74,7 +74,7 @@ is only used if you are allowing plugins with `object-src` at all.
 
 The content security policy
 
-```bash
+```
 Content-Security-Policy: plugin-types application/x-shockwave-flash
 ```
 
@@ -89,7 +89,7 @@ will allow to load flash objects:
 To load an {{HTMLElement("applet")}} you must specify
 `application/x-java-applet`:
 
-```bash
+```
 Content-Security-Policy: plugin-types application/x-java-applet
 ```
 
diff --git a/files/en-us/web/http/headers/content-security-policy/prefetch-src/index.md b/files/en-us/web/http/headers/content-security-policy/prefetch-src/index.md
index 169caec4f284457..0d25548269d99ba 100644
--- a/files/en-us/web/http/headers/content-security-policy/prefetch-src/index.md
+++ b/files/en-us/web/http/headers/content-security-policy/prefetch-src/index.md
@@ -40,7 +40,7 @@ be prefetched or prerendered.
 
 One or more sources can be allowed for the `prefetch-src` policy:
 
-```html
+```
 Content-Security-Policy: prefetch-src <source>;
 Content-Security-Policy: prefetch-src <source> <source>;
 ```
@@ -56,13 +56,17 @@ Content-Security-Policy: prefetch-src <source> <source>;
 
 Given a page with the following Content Security Policy:
 
-    Content-Security-Policy: prefetch-src https://example.com/
+```
+Content-Security-Policy: prefetch-src https://example.com/
+```
 
 Fetches for the following code will return network errors, as the URLs provided do not
 match `prefetch-src`'s source list:
 
+```html
     <link rel="prefetch" src="https://example.org/"></link>
     <link rel="prerender" src="https://example.org/"></link>
+```
 
 ## Specifications
 
diff --git a/files/en-us/web/http/headers/content-security-policy/referrer/index.md b/files/en-us/web/http/headers/content-security-policy/referrer/index.md
index 958d3f6c71c4c43..2324aeeaa2962b9 100644
--- a/files/en-us/web/http/headers/content-security-policy/referrer/index.md
+++ b/files/en-us/web/http/headers/content-security-policy/referrer/index.md
@@ -24,7 +24,7 @@ browsers.
 
 ## Syntax
 
-```html
+```
 Content-Security-Policy: referrer <referrer-policy>;
 ```
 
@@ -51,7 +51,9 @@ where `<referrer-policy>` can be one of the following values:
 
 ## Examples
 
-    Content-Security-Policy: referrer "none";
+```
+Content-Security-Policy: referrer "none";
+```
 
 ## Specifications
 
diff --git a/files/en-us/web/http/headers/content-security-policy/report-uri/index.md b/files/en-us/web/http/headers/content-security-policy/report-uri/index.md
index 2b24117da4d3891..f689788cd04de0a 100644
--- a/files/en-us/web/http/headers/content-security-policy/report-uri/index.md
+++ b/files/en-us/web/http/headers/content-security-policy/report-uri/index.md
@@ -53,7 +53,7 @@ with other directives.
 
 ## Syntax
 
-```html
+```
 Content-Security-Policy: report-uri <uri>;
 Content-Security-Policy: report-uri <uri> <uri>;
 ```
@@ -66,12 +66,15 @@ Content-Security-Policy: report-uri <uri> <uri>;
 See {{HTTPHeader("Content-Security-Policy-Report-Only")}} for more information and
 examples.
 
-    Content-Security-Policy: default-src https:; report-uri /csp-violation-report-endpoint/
+```
+Content-Security-Policy: default-src https:; report-uri /csp-violation-report-endpoint/
+```
 
 `/csp-violation-report-endpoint/` could for example run a PHP something like
 the following that logs the JSON detailing the violation and, if the violation is the
 first one added to the log file, sends an email to an administrator:
 
+```php
     <?php
 
     // Start configure
@@ -107,6 +110,7 @@ first one added to the log file, sends an email to an administrator:
 
       file_put_contents($log_file, $json_data, FILE_APPEND | LOCK_EX);
     }
+```
 
 ## Specifications
 
diff --git a/files/en-us/web/http/headers/content-security-policy/require-sri-for/index.md b/files/en-us/web/http/headers/content-security-policy/require-sri-for/index.md
index b2f66e5cee77b22..b1045e4f2a04f6f 100644
--- a/files/en-us/web/http/headers/content-security-policy/require-sri-for/index.md
+++ b/files/en-us/web/http/headers/content-security-policy/require-sri-for/index.md
@@ -20,7 +20,7 @@ Integrity](/en-US/docs/Web/Security/Subresource_Integrity) for scripts or styles
 
 ## Syntax
 
-```html
+```
 Content-Security-Policy: require-sri-for script;
 Content-Security-Policy: require-sri-for style;
 Content-Security-Policy: require-sri-for script style;
@@ -37,7 +37,9 @@ Content-Security-Policy: require-sri-for script style;
 
 If you set your site to require SRI for script and styles using this directive:
 
-    Content-Security-Policy: require-sri-for script style
+```
+Content-Security-Policy: require-sri-for script style
+```
 
 {{HTMLElement("script")}} elements like the following will be loaded as they use a
 valid integrity attribute.
diff --git a/files/en-us/web/http/headers/content-security-policy/require-trusted-types-for/index.md b/files/en-us/web/http/headers/content-security-policy/require-trusted-types-for/index.md
index e9cc53a5dfaa6a1..254f69a74c14489 100644
--- a/files/en-us/web/http/headers/content-security-policy/require-trusted-types-for/index.md
+++ b/files/en-us/web/http/headers/content-security-policy/require-trusted-types-for/index.md
@@ -16,7 +16,9 @@ When used, those functions only accept non-spoofable, typed values created by Tr
 
 ## Syntax
 
-    Content-Security-Policy: require-trusted-types-for 'script';
+```
+Content-Security-Policy: require-trusted-types-for 'script';
+````
 
 - `'script'`
   - : Disallows using strings with DOM XSS injection sink functions, and requires matching types created by Trusted Type policies.
@@ -30,14 +32,14 @@ const attackerInput = '<svg onload="alert(/cross-site-scripting/)" />';
 const el = document.createElement('div');
 
 if (typeof trustedTypes !== 'undefined') {
-  // Create a policy that can create TrustedHTML values
+  // Create a policy that can create TrustedHTML values
   // after sanitizing the input strings with DOMPurify library.
-  const sanitizer = trustedTypes.createPolicy('foo', {
-    createHTML: (input) => DOMPurify.sanitize(input)
-  });
+  const sanitizer = trustedTypes.createPolicy('foo', {
+    createHTML: (input) => DOMPurify.sanitize(input)
+  });
 
-  el.innerHTML = sanitizer.createHTML(attackerInput);  // Puts the sanitized value into the DOM.
-  el.innerHTML = attackerInput;                        // Rejects a string value; throws a TypeError.
+  el.innerHTML = sanitizer.createHTML(attackerInput);  // Puts the sanitized value into the DOM.
+  el.innerHTML = attackerInput;                        // Rejects a string value; throws a TypeError.
 }
 ```
 
diff --git a/files/en-us/web/http/headers/content-security-policy/sandbox/index.md b/files/en-us/web/http/headers/content-security-policy/sandbox/index.md
index e7a303e80ccfc1c..58313fe947e11f8 100644
--- a/files/en-us/web/http/headers/content-security-policy/sandbox/index.md
+++ b/files/en-us/web/http/headers/content-security-policy/sandbox/index.md
@@ -41,7 +41,7 @@ preventing the execution of plugins and scripts, and enforcing a same-origin pol
 
 ## Syntax
 
-```html
+```
 Content-Security-Policy: sandbox;
 Content-Security-Policy: sandbox <value>;
 ```
@@ -90,7 +90,7 @@ where `<value>` can optionally be one of the following values:
 
 ## Examples
 
-```bash
+```
 Content-Security-Policy: sandbox allow-scripts;
 ```
 
diff --git a/files/en-us/web/http/headers/content-security-policy/script-src-attr/index.md b/files/en-us/web/http/headers/content-security-policy/script-src-attr/index.md
index 3ef35bcf560703a..77bf32187701643 100644
--- a/files/en-us/web/http/headers/content-security-policy/script-src-attr/index.md
+++ b/files/en-us/web/http/headers/content-security-policy/script-src-attr/index.md
@@ -47,14 +47,14 @@ elements.
 
 One or more sources can be allowed for the `script-src-attr` policy:
 
-```html
+```
 Content-Security-Policy: script-src-attr <source>;
 Content-Security-Policy: script-src-attr <source> <source>;
 ```
 
 `script-src-attr` can be used in conjunction with {{CSP("script-src")}}:
 
-```html
+```
 Content-Security-Policy: script-src <source>;
 Content-Security-Policy: script-src-attr <source>;
 ```
diff --git a/files/en-us/web/http/headers/content-security-policy/script-src/index.md b/files/en-us/web/http/headers/content-security-policy/script-src/index.md
index 81c26a839a2f7d4..b0d82c0e8c4bef9 100644
--- a/files/en-us/web/http/headers/content-security-policy/script-src/index.md
+++ b/files/en-us/web/http/headers/content-security-policy/script-src/index.md
@@ -42,7 +42,7 @@ The HTTP {{HTTPHeader("Content-Security-Policy")}} (CSP) **`script-src`** direct
 
 One or more sources can be allowed for the `script-src` policy:
 
-```html
+```
 Content-Security-Policy: script-src <source>;
 Content-Security-Policy: script-src <source> <source>;
 ```
@@ -97,7 +97,9 @@ Content-Security-Policy: script-src <source> <source>;
 
 Given this CSP header:
 
-    Content-Security-Policy: script-src https://example.com/
+```
+Content-Security-Policy: script-src https://example.com/
+```
 
 the following script is blocked and won't be loaded or executed:
 
@@ -123,7 +125,9 @@ document.getElementById("btn").addEventListener('click', doSomething);
 
 To allow inline scripts and inline event handlers, `'unsafe-inline'`, a nonce-source or a hash-source that matches the inline block can be specified.
 
-    Content-Security-Policy: script-src 'unsafe-inline';
+```
+Content-Security-Policy: script-src 'unsafe-inline';
+```
 
 The above Content Security Policy will allow inline {{HTMLElement("script")}} elements
 
@@ -135,7 +139,9 @@ The above Content Security Policy will allow inline {{HTMLElement("script")}} el
 
 You can use a nonce-source to only allow specific inline script blocks:
 
-    Content-Security-Policy: script-src 'nonce-2726c7f26c'
+```
+Content-Security-Policy: script-src 'nonce-2726c7f26c'
+```
 
 You will have to set the same nonce on the {{HTMLElement("script")}} element:
 
@@ -147,7 +153,9 @@ You will have to set the same nonce on the {{HTMLElement("script")}} element:
 
 Alternatively, you can create hashes from your inline scripts. CSP supports sha256, sha384 and sha512.
 
-    Content-Security-Policy: script-src 'sha256-B2yPHKaXnvFWtRChIbabYmUBFZdVfKKXHbWtWidDVF8='
+```
+Content-Security-Policy: script-src 'sha256-B2yPHKaXnvFWtRChIbabYmUBFZdVfKKXHbWtWidDVF8='
+```
 
 When generating the hash, don't include the {{HTMLElement("script")}} tags and note that capitalization and whitespace matter, including leading or trailing whitespace.
 
@@ -173,16 +181,22 @@ The `'unsafe-eval'` source expression controls several script execution methods
 
 The `'strict-dynamic'` source expression specifies that the trust explicitly given to a script present in the markup, by accompanying it with a nonce or a hash, shall be propagated to all the scripts loaded by that root script. At the same time, any whitelist or source expressions such as `'self'` or `'unsafe-inline'` will be ignored. For example, a policy such as `script-src 'strict-dynamic' 'nonce-R4nd0m' https://whitelisted.com/` would allow loading of a root script with `<script nonce="R4nd0m" src="https://example.com/loader.js">` and propagate that trust to any script loaded by `loader.js`, but disallow loading scripts from `https://whitelisted.com/` unless accompanied by a nonce or loaded from a trusted script.
 
-    Content-Security-Policy: script-src 'strict-dynamic' 'nonce-someNonce'
+```
+Content-Security-Policy: script-src 'strict-dynamic' 'nonce-someNonce'
+```
 
 Or:
 
-    Content-Security-Policy: script-src 'strict-dynamic' 'sha256-base64EncodedHash'
+```
+Content-Security-Policy: script-src 'strict-dynamic' 'sha256-base64EncodedHash'
+```
 
 It is possible to deploy `strict-dynamic` in a backwards compatible way, without requiring user-agent sniffing.
 The policy:
 
-    Content-Security-Policy: script-src 'unsafe-inline' https: 'nonce-abcdefg' 'strict-dynamic'
+```
+Content-Security-Policy: script-src 'unsafe-inline' https: 'nonce-abcdefg' 'strict-dynamic'
+```
 
 will act like `'unsafe-inline' https:` in browsers that support CSP1, `https: 'nonce-abcdefg'` in browsers that support CSP2, and `'nonce-abcdefg' 'strict-dynamic'` in browsers that support CSP3.
 
diff --git a/files/en-us/web/http/headers/content-security-policy/style-src-attr/index.md b/files/en-us/web/http/headers/content-security-policy/style-src-attr/index.md
index 2a2a246fb93b27a..46b79719be4655b 100644
--- a/files/en-us/web/http/headers/content-security-policy/style-src-attr/index.md
+++ b/files/en-us/web/http/headers/content-security-policy/style-src-attr/index.md
@@ -48,15 +48,17 @@ specifies valid sources for inline styles applied to individual DOM elements.
 
 One or more sources can be allowed for the `style-src-attr` policy:
 
-```html
+```
 Content-Security-Policy: style-src-attr <source>;
 Content-Security-Policy: style-src-attr <source> <source>;
 ```
 
 `style-src-attr` can be used in conjunction with {{CSP("style-src")}}:
 
-    Content-Security-Policy: style-src <source>;
-    Content-Security-Policy: style-src-attr <source>;
+```
+Content-Security-Policy: style-src <source>;
+Content-Security-Policy: style-src-attr <source>;
+```
 
 ### Sources
 
diff --git a/files/en-us/web/http/headers/content-security-policy/style-src-elem/index.md b/files/en-us/web/http/headers/content-security-policy/style-src-elem/index.md
index c66392af4cc5e66..67b88dc739bb91d 100644
--- a/files/en-us/web/http/headers/content-security-policy/style-src-elem/index.md
+++ b/files/en-us/web/http/headers/content-security-policy/style-src-elem/index.md
@@ -49,7 +49,7 @@ specifies valid sources for stylesheets {{HTMLElement("style")}} elements and
 
 One or more sources can be allowed for the `style-src-elem` policy:
 
-```html
+```
 Content-Security-Policy: style-src-elem <source>;
 Content-Security-Policy: style-src-elem <source> <source>;
 ```
diff --git a/files/en-us/web/http/headers/content-security-policy/style-src/index.md b/files/en-us/web/http/headers/content-security-policy/style-src/index.md
index 5d97bc3ec9dec58..a9ba7a95daa78aa 100644
--- a/files/en-us/web/http/headers/content-security-policy/style-src/index.md
+++ b/files/en-us/web/http/headers/content-security-policy/style-src/index.md
@@ -42,7 +42,7 @@ The HTTP {{HTTPHeader("Content-Security-Policy")}} (CSP) **`style-src`** directi
 
 One or more sources can be allowed for the `style-src` policy:
 
-```html
+```
 Content-Security-Policy: style-src <source>;
 Content-Security-Policy: style-src <source> <source>;
 ```
@@ -57,7 +57,7 @@ Content-Security-Policy: style-src <source> <source>;
 
 Given this CSP header:
 
-```bash
+```
 Content-Security-Policy: style-src https://example.com/
 ```
 
@@ -77,7 +77,7 @@ the following stylesheets are blocked and won't load:
 
 as well as styles loaded using the {{HTTPHeader("Link")}} header:
 
-```bash
+```
 Link: <https://not-example.com/styles/stylesheet.css>;rel=stylesheet
 ```
 
@@ -124,7 +124,7 @@ The above Content Security Policy will allow inline styles like the {{HTMLElemen
 
 You can use a nonce-source to only allow specific inline style blocks:
 
-```bash
+```
 Content-Security-Policy: style-src 'nonce-2726c7f26c'
 ```
 
@@ -144,7 +144,7 @@ echo -n "#inline-style { background: red; }" | openssl dgst -sha256 -binary | op
 
 You can use a hash-source to only allow specific inline style blocks:
 
-```bash
+```
 Content-Security-Policy: style-src 'sha256-ozBpjL6dxO8fsS4u6fwG1dFDACYvpNxYeBA6tzR+FY8='
 ```
 
diff --git a/files/en-us/web/http/headers/content-security-policy/upgrade-insecure-requests/index.md b/files/en-us/web/http/headers/content-security-policy/upgrade-insecure-requests/index.md
index 6dc48aca3a772bf..71db8ec2e0d888a 100644
--- a/files/en-us/web/http/headers/content-security-policy/upgrade-insecure-requests/index.md
+++ b/files/en-us/web/http/headers/content-security-policy/upgrade-insecure-requests/index.md
@@ -36,17 +36,23 @@ not subject to SSL stripping attacks.
 
 ## Syntax
 
-```html
+```
 Content-Security-Policy: upgrade-insecure-requests;
 ```
 
 ## Examples
 
-    // header
-    Content-Security-Policy: upgrade-insecure-requests;
+### Using the HTTP header
+
+```
+Content-Security-Policy: upgrade-insecure-requests;
+```
 
-    // meta tag
-    <meta http-equiv="Content-Security-Policy" content="upgrade-insecure-requests">
+### Usting the HTML meta element
+
+```html
+<meta http-equiv="Content-Security-Policy" content="upgrade-insecure-requests">
+```
 
 With the above header set on a domain example.com that wants to migrate from HTTP to
 HTTPS, non-navigational insecure resource requests are automatically upgraded
@@ -80,8 +86,10 @@ With the help of the {{HTTPHeader("Content-Security-Policy-Report-Only")}} heade
 the {{CSP("report-uri")}} directive, you can set-up an enforced policy and a reported
 policy like this:
 
-    Content-Security-Policy: upgrade-insecure-requests; default-src https:
-    Content-Security-Policy-Report-Only: default-src https:; report-uri /endpoint
+```
+Content-Security-Policy: upgrade-insecure-requests; default-src https:
+Content-Security-Policy-Report-Only: default-src https:; report-uri /endpoint
+```
 
 That way, you still upgrade insecure requests on your secure site, but the only
 monitoring policy is violated and reports insecure resources to your endpoint.
diff --git a/files/en-us/web/http/headers/content-security-policy/worker-src/index.md b/files/en-us/web/http/headers/content-security-policy/worker-src/index.md
index 4562bd9218cbfda..446e29cea35b65c 100644
--- a/files/en-us/web/http/headers/content-security-policy/worker-src/index.md
+++ b/files/en-us/web/http/headers/content-security-policy/worker-src/index.md
@@ -47,7 +47,7 @@ scripts.
 
 One or more sources can be allowed for the `worker-src` policy:
 
-```html
+```
 Content-Security-Policy: worker-src <source>;
 Content-Security-Policy: worker-src <source> <source>;
 ```
@@ -62,7 +62,7 @@ Content-Security-Policy: worker-src <source> <source>;
 
 Given this CSP header:
 
-```bash
+```
 Content-Security-Policy: worker-src https://example.com/
 ```
 
@@ -88,6 +88,5 @@ blocked and won't load:
 ## See also
 
 - {{HTTPHeader("Content-Security-Policy")}}
-- [CSP
-  for Web Workers](/en-US/docs/Web/API/Web_Workers_API/Using_web_workers#content_security_policy)
+- [CSP for Web Workers](/en-US/docs/Web/API/Web_Workers_API/Using_web_workers#content_security_policy)
 - {{domxref("Worker")}}, {{domxref("SharedWorker")}}, {{domxref("ServiceWorker")}}
diff --git a/files/en-us/web/http/headers/content-type/index.md b/files/en-us/web/http/headers/content-type/index.md
index 3529cfaf1fc6284..cdf52ac55ad8a52 100644
--- a/files/en-us/web/http/headers/content-type/index.md
+++ b/files/en-us/web/http/headers/content-type/index.md
@@ -51,7 +51,7 @@ In requests, (such as {{HTTPMethod("POST")}} or {{HTTPMethod("PUT")}}), the clie
 
 ## Syntax
 
-```html
+```
 Content-Type: text/html; charset=UTF-8
 Content-Type: multipart/form-data; boundary=something
 ```
@@ -81,20 +81,22 @@ In a {{HTTPMethod("POST")}} request, resulting from an HTML form submission, the
 
 The request looks something like this (less interesting headers are omitted here):
 
-    POST /foo HTTP/1.1
-    Content-Length: 68137
-    Content-Type: multipart/form-data; boundary=---------------------------974767299852498929531610575
+```
+POST /foo HTTP/1.1
+Content-Length: 68137
+Content-Type: multipart/form-data; boundary=---------------------------974767299852498929531610575
 
-    -----------------------------974767299852498929531610575
-    Content-Disposition: form-data; name="description"
+-----------------------------974767299852498929531610575
+Content-Disposition: form-data; name="description"
 
-    some text
-    -----------------------------974767299852498929531610575
-    Content-Disposition: form-data; name="myFile"; filename="foo.txt"
-    Content-Type: text/plain
+some text
+-----------------------------974767299852498929531610575
+Content-Disposition: form-data; name="myFile"; filename="foo.txt"
+Content-Type: text/plain
 
-    (content of the uploaded file foo.txt)
-    -----------------------------974767299852498929531610575--
+(content of the uploaded file foo.txt)
+-----------------------------974767299852498929531610575--
+```
 
 ## Specifications
 
diff --git a/files/en-us/web/http/headers/cookie/index.md b/files/en-us/web/http/headers/cookie/index.md
index 9ead3f23b708f7f..28855b7ef197fbe 100644
--- a/files/en-us/web/http/headers/cookie/index.md
+++ b/files/en-us/web/http/headers/cookie/index.md
@@ -30,7 +30,7 @@ The `Cookie` header is optional and may be omitted if, for example, the browser'
 
 ## Syntax
 
-```html
+```
 Cookie: <cookie-list>
 Cookie: name=value
 Cookie: name=value; name2=value2; name3=value3
@@ -41,7 +41,9 @@ Cookie: name=value; name2=value2; name3=value3
 
 ## Examples
 
-    Cookie: PHPSESSID=298zf09hf012fh2; csrftoken=u32t4o3tb3gg43; _gat=1
+```
+Cookie: PHPSESSID=298zf09hf012fh2; csrftoken=u32t4o3tb3gg43; _gat=1
+```
 
 ## Specifications
 
diff --git a/files/en-us/web/http/headers/cookie2/index.md b/files/en-us/web/http/headers/cookie2/index.md
index 1beaa08726f15ca..640690266b29d06 100644
--- a/files/en-us/web/http/headers/cookie2/index.md
+++ b/files/en-us/web/http/headers/cookie2/index.md
@@ -28,7 +28,9 @@ The obsolete **`Cookie2`** HTTP request header used to advise the server that t
 
 ## Examples
 
-    Cookie2: $Version="1"
+```
+Cookie2: $Version="1"
+```
 
 ## Specifications
 
diff --git a/files/en-us/web/http/headers/cross-origin-embedder-policy/index.md b/files/en-us/web/http/headers/cross-origin-embedder-policy/index.md
index 7c9511004889b16..faeb9a449d20ea0 100644
--- a/files/en-us/web/http/headers/cross-origin-embedder-policy/index.md
+++ b/files/en-us/web/http/headers/cross-origin-embedder-policy/index.md
@@ -28,7 +28,7 @@ The HTTP **`Cross-Origin-Embedder-Policy`** (COEP) response header prevents a do
 
 ## Syntax
 
-```html
+```
 Cross-Origin-Embedder-Policy: unsafe-none | require-corp
 ```
 
@@ -46,8 +46,10 @@ Cross-Origin-Embedder-Policy: unsafe-none | require-corp
 
 You can only access certain features like {{jsxref("SharedArrayBuffer")}} objects or {{domxref("Performance.now()")}} with unthrottled timers, if your document has a COEP header with the value `require-corp` value set.
 
-    Cross-Origin-Embedder-Policy: require-corp
-    Cross-Origin-Opener-Policy: same-origin
+```
+Cross-Origin-Embedder-Policy: require-corp
+Cross-Origin-Opener-Policy: same-origin
+```
 
 See also the {{HTTPHeader("Cross-Origin-Opener-Policy")}} header which you'll need to set as well.
 
@@ -55,9 +57,9 @@ To check if cross origin isolation has been successful, you can test against the
 
 ```js
 if (crossOriginIsolated) {
-  // Post SharedArrayBuffer
+  // Post SharedArrayBuffer
 } else {
-  // Do something else
+  // Do something else
 }
 ```
 
diff --git a/files/en-us/web/http/headers/cross-origin-opener-policy/index.md b/files/en-us/web/http/headers/cross-origin-opener-policy/index.md
index 29146ecd5abd994..dbd241cce69ee2f 100644
--- a/files/en-us/web/http/headers/cross-origin-opener-policy/index.md
+++ b/files/en-us/web/http/headers/cross-origin-opener-policy/index.md
@@ -32,8 +32,10 @@ If a cross-origin document with COOP is opened in a new window, the opening docu
 
 ## Syntax
 
-```html
-Cross-Origin-Opener-Policy: unsafe-none | same-origin-allow-popups | same-origin
+```
+Cross-Origin-Opener-Policy: unsafe-none
+Cross-Origin-Opener-Policy: same-origin-allow-popups
+Cross-Origin-Opener-Policy: same-origin
 ```
 
 ### Directives
@@ -51,8 +53,10 @@ Cross-Origin-Opener-Policy: unsafe-none | same-origin-allow-popups | same-origin
 
 Certain features like {{jsxref("SharedArrayBuffer")}} objects or {{domxref("Performance.now()")}} with unthrottled timers are only available if your document has a COOP header with the value `same-origin` value set.
 
-    Cross-Origin-Opener-Policy: same-origin
-    Cross-Origin-Embedder-Policy: require-corp
+```
+Cross-Origin-Opener-Policy: same-origin
+Cross-Origin-Embedder-Policy: require-corp
+```
 
 See also the {{HTTPHeader("Cross-Origin-Embedder-Policy")}} header which you'll need to set as well.
 
@@ -60,9 +64,9 @@ To check if cross-origin isolation has been successful, you can test against the
 
 ```js
 if (crossOriginIsolated) {
-  // Post SharedArrayBuffer
+  // Post SharedArrayBuffer
 } else {
-  // Do something else
+  // Do something else
 }
 ```
 
diff --git a/files/en-us/web/http/headers/cross-origin-resource-policy/index.md b/files/en-us/web/http/headers/cross-origin-resource-policy/index.md
index 3af21386a9120ec..c6bd0a930b89bef 100644
--- a/files/en-us/web/http/headers/cross-origin-resource-policy/index.md
+++ b/files/en-us/web/http/headers/cross-origin-resource-policy/index.md
@@ -39,7 +39,7 @@ given resource.
 
 ## Syntax
 
-```html
+```
 Cross-Origin-Resource-Policy: same-site | same-origin | cross-origin
 ```
 
@@ -48,7 +48,9 @@ Cross-Origin-Resource-Policy: same-site | same-origin | cross-origin
 The response header below will cause compatible user agents to disallow cross-origin
 no-cors requests:
 
-    Cross-Origin-Resource-Policy: same-origin
+```
+Cross-Origin-Resource-Policy: same-origin
+```
 
 For more examples, see <https://resourcepolicy.fyi/>.
 
@@ -62,8 +64,6 @@ For more examples, see <https://resourcepolicy.fyi/>.
 
 ## See also
 
-- [Cross-Origin
-  Resource Policy (CORP) explainer](</en-US/docs/Web/HTTP/Cross-Origin_Resource_Policy_(CORP)>)
-- [Consider deploying Cross-Origin Resource
-  Policy](https://resourcepolicy.fyi/)
+- [Cross-Origin Resource Policy (CORP) explainer](</en-US/docs/Web/HTTP/Cross-Origin_Resource_Policy_(CORP)>)
+- [Consider deploying Cross-Origin Resource Policy](https://resourcepolicy.fyi/)
 - {{httpheader("Access-Control-Allow-Origin")}}
diff --git a/files/en-us/web/http/headers/date/index.md b/files/en-us/web/http/headers/date/index.md
index 4e04bec927bcd67..9f72d831620fc5e 100644
--- a/files/en-us/web/http/headers/date/index.md
+++ b/files/en-us/web/http/headers/date/index.md
@@ -44,7 +44,7 @@ at which the message was originated.
 
 ## Syntax
 
-```html
+```
 Date: <day-name>, <day> <month> <year> <hour>:<minute>:<second> GMT
 ```
 
@@ -71,7 +71,9 @@ Date: <day-name>, <day> <month> <year> <hour>:<minute>:<second> GMT
 
 ## Examples
 
-    Date: Wed, 21 Oct 2015 07:28:00 GMT
+```
+Date: Wed, 21 Oct 2015 07:28:00 GMT
+```
 
 ```js
 new Date().toUTCString()
diff --git a/files/en-us/web/http/headers/device-memory/index.md b/files/en-us/web/http/headers/device-memory/index.md
index af85ce9ebbc37fa..2c310591c294c76 100644
--- a/files/en-us/web/http/headers/device-memory/index.md
+++ b/files/en-us/web/http/headers/device-memory/index.md
@@ -39,7 +39,9 @@ The **`Device-Memory`** {{Glossary("Client hints","device client hint")}} reques
 
 ## Syntax
 
-    Device-Memory: <number>
+```
+Device-Memory: <number>
+```
 
 ## Directives
 
@@ -52,11 +54,15 @@ The amount of device RAM can be used as a fingerprinting variable, so values for
 
 The server first needs to opt in to receive `Device-Memory` header by sending the response headers {{HTTPHeader("Accept-CH")}} containing `Device-Memory`.
 
-    Accept-CH: Device-Memory
+```
+Accept-CH: Device-Memory
+```
 
 Then on subsequent requests the client might send `Device-Memory` header back:
 
-    Device-Memory: 1
+```
+Device-Memory: 1
+```
 
 ## Specifications
 
diff --git a/files/en-us/web/http/headers/digest/index.md b/files/en-us/web/http/headers/digest/index.md
index 97761b6d32774e3..d37daa8c0be7f65 100644
--- a/files/en-us/web/http/headers/digest/index.md
+++ b/files/en-us/web/http/headers/digest/index.md
@@ -39,8 +39,10 @@ The digest is calculated over the entire representation. The representation itse
 
 ## Syntax
 
-    Digest: <digest-algorithm>=<digest-value>
-    Digest: <digest-algorithm>=<digest-value>,<digest-algorithm>=<digest-value>
+```
+Digest: <digest-algorithm>=<digest-value>
+Digest: <digest-algorithm>=<digest-value>,<digest-algorithm>=<digest-value>
+```
 
 ## Directives
 
@@ -56,8 +58,10 @@ The digest is calculated over the entire representation. The representation itse
 
 ## Examples
 
-    Digest: sha-256=X48E9qOokqqrvdts8nOJRJN3OWDUoyWxBf7kbu9DBPE=
-    Digest: sha-256=X48E9qOokqqrvdts8nOJRJN3OWDUoyWxBf7kbu9DBPE=,unixsum=30637
+```
+Digest: sha-256=X48E9qOokqqrvdts8nOJRJN3OWDUoyWxBf7kbu9DBPE=
+Digest: sha-256=X48E9qOokqqrvdts8nOJRJN3OWDUoyWxBf7kbu9DBPE=,unixsum=30637
+```
 
 ## Specifications
 
diff --git a/files/en-us/web/http/headers/dnt/index.md b/files/en-us/web/http/headers/dnt/index.md
index f2934065bff5186..694893ad71f7f37 100644
--- a/files/en-us/web/http/headers/dnt/index.md
+++ b/files/en-us/web/http/headers/dnt/index.md
@@ -29,7 +29,7 @@ users indicate whether they would prefer privacy rather than personalized conten
 
 ## Syntax
 
-```html
+```
 DNT: 0
 DNT: 1
 DNT: null
@@ -68,10 +68,8 @@ navigator.doNotTrack; // "0" or "1"
 - {{domxref("Navigator.doNotTrack")}}
 - {{HTTPHeader("Tk")}} header
 - [Do Not Track on Wikipedia](https://en.wikipedia.org/wiki/Do_Not_Track)
-- [What
-  Does the "Track" in "Do Not Track" Mean? – EFF](https://www.eff.org/deeplinks/2011/02/what-does-track-do-not-track-mean)
+- [What Does the "Track" in "Do Not Track" Mean? – EFF](https://www.eff.org/deeplinks/2011/02/what-does-track-do-not-track-mean)
 - [donottrack.us](https://donottrack.us/)
 - DNT browser settings help:
-
   - [Firefox](https://www.mozilla.org/en-US/firefox/dnt/)
   - [Chrome](https://support.google.com/chrome/answer/2790761)
diff --git a/files/en-us/web/http/headers/downlink/index.md b/files/en-us/web/http/headers/downlink/index.md
index 5fb4dbf2de6888c..e56752e348c4f6f 100644
--- a/files/en-us/web/http/headers/downlink/index.md
+++ b/files/en-us/web/http/headers/downlink/index.md
@@ -39,7 +39,9 @@ The hint allows a server to choose what information is sent based on the network
 
 ## Syntax
 
-    Downlink: <number>
+```
+Downlink: <number>
+```
 
 ## Directives
 
@@ -50,11 +52,15 @@ The hint allows a server to choose what information is sent based on the network
 
 A server first needs to opt in to receive the `Downlink` header by sending the {{HTTPHeader("Accept-CH")}} response header containing `Downlink`.
 
-    Accept-CH: Downlink
+```
+Accept-CH: Downlink
+```
 
 Then on subsequent requests the client might send a `Downlink` header back:
 
-    Downlink: 1.7
+```
+Downlink: 1.7
+```
 
 ## Specifications
 
diff --git a/files/en-us/web/http/headers/dpr/index.md b/files/en-us/web/http/headers/dpr/index.md
index 437453ea1a11021..0fd7ec5101e6992 100644
--- a/files/en-us/web/http/headers/dpr/index.md
+++ b/files/en-us/web/http/headers/dpr/index.md
@@ -47,7 +47,9 @@ If the `DPR` header appears more than once in a message the last occurrence is u
 
 ## Syntax
 
-    DPR: <number>
+```
+DPR: <number>
+```
 
 ## Directives
 
@@ -58,15 +60,21 @@ If the `DPR` header appears more than once in a message the last occurrence is u
 
 A server must first opt in to receive the `DPR` header by sending the response header {{HTTPHeader("Accept-CH")}} containing the directive `DPR`.
 
-    Accept-CH: DPR
+```
+Accept-CH: DPR
+```
 
 Then on subsequent requests the client might send `DPR` header to the server:
 
-    DPR: 2.0
+```
+DPR: 2.0
+```
 
 If a request with the `DPR` header (as shown above) is for an image resource, then the server response must include the {{HTTPHeader("Content-DPR")}} header:
 
-    Content-DPR: 2.0
+```
+Content-DPR: 2.0
+```
 
 ## Browser compatibility
 
diff --git a/files/en-us/web/http/headers/early-data/index.md b/files/en-us/web/http/headers/early-data/index.md
index e00fb03acd0dc2f..fdae8348a8e4a5f 100644
--- a/files/en-us/web/http/headers/early-data/index.md
+++ b/files/en-us/web/http/headers/early-data/index.md
@@ -15,8 +15,7 @@ browser-compat: http.headers.Early-Data
 
 The **`Early-Data`** header is set by
 an intermediary to indicate that the request has been conveyed in [TLS early data](/en-US/docs/Web/Security/Transport_Layer_Security#tls_1.3),
-and also indicates that the intermediary understands the {{HTTPStatus("425", "425 (Too
-    Early)")}} status code.
+and also indicates that the intermediary understands the {{HTTPStatus("425", "425 (Too Early)")}} status code.
 
 The `Early-Data` header is **not** set by the originator of the
 request (i.e., a browser).
@@ -36,15 +35,17 @@ request (i.e., a browser).
 
 ## Syntax
 
-```html
+```
 Early-Data: 1
 ```
 
 ## Examples
 
-    GET /resource HTTP/1.0
-    Host: example.com
-    Early-Data: 1
+```
+GET /resource HTTP/1.0
+Host: example.com
+Early-Data: 1
+```
 
 ## Specifications
 
diff --git a/files/en-us/web/http/headers/ect/index.md b/files/en-us/web/http/headers/ect/index.md
index 987564c5e69b170..d2acc5af5f24fd2 100644
--- a/files/en-us/web/http/headers/ect/index.md
+++ b/files/en-us/web/http/headers/ect/index.md
@@ -39,7 +39,9 @@ The hint allows a server to choose what information is sent based on the broad c
 
 ## Syntax
 
-    ECT: <value>
+```
+ECT: <value>
+```
 
 ## Directives
 
@@ -50,11 +52,15 @@ The hint allows a server to choose what information is sent based on the broad c
 
 A server first needs to opt in to receive the `ECT` header by sending the {{HTTPHeader("Accept-CH")}} response header containing `ECT`.
 
-    Accept-CH: ECT
+```
+Accept-CH: ECT
+```
 
 Then on subsequent requests the client might send an `ECT` header back:
 
-    ECT: 2g
+```
+ECT: 2g
+```
 
 ## Specifications
 
diff --git a/files/en-us/web/http/headers/etag/index.md b/files/en-us/web/http/headers/etag/index.md
index 02d702dfedd3fb9..8dacd896e43e5bc 100644
--- a/files/en-us/web/http/headers/etag/index.md
+++ b/files/en-us/web/http/headers/etag/index.md
@@ -37,7 +37,7 @@ tracking server.
 
 ## Syntax
 
-```html
+```
 ETag: W/"<etag_value>"
 ETag: "<etag_value>"
 ```
@@ -61,8 +61,10 @@ ETag: "<etag_value>"
 
 ## Examples
 
-    ETag: "33a64df551425fcc55e4d42a148795d9f25f89d4"
-    ETag: W/"0815"
+```
+ETag: "33a64df551425fcc55e4d42a148795d9f25f89d4"
+ETag: W/"0815"
+```
 
 ### Avoiding mid-air collisions
 
@@ -72,13 +74,17 @@ can detect mid-air edit collisions.
 For example, when editing a wiki, the current wiki content may be hashed
 and put into an `Etag` header in the response:
 
-    ETag: "33a64df551425fcc55e4d42a148795d9f25f89d4"
+```
+ETag: "33a64df551425fcc55e4d42a148795d9f25f89d4"
+```
 
 When saving changes to a wiki page (posting data), the {{HTTPMethod("POST")}} request
 will contain the {{HTTPHeader("If-Match")}} header containing the `ETag`
 values to check freshness against.
 
-    If-Match: "33a64df551425fcc55e4d42a148795d9f25f89d4"
+```
+If-Match: "33a64df551425fcc55e4d42a148795d9f25f89d4"
+```
 
 If the hashes don't match, it means that the document has been edited in-between and a
 {{HTTPStatus("412")}} `Precondition Failed` error is thrown.
@@ -90,7 +96,9 @@ unchanged. If a user visits a given URL again (that has an `ETag` set), and
 it is _stale_ (too old to be considered usable), the client will send the value
 of its `ETag` along in an {{HTTPHeader("If-None-Match")}} header field:
 
-    If-None-Match: "33a64df551425fcc55e4d42a148795d9f25f89d4"
+```
+If-None-Match: "33a64df551425fcc55e4d42a148795d9f25f89d4"
+```
 
 The server compares the client's `ETag` (sent with
 `If-None-Match`) with the `ETag` for its current version of the
diff --git a/files/en-us/web/http/headers/expect-ct/index.md b/files/en-us/web/http/headers/expect-ct/index.md
index d5cb81b278e644f..01d5fcafda45c94 100644
--- a/files/en-us/web/http/headers/expect-ct/index.md
+++ b/files/en-us/web/http/headers/expect-ct/index.md
@@ -38,9 +38,11 @@ CT requirements can be satisfied via any one of the following mechanisms:
 
 ## Syntax
 
-    Expect-CT: report-uri="<uri>",
-               enforce,
-               max-age=<age>
+```
+Expect-CT: report-uri="<uri>",
+           enforce,
+           max-age=<age>
+```
 
 ##  Directives
 
@@ -66,7 +68,9 @@ CT requirements can be satisfied via any one of the following mechanisms:
 
 The following example specifies enforcement of Certificate Transparency for 24 hours and reports violations to `foo.example`.
 
-    Expect-CT: max-age=86400, enforce, report-uri="https://foo.example/report"
+```
+Expect-CT: max-age=86400, enforce, report-uri="https://foo.example/report"
+```
 
 ## Notes
 
diff --git a/files/en-us/web/http/headers/expect/index.md b/files/en-us/web/http/headers/expect/index.md
index 2dbc95d64467fdc..fdebbbc11da79c0 100644
--- a/files/en-us/web/http/headers/expect/index.md
+++ b/files/en-us/web/http/headers/expect/index.md
@@ -44,13 +44,13 @@ cURL do so by default.
 
 No other expectations except "100-continue" are specified currently.
 
-```html
+```
 Expect: 100-continue
 ```
 
 ## Directives
 
-- 100-continue
+- `100-continue`
   - : Informs recipients that the client is about to send a (presumably large) message
     body in this request and wishes to receive a {{HTTPStatus("100")}} (Continue) interim
     response.
@@ -62,11 +62,13 @@ Expect: 100-continue
 A client sends a request with a Expect header and waits for the server to respond
 before sending the message body.
 
-    PUT /somewhere/fun HTTP/1.1
-    Host: origin.example.com
-    Content-Type: video/h264
-    Content-Length: 1234567890987
-    Expect: 100-continue
+```
+PUT /somewhere/fun HTTP/1.1
+Host: origin.example.com
+Content-Type: video/h264
+Content-Length: 1234567890987
+Expect: 100-continue
+```
 
 The server now checks the request headers and may respond with a {{HTTPStatus("100")}}
 (Continue) response to instruct the client to go ahead and send the message body, or it
diff --git a/files/en-us/web/http/headers/expires/index.md b/files/en-us/web/http/headers/expires/index.md
index 8be7c6b18c1ed25..0fac32418fb7265 100644
--- a/files/en-us/web/http/headers/expires/index.md
+++ b/files/en-us/web/http/headers/expires/index.md
@@ -41,7 +41,7 @@ resource is already expired.
 
 ## Syntax
 
-```html
+```
 Expires: <http-date>
 ```
 
@@ -52,7 +52,9 @@ Expires: <http-date>
 
 ## Examples
 
-    Expires: Wed, 21 Oct 2015 07:28:00 GMT
+```
+Expires: Wed, 21 Oct 2015 07:28:00 GMT
+```
 
 ## Specifications
 
diff --git a/files/en-us/web/http/headers/feature-policy/accelerometer/index.md b/files/en-us/web/http/headers/feature-policy/accelerometer/index.md
index 66d3150a0df273b..572935afb0bd197 100644
--- a/files/en-us/web/http/headers/feature-policy/accelerometer/index.md
+++ b/files/en-us/web/http/headers/feature-policy/accelerometer/index.md
@@ -16,7 +16,9 @@ The HTTP {{HTTPHeader('Feature-Policy')}} header `accelerometer` directive contr
 
 ## Syntax
 
-    Feature-Policy: accelerometer <allowlist>;
+```
+Feature-Policy: accelerometer <allowlist>;
+```
 
 - \<allowlist>
   - : A list of origins for which the feature is allowed. See [`Feature-Policy`](/en-US/docs/Web/HTTP/Headers/Feature-Policy#syntax).
diff --git a/files/en-us/web/http/headers/feature-policy/ambient-light-sensor/index.md b/files/en-us/web/http/headers/feature-policy/ambient-light-sensor/index.md
index 8d388222474ca26..34f17a2421f103c 100644
--- a/files/en-us/web/http/headers/feature-policy/ambient-light-sensor/index.md
+++ b/files/en-us/web/http/headers/feature-policy/ambient-light-sensor/index.md
@@ -14,7 +14,9 @@ The HTTP {{HTTPHeader('Feature-Policy')}} header `ambient-light-sensor` directiv
 
 ## Syntax
 
-    Feature-Policy: ambient-light-sensor <allowlist>;
+```
+Feature-Policy: ambient-light-sensor <allowlist>;
+```
 
 - \<allowlist>
   - : A list of origins for which the feature is allowed. See [`Feature-Policy`](/en-US/docs/Web/HTTP/Headers/Feature-Policy#syntax).
diff --git a/files/en-us/web/http/headers/feature-policy/autoplay/index.md b/files/en-us/web/http/headers/feature-policy/autoplay/index.md
index dd0878a70b67895..fbf5110a3e6c20b 100644
--- a/files/en-us/web/http/headers/feature-policy/autoplay/index.md
+++ b/files/en-us/web/http/headers/feature-policy/autoplay/index.md
@@ -26,7 +26,9 @@ APIs](/en-US/docs/Web/Media/Autoplay_guide).
 
 ## Syntax
 
-    Feature-Policy: autoplay <allowlist>;
+```
+Feature-Policy: autoplay <allowlist>;
+```
 
 - \<allowlist>
   - : A list of origins for which the feature is allowed. See [`Feature-Policy`](/en-US/docs/Web/HTTP/Headers/Feature-Policy#syntax).
diff --git a/files/en-us/web/http/headers/feature-policy/battery/index.md b/files/en-us/web/http/headers/feature-policy/battery/index.md
index 47ab34157942260..6612351af377f87 100644
--- a/files/en-us/web/http/headers/feature-policy/battery/index.md
+++ b/files/en-us/web/http/headers/feature-policy/battery/index.md
@@ -14,7 +14,9 @@ The HTTP {{HTTPHeader("Feature-Policy")}} header `battery` directive controls wh
 
 ## Syntax
 
-    Feature-Policy: battery <allowlist>;
+```
+Feature-Policy: battery <allowlist>;
+```
 
 - \<allowlist>
   - : A list of origins for which the feature is allowed. See [`Feature-Policy`](/en-US/docs/Web/HTTP/Headers/Feature-Policy#syntax).
diff --git a/files/en-us/web/http/headers/feature-policy/camera/index.md b/files/en-us/web/http/headers/feature-policy/camera/index.md
index 09eda44d03276bd..aa22ca030647dd1 100644
--- a/files/en-us/web/http/headers/feature-policy/camera/index.md
+++ b/files/en-us/web/http/headers/feature-policy/camera/index.md
@@ -21,7 +21,9 @@ a `NotAllowedError` {{domxref("DOMException")}}.
 
 ## Syntax
 
-    Feature-Policy: camera <allowlist>;
+```
+Feature-Policy: camera <allowlist>;
+```
 
 - \<allowlist>
   - : A list of origins for which the feature is allowed. See [`Feature-Policy`](/en-US/docs/Web/HTTP/Headers/Feature-Policy#syntax).
diff --git a/files/en-us/web/http/headers/feature-policy/display-capture/index.md b/files/en-us/web/http/headers/feature-policy/display-capture/index.md
index 1ae3384625ffc79..ddf0dd07c250fe2 100644
--- a/files/en-us/web/http/headers/feature-policy/display-capture/index.md
+++ b/files/en-us/web/http/headers/feature-policy/display-capture/index.md
@@ -18,7 +18,9 @@ If `display-capture` is disabled in a document, the document will not be able to
 
 ## Syntax
 
-    Feature-Policy: display-capture <allowlist>;
+```
+Feature-Policy: display-capture <allowlist>;
+```
 
 - \<allowlist>
   - : A list of origins for which the feature is allowed. See [`Feature-Policy`](/en-US/docs/Web/HTTP/Headers/Feature-Policy#syntax).
diff --git a/files/en-us/web/http/headers/feature-policy/document-domain/index.md b/files/en-us/web/http/headers/feature-policy/document-domain/index.md
index acceaeb6965b3ec..21959efad136e6c 100644
--- a/files/en-us/web/http/headers/feature-policy/document-domain/index.md
+++ b/files/en-us/web/http/headers/feature-policy/document-domain/index.md
@@ -22,7 +22,9 @@ to set {{domxref("document.domain")}} will fail and cause a `SecurityError`
 
 ## Syntax
 
-    Feature-Policy: document-domain <allowlist>;
+```
+Feature-Policy: document-domain <allowlist>;
+```
 
 - \<allowlist>
   - : A list of origins for which the feature is allowed. See [`Feature-Policy`](/en-US/docs/Web/HTTP/Headers/Feature-Policy#syntax).
diff --git a/files/en-us/web/http/headers/feature-policy/encrypted-media/index.md b/files/en-us/web/http/headers/feature-policy/encrypted-media/index.md
index 5d63eff902d1265..a1ee4ec0543c222 100644
--- a/files/en-us/web/http/headers/feature-policy/encrypted-media/index.md
+++ b/files/en-us/web/http/headers/feature-policy/encrypted-media/index.md
@@ -17,7 +17,9 @@ The HTTP {{HTTPHeader("Feature-Policy")}} header `encrypted-media` directive con
 
 ## Syntax
 
-    Feature-Policy: encrypted-media <allowlist>;
+```
+Feature-Policy: encrypted-media <allowlist>;
+```
 
 - \<allowlist>
   - : A list of origins for which the feature is allowed. See [`Feature-Policy`](/en-US/docs/Web/HTTP/Headers/Feature-Policy#syntax).
diff --git a/files/en-us/web/http/headers/feature-policy/fullscreen/index.md b/files/en-us/web/http/headers/feature-policy/fullscreen/index.md
index 094c7e011dd3cef..ad29cef3379dbdb 100644
--- a/files/en-us/web/http/headers/feature-policy/fullscreen/index.md
+++ b/files/en-us/web/http/headers/feature-policy/fullscreen/index.md
@@ -20,7 +20,9 @@ By default, top-level documents and their same-origin child frames can request a
 
 ## Syntax
 
-    Feature-Policy: fullscreen <allowlist>;
+```
+Feature-Policy: fullscreen <allowlist>;
+```
 
 - \<allowlist>
   - : A list of origins for which the feature is allowed. See [`Feature-Policy`](/en-US/docs/Web/HTTP/Headers/Feature-Policy#syntax).
@@ -35,7 +37,7 @@ Default allow list for `fullscreen` is `'self'`.
 
 SecureCorp Inc. wants to disable the Fullscreen API within all browsing contexts except for its own origin and those whose origin is `https://example.com`. It can do so by delivering the following HTTP response header to define a feature policy:
 
-```bash
+```
 Feature-Policy: fullscreen 'self' https://example.com
 ```
 
@@ -43,7 +45,7 @@ Feature-Policy: fullscreen 'self' https://example.com
 
 FastCorp Inc. wants to disable `fullscreen` for all cross-origin child frames, except for a specific \<iframe>. It can do so by delivering the following HTTP response header to define a feature policy:
 
-```bash
+```
 Feature-Policy: fullscreen 'self'
 ```
 
diff --git a/files/en-us/web/http/headers/feature-policy/gamepad/index.md b/files/en-us/web/http/headers/feature-policy/gamepad/index.md
index a563193fa5991ee..8835fdf97ba05bd 100644
--- a/files/en-us/web/http/headers/feature-policy/gamepad/index.md
+++ b/files/en-us/web/http/headers/feature-policy/gamepad/index.md
@@ -17,7 +17,9 @@ In addition, the {{event("gamepadconnected")}} and {{event("gamepaddisconnected"
 
 ## Syntax
 
-    Feature-Policy: gamepad <allowlist>;
+```
+Feature-Policy: gamepad <allowlist>;
+```
 
 - \<allowlist>
   - : A list of origins for which the feature is allowed. See [`Feature-Policy`](/en-US/docs/Web/HTTP/Headers/Feature-Policy#syntax).
@@ -33,7 +35,7 @@ Default allow list for `gamepad` is `'self'`.
 SecureCorp Inc. wants to disable the Gamepad API within all browsing contexts except for its own origin and those whose origin is `https://example.com`.
 It can do so by delivering the following HTTP response header to define a feature policy:
 
-```bash
+```
 Feature-Policy: gamepad 'self' https://example.com
 ```
 
@@ -42,13 +44,15 @@ Feature-Policy: gamepad 'self' https://example.com
 FastCorp Inc. wants to disable `gamepad` for all cross-origin child frames, except for a specific \<iframe>.
 It can do so by delivering the following HTTP response header to define a feature policy:
 
-```bash
+```
 Feature-Policy: gamepad 'self'
 ```
 
 Then include an {{HTMLElement('iframe','allow','#Attributes')}} attribute on the `<iframe>` element:
 
-    <iframe src="https://other.com/game" allow="gamepad"></iframe>
+```html
+<iframe src="https://other.com/game" allow="gamepad"></iframe>
+```
 
 iframe attributes can selectively enable features in certain frames, and not in others, even if those frames contain documents from the same origin.
 
diff --git a/files/en-us/web/http/headers/feature-policy/geolocation/index.md b/files/en-us/web/http/headers/feature-policy/geolocation/index.md
index 3df76c649f3c344..3d88d85e82d2836 100644
--- a/files/en-us/web/http/headers/feature-policy/geolocation/index.md
+++ b/files/en-us/web/http/headers/feature-policy/geolocation/index.md
@@ -25,7 +25,9 @@ accessing geolocation. This includes same-origin frames.
 
 ## Syntax
 
-    Feature-Policy: geolocation <allowlist>;
+```
+Feature-Policy: geolocation <allowlist>;
+```
 
 - \<allowlist>
   - : A list of origins for which the feature is allowed. See [`Feature-Policy`](/en-US/docs/Web/HTTP/Headers/Feature-Policy#syntax).
@@ -42,7 +44,7 @@ SecureCorp Inc. wants to disable the Geolocation API within all browsing context
 except for its own origin and those whose origin is `https://example.com`. It
 can do so by delivering the following HTTP response header to define a feature policy:
 
-```bash
+```
 Feature-Policy: geolocation 'self' https://example.com
 ```
 
@@ -52,16 +54,18 @@ FastCorp Inc. wants to disable `geolocation` for all cross-origin child
 frames, except for a specific \<iframe>. It can do so by delivering the following
 HTTP response header to define a feature policy:
 
-```bash
+```
 Feature-Policy: geolocation 'self'
 ```
 
 Then include an {{HTMLElement('iframe','allow','#Attributes')}} attribute on the
 `<iframe>` element:
 
-    <iframe src="https://other.com/map" allow="geolocation"></iframe>
+```html
+<iframe src="https://other.com/map" allow="geolocation"></iframe>
+```
 
-iframe attributes can selectively enable features in certain frames, and not in others,
+Interestingly, `allow` attributes can selectively enable features in certain frames, and not in others,
 even if those frames contain documents from the same origin.
 
 ## Specifications
diff --git a/files/en-us/web/http/headers/feature-policy/gyroscope/index.md b/files/en-us/web/http/headers/feature-policy/gyroscope/index.md
index 51e008fb0dec106..e49e30cd82ffbf4 100644
--- a/files/en-us/web/http/headers/feature-policy/gyroscope/index.md
+++ b/files/en-us/web/http/headers/feature-policy/gyroscope/index.md
@@ -15,7 +15,9 @@ The HTTP {{HTTPHeader("Feature-Policy")}} header `gyroscope` directive controls
 
 ## Syntax
 
-    Feature-Policy: gyroscope <allowlist>;
+```
+Feature-Policy: gyroscope <allowlist>;
+```
 
 - \<allowlist>
   - : A list of origins for which the feature is allowed. See [`Feature-Policy`](/en-US/docs/Web/HTTP/Headers/Feature-Policy#syntax).
diff --git a/files/en-us/web/http/headers/feature-policy/index.md b/files/en-us/web/http/headers/feature-policy/index.md
index 33037b7b7c20ccf..26045eede447679 100644
--- a/files/en-us/web/http/headers/feature-policy/index.md
+++ b/files/en-us/web/http/headers/feature-policy/index.md
@@ -36,7 +36,9 @@ For more information, see the main [Feature Policy](/en-US/docs/Web/HTTP/Feature
 
 ## Syntax
 
-    Feature-Policy: <directive> <allowlist>
+```
+Feature-Policy: <directive> <allowlist>
+```
 
 - `<directive>`
   - : The Feature Policy directive to apply the `allowlist` to. See [Directives](#directives) below for a list of the permitted directive names.
@@ -131,7 +133,9 @@ For more information, see the main [Feature Policy](/en-US/docs/Web/HTTP/Feature
 
 SecureCorp Inc. wants to disable Microphone and Geolocation APIs in its application. It can do so by delivering the following HTTP response header to define a feature policy:
 
-    Feature-Policy: microphone 'none'; geolocation 'none'
+```
+Feature-Policy: microphone 'none'; geolocation 'none'
+```
 
 By specifying the `'none'` keyword for the origin list, the specified features will be disabled for all browsing contexts (this includes all iframes), regardless of their origin.
 
diff --git a/files/en-us/web/http/headers/feature-policy/layout-animations/index.md b/files/en-us/web/http/headers/feature-policy/layout-animations/index.md
index f42b6add04512c3..23604400ba3a7c1 100644
--- a/files/en-us/web/http/headers/feature-policy/layout-animations/index.md
+++ b/files/en-us/web/http/headers/feature-policy/layout-animations/index.md
@@ -17,7 +17,9 @@ The HTTP {{HTTPHeader("Feature-Policy")}} header `layout-animations` directive c
 
 ## Syntax
 
-    Feature-Policy: layout-animations <allowlist>;
+```
+Feature-Policy: layout-animations <allowlist>;
+```
 
 - \<allowlist>
   - : A list of origins for which the feature is allowed. See [`Feature-Policy`](/en-US/docs/Web/HTTP/Headers/Feature-Policy#syntax).
diff --git a/files/en-us/web/http/headers/feature-policy/legacy-image-formats/index.md b/files/en-us/web/http/headers/feature-policy/legacy-image-formats/index.md
index 2d2eab69542bf9e..58e55e498792d48 100644
--- a/files/en-us/web/http/headers/feature-policy/legacy-image-formats/index.md
+++ b/files/en-us/web/http/headers/feature-policy/legacy-image-formats/index.md
@@ -17,7 +17,9 @@ The HTTP {{HTTPHeader("Feature-Policy")}} header `legacy-image-formats` directiv
 
 ## Syntax
 
-    Feature-Policy: legacy-image-formats <allowlist>;
+```
+Feature-Policy: legacy-image-formats <allowlist>;
+```
 
 - \<allowlist>
   - : A list of origins for which the feature is allowed. See [`Feature-Policy`](/en-US/docs/Web/HTTP/Headers/Feature-Policy#syntax).
diff --git a/files/en-us/web/http/headers/feature-policy/magnetometer/index.md b/files/en-us/web/http/headers/feature-policy/magnetometer/index.md
index 3c747de4a1fde6b..739df2a0d07c5ec 100644
--- a/files/en-us/web/http/headers/feature-policy/magnetometer/index.md
+++ b/files/en-us/web/http/headers/feature-policy/magnetometer/index.md
@@ -16,7 +16,9 @@ The HTTP {{HTTPHeader("Feature-Policy")}} header `magnetometer` directive contro
 
 ## Syntax
 
-    Feature-Policy: magnetometer <allowlist>;
+```
+Feature-Policy: magnetometer <allowlist>;
+```
 
 - \<allowlist>
   - : A list of origins for which the feature is allowed. See [`Feature-Policy`](/en-US/docs/Web/HTTP/Headers/Feature-Policy#syntax).
diff --git a/files/en-us/web/http/headers/feature-policy/microphone/index.md b/files/en-us/web/http/headers/feature-policy/microphone/index.md
index f3dbfa8d1d3dc8b..c64a85f539b89f1 100644
--- a/files/en-us/web/http/headers/feature-policy/microphone/index.md
+++ b/files/en-us/web/http/headers/feature-policy/microphone/index.md
@@ -20,7 +20,9 @@ returned by {{domxref("MediaDevices.getUserMedia()")}} will reject with a
 
 ## Syntax
 
-    Feature-Policy: microphone <allowlist>;
+```
+Feature-Policy: microphone <allowlist>;
+```
 
 - \<allowlist>
   - : A list of origins for which the feature is allowed. See [`Feature-Policy`](/en-US/docs/Web/HTTP/Headers/Feature-Policy#syntax).
diff --git a/files/en-us/web/http/headers/feature-policy/midi/index.md b/files/en-us/web/http/headers/feature-policy/midi/index.md
index dcd1ab225abcfe8..74814c5073669a0 100644
--- a/files/en-us/web/http/headers/feature-policy/midi/index.md
+++ b/files/en-us/web/http/headers/feature-policy/midi/index.md
@@ -17,7 +17,9 @@ The HTTP {{HTTPHeader("Feature-Policy")}} header `midi` directive controls wheth
 
 ## Syntax
 
-    Feature-Policy: midi <allowlist>;
+```
+Feature-Policy: midi <allowlist>;
+```
 
 - \<allowlist>
   - : A list of origins for which the feature is allowed. See [`Feature-Policy`](/en-US/docs/Web/HTTP/Headers/Feature-Policy#syntax).
diff --git a/files/en-us/web/http/headers/feature-policy/oversized-images/index.md b/files/en-us/web/http/headers/feature-policy/oversized-images/index.md
index d79cf9e5142e5c0..9dbbb511f719f95 100644
--- a/files/en-us/web/http/headers/feature-policy/oversized-images/index.md
+++ b/files/en-us/web/http/headers/feature-policy/oversized-images/index.md
@@ -16,7 +16,9 @@ The HTTP {{HTTPHeader("Feature-Policy")}} header `oversized-images` directive co
 
 ## Syntax
 
-    Feature-Policy: oversized-images <allowlist>;
+```
+Feature-Policy: oversized-images <allowlist>;
+```
 
 - \<allowlist>
   - : A list of origins for which the feature is allowed. See [`Feature-Policy`](/en-US/docs/Web/HTTP/Headers/Feature-Policy#syntax).
diff --git a/files/en-us/web/http/headers/feature-policy/payment/index.md b/files/en-us/web/http/headers/feature-policy/payment/index.md
index b89ce3d29a3c869..3a0e4cfc2bf1b39 100644
--- a/files/en-us/web/http/headers/feature-policy/payment/index.md
+++ b/files/en-us/web/http/headers/feature-policy/payment/index.md
@@ -18,7 +18,9 @@ The HTTP {{HTTPHeader("Feature-Policy")}} header field's `payment` directive con
 
 ## Syntax
 
-    Feature-Policy: payment <allowlist>;
+```
+Feature-Policy: payment <allowlist>;
+```
 
 - \<allowlist>
   - : A list of origins for which the feature is allowed. See [`Feature-Policy`](/en-US/docs/Web/HTTP/Headers/Feature-Policy#syntax).
diff --git a/files/en-us/web/http/headers/feature-policy/picture-in-picture/index.md b/files/en-us/web/http/headers/feature-policy/picture-in-picture/index.md
index 7d271064d683da4..a502cbd96a05ad9 100644
--- a/files/en-us/web/http/headers/feature-policy/picture-in-picture/index.md
+++ b/files/en-us/web/http/headers/feature-policy/picture-in-picture/index.md
@@ -16,7 +16,9 @@ The HTTP {{HTTPHeader("Feature-Policy")}} header `picture-in-picture` directive
 
 ## Syntax
 
-    Feature-Policy: picture-in-picture <allowlist>;
+```
+Feature-Policy: picture-in-picture <allowlist>;
+```
 
 - \<allowlist>
   - : A list of origins for which the feature is allowed. See [`Feature-Policy`](/en-US/docs/Web/HTTP/Headers/Feature-Policy#syntax).
diff --git a/files/en-us/web/http/headers/feature-policy/publickey-credentials-get/index.md b/files/en-us/web/http/headers/feature-policy/publickey-credentials-get/index.md
index fc94b180e55feeb..3549b284eb97981 100644
--- a/files/en-us/web/http/headers/feature-policy/publickey-credentials-get/index.md
+++ b/files/en-us/web/http/headers/feature-policy/publickey-credentials-get/index.md
@@ -18,7 +18,9 @@ When this policy is enabled, any attempt to query public key credentials will re
 
 ## Syntax
 
-    Feature-Policy: publickey-credentials-get <allowlist>;
+```
+Feature-Policy: publickey-credentials-get <allowlist>;
+```
 
 - \<allowlist>
   - : A list of origins for which the feature is allowed. See [`Feature-Policy`](/en-US/docs/Web/HTTP/Headers/Feature-Policy#syntax).
diff --git a/files/en-us/web/http/headers/feature-policy/screen-wake-lock/index.md b/files/en-us/web/http/headers/feature-policy/screen-wake-lock/index.md
index cad64577b71c29f..770de48b0cc09b9 100644
--- a/files/en-us/web/http/headers/feature-policy/screen-wake-lock/index.md
+++ b/files/en-us/web/http/headers/feature-policy/screen-wake-lock/index.md
@@ -19,7 +19,9 @@ The HTTP {{HTTPHeader("Feature-Policy")}} header **`screen-wake-lock`** directiv
 
 ## Syntax
 
-    Feature-Policy: screen-wake-lock <allowlist>;
+```
+Feature-Policy: screen-wake-lock <allowlist>;
+```
 
 - \<allowlist>
   - : A list of origins for which the feature is allowed. See [`Feature-Policy`](/en-US/docs/Web/HTTP/Headers/Feature-Policy#syntax).
diff --git a/files/en-us/web/http/headers/feature-policy/sync-xhr/index.md b/files/en-us/web/http/headers/feature-policy/sync-xhr/index.md
index f7a57f80127b6e1..9ff446df85f3a38 100644
--- a/files/en-us/web/http/headers/feature-policy/sync-xhr/index.md
+++ b/files/en-us/web/http/headers/feature-policy/sync-xhr/index.md
@@ -17,7 +17,9 @@ The HTTP {{HTTPHeader("Feature-Policy")}} header `sync-xhr` directive controls
 
 ## Syntax
 
-    Feature-Policy: sync-xhr <allowlist>;
+```
+Feature-Policy: sync-xhr <allowlist>;
+```
 
 - \<allowlist>
   - : A list of origins for which the feature is allowed. See [`Feature-Policy`](/en-US/docs/Web/HTTP/Headers/Feature-Policy#syntax).
diff --git a/files/en-us/web/http/headers/feature-policy/unoptimized-images/index.md b/files/en-us/web/http/headers/feature-policy/unoptimized-images/index.md
index b42cfccf6e229b4..a57dd86602cc614 100644
--- a/files/en-us/web/http/headers/feature-policy/unoptimized-images/index.md
+++ b/files/en-us/web/http/headers/feature-policy/unoptimized-images/index.md
@@ -17,7 +17,9 @@ The HTTP {{HTTPHeader("Feature-Policy")}} header `unoptimized-images` directive
 
 ## Syntax
 
-    Feature-Policy: unoptimized-images <allowlist>;
+```
+Feature-Policy: unoptimized-images <allowlist>;
+```
 
 - \<allowlist>
   - : A list of origins for which the feature is allowed. See [`Feature-Policy`](/en-US/docs/Web/HTTP/Headers/Feature-Policy#syntax).
diff --git a/files/en-us/web/http/headers/feature-policy/unsized-media/index.md b/files/en-us/web/http/headers/feature-policy/unsized-media/index.md
index 70767872d4a25cb..f591291805cd08f 100644
--- a/files/en-us/web/http/headers/feature-policy/unsized-media/index.md
+++ b/files/en-us/web/http/headers/feature-policy/unsized-media/index.md
@@ -18,7 +18,9 @@ This restriction solves "layout instability" problem caused by providing default
 
 ## Syntax
 
-    Feature-Policy: unsized-media <allowlist>;
+```
+Feature-Policy: unsized-media <allowlist>;
+```
 
 - \<allowlist>
   - : A list of origins for which the feature is allowed. See [`Feature-Policy`](/en-US/docs/Web/HTTP/Headers/Feature-Policy#syntax).
diff --git a/files/en-us/web/http/headers/feature-policy/usb/index.md b/files/en-us/web/http/headers/feature-policy/usb/index.md
index 9c2db489f6e52c7..14878159a9e84b8 100644
--- a/files/en-us/web/http/headers/feature-policy/usb/index.md
+++ b/files/en-us/web/http/headers/feature-policy/usb/index.md
@@ -17,7 +17,9 @@ The HTTP {{HTTPHeader("Feature-Policy")}} header `usb` directive controls wheth
 
 ## Syntax
 
-    Feature-Policy: usb <allowlist>;
+```
+Feature-Policy: usb <allowlist>;
+```
 
 - \<allowlist>
   - : A list of origins for which the feature is allowed. See [`Feature-Policy`](/en-US/docs/Web/HTTP/Headers/Feature-Policy#syntax).
diff --git a/files/en-us/web/http/headers/feature-policy/vibrate/index.md b/files/en-us/web/http/headers/feature-policy/vibrate/index.md
index 35232f3e54e9f09..5fad3332cd94f38 100644
--- a/files/en-us/web/http/headers/feature-policy/vibrate/index.md
+++ b/files/en-us/web/http/headers/feature-policy/vibrate/index.md
@@ -18,7 +18,9 @@ The HTTP {{HTTPHeader("Feature-Policy")}} header `vibrate` {{deprecated_inline}}
 
 ## Syntax
 
-    Feature-Policy: vibrate <allowlist>;
+```
+Feature-Policy: vibrate <allowlist>;
+```
 
 - \<allowlist>
   - : A list of origins for which the feature is allowed. See [`Feature-Policy`](/en-US/docs/Web/HTTP/Headers/Feature-Policy#syntax).
diff --git a/files/en-us/web/http/headers/feature-policy/vr/index.md b/files/en-us/web/http/headers/feature-policy/vr/index.md
index cf725450e783e8f..e7d7a608976329b 100644
--- a/files/en-us/web/http/headers/feature-policy/vr/index.md
+++ b/files/en-us/web/http/headers/feature-policy/vr/index.md
@@ -21,7 +21,9 @@ The HTTP {{HTTPHeader("Feature-Policy")}} header `vr` directive controls whether
 
 ## Syntax
 
-    Feature-Policy: vr <allowlist>;
+```
+Feature-Policy: vr <allowlist>;
+```
 
 - \<allowlist>
   - : A list of origins for which the feature is allowed. See [`Feature-Policy`](/en-US/docs/Web/HTTP/Headers/Feature-Policy#syntax).
diff --git a/files/en-us/web/http/headers/feature-policy/web-share/index.md b/files/en-us/web/http/headers/feature-policy/web-share/index.md
index e740ebe77ede035..9c73799b07fbaad 100644
--- a/files/en-us/web/http/headers/feature-policy/web-share/index.md
+++ b/files/en-us/web/http/headers/feature-policy/web-share/index.md
@@ -14,7 +14,9 @@ The HTTP {{HTTPHeader('Feature-Policy')}} header `web-share` directive controls
 
 ## Syntax
 
-    Feature-Policy: web-share <allowlist>;
+```
+Feature-Policy: web-share <allowlist>;
+```
 
 - \<allowlist>
   - : A list of origins for which the feature is allowed. See [`Feature-Policy`](/en-US/docs/Web/HTTP/Headers/Feature-Policy#syntax).
diff --git a/files/en-us/web/http/headers/feature-policy/xr-spatial-tracking/index.md b/files/en-us/web/http/headers/feature-policy/xr-spatial-tracking/index.md
index ef8589865de5a47..c716ed8f1800b3d 100644
--- a/files/en-us/web/http/headers/feature-policy/xr-spatial-tracking/index.md
+++ b/files/en-us/web/http/headers/feature-policy/xr-spatial-tracking/index.md
@@ -17,7 +17,9 @@ The HTTP {{HTTPHeader("Feature-Policy")}} header `xr-spatial-tracking` directive
 
 ## Syntax
 
-    Feature-Policy: xr-spatial-tracking <allowlist>;
+```
+Feature-Policy: xr-spatial-tracking <allowlist>;
+```
 
 - \<allowlist>
   - : A list of origins for which the feature is allowed. See [`Feature-Policy`](/en-US/docs/Web/HTTP/Headers/Feature-Policy#syntax).
diff --git a/files/en-us/web/http/headers/forwarded/index.md b/files/en-us/web/http/headers/forwarded/index.md
index 58e34072ef57662..a7a304afd512774 100644
--- a/files/en-us/web/http/headers/forwarded/index.md
+++ b/files/en-us/web/http/headers/forwarded/index.md
@@ -32,7 +32,7 @@ This header is used for debugging, statistics, and generating location-dependent
 
 ## Syntax
 
-```html
+```
 Forwarded: by=<identifier>;for=<identifier>;host=<host>;proto=<http|https>
 ```
 
@@ -59,26 +59,30 @@ Forwarded: by=<identifier>;for=<identifier>;host=<host>;proto=<http|https>
 
 ### Using the `Forwarded` header
 
-    Forwarded: for="_mdn"
+```
+Forwarded: for="_mdn"
 
-    # case insensitive
-    Forwarded: For="[2001:db8:cafe::17]:4711"
+# case insensitive
+Forwarded: For="[2001:db8:cafe::17]:4711"
 
-    # separated by semicolon
-    Forwarded: for=192.0.2.60;proto=http;by=203.0.113.43
+# separated by semicolon
+Forwarded: for=192.0.2.60;proto=http;by=203.0.113.43
 
-    # multiple values can be appended using a comma
-    Forwarded: for=192.0.2.43, for=198.51.100.17
+# multiple values can be appended using a comma
+Forwarded: for=192.0.2.43, for=198.51.100.17
+```
 
 ### Transitioning from `X-Forwarded-For` to `Forwarded`
 
 If your application, server, or proxy supports the standardized `Forwarded` header, the {{HTTPHeader("X-Forwarded-For")}} header can be replaced. Note that IPv6 address are quoted and enclosed in square brackets in `Forwarded`.
 
-    X-Forwarded-For: 123.34.567.89
-    Forwarded: for=123.34.567.89
+```
+X-Forwarded-For: 123.34.567.89
+Forwarded: for=123.34.567.89
 
-    X-Forwarded-For: 192.0.2.43, "[2001:db8:cafe::17]"
-    Forwarded: for=192.0.2.43, for="[2001:db8:cafe::17]"
+X-Forwarded-For: 192.0.2.43, "[2001:db8:cafe::17]"
+Forwarded: for=192.0.2.43, for="[2001:db8:cafe::17]"
+```
 
 ## Specifications
 
diff --git a/files/en-us/web/http/headers/from/index.md b/files/en-us/web/http/headers/from/index.md
index 4628109ce3f65fb..3cc2118078424bf 100644
--- a/files/en-us/web/http/headers/from/index.md
+++ b/files/en-us/web/http/headers/from/index.md
@@ -33,7 +33,7 @@ robot is sending excessive, unwanted, or invalid requests.
 
 ## Syntax
 
-```html
+```
 From: <email>
 ```
 
@@ -44,7 +44,9 @@ From: <email>
 
 ## Examples
 
-    From: webmaster@example.org
+```
+From: webmaster@example.org
+```
 
 ## Specifications
 
diff --git a/files/en-us/web/http/headers/host/index.md b/files/en-us/web/http/headers/host/index.md
index 299f62dbc7795b0..d8c30ad6b7a4435 100644
--- a/files/en-us/web/http/headers/host/index.md
+++ b/files/en-us/web/http/headers/host/index.md
@@ -34,7 +34,7 @@ message that lacks a `Host` header field or that contains more than one.
 
 ## Syntax
 
-```html
+```
 Host: <host>:<port>
 ```
 
@@ -47,7 +47,9 @@ Host: <host>:<port>
 
 ## Examples
 
-    Host: developer.mozilla.org
+```
+Host: developer.mozilla.org
+```
 
 ## Specifications
 
diff --git a/files/en-us/web/http/headers/if-match/index.md b/files/en-us/web/http/headers/if-match/index.md
index 2e4b6b46721260e..90fe0828b341a4f 100644
--- a/files/en-us/web/http/headers/if-match/index.md
+++ b/files/en-us/web/http/headers/if-match/index.md
@@ -50,7 +50,7 @@ There are two common use cases:
 
 ## Syntax
 
-```html
+```
 If-Match: <etag_value>
 If-Match: <etag_value>, <etag_value>, …
 ```
@@ -68,11 +68,13 @@ If-Match: <etag_value>, <etag_value>, …
 
 ## Examples
 
+```
     If-Match: "bfc13a64729c4290ef5b2c2730249c88ca92d82d"
 
     If-Match: "67ab43", "54ed21", "7892dd"
 
     If-Match: *
+```
 
 ## Specifications
 
diff --git a/files/en-us/web/http/headers/if-modified-since/index.md b/files/en-us/web/http/headers/if-modified-since/index.md
index 6ba58bb5bdd50c1..d3de1c27e0d38b1 100644
--- a/files/en-us/web/http/headers/if-modified-since/index.md
+++ b/files/en-us/web/http/headers/if-modified-since/index.md
@@ -41,7 +41,7 @@ The most common use case is to update a cached entity that has no associated
 
 ## Syntax
 
-```html
+```
 If-Modified-Since: <day-name>, <day> <month> <year> <hour>:<minute>:<second> GMT
 ```
 
@@ -67,7 +67,9 @@ If-Modified-Since: <day-name>, <day> <month> <year> <hour>:<minute>:<second> GMT
 
 ## Examples
 
-    If-Modified-Since: Wed, 21 Oct 2015 07:28:00 GMT
+```
+If-Modified-Since: Wed, 21 Oct 2015 07:28:00 GMT
+```
 
 ## Specifications
 
diff --git a/files/en-us/web/http/headers/if-none-match/index.md b/files/en-us/web/http/headers/if-none-match/index.md
index c0d953ca493610d..9a84e1bdcd85a0a 100644
--- a/files/en-us/web/http/headers/if-none-match/index.md
+++ b/files/en-us/web/http/headers/if-none-match/index.md
@@ -39,7 +39,7 @@ There are two common use cases:
 
 ## Syntax
 
-```html
+```
 If-None-Match: "<etag_value>"
 If-None-Match: "<etag_value>", "<etag_value>", …
 If-None-Match: *
@@ -54,11 +54,13 @@ If-None-Match: *
 
 ## Examples
 
+```
     If-None-Match: "bfc13a64729c4290ef5b2c2730249c88ca92d82d"
 
     If-None-Match: W/"67ab43", "54ed21", "7892dd"
 
     If-None-Match: *
+```
 
 ## Specifications
 
diff --git a/files/en-us/web/http/headers/if-range/index.md b/files/en-us/web/http/headers/if-range/index.md
index 065e22add39519e..11c2ac5e89ba74b 100644
--- a/files/en-us/web/http/headers/if-range/index.md
+++ b/files/en-us/web/http/headers/if-range/index.md
@@ -39,7 +39,7 @@ has not been modified since the last fragment has been received.
 
 ## Syntax
 
-```html
+```
 If-Range: <day-name>, <day> <month> <year> <hour>:<minute>:<second> GMT
 If-Range: <etag>
 ```
@@ -71,7 +71,9 @@ If-Range: <etag>
 
 ## Examples
 
-    If-Range: Wed, 21 Oct 2015 07:28:00 GMT
+```
+If-Range: Wed, 21 Oct 2015 07:28:00 GMT
+```
 
 ## Specifications
 
diff --git a/files/en-us/web/http/headers/if-unmodified-since/index.md b/files/en-us/web/http/headers/if-unmodified-since/index.md
index 388e4df4f34a034..78141ad0f0f1f09 100644
--- a/files/en-us/web/http/headers/if-unmodified-since/index.md
+++ b/files/en-us/web/http/headers/if-unmodified-since/index.md
@@ -41,7 +41,7 @@ There are two common use cases:
 
 ## Syntax
 
-```html
+```
 If-Unmodified-Since: <day-name>, <day> <month> <year> <hour>:<minute>:<second> GMT
 ```
 
@@ -67,7 +67,9 @@ If-Unmodified-Since: <day-name>, <day> <month> <year> <hour>:<minute>:<second> G
 
 ## Examples
 
-    If-Unmodified-Since: Wed, 21 Oct 2015 07:28:00 GMT
+```
+If-Unmodified-Since: Wed, 21 Oct 2015 07:28:00 GMT
+```
 
 ## Specifications
 
diff --git a/files/en-us/web/http/headers/keep-alive/index.md b/files/en-us/web/http/headers/keep-alive/index.md
index 7bed22ca0b9d491..a32c0ce396696c4 100644
--- a/files/en-us/web/http/headers/keep-alive/index.md
+++ b/files/en-us/web/http/headers/keep-alive/index.md
@@ -35,7 +35,7 @@ The **`Keep-Alive`** general header allows the sender to hint about how the conn
 
 ## Syntax
 
-```html
+```
 Keep-Alive: parameters
 ```
 
@@ -52,16 +52,18 @@ Keep-Alive: parameters
 
 A response containing a `Keep-Alive` header:
 
-    HTTP/1.1 200 OK
-    Connection: Keep-Alive
-    Content-Encoding: gzip
-    Content-Type: text/html; charset=utf-8
-    Date: Thu, 11 Aug 2016 15:23:13 GMT
-    Keep-Alive: timeout=5, max=1000
-    Last-Modified: Mon, 25 Jul 2016 04:32:39 GMT
-    Server: Apache
-
-    (body)
+```
+HTTP/1.1 200 OK
+Connection: Keep-Alive
+Content-Encoding: gzip
+Content-Type: text/html; charset=utf-8
+Date: Thu, 11 Aug 2016 15:23:13 GMT
+Keep-Alive: timeout=5, max=1000
+Last-Modified: Mon, 25 Jul 2016 04:32:39 GMT
+Server: Apache
+
+(body)
+```
 
 ## Specifications
 
diff --git a/files/en-us/web/http/headers/large-allocation/index.md b/files/en-us/web/http/headers/large-allocation/index.md
index 5efd6ba83cca979..f703c7301892b6b 100644
--- a/files/en-us/web/http/headers/large-allocation/index.md
+++ b/files/en-us/web/http/headers/large-allocation/index.md
@@ -38,7 +38,7 @@ a dedicated process for the to-be-loaded document, for example.
 
 ## Syntax
 
-```html
+```
 Large-Allocation: 0
 Large-Allocation: <megabytes>
 ```
@@ -53,8 +53,10 @@ Large-Allocation: <megabytes>
 
 ## Examples
 
-    Large-Allocation: 0
-    Large-Allocation: 500
+```
+Large-Allocation: 0
+Large-Allocation: 500
+```
 
 ## Troubleshooting errors
 
diff --git a/files/en-us/web/http/headers/last-modified/index.md b/files/en-us/web/http/headers/last-modified/index.md
index 9001eadaf4851c0..6ed5d9f289e9c87 100644
--- a/files/en-us/web/http/headers/last-modified/index.md
+++ b/files/en-us/web/http/headers/last-modified/index.md
@@ -38,7 +38,7 @@ headers make use of this field.
 
 ## Syntax
 
-```html
+```
 Last-Modified: <day-name>, <day> <month> <year> <hour>:<minute>:<second> GMT
 ```
 
@@ -64,7 +64,9 @@ Last-Modified: <day-name>, <day> <month> <year> <hour>:<minute>:<second> GMT
 
 ## Examples
 
-    Last-Modified: Wed, 21 Oct 2015 07:28:00 GMT
+```
+Last-Modified: Wed, 21 Oct 2015 07:28:00 GMT
+```
 
 ## Specifications
 
diff --git a/files/en-us/web/http/headers/link/index.md b/files/en-us/web/http/headers/link/index.md
index 66e81b6db920734..2b7728f04ae1933 100644
--- a/files/en-us/web/http/headers/link/index.md
+++ b/files/en-us/web/http/headers/link/index.md
@@ -18,8 +18,8 @@ The HTTP **`Link`** entity-header field provides a means for serialising one or
 
 ## Syntax
 
-```html
-Link: < uri-reference >; param1=value1; param2="value2"
+```
+Link: <uri-reference>; param1=value1; param2="value2"
 ```
 
 - `<uri-reference>`
@@ -33,11 +33,11 @@ The link header contains parameters, which are separated with `;` and are equiva
 
 The URI (absolute or relative) must be enclosed between `<` and `>`:
 
-```plain example-good
+```example-good
 Link: <https://example.com>; rel="preconnect"
 ```
 
-```plain example-bad
+```example-bad
 Link: https://bad.example; rel="preconnect"
 ```
 
@@ -45,7 +45,9 @@ Link: https://bad.example; rel="preconnect"
 
 You can specify multiple links separated by commas, for example:
 
-    Link: <https://one.example.com>; rel="preconnect", <https://two.example.com>; rel="preconnect", <https://three.example.com>; rel="preconnect"
+```
+Link: <https://one.example.com>; rel="preconnect", <https://two.example.com>; rel="preconnect", <https://three.example.com>; rel="preconnect"
+```
 
 ## Specifications
 
diff --git a/files/en-us/web/http/headers/location/index.md b/files/en-us/web/http/headers/location/index.md
index 1f5dd6cc39bce50..d3e120dd1ea7f1b 100644
--- a/files/en-us/web/http/headers/location/index.md
+++ b/files/en-us/web/http/headers/location/index.md
@@ -53,7 +53,7 @@ with the entity returned.
 
 ## Syntax
 
-```html
+```
 Location: <url>
 ```
 
@@ -64,7 +64,9 @@ Location: <url>
 
 ## Examples
 
-    Location: /index.html
+```
+Location: /index.html
+```
 
 ## Specifications
 
diff --git a/files/en-us/web/http/headers/nel/index.md b/files/en-us/web/http/headers/nel/index.md
index f31fb90de91f9b7..3c0971401c9bb56 100644
--- a/files/en-us/web/http/headers/nel/index.md
+++ b/files/en-us/web/http/headers/nel/index.md
@@ -29,7 +29,7 @@ The HTTP **`NEL`** response header is used to configure network request logging.
 
 ## Syntax
 
-```html
+```
 NEL: { "report_to": "name_of_reporting_group", "max_age": 12345, "include_subdomains": false, "success_fraction": 0.0, "failure_fraction": 1.0 }
 ```
 
diff --git a/files/en-us/web/http/headers/origin/index.md b/files/en-us/web/http/headers/origin/index.md
index dd347a4fea3aa01..54e3cb0332799ee 100644
--- a/files/en-us/web/http/headers/origin/index.md
+++ b/files/en-us/web/http/headers/origin/index.md
@@ -35,7 +35,7 @@ The **`Origin`** request header indicates where a request originates from. It do
 
 ## Syntax
 
-```html
+```
 Origin: null
 Origin: <scheme> "://" <hostname> [ ":" <port> ]
 ```
@@ -51,7 +51,9 @@ Origin: <scheme> "://" <hostname> [ ":" <port> ]
 
 ## Examples
 
-    Origin: https://developer.mozilla.org
+```
+Origin: https://developer.mozilla.org
+```
 
 ## Specifications
 
diff --git a/files/en-us/web/http/headers/pragma/index.md b/files/en-us/web/http/headers/pragma/index.md
index 0c19623f0cc7af4..54e6bd9786bc069 100644
--- a/files/en-us/web/http/headers/pragma/index.md
+++ b/files/en-us/web/http/headers/pragma/index.md
@@ -49,7 +49,7 @@ chain. It is used for backwards compatibility with HTTP/1.0 caches where the
 
 ## Syntax
 
-```html
+```
 Pragma: no-cache
 ```
 
@@ -61,7 +61,9 @@ Pragma: no-cache
 
 ## Examples
 
-    Pragma: no-cache
+```
+Pragma: no-cache
+```
 
 ## Specifications
 
diff --git a/files/en-us/web/http/headers/proxy-authenticate/index.md b/files/en-us/web/http/headers/proxy-authenticate/index.md
index 7cbe06ef71380f3..ed087027c8ff756 100644
--- a/files/en-us/web/http/headers/proxy-authenticate/index.md
+++ b/files/en-us/web/http/headers/proxy-authenticate/index.md
@@ -34,7 +34,7 @@ The `Proxy-Authenticate` header is sent along with a {{HTTPStatus("407")}}
 
 ## Syntax
 
-```html
+```
 Proxy-Authenticate: <type> realm=<realm>
 ```
 
@@ -51,9 +51,11 @@ Proxy-Authenticate: <type> realm=<realm>
 
 ## Examples
 
-    Proxy-Authenticate: Basic
+```
+Proxy-Authenticate: Basic
 
-    Proxy-Authenticate: Basic realm="Access to the internal site"
+Proxy-Authenticate: Basic realm="Access to the internal site"
+```
 
 ## Specifications
 
diff --git a/files/en-us/web/http/headers/proxy-authorization/index.md b/files/en-us/web/http/headers/proxy-authorization/index.md
index 09769a67b6d719d..7fbaf05d6ac83c2 100644
--- a/files/en-us/web/http/headers/proxy-authorization/index.md
+++ b/files/en-us/web/http/headers/proxy-authorization/index.md
@@ -30,7 +30,7 @@ and the {{HTTPHeader("Proxy-Authenticate")}} header.
 
 ## Syntax
 
-```html
+```
 Proxy-Authorization: <type> <credentials>
 ```
 
@@ -57,7 +57,9 @@ Proxy-Authorization: <type> <credentials>
 
 ## Examples
 
-    Proxy-Authorization: Basic YWxhZGRpbjpvcGVuc2VzYW1l
+```
+Proxy-Authorization: Basic YWxhZGRpbjpvcGVuc2VzYW1l
+```
 
 ## Specifications
 
diff --git a/files/en-us/web/http/headers/public-key-pins-report-only/index.md b/files/en-us/web/http/headers/public-key-pins-report-only/index.md
index 37a525f4c438a8f..1d71567bc6ec0ea 100644
--- a/files/en-us/web/http/headers/public-key-pins-report-only/index.md
+++ b/files/en-us/web/http/headers/public-key-pins-report-only/index.md
@@ -42,7 +42,7 @@ article.
 
 ## Syntax
 
-```html
+```
 Public-Key-Pins-Report-Only: pin-sha256="<pin-value>";
                              max-age=<expire-time>;
                              includeSubDomains;
@@ -68,11 +68,13 @@ Public-Key-Pins-Report-Only: pin-sha256="<pin-value>";
 
 ## Example
 
-    Public-Key-Pins-Report-Only:
-      pin-sha256="cUPcTAZWKaASuYWhhneDttWpY3oBAkE3h2+soZS7sWs=";
-      pin-sha256="M8HztCzM3elUxkcjR2S5P4hhyBNf6lHkmjAHKhpGPWE=";
-      includeSubDomains;
-      report-uri="https://www.example.org/hpkp-report"
+```
+Public-Key-Pins-Report-Only:
+  pin-sha256="cUPcTAZWKaASuYWhhneDttWpY3oBAkE3h2+soZS7sWs=";
+  pin-sha256="M8HztCzM3elUxkcjR2S5P4hhyBNf6lHkmjAHKhpGPWE=";
+  includeSubDomains;
+  report-uri="https://www.example.org/hpkp-report"
+```
 
 In this example,
 **pin-sha256="cUPcTAZWKaASuYWhhneDttWpY3oBAkE3h2+soZS7sWs="** pins the
diff --git a/files/en-us/web/http/headers/public-key-pins/index.md b/files/en-us/web/http/headers/public-key-pins/index.md
index 49fc6f36f00a9f7..630a5e7318b2844 100644
--- a/files/en-us/web/http/headers/public-key-pins/index.md
+++ b/files/en-us/web/http/headers/public-key-pins/index.md
@@ -41,7 +41,7 @@ Public Key Pinning](/en-US/docs/Web/HTTP/Public_Key_Pinning) article.
 
 ## Syntax
 
-```html
+```
 Public-Key-Pins: pin-sha256="<pin-value>";
                  max-age=<expire-time>;
                  includeSubDomains;
@@ -71,11 +71,13 @@ Public-Key-Pins: pin-sha256="<pin-value>";
 > if used incorrectly!
 > The use of backup certificates and/or pinning the CA certificate is recommended.
 
-    Public-Key-Pins:
-      pin-sha256="cUPcTAZWKaASuYWhhneDttWpY3oBAkE3h2+soZS7sWs=";
-      pin-sha256="M8HztCzM3elUxkcjR2S5P4hhyBNf6lHkmjAHKhpGPWE=";
-      max-age=5184000; includeSubDomains;
-      report-uri="https://www.example.org/hpkp-report"
+```
+Public-Key-Pins:
+  pin-sha256="cUPcTAZWKaASuYWhhneDttWpY3oBAkE3h2+soZS7sWs=";
+  pin-sha256="M8HztCzM3elUxkcjR2S5P4hhyBNf6lHkmjAHKhpGPWE=";
+  max-age=5184000; includeSubDomains;
+  report-uri="https://www.example.org/hpkp-report"
+```
 
 In this example,
 **pin-sha256="cUPcTAZWKaASuYWhhneDttWpY3oBAkE3h2+soZS7sWs="** pins the
diff --git a/files/en-us/web/http/headers/range/index.md b/files/en-us/web/http/headers/range/index.md
index ff079235962dc53..31fb833a57ae1f8 100644
--- a/files/en-us/web/http/headers/range/index.md
+++ b/files/en-us/web/http/headers/range/index.md
@@ -28,7 +28,7 @@ The **`Range`** HTTP request header indicates the part of a document that the se
 
 ## Syntax
 
-```html
+```
 Range: <unit>=<range-start>-
 Range: <unit>=<range-start>-<range-end>
 Range: <unit>=<range-start>-<range-end>, <range-start>-<range-end>
@@ -51,11 +51,15 @@ Range: <unit>=-<suffix-length>
 
 Requesting three ranges from the file.
 
-    Range: bytes=200-1000, 2000-6576, 19000-
+```
+Range: bytes=200-1000, 2000-6576, 19000-
+```
 
 Requesting the first 500 and last 500 bytes of the file. The request may be rejected by the server if the ranges overlap.
 
-    Range: bytes=0-499, -500
+```
+Range: bytes=0-499, -500
+```
 
 ## Specifications
 
diff --git a/files/en-us/web/http/headers/referer/index.md b/files/en-us/web/http/headers/referer/index.md
index 4f7ee0bcb7fcf95..0c221fba84424f1 100644
--- a/files/en-us/web/http/headers/referer/index.md
+++ b/files/en-us/web/http/headers/referer/index.md
@@ -34,7 +34,7 @@ The `Referer` header may not contain URL fragments (i.e. "#section") or "usernam
 
 ## Syntax
 
-```html
+```
 Referer: <url>
 ```
 
@@ -45,9 +45,11 @@ Referer: <url>
 
 ## Examples
 
-    Referer: https://developer.mozilla.org/en-US/docs/Web/JavaScript
-    Referer: https://example.com/page?q=123
-    Referer: https://example.com/
+```
+Referer: https://developer.mozilla.org/en-US/docs/Web/JavaScript
+Referer: https://example.com/page?q=123
+Referer: https://example.com/
+```
 
 ## Specifications
 
diff --git a/files/en-us/web/http/headers/referrer-policy/index.md b/files/en-us/web/http/headers/referrer-policy/index.md
index 68636d6b1bfb976..1ef1f142ab26502 100644
--- a/files/en-us/web/http/headers/referrer-policy/index.md
+++ b/files/en-us/web/http/headers/referrer-policy/index.md
@@ -31,7 +31,7 @@ The **`Referrer-Policy`** {{glossary("HTTP header")}} controls how much [referre
 
 ## Syntax
 
-```html
+```
 Referrer-Policy: no-referrer
 Referrer-Policy: no-referrer-when-downgrade
 Referrer-Policy: origin
@@ -130,7 +130,7 @@ CSS can fetch resources referenced from stylesheets. These resources follow a re
 | https://example.com/page | https://mozilla.org           | https://example.com/     |
 | https://example.com/page | **http**://example.com/page   | https://example.com/     |
 
-### >`same-origin`
+### `same-origin`
 
 | From document            | Navigation to                 | Referrer used            |
 | ------------------------ | ----------------------------- | ------------------------ |
@@ -163,7 +163,9 @@ CSS can fetch resources referenced from stylesheets. These resources follow a re
 
 If you want to specify a fallback policy in any case the desired policy hasn't got wide enough browser support, use a comma-separated list with the desired policy specified last:
 
-    Referrer-Policy: no-referrer, strict-origin-when-cross-origin
+```
+Referrer-Policy: no-referrer, strict-origin-when-cross-origin
+```
 
 In the above scenario, `no-referrer` will only be used if `strict-origin-when-cross-origin` is not supported by the browser.
 
diff --git a/files/en-us/web/http/headers/retry-after/index.md b/files/en-us/web/http/headers/retry-after/index.md
index e4ada5166056eea..c1441078d46b58d 100644
--- a/files/en-us/web/http/headers/retry-after/index.md
+++ b/files/en-us/web/http/headers/retry-after/index.md
@@ -38,7 +38,7 @@ this header is used:
 
 ## Syntax
 
-```html
+```
 Retry-After: <http-date>
 Retry-After: <delay-seconds>
 ```
@@ -62,8 +62,10 @@ inconsistent. However, some crawlers and spiders, like the Googlebot, honor the
 {{HTTPStatus(503)}} (Service Unavailable) response, so that search engines will keep
 indexing your site when the downtime is over.
 
-    Retry-After: Wed, 21 Oct 2015 07:28:00 GMT
-    Retry-After: 120
+```
+Retry-After: Wed, 21 Oct 2015 07:28:00 GMT
+Retry-After: 120
+```
 
 ## Specifications
 
@@ -75,7 +77,6 @@ indexing your site when the downtime is over.
 
 ## See also
 
-- [Google
-  Webmaster blog: How to deal with planned site downtime](https://webmasters.googleblog.com/2011/01/how-to-deal-with-planned-site-downtime.html)
+- [Google Webmaster blog: How to deal with planned site downtime](https://webmasters.googleblog.com/2011/01/how-to-deal-with-planned-site-downtime.html)
 - {{HTTPStatus(503)}} (Service Unavailable)
 - {{HTTPStatus(301)}} (Moved Permanently)
diff --git a/files/en-us/web/http/headers/rtt/index.md b/files/en-us/web/http/headers/rtt/index.md
index 3fb9209949cecc0..38be545417e5d22 100644
--- a/files/en-us/web/http/headers/rtt/index.md
+++ b/files/en-us/web/http/headers/rtt/index.md
@@ -39,7 +39,9 @@ The hint allows a server to choose what information is sent based on the network
 
 ## Syntax
 
-    RTT: <number>
+```
+RTT: <number>
+```
 
 ## Directives
 
@@ -50,11 +52,15 @@ The hint allows a server to choose what information is sent based on the network
 
 A server first needs to opt in to receive the `RTT` header by sending the {{HTTPHeader("Accept-CH")}} response header containing `RTT`.
 
-    Accept-CH: RTT
+```
+Accept-CH: RTT
+```
 
 Then on subsequent requests the client might send an `RTT` header back:
 
-    RTT: 125
+```
+RTT: 125
+```
 
 ## Specifications
 
diff --git a/files/en-us/web/http/headers/save-data/index.md b/files/en-us/web/http/headers/save-data/index.md
index 47155d7de8a9152..829727242c91f1a 100644
--- a/files/en-us/web/http/headers/save-data/index.md
+++ b/files/en-us/web/http/headers/save-data/index.md
@@ -52,7 +52,7 @@ different markup and styling, disabled polling and automatic updates, and so on.
 
 ## Directives
 
-- `<sd-token>`
+- \<sd-token>
   - : A value indicating whether the client wants to opt in to reduced data
     usage mode. `on` indicates yes, while `off` (the default)
     indicates no.
@@ -67,37 +67,44 @@ from cellular to Wi-Fi]).
 ### With `Save-Data: on`
 
 Request:
-
-    GET /image.jpg HTTP/1.0
-    Host: example.com
-    Save-Data: on
+```
+GET /image.jpg HTTP/1.0
+Host: example.com
+Save-Data: on
+```
 
 Response:
 
-    HTTP/1.0 200 OK
-    Content-Length: 102832
-    Vary: Accept-Encoding, Save-Data
-    Cache-Control: public, max-age=31536000
-    Content-Type: image/jpeg
+```
+HTTP/1.0 200 OK
+Content-Length: 102832
+Vary: Accept-Encoding, Save-Data
+Cache-Control: public, max-age=31536000
+Content-Type: image/jpeg
 
-    [...]
+[...]
+```
 
 ### Without `Save-Data`
 
 Request:
 
-    GET /image.jpg HTTP/1.0
-    Host: example.com
+```
+GET /image.jpg HTTP/1.0
+Host: example.com
+```
 
 Response:
 
-    HTTP/1.0 200 OK
-    Content-Length: 481770
-    Vary: Accept-Encoding, Save-Data
-    Cache-Control: public, max-age=31536000
-    Content-Type: image/jpeg
+```
+HTTP/1.0 200 OK
+Content-Length: 481770
+Vary: Accept-Encoding, Save-Data
+Cache-Control: public, max-age=31536000
+Content-Type: image/jpeg
 
-    [...]
+[...]
+```
 
 ## Specifications
 
diff --git a/files/en-us/web/http/headers/sec-fetch-dest/index.md b/files/en-us/web/http/headers/sec-fetch-dest/index.md
index 64dcb502a9bede4..f9974ecf90c2958 100644
--- a/files/en-us/web/http/headers/sec-fetch-dest/index.md
+++ b/files/en-us/web/http/headers/sec-fetch-dest/index.md
@@ -37,27 +37,29 @@ This allows servers determine whether to service a request based on whether it i
 
 ## Syntax
 
-    Sec-Fetch-Dest: audio
-    Sec-Fetch-Dest: audioworklet
-    Sec-Fetch-Dest: document
-    Sec-Fetch-Dest: embed
-    Sec-Fetch-Dest: empty
-    Sec-Fetch-Dest: font
-    Sec-Fetch-Dest: frame
-    Sec-Fetch-Dest: iframe
-    Sec-Fetch-Dest: image
-    Sec-Fetch-Dest: manifest
-    Sec-Fetch-Dest: object
-    Sec-Fetch-Dest: paintworklet
-    Sec-Fetch-Dest: report
-    Sec-Fetch-Dest: script
-    Sec-Fetch-Dest: serviceworker
-    Sec-Fetch-Dest: sharedworker
-    Sec-Fetch-Dest: style
-    Sec-Fetch-Dest: track
-    Sec-Fetch-Dest: video
-    Sec-Fetch-Dest: worker
-    Sec-Fetch-Dest: xslt
+```
+Sec-Fetch-Dest: audio
+Sec-Fetch-Dest: audioworklet
+Sec-Fetch-Dest: document
+Sec-Fetch-Dest: embed
+Sec-Fetch-Dest: empty
+Sec-Fetch-Dest: font
+Sec-Fetch-Dest: frame
+Sec-Fetch-Dest: iframe
+Sec-Fetch-Dest: image
+Sec-Fetch-Dest: manifest
+Sec-Fetch-Dest: object
+Sec-Fetch-Dest: paintworklet
+Sec-Fetch-Dest: report
+Sec-Fetch-Dest: script
+Sec-Fetch-Dest: serviceworker
+Sec-Fetch-Dest: sharedworker
+Sec-Fetch-Dest: style
+Sec-Fetch-Dest: track
+Sec-Fetch-Dest: video
+Sec-Fetch-Dest: worker
+Sec-Fetch-Dest: xslt
+```
 
 Servers should ignore this header if it contains any other value.
 
@@ -112,9 +114,11 @@ Servers should ignore this header if it contains any other value.
 
 A cross-site request generated by an {{HTMLElement("img")}} element would result in a request with the following HTTP request headers (note that the destination is `image`):
 
-    Sec-Fetch-Dest: image
-    Sec-Fetch-Mode: no-cors
-    Sec-Fetch-Site: cross-site
+```
+Sec-Fetch-Dest: image
+Sec-Fetch-Mode: no-cors
+Sec-Fetch-Site: cross-site
+```
 
 ## Specifications
 
diff --git a/files/en-us/web/http/headers/sec-fetch-mode/index.md b/files/en-us/web/http/headers/sec-fetch-mode/index.md
index 30a852494c687d2..c7b6b220b1f5ab3 100644
--- a/files/en-us/web/http/headers/sec-fetch-mode/index.md
+++ b/files/en-us/web/http/headers/sec-fetch-mode/index.md
@@ -37,11 +37,13 @@ Broadly speaking, this allows a server to distinguish between: requests originat
 
 ## Syntax
 
-    Sec-Fetch-Mode: cors
-    Sec-Fetch-Mode: navigate
-    Sec-Fetch-Mode: no-cors
-    Sec-Fetch-Mode: same-origin
-    Sec-Fetch-Mode: websocket
+```
+Sec-Fetch-Mode: cors
+Sec-Fetch-Mode: navigate
+Sec-Fetch-Mode: no-cors
+Sec-Fetch-Mode: same-origin
+Sec-Fetch-Mode: websocket
+```
 
 Servers should ignore this header if it contains any other value.
 
@@ -64,16 +66,20 @@ Servers should ignore this header if it contains any other value.
 
 If a user clicks on a page link to another page on the same origin, the resulting request would have the following headers (note that the mode is `navigate`):
 
-    Sec-Fetch-Dest: document
-    Sec-Fetch-Mode: navigate
-    Sec-Fetch-Site: same-origin
-    Sec-Fetch-User: ?1
+```
+Sec-Fetch-Dest: document
+Sec-Fetch-Mode: navigate
+Sec-Fetch-Site: same-origin
+Sec-Fetch-User: ?1
+```
 
 A cross-site request generated by an {{HTMLElement("img")}} element would result in a request with the following HTTP request headers (note that the mode is `no-cors`):
 
-    Sec-Fetch-Dest: image
-    Sec-Fetch-Mode: no-cors
-    Sec-Fetch-Site: cross-site
+```
+Sec-Fetch-Dest: image
+Sec-Fetch-Mode: no-cors
+Sec-Fetch-Site: cross-site
+```
 
 ## Specifications
 
diff --git a/files/en-us/web/http/headers/sec-fetch-site/index.md b/files/en-us/web/http/headers/sec-fetch-site/index.md
index 0851a9d822b577a..f5b7212ea2038a9 100644
--- a/files/en-us/web/http/headers/sec-fetch-site/index.md
+++ b/files/en-us/web/http/headers/sec-fetch-site/index.md
@@ -39,10 +39,12 @@ Same-origin requests would usually be allowed by default, but what happens for r
 
 ## Syntax
 
-    Sec-Fetch-Site: cross-site
-    Sec-Fetch-Site: same-origin
-    Sec-Fetch-Site: same-site
-    Sec-Fetch-Site: none
+```
+Sec-Fetch-Site: cross-site
+Sec-Fetch-Site: same-origin
+Sec-Fetch-Site: same-site
+Sec-Fetch-Site: none
+```
 
 ## Directives
 
@@ -60,17 +62,21 @@ Same-origin requests would usually be allowed by default, but what happens for r
 A fetch request to `https://mysite.example/foo.json` originating from a web page on `https://mysite.example` (with the same port) is a same-origin request.
 The browser will generate the `Sec-Fetch-Site: same-origin` header as shown below, and the server will typically allow the request:
 
-    GET /foo.json
-    Sec-Fetch-Dest: empty
-    Sec-Fetch-Mode: cors
-    Sec-Fetch-Site: same-origin
+```
+GET /foo.json
+Sec-Fetch-Dest: empty
+Sec-Fetch-Mode: cors
+Sec-Fetch-Site: same-origin
+```
 
 A fetch request to the same URL from another site, for example `potentially-evil.com`, causes the browser to generate a different header (e.g. `Sec-Fetch-Site: cross-site`), which the server can choose to accept or reject:
 
-    GET /foo.json
-    Sec-Fetch-Dest: empty
-    Sec-Fetch-Mode: cors
-    Sec-Fetch-Site: cross-site
+```
+GET /foo.json
+Sec-Fetch-Dest: empty
+Sec-Fetch-Mode: cors
+Sec-Fetch-Site: cross-site
+```
 
 ## Specifications
 
diff --git a/files/en-us/web/http/headers/sec-fetch-user/index.md b/files/en-us/web/http/headers/sec-fetch-user/index.md
index 321085f17952da7..7cd0555e18857f0 100644
--- a/files/en-us/web/http/headers/sec-fetch-user/index.md
+++ b/files/en-us/web/http/headers/sec-fetch-user/index.md
@@ -37,7 +37,9 @@ A server can use this header to identify whether a navigation request from a doc
 
 ## Syntax
 
-    Sec-Fetch-User: ?1
+```
+Sec-Fetch-User: ?1
+```
 
 ## Directives
 
@@ -47,10 +49,12 @@ The value will always be `?1`. When a request is triggered by something other th
 
 If a user clicks on a page link to another page on the same origin, the resulting request would have the following headers:
 
-    Sec-Fetch-Dest: document
-    Sec-Fetch-Mode: navigate
-    Sec-Fetch-Site: same-origin
-    Sec-Fetch-User: ?1
+```
+Sec-Fetch-Dest: document
+Sec-Fetch-Mode: navigate
+Sec-Fetch-Site: same-origin
+Sec-Fetch-User: ?1
+```
 
 ## Specifications
 
diff --git a/files/en-us/web/http/headers/sec-websocket-accept/index.md b/files/en-us/web/http/headers/sec-websocket-accept/index.md
index 0021cad81444209..252e826cb15f3d7 100644
--- a/files/en-us/web/http/headers/sec-websocket-accept/index.md
+++ b/files/en-us/web/http/headers/sec-websocket-accept/index.md
@@ -33,7 +33,7 @@ server to client to inform that server is willing to initiate a websocket connec
 
 ## Syntax
 
-```html
+```
 Sec-WebSocket-Accept: <hashed key>
 ```
 
@@ -47,7 +47,9 @@ Sec-WebSocket-Accept: <hashed key>
 
 ## Examples
 
-    Sec-WebSocket-Accept: s3pPLMBiTxaQ9kYGzzhZRbK+xOo=
+```
+Sec-WebSocket-Accept: s3pPLMBiTxaQ9kYGzzhZRbK+xOo=
+```
 
 ## Specifications
 
diff --git a/files/en-us/web/http/headers/server-timing/index.md b/files/en-us/web/http/headers/server-timing/index.md
index 0cac37dc6284165..a9d8c9dfa4765e1 100644
--- a/files/en-us/web/http/headers/server-timing/index.md
+++ b/files/en-us/web/http/headers/server-timing/index.md
@@ -31,22 +31,24 @@ The syntax of the `Server-Timing` header allows you to communicate metrics in di
 
 The specification advices that names and descriptions should be kept as short as possible (use abbreviations and omit optional values where possible) to minimize the HTTP overhead.
 
-    // Single metric without value
-    Server-Timing: missedCache
+```
+// Single metric without value
+Server-Timing: missedCache
 
-    // Single metric with value
-    Server-Timing: cpu;dur=2.4
+// Single metric with value
+Server-Timing: cpu;dur=2.4
 
-    // Single metric with description and value
-    Server-Timing: cache;desc="Cache Read";dur=23.2
+// Single metric with description and value
+Server-Timing: cache;desc="Cache Read";dur=23.2
 
-    // Two metrics with value
-    Server-Timing: db;dur=53, app;dur=47.2
+// Two metrics with value
+Server-Timing: db;dur=53, app;dur=47.2
 
-    // Server-Timing as trailer
-    Trailer: Server-Timing
-    --- response body ---
-    Server-Timing: total;dur=123.4
+// Server-Timing as trailer
+Trailer: Server-Timing
+--- response body ---
+Server-Timing: total;dur=123.4
+```
 
 ## Privacy and security
 
diff --git a/files/en-us/web/http/headers/server/index.md b/files/en-us/web/http/headers/server/index.md
index 487f98ca5d312c9..dee0f2232d12655 100644
--- a/files/en-us/web/http/headers/server/index.md
+++ b/files/en-us/web/http/headers/server/index.md
@@ -31,13 +31,13 @@ generated the response.
 
 ## Syntax
 
-```html
+```
 Server: <product>
 ```
 
 ## Directives
 
-- `<product>`
+- \<product>
   - : The name of the software or product that handled the request. Usually in a format
     similar to {{HTTPHeader('User-Agent')}}.
 
@@ -49,7 +49,9 @@ versions had with {{HTTPHeader('Content-Encoding')}} combined with
 
 ## Examples
 
-    Server: Apache/2.4.1 (Unix)
+```
+Server: Apache/2.4.1 (Unix)
+```
 
 ## Specifications
 
diff --git a/files/en-us/web/http/headers/set-cookie/index.md b/files/en-us/web/http/headers/set-cookie/index.md
index 2a8b1609f1ecf5f..a4ff8a1b2158f9c 100644
--- a/files/en-us/web/http/headers/set-cookie/index.md
+++ b/files/en-us/web/http/headers/set-cookie/index.md
@@ -31,8 +31,7 @@ For more information, see the guide on [Using HTTP cookies](/en-US/docs/Web/HTTP
     <tr>
       <th scope="row">
         <a href="https://fetch.spec.whatwg.org/#forbidden-response-header-name"
-          >Forbidden response-header name</a
-        >
+          >Forbidden response-header name</a>
       </th>
       <td>yes</td>
     </tr>
@@ -41,7 +40,7 @@ For more information, see the guide on [Using HTTP cookies](/en-US/docs/Web/HTTP
 
 ## Syntax
 
-```html
+```
 Set-Cookie: <cookie-name>=<cookie-value>
 Set-Cookie: <cookie-name>=<cookie-value>; Expires=<date>
 Set-Cookie: <cookie-name>=<cookie-value>; Max-Age=<number>
@@ -169,17 +168,21 @@ Set-Cookie: <cookie-name>=<cookie-value>; Domain=<domain-value>; Secure; HttpOnl
 
 **Session cookies** are removed when the client shuts down. Cookies are session cookies if they don't specify the `Expires` or `Max-Age` attributes.
 
-    Set-Cookie: sessionId=38afes7a8
+```
+Set-Cookie: sessionId=38afes7a8
+```
 
 ### Permanent cookie
 
 Instead of expiring when the client is closed, **permanent cookies** expire at a specific date (`Expires`) or after a specific length of time (`Max-Age`).
 
-    Set-Cookie: id=a3fWa; Expires=Wed, 21 Oct 2015 07:28:00 GMT
-
-<!---->
+```
+Set-Cookie: id=a3fWa; Expires=Wed, 21 Oct 2015 07:28:00 GMT
+```
 
-    Set-Cookie: id=a3fWa; Max-Age=2592000
+```
+Set-Cookie: id=a3fWa; Max-Age=2592000
+```
 
 ### Invalid domains
 
@@ -187,13 +190,17 @@ A cookie for a domain that does not include the server that set it [should be re
 
 The following cookie will be rejected if set by a server hosted on `originalcompany.com`:
 
-    Set-Cookie: qwerty=219ffwef9w0f; Domain=somecompany.co.uk
+```
+Set-Cookie: qwerty=219ffwef9w0f; Domain=somecompany.co.uk
+```
 
 A cookie for a sub domain of the serving domain will be rejected.
 
 The following cookie will be rejected if set by a server hosted on `example.com`:
 
-    Set-Cookie: sessionId=e8bb43229de9; Domain=foo.example.com
+```
+Set-Cookie: sessionId=e8bb43229de9; Domain=foo.example.com
+```
 
 ### Cookie prefixes
 
@@ -203,18 +210,20 @@ In addition, cookies with the `__Host-` prefix must have a path of `/` (meaning
 
 > **Warning:** For clients that don't implement cookie prefixes, you cannot count on these additional assurances, and prefixed cookies will always be accepted.
 
-    // Both accepted when from a secure origin (HTTPS)
-    Set-Cookie: __Secure-ID=123; Secure; Domain=example.com
-    Set-Cookie: __Host-ID=123; Secure; Path=/
+```
+// Both accepted when from a secure origin (HTTPS)
+Set-Cookie: __Secure-ID=123; Secure; Domain=example.com
+Set-Cookie: __Host-ID=123; Secure; Path=/
 
-    // Rejected due to missing Secure attribute
-    Set-Cookie: __Secure-id=1
+// Rejected due to missing Secure attribute
+Set-Cookie: __Secure-id=1
 
-    // Rejected due to the missing Path=/ attribute
-    Set-Cookie: __Host-id=1; Secure
+// Rejected due to the missing Path=/ attribute
+Set-Cookie: __Host-id=1; Secure
 
-    // Rejected due to setting a Domain
-    Set-Cookie: __Host-id=1; Secure; Path=/; Domain=example.com
+// Rejected due to setting a Domain
+Set-Cookie: __Host-id=1; Secure; Path=/; Domain=example.com
+```
 
 ## Specifications
 
diff --git a/files/en-us/web/http/headers/set-cookie/samesite/index.md b/files/en-us/web/http/headers/set-cookie/samesite/index.md
index 54fee20d5659da6..5f6acd02d0a3c2e 100644
--- a/files/en-us/web/http/headers/set-cookie/samesite/index.md
+++ b/files/en-us/web/http/headers/set-cookie/samesite/index.md
@@ -45,21 +45,21 @@ Cookies will be sent in all contexts, i.e. in responses to both first-party and
 
 Warnings like the ones below might appear in your console:
 
-```html
-Cookie “myCookie” rejected because it has the “SameSite=None” attribute but is missing the “secure” attribute.
+```
+Cookie "myCookie" rejected because it has the "SameSite=None" attribute but is missing the "secure" attribute.
 
 This Set-Cookie was blocked because it had the "SameSite=None" attribute but did not have the "Secure" attribute, which is required in order to use "SameSite=None".
 ```
 
 The warning appears because any cookie that requests `SameSite=None` but is not marked `Secure` will be rejected.
 
-```plain example-bad
+```example-bad
 Set-Cookie: flavor=choco; SameSite=None
 ```
 
 To fix this, you will have to add the `Secure` attribute to your `SameSite=None` cookies.
 
-```plain example-good
+```example-good
 Set-Cookie: flavor=choco; SameSite=None; Secure
 ```
 
@@ -75,33 +75,35 @@ A [`Secure`](#secure) cookie is only sent to the server with an encrypted reques
 
 Recent versions of modern browsers provide a more secure default for `SameSite` to your cookies and so the following message might appear in your console:
 
-```html
-Cookie “myCookie” has “SameSite” policy set to “Lax” because it is missing a “SameSite” attribute, and “SameSite=Lax” is the default value for this attribute.
+```
+Cookie "myCookie" has "SameSite" policy set to "Lax" because it is missing a "SameSite" attribute, and "SameSite=Lax" is the default value for this attribute.
 ```
 
 The warning appears because the `SameSite` policy for a cookie was not explicitly specified:
 
-```plain example-bad
+```example-bad
 Set-Cookie: flavor=choco
 ```
 
 You should explicitly communicate the intended `SameSite` policy for your cookie (rather than relying on browsers to apply `SameSite=Lax` automatically). This will also improve the experience across browsers as not all of them default to `Lax` yet.
 
-```plain example-good
+```example-good
 Set-Cookie: flavor=choco; SameSite=Lax
 ```
 
 ## Example
 
-    RewriteEngine on
-    RewriteBase "/"
-    RewriteCond "%{HTTP_HOST}"       "^example\.org$" [NC]
-    RewriteRule "^(.*)"              "https://www.example.org/index.html" [R=301,L,QSA]
-    RewriteRule "^(.*)\.ht$"         "index.php?nav=$1 [NC,L,QSA,CO=RewriteRule;01;https://www.example.org;30/;SameSite=None;Secure]
-    RewriteRule "^(.*)\.htm$"        "index.php?nav=$1 [NC,L,QSA,CO=RewriteRule;02;https://www.example.org;30/;SameSite=None;Secure]
-    RewriteRule "^(.*)\.html$"       "index.php?nav=$1 [NC,L,QSA,CO=RewriteRule;03;https://www.example.org;30/;SameSite=None;Secure]
-    [...]
-    RewriteRule "^admin/(.*)\.html$" "admin/index.php?nav=$1 [NC,L,QSA,CO=RewriteRule;09;https://www.example.org:30/;SameSite=Strict;Secure]
+```
+RewriteEngine on
+RewriteBase "/"
+RewriteCond "%{HTTP_HOST}"       "^example\.org$" [NC]
+RewriteRule "^(.*)"              "https://www.example.org/index.html" [R=301,L,QSA]
+RewriteRule "^(.*)\.ht$"         "index.php?nav=$1 [NC,L,QSA,CO=RewriteRule;01;https://www.example.org;30/;SameSite=None;Secure]
+RewriteRule "^(.*)\.htm$"        "index.php?nav=$1 [NC,L,QSA,CO=RewriteRule;02;https://www.example.org;30/;SameSite=None;Secure]
+RewriteRule "^(.*)\.html$"       "index.php?nav=$1 [NC,L,QSA,CO=RewriteRule;03;https://www.example.org;30/;SameSite=None;Secure]
+[...]
+RewriteRule "^admin/(.*)\.html$" "admin/index.php?nav=$1 [NC,L,QSA,CO=RewriteRule;09;https://www.example.org:30/;SameSite=Strict;Secure]
+```
 
 ## Specifications
 
diff --git a/files/en-us/web/http/headers/set-cookie2/index.md b/files/en-us/web/http/headers/set-cookie2/index.md
index 9411f2cf04b352b..70bbd784a810027 100644
--- a/files/en-us/web/http/headers/set-cookie2/index.md
+++ b/files/en-us/web/http/headers/set-cookie2/index.md
@@ -30,7 +30,7 @@ specification. Use {{HTTPHeader("Set-Cookie")}} instead.
 
 ## Syntax
 
-```html
+```
 Set-Cookie2: <cookie-name>=<cookie-value>
 Set-Cookie2: <cookie-name>=<cookie-value>; Comment=<value>
 Set-Cookie2: <cookie-name>=<cookie-value>; CommentURL=<http-url>
diff --git a/files/en-us/web/http/headers/sourcemap/index.md b/files/en-us/web/http/headers/sourcemap/index.md
index c0a8eeaec127965..712720c2c1926d6 100644
--- a/files/en-us/web/http/headers/sourcemap/index.md
+++ b/files/en-us/web/http/headers/sourcemap/index.md
@@ -28,19 +28,21 @@ The **`SourceMap`** [HTTP](/en-US/docs/Web/HTTP) response header links generated
 
 ## Syntax
 
-```html
+```
 SourceMap: <url>
 X-SourceMap: <url> (deprecated)
 ```
 
 ### Directives
 
-- `<url>`
+- \<url>
   - : A relative (to the request URL) or absolute URL pointing to a source map file.
 
 ## Examples
 
-    SourceMap: /path/to/file.js.map
+```
+SourceMap: /path/to/file.js.map
+```
 
 ## Specifications
 
diff --git a/files/en-us/web/http/headers/strict-transport-security/index.md b/files/en-us/web/http/headers/strict-transport-security/index.md
index 40f1803e32fe696..7c8e98efb05d4af 100644
--- a/files/en-us/web/http/headers/strict-transport-security/index.md
+++ b/files/en-us/web/http/headers/strict-transport-security/index.md
@@ -30,7 +30,7 @@ be accessed using HTTPS, instead of using HTTP.
 
 ## Syntax
 
-```html
+```
 Strict-Transport-Security: max-age=<expire-time>
 Strict-Transport-Security: max-age=<expire-time>; includeSubDomains
 Strict-Transport-Security: max-age=<expire-time>; preload
@@ -114,7 +114,9 @@ treated as official.
 All present and future subdomains will be HTTPS for a max-age of 1 year. This blocks
 access to pages or sub domains that can only be served over HTTP.
 
-    Strict-Transport-Security: max-age=31536000; includeSubDomains
+```
+Strict-Transport-Security: max-age=31536000; includeSubDomains
+```
 
 In the following example, `max-age` is set to 2 years, raised from what was
 a former limit `max-age` of 1 year. Note that 1 year is acceptable for a
@@ -123,7 +125,9 @@ recommended goal as a website's final HSTS configuration as explained on <https:
 `preload` which is necessary for inclusion in most major web browsers' HSTS
 preload lists, e.g. Chromium, Edge, & Firefox.
 
-    Strict-Transport-Security: max-age=63072000; includeSubDomains; preload
+```
+Strict-Transport-Security: max-age=63072000; includeSubDomains; preload
+```
 
 ## Specifications
 
diff --git a/files/en-us/web/http/headers/te/index.md b/files/en-us/web/http/headers/te/index.md
index 27fa8dbde73c5da..19304f17152e24b 100644
--- a/files/en-us/web/http/headers/te/index.md
+++ b/files/en-us/web/http/headers/te/index.md
@@ -38,7 +38,7 @@ trailer fields in a chunked transfer coding using the "trailers" value.
 
 ## Syntax
 
-```html
+```
 TE: compress
 TE: deflate
 TE: gzip
@@ -79,5 +79,4 @@ TE: trailers, deflate;q=0.5
 
 - {{HTTPHeader("Transfer-Encoding")}}
 - {{HTTPHeader("Trailer")}}
-- [Chunked transfer
-  encoding](https://en.wikipedia.org/wiki/Chunked_transfer_encoding)
+- [Chunked transfer encoding](https://en.wikipedia.org/wiki/Chunked_transfer_encoding)
diff --git a/files/en-us/web/http/headers/timing-allow-origin/index.md b/files/en-us/web/http/headers/timing-allow-origin/index.md
index 035b52f80ee0a38..792c10d617823fb 100644
--- a/files/en-us/web/http/headers/timing-allow-origin/index.md
+++ b/files/en-us/web/http/headers/timing-allow-origin/index.md
@@ -28,7 +28,7 @@ The **`Timing-Allow-Origin`** response header specifies origins that are allowed
 
 ## Syntax
 
-```html
+```
 Timing-Allow-Origin: *
 Timing-Allow-Origin: <origin>[, <origin>]*
 ```
@@ -37,18 +37,22 @@ Timing-Allow-Origin: <origin>[, <origin>]*
 
 - `*`
   - : The server may specify "\*" as a wildcard, thereby allowing any origin to see timing resources.
-- `<origin>`
+- \<origin>
   - : Specifies a URI that may see the timing resources. You can specify multiple origins, separated by commas.
 
 ## Examples
 
 To allow any resource to see timing resources:
 
-    Timing-Allow-Origin: *
+```
+Timing-Allow-Origin: *
+```
 
 To allow `https://developer.mozilla.org` to see timing resources, you can specify:
 
-    Timing-Allow-Origin: https://developer.mozilla.org
+```
+Timing-Allow-Origin: https://developer.mozilla.org
+```
 
 ## Specifications
 
diff --git a/files/en-us/web/http/headers/tk/index.md b/files/en-us/web/http/headers/tk/index.md
index fddf3fa984d6425..0a0d8bdfe8dba98 100644
--- a/files/en-us/web/http/headers/tk/index.md
+++ b/files/en-us/web/http/headers/tk/index.md
@@ -30,7 +30,7 @@ applied to the corresponding request.
 
 ## Syntax
 
-```html
+```
 Tk: !  (under construction)
 Tk: ?  (dynamic)
 Tk: G  (gateway or multiple parties)
@@ -76,7 +76,9 @@ Tk: U  (updated)
 
 A `Tk` header for a resource that claims not to be tracking would look like:
 
-    Tk: N
+```
+Tk: N
+```
 
 ## Specifications
 
diff --git a/files/en-us/web/http/headers/trailer/index.md b/files/en-us/web/http/headers/trailer/index.md
index 8712310f804538a..4237b0966b4cb29 100644
--- a/files/en-us/web/http/headers/trailer/index.md
+++ b/files/en-us/web/http/headers/trailer/index.md
@@ -38,7 +38,7 @@ digital signature, or post-processing status.
 
 ## Syntax
 
-```html
+```
 Trailer: header-names
 ```
 
@@ -67,20 +67,22 @@ Trailer: header-names
 In this example, the {{HTTPHeader("Expires")}} header is used at the end of the chunked
 message and serves as a trailing header.
 
-    HTTP/1.1 200 OK
-    Content-Type: text/plain
-    Transfer-Encoding: chunked
-    Trailer: Expires
-
-    7\r\n
-    Mozilla\r\n
-    9\r\n
-    Developer\r\n
-    7\r\n
-    Network\r\n
-    0\r\n
-    Expires: Wed, 21 Oct 2015 07:28:00 GMT\r\n
-    \r\n
+```
+HTTP/1.1 200 OK
+Content-Type: text/plain
+Transfer-Encoding: chunked
+Trailer: Expires
+
+7\r\n
+Mozilla\r\n
+9\r\n
+Developer\r\n
+7\r\n
+Network\r\n
+0\r\n
+Expires: Wed, 21 Oct 2015 07:28:00 GMT\r\n
+\r\n
+```
 
 ## Specifications
 
diff --git a/files/en-us/web/http/headers/transfer-encoding/index.md b/files/en-us/web/http/headers/transfer-encoding/index.md
index c10ea945742e659..679210e79971173 100644
--- a/files/en-us/web/http/headers/transfer-encoding/index.md
+++ b/files/en-us/web/http/headers/transfer-encoding/index.md
@@ -49,7 +49,7 @@ message.
 
 ## Syntax
 
-```html
+```
 Transfer-Encoding: chunked
 Transfer-Encoding: compress
 Transfer-Encoding: deflate
@@ -99,18 +99,20 @@ total size of the response may not be known until the request has been fully pro
 For example, when generating a large HTML table resulting from a database query or when
 transmitting large images. A chunked response looks like this:
 
-    HTTP/1.1 200 OK
-    Content-Type: text/plain
-    Transfer-Encoding: chunked
+```
+HTTP/1.1 200 OK
+Content-Type: text/plain
+Transfer-Encoding: chunked
 
-    7\r\n
-    Mozilla\r\n
-    9\r\n
-    Developer\r\n
-    7\r\n
-    Network\r\n
-    0\r\n
-    \r\n
+7\r\n
+Mozilla\r\n
+9\r\n
+Developer\r\n
+7\r\n
+Network\r\n
+0\r\n
+\r\n
+```
 
 ## Specifications
 
@@ -127,5 +129,4 @@ transmitting large images. A chunked response looks like this:
 - {{HTTPHeader("Content-Length")}}
 - Header fields that regulate the use of trailers: {{HTTPHeader("TE")}} (requests) and
   {{HTTPHeader("Trailer")}} (responses).
-- [Chunked transfer
-  encoding](https://en.wikipedia.org/wiki/Chunked_transfer_encoding)
+- [Chunked transfer encoding](https://en.wikipedia.org/wiki/Chunked_transfer_encoding)
diff --git a/files/en-us/web/http/headers/upgrade-insecure-requests/index.md b/files/en-us/web/http/headers/upgrade-insecure-requests/index.md
index 37f16634aceedf7..98a2eb7f18d61d6 100644
--- a/files/en-us/web/http/headers/upgrade-insecure-requests/index.md
+++ b/files/en-us/web/http/headers/upgrade-insecure-requests/index.md
@@ -27,7 +27,7 @@ The HTTP **`Upgrade-Insecure-Requests`** request header sends a signal to the se
 
 ## Syntax
 
-```html
+```
 Upgrade-Insecure-Requests: 1
 ```
 
@@ -35,14 +35,18 @@ Upgrade-Insecure-Requests: 1
 
 A client's request signals to the server that it supports the upgrade mechanisms of {{CSP("upgrade-insecure-requests")}}:
 
-    GET / HTTP/1.1
-    Host: example.com
-    Upgrade-Insecure-Requests: 1
+```
+GET / HTTP/1.1
+Host: example.com
+Upgrade-Insecure-Requests: 1
+```
 
-The server can now redirect to a secure version of the site. A {{HTTPHeader("Vary")}} header can be used so that the site isn't served by caches to clients that don’t support the upgrade mechanism.
+The server can now redirect to a secure version of the site. A {{HTTPHeader("Vary")}} header can be used so that the site isn't served by caches to clients that don't support the upgrade mechanism.
 
-    Location: https://example.com/
-    Vary: Upgrade-Insecure-Requests
+```
+Location: https://example.com/
+Vary: Upgrade-Insecure-Requests
+```
 
 ## Specifications
 
diff --git a/files/en-us/web/http/headers/upgrade/index.md b/files/en-us/web/http/headers/upgrade/index.md
index d0d2fe513d9df9e..2debcb94a4e2b51 100644
--- a/files/en-us/web/http/headers/upgrade/index.md
+++ b/files/en-us/web/http/headers/upgrade/index.md
@@ -37,22 +37,26 @@ The `Upgrade` header field may be used by clients to invite a server to switch t
 
 For example, the client might send a `GET` request as shown, listing the preferred protocols to switch to (in this case "example/1" and "foo/2"):
 
-    GET /index.html HTTP/1.1
-    Host: www.example.com
-    Connection: upgrade
-    Upgrade: example/1, foo/2
+```
+GET /index.html HTTP/1.1
+Host: www.example.com
+Connection: upgrade
+Upgrade: example/1, foo/2
+```
 
 > **Note:** `Connection: upgrade` must be set whenever `Upgrade` is sent.
 
-The server can choose to ignore the request, for any reason, in which case it should just respond as though the `Upgrade` header had not been sent (for example, with a  {{HTTPStatus(200, "200 OK")}}).
+The server can choose to ignore the request, for any reason, in which case it should just respond as though the `Upgrade` header had not been sent (for example, with a {{HTTPStatus(200, "200 OK")}}).
 
 If the server decides to upgrade the connection, it must:
 
 1. Send back a {{HTTPStatus(101, "101 Switching Protocols")}} response status with an `Upgrade` header that specifies the protocol(s) being switched to. For example:
 
-        HTTP/1.1 101 Switching Protocols
-        Upgrade: foo/2
-        Connection: Upgrade
+```
+HTTP/1.1 101 Switching Protocols
+Upgrade: foo/2
+Connection: Upgrade
+```
 
 2. Send a response to the original request *using the new protocol* (the server may only switch to a protocol with which it can complete the original request).
 
@@ -62,16 +66,20 @@ More detail and examples are provided in the topic [Protocol upgrade mechanism](
 
 ## Syntax
 
-    Connection: upgrade
-    Upgrade: protocol_name[/protocol_version]
+```
+Connection: upgrade
+Upgrade: protocol_name[/protocol_version]
+```
 
 Notes:
 
 - The {{HTTPHeader("Connection")}} header with type `upgrade` must _always_ be sent with the `Upgrade` header (as shown above).
 - Protocols are listed, comma-separated, in order of descending preference. Protocol version is optional. For example:
 
-        Connection: upgrade
-        Upgrade: a_protocol/1, example ,another_protocol/2.2
+```
+Connection: upgrade
+Upgrade: a_protocol/1, example ,another_protocol/2.2
+```
 
 ## Directives
 
@@ -80,13 +88,15 @@ Notes:
 
 ## Examples
 
-    Connection: upgrade
-    Upgrade: HTTP/2.0, SHTTP/1.3, IRC/6.9, RTA/x11
+```
+Connection: upgrade
+Upgrade: HTTP/2.0, SHTTP/1.3, IRC/6.9, RTA/x11
+```
 
-<!---->
-
-    Connection: Upgrade
-    Upgrade: websocket
+```
+Connection: Upgrade
+Upgrade: websocket
+```
 
 ## Specifications
 
diff --git a/files/en-us/web/http/headers/user-agent/firefox/index.md b/files/en-us/web/http/headers/user-agent/firefox/index.md
index 3227da3eac231c9..a6cbcb245da54df 100644
--- a/files/en-us/web/http/headers/user-agent/firefox/index.md
+++ b/files/en-us/web/http/headers/user-agent/firefox/index.md
@@ -46,8 +46,10 @@ For other products based on Gecko, the string can take one of two forms, where t
 
 The `platform` part of the UA string indicates if Firefox is running on a phone-sized or tablet device. When Firefox runs on a device that has the phone form factor, there is a `Mobile;` token in the `platform` part of the UA string. When Firefox runs on a tablet device, there is a `Tablet;` token in the `platform` part of the UA string instead. For example:
 
-    Mozilla/5.0 (Android 4.4; Mobile; rv:41.0) Gecko/41.0 Firefox/41.0
-    Mozilla/5.0 (Android 4.4; Tablet; rv:41.0) Gecko/41.0 Firefox/41.0
+```
+Mozilla/5.0 (Android 4.4; Mobile; rv:41.0) Gecko/41.0 Firefox/41.0
+Mozilla/5.0 (Android 4.4; Tablet; rv:41.0) Gecko/41.0 Firefox/41.0
+```
 
 > **Note:** The version numbers are not relevant. Avoid inferring materials based on these.
 
@@ -105,7 +107,9 @@ Beginning in version 41, Firefox for Android will contain the Android version as
 
 From version 1, Focus is powered by Android WebView and uses the following user agent string format:
 
-    Mozilla/5.0 (Linux; <Android Version> <Build Tag etc.>) AppleWebKit/<WebKit Rev> (KHTML, like Gecko) Version/4.0 Focus/<focusversion> Chrome/<Chrome Rev> Mobile Safari/<WebKit Rev>
+```
+Mozilla/5.0 (Linux; <Android Version> <Build Tag etc.>) AppleWebKit/<WebKit Rev> (KHTML, like Gecko) Version/4.0 Focus/<focusversion> Chrome/<Chrome Rev> Mobile Safari/<WebKit Rev>
+```
 
 Tablet versions on WebView mirror mobile, but do not contain a `Mobile` token.
 
@@ -131,7 +135,9 @@ Since version 4.1, Klar for Android uses the same UA string as [Focus for Androi
 
 Version 7 of Focus for iOS uses a user agent string with the following format:
 
-    Mozilla/5.0 (iPhone; CPU iPhone OS 12_1 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) FxiOS/7.0.4 Mobile/16B91 Safari/605.1.15
+```
+Mozilla/5.0 (iPhone; CPU iPhone OS 12_1 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) FxiOS/7.0.4 Mobile/16B91 Safari/605.1.15
+```
 
 Note: this user agent was retrieved from an iPhone XR simulator and may be different on device.
 
@@ -139,7 +145,9 @@ Note: this user agent was retrieved from an iPhone XR simulator and may be diffe
 
 Version 3 (and probably earlier) of Firefox for Fire TV use a user agent string with the following format:
 
-    Mozilla/5.0 (Linux; <Android version>) AppleWebKit/537.36 (KHTML, like Gecko) Version/4.0 Focus/<firefoxversion> Chrome/<Chrome Rev> Safari/<WebKit Rev>
+```
+Mozilla/5.0 (Linux; <Android version>) AppleWebKit/537.36 (KHTML, like Gecko) Version/4.0 Focus/<firefoxversion> Chrome/<Chrome Rev> Safari/<WebKit Rev>
+```
 
 | Firefox TV version | User Agent string                                                                                                                  |
 | ------------------ | ---------------------------------------------------------------------------------------------------------------------------------- |
@@ -149,7 +157,9 @@ Version 3 (and probably earlier) of Firefox for Fire TV use a user agent string
 
 From version 1.1, Firefox for Echo Show uses a user agent string with the following format:
 
-    Mozilla/5.0 (Linux; <Android version>) AppleWebKit/537.36 (KHTML, like Gecko) Version/4.0 Focus/<firefoxversion> Chrome/<Chrome Rev> Safari/<WebKit Rev>
+```
+Mozilla/5.0 (Linux; <Android version>) AppleWebKit/537.36 (KHTML, like Gecko) Version/4.0 Focus/<firefoxversion> Chrome/<Chrome Rev> Safari/<WebKit Rev>
+```
 
 | Firefox for Echo Show version | User agent string                                                                                                                  |
 | ----------------------------- | ---------------------------------------------------------------------------------------------------------------------------------- |
@@ -170,7 +180,9 @@ Although it is **strongly discouraged** by Mozilla, some handset manufacturers u
 
 Here is a JavaScript regular expression that will detect all mobile devices, including devices with a device id in their UA string:
 
-    /mobi/i
+```
+/mobi/i
+!!
 
 The `i` makes it case-insensitive, and `mobi` matches all mobile browsers.
 
diff --git a/files/en-us/web/http/headers/user-agent/index.md b/files/en-us/web/http/headers/user-agent/index.md
index dc652c6f6009dc2..72c80478852afb6 100644
--- a/files/en-us/web/http/headers/user-agent/index.md
+++ b/files/en-us/web/http/headers/user-agent/index.md
@@ -29,30 +29,32 @@ The **User-Agent** {{Glossary("request header")}} is a characteristic string tha
 
 ## Syntax
 
-```html
+```
 User-Agent: <product> / <product-version> <comment>
 ```
 
 Common format for web browsers:
 
-```html
+```
 User-Agent: Mozilla/5.0 (<system-information>) <platform> (<platform-details>) <extensions>
 ```
 
 ### Directives
 
-- `<product>`
+- \<product>
   - : A product identifier — its name or development codename.
-- `<product-version>`
+- \<product-version>
   - : Version number of the product.
-- `<comment>`
+- \<comment>
   - : Zero or more comments containing more details; sub-product information, for example.
 
 ## Firefox UA string
 
 For more on Firefox- and Gecko-based user agent strings, see the [Firefox user agent string reference](/en-US/docs/Web/HTTP/Headers/User-Agent/Firefox). The UA string of Firefox is broken down into 4 components:
 
-    Mozilla/5.0 (platform; rv:geckoversion) Gecko/geckotrail Firefox/firefoxversion
+```
+Mozilla/5.0 (platform; rv:geckoversion) Gecko/geckotrail Firefox/firefoxversion
+```
 
 1. `Mozilla/5.0` is the general token that says the browser is Mozilla-compatible. For historical reasons, almost every browser today sends it.
 2. **_platform_** describes the native platform the browser is running on (Windows, Mac, Linux, Android, etc.), and if it's a mobile phone. {{Glossary("Firefox OS")}} phones say `Mobile` — the web is the platform. Note that **_platform_** can consist of multiple "`;`"-separated tokens. See below for further details and examples.
@@ -62,8 +64,10 @@ For more on Firefox- and Gecko-based user agent strings, see the [Firefox user a
 
 ### Examples
 
-    Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:47.0) Gecko/20100101 Firefox/47.0
-    Mozilla/5.0 (Macintosh; Intel Mac OS X x.y; rv:42.0) Gecko/20100101 Firefox/42.0
+```
+Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:47.0) Gecko/20100101 Firefox/47.0
+Mozilla/5.0 (Macintosh; Intel Mac OS X x.y; rv:42.0) Gecko/20100101 Firefox/42.0
+```
 
 ## Chrome UA string
 
@@ -71,7 +75,9 @@ The Chrome (or Chromium/Blink-based engines) user agent string is similar to Fir
 
 ### Examples
 
-    Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2704.103 Safari/537.36
+```
+Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2704.103 Safari/537.36
+```
 
 ## Opera UA string
 
@@ -79,12 +85,16 @@ The Opera browser is also based on the Blink engine, which is why it almost look
 
 ### Examples
 
-    Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2704.106 Safari/537.36 OPR/38.0.2220.41
+```
+Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2704.106 Safari/537.36 OPR/38.0.2220.41
+```
 
 Older, Presto-based Opera releases used:
 
-    Opera/9.80 (Macintosh; Intel Mac OS X; U; en) Presto/2.2.15 Version/10.00
-    Opera/9.60 (Windows NT 6.0; U; en) Presto/2.1.1
+```
+Opera/9.80 (Macintosh; Intel Mac OS X; U; en) Presto/2.2.15 Version/10.00
+Opera/9.60 (Windows NT 6.0; U; en) Presto/2.1.1
+```
 
 ## Microsoft Edge UA string
 
@@ -92,41 +102,51 @@ The Edge browser is also based on the Blink engine.
 
 ### Examples
 
-    Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/91.0.4472.124 Safari/537.36 Edg/91.0.864.59
+```
+Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/91.0.4472.124 Safari/537.36 Edg/91.0.864.59
+```
 
 ## Safari UA string
 
-In this example, the user agent string is mobile Safari’s version. It contains the word `"Mobile"`.
+In this example, the user agent string is mobile Safari's version. It contains the word `"Mobile"`.
 
 ### Examples
 
-    Mozilla/5.0 (iPhone; CPU iPhone OS 13_5_1 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/13.1.1 Mobile/15E148 Safari/604.1
+```
+Mozilla/5.0 (iPhone; CPU iPhone OS 13_5_1 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/13.1.1 Mobile/15E148 Safari/604.1
+```
 
 ## Internet Explorer UA string
 
 ### Examples
 
-    Mozilla/5.0 (compatible; MSIE 9.0; Windows Phone OS 7.5; Trident/5.0; IEMobile/9.0)
+```
+Mozilla/5.0 (compatible; MSIE 9.0; Windows Phone OS 7.5; Trident/5.0; IEMobile/9.0)
+```
 
 ## Crawler and bot UA strings
 
 ### Examples
 
-    Mozilla/5.0 (compatible; Googlebot/2.1; +http://www.google.com/bot.html)
-
-<!---->
+```
+Mozilla/5.0 (compatible; Googlebot/2.1; +http://www.google.com/bot.html)
+```
 
-    Mozilla/5.0 (compatible; YandexAccessibilityBot/3.0; +http://yandex.com/bots)
+```
+Mozilla/5.0 (compatible; YandexAccessibilityBot/3.0; +http://yandex.com/bots)
+```
 
 ## Library and net tool UA strings
 
 ### Examples
 
-    curl/7.64.1
-
-<!---->
+```
+curl/7.64.1
+```
 
-    PostmanRuntime/7.26.5
+```
+PostmanRuntime/7.26.5
+```
 
 ## Specifications
 
diff --git a/files/en-us/web/http/headers/vary/index.md b/files/en-us/web/http/headers/vary/index.md
index fde1be63997e947..0474430cbb6448c 100644
--- a/files/en-us/web/http/headers/vary/index.md
+++ b/files/en-us/web/http/headers/vary/index.md
@@ -35,7 +35,7 @@ The `Vary` header should be set on a {{HTTPStatus("304")}}
 
 ## Syntax
 
-```html
+```
 Vary: *
 Vary: <header-name>, <header-name>, ...
 ```
@@ -62,7 +62,9 @@ mistakenly serve a desktop version of your site to your mobile users. It can hel
 and other search engines to discover the mobile version of a page, and might also tell
 them that no [Cloaking](https://en.wikipedia.org/wiki/Cloaking) is intended.
 
-    Vary: User-Agent
+```
+Vary: User-Agent
+```
 
 ## Specifications
 
@@ -74,14 +76,10 @@ them that no [Cloaking](https://en.wikipedia.org/wiki/Cloaking) is intended.
 
 ## Compatibility notes
 
-- [Vary
-  with care – Vary header problems in IE6-9](https://blogs.msdn.microsoft.com/ieinternals/2009/06/17/vary-with-care/)
+- [Vary with care – Vary header problems in IE6-9](https://blogs.msdn.microsoft.com/ieinternals/2009/06/17/vary-with-care/)
 
 ## See also
 
-- [Understanding
-  The Vary Header - Smashing Magazine](https://www.smashingmagazine.com/2017/11/understanding-vary-header/)
-- [Best
-  Practices for Using the Vary Header – fastly.com](https://www.fastly.com/blog/best-practices-for-using-the-vary-header)
-- [Content
-  negotiation](/en-US/docs/Web/HTTP/Content_negotiation)
+- [Understanding The Vary Header - Smashing Magazine](https://www.smashingmagazine.com/2017/11/understanding-vary-header/)
+- [Best Practices for Using the Vary Header – fastly.com](https://www.fastly.com/blog/best-practices-for-using-the-vary-header)
+- [Content negotiation](/en-US/docs/Web/HTTP/Content_negotiation)
diff --git a/files/en-us/web/http/headers/via/index.md b/files/en-us/web/http/headers/via/index.md
index 61f26567302ecdb..af5d0f130d615fd 100644
--- a/files/en-us/web/http/headers/via/index.md
+++ b/files/en-us/web/http/headers/via/index.md
@@ -34,9 +34,8 @@ protocol capabilities of senders along the request/response chain.
 
 ## Syntax
 
-```html
+```
 Via: [ <protocol-name> "/" ] <protocol-version> <host> [ ":" <port> ]
-or
 Via: [ <protocol-name> "/" ] <protocol-version> <pseudonym>
 ```
 
@@ -53,9 +52,11 @@ Via: [ <protocol-name> "/" ] <protocol-version> <pseudonym>
 
 ## Examples
 
-    Via: 1.1 vegur
-    Via: HTTP/1.1 GWA
-    Via: 1.0 fred, 1.1 p.example.net
+```
+Via: 1.1 vegur
+Via: HTTP/1.1 GWA
+Via: 1.0 fred, 1.1 p.example.net
+```
 
 ## Specifications
 
diff --git a/files/en-us/web/http/headers/viewport-width/index.md b/files/en-us/web/http/headers/viewport-width/index.md
index 5d70bec287ba39d..53113cbb86f28bb 100644
--- a/files/en-us/web/http/headers/viewport-width/index.md
+++ b/files/en-us/web/http/headers/viewport-width/index.md
@@ -45,22 +45,28 @@ If the `Viewport-Width` header appears more than once in a message the last occu
 
 ## Syntax
 
-    Viewport-Width: <number>
+```
+Viewport-Width: <number>
+```
 
 ## Directives
 
-- `<number>`
+- \<number>
   - : The width of the user's viewport in {{Glossary("CSS pixel","CSS pixels")}}, rounded up to the nearest integer.
 
 ## Examples
 
 A server must first opt in to receive the `Viewport-Width` header by sending the response header {{HTTPHeader("Accept-CH")}} containing the directive `Viewport-Width`.
 
-    Accept-CH: Viewport-Width
+```
+Accept-CH: Viewport-Width
+```
 
 Then on subsequent requests the client might send `Viewport-Width` header back:
 
-    Viewport-Width: 320
+```
+Viewport-Width: 320
+```
 
 ## Browser compatibility
 
diff --git a/files/en-us/web/http/headers/want-digest/index.md b/files/en-us/web/http/headers/want-digest/index.md
index de16d9af1884247..df7c920b6909f62 100644
--- a/files/en-us/web/http/headers/want-digest/index.md
+++ b/files/en-us/web/http/headers/want-digest/index.md
@@ -49,7 +49,7 @@ information.
 
 ## Syntax
 
-```html
+```
 Want-Digest: <digest-algorithm>
 
 // Multiple algorithms, weighted with the quality value syntax:
@@ -58,18 +58,18 @@ Want-Digest: <digest-algorithm><q-value>,<digest-algorithm><q-value>
 
 ## Directives
 
-- `<digest-algorithm>`
+- \<digest-algorithm>
   - : Supported digest algorithms are defined in [RFC 3230](https://datatracker.ietf.org/doc/html/rfc3230) and [RFC 5843](https://datatracker.ietf.org/doc/html/rfc5843), and include
     `SHA-256` and `SHA-512`. Some of the supported algorithms,
     including `unixsum` and `MD5` are subject to collisions and are
     thus not suitable for applications in which collision-resistance is important.
-- `<q-value>`
+- \<q-value>
   - : The [quality value](/en-US/docs/Glossary/Quality_values) to apply to that
     option.
 
 ## Examples
 
-```html
+```
 Want-Digest: sha-256
 Want-Digest: SHA-512;q=0.3, sha-256;q=1, md5;q=0
 ```
@@ -79,44 +79,56 @@ Want-Digest: SHA-512;q=0.3, sha-256;q=1, md5;q=0
 The sender provides a list of digests which it is prepared to accept, and the server
 uses one of them:
 
-    Request:
+Request:
 
-      GET /item
-      Want-Digest: sha-256;q=0.3, sha;q=1
+```
+GET /item
+Want-Digest: sha-256;q=0.3, sha;q=1
+```
 
-    Response:
+Response:
 
-      HTTP/1.1 200 Ok
-      Digest: sha-256=X48E9qOokqqrvdts8nOJRJN3OWDUoyWxBf7kbu9DBPE=
+```
+HTTP/1.1 200 Ok
+Digest: sha-256=X48E9qOokqqrvdts8nOJRJN3OWDUoyWxBf7kbu9DBPE=
+```
 
 ### Unsupported digests
 
 The server does not support any of the requested digest algorithms, so uses a different
 algorithm:
 
-    Request:
+Request:
 
-      GET /item
-      Want-Digest: sha;q=1
+```
+GET /item
+Want-Digest: sha;q=1
+```
 
-    Response:
+Response:
 
-      HTTP/1.1 200 Ok
-      Digest: sha-256=X48E9qOokqqrvdts8nOJRJN3OWDUoyWxBf7kbu9DBPE=
+```
+HTTP/1.1 200 Ok
+Digest: sha-256=X48E9qOokqqrvdts8nOJRJN3OWDUoyWxBf7kbu9DBPE=
+```
 
 The server does not support any of the requested digest algorithms, so responds with a
 400 error and includes another `Want-Digest` header, listing the algorithms
 that it does support:
 
-    Request:
+Request:
 
-      GET /item
-      Want-Digest: sha;q=1
+```
+GET /item
+Want-Digest: sha;q=1
+```
 
-    Response:
+Response:
 
-      HTTP/1.1 400 Bad Request
-      Want-Digest: sha-256, sha-512
+```
+HTTP/1.1 400 Bad Request
+Want-Digest: sha-256, sha-512
+```
 
 ## Specifications
 
diff --git a/files/en-us/web/http/headers/warning/index.md b/files/en-us/web/http/headers/warning/index.md
index 87c06889c74ada1..b30968918966170 100644
--- a/files/en-us/web/http/headers/warning/index.md
+++ b/files/en-us/web/http/headers/warning/index.md
@@ -42,7 +42,7 @@ some warn-codes are specific to caches and can only be applied to response messa
 
 ## Syntax
 
-```html
+```
 Warning: <warn-code> <warn-agent> <warn-text> [<warn-date>]
 ```
 
@@ -71,8 +71,7 @@ Warning: <warn-code> <warn-agent> <warn-text> [<warn-date>]
 
 ## Warning codes
 
-The [HTTP Warn
-Codes registry at iana.org](https://www.iana.org/assignments/http-warn-codes/http-warn-codes.xhtml) defines the namespace for warn codes.
+The [HTTP Warn Codes registry at iana.org](https://www.iana.org/assignments/http-warn-codes/http-warn-codes.xhtml) defines the namespace for warn codes.
 
 | Code | Text                             | Description                                                                                                                           |
 | ---- | -------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------- |
@@ -86,10 +85,12 @@ Codes registry at iana.org](https://www.iana.org/assignments/http-warn-codes/htt
 
 ## Examples
 
-    Warning: 110 anderson/1.3.37 "Response is stale"
+```
+Warning: 110 anderson/1.3.37 "Response is stale"
 
-    Date: Wed, 21 Oct 2015 07:28:00 GMT
-    Warning: 112 - "cache down" "Wed, 21 Oct 2015 07:28:00 GMT"
+Date: Wed, 21 Oct 2015 07:28:00 GMT
+Warning: 112 - "cache down" "Wed, 21 Oct 2015 07:28:00 GMT"
+```
 
 ## Specifications
 
diff --git a/files/en-us/web/http/headers/width/index.md b/files/en-us/web/http/headers/width/index.md
index e07e15052802b82..f4d0fb093014361 100644
--- a/files/en-us/web/http/headers/width/index.md
+++ b/files/en-us/web/http/headers/width/index.md
@@ -47,22 +47,28 @@ If the `Width` header appears more than once in a message the last occurrence is
 
 ## Syntax
 
-    Width: <number>
+```
+Width: <number>
+```
 
 ## Directives
 
-- `<number>`
+- \<number>
   - : The width of the resource in physical pixels, rounded up to the nearest integer.
 
 ## Examples
 
 The server first needs to opt in to receive the `Width` header by sending the response headers {{HTTPHeader("Accept-CH")}} containing `Width`.
 
-    Accept-CH: Width
+```
+Accept-CH: Width
+```
 
 Then on subsequent requests the client might send `Width` header back:
 
-    Width: 1920
+```
+Width: 1920
+```
 
 ## Browser compatibility
 
diff --git a/files/en-us/web/http/headers/www-authenticate/index.md b/files/en-us/web/http/headers/www-authenticate/index.md
index c3251a52367939f..e2820f09b4f8870 100644
--- a/files/en-us/web/http/headers/www-authenticate/index.md
+++ b/files/en-us/web/http/headers/www-authenticate/index.md
@@ -30,7 +30,7 @@ The `WWW-Authenticate` header is sent along with a {{HTTPStatus("401")}} `Unauth
 
 ## Syntax
 
-```html
+```
 WWW-Authenticate: <type> realm=<realm>[, charset="UTF-8"]
 ```
 
@@ -47,7 +47,9 @@ WWW-Authenticate: <type> realm=<realm>[, charset="UTF-8"]
 
 Typically, a server response contains a `WWW-Authenticate` header that looks like this:
 
-    WWW-Authenticate: Basic realm="Access to the staging site", charset="UTF-8"
+```
+WWW-Authenticate: Basic realm="Access to the staging site", charset="UTF-8"
+```
 
 See also [HTTP authentication](/en-US/docs/Web/HTTP/Authentication) for examples on how to configure Apache or nginx servers to password protect your site with HTTP basic authentication.
 
diff --git a/files/en-us/web/http/headers/x-content-type-options/index.md b/files/en-us/web/http/headers/x-content-type-options/index.md
index fe767860bbd4235..8f62f0bec083fe1 100644
--- a/files/en-us/web/http/headers/x-content-type-options/index.md
+++ b/files/en-us/web/http/headers/x-content-type-options/index.md
@@ -51,7 +51,7 @@ Site security testers usually expect this header to be set.
 
 ## Syntax
 
-```html
+```
 X-Content-Type-Options: nosniff
 ```
 
@@ -78,12 +78,9 @@ X-Content-Type-Options: nosniff
 ## See also
 
 - {{HTTPHeader("Content-Type")}}
-- The [original
-  definition](https://blogs.msdn.microsoft.com/ie/2008/09/02/ie8-security-part-vi-beta-2-update/) of X-Content-Type-Options by Microsoft.
+- The [original definition](https://blogs.msdn.microsoft.com/ie/2008/09/02/ie8-security-part-vi-beta-2-update/) of X-Content-Type-Options by Microsoft.
 - The [Mozilla Observatory](https://observatory.mozilla.org/) tool testing
   the configuration (including this header) of Web sites for safety and security
-- [Mitigating
-  MIME Confusion Attacks in Firefox](https://blog.mozilla.org/security/2016/08/26/mitigating-mime-confusion-attacks-in-firefox/)
+- [Mitigating MIME Confusion Attacks in Firefox](https://blog.mozilla.org/security/2016/08/26/mitigating-mime-confusion-attacks-in-firefox/)
 - [Cross-Origin Read Blocking (CORB)](https://fetch.spec.whatwg.org/#corb)
-- [Google
-  Docs CORB explainer](https://chromium.googlesource.com/chromium/src/+/master/services/network/cross_origin_read_blocking_explainer.md)
+- [Google Docs CORB explainer](https://chromium.googlesource.com/chromium/src/+/master/services/network/cross_origin_read_blocking_explainer.md)
diff --git a/files/en-us/web/http/headers/x-dns-prefetch-control/index.md b/files/en-us/web/http/headers/x-dns-prefetch-control/index.md
index 622d7d981a30c9c..d4798087804f8ef 100644
--- a/files/en-us/web/http/headers/x-dns-prefetch-control/index.md
+++ b/files/en-us/web/http/headers/x-dns-prefetch-control/index.md
@@ -34,7 +34,7 @@ latency when the user clicks a link.
 
 ## Syntax
 
-```html
+```
 X-DNS-Prefetch-Control: on
 X-DNS-Prefetch-Control: off
 ```
diff --git a/files/en-us/web/http/headers/x-forwarded-for/index.md b/files/en-us/web/http/headers/x-forwarded-for/index.md
index e716071f899dc4c..f12027c83caf6d9 100644
--- a/files/en-us/web/http/headers/x-forwarded-for/index.md
+++ b/files/en-us/web/http/headers/x-forwarded-for/index.md
@@ -44,7 +44,7 @@ was forwarded from another account.
 
 ## Syntax
 
-```html
+```
 X-Forwarded-For: <client>, <proxy1>, <proxy2>
 ```
 
@@ -59,16 +59,20 @@ X-Forwarded-For: <client>, <proxy1>, <proxy2>
 
 ## Examples
 
-    X-Forwarded-For: 2001:db8:85a3:8d3:1319:8a2e:370:7348
+```
+X-Forwarded-For: 2001:db8:85a3:8d3:1319:8a2e:370:7348
 
-    X-Forwarded-For: 203.0.113.195
+X-Forwarded-For: 203.0.113.195
 
-    X-Forwarded-For: 203.0.113.195, 70.41.3.18, 150.172.238.178
+X-Forwarded-For: 203.0.113.195, 70.41.3.18, 150.172.238.178
+```
 
 Other non-standard forms:
 
-    # Used for some Google services
-    X-ProxyUser-Ip: 203.0.113.19
+```
+# Used for some Google services
+X-ProxyUser-Ip: 203.0.113.19
+```
 
 ## Specifications
 
diff --git a/files/en-us/web/http/headers/x-forwarded-host/index.md b/files/en-us/web/http/headers/x-forwarded-host/index.md
index b79ca66e5c3c696..5765f4d31ff57e5 100644
--- a/files/en-us/web/http/headers/x-forwarded-host/index.md
+++ b/files/en-us/web/http/headers/x-forwarded-host/index.md
@@ -42,7 +42,7 @@ A standardized version of this header is the HTTP {{HTTPHeader("Forwarded")}} he
 
 ## Syntax
 
-```html
+```
 X-Forwarded-Host: <host>
 ```
 
@@ -53,7 +53,9 @@ X-Forwarded-Host: <host>
 
 ## Examples
 
-    X-Forwarded-Host: id42.example-cdn.com
+```
+X-Forwarded-Host: id42.example-cdn.com
+```
 
 ## Specifications
 
diff --git a/files/en-us/web/http/headers/x-forwarded-proto/index.md b/files/en-us/web/http/headers/x-forwarded-proto/index.md
index b1c66eddd3dc19e..8bdcbca934e6b58 100644
--- a/files/en-us/web/http/headers/x-forwarded-proto/index.md
+++ b/files/en-us/web/http/headers/x-forwarded-proto/index.md
@@ -36,7 +36,7 @@ A standardized version of this header is the HTTP {{HTTPHeader("Forwarded")}} he
 
 ## Syntax
 
-```html
+```
 X-Forwarded-Proto: <protocol>
 ```
 
@@ -47,16 +47,20 @@ X-Forwarded-Proto: <protocol>
 
 ## Examples
 
-    X-Forwarded-Proto: https
+```
+X-Forwarded-Proto: https
+```
 
 Other non-standard forms:
 
-    # Microsoft
-    Front-End-Https: on
+```
+# Microsoft
+Front-End-Https: on
 
-    X-Forwarded-Protocol: https
-    X-Forwarded-Ssl: on
-    X-Url-Scheme: https
+X-Forwarded-Protocol: https
+X-Forwarded-Ssl: on
+X-Url-Scheme: https
+```
 
 ## Specifications
 
diff --git a/files/en-us/web/http/headers/x-frame-options/index.md b/files/en-us/web/http/headers/x-frame-options/index.md
index 4039cdd84063c8f..7228e17ff05ed2b 100644
--- a/files/en-us/web/http/headers/x-frame-options/index.md
+++ b/files/en-us/web/http/headers/x-frame-options/index.md
@@ -35,7 +35,7 @@ The added security is provided only if the user accessing the document is using
 
 There are two possible directives for `X-Frame-Options`:
 
-```html
+```
 X-Frame-Options: DENY
 X-Frame-Options: SAMEORIGIN
 ```
@@ -59,33 +59,41 @@ If you specify `DENY`, not only will attempts to load the page in a frame fail w
 
 To configure Apache to send the `X-Frame-Options` header for all pages, add this to your site's configuration:
 
-    Header always set X-Frame-Options "SAMEORIGIN"
+```
+Header always set X-Frame-Options "SAMEORIGIN"
+``
 
 To configure Apache to set the `X-Frame-Options` DENY, add this to your site's configuration:
 
-    Header set X-Frame-Options "DENY"
+```
+Header set X-Frame-Options "DENY"
+```
 
 ### Configuring nginx
 
 To configure nginx to send the `X-Frame-Options` header, add this either to your http, server or location configuration:
 
-    add_header X-Frame-Options SAMEORIGIN always;
+```
+add_header X-Frame-Options SAMEORIGIN always;
+```
 
 ### Configuring IIS
 
 To configure IIS to send the `X-Frame-Options` header, add this to your site's `Web.config` file:
 
-    <system.webServer>
-      ...
+```html
+<system.webServer>
+  ...
 
-      <httpProtocol>
-        <customHeaders>
-          <add name="X-Frame-Options" value="SAMEORIGIN" />
-        </customHeaders>
-      </httpProtocol>
+  <httpProtocol>
+    <customHeaders>
+      <add name="X-Frame-Options" value="SAMEORIGIN" />
+    </customHeaders>
+  </httpProtocol>
 
-      ...
-    </system.webServer>
+  ...
+</system.webServer>
+```
 
 Or see this [Microsoft support article on setting this configuration using the IIS Manager](https://support.office.com/en-us/article/Mitigating-framesniffing-with-the-X-Frame-Options-header-1911411b-b51e-49fd-9441-e8301dcdcd79) user interface.
 
@@ -93,11 +101,15 @@ Or see this [Microsoft support article on setting this configuration using the I
 
 To configure HAProxy to send the `X-Frame-Options` header, add this to your front-end, listen, or backend configuration:
 
-    rspadd X-Frame-Options:\ SAMEORIGIN
+```
+rspadd X-Frame-Options:\ SAMEORIGIN
+```
 
 Alternatively, in newer versions:
 
-    http-response set-header X-Frame-Options SAMEORIGIN
+```
+http-response set-header X-Frame-Options SAMEORIGIN
+```
 
 ### Configuring Express
 
diff --git a/files/en-us/web/http/headers/x-xss-protection/index.md b/files/en-us/web/http/headers/x-xss-protection/index.md
index 98430f9562e238c..1ce5429dcd95661 100644
--- a/files/en-us/web/http/headers/x-xss-protection/index.md
+++ b/files/en-us/web/http/headers/x-xss-protection/index.md
@@ -36,7 +36,7 @@ The HTTP **`X-XSS-Protection`** response header is a feature of Internet Explore
 
 ## Syntax
 
-```html
+```
 X-XSS-Protection: 0
 X-XSS-Protection: 1
 X-XSS-Protection: 1; mode=block
@@ -56,17 +56,19 @@ X-XSS-Protection: 1; report=<reporting-uri>
 
 Block pages from loading when they detect reflected XSS attacks:
 
-```bash
+```
 X-XSS-Protection: 1; mode=block
 ```
 
 PHP
 
-    header("X-XSS-Protection: 1; mode=block");
+```php
+header("X-XSS-Protection: 1; mode=block");
+```
 
 Apache (.htaccess)
 
-```bash
+```html
 <IfModule mod_headers.c>
   Header set X-XSS-Protection "1; mode=block"
 </IfModule>
@@ -74,7 +76,7 @@ Apache (.htaccess)
 
 Nginx
 
-```bash
+```
 add_header "X-XSS-Protection" "1; mode=block";
 ```
 
diff --git a/files/en-us/web/http/link_prefetching_faq/index.md b/files/en-us/web/http/link_prefetching_faq/index.md
index e31a7366a628c40..887907780675b39 100644
--- a/files/en-us/web/http/link_prefetching_faq/index.md
+++ b/files/en-us/web/http/link_prefetching_faq/index.md
@@ -23,11 +23,15 @@ Starting in Gecko 1.9.1 (Firefox 3.5), HTTPS content can be prefetched.
 
 The browser looks for either an HTML {{ HTMLElement("link") }} or an [HTTP `Link:` header](/en-US/docs/Web/HTTP/Headers "HTTP headers") with a relation type of either `next` or `prefetch`. An example using the `link` tag follows:
 
-    <link rel="prefetch" href="/images/big.jpeg">
+```html
+<link rel="prefetch" href="/images/big.jpeg">
+```
 
 The same prefetching hint using an HTTP `Link:` header:
 
-    Link: </images/big.jpeg>; rel=prefetch
+```
+Link: </images/big.jpeg>; rel=prefetch
+```
 
 The format for the `Link:` header is described in [RFC 5988](https://datatracker.ietf.org/doc/html/rfc5988) section 5.
 
@@ -35,8 +39,10 @@ The browser observes all of these hints and queues up each unique request to be
 
 Some more examples follow:
 
-    <link rel="prefetch alternate stylesheet" title="Designed for Mozilla" href="mozspecific.css">
-    <link rel="next" href="2.html">
+```html
+<link rel="prefetch alternate stylesheet" title="Designed for Mozilla" href="mozspecific.css">
+<link rel="next" href="2.html">
+```
 
 ### Are anchor (\<a>) tags prefetched?
 
@@ -78,7 +84,9 @@ This may impact referrer tracking that is commonly used on many sites. For this
 
 Yes, we send the following header along with each prefetch request:
 
-    X-moz: prefetch
+```
+X-moz: prefetch
+```
 
 Of course, this request header is not at all standardized, and it may change in future Mozilla releases. Chrome uses "X-Purpose: prefetch" or "Purpose: prefetch" [header](https://bugs.webkit.org/show_bug.cgi?id=46529).
 
@@ -86,7 +94,9 @@ Of course, this request header is not at all standardized, and it may change in
 
 Yes, there is a hidden preference that you can set to disable link prefetching. Add this line to your prefs.js file located in your profile directory (or make the appropriate change via `about:config`:
 
-    user_pref("network.prefetch-next", false);
+```js
+user_pref("network.prefetch-next", false);
+```
 
 However, the theory is that if link prefetching needs to be disabled then there must be something wrong with the implementation. We would rather improve the implementation if it does not work correctly, than expect users to locate and tweak some obscure preference.
 
diff --git a/files/en-us/web/http/methods/connect/index.md b/files/en-us/web/http/methods/connect/index.md
index 840faee8fa0cfdb..1658397fd2d4157 100644
--- a/files/en-us/web/http/methods/connect/index.md
+++ b/files/en-us/web/http/methods/connect/index.md
@@ -55,7 +55,7 @@ from the client.
 
 ## Syntax
 
-```html
+```
 CONNECT www.example.com:443 HTTP/1.1
 ```
 
@@ -64,9 +64,11 @@ CONNECT www.example.com:443 HTTP/1.1
 Some proxy servers might need authority to create a tunnel. See also the
 {{HTTPHeader("Proxy-Authorization")}} header.
 
-    CONNECT server.example.com:80 HTTP/1.1
-    Host: server.example.com:80
-    Proxy-Authorization: basic aGVsbG86d29ybGQ=
+```
+CONNECT server.example.com:80 HTTP/1.1
+Host: server.example.com:80
+Proxy-Authorization: basic aGVsbG86d29ybGQ=
+```
 
 ## Specifications
 
diff --git a/files/en-us/web/http/methods/delete/index.md b/files/en-us/web/http/methods/delete/index.md
index 562b5552e4baeef..8fac5e1059679e3 100644
--- a/files/en-us/web/http/methods/delete/index.md
+++ b/files/en-us/web/http/methods/delete/index.md
@@ -45,7 +45,7 @@ resource.
 
 ## Syntax
 
-```html
+```
 DELETE /file.html HTTP/1.1
 ```
 
@@ -53,8 +53,10 @@ DELETE /file.html HTTP/1.1
 
 ### Request
 
-    DELETE /file.html HTTP/1.1
-    Host: example.com
+```
+DELETE /file.html HTTP/1.1
+Host: example.com
+```
 
 ### Responses
 
@@ -68,16 +70,16 @@ status codes possible:
 - A {{HTTPStatus("200")}} (`OK`) status code if the action has been enacted
   and the response message includes a representation describing the status.
 
-<!---->
-
-    HTTP/1.1 200 OK
-    Date: Wed, 21 Oct 2015 07:28:00 GMT
-
-    <html>
-      <body>
-        <h1>File deleted.</h1>
-      </body>
-    </html>
+```
+HTTP/1.1 200 OK
+Date: Wed, 21 Oct 2015 07:28:00 GMT
+
+<html>
+  <body>
+    <h1>File deleted.</h1>
+  </body>
+</html>
+````
 
 ## Specifications
 
diff --git a/files/en-us/web/http/methods/get/index.md b/files/en-us/web/http/methods/get/index.md
index 57595de0ec3d730..672cdedb4cab525 100644
--- a/files/en-us/web/http/methods/get/index.md
+++ b/files/en-us/web/http/methods/get/index.md
@@ -44,7 +44,7 @@ The **HTTP `GET` method** requests a representation of the specified resource. R
 
 ## Syntax
 
-```html
+```
 GET /index.html
 ```
 
diff --git a/files/en-us/web/http/methods/head/index.md b/files/en-us/web/http/methods/head/index.md
index f4c42fbf6049286..2c7e8c0130c54a4 100644
--- a/files/en-us/web/http/methods/head/index.md
+++ b/files/en-us/web/http/methods/head/index.md
@@ -48,7 +48,7 @@ If the response to a `HEAD` request shows that a cached URL response is now outd
 
 ## Syntax
 
-```html
+```
 HEAD /index.html
 ```
 
diff --git a/files/en-us/web/http/methods/options/index.md b/files/en-us/web/http/methods/options/index.md
index 0ba14514819d1d5..c3d6e582d4a065f 100644
--- a/files/en-us/web/http/methods/options/index.md
+++ b/files/en-us/web/http/methods/options/index.md
@@ -42,7 +42,7 @@ The **HTTP `OPTIONS` method** requests permitted communication options for a giv
 
 ## Syntax
 
-```html
+```
 OPTIONS /index.html HTTP/1.1
 OPTIONS * HTTP/1.1
 ```
@@ -59,11 +59,13 @@ curl -X OPTIONS https://example.org -i
 
 The response then contains an {{HTTPHeader("Allow")}} header that holds the allowed methods:
 
-    HTTP/1.1 204 No Content
-    Allow: OPTIONS, GET, HEAD, POST
-    Cache-Control: max-age=604800
-    Date: Thu, 13 Oct 2016 11:45:00 GMT
-    Server: EOS (lax004/2813)
+```
+HTTP/1.1 204 No Content
+Allow: OPTIONS, GET, HEAD, POST
+Cache-Control: max-age=604800
+Date: Thu, 13 Oct 2016 11:45:00 GMT
+Server: EOS (lax004/2813)
+```
 
 ### Preflighted requests in CORS
 
@@ -72,17 +74,17 @@ In [CORS](/en-US/docs/Web/HTTP/CORS), a [preflight request](/en-US/docs/Glossary
 - The {{HTTPHeader("Access-Control-Request-Method")}} header sent in the preflight request tells the server that when the actual request is sent, it will have a {{HTTPMethod("POST")}} request method.
 - The {{HTTPHeader("Access-Control-Request-Headers")}} header tells the server that when the actual request is sent, it will have the `X-PINGOTHER` and `Content-Type` headers.
 
-<!---->
-
-    OPTIONS /resources/post-here/ HTTP/1.1
-    Host: bar.example
-    Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
-    Accept-Language: en-us,en;q=0.5
-    Accept-Encoding: gzip,deflate
-    Connection: keep-alive
-    Origin: https://foo.example
-    Access-Control-Request-Method: POST
-    Access-Control-Request-Headers: X-PINGOTHER, Content-Type
+```
+OPTIONS /resources/post-here/ HTTP/1.1
+Host: bar.example
+Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
+Accept-Language: en-us,en;q=0.5
+Accept-Encoding: gzip,deflate
+Connection: keep-alive
+Origin: https://foo.example
+Access-Control-Request-Method: POST
+Access-Control-Request-Headers: X-PINGOTHER, Content-Type
+```
 
 The server now can respond if it will accept a request under these circumstances. In this example, the server response says that:
 
@@ -95,18 +97,18 @@ The server now can respond if it will accept a request under these circumstances
 - {{HTTPHeader("Access-Control-Max-Age")}}
   - : The above permissions may be cached for 86,400 seconds (1 day).
 
-<!---->
-
-    HTTP/1.1 204 No Content
-    Date: Mon, 01 Dec 2008 01:15:39 GMT
-    Server: Apache/2.0.61 (Unix)
-    Access-Control-Allow-Origin: https://foo.example
-    Access-Control-Allow-Methods: POST, GET, OPTIONS
-    Access-Control-Allow-Headers: X-PINGOTHER, Content-Type
-    Access-Control-Max-Age: 86400
-    Vary: Accept-Encoding, Origin
-    Keep-Alive: timeout=2, max=100
-    Connection: Keep-Alive
+```
+HTTP/1.1 204 No Content
+Date: Mon, 01 Dec 2008 01:15:39 GMT
+Server: Apache/2.0.61 (Unix)
+Access-Control-Allow-Origin: https://foo.example
+Access-Control-Allow-Methods: POST, GET, OPTIONS
+Access-Control-Allow-Headers: X-PINGOTHER, Content-Type
+Access-Control-Max-Age: 86400
+Vary: Accept-Encoding, Origin
+Keep-Alive: timeout=2, max=100
+Connection: Keep-Alive
+```
 
 ## Specifications
 
diff --git a/files/en-us/web/http/methods/patch/index.md b/files/en-us/web/http/methods/patch/index.md
index bef08960d5e2b68..93923834c01e309 100644
--- a/files/en-us/web/http/methods/patch/index.md
+++ b/files/en-us/web/http/methods/patch/index.md
@@ -55,7 +55,7 @@ Another (implicit) indication that `PATCH` is allowed, is the presence of the {{
 
 ## Syntax
 
-```html
+```
 PATCH /file.txt HTTP/1.1
 ```
 
@@ -63,13 +63,15 @@ PATCH /file.txt HTTP/1.1
 
 ### Request
 
-    PATCH /file.txt HTTP/1.1
-    Host: www.example.com
-    Content-Type: application/example
-    If-Match: "e0023aa4e"
-    Content-Length: 100
+```
+PATCH /file.txt HTTP/1.1
+Host: www.example.com
+Content-Type: application/example
+If-Match: "e0023aa4e"
+Content-Length: 100
 
-    [description of changes]
+[description of changes]
+```
 
 ### Response
 
@@ -77,9 +79,11 @@ A successful response is indicated by any [2xx](https://datatracker.ietf.org/doc
 
 In the example below a {{HTTPStatus("204")}} response code is used, because the response does not carry a payload body. A {{HTTPStatus("200")}} response could have contained a payload body.
 
-    HTTP/1.1 204 No Content
-    Content-Location: /file.txt
-    ETag: "e0023aa4f"
+```
+HTTP/1.1 204 No Content
+Content-Location: /file.txt
+ETag: "e0023aa4f"
+```
 
 ## Specifications
 
diff --git a/files/en-us/web/http/methods/post/index.md b/files/en-us/web/http/methods/post/index.md
index 6b6351ee5a91f76..2214292d15317c3 100644
--- a/files/en-us/web/http/methods/post/index.md
+++ b/files/en-us/web/http/methods/post/index.md
@@ -60,7 +60,7 @@ When the `POST` request is sent via a method other than an HTML form — like vi
 
 ## Syntax
 
-```html
+```
 POST /test
 ```
 
@@ -68,28 +68,32 @@ POST /test
 
 A simple form using the default `application/x-www-form-urlencoded` content type:
 
-    POST /test HTTP/1.1
-    Host: foo.example
-    Content-Type: application/x-www-form-urlencoded
-    Content-Length: 27
+```
+POST /test HTTP/1.1
+Host: foo.example
+Content-Type: application/x-www-form-urlencoded
+Content-Length: 27
 
-    field1=value1&field2=value2
+field1=value1&field2=value2
+```
 
 A form using the `multipart/form-data` content type:
 
-    POST /test HTTP/1.1
-    Host: foo.example
-    Content-Type: multipart/form-data;boundary="boundary"
+```
+POST /test HTTP/1.1
+Host: foo.example
+Content-Type: multipart/form-data;boundary="boundary"
 
-    --boundary
-    Content-Disposition: form-data; name="field1"
+--boundary
+Content-Disposition: form-data; name="field1"
 
-    value1
-    --boundary
-    Content-Disposition: form-data; name="field2"; filename="example.txt"
+value1
+--boundary
+Content-Disposition: form-data; name="field2"; filename="example.txt"
 
-    value2
-    --boundary--
+value2
+--boundary--
+```
 
 ## Specifications
 
diff --git a/files/en-us/web/http/methods/put/index.md b/files/en-us/web/http/methods/put/index.md
index b1b5e8febbf3987..7f3525294ccf85c 100644
--- a/files/en-us/web/http/methods/put/index.md
+++ b/files/en-us/web/http/methods/put/index.md
@@ -46,7 +46,7 @@ The difference between `PUT` and {{HTTPMethod("POST")}} is that `PUT` is idempot
 
 ## Syntax
 
-```html
+```
 PUT /new.html HTTP/1.1
 ```
 
@@ -54,12 +54,14 @@ PUT /new.html HTTP/1.1
 
 ### Request
 
-    PUT /new.html HTTP/1.1
-    Host: example.com
-    Content-type: text/html
-    Content-length: 16
+```
+PUT /new.html HTTP/1.1
+Host: example.com
+Content-type: text/html
+Content-length: 16
 
-    <p>New File</p>
+<p>New File</p>
+```
 
 ### Responses
 
diff --git a/files/en-us/web/http/methods/trace/index.md b/files/en-us/web/http/methods/trace/index.md
index 0af4762aa7cec53..c4000066d73d992 100644
--- a/files/en-us/web/http/methods/trace/index.md
+++ b/files/en-us/web/http/methods/trace/index.md
@@ -44,7 +44,7 @@ The final recipient of the request should reflect the message received, excludin
 
 ## Syntax
 
-```html
+```
 TRACE /index.html
 ```
 
diff --git a/files/en-us/web/http/network_error_logging/index.md b/files/en-us/web/http/network_error_logging/index.md
index cfb427df7fbe8bc..1f5851b829cb4b6 100644
--- a/files/en-us/web/http/network_error_logging/index.md
+++ b/files/en-us/web/http/network_error_logging/index.md
@@ -17,8 +17,10 @@ Reports are sent to a reporting group defined within a {{HTTPHeader("Report-To")
 
 Web applications opt in to this behavior with the NEL header, which is a _[JSON-encoded](/en-US/docs/Glossary/Response_header)_ object:
 
-    NEL: { "report_to": "nel",
-           "max_age": 31556952 }
+```
+NEL: { "report_to": "nel",
+       "max_age": 31556952 }
+```
 
 An origin considered secure by the browser is required.
 
@@ -37,11 +39,14 @@ The following object keys can be specified in the NEL header:
 
 The reporting group referenced above is defined in the usual manner within the {{HTTPHeader("Report-To")}} header, for example:
 
-    Report-To: { "group": "nel",
-                 "max_age": 31556952,
-                 "endpoints": [
-                   { "url": "https://example.com/csp-reports" }
-                 ] }
+```
+Report-To: { "group": "nel",
+             "max_age": 31556952,
+             "endpoints": [
+              { "url": "https://example.com/csp-reports" }
+             ]
+           }
+```
 
 ## Error reports
 
diff --git a/files/en-us/web/http/overview/index.md b/files/en-us/web/http/overview/index.md
index dbca02c49765fd6..3372456db259730 100644
--- a/files/en-us/web/http/overview/index.md
+++ b/files/en-us/web/http/overview/index.md
@@ -102,22 +102,26 @@ When a client wants to communicate with a server, either the final server or an
 1. Open a TCP connection: The TCP connection is used to send a request, or several, and receive an answer. The client may open a new connection, reuse an existing connection, or open several TCP connections to the servers.
 2. Send an HTTP message: HTTP messages (before HTTP/2) are human-readable. With HTTP/2, these simple messages are encapsulated in frames, making them impossible to read directly, but the principle remains the same. For example:
 
-        GET / HTTP/1.1
-        Host: developer.mozilla.org
-        Accept-Language: fr
+```
+GET / HTTP/1.1
+Host: developer.mozilla.org
+Accept-Language: fr
+```
 
 3. Read the response sent by the server, such as:
 
-        HTTP/1.1 200 OK
-        Date: Sat, 09 Oct 2010 14:28:02 GMT
-        Server: Apache
-        Last-Modified: Tue, 01 Dec 2009 20:18:22 GMT
-        ETag: "51142bc1-7449-479b075b2891b"
-        Accept-Ranges: bytes
-        Content-Length: 29769
-        Content-Type: text/html
-
-        <!DOCTYPE html... (here comes the 29769 bytes of the requested web page)
+```
+HTTP/1.1 200 OK
+Date: Sat, 09 Oct 2010 14:28:02 GMT
+Server: Apache
+Last-Modified: Tue, 01 Dec 2009 20:18:22 GMT
+ETag: "51142bc1-7449-479b075b2891b"
+Accept-Ranges: bytes
+Content-Length: 29769
+Content-Type: text/html
+```
+
+<!DOCTYPE html... (here comes the 29769 bytes of the requested web page)
 
 4. Close or reuse the connection for further requests.
 
diff --git a/files/en-us/web/http/protocol_upgrade_mechanism/index.md b/files/en-us/web/http/protocol_upgrade_mechanism/index.md
index 66b7b9034de7076..ab1d0d911c90184 100644
--- a/files/en-us/web/http/protocol_upgrade_mechanism/index.md
+++ b/files/en-us/web/http/protocol_upgrade_mechanism/index.md
@@ -25,7 +25,7 @@ The {{HTTPHeader("Upgrade")}} header field is used by clients to invite the serv
 
 Because `Upgrade` is a hop-by-hop header, it also needs to be listed in the {{HTTPHeader("Connection")}} header field. This means that a typical request that includes Upgrade would look something like:
 
-```html
+```
 GET /index.html HTTP/1.1
 Host: www.example.com
 Connection: upgrade
@@ -56,8 +56,10 @@ The {{domxref("WebSocket.WebSocket", "WebSocket()")}} constructor does all the w
 
 If you need to create a WebSocket connection from scratch, you'll have to handle the handshaking process yourself. After creating the initial HTTP/1.1 session, you need to request the upgrade by adding to a standard request the {{HTTPHeader("Upgrade")}} and {{HTTPHeader("Connection")}} headers, as follows:
 
-    Connection: Upgrade
-    Upgrade: websocket
+```
+Connection: Upgrade
+Upgrade: websocket
+```
 
 ### WebSocket-specific headers
 
@@ -67,7 +69,7 @@ The following headers are involved in the WebSocket upgrade process. Other than
 
 Specifies one or more protocol-level WebSocket extensions to ask the server to use. Using more than one `Sec-WebSocket-Extension` header in a request is permitted; the result is the same as if you included all of the listed extensions in one such header.
 
-```html
+```
 Sec-WebSocket-Extensions: extensions
 ```
 
@@ -76,7 +78,9 @@ Sec-WebSocket-Extensions: extensions
 
 For example:
 
-    Sec-WebSocket-Extensions: superspeed, colormode; depth=16
+```
+Sec-WebSocket-Extensions: superspeed, colormode; depth=16
+```
 
 #### {{HTTPHeader("Sec-WebSocket-Key")}}
 
@@ -84,7 +88,7 @@ Provides information to the server which is needed in order to confirm that the
 
 This header is automatically added by clients that choose to use it; it cannot be added using the {{domxref("XMLHttpRequest.setRequestHeader()")}} method.
 
-```html
+```
 Sec-WebSocket-Key: key
 ```
 
@@ -97,7 +101,7 @@ The server's response's {{HTTPHeader("Sec-WebSocket-Accept")}} header will have
 
 The `Sec-WebSocket-Protocol` header specifies one or more WebSocket protocols that you wish to use, in order of preference. The first one that is supported by the server will be selected and returned by the server in a `Sec-WebSocket-Protocol` header included in the response. You can use this more than once in the header, as well; the result is the same as if you used a comma-delineated list of subprotocol identifiers in a single header.
 
-```html
+```
 Sec-WebSocket-Protocol: subprotocols
 ```
 
@@ -110,7 +114,7 @@ Sec-WebSocket-Protocol: subprotocols
 
 Specifies the WebSocket protocol version the client wishes to use, so the server can confirm whether or not that version is supported on its end.
 
-```html
+```
 Sec-WebSocket-Version: version
 ```
 
@@ -121,7 +125,7 @@ Sec-WebSocket-Version: version
 
 If the server can't communicate using the specified version of the WebSocket protocol, it will respond with an error (such as 426 Upgrade Required) that includes in its headers a `Sec-WebSocket-Version` header with a comma-separated list of the supported protocol versions. If the server does support the requested protocol version, no `Sec-WebSocket-Version` header is included in the response.
 
-```html
+```
 Sec-WebSocket-Version: supportedVersions
 ```
 
@@ -136,7 +140,7 @@ The response from the server may include these.
 
 Included in the response message from the server during the opening handshake process when the server is willing to initiate a WebSocket connection. It will appear no more than once in the response headers.
 
-```html
+```
 Sec-WebSocket-Accept: hash
 ```
 
diff --git a/files/en-us/web/http/public_key_pinning/index.md b/files/en-us/web/http/public_key_pinning/index.md
index 58792dbf4cc2630..17663aa9b6e0dd0 100644
--- a/files/en-us/web/http/public_key_pinning/index.md
+++ b/files/en-us/web/http/public_key_pinning/index.md
@@ -25,7 +25,9 @@ HPKP is a _Trust on First Use_ ({{Glossary("TOFU")}}) technique. The first time
 
 To enable this feature for your site, you need to return the {{HTTPHeader("Public-Key-Pins")}} HTTP header when your site is accessed over HTTPS:
 
-    Public-Key-Pins: pin-sha256="base64=="; max-age=expireTime [; includeSubDomains][; report-uri="reportURI"]
+```
+Public-Key-Pins: pin-sha256="base64=="; max-age=expireTime [; includeSubDomains][; report-uri="reportURI"]
+```
 
 - `pin-sha256`
   - : The quoted string is the Base64 encoded _Subject Public Key Information_ ({{Glossary("SPKI")}}) fingerprint. It is possible to specify multiple pins for different public keys. Some browsers might allow other hashing algorithms than SHA-256 in the future. See below on how to extract this information out of a certificate or key file.
@@ -46,31 +48,31 @@ First you need to extract the public key information from your certificate or ke
 
 The following commands will help you extract the Base64 encoded information from a key file, a certificate signing request, or a certificate.
 
-    openssl rsa -in my-rsa-key-file.key -outform der -pubout | openssl dgst -sha256 -binary | openssl enc -base64
+```
+openssl rsa -in my-rsa-key-file.key -outform der -pubout | openssl dgst -sha256 -binary | openssl enc -base64
 
-<!---->
+openssl ec -in my-ecc-key-file.key -outform der -pubout | openssl dgst -sha256 -binary | openssl enc -base64
 
-    openssl ec -in my-ecc-key-file.key -outform der -pubout | openssl dgst -sha256 -binary | openssl enc -base64
+openssl req -in my-signing-request.csr -pubkey -noout | openssl pkey -pubin -outform der | openssl dgst -sha256 -binary | openssl enc -base64
 
-<!---->
-
-    openssl req -in my-signing-request.csr -pubkey -noout | openssl pkey -pubin -outform der | openssl dgst -sha256 -binary | openssl enc -base64
-
-<!---->
-
-    openssl x509 -in my-certificate.crt -pubkey -noout | openssl pkey -pubin -outform der | openssl dgst -sha256 -binary | openssl enc -base64
+openssl x509 -in my-certificate.crt -pubkey -noout | openssl pkey -pubin -outform der | openssl dgst -sha256 -binary | openssl enc -base64
+```
 
 The following command will extract the Base64 encoded information for a website.
 
-    openssl s_client -servername www.example.com -connect www.example.com:443 | openssl x509 -pubkey -noout | openssl pkey -pubin -outform der | openssl dgst -sha256 -binary | openssl enc -base64
+```
+openssl s_client -servername www.example.com -connect www.example.com:443 | openssl x509 -pubkey -noout | openssl pkey -pubin -outform der | openssl dgst -sha256 -binary | openssl enc -base64
+```
 
 ### Example HPKP Header
 
-    Public-Key-Pins:
-      pin-sha256="cUPcTAZWKaASuYWhhneDttWpY3oBAkE3h2+soZS7sWs=";
-      pin-sha256="M8HztCzM3elUxkcjR2S5P4hhyBNf6lHkmjAHKhpGPWE=";
-      max-age=5184000; includeSubDomains;
-      report-uri="https://www.example.org/hpkp-report"
+```
+Public-Key-Pins:
+  pin-sha256="cUPcTAZWKaASuYWhhneDttWpY3oBAkE3h2+soZS7sWs=";
+  pin-sha256="M8HztCzM3elUxkcjR2S5P4hhyBNf6lHkmjAHKhpGPWE=";
+  max-age=5184000; includeSubDomains;
+  report-uri="https://www.example.org/hpkp-report"
+```
 
 In this example, **pin-sha256="cUPcTAZWKaASuYWhhneDttWpY3oBAkE3h2+soZS7sWs="** pins the server's public key used in production. The second pin declaration **pin-sha256="M8HztCzM3elUxkcjR2S5P4hhyBNf6lHkmjAHKhpGPWE="** also pins the backup key. **max-age=5184000** tells the client to store this information for two months, which is a reasonable time limit according to the IETF RFC. This key pinning is also valid for all subdomains, which is told by the **includeSubDomains** declaration. Finally, **report-uri="https\://www\.example.net/hpkp-report"** explains where to report pin validation failures.
 
@@ -90,39 +92,49 @@ The concrete steps necessary to deliver the HPKP header depend on the web server
 
 Adding a line similar to the following to your webserver's config will enable HPKP on your Apache. This requires `mod_headers` enabled.
 
-    Header always set Public-Key-Pins "pin-sha256=\"base64+primary==\"; pin-sha256=\"base64+backup==\"; max-age=5184000; includeSubDomains"
+```
+Header always set Public-Key-Pins "pin-sha256=\"base64+primary==\"; pin-sha256=\"base64+backup==\"; max-age=5184000; includeSubDomains"
+```
 
 #### Nginx
 
 Adding the following line and inserting the appropriate `pin-sha256="..."` values will enable HPKP on your nginx. This requires the `ngx_http_headers_module.`
 
-    add_header Public-Key-Pins 'pin-sha256="base64+primary=="; pin-sha256="base64+backup=="; max-age=5184000; includeSubDomains' always;
+```
+add_header Public-Key-Pins 'pin-sha256="base64+primary=="; pin-sha256="base64+backup=="; max-age=5184000; includeSubDomains' always;
+```
 
 #### Lighttpd
 
 The following line with your relevant key information (pin-sha256="..." fields) will enable HPKP on lighttpd.
 
-    setenv.add-response-header  = ( "Public-Key-Pins" => "pin-sha256=\"base64+primary==\"; pin-sha256=\"base64+backup==\"; max-age=5184000; includeSubDomains")
+```
+setenv.add-response-header  = ( "Public-Key-Pins" => "pin-sha256=\"base64+primary==\"; pin-sha256=\"base64+backup==\"; max-age=5184000; includeSubDomains")
+```
 
 **Note:** This requires the `mod_setenv` server.module loaded which can be included by the following if not already loaded.
 
-    server.modules += ( "mod_setenv" )
+```
+server.modules += ( "mod_setenv" )
+```
 
 #### IIS
 
 Add the following line to the Web.config file to send the `Public-Key-Pins` header:
 
-    <system.webServer>
-      ...
+```
+<system.webServer>
+  ...
 
-      <httpProtocol>
-        <customHeaders>
-          <add name="Public-Key-Pins" value="pin-sha256=&quot;base64+primary==&quot;; pin-sha256=&quot;base64+backup==&quot;; max-age=5184000; includeSubDomains" />
-        </customHeaders>
-      </httpProtocol>
+  <httpProtocol>
+    <customHeaders>
+      <add name="Public-Key-Pins" value="pin-sha256=&quot;base64+primary==&quot;; pin-sha256=&quot;base64+backup==&quot;; max-age=5184000; includeSubDomains" />
+    </customHeaders>
+  </httpProtocol>
 
-      ...
-    </system.webServer>
+  ...
+</system.webServer>
+```
 
 ## Specifications
 
diff --git a/files/en-us/web/http/range_requests/index.md b/files/en-us/web/http/range_requests/index.md
index 34accaa3db68caf..6a704da5d434205 100644
--- a/files/en-us/web/http/range_requests/index.md
+++ b/files/en-us/web/http/range_requests/index.md
@@ -14,22 +14,26 @@ HTTP range requests allow to send only a portion of an HTTP message from a serve
 
 If the {{HTTPHeader("Accept-Ranges")}} is present in HTTP responses (and its value isn't "`none`"), the server supports range requests. You can check this by issuing a {{HTTPMethod("HEAD")}} request with cURL, for example.
 
-    curl -I http://i.imgur.com/z4d4kWk.jpg
+```
+curl -I http://i.imgur.com/z4d4kWk.jpg
 
-    HTTP/1.1 200 OK
-    ...
-    Accept-Ranges: bytes
-    Content-Length: 146515
+HTTP/1.1 200 OK
+...
+Accept-Ranges: bytes
+Content-Length: 146515
+```
 
 In this response, `Accept-Ranges: bytes` indicates that bytes can be used as unit to define a range. Here the {{HTTPHeader("Content-Length")}} header is also useful as it indicates the full size of the image to retrieve.
 
 If sites omit the `Accept-Ranges` header, they likely don't support partial requests. Some sites also explicitly send "`none`" as a value, indicating no support. In some apps, download managers disable their pause buttons in that case.
 
-    curl -I https://www.youtube.com/watch?v=EwTZ2xpQwpA
+```
+curl -I https://www.youtube.com/watch?v=EwTZ2xpQwpA
 
-    HTTP/1.1 200 OK
-    ...
-    Accept-Ranges: none
+HTTP/1.1 200 OK
+...
+Accept-Ranges: none
+```
 
 ## Requesting a specific range from a server
 
@@ -39,21 +43,27 @@ If the server supports range requests, you can issue such a request by using the
 
 We can request a single range from a resource. Again, we can test a request by using cURL. The "`-H`" option will append a header line to the request, which in this case is the `Range` header requesting the first 1024 bytes.
 
-    curl http://i.imgur.com/z4d4kWk.jpg -i -H "Range: bytes=0-1023"
+```
+curl http://i.imgur.com/z4d4kWk.jpg -i -H "Range: bytes=0-1023"
+```
 
 The issued request looks like this:
 
-    GET /z4d4kWk.jpg HTTP/1.1
-    Host: i.imgur.com
-    Range: bytes=0-1023
+```
+GET /z4d4kWk.jpg HTTP/1.1
+Host: i.imgur.com
+Range: bytes=0-1023
+```
 
 The server responses with the {{HTTPStatus("206")}} `Partial Content` status:
 
-    HTTP/1.1 206 Partial Content
-    Content-Range: bytes 0-1023/146515
-    Content-Length: 1024
-    ...
-    (binary content)
+```
+HTTP/1.1 206 Partial Content
+Content-Range: bytes 0-1023/146515
+Content-Length: 1024
+...
+(binary content)
+```
 
 The {{HTTPHeader("Content-Length")}} header now indicates the size of the requested range (and not the full size of the image). The {{HTTPHeader("Content-Range")}} response header indicates where in the full resource this partial message belongs.
 
@@ -61,28 +71,32 @@ The {{HTTPHeader("Content-Length")}} header now indicates the size of the reques
 
 The {{HTTPHeader("Range")}} header also allows you to get multiple ranges at once in a multipart document. The ranges are separated by a comma.
 
-    curl http://www.example.com -i -H "Range: bytes=0-50, 100-150"
+```
+curl http://www.example.com -i -H "Range: bytes=0-50, 100-150"
+```
 
 The server responses with the {{HTTPStatus("206")}} `Partial Content` status and a {{HTTPHeader("Content-Type")}}`: multipart/byteranges; boundary=3d6b6a416f9b5` header, indicating that a multipart byterange follows. Each part contains its own `Content-Type` and `Content-Range` fields and the required boundary parameter specifies the boundary string used to separate each body-part.
 
-    HTTP/1.1 206 Partial Content
-    Content-Type: multipart/byteranges; boundary=3d6b6a416f9b5
-    Content-Length: 282
+```
+HTTP/1.1 206 Partial Content
+Content-Type: multipart/byteranges; boundary=3d6b6a416f9b5
+Content-Length: 282
 
-    --3d6b6a416f9b5
-    Content-Type: text/html
-    Content-Range: bytes 0-50/1270
+--3d6b6a416f9b5
+Content-Type: text/html
+Content-Range: bytes 0-50/1270
 
-    <!doctype html>
-    <html>
-    <head>
-        <title>Example Do
-    --3d6b6a416f9b5
-    Content-Type: text/html
-    Content-Range: bytes 100-150/1270
+<!doctype html>
+<html>
+<head>
+    <title>Example Do
+--3d6b6a416f9b5
+Content-Type: text/html
+Content-Range: bytes 100-150/1270
 
-    eta http-equiv="Content-type" content="text/html; c
-    --3d6b6a416f9b5--
+eta http-equiv="Content-type" content="text/html; c
+--3d6b6a416f9b5--
+```
 
 ### Conditional range requests
 
@@ -90,7 +104,9 @@ When resuming to request more parts of a resource, you need to guarantee that th
 
 The {{HTTPHeader("If-Range")}} HTTP request header makes a range request conditional: if the condition is fulfilled, the range request will be issued and the server sends back a {{HTTPStatus("206")}} `Partial Content` answer with the appropriate body. If the condition is not fulfilled, the full resource is sent back, with a {{HTTPStatus("200")}} `OK` status. This header can be used either with a {{HTTPHeader("Last-Modified")}} validator, or with an {{HTTPHeader("ETag")}}, but not with both.
 
-    If-Range: Wed, 21 Oct 2015 07:28:00 GMT
+```
+If-Range: Wed, 21 Oct 2015 07:28:00 GMT
+```
 
 ## Partial request responses
 
diff --git a/files/en-us/web/http/redirections/index.md b/files/en-us/web/http/redirections/index.md
index cc1d47d76ec83ae..18e195d0c49c8b7 100644
--- a/files/en-us/web/http/redirections/index.md
+++ b/files/en-us/web/http/redirections/index.md
@@ -147,24 +147,30 @@ Redirects can be set either in the server config file or in the `.htaccess` of e
 
 The [`mod_alias`](https://httpd.apache.org/docs/current/mod/mod_alias.html) module has `Redirect` and `RedirectMatch` directives that set up {{HTTPStatus("302")}} redirects by default:
 
-    <VirtualHost *:443>
-    	ServerName example.com
-    	Redirect / https://www.example.com
-    </VirtualHost>
+```html
+<VirtualHost *:443>
+  ServerName example.com
+  Redirect / https://www.example.com
+</VirtualHost>
+```
 
 The URL `https://example.com/` will be redirected to `https://www.example.com/`, as will any files or directories under it (`https://example.com/some-page` will be redirected to `https://www.example.com/some-page`)
 
 `RedirectMatch` does the same, but takes a {{glossary("regular expression")}} to define a collection of affected URLs:
 
-    RedirectMatch ^/images/(.*)$ https://images.example.com/$1
+```
+RedirectMatch ^/images/(.*)$ https://images.example.com/$1
+```
 
 All documents in the `images/` directory will redirect to a different domain.
 
 If you don't want a temporary redirect, an extra parameter (either the HTTP status code to use or the `permanent` keyword) can be used to set up a different redirect:
 
-    Redirect permanent / https://www.example.com
-    # …acts the same as:
-    Redirect 301 / https://www.example.com
+```
+Redirect permanent / https://www.example.com
+# …acts the same as:
+Redirect 301 / https://www.example.com
+```
 
 The [`mod_rewrite`](https://httpd.apache.org/docs/current/mod/mod_rewrite.html) module can also create redirects. It is more flexible, but a bit more complex.
 
@@ -172,16 +178,20 @@ The [`mod_rewrite`](https://httpd.apache.org/docs/current/mod/mod_rewrite.html)
 
 In Nginx, you create a specific server block for the content you want to redirect:
 
-    server {
-    	listen 80;
-    	server_name example.com;
-    	return 301 $scheme://www.example.com$request_uri;
-    }
+```
+server {
+  listen 80;
+  server_name example.com;
+  return 301 $scheme://www.example.com$request_uri;
+}
+```
 
 To apply a redirect to a directory or only certain pages, use the `rewrite` directive:
 
-    rewrite ^/images/(.*)$ https://images.example.com/$1 redirect;
-    rewrite ^/images/(.*)$ https://images.example.com/$1 permanent;
+```
+rewrite ^/images/(.*)$ https://images.example.com/$1 redirect;
+rewrite ^/images/(.*)$ https://images.example.com/$1 permanent;
+```
 
 ### IIS
 
diff --git a/files/en-us/web/http/session/index.md b/files/en-us/web/http/session/index.md
index 6b904c582998be4..2b1a1e097552eba 100644
--- a/files/en-us/web/http/session/index.md
+++ b/files/en-us/web/http/session/index.md
@@ -38,20 +38,24 @@ Once the connection is established, the user-agent can send the request (a user-
 
 Fetching the root page of developer.mozilla.org, (`https://developer.mozilla.org/`), and telling the server that the user-agent would prefer the page in French, if possible:
 
-    GET / HTTP/1.1
-    Host: developer.mozilla.org
-    Accept-Language: fr
+```
+GET / HTTP/1.1
+Host: developer.mozilla.org
+Accept-Language: fr
+```
 
 Observe that final empty line, this separates the data block from the header block. As there is no `Content-Length` provided in an HTTP header, this data block is presented empty, marking the end of the headers, allowing the server to process the request the moment it receives this empty line.
 
 For example, sending the result of a form:
 
-    POST /contact_form.php HTTP/1.1
-    Host: developer.mozilla.org
-    Content-Length: 64
-    Content-Type: application/x-www-form-urlencoded
+```
+POST /contact_form.php HTTP/1.1
+Host: developer.mozilla.org
+Content-Length: 64
+Content-Type: application/x-www-form-urlencoded
 
-    name=Joe%20User&request=Send%20me%20one%20of%20your%20catalogue
+name=Joe%20User&request=Send%20me%20one%20of%20your%20catalogue
+```
 
 ### Request methods
 
@@ -72,68 +76,74 @@ After the connected agent has sent its request, the web server processes it, and
 
 Successful web page response:
 
-    HTTP/1.1 200 OK
-    Content-Type: text/html; charset=utf-8
-    Content-Length: 55743
-    Connection: keep-alive
-    Cache-Control: s-maxage=300, public, max-age=0
-    Content-Language: en-US
-    Date: Thu, 06 Dec 2018 17:37:18 GMT
-    ETag: "2e77ad1dc6ab0b53a2996dfd4653c1c3"
-    Server: meinheld/0.6.1
-    Strict-Transport-Security: max-age=63072000
-    X-Content-Type-Options: nosniff
-    X-Frame-Options: DENY
-    X-XSS-Protection: 1; mode=block
-    Vary: Accept-Encoding,Cookie
-    Age: 7
-
-    <!DOCTYPE html>
-    <html lang="en">
-    <head>
-      <meta charset="utf-8">
-      <title>A simple webpage</title>
-    </head>
-    <body>
-      <h1>Simple HTML5 webpage</h1>
-      <p>Hello, world!</p>
-    </body>
-    </html>
+```
+HTTP/1.1 200 OK
+Content-Type: text/html; charset=utf-8
+Content-Length: 55743
+Connection: keep-alive
+Cache-Control: s-maxage=300, public, max-age=0
+Content-Language: en-US
+Date: Thu, 06 Dec 2018 17:37:18 GMT
+ETag: "2e77ad1dc6ab0b53a2996dfd4653c1c3"
+Server: meinheld/0.6.1
+Strict-Transport-Security: max-age=63072000
+X-Content-Type-Options: nosniff
+X-Frame-Options: DENY
+X-XSS-Protection: 1; mode=block
+Vary: Accept-Encoding,Cookie
+Age: 7
+
+<!DOCTYPE html>
+<html lang="en">
+<head>
+  <meta charset="utf-8">
+  <title>A simple webpage</title>
+</head>
+<body>
+  <h1>Simple HTML5 webpage</h1>
+  <p>Hello, world!</p>
+</body>
+</html>
+```
 
 Notification that the requested resource has permanently moved:
 
-    HTTP/1.1 301 Moved Permanently
-    Server: Apache/2.4.37 (Red Hat)
-    Content-Type: text/html; charset=utf-8
-    Date: Thu, 06 Dec 2018 17:33:08 GMT
-    Location: https://developer.mozilla.org/ (this is the new link to the resource; it is expected that the user-agent will fetch it)
-    Keep-Alive: timeout=15, max=98
-    Accept-Ranges: bytes
-    Via: Moz-Cache-zlb05
-    Connection: Keep-Alive
-    Content-Length: 325 (the content contains a default page to display if the user-agent is not able to follow the link)
-
-    <!DOCTYPE html... (contains a site-customized page helping the user to find the missing resource)
+```
+HTTP/1.1 301 Moved Permanently
+Server: Apache/2.4.37 (Red Hat)
+Content-Type: text/html; charset=utf-8
+Date: Thu, 06 Dec 2018 17:33:08 GMT
+Location: https://developer.mozilla.org/ (this is the new link to the resource; it is expected that the user-agent will fetch it)
+Keep-Alive: timeout=15, max=98
+Accept-Ranges: bytes
+Via: Moz-Cache-zlb05
+Connection: Keep-Alive
+Content-Length: 325 (the content contains a default page to display if the user-agent is not able to follow the link)
+
+<!DOCTYPE html... (contains a site-customized page helping the user to find the missing resource)
+```
 
 Notification that the requested resource doesn't exist:
 
-    HTTP/1.1 404 Not Found
-    Content-Type: text/html; charset=utf-8
-    Content-Length: 38217
-    Connection: keep-alive
-    Cache-Control: no-cache, no-store, must-revalidate, max-age=0
-    Content-Language: en-US
-    Date: Thu, 06 Dec 2018 17:35:13 GMT
-    Expires: Thu, 06 Dec 2018 17:35:13 GMT
-    Server: meinheld/0.6.1
-    Strict-Transport-Security: max-age=63072000
-    X-Content-Type-Options: nosniff
-    X-Frame-Options: DENY
-    X-XSS-Protection: 1; mode=block
-    Vary: Accept-Encoding,Cookie
-    X-Cache: Error from cloudfront
-
-    <!DOCTYPE html... (contains a site-customized page helping the user to find the missing resource)
+```
+HTTP/1.1 404 Not Found
+Content-Type: text/html; charset=utf-8
+Content-Length: 38217
+Connection: keep-alive
+Cache-Control: no-cache, no-store, must-revalidate, max-age=0
+Content-Language: en-US
+Date: Thu, 06 Dec 2018 17:35:13 GMT
+Expires: Thu, 06 Dec 2018 17:35:13 GMT
+Server: meinheld/0.6.1
+Strict-Transport-Security: max-age=63072000
+X-Content-Type-Options: nosniff
+X-Frame-Options: DENY
+X-XSS-Protection: 1; mode=block
+Vary: Accept-Encoding,Cookie
+X-Cache: Error from cloudfront
+
+<!DOCTYPE html... (contains a site-customized page helping the user to find the missing resource)
+```
 
 ### Response status codes
 
diff --git a/files/en-us/web/http/status/100/index.md b/files/en-us/web/http/status/100/index.md
index 5c20d851b707be7..64028165136be4f 100644
--- a/files/en-us/web/http/status/100/index.md
+++ b/files/en-us/web/http/status/100/index.md
@@ -19,7 +19,7 @@ and receive a `100 Continue` status code in response before sending the body.
 
 ## Status
 
-```html
+```
 100 Continue
 ```
 
diff --git a/files/en-us/web/http/status/101/index.md b/files/en-us/web/http/status/101/index.md
index 60bbe5e4f242fc1..bcd605bbe10899a 100644
--- a/files/en-us/web/http/status/101/index.md
+++ b/files/en-us/web/http/status/101/index.md
@@ -21,7 +21,7 @@ mechanism](/en-US/docs/Web/HTTP/Protocol_upgrade_mechanism).
 
 ## Status
 
-```html
+```
 101 Switching Protocols
 ```
 
@@ -29,9 +29,11 @@ mechanism](/en-US/docs/Web/HTTP/Protocol_upgrade_mechanism).
 
 Switching protocols might be used with [WebSockets](/en-US/docs/Web/API/WebSockets_API).
 
-    HTTP/1.1 101 Switching Protocols
-    Upgrade: websocket
-    Connection: Upgrade
+```
+HTTP/1.1 101 Switching Protocols
+Upgrade: websocket
+Connection: Upgrade
+```
 
 ## Specifications
 
diff --git a/files/en-us/web/http/status/103/index.md b/files/en-us/web/http/status/103/index.md
index d967596a0224722..d0b13e49730ea49 100644
--- a/files/en-us/web/http/status/103/index.md
+++ b/files/en-us/web/http/status/103/index.md
@@ -18,7 +18,7 @@ user agent to start preloading resources while the server is still preparing a r
 
 ## Syntax
 
-```html
+```
 103 Early Hints
 ```
 
diff --git a/files/en-us/web/http/status/200/index.md b/files/en-us/web/http/status/200/index.md
index f335e36adf5c4d4..8e613315de87c36 100644
--- a/files/en-us/web/http/status/200/index.md
+++ b/files/en-us/web/http/status/200/index.md
@@ -22,7 +22,7 @@ The successful result of a {{HTTPMethod("PUT")}} or a {{HTTPMethod("DELETE")}} i
 
 ## Status
 
-```html
+```
 200 OK
 ```
 
diff --git a/files/en-us/web/http/status/201/index.md b/files/en-us/web/http/status/201/index.md
index 67d8006721146c4..b23e4064fa4be34 100644
--- a/files/en-us/web/http/status/201/index.md
+++ b/files/en-us/web/http/status/201/index.md
@@ -21,7 +21,7 @@ request.
 
 ## Status
 
-```html
+```
 201 Created
 ```
 
diff --git a/files/en-us/web/http/status/202/index.md b/files/en-us/web/http/status/202/index.md
index 82f9f4ecbf3d886..1f7968a6727509c 100644
--- a/files/en-us/web/http/status/202/index.md
+++ b/files/en-us/web/http/status/202/index.md
@@ -21,7 +21,7 @@ for cases where another process or server handles the request, or for batch proc
 
 ## Status
 
-```html
+```
 202 Accepted
 ```
 
diff --git a/files/en-us/web/http/status/203/index.md b/files/en-us/web/http/status/203/index.md
index f1dd064d47615ad..9a5de4b740fa052 100644
--- a/files/en-us/web/http/status/203/index.md
+++ b/files/en-us/web/http/status/203/index.md
@@ -23,7 +23,7 @@ status code.
 
 ## Status
 
-```html
+```
 203 Non-Authoritative Information
 ```
 
diff --git a/files/en-us/web/http/status/204/index.md b/files/en-us/web/http/status/204/index.md
index 3c0cdee6cf7acfe..d77e1c78befe9ca 100644
--- a/files/en-us/web/http/status/204/index.md
+++ b/files/en-us/web/http/status/204/index.md
@@ -22,7 +22,7 @@ A 204 response is cacheable by default (an {{HTTPHeader("ETag")}} header is incl
 
 ## Status
 
-```html
+```
 204 No Content
 ```
 
diff --git a/files/en-us/web/http/status/205/index.md b/files/en-us/web/http/status/205/index.md
index 05f3adc5d297d74..e9bc76d0719bd59 100644
--- a/files/en-us/web/http/status/205/index.md
+++ b/files/en-us/web/http/status/205/index.md
@@ -15,7 +15,7 @@ a canvas state, or to refresh the UI.
 
 ## Status
 
-```html
+```
 205 Reset Content
 ```
 
diff --git a/files/en-us/web/http/status/206/index.md b/files/en-us/web/http/status/206/index.md
index 37c87f8e1e4fcec..4708849db925292 100644
--- a/files/en-us/web/http/status/206/index.md
+++ b/files/en-us/web/http/status/206/index.md
@@ -23,7 +23,7 @@ If several ranges are sent back, the {{HTTPHeader("Content-Type")}} is set to
 
 ## Status
 
-```html
+```
 206 Partial Content
 ```
 
diff --git a/files/en-us/web/http/status/300/index.md b/files/en-us/web/http/status/300/index.md
index f7b5c7bf18135b6..77620af6a1ca7ad 100644
--- a/files/en-us/web/http/status/300/index.md
+++ b/files/en-us/web/http/status/300/index.md
@@ -19,7 +19,7 @@ header.
 
 ## Status
 
-```html
+```
 300 Multiple Choices
 ```
 
diff --git a/files/en-us/web/http/status/301/index.md b/files/en-us/web/http/status/301/index.md
index 6a1fc04a3e8738f..083337426e09dd9 100644
--- a/files/en-us/web/http/status/301/index.md
+++ b/files/en-us/web/http/status/301/index.md
@@ -16,7 +16,7 @@ Even if the specification requires the method (and the body) not to be altered w
 
 ## Status
 
-```html
+```
 301 Moved Permanently
 ```
 
@@ -24,13 +24,17 @@ Even if the specification requires the method (and the body) not to be altered w
 
 ### Client request
 
-    GET /index.php HTTP/1.1
-    Host: www.example.org
+```
+GET /index.php HTTP/1.1
+Host: www.example.org
+```
 
 ### Server response
 
-    HTTP/1.1 301 Moved Permanently
-    Location: http://www.example.org/index.asp
+```
+HTTP/1.1 301 Moved Permanently
+Location: http://www.example.org/index.asp
+```
 
 ## Specifications
 
diff --git a/files/en-us/web/http/status/302/index.md b/files/en-us/web/http/status/302/index.md
index f53102f6edfd68d..6f4fe8aef8d5bb6 100644
--- a/files/en-us/web/http/status/302/index.md
+++ b/files/en-us/web/http/status/302/index.md
@@ -30,7 +30,7 @@ confirmation message such as: 'you successfully uploaded XYZ'.
 
 ## Status
 
-```html
+```
 302 Found
 ```
 
diff --git a/files/en-us/web/http/status/303/index.md b/files/en-us/web/http/status/303/index.md
index eefcc689781510a..ecd0ddf1a56f3c9 100644
--- a/files/en-us/web/http/status/303/index.md
+++ b/files/en-us/web/http/status/303/index.md
@@ -19,7 +19,7 @@ redirected page is always {{HTTPMethod("GET")}}.
 
 ## Status
 
-```html
+```
 303 See Other
 ```
 
diff --git a/files/en-us/web/http/status/304/index.md b/files/en-us/web/http/status/304/index.md
index 214f6ca11bb51be..fe793f7b9b15fc3 100644
--- a/files/en-us/web/http/status/304/index.md
+++ b/files/en-us/web/http/status/304/index.md
@@ -28,7 +28,7 @@ headers {{HTTPHeader("Cache-Control")}}, {{HTTPHeader("Content-Location")}},
 
 ## Status
 
-```html
+```
 304 Not Modified
 ```
 
diff --git a/files/en-us/web/http/status/307/index.md b/files/en-us/web/http/status/307/index.md
index d2cf2b2116562a9..45d0afcce0d72f5 100644
--- a/files/en-us/web/http/status/307/index.md
+++ b/files/en-us/web/http/status/307/index.md
@@ -30,7 +30,7 @@ identical.
 
 ## Status
 
-```html
+```
 307 Temporary Redirect
 ```
 
diff --git a/files/en-us/web/http/status/308/index.md b/files/en-us/web/http/status/308/index.md
index 5a31962a44124d7..adfbfaf9093b13d 100644
--- a/files/en-us/web/http/status/308/index.md
+++ b/files/en-us/web/http/status/308/index.md
@@ -27,7 +27,7 @@ incorrectly sometimes be changed to a {{HTTPMethod("GET")}} method.
 
 ## Status
 
-```html
+```
 308 Permanent Redirect
 ```
 
diff --git a/files/en-us/web/http/status/400/index.md b/files/en-us/web/http/status/400/index.md
index c9ee4119fa3ec2a..32097b80793e5d8 100644
--- a/files/en-us/web/http/status/400/index.md
+++ b/files/en-us/web/http/status/400/index.md
@@ -16,8 +16,8 @@ The HyperText Transfer Protocol (HTTP) **`400 Bad Request`** response status cod
 
 ## Status
 
-```html
-400 Bad Request 
+```
+400 Bad Request
 ```
 
 ## Specifications
diff --git a/files/en-us/web/http/status/401/index.md b/files/en-us/web/http/status/401/index.md
index e50ff2b02e8d64b..e2c462216e612ca 100644
--- a/files/en-us/web/http/status/401/index.md
+++ b/files/en-us/web/http/status/401/index.md
@@ -22,15 +22,17 @@ possible.
 
 ## Status
 
-```html
+```
 401 Unauthorized
 ```
 
 ## Example response
 
-    HTTP/1.1 401 Unauthorized
-    Date: Wed, 21 Oct 2015 07:28:00 GMT
-    WWW-Authenticate: Basic realm="Access to staging site"
+```
+HTTP/1.1 401 Unauthorized
+Date: Wed, 21 Oct 2015 07:28:00 GMT
+WWW-Authenticate: Basic realm="Access to staging site"
+```
 
 ## Specifications
 
diff --git a/files/en-us/web/http/status/402/index.md b/files/en-us/web/http/status/402/index.md
index b01f1b42702cbc8..9e38f271d50de0f 100644
--- a/files/en-us/web/http/status/402/index.md
+++ b/files/en-us/web/http/status/402/index.md
@@ -16,13 +16,13 @@ Sometimes, this code indicates that the request can not be processed until the c
 
 ## Status
 
-```html
+```
 402 Payment Required
 ```
 
 ## Example response
 
-```bash
+```
 HTTP/1.1 402 Payment Required
 Date: Wed, 21 Oct 2015 07:28:00 GMT
 ```
diff --git a/files/en-us/web/http/status/403/index.md b/files/en-us/web/http/status/403/index.md
index d39281f6a7c8f10..a4142fe7e1d1d79 100644
--- a/files/en-us/web/http/status/403/index.md
+++ b/files/en-us/web/http/status/403/index.md
@@ -16,14 +16,16 @@ This status is similar to {{HTTPStatus("401")}}, but in this case, re-authentica
 
 ## Status
 
-```html
+```
 403 Forbidden
 ```
 
 ## Example response
 
-    HTTP/1.1 403 Forbidden
-    Date: Wed, 21 Oct 2015 07:28:00 GMT
+```
+HTTP/1.1 403 Forbidden
+Date: Wed, 21 Oct 2015 07:28:00 GMT
+```
 
 ## Specifications
 
diff --git a/files/en-us/web/http/status/404/index.md b/files/en-us/web/http/status/404/index.md
index f759173cae7b734..b6d6d5cd8579e56 100644
--- a/files/en-us/web/http/status/404/index.md
+++ b/files/en-us/web/http/status/404/index.md
@@ -16,7 +16,7 @@ A 404 status code does not indicate whether the resource is temporarily or perma
 
 ## Status
 
-```html
+```
 404 Not Found
 ```
 
@@ -24,7 +24,7 @@ A 404 status code does not indicate whether the resource is temporarily or perma
 
 Many web sites customize the look of a 404 page to be more helpful to the user and provide guidance on what to do next. Apache servers can be configured using an `.htaccess` file and a code snippet like the following example.
 
-```bash
+```
 ErrorDocument 404 /notfound.html
 ```
 
diff --git a/files/en-us/web/http/status/405/index.md b/files/en-us/web/http/status/405/index.md
index fe8473305771523..85374d4a4652ba1 100644
--- a/files/en-us/web/http/status/405/index.md
+++ b/files/en-us/web/http/status/405/index.md
@@ -16,7 +16,7 @@ The server **must** generate an **`Allow`** header field in a 405 response conta
 
 ## Status
 
-```html
+```
 405 Method Not Allowed
 ```
 
diff --git a/files/en-us/web/http/status/406/index.md b/files/en-us/web/http/status/406/index.md
index 308015f6f08e924..5a17def83a9c856 100644
--- a/files/en-us/web/http/status/406/index.md
+++ b/files/en-us/web/http/status/406/index.md
@@ -31,7 +31,7 @@ among them.
 
 ## Status
 
-```html
+```
 406 Not Acceptable
 ```
 
diff --git a/files/en-us/web/http/status/407/index.md b/files/en-us/web/http/status/407/index.md
index e13aecf47b389b3..7d7726aa4dc501d 100644
--- a/files/en-us/web/http/status/407/index.md
+++ b/files/en-us/web/http/status/407/index.md
@@ -20,15 +20,17 @@ information on how to authorize correctly.
 
 ## Status
 
-```html
-407 Proxy Authentication Required 
+```
+407 Proxy Authentication Required
 ```
 
 ## Example response
 
-    HTTP/1.1 407 Proxy Authentication Required
-    Date: Wed, 21 Oct 2015 07:28:00 GMT
-    Proxy-Authenticate: Basic realm="Access to internal site"
+```
+HTTP/1.1 407 Proxy Authentication Required
+Date: Wed, 21 Oct 2015 07:28:00 GMT
+Proxy-Authenticate: Basic realm="Access to internal site"
+```
 
 ## Specifications
 
diff --git a/files/en-us/web/http/status/408/index.md b/files/en-us/web/http/status/408/index.md
index 73f6c2b4008a634..0b82ebf6e3de19a 100644
--- a/files/en-us/web/http/status/408/index.md
+++ b/files/en-us/web/http/status/408/index.md
@@ -27,7 +27,7 @@ use HTTP pre-connection mechanisms to speed up surfing.
 
 ## Status
 
-```html
+```
 408 Request Timeout
 ```
 
diff --git a/files/en-us/web/http/status/409/index.md b/files/en-us/web/http/status/409/index.md
index c90babe56a61a91..04edb716566d87a 100644
--- a/files/en-us/web/http/status/409/index.md
+++ b/files/en-us/web/http/status/409/index.md
@@ -16,7 +16,7 @@ Conflicts are most likely to occur in response to a {{HTTPMethod("PUT")}} reques
 
 ## Status
 
-```html
+```
 409 Conflict
 ```
 
diff --git a/files/en-us/web/http/status/410/index.md b/files/en-us/web/http/status/410/index.md
index fdd589b811ba7a2..d85df49d211f913 100644
--- a/files/en-us/web/http/status/410/index.md
+++ b/files/en-us/web/http/status/410/index.md
@@ -18,7 +18,7 @@ If you don't know whether this condition is temporary or permanent, a {{HTTPStat
 
 ## Status
 
-```html
+```
 410 Gone
 ```
 
diff --git a/files/en-us/web/http/status/411/index.md b/files/en-us/web/http/status/411/index.md
index 1833ce15fe1decd..17f16a01dee4c06 100644
--- a/files/en-us/web/http/status/411/index.md
+++ b/files/en-us/web/http/status/411/index.md
@@ -22,7 +22,7 @@ that the server refuses to accept the request without a defined
 
 ## Status
 
-```html
+```
 411 Length Required
 ```
 
diff --git a/files/en-us/web/http/status/412/index.md b/files/en-us/web/http/status/412/index.md
index 923ac96cec02bf0..2523a7ecb1d00ab 100644
--- a/files/en-us/web/http/status/412/index.md
+++ b/files/en-us/web/http/status/412/index.md
@@ -21,7 +21,7 @@ cannot be made and this error response is sent back.
 
 ## Status
 
-```html
+```
 412 Precondition Failed
 ```
 
diff --git a/files/en-us/web/http/status/413/index.md b/files/en-us/web/http/status/413/index.md
index 4f36cf2570b7d46..f63df1e4eff5ce5 100644
--- a/files/en-us/web/http/status/413/index.md
+++ b/files/en-us/web/http/status/413/index.md
@@ -14,7 +14,7 @@ The HTTP **`413 Payload Too Large`** response status code indicates that the req
 
 ## Status
 
-```html
+```
 413 Payload Too Large
 ```
 
diff --git a/files/en-us/web/http/status/414/index.md b/files/en-us/web/http/status/414/index.md
index 475d378228ebb8f..fc8210149f95022 100644
--- a/files/en-us/web/http/status/414/index.md
+++ b/files/en-us/web/http/status/414/index.md
@@ -23,7 +23,7 @@ There are a few rare conditions when this might occur:
 
 ## Status
 
-```html
+```
 414 URI Too Long
 ```
 
diff --git a/files/en-us/web/http/status/415/index.md b/files/en-us/web/http/status/415/index.md
index 364d3f3092b127a..fe6b81af50305e4 100644
--- a/files/en-us/web/http/status/415/index.md
+++ b/files/en-us/web/http/status/415/index.md
@@ -20,7 +20,7 @@ inspecting the data directly.
 
 ## Status
 
-```html
+```
 415 Unsupported Media Type
 ```
 
diff --git a/files/en-us/web/http/status/416/index.md b/files/en-us/web/http/status/416/index.md
index beb404de4cafd23..da53c60f6b50b72 100644
--- a/files/en-us/web/http/status/416/index.md
+++ b/files/en-us/web/http/status/416/index.md
@@ -17,7 +17,7 @@ Faced with this error, browsers usually either abort the operation (for example,
 
 ## Status
 
-```html
+```
 416 Range Not Satisfiable
 ```
 
diff --git a/files/en-us/web/http/status/417/index.md b/files/en-us/web/http/status/417/index.md
index 183ec68f8c0fb55..291d8efdeaa7fb7 100644
--- a/files/en-us/web/http/status/417/index.md
+++ b/files/en-us/web/http/status/417/index.md
@@ -18,7 +18,7 @@ See the {{HTTPHeader("Expect")}} header for more details.
 
 ## Status
 
-```html
+```
 417 Expectation Failed
 ```
 
diff --git a/files/en-us/web/http/status/418/index.md b/files/en-us/web/http/status/418/index.md
index 82991f7aa780a73..639f106b2692c35 100644
--- a/files/en-us/web/http/status/418/index.md
+++ b/files/en-us/web/http/status/418/index.md
@@ -15,7 +15,7 @@ Some websites use this response for requests they do not wish to handle, such as
 
 ## Status
 
-```html
+```
 418 I'm a teapot
 ```
 
diff --git a/files/en-us/web/http/status/422/index.md b/files/en-us/web/http/status/422/index.md
index 0cc57e8308cc00c..e83051505e42d56 100644
--- a/files/en-us/web/http/status/422/index.md
+++ b/files/en-us/web/http/status/422/index.md
@@ -20,7 +20,7 @@ the request entity is correct, but it was unable to process the contained instru
 
 ## Status
 
-```html
+```
 422 Unprocessable Entity
 ```
 
diff --git a/files/en-us/web/http/status/425/index.md b/files/en-us/web/http/status/425/index.md
index 45f9b5e29d141bd..0bd18baee565138 100644
--- a/files/en-us/web/http/status/425/index.md
+++ b/files/en-us/web/http/status/425/index.md
@@ -16,7 +16,7 @@ that might be replayed, which creates the potential for a replay attack.
 
 ## Status
 
-```html
+```
 425 Too Early
 ```
 
diff --git a/files/en-us/web/http/status/426/index.md b/files/en-us/web/http/status/426/index.md
index 13479ed92a19607..98e1f094796597c 100644
--- a/files/en-us/web/http/status/426/index.md
+++ b/files/en-us/web/http/status/426/index.md
@@ -19,7 +19,7 @@ required protocol(s).
 
 ## Status
 
-```html
+```
 426 Upgrade Required
 ```
 
diff --git a/files/en-us/web/http/status/428/index.md b/files/en-us/web/http/status/428/index.md
index 0e9cd6b9cb3275e..98599a50c6fdf62 100644
--- a/files/en-us/web/http/status/428/index.md
+++ b/files/en-us/web/http/status/428/index.md
@@ -21,7 +21,7 @@ response should be {{HTTPStatus(412)}} `Precondition Failed`.
 
 ## Status
 
-```html
+```
 428 Precondition Required
 ```
 
diff --git a/files/en-us/web/http/status/429/index.md b/files/en-us/web/http/status/429/index.md
index 22e7a34ec496c3e..939079fc6ca0b15 100644
--- a/files/en-us/web/http/status/429/index.md
+++ b/files/en-us/web/http/status/429/index.md
@@ -16,15 +16,17 @@ A {{HTTPHeader("Retry-After")}} header might be included to this response indica
 
 ## Status
 
-```html
+```
 429 Too Many Requests
 ```
 
 ## Example
 
-    HTTP/1.1 429 Too Many Requests
-    Content-Type: text/html
-    Retry-After: 3600
+```
+HTTP/1.1 429 Too Many Requests
+Content-Type: text/html
+Retry-After: 3600
+```
 
 ## Specifications
 
diff --git a/files/en-us/web/http/status/431/index.md b/files/en-us/web/http/status/431/index.md
index 20867db3cf5e6dc..69ba465b2d5a22b 100644
--- a/files/en-us/web/http/status/431/index.md
+++ b/files/en-us/web/http/status/431/index.md
@@ -29,7 +29,7 @@ Servers will often produce this status if:
 
 ## Status
 
-```html
+```
 431 Request Header Fields Too Large
 ```
 
diff --git a/files/en-us/web/http/status/451/index.md b/files/en-us/web/http/status/451/index.md
index 64c56dff1871a47..04e06eacae8669c 100644
--- a/files/en-us/web/http/status/451/index.md
+++ b/files/en-us/web/http/status/451/index.md
@@ -14,7 +14,7 @@ The HyperText Transfer Protocol (HTTP) **`451 Unavailable For Legal Reasons`** c
 
 ## Status
 
-```html
+```
 451 Unavailable For Legal Reasons
 ```
 
diff --git a/files/en-us/web/http/status/500/index.md b/files/en-us/web/http/status/500/index.md
index b8b869c678e3dbe..b08a6757cc7be79 100644
--- a/files/en-us/web/http/status/500/index.md
+++ b/files/en-us/web/http/status/500/index.md
@@ -15,7 +15,7 @@ This error response is a generic "catch-all" response. Usually, this indicates t
 
 ## Status
 
-```html
+```
 500 Internal Server Error
 ```
 
diff --git a/files/en-us/web/http/status/501/index.md b/files/en-us/web/http/status/501/index.md
index c626c1cb515b85c..cdd63ca0523a885 100644
--- a/files/en-us/web/http/status/501/index.md
+++ b/files/en-us/web/http/status/501/index.md
@@ -24,7 +24,7 @@ If the server _does_ recognize the method, but intentionally does not support it
 
 ## Status
 
-```html
+```
 501 Not Implemented
 ```
 
diff --git a/files/en-us/web/http/status/502/index.md b/files/en-us/web/http/status/502/index.md
index b1abbbcbf20c7a4..6f0aedab1293cd1 100644
--- a/files/en-us/web/http/status/502/index.md
+++ b/files/en-us/web/http/status/502/index.md
@@ -15,7 +15,7 @@ The HyperText Transfer Protocol (HTTP) **`502 Bad Gateway`** server error respon
 
 ## Status
 
-```html
+```
 502 Bad Gateway
 ```
 
diff --git a/files/en-us/web/http/status/503/index.md b/files/en-us/web/http/status/503/index.md
index d664b9ebfdade08..b94c3654682d422 100644
--- a/files/en-us/web/http/status/503/index.md
+++ b/files/en-us/web/http/status/503/index.md
@@ -20,7 +20,7 @@ Caching-related headers that are sent along with this response should be taken c
 
 ## Status
 
-```html
+```
 503 Service Unavailable
 ```
 
diff --git a/files/en-us/web/http/status/504/index.md b/files/en-us/web/http/status/504/index.md
index 3b92fb543f1f9cc..b3ea39f8027b487 100644
--- a/files/en-us/web/http/status/504/index.md
+++ b/files/en-us/web/http/status/504/index.md
@@ -15,7 +15,7 @@ The HyperText Transfer Protocol (HTTP) **`504 Gateway Timeout`** server error re
 
 ## Status
 
-```html
+```
 504 Gateway Timeout
 ```
 
diff --git a/files/en-us/web/http/status/505/index.md b/files/en-us/web/http/status/505/index.md
index 8e7043e9bc2995f..05f7a8956472c68 100644
--- a/files/en-us/web/http/status/505/index.md
+++ b/files/en-us/web/http/status/505/index.md
@@ -15,7 +15,7 @@ indicates that the HTTP version used in the request is not supported by the serv
 
 ## Status
 
-```html
+```
 505 HTTP Version Not Supported
 ```
 
diff --git a/files/en-us/web/http/status/506/index.md b/files/en-us/web/http/status/506/index.md
index b36478e3018494e..8ab44cef4208bc3 100644
--- a/files/en-us/web/http/status/506/index.md
+++ b/files/en-us/web/http/status/506/index.md
@@ -14,7 +14,7 @@ The **`Variant Also Negotiates`** status code indicates an internal server confi
 
 ## Status
 
-```html
+```
 506 Variant Also Negotiates
 ```
 
diff --git a/files/en-us/web/http/status/507/index.md b/files/en-us/web/http/status/507/index.md
index 952fe820cd2a617..32b69da48ca91d0 100644
--- a/files/en-us/web/http/status/507/index.md
+++ b/files/en-us/web/http/status/507/index.md
@@ -14,7 +14,7 @@ It indicates that a method could not be performed because the server cannot stor
 
 ## Status
 
-```html
+```
 507 Insufficient Storage
 ```
 
diff --git a/files/en-us/web/http/status/508/index.md b/files/en-us/web/http/status/508/index.md
index ea234e5f7477f37..e78b4bf70273a7e 100644
--- a/files/en-us/web/http/status/508/index.md
+++ b/files/en-us/web/http/status/508/index.md
@@ -19,7 +19,7 @@ entire operation failed.
 
 ## Status
 
-```html
+```
 508 Loop Detected
 ```
 
diff --git a/files/en-us/web/http/status/510/index.md b/files/en-us/web/http/status/510/index.md
index 14ebc3c6228b178..66880e8c0767a68 100644
--- a/files/en-us/web/http/status/510/index.md
+++ b/files/en-us/web/http/status/510/index.md
@@ -19,7 +19,7 @@ responds with the 510 status code.
 
 ## Status
 
-```html
+```
 510 Not Extended
 ```
 
diff --git a/files/en-us/web/http/status/511/index.md b/files/en-us/web/http/status/511/index.md
index 4c2637f5b4272a0..cb6baef0b12c96e 100644
--- a/files/en-us/web/http/status/511/index.md
+++ b/files/en-us/web/http/status/511/index.md
@@ -23,7 +23,7 @@ Control ({{Glossary("MAC")}}) addresses.
 
 ## Status
 
-```html
+```
 511 Network Authentication Required
 ```