Apply suggestions from code review

Co-authored-by: Garrett Guillotte <gguillotte@users.noreply.github.com>
Signed-off-by: Lynette  Miles <6818907+esmerel@users.noreply.github.com>

Author: esmerel

pipeline/filters/expect.md

@@ -1,12 +1,12 @@
 ---
-description: Testing your records for expected key and values
+description: Testing records to ensure they contain an expected key and values
 ---
 
 # Expect
 
 The _expect_ filter plugin lets you validate that records match certain criteria in their structure, like validating that a key exists or it has a specific value.
 
-For a detailed explanation of its usage and use cases, refer to [Validating and your Data and Structure](../../local-testing/validating-your-data-and-structure.md).
+For a detailed explanation of its usage and use cases, see [Validating and your Data and Structure](../../local-testing/validating-your-data-and-structure.md).
 
 ## Configuration parameters
 
@@ -20,4 +20,4 @@ The plugin supports the following configuration parameters:
 | `key_val_is_not_null` | Check that the value of the key is `NOT NULL`. |
 | `key_val_eq` | Check that the value of the key equals the given value in the configuration. |
 | `action` | Action to take when a rule doesn't match. Available options are `warn` , `exit` or `result_key`. On `warn`, a warning message is sent to the logging layer when a mismatch of the `key*` rules is found. Using `exit` makes Fluent Bit exit with status code `255`. `result_key` adds a matching result to each record. |
-| `result_key` | Specify a key name of matching result. Used only when `action` is `result_key`.|
+| `result_key` | Specify a key name for the matching result added when `action` is set to `result_key`. |