Fix typos

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

@@ -18,7 +18,7 @@ Other elements get their accessible name from the content of associated elements
 
 For some elements, the accessible name comes from the element's attributes; for example, the `alt` attribute in the case of {{HTMLElement("img")}}. Given `<img src="grape.jpg" alt="banana"/>`, the image's accessible name is "banana."
 
-To create an association between visible content and an element or multiple text nodes and an element, the [`aria-labeledby`](/en-US/docs/Web/Accessibility/ARIA/Attributes/aria-labelledby) attribute can be used. If there is no visible text to associate with a UI element needing an accessible name, the [`aria-label`](/en-US/docs/Web/Accessibility/ARIA/Attributes/aria-label) attribute can be used. Names should not be added to elements marking up inline text, like {{HTMLElement("code")}}, {{HTMLElement("del")}}, and {{HTMLElement("mark")}}.
+To create an association between visible content and an element or multiple text nodes and an element, the [`aria-labelledby`](/en-US/docs/Web/Accessibility/ARIA/Attributes/aria-labelledby) attribute can be used. If there is no visible text to associate with a UI element needing an accessible name, the [`aria-label`](/en-US/docs/Web/Accessibility/ARIA/Attributes/aria-label) attribute can be used. Names should not be added to elements marking up inline text, like {{HTMLElement("code")}}, {{HTMLElement("del")}}, and {{HTMLElement("mark")}}.
 
 Many elements, such as sections of textual content, don't need an accessible name. All controls should have an accessible name. All images that convey information and aren't purely presentational do too.
 

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

@@ -6,7 +6,7 @@ page-type: glossary-definition
 
 {{GlossarySidebar}}
 
-In computing, especially in networking, **rate limiting** means controlling how many operations can be performed in a given amount of time, usually to avoid overloading the system and causing performance degredation. For example, a server might limit the number of requests it will accept from a single client in a given time period, which not only optimizes the server's overall performance but also mitigates attacks like {{glossary("DoS attack")}}.
+In computing, especially in networking, **rate limiting** means controlling how many operations can be performed in a given amount of time, usually to avoid overloading the system and causing performance degradation. For example, a server might limit the number of requests it will accept from a single client in a given time period, which not only optimizes the server's overall performance but also mitigates attacks like {{glossary("DoS attack")}}.
 
 Rate limiting is typically synonymous with {{glossary("throttle", "throttling")}}, although {{glossary("debounce", "debouncing")}} is another viable strategy which provides better semantics and user experience in certain cases.
 

files/en-us/learn/css/building_blocks/backgrounds_and_borders/index.md

@@ -260,7 +260,7 @@ The individual properties include the {{cssxref("border-width")}}, {{cssxref("bo
 }
 ```
 
-There are longhand properities for width, style, and color for each of the four sides:
+There are longhand properties for width, style, and color for each of the four sides:
 
 ```css
 .box {

files/en-us/learn/server-side/django/deployment/index.md

@@ -830,7 +830,7 @@ You can click the site URL (highlighted above) to open the site in a browser (it
 When the site is opened, at this point you'll see an error debug screen as shown below.
 This is a Django security error that is raised because our source code is not running on an "allowed host".
 
-![A detailed error page with a full traceback of an invalid HTTP_HOST header](site_error_dissallowed_host.png)
+![A detailed error page with a full traceback of an invalid HTTP_HOST header](site_error_disallowed_host.png)
 
 > [!NOTE]
 > This kind of debug information is very useful when you're getting set up, but is a security risk in a deployed site.

files/en-us/learn/tools_and_testing/understanding_client-side_tools/introducing_complete_toolchain/index.md

@@ -64,7 +64,7 @@ For our sample project, we'll be using a toolchain specifically designed to aid
 
 ## Checking prerequisites
 
-You should have most of the softwares already if you've been following along with the previous chapters. Here's what you should have before proceeding to the real setup steps. They only need to be done once and you don't need to repeat these again for future projects.
+You should have most of the software already if you've been following along with the previous chapters. Here's what you should have before proceeding to the real setup steps. They only need to be done once and you don't need to repeat these again for future projects.
 
 ### Creating a GitHub account
 

files/en-us/web/api/clipboard_api/index.md

@@ -27,7 +27,7 @@ The Clipboard API allows users to programmatically read and write text and other
 
 Events are fired as the result of {{domxref("Element/cut_event", "cut")}}, {{domxref("Element/copy_event", "copy")}}, and {{domxref("Element/paste_event", "paste")}} operations modifying the clipboard.
 The events have a default action, for example the `copy` action copies the current selection to the system clipboard by default.
-The default action can be overriden by the event handler — see each of the events for more information.
+The default action can be overridden by the event handler — see each of the events for more information.
 
 ## Interfaces
 

files/en-us/web/api/clipboarditem/clipboarditem/index.md

@@ -61,7 +61,7 @@ async function writeClipImg() {
       ]);
       console.log("Fetched image copied.");
     } else {
-      console.log("image png is not suported");
+      console.log("image png is not supported");
     }
   } catch (err) {
     console.error(err.name, err.message);

files/en-us/web/api/compute_pressure_api/index.md

@@ -64,7 +64,7 @@ The Compute Pressure API is [policy-controlled](/en-US/docs/Web/HTTP/Permissions
 The following interfaces are present in the Compute Pressure API and the API surface is similar to other observers, such as {{domxref("IntersectionObserver")}}, {{domxref("MutationObserver")}}, or {{domxref("PerformanceObserver")}}.
 
 - {{domxref("PressureObserver")}} {{experimental_inline}}
-  - : Notifies when the system's pressure changes for a specfied number of sources (e.g. the CPU) at a predefined sample interval.
+  - : Notifies when the system's pressure changes for a specified number of sources (e.g. the CPU) at a predefined sample interval.
 - {{domxref("PressureRecord")}}
   - : Describes the pressure trend at a specific moment of transition.
 

files/en-us/web/api/customstateset/index.md

@@ -485,7 +485,7 @@ Click the element to see a different border being applied as the state changes.
 
 {{EmbedLiveSample("Non-boolean internal states", "100%", 50)}}
 
-## Comptability with `<dashed-ident>` syntax
+## Comptibility with `<dashed-ident>` syntax
 
 Previously custom elements with custom states were selected using a `<dashed-ident>` instead of the [`:state()`](/en-US/docs/Web/CSS/:state) function.
 Browser versions that don't support `:state()` will throw an error when supplied with an ident that is not prefixed with the double dash.

files/en-us/web/api/element/innerhtml/index.md

@@ -17,7 +17,7 @@ To insert the HTML into the document rather than replace the contents of an elem
 The serialization of the DOM tree read from the property does not include {{glossary("shadow tree", "shadow roots")}} — if you want to get a HTML string that includes shadow roots, you must instead use the {{domxref("Element.getHTML()")}} or {{domxref("ShadowRoot.getHTML()")}} methods.
 Similarly, when setting element content using `innerHTML`, the HTML string is parsed into DOM elements that do not contain shadow roots.
 
-So for example [`<template>`](/en-US/docs/Web/HTML/Element/template) is parsed into as {{domxref("HTMLTemplateElement")}}, whether or not the [`shadowrootmode`](/en-US/docs/Web/HTML/Element/template#shadowrootmode) attribute is specfied
+So for example [`<template>`](/en-US/docs/Web/HTML/Element/template) is parsed into as {{domxref("HTMLTemplateElement")}}, whether or not the [`shadowrootmode`](/en-US/docs/Web/HTML/Element/template#shadowrootmode) attribute is specified
 In order to set an element's contents from an HTML string that includes declarative shadow roots, you must use either {{domxref("Element.setHTMLUnsafe()")}} or {{domxref("ShadowRoot.setHTMLUnsafe()")}}.
 
 ## Value

files/en-us/web/api/htmlbuttonelement/type/index.md

@@ -29,7 +29,7 @@ Its possible values are listed in the attribute's [button types](/en-US/docs/Web
 ### JavaScript
 
 ```js
-const buttonElement = document.querySelector("#buttton");
+const buttonElement = document.querySelector("#button");
 console.log(buttonElement.type); // "reset"
 ```
 

files/en-us/web/api/mediacapabilities/decodinginfo/index.md

@@ -186,7 +186,7 @@ All supported audio codecs report `powerEfficient` as true.
 
 ## Usage notes
 
-### Comparision with Navigator.requestMediaKeySystemAccess()
+### Comparison with Navigator.requestMediaKeySystemAccess()
 
 `decodingInfo()` and the {{domxref("Navigator.requestMediaKeySystemAccess()")}} method of the [Encrypted Media Extensions API](/en-US/docs/Web/API/Encrypted_Media_Extensions_API) reflect fundamentally different approaches for selecting a configuration for decoding encrypted media.
 

files/en-us/web/api/rtcrtptransceiver/setcodecpreferences/index.md

@@ -97,7 +97,7 @@ You can get the codecs supported for decoding data using the {{domxref("RTCRtpRe
 const availReceiveCodecs = transceiver.receiver.getCapabilities("video").codecs;
 ```
 
-To reorder the codecs array to our preferred order, we can use the sorting fuction below to sort on MIME type (this comes from [setCodecPreferences is now in all browsers!](https://blog.mozilla.org/webrtc/cross-browser-support-for-choosing-webrtc-codecs/) on blog.mozilla.org (2024)).
+To reorder the codecs array to our preferred order, we can use the sorting function below to sort on MIME type (this comes from [setCodecPreferences is now in all browsers!](https://blog.mozilla.org/webrtc/cross-browser-support-for-choosing-webrtc-codecs/) on blog.mozilla.org (2024)).
 
 ```js
 function sortByMimeTypes(codecs, preferredOrder) {

files/en-us/web/api/storage_api/storage_quotas_and_eviction_criteria/index.md

@@ -109,7 +109,7 @@ Like with Firefox, because this quota is calculated based on the hard drive tota
 
 Starting with macOS 14 and iOS 17, Safari allots up to around 20% of the total disk space for each origin. If the user has saved it as a web app on the Home Screen or the Dock, this limit is increased to up to 60% of the disk size. For privacy reasons, {{Glossary("Same-origin policy", "cross-origin")}} frames have a separate quota, amounting to roughly 1/10 of their parents.
 
-For instance, a macOS device with a 1 TiB drive will limit each origin to around 200 GiB. If the user stores a web app on its Dock, that will be alloted a greater limit of around 600 GiB.
+For instance, a macOS device with a 1 TiB drive will limit each origin to around 200 GiB. If the user stores a web app on its Dock, that will be allotted a greater limit of around 600 GiB.
 
 Like other browsers, the exact limits enforced by the quota may vary as to avoid fingerprinting. Additionally, Safari also enforces an overall quota that stored data across all origins cannot grow beyond: 80% of disk size for each browser and web app, and 15% of disk size for each non-browser app that displays web content. More info on Safari's storage policies can be found on the [Webkit blog](https://www.webkit.org/blog/14403/updates-to-storage-policy/).
 

files/en-us/web/api/webrtc_api/using_encoded_transforms/index.md

@@ -219,7 +219,7 @@ event.transformer.options.port.onmessage = (event) => {
 ### Triggering a key frame
 
 Raw video is rarely sent or stored because it consumes a lot of space and bandwidth to represent each frame as a complete image.
-Instead, codecs periodically generate a "key frame" that contains enough infomation to construct a full image, and between key frames sends "delta frames" that just include the changes since the last delta frame.
+Instead, codecs periodically generate a "key frame" that contains enough information to construct a full image, and between key frames sends "delta frames" that just include the changes since the last delta frame.
 While this is far more efficient that sending raw video, it means that in order to display the image associated with a particular delta frame, you need the last key frame and all subsequent delta frames.
 
 This can cause a delay for new users joining a WebRTC conference application, because they can't display video until they have received their first key frame.

files/en-us/web/api/websockets_api/using_websocketstream/index.md

@@ -209,7 +209,7 @@ wss.closed.then((result) => {
 });
 ```
 
-Finally, we add an event listener to the close button that closes the conenction using the `close()` method, with a code and custom reason. The function also disables the close button — we don't want users to press it once the connection is already closed.
+Finally, we add an event listener to the close button that closes the connection using the `close()` method, with a code and custom reason. The function also disables the close button — we don't want users to press it once the connection is already closed.
 
 ```js
 closeBtn.addEventListener("click", () => {

files/en-us/web/api/xrwebgllayer/fixedfoveation/index.md

@@ -18,7 +18,7 @@ It is most useful for low contrast textures, such as background images but less
 
 A number between 0 and 1.
 
-- The minium amount of foveation is indicated by 0 (full resolution).
+- The minimum amount of foveation is indicated by 0 (full resolution).
 - The maximum amount of foveation is indicated by 1 (the edges render at lower resolution).
 
 It's up to the user agent how to interpret the numbers in this range. When changing the foveation level, the effect will visible in the next {{domxref("XRFrame")}}.

files/en-us/web/css/@container/index.md

@@ -297,7 +297,7 @@ The following container query checks if the {{cssxref("computed_value")}} of the
 ```
 
 > [!NOTE]
-> If a custom property has a value of `blue`, the equivalent hexidecimal code `#0000ff` will not match unless the property has been defined as a color with {{cssxref("@property")}} so the browser can properly compare computed values.
+> If a custom property has a value of `blue`, the equivalent hexadecimal code `#0000ff` will not match unless the property has been defined as a color with {{cssxref("@property")}} so the browser can properly compare computed values.
 
 Style features that query a shorthand property are true if the computed values match for each of its longhand properties, and false otherwise. For example, `@container style(border: 2px solid red)` will resolve to true if all 12 longhand properties (`border-bottom-style`, etc.) that make up that shorthand are true.
 

files/en-us/web/css/@counter-style/range/index.md

@@ -54,7 +54,7 @@ The value of the `range` descriptor can be either `auto` or a comma separated li
 
 When the value is set to `auto`, the range is the default range for the counter system. If the `system` is `cyclic`, `numeric`, or `fixed`, the range will be from negative infinity to positive infinity. If the `system` is `alphabetic` or `symbolic`, the range will be from `1` to positive `infinity`. For `system: additive`, `auto` results in the range `0` to positive `infinity`.
 
-When extending a counter, if `range` is set to `auto`, the range value will be the range of the `system` of the counter that is being extended, not the `range` value, if any, of that counter. For example, if counter "B" has the `system: extends A` set, with counter being an `alphabetic` counter, setting `range: auto` on "B" sets the range of "B" from `1` to `infinity`. This is the range of the `alphabetic` system, not necessarily the range set in the "A" counter style definiton. With `range: auto` set on "B", the `range` is set to the default range of the `alphabetic` system, not the `range` value set in counter A's descriptor list.
+When extending a counter, if `range` is set to `auto`, the range value will be the range of the `system` of the counter that is being extended, not the `range` value, if any, of that counter. For example, if counter "B" has the `system: extends A` set, with counter being an `alphabetic` counter, setting `range: auto` on "B" sets the range of "B" from `1` to `infinity`. This is the range of the `alphabetic` system, not necessarily the range set in the "A" counter style definition. With `range: auto` set on "B", the `range` is set to the default range of the `alphabetic` system, not the `range` value set in counter A's descriptor list.
 
 ### `infinite` explained
 

files/en-us/web/css/bottom/index.md

@@ -60,7 +60,7 @@ bottom: unset;
   - : Specifies that:
 
     - for _absolutely positioned elements_, the position of the element is based on the {{Cssxref("top")}} property, while `height: auto` is treated as a height based on the content; or if `top` is also `auto`, the element is positioned where it should vertically be positioned if it were a static element.
-    - for _anchor positioned elements_, a percentage withing the {{cssxref("anchor()")}} function specifies the distance, as a percentage, from the start of the element's content along the block axis.
+    - for _anchor positioned elements_, a percentage within the {{cssxref("anchor()")}} function specifies the distance, as a percentage, from the start of the element's content along the block axis.
     - for _relatively positioned elements_, the distance of the element from its normal position is based on the {{Cssxref("top")}} property; or if `top` is also `auto`, the element is not moved vertically at all.
 
 - `inherit`

files/en-us/web/css/css_flexible_box_layout/mastering_wrapping_of_flex_items/index.md

@@ -87,5 +87,5 @@ If this causes a problem for your layout it may require a rethinking of the stru
 
 ### Using `visibility: hidden` and `display: none`
 
-In previous live example, try using `visibility: hidden` or `display: none` instead of `visiblity: collapse`. Using `visibility: hidden`, the item is made invisible but the box is kept in the formatting structure, so it still behaves as if it were part of the layout.
+In previous live example, try using `visibility: hidden` or `display: none` instead of `visibility: collapse`. Using `visibility: hidden`, the item is made invisible but the box is kept in the formatting structure, so it still behaves as if it were part of the layout.
 When you use `display: none`, the item is completely removed from the formatting structure. Not only is it invisible but the structure is removed as well. This means counters ignore it and things like transitions do not run.

files/en-us/web/css/position-try-fallbacks/index.md

@@ -104,7 +104,7 @@ Referred to as a `<try-tactic>` in the specification, the predefined values move
 A single position-try fallback option can include more than one `<try-tactic>` or `dashed-ident` options, or a combination of both by declaring them as a single space-separated option:
 
 - In the case of multiple predefined `<try-tactic>` options, their transformations are composed together.
-- In the case of declaring a predefined `<try-tactic>` and a `<dashed-ident>` named `@postion-try` option, the custom position option is applied first, then the `<try-tactic>` transformation is applied.
+- In the case of declaring a predefined `<try-tactic>` and a `<dashed-ident>` named `@position-try` option, the custom position option is applied first, then the `<try-tactic>` transformation is applied.
 
 `position-area` values cannot be combined like this.
 

files/en-us/web/css/quotes/index.md

@@ -11,7 +11,7 @@ The [CSS](/en-US/docs/Web/CSS) **`quotes`** property sets how the browser should
 
 {{EmbedInteractiveExample("pages/css/quotes.html")}}
 
-Browsers insert quotation marks at the opening and closing of `<q>` elements and for the `open-quote` and `close-quote` values of the `content` property. Each opening or closing quote is replaced by one of the strings from the value of `quotes`, based on the depth of nesting, or, if `quotes` is explicity set to or otherwise resolves to `auto`, the quotation marks used are language dependent.
+Browsers insert quotation marks at the opening and closing of `<q>` elements and for the `open-quote` and `close-quote` values of the `content` property. Each opening or closing quote is replaced by one of the strings from the value of `quotes`, based on the depth of nesting, or, if `quotes` is explicitly set to or otherwise resolves to `auto`, the quotation marks used are language dependent.
 
 ## Syntax
 

files/en-us/web/html/element/template/index.md

@@ -252,7 +252,7 @@ For the shadow root that does not have `shadowrootdelegatesfocus` set you can cl
 ![Screenshot of code with no focus set](template_with_no_focus.png)
 
 For the shadow root with `shadowrootdelegatesfocus` set, clicking on the text (which is non-focusable) selects the `<input>` element, as this is the first focusable element in the tree.
-This also focusses the parent element as shown below.
+This also focuses the parent element as shown below.
 
 ![Screenshot of the code where the element has focus](template_with_focus.png)
 

files/en-us/web/http/status/404/index.md

@@ -27,7 +27,7 @@ For more information, see the [Redirections in HTTP](/en-US/docs/Web/HTTP/Redire
 
 ### Page not found
 
-Fetching a non-existant page may look like the following request:
+Fetching a non-existent page may look like the following request:
 
 ```http
 GET /my-deleted-blog-post HTTP/1.1