Assorted typo fixes.

Author: XhmikosR

locale/en/blog/release/v0.5.10.md

@@ -11,7 +11,7 @@ layout: blog-post.hbs
 
 2011.10.21, Version 0.5.10 (unstable)
 <ul><li>Remove cmake build system, support for Cygwin, legacy code base, process.ENV, process.ARGV, process.memoryUsage().vsize, os.openOSHandle</li>
-<li>Documentation improvments (Igor Zinkovsky, Bert Belder, Ilya Dmitrichenko, koichik, Maciej Małecki, Guglielmo Ferri, isaacs)</li>
+<li>Documentation improvements (Igor Zinkovsky, Bert Belder, Ilya Dmitrichenko, koichik, Maciej Małecki, Guglielmo Ferri, isaacs)</li>
 <li>Performance improvements (Daniel Ennis, Bert Belder, Ben Noordhuis) </li>
 <li>Long process.title support (Ben Noordhuis)</li>
 <li>net: register net.Server callback only once (Simen Brekken)</li>

locale/en/blog/release/v0.5.5.md

@@ -40,4 +40,4 @@ layout: blog-post.hbs
 <p>Documentation: <a href="https://nodejs.org/docs/v0.5.5/api/">https://nodejs.org/docs/v0.5.5/api/</a></p>
 <br /><br />
 
-<b>Update:</b> The <code>.exe</code> has a bug that results in incompatibility with Windows XP and Server 2003. This has been reported in <a href="https://github.com/joyent/node/issues/1592">issue #1592</a> and fixed. A new binary was made that is compatibile with the older Windows: <a href="https://nodejs.org/dist/v0.5.5/node-186364e.exe">https://nodejs.org/dist/v0.5.5/node-186364e.exe</a>.
+<b>Update:</b> The <code>.exe</code> has a bug that results in incompatibility with Windows XP and Server 2003. This has been reported in <a href="https://github.com/joyent/node/issues/1592">issue #1592</a> and fixed. A new binary was made that is compatible with the older Windows: <a href="https://nodejs.org/dist/v0.5.5/node-186364e.exe">https://nodejs.org/dist/v0.5.5/node-186364e.exe</a>.

locale/en/blog/release/v5.10.1.md

@@ -11,7 +11,7 @@ author: Myles Borins
 ### Notable changes
 
 * **http**:
-  * Enclose IPv6 Host header in square brackets. This will enable proper seperation of the host adress from any port reference (Mihai Potra) [#5314](https://github.com/nodejs/node/pull/5314)
+  * Enclose IPv6 Host header in square brackets. This will enable proper separation of the host address from any port reference (Mihai Potra) [#5314](https://github.com/nodejs/node/pull/5314)
 
 * **path**:
   * Make win32.isAbsolute more consistent (Brian White) [#6028](https://github.com/nodejs/node/pull/6028)

locale/en/knowledge/cryptography/how-to-use-crypto-module.md

@@ -125,7 +125,7 @@ if (argv.e && argv.key) {
 }
 ```
 
-NODE PRO TIP: The `crypto.createCipheriv()` and `crypto.createDecipheriv()` methods do not take a password, rather a `key` and an `iv` which are combined together to form a random password. The size of the `key` and `iv` depends on the choosen algorithm. A reference to common algorithms and their `key` and `iv` size is given below:
+NODE PRO TIP: The `crypto.createCipheriv()` and `crypto.createDecipheriv()` methods do not take a password, rather a `key` and an `iv` which are combined together to form a random password. The size of the `key` and `iv` depends on the chosen algorithm. A reference to common algorithms and their `key` and `iv` size is given below:
 
 | Algorithm      | Key                | iv                 |
 | -------------  |:-----------------: | :----------------: |

locale/ko/about/trademark.md

@@ -34,7 +34,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:trademark@nodejs.org).
 
 Guidelines for the visual display of the Node.js mark are described in

locale/ru/knowledge/HTTP/clients/how-to-create-a-HTTP-request.md

@@ -24,12 +24,12 @@ As an example, we are going to preform a GET request to [www.random.org/integers
     callback = function(response) {
       var str = '';
 
-      //another chunk of data has been recieved, so append it to `str`
+      //another chunk of data has been received, so append it to `str`
       response.on('data', function (chunk) {
         str += chunk;
       });
 
-      //the whole response has been recieved, so we just print it out here
+      //the whole response has been received, so we just print it out here
       response.on('end', function () {
         console.log(str);
       });

locale/ru/knowledge/HTTP/servers/how-to-read-POST-data.md

@@ -36,9 +36,9 @@ Here is a quick script that shows you how to do exactly that:
 
 The variable `postHTML` is a static string containing the HTML for two input boxes and a submit box - this HTML is provided so that you can `POST` example data. This is NOT the right way to serve static HTML - please see [How to Serve Static Files](link) for a more proper example.
 
-With the HTML out of the way, we [create a server](/how-do-i-create-a-http-server) to listen for requests. It is important to note, when listening for POST data, that the `req` object is also an [Event Emitter](/what-are-event-emitters).  `req`, therefore, will emit a `data` event whenever a 'chunk' of incoming data is received; when there is no more incoming data, the `end` event is emitted. So, in our case, we listen for `data` events. Once all the data is recieved, we log the data to the console and send the response. 
+With the HTML out of the way, we [create a server](/how-do-i-create-a-http-server) to listen for requests. It is important to note, when listening for POST data, that the `req` object is also an [Event Emitter](/what-are-event-emitters).  `req`, therefore, will emit a `data` event whenever a 'chunk' of incoming data is received; when there is no more incoming data, the `end` event is emitted. So, in our case, we listen for `data` events. Once all the data is received, we log the data to the console and send the response. 
 
 Something important to note is that the event listeners are being added immediately after the request object is received. If you don't immediately set them, then there is a possibility of missing some of the events. If, for example, an event listener was attached from inside a callback, then the `data` and `end` events might be fired in the meantime with no listeners attached!
 
-You can save this script to `server.js` and run it with `node server.js`. Once you run it you will notice that occassionally you will see lines with no data, e.g. `POSTed:`. This happens because regular `GET` requests go through the same codepath. In a more 'real-world' application, it would be proper practice to check the type of request and handle the different request types differently.
+You can save this script to `server.js` and run it with `node server.js`. Once you run it you will notice that occasionally you will see lines with no data, e.g. `POSTed:`. This happens because regular `GET` requests go through the same codepath. In a more 'real-world' application, it would be proper practice to check the type of request and handle the different request types differently.
 

locale/ru/knowledge/file-system/how-to-use-the-path-module.md

@@ -53,7 +53,7 @@ Note that `basename` has an optional second parameter that will strip out the ex
 
 Lastly, the `path` module provides methods to check whether or not a given path exists: `exists` and `existsSync` They both take the path of a file for the first parameter. 
 
-`exists` takes a callback as its second parameter, to which is returned a boolean representing the existance of the file. 
+`exists` takes a callback as its second parameter, to which is returned a boolean representing the existence of the file. 
 
 `existsSync`, on the other hand, checks the given path synchronously, returning the boolean directly.  In Node.js, you will typically want to use the asynchronous functions for most file system I/O - the synchronous versions will block your entire process until they finish. 
 

locale/ru/knowledge/getting-started/control-flow/what-are-callbacks.md

@@ -26,7 +26,7 @@ The node.js way to deal with the above would look a bit more like this:
     function processData (callback) {
       fetchData(function (err, data) {
         if (err) {
-          console.log("An error has occured. Abort everything!");
+          console.log("An error has occurred. Abort everything!");
           return callback(err);
         }
         data += 1;
@@ -41,7 +41,7 @@ The typical convention with asynchronous functions (which almost all of your fun
     function asyncOperation ( a, b, c, callback ) {
       // ... lots of hard work ...
       if ( /* an error occurs */ ) {
-        return callback(new Error("An error has occured"));
+        return callback(new Error("An error has occurred"));
       }
       // ... more work ...
       callback(null, d, e, f);

locale/ru/knowledge/getting-started/control-flow/what-are-event-emitters.md

@@ -34,7 +34,7 @@ In node.js an event can be described simply as a string with a corresponding cal
     > example_emitter.emit("unhandled");
     false   //return value
 
-This demonstates all the basic functionality of an EventEmitter. The `on` or `addListener` method (basically the subscription method) allows you to choose the event to watch for and the callback to be called. The `emit` method (the publish method), on the other hand, allows you to "emit" an event, which causes all callbacks registered to the event to 'fire', (get called).
+This demonstrates all the basic functionality of an EventEmitter. The `on` or `addListener` method (basically the subscription method) allows you to choose the event to watch for and the callback to be called. The `emit` method (the publish method), on the other hand, allows you to "emit" an event, which causes all callbacks registered to the event to 'fire', (get called).
 
 So in the example, we first subscribe to both the `test` and `print` events. Then we emit the `test`, `print`, and `unhandled` events. Since `unhandled` has no callback, it just returns false; the other two run all the attached callbacks and return true.
 
@@ -99,5 +99,5 @@ If you want remove a specific callback, you can use `removeListener`. If you wan
     > ee.emit("event");
     false
 
-NOTE: If you want create more than 10 listeners on a single event, you will have to make a call to `ee.setMaxListeners(n)` where n is the max numbers of listeners (with zero being unlimited number of listeners). This is used to make sure you aren't accidently leaking event listeners.
+NOTE: If you want create more than 10 listeners on a single event, you will have to make a call to `ee.setMaxListeners(n)` where n is the max numbers of listeners (with zero being unlimited number of listeners). This is used to make sure you aren't accidentally leaking event listeners.