Fixed some typos in API documentation (#1935)

IoT.js-DCO-1.0-Signed-off-by: Adam Kallai [email protected]

Author: kaadam

docs/api/IoT.js-API-Events.md

@@ -19,7 +19,7 @@ IoT.js is based on event-driven programming where objects (called "emitters") pe
 # Class: EventEmitter
 
 The `EventEmitter` plays a role as base class for "emitters".
-User application would not directly creates an instance of `EventEmitter` since `EventEmitter` is an abstract trait which defines its behavior and grants to sub-classes.
+User application would not directly create an instance of `EventEmitter` since `EventEmitter` is an abstract trait which defines its behavior and grants to sub-classes.
 
 ### new EventEmitter()
 * Returns {EventEmitter}.

docs/api/IoT.js-API-HTTP.md

@@ -99,7 +99,7 @@ server.listen(port, function() {
 * Returns: {http.ClientRequest}
 
 The function creates a `http.ClientRequest` instance with the `options` defined.
-This can be used to get data form a server or to send data for a server.
+This can be used to get data from a server or to send data for a server.
 
 In case of data send the `'Content-Length'` header should be specifed so the server can properly handle the request.
 

docs/api/IoT.js-API-MQTT.md

@@ -20,7 +20,7 @@ The QoS level can be 0, 1 or 2.
 - Level 1 means the packet arrives at least once (duplications might occur, it is the user's responsibility to take care of them).
 - Level 2 means that the package is delivered exactly once.
 
-### Topic seperating and wildcarding
+### Topic separating and wildcarding
 Topics can be wildcarded and they also can be structured into multiple levels. These levels are divided by the `/` sign (eg. `iotjs/jerryscript/jerry-core`). There are multiple wildcarding possibilities:
  - `Multi-level wildcard` The `#` sign is a wildcard character that matches any number of levels within a topic. This character MUST be the last character in a topic name. Typing `iotjs/#` means the client subscribes to anything that is under the `iotjs` topic.
  - `Single-level wildcard` The `+` sign is a wildcard character that matches only one topic level. It can be used more at than one level in the topic name. It MUST be used so it occupies an entire level of the name. Typing `iotjs/+/jerry-core` subscribes you to `jerry-core` topic.
@@ -36,14 +36,14 @@ The `MQTTClient` can subscribe or publish data to a broker. It sends data over a
     - `host` {Buffer | string} The address of the broker.
     - `port` {number} The port of the broker.
     - `socket` {net.Socket | TLSSocket} If a `TLSSocket` is given for secure communication it is the user's responsibility to connect it to establish the TLS connection first. Otherwise the client automatically connects the socket to the server.
-    - `username` {Buffer | string} Optional. Use username when onnecting to a broker.
+    - `username` {Buffer | string} Optional. Use username when connecting to a broker.
     - `password` {Buffer | string} Optional. Use password authentication when connecting to a broker.
     - `keepalive` {number} Keepalive time in seconds. If no data is sent on the connection in the given time window the broker disconnects the client.
     - `will` {boolean} Optional. If this flag is set to `true`, a `message` and a `topic` must follow with a QoS value between 0 and 2.
     - `qos` {number} If `will` is set to `true`, the message will be sent with the given QoS.
     - `topic` {Buffer | string} Only processed when `will` is set to `true`. The topic the `message` should be sent to.
     - `message` {Buffer | string} Only processed when `will` is set to `true`. The message to be sent to the broker when connecting.
-- `callback` {function} the function which will be executed when the client successfuly connected to the broker.
+- `callback` {function} the function which will be executed when the client successfully connected to the broker.
 
 Returns with an MQTTClient object and starts connecting to a broker. Emits a `connect` event after the connection is completed.
 
@@ -153,7 +153,7 @@ Emitted when the client successfully connects to a broker.
 A `disconnect` event is emitted when the broker disconnects the client gracefully.
 
 ### `error`
-If an error occured an `error` event is emitted with the error data.
+If an error occurred an `error` event is emitted with the error data.
 
 ### `message`
 When data is received from the server a `message` event is emitted with a `data` object. It has the following properties:

docs/api/IoT.js-API-Process.md

@@ -126,7 +126,7 @@ IoT.js will not exit till all `'exit'` event listeners are called.
 The `process.exit()` method call will force the process to exit as quickly as possible,
 ignoring if there is any asynchronous operations still pending.
 
-In most situations, it is not necessary to explcitly call `process.exit()`. The IoT.js will exit on its own
+In most situations, it is not necessary to explicitly call `process.exit()`. The IoT.js will exit on its own
 if there is no additional work pending in the event loop. The `process.exitCode` property can be set
 to exit code when the process exits gracefully.
 

docs/api/IoT.js-API-TLS.md

@@ -112,7 +112,7 @@ The method returns a special object containing the tls context and credential in
 
 ## Class: tls.Server
 
-A server object repesenting a TLS server. Based on the `net.Server`.
+A server object representing a TLS server. Based on the `net.Server`.
 All events, methods and properties are inherited from the `net.Server`.
 
 ### new tls.Server([options][, secureConnectionListener])
@@ -121,7 +121,7 @@ All events, methods and properties are inherited from the `net.Server`.
   * `secureContext` {object} An special object containing the tls credential information.
     This should be only created via a `tls.createSecureContext()` call if needed. If not provided
     a secureContext will be created automatically, using the `options` object. No default value is provided.
-  * Additonal options are from `tls.createSecureContext()`.
+  * Additional options are from `tls.createSecureContext()`.
 * `secureConnectionListener` {Function}
   * `socket` {tls.TLSSocket}
 * Returns {tls.Server}

docs/api/IoT.js-API-Timers.md

@@ -89,4 +89,4 @@ When called, requests that the IoT.js event loop should not exit as long as the
 
 ### timeout.unref()
 
-When called, the active `Timeout` object will not force the IoT.js event loop to remain active. If there are no other scheduled activites, the process may exit, the process may exit before the `Timeout` object's callback is invoked.
+When called, the active `Timeout` object will not force the IoT.js event loop to remain active. If there are no other scheduled activities, the process may exit, the process may exit before the `Timeout` object's callback is invoked.