[release/v1.1] Remove incorrect info in otelcol.processor.tail_sampli…

…ng topic (#2231)

(cherry picked from commit 40201a9)

Co-authored-by: Clayton Cornell <[email protected]>

docs/sources/reference/components/otelcol/otelcol.processor.tail_sampling.md

@@ -12,17 +12,10 @@ title: otelcol.processor.tail_sampling
 policies. All spans for a given trace *must* be received by the same collector
 instance for effective sampling decisions.
 
-The `tail_sampling` component uses both soft and hard limits, where the hard limit
-is always equal or larger than the soft limit. When memory usage goes above the
-soft limit, the processor component drops data and returns errors to the
-preceding components in the pipeline. When usage exceeds the hard
-limit, the processor forces a garbage collection in order to try and free
-memory. When usage is below the soft limit, no data is dropped and no forced
-garbage collection is performed.
-
-> **Note**: `otelcol.processor.tail_sampling` is a wrapper over the upstream
-> OpenTelemetry Collector Contrib `tail_sampling` processor. Bug reports or feature
-> requests will be redirected to the upstream repository, if necessary.
+{{< admonition type="note" >}}
+`otelcol.processor.tail_sampling` is a wrapper over the upstream OpenTelemetry Collector Contrib `tail_sampling` processor.
+Bug reports or feature requests will be redirected to the upstream repository, if necessary.
+{{< /admonition >}}
 
 Multiple `otelcol.processor.tail_sampling` components can be specified by
 giving them different labels.