From f5b41c22e5503b207ad3e82f6ac01fe34be73621 Mon Sep 17 00:00:00 2001 From: king_he <6384784@qq.com> Date: Mon, 16 May 2022 03:39:09 +0000 Subject: [PATCH] update en/device-dev/driver/driver-platform-dac-develop.md. Signed-off-by: king_he <6384784@qq.com> --- en/device-dev/driver/driver-platform-dac-develop.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/en/device-dev/driver/driver-platform-dac-develop.md b/en/device-dev/driver/driver-platform-dac-develop.md index 04edd78547..50b0bc60da 100644 --- a/en/device-dev/driver/driver-platform-dac-develop.md +++ b/en/device-dev/driver/driver-platform-dac-develop.md @@ -36,7 +36,7 @@ The DAC module is divided into the following layers: - The core layer provides the capabilities of binding, initializing, and releasing devices. - The adaptation layer implements other functions. -![](../public_sys-resources/icon-note.gif)NOTE
+>![](../public_sys-resources/icon-note.gif) **NOTE**
>The core layer can call the functions of the interface layer and uses the hook to call functions of the adaptation layer. In this way, the adaptation layer can indirectly call the functions of the interface layer, but the interface layer cannot call the functions of the adaptation layer. **Figure 1** Unified service mode @@ -284,7 +284,7 @@ The DAC module adaptation procedure is as follows: }; ``` - ![](../public_sys-resources/icon-note.gif)NOTE
+ >![](../public_sys-resources/icon-note.gif) **NOTE**
>For details about **DacMethod**, see [Available APIs](#available-apis). -- GitLab