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

Co-authored-by: Mark Fussell <markfussell@gmail.com>
Signed-off-by: Mirel <15373565+MyMirelHub@users.noreply.github.com>

Author: MyMirelHub

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

@@ -87,7 +87,7 @@ Jaeger V2 can be deployed using the OpenTelemetry Operator for simplified manage
 
 > **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 in this case we will be letting helm to create an automatically generated self-signed certificate,
+For simplicity you can use Helm to create an automatically generated self-signed certificate.
 
 ```bash
 ```