update docs

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

en/application-dev/reference/apis/js-apis-sim.md

@@ -350,7 +350,7 @@ Obtains the status of the SIM card in the specified slot. This API uses an async
 | Name  | Type                                  | Mandatory| Description                                  |
 | -------- | -------------------------------------- | ---- | -------------------------------------- |
 | slotId   | number                                 | Yes  | Card slot ID. The options are as follows:<br>- **0**: card slot 1<br>- **1**: card slot 2|
-| callback | AsyncCallback\<[SimState](#simstate)\> | Yes  | Callback used to return the result. For details, see [SimState](#simState). |
+| callback | AsyncCallback\<[SimState](#simstate)\> | Yes  | Callback used to return the result. For details, see [SimState](#simstate). |
 
 **Example**
 

en/device-dev/subsystems/subsys-tel-guide.md

@@ -121,7 +121,7 @@ The following table describes the API for initializing a modem vendor library.
 
 ### Debugging and Verification<a name="section5351151517132"></a>
 
-1.  Use the  [hdc\_std](https://gitee.com/openharmony/docs/blob/master/en/device-dev/subsystems/subsys-toolchain-hdc-guide.md#preparations)  tool to connect to a debugging device. Then, run the following command to send the generated  **libril\_vendor.z.so**  library file to the  **/system/lib/**  directory of the device. For details about how to integrate a library file, see  [Integrating Modem Vendor Libraries](#section590mcpsimp).
+1.  Use the [hdc\_std](https://gitee.com/openharmony/docs/blob/master/en/device-dev/subsystems/subsys-toolchain-hdc-guide.md#preparations) tool to connect to a debugging device. Then, run the following command to send the generated  **libril\_vendor.z.so**  library file to the  **/system/lib/**  directory of the device. For details about how to integrate a library file, see  [Integrating Modem Vendor Libraries](#section590mcpsimp).
 
     ```
     hdc_std file send libril_vendor.z.so /system/lib/
@@ -241,7 +241,7 @@ The following table describes the APIs for responding to modem service requests,
 
 ### Debugging and Verification<a name="section10207938171413"></a>
 
-1.  Use the  [hdc\_std](en-us_topic_0000001080478129.md#section05992022154916)  tool to connect to a debugging device. Then, run the following command to send the generated  **libril\_vendor.z.so**  library file to the  **/system/lib/**  directory of the device.
+1.  Use the [hdc\_std](https://gitee.com/openharmony/docs/blob/master/en/device-dev/subsystems/subsys-toolchain-hdc-guide.md#preparations) tool to connect to a debugging device. Then, run the following command to send the generated  **libril\_vendor.z.so**  library file to the  **/system/lib/**  directory of the device.
 
     ```
     hdc_std file send libril_vendor.z.so /system/lib/
@@ -380,7 +380,7 @@ The following table describes the API for reporting modem events.
 
 ### Debugging and Verification<a name="section16999174401516"></a>
 
-1.  Use the  [hdc\_std](en-us_topic_0000001080478129.md#section05992022154916)  tool to connect to a debugging device. Then, run the following command to send the generated  **libril\_vendor.z.so**  library file to the  **/system/lib/**  directory of the device.
+1.  Use the [hdc\_std](https://gitee.com/openharmony/docs/blob/master/en/device-dev/subsystems/subsys-toolchain-hdc-guide.md#preparations) tool to connect to a debugging device. Then, run the following command to send the generated  **libril\_vendor.z.so**  library file to the  **/system/lib/**  directory of the device.
 
     ```
     hdc_std file send libril_vendor.z.so /system/lib/