diff --git a/docs/content/en/docs/fleet-manager/rollout/abtest.md b/docs/content/en/docs/fleet-manager/rollout/abtest.md
index 62886800..8bef0fa3 100644
--- a/docs/content/en/docs/fleet-manager/rollout/abtest.md
+++ b/docs/content/en/docs/fleet-manager/rollout/abtest.md
@@ -114,6 +114,7 @@ istio-system   public-gateway   17s
 When Nginx is specified in fleet's `rollout.trafficRoutingProvider` , Kurator will install Nginx and its supporting Prometheus via helm in the fleet-managed clusters.
 
 You can review the results a few minutes after applying fleet:
+
 ```console
 kubectl get po -n ingress-nginx --kubeconfig=/root/.kube/kurator-member1.config   
 NAME                                                              READY   STATUS    RESTARTS   AGE
@@ -347,6 +348,7 @@ If the status shows as `Initialized`, it means the initialization of rollout pro
 **Notes**: In the above configuration, we set the `kustomization.interval` to 0s. This disables Fluxcd's periodic synchronization of configurations between the local mirror and cluster. The reason is that Flagger needs to modify the replica counts in Deployments to complete its initialization process. If you are uncertain whether the replicas for all applications in your deployments are set to zero, it is recommended to also set `kustomization.interval` to 0s.
 
 ### Using Nginx
+
 You can deploy a abtest application demo using Nginx by the following command:
 
 ```console
@@ -439,8 +441,7 @@ spec:
         timeout: 2m0s
 ```
 
-To use Nginx, you need to provide the `host` it uses. Kurator will generate an ingress resource based on this field. Here is the [specific configuration generated](/docs/references/app-api/#apps.kurator.dev/v1alpha1.TrafficRoutingConfig).
-. Other configurations are the same as above.
+To use Nginx, you need to provide the `host` it uses. Kurator will generate an ingress resource based on this field. Here is the [specific configuration generated](/docs/references/app-api/#apps.kurator.dev/v1alpha1.TrafficRoutingConfig). Other configurations are the same as above.
 
 **Notes:**There is a problem with the metric provided by the current flagger, so `customMetric` is used.Here is the detailed [API](/docs/references/app-api/#apps.kurator.dev/v1alpha1.Metric).
 
diff --git a/docs/content/en/docs/fleet-manager/rollout/blue-green.md b/docs/content/en/docs/fleet-manager/rollout/blue-green.md
index f2e35ae6..5a9807f4 100644
--- a/docs/content/en/docs/fleet-manager/rollout/blue-green.md
+++ b/docs/content/en/docs/fleet-manager/rollout/blue-green.md
@@ -114,6 +114,7 @@ istio-system   public-gateway   17s
 When Nginx is specified in fleet's `rollout.trafficRoutingProvider` , Kurator will install Nginx and its supporting Prometheus via helm in the fleet-managed clusters.
 
 You can review the results a few minutes after applying fleet:
+
 ```console
 kubectl get po -n ingress-nginx --kubeconfig=/root/.kube/kurator-member1.config
 NAME                                                              READY   STATUS    RESTARTS   AGE
@@ -339,6 +340,7 @@ If the status shows as `Initialized`, it means the initialization of rollout pro
 **Notes**: In the above configuration, we set the `kustomization.interval` to 0s. This disables Fluxcd's periodic synchronization of configurations between the local mirror and cluster. The reason is that Flagger needs to modify the replica counts in Deployments to complete its initialization process. If you are uncertain whether the replicas for all applications in your deployments are set to zero, it is recommended to also set `kustomization.interval` to 0s.
 
 ### Using Nginx
+
 You can deploy a blue-green application demo using Nginx by the following command:
 
 ```console
@@ -346,6 +348,7 @@ kubectl apply -f examples/rollout/blue_greenNginx.yaml
 ```
 
 Here is the configuration:
+
 ```yaml
 apiVersion: apps.kurator.dev/v1alpha1
 kind: Application
@@ -424,8 +427,7 @@ spec:
         timeout: 2m0s
 ```
 
-To use Nginx, you need to provide the `host` it uses. Kurator will generate an ingress resource based on this field. Here is the [specific configuration generated](/docs/references/app-api/#apps.kurator.dev/v1alpha1.TrafficRoutingConfig).
-. Other configurations are the same as above.
+To use Nginx, you need to provide the `host` it uses. Kurator will generate an ingress resource based on this field. Here is the [specific configuration generated](/docs/references/app-api/#apps.kurator.dev/v1alpha1.TrafficRoutingConfig). Other configurations are the same as above.
 
 **Notes:**There is a problem with the metric provided by the current flagger, so `customMetric` is used.Here is the detailed [API](/docs/references/app-api/#apps.kurator.dev/v1alpha1.Metric).
 
diff --git a/docs/content/en/docs/fleet-manager/rollout/canary.md b/docs/content/en/docs/fleet-manager/rollout/canary.md
index f5913fcb..b2c1fabb 100644
--- a/docs/content/en/docs/fleet-manager/rollout/canary.md
+++ b/docs/content/en/docs/fleet-manager/rollout/canary.md
@@ -110,9 +110,11 @@ istio-system   public-gateway   17s
 ```
 
 ### Kuma
+
 When Kuma is specified in fleet's `rollout.trafficRoutingProvider` , Kurator will install Kuma via helm in the fleet-managed clusters.
 
 You can review the results a few minutes after applying fleet:
+
 ```console
 kubectl get po -n kuma-system --kubeconfig=/root/.kube/kurator-member1.config
 NAME                                                              READY   STATUS    RESTARTS   AGE
@@ -129,6 +131,7 @@ You can install Prometheus paired with Kuma using the following commands:
 export KUBECONFIG=/root/.kube/kurator-member1.config
 kumactl install observability --components "prometheus" | kubectl apply -f -
 ```
+
 **Note:**Refer to [kuma documentation](https://docs.konghq.com/mesh/latest/production/install-kumactl/) for instructions on installing kumactl.
 
 Review the results:
@@ -165,7 +168,6 @@ EOF
 Review the results:
 
 ```console
-TODO:
 kubectl get mesh --kubeconfig=/root/.kube/kurator-member1.config
            
 NAME      AGE
@@ -178,6 +180,7 @@ default   12m
 When Nginx is specified in fleet's `rollout.trafficRoutingProvider` , Kurator will install Nginx and its supporting Prometheus via helm in the fleet-managed clusters.
 
 You can review the results a few minutes after applying fleet:
+
 ```console
 kubectl get po -n ingress-nginx --kubeconfig=/root/.kube/kurator-member1.config
 NAME                                                              READY   STATUS    RESTARTS   AGE
@@ -414,6 +417,7 @@ kubectl apply -f examples/rollout/canaryKuma.yaml
 ```
 
 Here is the configuration:
+
 ```yaml
 apiVersion: apps.kurator.dev/v1alpha1
 kind: Application
@@ -496,10 +500,10 @@ spec:
 
 To use Kuma, you need to provide the `protocol` it uses. If you do not specify the protocol, Kurator will use `http` by default. Other configurations are the same as above.
 
-**Notes:**There is a problem with the metric provided by the current flagger, so `customMetric` is used.Here is the detailed [API]( 
-/docs/references/app-api/#apps.kurator.dev/v1alpha1.Metric).
+**Notes:**There is a problem with the metric provided by the current flagger, so `customMetric` is used.Here is the detailed [API](/docs/references/app-api/#apps.kurator.dev/v1alpha1.Metric).
 
 ### Using Nginx
+
 You can deploy a canary application demo using Nginx by the following command:
 
 ```console
@@ -507,6 +511,7 @@ kubectl apply -f examples/rollout/canaryNginx.yaml
 ```
 
 Here is the configuration:
+
 ```yaml
 apiVersion: apps.kurator.dev/v1alpha1
 kind: Application