Apply suggestions from code review

Co-authored-by: Adam Locke <[email protected]>
Signed-off-by: esmerel <[email protected]>

Author: esmerel

administration/troubleshooting.md

@@ -24,7 +24,7 @@ $ docker run --rm -ti fluent/fluent-bit:latest --help | grep trace
 ```
 
 If the `--enable-chunk-trace` option is present, your Fluent Bit version supports
-Fluent Bit Tap but it's disabled by default. Use this option to enable it.
+Fluent Bit Tap, but it's disabled by default. Use this option to enable it.
 
 You can start Fluent Bit with tracing activated from the beginning by using the
 `trace-input` and `trace-output` properties:
@@ -127,11 +127,11 @@ All three options can also be defined using the more flexible `--trace` option:
 fluent-bit -Z -i dummy -o stdout -f 1 --trace="input=dummy.0 output=stdout output.format=json_lines"
 ```
 
-This example defines the tap pipeline using this configuration: `input=dummy.0 output=stdout output.format=json_lines` which defines the following:
+This example defines the Tap pipeline using this configuration: `input=dummy.0 output=stdout output.format=json_lines` which defines the following:
 
-- `input`: `dummy.0` - listens to the tag or alias `dummy.0`
-- `output`: `stdout` - outputs to a stdout plugin
-- `output.format`: `json_lines` - sets the stdout format to `json_lines`
+- `input`: `dummy.0` listens to the tag or alias `dummy.0`.
+- `output`: `stdout` outputs to a stdout plugin.
+- `output.format`: `json_lines` sets the stdout format to `json_lines`.
 
 Tap support can also be activated and deactivated using the embedded web server:
 
@@ -263,8 +263,8 @@ When activating Tap, any plugin parameter can be given. These parameters can be
 to modify the output format, the name of the time key, the format of the date, and
 other details.
 
-The following example uses the parameter ```"format": "json"``` to demonstrate how
-to show `stdout` in `JSON` format.
+The following example uses the parameter `"format": "json"` to demonstrate how
+to show `stdout` in JSON format.
 
 First, run Fluent Bit enabling Tap:
 
@@ -338,7 +338,7 @@ This filter record is an example to explain the details of a Tap record:
 
 - `type`: Defines the stage the event is generated:
   - `1`: Input record. This is the unadulterated input record.
-  - `2`: Filtered record. This is a record once it has been filtered. One record is
+  - `2`: Filtered record. This is a record after it was filtered. One record is
     generated per filter.
   - `3`: Pre-output record. This is the record right before it's sent for output.
 
@@ -380,7 +380,7 @@ Run the following `kill` command to signal Fluent Bit:
 kill -CONT `pidof fluent-bit`
 ```
 
-The command `pidof` aims to lookup the Process ID of Fluent Bit.
+The command `pidof` aims to identify the Process ID of Fluent Bit.
 
 Fluent Bit will dump the following information to the standard output interface
 (`stdout`):
@@ -444,9 +444,9 @@ The Task dump describes the tasks associated to the input plugin:
 | Entry | Description |
 | :--- | :--- |
 | `total_tasks` | Total number of active tasks associated to data generated by the input plugin. |
-| `new` | Number of tasks not assigned yet to an output plugin. Tasks are in `new` status for a very short period of time. This value is normally very low or zero. |
+| `new` | Number of tasks not yet assigned to an output plugin. Tasks are in `new` status for a very short period of time. This value is normally very low or zero. |
 | `running` | Number of active tasks being processed by output plugins. |
-| `size` | Amount of memory used by the Chunks being processed (Total chunks size). |
+| `size` | Amount of memory used by the Chunks being processed (total chunk size). |
 
 ### Chunks