Spelling/grammar fixes (#33400)

* Fix typo `usoing` -> `using` * Spelling fix `misissuance` is uncountable. * Misspelling `Digicert` -> `DigiCert` * Fix typo `illegimitate` -> `illegitimate` * Fix typo `embeded` -> `embedded` * Spelling fixes `Kbps` -> `kbps` * Spelling fixes `Kbps` -> `kbps` * Fix typo `kbpz` -> `kbps` * Typo & spelling fixes `ffpmeg` -> `FFmpeg` `ffmpeg` -> `FFmpeg` * Fix typo `Bernouilli` -> `Bernoulli`
mdn · May 6, 2024 · 4d26c99 · 4d26c99
1 parent b25347d
commit 4d26c99
Show file tree

Hide file tree

Showing 9 changed files with 18 additions and 18 deletions.
diff --git a/files/en-us/web/mathml/examples/index.md b/files/en-us/web/mathml/examples/index.md
@@ -33,5 +33,5 @@ The following demos mix MathML with other Web technologies to produce advanced c
  - : A greek article about the Riemann zeta function, with [Web fonts](/en-US/docs/Learn/CSS/Styling_text/Web_fonts) from the [Greek Font Society](https://greekfontsociety-gfs.gr/).
 - [Pell's equation](https://people.igalia.com/fwang/pell-bigint-mathml/)
  - : A JavaScript program to solve Pell's equation using [`BigInt`](/en-US/docs/Web/JavaScript/Reference/Global_Objects/BigInt).
-- [Lovelace's program for Bernouilli numbers](https://people.igalia.com/fwang/lovelace-jsclass-mathml/)
- - : An emulator for Ada Lovelace's program to calculate Bernouilli numbers, using [Private properties](/en-US/docs/Web/JavaScript/Reference/Classes/Private_properties).
+- [Lovelace's program for Bernoulli numbers](https://people.igalia.com/fwang/lovelace-jsclass-mathml/)
+ - : An emulator for Ada Lovelace's program to calculate Bernoulli numbers, using [Private properties](/en-US/docs/Web/JavaScript/Reference/Classes/Private_properties).
diff --git a/files/en-us/web/media/dash_adaptive_streaming_for_html_5_video/index.md b/files/en-us/web/media/dash_adaptive_streaming_for_html_5_video/index.md
@@ -16,13 +16,13 @@ Firefox 23 removed support for DASH for HTML WebM video. It will be replaced by
 
 ## Using DASH - Server Side
 
-First you'll need to convert your WebM video to a DASH manifest with the accompanying video files in various bit rates. To start with you'll only need the ffpmeg program from [ffmpeg.org](https://www.ffmpeg.org/), with libvpx and libvorbis support for WebM video and audio, at least version 2.5 (probably; this was tested with 3.2.5).
+First you'll need to convert your WebM video to a DASH manifest with the accompanying video files in various bit rates. To start with you'll only need the FFmpeg program from [ffmpeg.org](https://www.ffmpeg.org/), with libvpx and libvorbis support for WebM video and audio, at least version 2.5 (probably; this was tested with 3.2.5).
 
 ### 1. Use your existing WebM file to create one audio file and multiple video files
 
 For example:
 
-The file **_in.video_** can be any container with at least one audio and one video stream that can be decoded by ffmpeg,
+The file **_in.video_** can be any container with at least one audio and one video stream that can be decoded by FFmpeg,
 
 Create the audio using:
 

diff --git a/files/en-us/web/media/formats/audio_codecs/index.md b/files/en-us/web/media/formats/audio_codecs/index.md
@@ -546,7 +546,7 @@ As a speech-specific codec, AMR is essentially useless for any other content, in
   <th rowspan="2" scope="row">Supported bit rates</th>
   <td>
   <strong>Half Rate (HR) and Full Rate (FR):</strong> 1.8 kbps, 4.75 kbps,
-  5.15 kbpz, 5.9 kbps, 6.7 kbps, 7.4 kbps, 7.95 kbps
+  5.15 kbps, 5.9 kbps, 6.7 kbps, 7.4 kbps, 7.95 kbps
   </td>
  </tr>
  <tr>

diff --git a/files/en-us/web/media/formats/video_codecs/index.md b/files/en-us/web/media/formats/video_codecs/index.md
@@ -811,7 +811,7 @@ H.263 is a proprietary format, with [patents](https://www.itu.int/ITU-T/recommen
  <tbody>
  <tr>
   <th scope="row">Supported bit rates</th>
-  <td>Unrestricted, but typically below 64 Kbps</td>
+  <td>Unrestricted, but typically below 64 kbps</td>
  </tr>
  <tr>
   <th scope="row">Supported frame rates</th>
@@ -930,7 +930,7 @@ HEVC is a proprietary format and is covered by a number of patents. Licensing is
  <tbody>
  <tr>
   <th scope="row">Supported bit rates</th>
-  <td>Up to 800,000 Kbps</td>
+  <td>Up to 800,000 kbps</td>
  </tr>
  <tr>
   <th scope="row">Supported frame rates</th>
@@ -1113,7 +1113,7 @@ You almost certainly don't want to use this format, since it isn't supported in
  <tbody>
  <tr>
   <th scope="row">Supported bit rates</th>
-  <td>5 Kbps to 1 Gbps and more</td>
+  <td>5 kbps to 1 Gbps and more</td>
  </tr>
  <tr>
   <th scope="row">Supported frame rates</th>

diff --git a/files/en-us/web/performance/understanding_latency/index.md b/files/en-us/web/performance/understanding_latency/index.md
@@ -30,11 +30,11 @@ In the developer tools, under the network table, you can switch the throttling o
 
 | Selection | Download speed | Upload speed | Minimum latency (ms) |
 | -------------- | -------------- | ------------ | -------------------- |
-| GPRS | 50 Kbps | 20 Kbps | 500 |
-| Regular 2G | 250 Kbps | 50 Kbps | 300 |
-| Good 2G | 450 Kbps | 150 Kbps | 150 |
-| Regular 3G | 750 Kbps | 250 Kbps | 100 |
-| Good 3G | 1.5 Mbps | 750 Kbps | 40 |
+| GPRS | 50 kbps | 20 kbps | 500 |
+| Regular 2G | 250 kbps | 50 kbps | 300 |
+| Good 2G | 450 kbps | 150 kbps | 150 |
+| Regular 3G | 750 kbps | 250 kbps | 100 |
+| Good 3G | 1.5 Mbps | 750 kbps | 40 |
 | Regular 4G/LTE | 4 Mbps | 3 Mbps | 20 |
 | DSL | 2 Mbps | 1 Mbps | 5 |
 | Wi-Fi | 30 Mbps | 15 Mbps | 2 |

diff --git a/files/en-us/web/privacy/third-party_cookies/index.md b/files/en-us/web/privacy/third-party_cookies/index.md
@@ -44,9 +44,9 @@ Each of the three sites has an embedded sign-in widget, hosted at `auth.site`, t
 
 ## What is the problem with third-party cookies?
 
-The above use cases sound innocent enough. However, third-party cookies can also be used for illegimitate purposes without the user's consent, which are technically undistinguishable from valid use cases.
+The above use cases sound innocent enough. However, third-party cookies can also be used for illegitimate purposes without the user's consent, which are technically undistinguishable from valid use cases.
 
-Following a link to a third-party or interacting with third-party content embeded in an `<iframe>` (for example, filling out a form or clicking a button) could result in cookies being set that put a user's information in the hands of someone they didn't expect. This information could be used to:
+Following a link to a third-party or interacting with third-party content embedded in an `<iframe>` (for example, filling out a form or clicking a button) could result in cookies being set that put a user's information in the hands of someone they didn't expect. This information could be used to:
 
 - Chase users around the web with targetted ads whenever they search for information on a specific product.
 - Target users with spam emails or phone calls.

diff --git a/files/en-us/web/security/certificate_transparency/index.md b/files/en-us/web/security/certificate_transparency/index.md
@@ -16,7 +16,7 @@ CT logs are built upon the foundation of the _Merkle tree_ data structure. Nodes
 
 In the context of certificate transparency, the data hashed by the leaf nodes are the certificates that have been issued by the various different CAs operating today. Certificate inclusion can be verified via an _audit proof_ which can be generated and verified efficiently, in logarithmic O(log n) time.
 
-Certificate transparency initially came about in 2013 against a backdrop of CA compromises (DigiNotar breach in 2011), questionable decisions (Trustwave subordinate root incident in 2012) and technical issuance issues (weak, 512-bit certificate issuance by Digicert Sdn Bhd of Malaysia).
+Certificate transparency initially came about in 2013 against a backdrop of CA compromises (DigiNotar breach in 2011), questionable decisions (Trustwave subordinate root incident in 2012) and technical issuance issues (weak, 512-bit certificate issuance by DigiCert Sdn Bhd of Malaysia).
 
 ## Implementation
 

diff --git a/files/en-us/web/security/index.md b/files/en-us/web/security/index.md
@@ -53,7 +53,7 @@ Related topics:
 - [HTTP Strict-Transport-Security](/en-US/docs/Web/HTTP/Headers/Strict-Transport-Security)
  - : The `Strict-Transport-Security:` [HTTP](/en-US/docs/Web/HTTP) header lets a website specify that it may only be accessed using HTTPS.
 - [Certificate Transparency](/en-US/docs/Web/Security/Certificate_Transparency)
- - : **Certificate Transparency** is an open framework designed to protect against and monitor for certificate misissuances. Newly issued certificates are 'logged' to publicly run, often independent CT logs which maintain an append-only, cryptographically assured record of issued TLS certificates.
+ - : **Certificate Transparency** is an open framework designed to protect against and monitor for certificate misissuance. Newly issued certificates are 'logged' to publicly run, often independent CT logs which maintain an append-only, cryptographically assured record of issued TLS certificates.
 - [Mixed content](/en-US/docs/Web/Security/Mixed_content)
  - : An HTTPS page that includes content fetched using cleartext HTTP is called a **mixed content** page. Pages like this are only partially encrypted, leaving the unencrypted content accessible to sniffers and man-in-the-middle attackers.
 - [How to fix a website with blocked mixed content](/en-US/docs/Web/Security/Mixed_content/How_to_fix_website_with_mixed_content)

diff --git a/files/en-us/webassembly/reference/memory/load/index.md b/files/en-us/webassembly/reference/memory/load/index.md
@@ -13,7 +13,7 @@ The **`load`** [memory instructions](/en-US/docs/WebAssembly/Reference/Memory) a
 
 There are `load` instructions for loading from a memory into an `i32`, `i64`, `f32`, and `f64`.
 For the integer numbers, there are separate instruction variants for loading a narrower signed number and unsigned number from memory and extending it into a wider type.
-For example, you can load an unsigned 8-bit number and convert it into an i32 usoing `i32.load8_u`.
+For example, you can load an unsigned 8-bit number and convert it into an i32 using `i32.load8_u`.
 All the variants are [listed below](#instructions_and_opcodes).
 
 {{EmbedInteractiveExample("pages/wat/load.html", "tabbed-taller")}}