Additional fixes

content/en/docs/collector/configuration.md

@@ -3,7 +3,7 @@ title: Configuration
 weight: 20
 description: Learn how to configure the Collector to suit your needs
 # prettier-ignore
-cSpell:ignore: cfssl cfssljson fluentforward gencert genkey hostmetrics initca loglevel OIDC oidc otlphttp pprof prodevent prometheusremotewrite servicegraph spanevents spanmetrics upsert zpages
+cSpell:ignore: cfssl cfssljson fluentforward gencert genkey hostmetrics initca loglevel OIDC oidc otlphttp pprof prodevent prometheusremotewrite servicegraph spanevents spanmetrics upsert zpages struct
 ---
 
 <!-- markdownlint-disable link-fragments -->
@@ -563,8 +563,9 @@ section. See the full list of `logs` options
 The `metrics` subsection lets you configure metrics generated by the Collector.
 By default, the Collector generates basic metrics about itself and expose them
 for scraping at <http://localhost:8888/metrics>. For the full list of options
-for the `metrics` subsection, see the 
-[`ServiceTelemetryMetrics struct`](https://github.com/open-telemetry/opentelemetry-collector/blob/7666eb04c30e5cfd750db9969fe507562598f0ae/config/service.go#L99-L111) comments.
+for the `metrics` subsection, see the
+[`ServiceTelemetryMetrics struct`](https://github.com/open-telemetry/opentelemetry-collector/blob/7666eb04c30e5cfd750db9969fe507562598f0ae/config/service.go#L99-L111)
+comments.
 
 The following example shows Collector telemetry configuration:
 
@@ -633,7 +634,7 @@ Each authentication extension has two possible usages:
 
 For a list of known authenticators, see the
 [Registry](/ecosystem/registry/?s=authenticator&component=extension). If you're
-interested in developing a custom authenticator, see 
+interested in developing a custom authenticator, see
 [Building a custom authenticator](../custom-auth).
 
 To add a server authenticator to a receiver in the Collector, follow these