[release-v2.6] [DOC] Correct Jaeger spelling mistake (#4016)

Co-authored-by: Kim Nylander <104772500+knylander-grafana@users.noreply.github.com>

docs/sources/helm-charts/tempo-distributed/get-started-helm-charts/_index.md

@@ -352,7 +352,7 @@ Update the `storage` configuration options based upon your requirements:
 The Helm chart values in your `custom.yaml` file are configure to use OTLP.
 If you are using other receivers, then you need to configure them.
 
-You can configure Tempo can to receive data from OTLP, Jaegar, Zipkin, Kafka, and OpenCensus.
+You can configure Tempo can to receive data from OTLP, Jaeger, Zipkin, Kafka, and OpenCensus. 
 The following example enables OTLP on the distributor. For other options, refer to the [distributor documentation]({{< relref "/docs/tempo/latest/configuration#distributor" >}})
 
 The example used in this procedure has OTLP enabled.

docs/sources/tempo/getting-started/instrumentation.md

@@ -59,7 +59,7 @@ information from a client application with minimal manual instrumentation of the
 ### Jaeger
 
 {{< admonition type="note" >}}
-Jaegar client libraries have been deprecated. For more information, refer to the [Deprecating Jaeger clients article](https://www.jaegertracing.io/docs/1.50/client-libraries/#deprecating-jaeger-clients). Jaegar now recommends using OpenTelemetry SDKs.
+Jaeger client libraries have been deprecated. For more information, refer to the [Deprecating Jaeger clients article](https://www.jaegertracing.io/docs/1.50/client-libraries/#deprecating-jaeger-clients). Jaeger now recommends using OpenTelemetry SDKs.
 {{% /admonition %}}
 
 - [Jaeger Language Specific Instrumentation](https://www.jaegertracing.io/docs/latest/client-libraries/)