core: fix typos in different sections (#146)

Signed-off-by: ialidzhikov <i.alidjikov@gmail.com>

Author: ialidzhikov

configuration/backpressure.md

@@ -15,12 +15,12 @@ This option is disabled by default and can be applied to all input plugins. Let'
 * engine scheduler will retry the flush after 10 seconds
 * input plugin tries to append 500KB
 
-At this exact point, the engine will **allow** to append those 500KB of data into the engine: in total we have 1.2MB. The options works in a permisive mode before to reach the limit, but the limit is **exceeded** the following actions are taken:
+At this exact point, the engine will **allow** to append those 500KB of data into the engine: in total we have 1.2MB. The options works in a permissive mode before to reach the limit, but the limit is **exceeded** the following actions are taken:
 
 * block local buffers for the input plugin \(cannot append more data\)
 * notify the input plugin invoking a **pause** callback
 
-The engine will protect it self and will not append more data coming from the input plugin in question; Note that is the plugin responsability to keep their state and take some decisions about what to do on that _paused_ state.
+The engine will protect it self and will not append more data coming from the input plugin in question; Note that is the plugin responsibility to keep their state and take some decisions about what to do on that _paused_ state.
 
 After some seconds if the scheduler was able to flush the initial 700KB of data or it gave up after retrying, that amount memory is released and internally the following actions happens:
 

configuration/memory_usage.md

@@ -8,7 +8,7 @@ In order to estimate we will assume that the input plugins have set the **Mem\_B
 
 Input plugins append data independently, so in order to do an estimation a limit should be imposed through the **Mem\_Buf\_Limit** option. If the limit was set to _10MB_ we need to estimate that in the worse case, the output plugin likely could use _20MB_.
 
-Fluent Bit has an internal binary representation for the data being processed, but when this data reach an output plugin, this one will likely create their own representation in a new memory buffer for processing. The best example are the [InfluxDB](../output/influxdb.md) and [Elasticsearch](../output/elasticsearch.md) output plugins, both needs to convert the binary repesentation to their respective-custom JSON formats before to talk to their backend servers.
+Fluent Bit has an internal binary representation for the data being processed, but when this data reach an output plugin, this one will likely create their own representation in a new memory buffer for processing. The best example are the [InfluxDB](../output/influxdb.md) and [Elasticsearch](../output/elasticsearch.md) output plugins, both needs to convert the binary representation to their respective-custom JSON formats before to talk to their backend servers.
 
 So, if we impose a limit of _10MB_ for the input plugins and considering the worse case scenario of the output plugin consuming _20MB_ extra, as a minimum we need \(_30MB_ x 1.2\) = **36MB**.
 

development/library_api.md

@@ -227,7 +227,7 @@ To stop a running Fluent Bit engine, we provide the call **flb\_stop\(\)** for t
 int flb_stop(flb_ctx_t *ctx);
 ```
 
-The argument **ctx** is a reference to the context created at the beginnning with **flb\_create\(\)** and previously started with **flb\_start\(\)**.
+The argument **ctx** is a reference to the context created at the beginning with **flb\_create\(\)** and previously started with **flb\_start\(\)**.
 
 When the call is invoked, the engine will wait a maximum of five seconds to flush buffers and release the resources in use. A stopped context can be re-started any time but without any data on it.
 
@@ -253,7 +253,7 @@ A library context must be destroyed after is not longer necessary, note that a p
 void flb_destroy(flb_ctx_t *ctx);
 ```
 
-The argument **ctx** is a reference to the context created at the beginnning with **flb\_create\(\)**.
+The argument **ctx** is a reference to the context created at the beginning with **flb\_create\(\)**.
 
 **Return Value**
 

filter/throttle.md

@@ -8,7 +8,7 @@ The plugin supports the following configuration parameters:
 
 | Key | Value Format | Description |
 | :--- | :--- | :--- |
-| Rate | Integer | Amount of meassages for the time. |
+| Rate | Integer | Amount of messages for the time. |
 | Window | Integer | Amount of intervals to calculate average over. Default 5. |
 | Interval | String | Time interval, expressed in "sleep" format. e.g 3s, 1.5m, 0.5h etc |
 | Print\_Status | Bool | Whether to print status messages with current rate and the limits to information logs |
@@ -103,7 +103,7 @@ XXXX XXXX  XXXX XXXX XXXX XXXX
 +-+-+-+-+-+--+-+-+-+-+-+-+-+-+-+
 ```
 
-It may drop some data if the rate is ragged. I would recommend to use bigger interval and rate for streams of rare but important events, while keep _Window_ bigger and _Interval_ small for contantly intensive inputs.
+It may drop some data if the rate is ragged. I would recommend to use bigger interval and rate for streams of rare but important events, while keep _Window_ bigger and _Interval_ small for constantly intensive inputs.
 
 ### Command Line
 

output/kafka-rest-proxy.md

@@ -13,7 +13,7 @@ The **kafka-rest** output plugin, allows to flush your records into a [Kafka RES
 | Message\_Key | Set a message key \(optional\) |  |
 | Time\_Key | The Time\_Key property defines the name of the field that holds the record timestamp. | @timestamp |
 | Time\_Key\_Format | Defines the format of the timestamp. | %Y-%m-%dT%H:%M:%S |
-| Include\_Tag\_Key | Aappend the Tag name to the final record. | Off |
+| Include\_Tag\_Key | Append the Tag name to the final record. | Off |
 | Tag\_Key | If Include\_Tag\_Key is enabled, this property defines the key name for the tag. | \_flb-key |
 
 ### TLS / SSL

output/splunk.md

@@ -55,7 +55,7 @@ In your main configuration file append the following _Input_ & _Output_ sections
 
 By default, the Splunk output plugin nests the record under the `event` key in the payload sent to the HEC. It will also append the time of the record to a top level `time` key.
 
-If you would like to customize any of the Splunk event metadata, such as the host or target index, you can set `Splunk_Send_Raw On` in the plugin configuraiton, and add the metadata as keys/values in the record. *Note*: with `Splunk_Send_Raw` enabled, you are responsible for creating and populating the `event` section of the payload.
+If you would like to customize any of the Splunk event metadata, such as the host or target index, you can set `Splunk_Send_Raw On` in the plugin configuration, and add the metadata as keys/values in the record. *Note*: with `Splunk_Send_Raw` enabled, you are responsible for creating and populating the `event` section of the payload.
 
 For example, to add a custom index and hostname: