fixed a few broken anchors

Author: ericallam

docs/config/config-file.mdx

@@ -165,7 +165,10 @@ You can also configure custom telemetry exporters to send your traces, logs, and
 ```
 
 <Note>
-  Axiom's `/v1/metrics` endpoint only supports protobuf (`application/x-protobuf`), not JSON. Use `@opentelemetry/exporter-metrics-otlp-proto` instead of `@opentelemetry/exporter-metrics-otlp-http` for metrics. Traces and logs work fine with the `-http` (JSON) exporters.
+  Axiom's `/v1/metrics` endpoint only supports protobuf (`application/x-protobuf`), not JSON. Use
+  `@opentelemetry/exporter-metrics-otlp-proto` instead of
+  `@opentelemetry/exporter-metrics-otlp-http` for metrics. Traces and logs work fine with the
+  `-http` (JSON) exporters.
 </Note>
 
 Then, configure the exporters in your `trigger.config.ts` file:
@@ -264,8 +267,6 @@ export default defineConfig({
 });
 ```
 
-Each metric exporter is automatically wrapped in a `PeriodicExportingMetricReader`. If you need more control over the reader configuration (e.g., custom export intervals), use `metricReaders` instead.
-
 ## Runtime
 
 We currently only officially support the `node` runtime, but you can try our experimental `bun` runtime by setting the `runtime` option in your config file:
@@ -492,8 +493,9 @@ export default defineConfig({
 ```
 
 <Note>
-  Any packages that install or build a native binary or use WebAssembly (WASM) should be added to external, as they
-  cannot be bundled. For example, `re2`, `sharp`, `sqlite3`, and WASM packages should be added to external.
+  Any packages that install or build a native binary or use WebAssembly (WASM) should be added to
+  external, as they cannot be bundled. For example, `re2`, `sharp`, `sqlite3`, and WASM packages
+  should be added to external.
 </Note>
 
 ### JSX

docs/logging.mdx

@@ -82,7 +82,7 @@ export const customTrace = task({
 
 Trigger.dev collects system and runtime metrics automatically for deployed tasks, and provides an API for recording custom metrics using OpenTelemetry.
 
-You can view metrics in the [Metrics dashboards](/insights/metrics), query them with [TRQL](/insights/query), and export them to external services via [telemetry exporters](/config/config-file#telemetry).
+You can view metrics in the [Metrics dashboards](/insights/metrics), query them with [TRQL](/insights/query), and export them to external services via [telemetry exporters](/config/config-file#telemetry-exporters).
 
 ### Custom metrics API
 
@@ -199,4 +199,4 @@ See the [Query page](/insights/query#metrics-table-columns) for the full `metric
 
 ### Exporting metrics
 
-You can send metrics to external observability services (Axiom, Honeycomb, Datadog, etc.) by configuring [telemetry exporters](/config/config-file#telemetry) in your `trigger.config.ts`.
+You can send metrics to external observability services (Axiom, Honeycomb, Datadog, etc.) by configuring [telemetry exporters](/config/config-file#telemetry-exporters) in your `trigger.config.ts`.