fix: improve clarity and correctness in Jaeger V2 documentation

Signed-off-by: MyMirelHub <15373565+MyMirelHub@users.noreply.github.com>

Author: MyMirelHub

daprdocs/content/en/operations/observability/tracing/otel-collector/open-telemetry-collector-jaeger.md

@@ -29,7 +29,7 @@ docker run -d --rm --name jaeger \
   cr.jaegertracing.io/jaegertracing/jaeger:2.11.0
 ```
 
-You can also view the logs the jaeger container using: 
+You can also view the logs from the jaeger container using: 
 
 ```bash
 docker logs jaeger
@@ -85,12 +85,9 @@ Jaeger V2 can be deployed using the OpenTelemetry Operator for simplified manage
 
 #### Installation
 
-> **Note:**In order for the API server to communicate with the webhook component of the operator, the webhook requires a TLS certificate that the API server is configured to trust. There are a few different ways you can use to generate/configure the required TLS certificate detailed in the [otel operator chart docs](https://github.com/open-telemetry/opentelemetry-helm-charts/tree/main/charts/opentelemetry-operator#tls-certificate-requirement)
+> **Note:** In order for the API server to communicate with the webhook component of the operator, the webhook requires a TLS certificate that the API server is configured to trust. There are a few different ways you can use to generate/configure the required TLS certificate detailed in the [otel operator chart docs](https://github.com/open-telemetry/opentelemetry-helm-charts/tree/main/charts/opentelemetry-operator#tls-certificate-requirement)
 
 For simplicity you can use Helm to create an automatically generated self-signed certificate.
- 
-```bash
-```
 
 1. **Install the OpenTelemetry Operator**:
 
@@ -103,7 +100,7 @@ For simplicity you can use Helm to create an automatically generated self-signed
    Confirm that all resources in the `opentelemetry-operator-system` namespace are ready.
 
 1. **Deploy a Jaeger V2 instance with in-memory storage**:
-   Apply the following configuration to create a Jaeger V2 instance:
+   Create a file named `jaeger-inmemory.yaml` with the following configuration:
    ```yaml
    apiVersion: opentelemetry.io/v1beta1
    kind: OpenTelemetryCollector
@@ -152,7 +149,7 @@ For simplicity you can use Helm to create an automatically generated self-signed
 
 Create a Dapr configuration file to enable tracing and export the sidecar traces directly to the Jaeger V2 instance.
 
-1. Create a configuration file (e.g., `tracing.yaml`) with the following content, updating the `namespace` and `otel.endpointAddress` to match your Jaeger V2 instance:
+1. Create a configuration file (for example `tracing.yaml`) with the following content, updating the `namespace` and `otel.endpointAddress` to match your Jaeger V2 instance:
    ```yaml
    apiVersion: dapr.io/v1alpha1
    kind: Configuration
@@ -203,7 +200,7 @@ That’s it! There’s no need to include the OpenTelemetry SDK or instrument yo
 To view Dapr sidecar traces, port-forward the Jaeger V2 service and open the UI:
 
 ```bash
-kubectl port-forward svc/jaeger-inmemory-instance-collector 16686 -n observability
+kubectl port-forward svc/jaeger-inmemory-instance-collector 16686:16686 -n observability
 ```
 
 In your browser, go to `http://localhost:16686` to see the Jaeger V2 UI.