Fix: Typo for diligence,distributed,documenting,controlled (#704)

## Which problem is this PR solving? - Resolves #701 ## Checklist - [x] I have read https://github.com/jaegertracing/jaeger/blob/master/CONTRIBUTING_GUIDELINES.md - [x] I have signed all commits --------- Signed-off-by: Jeeva Ramanathan <[email protected]> Signed-off-by: Yuri Shkuro <[email protected]> Co-authored-by: Yuri Shkuro <[email protected]>
jaegertracing · May 13, 2024 · 663b65d · 663b65d
1 parent 16a738b
commit 663b65d
Show file tree

Hide file tree

Showing 32 changed files with 32 additions and 36 deletions.
diff --git a/content/docs/1.40/operator.md b/content/docs/1.40/operator.md
@@ -972,7 +972,7 @@ In order to workaround that issue:
 - change `/healtz` and `/readyz` ports from 8081 to other value
 - change `kube-rbac-proxy` secure port from 8443 to other value
 - change `webhook-server` port from 9443 to other value
-  - this setting is conrolled by `webhook-bind-port` flag
+  - this setting is controlled by `webhook-bind-port` flag
 
 Jaeger operator config example:
 

diff --git a/content/docs/1.41/operator.md b/content/docs/1.41/operator.md
@@ -972,7 +972,7 @@ In order to workaround that issue:
 - change `/healtz` and `/readyz` ports from 8081 to other value
 - change `kube-rbac-proxy` secure port from 8443 to other value
 - change `webhook-server` port from 9443 to other value
-  - this setting is conrolled by `webhook-bind-port` flag
+  - this setting is controlled by `webhook-bind-port` flag
 
 Jaeger operator config example:
 

diff --git a/content/docs/1.42/operator.md b/content/docs/1.42/operator.md
@@ -972,7 +972,7 @@ In order to workaround that issue:
 - change `/healtz` and `/readyz` ports from 8081 to other value
 - change `kube-rbac-proxy` secure port from 8443 to other value
 - change `webhook-server` port from 9443 to other value
-  - this setting is conrolled by `webhook-bind-port` flag
+  - this setting is controlled by `webhook-bind-port` flag
 
 Jaeger operator config example:
 

diff --git a/content/docs/1.43/operator.md b/content/docs/1.43/operator.md
@@ -972,7 +972,7 @@ In order to workaround that issue:
 - change `/healtz` and `/readyz` ports from 8081 to other value
 - change `kube-rbac-proxy` secure port from 8443 to other value
 - change `webhook-server` port from 9443 to other value
-  - this setting is conrolled by `webhook-bind-port` flag
+  - this setting is controlled by `webhook-bind-port` flag
 
 Jaeger operator config example:
 

diff --git a/content/docs/1.44/operator.md b/content/docs/1.44/operator.md
@@ -972,7 +972,7 @@ In order to workaround that issue:
 - change `/healtz` and `/readyz` ports from 8081 to other value
 - change `kube-rbac-proxy` secure port from 8443 to other value
 - change `webhook-server` port from 9443 to other value
-  - this setting is conrolled by `webhook-bind-port` flag
+  - this setting is controlled by `webhook-bind-port` flag
 
 Jaeger operator config example:
 

diff --git a/content/docs/1.45/operator.md b/content/docs/1.45/operator.md
@@ -972,7 +972,7 @@ In order to workaround that issue:
 - change `/healtz` and `/readyz` ports from 8081 to other value
 - change `kube-rbac-proxy` secure port from 8443 to other value
 - change `webhook-server` port from 9443 to other value
-  - this setting is conrolled by `webhook-bind-port` flag
+  - this setting is controlled by `webhook-bind-port` flag
 
 Jaeger operator config example:
 

diff --git a/content/docs/1.46/operator.md b/content/docs/1.46/operator.md
@@ -972,7 +972,7 @@ In order to workaround that issue:
 - change `/healtz` and `/readyz` ports from 8081 to other value
 - change `kube-rbac-proxy` secure port from 8443 to other value
 - change `webhook-server` port from 9443 to other value
-  - this setting is conrolled by `webhook-bind-port` flag
+  - this setting is controlled by `webhook-bind-port` flag
 
 Jaeger operator config example:
 

diff --git a/content/docs/1.47/operator.md b/content/docs/1.47/operator.md
@@ -972,7 +972,7 @@ In order to workaround that issue:
 - change `/healtz` and `/readyz` ports from 8081 to other value
 - change `kube-rbac-proxy` secure port from 8443 to other value
 - change `webhook-server` port from 9443 to other value
-  - this setting is conrolled by `webhook-bind-port` flag
+  - this setting is controlled by `webhook-bind-port` flag
 
 Jaeger operator config example:
 

diff --git a/content/docs/1.48/getting-started.md b/content/docs/1.48/getting-started.md
@@ -71,7 +71,7 @@ Please see Kubernetes Operator: https://github.com/jaegertracing/jaeger-operator
 ## Sample App: HotROD
 
 HotROD (Rides on Demand) is a demo application that consists of several microservices and illustrates
-the use of [OpenTelemetry][otel] and distirbuted tracing. A tutorial / walkthrough is available in the blog post:
+the use of [OpenTelemetry][otel] and distributed tracing. A tutorial / walkthrough is available in the blog post:
 [Take Jaeger for a HotROD ride][hotrod-tutorial].
 
 The HotROD app can be run standalone, but requires Jaeger backend to view the traces.

diff --git a/content/docs/1.48/operator.md b/content/docs/1.48/operator.md
@@ -972,7 +972,7 @@ In order to workaround that issue:
 - change `/healtz` and `/readyz` ports from 8081 to other value
 - change `kube-rbac-proxy` secure port from 8443 to other value
 - change `webhook-server` port from 9443 to other value
-  - this setting is conrolled by `webhook-bind-port` flag
+  - this setting is controlled by `webhook-bind-port` flag
 
 Jaeger operator config example:
 

diff --git a/content/docs/1.49/getting-started.md b/content/docs/1.49/getting-started.md
@@ -71,7 +71,7 @@ Please see Kubernetes Operator: https://github.com/jaegertracing/jaeger-operator
 ## Sample App: HotROD
 
 HotROD (Rides on Demand) is a demo application that consists of several microservices and illustrates
-the use of [OpenTelemetry][otel] and distirbuted tracing. A tutorial / walkthrough is available in the blog post:
+the use of [OpenTelemetry][otel] and distributed tracing. A tutorial / walkthrough is available in the blog post:
 [Take Jaeger for a HotROD ride][hotrod-tutorial].
 
 The HotROD app can be run standalone, but requires Jaeger backend to view the traces.

diff --git a/content/docs/1.49/operator.md b/content/docs/1.49/operator.md
@@ -972,7 +972,7 @@ In order to workaround that issue:
 - change `/healtz` and `/readyz` ports from 8081 to other value
 - change `kube-rbac-proxy` secure port from 8443 to other value
 - change `webhook-server` port from 9443 to other value
-  - this setting is conrolled by `webhook-bind-port` flag
+  - this setting is controlled by `webhook-bind-port` flag
 
 Jaeger operator config example:
 

diff --git a/content/docs/1.50/getting-started.md b/content/docs/1.50/getting-started.md
@@ -71,7 +71,7 @@ Please see Kubernetes Operator: https://github.com/jaegertracing/jaeger-operator
 ## Sample App: HotROD
 
 HotROD (Rides on Demand) is a demo application that consists of several microservices and illustrates
-the use of [OpenTelemetry][otel] and distirbuted tracing. A tutorial / walkthrough is available in the blog post:
+the use of [OpenTelemetry][otel] and distributed tracing. A tutorial / walkthrough is available in the blog post:
 [Take Jaeger for a HotROD ride][hotrod-tutorial].
 
 The HotROD app can be run standalone, but requires Jaeger backend to view the traces.

diff --git a/content/docs/1.50/operator.md b/content/docs/1.50/operator.md
@@ -972,7 +972,7 @@ In order to workaround that issue:
 - change `/healtz` and `/readyz` ports from 8081 to other value
 - change `kube-rbac-proxy` secure port from 8443 to other value
 - change `webhook-server` port from 9443 to other value
-  - this setting is conrolled by `webhook-bind-port` flag
+  - this setting is controlled by `webhook-bind-port` flag
 
 Jaeger operator config example:
 

diff --git a/content/docs/1.51/getting-started.md b/content/docs/1.51/getting-started.md
@@ -71,7 +71,7 @@ Please see Kubernetes Operator: https://github.com/jaegertracing/jaeger-operator
 ## Sample App: HotROD
 
 HotROD (Rides on Demand) is a demo application that consists of several microservices and illustrates
-the use of [OpenTelemetry][otel] and distirbuted tracing. A tutorial / walkthrough is available in the blog post:
+the use of [OpenTelemetry][otel] and distributed tracing. A tutorial / walkthrough is available in the blog post:
 [Take Jaeger for a HotROD ride][hotrod-tutorial].
 
 The HotROD app can be run standalone, but requires Jaeger backend to view the traces.

diff --git a/content/docs/1.51/operator.md b/content/docs/1.51/operator.md
@@ -972,7 +972,7 @@ In order to workaround that issue:
 - change `/healtz` and `/readyz` ports from 8081 to other value
 - change `kube-rbac-proxy` secure port from 8443 to other value
 - change `webhook-server` port from 9443 to other value
-  - this setting is conrolled by `webhook-bind-port` flag
+  - this setting is controlled by `webhook-bind-port` flag
 
 Jaeger operator config example:
 

diff --git a/content/docs/1.52/getting-started.md b/content/docs/1.52/getting-started.md
@@ -71,7 +71,7 @@ Please see Kubernetes Operator: https://github.com/jaegertracing/jaeger-operator
 ## Sample App: HotROD
 
 HotROD (Rides on Demand) is a demo application that consists of several microservices and illustrates
-the use of [OpenTelemetry][otel] and distirbuted tracing. A tutorial / walkthrough is available in the blog post:
+the use of [OpenTelemetry][otel] and distributed tracing. A tutorial / walkthrough is available in the blog post:
 [Take Jaeger for a HotROD ride][hotrod-tutorial].
 
 The HotROD app can be run standalone, but requires Jaeger backend to view the traces.

diff --git a/content/docs/1.52/operator.md b/content/docs/1.52/operator.md
@@ -972,7 +972,7 @@ In order to workaround that issue:
 - change `/healtz` and `/readyz` ports from 8081 to other value
 - change `kube-rbac-proxy` secure port from 8443 to other value
 - change `webhook-server` port from 9443 to other value
-  - this setting is conrolled by `webhook-bind-port` flag
+  - this setting is controlled by `webhook-bind-port` flag
 
 Jaeger operator config example:
 

diff --git a/content/docs/1.53/getting-started.md b/content/docs/1.53/getting-started.md
@@ -71,7 +71,7 @@ Please see Kubernetes Operator: https://github.com/jaegertracing/jaeger-operator
 ## Sample App: HotROD
 
 HotROD (Rides on Demand) is a demo application that consists of several microservices and illustrates
-the use of [OpenTelemetry][otel] and distirbuted tracing. A tutorial / walkthrough is available in the blog post:
+the use of [OpenTelemetry][otel] and distributed tracing. A tutorial / walkthrough is available in the blog post:
 [Take Jaeger for a HotROD ride][hotrod-tutorial].
 
 The HotROD app can be run standalone, but requires Jaeger backend to view the traces.

diff --git a/content/docs/1.53/operator.md b/content/docs/1.53/operator.md
@@ -972,7 +972,7 @@ In order to workaround that issue:
 - change `/healtz` and `/readyz` ports from 8081 to other value
 - change `kube-rbac-proxy` secure port from 8443 to other value
 - change `webhook-server` port from 9443 to other value
-  - this setting is conrolled by `webhook-bind-port` flag
+  - this setting is controlled by `webhook-bind-port` flag
 
 Jaeger operator config example:
 

diff --git a/content/docs/1.54/getting-started.md b/content/docs/1.54/getting-started.md
@@ -71,7 +71,7 @@ Please see Kubernetes Operator: https://github.com/jaegertracing/jaeger-operator
 ## Sample App: HotROD
 
 HotROD (Rides on Demand) is a demo application that consists of several microservices and illustrates
-the use of [OpenTelemetry][otel] and distirbuted tracing. A tutorial / walkthrough is available in the blog post:
+the use of [OpenTelemetry][otel] and distributed tracing. A tutorial / walkthrough is available in the blog post:
 [Take Jaeger for a HotROD ride][hotrod-tutorial].
 
 The HotROD app can be run standalone, but requires Jaeger backend to view the traces.

diff --git a/content/docs/1.54/operator.md b/content/docs/1.54/operator.md
@@ -972,7 +972,7 @@ In order to workaround that issue:
 - change `/healtz` and `/readyz` ports from 8081 to other value
 - change `kube-rbac-proxy` secure port from 8443 to other value
 - change `webhook-server` port from 9443 to other value
-  - this setting is conrolled by `webhook-bind-port` flag
+  - this setting is controlled by `webhook-bind-port` flag
 
 Jaeger operator config example:
 

diff --git a/content/docs/1.55/getting-started.md b/content/docs/1.55/getting-started.md
@@ -71,7 +71,7 @@ Please see Kubernetes Operator: https://github.com/jaegertracing/jaeger-operator
 ## Sample App: HotROD
 
 HotROD (Rides on Demand) is a demo application that consists of several microservices and illustrates
-the use of [OpenTelemetry][otel] and distirbuted tracing. A tutorial / walkthrough is available in the blog post:
+the use of [OpenTelemetry][otel] and distributed tracing. A tutorial / walkthrough is available in the blog post:
 [Take Jaeger for a HotROD ride][hotrod-tutorial].
 
 The HotROD app can be run standalone, but requires Jaeger backend to view the traces.

diff --git a/content/docs/1.55/operator.md b/content/docs/1.55/operator.md
@@ -972,7 +972,7 @@ In order to workaround that issue:
 - change `/healtz` and `/readyz` ports from 8081 to other value
 - change `kube-rbac-proxy` secure port from 8443 to other value
 - change `webhook-server` port from 9443 to other value
-  - this setting is conrolled by `webhook-bind-port` flag
+  - this setting is controlled by `webhook-bind-port` flag
 
 Jaeger operator config example:
 

diff --git a/content/docs/1.56/getting-started.md b/content/docs/1.56/getting-started.md
@@ -71,7 +71,7 @@ Please see Kubernetes Operator: https://github.com/jaegertracing/jaeger-operator
 ## Sample App: HotROD
 
 HotROD (Rides on Demand) is a demo application that consists of several microservices and illustrates
-the use of [OpenTelemetry][otel] and distirbuted tracing. A tutorial / walkthrough is available in the blog post:
+the use of [OpenTelemetry][otel] and distributed tracing. A tutorial / walkthrough is available in the blog post:
 [Take Jaeger for a HotROD ride][hotrod-tutorial].
 
 The HotROD app can be run standalone, but requires Jaeger backend to view the traces.

diff --git a/content/docs/1.56/operator.md b/content/docs/1.56/operator.md
@@ -972,7 +972,7 @@ In order to workaround that issue:
 - change `/healtz` and `/readyz` ports from 8081 to other value
 - change `kube-rbac-proxy` secure port from 8443 to other value
 - change `webhook-server` port from 9443 to other value
-  - this setting is conrolled by `webhook-bind-port` flag
+  - this setting is controlled by `webhook-bind-port` flag
 
 Jaeger operator config example:
 

diff --git a/content/docs/1.57/getting-started.md b/content/docs/1.57/getting-started.md
@@ -71,7 +71,7 @@ Please see Kubernetes Operator: https://github.com/jaegertracing/jaeger-operator
 ## Sample App: HotROD
 
 HotROD (Rides on Demand) is a demo application that consists of several microservices and illustrates
-the use of [OpenTelemetry][otel] and distirbuted tracing. A tutorial / walkthrough is available in the blog post:
+the use of [OpenTelemetry][otel] and distributed tracing. A tutorial / walkthrough is available in the blog post:
 [Take Jaeger for a HotROD ride][hotrod-tutorial].
 
 The HotROD app can be run standalone, but requires Jaeger backend to view the traces.

diff --git a/content/docs/1.57/operator.md b/content/docs/1.57/operator.md
@@ -972,7 +972,7 @@ In order to workaround that issue:
 - change `/healtz` and `/readyz` ports from 8081 to other value
 - change `kube-rbac-proxy` secure port from 8443 to other value
 - change `webhook-server` port from 9443 to other value
-  - this setting is conrolled by `webhook-bind-port` flag
+  - this setting is controlled by `webhook-bind-port` flag
 
 Jaeger operator config example:
 

diff --git a/content/docs/next-release/getting-started.md b/content/docs/next-release/getting-started.md
@@ -71,7 +71,7 @@ Please see Kubernetes Operator: https://github.com/jaegertracing/jaeger-operator
 ## Sample App: HotROD
 
 HotROD (Rides on Demand) is a demo application that consists of several microservices and illustrates
-the use of [OpenTelemetry][otel] and distirbuted tracing. A tutorial / walkthrough is available in the blog post:
+the use of [OpenTelemetry][otel] and distributed tracing. A tutorial / walkthrough is available in the blog post:
 [Take Jaeger for a HotROD ride][hotrod-tutorial].
 
 The HotROD app can be run standalone, but requires Jaeger backend to view the traces.

diff --git a/content/docs/next-release/operator.md b/content/docs/next-release/operator.md
@@ -936,7 +936,7 @@ In order to workaround that issue:
 - change `/healtz` and `/readyz` ports from 8081 to other value
 - change `kube-rbac-proxy` secure port from 8443 to other value
 - change `webhook-server` port from 9443 to other value
-  - this setting is conrolled by `webhook-bind-port` flag
+  - this setting is controlled by `webhook-bind-port` flag
 
 Jaeger operator config example:
 

diff --git a/content/mentorship-for-mentees.md b/content/mentorship-for-mentees.md
@@ -45,7 +45,7 @@ We do not have an exact checklist that we use for evaluation, but the following
   * their coding and problem solving skills.
 * High quality proposal that demonstrates:
   * good understanding of the problem,
-  * technical due dilligence conducted,
+  * technical due diligence conducted,
   * viable approach to solving the problem.
 * Evidence of previous high quality development tasks completed, e.g., in other open source projects.
 
@@ -101,7 +101,7 @@ Why the log is important:
   in the documentation or the code, then don’t hesitate to ask your mentor for pointers. You can also ask in
   [#jaeger](https://cloud-native.slack.com/archives/CGG7NFUJ3) and #jaeger-mentorships Slack channels.
 - Before embarking on a relatively substantial change, write up a plan on what you plan to do,
-  why and potential challenges or unknowns. Consider documentiing this as a
+  why and potential challenges or unknowns. Consider documenting this as a
   [new issue](https://github.com/jaegertracing/jaeger/issues) in Jaeger.
 - Work on small deliverables at a time, making small enhancements as you go along.
   Breaking down a large task into smaller pieces can help make a seemingly daunting task appear manageable.

diff --git a/scripts/cspell/project-words.txt b/scripts/cspell/project-words.txt
@@ -14,17 +14,13 @@ certfile
 changeme
 clickhouse
 cncf
-conrolled
 containerd
 cqlsh
 cqlshrc
 daemonset
 datacenter
 datasource
 developercertificate
-dilligence
-distirbuted
-documentiing
 downsampling
 dropwizard
 dsoie