From 75c656f11796da8cfa2888b72a8cb74e9b8b39cf Mon Sep 17 00:00:00 2001
From: Taichi Haradaguchi <20001722@protonmail.com>
Date: Mon, 13 Jan 2025 10:52:35 +0900
Subject: [PATCH] ICU-22921 Fix broken link in userguide

* Fix link from gitdev to ci/exhaustive-tests.
* Fix link from ci to gitdev.
---
 docs/userguide/dev/ci.md     | 2 +-
 docs/userguide/dev/gitdev.md | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/docs/userguide/dev/ci.md b/docs/userguide/dev/ci.md
index 378fbcba3fe9..57399daccf5a 100644
--- a/docs/userguide/dev/ci.md
+++ b/docs/userguide/dev/ci.md
@@ -29,7 +29,7 @@ ICU4J's unit tests in JUnit).
 
 ICU uses Continuous Integration systems to run these tests automatically for each new code contribution,
 and upon each update to a future contribution under development
-(that is: for each [successful Pull Request merge, and upon a new push of new git commits to a Pull Request](../gitdev.md)).
+(that is: for each [successful Pull Request merge, and upon a new push of new git commits to a Pull Request](./gitdev.md)).
 ICU has GitHub Actions configured to run Continuous Integration testing.
 
 Continuous Integration systems can also be used to regularly and automatically run other tasks besides testing.
diff --git a/docs/userguide/dev/gitdev.md b/docs/userguide/dev/gitdev.md
index 91a04b4194a4..a247d8896b4c 100644
--- a/docs/userguide/dev/gitdev.md
+++ b/docs/userguide/dev/gitdev.md
@@ -596,4 +596,4 @@ every Saturday (at 4:00 AM UTC) and post merging on the maintenance branches.
 They do not run on pull-requests by default as they take 1-2 hours to run.
 
 However, you can manually request the CI builds to run the exhaustive tests.
-See [Continuous Integration / Exhaustive Tests](../ci.md#exhaustive-tests).
+See [Continuous Integration / Exhaustive Tests](./ci.md#exhaustive-tests).