nodejs · fhemberger · Feb 7, 2017 · Feb 6, 2017
diff --git a/TRANSLATION.md b/TRANSLATION.md
@@ -49,7 +49,7 @@ would like to contribute to the translation of nodejs.org, please refer to the f
 
 * Ensure that any site translations are done as pull requests into the appropriate language folder in this repo. This will ensure the build process, layout, and styling, remain consistent across the different translations of the site.
 
-* You can find the appropriate language folder within `locale/`. If not, create one matching the two-letter [ISO code](https://en.wikipedia.org/wiki/List_of_ISO_639-1_codes) of your language. To specify a dialect for your language, [separate it with a dash](https://en.wikipedia.org/wiki/IETF_language_tag) (e.g. `pt-br` for Brazilian Portugese, `zh-tw` for Taiwanese Mandarin).
+* You can find the appropriate language folder within `locale/`. If not, create one matching the two-letter [ISO code](https://en.wikipedia.org/wiki/List_of_ISO_639-1_codes) of your language. To specify a dialect for your language, [separate it with a dash](https://en.wikipedia.org/wiki/IETF_language_tag) (e.g. `pt-br` for Brazilian Portuguese, `zh-tw` for Taiwanese Mandarin).
 
 * The following files need to be in your language folder:
 

diff --git a/locale/en/about/trademark.md b/locale/en/about/trademark.md
@@ -21,7 +21,7 @@ goal in mind, we’ve tried to make the policy as flexible and easy to understan
 as legally possible.
 
 Please read the [full policy](/static/documents/trademark-policy.pdf).
-If you have any questions don't hesistate to
+If you have any questions don't hesitate to
 [email us](mailto:[email protected]).
 
 Guidelines for the visual display of the Node.js mark are described in

diff --git a/locale/en/blog/uncategorized/node-interactive-convince-boss.md b/locale/en/blog/uncategorized/node-interactive-convince-boss.md
@@ -15,7 +15,7 @@ Dear `Boss Name`,
 
 I’d like to attend **[Node.js Interactive 2015](http://events.linuxfoundation.org/events/node-interactive)** taking place December 8-9, 2015, in Portland, OR. There are a lot of Node.js conferences during the year, but this is the premier conference put on by the Node.js Foundation. Vendor-neutral by design, it is focused on everything from fine-tuning my skills in Node.js to the future of the platform. Node.js is penetrating almost every single aspect of technology from powering robots to enterprise, and is downloaded 2 million times per month. It’s a pretty big deal.
 
-They are anticipating more than 700 individuals will attend the event. The conference welcomes experienced developers as well as those interested in learning how to implement Node.js into their business, and everyone inbetween. The tracks focus on IoT, frontend and backend technologies. Here are just a few advantages of me going to the conference. 
+They are anticipating more than 700 individuals will attend the event. The conference welcomes experienced developers as well as those interested in learning how to implement Node.js into their business, and everyone between. The tracks focus on IoT, frontend and backend technologies. Here are just a few advantages of me going to the conference. 
 * One of the great features about the technology is how diverse it is. It can be used to build mobile apps or enterprise apps, and almost every single big named company is using it from LinkedIn to IBM to Netflix. If we decide to build out our product strategy or offering, it is likely that Node.js will be the technology that I use across the board. 
 
 * There will be more than 50 sessions in the two day conference. These sessions include visionary keynotes, hands-on tutorials, deep-dive technical lectures, and presentations.

diff --git a/locale/en/blog/vulnerability/openssl-march-2016.md b/locale/en/blog/vulnerability/openssl-march-2016.md
@@ -35,7 +35,7 @@ If the OpenSSL 1.0.1s release contains important fixes that impact Node.js v0.10
 
 A release of Node.js v0.12.11 has been proposed for this week, it currently contains fixes for domains, an important fix for a regression in http_parser that was introduced in v0.12.10, and some other minor fixes. Details of the changes included in this release along with instructions on how to download and use a release candidate (v0.12.11-rc.1) can be found in <https://github.com/nodejs/node/pull/5403>. Node.js v0.12 users are encouraged to test the release candidate build to ensure compatibility with existing deployments.
 
-If the OpenSSL 1.0.1s release contains important fixes for Node.js v0.12 we will endevour to ensure that our v0.12.11 release contains the update.
+If the OpenSSL 1.0.1s release contains important fixes for Node.js v0.12 we will endeavour to ensure that our v0.12.11 release contains the update.
 
 ### Node.js v4 (LTS "Argon")
 
@@ -49,7 +49,7 @@ If the OpenSSL 1.0.2g update _does not include_ important fixes that impact Node
 
 A regular update to Node.js v5 has been proposed for this week. You can read about what will be included in the proposed Node.js v5.7.1 at <https://github.com/nodejs/node/pull/5464>. We are excluding any semver-minor changes from this release although it has fixes for some regressions 
 
-If the OpenSSL 1.0.2g release contains important fixes for Node.js v5, we will endevour to ensure that our v5.7.1 release contains the update.
+If the OpenSSL 1.0.2g release contains important fixes for Node.js v5, we will endeavour to ensure that our v5.7.1 release contains the update.
 
 ### Summary
 

diff --git a/locale/en/blog/weekly-updates/weekly-update.2015-02-13.md b/locale/en/blog/weekly-updates/weekly-update.2015-02-13.md
@@ -69,7 +69,7 @@ View the [original article](https://medium.com/@mikeal/how-io-js-built-a-146-per
 * [`iojs-sv`](https://github.com/iojs/iojs-sv) Swedish Community
 * [`iojs-tr`](https://github.com/iojs/iojs-tr) Turkish Community
 * [`iojs-tw`](https://github.com/iojs/iojs-tw) Taiwan Community
-* [`iojs-uk`](https://github.com/iojs/iojs-uk) Ukranian Community
+* [`iojs-uk`](https://github.com/iojs/iojs-uk) Ukrainian Community
 
 ## io.js and Node.js
 View the [original article](https://medium.com/@iojs/io-js-and-a-node-js-foundation-4e14699fb7be) on Medium.

diff --git a/locale/en/foundation/case-studies.md b/locale/en/foundation/case-studies.md
@@ -106,7 +106,7 @@ his long history of success with Node.js and his current work at GoDaddy.
 
 <iframe width="560" height="315" src="https://www.youtube.com/embed/dvMq4gqBleo" frameborder="0" allowfullscreen></iframe>
 
-## Captial One (Episode 1)
+## Capital One (Episode 1)
 
 Azat Mardan shares his experience transforming CaptialOne with Node.js.
 

diff --git a/locale/en/foundation/outreachy.md b/locale/en/foundation/outreachy.md
@@ -132,7 +132,7 @@ In this project, you will collaborate with members of the Node.js project, and m
 
 The project will be broken down into a number of stages including:
 
- * Getting familliar with the Node.js code base
+ * Getting familiar with the Node.js code base
  * Getting your first commits into Node.js core
    - A list of good first contributions can be found [here](https://github.com/nodejs/node/issues?q=is%3Aissue+is%3Aopen+label%3A%22good+first+contribution%22)
  * Getting familiar with the libuv code base

diff --git a/locale/en/foundation/tsc/minutes/2014-12-10.md b/locale/en/foundation/tsc/minutes/2014-12-10.md
@@ -21,7 +21,7 @@ problems for users who link node with a dynamic shared libuv.
 
 ### 0.11.15
 
-Nobody had any blocker for the next developement release, whose release is
+Nobody had any blocker for the next development release, whose release is
 also scheduled to happen in the next few days. The priority is given to
 releasing 0.10.34 first though.
 

diff --git a/locale/en/foundation/tsc/minutes/2015-01-22.md b/locale/en/foundation/tsc/minutes/2015-01-22.md
@@ -80,7 +80,7 @@ Michael agreed that the target for such a port would likely be 0.14.0. Michael
 mentioned that ideally the process of upstreaming changes to V8 would be done
 by that time. If not, there has been discussions recently between TJ and Chris
 on refactoring the dependencies management so that maintaining floating
-patches (also for other dependencies liek c-ares and OpenSSL) would be easier.
+patches (also for other dependencies like c-ares and OpenSSL) would be easier.
 
 ### 0.10.36 release
 

diff --git a/locale/en/foundation/tsc/minutes/2015-02-09.md b/locale/en/foundation/tsc/minutes/2015-02-09.md
@@ -51,7 +51,7 @@ abstraction layer.
 Alexis, TJ: that would become the blessed V8/JSruntime API for binary add-ons.
 
 TJ: C++ ABI has worked so far, but probably because we've been lucky. So C API
-makes more sense and would be more robust accross different platforms.
+makes more sense and would be more robust across different platforms.
 
 Alexis Campailla: What about nan?
 
@@ -145,7 +145,7 @@ any GitHub pull request.
 
 ## Alexis Campailla: Running benchmarks for Windows.
 
-Julien: Tracking benchmarks results accross every commit would be very useful
+Julien: Tracking benchmarks results across every commit would be very useful
 to identify the causes of performance regressions.
 
 James Snell, Michael Dawson: IBM started to run benchmarks for downstream

diff --git a/locale/en/foundation/tsc/minutes/2015-03-19.md b/locale/en/foundation/tsc/minutes/2015-03-19.md
@@ -79,7 +79,7 @@ agreed the existing fix is appropriate and we should just backport it to
 
 Julien is talking with some groups about doing some pre-release testing on
 release candidates. TJ suggested we should ask for volunteers on the blog or
-twitter. It will need to be a full blown release candiate due to gyp
+twitter. It will need to be a full blown release candidate due to gyp
 dependencies etc. Julien will write up a proposal.
 
 #### Tooling around issues/PR triaging

diff --git a/locale/en/foundation/tsc/minutes/2015-04-24.md b/locale/en/foundation/tsc/minutes/2015-04-24.md
@@ -21,7 +21,7 @@ layout: foundation-tsc-minutes-post.hbs
 Discussion around removal of RC4 to address Bar Mitzva attack.  Progress
 being made, need to update to clarify precedence of command line 
 options (https://github.com/joyent/node/pull/19148), update code/tests to 
-match this descripton (James), finalize release notes (Julien with input from all) 
+match this description (James), finalize release notes (Julien with input from all) 
 and then do one final review before release (all).   Important that we add
 tests to make sure merge with 0.12.X can be easily validated.
 

diff --git a/locale/en/foundation/tsc/minutes/2015-04-30.md b/locale/en/foundation/tsc/minutes/2015-04-30.md
@@ -75,9 +75,9 @@ James: Initial convergance plan: https://github.com/jasnell/dev-policy/pull/66.
 
 James: nothing set in stone. Current plan:
 
-* io.js organization transfered to nodejs organization. Will keep everything
+* io.js organization transferred to nodejs organization. Will keep everything
 they've already setup.
-* joyent/node and other joyent/node-related repos will also be transfered to
+* joyent/node and other joyent/node-related repos will also be transferred to
 this organization.
 * Both joyent/node and iojs/iojs repos would be under the foundation.
 * For the converged repo, a fork of iojs repo would be created.