[editorial] normalize link to prometheus docs (open-telemetry#3232)

Co-authored-by: Carlos Alberto Cortez <[email protected]>

specification/compatibility/prometheus_and_openmetrics.md

@@ -180,7 +180,7 @@ When scraping a Prometheus endpoint, resource attributes MUST be added to the
 scraped metrics to distinguish them from metrics from other Prometheus
 endpoints. In particular, `service.name` and `service.instance.id`, are needed
 to ensure Prometheus exporters can disambiguate metrics using
-[`job` and `instance` labels](https://Prometheus.io/docs/concepts/jobs_instances/#jobs-and-instances)
+[`job` and `instance` labels](https://prometheus.io/docs/concepts/jobs_instances/#jobs-and-instances)
 as [described below](#resource-attributes-1).
 
 The following attributes MUST be associated with scraped metrics as resource
@@ -348,7 +348,7 @@ An [OpenTelemetry Summary](../metrics/data-model.md#summary-legacy) MUST be conv
 ### Metric Attributes
 
 OpenTelemetry Metric Attributes MUST be converted to
-[Prometheus labels](https://Prometheus.io/docs/concepts/data_model/#metric-names-and-labels).
+[Prometheus labels](https://prometheus.io/docs/concepts/data_model/#metric-names-and-labels).
 String Attribute values are converted directly to Metric Attributes, and
 non-string Attribute values MUST be converted to string attributes following
 the [attribute specification](../common/README.md#attribute).  Prometheus
@@ -387,9 +387,9 @@ possible for metrics from multiple targets to be sent together, so targets must
 be disambiguated from one another. However, the Prometheus exposition format
 and [remote-write](https://github.com/Prometheus/Prometheus/blob/main/prompb/remote.proto)
 formats do not include a notion of resource, and expect metric labels to
-distinguish scraped targets. By convention, [`job` and `instance`](https://Prometheus.io/docs/concepts/jobs_instances/#jobs-and-instances)
+distinguish scraped targets. By convention, [`job` and `instance`](https://prometheus.io/docs/concepts/jobs_instances/#jobs-and-instances)
 labels distinguish targets and are expected to be present on metrics exposed on
-a Prometheus pull exporter (a ["federated"](https://Prometheus.io/docs/Prometheus/latest/federation/)
+a Prometheus pull exporter (a ["federated"](https://prometheus.io/docs/prometheus/latest/federation/)
 Prometheus endpoint) or pushed via Prometheus remote-write. In OTLP, the
 `service.name`, `service.namespace`, and `service.instance.id` triplet is
 [required to be unique](../resource/semantic_conventions/README.md#service),