Apply suggestions from code review

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

concepts/data-pipeline/filter.md

@@ -4,7 +4,7 @@ description: Modify, enrich or drop your records
 
 # Filter
 
-In production environments you want to have full control of the data being collected.
+In production environments you need full control of the data you're collecting.
 Filtering lets you alter the collected data before delivering it to a destination.
 
 ```mermaid
@@ -21,11 +21,11 @@ graph LR
     style C stroke:darkred,stroke-width:2px;
 ```
 
-Filtering is implemented through plugins. Each available filter could be used to
-match, exclude or enrich your logs with specific metadata.
+Filtering is implemented through plugins. Each available filter can be used to
+match, exclude, or enrich your logs with specific metadata.
 
 Fluent Bit support many filters. A common use case for filtering is Kubernetes
-deployments. Every pod log needs the proper metadata associated.
+deployments. Every pod log needs the proper metadata associated with it.
 
 Like input plugins, filters run in an instance context, which has its own independent
 configuration. Configuration keys are often called _properties_.