diff --git a/opentelemetry-proto/src/opentelemetry/proto/metrics/v1/metrics_pb2.pyi b/opentelemetry-proto/src/opentelemetry/proto/metrics/v1/metrics_pb2.pyi
index 7bb4d95b10..b3e3e4d04d 100644
--- a/opentelemetry-proto/src/opentelemetry/proto/metrics/v1/metrics_pb2.pyi
+++ b/opentelemetry-proto/src/opentelemetry/proto/metrics/v1/metrics_pb2.pyi
@@ -959,7 +959,7 @@ class HistogramDataPoint(google.protobuf.message.Message):
     events, and is assumed to be monotonic over the values of these events.
     Negative events *can* be recorded, but sum should not be filled out when
     doing so.  This is specifically to enforce compatibility w/ OpenMetrics,
-    see: https://github.com/OpenObservability/OpenMetrics/blob/main/specification/OpenMetrics.md#histogram
+    see: https://github.com/prometheus/OpenMetrics/blob/v1.0.0/specification/OpenMetrics.md#histogram
     """
     @property
     def bucket_counts(
@@ -1205,7 +1205,7 @@ class ExponentialHistogramDataPoint(google.protobuf.message.Message):
     events, and is assumed to be monotonic over the values of these events.
     Negative events *can* be recorded, but sum should not be filled out when
     doing so.  This is specifically to enforce compatibility w/ OpenMetrics,
-    see: https://github.com/OpenObservability/OpenMetrics/blob/main/specification/OpenMetrics.md#histogram
+    see: https://github.com/prometheus/OpenMetrics/blob/v1.0.0/specification/OpenMetrics.md#histogram
     """
     scale: builtins.int
     """scale describes the resolution of the histogram.  Boundaries are
@@ -1451,7 +1451,7 @@ class SummaryDataPoint(google.protobuf.message.Message):
     events, and is assumed to be monotonic over the values of these events.
     Negative events *can* be recorded, but sum should not be filled out when
     doing so.  This is specifically to enforce compatibility w/ OpenMetrics,
-    see: https://github.com/OpenObservability/OpenMetrics/blob/main/specification/OpenMetrics.md#summary
+    see: https://github.com/prometheus/OpenMetrics/blob/v1.0.0/specification/OpenMetrics.md#summary
     """
     @property
     def quantile_values(
diff --git a/opentelemetry-semantic-conventions/src/opentelemetry/semconv/_incubating/metrics/hw_metrics.py b/opentelemetry-semantic-conventions/src/opentelemetry/semconv/_incubating/metrics/hw_metrics.py
index ca615236e7..78199c68ad 100644
--- a/opentelemetry-semantic-conventions/src/opentelemetry/semconv/_incubating/metrics/hw_metrics.py
+++ b/opentelemetry-semantic-conventions/src/opentelemetry/semconv/_incubating/metrics/hw_metrics.py
@@ -98,7 +98,7 @@ def create_hw_power(
 Operational status: `1` (true) or `0` (false) for each of the possible states
 Instrument: updowncounter
 Unit: 1
-Note: `hw.status` is currently specified as an *UpDownCounter* but would ideally be represented using a [*StateSet* as defined in OpenMetrics](https://github.com/OpenObservability/OpenMetrics/blob/main/specification/OpenMetrics.md#stateset). This semantic convention will be updated once *StateSet* is specified in OpenTelemetry. This planned change is not expected to have any consequence on the way users query their timeseries backend to retrieve the values of `hw.status` over time.
+Note: `hw.status` is currently specified as an *UpDownCounter* but would ideally be represented using a [*StateSet* as defined in OpenMetrics](https://github.com/prometheus/OpenMetrics/blob/v1.0.0/specification/OpenMetrics.md#stateset). This semantic convention will be updated once *StateSet* is specified in OpenTelemetry. This planned change is not expected to have any consequence on the way users query their timeseries backend to retrieve the values of `hw.status` over time.
 """