remove/move placeholder info

Signed-off-by: Alexa Kreizinger <alexakreizinger@gmail.com>

Author: alexakreizinger

administration/configuring-fluent-bit/yaml.md

@@ -20,41 +20,3 @@ YAML configuration files support the following top-level sections:
 {% hint style="info" %}
 YAML configuration is used in the smoke tests for containers. An always-correct up-to-date example is here: <https://github.com/fluent/fluent-bit/blob/master/packaging/testing/smoke/container/fluent-bit.yaml>.
 {% endhint %}
-
-----
-
-
-## List of available sections
-
-Configuring Fluent Bit with YAML introduces the following root-level sections:
-
-| Section Name | Description |
-|--------------|-------------|
-| `service` | Describes the global configuration for the Fluent Bit service. Optional. If not set, default values will apply. Only one `service` section can be defined. |
-| `parsers` | Lists parsers to be used by components like inputs, processors, filters, or output plugins. You can define multiple `parsers` sections, which can also be loaded from external files included in the main YAML configuration. |
-| `multiline_parsers`  | Lists multiline parsers, functioning similarly to `parsers`. Multiple definitions can exist either in the root or in included files. |
-| `pipeline` | Defines a pipeline composed of inputs, processors, filters, and output plugins. You can define multiple `pipeline` sections, but they won't operate independently. Instead, all components will be merged into a single pipeline internally. |
-| `plugins` | Specifies the path to external plugins (`.so` files) to be loaded by Fluent Bit at runtime. |
-| `upstream_servers` | Refers to a group of node endpoints that can be referenced by output plugins that support this feature. |
-| `env` | Sets a list of environment variables for Fluent Bit. System environment variables are available, while the ones defined in the configuration apply only to Fluent Bit. |
-
-## Section documentation
-
-To access detailed configuration guides for each section, use the following links:
-
-- [Service Section documentation](./yaml/service-section.md)
-  - Overview of global settings, configuration options, and examples.
-- [Parsers Section documentation](./yaml/parsers-section.md)
-  - Detailed guide on defining parsers and supported formats.
-- [Multiline Parsers Section documentation](./yaml/multiline-parsers-section.md)
-  - Explanation of multiline parsing configuration.
-- [Pipeline Section documentation](./yaml/pipeline-section.md)
-  - Details on setting up pipelines and using processors.
-- [Plugins Section documentation](./yaml/plugins-section.md)
-  - How to load external plugins.
-- [Upstream Servers Section documentation](./yaml/upstream-servers-section.md)
-  - Guide on setting up and using upstream nodes with supported plugins.
-- [Environment Variables Section documentation](./yaml/environment-variables-section.md)
-  - Information on setting environment variables and their scope within Fluent Bit.
-- [Includes Section documentation](./yaml/includes-section.md)
-  - Description on how to include external YAML files.

administration/configuring-fluent-bit/yaml/pipeline-section.md

@@ -16,7 +16,7 @@ Unlike filters, processors and parsers aren't defined within a unified section o
 
 ## Format
 
-A `pipeline` section will define a complete pipeline configuration, including `inputs`, `filters`, and `outputs` subsections.
+A `pipeline` section will define a complete pipeline configuration, including `inputs`, `filters`, and `outputs` subsections. You can define multiple `pipeline` sections, but they won't operate independently. Instead, all components will be merged into a single pipeline internally.
 
 ```yaml
 pipeline: