[yunikorn-site] branch master updated: [YUNIKORN-1753] [ADDENDUM] Fix build issue (again)

[cc...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

ccondit pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/yunikorn-site.git


The following commit(s) were added to refs/heads/master by this push:
     new 422e5cc6c [YUNIKORN-1753] [ADDENDUM] Fix build issue (again)
422e5cc6c is described below

commit 422e5cc6ce1cb59ee6895f9d82dfb1f0c6880eca
Author: Craig Condit <cc...@apache.org>
AuthorDate: Tue May 23 13:18:12 2023 -0500

    [YUNIKORN-1753] [ADDENDUM] Fix build issue (again)
---
 docs/user_guide/prometheus.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/user_guide/prometheus.md b/docs/user_guide/prometheus.md
index 40a803e13..9025878a5 100644
--- a/docs/user_guide/prometheus.md
+++ b/docs/user_guide/prometheus.md
@@ -26,7 +26,7 @@ YuniKorn exposes its scheduling metrics via Prometheus. Thus, we need to set up
 
 We will provide two methods for building Prometheus: either running it locally or using Helm to deploy it in your cluster. Additionally, in the Helm version, we will explain how to integrate it with Grafana and provide generic Grafana Dashboards for monitoring Yunikorn's metrics and observing the changes over time.
 
-If you don't know what metric can be used, you can use [REST API](scheduler#metrics).
+If you don't know what metric can be used, you can use [REST API](../api/scheduler.md#metrics).
 
 ## Run Prometheus locally