diff --git a/files/en-us/_redirects.txt b/files/en-us/_redirects.txt
index 75b7688379cb339..90c6208acba40ac 100644
--- a/files/en-us/_redirects.txt
+++ b/files/en-us/_redirects.txt
@@ -4000,7 +4000,7 @@
 /en-US/docs/Inbox/Advanced_layouts_with_flexbox	/en-US/docs/Glossary/Flexbox
 /en-US/docs/Inbox/Using_flexbox_to_lay_out_web_applications	/en-US/docs/Web/CSS/CSS_flexible_box_layout/Typical_use_cases_of_flexbox
 /en-US/docs/Inbox/Writing_a_WebSocket_server_in_Java	/en-US/docs/Web/API/WebSockets_API/Writing_a_WebSocket_server_in_Java
-/en-US/docs/Incorrect_MIME_Type_for_CSS_Files	/en-US/docs/Web/HTTP/Basics_of_HTTP/MIME_types
+/en-US/docs/Incorrect_MIME_Type_for_CSS_Files	/en-US/docs/Web/HTTP/MIME_types
 /en-US/docs/IndexedDB	/en-US/docs/Web/API/IndexedDB_API
 /en-US/docs/IndexedDB/Basic_Concepts_Behind_IndexedDB	/en-US/docs/Web/API/IndexedDB_API/Basic_Terminology
 /en-US/docs/IndexedDB/Cursor	/en-US/docs/Web/API/IDBCursor
@@ -12286,18 +12286,21 @@
 /en-US/docs/Web/HTML/element/content	/en-US/docs/Web/HTML/element/slot
 /en-US/docs/Web/HTTP/Access_control_CORS	/en-US/docs/Web/HTTP/CORS
 /en-US/docs/Web/HTTP/Basic_access_authentication	/en-US/docs/Web/HTTP/Authentication
+/en-US/docs/Web/HTTP/Basics_of_HTTP	/en-US/docs/Web/HTTP
 /en-US/docs/Web/HTTP/Basics_of_HTTP/Choosing_between_www_and_non-www_URLs	/en-US/docs/Web/URI/Authority/Choosing_between_www_and_non-www_URLs
 /en-US/docs/Web/HTTP/Basics_of_HTTP/Data_URIs	/en-US/docs/Web/URI/Schemes/data
 /en-US/docs/Web/HTTP/Basics_of_HTTP/Data_URLs	/en-US/docs/Web/URI/Schemes/data
+/en-US/docs/Web/HTTP/Basics_of_HTTP/Evolution_of_HTTP	/en-US/docs/Web/HTTP/Evolution_of_HTTP
 /en-US/docs/Web/HTTP/Basics_of_HTTP/Introduction_to_www_and_non-www_URLs	/en-US/docs/Web/URI/Authority/Choosing_between_www_and_non-www_URLs
-/en-US/docs/Web/HTTP/Basics_of_HTTP/MIME_types/Complete_list_of_MIME_types	/en-US/docs/Web/HTTP/Basics_of_HTTP/MIME_types/Common_types
+/en-US/docs/Web/HTTP/Basics_of_HTTP/MIME_types	/en-US/docs/Web/HTTP/MIME_types
+/en-US/docs/Web/HTTP/Basics_of_HTTP/MIME_types/Common_types	/en-US/docs/Web/HTTP/MIME_types/Common_types
+/en-US/docs/Web/HTTP/Basics_of_HTTP/MIME_types/Complete_list_of_MIME_types	/en-US/docs/Web/HTTP/MIME_types/Common_types
 /en-US/docs/Web/HTTP/Basics_of_HTTP/Resource_URLs	/en-US/docs/Web/URI/Schemes/resource
 /en-US/docs/Web/HTTP/CORS/Errors/Reason:_CORS_header_‘Origin’_cannot_be_added	/en-US/docs/Web/HTTP/CORS/Errors/CORSOriginHeaderNotAdded
 /en-US/docs/Web/HTTP/Caching_FAQ	/en-US/docs/Web/HTTP/Caching
 /en-US/docs/Web/HTTP/Controlling_DNS_prefetching	/en-US/docs/Web/HTTP/Headers/X-DNS-Prefetch-Control
 /en-US/docs/Web/HTTP/Cookies/Cookie_Prefixes	/en-US/docs/Web/HTTP/Cookies#Cookie_prefixes
 /en-US/docs/Web/HTTP/Cross-Origin_Resource_Policy_(CORP)	/en-US/docs/Web/HTTP/Cross-Origin_Resource_Policy
-/en-US/docs/Web/HTTP/Evolution_of_HTTP	/en-US/docs/Web/HTTP/Basics_of_HTTP/Evolution_of_HTTP
 /en-US/docs/Web/HTTP/Feature_Policy	/en-US/docs/Web/HTTP/Permissions_Policy
 /en-US/docs/Web/HTTP/Gecko_user_agent_string_reference	/en-US/docs/Web/HTTP/Headers/User-Agent/Firefox
 /en-US/docs/Web/HTTP/HTTP_response_codes	/en-US/docs/Web/HTTP/Status
@@ -12351,13 +12354,13 @@
 /en-US/docs/Web/HTTP/Headers/Ranges	/en-US/docs/Web/HTTP/Headers/Range
 /en-US/docs/Web/HTTP/Headers/Set-Cookie/SameSite	/en-US/docs/Web/HTTP/Headers/Set-Cookie#samesitesamesite-value
 /en-US/docs/Web/HTTP/Headers/Set-Cookie2	/en-US/docs/Web/HTTP/Headers/Set-Cookie
-/en-US/docs/Web/HTTP/History_of_HTTP_versions	/en-US/docs/Web/HTTP/Basics_of_HTTP/Evolution_of_HTTP
+/en-US/docs/Web/HTTP/History_of_HTTP_versions	/en-US/docs/Web/HTTP/Evolution_of_HTTP
 /en-US/docs/Web/HTTP/Index	/en-US/docs/Web/HTTP
 /en-US/docs/Web/HTTP/Link_prefetching_FAQ	/en-US/docs/Glossary/Prefetch
 /en-US/docs/Web/HTTP/Pipelining_FAQ	/en-US/docs/Web/HTTP/Connection_management_in_HTTP_1.x
 /en-US/docs/Web/HTTP/Proxy_servers_and_tunneling/Proxy_Auto-Configuration_(PAC)_file	/en-US/docs/Web/HTTP/Proxy_servers_and_tunneling/Proxy_Auto-Configuration_PAC_file
 /en-US/docs/Web/HTTP/Public_Key_Pinning	/en-US/docs/Web/Security/Certificate_Transparency
-/en-US/docs/Web/HTTP/Resources_and_URIs	/en-US/docs/Web/HTTP/Basics_of_HTTP/MIME_types
+/en-US/docs/Web/HTTP/Resources_and_URIs	/en-US/docs/Web/HTTP/MIME_types
 /en-US/docs/Web/HTTP/Response_codes	/en-US/docs/Web/HTTP/Status
 /en-US/docs/Web/HTTP/Server-Side_Access_Control	/en-US/docs/Web/HTTP/CORS
 /en-US/docs/Web/HTTP/Status/416_Range_Not_Satisfiable	/en-US/docs/Web/HTTP/Status/416
diff --git a/files/en-us/_wikihistory.json b/files/en-us/_wikihistory.json
index 1e046ceacbcb891..ef80cfaacde39eb 100644
--- a/files/en-us/_wikihistory.json
+++ b/files/en-us/_wikihistory.json
@@ -98403,115 +98403,6 @@
       "teoli"
     ]
   },
-  "Web/HTTP/Basics_of_HTTP": {
-    "modified": "2020-09-30T16:56:11.613Z",
-    "contributors": [
-      "firstnamelastname",
-      "chrisdavidmills",
-      "frattinijulien29",
-      "lbd1607",
-      "mfuji09",
-      "ExE-Boss",
-      "funghorn",
-      "BunnyWong",
-      "cissoid",
-      "teoli",
-      "fscholz"
-    ]
-  },
-  "Web/HTTP/Basics_of_HTTP/Evolution_of_HTTP": {
-    "modified": "2020-09-25T15:02:32.165Z",
-    "contributors": [
-      "mfuji09",
-      "darby",
-      "VitalyKrenel",
-      "Sgeo",
-      "ivnl",
-      "ExE-Boss",
-      "chrisdavidmills",
-      "zhaoyingdu",
-      "maruhgar",
-      "BunnyWong",
-      "rileym7",
-      "stephaniehobson",
-      "Yonkai",
-      "xcoderreal",
-      "fscholz",
-      "Cameron-Riecan",
-      "david_ross",
-      "DarrenLester",
-      "teoli"
-    ]
-  },
-  "Web/HTTP/Basics_of_HTTP/MIME_types": {
-    "modified": "2019-11-03T12:37:56.527Z",
-    "contributors": [
-      "mfuji09",
-      "Sheppy",
-      "Alhadis",
-      "awwright",
-      "sideshowbarker",
-      "ExE-Boss",
-      "Dzonny",
-      "Tigt",
-      "tribak",
-      "amitgupta15",
-      "nakkurt",
-      "MicroJes",
-      "snuggs",
-      "d4nyll",
-      "xgqfrms-GitHub",
-      "dawsonbotsford",
-      "g-patel",
-      "strattadb",
-      "david_ross",
-      "DJ-Leith",
-      "teoli",
-      "fscholz"
-    ]
-  },
-  "Web/HTTP/Basics_of_HTTP/MIME_types/Common_types": {
-    "modified": "2020-05-01T18:32:40.232Z",
-    "contributors": [
-      "broofa",
-      "sideshowbarker",
-      "chrisdavidmills",
-      "charj",
-      "SphinxKnight",
-      "mathiasbynens",
-      "Dorward",
-      "igorskyflyer",
-      "rctgamer3",
-      "mfuji09",
-      "Coder-Arjun",
-      "joeyparrish",
-      "devex23",
-      "ignaloidas",
-      "aadityataparia",
-      "dunglas",
-      "gabriele.bernuzzi",
-      "evilpie",
-      "xiaopanke",
-      "Loadmaster",
-      "iamakidilam",
-      "snuggs",
-      "Sheppy",
-      "Thw0rted",
-      "Krenair",
-      "Vikaash",
-      "Naesten",
-      "dave.shaheen",
-      "alettieri",
-      "NaveenDA",
-      "AbsoluteZERO",
-      "BrienA",
-      "kyrylkov",
-      "choury",
-      "david_ross",
-      "fscholz",
-      "teoli"
-    ]
-  },
   "Web/HTTP/Browser_detection_using_the_user_agent": {
     "modified": "2020-07-11T11:53:53.804Z",
     "contributors": [
@@ -99034,6 +98925,30 @@
       "fscholz"
     ]
   },
+  "Web/HTTP/Evolution_of_HTTP": {
+    "modified": "2020-09-25T15:02:32.165Z",
+    "contributors": [
+      "mfuji09",
+      "darby",
+      "VitalyKrenel",
+      "Sgeo",
+      "ivnl",
+      "ExE-Boss",
+      "chrisdavidmills",
+      "zhaoyingdu",
+      "maruhgar",
+      "BunnyWong",
+      "rileym7",
+      "stephaniehobson",
+      "Yonkai",
+      "xcoderreal",
+      "fscholz",
+      "Cameron-Riecan",
+      "david_ross",
+      "DarrenLester",
+      "teoli"
+    ]
+  },
   "Web/HTTP/Headers": {
     "modified": "2020-11-16T08:22:37.817Z",
     "contributors": [
@@ -100462,6 +100377,75 @@
       "fscholz"
     ]
   },
+  "Web/HTTP/MIME_types": {
+    "modified": "2019-11-03T12:37:56.527Z",
+    "contributors": [
+      "mfuji09",
+      "Sheppy",
+      "Alhadis",
+      "awwright",
+      "sideshowbarker",
+      "ExE-Boss",
+      "Dzonny",
+      "Tigt",
+      "tribak",
+      "amitgupta15",
+      "nakkurt",
+      "MicroJes",
+      "snuggs",
+      "d4nyll",
+      "xgqfrms-GitHub",
+      "dawsonbotsford",
+      "g-patel",
+      "strattadb",
+      "david_ross",
+      "DJ-Leith",
+      "teoli",
+      "fscholz"
+    ]
+  },
+  "Web/HTTP/MIME_types/Common_types": {
+    "modified": "2020-05-01T18:32:40.232Z",
+    "contributors": [
+      "broofa",
+      "sideshowbarker",
+      "chrisdavidmills",
+      "charj",
+      "SphinxKnight",
+      "mathiasbynens",
+      "Dorward",
+      "igorskyflyer",
+      "rctgamer3",
+      "mfuji09",
+      "Coder-Arjun",
+      "joeyparrish",
+      "devex23",
+      "ignaloidas",
+      "aadityataparia",
+      "dunglas",
+      "gabriele.bernuzzi",
+      "evilpie",
+      "xiaopanke",
+      "Loadmaster",
+      "iamakidilam",
+      "snuggs",
+      "Sheppy",
+      "Thw0rted",
+      "Krenair",
+      "Vikaash",
+      "Naesten",
+      "dave.shaheen",
+      "alettieri",
+      "NaveenDA",
+      "AbsoluteZERO",
+      "BrienA",
+      "kyrylkov",
+      "choury",
+      "david_ross",
+      "fscholz",
+      "teoli"
+    ]
+  },
   "Web/HTTP/Messages": {
     "modified": "2020-12-03T23:53:07.614Z",
     "contributors": [
diff --git a/files/en-us/glossary/http_2/index.md b/files/en-us/glossary/http_2/index.md
index 3e236e22f68157c..ec4aaf9dca94daf 100644
--- a/files/en-us/glossary/http_2/index.md
+++ b/files/en-us/glossary/http_2/index.md
@@ -6,11 +6,13 @@ page-type: glossary-definition
 
 {{GlossarySidebar}}
 
-**HTTP/2** is a major revision of the [HTTP network protocol](/en-US/docs/Web/HTTP/Basics_of_HTTP).
+**HTTP/2** is a major revision of the [HTTP network protocol](/en-US/docs/Web/HTTP).
 
-The primary goals for HTTP/2 are to reduce {{glossary("latency")}} by enabling full request and response multiplexing, minimize protocol overhead via efficient compression of HTTP header fields, and add support for request prioritization and server push.
+The primary goals for HTTP/2 are to reduce {{glossary("latency")}} and head-of-line blocking by enabling full request and response multiplexing, minimize protocol overhead via efficient compression of HTTP header fields, and add support for request prioritization and server push.
 
-HTTP/2 does not modify the application semantics of HTTP in any way. All the core concepts found in HTTP 1.1, such as HTTP methods, status codes, URIs, and header fields, remain in place. Instead, HTTP/2 modifies how the data is formatted (framed) and transported between the client and server, both of which manage the entire process, and hides application complexity within the new framing layer. As a result, all existing applications can be delivered without modification.
+HTTP/2 does not modify the semantics of HTTP, meaning the core concepts found in HTTP/1.1, such as methods, status codes, URIs, and header fields, remain the same.
+Instead, HTTP/2 modifies how the data is formatted (framed) and transported between the client and server, both of which manage the entire process, and hides protocol complexity within a framing layer.
+As a result, all existing applications can be delivered over the protocol without modification.
 
 ## See also
 
diff --git a/files/en-us/glossary/http_3/index.md b/files/en-us/glossary/http_3/index.md
index 2ab88ddb4422629..634a074fc61a1d1 100644
--- a/files/en-us/glossary/http_3/index.md
+++ b/files/en-us/glossary/http_3/index.md
@@ -6,13 +6,13 @@ page-type: glossary-definition
 
 {{GlossarySidebar}}
 
-**HTTP/3** is the upcoming major revision of the [HTTP network protocol](/en-US/docs/Web/HTTP/Basics_of_HTTP), succeeding {{glossary("HTTP 2", "HTTP/2")}}.
+**HTTP/3** is a major revision of the [HTTP network protocol](/en-US/docs/Web/HTTP), succeeding {{glossary("HTTP 2", "HTTP/2")}}.
 
-The major point of HTTP/3 is that it uses a new {{glossary("UDP")}} protocol named QUIC, instead of {{glossary("TCP")}}.
+The most notable difference in HTTP/3 is that it uses a protocol named QUIC over {{glossary("UDP")}} instead of {{glossary("TCP")}}.
 
 ## See also
 
-- [HTTP on MDN](/en-US/docs/Web/HTTP)
+- [HTTP documentation](/en-US/docs/Web/HTTP)
 - [HTTP/3](https://en.wikipedia.org/wiki/HTTP/3) on Wikipedia
 - Related glossary terms:
   - {{glossary("HTTP")}}
diff --git a/files/en-us/glossary/lossy_compression/index.md b/files/en-us/glossary/lossy_compression/index.md
index c413b75b47a6605..004f1997b50971f 100644
--- a/files/en-us/glossary/lossy_compression/index.md
+++ b/files/en-us/glossary/lossy_compression/index.md
@@ -8,7 +8,7 @@ page-type: glossary-definition
 
 **Lossy compression**, or irreversible compression, is a data-compression method that uses inexact approximations and partial-data discarding to represent content. In simpler terms: lossy compression causes data from the initial file to be lost, possibly causing degradation in quality. The process of such compression is irreversible; once lossy compression of the content has been performed, the content cannot be restored to its original state. Therefore, content that has undergone lossy compression should generally not be further edited.
 
-Lossy compression is widely used in image formats such as {{glossary("JPEG")}}, {{glossary("WebP")}}, and audio and video formats such as [MP3, MP4, H.264 and others](/en-US/docs/Web/HTTP/Basics_of_HTTP/MIME_types/Common_types).
+Lossy compression is widely used in image formats such as {{glossary("JPEG")}}, {{glossary("WebP")}}, and audio and video formats such as [MP3, MP4, H.264 and others](/en-US/docs/Web/HTTP/MIME_types/Common_types).
 Compression methods such as {{glossary("WebP")}} are capable of [both lossy and lossless compression](https://developers.google.com/speed/webp/docs/compression) depending on the compression level or the options you want to use during encoding.
 
 ![Lossy compression image](2019-11-18.png)
diff --git a/files/en-us/glossary/mime_type/index.md b/files/en-us/glossary/mime_type/index.md
index 2006f51e3da7e25..2816f19509abd86 100644
--- a/files/en-us/glossary/mime_type/index.md
+++ b/files/en-us/glossary/mime_type/index.md
@@ -16,6 +16,6 @@ The name originates from the {{glossary("mime","MIME")}} standard originally use
 - [Internet media type](https://en.wikipedia.org/wiki/Internet_media_type) on Wikipedia
 - [List of MIME types](https://www.iana.org/assignments/media-types/media-types.xhtml)
 - [Properly Configuring Server MIME Types](/en-US/docs/Learn/Server-side/Configuring_server_MIME_types)
-- Details information about the usage of [MIME Types](/en-US/docs/Web/HTTP/Basics_of_HTTP/MIME_types) in a Web context.
-- [Incomplete list of MIME types](/en-US/docs/Web/HTTP/Basics_of_HTTP/MIME_types/Common_types)
+- Details information about the usage of [MIME Types](/en-US/docs/Web/HTTP/MIME_types) in a Web context.
+- [Incomplete list of MIME types](/en-US/docs/Web/HTTP/MIME_types/Common_types)
 - [MediaRecorder.mimeType](/en-US/docs/Web/API/MediaRecorder/mimeType)
diff --git a/files/en-us/learn/forms/sending_and_retrieving_form_data/index.md b/files/en-us/learn/forms/sending_and_retrieving_form_data/index.md
index 8c9d800e7f77eff..f7e27d083a2c5bd 100644
--- a/files/en-us/learn/forms/sending_and_retrieving_form_data/index.md
+++ b/files/en-us/learn/forms/sending_and_retrieving_form_data/index.md
@@ -17,7 +17,7 @@ Once the form data has been validated on the client-side, it is okay to submit t
         <a href="/en-US/docs/Learn/HTML/Introduction_to_HTML"
           >understanding of HTML</a
         >, and basic knowledge of
-        <a href="/en-US/docs/Web/HTTP/Basics_of_HTTP">HTTP</a> and
+        <a href="/en-US/docs/Web/HTTP">HTTP</a> and
         <a href="/en-US/docs/Learn/Server-side/First_steps"
           >server-side programming</a
         >.
diff --git a/files/en-us/learn/getting_started_with_the_web/the_web_and_web_standards/index.md b/files/en-us/learn/getting_started_with_the_web/the_web_and_web_standards/index.md
index a71c9de758ee010..3cfd601cde8c236 100644
--- a/files/en-us/learn/getting_started_with_the_web/the_web_and_web_standards/index.md
+++ b/files/en-us/learn/getting_started_with_the_web/the_web_and_web_standards/index.md
@@ -66,7 +66,7 @@ You are probably reading these words inside a web browser in this very moment (u
 
 ### HTTP
 
-Hypertext Transfer Protocol, or [HTTP](/en-US/docs/Web/HTTP/Basics_of_HTTP), is a messaging protocol that allows web browsers to communicate with web servers (where websites are stored). A typical conversation goes something like
+Hypertext Transfer Protocol, or [HTTP](/en-US/docs/Web/HTTP), is a messaging protocol that allows web browsers to communicate with web servers (where websites are stored). A typical conversation goes something like
 
 ```plain
 "Hello web server. Can you give me the files I need to render bbc.co.uk"?
diff --git a/files/en-us/learn/server-side/configuring_server_mime_types/index.md b/files/en-us/learn/server-side/configuring_server_mime_types/index.md
index 2330b7b820993c8..19a9e101e7f150f 100644
--- a/files/en-us/learn/server-side/configuring_server_mime_types/index.md
+++ b/files/en-us/learn/server-side/configuring_server_mime_types/index.md
@@ -62,7 +62,7 @@ When looking for information about JavaScript MIME types, you may see several MI
 While browsers may support any, some, or all of these alternative MIME types, you should **only** use `text/javascript` to indicate the MIME type of JavaScript files.
 
 > [!NOTE]
-> See [MIME types (IANA media types)](/en-US/docs/Web/HTTP/Basics_of_HTTP/MIME_types) for more information.
+> See [MIME types (IANA media types)](/en-US/docs/Web/HTTP/MIME_types) for more information.
 
 ## How to determine the MIME type to set
 
@@ -109,6 +109,6 @@ Trying to instead set it with just `header('application/pdf')` won't work.
 
 - [IANA | MIME Media Types](https://www.iana.org/assignments/media-types/media-types.xhtml)
 - [Hypertext Transfer Protocol — HTTP/1.1](https://www.w3.org/Protocols/rfc2616/rfc2616.html)
-- [MIME types (IANA media types)](/en-US/docs/Web/HTTP/Basics_of_HTTP/MIME_types)
+- [MIME types (IANA media types)](/en-US/docs/Web/HTTP/MIME_types)
 - [Apache vs Nginx: Practical Considerations](https://www.digitalocean.com/community/tutorials/apache-vs-nginx-practical-considerations)
 - [Migrate Apache .htaccess to Nginx server block](https://barryvanveen.nl/articles/56-migrate-apache-htaccess-to-nginx-server-block/)
diff --git a/files/en-us/learn/server-side/node_server_without_framework/index.md b/files/en-us/learn/server-side/node_server_without_framework/index.md
index 58821f0e31151a4..c78e5020fb4d863 100644
--- a/files/en-us/learn/server-side/node_server_without_framework/index.md
+++ b/files/en-us/learn/server-side/node_server_without_framework/index.md
@@ -90,7 +90,7 @@ If the file can be served (the server process has access and no path-traversal v
 Note that other status codes can be found in `http.STATUS_CODES`.
 With `404` status we will return content of `'/404.html'` file.
 
-The extension of the file being requested will be parsed and lower-cased. After that we will search `MIME_TYPES` collection for the right [MIME types](/en-US/docs/Web/HTTP/Basics_of_HTTP/MIME_types). If no matches are found, we use the `application/octet-stream` as the default type.
+The extension of the file being requested will be parsed and lower-cased. After that we will search `MIME_TYPES` collection for the right [MIME types](/en-US/docs/Web/HTTP/MIME_types). If no matches are found, we use the `application/octet-stream` as the default type.
 
 Finally, if there are no errors, we send the requested file. The `file.stream` will contain a `Readable` stream that will be piped into `res` (an instance of the `Writable` stream).
 
diff --git a/files/en-us/mozilla/firefox/releases/65/index.md b/files/en-us/mozilla/firefox/releases/65/index.md
index 47063d4a3ef0e4b..c927185ecac50b6 100644
--- a/files/en-us/mozilla/firefox/releases/65/index.md
+++ b/files/en-us/mozilla/firefox/releases/65/index.md
@@ -107,7 +107,7 @@ _No changes._
 #### Fetch and Service workers
 
 - The {{domxref("Response.redirect_static", "Response.redirect()")}} method now correctly throws a `TypeError` if a non-valid URL is specified as the first parameter ([Firefox bug 1503276](https://bugzil.la/1503276)).
-- The {{domxref("ServiceWorkerContainer.register()")}} and {{domxref("WorkerGlobalScope.importScripts()")}} (when used by a service worker) methods will now accept any files with a valid [JavaScript MIME type](/en-US/docs/Web/HTTP/Basics_of_HTTP/MIME_types#textjavascript) ([Firefox bug 1354577](https://bugzil.la/1354577)).
+- The {{domxref("ServiceWorkerContainer.register()")}} and {{domxref("WorkerGlobalScope.importScripts()")}} (when used by a service worker) methods will now accept any files with a valid [JavaScript MIME type](/en-US/docs/Web/HTTP/MIME_types#textjavascript) ([Firefox bug 1354577](https://bugzil.la/1354577)).
 - The {{domxref("FetchEvent.replacesClientId")}} and {{domxref("FetchEvent.resultingClientId")}} properties are now supported ([Firefox bug 1264177](https://bugzil.la/1264177)).
 - The {{domxref("ServiceWorkerGlobalScope.messageerror_event", "ServiceWorkerGlobalScope.onmessageerror")}} and {{domxref("ServiceWorkerContainer.messageerror_event", "ServiceWorkerContainer.onmessageerror")}} handler properties have been implemented ([Firefox bug 1399446](https://bugzil.la/1399446)).
 - The {{httpheader("Origin")}} header is no longer set on Fetch requests with a method of {{HTTPMethod("HEAD")}} or {{HTTPMethod("GET")}} ([Firefox bug 1508661](https://bugzil.la/1508661)).
diff --git a/files/en-us/web/api/datatransferitem/type/index.md b/files/en-us/web/api/datatransferitem/type/index.md
index 87e85513e2c9359..1e907658398bc34 100644
--- a/files/en-us/web/api/datatransferitem/type/index.md
+++ b/files/en-us/web/api/datatransferitem/type/index.md
@@ -61,4 +61,4 @@ function dropHandler(ev) {
 ## See also
 
 - {{domxref("DataTransfer.types()")}}
-- [List of common MIME types](/en-US/docs/Web/HTTP/Basics_of_HTTP/MIME_types/Common_types)
+- [List of common MIME types](/en-US/docs/Web/HTTP/MIME_types/Common_types)
diff --git a/files/en-us/web/api/htmlmediaelement/canplaytype/index.md b/files/en-us/web/api/htmlmediaelement/canplaytype/index.md
index 52aa0e4ab4a4697..f70fe1bd45e3ee3 100644
--- a/files/en-us/web/api/htmlmediaelement/canplaytype/index.md
+++ b/files/en-us/web/api/htmlmediaelement/canplaytype/index.md
@@ -8,7 +8,7 @@ browser-compat: api.HTMLMediaElement.canPlayType
 
 {{APIRef("HTML DOM")}}
 
-The {{domxref("HTMLMediaElement")}} method **`canPlayType()`** reports how likely it is that the current browser will be able to play media of a given [MIME type](/en-US/docs/Web/HTTP/Basics_of_HTTP/MIME_types).
+The {{domxref("HTMLMediaElement")}} method **`canPlayType()`** reports how likely it is that the current browser will be able to play media of a given [MIME type](/en-US/docs/Web/HTTP/MIME_types).
 
 ## Syntax
 
@@ -19,7 +19,7 @@ canPlayType(type)
 ### Parameters
 
 - `type`
-  - : A string specifying the [MIME type](/en-US/docs/Web/HTTP/Basics_of_HTTP/MIME_types) of the media and (optionally) a [`codecs` parameter](/en-US/docs/Web/Media/Formats/codecs_parameter) containing a comma-separated list of the supported codecs.
+  - : A string specifying the [MIME type](/en-US/docs/Web/HTTP/MIME_types) of the media and (optionally) a [`codecs` parameter](/en-US/docs/Web/Media/Formats/codecs_parameter) containing a comma-separated list of the supported codecs.
 
 ### Return value
 
diff --git a/files/en-us/web/api/htmlscriptelement/index.md b/files/en-us/web/api/htmlscriptelement/index.md
index 836a73923a6b3db..2f77eeaa46a8af7 100644
--- a/files/en-us/web/api/htmlscriptelement/index.md
+++ b/files/en-us/web/api/htmlscriptelement/index.md
@@ -9,7 +9,7 @@ browser-compat: api.HTMLScriptElement
 
 HTML {{HTMLElement("script")}} elements expose the **`HTMLScriptElement`** interface, which provides special properties and methods for manipulating the behavior and execution of `<script>` elements (beyond the inherited {{domxref("HTMLElement")}} interface).
 
-JavaScript files should be served with the `text/javascript` [MIME type](/en-US/docs/Web/HTTP/Basics_of_HTTP/MIME_types), but browsers are lenient and block them only if the script is served with an image type (`image/*`), video type (`video/*`), audio type (`audio/*`), or `text/csv`. If the script is blocked, its element receives an {{domxref("HTMLElement/error_event", "error")}} event; otherwise, it receives a {{domxref("Window/load_event", "load")}} event.
+JavaScript files should be served with the `text/javascript` [MIME type](/en-US/docs/Web/HTTP/MIME_types), but browsers are lenient and block them only if the script is served with an image type (`image/*`), video type (`video/*`), audio type (`audio/*`), or `text/csv`. If the script is blocked, its element receives an {{domxref("HTMLElement/error_event", "error")}} event; otherwise, it receives a {{domxref("Window/load_event", "load")}} event.
 
 {{InheritanceDiagram}}
 
diff --git a/files/en-us/web/api/imagedecoder/imagedecoder/index.md b/files/en-us/web/api/imagedecoder/imagedecoder/index.md
index feee4219bdbb96a..d830770120c9c20 100644
--- a/files/en-us/web/api/imagedecoder/imagedecoder/index.md
+++ b/files/en-us/web/api/imagedecoder/imagedecoder/index.md
@@ -23,7 +23,7 @@ new ImageDecoder(init)
 - `init`
   - : An object containing the following members:
     - `type`
-      - : A string containing the [MIME type](/en-US/docs/Web/HTTP/Basics_of_HTTP/MIME_types) of the image file to be decoded.
+      - : A string containing the [MIME type](/en-US/docs/Web/HTTP/MIME_types) of the image file to be decoded.
     - `data`
       - : An {{jsxref("ArrayBuffer")}}, a {{jsxref("TypedArray")}}, a {{jsxref("DataView")}}, or a {{domxref("ReadableStream")}} of bytes representing an encoded image type as described by `type`.
     - `premultiplyAlpha` {{optional_inline}}
diff --git a/files/en-us/web/api/imagedecoder/index.md b/files/en-us/web/api/imagedecoder/index.md
index bc41f70f81434dc..1caf039456e1243 100644
--- a/files/en-us/web/api/imagedecoder/index.md
+++ b/files/en-us/web/api/imagedecoder/index.md
@@ -25,12 +25,12 @@ The **`ImageDecoder`** interface of the {{domxref('WebCodecs API','','','true')}
 - {{domxref("ImageDecoder.tracks")}} {{ReadOnlyInline}} {{Experimental_Inline}}
   - : Returns an {{domxref("ImageTrackList")}} object listing the available tracks and providing a method for selecting a track to decode.
 - {{domxref("ImageDecoder.type")}} {{ReadOnlyInline}} {{Experimental_Inline}}
-  - : Returns a string reflecting the [MIME type](/en-US/docs/Web/HTTP/Basics_of_HTTP/MIME_types) configured during construction.
+  - : Returns a string reflecting the [MIME type](/en-US/docs/Web/HTTP/MIME_types) configured during construction.
 
 ## Static methods
 
 - {{domxref("ImageDecoder.isTypeSupported_static", "ImageDecoder.isTypeSupported()")}} {{Experimental_Inline}}
-  - : Indicates if the provided [MIME type](/en-US/docs/Web/HTTP/Basics_of_HTTP/MIME_types) is supported for unpacking and decoding.
+  - : Indicates if the provided [MIME type](/en-US/docs/Web/HTTP/MIME_types) is supported for unpacking and decoding.
 
 ## Instance methods
 
diff --git a/files/en-us/web/api/imagedecoder/istypesupported_static/index.md b/files/en-us/web/api/imagedecoder/istypesupported_static/index.md
index c7260863b2ce407..9308c867db1d0ca 100644
--- a/files/en-us/web/api/imagedecoder/istypesupported_static/index.md
+++ b/files/en-us/web/api/imagedecoder/istypesupported_static/index.md
@@ -10,7 +10,7 @@ browser-compat: api.ImageDecoder.isTypeSupported_static
 
 {{securecontext_header}}{{APIRef("WebCodecs API")}}{{SeeCompatTable}}{{AvailableInWorkers("window_and_dedicated")}}
 
-The **`ImageDecoder.isTypeSupported()`** static method checks if a given [MIME type](/en-US/docs/Web/HTTP/Basics_of_HTTP/MIME_types) can be decoded by the user agent.
+The **`ImageDecoder.isTypeSupported()`** static method checks if a given [MIME type](/en-US/docs/Web/HTTP/MIME_types) can be decoded by the user agent.
 
 ## Syntax
 
@@ -21,7 +21,7 @@ ImageDecoder.isTypeSupported(type)
 ### Parameters
 
 - `type`
-  - : A string containing the [MIME type](/en-US/docs/Web/HTTP/Basics_of_HTTP/MIME_types) to check for decoding support.
+  - : A string containing the [MIME type](/en-US/docs/Web/HTTP/MIME_types) to check for decoding support.
 
 ### Return value
 
diff --git a/files/en-us/web/api/imagedecoder/type/index.md b/files/en-us/web/api/imagedecoder/type/index.md
index 8bfd96fec2cf986..5eb709a158c36fa 100644
--- a/files/en-us/web/api/imagedecoder/type/index.md
+++ b/files/en-us/web/api/imagedecoder/type/index.md
@@ -10,11 +10,11 @@ browser-compat: api.ImageDecoder.type
 
 {{securecontext_header}}{{APIRef("WebCodecs API")}}{{SeeCompatTable}}{{AvailableInWorkers("window_and_dedicated")}}
 
-The **`type`** read-only property of the {{domxref("ImageDecoder")}} interface reflects the [MIME type](/en-US/docs/Web/HTTP/Basics_of_HTTP/MIME_types) configured during construction.
+The **`type`** read-only property of the {{domxref("ImageDecoder")}} interface reflects the [MIME type](/en-US/docs/Web/HTTP/MIME_types) configured during construction.
 
 ## Value
 
-A string containing the configured [MIME type](/en-US/docs/Web/HTTP/Basics_of_HTTP/MIME_types).
+A string containing the configured [MIME type](/en-US/docs/Web/HTTP/MIME_types).
 
 ## Examples
 
diff --git a/files/en-us/web/api/mediarecorder/mimetype/index.md b/files/en-us/web/api/mediarecorder/mimetype/index.md
index 2e813ee53c64a32..4fa57ee39021a56 100644
--- a/files/en-us/web/api/mediarecorder/mimetype/index.md
+++ b/files/en-us/web/api/mediarecorder/mimetype/index.md
@@ -25,7 +25,7 @@ This string _may_ include the [`codecs` parameter,](/en-US/docs/Web/Media/Format
 
 The media type strings are standardized by the Internet Assigned Numbers Authority (IANA).
 For their official list of defined media type strings, see the article [Media Types](https://www.iana.org/assignments/media-types/media-types.xhtml) on the IANA site.
-See also [media types](/en-US/docs/Web/HTTP/Basics_of_HTTP/MIME_types) to learn more about media types and how they're used in web content and by web browsers.
+See also [media types](/en-US/docs/Web/HTTP/MIME_types) to learn more about media types and how they're used in web content and by web browsers.
 
 ## Examples
 
diff --git a/files/en-us/web/api/ndefmessage/ndefmessage/index.md b/files/en-us/web/api/ndefmessage/ndefmessage/index.md
index 32faac7feaa51a4..9a89521d7be4407 100644
--- a/files/en-us/web/api/ndefmessage/ndefmessage/index.md
+++ b/files/en-us/web/api/ndefmessage/ndefmessage/index.md
@@ -33,7 +33,7 @@ new NDEFMessage(records)
     - `lang` {{optional_inline}}
       - : A valid language tag according to {{RFC(5646, "Tags for Identifying Languages (also known as BCP 47)")}}.
     - `mediaType` {{optional_inline}}
-      - : A valid [MIME type](/en-US/docs/Web/HTTP/Basics_of_HTTP/MIME_types).
+      - : A valid [MIME type](/en-US/docs/Web/HTTP/MIME_types).
     - `recordType`
 
       - : A string indicating the type of data stored in `data`. It must be one of the following values:
@@ -47,7 +47,7 @@ new NDEFMessage(records)
           - : An empty {{domxref("NDEFRecord")}}.
 
         - `"mime"`
-          - : A valid [MIME type](/en-US/docs/Web/HTTP/Basics_of_HTTP/MIME_types).
+          - : A valid [MIME type](/en-US/docs/Web/HTTP/MIME_types).
         - `"smart-poster"`
           - : A smart poster as defined by the [NDEF-SMARTPOSTER](https://w3c.github.io/web-nfc/#bib-ndef-smartposter) specification.
         - `"text"`
diff --git a/files/en-us/web/api/ndefreader/write/index.md b/files/en-us/web/api/ndefreader/write/index.md
index 995c40398788c9f..46b9ceefcfa2b00 100644
--- a/files/en-us/web/api/ndefreader/write/index.md
+++ b/files/en-us/web/api/ndefreader/write/index.md
@@ -36,7 +36,7 @@ write(message, options)
     - `lang` {{optional_inline}}
       - : A valid language tag according to {{RFC(5646, "Tags for Identifying Languages (also known as BCP 47)")}}.
     - `mediaType` {{optional_inline}}
-      - : A valid [MIME type](/en-US/docs/Web/HTTP/Basics_of_HTTP/MIME_types).
+      - : A valid [MIME type](/en-US/docs/Web/HTTP/MIME_types).
     - `recordType`
 
       - : A string indicating the type of data stored in `data`. It must be one of the following values:
@@ -46,7 +46,7 @@ write(message, options)
         - `"empty"`
           - : An empty {{domxref("NDEFRecord")}}.
         - `"mime"`
-          - : A valid [MIME type](/en-US/docs/Web/HTTP/Basics_of_HTTP/MIME_types).
+          - : A valid [MIME type](/en-US/docs/Web/HTTP/MIME_types).
         - `"smart-poster"`
           - : A smart poster as defined by the [NDEF-SMARTPOSTER](https://w3c.github.io/web-nfc/#bib-ndef-smartposter) specification.
         - `"text"`
diff --git a/files/en-us/web/api/ndefreadingevent/ndefreadingevent/index.md b/files/en-us/web/api/ndefreadingevent/ndefreadingevent/index.md
index 57856b2bc98141c..89b564de9e16f7f 100644
--- a/files/en-us/web/api/ndefreadingevent/ndefreadingevent/index.md
+++ b/files/en-us/web/api/ndefreadingevent/ndefreadingevent/index.md
@@ -42,7 +42,7 @@ new NDEFReadingEvent(type, options)
         - `lang` {{optional_inline}}
           - : A valid language tag according to {{RFC(5646, "Tags for Identifying Languages (also known as BCP 47)")}}.
         - `mediaType` {{optional_inline}}
-          - : A valid [MIME type](/en-US/docs/Web/HTTP/Basics_of_HTTP/MIME_types).
+          - : A valid [MIME type](/en-US/docs/Web/HTTP/MIME_types).
         - `recordType`
 
           - : A string indicating the type of data stored in `data`. It must be one of the following values:
@@ -56,7 +56,7 @@ new NDEFReadingEvent(type, options)
               - : An empty {{domxref("NDEFRecord")}}.
 
             - `"mime"`
-              - : A valid [MIME type](/en-US/docs/Web/HTTP/Basics_of_HTTP/MIME_types).
+              - : A valid [MIME type](/en-US/docs/Web/HTTP/MIME_types).
             - `"smart-poster"`
               - : A smart poster as defined by the [NDEF-SMARTPOSTER](https://w3c.github.io/web-nfc/#bib-ndef-smartposter) specification.
             - `"text"`
diff --git a/files/en-us/web/api/ndefrecord/ndefrecord/index.md b/files/en-us/web/api/ndefrecord/ndefrecord/index.md
index 37e2aabe465317c..3e4b2242a4d2481 100644
--- a/files/en-us/web/api/ndefrecord/ndefrecord/index.md
+++ b/files/en-us/web/api/ndefrecord/ndefrecord/index.md
@@ -36,7 +36,7 @@ new NDEFRecord(options)
     - `lang` {{optional_inline}}
       - : A valid language tag according to {{RFC(5646, "Tags for Identifying Languages (also known as BCP 47)")}}.
     - `mediaType` {{optional_inline}}
-      - : A valid [MIME type](/en-US/docs/Web/HTTP/Basics_of_HTTP/MIME_types).
+      - : A valid [MIME type](/en-US/docs/Web/HTTP/MIME_types).
     - `recordType`
 
       - : A string indicating the type of data stored in `data`. It must be one of the following values:
@@ -50,7 +50,7 @@ new NDEFRecord(options)
           - : An empty {{domxref("NDEFRecord")}}.
 
         - `"mime"`
-          - : A valid [MIME type](/en-US/docs/Web/HTTP/Basics_of_HTTP/MIME_types).
+          - : A valid [MIME type](/en-US/docs/Web/HTTP/MIME_types).
         - `"smart-poster"`
           - : A smart poster as defined by the [NDEF-SMARTPOSTER](https://w3c.github.io/web-nfc/#bib-ndef-smartposter) specification.
         - `"text"`
diff --git a/files/en-us/web/api/serviceworkercontainer/register/index.md b/files/en-us/web/api/serviceworkercontainer/register/index.md
index 18959833d9ac9f0..2bf797b8ececc48 100644
--- a/files/en-us/web/api/serviceworkercontainer/register/index.md
+++ b/files/en-us/web/api/serviceworkercontainer/register/index.md
@@ -28,7 +28,7 @@ register(scriptURL, options)
 
 - `scriptURL`
   - : The URL of the service worker script. The registered service worker file needs to
-    have a valid [JavaScript MIME type](/en-US/docs/Web/HTTP/Basics_of_HTTP/MIME_types#textjavascript).
+    have a valid [JavaScript MIME type](/en-US/docs/Web/HTTP/MIME_types#textjavascript).
 - `options` {{optional_inline}}
 
   - : An object containing registration options. Currently available options are:
diff --git a/files/en-us/web/api/sharedworker/sharedworker/index.md b/files/en-us/web/api/sharedworker/sharedworker/index.md
index bbb2959628f4551..9ccb489a1c684b1 100644
--- a/files/en-us/web/api/sharedworker/sharedworker/index.md
+++ b/files/en-us/web/api/sharedworker/sharedworker/index.md
@@ -68,7 +68,7 @@ new SharedWorker(aURL, options)
 - `SecurityError` {{domxref("DOMException")}}
   - : Thrown if the document is not allowed to start workers, for example if the URL has an invalid syntax or if the same-origin policy is violated, or if the `sameSiteCookies` value is not supported in the given context.
 - `NetworkError` {{domxref("DOMException")}}
-  - : Thrown if the MIME type of the worker script is incorrect. It should _always_ be `text/javascript` (for historical reasons [other JavaScript MIME types](/en-US/docs/Web/HTTP/Basics_of_HTTP/MIME_types#textjavascript) may be accepted).
+  - : Thrown if the MIME type of the worker script is incorrect. It should _always_ be `text/javascript` (for historical reasons [other JavaScript MIME types](/en-US/docs/Web/HTTP/MIME_types#textjavascript) may be accepted).
 - `SyntaxError` {{domxref("DOMException")}}
   - : Thrown if `aURL` cannot be parsed.
 
diff --git a/files/en-us/web/api/window/showopenfilepicker/index.md b/files/en-us/web/api/window/showopenfilepicker/index.md
index 0bbb2fd166472cd..57d28dc587f77fe 100644
--- a/files/en-us/web/api/window/showopenfilepicker/index.md
+++ b/files/en-us/web/api/window/showopenfilepicker/index.md
@@ -49,7 +49,7 @@ showOpenFilePicker()
         - `description` {{Optional_Inline}}
           - : An optional description of the category of files types allowed. Defaults to an empty string.
         - `accept`
-          - : An {{jsxref('Object')}} with the keys set to the [MIME type](/en-US/docs/Web/HTTP/Basics_of_HTTP/MIME_types/Common_types) and the values an {{jsxref('Array')}} of file extensions (see below
+          - : An {{jsxref('Object')}} with the keys set to the [MIME type](/en-US/docs/Web/HTTP/MIME_types/Common_types) and the values an {{jsxref('Array')}} of file extensions (see below
             for an example).
 
 ### Return value
diff --git a/files/en-us/web/api/window/showsavefilepicker/index.md b/files/en-us/web/api/window/showsavefilepicker/index.md
index 8d5b7363ad8c517..710ce40c7cf3194 100644
--- a/files/en-us/web/api/window/showsavefilepicker/index.md
+++ b/files/en-us/web/api/window/showsavefilepicker/index.md
@@ -49,7 +49,7 @@ showSaveFilePicker()
           - : An optional description of the category of files
             types allowed. Default to be an empty string.
         - `accept`
-          - : An {{jsxref('Object')}} with the keys set to the [MIME type](/en-US/docs/Web/HTTP/Basics_of_HTTP/MIME_types/Common_types) and the values an {{jsxref('Array')}} of file extensions (see below
+          - : An {{jsxref('Object')}} with the keys set to the [MIME type](/en-US/docs/Web/HTTP/MIME_types/Common_types) and the values an {{jsxref('Array')}} of file extensions (see below
             for an example).
 
 ### Return value
diff --git a/files/en-us/web/api/worker/worker/index.md b/files/en-us/web/api/worker/worker/index.md
index 0262acffebb1826..28f2c4bb233231d 100644
--- a/files/en-us/web/api/worker/worker/index.md
+++ b/files/en-us/web/api/worker/worker/index.md
@@ -52,7 +52,7 @@ new Worker(url, options)
   - : Thrown if the document is not allowed to start workers, e.g. if the URL has an invalid syntax or if the same-origin policy is violated.
 - `NetworkError` {{domxref("DOMException")}}
   - : Thrown if the MIME type of the worker script is incorrect. It _should_ always be `text/javascript`
-    (for historical reasons [other JavaScript MIME types](/en-US/docs/Web/HTTP/Basics_of_HTTP/MIME_types#legacy_javascript_mime_types) may be accepted).
+    (for historical reasons [other JavaScript MIME types](/en-US/docs/Web/HTTP/MIME_types#legacy_javascript_mime_types) may be accepted).
 - `SyntaxError` {{domxref("DOMException")}}
   - : Thrown if _aURL_ cannot be parsed.
 
diff --git a/files/en-us/web/api/workerglobalscope/importscripts/index.md b/files/en-us/web/api/workerglobalscope/importscripts/index.md
index 82a2e18f2131605..46b1d04275f8055 100644
--- a/files/en-us/web/api/workerglobalscope/importscripts/index.md
+++ b/files/en-us/web/api/workerglobalscope/importscripts/index.md
@@ -30,7 +30,7 @@ None ({{jsxref("undefined")}}).
 ### Exceptions
 
 - `NetworkError`
-  - : Imported scripts were served without a `text/javascript` MIME type or without one of the permitted [legacy JavaScript MIME types](/en-US/docs/Web/HTTP/Basics_of_HTTP/MIME_types#legacy_javascript_mime_types).
+  - : Imported scripts were served without a `text/javascript` MIME type or without one of the permitted [legacy JavaScript MIME types](/en-US/docs/Web/HTTP/MIME_types#legacy_javascript_mime_types).
 - {{jsxref("TypeError")}}
   - : Thrown if the current {{domxref("WorkerGlobalScope")}} is a module. Use [`import`](/en-US/docs/Web/JavaScript/Reference/Statements/import) instead.
 
diff --git a/files/en-us/web/html/element/input/file/index.md b/files/en-us/web/html/element/input/file/index.md
index d248bcb45499cb2..e684b364b5685bc 100644
--- a/files/en-us/web/html/element/input/file/index.md
+++ b/files/en-us/web/html/element/input/file/index.md
@@ -119,7 +119,7 @@ Each `File` object contains the following information:
 - `size`
   - : The size of the file in bytes.
 - `type`
-  - : The file's [MIME type](/en-US/docs/Web/HTTP/Basics_of_HTTP/MIME_types).
+  - : The file's [MIME type](/en-US/docs/Web/HTTP/MIME_types).
 - `webkitRelativePath` {{non-standard_inline}}
   - : A string specifying the file's path relative to the base directory selected in a directory picker (that is, a `file` picker in which the [`webkitdirectory`](#webkitdirectory) attribute is set). _This is non-standard and should be used with caution._
 
diff --git a/files/en-us/web/html/element/meta/index.md b/files/en-us/web/html/element/meta/index.md
index 1e3eec5896a6b35..e9afb1fd0a12e28 100644
--- a/files/en-us/web/html/element/meta/index.md
+++ b/files/en-us/web/html/element/meta/index.md
@@ -39,7 +39,7 @@ This element includes the [global attributes](/en-US/docs/Web/HTML/Global_attrib
 
     - `content-type`
 
-      - : Declares the [MIME type](/en-US/docs/Web/HTTP/Basics_of_HTTP/MIME_types) and the document's character encoding. The `content` attribute must have the value `"text/html; charset=utf-8"` if specified. This is equivalent to a `<meta>` element with the [`charset`](#charset) attribute specified and carries the same restriction on placement within the document. **Note:** Can only be used in documents served with a `text/html` — not in documents served with an XML MIME type.
+      - : Declares the [MIME type](/en-US/docs/Web/HTTP/MIME_types) and the document's character encoding. The `content` attribute must have the value `"text/html; charset=utf-8"` if specified. This is equivalent to a `<meta>` element with the [`charset`](#charset) attribute specified and carries the same restriction on placement within the document. **Note:** Can only be used in documents served with a `text/html` — not in documents served with an XML MIME type.
 
         Also see {{HTTPHeader("Content-Type")}}.
 
diff --git a/files/en-us/web/html/element/picture/index.md b/files/en-us/web/html/element/picture/index.md
index 102c96dd74482bd..48640038d08c168 100644
--- a/files/en-us/web/html/element/picture/index.md
+++ b/files/en-us/web/html/element/picture/index.md
@@ -105,7 +105,7 @@ For more information on using `srcset`, see the [Responsive images](/en-US/docs/
 
 ### The type attribute
 
-The `type` attribute specifies a [MIME type](/en-US/docs/Web/HTTP/Basics_of_HTTP/MIME_types) for the resource URL(s) in the {{HTMLElement("source")}} element's `srcset` attribute. If the user agent does not support the given type, the {{HTMLElement("source")}} element is skipped.
+The `type` attribute specifies a [MIME type](/en-US/docs/Web/HTTP/MIME_types) for the resource URL(s) in the {{HTMLElement("source")}} element's `srcset` attribute. If the user agent does not support the given type, the {{HTMLElement("source")}} element is skipped.
 
 ```html
 <picture>
diff --git a/files/en-us/web/html/element/script/index.md b/files/en-us/web/html/element/script/index.md
index 903ccc018d881d1..41a2e93285b06b7 100644
--- a/files/en-us/web/html/element/script/index.md
+++ b/files/en-us/web/html/element/script/index.md
@@ -122,7 +122,7 @@ This element includes the [global attributes](/en-US/docs/Web/HTML/Global_attrib
     - **Attribute is not set (default), an empty string, or a JavaScript MIME type**
       - : Indicates that the script is a "classic script", containing JavaScript code.
         Authors are encouraged to omit the attribute if the script refers to JavaScript code rather than specify a MIME type.
-        JavaScript MIME types are [listed in the IANA media types specification](/en-US/docs/Web/HTTP/Basics_of_HTTP/MIME_types#textjavascript).
+        JavaScript MIME types are [listed in the IANA media types specification](/en-US/docs/Web/HTTP/MIME_types#textjavascript).
     - [`importmap`](/en-US/docs/Web/HTML/Element/script/type/importmap)
       - : This value indicates that the body of the element contains an import map.
         The import map is a JSON object that developers can use to control how the browser resolves module specifiers when importing [JavaScript modules](/en-US/docs/Web/JavaScript/Guide/Modules#importing_modules_using_import_maps).
diff --git a/files/en-us/web/html/element/script/type/index.md b/files/en-us/web/html/element/script/type/index.md
index 2f1ff8d3cbaa01d..3e850bbdeaccaf8 100644
--- a/files/en-us/web/html/element/script/type/index.md
+++ b/files/en-us/web/html/element/script/type/index.md
@@ -16,7 +16,7 @@ The value of this attribute indicates the type of data represented by the script
 - **Attribute is not set (default), an empty string, or a JavaScript MIME type**
   - : Indicates that the script is a "classic script", containing JavaScript code.
     Authors are encouraged to omit the attribute if the script refers to JavaScript code rather than specify a MIME type.
-    JavaScript MIME types are [listed in the IANA media types specification](/en-US/docs/Web/HTTP/Basics_of_HTTP/MIME_types#textjavascript).
+    JavaScript MIME types are [listed in the IANA media types specification](/en-US/docs/Web/HTTP/MIME_types#textjavascript).
 - [`importmap`](/en-US/docs/Web/HTML/Element/script/type/importmap)
   - : This value indicates that the body of the element contains an import map.
     The import map is a JSON object that developers can use to control how the browser resolves module specifiers when importing [JavaScript modules](/en-US/docs/Web/JavaScript/Guide/Modules#importing_modules_using_import_maps).
diff --git a/files/en-us/web/http/basics_of_http/index.md b/files/en-us/web/http/basics_of_http/index.md
deleted file mode 100644
index 1d02d7dfe39bd37..000000000000000
--- a/files/en-us/web/http/basics_of_http/index.md
+++ /dev/null
@@ -1,32 +0,0 @@
----
-title: Basics of HTTP
-slug: Web/HTTP/Basics_of_HTTP
-page-type: guide
----
-
-{{HTTPSidebar}}
-
-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.
-
-## Articles
-
-- [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.
-- [URIs](/en-US/docs/Web/URI)
-  - : URIs are used to locate resources on the web and can be used as the targets of HTTP requests.
-- [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.
-- [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/cors/index.md b/files/en-us/web/http/cors/index.md
index 2bfcd4726d215e8..1d60ddf4f6b9a6b 100644
--- a/files/en-us/web/http/cors/index.md
+++ b/files/en-us/web/http/cors/index.md
@@ -31,7 +31,7 @@ This is a general article about Cross-Origin Resource Sharing and includes a dis
 
 ## Functional overview
 
-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.
+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/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.
 
 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.
 
diff --git a/files/en-us/web/http/basics_of_http/evolution_of_http/index.md b/files/en-us/web/http/evolution_of_http/index.md
similarity index 99%
rename from files/en-us/web/http/basics_of_http/evolution_of_http/index.md
rename to files/en-us/web/http/evolution_of_http/index.md
index d16d6017228892a..73a26d3e8ad4a1d 100644
--- a/files/en-us/web/http/basics_of_http/evolution_of_http/index.md
+++ b/files/en-us/web/http/evolution_of_http/index.md
@@ -1,6 +1,6 @@
 ---
 title: Evolution of HTTP
-slug: Web/HTTP/Basics_of_HTTP/Evolution_of_HTTP
+slug: Web/HTTP/Evolution_of_HTTP
 page-type: guide
 ---
 
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 3ab015ba0102b0e..619c2407035d70a 100644
--- a/files/en-us/web/http/headers/accept-post/index.md
+++ b/files/en-us/web/http/headers/accept-post/index.md
@@ -7,7 +7,7 @@ spec-urls: https://www.w3.org/TR/ldp/#header-accept-post
 
 {{HTTPSidebar}}
 
-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.
+The **`Accept-Post`** response HTTP header advertises which [media types](/en-US/docs/Web/HTTP/MIME_types) are accepted by the server for HTTP post requests.
 
 **`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).
 
diff --git a/files/en-us/web/http/headers/accept/index.md b/files/en-us/web/http/headers/accept/index.md
index 83e3d9c2724be87..ab6642dec7a7dce 100644
--- a/files/en-us/web/http/headers/accept/index.md
+++ b/files/en-us/web/http/headers/accept/index.md
@@ -7,7 +7,7 @@ browser-compat: http.headers.Accept
 
 {{HTTPSidebar}}
 
-The **`Accept`** request HTTP header indicates which content types, expressed as [MIME types](/en-US/docs/Web/HTTP/Basics_of_HTTP/MIME_types), the client is able to understand. The server uses [content negotiation](/en-US/docs/Web/HTTP/Content_negotiation) to select one of the proposals and informs the client of the choice with the {{HTTPHeader("Content-Type")}} response header. Browsers set required values for this header based on the context of the request. For example, a browser uses different values in a request when fetching a CSS stylesheet, image, video, or a script.
+The **`Accept`** request HTTP header indicates which content types, expressed as [MIME types](/en-US/docs/Web/HTTP/MIME_types), the client is able to understand. The server uses [content negotiation](/en-US/docs/Web/HTTP/Content_negotiation) to select one of the proposals and informs the client of the choice with the {{HTTPHeader("Content-Type")}} response header. Browsers set required values for this header based on the context of the request. For example, a browser uses different values in a request when fetching a CSS stylesheet, image, video, or a script.
 
 <table class="properties">
   <tbody>
@@ -46,7 +46,7 @@ Accept: text/html, application/xhtml+xml, application/xml;q=0.9, image/webp, */*
 ## Directives
 
 - `<MIME_type>/<MIME_subtype>`
-  - : A single, precise [MIME type](/en-US/docs/Web/HTTP/Basics_of_HTTP/MIME_types), like `text/html`.
+  - : A single, precise [MIME type](/en-US/docs/Web/HTTP/MIME_types), like `text/html`.
 - `<MIME_type>/*`
   - : A MIME type, but without a subtype. `image/*` corresponds to `image/png`, `image/svg`, `image/gif`, and other image types.
 - `*/*`
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 a9946065c65afd7..dd1857715c1a549 100644
--- a/files/en-us/web/http/headers/content-type/index.md
+++ b/files/en-us/web/http/headers/content-type/index.md
@@ -16,7 +16,7 @@ If a server implementation or configuration is strict about content type handlin
 The `Content-Type` header differs from {{HTTPHeader("Content-Encoding")}} in that `Content-Encoding` helps the recipient understand how to decode data to its original form.
 
 > [!NOTE]
-> This value may be ignored if browsers perform [MIME sniffing](/en-US/docs/Web/HTTP/Basics_of_HTTP/MIME_types#mime_sniffing) (or content sniffing) on responses.
+> This value may be ignored if browsers perform [MIME sniffing](/en-US/docs/Web/HTTP/MIME_types#mime_sniffing) (or content sniffing) on responses.
 > To prevent browsers from using MIME sniffing, set the {{HTTPHeader("X-Content-Type-Options")}} header value to `nosniff`.
 > See [MIME type verification](/en-US/docs/Web/Security/Practical_implementation_guides/MIME_types) for more details.
 
@@ -65,7 +65,7 @@ Content-Type: multipart/form-data; boundary=ExampleBoundaryString
 
 - `<media-type>`
 
-  - : The [media type](/en-US/docs/Web/HTTP/Basics_of_HTTP/MIME_types) of the resource or data.
+  - : The [media type](/en-US/docs/Web/HTTP/MIME_types) of the resource or data.
     May contain the following parameters:
 
     - **`charset`**: Indicates the {{Glossary("character encoding")}} standard used. The value is case insensitive, but lowercase is preferred.
diff --git a/files/en-us/web/http/headers/index.md b/files/en-us/web/http/headers/index.md
index 8d65f60dfbd47c1..5e00b71c200ba47 100644
--- a/files/en-us/web/http/headers/index.md
+++ b/files/en-us/web/http/headers/index.md
@@ -19,7 +19,7 @@ Headers can be grouped according to their contexts:
 - {{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.
+  - : Contain information about the body of the resource, like its [MIME type](/en-US/docs/Web/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.
 
@@ -92,9 +92,9 @@ For more details, refer to the [Content negotiation article](/en-US/docs/Web/HTT
 - {{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).
 - {{HTTPHeader("Accept-Patch")}}
-  - : A _request content negotiation_ response header that advertises which [media type](/en-US/docs/Web/HTTP/Basics_of_HTTP/MIME_types) the server is able to understand in a {{HTTPMethod("PATCH")}} request.
+  - : A _request content negotiation_ response header that advertises which [media type](/en-US/docs/Web/HTTP/MIME_types) the server is able to understand in a {{HTTPMethod("PATCH")}} request.
 - {{HTTPHeader("Accept-Post")}}
-  - : A _request content negotiation_ response header that advertises which [media type](/en-US/docs/Web/HTTP/Basics_of_HTTP/MIME_types) the server is able to understand in a {{HTTPMethod("POST")}} request.
+  - : A _request content negotiation_ response header that advertises which [media type](/en-US/docs/Web/HTTP/MIME_types) the server is able to understand in a {{HTTPMethod("POST")}} request.
 
 ## Controls
 
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 8096af008c83da9..a3c79282cf7dca9 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,8 +8,8 @@ browser-compat: http.headers.X-Content-Type-Options
 {{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 be followed and not be changed. The header allows you to avoid [MIME type sniffing](/en-US/docs/Web/HTTP/Basics_of_HTTP/MIME_types#mime_sniffing) by saying that the MIME types are deliberately
+marker used by the server to indicate that the [MIME types](/en-US/docs/Web/HTTP/MIME_types) advertised in the
+{{HTTPHeader("Content-Type")}} headers should be followed and not be changed. The header allows you to avoid [MIME type sniffing](/en-US/docs/Web/HTTP/MIME_types#mime_sniffing) by saying that the MIME types are deliberately
 configured.
 
 This header was introduced by Microsoft in IE 8 as a way for webmasters to block
diff --git a/files/en-us/web/http/index.md b/files/en-us/web/http/index.md
index cafae1b593a4257..5b383c28dc2d2f1 100644
--- a/files/en-us/web/http/index.md
+++ b/files/en-us/web/http/index.md
@@ -6,46 +6,113 @@ page-type: landing-page
 
 {{HTTPSidebar}}
 
-**_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.
+**_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, such as machine-to-machine communication, programmatic access to APIs, and more.
 
-## Tutorials
+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 from the server.
+HTTP is a [stateless protocol](https://en.wikipedia.org/wiki/Stateless_protocol), meaning that the server does not keep any session data between two requests, although the later addition of [cookies](/en-US/docs/Web/HTTP/Cookies) adds state to some client-server interactions.
 
-Learn how to use HTTP with guides and tutorials.
+## References
+
+The HTTP reference documentation contains detailed information about headers, request methods, status responses, and lists relevant specifications and standards documents.
+
+- [HTTP headers](/en-US/docs/Web/HTTP/Headers)
+  - : Message headers are used to send metadata about a resource or a HTTP message, and to describe the behavior of the client or the server.
+- [HTTP request methods](/en-US/docs/Web/HTTP/Methods)
+  - : Request methods indicate the purpose of the request and what is expected if the request is successful.
+    The most common methods are {{HTTPMethod("GET")}} and {{HTTPMethod("POST")}} for retrieving and sending data to servers, respectively, but there are other methods which serve different purposes.
+- [HTTP response status codes](/en-US/docs/Web/HTTP/Status)
+  - : Response status codes indicate the outcome of a specific HTTP request.
+    Responses are grouped in five classes: informational, successful, redirections, client errors, and server errors.
+- [HTTP resources and specifications](/en-US/docs/Web/HTTP/Resources_and_specifications)
+  - : This page lists relevant resources about HTTP since it was first specified in the early 1990s.
+
+## HTTP guides
+
+HTTP is an extensible protocol that relies on concepts like resources and Uniform Resource Identifiers (URIs), a simple message structure, and client-server communication model.
+On top of these concepts, numerous extensions have been developed over the years that add functionality and updated semantics, including additional HTTP methods and headers.
+
+The guides below are listed in order from general overviews to specialized, use-case-driven topics.
+Beginners are encouraged to start with the foundational guides before exploring more focused articles.
 
 - [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 websites. 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.
-- [HTTP Client Hints](/en-US/docs/Web/HTTP/Client_hints)
-  - : **Client Hints** are a set of response headers that a server can use to proactively request information from a client about the device, network, user, and user-agent-specific preferences.
-    The server can then determine which resources to send, based on the information that the client chooses to provide.
-- [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://infosec.mozilla.org/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.
+  - : The basic features of HTTP, what it can do, its intended use in web architecture, and its position in the protocol stack.
 - [A typical HTTP session](/en-US/docs/Web/HTTP/Session)
-  - : Shows and explains the flow of a usual HTTP session.
+  - : Describes the flow of an HTTP session, from establishing a connection, sending a request, to receiving a response.
+- [HTTP messages](/en-US/docs/Web/HTTP/Messages)
+  - : HTTP messages transmitted as requests and responses have a defined structure.
+    This article describes this general structure, its purpose, and the different types of messages.
+- [URIs](/en-US/docs/Web/URI)
+  - : Uniform Resource Identifiers (URIs) are used to describe and locate resources on the web and are an essential component in HTTP requests.
+- [MIME types](/en-US/docs/Web/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.
+    A shortlist of common types used by web developers can be found in [Common MIME types](Web/HTTP/MIME_types/Common_types).
+- [Compression in HTTP](/en-US/docs/Web/HTTP/Compression)
+  - : Browsers and servers compress their messages before sending them over the network to reduce the amount of data that needs to be transmitted, improving transfer speed and bandwidth utilization.
+- [HTTP caching](/en-US/docs/Web/HTTP/Caching)
+  - : Caching is a highly important mechanism for delivering fast experiences on the Web and for efficient use of resources.
+    This article describes different methods of caching and how to use HTTP headers to control them.
+- [HTTP authentication](/en-US/docs/Web/HTTP/Authentication)
+  - : Authentication is a way to verify the identity of a client when making requests to a server.
+    It ensures that only authorized users or systems can access certain resources.
+- [Using HTTP cookies](/en-US/docs/Web/HTTP/Cookies)
+  - : Although HTTP is a stateless protocol, a server can send a {{HTTPHeader("Set-Cookie")}} header with the response.
+    The client then returns the cookie's value with every subsequent request to the server in the form of a {{HTTPHeader("Cookie")}} request header.
+    This adds the ability to store and exchange a small amount of data which effectively adds state to some client-server interactions.
+- [Redirections in HTTP](/en-US/docs/Web/HTTP/Redirections)
+  - : URL redirection, also known as URL forwarding, is a technique to give more than one URL address to a page, a form, a whole website, or a web application.
+    HTTP has a special kind of response, called a HTTP redirect, for this operation.
+- [HTTP conditional requests](/en-US/docs/Web/HTTP/Conditional_requests)
+  - : In conditional requests, the outcome of a request depends on the value of a validator in the request.
+    This method is used heavily in [caching](/en-US/docs/Web/HTTP/Caching) and use cases such as resuming a download, preventing lost updates when modifying a document on the server, and more.
+- [HTTP range requests](/en-US/docs/Web/HTTP/Range_requests)
+  - : A range request asks the server to send a specific part (or parts) of a resource back to a client instead of the full resource.
+    Range requests are useful for cases when a client knows they need only part of a large file, or for cases where an application allows the user to pause and resume a download.
+- [Content negotiation](/en-US/docs/Web/HTTP/Content_negotiation)
+  - : HTTP defines a set of message 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 to a request.
 - [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.
-
-## Reference
+  - : HTTP/1.1 was the first version of HTTP to support persistent connections and pipelining.
+    This article explains both concepts, including the pros and cons of each.
+- [Evolution of HTTP](/en-US/docs/Web/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, through HTTP/2 and HTTP/3, as well as novelties introduced over the years.
+- [Protocol upgrade mechanism](/en-US/docs/Web/HTTP/Protocol_upgrade_mechanism)
+  - : HTTP/1.1 provides a mechanism to upgrade an already-established connection to a different protocol using the {{HTTPHeader("Upgrade")}} header.
+    A client can upgrade a connection from HTTP/1.1 to HTTP/2, or an HTTP(S) connection to a [WebSocket](/en-US/docs/Web/API/WebSocket) (`ws` / `wss`).
+- [Proxy servers and tunneling](/en-US/docs/Web/HTTP/Proxy_servers_and_tunneling)
+  - : 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.
+- [HTTP Client hints](/en-US/docs/Web/HTTP/Client_hints)
+  - : Client Hints are a set of response headers that a server can use to proactively request information from a client about the device, network, user, and user-agent-specific preferences.
+    The server can then determine which resources to send, based on the information that the client chooses to provide.
+- [Network Error Logging](/en-US/docs/Web/HTTP/Network_Error_Logging) {{experimental_inline}}
+  - : Network Error Logging is a mechanism that can be configured via the `NEL` HTTP response header.
+    This experimental header allows websites and applications to opt-in to receive reports about failed (or even successful) network fetches from supporting browsers.
+- [Browser detection using the user agent](/en-US/docs/Web/HTTP/Browser_detection_using_the_user_agent)
+  - : It's very rarely a good idea to use user agent sniffing to detect a browser, but there are edge cases that require it.
+    This document will guide you in doing this as correctly as possible when this is necessary, with an emphasis on considerations to make before embarking on this route.
+- [Configuring servers for Ogg media](/en-US/docs/Web/HTTP/Configuring_servers_for_Ogg_media)
+  - : 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.
 
-Browse through detailed HTTP reference documentation.
+### Security and privacy
 
-- [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 maintained in an [IANA HTTP Field Name Registry](https://www.iana.org/assignments/http-fields/http-fields.xhtml), which includes [information about their status](https://github.com/protocol-registries/http-fields?tab=readme-ov-file#choosing-the-right-status), which may be "permanent" (standards-defined), "provisional" (new), "deprecated" (use not recommended), or "obsolete" (no longer in use).
-- [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 website 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.
+- [Mozilla web security guidelines](https://infosec.mozilla.org/guidelines/web_security)
+  - : A collection of tips to help operational teams with creating secure web applications.
+- [Permissions Policy](/en-US/docs/Web/HTTP/Permissions_Policy)
+  - : Permissions Policy provides mechanisms for web developers to explicitly declare what functionality can and cannot be used on a website.
+    You define a set of "policies" that restrict what APIs the site's code can access or modify the browser's default behavior for certain features.
+- [Cross-Origin Resource Sharing (CORS)](/en-US/docs/Web/HTTP/CORS)
+  - : Cross-site HTTP requests are requests for resources from a different domain than that of the resource making the request.
+    Web pages today very commonly load cross-site resources, for example, a page 'Domain A' (`http://domaina.example/`) requests an image on 'Domain B' (`http://domainb.foo/image.jpg`) via the `img` element.
+    CORS allows web developers to control how their site reacts to cross-site requests.
+- [Content Security Policy (CSP)](/en-US/docs/Web/HTTP/CSP)
+  - : CSP allows website administrators to use the {{HTTPHeader("Content-Security-Policy")}} response header to control which resources the client is allowed to load for a given page.
+    The CSP guide describes the overall Content Security Policy mechanism which helps detect and mitigate certain types of attacks, including Cross-Site Scripting (XSS) and data injection attacks.
+- [Cross-Origin Resource Policy (CORP)](/en-US/docs/Web/HTTP/Cross-Origin_Resource_Policy)
+  - : CORP lets websites and applications opt in to protection against specific requests from other origins (such as those issued with elements like `<script>` and `<img>`), to mitigate speculative side-channel attacks.
 
 ## Tools & resources
 
@@ -57,5 +124,10 @@ Helpful tools and resources for understanding and debugging HTTP.
   - : 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.
+- [nghttp2](https://github.com/nghttp2/nghttp2)
+  - : An HTTP/2 client, server and proxy implementation written in C with load test and benchmarking tools and an HPACK encoder and decoder.
+- [curl](https://github.com/curl/curl)
+  - : A command-line tool for transferring data specified with URL syntax.
+    Supports HTTP, HTTPS, WS, WSS, among many other protocols.
 - [How Browsers Work (2011)](https://web.dev/articles/howbrowserswork)
   - : A very comprehensive article on browser internals and request flow through HTTP protocol.
diff --git a/files/en-us/web/http/messages/index.md b/files/en-us/web/http/messages/index.md
index 10f86bf847ff728..103258f1bf3c2c4 100644
--- a/files/en-us/web/http/messages/index.md
+++ b/files/en-us/web/http/messages/index.md
@@ -69,7 +69,7 @@ Not all requests have one: requests with a {{HTTPMethod("GET")}} _[HTTP method](
 Bodies can be broadly divided into two categories:
 
 - 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).
+- [Multiple-resource bodies](/en-US/docs/Web/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).
 
 ## HTTP Responses
 
@@ -106,7 +106,7 @@ Bodies can be broadly divided into three categories:
 
 - 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.
+- [Multiple-resource bodies](/en-US/docs/Web/HTTP/MIME_types#multipartform-data), consisting of a multipart body, each containing a different section of information. These are relatively rare.
 
 ## HTTP/2 Frames
 
diff --git a/files/en-us/web/http/basics_of_http/mime_types/common_types/index.md b/files/en-us/web/http/mime_types/common_types/index.md
similarity index 99%
rename from files/en-us/web/http/basics_of_http/mime_types/common_types/index.md
rename to files/en-us/web/http/mime_types/common_types/index.md
index 6d42ba75a96d1eb..a08804ae43a6ae7 100644
--- a/files/en-us/web/http/basics_of_http/mime_types/common_types/index.md
+++ b/files/en-us/web/http/mime_types/common_types/index.md
@@ -1,6 +1,6 @@
 ---
 title: Common MIME types
-slug: Web/HTTP/Basics_of_HTTP/MIME_types/Common_types
+slug: Web/HTTP/MIME_types/Common_types
 page-type: guide
 ---
 
diff --git a/files/en-us/web/http/basics_of_http/mime_types/index.md b/files/en-us/web/http/mime_types/index.md
similarity index 99%
rename from files/en-us/web/http/basics_of_http/mime_types/index.md
rename to files/en-us/web/http/mime_types/index.md
index df3ce1b66f62fe1..ed98e7532c308ed 100644
--- a/files/en-us/web/http/basics_of_http/mime_types/index.md
+++ b/files/en-us/web/http/mime_types/index.md
@@ -1,6 +1,6 @@
 ---
 title: MIME types (IANA media types)
-slug: Web/HTTP/Basics_of_HTTP/MIME_types
+slug: Web/HTTP/MIME_types
 page-type: guide
 ---
 
@@ -207,7 +207,7 @@ The [codecs used by WebRTC](/en-US/docs/Web/Media/Formats/WebRTC_codecs) guide e
 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.
 
-For more information on common media types, see the [Common MIME types](/en-US/docs/Web/HTTP/Basics_of_HTTP/MIME_types/Common_types) page.
+For more information on common media types, see the [Common MIME types](/en-US/docs/Web/HTTP/MIME_types/Common_types) page.
 
 ### multipart/form-data
 
diff --git a/files/en-us/web/javascript/reference/statements/import/with/index.md b/files/en-us/web/javascript/reference/statements/import/with/index.md
index 46f198c5f91246a..091a9f69a09b147 100644
--- a/files/en-us/web/javascript/reference/statements/import/with/index.md
+++ b/files/en-us/web/javascript/reference/statements/import/with/index.md
@@ -54,7 +54,7 @@ Content-Type: application/json; charset=utf-8
 {"name":"John"}
 ```
 
-Modules are identified and parsed only according to their served [MIME type](/en-US/docs/Web/HTTP/Basics_of_HTTP/MIME_types) — the file extension in the URL cannot be used to identify a file's type. In this case, the MIME type is `application/json`, which tells the browser that the file is JSON and must be parsed as JSON. If, for some reason (e.g. the server is hijacked or bogus), the MIME type in the server response is set to `text/javascript` (for JavaScript source), then the file would be parsed and executed as code. If the "JSON" file actually contains malicious code, the `import` declaration would unintentionally execute external code, posing a serious security threat.
+Modules are identified and parsed only according to their served [MIME type](/en-US/docs/Web/HTTP/MIME_types) — the file extension in the URL cannot be used to identify a file's type. In this case, the MIME type is `application/json`, which tells the browser that the file is JSON and must be parsed as JSON. If, for some reason (e.g. the server is hijacked or bogus), the MIME type in the server response is set to `text/javascript` (for JavaScript source), then the file would be parsed and executed as code. If the "JSON" file actually contains malicious code, the `import` declaration would unintentionally execute external code, posing a serious security threat.
 
 Import attributes fix this problem by allowing the author to explicitly specify how a module should be validated. For example, the import statement above, which lacks an attribute, would actually fail:
 
diff --git a/files/en-us/web/manifest/file_handlers/index.md b/files/en-us/web/manifest/file_handlers/index.md
index e876d3fe49b4419..ada17f781bf8900 100644
--- a/files/en-us/web/manifest/file_handlers/index.md
+++ b/files/en-us/web/manifest/file_handlers/index.md
@@ -13,7 +13,7 @@ The `file_handlers` member specifies an array of objects representing the types
 
 The `file_handlers` member is read by the browser when the PWA is installed and used to associate the application with a given set of file types at the operating system level.
 
-For example, a PWA can be registered to handle files that match the `text/plain` [MIME type](/en-US/docs/Web/HTTP/Basics_of_HTTP/MIME_types/Common_types). Once this PWA is installed, the operating system is able to use it to handle text files, opening the PWA when the user opens a file of this type. Note that other applications may also be registered as text file handlers, and the way operating systems manage the association between file types and applications, and the way they let users choose an application to handle a given file can vary from one device to another.
+For example, a PWA can be registered to handle files that match the `text/plain` [MIME type](/en-US/docs/Web/HTTP/MIME_types/Common_types). Once this PWA is installed, the operating system is able to use it to handle text files, opening the PWA when the user opens a file of this type. Note that other applications may also be registered as text file handlers, and the way operating systems manage the association between file types and applications, and the way they let users choose an application to handle a given file can vary from one device to another.
 
 > [!NOTE]
 > While the `file_handlers` member is used to register a PWA with a given set of file types, this only results in the operating system launching the PWA when a matching file is opened. The PWA then needs to actually handle the file using JavaScript code. See [Handling the files](#handling_the_files) for more information.
diff --git a/files/en-us/web/progressive_web_apps/how_to/share_data_between_apps/index.md b/files/en-us/web/progressive_web_apps/how_to/share_data_between_apps/index.md
index 81b47092434f479..8c45e77e29ddb85 100644
--- a/files/en-us/web/progressive_web_apps/how_to/share_data_between_apps/index.md
+++ b/files/en-us/web/progressive_web_apps/how_to/share_data_between_apps/index.md
@@ -240,7 +240,7 @@ The following code snippet shows how a PWA can be configured to accept different
 }
 ```
 
-As this example shows, each file object in the `files` property must have a `name` property and an `accept` property. The `accept` property must specify the accepted [MIME types](/en-US/docs/Web/HTTP/Basics_of_HTTP/MIME_types) or file extensions.
+As this example shows, each file object in the `files` property must have a `name` property and an `accept` property. The `accept` property must specify the accepted [MIME types](/en-US/docs/Web/HTTP/MIME_types) or file extensions.
 
 When the app is selected by the user to handle a shared file (or files), the app is launched with a `POST` request at the `/share-file-handler` URL, with encoded form data.
 
diff --git a/files/en-us/web/security/index.md b/files/en-us/web/security/index.md
index 53ed9e3b676c3c9..bdde4c47a07cb0a 100644
--- a/files/en-us/web/security/index.md
+++ b/files/en-us/web/security/index.md
@@ -136,7 +136,7 @@ Related topics:
 - [HTTP Access-Control-Allow-Origin](/en-US/docs/Web/HTTP/Headers/Access-Control-Allow-Origin)
   - : The **`Access-Control-Allow-Origin`** response header indicates whether the response can be shared with requesting code from the given {{glossary("origin")}}.
 - [HTTP X-Content-Type-Options](/en-US/docs/Web/HTTP/Headers/X-Content-Type-Options)
-  - : The **`X-Content-Type-Options`** response 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 must be followed. This header 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 specify that the MIME types are deliberately configured.
+  - : The **`X-Content-Type-Options`** response header is a marker used by the server to indicate that the [MIME types](/en-US/docs/Web/HTTP/MIME_types) advertised in the {{HTTPHeader("Content-Type")}} headers should not be changed and must be followed. This header is a way to opt out of [MIME type sniffing](/en-US/docs/Web/HTTP/MIME_types#mime_sniffing), or, in other words, to specify that the MIME types are deliberately configured.
 
 ### Sanitize form input
 
diff --git a/files/en-us/web/security/practical_implementation_guides/mime_types/index.md b/files/en-us/web/security/practical_implementation_guides/mime_types/index.md
index a09a8caf398b5a6..a398f5a7489521c 100644
--- a/files/en-us/web/security/practical_implementation_guides/mime_types/index.md
+++ b/files/en-us/web/security/practical_implementation_guides/mime_types/index.md
@@ -19,7 +19,7 @@ All sites must set the `X-Content-Type-Options` header with a value of `nosniff`
 `nosniff` blocks a request if the request destination:
 
 - is of type `style` and the MIME type is not `text/css`.
-- is of type `script` and the MIME type is not a valid [JavaScript MIME type](/en-US/docs/Web/HTTP/Basics_of_HTTP/MIME_types#textjavascript).
+- is of type `script` and the MIME type is not a valid [JavaScript MIME type](/en-US/docs/Web/HTTP/MIME_types#textjavascript).
 
 ## Examples
 
@@ -31,5 +31,5 @@ X-Content-Type-Options: nosniff
 
 ## See also
 
-- [MIME types (IANA media types): MIME sniffing](/en-US/docs/Web/HTTP/Basics_of_HTTP/MIME_types#mime_sniffing)
+- [MIME types (IANA media types): MIME sniffing](/en-US/docs/Web/HTTP/MIME_types#mime_sniffing)
 - [Properly configuring server MIME types](/en-US/docs/Learn/Server-side/Configuring_server_MIME_types)
diff --git a/files/en-us/web/uri/schemes/data/index.md b/files/en-us/web/uri/schemes/data/index.md
index 92175c9b38ac26d..5c30491403eea80 100644
--- a/files/en-us/web/uri/schemes/data/index.md
+++ b/files/en-us/web/uri/schemes/data/index.md
@@ -14,17 +14,17 @@ browser-compat: http.data-url
 
 ## Syntax
 
-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:
+Data URLs are composed of four parts: a prefix (`data:`), a [MIME type](/en-US/docs/Web/HTTP/MIME_types) indicating the type of data, an optional `base64` token if non-textual, and the data itself:
 
 ```plain
 data:[<mediatype>][;base64],<data>
 ```
 
-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`
+The `mediatype` is a [MIME type](/en-US/docs/Web/HTTP/MIME_types) string, such as `'image/jpeg'` for a JPEG image file. If omitted, defaults to `text/plain;charset=US-ASCII`
 
 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 {{Glossary("Percent-encoding", "percent-encoded")}}.
 
-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).
+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/MIME_types) and [here](/en-US/docs/Web/HTTP/MIME_types/Common_types).
 
 A few examples: