From dd33b10ca1a27962d84ccaf91e0a50a367d5803d Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?=E8=B5=B7=E5=B2=9A?=
 <155608604+xiaoyaoqilan@users.noreply.github.com>
Date: Mon, 10 Aug 2026 17:40:15 +0800
Subject: [PATCH] [Ascend] Requests-only pods skip memory validation, so an
 over-capacity request

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

diff --git a/docs/develop/design.md b/docs/develop/design.md
index 1f10c7f0f5..28dc220391 100644
--- a/docs/develop/design.md
+++ b/docs/develop/design.md
@@ -6,7 +6,7 @@ The architecture of HAMi is shown in the figure above. It is organized in the fo
 
 - MutatingWebhook
 
-The MutatingWebhook checks the validity of each task, and set the "schedulerName" to "HAMi scheduler" if the resource requests have been recognized by HAMi
+The MutatingWebhook checks the validity of each task, and set the "schedulerName" to "HAMi scheduler" if the resource limits have been recognized by HAMi
 If Not, the MutatingWebhook does nothing and pass this task to default-scheduler.
 
 - Scheduler