correct image ref in markdown for PodOpsLifecycle doc

docs/operating/concepts/podopslifecycle.md

@@ -22,15 +22,15 @@ In PodOpsLifecycle, participants are classified into two roles: `operation contr
 
 The two types of controllers do not need to be aware of each other. All controllers are organized by PodOpsLifecycle. Additionally, KusionStack Operating introduces extra phases around the native Kubernetes Pod Lifecycle: ServiceAvailable, Preparing, and Completing.
 
-<img src="../../../static/img/operating/concepts/podopslifecycle/pod-ops-lifecycle.png" width="800"/>
+![pod-ops-lifecycle](../../../static/img/operating/concepts/podopslifecycle/pod-ops-lifecycle.png)
 
 - **Completing**: After a Pod is created or updated and becomes ready, Operating marks its PodOpsLifecycle as the `Completing` phase. During this phase, the Pod is in a ready condition, prompting cooperation controllers to perform actions such as registering the Pod IP in the traffic route. Once all cooperation controllers complete their tasks, Operating sets the PodOpsLifecycle to the `ServiceAvailable` phase.
 - **ServiceAvailable**: This phase indicates that the Pod is in a normal state and ready to serve. If everything goes smoothly, the Pod remains in the `ServiceAvailable` phase until the next operation.
 - **Preparing**: When an operation controller needs to operate the Pod, it triggers a new PodOpsLifecycle. The Pod then transitions from the `ServiceAvailable` phase to the `Preparing` phase. During this phase, the Pod is initially marked as Unready by setting ReadinessGate to false. All cooperation controllers then begin preparing tasks, such as removing the Pod's IP from the traffic route. After completing these tasks, the Pod enters the `Operating` phase.
 - **Operating**: If a Pod enters the `Operating` phase, it is expected to accept any kind of operation without any damage, including recreation, scaling-in, upgrading, etc. Operation controllers are permitted to apply any changes to this Pod. Once all these operations are completed, the Pod advances to the next phase — `Completing`, and the PodOpsLifecycle continues.
   The relationship between PodOpsLifecycle and Kubernetes native Pod Lifecycle can be checked by following sequence diagram.
 
-<img src="../../../static/img/operating/concepts/podopslifecycle/pod-ops-lifecycle-sequence-diagram.png"/>
+![pod-ops-lifecycle-sequence-diagram](../../../static/img/operating/concepts/podopslifecycle/pod-ops-lifecycle-sequence-diagram.png)
 
 ## Developer's Guide