!4276 #I58269完成，请审批

Merge pull request !4276 from Annie_wang/PR3074

en/device-dev/driver/driver-platform-adc-des.md

@@ -5,10 +5,11 @@
 An analog-to-digital converter (ADC) is a device that converts analog signals into digital signals.
 
 The ADC APIs provide a set of common functions for ADC data transfer, including:
--   Opening or closing an ADC device
+- Opening or closing an ADC device
+
 -   Obtaining the analog-to-digital (AD) conversion result
 
-    **Figure 1** ADC physical connection<a name="fig1"></a>
+    **Figure 1** ADC physical connection
 	
     ![](figures/ADC_physical_connection.png "ADC_physical_connection")
 
@@ -51,11 +52,11 @@ The ADC APIs provide a set of common functions for ADC data transfer, including:
 
 ### How to Use<a name="section4"></a>
 
-[Figure 2](#fig2) shows how an ADC device works.
+The figure below illustrates how to use the APIs.
+
+ **Figure 2** Using ADC driver APIs
 
- **Figure 2** How ADC works<a name="fig2"></a>
- 
-![](figures/ADC_flowchart.png "ADC_flowchart")
+![](figures/using-ADC-process.png "using-ADC-process.png")
 
 ### Opening an ADC Device<a name="section5"></a>
 

en/device-dev/driver/driver-platform-dac-des.md

@@ -69,15 +69,15 @@ The table below describes the APIs of the DAC module. For more details, see API
 | :------------------------------------------------------------| :------------ |
 | DevHandle DacOpen(uint32_t number)                           | Opens a DAC device. |
 | void DacClose(DevHandle handle)                              | Closes a DAC device. |
-| int32_t DacWrite(DevHandle handle, uint32_t channel, uint32_t val) | Sets the target DA value. |
+| int32_t DacWrite(DevHandle handle, uint32_t channel, uint32_t val) | Sets a target DA value. |
 
 ### How to Develop
 
-The figure below illustrates the process of using a DAC device.
+The figure below illustrates how to use the APIs.
 
-**Figure 2** Process of using a DAC device
- 
-![](figures/process-of-using-DAC.png "Process of using a DAC")
+**Figure 2** Using DAC driver APIs
+
+![](figures/using-DAC-process.png "using-DAC-process.png")
 
 #### Opening a DAC Device
 
@@ -111,7 +111,7 @@ if (dacHandle == NULL) {
 }
 ```
 
-#### Setting the Target DA Value
+#### Setting a Target DA Value
 
 ```
 int32_t DacWrite(DevHandle handle, uint32_t channel, uint32_t val);

en/device-dev/driver/driver-platform-gpio-des.md

@@ -7,11 +7,11 @@ Generally, a general-purpose input/output \(GPIO\) controller manages all GPIO p
 
 The GPIO APIs define a set of standard functions for performing operations on GPIO pins, including:
 
--   Setting the pin direction, which can be input or output \(High impedance is not supported currently.\)
+-   Setting the pin direction, which can be input or output \(high impedance is not supported currently\)
 
 -   Reading and writing level values, which can be low or high
 -   Setting an interrupt service routine \(ISR\) function and interrupt trigger mode for a pin
--   Enabling or disabling a pin interrupt
+-   Enabling or disabling interrupts for a pin
 
 ## Available APIs<a name="section589913442203"></a>
 
@@ -64,17 +64,18 @@ The GPIO APIs define a set of standard functions for performing operations on GP
 </tr>
 <tr id="row396907112117"><td class="cellrowborder" valign="top" headers="mcps1.2.4.1.1 "><p id="p109694717216"><a name="p109694717216"></a><a name="p109694717216"></a>GpioEnableIrq</p>
 </td>
-<td class="cellrowborder" valign="top" headers="mcps1.2.4.1.2 "><p id="p2969473216"><a name="p2969473216"></a><a name="p2969473216"></a>Enables a GPIO interrupt.</p>
+<td class="cellrowborder" valign="top" headers="mcps1.2.4.1.2 "><p id="p2969473216"><a name="p2969473216"></a><a name="p2969473216"></a>Enables GPIO interrupts for a pin.</p>
 </td>
 </tr>
 <tr id="row14969117152113"><td class="cellrowborder" valign="top" headers="mcps1.2.4.1.1 "><p id="p18969157182116"><a name="p18969157182116"></a><a name="p18969157182116"></a>GpioDisableIrq</p>
 </td>
-<td class="cellrowborder" valign="top" headers="mcps1.2.4.1.2 "><p id="p19690710214"><a name="p19690710214"></a><a name="p19690710214"></a>Disables a GPIO interrupt.</p>
+<td class="cellrowborder" valign="top" headers="mcps1.2.4.1.2 "><p id="p19690710214"><a name="p19690710214"></a><a name="p19690710214"></a>Disables GPIO interrupts for a pin.</p>
 </td>
 </tr>
 </tbody>
 </table>
 
+
 >![](../public_sys-resources/icon-note.gif) **NOTE**<br> 
 >All functions provided in this document can be called only in kernel mode.
 
@@ -82,22 +83,27 @@ The GPIO APIs define a set of standard functions for performing operations on GP
 
 ### How to Use<a name="section103477714216"></a>
 
-The GPIO APIs use the GPIO pin number to specify a pin. [Figure 1](#fig16151101653713)  shows the general process of using a GPIO.
+The GPIO APIs use the GPIO pin number to specify a pin. The figure below illustrates how to use the APIs.
+
+**Figure  1** Using GPIO driver APIs
+ 
+![](figures/using-gpio-process.png "using-gpio-process.png")
 
-**Figure  1** Process of using a GPIO<a name="fig16151101653713"></a>  
-![](figures/process-of-using-a-gpio.png "process-of-using-a-gpio")
+### Determining the GPIO Pin Number<a name="section370083272117"></a>
 
-### Determining a GPIO Pin Number<a name="section370083272117"></a>
+The method for converting GPIO pin numbers varies depending on the GPIO controller model, parameters, and controller driver of different system on chips \(SoCs\).
 
-The method for converting GPIO pin numbers varies according to the GPIO controller model, parameters, and controller driver of different system on chips \(SoCs\).
+- Hi3516DV300
 
--   Hi3516DV300
+  A controller manages 12 groups of GPIO pins. Each group contains 8 GPIO pins.
 
-    A controller manages 12 groups of GPIO pins. Each group contains 8 GPIO pins.
+  GPIO pin number = GPIO group index x Number of GPIO pins in each group + Offset in the group
 
-    GPIO pin number = GPIO group index \(0–11\) x Number of GPIO pins in each group \(8\) + Offset in the group
+  The group index ranges from 0 to 11. 
 
-    Example: GPIO number of GPIO10\_3 = 10 x 8 + 3 = 83
+  Example: 
+
+  GPIO pin number of GPIO10\_3 = 10 x 8 + 3 = 83
 
 -   Hi3518EV300
 
@@ -105,14 +111,18 @@ The method for converting GPIO pin numbers varies according to the GPIO controll
 
     GPIO pin number = GPIO group index \(0–9\) x Number of GPIO pins in each group \(10\) + Offset in the group
 
-    Example: GPIO pin number of GPIO7\_3 = 7 x 10 + 3 = 73
+    The group index ranges from 0 to 9.
+    
+    Example: 
+    
+    GPIO pin number of GPIO7\_3 = 7 x 10 + 3 = 73
 
 
 ### Using APIs to Operate GPIO Pins<a name="section13604050132118"></a>
 
 -   Set the direction for a GPIO pin.
 
-    Before performing read/write operations on a GPIO pin, call the following function to set the direction:
+    Before performing read/write operations on a GPIO pin, call **GpioSetDir**() to set the direction.
 
     int32\_t GpioSetDir\(uint16\_t gpio, uint16\_t dir\);
 
@@ -141,12 +151,12 @@ The method for converting GPIO pin numbers varies according to the GPIO controll
     </tr>
     <tr id="row205931212123817"><td class="cellrowborder" valign="top" width="48.120000000000005%"><p id="p18312151463"><a name="p18312151463"></a><a name="p18312151463"></a>0</p>
     </td>
-    <td class="cellrowborder" valign="top" width="51.88%"><p id="p103124517618"><a name="p103124517618"></a><a name="p103124517618"></a>Succeeded in setting the direction for a GPIO pin.</p>
+    <td class="cellrowborder" valign="top" width="51.88%"><p id="p103124517618"><a name="p103124517618"></a><a name="p103124517618"></a>The operation is successful.</p>
     </td>
     </tr>
     <tr id="row75931212153818"><td class="cellrowborder" valign="top" width="48.120000000000005%"><p id="p23121951261"><a name="p23121951261"></a><a name="p23121951261"></a>Negative value</p>
     </td>
-    <td class="cellrowborder" valign="top" width="51.88%"><p id="p153121553610"><a name="p153121553610"></a><a name="p153121553610"></a>Failed to set the direction for a GPIO pin.</p>
+    <td class="cellrowborder" valign="top" width="51.88%"><p id="p153121553610"><a name="p153121553610"></a><a name="p153121553610"></a>The operation failed.</p>
     </td>
     </tr>
     </tbody>
@@ -155,7 +165,7 @@ The method for converting GPIO pin numbers varies according to the GPIO controll
 
 -   Read or write the level value for a GPIO pin.
 
-    To read the level value of a GPIO pin, call the following function:
+    Call **GpioRead**() to read the level value of a GPIO pin.
 
     int32\_t GpioRead\(uint16\_t gpio, uint16\_t \*val\);
 
@@ -184,23 +194,24 @@ The method for converting GPIO pin numbers varies according to the GPIO controll
     </tr>
     <tr id="row3348184311486"><td class="cellrowborder" valign="top" width="48.120000000000005%"><p id="p1934854315487"><a name="p1934854315487"></a><a name="p1934854315487"></a>0</p>
     </td>
-    <td class="cellrowborder" valign="top" width="51.88%"><p id="p103481943114814"><a name="p103481943114814"></a><a name="p103481943114814"></a>Succeeded in reading the level value.</p>
+    <td class="cellrowborder" valign="top" width="51.88%"><p id="p103481943114814"><a name="p103481943114814"></a><a name="p103481943114814"></a>The operation is successful.</p>
     </td>
     </tr>
     <tr id="row23485436482"><td class="cellrowborder" valign="top" width="48.120000000000005%"><p id="p1134834310486"><a name="p1134834310486"></a><a name="p1134834310486"></a>Negative value</p>
     </td>
-    <td class="cellrowborder" valign="top" width="51.88%"><p id="p93491343144815"><a name="p93491343144815"></a><a name="p93491343144815"></a>Failed to read the level value.</p>
+    <td class="cellrowborder" valign="top" width="51.88%"><p id="p93491343144815"><a name="p93491343144815"></a><a name="p93491343144815"></a>The operation failed.</p>
     </td>
     </tr>
     </tbody>
     </table>
-
-    To write the level value for a GPIO pin, call the following function:
-
+   
+   
+    Call **GpioWrite()** to write the level value for a GPIO pin.
+   
     int32\_t GpioWrite\(uint16\_t gpio, uint16\_t val\);
-
+   
    **Table  4** Description of GpioWrite
-
+   
     <a name="table1214911207520"></a>
     <table><tbody><tr id="row6149720175218"><td class="cellrowborder" valign="top" width="48.120000000000005%"><p id="p18149132005216"><a name="p18149132005216"></a><a name="p18149132005216"></a><strong id="b19864427181615"><a name="b19864427181615"></a><a name="b19864427181615"></a>Parameter</strong></p>
     </td>
@@ -224,19 +235,19 @@ The method for converting GPIO pin numbers varies according to the GPIO controll
     </tr>
     <tr id="row111503202526"><td class="cellrowborder" valign="top" width="48.120000000000005%"><p id="p171501320205216"><a name="p171501320205216"></a><a name="p171501320205216"></a>0</p>
     </td>
-    <td class="cellrowborder" valign="top" width="51.88%"><p id="p15150102017522"><a name="p15150102017522"></a><a name="p15150102017522"></a>Succeeded in writing the level value.</p>
+    <td class="cellrowborder" valign="top" width="51.88%"><p id="p15150102017522"><a name="p15150102017522"></a><a name="p15150102017522"></a>The operation is successful.</p>
     </td>
     </tr>
     <tr id="row1615002018528"><td class="cellrowborder" valign="top" width="48.120000000000005%"><p id="p15150182045212"><a name="p15150182045212"></a><a name="p15150182045212"></a>Negative value</p>
     </td>
-    <td class="cellrowborder" valign="top" width="51.88%"><p id="p13150320105212"><a name="p13150320105212"></a><a name="p13150320105212"></a>Failed to write the level value.</p>
+    <td class="cellrowborder" valign="top" width="51.88%"><p id="p13150320105212"><a name="p13150320105212"></a><a name="p13150320105212"></a>The operation failed.</p>
     </td>
     </tr>
     </tbody>
     </table>
-
+   
     Example:
-
+   
     ```
     int32_t ret;
     uint16_t val;
@@ -265,7 +276,7 @@ The method for converting GPIO pin numbers varies according to the GPIO controll
 
 -   Set the ISR function for a GPIO pin.
 
-    To set the ISR function for a GPIO pin, call the following function:
+    Call **GpioSetIrq()** to set the ISR function for a GPIO pin.
 
     int32\_t GpioSetIrq\(uint16\_t gpio, uint16\_t mode, GpioIrqFunc func, void \*arg\);
 
@@ -304,21 +315,21 @@ The method for converting GPIO pin numbers varies according to the GPIO controll
     </tr>
     <tr id="row12299632125817"><td class="cellrowborder" valign="top" width="48.54%"><p id="p1180511189465"><a name="p1180511189465"></a><a name="p1180511189465"></a>0</p>
     </td>
-    <td class="cellrowborder" valign="top" width="51.459999999999994%"><p id="p180521812465"><a name="p180521812465"></a><a name="p180521812465"></a>Succeeded in setting the ISR function for a GPIO pin.</p>
+    <td class="cellrowborder" valign="top" width="51.459999999999994%"><p id="p180521812465"><a name="p180521812465"></a><a name="p180521812465"></a>The operation is successful.</p>
     </td>
     </tr>
     <tr id="row029833235815"><td class="cellrowborder" valign="top" width="48.54%"><p id="p1080591814468"><a name="p1080591814468"></a><a name="p1080591814468"></a>Negative value</p>
     </td>
-    <td class="cellrowborder" valign="top" width="51.459999999999994%"><p id="p18805141884611"><a name="p18805141884611"></a><a name="p18805141884611"></a>Failed to set the ISR function for a GPIO pin.</p>
+    <td class="cellrowborder" valign="top" width="51.459999999999994%"><p id="p18805141884611"><a name="p18805141884611"></a><a name="p18805141884611"></a>The operation failed.</p>
     </td>
     </tr>
     </tbody>
     </table>
 
-    >![](../public_sys-resources/icon-caution.gif) **CAUTION:** 
+    >![](../public_sys-resources/icon-caution.gif) **CAUTION**<br/> 
     >Only one ISR function can be set for a GPIO pin at a time. If **GpioSetIrq** is called repeatedly, the previous IRS function will be replaced.
 
-    If the ISR function is no longer required, call the following function to cancel the setting:
+    If the ISR function is no longer required, call **GpioUnSetIrq()** to cancel the setting.
 
     int32\_t GpioUnSetIrq\(uint16\_t gpio\);
 
@@ -342,18 +353,18 @@ The method for converting GPIO pin numbers varies according to the GPIO controll
     </tr>
     <tr id="row357318466439"><td class="cellrowborder" valign="top" width="48.54%"><p id="p1573164616438"><a name="p1573164616438"></a><a name="p1573164616438"></a>0</p>
     </td>
-    <td class="cellrowborder" valign="top" width="51.459999999999994%"><p id="p857384614319"><a name="p857384614319"></a><a name="p857384614319"></a>Succeeded in canceling the ISR function.</p>
+    <td class="cellrowborder" valign="top" width="51.459999999999994%"><p id="p857384614319"><a name="p857384614319"></a><a name="p857384614319"></a>The operation is successful.</p>
     </td>
     </tr>
     <tr id="row18573124610433"><td class="cellrowborder" valign="top" width="48.54%"><p id="p165731146134311"><a name="p165731146134311"></a><a name="p165731146134311"></a>Negative value</p>
     </td>
-    <td class="cellrowborder" valign="top" width="51.459999999999994%"><p id="p6573164613437"><a name="p6573164613437"></a><a name="p6573164613437"></a>Failed to cancel the ISR function.</p>
+    <td class="cellrowborder" valign="top" width="51.459999999999994%"><p id="p6573164613437"><a name="p6573164613437"></a><a name="p6573164613437"></a>The operation failed.</p>
     </td>
     </tr>
     </tbody>
     </table>
 
-    After the ISR function is set, call the following function to enable a GPIO interrupt:
+    After the ISR function is set, call **GpioEnableIrq()** to enable interrupts.
 
     int32\_t GpioEnableIrq\(uint16\_t gpio\);
 
@@ -377,21 +388,21 @@ The method for converting GPIO pin numbers varies according to the GPIO controll
     </tr>
     <tr id="row154188171403"><td class="cellrowborder" valign="top" width="50%"><p id="p1866610292563"><a name="p1866610292563"></a><a name="p1866610292563"></a>0</p>
     </td>
-    <td class="cellrowborder" valign="top" width="50%"><p id="p13666182975613"><a name="p13666182975613"></a><a name="p13666182975613"></a>Succeeded in enabling a GPIO interrupt.</p>
+    <td class="cellrowborder" valign="top" width="50%"><p id="p13666182975613"><a name="p13666182975613"></a><a name="p13666182975613"></a>The operation is successful.</p>
     </td>
     </tr>
     <tr id="row1041891720012"><td class="cellrowborder" valign="top" width="50%"><p id="p766642911562"><a name="p766642911562"></a><a name="p766642911562"></a>Negative value</p>
     </td>
-    <td class="cellrowborder" valign="top" width="50%"><p id="p1566652995613"><a name="p1566652995613"></a><a name="p1566652995613"></a>Failed to enable a GPIO interrupt.</p>
+    <td class="cellrowborder" valign="top" width="50%"><p id="p1566652995613"><a name="p1566652995613"></a><a name="p1566652995613"></a>The operation failed.</p>
     </td>
     </tr>
     </tbody>
     </table>
 
-    >![](../public_sys-resources/icon-caution.gif) **CAUTION:** 
+    >![](../public_sys-resources/icon-caution.gif) **CAUTION**<br/> 
     >The configured ISR function can be responded only after the GPIO interrupt is enabled.
 
-    Use the following function to disable the GPIO interrupt:
+    Call **GpioDisableIrq()** to disable interrupts.
 
     int32\_t GpioDisableIrq\(uint16\_t gpio\);
 
@@ -415,12 +426,12 @@ The method for converting GPIO pin numbers varies according to the GPIO controll
     </tr>
     <tr id="row156694410112"><td class="cellrowborder" valign="top" width="50%"><p id="p14669141214"><a name="p14669141214"></a><a name="p14669141214"></a>0</p>
     </td>
-    <td class="cellrowborder" valign="top" width="50%"><p id="p1266934818"><a name="p1266934818"></a><a name="p1266934818"></a>Succeeded in disabling a GPIO interrupt.</p>
+    <td class="cellrowborder" valign="top" width="50%"><p id="p1266934818"><a name="p1266934818"></a><a name="p1266934818"></a>The operation is successful.</p>
     </td>
     </tr>
     <tr id="row176691543117"><td class="cellrowborder" valign="top" width="50%"><p id="p7669941716"><a name="p7669941716"></a><a name="p7669941716"></a>Negative value</p>
     </td>
-    <td class="cellrowborder" valign="top" width="50%"><p id="p4669164219"><a name="p4669164219"></a><a name="p4669164219"></a>Failed to disable a GPIO interrupt.</p>
+    <td class="cellrowborder" valign="top" width="50%"><p id="p4669164219"><a name="p4669164219"></a><a name="p4669164219"></a>The operation failed.</p>
     </td>
     </tr>
     </tbody>
@@ -470,11 +481,15 @@ The method for converting GPIO pin numbers varies according to the GPIO controll
 
 ## Usage Example<a name="section25941262111"></a>
 
-In this example, we test the interrupt trigger of a GPIO pin as follows: Set the ISR function for the pin, set the trigger mode to rising edge and failing edge, write high and low levels to the pin alternately to generate level fluctuation, and observe the execution of the ISR function.
+The procedure is as follows:
+
+1. Select an idle GPIO pin. 
+
+   This example uses pin GPIO10\_3 on a Hi3516D V300 development board as an example. The pin number is 83. You can select an idle GPIO pin as required.
 
-Select an idle GPIO pin. This example uses a Hi3516D V300 development board and GPIO pin GPIO10\_3, which is numbered GPIO83.
+2. Set the ISR function for the pin, with the trigger mode of rising edge and failing edge.
 
-You can select an idle GPIO pin based on the development board and schematic diagram.
+3. Write high and low levels to the pin alternately, and observe the execution of the ISR function.
 
 ```
 #include "gpio_if.h"

en/device-dev/driver/driver-platform-i2c-des.md

@@ -2,19 +2,20 @@
 
 ## Overview<a name="section5361140416"></a>
 
--   The Inter-Integrated Circuit \(I2C\) is a simple, bidirectional, and synchronous serial bus that uses merely two wires.
--   In an I2C communication, one controller communicates with one or more devices through the serial data line \(SDA\) and serial clock line \(SCL\), as shown in  [Figure 1](#fig1135561232714).
+The Inter-Integrated Circuit \(I2C\) is a simple, bidirectional, and synchronous serial bus that uses merely two wires.
 
--   I2C data transfer must begin with a  **START**  condition and end with a  **STOP**  condition. Data is transmitted byte-by-byte from the most significant bit to the least significant bit.
--   Each I2C node is recognized by a unique address and can serve as either a controller or a device. When the controller needs to communicate with a device, it writes the device address to the bus through broadcast. A device matching this address sends a response to set up a data transfer channel.
+In an I2C communication, one controller communicates with one or more devices through the serial data line \(SDA\) and serial clock line \(SCL\), as shown in  [Figure 1](#fig1135561232714).
 
--   The I2C APIs define a set of common functions for I2C data transfer, including:
+I2C data transfer must begin with a  **START**  condition and end with a  **STOP**  condition. Data is transmitted byte-by-byte from the most significant bit to the least significant bit.
 
-    -   I2C controller management: opening or closing an I2C controller
-    -   I2C message transfer: custom transfer by using a message array
+Each I2C node is recognized by a unique address and can serve as either a controller or a device. When the controller needs to communicate with a device, it writes the device address to the bus through broadcast. A device matching this address sends a response to set up a data transfer channel.
 
-    **Figure  1**  Physical connection diagram for I2C<a name="fig1135561232714"></a>  
-    ![](figures/physical-connection-diagram-for-i2c.png "physical-connection-diagram-for-i2c")
+The I2C APIs define a set of common functions for I2C data transfer, including:
+
+-   I2C controller management: opening or closing an I2C controller
+-   I2C message transfer: custom transfer by using a message array
+
+**Figure  1**  Physical connection diagram for I2C<br/>![](figures/physical-connection-diagram-for-i2c.png "physical-connection-diagram-for-i2c")
 
 
 ## Available APIs<a name="section545869122317"></a>
@@ -52,21 +53,22 @@
 </tbody>
 </table>
 
->![](../public_sys-resources/icon-note.gif) **NOTE:** 
+>![](../public_sys-resources/icon-note.gif) **NOTE**<br/> 
 >All functions provided in this document can be called only in kernel mode.
 
 ## Usage Guidelines<a name="section1695201514281"></a>
 
 ### How to Use<a name="section1338373417288"></a>
 
-[Figure 2](#fig183017194234)  illustrates the process of an I2C device.
+The figure below illustrates how to use the APIs.
 
-**Figure  2**  Process of using an I2C device<a name="fig183017194234"></a>  
-![](figures/process-of-using-an-i2c-device.png "process-of-using-an-i2c-device")
+**Figure  2**  Using I2C driver APIs
+
+![](figures/using-i2c-process.png "process-of-using-an-i2c-device")
 
 ### Opening an I2C Controller<a name="section13751110132914"></a>
 
-Call the following function to open an I2C controller:
+Call the **I2cOpen()** function to open an I2C controller.
 
 DevHandle I2cOpen\(int16\_t number\);
 
@@ -117,7 +119,7 @@ if (i2cHandle == NULL) {
 
 ### Performing I2C Communication<a name="section9202183372916"></a>
 
-Use the following function for message transfer:
+Call the **I2cTransfer()** function to transfer messages.
 
 int32\_t I2cTransfer\(DevHandle handle, struct I2cMsg \*msgs, int16\_t count\);
 
@@ -186,15 +188,14 @@ if (ret != 2) {
 }
 ```
 
->![](../public_sys-resources/icon-caution.gif) **CAUTION:** 
+>![](../public_sys-resources/icon-caution.gif) **CAUTION**<br/>
 >-   The device address in the  **I2cMsg**  structure does not contain the read/write flag bit. The read/write information is transferred by the read/write control bit in the member variable  **flags**.
->-   The  **I2cTransfer**  function does not limit the number of message structures, which is determined by the I2C controller.
->-   The  **I2cTransfer**  function does not limit the data length of each message structure, which is determined by the I2C controller.
+>-   The  **I2cTransfer**  function does not limit the number of message structures and the data length of each message structure, which are determined by the I2C controller.
 >-   The  **I2cTransfer**  function may cause the system to sleep and therefore cannot be called in the interrupt context.
 
 ### Closing an I2C Controller<a name="section19481164133018"></a>
 
-Call the following function to close the I2C controller after the communication is complete:
+Call the **I2cClose()** function to close the I2C controller after the communication is complete.
 
 void I2cClose\(DevHandle \*handle\); 
 
@@ -209,12 +210,13 @@ void I2cClose\(DevHandle \*handle\);
 </thead>
 <tbody><tr id="row1926109193116"><td class="cellrowborder" valign="top" width="50%" headers="mcps1.2.3.1.1 "><p id="p105419317318"><a name="p105419317318"></a><a name="p105419317318"></a>handle</p>
 </td>
-<td class="cellrowborder" valign="top" width="50%" headers="mcps1.2.3.1.2 "><p id="p1213245577"><a name="p1213245577"></a><a name="p1213245577"></a>Handle of an I2C controller.</p>
+<td class="cellrowborder" valign="top" width="50%" headers="mcps1.2.3.1.2 "><p id="p1213245577"><a name="p1213245577"></a><a name="p1213245577"></a>Handle of the I2C controller to close.</p>
 </td>
 </tr>
 </tbody>
 </table>
 
+
 ```
 I2cClose(i2cHandle); /* Close the I2C controller. */
 ```
@@ -233,7 +235,7 @@ This example shows a simple register read/write operation on TouchPad on a Hi351
 
 In this example, first we reset Touch IC. \(The development board supplies power to Touch IC by default after being powered on, and this use case does not consider the power supply\). Then, we perform a read/write operation on an internal register to test whether the I2C channel is normal.
 
->![](../public_sys-resources/icon-note.gif) **NOTE:** 
+>![](../public_sys-resources/icon-note.gif) **NOTE** <br/>
 >The example focuses on I2C device access and verifies the I2C channel. The read and write values of the device register are not concerned. The behavior caused by the read and write operations on the register is determined by the device itself.
 
 Example:

en/device-dev/driver/driver-platform-mipicsi-des.md

@@ -59,12 +59,11 @@ The figure below shows a simplified CSI. The D-PHY transmits data by using one p
 
 ### How to Use<a name="section2.1_MIPI_CSIDes"></a>
 
-The figure below shows the process of using a MIPI CSI device.
+The figure below illustrates how to use the APIs.
 
-**Figure 2** MIPI CSI usage process<a name="fig2_MIPI_CSIDes"></a> 
+**Figure 2** Using MIPI CSI driver APIs 
 
-
-![](figures/process-of-using-MIPI-CSI.png)
+![](figures/using-MIPI-CSI-process.png)
 
 ### Opening the MIPI CSI Controller Operation Handle<a name="section2.2_MIPI_CSIDes"></a>
 

en/device-dev/driver/driver-platform-mipidsi-des.md

-# MIPI DSI<a name="EN-US_TOPIC_0000001160971534"></a>
+# MIPI DSI
 
-## Overview<a name="section16806142183217"></a>
+## Overview
 
 The Display Serial Interface \(DSI\) is a specification stipulated by the Mobile Industry Processor Interface \(MIPI\) Alliance, aiming to reduce the cost of display controllers in a mobile device. It defines a serial bus and communication protocol among the host, the source of image data, and the target device. In this way, the DSI can send pixel data or commands to peripherals \(usually LCDs or similar display devices\) in serial mode, or reads information such as status and pixel from the peripherals.
 
@@ -11,7 +11,7 @@ MIPI DSI is capable of working in both high speed \(HS\) mode and low power \(LP
     ![](figures/dsi-transmitting-and-receiving-interface.png "dsi-transmitting-and-receiving-interface")
 
 
-## Available APIs<a name="section12720125432316"></a>
+## Available APIs
 
 **Table  1** APIs for MIPI DSI
 
@@ -75,17 +75,17 @@ MIPI DSI is capable of working in both high speed \(HS\) mode and low power \(LP
 </tbody>
 </table>
 
->![](../public_sys-resources/icon-note.gif) **NOTE**<br> 
->All functions described in this document can be called only in kernel space.
+>![](../public_sys-resources/icon-note.gif) **NOTE**<br> All functions described in this document can be called only in kernel space.
 
-## Usage Guidelines<a name="section037231715335"></a>
+## Usage Guidelines
 
-### How to Use<a name="section49299119344"></a>
+### How to Use
 
-[Figure 2](#fig129103491241) shows the process of using a MIPI DSI device.
+The figure below illustrates how to use the APIs.
 
-**Figure  2** Process of using a MIPI DSI device<a name="fig129103491241"></a>  
-![](figures/process-of-using-a-mipi-dsi-device.png)
+**Figure  2** Using MIPI DSI driver APIs
+
+ ![](figures/using-mipi-dsi-process.png)
 
 ### Obtaining a MIPI DSI Device Handle<a name="section5126155683811"></a>
 

en/device-dev/driver/driver-platform-pin-des.md

@@ -68,10 +68,11 @@ The table below describes the APIs of the pin module. For more details, see API
 
 ### How to Develop<a name="section9"></a>
 
-The figure below shows the process.
+The figure below illustrates how to use the APIs.
 
- **Figure 2** Process of using the pin module<a name="fig2"></a> 
-![](figures/process-of-using-pin.png "Process of using the pin module")
+ **Figure 2** Using the pin driver APIs 
+ 
+![](figures/using-pin-process.png "Process of using the pin module")
 
 #### Obtaining the Pin Description Handle
 
@@ -122,7 +123,7 @@ int32_t PinSetPull(DevHandle handle, enum PinPullType pullType);
 | pullType   | Pull type to set.        |
 | **Return Value**| **Description**        |
 | 0          | The operation is successful.|
-| Negative value      | The operation fails.|
+| Negative value      | The operation failed.|
 
 Example: Set the pull type to pull-up.
 
@@ -156,7 +157,7 @@ int32_t PinGetPull(DevHandle handle, enum PinPullType *pullType);
 | pullType   | Pointer to the pull type obtained.|
 | **Return Value**| **Description**          |
 | 0          | The operation is successful.  |
-| Negative value      | The operation fails.  |
+| Negative value      | The operation failed.  |
 
 Example: Obtain the pull type of a pin.
 
@@ -189,7 +190,7 @@ int32_t PinSetStrength(DevHandle handle, uint32_t strength);
 | strength   | Pull strength to set.        |
 | **Return Value**| **Description**        |
 | 0          | The operation is successful.|
-| Negative value      | The operation fails.|
+| Negative value      | The operation failed.|
 
 Example: Set the pull strength of the pin to 2. 
 
@@ -223,7 +224,7 @@ int32_t PinGetStrength(DevHandle handle, uint32_t *strength);
 | strength   | Pointer to the pull strength obtained.|
 | **Return Value**| **Description**          |
 | 0          | The operation is successful.  |
-| Negative value      | The operation fails.  |
+| Negative value      | The operation failed.  |
 
 Example: Obtain the pull strength of a pin.
 
@@ -258,7 +259,7 @@ int32_t PinSetFunc(DevHandle handle, const char *funcName);
 | funcName   | Pointer to the pin function to set.      |
 | **Return Value**| **Description**    |
 | 0          | The operation is successful.|
-| Negative value      | The operation fails.|
+| Negative value      | The operation failed.|
 
 Example: Set the pin function to LSADC_CH1 (ADC channel 1).
 
@@ -291,7 +292,7 @@ int32_t PinGetFunc(DevHandle handle, const char **funcName);
 | funcName   | Pointer to the function name obtained.|
 | **Return Value**| **Description**      |
 | 0          | The operation is successful.  |
-| Negative value      | The operation fails.  |
+| Negative value      | The operation failed.  |
 
 Example: Obtain the pin function. 
 

en/device-dev/driver/driver-platform-pwm-des.md

@@ -48,11 +48,11 @@ Pulse width modulation (PWM) is a technology that digitally encodes analog signa
 
 ### How to Use
 
-The figure below shows the general process of using the PWM.
+The figure below illustrates how to use the APIs.
 
-  **Figure 1** Process of using the PWM module
+**Figure 1** Using the PWM driver APIs
 
-![](figures/process-of-using-PWM.png)
+![](figures/using-PWM-process.png)
 
 
 ### Opening a PWM Device Handle
@@ -71,7 +71,7 @@ DevHandle PwmOpen(uint32_t num);
 | num        | PWM device number.            |
 | **Return Value** | **Description**         |
 | handle     | Handle of the PWM device obtained.|
-| NULL       | The operation fails.               |
+| NULL       | The operation failed.             |
 
 Example: Open the device handle of PWM device 0.
 
@@ -126,7 +126,7 @@ int32_t PwmEnable(DevHandle handle);
 | handle     | PWM device handle.   |
 | **Return Value** | **Description** |
 | 0          | The operation is successful.      |
-| Negative number      | The operation fails.      |
+| Negative number      | The operation failed.    |
 
 
 ```
@@ -156,7 +156,7 @@ int32_t PwmDisable(DevHandle handle);
 | handle     | PWM device handle.   |
 | **Return Value** | **Description** |
 | 0          | The operation is successful.      |
-| Negative number      | The operation fails.      |
+| Negative number      | The operation failed.     |
 
 
 ```
@@ -187,7 +187,7 @@ int32_t PwmSetPeriod(DevHandle handle, uint32_t period);
 | period     | PWM period to set, in ns.|
 | **Return Value**| **Description**           |
 | 0          | The operation is successful.                |
-| Negative number      | The operation fails.                |
+| Negative number      | The operation failed.              |
 
 
 ```
@@ -218,7 +218,7 @@ int32_t PwmSetDuty(DevHandle handle, uint32_t duty);
 | duty       | Time that the signal is in the ON state, in ns.|
 | **Return Value**| **Description**               |
 | 0          | The operation is successful.                    |
-| Negative number      | The operation fails.                    |
+| Negative number      | The operation failed.                  |
 
 
 ```
@@ -249,7 +249,7 @@ int32_t PwmSetPolarity(DevHandle handle, uint8_t polarity);
 | polarity   | Polarity to set, which can be **PWM\_NORMAL\_POLARITY** or **PWM\_INVERTED\_POLARITY**.|
 | **Return Value**| **Description**      |
 | 0          | The operation is successful.           |
-| Negative number      | The operation fails.           |
+| Negative number      | The operation failed.          |
 
 
 ```
@@ -280,7 +280,7 @@ int32_t PwmSetConfig(DevHandle handle, struct PwmConfig *config);
 | \*config   | Pointer to PWM parameters.      |
 | **Return Value**| **Description** |
 | 0          | The operation is successful.      |
-| Negative number      | The operation fails.      |
+| Negative number      | The operation failed.    |
 
 
 ```
@@ -317,7 +317,7 @@ int32_t PwmGetConfig(DevHandle handle, struct PwmConfig *config);
 | \*config   | Pointer to PWM parameters.      |
 | **Return Value**| **Description** |
 | 0          | The operation is successful.      |
-| Negative number      | The operation fails.      |
+| Negative number      | The operation failed.    |
 
 
 ```

en/device-dev/driver/driver-platform-regulator-des.md

@@ -42,7 +42,8 @@ The regulator 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<br/>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.
+> ![icon-note.gif](../public_sys-resources/icon-note.gif) **NOTE**<br/>
+> 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
 
@@ -84,11 +85,11 @@ Regulators are used to:
 
 During the OS startup process, the driver management module loads the regulator driver based on the configuration file. Then, the regulator driver detects the regulator devices and initializes the driver.
 
-The figure below illustrates the process of using a regulator.
+The figure below illustrates how to use the APIs.
 
-**Figure 2** Process of using a regulator 
+**Figure 2** Using regulator driver APIs
 
-![](figures/process-of-using-regulator.png)
+![](figures/using-regulator-process.png)
 
 #### Opening a Regulator Device Handle
 
@@ -105,7 +106,7 @@ DevHandle RegulatorOpen(const char *name);
 | name       | Name of the target regulator.            |
 | **Return Value**| **Description**               |
 | handle     | The regulator device handle is returned if the operation is successful.|
-| NULL       | The operation fails.                     |
+| NULL       | The operation failed.                     |
 
 
 
@@ -155,7 +156,7 @@ int32_t RegulatorEnable(DevHandle handle);
 | handle     | Device handle of the target regulator.|
 | **Return Value**| **Description**   |
 | 0          | The operation is successful.         |
-| Negative value      | The operation fails.         |
+| Negative value      | The operation failed.         |
 
 
 
@@ -184,7 +185,7 @@ int32_t RegulatorDisable(DevHandle handle);
 | handle     | Device handle of the target regulator.|
 | **Return Value**| **Description**   |
 | 0          | The operation is successful.         |
-| Negative value      | The operation fails.         |
+| Negative value      | The operation failed.         |
 
 ```
 int32_t ret;
@@ -212,7 +213,7 @@ int32_t RegulatorForceDisable(DevHandle handle);
 | handle     | Device handle of the target regulator.|
 | **Return Value**| **Description**   |
 | 0          | The operation is successful.         |
-| Negative value      | The operation fails.         |
+| Negative value      | The operation failed.         |
 
 ```
 int32_t ret;
@@ -241,7 +242,7 @@ int32_t RegulatorSetVoltage(DevHandle handle, uint32_t minUv, uint32_t maxUv);
 | maxUv      | Maximum voltage to set.         |
 | **Return Value**| **Description**   |
 | 0          | The operation is successful.         |
-| Negative value      | The operation fails.         |
+| Negative value      | The operation failed.         |
 
 ```
 int32_t ret;
@@ -272,7 +273,7 @@ int32_t RegulatorGetVoltage(DevHandle handle, uint32_t *voltage);
 | *voltage   | Pointer to the regulator voltage information.         |
 | **Return Value**| **Description**   |
 | 0          | The operation is successful.         |
-| Negative value      | The operation fails.         |
+| Negative value      | The operation failed.         |
 
 ```
 int32_t ret;
@@ -302,7 +303,7 @@ int32_t RegulatorSetCurrent(DevHandle handle, uint32_t minUa, uint32_t maxUa);
 | maxUa      | Maximum current to set.         |
 | **Return Value**| **Description**   |
 | 0          | The operation is successful.         |
-| Negative value      | The operation fails.         |
+| Negative value      | The operation failed.         |
 
 ```
 int32_t ret;
@@ -332,7 +333,7 @@ int32_t RegulatorGetCurrent(DevHandle handle, uint32_t *regCurrent);
 | *regCurrent | Pointer to the regulator current information.         |
 | **Return Value** | **Description**   |
 | 0           | The operation is successful.         |
-| Negative value       | The operation fails.         |
+| Negative value       | The operation failed.         |
 
 ```
 int32_t ret;
@@ -361,7 +362,7 @@ int32_t RegulatorGetStatus(DevHandle handle, uint32_t *status);
 | *status    | Pointer to the regulator status information.         |
 | **Return Value**| **Description**   |
 | 0          | The operation is successful.         |
-| Negative value      | The operation fails.         |
+| Negative value      | The operation failed.         |
 
 ```
 int32_t ret;

en/device-dev/driver/driver-platform-rtc-des.md

@@ -104,12 +104,12 @@ The real-time clock \(RTC\) driver provides precise real time for the operating
 
 During the OS startup, the HDF loads the RTC driver based on the configuration file. The RTC driver detects the RTC component and initializes the driver.
 
-[Figure 1](#fig1610020107333)  illustrates the process of using an RTC device.
+The figure below illustrates how to use the APIs.
 
-**Figure  1** Process of using an RTC device<a name="fig1610020107333"></a>  
-![](figures/process-of-using-an-rtc-device.png "process-of-using-an-rtc-device")
+**Figure  1** Process of using an RTC device  
+![](figures/using-rtc-process.png "process-of-using-an-rtc-device")
 
-### Creating an RTC Device Handle<a name="section1131212144310"></a>
+### Opening the RTC Device Handle<a name="section1131212144310"></a>
 
 After the RTC driver is loaded, you can use the API provided by the HDF and call APIs of the RTC driver.
 
@@ -138,17 +138,18 @@ DevHandle RtcOpen\(void\);
 </tr>
 <tr id="row2808192935615"><td class="cellrowborder" valign="top" width="21.45%"><p id="p380852915567"><a name="p380852915567"></a><a name="p380852915567"></a>handle</p>
 </td>
-<td class="cellrowborder" valign="top" width="78.55%"><p id="p26881319114110"><a name="p26881319114110"></a><a name="p26881319114110"></a>Returns the  if the operation is successful.</p>
+<td class="cellrowborder" valign="top" width="78.55%"><p id="p26881319114110"><a name="p26881319114110"></a><a name="p26881319114110"></a>The operation is successful.</p>
 </td>
 </tr>
 <tr id="row4808142945615"><td class="cellrowborder" valign="top" width="21.45%"><p id="p188084291561"><a name="p188084291561"></a><a name="p188084291561"></a>NULL</p>
 </td>
-<td class="cellrowborder" valign="top" width="78.55%"><p id="p780852912566"><a name="p780852912566"></a><a name="p780852912566"></a>The operation fails.</p>
+<td class="cellrowborder" valign="top" width="78.55%"><p id="p780852912566"><a name="p780852912566"></a><a name="p780852912566"></a>The operation failed.</p>
 </td>
 </tr>
 </tbody>
 </table>
 
+
 ```
 DevHandle  handle = NULL;
 
@@ -161,7 +162,7 @@ if (handle  == NULL) {
 
 ### Releasing the RTC Device Handle<a name="section10744117144314"></a>
 
-You can call the following function to release the RTC device handle, thereby releasing resources of the device:
+You can call **RtcClose()** function to release the RTC device handle, thereby releasing resources of the device.
 
 void RtcClose\(DevHandle handle\);
 
@@ -186,7 +187,7 @@ void RtcClose\(DevHandle handle\);
 RtcClose(handle);
 ```
 
-### Registering RtcAlarmCallback<a name="section14839440184320"></a>
+### Registering RtcAlarmCallback
 
 After the OS is started, call the following function to register **RtcAlarmCallback**, which will be invoked when an alarm is generated at the specified time:
 
@@ -228,7 +229,7 @@ int32\_t RtcRegisterAlarmCallback\(DevHandle handle, enum RtcAlarmIndex alarmInd
 </tr>
 <tr id="row1241081213303"><td class="cellrowborder" valign="top" width="21.36%" headers="mcps1.2.3.1.1 "><p id="p1123362173010"><a name="p1123362173010"></a><a name="p1123362173010"></a>Negative value</p>
 </td>
-<td class="cellrowborder" valign="top" width="78.64%" headers="mcps1.2.3.1.2 "><p id="p1723362153010"><a name="p1723362153010"></a><a name="p1723362153010"></a>The operation fails.</p>
+<td class="cellrowborder" valign="top" width="78.64%" headers="mcps1.2.3.1.2 "><p id="p1723362153010"><a name="p1723362153010"></a><a name="p1723362153010"></a>The operation failed.</p>
 </td>
 </tr>
 </tbody>
@@ -257,11 +258,11 @@ if (ret != 0) {
 }
 ```
 
-### Performing RTC-related Operations<a name="section161927578433"></a>
+### Performing RTC-related Operations
 
 -   Reading RTC time
 
-Call the following function to read time information from the RTC driver, including the year, month, the day of the week, day, hour, minute, second, and millisecond:
+Call the **RtcReadTime()** function to read time information from the RTC driver, including the year, month, the day of the week, day, hour, minute, second, and millisecond.
 
 int32\_t RtcReadTime\(DevHandle handle, struct RtcTime \*time\);
 
@@ -295,7 +296,7 @@ int32\_t RtcReadTime\(DevHandle handle, struct RtcTime \*time\);
 </tr>
 <tr id="row15393184519323"><td class="cellrowborder" valign="top" width="21.45%"><p id="p13521182309"><a name="p13521182309"></a><a name="p13521182309"></a>Negative value</p>
 </td>
-<td class="cellrowborder" valign="top" width="78.55%"><p id="p1035216186309"><a name="p1035216186309"></a><a name="p1035216186309"></a>The operation fails.</p>
+<td class="cellrowborder" valign="top" width="78.55%"><p id="p1035216186309"><a name="p1035216186309"></a><a name="p1035216186309"></a>The operation failed.</p>
 </td>
 </tr>
 </tbody>
@@ -314,7 +315,7 @@ if (ret != 0) {
 
 -   Setting RTC time
 
-Call the following function to set the RTC time:
+Call the **RtcWriteTime()** function to set the RTC time.
 
 int32\_t RtcWriteTime\(DevHandle handle, struct RtcTime \*time\);
 
@@ -348,7 +349,7 @@ int32\_t RtcWriteTime\(DevHandle handle, struct RtcTime \*time\);
 </tr>
 <tr id="row024153123616"><td class="cellrowborder" valign="top" width="21.54%"><p id="p5602191619300"><a name="p5602191619300"></a><a name="p5602191619300"></a>Negative value</p>
 </td>
-<td class="cellrowborder" valign="top" width="78.46%"><p id="p12602131643015"><a name="p12602131643015"></a><a name="p12602131643015"></a>The operation fails.</p>
+<td class="cellrowborder" valign="top" width="78.46%"><p id="p12602131643015"><a name="p12602131643015"></a><a name="p12602131643015"></a>The operation failed.</p>
 </td>
 </tr>
 </tbody>
@@ -378,7 +379,7 @@ if (ret != 0) {
 
 -   Reading the RTC alarm time
 
-Call the following function to read the alarm time:
+Call the **RtcReadAlarm()** function to read the alarm time.
 
 int32\_t RtcReadAlarm\(DevHandle handle, enum RtcAlarmIndex alarmIndex, struct RtcTime \*time\);
 
@@ -417,7 +418,7 @@ int32\_t RtcReadAlarm\(DevHandle handle, enum RtcAlarmIndex alarmIndex, struct R
 </tr>
 <tr id="row016911915461"><td class="cellrowborder" valign="top" width="21.54%"><p id="p6833213133013"><a name="p6833213133013"></a><a name="p6833213133013"></a>Negative value</p>
 </td>
-<td class="cellrowborder" valign="top" width="78.46%"><p id="p168341213143015"><a name="p168341213143015"></a><a name="p168341213143015"></a>The operation fails.</p>
+<td class="cellrowborder" valign="top" width="78.46%"><p id="p168341213143015"><a name="p168341213143015"></a><a name="p168341213143015"></a>The operation failed.</p>
 </td>
 </tr>
 </tbody>
@@ -436,7 +437,7 @@ if (ret != 0) {
 
 -   Setting RTC alarm time
 
-Call the following function to set the RTC alarm time based on the alarm index:
+Call the **RtcWriteAlarm()** function to set the RTC alarm time based on the alarm index.
 
 int32\_t RtcWriteAlarm\(DevHandle handle, enum RtcAlarmIndex  alarmIndex, struct RtcTime \*time\);
 
@@ -475,7 +476,7 @@ int32\_t RtcWriteAlarm\(DevHandle handle, enum RtcAlarmIndex  alarmIndex, struct
 </tr>
 <tr id="row1686918225483"><td class="cellrowborder" valign="top" width="21.62%"><p id="p16246181033012"><a name="p16246181033012"></a><a name="p16246181033012"></a>Negative value</p>
 </td>
-<td class="cellrowborder" valign="top" width="78.38000000000001%"><p id="p3246111019309"><a name="p3246111019309"></a><a name="p3246111019309"></a>The operation fails.</p>
+<td class="cellrowborder" valign="top" width="78.38000000000001%"><p id="p3246111019309"><a name="p3246111019309"></a><a name="p3246111019309"></a>The operation failed.</p>
 </td>
 </tr>
 </tbody>
@@ -505,7 +506,7 @@ if (ret != 0) {
 
 -   Enabling or disabling alarm interrupts
 
-Before performing alarm operations, use the following function to enable alarm interrupts, so that **RtcAlarmCallback** will be called when the alarm is not generated upon a timeout:
+Before performing alarm operations, use the **RtcAlarmInterruptEnable()** function to enable alarm interrupts, so that **RtcAlarmCallback** will be called when the alarm is not generated upon a timeout.
 
 int32\_t RtcAlarmInterruptEnable\(DevHandle handle, enum RtcAlarmIndex alarmIndex, uint8\_t enable\);
 
@@ -544,7 +545,7 @@ int32\_t RtcAlarmInterruptEnable\(DevHandle handle, enum RtcAlarmIndex alarmInde
 </tr>
 <tr id="row2347115321514"><td class="cellrowborder" valign="top" width="21.36%"><p id="p324855163018"><a name="p324855163018"></a><a name="p324855163018"></a>Negative value</p>
 </td>
-<td class="cellrowborder" valign="top" width="78.64%"><p id="p7248857302"><a name="p7248857302"></a><a name="p7248857302"></a>The operation fails.</p>
+<td class="cellrowborder" valign="top" width="78.64%"><p id="p7248857302"><a name="p7248857302"></a><a name="p7248857302"></a>The operation failed.</p>
 </td>
 </tr>
 </tbody>
@@ -562,7 +563,7 @@ if (ret != 0) {
 
 -   Reading RTC external frequency
 
-Call the following function to read the frequency of the external crystal oscillator connected to the RTC driver:
+Call the **RtcGetFreq()** function to read the frequency of the external crystal oscillator connected to the RTC driver.
 
 int32\_t RtcGetFreq\(DevHandle handle, uint32\_t \*freq\);
 
@@ -596,7 +597,7 @@ int32\_t RtcGetFreq\(DevHandle handle, uint32\_t \*freq\);
 </tr>
 <tr id="row135892261811"><td class="cellrowborder" valign="top" width="21.36%"><p id="p152692538292"><a name="p152692538292"></a><a name="p152692538292"></a>Negative value</p>
 </td>
-<td class="cellrowborder" valign="top" width="78.64%"><p id="p327015313294"><a name="p327015313294"></a><a name="p327015313294"></a>The operation fails.</p>
+<td class="cellrowborder" valign="top" width="78.64%"><p id="p327015313294"><a name="p327015313294"></a><a name="p327015313294"></a>The operation failed.</p>
 </td>
 </tr>
 </tbody>
@@ -615,7 +616,7 @@ if (ret != 0) {
 
 -   Setting the frequency of the external crystal oscillator connected to the RTC driver
 
-Call the following function to set the frequency of the external crystal oscillator connected to the RTC driver:
+Call the **RtcSetFreq()** function to set the frequency of the external crystal oscillator connected to the RTC driver.
 
 int32\_t RtcSetFreq\(DevHandle handle, uint32\_t freq\);
 
@@ -649,7 +650,7 @@ int32\_t RtcSetFreq\(DevHandle handle, uint32\_t freq\);
 </tr>
 <tr id="row10702194313201"><td class="cellrowborder" valign="top" width="21.36%"><p id="p165182216306"><a name="p165182216306"></a><a name="p165182216306"></a>Negative value</p>
 </td>
-<td class="cellrowborder" valign="top" width="78.64%"><p id="p651815219302"><a name="p651815219302"></a><a name="p651815219302"></a>The operation fails.</p>
+<td class="cellrowborder" valign="top" width="78.64%"><p id="p651815219302"><a name="p651815219302"></a><a name="p651815219302"></a>The operation failed.</p>
 </td>
 </tr>
 </tbody>
@@ -668,7 +669,7 @@ if (ret != 0) {
 
 -   Resetting the RTC driver
 
-Call the following function to perform a reset on the RTC driver \(after the reset, the registers are restored to the default values\):
+Call the **RtcReset()** function to perform a reset on the RTC driver \(after the reset, the registers are restored to the default values\).
 
 int32\_t RtcReset\(DevHandle handle\);
 
@@ -697,7 +698,7 @@ int32\_t RtcReset\(DevHandle handle\);
 </tr>
 <tr id="row16990133152516"><td class="cellrowborder" valign="top" width="21.36%"><p id="p17536173573015"><a name="p17536173573015"></a><a name="p17536173573015"></a>Negative value</p>
 </td>
-<td class="cellrowborder" valign="top" width="78.64%"><p id="p1153623503014"><a name="p1153623503014"></a><a name="p1153623503014"></a>The operation fails.</p>
+<td class="cellrowborder" valign="top" width="78.64%"><p id="p1153623503014"><a name="p1153623503014"></a><a name="p1153623503014"></a>The operation failed.</p>
 </td>
 </tr>
 </tbody>
@@ -715,7 +716,7 @@ if (ret != 0) {
 
 -   Reading the configuration of a custom RTC register
 
-Call the following function to read the configuration of a custom RTC register based on the register index \(one index corresponds to one byte of the configuration value\):
+Call the **RtcReadReg()** function to read the configuration of a custom RTC register based on the register index \(one index corresponds to one byte of the configuration value\):
 
 int32\_t RtcReadReg\(DevHandle handle, uint8\_t usrDefIndex, uint8\_t \*value\);
 
@@ -754,7 +755,7 @@ int32\_t RtcReadReg\(DevHandle handle, uint8\_t usrDefIndex, uint8\_t \*value\);
 </tr>
 <tr id="row1424719410333"><td class="cellrowborder" valign="top" width="21.62%"><p id="p112477417335"><a name="p112477417335"></a><a name="p112477417335"></a>Negative value</p>
 </td>
-<td class="cellrowborder" valign="top" width="78.38000000000001%"><p id="p7247547338"><a name="p7247547338"></a><a name="p7247547338"></a>The operation fails.</p>
+<td class="cellrowborder" valign="top" width="78.38000000000001%"><p id="p7247547338"><a name="p7247547338"></a><a name="p7247547338"></a>The operation failed.</p>
 </td>
 </tr>
 </tbody>
@@ -774,7 +775,7 @@ if (ret != 0) {
 
 -   Setting the configuration of a custom RTC register
 
-Call the following function to configure a register based on the specified register index \(one index corresponds to one byte of the configuration value\):
+Call the **RtcWriteReg()** function to configure a register based on the specified register index \(one index corresponds to one byte of the configuration value\).
 
 int32\_t RtcWriteReg\(DevHandle handle, uint8\_t usrDefIndex, uint8\_t value\);
 
@@ -813,7 +814,7 @@ int32\_t RtcWriteReg\(DevHandle handle, uint8\_t usrDefIndex, uint8\_t value\);
 </tr>
 <tr id="row127231848123615"><td class="cellrowborder" valign="top" width="21.62%"><p id="p197231148173613"><a name="p197231148173613"></a><a name="p197231148173613"></a>Negative value</p>
 </td>
-<td class="cellrowborder" valign="top" width="78.38000000000001%"><p id="p16723134823618"><a name="p16723134823618"></a><a name="p16723134823618"></a>The operation fails.</p>
+<td class="cellrowborder" valign="top" width="78.38000000000001%"><p id="p16723134823618"><a name="p16723134823618"></a><a name="p16723134823618"></a>The operation failed.</p>
 </td>
 </tr>
 </tbody>

en/device-dev/driver/driver-platform-sdio-des.md

-# SDIO<a name="EN-US_TOPIC_0000001160653028"></a>
+# SDIO
 
 ## Overview<a name="section1155271783811"></a>
 
@@ -13,8 +13,7 @@ The SDIO bus has two ends, named host and device. All communication starts when
 - D0-3 signal: four data lines. The DAT1 signal cable is multiplexed as the interrupt line. In 1-bit mode, DAT0 is used to transmit data. In 4-bit mode, DAT0 to DAT3 are used to transmit data.
 - CMD signal: used by the host to send commands and the device to respond to commands.
 
-**Figure 1**  Connections between the host and devices in SDIO<a name="fig1185316527498"></a>  
-    
+**Figure 1**  Connections between the host and devices in SDIO  
 
 ![](figures/en-us_image_0000001160971556.png)
 
@@ -149,12 +148,14 @@ The SDIO interface defines a set of common methods for operating an SDIO device,
 
 ### How to Use<a name="section1490685512255"></a>
 
-[Figure 2](#fig1343742311264)  illustrates the process of using an SDIO.
+The figure below illustrates how to use the APIs.
+
+**Figure 2**  Using SDIO driver APIs
 
-**Figure 2**  Process of using an SDIO<a name="fig1343742311264"></a>  
+  
 
 
-![](figures/en-us_image_0000001206291517.png)
+![](figures/using-SDIO-process.png)
 
 ### Opening an SDIO Controller<a name="section10782428132616"></a>
 

en/device-dev/driver/driver-platform-spi-des.md

@@ -104,10 +104,10 @@ SPI communication is usually initiated by the SPI controller and is operated as
 
 ### How to Use<a name="section32846814820"></a>
 
-[Figure 2](#fig1586912310348)  shows the process of using an SPI device.
+The figure below illustrates how to use the APIs.
 
-**Figure  2** Process of using an SPI device<a name="fig1586912310348"></a>  
-![](figures/process-of-using-an-spi-device.png "process-of-using-an-spi-device")
+**Figure  2** Using SPI driver APIs<a name="fig1586912310348"></a>  
+![](figures/using-spi-process.png "process-of-using-an-spi-device")
 
 ### Obtaining an SPI Device Handle<a name="section1927265711481"></a>
 

en/device-dev/driver/driver-platform-uart-des.md

@@ -103,10 +103,10 @@ The UART interface defines a set of common functions for operating a UART port,
 
 ### How to Use<a name="section1858116395510"></a>
 
-[Figure 3](#fig99673244388)  shows the process of using a UART device.
+The figure below illustrates how to use the APIs.
 
-**Figure  3** Process of using a UART device<a name="fig99673244388"></a>  
-![](figures/process-of-using-a-uart-device.png "process-of-using-a-uart-device")
+**Figure  3** Using UART driver APIs<a name="fig99673244388"></a>  
+![](figures/using-uart-process.png "process-of-using-a-uart-device")
 
 ### Obtaining a UART Device Handle<a name="section124512065617"></a>
 

en/device-dev/driver/driver-platform-watchdog-des.md

@@ -77,10 +77,10 @@ A watchdog, also called a watchdog timer, is a hardware timing device. If an err
 
 ### How to Use<a name="section10181195910815"></a>
 
-[Figure 1](#fig430533913392)  illustrates the process of using a watchdog.
+The figure below illustrates how to use the APIs.
 
-**Figure  1** Process of using a watchdog<a name="fig430533913392"></a>  
-![](figures/process-of-using-a-watchdog.png "process-of-using-a-watchdog")
+**Figure  1** Using watchdog driver APIs  
+![](figures/using-watchdog-process.png "process-of-using-a-watchdog")
 
 ### Opening a Watchdog<a name="section66089201107"></a>