fix: auto-cleanup by bot (#42169)

* chore: auto-fix Markdownlint, Prettier, and front-matter issues

* Fix more

---------

Co-authored-by: Joshua Chen <[email protected]>

Author: mdn-bot

files/en-us/games/tutorials/2d_breakout_game_phaser/initialize_the_framework/index.md

@@ -74,7 +74,7 @@ The {{htmlelement("canvas")}} element is generated automatically by the framewor
 
 ## Running the application
 
-To run the app, you cannot directly open the `index.html` file, because later we will be loading external assets, which will be blocked by the browser's [same-origin policy](/en-US/docs/Web/Security/Same-origin_policy).
+To run the app, you cannot directly open the `index.html` file, because later we will be loading external assets, which will be blocked by the browser's [same-origin policy](/en-US/docs/Web/Security/Defenses/Same-origin_policy).
 
 To fix the problem, you need to run a local web server to serve the HTML files and the image files. [As the official document of Phaser suggests](https://docs.phaser.io/phaser/getting-started/set-up-dev-environment#installing-a-web-server), we have a lot of options to run a local web server. We also have our own [tutorials for setting up a local server](/en-US/docs/Learn_web_development/Howto/Tools_and_setup/set_up_a_local_testing_server)—use any option you prefer. For example, if you choose to use the Python HTTP server, then open a terminal, navigate to the directory where your `index.html` file is located, and run the following command:
 

files/en-us/glossary/cors/index.md

@@ -7,7 +7,7 @@ sidebar: glossarysidebar
 
 **CORS** (Cross-Origin Resource Sharing) is a system, consisting of transmitting {{Glossary("HTTP_header", "HTTP headers")}}, that determines whether browsers block frontend JavaScript code from accessing responses for cross-origin requests.
 
-The [same-origin security policy](/en-US/docs/Web/Security/Same-origin_policy) forbids cross-origin access to resources. But CORS gives web servers the ability to say they want to opt into allowing cross-origin access to their resources.
+The [same-origin security policy](/en-US/docs/Web/Security/Defenses/Same-origin_policy) forbids cross-origin access to resources. But CORS gives web servers the ability to say they want to opt into allowing cross-origin access to their resources.
 
 ## CORS headers
 

files/en-us/glossary/https/index.md

@@ -11,7 +11,7 @@ sidebar: glossarysidebar
 
 - [HTTPS](https://en.wikipedia.org/wiki/HTTPS) on Wikipedia
 - [Moving to HTTPS community guide](https://movingtohttps.com/)
-- [Secure Contexts](/en-US/docs/Web/Security/Secure_Contexts)
+- [Secure Contexts](/en-US/docs/Web/Security/Defenses/Secure_Contexts)
 - Related glossary terms:
   - {{glossary("HTTP")}}
   - {{glossary("TLS")}}

files/en-us/glossary/mitm/index.md

@@ -18,5 +18,4 @@ In physical mail and in online communication, MITM attacks are tough to defend.
 ## See also
 
 - OWASP: [Manipulator-in-the-middle attack](https://owasp.org/www-community/attacks/Manipulator-in-the-middle_attack)
-- PortSwigger: [Latest manipulator-in-the-middle attacks news](https://portswigger.net/daily-swig/mitm)
 - Wikipedia: [Man-in-the-middle attack](https://en.wikipedia.org/wiki/Man-in-the-middle_attack)

files/en-us/glossary/origin/index.md

@@ -53,7 +53,7 @@ These are not same origin because they use different ports:
 
 ## See also
 
-- [Same-origin policy](/en-US/docs/Web/Security/Same-origin_policy)
+- [Same-origin policy](/en-US/docs/Web/Security/Defenses/Same-origin_policy)
 - Related glossary terms:
   - {{Glossary("Site")}}
 - [HTML specification: origin](https://html.spec.whatwg.org/multipage/origin.html#origin)

files/en-us/glossary/same-origin_policy/index.md

@@ -5,13 +5,13 @@ page-type: glossary-definition
 sidebar: glossarysidebar
 ---
 
-The **[same-origin policy](/en-US/docs/Web/Security/Same-origin_policy)** is a critical security mechanism that restricts how a document or script loaded from one {{Glossary("origin")}} can interact with a resource from another origin.
+The **[same-origin policy](/en-US/docs/Web/Security/Defenses/Same-origin_policy)** is a critical security mechanism that restricts how a document or script loaded from one {{Glossary("origin")}} can interact with a resource from another origin.
 
 It helps isolate potentially malicious documents, reducing possible attack vectors.
 
 ## See also
 
-- [Same-origin policy](/en-US/docs/Web/Security/Same-origin_policy)
+- [Same-origin policy](/en-US/docs/Web/Security/Defenses/Same-origin_policy)
 - Related glossary terms:
   - {{Glossary("CORS")}}
   - {{Glossary("origin")}}

files/en-us/glossary/secure_context/index.md

@@ -7,4 +7,4 @@ sidebar: glossarysidebar
 
 A **secure context** is a `Window` or `Worker` in which certain minimum standards of authentication and confidentiality are met. Many Web APIs and features are only accessible in secure contexts, reducing the opportunity for misuse by malicious code.
 
-For more information see: [Web > Security > Secure Contexts](/en-US/docs/Web/Security/Secure_Contexts).
+For more information see: [Web > Security > Secure Contexts](/en-US/docs/Web/Security/Defenses/Secure_Contexts).

files/en-us/glossary/site/index.md

@@ -16,7 +16,7 @@ According to this definition, `support.mozilla.org` and `developer.mozilla.org`
 In some contexts, the scheme is also considered when differentiating sites. This would make `http://vpl.ca` and `https://vpl.ca` different sites. Including the scheme prevents an insecure (HTTP) site from being treated as the same site as a secure (HTTPS) site. A definition that considers the scheme is sometimes called a _schemeful same-site_. This stricter definition is applied in the rules for handling [`SameSite`](/en-US/docs/Web/HTTP/Reference/Headers/Set-Cookie#samesitesamesite-value) cookies.
 
 > [!NOTE]
-> Browsers sometimes make security decisions (for example, deciding which resources a script can access) based on the {{Glossary("Origin")}} of a resource. This is a more restrictive concept than the site, encompassing the scheme, the whole domain, and the port. See also [same-origin policy](/en-US/docs/Web/Security/Same-origin_policy).
+> Browsers sometimes make security decisions (for example, deciding which resources a script can access) based on the {{Glossary("Origin")}} of a resource. This is a more restrictive concept than the site, encompassing the scheme, the whole domain, and the port. See also [same-origin policy](/en-US/docs/Web/Security/Defenses/Same-origin_policy).
 
 ## Examples
 
@@ -45,4 +45,4 @@ These are the same site, or different sites if the scheme is considered:
 - [What is a URL](/en-US/docs/Learn_web_development/Howto/Web_mechanics/What_is_a_URL)
 - Related glossary terms:
   - {{Glossary("Origin")}}
-- [Same-origin policy](/en-US/docs/Web/Security/Same-origin_policy)
+- [Same-origin policy](/en-US/docs/Web/Security/Defenses/Same-origin_policy)

files/en-us/glossary/sri/index.md

@@ -9,4 +9,4 @@ sidebar: glossarysidebar
 
 ## See also
 
-- [Subresource Integrity](/en-US/docs/Web/Security/Subresource_Integrity)
+- [Subresource Integrity](/en-US/docs/Web/Security/Defenses/Subresource_Integrity)

files/en-us/glossary/ssl/index.md

@@ -10,7 +10,7 @@ Secure Sockets Layer, or SSL, was the old standard security technology for creat
 ## See also
 
 - [Transport Layer Security](https://en.wikipedia.org/wiki/Transport_Layer_Security) (Wikipedia)
-- [Transport Layer Security (TLS) protocol](/en-US/docs/Web/Security/Transport_Layer_Security)
+- [Transport Layer Security (TLS) protocol](/en-US/docs/Web/Security/Defenses/Transport_Layer_Security)
 - Related glossary terms:
   - {{Glossary("HTTPS")}}
   - {{Glossary("TLS")}}