[chore] Spelling: the..typescript (#6037)

Signed-off-by: Josh Soref <[email protected]>

Author: jsoref

content/en/blog/2024/otel-operator-q-and-a/index.md

@@ -130,8 +130,8 @@ along with the
 
 For every Collector release, there is an Operator release which provides support
 for that Collector version. For example, at the time of this writing, the latest
-Operator version is 0.98.0. Thus, the the default image of the Collector used by
-the Operator is version 0.98.0 of the
+Operator version is 0.98.0. Thus, the default image of the Collector used by the
+Operator is version 0.98.0 of the
 [core distribution](/blog/2024/otel-collector-anti-patterns/#3--not-using-the-right-collector-distribution-or-not-building-your-own-distribution)
 (as opposed to the contrib distribution).
 

content/en/blog/2024/prom-and-otel/index.md

@@ -220,7 +220,7 @@ Let’s dig into each of these.
 The Target Allocator’s first job is to discover targets to scrape and OTel
 Collectors to allocate targets to. It does so as follows:
 
-1. The Target Allocator finds all of the the metrics targets to scrape
+1. The Target Allocator finds all of the metrics targets to scrape
 2. The Target Allocator finds all of the available Collectors
 3. The Target Allocator determines which Collectors scrape which metrics
 4. The Collectors query the Target Allocator to find out what metrics to scrape

content/en/docs/concepts/components.md

@@ -133,7 +133,7 @@ For more information, see [K8s Operator](/docs/kubernetes/operator/).
 OpenTelemetry supports various methods of monitoring Function-as-a-Service
 provided by different cloud vendors. The OpenTelemetry community currently
 provides pre-built Lambda layers able to auto-instrument your application as
-well as a the option of standalone Collector Lambda layer that can be used when
+well as the option of a standalone Collector Lambda layer that can be used when
 instrumenting applications manually or automatically.
 
 For more information, see [Functions as a Service](/docs/faas/).

content/en/docs/faas/_index.md

@@ -19,7 +19,7 @@ also known as Lambda.
 ### Community Assets
 
 The OpenTelemetry community currently provides pre-built Lambda layers able to
-auto-instrument your application as well as a the option of standalone Collector
+auto-instrument your application as well as the option of a standalone Collector
 Lambda layer that can be used when instrumenting applications manually or
 automatically.
 

content/en/docs/languages/js/exporters.md

@@ -51,7 +51,7 @@ JavaScript) from the
 [Getting Started](/docs/languages/js/getting-started/nodejs/) like the following
 to export traces and metrics via OTLP (`http/protobuf`) :
 
-{{< tabpane text=true >}} {{% tab Typescript %}}
+{{< tabpane text=true >}} {{% tab TypeScript %}}
 
 ```ts
 /*instrumentation.ts*/
@@ -256,7 +256,7 @@ npm install --save @opentelemetry/exporter-prometheus
 Update your OpenTelemetry configuration to use the exporter and to send data to
 your Prometheus backend:
 
-{{< tabpane text=true >}} {{% tab Typescript %}}
+{{< tabpane text=true >}} {{% tab TypeScript %}}
 
 ```ts
 import * as opentelemetry from '@opentelemetry/sdk-node';
@@ -314,7 +314,7 @@ npm install --save @opentelemetry/exporter-zipkin
 Update your OpenTelemetry configuration to use the exporter and to send data to
 your Zipkin backend:
 
-{{< tabpane text=true >}} {{% tab Typescript %}}
+{{< tabpane text=true >}} {{% tab TypeScript %}}
 
 ```ts
 import * as opentelemetry from '@opentelemetry/sdk-node';
@@ -347,7 +347,7 @@ const sdk = new opentelemetry.NodeSDK({
 
 {{% docs/languages/exporters/outro js "https://open-telemetry.github.io/opentelemetry-js/interfaces/_opentelemetry_sdk_trace_base.SpanExporter.html" %}}
 
-{{< tabpane text=true >}} {{% tab Typescript %}}
+{{< tabpane text=true >}} {{% tab TypeScript %}}
 
 ```ts
 /*instrumentation.ts*/

scripts/registry-scanner/index.mjs

@@ -281,7 +281,7 @@ async function createFilesFromScanResult(existing, found, settings) {
         current.html_url,
         parsedReadme.description,
       );
-      // collector entries are named reverse (collector-{registryTpe}) compared to languages ({registryTpe}-{language}), we fix this here.
+      // collector entries are named reverse (collector-{registryType}) compared to languages ({registryType}-{language}), we fix this here.
       const fileName = (
         language === 'collector'
           ? `${language}-${registryType}-${currentKey}.yml`