[pull] main from mdn:main

files/en-us/web/css/reference/values/length/index.md

@@ -19,8 +19,19 @@ The `<length>` data type consists of a {{cssxref("&lt;number&gt;")}} followed by
 > [!NOTE]
 > Some properties allow negative `<length>` values, while others do not.
 
+### Specified vs. computed values
+
 The [specified value](/en-US/docs/Web/CSS/Guides/Cascade/Property_value_processing#specified_value) of a length (_specified length_) is represented by its quantity and unit. The [computed value](/en-US/docs/Web/CSS/Guides/Cascade/Property_value_processing#computed_value) of a length (_computed length_) is the specified length resolved to an absolute length, and its unit is not distinguished.
 
+For some properties, such as `border-width`, `outline-width`, `column-rule-width`, and `outline-offset`, the computed `<length>` values are rounded to an integer number of {{glossary("device pixel", "device pixels")}} to ensure reasonable visual display:
+
+- A non-zero value less than 1 device pixel is rounded up.
+- A value greater than 1 device pixel is rounded down to the nearest whole device pixel.
+
+For example, on a screen with a {{domxref("Window.devicePixelRatio", "devicePixelRatio")}} of 3, `border-width: 1.5px` computes to approximately `1.33px` (rounded down from 4.5 to 4 device pixels), and `outline-width: 0.2px` computes to approximately `0.33px` (rounded up from 0.6 to 1 device pixel).
+
+### Relative vs. absolute lengths
+
 The `<length>` units can be relative or absolute. Relative lengths represent a measurement in terms of some other distance. Depending on the unit, this distance can be the size of a specific character, the [line height](/en-US/docs/Web/CSS/Reference/Properties/line-height), or the size of the {{Glossary("viewport")}}. Style sheets that use relative length units can more easily scale from one output environment to another.
 
 > [!NOTE]

files/en-us/web/html/reference/elements/q/index.md

@@ -39,9 +39,9 @@ This element includes the [global attributes](/en-US/docs/Web/HTML/Reference/Glo
 ```html
 <p>
   According to Mozilla's website,
-  <q cite="https://www.mozilla.org/en-US/about/history/details/">
-    Firefox 1.0 was released in 2004 and became a big success.
-  </q>
+  <q cite="https://www.mozilla.org/en-US/about/history/details/"
+    >Firefox 1.0 was released in 2004 and became a big success.</q
+  >
 </p>
 ```
 

files/en-us/web/javascript/reference/global_objects/temporal/zoneddatetime/offsetnanoseconds/index.md

@@ -9,7 +9,7 @@ sidebar: jsref
 
 The **`offsetNanoseconds`** accessor property of {{jsxref("Temporal.ZonedDateTime")}} instances returns an integer representing the [offset](/en-US/docs/Web/JavaScript/Reference/Global_Objects/Temporal/ZonedDateTime#time_zones_and_offsets) used to interpret the internal instant, as a number of nanoseconds (positive or negative). The value is a safe integer because it's less than a day, which is 8.64e15 nanoseconds.
 
-The set accessor of `offsetNanoseconds` is `undefined`. You cannot change this property directly. Change {{jsxref("Temporal/ZonedDateTime/offset", "offset")}} to change this property too.
+The set accessor of `offsetNanoseconds` is `undefined`. You cannot change this property directly. Use the {{jsxref("Temporal/ZonedDateTime/with", "with()")}} method to create a new `Temporal.ZonedDateTime` object with the desired new {{jsxref("Temporal/ZonedDateTime/offset", "offset")}} value (which will change this property too), or use the {{jsxref("Temporal/ZonedDateTime/withTimeZone", "withTimeZone()")}} method to create a new `Temporal.ZonedDateTime` object in another time zone.
 
 ## Examples
 

package.json

@@ -71,7 +71,7 @@
     "imagemin-pngquant": "^10.0.0",
     "imagemin-svgo": "^12.0.0",
     "is-svg": "^6.1.0",
-    "lefthook": "^2.1.9",
+    "lefthook": "^2.1.10",
     "markdownlint-cli2": "0.23.0",
     "markdownlint-rule-search-replace": "1.2.0",
     "node-html-parser": "^9.0.0",