docs: fix navigation.json path in adding-pages guide and typos in blog posts

docs/adding-pages.md tells contributors twice to edit
`app/site/navigation.json`, which does not exist. The file is
`apps/site/navigation.json`.

Also fix misspellings in the English blog posts: occuring, effected,
additon, millenia, rewritting, overwitten, encounted, retrive,
interuption, priviledges, serverity, delievered, protoype, annoucement.

Signed-off-by: toyeshhm <toyeshhm@gmail.com>

Author: toyeshhm

apps/site/pages/en/blog/announcements/making-nodejs-downloads-reliable.md

@@ -77,7 +77,7 @@ There were also a handful of other issues with the origin server pertaining to i
 
 All of these issues combined created for scenarios where the origin server wasn't touched unless necessary, including a period in which it had over _3 years of uptime_.
 These factors also contributed to incidents such as the one that occurred from [March 15th, 2023 to March 17th, 2023](/en/blog/announcements/node-js-march-17-incident), where the Node.js release assets were unavailable for 2 days due to the origin server being overloaded and improper caching rules.
-Between incidents like this and the daily outages that were occuring, users were being effected and were painfully aware of the unreliability of the infrastructure.
+Between incidents like this and the daily outages that were occurring, users were being affected and were painfully aware of the unreliability of the infrastructure.
 
 This needed to be fixed.
 
@@ -138,7 +138,7 @@ However, R2 doesn't support symlinks, meaning we needed to come up with a soluti
 Finally, we needed to meet the reliability goal.
 To do this, we implemented four things:
 
-1. Any request to R2 that fails is retried 3 times (in additon to the retries that Workers already performs).
+1. Any request to R2 that fails is retried 3 times (in addition to the retries that Workers already performs).
 2. A "fallback" system. Any request to R2 that fails all retries is rewritten to the old infrastructure.
 3. When an error does happen, it's recorded in [Sentry](https://sentry.io/welcome) and we're notified so we can take appropriate action.
 4. Slack alerts are in place for Sentry and for any critical point of failure in the Release Worker (ex/ deployment failure).

apps/site/pages/en/blog/community/2025-pride.md

@@ -24,7 +24,7 @@ Queer humans experience this for other parts of their identity. When we were you
 
 We grow older, and a boy finds they can't stop staring at how another boy moves. A girl touches her friend and starts burning inside. A young woman finds that dresses make her preferred activities more difficult, that her breasts feel malignant. We learned labels for these feelings: lesbian, gay, bisexual, transgender — LGBT.
 
-These labels are hard-won knowledge dating back decades, centuries, millenia. Regardless of your moral opinion on the matter, there are indisputable references to queer identity in literature, media, culture, religion, spirituality, dating back thousands of years. Its presence is inarguable.
+These labels are hard-won knowledge dating back decades, centuries, millennia. Regardless of your moral opinion on the matter, there are indisputable references to queer identity in literature, media, culture, religion, spirituality, dating back thousands of years. Its presence is inarguable.
 
 Even with this cultural legacy, some of us have learned through our lives that these labels too are insufficient. Like open source, we take what was known and build on it. New labels are created and spread through word of mouth, through writing and videos, through intimate conversations with our friends and partners. An academic publishes survey results; a TikTok creator's video resonates; a psychologist writes a bestselling book. As advancements in open source inform our profession, evolving language around queer identity informs our self image; indistinct visions gain clarity.
 

apps/site/pages/en/blog/events/collab-summit-2025-paris.md

@@ -93,4 +93,4 @@ We combined two topics about modules into one session block.
 
 Joyee Cheung gave a status update on the module loader hooks and what's next for `module.registerHooks()`. The consensus in the room was that we can make the internal module loading paths synchronous for better performance and reduce quirks/bugs, then implement `module.register()` as a helper on top of `module.registerHooks()` for those who want out-of-the-box worker orchestration and compatibility of the older API. For those who wish to run asynchronous code from `module.registerHooks()`, we can provide a utility similar to [everysync](https://www.npmjs.com/package/everysync). For the upcoming [evaluate hook](https://github.com/nodejs/node/pull/57139), we think that it could land with the current naming, so that it can make at least part of the lives of module customizers easier, even though it won't cover all evaluation edges due to JS spec constraints.
 
-Bryan English introduced a new mechanism to instrument ESM - instead of patching module exports externally, which can run into issues with live binding of exports that are lazily initialized, patch the exports internally by parsing, analysing, and rewriting the AST of the target exports to inject tracing channels. This rust-based instrumentation library has now been open-sourced on [GitHub](https://github.com/DataDog/orchestrion-js). We discussed what Node.js core can provide to make instrumentation like this more streamlined, and how to integrate AsyncContext with it to improve handling of edge cases like constructors with `super()`. While it's still in development and there are still some open issues to solve, hopefully this can be a breeding ground for adding official tracing channel support in libraries for observability without rewritting the AST in a third-party tool.
+Bryan English introduced a new mechanism to instrument ESM - instead of patching module exports externally, which can run into issues with live binding of exports that are lazily initialized, patch the exports internally by parsing, analysing, and rewriting the AST of the target exports to inject tracing channels. This rust-based instrumentation library has now been open-sourced on [GitHub](https://github.com/DataDog/orchestrion-js). We discussed what Node.js core can provide to make instrumentation like this more streamlined, and how to integrate AsyncContext with it to improve handling of edge cases like constructors with `super()`. While it's still in development and there are still some open issues to solve, hopefully this can be a breeding ground for adding official tracing channel support in libraries for observability without rewriting the AST in a third-party tool.

apps/site/pages/en/blog/vulnerability/aug-2021-security-releases2.md

@@ -28,7 +28,7 @@ Impacts:
 
 - All versions of the 14.x, and 12.x releases lines
 
-**Note**: [CVE-2021-39134](https://github.com/npm/arborist/security/advisories/GHSA-2h3h-q99f-3fhc) and [CVE-2021-39135](https://github.com/npm/arborist/security/advisories/GHSA-gmw6-94gg-2rc2) previously mentioned in this annoucement do not apply to Node.js 12 and 14 as npm@6 does not depend on the `@npm/arborist` module. These vulnerabilities applied to Node.js 16 and have been fixed via the npm 7.21.0 update which was shipped in [Node.js v16.8.0 (Current)](/blog/release/v16.8.0/).
+**Note**: [CVE-2021-39134](https://github.com/npm/arborist/security/advisories/GHSA-2h3h-q99f-3fhc) and [CVE-2021-39135](https://github.com/npm/arborist/security/advisories/GHSA-gmw6-94gg-2rc2) previously mentioned in this announcement do not apply to Node.js 12 and 14 as npm@6 does not depend on the `@npm/arborist` module. These vulnerabilities applied to Node.js 16 and have been fixed via the npm 7.21.0 update which was shipped in [Node.js v16.8.0 (Current)](/blog/release/v16.8.0/).
 
 ## Downloads and release details
 

apps/site/pages/en/blog/vulnerability/august-2023-security-releases.md

@@ -84,7 +84,7 @@ Impacts
 Thank you, to LeoDog896 for reporting this vulnerability and thank you [Tobias Nießen](https://github.com/tniessen)
 for fixing it.
 
-## `fs.statfs` can retrive stats from files restricted by the Permission Model (LOW)(CVE-2023-32005)
+## `fs.statfs` can retrieve stats from files restricted by the Permission Model (LOW)(CVE-2023-32005)
 
 A vulnerability has been identified in Node.js version 20, affecting users of the experimental permission model when the `--allow-fs-read` flag is used with a non-`*` argument.
 

apps/site/pages/en/blog/vulnerability/february-2023-security-releases.md

@@ -65,7 +65,7 @@ Impacts:
 
 ## Node.js insecure loading of ICU data through ICU_DATA environment variable (Low) ([CVE-2023-23920](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-23920))
 
-Node.js would search and potentially load ICU data when running with elevated priviledges. Node.js
+Node.js would search and potentially load ICU data when running with elevated privileges. Node.js
 was modified to build with `ICU_NO_USER_DATA_OVERRIDE` to avoid this.
 
 Thank you, to Ben Noordhuis for reporting this vulnerability and thank you [Rafael Gonzaga](https://github.com/RafaelGSS) for fixing it.

apps/site/pages/en/blog/vulnerability/february-2024-security-releases.md

@@ -101,7 +101,7 @@ for fixing it.
 
 ## Multiple permission model bypasses due to improper path traversal sequence sanitization (CVE-2024-21891) - (Medium)
 
-Node.js depends on multiple built-in utility functions to normalize paths provided to node:fs functions, which can be overwitten with user-defined implementations leading to filesystem permission model bypass through path traversal attack.
+Node.js depends on multiple built-in utility functions to normalize paths provided to node:fs functions, which can be overwritten with user-defined implementations leading to filesystem permission model bypass through path traversal attack.
 
 Impacts:
 
@@ -136,7 +136,7 @@ Therefore, the new target date is Wednesday 14th.
 
 ## _(Update 08-February-2024)_ Security Release target Tuesday 13th
 
-We have encounted an error in one of our patches, therefore, the release will take a bit longer than expected
+We have encountered an error in one of our patches, therefore, the release will take a bit longer than expected
 and the Node.js Security Releases should be available on, or shortly after, Tuesday, February 13th, 2024.
 
 ## _(Update 06-February-2024)_ Security Release target Thursday 8th

apps/site/pages/en/blog/vulnerability/jan-2022-security-releases.md

@@ -57,7 +57,7 @@ Impacts:
 
 Due to the formatting logic of the `console.table()` function it was not safe to allow user controlled input to be passed to the `properties` parameter while simultaneously passing a plain object with at least one property as the first parameter, which could be `__proto__`. The prototype pollution has very limited control, in that it only allows an empty string to be assigned to numerical keys of the object prototype.
 
-Versions of Node.js with the fix for this use a null protoype for the object these properties are being assigned to.
+Versions of Node.js with the fix for this use a null prototype for the object these properties are being assigned to.
 
 More details will be available at [CVE-2022-21824](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-21824) after publication.
 

apps/site/pages/en/blog/vulnerability/july-2022-security-releases.md

@@ -160,7 +160,7 @@ Therefore, Node.js is not affected.
 
 #### AES OCB fails to encrypt some bytes (CVE-2022-2097) (MODERATE)
 
-This vulnerability affects Windows 32-Bit x86 users using `AES OCB` encryption. The serverity is MODERATE.
+This vulnerability affects Windows 32-Bit x86 users using `AES OCB` encryption. The severity is MODERATE.
 
 ## (Update 04-Jul-2022) OpenSSL Security Release
 

apps/site/pages/en/blog/vulnerability/june-2023-security-releases.md

@@ -137,7 +137,7 @@ Please note that at the time this CVE was issued, the permission model is an exp
 
 Thanks to [Tobias Nießen](https://github.com/tniessen) for reporting this vulnerability and fixing it.
 
-## Process interuption due to invalid Public Key information in x509 certificates (Medium) (CVE-2023-30588)
+## Process interruption due to invalid Public Key information in x509 certificates (Medium) (CVE-2023-30588)
 
 When an invalid public key is used to create an x509 certificate using the crypto.X509Certificate() API a non-expect
 termination occurs making it susceptible to DoS attacks when the attacker could force interruptions of application processing,