Link to local spec pages (#2476)

content/en/blog/2022/debug-otel-with-otel/index.md

@@ -250,7 +250,7 @@ COPY opentelemetry_module.conf /etc/nginx/conf.d
   /blog/2022/instrument-nginx/#put-nginx-between-two-services
 [localhost:16686]: http://localhost:16686/
 [http request & response headers]:
-  https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/trace/semantic_conventions/http.md#http-request-and-response-headers
+  /docs/reference/specification/trace/semantic_conventions/http/#http-request-and-response-headers
 [rfc7230]: https://httpwg.org/specs/rfc7230.html#field.order
 [added some checks to the nginx module]:
   https://github.com/open-telemetry/opentelemetry-cpp-contrib/pull/204

content/en/blog/2022/instrument-kafka-clients/index.md

@@ -23,7 +23,7 @@ comes into the picture. It provides multiple instrumentation libraries for
 adding tracing to messaging based applications. Of course, there is one for
 Apache Kafka clients. It also defines the specification of semantic conventions
 for
-[messaging systems](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/trace/semantic_conventions/messaging.md).
+[messaging systems](/docs/reference/specification/trace/semantic_conventions/messaging/).
 
 But usually, the architecture can even be more complicated: having applications
 not able to connect directly to the Apache Kafka cluster and talking its own

content/en/blog/2023/http-conventions-stability.md

@@ -6,9 +6,8 @@ author: '[Trask Stalnaker](https://github.com/trask) (Microsoft)'
 ---
 
 The OpenTelemetry community is beginning the final push to declare HTTP
-[tracing](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/trace/semantic_conventions/http.md)
-and
-[metrics](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/metrics/semantic_conventions/http-metrics.md)
+[tracing](/docs/reference/specification/trace/semantic_conventions/http/) and
+[metrics](/docs/reference/specification/metrics/semantic_conventions/http-metrics/)
 semantic conventions stable!
 
 Following the recently proposed

content/en/docs/collector/transforming-telemetry.md

@@ -80,7 +80,7 @@ processors:
 ```
 
 The resource processor has an identical configuration, but applies only to
-[resource attributes](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/resource/semantic_conventions/README.md).
+[resource attributes](/docs/reference/specification/resource/semantic_conventions/).
 Use the resource processor to modify infrastructure metadata related to
 telemetry. For example, this inserts the Kubernetes cluster name:
 

content/en/docs/demo/services/frontend.md

@@ -17,7 +17,7 @@ libraries to leverage, or make use of the `getNodeAutoInstrumentations()`
 function which includes most popular frameworks. The
 `utils/telemetry/Instrumentation.js` file contains all code required to
 initialize the SDK and auto-instrumentation based on standard
-[OpenTelemetry environment variables](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/sdk-environment-variables.md)
+[OpenTelemetry environment variables](/docs/reference/specification/sdk-environment-variables/)
 for OTLP export, resource attributes, and service name.
 
 ```javascript

content/en/docs/demo/services/load-generator.md

@@ -18,7 +18,7 @@ Since this service is a
 OpenTelemetry SDK is initialized after the import statements. This code will
 create a tracer provider, and establish a Span Processor to use. Export
 endpoints, resource attributes, and service name are automatically set using
-[OpenTelemetry environment variables](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/sdk-environment-variables.md).
+[OpenTelemetry environment variables](/docs/reference/specification/sdk-environment-variables/).
 
 ```python
 tracer_provider = TracerProvider()

content/en/docs/instrumentation/python/automatic/example.md

@@ -347,7 +347,7 @@ If those headers are available, they will be included in your span:
 ```
 
 [semantic convention]:
-  https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/trace/semantic_conventions/http.md#http-request-and-response-headers
+  /docs/reference/specification/trace/semantic_conventions/http/#http-request-and-response-headers
 [api reference]:
   https://opentelemetry-python.readthedocs.io/en/latest/index.html
 [distro]: