From dcbc7cd8bee39659889789ea5fad32f41995b778 Mon Sep 17 00:00:00 2001
From: Yuhang Guo <22561797+Sherry520@users.noreply.github.com>
Date: Wed, 23 Sep 2026 18:03:13 +0800
Subject: [PATCH] Update maintaining.asc

Fix broken maintain Git link
---
 book/05-distributed-git/sections/maintaining.asc | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/book/05-distributed-git/sections/maintaining.asc b/book/05-distributed-git/sections/maintaining.asc
index c377bb68d..0fa69d552 100644
--- a/book/05-distributed-git/sections/maintaining.asc
+++ b/book/05-distributed-git/sections/maintaining.asc
@@ -364,7 +364,7 @@ When a topic branch has finally been merged into `master`, it's removed from the
 The Git project also has a `maint` branch that is forked off from the last release to provide backported patches in case a maintenance release is required.
 Thus, when you clone the Git repository, you have four branches that you can check out to evaluate the project in different stages of development, depending on how cutting edge you want to be or how you want to contribute; and the maintainer has a structured workflow to help them vet new contributions.
 The Git project's workflow is specialized.
-To clearly understand this you could check out the https://github.com/git/git/blob/master/Documentation/howto/maintain-git.txt[Git Maintainer's guide^].
+To clearly understand this you could check out the https://github.com/git/git/blob/master/Documentation/howto/maintain-git.adoc[Git Maintainer's guide^].
 
 [[_rebase_cherry_pick]]
 ===== Rebasing and Cherry-Picking Workflows