diff --git a/docs/content/en/docs/fleet-manager/rollout/abtest/nginx-abtest.md b/docs/content/en/docs/fleet-manager/rollout/abtest/nginx-abtest.md
index 32f61875..b05836c0 100644
--- a/docs/content/en/docs/fleet-manager/rollout/abtest/nginx-abtest.md
+++ b/docs/content/en/docs/fleet-manager/rollout/abtest/nginx-abtest.md
@@ -139,7 +139,7 @@ spec:
         timeout: 2m0s
 ```
 
-**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).
 
 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 as follow.
 
diff --git a/docs/content/en/docs/fleet-manager/rollout/blue-green/nginx-blue-green.md b/docs/content/en/docs/fleet-manager/rollout/blue-green/nginx-blue-green.md
index e71e38f2..387153c1 100644
--- a/docs/content/en/docs/fleet-manager/rollout/blue-green/nginx-blue-green.md
+++ b/docs/content/en/docs/fleet-manager/rollout/blue-green/nginx-blue-green.md
@@ -131,7 +131,7 @@ spec:
         timeout: 2m0s
 ```
 
-**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).
 
 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). 
 
diff --git a/docs/content/en/docs/fleet-manager/rollout/canary/kuma-canary.md b/docs/content/en/docs/fleet-manager/rollout/canary/kuma-canary.md
index 6eee8f1c..b988760a 100644
--- a/docs/content/en/docs/fleet-manager/rollout/canary/kuma-canary.md
+++ b/docs/content/en/docs/fleet-manager/rollout/canary/kuma-canary.md
@@ -183,7 +183,7 @@ spec:
         timeout: 2m0s
 ```
 
-**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).
 
 To use Kuma, you need to provide the `protocol` it uses. If you do not specify the protocol, Kurator will use `http` by default. 
 
diff --git a/docs/content/en/docs/fleet-manager/rollout/canary/nginx-canary.md b/docs/content/en/docs/fleet-manager/rollout/canary/nginx-canary.md
index 4f9bd686..2e5c7650 100644
--- a/docs/content/en/docs/fleet-manager/rollout/canary/nginx-canary.md
+++ b/docs/content/en/docs/fleet-manager/rollout/canary/nginx-canary.md
@@ -133,7 +133,7 @@ spec:
         timeout: 2m0s
 ```
 
-**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).
 
 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).