diff --git a/concepts/data-pipeline/output.md b/concepts/data-pipeline/output.md
index 2fad550bd..d341a67f0 100644
--- a/concepts/data-pipeline/output.md
+++ b/concepts/data-pipeline/output.md
@@ -1,10 +1,12 @@
 ---
-description: 'Destinations for your data: databases, cloud services and more!'
+description: Learn about destinations for your data, such as databases and cloud services.
 ---
 
 # Output
 
-The output interface allows us to define destinations for the data. Common destinations are remote services, local file system or standard interface with others. Outputs are implemented as plugins and there are many available.
+The output interface lets you define destinations for your data. Common destinations
+are remote services, local file systems, or other standard interfaces. Outputs are
+implemented as plugins.
 
 ```mermaid
 graph LR
@@ -22,8 +24,10 @@ graph LR
     style H stroke:darkred,stroke-width:2px;
 ```
 
-When an output plugin is loaded, an internal _instance_ is created. Every instance has its own independent configuration. Configuration keys are often called **properties**.
+When an output plugin is loaded, an internal _instance_ is created. Every instance
+has its own independent configuration. Configuration keys are often called
+_properties_.
 
 Every output plugin has its own documentation section specifying how it can be used and what properties are available.
 
-For more details, please refer to the [Output Plugins](https://docs.fluentbit.io/manual/pipeline/outputs) section.
+For more details, see [Output Plugins](https://docs.fluentbit.io/manual/pipeline/outputs).