fix(docs): Correct 'noe visible' typo in troubleshooting guide (#1125)

Fixes a typo in the service mesh troubleshooting section: "noe visible"
→ "not visible".

Applied across all versioned docs (`_dev` and 2.1–2.20) so the live site
and future snapshots are consistent.

Signed-off-by: Yuri Shkuro <github@ysh.us>
Co-authored-by: Yuri Shkuro <github@ysh.us>
Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

Author: 3 people

content/docs/v2/2.1/operations/troubleshooting.md

@@ -62,7 +62,7 @@ If Jaeger is able to receive traces, the counter `otelcol_receiver_accepted_span
 
 ## Service Mesh: missing spans
 
-When deploying your application as part of a service mesh like Istio, the number of moving parts increases significantly and might affect how (and which) spans are reported. If you expect to see spans generated by a service mesh but they are noe visible in the Jaeger UI, check the troubleshooting guides for the service mesh you are using. For example, on [Istio's website](https://istio.io/faq/distributed-tracing/#no-tracing).
+When deploying your application as part of a service mesh like Istio, the number of moving parts increases significantly and might affect how (and which) spans are reported. If you expect to see spans generated by a service mesh but they are not visible in the Jaeger UI, check the troubleshooting guides for the service mesh you are using. For example, on [Istio's website](https://istio.io/faq/distributed-tracing/#no-tracing).
 
 ## Run debug images of the backend components
 

content/docs/v2/2.10/operations/troubleshooting.md

@@ -62,7 +62,7 @@ If Jaeger is able to receive traces, the counter `otelcol_receiver_accepted_span
 
 ## Service Mesh: missing spans
 
-When deploying your application as part of a service mesh like Istio, the number of moving parts increases significantly and might affect how (and which) spans are reported. If you expect to see spans generated by a service mesh but they are noe visible in the Jaeger UI, check the troubleshooting guides for the service mesh you are using. For example, on [Istio's website](https://istio.io/faq/distributed-tracing/#no-tracing).
+When deploying your application as part of a service mesh like Istio, the number of moving parts increases significantly and might affect how (and which) spans are reported. If you expect to see spans generated by a service mesh but they are not visible in the Jaeger UI, check the troubleshooting guides for the service mesh you are using. For example, on [Istio's website](https://istio.io/faq/distributed-tracing/#no-tracing).
 
 ## Run debug images of the backend components
 

content/docs/v2/2.11/operations/troubleshooting.md

@@ -62,7 +62,7 @@ If Jaeger is able to receive traces, the counter `otelcol_receiver_accepted_span
 
 ## Service Mesh: missing spans
 
-When deploying your application as part of a service mesh like Istio, the number of moving parts increases significantly and might affect how (and which) spans are reported. If you expect to see spans generated by a service mesh but they are noe visible in the Jaeger UI, check the troubleshooting guides for the service mesh you are using. For example, on [Istio's website](https://istio.io/faq/distributed-tracing/#no-tracing).
+When deploying your application as part of a service mesh like Istio, the number of moving parts increases significantly and might affect how (and which) spans are reported. If you expect to see spans generated by a service mesh but they are not visible in the Jaeger UI, check the troubleshooting guides for the service mesh you are using. For example, on [Istio's website](https://istio.io/faq/distributed-tracing/#no-tracing).
 
 ## Run debug images of the backend components
 

content/docs/v2/2.12/operations/troubleshooting.md

@@ -62,7 +62,7 @@ If Jaeger is able to receive traces, the counter `otelcol_receiver_accepted_span
 
 ## Service Mesh: missing spans
 
-When deploying your application as part of a service mesh like Istio, the number of moving parts increases significantly and might affect how (and which) spans are reported. If you expect to see spans generated by a service mesh but they are noe visible in the Jaeger UI, check the troubleshooting guides for the service mesh you are using. For example, on [Istio's website](https://istio.io/faq/distributed-tracing/#no-tracing).
+When deploying your application as part of a service mesh like Istio, the number of moving parts increases significantly and might affect how (and which) spans are reported. If you expect to see spans generated by a service mesh but they are not visible in the Jaeger UI, check the troubleshooting guides for the service mesh you are using. For example, on [Istio's website](https://istio.io/faq/distributed-tracing/#no-tracing).
 
 ## Run debug images of the backend components
 

content/docs/v2/2.13/operations/troubleshooting.md

@@ -62,7 +62,7 @@ If Jaeger is able to receive traces, the counter `otelcol_receiver_accepted_span
 
 ## Service Mesh: missing spans
 
-When deploying your application as part of a service mesh like Istio, the number of moving parts increases significantly and might affect how (and which) spans are reported. If you expect to see spans generated by a service mesh but they are noe visible in the Jaeger UI, check the troubleshooting guides for the service mesh you are using. For example, on [Istio's website](https://istio.io/faq/distributed-tracing/#no-tracing).
+When deploying your application as part of a service mesh like Istio, the number of moving parts increases significantly and might affect how (and which) spans are reported. If you expect to see spans generated by a service mesh but they are not visible in the Jaeger UI, check the troubleshooting guides for the service mesh you are using. For example, on [Istio's website](https://istio.io/faq/distributed-tracing/#no-tracing).
 
 ## Run debug images of the backend components
 

content/docs/v2/2.14/operations/troubleshooting.md

@@ -62,7 +62,7 @@ If Jaeger is able to receive traces, the counter `otelcol_receiver_accepted_span
 
 ## Service Mesh: missing spans
 
-When deploying your application as part of a service mesh like Istio, the number of moving parts increases significantly and might affect how (and which) spans are reported. If you expect to see spans generated by a service mesh but they are noe visible in the Jaeger UI, check the troubleshooting guides for the service mesh you are using. For example, on [Istio's website](https://istio.io/faq/distributed-tracing/#no-tracing).
+When deploying your application as part of a service mesh like Istio, the number of moving parts increases significantly and might affect how (and which) spans are reported. If you expect to see spans generated by a service mesh but they are not visible in the Jaeger UI, check the troubleshooting guides for the service mesh you are using. For example, on [Istio's website](https://istio.io/faq/distributed-tracing/#no-tracing).
 
 ## Run debug images of the backend components
 

content/docs/v2/2.15/operations/troubleshooting.md

@@ -62,7 +62,7 @@ If Jaeger is able to receive traces, the counter `otelcol_receiver_accepted_span
 
 ## Service Mesh: missing spans
 
-When deploying your application as part of a service mesh like Istio, the number of moving parts increases significantly and might affect how (and which) spans are reported. If you expect to see spans generated by a service mesh but they are noe visible in the Jaeger UI, check the troubleshooting guides for the service mesh you are using. For example, on [Istio's website](https://istio.io/faq/distributed-tracing/#no-tracing).
+When deploying your application as part of a service mesh like Istio, the number of moving parts increases significantly and might affect how (and which) spans are reported. If you expect to see spans generated by a service mesh but they are not visible in the Jaeger UI, check the troubleshooting guides for the service mesh you are using. For example, on [Istio's website](https://istio.io/faq/distributed-tracing/#no-tracing).
 
 ## Run debug images of the backend components
 

content/docs/v2/2.16/operations/troubleshooting.md

@@ -62,7 +62,7 @@ If Jaeger is able to receive traces, the counter `otelcol_receiver_accepted_span
 
 ## Service Mesh: missing spans
 
-When deploying your application as part of a service mesh like Istio, the number of moving parts increases significantly and might affect how (and which) spans are reported. If you expect to see spans generated by a service mesh but they are noe visible in the Jaeger UI, check the troubleshooting guides for the service mesh you are using. For example, on [Istio's website](https://istio.io/faq/distributed-tracing/#no-tracing).
+When deploying your application as part of a service mesh like Istio, the number of moving parts increases significantly and might affect how (and which) spans are reported. If you expect to see spans generated by a service mesh but they are not visible in the Jaeger UI, check the troubleshooting guides for the service mesh you are using. For example, on [Istio's website](https://istio.io/faq/distributed-tracing/#no-tracing).
 
 ## Run debug images of the backend components
 

content/docs/v2/2.17/operations/troubleshooting.md

@@ -62,7 +62,7 @@ If Jaeger is able to receive traces, the counter `otelcol_receiver_accepted_span
 
 ## Service Mesh: missing spans
 
-When deploying your application as part of a service mesh like Istio, the number of moving parts increases significantly and might affect how (and which) spans are reported. If you expect to see spans generated by a service mesh but they are noe visible in the Jaeger UI, check the troubleshooting guides for the service mesh you are using. For example, on [Istio's website](https://istio.io/faq/distributed-tracing/#no-tracing).
+When deploying your application as part of a service mesh like Istio, the number of moving parts increases significantly and might affect how (and which) spans are reported. If you expect to see spans generated by a service mesh but they are not visible in the Jaeger UI, check the troubleshooting guides for the service mesh you are using. For example, on [Istio's website](https://istio.io/faq/distributed-tracing/#no-tracing).
 
 ## Run debug images of the backend components
 

content/docs/v2/2.18/operations/troubleshooting.md

@@ -62,7 +62,7 @@ If Jaeger is able to receive traces, the counter `otelcol_receiver_accepted_span
 
 ## Service Mesh: missing spans
 
-When deploying your application as part of a service mesh like Istio, the number of moving parts increases significantly and might affect how (and which) spans are reported. If you expect to see spans generated by a service mesh but they are noe visible in the Jaeger UI, check the troubleshooting guides for the service mesh you are using. For example, on [Istio's website](https://istio.io/faq/distributed-tracing/#no-tracing).
+When deploying your application as part of a service mesh like Istio, the number of moving parts increases significantly and might affect how (and which) spans are reported. If you expect to see spans generated by a service mesh but they are not visible in the Jaeger UI, check the troubleshooting guides for the service mesh you are using. For example, on [Istio's website](https://istio.io/faq/distributed-tracing/#no-tracing).
 
 ## Run debug images of the backend components