diff --git a/en/device-dev/driver/driver-peripherals-pinauth-des.md b/en/device-dev/driver/driver-peripherals-pinauth-des.md
index a17fa987d7f3ed178f51030d6e0a064217b15e48..e37576d649ca086f21b1e71218e935529223cd9b 100644
--- a/en/device-dev/driver/driver-peripherals-pinauth-des.md
+++ b/en/device-dev/driver/driver-peripherals-pinauth-des.md
@@ -58,7 +58,7 @@ The Pin_auth driver provides basic PIN authentication capabilities for the upper
 
 **Figure 2** Pin_auth service and pin_auth driver APIs
 
-![image](figures/pin_auth_service_and_driver_interaction.png "interaction between the Pin_auth service and driver")
+![image](figures/pin_auth_service_and_driver_interaction.png "interaction between the pin_auth service and driver")
 
 ### Constraints
 PIN authentication must be implemented in a TEE, and the confidential information, such as PINs and credentials, must be stored in a TEE.
@@ -110,7 +110,7 @@ The following uses the RK3568 platform as an example to demonstrate how to devel
 
 The development procedure is as follows:
 
-1. Develop the Pin_auth driver based on the HDF. The **Bind()**, **Init()**, **Release()**, and **Dispatch()** functions are used. For details about the code, see [pin_auth_interface_driver.cpp](https://gitee.com/openharmony/drivers_peripheral/blob/master/Pin_auth/hdi_service/src/pin_auth_interface_driver.cpp).
+1. Develop the Pin_auth driver based on the HDF. The **Bind()**, **Init()**, **Release()**, and **Dispatch()** functions are used. For details about the code, see [pin_auth_interface_driver.cpp](https://gitee.com/openharmony/drivers_peripheral/blob/master/pin_auth/hdi_service/src/pin_auth_interface_driver.cpp).
 
    ```c++
    // Create the PinAuthInterfaceService object by using the custom HdfPinAuthInterfaceHost object, which consists of the IoService object and HDI service.