diff --git a/SUMMARY.md b/SUMMARY.md
index 064a9200e..af2be189e 100644
--- a/SUMMARY.md
+++ b/SUMMARY.md
@@ -146,8 +146,8 @@
   * [Labels](pipeline/processors/labels.md)
   * [Metrics Selector](pipeline/processors/metrics-selector.md)
   * [OpenTelemetry Envelope](pipeline/processors/opentelemetry-envelope.md)
+  * [Sampling](pipeline/processors/sampling.md)
   * [SQL](pipeline/processors/sql.md)
-  * [Traces](pipeline/processors/traces.md)
   * [Filters as processors](pipeline/processors/filters.md)
   * [Conditional processing](pipeline/processors/conditional-processing.md)
 * [Filters](pipeline/filters/README.md)
diff --git a/pipeline/processors/README.md b/pipeline/processors/README.md
index e33aa14e1..30e442bd8 100644
--- a/pipeline/processors/README.md
+++ b/pipeline/processors/README.md
@@ -18,9 +18,9 @@ Fluent Bit offers the following processors:
 - [Metrics Selector](metrics-selector.md): Choose which metrics to keep or discard.
 - [OpenTelemetry Envelope](opentelemetry-envelope.md): Transform logs into an
   OpenTelemetry-compatible format.
-- [SQL](sql.md): Use SQL queries to extract log content.
-- [Traces](traces.md): Trace sampling designed with a pluggable architecture,
+- [Sampling](sampling.md): Trace sampling designed with a pluggable architecture,
   allowing easy extension to support multiple sampling strategies and backends.
+- [SQL](sql.md): Use SQL queries to extract log content.
 - [Filters](filters.md): Any filter can be used as a processor.
 
 ## Features
diff --git a/pipeline/processors/traces.md b/pipeline/processors/sampling.md
similarity index 97%
rename from pipeline/processors/traces.md
rename to pipeline/processors/sampling.md
index ab5a46b8c..5f44b8614 100644
--- a/pipeline/processors/traces.md
+++ b/pipeline/processors/sampling.md
@@ -1,6 +1,6 @@
-# Traces
+# Sampling
 
-The _Traces_ sampling processor is designed with a pluggable architecture, allowing easy extension to support multiple sampling strategies and backends. It provides you with the ability to apply head or tail sampling to incoming trace telemetry data.
+The _Sampling_ processor is designed with a pluggable architecture, allowing easy extension to support multiple trace sampling strategies and backends. It provides you with the ability to apply head or tail sampling to incoming trace telemetry data.
 
 Available samplers:
 
@@ -21,9 +21,9 @@ Conditions:
 
 The processor does not provide any extra configuration parameter, it can be used directly in your _processors_ Yaml directive.
 
-## Traces types
+## Sampling types
 
-Traces have both a name and a type with the following possible settings:
+Sampling has both a name and a type with the following possible settings:
 
 | Key    |     Possible values     |
 | :----- | :---------------------: |