chore: Fix spelling errors and typos in documentation (#3044)

Co-authored-by: Cijo Thomas <[email protected]>

Author: Copilot

.cspell.json

@@ -12,7 +12,8 @@
     "ignoreWords": [
         "otel",
         "rustdoc",
-        "rustfilt"
+        "rustfilt",
+        "webkpi"
     ],
     // these are words that are always considered incorrect.
     "flagWords": [
@@ -34,47 +35,61 @@
         "Bhasin",
         "Björn",
         "BLRP",
+        "chrono",
         "Cijo",
         "clippy",
         "clonable",
         "codecov",
+        "dashmap",
         "datapoint",
         "deque",
         "Dirkjan",
         "docsrs",
         "Dwarnings",
+        "eprintln",
         "EPYC",
         "flamegraph",
         "Gerring",
+        "grpcio",
         "Grübel",
         "hasher",
+        "impls",
+        "isahc",
         "Isobel",
         "jaegertracing",
         "Kühle",
         "Kumar",
         "Lalit",
         "LIBCLANG",
+        "logrecord",
         "MILLIS",
+        "mpsc",
         "msrv",
         "mykey",
+        "myunit",
         "myvalue",
         "nocapture",
         "Ochtman",
         "opentelemetry",
+        "openzipkin",
+        "otcorrelations",
         "OTELCOL",
         "OTLP",
         "periodicreader",
         "Pillai",
         "pprof",
+        "protos",
         "prost",
         "protoc",
         "quantile",
+        "quantiles",
         "Redelmeier",
         "reqwest",
         "rstest",
         "runtimes",
         "rustc",
         "rustls",
+        "schemars",
         "semconv",
         "serde",
         "shoppingcart",
@@ -83,10 +98,18 @@
         "testcontainers",
         "testresults",
         "thiserror",
+        "traceparent",
+        "Traceparent",
         "tracerprovider",
+        "tracestate",
+        "UCUM",
         "Umesan",
+        "unsampled",
         "updown",
+        "urlencoding",
+        "usize",
         "Utkarsh",
+        "webpki",
         "Zhongyang",
         "zipkin"
     ],

docs/adr/001_error_handling.md

@@ -4,13 +4,13 @@
 
 ## Summary
 
-This ADR describes the general pattern we will follow when modelling errors in public API interfaces - that is, APIs that are exposed to users of the project's published crates. It summarises the discussion and final option from [#2571](https://github.com/open-telemetry/opentelemetry-rust/issues/2571); for more context check out that issue. 
+This ADR describes the general pattern we will follow when modelling errors in public API interfaces - that is, APIs that are exposed to users of the project's published crates. It summarizes the discussion and final option from [#2571](https://github.com/open-telemetry/opentelemetry-rust/issues/2571); for more context check out that issue. 
 
 We will focus on the exporter traits in this example, but the outcome should be applied to _all_ public traits and their fallible operations. 
 
 These include [SpanExporter](https://github.com/open-telemetry/opentelemetry-rust/blob/eca1ce87084c39667061281e662d5edb9a002882/opentelemetry-sdk/src/trace/export.rs#L18), [LogExporter](https://github.com/open-telemetry/opentelemetry-rust/blob/eca1ce87084c39667061281e662d5edb9a002882/opentelemetry-sdk/src/logs/export.rs#L115), and [PushMetricExporter](https://github.com/open-telemetry/opentelemetry-rust/blob/eca1ce87084c39667061281e662d5edb9a002882/opentelemetry-sdk/src/metrics/exporter.rs#L11) which form part of the API surface of `opentelemetry-sdk`.
 
-There are various ways to handle errors on trait methods, including swallowing them and logging, panicing, returning a shared global error, or returning a method-specific error. We strive for consistency, and we want to be sure that we've put enough thought into what this looks like that we don't have to make breaking interface changes unecessarily in the future.
+There are various ways to handle errors on trait methods, including swallowing them and logging, panicking, returning a shared global error, or returning a method-specific error. We strive for consistency, and we want to be sure that we've put enough thought into what this looks like that we don't have to make breaking interface changes unnecessarily in the future.
 
 ## Design Guidance
 
@@ -69,7 +69,7 @@ trait MyTrait {
 
 ## 3. Consolidate error types between signals where we can, let them diverge where we can't
 
-Consider the `Exporter`s mentioned earlier. Each of them has the same failure indicators - as dicated by the OpenTelemetry spec  - and we will
+Consider the `Exporter`s mentioned earlier. Each of them has the same failure indicators - as dictated by the OpenTelemetry spec  - and we will
 share the error types accordingly: 
 
 **Don't do this** - each signal has its own error type, despite having exactly the same failure cases: 

opentelemetry-http/CHANGELOG.md

@@ -53,7 +53,7 @@ Released 2024-Sep-30
 
 ## v0.12.0
 
-- Add `reqwest-rustls-webkpi-roots` feature flag to configure [`reqwest`](https://docs.rs/reqwest/0.11.27/reqwest/index.html#optional-features) to use embedded `webkpi-roots`.
+- Add `reqwest-rustls-webpki-roots` feature flag to configure [`reqwest`](https://docs.rs/reqwest/0.11.27/reqwest/index.html#optional-features) to use embedded `webpki-roots`.
 - Update `opentelemetry` dependency version to 0.23
 
 ## v0.11.1

opentelemetry-otlp/CHANGELOG.md

@@ -27,7 +27,7 @@ Released 2025-Mar-21
 - Update `opentelemetry-http` dependency version to 0.29
 - Update `opentelemetry-proto` dependency version to 0.29
 
-- The `OTEL_EXPORTER_OTLP_TIMEOUT`, `OTEL_EXPORTER_OTLP_TRACES_TIMEOUT`, `OTEL_EXPORTER_OTLP_METRICS_TIMEOUT` and `OTEL_EXPORTER_OTLP_LOGS_TIMEOUT` are changed from seconds to miliseconds.
+- The `OTEL_EXPORTER_OTLP_TIMEOUT`, `OTEL_EXPORTER_OTLP_TRACES_TIMEOUT`, `OTEL_EXPORTER_OTLP_METRICS_TIMEOUT` and `OTEL_EXPORTER_OTLP_LOGS_TIMEOUT` are changed from seconds to milliseconds.
 - Fixed `.with_headers()` in `HttpExporterBuilder` to correctly support multiple key/value pairs. [#2699](https://github.com/open-telemetry/opentelemetry-rust/pull/2699)
 - Fixed
   [#2770](https://github.com/open-telemetry/opentelemetry-rust/issues/2770)
@@ -199,7 +199,7 @@ now use `.with_resource(RESOURCE::default())` to configure Resource when using
 ### Added
 
 - Added `DeltaTemporalitySelector` ([#1568])
-- Add `webkpi-roots` features to `reqwest` and `tonic` backends
+- Add `webpki-roots` features to `reqwest` and `tonic` backends
 
 [#1568]: https://github.com/open-telemetry/opentelemetry-rust/pull/1568
 

opentelemetry-sdk/CHANGELOG.md

@@ -189,7 +189,7 @@ Released 2025-Mar-21
  needs to mutate state, it should rely on interior mutability.
  [2764](https://github.com/open-telemetry/opentelemetry-rust/pull/2764)
 - *Breaking (Affects custom Exporter/Processor authors only)* Removed
- `opentelelemetry_sdk::logs::error::{LogError, LogResult}`. These were not
+ `opentelemetry_sdk::logs::error::{LogError, LogResult}`. These were not
  intended to be public. If you are authoring custom processor/exporters, use
  `opentelemetry_sdk::error::OTelSdkError` and
  `opentelemetry_sdk::error::OTelSdkResult`.

opentelemetry/CHANGELOG.md

@@ -35,7 +35,7 @@ predictable and efficient observability pipelines.
 
 Release 2025-Apr-01
 
-- Bug Fix: Re-export `WithContext` at `opentelemetry::trace::context::WithContext` [#2879](https://github.com/open-telemetry/opentelemetry-rust/pull/2879) to restore backwards compatability
+- Bug Fix: Re-export `WithContext` at `opentelemetry::trace::context::WithContext` [#2879](https://github.com/open-telemetry/opentelemetry-rust/pull/2879) to restore backwards compatibility
   - The new path for `WithContext` and `FutureExt` are in  `opentelemetry::context` as they are independent of the trace signal. Users should prefer this path.
 
 ## 0.29.0
@@ -504,7 +504,7 @@ and SDK are still unstable.
 - Use current span for SDK-less context propagation #510
 - Always export span batch when limit reached #519
 - Rename message events to events #530
-- Update resource merge behaviour #537
+- Update resource merge behavior #537
 - Ignore links with invalid context #538
 
 ## Removed
@@ -529,7 +529,7 @@ use `opentelemetry::global::shutdown_tracer_provider` explicitly instead.
 
 ## Changed
 
-- Pull configrations from environment variables by default when creating BatchSpanProcessor #445
+- Pull configurations from environment variables by default when creating BatchSpanProcessor #445
 - Convert doc links to intra-doc #466
 - Switch to Cow for event names #471
 - Use API to configure async runtime instead of features #481
@@ -826,7 +826,7 @@ use `opentelemetry::global::shutdown_tracer_provider` explicitly instead.
 - Make trace and metrics features optional
 - ExportResult as specified in the specification
 - Add Futures compatibility API
-- Added serde serialise support to SpanData
+- Added serde serialize support to SpanData
 - Separate OpenTelemetry Jaeger crate
 
 ### Changed