Skip to content

Commit b6c1825

Browse files
authored
Merge pull request #1487 from fluent/lynettemiles/sc-105699/update-concepts-data-pipeline-output-md-fluent
2 parents 1de2cbe + a843fbd commit b6c1825

File tree

1 file changed

+8
-4
lines changed

1 file changed

+8
-4
lines changed

concepts/data-pipeline/output.md

Lines changed: 8 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,10 +1,12 @@
11
---
2-
description: 'Destinations for your data: databases, cloud services and more!'
2+
description: Learn about destinations for your data, such as databases and cloud services.
33
---
44

55
# Output
66

7-
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.
7+
The output interface lets you define destinations for your data. Common destinations
8+
are remote services, local file systems, or other standard interfaces. Outputs are
9+
implemented as plugins.
810

911
```mermaid
1012
graph LR
@@ -22,8 +24,10 @@ graph LR
2224
style H stroke:darkred,stroke-width:2px;
2325
```
2426

25-
When an output plugin is loaded, an internal _instance_ is created. Every instance has its own independent configuration. Configuration keys are often called **properties**.
27+
When an output plugin is loaded, an internal _instance_ is created. Every instance
28+
has its own independent configuration. Configuration keys are often called
29+
_properties_.
2630

2731
Every output plugin has its own documentation section specifying how it can be used and what properties are available.
2832

29-
For more details, please refer to the [Output Plugins](https://docs.fluentbit.io/manual/pipeline/outputs) section.
33+
For more details, see [Output Plugins](https://docs.fluentbit.io/manual/pipeline/outputs).

0 commit comments

Comments
 (0)