[chore] Spelling: preexisting..system (#6020)

Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com>

.github/workflows/scripts/check-i18n-helper.sh

@@ -5,7 +5,7 @@ echo "For localization docs, see https://opentelemetry.io/docs/contributing/loca
 CHANGES=`git status --porcelain`
 
 if [[ -z $CHANGES ]]; then
-  echo "All localization pages have the requisit commit hash. <3"
+  echo "All localization pages have the requisite commit hash. <3"
   exit;
 fi
 

content/en/blog/2022/announcing-opentelemetry-demo-release/index.md

@@ -14,7 +14,7 @@ announce
 With this demo, you’ll be able to quickly run a complete end-to-end distributed
 system instrumented with 100% OpenTelemetry Traces and Metrics.
 
-![The system architecture of the demo application represented as directed acyclic graph in Jaeger UI](sytem-architecture.png)
+![The system architecture of the demo application represented as directed acyclic graph in Jaeger UI](system-architecture.png)
 
 One of our primary goals of this project has been to create a robust sample
 application for developers to use in learning OpenTelemetry, and we’re proud to

content/en/blog/2022/demo-announcement/index.md

@@ -7,7 +7,7 @@ author: '[Carter Socha](https://github.com/cartersocha)'
 
 ## TL;DR
 
-The OpenTelemetry community has taken a good pre-existing demo (thanks,
+The OpenTelemetry community has taken a good preexisting demo (thanks,
 [Google](https://github.com/GoogleCloudPlatform/microservices-demo)!) and is in
 the process of making it even better. Every GA SDK (besides Swift) will be
 represented, demo support will be extended to Metrics and Logs, and canonical
@@ -66,8 +66,8 @@ backend choice, and they’re overly reliant on instrumentation libraries.
 As a starting point, we have selected a fork of the popular GCP microservices
 demo. Our first feature additions have been to simplify local deployment by
 consolidating the project onto a single docker compose file, updating the
-documentation, and replacing a pre-existing service with a Ruby example.
-Otherwise the pre-existing feature set from the GCP demo remains the same:
+documentation, and replacing a preexisting service with a Ruby example.
+Otherwise the preexisting feature set from the GCP demo remains the same:
 
 - 10 application microservice with support for 6 languages (C#, Go, Java,
   Node.js, Python, and Ruby)

content/en/blog/2023/lambda-release.md

@@ -21,7 +21,7 @@ had a
 and they've been available on AWS for years.
 
 You're totally correct. Rest assured, we're not reinventing the wheel. However,
-there are some pre-existing problems that may impact users:
+there are some preexisting problems that may impact users:
 
 - The OTel Lambda layers were only released as part of the
   [AWS Distribution for OTel (ADOT)](https://aws-otel.github.io/), and the

content/en/blog/2024/otel-collector-container-log-parser/index.md

@@ -81,7 +81,7 @@ combine them into one at first place:
 
 ```text
 2024-04-06T00:17:10.113242941Z stdout P This is a very very long line th
-2024-04-06T00:17:10.113242941Z stdout P at is really really long and spa
+2024-04-06T00:17:10.113242941Z stdout P at is really, really, long and spa
 2024-04-06T00:17:10.113242941Z stdout F ns across multiple log entries
 ```
 

content/en/docs/collector/troubleshooting.md

@@ -344,8 +344,8 @@ The Collector might exit or restart due to:
 - Memory pressure from a missing or misconfigured
   [`memory_limiter` processor](https://github.com/open-telemetry/opentelemetry-collector/blob/main/processor/memorylimiterprocessor/README.md).
 - Improper sizing for load.
-- Improper configuration. For example, a queue size configured higher than
-  available memory.
+- Improper configuration. For example, a queue sized to be larger than available
+  memory.
 - Infrastructure resource limits. For example, Kubernetes.
 
 #### Collector fails to start in Windows Docker containers

content/en/docs/zero-code/java/spring-boot-starter/annotations.md

@@ -1,7 +1,6 @@
 ---
 title: Annotations
 weight: 50
-cSpell:ignore: proxys
 ---
 
 <!-- markdownlint-disable blanks-around-fences -->
@@ -50,7 +49,7 @@ public class TracedClass {
 <!-- prettier-ignore-end -->
 
 {{% alert title="Note" color="info" %}} The OpenTelemetry annotations use Spring
-AOP based on proxys.
+AOP based on proxies.
 
 These annotations work only for the methods of the proxy. You can learn more in
 the

templates/registry-entry.yml

@@ -7,7 +7,7 @@ tags:
 urls:
   repo: https://github.com/your-organization/your-repo # (mandatory) projects don't have to be hosted on GitHub, but this should link to the git or other source control repository for your project
   docs: https://your-organization/your-instructions # (optional) path to a documentation for the specific project.
-license: Apache 2.0 # or whatever your OSS license is (see https://opensource.org/licenses/), properietary or non-OSI approved may be rejected
+license: Apache 2.0 # or whatever your OSS license is (see https://opensource.org/licenses/), proprietary or non-OSI approved may be rejected
 description: A friendly description of your integration/plugin
 authors:
   - name: First author name