Fixing links

Signed-off-by: Lynette Miles <[email protected]>

Author: esmerel

administration/configuring-fluent-bit/yaml.md

@@ -26,19 +26,19 @@ Configuring Fluent Bit with YAML introduces the following root-level sections:
 
 To access detailed configuration guides for each section, use the following links:
 
-- [Service Section documentation](service-section.md)
+- [Service Section documentation](./yaml/service-section.md)
   - Overview of global settings, configuration options, and examples.
-- [Parsers Section documentation](parsers-section.md)
+- [Parsers Section documentation](./yaml/parsers-section.md)
   - Detailed guide on defining parsers and supported formats.
-- [Multiline Parsers Section documentation](multiline-parsers-section.md)
+- [Multiline Parsers Section documentation](./yaml/multiline-parsers-section.md)
   - Explanation of multiline parsing configuration.
-- [Pipeline Section documentation](pipeline-section.md)
+- [Pipeline Section documentation](./yaml/pipeline-section.md)
   - Details on setting up pipelines and using processors.
-- [Plugins Section documentation](plugins-section.md)
+- [Plugins Section documentation](./yaml/plugins-section.md)
   - How to load external plugins.
-- [Upstream Servers Section documentation](upstream-servers-section.md)
+- [Upstream Servers Section documentation](./yaml/upstream-servers-section.md)
   - Guide on setting up and using upstream nodes with supported plugins.
-- [Environment Variables Section documentation](environment-variables-section.md)
+- [Environment Variables Section documentation](./yaml/environment-variables-section.md)
   - Information on setting environment variables and their scope within Fluent Bit.
-- [Includes Section documentation](includes-section.md)
+- [Includes Section documentation](./yaml/includes-section.md)
   - Description on how to include external YAML files.

installation/linux.md

@@ -29,7 +29,7 @@ The GPG Key fingerprint of the old key is:
 F209 D876 2A60 CD49 E680 633B 4FF8 368B 6EA0 722A
 ```
 
-Refer to the [supported platform documentation](./../supported-platforms.md) to see which platforms are supported in each release.
+Refer to the [supported platform documentation](supported-platforms.md) to see which platforms are supported in each release.
 
 ## Migration to Fluent Bit
 

installation/sources/build-with-static-configuration.md

@@ -12,7 +12,7 @@ The following steps assume you are familiar with configuring Fluent Bit using te
 
 #### Configuration directory
 
-In your file system, prepare a specific directory that will be used as an entry point for the build system to lookup and parse the configuration files. This directory must contain a minimum of one configuration file, called `fluent-bit.conf`, that contains the required [`SERVICE`](/administration/configuring-fluent-bit/yaml/service-section.md), [`INPUT`](../../pipeline/input.md), and [`OUTPUT`](../../pipeline/output.md) sections.
+In your file system, prepare a specific directory that will be used as an entry point for the build system to lookup and parse the configuration files. This directory must contain a minimum of one configuration file, called `fluent-bit.conf`, that contains the required [`SERVICE`](/administration/configuring-fluent-bit/yaml/service-section.md), [`INPUT`](../../pipeline/inputs.md), and [`OUTPUT`](../../pipeline/outputs.md) sections.
 
 As an example, create a new `fluent-bit.yaml` file or `fluent-bit.conf` file:
 

pipeline/outputs/logdna.md

@@ -18,7 +18,7 @@ This plugin uses the following configuration parameters:
 | `tags` | A list of comma-separated strings to group records in LogDNA and simplify the query with filters. | _none_ |
 | `file` | Optional name of a file being monitored. This value is only set if the record doesn't contain a reference to it. | _none_ |
 | `app` | Name of the application. This value is automatically discovered on each record. If no value is found, the default value is used. | `Fluent Bit` |
-| `workers` | The number of [workers](../../administration/multithreading#outputs) to perform flush operations for this output. | `0` |
+| `workers` | The number of [workers](../../administration/multithreading.md#outputs) to perform flush operations for this output. | `0` |
 
 ## Data discovery and enrichment
 

pipeline/processors.md

@@ -14,16 +14,16 @@ Only [YAML configuration files](../../administration/configuring-fluent-bit/yaml
 
 Fluent Bit offers the following processors:
 
-- [Content modifier](content-modifier.md): Manipulate the content, metadata, and attributes of logs and traces.
-- [Labels](labels.md): Add, update, or delete metric labels.
-- [Metrics selector](metrics-selector.md): Choose which metrics to keep or discard.
-- [OpenTelemetry envelope](opentelemetry-envelope.md): Transform logs into an OpenTelemetry-compatible format.
-- [Sampling](sampling.md): Apply head or tail sampling to incoming traces.
-- [SQL](sql.md): Use SQL queries to extract log content.
+- [Content modifier](./processors/content-modifier.md): Manipulate the content, metadata, and attributes of logs and traces.
+- [Labels](./processors/labels.md): Add, update, or delete metric labels.
+- [Metrics selector](./processors/metrics-selector.md): Choose which metrics to keep or discard.
+- [OpenTelemetry envelope](./processors/opentelemetry-envelope.md): Transform logs into an OpenTelemetry-compatible format.
+- [Sampling](./processors/sampling.md): Apply head or tail sampling to incoming traces.
+- [SQL](./processors/sql.md): Use SQL queries to extract log content.
 - [Filters as processors](filters.md): Use filters as processors.
 
 ## Features
 
 Compatible processors include the following features:
 
-- [Conditional processing](conditional-processing.md): Selectively apply processors to logs based on the value of fields that those logs contain.
+- [Conditional processing](./processors/conditional-processing.md): Selectively apply processors to logs based on the value of fields that those logs contain.