fix: auto-cleanup by bot (mdn#40803)

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

* Update index.md

* Fix lint

* Fix links

* Revert some

---------

Co-authored-by: Joshua Chen <sidachen2003@gmail.com>

Author: mdn-bot

files/en-us/learn_web_development/core/css_layout/multiple-column_layout/index.md

@@ -386,7 +386,7 @@ body {
   background-color: rgb(207 232 220);
   border: 2px solid rgb(79 185 227);
   padding: 10px;
-  margin: 0 0 1em 0;
+  margin-bottom: 1em;
 }
 ```
 
@@ -402,7 +402,7 @@ To control this behavior, we can use properties from the [CSS Fragmentation](/en
   background-color: rgb(207 232 220);
   border: 2px solid rgb(79 185 227);
   padding: 10px;
-  margin: 0 0 1em 0;
+  margin-bottom: 1em;
 }
 ```
 

files/en-us/learn_web_development/core/css_layout/practical_positioning_examples/index.md

@@ -162,7 +162,7 @@ Next, we'll style the buttons to look like tabs. Add the following CSS:
 
 ```css
 .info-box [role="tab"] {
-  padding: 0 1rem 0 1rem;
+  padding: 0 1rem;
   line-height: 3rem;
   background: white;
   color: #b60000;

files/en-us/learn_web_development/core/styling_basics/images_media_forms/index.md

@@ -235,7 +235,7 @@ label {
 input[type="text"],
 input[type="email"] {
   border: 2px solid black;
-  margin: 0 0 1em 0;
+  margin-bottom: 1em;
   padding: 10px;
   width: 80%;
 }

files/en-us/learn_web_development/core/styling_basics/test_your_skills/selectors/index.md

@@ -348,7 +348,7 @@ ul {
 }
 
 li {
-  margin: 0 0 0.5em 0;
+  margin-bottom: 0.5em;
 }
 
 a {

files/en-us/learn_web_development/extensions/forms/how_to_build_custom_form_controls/index.md

@@ -2032,7 +2032,7 @@ We'll do a little styling of the radio button list (not the legend/fieldset) to
 .styledSelect label {
   margin: 0;
   line-height: 2;
-  padding: 0 0 0 4px;
+  padding-left: 4px;
 }
 .styledSelect:not(:focus-within) input:not(:checked) + label {
   height: 0;

files/en-us/learn_web_development/extensions/forms/how_to_structure_a_web_form/example/index.md

@@ -148,7 +148,7 @@ input:focus {
 }
 
 button {
-  margin: 20px 0 0 0;
+  margin-top: 20px;
 }
 
 label {

files/en-us/learn_web_development/extensions/forms/how_to_structure_a_web_form/index.md

@@ -375,7 +375,7 @@ Let's put these ideas into practice and build a slightly more involved form —
    }
 
    button {
-     margin: 20px 0 0 0;
+     margin-top: 20px;
    }
 
    label {

files/en-us/mdn/community/community_participation_guidelines/index.md

@@ -88,7 +88,7 @@ MDN Community Management assesses the severity of the violation, applies the enf
 
 ### Appeals
 
-Once an incident has been investigated and a decision has been communicated to the relevant parties, all have the opportunity to appeal this decision by sending an email to mdn-cpg-report@mozilla.com. 
+Once an incident has been investigated and a decision has been communicated to the relevant parties, all have the opportunity to appeal this decision by sending an email to mdn-cpg-report@mozilla.com.
 Appeals are reviewed by a separate, impartial panel.
 
 ### Documentation and record keeping

files/en-us/mdn/writing_guidelines/howto/write_an_api_reference/information_contained_in_a_webidl_file/index.md

@@ -15,7 +15,7 @@ WebIDL can be found in multiple locations:
 
 - Each specification contains WebIDL inside the text: it is a very convenient way to convey precise definition. These describe the syntax of the API. Though the canonical reference, we have to keep in mind that they may differ from the actual implementation. On MDN we want to be practical and document what the Web platform really is, not what it ideally should be. So double check what is there with implementations (and don't hesitate to file bugs if you discover incoherence).
 - Three browser engines use (modified) WebIDL as part as their toolchain: Gecko, Chromium/Blink, and WebCore/WebKit. Pre-Chromium versions of Edge used it internally, but these are unfortunately not public.
-  - For Gecko, all WebIDL files are grouped in a single directory: <https://searchfox.org/mozilla-central/source/dom/webidl/>. Their extension is `.webidl`. There are other `*.idl` files in the Gecko source tree but they are not WebIDL, so you can ignore them. Older versions of Gecko have some of their WebIDL scattered around somewhat, and may even use Mozilla's IDL instead of WebIDL to describe some Web interfaces, but this won't be a problem in any recent Gecko code.
+  - For Gecko, all WebIDL files are grouped in a single directory: <https://searchfox.org/firefox-main/source/dom/webidl/>. Their extension is `.webidl`. There are other `*.idl` files in the Gecko source tree but they are not WebIDL, so you can ignore them. Older versions of Gecko have some of their WebIDL scattered around somewhat, and may even use Mozilla's IDL instead of WebIDL to describe some Web interfaces, but this won't be a problem in any recent Gecko code.
   - For Chromium, they are located in two locations, both subtrees of the source code's [`renderer/`](https://source.chromium.org/chromium/chromium/src/+/main:third_party/blink/renderer/) directory: [`core/`](https://source.chromium.org/chromium/chromium/src/+/main:third_party/blink/renderer/core/) and [`modules/`](https://source.chromium.org/chromium/chromium/src/+/main:third_party/blink/renderer/modules/). Chromium source code has IDL files in other locations, but these are part of the testing system and not relevant to API implementations.
   - For WebCore, they are scattered around the source code, so you need to dig a bit more: E.g. <https://github.com/WebKit/webkit/blob/main/Source/WebCore/html/DOMTokenList.idl>
 

files/en-us/mozilla/add-ons/webextensions/user_interface/browser_styles/index.md

@@ -122,7 +122,7 @@ As `browser_style` is a deprecated in Manifest V3 you may want to remove support
 - Does the appearance of your extensions UI change?
   - If the appearance doesn't change, remove the key.
   - If the appearance changes, experiment to determine what dependency exist and add the relevant properties in the extension's stylesheet. The styles are most likely to cause layout changes are `box-sizing:`, `border-box`, and `display: flex`.
-    If you cannot identify the dependencies, include the content of [extension.css](https://searchfox.org/mozilla-central/source/browser/components/extensions/extension.css) with the extension and delete all parts that aren't relevant, usually the `body` and `body *` blocks as most extensions don't use the `browser-style` class.
+    If you cannot identify the dependencies, include the content of [extension.css](https://searchfox.org/firefox-main/source/browser/components/extensions/extension.css) with the extension and delete all parts that aren't relevant, usually the `body` and `body *` blocks as most extensions don't use the `browser-style` class.
 
 ## Firefox panel components (legacy)