Update tutorial/OpenTelemetry/OpenTelemetry_OPEA_Guide.rst and ChatQnA.md

Co-authored-by: Malini Bhandaru <[email protected]>
Signed-off-by: Tsai, Louie <[email protected]>

Author: louie-tsai

tutorial/OpenTelemetry/OpenTelemetry_OPEA_Guide.rst

@@ -36,7 +36,7 @@ Deployment
 
 In the OpenTelemetry-enabled GenAIExamples, OpenTelemetry Metrics is activated by default, while OpenTelemetry Tracing is initially disabled.  
 Similarly, the Telemetry UI services, including Grafana, Prometheus, and Jaeger, are also disabled by default.  
-To enable OTel tracing along with Grafana, Prometheus, and Jaeger for an example, you can include an additional telemetry Docker Compose YAML file. 
+To enable OTel tracing along with Grafana, Prometheus, and Jaeger you need to include an additional telemetry Docker Compose YAML file. 
 For instance, adding compose.telemetry.yaml alongside compose.yaml will activate all telemetry features for the example.  
 
 
@@ -57,7 +57,7 @@ Below are the GenAIExamples that include support for Grafana, Prometheus, and Ja
 How to Monitor 
 ****************
 
-OpenTelemetry metrics and tracing can be visualized through three primary monitoring UI web pages.  
+OpenTelemetry metrics and tracing currently can be visualized through one of three primary monitoring UI web pages.  
 
 1. Prometheus
 +++++++++++++++
@@ -82,7 +82,7 @@ If a service is marked as "down," Grafana Dashboards will be unable to display t
 
 The Grafana UI displays telemetry metrics through pre-defined dashboards, providing a clear visualization of data. 
 For OPEA examples, Grafana is configured by default to use Prometheus as its data source, eliminating the need for manual setup. 
-The Grafana UI web page could be accessed using the following URL.
+The Grafana UI web page can be accessed using the following URL.
 
 .. code-block:: bash
 

tutorial/OpenTelemetry/deploy/ChatQnA.md

@@ -19,8 +19,10 @@ This trace contains two spans: one for the first token and another for all subse
 
 ![chatqna_1req](../assets/jaeger_ui_opea_chatqna_1req.png)
 
-The first trace along the timeline is opea: ServiceOrchestrator.schedule, which operates on the CPU. 
-This trace provides insights into the orchestration and scheduling of services within the ChatQnA megaservice, highlighting the execution flow during the process.
+The first trace along the timeline is opea: ServiceOrchestrator.schedule, which runs on the CPU. 
+
+It provides insights into the orchestration and scheduling of services within the ChatQnA megaservice, highlighting the execution flow during the process.
+
 
 ![chatqna_cpu_req](../assets/jaeger_ui_opea_chatqna_req_cpu.png)