diff --git a/apis/apps/v1/cluster_types.go b/apis/apps/v1/cluster_types.go
index d3acc768ac4..5074b278783 100644
--- a/apis/apps/v1/cluster_types.go
+++ b/apis/apps/v1/cluster_types.go
@@ -475,8 +475,6 @@ type ClusterComponentSpec struct {
 	//
 	// Setting instances to offline allows for a controlled scale-in process, preserving their data and maintaining
 	// ordinal consistency within the Cluster.
-	// Note that offline instances and their associated resources, such as PVCs, are not automatically deleted.
-	// The administrator must manually manage the cleanup and removal of these resources when they are no longer needed.
 	//
 	// +optional
 	OfflineInstances []string `json:"offlineInstances,omitempty"`
diff --git a/config/crd/bases/apps.kubeblocks.io_clusters.yaml b/config/crd/bases/apps.kubeblocks.io_clusters.yaml
index bd077974696..31b1c1005ce 100644
--- a/config/crd/bases/apps.kubeblocks.io_clusters.yaml
+++ b/config/crd/bases/apps.kubeblocks.io_clusters.yaml
@@ -3827,8 +3827,6 @@ spec:
 
                         Setting instances to offline allows for a controlled scale-in process, preserving their data and maintaining
                         ordinal consistency within the Cluster.
-                        Note that offline instances and their associated resources, such as PVCs, are not automatically deleted.
-                        The administrator must manually manage the cleanup and removal of these resources when they are no longer needed.
                       items:
                         type: string
                       type: array
@@ -12580,8 +12578,6 @@ spec:
 
                             Setting instances to offline allows for a controlled scale-in process, preserving their data and maintaining
                             ordinal consistency within the Cluster.
-                            Note that offline instances and their associated resources, such as PVCs, are not automatically deleted.
-                            The administrator must manually manage the cleanup and removal of these resources when they are no longer needed.
                           items:
                             type: string
                           type: array
diff --git a/deploy/helm/crds/apps.kubeblocks.io_clusters.yaml b/deploy/helm/crds/apps.kubeblocks.io_clusters.yaml
index bd077974696..31b1c1005ce 100644
--- a/deploy/helm/crds/apps.kubeblocks.io_clusters.yaml
+++ b/deploy/helm/crds/apps.kubeblocks.io_clusters.yaml
@@ -3827,8 +3827,6 @@ spec:
 
                         Setting instances to offline allows for a controlled scale-in process, preserving their data and maintaining
                         ordinal consistency within the Cluster.
-                        Note that offline instances and their associated resources, such as PVCs, are not automatically deleted.
-                        The administrator must manually manage the cleanup and removal of these resources when they are no longer needed.
                       items:
                         type: string
                       type: array
@@ -12580,8 +12578,6 @@ spec:
 
                             Setting instances to offline allows for a controlled scale-in process, preserving their data and maintaining
                             ordinal consistency within the Cluster.
-                            Note that offline instances and their associated resources, such as PVCs, are not automatically deleted.
-                            The administrator must manually manage the cleanup and removal of these resources when they are no longer needed.
                           items:
                             type: string
                           type: array
diff --git a/docs/developer_docs/api-reference/cluster.md b/docs/developer_docs/api-reference/cluster.md
index d2c34f71d2e..5ccbe3f4b1c 100644
--- a/docs/developer_docs/api-reference/cluster.md
+++ b/docs/developer_docs/api-reference/cluster.md
@@ -3131,9 +3131,7 @@ future reuse or data recovery, but it is no longer actively used.</li>
 and avoiding conflicts with new instances.</li>
 </ol>
 <p>Setting instances to offline allows for a controlled scale-in process, preserving their data and maintaining
-ordinal consistency within the Cluster.
-Note that offline instances and their associated resources, such as PVCs, are not automatically deleted.
-The administrator must manually manage the cleanup and removal of these resources when they are no longer needed.</p>
+ordinal consistency within the Cluster.</p>
 </td>
 </tr>
 <tr>