Updates: Reviewed the language and grammar changes.

Signed-off-by: Azeem Sajid <azeem.sajid@gmail.com>

Author: iamazeem

README.md

@@ -2,9 +2,9 @@
 
 ![](.gitbook/assets/images/logo_documentation_1.0.png)
 
-[Fluentd](https://www.fluentd.org/) is an open-source data collector for unified
-logging layer. Fluentd allows you to unify data collection and consumption for a
-better use and understanding of data.
+[Fluentd](https://www.fluentd.org/) is an open-source data collector for a
+unified logging layer. Fluentd allows you to unify data collection and
+consumption for better use and understanding of data.
 
 [Fluentd](https://www.fluentd.org/) is licensed under the terms of the
 [Apache License v2.0](http://www.apache.org/licenses/LICENSE-2.0). This project

configuration/buffer-section.md

@@ -6,7 +6,7 @@ of events. The buffering is handled by the Fluentd core.
 
 ## Buffer Section Overview
 
-Buffer section comes under `<match>` section. It is enabled for those output
+Buffer section comes under the `<match>` section. It is enabled for those output
 plugins that support buffered output features.
 
 ```
@@ -42,7 +42,7 @@ Third-party plugins may also be installed and configured.
 
 However, the `@type` parameter is not mandatory. If omitted, by default, the
 buffer plugin specified by the output plugin is used (if possible). Otherwise,
-`memory` buffer plugin is used.
+the `memory` buffer plugin is used.
 
 For the usual workload, the file buffer plugin is recommended. It is more
 durable for the general use-cases.
@@ -130,7 +130,7 @@ For example:
   "13:59:59"]`, ...
 
 The events will be grouped into chunks by their time range. They will be flushed
-by the output plugin after expiration of the time key range.
+by the output plugin after the expiration of the time key range.
 
 ```
 <match tag.**>
@@ -324,8 +324,8 @@ Same with chunk keys:
 
 ### Argument
 
-Argument is an array of chunk keys that must be a list of comma-separated
-strings. It can also be left as blank.
+It is an array of chunk keys that must be a list of comma-separated strings. It
+can also be left blank.
 
 ```
 <buffer> # blank

configuration/config-file.md

@@ -40,7 +40,7 @@ Sending a `SIGHUP` signal will reload the config file.
 
 ### Docker
 
-For a Docker container, the default location of config file is
+For a Docker container, the default location of the config file is
 `/fluentd/etc/fluent.conf`. To mount a config file from outside of Docker, use a
 `bind-mount`.
 
@@ -71,7 +71,7 @@ The configuration file consists of the following directives:
 1.  **`source`** directives determine the input sources
 2.  **`match`** directives determine the output destinations
 3.  **`filter`** directives determine the event processing pipelines
-4.  **`system`** directives set system wide configuration
+4.  **`system`** directives set system-wide configuration
 5.  **`label`** directives group the output and filter for internal routing
 6.  **`@include`** directives include other files
 
@@ -115,7 +115,7 @@ and it must be in the Unix time format. The `record` is a JSON object.
 
 Fluentd accepts all non-period characters as a part of a `tag`. However, since
 the `tag` is sometimes used in a different context by output destinations (e.g.
-table name, database name, key name, etc.), **it is strongly recommended that
+the table name, database name, key name, etc.), **it is strongly recommended that
 you stick to the lower-case alphabets, digits and underscore** (e.g.
 `^[a-z0-9_]+$`).
 
@@ -173,7 +173,7 @@ destination (in the above example, only the events with the tag `myapp.access`
 are matched. See [the section below for more advanced usage](#how-match-patterns-work)).
 The `@type` parameter specifies the output plugin to use.
 
-Just like input sources, you can add new output destinations by writing your own
+Just like input sources, you can add new output destinations by writing custom
 plugins. For further information regarding Fluentd output destinations, please
 refer to the [Output Plugin Overview](/plugins/output/README.md) article.
 
@@ -219,9 +219,9 @@ information regarding Fluentd filter destinations, please refer to the
 [Filter Plugin Overview](/plugins/filter/README.md) article.
 
 
-## 4. Set system wide configuration: the "system" directive
+## 4. Set system-wide configuration: the `system` directive
 
-System-wide configurations are set by **system** directive. Most of them are
+System-wide configurations are set by `system` directive. Most of them are
 also available via command line options. For example, the following
 configurations are available:
 
@@ -316,7 +316,8 @@ In this configuration, `forward` events are routed to `record_transformer`
 filter / `elasticsearch` output and `in_tail` events are routed to `grep` filter
 / `s3` output inside `@SYSTEM` label.
 
-The `label` parameter is useful for event flow separation without `tag` prefix.
+The `label` parameter is useful for event flow separation without the `tag`
+prefix.
 
 
 ### `@ERROR` label
@@ -325,10 +326,10 @@ The `@ERROR` label is a builtin label used for error record emitted by plugin's
 `emit_error_event` API.
 
 If `<label @ERROR>` is set, the events are routed to this label when the related
-errors are emitted e.g. buffer is full or invalid record.
+errors are emitted e.g. the buffer is full or the record is invalid.
 
 
-## 6. Reuse your config: the "@include" directive
+## 6. Reuse your config: the `@include` directive
 
 The directives in separate configuration files can be imported using the
 **@include** directive:
@@ -537,7 +538,7 @@ defined as follows:
     -   `<INTEGER>m` or `<INTEGER>M`: number of megabytes
     -   `<INTEGER>g` or `<INTEGER>G`: number of gigabytes
     -   `<INTEGER>t` or `<INTEGER>T`: number of terabytes
-    -   Otherwise, the field is parsed as integer, and that integer is the
+    -   Otherwise, the field is parsed as an integer, and that integer is the
         **number of bytes**.
 -   `time`: the field is parsed as a time duration.
     -   `<INTEGER>s`: seconds
@@ -548,11 +549,11 @@ defined as follows:
         **number of seconds**. This option is useful for specifying sub-second
         time durations such as 0.1 (0.1 second = 100 milliseconds).
 -   `array`: the field is parsed as a JSON array. It also supports the shorthand
-    syntax. These are same values:
+    syntax. These are the same values:
     -   normal: `["key1", "key2"]`
     -   shorthand: `key1,key2`
 -   `hash`: the field is parsed as a JSON object. It also supports the shorthand
-    syntax. These are same values:
+    syntax. These are the same values:
     -   normal: `{"key1": "value1", "key2": "value2"}`
     -   shorthand: `key1:value1,key2:value2`
 
@@ -654,7 +655,7 @@ host_param  "#{hostname}"  # This is same with Socket.gethostname
 ```
 
 The `worker_id` shortcut is useful under multiple workers. For example, for a
-separate plugin id, add `worker_id` to store path in s3 to avoid file conflict.
+separate plugin id, add `worker_id` to store the path in s3 to avoid file conflict.
 
 Since v1.8.0, helper methods `use_nil` and `use_default` are available:
 
@@ -674,7 +675,7 @@ The `config-xxx` mixins use `"${}"`, not `"#{}"`. These embedded configurations
 are two different things.
 
 
-### In double quoted string literal, `\` is escape character
+### In double-quoted string literal, `\` is the escape character
 
 The forward slash `\` is interpreted as an escape character. You need `\` for
 setting `"`, `\r`, `\n`, `\t`, `\` or several characters in double-quoted string

configuration/parse-section.md

@@ -70,7 +70,7 @@ Here's the list of built-in parser plugins:
 The default value of the following parameters will be overridden by the
 individual parser plugins:
 
--   **`types`** (hash) (optional): Specify types for converting field into other
+-   **`types`** (hash) (optional): Specify types for converting field into another
     type. See below "The detail of types parameter" section.
     -   Default: `nil`
     -   string-based hash: `field1:type, field2:type, field3:type:option,
@@ -103,15 +103,15 @@ individual parser plugins:
 
 #### `types` Parameter
 
-For `types` parameter, the following types are supported:
+For the `types` parameter, the following types are supported:
 
 - `string`: Converts the field into `String` type. This uses `to_s` method for
   conversion.
 
 - `bool`: Converts the string `"true"`, `"yes"` or `"1"` into `true`. Otherwise,
   `false`.
 
-- `integer` (not `int`): Converts the field into `Integer` type. This uses
+- `integer` (not `int`): Converts the field into the `Integer` type. This uses
   `to_i` method for conversion. For example, the string `"1000"` converts into
   `1000`.
 

configuration/plugin-common-parameters.md

@@ -104,7 +104,7 @@ set of the `<filter>` and `<match>` subsections under `<label>`.
 </label>
 ```
 
-NOTE: The values for `@label` parameter MUST start with `@` character.
+NOTE: The values for the `@label` parameter MUST start with `@` character.
 
 Specifying `@label` is strongly recommended to route events to any plugin
 without modifying the tags. It helps make the complex configuration modular and

configuration/routing-examples.md

@@ -92,7 +92,7 @@ Label reduces complex `tag` handling by separating data pipelines.
 ## Reroute Event by Tag
 
 Use [fluent-plugin-route](https://github.com/tagomoris/fluent-plugin-route)
-plugin. This plugin rewrites `tag` and re-emit events to other match or Label.
+plugin. This plugin rewrites `tag` and re-emit events to other `match` or Label.
 
 ```
 <match worker.**>

configuration/service_discovery-section.md

@@ -1,6 +1,6 @@
 # Service Discovery Section Configurations
 
-Some of Fluentd plugins support the `<service_discovery>` section to set the
+Some of the Fluentd plugins support the `<service_discovery>` section to set the
 target nodes dynamically.
 
 ## Service Discovery Section Overview
@@ -40,7 +40,7 @@ For more details, see plugins documentation.
 
 ### `@type`
 
-The `@type` parameter specifies the type of the service discovery plugin.
+The `@type` parameter specifies the type of service discovery plugin.
 
 ```
 <service_discovery>

configuration/transport-section.md

@@ -50,7 +50,7 @@ sections. It specifies the transport protocol, version, and certificates.
     -   Default: `false` (uses secure connection with `tls`)
 
 If you want to accept multiple TLS protocols, use `min_version`/`max_version`
-instead of `version`. To support old style, fluentd accepts `TLS1_1` and
+instead of `version`. To support the old style, fluentd accepts `TLS1_1` and
 `TLSv1_1` values.
 
 NOTE: `TLS1_3` is available when your system supports TLS 1.3.

container-deployment/docker-compose.md

@@ -86,7 +86,7 @@ services:
 
 The `logging` section (check [Docker Compose documentation](https://docs.docker.com/compose/compose-file/#/logging))
 of `web` container specifies [Docker Fluentd Logging Driver](https://docs.docker.com/engine/admin/logging/fluentd/)
-as a default container logging driver. All the logs from `web` container will
+as a default container logging driver. All the logs from the `web` container will
 automatically be forwarded to `host:port` specified by `fluentd-address`.
 
 
@@ -96,7 +96,7 @@ Create `fluentd/Dockerfile` with the following content using the Fluentd
 [official Docker image](https://hub.docker.com/r/fluent/fluentd/); and then,
 install the Elasticsearch plugin:
 
-``` {.CodeRay}
+```
 # fluentd/Dockerfile
 
 FROM fluent/fluentd:v1.6-debian-1
@@ -110,7 +110,7 @@ Then, create the Fluentd configuration file `fluentd/conf/fluent.conf`. The
 Docker logging driver and `elasticsearch` output plugin forwards these logs to
 Elasticsearch.
 
-``` {.CodeRay}
+```
 # fluentd/conf/fluent.conf
 
 <source>
@@ -190,7 +190,7 @@ Specify `fluentd-*` to `Index name or pattern` and click `Create`.
 Timestamp](/images/7.2_efk-kibana-timestamp.png)
 
 Then, go to `Discover` tab to check the logs. As you can see, logs are properly
-collected into Elasticsearch + Kibana, via Fluentd.
+collected into the Elasticsearch + Kibana, via Fluentd.
 
 ![Kibana Discover](/images/7.2_efk-kibana-discover.png)
 

container-deployment/docker-logging-driver.md

@@ -10,8 +10,8 @@ over the registers, or on the other hand, if the application has multiple
 instances running, the scenario becomes even more complex.
 
 On Docker v1.6, the concept of **[logging drivers](https://docs.docker.com/engine/admin/logging/overview/)**
-was introduced. Basically, the Docker engine is aware about the output
-interfaces that manage the application messages.
+was introduced. The Docker engine is aware of the output interfaces that manage
+the application messages.
 
 ![Fluentd Docker](https://www.fluentd.org/assets/img/recipes/fluentd_docker.png)
 
@@ -20,7 +20,7 @@ For Docker v1.8, we have implemented a native
 Now, you are able to have a unified and structured logging system with the
 simplicity and high performance of [Fluentd](http://fluentd.org).
 
-NOTE: Currently, Fluentd logging driver doesn't support sub-second precision.
+NOTE: Currently, the Fluentd logging driver doesn't support sub-second precision.
 
 
 ## Getting Started
@@ -129,8 +129,8 @@ information from the source container along with the message.
 
 ### Additional Step 1: Parse Log Message
 
-Application log is stored in the `"log"` field in the record. You can parse this
-log before sending it to the destinations by using
+The application log is stored in the `"log"` field in the record. You can parse
+this log before sending it to the destinations by using
 [`filter_parser`](/plugins/filter/parser.md).
 
 ``` {.CodeRay}
@@ -159,8 +159,8 @@ Filtered Event:
 
 ### Additional Step 2: Concatenate Multiple Lines Log Messages
 
-Application log is stored in the `log` field of the record. You can concatenate
-these logs by using
+The application log is stored in the `log` field of the record. You can
+concatenate these logs by using
 [`fluent-plugin-concat`](https://github.com/fluent-plugins-nursery/fluent-plugin-concat)
 filter before sending it to the destinations.
 
@@ -184,7 +184,7 @@ Original Events:
 
 Filtered Events:
 
-``` {.CodeRay}
+```
 2016-04-13 14:45:55 +0900 docker.28cf38e21204: {"container_id":"28cf38e212042225f5f80a56fac08f34c8f0b235e738900c4e0abcf39253a702","container_name":"/romantic_dubinsky","source":"stdout","log":"-e:2:in `/'\n-e:2:in `do_division_by_zero'\n-e:4:in `<main>'"}
 ```
 
@@ -197,7 +197,7 @@ plugin instead.
 
 The [Fluentd Logging
 Driver](https://docs.docker.com/engine/admin/logging/fluentd/) supports
-following options through the `--log-opt` Docker command line argument:
+following options through the `--log-opt` Docker command-line argument:
 
 - `fluentd-address`
 - `tag`
@@ -229,7 +229,7 @@ $ docker run --log-driver=fluentd --log-opt tag=docker.my_new_tag ubuntu echo ".
 Additionally, this option allows to specify some internal variables such as
 `{{.ID}}`, `{{.FullID}}` or `{{.Name}}` like this:
 
-``` {.CodeRay}
+```
 $ docker run --log-driver=fluentd --log-opt tag=docker.{{.ID}} ubuntu echo "..."
 ```
 
@@ -238,7 +238,7 @@ $ docker run --log-driver=fluentd --log-opt tag=docker.{{.ID}} ubuntu echo "..."
 
 For a real-world use-case, you would want to use something other than the
 Fluentd standard output to store Docker container messages, such as
-Elasticsearch, MongoDB, HDFS, S3, Google Cloud Storage and so on.
+Elasticsearch, MongoDB, HDFS, S3, Google Cloud Storage, and so on.
 
 This document describes how to set up a multi-container logging environment via
 EFK (Elasticsearch, Fluentd, Kibana) with Docker Compose.