update readme

Author: lalitb

examples/self-diagnostics/README.md

@@ -4,16 +4,15 @@ This example shows how to setup the custom error handler for self-diagnostics.
 
 ## Custom Error Handling:
 
-A custom error handler is implemented to log errors using the `tracing` crate's `error!` macro. These errors are exporter to collector using `opentelemetry-appender-tracing` which uses OTLP log exporter over HTTP/protobuf.
-So, any errors generated by the configured OTLP metrics pipeline are exporter through this custom error handler.
+A custom error handler is set up to capture and record errors using the `tracing` crate's `error!` macro. These errors are then exported to a collector using the `opentelemetry-appender-tracing` crate, which utilizes the OTLP log exporter over `HTTP/protobuf`. As a result, any errors generated by the configured OTLP metrics pipeline are funneled through this custom error handler for proper recording and export.
 
 ## 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` level. This helps prevent an infinite loop of log generation when these crates emit logs that are picked up by the tracing subscriber.
+The example configures a tracing `filter` to restrict logs from external crates (`hyper`, `tonic`, and `reqwest`) 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.
 
 ## Ensure that the internally generated errors are logged only once:
 
-By using a set to track seen errors, the custom error handler ensures that the same error is not logged multiple times. This is particularly useful for handling scenarios where continuous error logging might occur, such as when the OpenTelemetry collector is not running. 
+By using a hashset to track seen errors, the custom error handler ensures that the same error is not logged multiple times. This is particularly useful for handling scenarios where continuous error logging might occur, such as when the OpenTelemetry collector is not running. 
 
 
 ## Usage