update doc

Signed-off-by: Nshawn_he <shawn.he@huawei.com>

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

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: