diff --git a/developer-guide/concepts-and-designs/sig-observability/kubesphere-monitoring.md b/developer-guide/concepts-and-designs/sig-observability/kubesphere-monitoring.md
index 4a5f83806..abc7960b9 100644
--- a/developer-guide/concepts-and-designs/sig-observability/kubesphere-monitoring.md
+++ b/developer-guide/concepts-and-designs/sig-observability/kubesphere-monitoring.md
@@ -2,7 +2,7 @@
 
 ## Overview
 
-The KubeSphere monitoring system comprises many components that work together to achieve overall monitoring functionality. KubeSphere defaults to installing the monitoring module. It will deploy  or create a few components within the namespace `kubesphere-monitoring-system`:
+The KubeSphere monitoring system comprises of many components that work together to achieve overall monitoring functionality. KubeSphere defaults to installing the monitoring module. It will deploy or create a few components within the namespace `kubesphere-monitoring-system`:
 
 - Prometheus Operator: automates tasks for operating Prometheus instances.
 - Prometheus: scrapes metrics and provides monitoring service.
@@ -15,7 +15,7 @@ Besides, the monitoring stack includes CRD resources:
 - Prometheus: defines a desired Prometheus deployment.
 - PrometheusRule: defines a desired Prometheus rule file.
 
-In KubeSphere, Prometheus will monitor the following services by default: 
+In KubeSphere, Prometheus will monitor the following services by default:
 
 - kube-state-metrics
 - node-exporter
@@ -33,4 +33,4 @@ The [contrib/kube-prometheus](https://github.com/kubesphere/prometheus-operator/
 
 The diagram below presents the overall monitoring architecture:
 
-![](../../images/kubesphere-monitoring-architecture.png)
+![Monitoring Arch](../../images/kubesphere-monitoring-architecture.png)