Java agent config: link into local spec pages (#1474)

content/en/docs/instrumentation/java/automatic/agent-config.md

@@ -2,6 +2,7 @@
 title: Agent Configuration
 linkTitle: Configuration
 weight: 2
+spelling: cSpell:ignore autoconfiguration Autoconfiguration Dotel HSET javaagent serverlessapis Servlet servlet
 ---
 
 > <h3>NOTE: subject to change!</h3>
@@ -71,9 +72,9 @@ Common settings that apply to multiple instrumentations at once.
 
 ### Peer service name
 
-The [peer service name](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/trace/semantic_conventions/span-general.md#general-remote-service-attributes)
+The [peer service name](/docs/reference/specification/trace/semantic_conventions/span-general/#general-remote-service-attributes)
 is the name of a remote service to which a connection is made. It corresponds to `service.name` in
-the [Resource](https://github.com/open-telemetry/opentelemetry-specification/tree/main/specification/resource/semantic_conventions#service)
+the [resource](/docs/reference/specification/resource/semantic_conventions/#service)
 for the local service.
 
 {{% config_option name="otel.instrumentation.common.peer-service-mapping" %}}
@@ -116,7 +117,7 @@ to disable it:
 ### Capturing HTTP request and response headers
 
 You can configure the agent to capture predefined HTTP headers as span attributes, according to the
-[semantic convention](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/trace/semantic_conventions/http.md#http-request-and-response-headers).
+[semantic convention](/docs/reference/specification/trace/semantic_conventions/http/#http-request-and-response-headers).
 Use the following properties to define which HTTP headers you want to capture:
 
 {{% config_option name="otel.instrumentation.http.capture-headers.client.request" %}}
@@ -305,11 +306,11 @@ set `OTEL_INSTRUMENTATION_AKKA_ACTOR_ENABLED` to `false`.
 ### Suppressing controller and/or view spans
 
 Some instrumentations (e.g. Spring Web MVC instrumentation) produce
-[SpanKind.Internal](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/trace/api.md#spankind)
+[SpanKind.Internal](/docs/reference/specification/trace/api/#spankind)
 spans to capture the controller and/or view execution.
 These spans can be suppressed using the configuration settings below, without suppressing the entire
 instrumentation which would also disable the instrumentation's capturing of `http.route` and associated span name on the parent
-[SpanKind.Server](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/trace/api.md#spankind)
+[SpanKind.Server](/docs/reference/specification/trace/api/#spankind)
 span.
 
 {{% config_option