From 783ffd9c1cf35421242e028a1b8743cf2b1918dd Mon Sep 17 00:00:00 2001
From: Joshua Chen <sidachen2003@gmail.com>
Date: Tue, 8 Oct 2024 01:47:21 -0400
Subject: [PATCH] Fix typos and pseudo-typos 5 (#36246)

* Fix typos and pseudo-typos 5

* Update index.md

Co-authored-by: Estelle Weyl <estelle@openwebdocs.org>

---------

Co-authored-by: Estelle Weyl <estelle@openwebdocs.org>
---
 files/en-us/web/events/index.md               |  2 +-
 .../challenge_solutions/index.md              |  8 ++--
 .../web/html/attributes/disabled/index.md     |  4 +-
 files/en-us/web/html/element/audio/index.md   |  2 +
 .../web/html/element/fencedframe/index.md     |  2 +-
 files/en-us/web/html/element/img/index.md     |  4 +-
 .../web/html/element/input/button/index.md    |  4 +-
 .../element/input/datetime-local/index.md     | 12 +++---
 files/en-us/web/html/element/input/index.md   |  2 +-
 .../web/html/element/input/search/index.md    |  2 +-
 .../web/html/element/input/submit/index.md    |  2 +-
 .../web/html/element/input/time/index.md      | 37 ++++++++++++-------
 .../en-us/web/html/element/input/url/index.md |  2 +-
 files/en-us/web/html/element/kbd/index.md     |  4 +-
 files/en-us/web/html/element/link/index.md    |  4 +-
 .../element/script/type/importmap/index.md    |  6 +--
 .../en-us/web/html/element/textarea/index.md  |  4 +-
 files/en-us/web/html/element/track/index.md   |  2 +-
 files/en-us/web/html/element/u/index.md       |  6 ++-
 .../web/html/global_attributes/lang/index.md  |  2 +-
 .../index.md                                  |  2 +-
 files/en-us/web/http/compression/index.md     |  4 +-
 files/en-us/web/http/cookies/index.md         |  8 ++--
 files/en-us/web/http/cors/errors/index.md     |  2 +-
 files/en-us/web/http/csp/index.md             |  4 +-
 .../en-us/web/http/evolution_of_http/index.md |  8 ++--
 .../web/http/headers/set-cookie/index.md      |  4 +-
 .../http/headers/user-agent/firefox/index.md  | 24 ++++++------
 .../web/http/headers/user-agent/index.md      |  8 ++--
 files/en-us/web/http/messages/index.md        |  2 +-
 files/en-us/web/http/methods/post/index.md    |  2 +-
 .../web/http/permissions_policy/index.md      |  2 +-
 .../index.md                                  |  8 ++--
 files/en-us/web/http/status/103/index.md      |  2 +-
 files/en-us/web/http/status/206/index.md      |  2 +-
 files/en-us/web/http/status/423/index.md      |  2 +-
 36 files changed, 104 insertions(+), 91 deletions(-)

diff --git a/files/en-us/web/events/index.md b/files/en-us/web/events/index.md
index 3033c721eaba4ea..0e62c11ff3ad2a4 100644
--- a/files/en-us/web/events/index.md
+++ b/files/en-us/web/events/index.md
@@ -487,7 +487,7 @@ This topic provides an index to the main _sorts_ of events you might be interest
           <a href="/en-US/docs/Web/API/MouseEvent">computer mouse</a>.
         </p>
         <p>
-          Used to notify when the mouse is clicked, doubleclicked, up and down
+          Used to notify when the mouse is clicked, double-clicked, up and down
           events, right-click, movement in and out of an element, text
           selection, etc.
         </p>
diff --git a/files/en-us/web/guide/css/getting_started/challenge_solutions/index.md b/files/en-us/web/guide/css/getting_started/challenge_solutions/index.md
index 245590ca200110f..9957718c1a59fa1 100644
--- a/files/en-us/web/guide/css/getting_started/challenge_solutions/index.md
+++ b/files/en-us/web/guide/css/getting_started/challenge_solutions/index.md
@@ -15,7 +15,7 @@ The challenges on page [Why use CSS](/en-US/docs/Learn/CSS/First_steps/How_CSS_w
 - Challenge
   - : Without looking up a reference, find five more color names that work in your stylesheet.
 - Solution
-  - : CSS supports common color names like `orange`, `yellow`, `blue`, `green`, or `black`. It also supports some more exotic color names like `chartreuse`, `fuschia`, or `burlywood`. See [CSS Color value](/en-US/docs/Web/CSS/color_value) for a complete list as well as other ways of specifying colors.
+  - : CSS supports common color names like `orange`, `yellow`, `blue`, `green`, or `black`. It also supports some more exotic color names like `chartreuse`, `fuchsia`, or `burlywood`. See [CSS Color value](/en-US/docs/Web/CSS/color_value) for a complete list as well as other ways of specifying colors.
 
 ## How CSS works
 
@@ -199,11 +199,11 @@ The challenges on page [Lists](/en-US/docs/Learn/CSS/Styling_text/Styling_lists)
     ```css
     /* numbered headings */
     body {
-      counter-reset: headnum;
+      counter-reset: head-num;
     }
     h3::before {
-      content: "(" counter(headnum, upper-latin) ") ";
-      counter-increment: headnum;
+      content: "(" counter(head-num, upper-latin) ") ";
+      counter-increment: head-num;
     }
     ```
 
diff --git a/files/en-us/web/html/attributes/disabled/index.md b/files/en-us/web/html/attributes/disabled/index.md
index c7541282b8b97ab..6c09f532a0e898c 100644
--- a/files/en-us/web/html/attributes/disabled/index.md
+++ b/files/en-us/web/html/attributes/disabled/index.md
@@ -64,12 +64,12 @@ When form controls are disabled, many browsers will display them in a lighter, g
   <legend>Checkboxes</legend>
   <p>
     <label>
-      <input type="checkbox" name="chbox" value="regular" /> Regular
+      <input type="checkbox" name="ch-box" value="regular" /> Regular
     </label>
   </p>
   <p>
     <label>
-      <input type="checkbox" name="chbox" value="disabled" disabled /> disabled
+      <input type="checkbox" name="ch-box" value="disabled" disabled /> disabled
     </label>
   </p>
 </fieldset>
diff --git a/files/en-us/web/html/element/audio/index.md b/files/en-us/web/html/element/audio/index.md
index 6347685ed8b2062..8317bcb483fcc08 100644
--- a/files/en-us/web/html/element/audio/index.md
+++ b/files/en-us/web/html/element/audio/index.md
@@ -319,6 +319,8 @@ The `<audio>` element doesn't directly support WebVTT. You will have to find a l
 
 In addition to spoken dialog, subtitles and transcripts should also identify music and sound effects that communicate important information. This includes emotion and tone. For example, in the WebVTT below, note the use of square brackets to provide tone and emotional insight to the viewer; this can help establish the mood otherwise provided using music, nonverbal sounds and crucial sound effects, and so forth.
 
+<!-- cSpell:ignore switchwatch Swisswatch -->
+
 ```plain
 1
 00:00:00 --> 00:00:45
diff --git a/files/en-us/web/html/element/fencedframe/index.md b/files/en-us/web/html/element/fencedframe/index.md
index 5aefb54bb8f28c7..c9c3d4e1b4fb1a9 100644
--- a/files/en-us/web/html/element/fencedframe/index.md
+++ b/files/en-us/web/html/element/fencedframe/index.md
@@ -13,7 +13,7 @@ The **`<fencedframe>`** [HTML](/en-US/docs/Web/HTML) element represents a nested
 
 - Communication is restricted between the `<fencedframe>` content and its embedding site.
 - A `<fencedframe>` can access cross-site data, but only in a very specific set of controlled circumstances that preserve user privacy.
-- A `<fencedframes>` cannot be manipulated or have its data accessed via regular scripting (for example reading or setting the source URL). `<fencedframe>` content can only be embedded via [specific APIs](/en-US/docs/Web/API/Fenced_frame_API#use_cases).
+- A `<fencedframe>` cannot be manipulated or have its data accessed via regular scripting (for example reading or setting the source URL). `<fencedframe>` content can only be embedded via [specific APIs](/en-US/docs/Web/API/Fenced_frame_API#use_cases).
 - A `<fencedframe>` cannot access the embedding context's DOM, nor can the embedding context access the `<fencedframe>`'s DOM.
 
 The `<fencedframe>` element is a type of `<iframe>` with more native privacy features built in. It addresses shortcomings of `<iframe>`s such as reliance on third-party cookies and other privacy risks. See [Fenced frame API](/en-US/docs/Web/API/Fenced_frame_API) for more details.
diff --git a/files/en-us/web/html/element/img/index.md b/files/en-us/web/html/element/img/index.md
index f316ec277af692b..218852461e48450 100644
--- a/files/en-us/web/html/element/img/index.md
+++ b/files/en-us/web/html/element/img/index.md
@@ -14,7 +14,7 @@ The **`<img>`** [HTML](/en-US/docs/Web/HTML) element embeds an image into the do
 The above example shows usage of the `<img>` element:
 
 - The `src` attribute is **required**, and contains the path to the image you want to embed.
-- The `alt` attribute holds a textual replacement for the image, which is mandatory and **incredibly useful** for accessibility — screen readers read the attribute value out to their users so they know what the image means. Alt text is also displayed on the page if the image can't be loaded for some reason: for example, network errors, content blocking, or linkrot.
+- The `alt` attribute holds a textual replacement for the image, which is mandatory and **incredibly useful** for accessibility — screen readers read the attribute value out to their users so they know what the image means. Alt text is also displayed on the page if the image can't be loaded for some reason: for example, network errors, content blocking, or link rot.
 
 There are many other attributes to achieve various purposes:
 
@@ -180,7 +180,7 @@ This element includes the [global attributes](/en-US/docs/Web/HTML/Global_attrib
     > Loading is only deferred when JavaScript is enabled. This is an anti-tracking measure, because if a user agent supported lazy loading when scripting is disabled, it would still be possible for a site to track a user's approximate scroll position throughout a session, by strategically placing images in a page's markup such that a server can track how many images are requested and when.
 
     > [!NOTE]
-    > Images with `loading` set to `lazy` will never be loaded if they do not intersect a visible part of an element, even if loading them would change that as unloaded images have a `width` and `height` of `0`. Putting `width` and `height` on lazyloaded images fixes this issue and is a best practice, [recommended by the specification](https://html.spec.whatwg.org/multipage/embedded-content.html#the-img-element). Doing so also helps prevent layout shifts.
+    > Images with `loading` set to `lazy` will never be loaded if they do not intersect a visible part of an element, even if loading them would change that as unloaded images have a `width` and `height` of `0`. Putting `width` and `height` on lazy-loaded images fixes this issue and is a best practice, [recommended by the specification](https://html.spec.whatwg.org/multipage/embedded-content.html#the-img-element). Doing so also helps prevent layout shifts.
 
 - `referrerpolicy`
 
diff --git a/files/en-us/web/html/element/input/button/index.md b/files/en-us/web/html/element/input/button/index.md
index 9114fa6b7fc6d53..e8e5a105e47c1b4 100644
--- a/files/en-us/web/html/element/input/button/index.md
+++ b/files/en-us/web/html/element/input/button/index.md
@@ -105,7 +105,7 @@ function updateButton() {
 {{EmbedLiveSample("Adding_keyboard_shortcuts_to_buttons", 650, 100)}}
 
 > [!NOTE]
-> The problem with the above example of course is that the user will not know what the access key is! In a real site, you'd have to provide this information in a way that doesn't interfere with the site design (for example by providing an easily accessible link that points to information on what the site accesskeys are).
+> The problem with the above example of course is that the user will not know what the access key is! In a real site, you'd have to provide this information in a way that doesn't interfere with the site design (for example by providing an easily accessible link that points to information on what the site access keys are).
 
 ### Disabling and enabling a button
 
@@ -249,7 +249,7 @@ function degToRad(degrees) {
   return (degrees * Math.PI) / 180;
 }
 
-// update sizepicker output value
+// update size picker output value
 
 sizePicker.oninput = () => {
   output.textContent = sizePicker.value;
diff --git a/files/en-us/web/html/element/input/datetime-local/index.md b/files/en-us/web/html/element/input/datetime-local/index.md
index 9dba3734c5769b3..fc5c4f73c592fdf 100644
--- a/files/en-us/web/html/element/input/datetime-local/index.md
+++ b/files/en-us/web/html/element/input/datetime-local/index.md
@@ -26,16 +26,16 @@ You can set a default value for the input by including a date and time inside th
 <input
   id="party"
   type="datetime-local"
-  name="partydate"
+  name="party-date"
   value="2017-06-01T08:30" />
 ```
 
 {{ EmbedLiveSample('Value', 600, 60) }}
 
-One thing to note is that the displayed date and time formats differ from the actual `value`; the displayed date and time are formatted according to the user's locale as reported by their operating system, whereas the date/time `value` is always formatted `YYYY-MM-DDTHH:mm`. When the above value is submitted to the server, for example, it will look like `partydate=2024-06-01T08:30`.
+One thing to note is that the displayed date and time formats differ from the actual `value`; the displayed date and time are formatted according to the user's locale as reported by their operating system, whereas the date/time `value` is always formatted `YYYY-MM-DDTHH:mm`. When the above value is submitted to the server, for example, it will look like `party-date=2024-06-01T08:30`.
 
 > [!NOTE]
-> Also bear in mind that if such data is submitted via HTTP [`GET`](/en-US/docs/Web/HTTP/Methods/GET), the colon character will need to be escaped for inclusion in the URL parameters, e.g. `partydate=2024-06-01T08%3A30`. See {{jsxref("Global_Objects/encodeURI", "encodeURI()")}} for one way to do this.
+> Also bear in mind that if such data is submitted via HTTP [`GET`](/en-US/docs/Web/HTTP/Methods/GET), the colon character will need to be escaped for inclusion in the URL parameters, e.g. `party-date=2024-06-01T08%3A30`. See {{jsxref("Global_Objects/encodeURI", "encodeURI()")}} for one way to do this.
 
 You can also get and set the date value in JavaScript using the {{domxref("HTMLInputElement")}} `value` property, for example:
 
@@ -123,7 +123,7 @@ Let's look at an example; here we've set minimum and maximum date/time values, a
     <input
       id="party"
       type="datetime-local"
-      name="partydate"
+      name="party-date"
       min="2017-06-01T08:30"
       max="2017-06-30T16:30"
       required />
@@ -179,7 +179,7 @@ The simplest use of `<input type="datetime-local">` involves a basic `<input>` a
 ```html
 <form>
   <label for="party">Enter a date and time for your party booking:</label>
-  <input id="party" type="datetime-local" name="partydate" />
+  <input id="party" type="datetime-local" name="party-date" />
 </form>
 ```
 
@@ -195,7 +195,7 @@ You can use the [`min`](/en-US/docs/Web/HTML/Element/input#min) and [`max`](/en-
   <input
     id="party"
     type="datetime-local"
-    name="partydate"
+    name="party-date"
     min="2024-06-01T08:30"
     max="2024-06-30T16:30" />
 </form>
diff --git a/files/en-us/web/html/element/input/index.md b/files/en-us/web/html/element/input/index.md
index 992dbcf18a66a41..b784612c02dfb6c 100644
--- a/files/en-us/web/html/element/input/index.md
+++ b/files/en-us/web/html/element/input/index.md
@@ -582,7 +582,7 @@ A few additional non-standard attributes are listed following the descriptions o
 
 - [`size`](/en-US/docs/Web/HTML/Attributes/size)
 
-  - : Valid for `email`, `password`, `tel`, `url`, and `text`, the `size` attribute specifies how much of the input is shown. Basically creates same result as setting CSS [`width`](/en-US/docs/Web/CSS/width) property with a few specialities. The actual unit of the value depends on the input type. For `password` and `text`, it is a number of characters (or `em` units) with a default value of `20`, and for others, it is pixels (or `px` units). CSS `width` takes precedence over the `size` attribute.
+  - : Valid for `email`, `password`, `tel`, `url`, and `text`, the `size` attribute specifies how much of the input is shown. Basically creates same result as setting CSS [`width`](/en-US/docs/Web/CSS/width) property with a few specialties. The actual unit of the value depends on the input type. For `password` and `text`, it is a number of characters (or `em` units) with a default value of `20`, and for others, it is pixels (or `px` units). CSS `width` takes precedence over the `size` attribute.
 
 - `src`
 
diff --git a/files/en-us/web/html/element/input/search/index.md b/files/en-us/web/html/element/input/search/index.md
index 365bc070046f946..90b610919a15bd3 100644
--- a/files/en-us/web/html/element/input/search/index.md
+++ b/files/en-us/web/html/element/input/search/index.md
@@ -135,7 +135,7 @@ This renders like so:
 
 {{EmbedLiveSample("Basic_example", 600, 40)}}
 
-`q` is the most common `name` given to search inputs, although it's not mandatory. When submitted, the data name/value pair sent to the server will be `q=searchterm`.
+`q` is the most common `name` given to search inputs, although it's not mandatory. When submitted, the data name/value pair sent to the server will be `q=searchTerm`.
 
 > [!NOTE]
 > You must remember to set a [`name`](/en-US/docs/Web/HTML/Element/input#name) for your input, otherwise nothing will be submitted.
diff --git a/files/en-us/web/html/element/input/submit/index.md b/files/en-us/web/html/element/input/submit/index.md
index 3b3ae02ee82ef7d..b23291bd4f6c417 100644
--- a/files/en-us/web/html/element/input/submit/index.md
+++ b/files/en-us/web/html/element/input/submit/index.md
@@ -120,7 +120,7 @@ This renders like so:
 
 Try entering some text into the text field, and then submitting the form.
 
-Upon submitting, the data name/value pair gets sent to the server. In this instance, the string will be `text=usertext`, where "usertext" is the text entered by the user, encoded to preserve special characters. Where and how the data is submitted depends on the configuration of the `<form>`; see [Sending form data](/en-US/docs/Learn/Forms/Sending_and_retrieving_form_data) for more details.
+Upon submitting, the data name/value pair gets sent to the server. In this instance, the string will be `text=user-text`, where "user-text" is the text entered by the user, encoded to preserve special characters. Where and how the data is submitted depends on the configuration of the `<form>`; see [Sending form data](/en-US/docs/Learn/Forms/Sending_and_retrieving_form_data) for more details.
 
 ### Adding a keyboard shortcut to a submit button
 
diff --git a/files/en-us/web/html/element/input/time/index.md b/files/en-us/web/html/element/input/time/index.md
index 27a68ee37ff3e45..d14a7e0c1ef1a06 100644
--- a/files/en-us/web/html/element/input/time/index.md
+++ b/files/en-us/web/html/element/input/time/index.md
@@ -18,8 +18,12 @@ While the control's user interface appearance is based on the browser and operat
 You can set a default value for the input by including a valid time in the [`value`](/en-US/docs/Web/HTML/Element/input#value) attribute when creating the `<input>` element, like so:
 
 ```html
-<label for="appt-time">Choose an appointment time: </label>
-<input id="appt-time" type="time" name="appt-time" value="13:30" />
+<label for="appointment-time">Choose an appointment time: </label>
+<input
+  id="appointment-time"
+  type="time"
+  name="appointment-time"
+  value="13:30" />
 ```
 
 {{ EmbedLiveSample('Setting_the_value_attribute', 600, 60) }}
@@ -118,8 +122,8 @@ The simplest use of `<input type="time">` involves a basic `<input>` and {{htmle
 
 ```html
 <form>
-  <label for="appt-time">Choose an appointment time: </label>
-  <input id="appt-time" type="time" name="appt-time" />
+  <label for="appointment-time">Choose an appointment time: </label>
+  <input id="appointment-time" type="time" name="appointment-time" />
 </form>
 ```
 
@@ -137,8 +141,8 @@ It takes an integer value defining the number of seconds you want to increment b
 
 ```html
 <form>
-  <label for="appt-time">Choose an appointment time: </label>
-  <input id="appt-time" type="time" name="appt-time" step="2" />
+  <label for="appointment-time">Choose an appointment time: </label>
+  <input id="appointment-time" type="time" name="appointment-time" step="2" />
 </form>
 ```
 
@@ -156,10 +160,15 @@ You can use the [`min`](/en-US/docs/Web/HTML/Element/input#min) and [`max`](/en-
 
 ```html
 <form>
-  <label for="appt-time">
+  <label for="appointment-time">
     Choose an appointment time (opening hours 12:00 to 18:00):
   </label>
-  <input id="appt-time" type="time" name="appt-time" min="12:00" max="18:00" />
+  <input
+    id="appointment-time"
+    type="time"
+    name="appointment-time"
+    min="12:00"
+    max="18:00" />
   <span class="validity"></span>
 </form>
 ```
@@ -226,13 +235,13 @@ Let's look at an example; here we've set minimum and maximum times, and also mad
 ```html
 <form>
   <div>
-    <label for="appt-time">
+    <label for="appointment-time">
       Choose an appointment time (opening hours 12:00 to 18:00):
     </label>
     <input
-      id="appt-time"
+      id="appointment-time"
       type="time"
-      name="appt-time"
+      name="appointment-time"
       min="12:00"
       max="18:00"
       required />
@@ -259,13 +268,13 @@ In this example, we create an interface element for choosing time using the nati
 
 ```html
 <form>
-  <label for="appt-time">
+  <label for="appointment-time">
     Choose an appointment time (opening hours 12:00 to 18:00):
   </label>
   <input
-    id="appt-time"
+    id="appointment-time"
     type="time"
-    name="appt-time"
+    name="appointment-time"
     min="12:00"
     max="18:00"
     required />
diff --git a/files/en-us/web/html/element/input/url/index.md b/files/en-us/web/html/element/input/url/index.md
index 244f4fb97920f90..c2cf25fdf3a0865 100644
--- a/files/en-us/web/html/element/input/url/index.md
+++ b/files/en-us/web/html/element/input/url/index.md
@@ -18,7 +18,7 @@ The input value is automatically validated to ensure that it's either empty or a
 The {{HTMLElement("input")}} element's [`value`](/en-US/docs/Web/HTML/Element/input#value) attribute contains a string that is automatically validated as conforming to URL syntax. More specifically, there are two possible value formats that will pass validation:
 
 1. An empty string ("") indicates the user did not enter a value or that the value was removed.
-2. A single properly-formed absolute URL. This doesn't necessarily mean the URL address exists, but it is at least formatted correctly. An entry matching `urlscheme://restofurl` can be valid, even if the `urlscheme` entered doesn't exist.
+2. A single properly-formed absolute URL. This doesn't necessarily mean the URL address exists, but it is at least formatted correctly. An entry matching `urlscheme://rest-of-url` can be valid, even if the `urlscheme` entered doesn't exist.
 
 See [Validation](#validation) for details on how URLs are validated to ensure that they're formatted properly.
 
diff --git a/files/en-us/web/html/element/kbd/index.md b/files/en-us/web/html/element/kbd/index.md
index d1945865797cc92..07a6f411a23413e 100644
--- a/files/en-us/web/html/element/kbd/index.md
+++ b/files/en-us/web/html/element/kbd/index.md
@@ -34,8 +34,8 @@ Other elements can be used in tandem with `<kbd>` to represent more specific sce
 
 ```html
 <p>
-  Use the command <kbd>help mycommand</kbd> to view documentation for the
-  command "mycommand".
+  Use the command <kbd>help my-command</kbd> to view documentation for the
+  command "my-command".
 </p>
 ```
 
diff --git a/files/en-us/web/html/element/link/index.md b/files/en-us/web/html/element/link/index.md
index d81bb884b0ac377..3e08ce30b55c411 100644
--- a/files/en-us/web/html/element/link/index.md
+++ b/files/en-us/web/html/element/link/index.md
@@ -218,9 +218,9 @@ This element includes the [global attributes](/en-US/docs/Web/HTML/Global_attrib
     Allowed values are specified by {{RFC(5646, "Tags for Identifying Languages (also known as BCP 47)")}}.
     Use this attribute only if the [`href`](/en-US/docs/Web/HTML/Element/a#href) attribute is present.
 - `imagesizes`
-  - : For `rel="preload"` and `as="image"` only, the `imagesizes` attribute is [a sizes attribute](https://html.spec.whatwg.org/multipage/images.html#sizes-attribute) that indicates to preload the appropriate resource used by an `img` element with corresponding values for its `srcset` and `sizes` attributes.
+  - : For `rel="preload"` and `as="image"` only, the `imagesizes` attribute has similar syntax and semantics as the [`sizes`](/en-US/docs/Web/HTML/Element/img#sizes) attribute that indicates to preload the appropriate resource used by an `img` element with corresponding values for its `srcset` and `sizes` attributes.
 - `imagesrcset`
-  - : For `rel="preload"` and `as="image"` only, the `imagesrcset` attribute is [a sourceset attribute](https://html.spec.whatwg.org/multipage/images.html#srcset-attribute) that indicates to preload the appropriate resource used by an `img` element with corresponding values for its `srcset` and `sizes` attributes.
+  - : For `rel="preload"` and `as="image"` only, the `imagesrcset` attribute has similar syntax and semantics as the [`srcset`](/en-US/docs/Web/HTML/Element/img#srcset) attribute that indicates to preload the appropriate resource used by an `img` element with corresponding values for its `srcset` and `sizes` attributes.
 - `integrity`
   - : Contains inline metadata — a base64-encoded cryptographic hash of the resource (file) you're telling the browser to fetch.
     The browser can use this to verify that the fetched resource has been delivered without unexpected manipulation.
diff --git a/files/en-us/web/html/element/script/type/importmap/index.md b/files/en-us/web/html/element/script/type/importmap/index.md
index 65a573fd362db66..4da7d9aa563d62a 100644
--- a/files/en-us/web/html/element/script/type/importmap/index.md
+++ b/files/en-us/web/html/element/script/type/importmap/index.md
@@ -86,7 +86,7 @@ Note that in this case the property and mapped path must both have a trailing fo
   {
     "imports": {
       "shapes/": "./module/shapes/",
-      "othershapes/": "https://example.com/modules/shapes/"
+      "other-shapes/": "https://example.com/modules/shapes/"
     }
   }
 </script>
@@ -125,7 +125,7 @@ You can use the `scopes` key to provide mappings that are only used if the scrip
 If the URL of the loading script matches the supplied path, the mapping associated with the scope will be used.
 This allows different versions of the module to be used depending on what code is doing the importing.
 
-For example, the map below will only use the scoped map if the loading module has a URL that includes the path: "/modules/customshapes/".
+For example, the map below will only use the scoped map if the loading module has a URL that includes the path: "/modules/custom-shapes/".
 
 ```html
 <script type="importmap">
@@ -134,7 +134,7 @@ For example, the map below will only use the scoped map if the loading module ha
       "square": "./module/shapes/square.js"
     },
     "scopes": {
-      "/modules/customshapes/": {
+      "/modules/custom-shapes/": {
         "square": "https://example.com/modules/shapes/square.js"
       }
     }
diff --git a/files/en-us/web/html/element/textarea/index.md b/files/en-us/web/html/element/textarea/index.md
index 72030cfa9a60338..95fd4c84fe9f152 100644
--- a/files/en-us/web/html/element/textarea/index.md
+++ b/files/en-us/web/html/element/textarea/index.md
@@ -199,7 +199,7 @@ textarea {
 > [!NOTE]
 > Placeholders should only be used to show an example of the type of data that should be entered into a form; they are _not_ a substitute for a proper {{HTMLElement("label")}} element tied to the input. See [`<input>` labels](/en-US/docs/Web/HTML/Element/input#labels) for a full explanation.
 
-### Disabled and readonly textareas
+### Disabled and readonly text areas
 
 This example shows two `<textarea>`s — one is [`readonly`](/en-US/docs/Web/HTML/Attributes/readonly) and one is [`disabled`](/en-US/docs/Web/HTML/Attributes/disabled).
 You cannot edit the contents of either element, but the `readonly` element is focusable and its value is submitted in forms.
@@ -224,7 +224,7 @@ textarea {
 
 #### Result
 
-{{EmbedLiveSample('disabled_and_readonly_textareas', '', '230')}}
+{{EmbedLiveSample('disabled_and_readonly_text_areas', '', '230')}}
 
 ## Technical summary
 
diff --git a/files/en-us/web/html/element/track/index.md b/files/en-us/web/html/element/track/index.md
index 0a45c9aac2aba6f..2f17687f59dd4fc 100644
--- a/files/en-us/web/html/element/track/index.md
+++ b/files/en-us/web/html/element/track/index.md
@@ -70,7 +70,7 @@ The underlying {{domxref("TextTrack")}}, indicated by the {{domxref("HTMLTrackEl
 If the track _is_ associated with a media element, using the `<track>` element as a child of the {{HTMLElement("audio")}} or {{HTMLElement("video")}} element, the `cuechange` event is also sent to the {{domxref("HTMLTrackElement")}}.
 
 ```js
-let textTrackElem = document.getElementById("texttrack");
+let textTrackElem = document.getElementById("text-track");
 
 textTrackElem.addEventListener("cuechange", (event) => {
   let cues = event.target.track.activeCues;
diff --git a/files/en-us/web/html/element/u/index.md b/files/en-us/web/html/element/u/index.md
index bed8514a30abd91..91cb9f9b34ba000 100644
--- a/files/en-us/web/html/element/u/index.md
+++ b/files/en-us/web/html/element/u/index.md
@@ -56,6 +56,8 @@ This example uses the `<u>` element and some CSS to display a paragraph which in
 
 #### HTML
 
+<!-- cSpell:ignore wrnogly -->
+
 ```html
 <p>This paragraph includes a <u class="spelling">wrnogly</u> spelled word.</p>
 ```
@@ -113,7 +115,7 @@ Book titles should be presented using the {{HTMLElement("cite")}} element instea
 ##### Using the cite element
 
 ```html
-<p>The class read <cite>Moby Dick</cite> in the first term.</p>
+<p>The class read <cite>Moby-Dick</cite> in the first term.</p>
 ```
 
 {{EmbedLiveSample("Using_the_cite_element", 650, 80)}}
@@ -123,7 +125,7 @@ Book titles should be presented using the {{HTMLElement("cite")}} element instea
 The default styling for the `<cite>` element renders the text in italics. You can override that using CSS:
 
 ```html
-<p>The class read <cite>Moby Dick</cite> in the first term.</p>
+<p>The class read <cite>Moby-Dick</cite> in the first term.</p>
 ```
 
 ```css
diff --git a/files/en-us/web/html/global_attributes/lang/index.md b/files/en-us/web/html/global_attributes/lang/index.md
index 5f7226751f04d34..f54cee2dfed0df9 100644
--- a/files/en-us/web/html/global_attributes/lang/index.md
+++ b/files/en-us/web/html/global_attributes/lang/index.md
@@ -31,7 +31,7 @@ A language tag is made of hyphen-separated _language subtags_, where each subtag
 - Script subtag
   - : Optional. This subtag defines the writing system used for the language, and is always 4 characters long, with the first letter capitalized. For example, French-in-Braille is `fr-Brai` and `ja-Kana` is Japanese written with the Katakana alphabet. If the language is written in a highly typical way, like English in the Latin alphabet, there is no need to use this subtag.
 - Region subtag
-  - : Optional. This subtag defines a dialect of the base language from a particular location, and is either 2 letters in ALLCAPS matching a country code, or 3 numbers matching a non-country area. For example, `es-ES` is for Spanish as spoken in Spain, and `es-013` is Spanish as spoken in Central America. "International Spanish" would just be `es`.
+  - : Optional. This subtag defines a dialect of the base language from a particular location and is either two upper-case letters matching a country code or three numbers matching a non-country area. For example, `es-ES` is for Spanish as spoken in Spain, and `es-013` is Spanish as spoken in Central America. "International Spanish" would just be `es`.
 
 The script subtag precedes the region subtag if both are present — `ru-Cyrl-BY` is Russian, written in the Cyrillic alphabet, as spoken in Belarus.
 
diff --git a/files/en-us/web/http/browser_detection_using_the_user_agent/index.md b/files/en-us/web/http/browser_detection_using_the_user_agent/index.md
index bd2c43c6686064e..7fc83f9e9ed0a6a 100644
--- a/files/en-us/web/http/browser_detection_using_the_user_agent/index.md
+++ b/files/en-us/web/http/browser_detection_using_the_user_agent/index.md
@@ -125,7 +125,7 @@ if (hasTouchScreen) {
 
 As for the screen size, use `window.innerWidth` and `window.addEventListener("resize", () => { /* Refresh screen size dependent things */ })`. What you want to do for screen size is not slash off information on smaller screens. That will only annoy people because it will force them to use the desktop version. Rather, try to have fewer columns of information in a longer page on smaller screens while having more columns with a shorter page on larger screen sizes. This effect can be easily achieved using CSS [flexboxes](/en-US/docs/Learn/CSS/CSS_layout/Flexbox), sometimes with [floats](/en-US/docs/Learn/CSS/CSS_layout/Floats) as a partial fallback.
 
-Also try to move less relevant/important information down to the bottom and group the page's content together meaningfully. Although it is off-topic, perhaps the following detailed example might give you insights and ideas that persuade you to forgo user agent sniffing. Let us imagine a page composed of boxes of information; each box is about a different feline breed or canine breed. Each box has an image, an overview, and a historical fun fact. The pictures are kept to a maximum reasonable size even on large screens. For the purposes of grouping the content meaningfully, all the cat boxes are separated from all the dog boxes such that the cat and dog boxes are not intermixed together. On a large screen, it saves space to have multiple columns to reduce the space wasted to the left and to the right of the pictures. The boxes can be separated into multiple columns via two equally fair method. From this point on, we shall assume that all the dog boxes are at the top of the source code, that all the cat boxes are at the bottom of the source code, and that all these boxes have the same parent element. There's a single instance of a dog box immediately above a cat box, of course. The first method uses horizontal [Flexboxes](/en-US/docs/Learn/CSS/CSS_layout/Flexbox) to group the content such that when the page is displayed to the end user, all the dogs boxes are at the top of the page and all the cat boxes are lower on the page. The second method uses a [Column](/en-US/docs/Web/CSS/Layout_cookbook/Column_layouts) layout and resents all the dogs to the left and all the cats to the right. Only in this particular scenario, it is appropriate to provide no fallback for the flexboxes/multicolumns, resulting in a single column of very wide boxes on old browsers. Also consider the following. If more people visit the webpage to see the cats, then it might be a good idea to put all the cats higher in the source code than the dogs so that more people can find what they are looking for faster on smaller screens where the content collapses down to one column.
+Also try to move less relevant/important information down to the bottom and group the page's content together meaningfully. Although it is off-topic, perhaps the following detailed example might give you insights and ideas that persuade you to forgo user agent sniffing. Let us imagine a page composed of boxes of information; each box is about a different feline breed or canine breed. Each box has an image, an overview, and a historical fun fact. The pictures are kept to a maximum reasonable size even on large screens. For the purposes of grouping the content meaningfully, all the cat boxes are separated from all the dog boxes such that the cat and dog boxes are not intermixed together. On a large screen, it saves space to have multiple columns to reduce the space wasted to the left and to the right of the pictures. The boxes can be separated into multiple columns via two equally fair method. From this point on, we shall assume that all the dog boxes are at the top of the source code, that all the cat boxes are at the bottom of the source code, and that all these boxes have the same parent element. There's a single instance of a dog box immediately above a cat box, of course. The first method uses horizontal [Flexboxes](/en-US/docs/Learn/CSS/CSS_layout/Flexbox) to group the content such that when the page is displayed to the end user, all the dogs boxes are at the top of the page and all the cat boxes are lower on the page. The second method uses a [Column](/en-US/docs/Web/CSS/Layout_cookbook/Column_layouts) layout and resents all the dogs to the left and all the cats to the right. Only in this particular scenario, it is appropriate to provide no fallback for the flexbox/multicolumn layouts, resulting in a single column of very wide boxes on old browsers. Also consider the following. If more people visit the webpage to see the cats, then it might be a good idea to put all the cats higher in the source code than the dogs so that more people can find what they are looking for faster on smaller screens where the content collapses down to one column.
 
 Next, always make your code dynamic.
 The user can flip their mobile device on its side, changing the width and height of the page.
diff --git a/files/en-us/web/http/compression/index.md b/files/en-us/web/http/compression/index.md
index 935fda412fe63b8..f3eb74111031ed4 100644
--- a/files/en-us/web/http/compression/index.md
+++ b/files/en-us/web/http/compression/index.md
@@ -18,7 +18,7 @@ In practice, web developers don't need to implement compression mechanisms, both
 
 Each data type has some redundancy, that is _wasted space_, in it. If text can typically have as much as 60% redundancy, this rate can be much higher for some other media like audio and video. Unlike text, these other media types use a lot of space to store their data and the need to optimize storage and regain space was apparent very early. Engineers designed the optimized compression algorithm used by file formats designed for this specific purpose. Compression algorithms used for files can be grouped into two broad categories:
 
-- _Loss-less compression_, where the compression-uncompression cycle doesn't alter the data that is recovered. It matches (byte to byte) with the original.
+- _Loss-less compression_, where the compression-decompression cycle doesn't alter the data that is recovered. It matches (byte to byte) with the original.
   For images, `gif` or `png` are using lossless compression.
 - _Lossy compression_, where the cycle alters the original data in a (hopefully) imperceptible way for the user.
   Video formats on the Web are lossy; the `jpeg` image format is also lossy.
@@ -127,7 +127,7 @@ sequenceDiagram
     Note over Node2: Compresses body and forwards message.
     Node2->>Node1: HTTP/1.1 200 OK<br/>Transfer-Encoding: br
 
-    Note over Node1: Uncompresses resource and returns message to Client.
+    Note over Node1: Decompresses resource and returns message to Client.
     Node1->>Client: HTTP/1.1 200 OK
 -->
 
diff --git a/files/en-us/web/http/cookies/index.md b/files/en-us/web/http/cookies/index.md
index 01144fc870134d0..a6f8a5205b51f4c 100644
--- a/files/en-us/web/http/cookies/index.md
+++ b/files/en-us/web/http/cookies/index.md
@@ -52,7 +52,7 @@ The following HTTP response instructs the receiving browser to store a pair of c
 ```http
 HTTP/2.0 200 OK
 Content-Type: text/html
-Set-Cookie: yummy_cookie=choco
+Set-Cookie: yummy_cookie=chocolate
 Set-Cookie: tasty_cookie=strawberry
 
 [page content]
@@ -66,7 +66,7 @@ When a new request is made, the browser usually sends previously stored cookies
 ```http
 GET /sample_page.html HTTP/2.0
 Host: www.example.org
-Cookie: yummy_cookie=choco; tasty_cookie=strawberry
+Cookie: yummy_cookie=chocolate; tasty_cookie=strawberry
 ```
 
 ### Removal: defining the lifetime of a cookie
@@ -109,7 +109,7 @@ There are several reasons why you might want to do this, for example if a user h
 In the browser, you can create new cookies via JavaScript using the {{domxref("Document.cookie")}} property, or the asynchronous {{domxref("Cookie_Store_API", "Cookie Store API", "", "nocode")}}. Note that all examples below use `Document.cookie`, as it is the most widely supported/established option.
 
 ```js
-document.cookie = "yummy_cookie=choco";
+document.cookie = "yummy_cookie=chocolate";
 document.cookie = "tasty_cookie=strawberry";
 ```
 
@@ -117,7 +117,7 @@ You can also access existing cookies and set new values for them, provided the [
 
 ```js
 console.log(document.cookie);
-// logs "yummy_cookie=choco; tasty_cookie=strawberry"
+// logs "yummy_cookie=chocolate; tasty_cookie=strawberry"
 
 document.cookie = "yummy_cookie=blueberry";
 
diff --git a/files/en-us/web/http/cors/errors/index.md b/files/en-us/web/http/cors/errors/index.md
index 04457b20b918eae..f02748a58559a1c 100644
--- a/files/en-us/web/http/cors/errors/index.md
+++ b/files/en-us/web/http/cors/errors/index.md
@@ -8,7 +8,7 @@ page-type: landing-page
 
 [Cross-Origin Resource Sharing](/en-US/docs/Web/HTTP/CORS) ({{Glossary("CORS")}}) is a standard that allows a server to relax the [same-origin policy](/en-US/docs/Web/Security/Same-origin_policy). This is used to explicitly allow some cross-origin requests while rejecting others. For example, if a site offers an embeddable service, it may be necessary to relax certain restrictions. Setting up such a CORS configuration isn't necessarily easy and may present some challenges. In these pages, we'll look into some common CORS error messages and how to resolve them.
 
-If the CORS configuration isn't set up correctly, the browser console will present an error like `"Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at $somesite"` indicating that the request was blocked due to violating the CORS security rules. This might not necessarily be a set-up mistake, though. It's possible that the request is in fact intentionally being disallowed by the user's web application and remote external service. However, If the endpoint is meant to be available, some debugging is needed to succeed.
+If the CORS configuration isn't set up correctly, the browser console will present an error like `"Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at [some site]"` indicating that the request was blocked due to violating the CORS security rules. This might not necessarily be a set-up mistake, though. It's possible that the request is in fact intentionally being disallowed by the user's web application and remote external service. However, If the endpoint is meant to be available, some debugging is needed to succeed.
 
 ## Identifying the issue
 
diff --git a/files/en-us/web/http/csp/index.md b/files/en-us/web/http/csp/index.md
index fb74d02de296ebe..7d5086943e0afac 100644
--- a/files/en-us/web/http/csp/index.md
+++ b/files/en-us/web/http/csp/index.md
@@ -101,14 +101,14 @@ A website administrator wants to allow users of a web application to include ima
 but to restrict audio or video media to trusted providers, and all scripts only to a specific server that hosts trusted code.
 
 ```http
-Content-Security-Policy: default-src 'self'; img-src *; media-src example.org example.net; script-src userscripts.example.com
+Content-Security-Policy: default-src 'self'; img-src *; media-src example.org example.net; script-src userscript.example.com
 ```
 
 Here, by default, content is only permitted from the document's origin, with the following exceptions:
 
 - Images may load from anywhere (note the "\*" wildcard).
 - Media is only allowed from example.org and example.net (and not from subdomains of those sites).
-- Executable script is only allowed from userscripts.example.com.
+- Executable script is only allowed from userscript.example.com.
 
 ### Example 4
 
diff --git a/files/en-us/web/http/evolution_of_http/index.md b/files/en-us/web/http/evolution_of_http/index.md
index 73a26d3e8ad4a1d..16e4a4b90701e6d 100644
--- a/files/en-us/web/http/evolution_of_http/index.md
+++ b/files/en-us/web/http/evolution_of_http/index.md
@@ -26,7 +26,7 @@ The HTTP protocol used in those early phases was very simple. It was later dubbe
 The initial version of HTTP had no version number; it was later called 0.9 to differentiate it from later versions. HTTP/0.9 was extremely simple: requests consisted of a single line and started with the only possible method {{HTTPMethod("GET")}} followed by the path to the resource. The full URL wasn't included as the protocol, server, and port weren't necessary once connected to the server.
 
 ```http
-GET /mypage.html
+GET /my-page.html
 ```
 
 The response was extremely simple, too: it only consisted of the file itself.
@@ -51,7 +51,7 @@ HTTP/0.9 was very limited, but browsers and servers quickly made it more versati
 At this point in time, a typical request and response looked like this:
 
 ```http
-GET /mypage.html HTTP/1.0
+GET /my-page.html HTTP/1.0
 User-Agent: NCSA_Mosaic/2.0 (Windows 3.1)
 
 HTTP/1.0 200 OK
@@ -60,14 +60,14 @@ Server: CERN/3.0 libwww/2.17
 Content-Type: text/html
 <HTML>
 A page with an image
-  <IMG SRC="/myimage.gif">
+  <IMG SRC="/my-image.gif">
 </HTML>
 ```
 
 It was followed by a second connection and a request to fetch the image (with the corresponding response):
 
 ```http
-GET /myimage.gif HTTP/1.0
+GET /my-image.gif HTTP/1.0
 User-Agent: NCSA_Mosaic/2.0 (Windows 3.1)
 
 HTTP/1.0 200 OK
diff --git a/files/en-us/web/http/headers/set-cookie/index.md b/files/en-us/web/http/headers/set-cookie/index.md
index aff75bbb0b5e399..9896d2554904dcb 100644
--- a/files/en-us/web/http/headers/set-cookie/index.md
+++ b/files/en-us/web/http/headers/set-cookie/index.md
@@ -197,10 +197,10 @@ Set-Cookie: id=a3fWa; Max-Age=2592000
 
 A cookie for a domain that does not include the server that set it [should be rejected by the user agent](https://datatracker.ietf.org/doc/html/rfc6265#section-4.1.2.3).
 
-The following cookie will be rejected if set by a server hosted on `originalcompany.com`:
+The following cookie will be rejected if set by a server hosted on `original-company.com`:
 
 ```http
-Set-Cookie: qwerty=219ffwef9w0f; Domain=somecompany.co.uk
+Set-Cookie: qwerty=219ffwef9w0f; Domain=some-company.co.uk
 ```
 
 A cookie for a subdomain of the serving domain will be rejected.
diff --git a/files/en-us/web/http/headers/user-agent/firefox/index.md b/files/en-us/web/http/headers/user-agent/firefox/index.md
index 04abc796fabb4e6..62d02b3f2e4cbec 100644
--- a/files/en-us/web/http/headers/user-agent/firefox/index.md
+++ b/files/en-us/web/http/headers/user-agent/firefox/index.md
@@ -12,27 +12,27 @@ This document describes the user agent string used in Firefox 4 and later and ap
 
 The UA string of Firefox itself is broken down into four components:
 
-`Mozilla/5.0 (platform; rv:geckoversion) Gecko/geckotrail Firefox/firefoxversion`
+`Mozilla/5.0 (platform; rv:gecko-version) Gecko/gecko-trail Firefox/firefox-version`
 
 - `Mozilla/5.0` is the general token that says the browser is Mozilla compatible, and is common to almost every browser today.
 - `platform` describes the native platform the browser is running on (e.g. Windows, Mac, Linux or Android), and whether or not it's a mobile phone. Firefox OS phones say `Mobile`; the web is the platform. Note that `platform` can consist of multiple `;`-separated tokens. See below for further details and examples.
 
-- `rv:geckoversion` indicates the release version of Gecko (such as `17.0`).
-- `Gecko/geckotrail` indicates that the browser is based on Gecko.
-- On Desktop, `geckotrail` is the fixed string `20100101`.
-- `Firefox/firefoxversion` indicates the browser is Firefox, and provides the version (such as `17.0`).
-- From Firefox 10 on mobile, `geckotrail` is the same as `firefoxversion`.
+- `rv:gecko-version` indicates the release version of Gecko (such as `17.0`).
+- `Gecko/gecko-trail` indicates that the browser is based on Gecko.
+- On Desktop, `gecko-trail` is the fixed string `20100101`.
+- `Firefox/firefox-version` indicates the browser is Firefox, and provides the version (such as `17.0`).
+- From Firefox 10 on mobile, `gecko-trail` is the same as `firefox-version`.
 
 > [!NOTE]
 > The recommended way of sniffing for Gecko-based browsers (if you _have to_ sniff for the browser engine instead of using feature detection) is by the presence of the `Gecko` and `rv:` strings, since some other browsers include a `like Gecko` token.
 
 For other products based on Gecko, the string can take one of two forms, where the tokens have the same meaning except those noted below:
 
-`Mozilla/5.0 (platform; rv:geckoversion) Gecko/geckotrail appname/appversion`
-`Mozilla/5.0 (platform; rv:geckoversion) Gecko/geckotrail Firefox/firefoxversion appname/appversion`
+`Mozilla/5.0 (platform; rv:gecko-version) Gecko/gecko-trail appname/appversion`
+`Mozilla/5.0 (platform; rv:gecko-version) Gecko/gecko-trail Firefox/firefox-version appname/appversion`
 
 - `appname/appversion` indicates the application name and version. For instance, this could be `Camino/2.1.1`, or `SeaMonkey/2.7.1`.
-- `Firefox/firefoxversion` is an optional compatibility token that some Gecko-based browsers may choose to incorporate, to achieve maximum compatibility with websites that expect Firefox. `firefoxversion` will generally represent the equivalent Firefox release corresponding to the given Gecko version. Some Gecko-based browsers may not opt into using this token; for this reason, sniffers should be looking for Gecko — not Firefox!
+- `Firefox/firefox-version` is an optional compatibility token that some Gecko-based browsers may choose to incorporate, to achieve maximum compatibility with websites that expect Firefox. `firefox-version` will generally represent the equivalent Firefox release corresponding to the given Gecko version. Some Gecko-based browsers may not opt into using this token; for this reason, sniffers should be looking for Gecko — not Firefox!
 
 ## Mobile and Tablet indicators
 
@@ -92,7 +92,7 @@ Firefox for Android contains the Android version as part of the _platform_ token
 From version 1, Focus is powered by Android WebView and uses the following user agent string format:
 
 ```plain
-Mozilla/5.0 (Linux; <Android Version> <Build Tag etc.>) AppleWebKit/<WebKit Rev> (KHTML, like Gecko) Version/4.0 Focus/<focusversion> Chrome/<Chrome Rev> Mobile Safari/<WebKit Rev>
+Mozilla/5.0 (Linux; <Android Version> <Build Tag etc.>) AppleWebKit/<WebKit Rev> (KHTML, like Gecko) Version/4.0 Focus/<focus version> Chrome/<Chrome Rev> Mobile Safari/<WebKit Rev>
 ```
 
 Tablet versions on WebView mirror mobile, but do not contain a `Mobile` token.
@@ -134,7 +134,7 @@ Note: this user agent was retrieved from an iPhone XR simulator and may be diffe
 Version 3 (and probably earlier) of Firefox for Fire TV use a user agent string with the following format:
 
 ```plain
-Mozilla/5.0 (Linux; <Android version>) AppleWebKit/537.36 (KHTML, like Gecko) Version/4.0 Focus/<firefoxversion> Chrome/<Chrome Rev> Safari/<WebKit Rev>
+Mozilla/5.0 (Linux; <Android version>) AppleWebKit/537.36 (KHTML, like Gecko) Version/4.0 Focus/<firefox-version> Chrome/<Chrome Rev> Safari/<WebKit Rev>
 ```
 
 | Firefox TV version | User Agent string                                                                                                                  |
@@ -146,7 +146,7 @@ Mozilla/5.0 (Linux; <Android version>) AppleWebKit/537.36 (KHTML, like Gecko) Ve
 From version 1.1, Firefox for Echo Show uses a user agent string with the following format:
 
 ```plain
-Mozilla/5.0 (Linux; <Android version>) AppleWebKit/537.36 (KHTML, like Gecko) Version/4.0 Focus/<firefoxversion> Chrome/<Chrome Rev> Safari/<WebKit Rev>
+Mozilla/5.0 (Linux; <Android version>) AppleWebKit/537.36 (KHTML, like Gecko) Version/4.0 Focus/<firefox-version> Chrome/<Chrome Rev> Safari/<WebKit Rev>
 ```
 
 | Firefox for Echo Show version | User agent string                                                                                                                  |
diff --git a/files/en-us/web/http/headers/user-agent/index.md b/files/en-us/web/http/headers/user-agent/index.md
index 9676edcbf342466..e84d5e7e49316e2 100644
--- a/files/en-us/web/http/headers/user-agent/index.md
+++ b/files/en-us/web/http/headers/user-agent/index.md
@@ -51,14 +51,14 @@ User-Agent: Mozilla/5.0 (<system-information>) <platform> (<platform-details>) <
 For more on Firefox- and Gecko-based user agent strings, see the [Firefox user agent string reference](/en-US/docs/Web/HTTP/Headers/User-Agent/Firefox). The UA string of Firefox is broken down into 4 components:
 
 ```plain
-Mozilla/5.0 (platform; rv:geckoversion) Gecko/geckotrail Firefox/firefoxversion
+Mozilla/5.0 (platform; rv:gecko-version) Gecko/gecko-trail Firefox/firefox-version
 ```
 
 1. `Mozilla/5.0` is the general token that says that the browser is Mozilla-compatible. For historical reasons, almost every browser today sends it.
 2. **_platform_** describes the native platform that the browser is running on (Windows, Mac, Linux, Android, etc.) and if it is a mobile phone. {{Glossary("Firefox OS")}} phones say `Mobile` — the web is the platform. Note that **_platform_** can consist of multiple `;`-separated tokens. See below for further details and examples.
-3. **rv:_geckoversion_** indicates the release version of Gecko (such as "_17.0_"). In recent browsers, **_geckoversion_** is the same as **_firefoxversion_**.
-4. **_Gecko/geckotrail_** indicates that the browser is based on Gecko. (On the desktop, **_geckotrail_** is always the fixed string `20100101`.)
-5. **_Firefox/firefoxversion_** indicates that the browser is Firefox and provides the version (such as "_17.0_").
+3. **rv:_gecko-version_** indicates the release version of Gecko (such as "_17.0_"). In recent browsers, **_gecko-version_** is the same as **_firefox-version_**.
+4. **_Gecko/gecko-trail_** indicates that the browser is based on Gecko. (On the desktop, **_gecko-trail_** is always the fixed string `20100101`.)
+5. **_Firefox/firefox-version_** indicates that the browser is Firefox and provides the version (such as "_17.0_").
 
 ### Examples
 
diff --git a/files/en-us/web/http/messages/index.md b/files/en-us/web/http/messages/index.md
index 103258f1bf3c2c4..42803ca635f944d 100644
--- a/files/en-us/web/http/messages/index.md
+++ b/files/en-us/web/http/messages/index.md
@@ -39,7 +39,7 @@ HTTP requests are messages sent by the client to initiate an action on the serve
      - `POST / HTTP/1.1`
      - `GET /background.png HTTP/1.0`
      - `HEAD /test.html?query=alibaba HTTP/1.1`
-     - `OPTIONS /anypage.html HTTP/1.0`
+     - `OPTIONS /any-page.html HTTP/1.0`
    - A complete URL, known as the _absolute form_, is mostly used with `GET` when connected to a proxy.
      `GET https://developer.mozilla.org/en-US/docs/Web/HTTP/Messages HTTP/1.1`
    - The authority component of a URL, consisting of the domain name and optionally the port (prefixed by a `':'`), is called the _authority form_. It is only used with `CONNECT` when setting up an HTTP tunnel.
diff --git a/files/en-us/web/http/methods/post/index.md b/files/en-us/web/http/methods/post/index.md
index 0579ec23d9a674b..6c28093eb0f6a72 100644
--- a/files/en-us/web/http/methods/post/index.md
+++ b/files/en-us/web/http/methods/post/index.md
@@ -16,7 +16,7 @@ Successive identical `POST` requests may have additional effects, such as creati
 For HTML forms the format/encoding of the body content is determined by the [`enctype`](/en-US/docs/Web/HTML/Element/form#enctype) attribute of the {{HTMLElement("form")}} element or the [`formenctype`](/en-US/docs/Web/HTML/Element/input#formenctype) attribute of the {{HTMLElement("input") }} or {{HTMLElement("button")}} elements.
 The encoding may be one of the following:
 
-- `application/x-www-form-urlencoded`: the keys and values are encoded in key-value tuples separated by an ampersand (`&`), with an equals symbol (`=`) between the key and the value (e.g., `firstname=Frida&lastname=Kahlo`).
+- `application/x-www-form-urlencoded`: the keys and values are encoded in key-value tuples separated by an ampersand (`&`), with an equals symbol (`=`) between the key and the value (e.g., `first-name=Frida&last-name=Kahlo`).
   Non-alphanumeric characters in both keys and values are {{Glossary("Percent-encoding", "percent-encoded")}}: this is the reason why this type is not suitable to use with binary data and you should use `multipart/form-data` for this purpose instead.
 - `multipart/form-data`: each value is sent as a block of data ("body part"), with a user agent-defined delimiter (for example, `boundary="delimiter12345"`) separating each part.
   The keys are described in the {{HTTPHeader("Content-Disposition")}} header of each part or block of data.
diff --git a/files/en-us/web/http/permissions_policy/index.md b/files/en-us/web/http/permissions_policy/index.md
index f21cd331eee52bc..17dd8b50d08f6b9 100644
--- a/files/en-us/web/http/permissions_policy/index.md
+++ b/files/en-us/web/http/permissions_policy/index.md
@@ -189,7 +189,7 @@ It is worth giving the `src` value a special mention. We mentioned above that us
 
 ### Fenced frames and permissions policy
 
-{{htmlelement("fencedframe")}}s interact with permissions policies in the same way as `<iframe>`s, but in a much more restricted capacity. Only specific features designed to be used in `<fencedframes>`s can be enabled via permissions policies set on them; other policy-controlled features are not available in this context.
+{{htmlelement("fencedframe")}}s interact with permissions policies in the same way as `<iframe>`s, but in a much more restricted capacity. Only specific features designed to be used in `<fencedframe>`s can be enabled via permissions policies set on them; other policy-controlled features are not available in this context.
 
 See [Permissions policies available to fenced frames](/en-US/docs/Web/HTML/Element/fencedframe#permissions_policies_available_to_fenced_frames) for more details.
 
diff --git a/files/en-us/web/http/proxy_servers_and_tunneling/proxy_auto-configuration_pac_file/index.md b/files/en-us/web/http/proxy_servers_and_tunneling/proxy_auto-configuration_pac_file/index.md
index 2a04e4a5973e11b..3ea63ab1183dcd9 100644
--- a/files/en-us/web/http/proxy_servers_and_tunneling/proxy_auto-configuration_pac_file/index.md
+++ b/files/en-us/web/http/proxy_servers_and_tunneling/proxy_auto-configuration_pac_file/index.md
@@ -175,14 +175,14 @@ dnsDomainIs("www", ".mozilla.org") // false
 #### Syntax
 
 ```js-nolint
-localHostOrDomainIs(host, hostdom)
+localHostOrDomainIs(host, hostDom)
 ```
 
 #### Parameters
 
 - host
   - : The hostname from the URL.
-- hostdom
+- hostDom
   - : Fully qualified hostname to match against.
 
 #### Description
@@ -344,14 +344,14 @@ dnsDomainLevels("www.mozilla.org"); // 2
 #### Syntax
 
 ```js-nolint
-shExpMatch(str, shexp)
+shExpMatch(str, shExp)
 ```
 
 #### Parameters
 
 - str
   - : is any string to compare (e.g. the URL, or the hostname).
-- shexp
+- shExp
   - : is a shell expression to compare against.
 
 Returns `true` if the string matches the specified shell glob expression.
diff --git a/files/en-us/web/http/status/103/index.md b/files/en-us/web/http/status/103/index.md
index 986e740d3a5edb5..c65dbeaacc1bcb7 100644
--- a/files/en-us/web/http/status/103/index.md
+++ b/files/en-us/web/http/status/103/index.md
@@ -57,7 +57,7 @@ Content-Type: text/html
 
 <!doctype html>
 ...
-<link rel="preload" href="https://cdn.example.com/fonts/myfont.woff2" as="font" type="font/woff2" crossorigin>
+<link rel="preload" href="https://cdn.example.com/fonts/my-font.woff2" as="font" type="font/woff2" crossorigin>
 ...
 <img src="https://cdn.example.com/images/image.jpg" alt="">
 ...
diff --git a/files/en-us/web/http/status/206/index.md b/files/en-us/web/http/status/206/index.md
index 270236e27b94d0b..7e9325f42bd381e 100644
--- a/files/en-us/web/http/status/206/index.md
+++ b/files/en-us/web/http/status/206/index.md
@@ -52,7 +52,7 @@ Following is a sample `206` response when two ranges of a PDF file are requested
 The response contains the `multipart/byteranges` {{HTTPHeader("Content-Type")}} with a separate {{HTTPHeader("Content-Type")}} (`application/pdf`) and {{HTTPHeader("Content-Range")}} for each range.
 
 ```http
-GET /pricelist.pdf HTTP/1.1
+GET /price-list.pdf HTTP/1.1
 Host: example.com
 Range: bytes=234-639,4590-7999
 ```
diff --git a/files/en-us/web/http/status/423/index.md b/files/en-us/web/http/status/423/index.md
index f1c2ac41451282b..77aa1c2f5b2fc94 100644
--- a/files/en-us/web/http/status/423/index.md
+++ b/files/en-us/web/http/status/423/index.md
@@ -32,7 +32,7 @@ Content-Length: xxxx
 <?xml version="1.0" encoding="utf-8" ?>
 <D:error xmlns:D="DAV:">
   <D:lock-token-submitted>
-    <D:href>/workspace/webdav/</D:href>
+    <D:href>/workspace/web-dav/</D:href>
   </D:lock-token-submitted>
 </D:error>
 ```