diff --git a/content/en/blogs/cilium-as-cni.md b/content/en/blogs/cilium-as-cni.md
index 61a61e8a9..123012ba6 100644
--- a/content/en/blogs/cilium-as-cni.md
+++ b/content/en/blogs/cilium-as-cni.md
@@ -167,7 +167,7 @@ For more information about Linux compatibility, check out [Linux Distribution Co
 
 Hubble is designed for network visualization. Through the eBPF data paths provided by Cilium, Hubble enables deep visibility into the network traffic of applications and services running on Kubernetes. You can use the Hubble CLI or UI tools to realize quick interactive diagnoses of issues like DNS-related ones. In addition to Hubble's own monitoring tools, you can also extend your monitoring policies by integrating other popular cloud-native monitoring system such as Prometheus and Grafana.
 
-1. Hover your cursor over <img src="/images/blogs/en/cilium-as-cni/hammer.png" width="20px"> and select **Kubectl**.
+1. Hover your cursor over <img src="/images/blogs/en/cilium-as-cni/hammer.png" width="20px" alt="icon" > and select **Kubectl**.
 
    ![kubectl](/images/blogs/en/cilium-as-cni/kubectl.png)
 
@@ -204,7 +204,7 @@ Hubble is designed for network visualization. Through the eBPF data paths provid
 
    ![get-demo](/images/blogs/en/cilium-as-cni/get-demo.png)
 
-3. On the **Services** page of KubeSphere console, select `kube-system` from the drop-down list, enter `hubble` in the search box, and press **Enter**. Click <img src="/images/blogs/en/cilium-as-cni/three-dots.png" width="20px"> on the right of `hubble-ui` and select **Edit Internet Access**.
+3. On the **Services** page of KubeSphere console, select `kube-system` from the drop-down list, enter `hubble` in the search box, and press **Enter**. Click <img src="/images/blogs/en/cilium-as-cni/three-dots.png" width="20px" alt="icon" > on the right of `hubble-ui` and select **Edit Internet Access**.
 
    ![edit-access](/images/blogs/en/cilium-as-cni/edit-access.png)
 
diff --git a/content/en/docs/v3.3/project-administration/disk-log-collection.md b/content/en/docs/v3.3/project-administration/disk-log-collection.md
index c7b4ca23d..634317a22 100644
--- a/content/en/docs/v3.3/project-administration/disk-log-collection.md
+++ b/content/en/docs/v3.3/project-administration/disk-log-collection.md
@@ -51,7 +51,7 @@ This tutorial demonstrates how to collect logs for an example app.
 
    {{</ notice >}} 
 
-6. On the **Storage Settings** tab, click <img src="/images/docs/v3.3/project-administration/disk-log-collection/toggle-switch.png" width="20" /> to enable **Collect Logs on Volumes** and click **Mount Volume**.
+6. On the **Storage Settings** tab, click <img src="/images/docs/v3.3/project-administration/disk-log-collection/toggle-switch.png" width="20" alt="icon" /> to enable **Collect Logs on Volumes** and click **Mount Volume**.
 
 7. On the **Temporary Volume** tab, enter a name for the volume (for example, `demo-disk-log-collection`) and set the access mode and path.
 
@@ -69,7 +69,7 @@ This tutorial demonstrates how to collect logs for an example app.
 
 1. Under the **Deployments** tab, click the Deployment just created to go to its detail page.
 
-2. In **Resource Status**, you can click <img src="/images/docs/v3.3/project-administration/disk-log-collection/arrow.png" width="20" /> to view container details, and then click <img src="/images/docs/v3.3/project-administration/disk-log-collection/log-icon.png" width="20" alt="icon" /> of `logsidecar-container` (filebeat container) to view logs.
+2. In **Resource Status**, you can click <img src="/images/docs/v3.3/project-administration/disk-log-collection/arrow.png" width="20" alt="icon" /> to view container details, and then click <img src="/images/docs/v3.3/project-administration/disk-log-collection/log-icon.png" width="20" alt="icon" /> of `logsidecar-container` (filebeat container) to view logs.
 
-3. Alternatively, you can also click <img src="/images/docs/v3.3/project-administration/disk-log-collection/toolbox.png" width="20" />  in the lower-right corner and select **Log Search** to view stdout logs. For example, use the Pod name of the Deployment for a fuzzy query.
+3. Alternatively, you can also click <img src="/images/docs/v3.3/project-administration/disk-log-collection/toolbox.png" width="20" alt="icon" />  in the lower-right corner and select **Log Search** to view stdout logs. For example, use the Pod name of the Deployment for a fuzzy query.
 
diff --git a/content/en/docs/v3.3/toolbox/events-query.md b/content/en/docs/v3.3/toolbox/events-query.md
index d082aa01f..de6a88c08 100644
--- a/content/en/docs/v3.3/toolbox/events-query.md
+++ b/content/en/docs/v3.3/toolbox/events-query.md
@@ -16,13 +16,13 @@ This guide demonstrates how you can do multi-level, fine-grained event queries t
 
 ## Query Events
 
-1. The event query function is available for all users. Log in to the console with any account, hover over <img src="/images/docs/v3.3/toolbox/event-query/toolbox.png" width='20' /> in the lower-right corner and select **Resource Event Search**.
+1. The event query function is available for all users. Log in to the console with any account, hover over <img src="/images/docs/v3.3/toolbox/event-query/toolbox.png" width='20' alt="icon" /> in the lower-right corner and select **Resource Event Search**.
 
 2. In the displayed dialog box, you can view the number of events that the user has permission to view.
 
     {{< notice note >}}
 
-- KubeSphere supports event queries on each cluster separately if you have enabled the [multi-cluster feature](../../multicluster-management/). You can click <img src="/images/docs/v3.3/toolbox/event-query/drop-down-list.png" width='20' /> on the left of the search box and select a target cluster.
+- KubeSphere supports event queries on each cluster separately if you have enabled the [multi-cluster feature](../../multicluster-management/). You can click <img src="/images/docs/v3.3/toolbox/event-query/drop-down-list.png" width='20' alt="icon" /> on the left of the search box and select a target cluster.
 
 - KubeSphere stores events for the last seven days by default.
 
diff --git a/content/en/docs/v3.3/toolbox/log-query.md b/content/en/docs/v3.3/toolbox/log-query.md
index 4feaedb83..f95bdfbd0 100644
--- a/content/en/docs/v3.3/toolbox/log-query.md
+++ b/content/en/docs/v3.3/toolbox/log-query.md
@@ -16,13 +16,13 @@ You need to enable the [KubeSphere Logging System](../../pluggable-components/lo
 
 ## Enter the Log Query Interface
 
-1. The log query function is available for all users. Log in to the console with any account, hover over <img src="/images/docs/v3.3/toolbox/log-query/toolbox.png" width='20' /> in the lower-right corner and select **Log Search**.
+1. The log query function is available for all users. Log in to the console with any account, hover over <img src="/images/docs/v3.3/toolbox/log-query/toolbox.png" width='20' alt="icon" /> in the lower-right corner and select **Log Search**.
 
 2. In the pop-up window, you can see a time histogram of log numbers, a cluster selection drop-down list, and a log search bar.
 
     {{< notice note >}}
 
-- KubeSphere supports log queries on each cluster separately if you have enabled the [multi-cluster feature](../../multicluster-management/). You can click <img src="/images/docs/v3.3/toolbox/log-query/drop-down-list.png" width='20' /> on the left of the search box and select a target cluster.
+- KubeSphere supports log queries on each cluster separately if you have enabled the [multi-cluster feature](../../multicluster-management/). You can click <img src="/images/docs/v3.3/toolbox/log-query/drop-down-list.png" width='20' alt="icon" /> on the left of the search box and select a target cluster.
 
 - KubeSphere stores logs for last seven days by default.
 
@@ -50,7 +50,7 @@ The log query interface supports dynamic refreshing with 5s, 10s or 15s, and all
 
     {{</ notice >}}
 
-4. In the left panel, you can click <img src="/images/docs/v3.3/toolbox/log-query/view-detail-page.png" width='20' /> to view the Pod details page or container details page.
+4. In the left panel, you can click <img src="/images/docs/v3.3/toolbox/log-query/view-detail-page.png" width='20' alt="icon" /> to view the Pod details page or container details page.
 
 ## Drill into the Details Page
 
diff --git a/content/zh/docs/v3.3/cluster-administration/cluster-settings/cluster-gateway.md b/content/zh/docs/v3.3/cluster-administration/cluster-settings/cluster-gateway.md
index 777e44ec9..706ecd795 100644
--- a/content/zh/docs/v3.3/cluster-administration/cluster-settings/cluster-gateway.md
+++ b/content/zh/docs/v3.3/cluster-administration/cluster-settings/cluster-gateway.md
@@ -69,7 +69,7 @@ KubeSphere v3.3.0 提供集群级别的网关，使所有项目共用一个全
 
 在**网关设置**页面，点击**项目网关**选项卡，以查看项目网关。
 
-点击项目网关右侧的 <img src="/images/docs/v3.3/project-administration/role-and-member-management/three-dots.png" width="20px"> ，从下拉菜单中选择操作：
+点击项目网关右侧的 <img src="/images/docs/v3.3/project-administration/role-and-member-management/three-dots.png" width="20px" alt="icon" > ，从下拉菜单中选择操作：
 
 - **编辑**：编辑项目网关的配置。
 - **关闭**：关闭项目网关。
diff --git a/content/zh/docs/v3.3/cluster-administration/cluster-wide-alerting-and-notification/alerting-policy.md b/content/zh/docs/v3.3/cluster-administration/cluster-wide-alerting-and-notification/alerting-policy.md
index da8f3d12b..84e44c2d3 100644
--- a/content/zh/docs/v3.3/cluster-administration/cluster-wide-alerting-and-notification/alerting-policy.md
+++ b/content/zh/docs/v3.3/cluster-administration/cluster-wide-alerting-and-notification/alerting-policy.md
@@ -63,8 +63,8 @@ KubeSphere 还具有内置策略，一旦满足为这些策略定义的条件，
 
 {{< notice note >}}
 
-您可以点击右上角的 <img src="/images/docs/v3.3/zh-cn/cluster-administration/cluster-wide-alerting-and-notification/alerting-policy-node-level/drop-down-list.png" width='20' /> 选择告警监控的时间范围或者自定义时间范围。
+您可以点击右上角的 <img src="/images/docs/v3.3/zh-cn/cluster-administration/cluster-wide-alerting-and-notification/alerting-policy-node-level/drop-down-list.png" width='20' alt="icon" /> 选择告警监控的时间范围或者自定义时间范围。
 
-您还可以点击右上角的 <img src="/images/docs/v3.3/zh-cn/cluster-administration/cluster-wide-alerting-and-notification/alerting-policy-node-level/refresh.png" width='25' /> 来手动刷新告警监控图。
+您还可以点击右上角的 <img src="/images/docs/v3.3/zh-cn/cluster-administration/cluster-wide-alerting-and-notification/alerting-policy-node-level/refresh.png" width='25' alt="icon" /> 来手动刷新告警监控图。
 
 {{</ notice >}}
diff --git a/content/zh/docs/v3.3/devops-user-guide/how-to-use/pipelines/create-a-pipeline-using-jenkinsfile.md b/content/zh/docs/v3.3/devops-user-guide/how-to-use/pipelines/create-a-pipeline-using-jenkinsfile.md
index a89b6dd18..bfc989222 100644
--- a/content/zh/docs/v3.3/devops-user-guide/how-to-use/pipelines/create-a-pipeline-using-jenkinsfile.md
+++ b/content/zh/docs/v3.3/devops-user-guide/how-to-use/pipelines/create-a-pipeline-using-jenkinsfile.md
@@ -185,7 +185,7 @@ KubeSphere 中可以创建两种类型的流水线：一种是本教程中介绍
 
    {{< notice note >}}
 
-   - 您可以点击该流水线右侧的 <img src="/images/docs/v3.3/common-icons/three-dots.png" width="15" />，然后选择**复制**来创建该流水线的副本。如需并发运行不包含多分支的多个流水线，您可以将这些流水线全选，然后点击**运行**来批量运行它们。
+   - 您可以点击该流水线右侧的 <img src="/images/docs/v3.3/common-icons/three-dots.png" width="15" alt="icon" />，然后选择**复制**来创建该流水线的副本。如需并发运行不包含多分支的多个流水线，您可以将这些流水线全选，然后点击**运行**来批量运行它们。
    - 流水线详情页显示**同步状态**，即 KubeSphere 和 Jenkins 的同步结果。若同步成功，您会看到**成功**图标中打上绿色的对号。
 
    {{</ notice >}} 
diff --git a/content/zh/docs/v3.3/installing-on-linux/cluster-operation/add-edge-nodes.md b/content/zh/docs/v3.3/installing-on-linux/cluster-operation/add-edge-nodes.md
index eea6f1a07..b4a3e0d1f 100644
--- a/content/zh/docs/v3.3/installing-on-linux/cluster-operation/add-edge-nodes.md
+++ b/content/zh/docs/v3.3/installing-on-linux/cluster-operation/add-edge-nodes.md
@@ -136,7 +136,7 @@ KubeSphere 利用 [KubeEdge](https://kubeedge.io/zh/) 将原生容器化应用
 
 3. 在右侧的搜索框中，输入 `clusterconfiguration`，并点击结果查看其详细页面。
 
-4. 点击 `ks-installer` 右侧的 <img src="/images/docs/v3.3/common-icons/three-dots.png" width="15" />，选择**编辑 YAML**。
+4. 点击 `ks-installer` 右侧的 <img src="/images/docs/v3.3/common-icons/three-dots.png" width="15" alt="icon" />，选择**编辑 YAML**。
 
 5. 找到 **metrics_server**，将 `enabled` 的 `false` 更改为 `true`。
 
diff --git a/content/zh/docs/v3.3/project-user-guide/application-workloads/daemonsets.md b/content/zh/docs/v3.3/project-user-guide/application-workloads/daemonsets.md
index f78d0e12b..e93e39a2f 100644
--- a/content/zh/docs/v3.3/project-user-guide/application-workloads/daemonsets.md
+++ b/content/zh/docs/v3.3/project-user-guide/application-workloads/daemonsets.md
@@ -82,7 +82,7 @@ weight: 10230
 
 ### 详情页面
 
-1. 守护进程集创建后会显示列表中。您可以点击右边的 <img src="/images/docs/v3.3/zh-cn/project-user-guide/application-workloads/daemonsets/three-dots.png" width="20px" />，在弹出菜单中选择操作，修改您的守护进程集。
+1. 守护进程集创建后会显示列表中。您可以点击右边的 <img src="/images/docs/v3.3/zh-cn/project-user-guide/application-workloads/daemonsets/three-dots.png" width="20px" alt="icon" />，在弹出菜单中选择操作，修改您的守护进程集。
 
     - **编辑信息**：查看并编辑基本信息。
     - **编辑 YAML**：查看、上传、下载或者更新 YAML 文件。
@@ -123,9 +123,9 @@ weight: 10230
 
 2. 点击右上角的下拉菜单以自定义时间范围和采样间隔。
 
-3. 点击右上角的 <img src="/images/docs/v3.3/zh-cn/project-user-guide/application-workloads/daemonsets/daemonsets_autorefresh_start.png" width="20px" />/<img src="/images/docs/v3.3/zh-cn/project-user-guide/application-workloads/daemonsets/daemonsets_autorefresh_stop.png" width="20px" /> 以开始或停止自动刷新数据。
+3. 点击右上角的 <img src="/images/docs/v3.3/zh-cn/project-user-guide/application-workloads/daemonsets/daemonsets_autorefresh_start.png" width="20px" alt="icon" />/<img src="/images/docs/v3.3/zh-cn/project-user-guide/application-workloads/daemonsets/daemonsets_autorefresh_stop.png" width="20px" alt="icon" /> 以开始或停止自动刷新数据。
 
-4. 点击右上角的 <img src="/images/docs/v3.3/zh-cn/project-user-guide/application-workloads/daemonsets/daemonsets_refresh.png" width="20px" /> 以手动刷新数据。
+4. 点击右上角的 <img src="/images/docs/v3.3/zh-cn/project-user-guide/application-workloads/daemonsets/daemonsets_refresh.png" width="20px" alt="icon" /> 以手动刷新数据。
 
 ### 环境变量
 
diff --git a/content/zh/docs/v3.3/project-user-guide/application-workloads/deployments.md b/content/zh/docs/v3.3/project-user-guide/application-workloads/deployments.md
index 0e4f43484..beb4e12d7 100644
--- a/content/zh/docs/v3.3/project-user-guide/application-workloads/deployments.md
+++ b/content/zh/docs/v3.3/project-user-guide/application-workloads/deployments.md
@@ -84,7 +84,7 @@ weight: 10210
 
 ### 详情页面
 
-1. 部署创建后会显示在列表中。您可以点击右边的 <img src="/images/docs/v3.3/zh-cn/project-user-guide/application-workloads/deployments/three-dots.png" width="20px" />，在弹出菜单中选择操作，修改您的部署。
+1. 部署创建后会显示在列表中。您可以点击右边的 <img src="/images/docs/v3.3/zh-cn/project-user-guide/application-workloads/deployments/three-dots.png" width="20px" alt="icon" />，在弹出菜单中选择操作，修改您的部署。
 
     - **编辑信息**：查看并编辑基本信息。
     - **编辑 YAML**：查看、上传、下载或者更新 YAML 文件。
diff --git a/content/zh/docs/v3.3/project-user-guide/application-workloads/horizontal-pod-autoscaling.md b/content/zh/docs/v3.3/project-user-guide/application-workloads/horizontal-pod-autoscaling.md
index 4c2ab855f..2f88f3a3d 100755
--- a/content/zh/docs/v3.3/project-user-guide/application-workloads/horizontal-pod-autoscaling.md
+++ b/content/zh/docs/v3.3/project-user-guide/application-workloads/horizontal-pod-autoscaling.md
@@ -83,7 +83,7 @@ HPA 功能会自动调整容器组的数量，将容器组的平均资源使用
 
 1. 负载生成器部署创建好后，在左侧导航栏中选择**应用负载**下的**工作负载**，然后点击右侧的 HPA 部署（例如，hpa-v1）。页面中显示的容器组的数量会自动增加以满足资源使用目标。
 
-2. 在左侧导航栏选择**应用负载**中的**工作负载**，点击负载生成器部署（例如，load-generator-v1）右侧的 <img src="/images/docs/v3.3/zh-cn/project-user-guide/application-workloads/horizontal-pod-autoscaling/three-dots.png" width="20px" />，从下拉菜单中选择**删除**。负载生成器部署删除后，再次检查 HPA 部署的状态。容器组的数量会减少到最小值。
+2. 在左侧导航栏选择**应用负载**中的**工作负载**，点击负载生成器部署（例如，load-generator-v1）右侧的 <img src="/images/docs/v3.3/zh-cn/project-user-guide/application-workloads/horizontal-pod-autoscaling/three-dots.png" width="20px" alt="icon" />，从下拉菜单中选择**删除**。负载生成器部署删除后，再次检查 HPA 部署的状态。容器组的数量会减少到最小值。
 
 {{< notice note >}}
 
@@ -99,5 +99,5 @@ HPA 功能会自动调整容器组的数量，将容器组的平均资源使用
 
 1. 在左侧导航栏选择**应用负载**中的**工作负载**，点击右侧的 HPA 部署（例如，hpa-v1）。
 
-2. 点击**自动伸缩**右侧的 <img src="/images/docs/v3.3/zh-cn/project-user-guide/application-workloads/horizontal-pod-autoscaling/three-dots.png" width="20px" />，从下拉菜单中选择**取消**。
+2. 点击**自动伸缩**右侧的 <img src="/images/docs/v3.3/zh-cn/project-user-guide/application-workloads/horizontal-pod-autoscaling/three-dots.png" width="20px" alt="icon" />，从下拉菜单中选择**取消**。
 
diff --git a/content/zh/docs/v3.3/project-user-guide/application-workloads/jobs.md b/content/zh/docs/v3.3/project-user-guide/application-workloads/jobs.md
index 5d43bbe1b..15028da8d 100644
--- a/content/zh/docs/v3.3/project-user-guide/application-workloads/jobs.md
+++ b/content/zh/docs/v3.3/project-user-guide/application-workloads/jobs.md
@@ -115,7 +115,7 @@ weight: 10250
 
     {{< notice tip >}}如果任务失败，您可以重新运行该任务，失败原因显示在**消息**下。{{</ notice >}}
 
-3. 在**资源状态**中，您可以查看容器组状态。先前将**并行容器组数量**设置为 2，因此每次会创建两个容器组。点击右侧的 <img src="/images/docs/v3.3/zh-cn/project-user-guide/application-workloads/jobs/down-arrow.png" width="20px" />，然后点击 <img src="/images/docs/v3.3/zh-cn/project-user-guide/application-workloads/jobs/container-log-icon.png" width="20px" alt="icon" /> 查看容器日志，该日志显示了预期的计算结果。
+3. 在**资源状态**中，您可以查看容器组状态。先前将**并行容器组数量**设置为 2，因此每次会创建两个容器组。点击右侧的 <img src="/images/docs/v3.3/zh-cn/project-user-guide/application-workloads/jobs/down-arrow.png" width="20px" alt="icon" />，然后点击 <img src="/images/docs/v3.3/zh-cn/project-user-guide/application-workloads/jobs/container-log-icon.png" width="20px" alt="icon" /> 查看容器日志，该日志显示了预期的计算结果。
 
     {{< notice tip >}}
 
diff --git a/content/zh/docs/v3.3/project-user-guide/application-workloads/services.md b/content/zh/docs/v3.3/project-user-guide/application-workloads/services.md
index b646ae06b..ccaa986ae 100644
--- a/content/zh/docs/v3.3/project-user-guide/application-workloads/services.md
+++ b/content/zh/docs/v3.3/project-user-guide/application-workloads/services.md
@@ -159,7 +159,7 @@ KubeSphere 提供三种创建服务的基本方法：**无状态服务**、**有
 
 ### 详情页面
 
-1. 创建服务后，您可以点击右侧的 <img src="/images/docs/v3.3/zh-cn/project-user-guide/application-workloads/services/three-dots.png" width="20px" /> 进一步编辑它，例如元数据（**名称**无法编辑）、配置文件、端口以及外部访问。
+1. 创建服务后，您可以点击右侧的 <img src="/images/docs/v3.3/zh-cn/project-user-guide/application-workloads/services/three-dots.png" width="20px" alt="icon" /> 进一步编辑它，例如元数据（**名称**无法编辑）、配置文件、端口以及外部访问。
 
     - **编辑**：查看和编辑基本信息。
     - **编辑 YAML**：查看、上传、下载或者更新 YAML 文件。
@@ -179,7 +179,7 @@ KubeSphere 提供三种创建服务的基本方法：**无状态服务**、**有
 
 1. 点击**资源状态**选项卡以查看服务端口、工作负载和容器组信息。
 
-2. 在**容器组**区域，点击 <img src="/images/docs/v3.3/zh-cn/project-user-guide/application-workloads/services/services_refresh_pods.png" width="20px" /> 以刷新容器组信息，点击 <img src="/images/docs/v3.3/zh-cn/project-user-guide/application-workloads/services/services_display_containers.png" width="20px" />/<img src="/images/docs/v3.3/zh-cn/project-user-guide/application-workloads/services/services_hide_containers.png" width="20px" /> 以显示或隐藏每个容器组中的容器。
+2. 在**容器组**区域，点击 <img src="/images/docs/v3.3/zh-cn/project-user-guide/application-workloads/services/services_refresh_pods.png" width="20px" alt="icon" /> 以刷新容器组信息，点击 <img src="/images/docs/v3.3/zh-cn/project-user-guide/application-workloads/services/services_display_containers.png" width="20px" />/<img src="/images/docs/v3.3/zh-cn/project-user-guide/application-workloads/services/services_hide_containers.png" width="20px" /> 以显示或隐藏每个容器组中的容器。
 
 ### 元数据
 
diff --git a/content/zh/docs/v3.3/project-user-guide/application-workloads/statefulsets.md b/content/zh/docs/v3.3/project-user-guide/application-workloads/statefulsets.md
index 690307978..ec90a5d6b 100644
--- a/content/zh/docs/v3.3/project-user-guide/application-workloads/statefulsets.md
+++ b/content/zh/docs/v3.3/project-user-guide/application-workloads/statefulsets.md
@@ -93,7 +93,7 @@ weight: 10220
 
 ### 详情页面
 
-1. 有状态副本集创建后会显示列表中。您可以点击右边的 <img src="/images/docs/v3.3/zh-cn/project-user-guide/application-workloads/statefulsets/three-dots.png" width="20px" />，在弹出菜单中选择操作，修改您的有状态副本集。
+1. 有状态副本集创建后会显示列表中。您可以点击右边的 <img src="/images/docs/v3.3/zh-cn/project-user-guide/application-workloads/statefulsets/three-dots.png" width="20px" alt="icon" />，在弹出菜单中选择操作，修改您的有状态副本集。
 
     - **编辑信息**：查看并编辑基本信息。
     - **编辑 YAML**：查看、上传、下载或者更新 YAML 文件。
@@ -135,9 +135,9 @@ weight: 10220
 
 2. 点击右上角的下拉菜单以自定义时间范围和采样间隔。
 
-3. 点击右上角的 <img src="/images/docs/v3.3/zh-cn/project-user-guide/application-workloads/statefulsets/statefulsets_autorefresh_start.png" alt="statefulsets_autorefresh_start" width="20px" />/<img src="/images/docs/v3.3/zh-cn/project-user-guide/application-workloads/statefulsets/statefulsets_autorefresh_stop.png" width="20px" /> 以开始或停止自动刷新数据。
+3. 点击右上角的 <img src="/images/docs/v3.3/zh-cn/project-user-guide/application-workloads/statefulsets/statefulsets_autorefresh_start.png" alt="statefulsets_autorefresh_start" width="20px" alt="icon" />/<img src="/images/docs/v3.3/zh-cn/project-user-guide/application-workloads/statefulsets/statefulsets_autorefresh_stop.png" width="20px" alt="icon" /> 以开始或停止自动刷新数据。
 
-4. 点击右上角的 <img src="/images/docs/v3.3/zh-cn/project-user-guide/application-workloads/statefulsets/statefulsets_refresh.png" width="20px" /> 以手动刷新数据。
+4. 点击右上角的 <img src="/images/docs/v3.3/zh-cn/project-user-guide/application-workloads/statefulsets/statefulsets_refresh.png" width="20px" alt="icon" /> 以手动刷新数据。
 
 ### 环境变量
 
diff --git a/content/zh/docs/v3.3/project-user-guide/grayscale-release/canary-release.md b/content/zh/docs/v3.3/project-user-guide/grayscale-release/canary-release.md
index e8e13b722..f69777572 100644
--- a/content/zh/docs/v3.3/project-user-guide/grayscale-release/canary-release.md
+++ b/content/zh/docs/v3.3/project-user-guide/grayscale-release/canary-release.md
@@ -116,7 +116,7 @@ KubeSphere 提供基于 [Jaeger](https://www.jaegertracing.io/) 的分布式追
 
 1. 在**任务状态**中，点击金丝雀发布任务。
 
-2. 在弹出的对话框中，点击 **reviews v2** 右侧的 <img src="/images/docs/v3.3/zh-cn/project-user-guide/grayscale-release/canary-release/three-dots.png" width="20px" />，选择**接管**。这代表 100% 的流量将会被发送到新版本 (v2)。
+2. 在弹出的对话框中，点击 **reviews v2** 右侧的 <img src="/images/docs/v3.3/zh-cn/project-user-guide/grayscale-release/canary-release/three-dots.png" width="20px" alt="icon" />，选择**接管**。这代表 100% 的流量将会被发送到新版本 (v2)。
 
    {{< notice note >}}
    如果新版本出现任何问题，可以随时回滚到之前的 v1 版本。
diff --git a/content/zh/docs/v3.3/project-user-guide/image-builder/source-to-image.md b/content/zh/docs/v3.3/project-user-guide/image-builder/source-to-image.md
index a7e03e2d4..5f6bb5155 100644
--- a/content/zh/docs/v3.3/project-user-guide/image-builder/source-to-image.md
+++ b/content/zh/docs/v3.3/project-user-guide/image-builder/source-to-image.md
@@ -95,7 +95,7 @@ Source-to-Image (S2I) 是一个工具箱和工作流，用于从源代码构建
 
 1. 稍等片刻，您可以看到镜像构建器状态变为**成功**。
 
-2. 点击该镜像构建器前往其详情页面。在**任务记录**下，点击记录右侧的 <img src="/images/docs/v3.3/zh-cn/project-user-guide/image-builder/source-to-image/down-arrow.png" width="20px" /> 查看构建日志。如果一切运行正常，您可以在日志末尾看到 `Build completed successfully`。
+2. 点击该镜像构建器前往其详情页面。在**任务记录**下，点击记录右侧的 <img src="/images/docs/v3.3/zh-cn/project-user-guide/image-builder/source-to-image/down-arrow.png" width="20px" alt="icon" /> 查看构建日志。如果一切运行正常，您可以在日志末尾看到 `Build completed successfully`。
 
 3. 回到**服务**、**部署**和**任务**页面，您可以看到该镜像相应的服务、部署和任务都已成功创建。
 
diff --git a/content/zh/docs/v3.3/toolbox/events-query.md b/content/zh/docs/v3.3/toolbox/events-query.md
index ccee59271..78006db48 100644
--- a/content/zh/docs/v3.3/toolbox/events-query.md
+++ b/content/zh/docs/v3.3/toolbox/events-query.md
@@ -22,13 +22,13 @@ Kubernetes 事件系统用于深入了解集群内部发生的事件，KubeSpher
 
 ## 查询事件
 
-1. 所有用户都可以使用事件查询功能。使用任意帐户登录控制台，在右下角的 <img src="/images/docs/v3.3/zh-cn/toolbox/event-query/toolbox.png" width="20" /> 上悬停，然后在弹出菜单中选择**资源事件查询**。
+1. 所有用户都可以使用事件查询功能。使用任意帐户登录控制台，在右下角的 <img src="/images/docs/v3.3/zh-cn/toolbox/event-query/toolbox.png" width="20" alt="icon" /> 上悬停，然后在弹出菜单中选择**资源事件查询**。
 
 2. 在弹出窗口中，您可以看到该帐户有权限查看的事件数量。
 
     {{< notice note >}}
 
-- 如果您启用了[多集群功能](../../multicluster-management/)，KubeSphere 支持对每个集群分别进行事件查询。您可以点击搜索栏左侧的 <img src="/images/docs/v3.3/zh-cn/toolbox/event-query/drop-down-list.png" width='20' />，然后选择一个目标集群。
+- 如果您启用了[多集群功能](../../multicluster-management/)，KubeSphere 支持对每个集群分别进行事件查询。您可以点击搜索栏左侧的 <img src="/images/docs/v3.3/zh-cn/toolbox/event-query/drop-down-list.png" width='20' alt="icon" />，然后选择一个目标集群。
 
 - KubeSphere 默认存储最近七天的事件。
 
diff --git a/content/zh/docs/v3.3/toolbox/log-query.md b/content/zh/docs/v3.3/toolbox/log-query.md
index c89a8df08..801d49966 100644
--- a/content/zh/docs/v3.3/toolbox/log-query.md
+++ b/content/zh/docs/v3.3/toolbox/log-query.md
@@ -22,14 +22,14 @@ weight: 15100
 
 ## 进入日志查询界面
 
-1. 所有用户都可以使用日志查询功能。使用任意帐户登录控制台，在右下角的 <img src="/images/docs/v3.3/zh-cn/toolbox/log-query/toolbox.png" width='20' /> 上悬停，然后在弹出菜单中选择**日志查询**。
+1. 所有用户都可以使用日志查询功能。使用任意帐户登录控制台，在右下角的 <img src="/images/docs/v3.3/zh-cn/toolbox/log-query/toolbox.png" width='20' alt="icon" /> 上悬停，然后在弹出菜单中选择**日志查询**。
 
 2. 在弹出窗口中，您可以看到日志数量的时间直方图、集群选择下拉列表以及日志查询栏。
 
 
 ​      {{< notice note >}}
 
-- 如果您启用了[多集群功能](../../multicluster-management/)，KubeSphere 支持对每个集群分别进行日志查询。您可以点击搜索栏左侧的 <img src="/images/docs/v3.3/zh-cn/toolbox/log-query/drop-down-list.png" width='20' /> 切换目标集群。
+- 如果您启用了[多集群功能](../../multicluster-management/)，KubeSphere 支持对每个集群分别进行日志查询。您可以点击搜索栏左侧的 <img src="/images/docs/v3.3/zh-cn/toolbox/log-query/drop-down-list.png" width='20' alt="icon" /> 切换目标集群。
 
 - KubeSphere 默认存储最近七天内的日志。
 
@@ -55,15 +55,15 @@ weight: 15100
     {{< notice note >}}
 
 - 日志查询界面支持每 5 秒、10 秒或 15 秒动态刷新一次。
-- 您可以点击右上角的 <img src="/images/docs/v3.3/zh-cn/toolbox/log-query/export-logs.png" width='20' /> 将日志导出至本地文件进行进一步分析。
+- 您可以点击右上角的 <img src="/images/docs/v3.3/zh-cn/toolbox/log-query/export-logs.png" width='20' alt="icon" /> 将日志导出至本地文件进行进一步分析。
 
 {{</ notice >}}
 
-4. 在左侧面板中，您可以点击 <img src="/images/docs/v3.3/zh-cn/toolbox/log-query/drop-down-list.png" width='20' /> 切换 Pod 并查看其在同一个项目中的容器，从而查看是否有任何异常 Pod 影响到其他 Pod。
+4. 在左侧面板中，您可以点击 <img src="/images/docs/v3.3/zh-cn/toolbox/log-query/drop-down-list.png" width='20' alt="icon" /> 切换 Pod 并查看其在同一个项目中的容器，从而查看是否有任何异常 Pod 影响到其他 Pod。
 
 
 ## 进入详情页面
 
-在左侧面板，您可以点击 <img src="/images/docs/v3.3/zh-cn/toolbox/log-query/view-detail-page.png" width='20' /> 查看 Pod 详情页面或容器详情页面。
+在左侧面板，您可以点击 <img src="/images/docs/v3.3/zh-cn/toolbox/log-query/view-detail-page.png" width='20' alt="icon" /> 查看 Pod 详情页面或容器详情页面。
 
 您可以点击右上角的**终端**打开终端为容器排除故障。
diff --git a/content/zh/docs/v3.3/toolbox/metering-and-billing/view-resource-consumption.md b/content/zh/docs/v3.3/toolbox/metering-and-billing/view-resource-consumption.md
index 637590bd8..256da95b8 100644
--- a/content/zh/docs/v3.3/toolbox/metering-and-billing/view-resource-consumption.md
+++ b/content/zh/docs/v3.3/toolbox/metering-and-billing/view-resource-consumption.md
@@ -17,7 +17,7 @@ KubeSphere 计量功能帮助您在不同层级追踪集群或企业空间中的
 
 **集群资源消费情况**包含集群（也包括节点）的资源使用情况，如 CPU、内存、存储等。
 
-1. 使用 `admin` 用户登录 KubeSphere Web 控制台，点击右下角的 <img src="/images/docs/v3.3/zh-cn/toolbox/metering-and-billing/view-resource-consumption/toolbox.png" width='20px' />，然后选择**资源消费统计**。
+1. 使用 `admin` 用户登录 KubeSphere Web 控制台，点击右下角的 <img src="/images/docs/v3.3/zh-cn/toolbox/metering-and-billing/view-resource-consumption/toolbox.png" width='20px' alt="icon" />，然后选择**资源消费统计**。
 
 2. 在**集群资源消费情况**一栏，点击**查看消费**。
 
@@ -58,7 +58,7 @@ KubeSphere 计量功能帮助您在不同层级追踪集群或企业空间中的
 
 **企业空间（项目）资源消费情况**包含企业空间（包括项目）的资源使用情况，如 CPU、内存、存储等。
 
-1. 使用 `admin` 用户登录 KubeSphere Web 控制台，点击右下角的 <img src="/images/docs/v3.3/zh-cn/toolbox/metering-and-billing/view-resource-consumption/toolbox.png" width='20'/> 图标，然后选择**资源消费统计**。
+1. 使用 `admin` 用户登录 KubeSphere Web 控制台，点击右下角的 <img src="/images/docs/v3.3/zh-cn/toolbox/metering-and-billing/view-resource-consumption/toolbox.png" width='20' alt="icon" /> 图标，然后选择**资源消费统计**。
 
 2. 在**企业空间资源消费情况**一栏，点击**查看**。