[chore] Two spelling lints. (#12892)

#### Description

The cSpell action has been flaky for two reasons, fixed here.

Author: jmacd

CHANGELOG.md

@@ -3464,7 +3464,7 @@ This release is marked as "bad" since the metrics pipelines will produce bad dat
 - Rename ForEach (in pdata) with Range to be consistent with sync.Map (#2931)
 - Rename `componenthelper.Start` to `componenthelper.StartFunc` (#2880)
 - Rename `componenthelper.Stop` to `componenthelper.StopFunc` (#2880)
-- Remove `exporterheleper.WithCustomUnmarshaler`, `processorhelper.WithCustomUnmarshaler`, `receiverhelper.WithCustomUnmarshaler`, `extensionheleper.WithCustomUnmarshaler`, implement `config.CustomUnmarshaler` interface instead (#2867)
+- Remove `exporterhelper.WithCustomUnmarshaler`, `processorhelper.WithCustomUnmarshaler`, `receiverhelper.WithCustomUnmarshaler`, `extensionhelper.WithCustomUnmarshaler`, implement `config.CustomUnmarshaler` interface instead (#2867)
 - Remove `component.CustomUnmarshaler` implement `config.CustomUnmarshaler` interface instead (#2867)
 - Remove `testutil.HostPortFromAddr`, users can write their own parsing helper (#2919)
 - Remove `configparser.DecodeTypeAndName`, use `config.IDFromString` (#2869)

docs/rfcs/env-vars.md

@@ -104,9 +104,8 @@ environment variable whose name is stored in the URL
 The environment variable value is parsed by the yaml.v3 parser to an
 any-typed variable. The yaml.v3 parser mostly follows the YAML v1.2
 specification with [*some exceptions*](https://github.com/go-yaml/yaml#compatibility). 
-You can see
-how it works for some edge cases in this example:
-[`go.dev/play/p/3vNLznwSZQe`](https://go.dev/play/p/3vNLznwSZQe).
+You can see how it works for some edge cases in
+[this go.dev/play example](https://go.dev/play/p/3vNLznwSZQe).
 
 ### Issues of current behavior