Apply suggestions from code review

Co-authored-by: Craig Norris <[email protected]>
Signed-off-by: Alexa Kreizinger <[email protected]>

Author: alexakreizinger

pipeline/parsers/decoders.md

@@ -1,6 +1,6 @@
 # Decoders
 
-There are cases where the log messages that you want to parse contain encoded data. A typical use case can be found in containerized environments with Docker. Docker logs its data in JSON format, which uses escaped strings.
+There are cases where the log messages you want to parse contain encoded data. A typical use case can be found in containerized environments with Docker. Docker logs its data in JSON format, which uses escaped strings.
 
 Consider the following message generated by the application:
 
@@ -14,11 +14,11 @@ The Docker log message encapsulates something like this:
 {"log":"{\"status\": \"up and running\"}\r\n","stream":"stdout","time":"2018-03-09T01:01:44.851160855Z"}
 ```
 
-The original message is handled as an escaped string. Fluent Bit wants to use the original structured message and not a string.
+The original message is handled as an escaped string. Fluent Bit will use the original structured message, and not a string.
 
 ## Get started
 
-Decoders are a built-in feature of parsers in Fluent Bit. Each parser definition can optionally set one or more decoders. There are two types of decoders:
+Decoders are a built-in feature of parsers in Fluent Bit. Each parser definition can optionally set one or more decoders. Select from one of these decoder types:
 
 - `Decode_Field`: If the content can be decoded in a structured message, append
   the structured message (keys and values) to the original log message.
@@ -82,7 +82,7 @@ If a decoder fails to decode the field, or if you want to try another decoder, y
 Actions are affected by some restrictions:
 
 - `Decode_Field_As`: If successful, another decoder of the same type and the same field can be applied only if the data continues being an unstructured message (raw text).
-- `Decode_Field`: If successful, can only be applied once for the same field. `Decode_Field` is intended to decode a structured message.
+- `Decode_Field`: If successful, can be applied only once for the same field. `Decode_Field` is intended to decode a structured message.
 
 ### Examples