[chore] doc review

exporter/loadbalancingexporter/README.md

@@ -29,12 +29,8 @@ The options for `routing_key` are: `service`, `traceID`, `metric` (metric name),
 | resource | metrics |
 | metric | metrics |
 
-**Important**: Don't use traceID in metric pipeline.
-
 If no `routing_key` is configured, the default routing mechanism is `traceID`  for traces, while `service` is the default for metrics. This means that spans belonging to the same `traceID` (or `service.name`, when `service` is used as the `routing_key`) will be sent to the same backend.
 
-If no routing_key is configured, the default routing mechanism is traceID for traces, while service is the default for metrics
-
 It requires a source of backend information to be provided: static, with a fixed list of backends, or DNS, with a hostname that will resolve to all IP addresses to use. The DNS resolver will periodically check for updates.
 
 Note that either the Trace ID or Service name is used for the decision on which backend to use: the actual backend load isn't taken into consideration. Even though this load-balancer won't do round-robin balancing of the batches, the load distribution should be very similar among backends with a standard deviation under 5% at the current configuration.