docs(external): updates concepts/traces page (#22955)

* docs(external): updates concepts/traces page

* address Benson's review point

* rmv trailing spaces

* md fixes

Author: pront

website/content/en/docs/about/concepts.md

@@ -26,9 +26,23 @@ A **metric** event represents a numerical operation performed on a time series.
 
 ### Traces
 
-A **trace** event can be thought of as a special kind of log event. The components that support trace events are: the `datadog_agent` source, the `datadog_traces` sink, and the `sample` and `remap` transforms. **Note**: Support for traces is limited and is in alpha.
+A **trace** event can be thought of as a special kind of log event. The components that support trace events are:
+
+* the `datadog_agent` source
+* the `datadog_traces` sink
+* the `opentelemetry` source
+* the `sample` transform
+* the `remap` transform
+* the `native`, `native_json` decoders
+* the `native`, `native_json` and `json` encoders
+  * the `opentelemetry` sink and any other sink that uses the above encoders
+
+**Note**: Support for traces is limited and is in alpha.
+
+If you’re interested in using traces with a Vector component that doesn’t yet support them,
+please check the list of open issues [here](https://github.com/vectordotdev/vector/issues?q=is%3Aissue+state%3Aopen+label%3A%22domain%3A%20traces%22).
+If you don’t see your use case covered, feel free to [open a new issue](https://github.com/vectordotdev/vector/issues/new?template=feature.yml).
 
-If you're interested in using traces with a Vector component that doesn't yet support them, please open an issue so we can have a better understanding of what components to prioritize adding trace support for.
 
 ## Components
 
@@ -92,9 +106,9 @@ For example, if you have a single source sending to 3 sinks in this configuratio
 backpressure from sink 2 (500 events/sec) since that is the slowest sink configured to provide backpressure.
 Sink 1 will drop up to 250 events/sec, and sink 3 will be underutilized.
 
-- Sink 1: Can send at 250 events/sec (`buffer.when_full = drop_newest`)
-- Sink 2: Can send at 500 events/sec  (`buffer.when_full = block`)
-- Sink 3: Can send at 1000 events/sec  (`buffer.when_full = block`)
+* Sink 1: Can send at 250 events/sec (`buffer.when_full = drop_newest`)
+* Sink 2: Can send at 500 events/sec  (`buffer.when_full = block`)
+* Sink 3: Can send at 1000 events/sec  (`buffer.when_full = block`)
 
 If there are multiple sources configured for a single component, Vector currently makes no guarantees
 which source will have priority during backpressure. To make sure all inputs are fully processed, make