From 66d8e589b0474ef472a3f162c2f5eb4b15142e04 Mon Sep 17 00:00:00 2001 From: Lynette Miles Date: Thu, 24 Oct 2024 11:39:49 -0700 Subject: [PATCH 1/2] Fluentbit: docs: Update input concept for style Signed-off-by: Lynette Miles --- concepts/data-pipeline/input.md | 13 +++++++++---- 1 file changed, 9 insertions(+), 4 deletions(-) diff --git a/concepts/data-pipeline/input.md b/concepts/data-pipeline/input.md index 0779c0985..2aa6de262 100644 --- a/concepts/data-pipeline/input.md +++ b/concepts/data-pipeline/input.md @@ -4,7 +4,10 @@ description: The way to gather data from your sources # Input -[Fluent Bit](http://fluentbit.io) provides different _Input Plugins_ to gather information from different sources, some of them just collect data from log files while others can gather metrics information from the operating system. There are many plugins for different needs. +[Fluent Bit](http://fluentbit.io) provides input plugins to gather information from +different sources. Some plugins collect data from log files, while others can +gather metrics information from the operating system. There are many plugins for +different needs. ```mermaid graph LR @@ -20,8 +23,10 @@ graph LR style A stroke:darkred,stroke-width:2px; ``` -When an input plugin is loaded, an internal _instance_ is created. Every instance has its own and independent configuration. Configuration keys are often called **properties**. +When an input plugin loads, an internal _instance_ is created. Each instance has its +own independent configuration. Configuration keys are often called _properties_. -Every input plugin has its own documentation section where it's specified how it can be used and what properties are available. +Every input plugin has its own documentation section where it's specified how it can +be used and what properties are available. -For more details, please refer to the [Input Plugins](https://docs.fluentbit.io/manual/pipeline/inputs) section. +For more details, see [Input Plugins](https://docs.fluentbit.io/manual/pipeline/inputs). From 7fff8516589dab091c1081abf91eaffbf6389809 Mon Sep 17 00:00:00 2001 From: esmerel <6818907+esmerel@users.noreply.github.com> Date: Fri, 25 Oct 2024 09:00:48 -0700 Subject: [PATCH 2/2] Apply suggestions from code review Co-authored-by: Alexa Kreizinger Signed-off-by: esmerel <6818907+esmerel@users.noreply.github.com> --- concepts/data-pipeline/input.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/concepts/data-pipeline/input.md b/concepts/data-pipeline/input.md index 2aa6de262..20f73ddcf 100644 --- a/concepts/data-pipeline/input.md +++ b/concepts/data-pipeline/input.md @@ -6,7 +6,7 @@ description: The way to gather data from your sources [Fluent Bit](http://fluentbit.io) provides input plugins to gather information from different sources. Some plugins collect data from log files, while others can -gather metrics information from the operating system. There are many plugins for +gather metrics information from the operating system. There are many plugins to suit different needs. ```mermaid @@ -26,7 +26,7 @@ graph LR When an input plugin loads, an internal _instance_ is created. Each instance has its own independent configuration. Configuration keys are often called _properties_. -Every input plugin has its own documentation section where it's specified how it can -be used and what properties are available. +Every input plugin has its own documentation section that specifies how to use it +and what properties are available. For more details, see [Input Plugins](https://docs.fluentbit.io/manual/pipeline/inputs).