diff --git a/Documentation/ceph-csi-drivers.md b/Documentation/ceph-csi-drivers.md
index dd10a2ca7..31b94e0cf 100644
--- a/Documentation/ceph-csi-drivers.md
+++ b/Documentation/ceph-csi-drivers.md
@@ -121,15 +121,18 @@ kubectl delete -f cluster/examples/kubernetes/ceph/csi/example/rbd/snapshot.yaml
 kubectl delete -f cluster/examples/kubernetes/ceph/csi/example/rbd/snapshotclass.yaml
 ```
 
-#### Liveness Sidecar
+## Liveness Sidecar
+
 All CSI pods are deployed with a sidecar container that provides a prometheus metric for tracking if the CSI plugin is alive and runnning.
 These metrics are meant to be collected by prometheus but can be acceses through a GET request to a specific node ip.
 for example `curl -X get http://[pod ip]:[liveness-port][liveness-path]  2>/dev/null | grep csi`
 the expected output should be
+
 ```bash
-[root@worker2 /]# curl -X GET http://10.109.65.142:9080/metrics 2>/dev/null | grep csi
+curl -X GET http://10.109.65.142:9080/metrics 2>/dev/null | grep csi
 # HELP csi_liveness Liveness Probe
 # TYPE csi_liveness gauge
 csi_liveness 1
 ```
-Check the [monitoring doc](https://github.com/rook/rook.github.io/blob/master/docs/rook/master/ceph-monitoring.md) to see how to integrate CSI liveness into ceph monitoring.
+
+Check the [monitoring doc](ceph-monitoring.md) to see how to integrate CSI liveness into ceph monitoring.