diff --git a/en/device-dev/subsystems/figures/call-chain-trace-in-synchronous-communication.png b/en/device-dev/subsystems/figures/call-chain-trace-in-synchronous-communication.png
new file mode 100644
index 0000000000000000000000000000000000000000..585d8aac7b4857645b78ab11effbe900e5350f9d
Binary files /dev/null and b/en/device-dev/subsystems/figures/call-chain-trace-in-synchronous-communication.png differ
diff --git a/en/device-dev/subsystems/subsys-dfx-faultlogger.md b/en/device-dev/subsystems/subsys-dfx-faultlogger.md
index f93b4ba889ade3d50331f759c1a99fabbbe0f7d7..21513ea9cf913eff37a626c7e74294e95fde69ed 100644
--- a/en/device-dev/subsystems/subsys-dfx-faultlogger.md
+++ b/en/device-dev/subsystems/subsys-dfx-faultlogger.md
@@ -46,7 +46,7 @@ The following table describes the application scenarios.
 | Crash fault location| Crash log and addr2line tool| For details, see [Locating Faults Based on the Crash Log](#locating-faults-based-on-the-crash-log).|
 
 
-## Using DumpCatcher APIs to Obtain the Call Stack Information
+## Using DumpCatcher APIs to Obtain Call Stack Information
 
 
 ### Available APIs
diff --git a/en/device-dev/subsystems/subsys-dfx-hitracechain.md b/en/device-dev/subsystems/subsys-dfx-hitracechain.md
index f8a7c70451cf0b7b357492d7fd01ba9aca287e36..e58467e1ca4814649adfc40bad1f28be1b96f4d5 100644
--- a/en/device-dev/subsystems/subsys-dfx-hitracechain.md
+++ b/en/device-dev/subsystems/subsys-dfx-hitracechain.md
@@ -146,7 +146,9 @@ Some built-in communication mechanisms (such as ZIDL) of OpenHarmony already sup
 The following figure shows the process of transferring **traceid** in synchronous call. The process of transferring **traceid** in asynchronous call is similar.
 
   Extended communication mechanisms can also follow this implementation.
+
   **Figure 5** Call chain trace in synchronous communication
+
   ![](figures/call-chain-trace-in-synchronous-communication.png "call-chain-trace-in-synchronous-communication")
 
 The process is as follows: