[pull] main from mdn:main

files/en-us/mozilla/add-ons/webextensions/manifest.json/browser_specific_settings/index.md

@@ -95,8 +95,14 @@ The `gecko` sub-key supports these properties:
 
 - `strict_min_version`
   - : Minimum version of Gecko to support. If the Firefox version on which the extension is being installed or run is below this version, the extension is not installed or not run. If not provided, all versions earlier than `strict_max_version` are supported. "\*" is not valid in this field.
+    > [!NOTE]
+    > The minimum supported version capable of receiving updates is 115.0 (ESR) or, if ESR versions are not included, 128.0. This is due to the expiration of the root certificate in Firefox in March 2025. As a result, older versions of Firefox don't recognize extension signatures. See [Update Firefox to prevent add-ons issues from root certificate expiration](https://support.mozilla.org/en-US/kb/root-certificate-expiration) for more information.
 - `strict_max_version`
   - : Maximum version of Gecko to support. If the Firefox version on which the extension is being installed or run is above this version, the extension is not installed or not run. Defaults to "\*", which disables checking for a maximum version.
+
+    > [!CALLOUT]
+    > See the list of [valid Gecko versions](https://addons.mozilla.org/api/v5/applications/firefox/).
+
 - `update_url`
   - : A link to an [extension update manifest](https://extensionworkshop.com/documentation/manage/updating-your-extension/). Note that the link must begin with "https". This key is for managing extension updates yourself (i.e., not through AMO).
 
@@ -107,8 +113,6 @@ The `gecko_android` sub-key supports these properties:
 - `strict_max_version`
   - : Maximum version of Gecko to support on Android. If the Firefox version on which the extension is being installed or run is above this version, the extension is not installed or not run. Defaults to the version determined by `gecko.strict_max_version`.
 
-See the list of [valid Gecko versions](https://addons.mozilla.org/api/v5/applications/firefox/).
-
 To support Firefox for Android without specifying a version range, the `gecko_android` sub-key must be an empty object, i.e., `"gecko_android": {}`. Otherwise, the extension is only made available on desktop Firefox.
 
 #### Extension ID format

files/en-us/web/api/htmlimageelement/sizes/index.md

@@ -198,7 +198,7 @@ It also allows you to see the effect of changing the size of a container on the
 
 #### HTML
 
-The HTML is similar to that in the previous example, except that it defines three near-identical {{htmlelement("img")}} elements, each with a `scrset` indicating 3 images that are `600px`, `400px`, and `200px` wide, and with a `sizes` value of `auto`.
+The HTML is similar to that in the previous example, except that it defines three near-identical {{htmlelement("img")}} elements, each with a `srcset` indicating 3 images that are `600px`, `400px`, and `200px` wide, and with a `sizes` value of `auto`.
 These are constrained within containers that are sized to select the different images.
 
 ```html

files/en-us/web/security/threat_modeling/index.md

@@ -12,7 +12,7 @@ Depending on your goal, threat modeling can be more involved than described here
 This page describes the overall threat modeling process. For threat model frameworks and resources, see:
 
 - [Threat modeling frameworks and tools](/en-US/docs/Web/Security/Threat_modeling/Frameworks)
-  - : Overview of the STRIDE and LUNDDUN frameworks that provide structure for threat modeling processes, and additional threat modeling tools.
+  - : Overview of the STRIDE and LINDDUN frameworks that provide structure for threat modeling processes, and additional threat modeling tools.
 
 For an example threat model, see:
 
@@ -210,7 +210,7 @@ You can revisit the issues you filed and the documentation you've written in the
 
 We provide an [example threat model](/en-US/docs/Web/Security/Threat_modeling/Example_threat_model) for inspiration. Threat model documents don't get published very often and aren't shared broadly unfortunately; they are often an internal resource. Although it is good practice to publish your threat model, both to demonstrate trustworthiness and to solicit additional feedback.
 
-In our threat modeling above, we focus on the four key questions as defined in the [Threat Modeling Manifesto](https://www.threatmodelingmanifesto.org). Frameworks exist, including STRIDE and LUNDDUN, that provide structure for threat modeling processes. See the [threat modeling frameworks and resources](/en-US/docs/Web/Security/Threat_modeling/Frameworks) guide for a list of privacy and security threats, along with example questions that may help guide you in your own threat model development.
+In our threat modeling above, we focus on the four key questions as defined in the [Threat Modeling Manifesto](https://www.threatmodelingmanifesto.org). Frameworks exist, including STRIDE and LINDDUN, that provide structure for threat modeling processes. See the [threat modeling frameworks and resources](/en-US/docs/Web/Security/Threat_modeling/Frameworks) guide for a list of privacy and security threats, along with example questions that may help guide you in your own threat model development.
 
 ## See also
 

package.json

@@ -50,7 +50,7 @@
   },
   "devDependencies": {
     "@apideck/better-ajv-errors": "^0.3.7",
-    "@mdn/fred": "2.4.2",
+    "@mdn/fred": "2.4.3",
     "@octokit/rest": "^22.0.1",
     "ajv": "^8.18.0",
     "ajv-formats": "^3.0.1",