From f739c72e40fb7fe40ff5aba079f6f41b9aecf6b7 Mon Sep 17 00:00:00 2001
From: Liudmila Molkova <limolkova@microsoft.com>
Date: Mon, 22 Apr 2024 15:44:52 -0700
Subject: [PATCH] Update docs/database/database-metrics.md

---
 docs/database/database-metrics.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/database/database-metrics.md b/docs/database/database-metrics.md
index 37a80415df..ccf76a54b1 100644
--- a/docs/database/database-metrics.md
+++ b/docs/database/database-metrics.md
@@ -48,7 +48,7 @@ This metric is [required][MetricRequired].
 When this metric is reported alongside a database operation span, the metric value SHOULD be the same as the database operation span duration.
 
 This metric SHOULD be specified with
-[`ExplicitBucketBoundaries`](https://github.com/open-telemetry/opentelemetry-specification/tree/v1.26.0/specification/metrics/api.md#instrument-advisory-parameters)
+[`ExplicitBucketBoundaries`](https://github.com/open-telemetry/opentelemetry-specification/tree/v1.31.0/specification/metrics/api.md#instrument-advisory-parameters)
 of `[ 0.001, 0.005, 0.01, 0.05, 0.1, 0.5, 1, 5, 10 ]`.
 
 <!-- semconv metric.db.client.operation.duration(metric_table) -->