diff --git a/tidb-resource-control-runaway-queries.md b/tidb-resource-control-runaway-queries.md
index bcf12ea11a835..901da621dd75a 100644
--- a/tidb-resource-control-runaway-queries.md
+++ b/tidb-resource-control-runaway-queries.md
@@ -37,7 +37,9 @@ There are three methods for `WATCH` to match for quick identification:
 
 The `DURATION` option in `WATCH` indicates the duration of the identification item, which is infinite by default.
 
-After a watch item is added, neither the matching feature nor the `ACTION` is changed or deleted whenever the `QUERY_LIMIT` configuration is changed or deleted. You can use `QUERY WATCH REMOVE` to remove a watch item.
+After a watch item is added, neither the matching feature nor the `ACTION` is changed or deleted whenever the `QUERY_LIMIT` configuration is changed or deleted.
+
+You can use `QUERY WATCH REMOVE` to remove a watch item, or use `QUERY WATCH REMOVE RESOURCE GROUP` (New in v9.0.0) to remove all watch items of a specific resource group in a batch.
 
 The parameters of `QUERY_LIMIT` are as follows:
 
@@ -134,6 +136,12 @@ The parameters are as follows:
     QUERY WATCH REMOVE 1;
     ```
 
+- Remove all watch items of a specific resource group (New in v9.0.0):
+
+    ```sql
+    QUERY WATCH REMOVE RESOURCE GROUP rg1;
+    ```
+
 ## Observability
 
 You can get more information about runaway queries from the following system tables and `INFORMATION_SCHEMA`: