Fixed typos (#12308)

* fixed-typos

found the typos using my script
https://github.com/Uziel302/websites-spell-checker/blob/master/mdnversion

* another batch

* almost done

* done

Co-authored-by: Asaf M <[email protected]>

files/en-us/learn/accessibility/wai-aria_basics/index.md

@@ -79,7 +79,7 @@ The problem here is that visually they work, but screenreaders can't make any se
 
 An important point about WAI-ARIA attributes is that they don't affect anything about the web page, except for the information exposed by the browser's accessibility APIs (where screenreaders get their information from). WAI-ARIA doesn't affect webpage structure, the DOM, etc., although the attributes can be useful for selecting elements by CSS.
 
-> **Note:** You can find a useful list of all the ARIA roles and their uses, with links to futher information, in the WAI-ARIA spec — see [Definition of Roles](https://www.w3.org/TR/wai-aria-1.1/#role_definitions) — on on this site — see [ARIA roles](/en-US/docs/Web/accessibility/ARIA/roles).
+> **Note:** You can find a useful list of all the ARIA roles and their uses, with links to further information, in the WAI-ARIA spec — see [Definition of Roles](https://www.w3.org/TR/wai-aria-1.1/#role_definitions) — on on this site — see [ARIA roles](/en-US/docs/Web/accessibility/ARIA/roles).
 >
 > The spec also contains a list of all the properties and states, with links to further information — see [Definitions of States and Properties (all aria-\* attributes)](https://www.w3.org/TR/wai-aria-1.1/#state_prop_def).
 

files/en-us/learn/tools_and_testing/client-side_javascript_frameworks/vue_refs_focus_management/index.md

@@ -220,7 +220,7 @@ Inside `App.vue`, update your `<h2>` as follows:
  <h2 id="list-summary" ref="listSummary" tabindex="-1">\{{listSummary}}</h2>
 ```
 
-> **Note:** [`tabindex`](/en-US/docs/Web/HTML/Global_attributes/tabindex) is a really powerful tool for handling certian accessibility problems. However, it should be used with caution. Over-using `tabindex="-1"` can cause problems for all sorts of users, so only use it exactly where you need to. You should also almost never use `tabindex` > = `0`, as it can cause problems for users since it can make the DOM flow and the tab-order mismatch, and/or add non-interactive elements to the tab order. This can be confusing to users, especially those using screen readers and other assistive technology.
+> **Note:** [`tabindex`](/en-US/docs/Web/HTML/Global_attributes/tabindex) is a really powerful tool for handling certain accessibility problems. However, it should be used with caution. Over-using `tabindex="-1"` can cause problems for all sorts of users, so only use it exactly where you need to. You should also almost never use `tabindex` > = `0`, as it can cause problems for users since it can make the DOM flow and the tab-order mismatch, and/or add non-interactive elements to the tab order. This can be confusing to users, especially those using screen readers and other assistive technology.
 
 Now that we have a `ref` and have let browsers know that we can programmatically focus the `<h2>`, we need to set focus on it. At the end of `deleteToDo()`, use the `listSummary` ref to set focus on the `<h2>`. Since the `<h2>` is always rendered in the app, you do not need to worry about using `$nextTick` of lifecycle methods to handle focusing it.
 

files/en-us/mdn/contribute/changelog/index.md

@@ -37,7 +37,7 @@ Previously, the syntax blocks of JavaScript builtin and WebAPI methods that can
 
 This was problematic — many developers were confused by this, and it conflicts with valid syntax forms in other programming languages (e.g. `[]` is also an array in JavaScript).
 
-As a result, going forward we are now writing multiple syntax forms of a method on separate lines inside the syntax block. See [Syntax sections > Multiple lines/Optional paramaters](/en-US/docs/MDN/Structures/Syntax_sections#Multiple_lines) for further information and examples.
+As a result, going forward we are now writing multiple syntax forms of a method on separate lines inside the syntax block. See [Syntax sections > Multiple lines/Optional parameters](/en-US/docs/MDN/Structures/Syntax_sections#Multiple_lines) for further information and examples.
 
 ### Documenting mixins
 

files/en-us/mdn/guidelines/json_structured_data/index.md

@@ -71,7 +71,7 @@ An entry in `GroupData.json` has the following structure:
     > **Note:** The properties of the interfaces listed in `"interfaces"` **must** not be listed there. They are automatically added to the sidebar if the tag `Property` is in the YAML header on that page.
 * `"events"`
   * : This lists events of other interfaces that are part of the API. The values are the _title of the pages_ (that must reside under `Web/Events`)
-    > **Note:** The events targetting the interfaces listed in `"interfaces"` **must** not be listed there. They are automatically added to the sidebar if the tag `Event` (singular!) is in the YAML header on that page.
+    > **Note:** The events targeting the interfaces listed in `"interfaces"` **must** not be listed there. They are automatically added to the sidebar if the tag `Event` (singular!) is in the YAML header on that page.
 
 There are two other keys, `"dictionaries"` and `"callbacks"`, operating on the same principle. As we no longer document these entities in their own pages, their use is deprecated, and no new entry should be added to them (and we remove them little by little).
 

files/en-us/mdn/mdn_product_advisory_board/members/index.md

@@ -19,7 +19,7 @@ Current members of the MDN Product Advisory Board are:
   - : Daniel Appelquist leads the Web Developer Advocacy team at Samsung Internet <<https://samsunginter.net>>, Samsung's mobile and VR web browser. He has also been co-chair of the [W3C's Technical Architecture Group](https://w3.org/tag) since 2013. He has been working on the web for over 2 decades, first helping to create start-ups in the web publishing sphere and then (after moving to London from New York in '99) working on the convergence between web and mobile through many projects and initiatives. He has also led open standards strategy for the UK Government and remains a member of the [UK Government Open Standards Board](https://www.gov.uk/government/groups/open-standards-board). In between all this he's been an active community builder and event organizer.
 - **Sukriti Chadha**
   **Product Manager, Spotify**
-  - : Sukriti Chadha is a mobile developer-turned-product manager at Spotify where she leads efforts in cross-platform accessibility and developer experience on mobile. She also serves as an Invited Expert at the [W3C WCAG (Web Content Accessibility Guidelines) Working Group](https://www.w3.org/WAI/standards-guidelines/wcag/) and the [Mobile Accessibility Task Force (MATF)](https://www.w3.org/WAI/standards-guidelines/mobile/), where she contributes to industry guidelines for accessible web and mobile applications. She built a new way of making data visualization accessible for viusally impaired users, and [open-sourced the Android solution in 2019](https://developer.yahoo.com/blogs/612790529269366784/). Sukriti’s product role entails managing developer experience roadmaps, automated testing, and embedding accessibility in the product lifecycle.
+  - : Sukriti Chadha is a mobile developer-turned-product manager at Spotify where she leads efforts in cross-platform accessibility and developer experience on mobile. She also serves as an Invited Expert at the [W3C WCAG (Web Content Accessibility Guidelines) Working Group](https://www.w3.org/WAI/standards-guidelines/wcag/) and the [Mobile Accessibility Task Force (MATF)](https://www.w3.org/WAI/standards-guidelines/mobile/), where she contributes to industry guidelines for accessible web and mobile applications. She built a new way of making data visualization accessible for visually impaired users, and [open-sourced the Android solution in 2019](https://developer.yahoo.com/blogs/612790529269366784/). Sukriti’s product role entails managing developer experience roadmaps, automated testing, and embedding accessibility in the product lifecycle.
 - **Hermina Condei**
   **Head of Product CE, Marketing Operations, Mozilla**
   - : Hermina Condei leads product management and engineering for MDN Web Docs and platform engineering for SUMO, at Mozilla. Over the past years, she's driven company-wide projects focused on access and identity management for employees and community. She also led the product team in the Open Innovation Group**,** with a focus on managing internal and external stakeholders for the team's portfolio of projects.

files/en-us/mdn/structures/compatibility_tables/index.md

@@ -241,7 +241,7 @@ There is a fourth, optional, member that can go inside the `__compat` member —
 
 ### Sub-features
 
-In a page where the compat table has more than one row, you'll need multiple subfeatures inside each feature to define the information for each row. This can happen, for example, when you've got the basic support for a feature stored in one row, but then the feature also has a new property or value type that was addded much later in the specification's life and is only supported in a couple of browsers.
+In a page where the compat table has more than one row, you'll need multiple subfeatures inside each feature to define the information for each row. This can happen, for example, when you've got the basic support for a feature stored in one row, but then the feature also has a new property or value type that was added much later in the specification's life and is only supported in a couple of browsers.
 
 As an example, see the [compat data](https://github.com/mdn/browser-compat-data/blob/main/css/properties/background-color.json) and [corresponding MDN page](/en-US/docs/Web/CSS/background-color) for the `background-color` property. The basic support exists inside the `__compat` object as explained above, then you have an additional row for browsers' support for "alpha channel for hex values", which contains its own `__compat` object.
 

files/en-us/mozilla/firefox/releases/16/index.md

@@ -31,7 +31,7 @@ Firefox 16 shipped on October 9, 2012. This article lists key changes that are u
 - Support for the standard, unprefixed version of {{cssxref("calc()")}} has been landed ([bug 771678](https://bugzilla.mozilla.org/show_bug.cgi?id=771678)).
 - The {{cssxref("<resolution>")}} CSS data type has been extended to support the `dppx` ([bug 741644](https://bugzilla.mozilla.org/show_bug.cgi?id=741644)).
 - On screen, for [media queries](/en-US/docs/Web/CSS/Media_Queries/Using_media_queries), `dppx`, `dpi`, and `dpcm` are now representing values based on CSS pixels and no more with the physical units ([bug 771390](https://bugzilla.mozilla.org/show_bug.cgi?id=771390)).
-- Three new pseudo-classes `:-moz-meter-optimum`, `:-moz-meter-sub-optimum`, and `:-moz-meter-sub-sub-optimum` have been added for accessing/styling a {{HTMLElement("meter")}} element in a paraticular state ([bug 660238](https://bugzilla.mozilla.org/show_bug.cgi?id=660238)).
+- Three new pseudo-classes `:-moz-meter-optimum`, `:-moz-meter-sub-optimum`, and `:-moz-meter-sub-sub-optimum` have been added for accessing/styling a {{HTMLElement("meter")}} element in a particular state ([bug 660238](https://bugzilla.mozilla.org/show_bug.cgi?id=660238)).
 - The {{cssxref("appearance")}} property gains two new values: `meterbar` and `meterchunk`. They represent components inside the {{HTMLElement("meter")}} element ([bug 659999](https://bugzilla.mozilla.org/show_bug.cgi?id=659999)).
 - The {{cssxref("min-width")}} and {{cssxref("min-height")}} now supports the `auto` keyword for flex items (and resolves to `0` for other items) ({{bug("763689")}}).
 

files/en-us/mozilla/firefox/releases/33/index.md

@@ -70,7 +70,7 @@ For details please [see the hacks post](https://hacks.mozilla.org/2014/07/event-
 - The properties {{domxref("HTMLMediaElement.audioTracks")}} and {{domxref("HTMLMediaElement.videoTracks")}} have been experimentally implemented. They are controlled by the `media.track.enabled`, off by default ({{bug(744896)}}).
 - The non-standard `XMLHttpRequest.mozBackgroundRequest()` is no more accessible from Web sites. Only Firefox-internal code (Chrome code) can use it ({{bug(1035242)}}).
 - The {{event("touchenter")}} and {{event("touchleave")}} events, removed from the specification, have been removed ({{bug(1036444)}}).
-- The formely called `loaded` event, sent on a {{domxref("HTMLTrackElement")}} has been renamed {{event("load")}} to match the specification ({{bug(1035505)}}).
+- The formerly called `loaded` event, sent on a {{domxref("HTMLTrackElement")}} has been renamed {{event("load")}} to match the specification ({{bug(1035505)}}).
 - The IndexedDB interface `FileHandle` has been renamed in {{domxref("IDBMutableFile")}} ({{bug(1006485)}}).
 - The IndexedDB interface {{domxref("LockedFile")}} has been renamed in {{domxref("IDBFileHandle")}} ({{bug(1006485)}}).
 - The {{domxref("ServiceWorker")}} interface has been implemented, behind the `dom.serviceWorkers.enabled` flag ({{bug(903441)}}).

files/en-us/mozilla/firefox/releases/69/index.md

@@ -104,7 +104,7 @@ This article provides information about the changes in Firefox 69 that will af
 #### Media, Web Audio, and WebRTC
 
 - For improved user security, and in-keeping with the latest versions of the [Media Capture and Streams](/en-US/docs/Web/API/Media_Streams_API) specification, the {{domxref("navigator.mediaDevices")}} property is no longer present if the context is insecure. To use {{domxref("MediaDevices.getUserMedia", "getUserMedia()")}}, {{domxref("MediaDevices.getDisplayMedia", "getDisplayMedia()")}}, {{domxref("MediaDevices.enumerateDevices", "enumerateDevices()")}}, and so forth, be sure your content is loaded using {{Glossary("HTTPS")}} ({{bug(1528031)}}).
-- The Web Audio API's {{domxref("AudioParam.value")}} property now returns the actual value of the property at the current time, taking into account all scheduled or gradiated value changes. Previously, Firefox only returned the most recent explicitly-set value (as through using the `value` setter) ({{bug(893020)}}).
+- The Web Audio API's {{domxref("AudioParam.value")}} property now returns the actual value of the property at the current time, taking into account all scheduled or graduated value changes. Previously, Firefox only returned the most recent explicitly-set value (as through using the `value` setter) ({{bug(893020)}}).
 - We've updated {{domxref("MediaStreamAudioSourceNode")}} to use the new, lexicographical, ordering for tracks. Previously, track ordering was up to the individual browser, and could even change arbitrarily. In addition, attempting to create a `MediaStreamAudioSourceNode` using a stream that has no audio tracks now throws an `InvalidStateError` exception ({{bug(1553215)}}).
 - The {{domxref("MediaTrackSettings.facingMode", "facingMode")}}, {{domxref("MediaTrackSettings.deviceId", "deviceId")}}, and {{domxref("MediaTrackSettings.groupId", "groupId")}} settings are now included as members of the {{domxref("MediaTrackSettings")}} object returned by calls to {{domxref("MediaStreamTrack.getSettings()")}} ({{bug(1537986)}}).
 

files/en-us/mozilla/projects/nss/pkcs11/module_specs/index.html

@@ -87,7 +87,7 @@ <h3 id="NSS_Specific_Parameters_in_Module_Specs">NSS Specific Parameters in Modu
  <dt>trustOrder</dt>
  <dd>integer value specifying the order in which the trust information for certificates specified by tokens on this PKCS #11 library should be rolled up. A value of <kbd>0</kbd> means that tokens on this library should not supply trust information. The default trust order value is <kbd>50</kbd>. The relative order of two pkcs#11 libraries which have the same trustOrder value is undefined.</dd>
  <dt>cipherOrder</dt>
- <dd>integer value specifiying the order in which tokens are searched when looking for a token to do a generic operation (DES/Hashing, etc).</dd>
+ <dd>integer value specifying the order in which tokens are searched when looking for a token to do a generic operation (DES/Hashing, etc).</dd>
  <dt>ciphers</dt>
  <dd>comma separated list of ciphers this token will enable that isn't already enabled by the library (currently only <strong>FORTEZZA</strong> is defined) (case-insensitive).</dd>
  <dt>slotParams</dt>

files/en-us/mozilla/projects/nss/python_binding_for_nss/index.html

@@ -37,8 +37,8 @@ <h3 id="Design_Goals">Design Goals</h3>
  <li>NSS/NSPR objects whose collection elements can be referenced by name support associative indexing.</li>
  <li>NSS/NSPR objects which have "get" and "set" API function calls are exposed as Python properties.</li>
  <li>All NSS/NSPR Python objects can print their current value by evaluting the Python object in a string context or by using the Python str() function.</li>
- <li>Support threading. The Python Global Interpreter Lock (GIL) is released prior to calling NSS/NSPR C functions and reaquired after the NSS/NSPR C function returns. This allows other Python threads to execute during the time a NSS/NSPR function is progress in another thread. Also, any "global" values which are set in python-nss are actually thread-local. Examples of this are the various callbacks which can be set and their parameters. Thus each thread gets it own set of callbacks.</li>
- <li>Many methods/functions provide sane default (keyword) parameters freeing the Python programmer from having to specify all parameters yet allowing them to be overriden when necessary.</li>
+ <li>Support threading. The Python Global Interpreter Lock (GIL) is released prior to calling NSS/NSPR C functions and reacquired after the NSS/NSPR C function returns. This allows other Python threads to execute during the time a NSS/NSPR function is progress in another thread. Also, any "global" values which are set in python-nss are actually thread-local. Examples of this are the various callbacks which can be set and their parameters. Thus each thread gets it own set of callbacks.</li>
+ <li>Many methods/functions provide sane default (keyword) parameters freeing the Python programmer from having to specify all parameters yet allowing them to be overridden when necessary.</li>
  <li>Error codes are <em>never</em> returned from methods/functions. python-nss follows the existing Python exception mechanism. Any error reported by NSS/NSPR is converted into a Python exception and raised. The exact error code, error description, and often contextual error information will be present in the exception object.</li>
  <li>Enumerated constants used in the NSS/NSPR API's are available in the Python module under the <em>exact</em> same name as they appear in the C header files of NSS/NSPR.</li>
  <li>Convenience functions are provided to translate between the numeric value of an enumerated constant and it's string representation and visa versa.</li>
@@ -176,7 +176,7 @@ <h3 id="Release_1.0.0">Release 1.0.0</h3>
     <ul>
      <li>Allow custom include root in setup.py as command line arg.</li>
      <li>Add TLS chacha20 poly1305 constants.</li>
-     <li>Remove checks for whether a socket is open for reading. It's not possible for the binding to know in all cases, especially if the socket is created from an xternal socket passed in.</li>
+     <li>Remove checks for whether a socket is open for reading. It's not possible for the binding to know in all cases, especially if the socket is created from an external socket passed in.</li>
      <li>The following module functions were added:
       <ul>
        <li>nss.get_all_tokens</li>
@@ -622,7 +622,7 @@ <h3 id="Release_0.14.1">Release 0.14.1</h3>
       <p>Rewrite setup_certs.py, it was written like an expect script reacting to prompts read from a pseudo terminal but it was fragile and would hang on some systems. New version uses temporary password file and writes hardcoded responses to the stdin of certuil and modutil.</p>
      </li>
      <li>
-      <p>setup_certs now creates a new sql sytle NSS database (sql:pki)</p>
+      <p>setup_certs now creates a new sql style NSS database (sql:pki)</p>
      </li>
      <li>
       <p>All tests and examples now load the sql:pki database. Command line arg and variable changed from dbdir to db_name to reflect the database specification is no longer just a directory.</p>

files/en-us/mozilla/projects/nss/tools/nss_tools_dbck-tasks/index.html

@@ -10,7 +10,7 @@ <h2 id="NSS_Security_Tools_dbck_Tasks">NSS Security Tools: dbck Tasks</h2>
 <ol>
   <li>In analyze mode, there should be an option to create a file containing a graph of the certificate database without any information about the user's certificates (no common names, email addresses, etc.). This file could be mailed to a mail alias to assist in finding the source of database corruption.
   </li>
-  <li>The dbck tool should be able to repair a currupted database. There should be command-line options and, perhaps, an interactive mode to allow determine which certificates to keep.
+  <li>The dbck tool should be able to repair a corrupted database. There should be command-line options and, perhaps, an interactive mode to allow determine which certificates to keep.
   </li>
   <li>The dbck tool should be able to update a databa </li>
 </ol>