diff --git a/en/contribute/OpenHarmony-hdf-coding-guide.md b/en/contribute/OpenHarmony-hdf-coding-guide.md
index 84deab62a8cea60e9cd9febfe50ab8df0b3dc2f7..2349d0148c5b4c2bd3128afbe5e4b5f026ae5222 100644
--- a/en/contribute/OpenHarmony-hdf-coding-guide.md
+++ b/en/contribute/OpenHarmony-hdf-coding-guide.md
@@ -190,7 +190,7 @@ root {
 
 [Description] The HDF places the same type of devices in the same host. You can develop and deploy the driver functionalities of the host by layer, so that one driver has multiple nodes. The following figure shows the HDF driver model.
 
-![HDFDriverModel.png]( ../device-dev/driver/figures/HDFDriverModel.png)
+![hdf-driver-model.png]( ../device-dev/driver/figures/hdf-driver-model.png)
 
 Place devices of the same type in the same host. When adding a device, check whether the host of the same type already exists. If such a host already exists, configure the device in the host. Do not configure the same host again. A device belongs to only one driver. Therefore, do not configure the same device in different hosts.
 
diff --git a/en/device-dev/driver/driver-platform-i2c-des.md b/en/device-dev/driver/driver-platform-i2c-des.md
index 0cd8cc6526887c83dd25f67bddb0b82e6bce26d2..9ba71d09003c5598ca4636eed7fe718406a1f960 100644
--- a/en/device-dev/driver/driver-platform-i2c-des.md
+++ b/en/device-dev/driver/driver-platform-i2c-des.md
@@ -64,7 +64,7 @@ The figure below illustrates how to use the APIs.
 
 **Figure  2**  Using I2C driver APIs
 
-![](figures/using-i2c-process.png "process-of-using-an-i2c-device")
+![](figures/using-I2C-process.png "process-of-using-an-i2c-device")
 
 ### Opening an I2C Controller<a name="section13751110132914"></a>
 
diff --git a/en/device-dev/driver/driver-platform-spi-des.md b/en/device-dev/driver/driver-platform-spi-des.md
index 066b92ea231bf86f8a0b2688b1119ef3bd832f84..8c536413b9eb82b92de579038d2f639865f3b157 100644
--- a/en/device-dev/driver/driver-platform-spi-des.md
+++ b/en/device-dev/driver/driver-platform-spi-des.md
@@ -107,7 +107,7 @@ SPI communication is usually initiated by the SPI controller and is operated as
 The figure below illustrates how to use the APIs.
 
 **Figure  2** Using SPI driver APIs<a name="fig1586912310348"></a>  
-![](figures/using-spi-process.png "process-of-using-an-spi-device")
+![](figures/using-SPI-process.png "process-of-using-an-spi-device")
 
 ### Obtaining an SPI Device Handle<a name="section1927265711481"></a>
 
diff --git a/en/device-dev/driver/driver-platform-uart-des.md b/en/device-dev/driver/driver-platform-uart-des.md
index 20340bfd49d68136a9ca711cca35ca5c2cdb0834..5c52adac895044791d673de7e48ef4c4ead18943 100644
--- a/en/device-dev/driver/driver-platform-uart-des.md
+++ b/en/device-dev/driver/driver-platform-uart-des.md
@@ -106,7 +106,7 @@ The UART interface defines a set of common functions for operating a UART port,
 The figure below illustrates how to use the APIs.
 
 **Figure  3** Using UART driver APIs<a name="fig99673244388"></a>  
-![](figures/using-uart-process.png "process-of-using-a-uart-device")
+![](figures/using-UART-process.png "process-of-using-a-uart-device")
 
 ### Obtaining a UART Device Handle<a name="section124512065617"></a>