diff --git a/spring-boot-project/spring-boot-actuator-autoconfigure/src/docs/antora/modules/api/pages/rest/actuator/metrics.adoc b/spring-boot-project/spring-boot-actuator-autoconfigure/src/docs/antora/modules/api/pages/rest/actuator/metrics.adoc
index dfd68ff73626..9c5fcc89221c 100644
--- a/spring-boot-project/spring-boot-actuator-autoconfigure/src/docs/antora/modules/api/pages/rest/actuator/metrics.adoc
+++ b/spring-boot-project/spring-boot-actuator-autoconfigure/src/docs/antora/modules/api/pages/rest/actuator/metrics.adoc
@@ -4,7 +4,7 @@
 The `metrics` endpoint provides access to application metrics to diagnose the metrics the application has recorded.
 This endpoint should not be "scraped" or used as a metrics backend in production.
 Its purpose is to show the currently registered metrics so users can see what metrics are available, what their current values are, and if triggering certain operations cause any change in certain values.
-If you want to diagnose your applications through the metrics they collect, you should use an external metrics backend.
+If you want to diagnose your applications through the metrics they collect, you should use an xref:reference:actuator/metrics.adoc[external metrics backend].
 In this case, the `metrics` endpoint can still be useful.