readmefix

Author: cijothomas

examples/self-diagnostics/README.md

@@ -9,11 +9,12 @@ which the logs are simply discarded.
 ## Filtering logs from external dependencies of OTLP Exporter:
 
 The example configures a tracing `filter` to restrict logs from external crates
-(`hyper`, `tonic`, and `reqwest`) used by the OTLP Exporter to the `error`
+(`hyper`, `tonic`, and `reqwest` etc.) used by the OTLP Exporter to the `error`
 level. This helps prevent an infinite loop of log generation when these crates
 emit logs that are picked up by the tracing subscriber. This is only a
-workaround until https://github.com/open-telemetry/opentelemetry-rust/issues/761
-is resolved.
+workaround until [the root
+issue](https://github.com/open-telemetry/opentelemetry-rust/issues/761) is
+resolved.
 
 ## Filtering logs to be send to OpenTelemetry itself
 
@@ -23,4 +24,5 @@ to OpenTelemetry, then enabling OpenTelemetry internal logs can also cause
 infinite, recursive logging. You can filter out all OpenTelemetry internal logs
 from being sent to [OpenTelemetry Tracing
 Appender](../../opentelemetry-appender-tracing/README.md) using a filter, like
-"add_directive("opentelemetry=off".parse().unwrap())".
+"add_directive("opentelemetry=off".parse().unwrap())" being done for tracing's
+`FmtSubscriber`.