Fixing links for readmes

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

Author: esmerel

administration/configuring-fluent-bit.md

@@ -2,8 +2,8 @@
 
 Fluent Bit supports two configuration formats:
 
-- [YAML](yaml/README.md): Standard configuration format as of v3.2.
-- [Classic mode](classic-mode/README.md): To be deprecated at the end of 2026.
+- [YAML](./configuring-fluent-bit/yaml.md): Standard configuration format as of v3.2.
+- [Classic mode](./configuring-fluent-bit/classic-mode/README.md): To be deprecated at the end of 2026.
 
 ## Command line interface
 

administration/multithreading.md

@@ -9,14 +9,14 @@ timers, receiving internal messages, scheduling flushes, and handling retries.
 This event loop runs in the main Fluent Bit thread.
 
 To free up resources in the main thread, you can configure
-[inputs](../pipeline/inputs/README.md) and [outputs](../pipeline/outputs/README.md)
+[inputs](../pipeline/inputs.md) and [outputs](../pipeline/outputs.md)
 to run in their own self-contained threads. However, inputs and outputs implement
 multithreading in distinct ways: inputs can run in `threaded` mode, and outputs
 can use one or more `workers`.
 
 Threading also affects certain processes related to inputs and outputs. For example,
-[filters](../pipeline/filters/README.md) always run in the main thread, but
-[processors](../pipeline/processors/README.md) run in the self-contained threads of
+[filters](../pipeline/filters.md) always run in the main thread, but
+[processors](../pipeline/processors.md) run in the self-contained threads of
 their respective inputs or outputs, if applicable.
 
 ## Inputs

pipeline/processors.md

@@ -1,6 +1,6 @@
 # Processors
 
-Processors are components that modify, transform, or enhance data as it flows through Fluent Bit. Unlike [filters](../filters/README.md), processors are tightly coupled to inputs, which means they execute immediately and avoid creating a performance bottleneck.
+Processors are components that modify, transform, or enhance data as it flows through Fluent Bit. Unlike [filters](filters.md), processors are tightly coupled to inputs, which means they execute immediately and avoid creating a performance bottleneck.
 
 Additionally, filters can be implemented in a way that mimics the behavior of processors, but processors can't be implemented in a way that mimics filters.
 

pipeline/processors/conditional-processing.md

@@ -1,6 +1,6 @@
 # Conditional processing
 
-Conditional processing lets you selectively apply [processors](README.md) to logs based on the value of fields within those logs. This feature lets you create processing pipelines that only process records that meet certain criteria, and ignore the rest.
+Conditional processing lets you selectively apply [processors](../processors.md) to logs based on the value of fields within those logs. This feature lets you create processing pipelines that only process records that meet certain criteria, and ignore the rest.
 
 Conditional processing is available in Fluent Bit version 4.0 and greater.
 
@@ -10,8 +10,8 @@ You can turn a standard processor into a conditional processor by adding a `cond
 
 {% hint style="info" %}
 
-- Only [YAML configuration files](../../administration/configuring-fluent-bit/yaml/README.md) support processors, including conditional processors.
-- Conditional processing isn't supported if you're using a [filter as a processor](../filters).
+- Only [YAML configuration files](../../administration/configuring-fluent-bit/yaml.md) support processors, including conditional processors.
+- Conditional processing isn't supported if you're using a [filter as a processor](../filters.md).
 
 {% endhint %}
 

pipeline/processors/content-modifier.md

@@ -6,7 +6,7 @@ Similar to how filters work, this processor uses a unified mechanism to perform
 
 {% hint style="info" %}
 
-Only [YAML configuration files](../../administration/configuring-fluent-bit/yaml/README.md) support processors.
+Only [YAML configuration files](../../administration/configuring-fluent-bit/yaml.md) support processors.
 
 {% endhint %}
 

pipeline/processors/filters.md

@@ -1,10 +1,10 @@
 # Filters as processors
 
-You can use any [filter](../filters/README.md) as a processor in Fluent Bit.
+You can use any [filter](../filters.md) as a processor in Fluent Bit.
 
 {% hint style="info" %}
 
-Only [YAML configuration files](../../administration/configuring-fluent-bit/yaml/README.md) support processors.
+Only [YAML configuration files](../../administration/configuring-fluent-bit/yaml.md) support processors.
 
 {% endhint %}
 
@@ -33,4 +33,4 @@ pipeline:
 ```
 
 {% endtab %}
-{% endtabs %}
+{% endtabs %}

pipeline/processors/labels.md

@@ -6,7 +6,7 @@ Similar to filters, this processor presents an enriching/modifying mechanism to
 
 {% hint style="info" %}
 
-Only [YAML configuration files](../../administration/configuring-fluent-bit/yaml/README.md) support processors.
+Only [YAML configuration files](../../administration/configuring-fluent-bit/yaml.md) support processors.
 
 {% endhint %}
 
@@ -36,7 +36,7 @@ pipeline:
         metrics:
           - name: labels
             update: name fluentbit
-  
+
   outputs:
     - name : stdout
       match: '*'
@@ -86,7 +86,7 @@ pipeline:
         metrics:
           - name: labels
             upsert: name fluentbit
-  
+
   outputs:
     - name : stdout
       match: '*'
@@ -111,7 +111,7 @@ pipeline:
         metrics:
           - name: labels
             delete: name
-  
+
   outputs:
     - name : stdout
       match: '*'
@@ -143,4 +143,4 @@ pipeline:
 ```
 
 {% endtab %}
-{% endtabs %}
+{% endtabs %}

pipeline/processors/opentelemetry-envelope.md

@@ -6,7 +6,7 @@ The _OpenTelemetry envelope_ processor transforms your data to be compatible wit
 
 {% hint style="info" %}
 
-Only [YAML configuration files](../../administration/configuring-fluent-bit/yaml/README.md) support processors.
+Only [YAML configuration files](../../administration/configuring-fluent-bit/yaml.md) support processors.
 
 {% endhint %}
 
@@ -178,4 +178,5 @@ The collector JSON output will resemble the following:
 }
 ```
 
-For more details about further processing, read the [content modifier](../processors/content-modifier.md) processor documentation.
+For more details about further processing, read the [content
+modifier](../processors/content-modifier.md) processor documentation.

pipeline/processors/sampling.md

@@ -4,7 +4,7 @@ The _sampling_ processor uses an extendable architecture that supports multiple
 
 {% hint style="info" %}
 
-Only [YAML configuration files](../../administration/configuring-fluent-bit/yaml/README.md) support processors.
+Only [YAML configuration files](../../administration/configuring-fluent-bit/yaml.md) support processors.
 
 {% endhint %}
 

pipeline/processors/sql.md

@@ -6,7 +6,7 @@ This processor differs from the stream processor interface that runs after filte
 
 {% hint style="info" %}
 
-Only [YAML configuration files](../../administration/configuring-fluent-bit/yaml/README.md) support processors.
+Only [YAML configuration files](../../administration/configuring-fluent-bit/yaml.md) support processors.
 
 {% endhint %}
 
@@ -82,4 +82,4 @@ The resulting output resembles the following:
   "date": 1711059261.630668,
   "http_domain": "fluentbit.io"
 }
-```
+```