Apply suggestions from code review

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

Author: esmerel

pipeline/parsers/decoders.md

@@ -2,7 +2,7 @@
 
 There are cases where the log messages being parsed 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.
+data in JSON format, which uses escaped strings.
 
 Consider the following message generated by the application:
 
@@ -27,7 +27,7 @@ definition can optionally set one or more decoders. There are two types of decod
 - `Decode_Field`: If the content can be decoded in a structured message, append
   the structured message (keys and values) to the original log message.
 - `Decode_Field_As`: Any decoded content (unstructured or structured) will be
-  replaced in the same key/value, no extra keys are added.
+  replaced in the same key/value, and no extra keys are added.
 
 Our pre-defined Docker parser has the following definition:
 
@@ -45,7 +45,7 @@ Our pre-defined Docker parser has the following definition:
 
 Each line in the parser with a key `Decode_Field` instructs the parser to apply
 a specific decoder on a given field. Optionally, it offers the option to take an
-extra action if the decoder can't succeed.
+extra action if the decoder doesn't succeed.
 
 ### Decoder options