diff --git a/faq/failed-to-load-resource.md b/faq/failed-to-load-resource.md
index e26f51d5..40cb4005 100644
--- a/faq/failed-to-load-resource.md
+++ b/faq/failed-to-load-resource.md
@@ -34,7 +34,7 @@ By default, “127.0.0.1” is used for service connection. "127.0.0.1" uses a s
Set back to self-signed certificate "127.0.0.1" by comment the line `Dynamsoft.WebTwainEnv.Host = "local.dynamsoft.com"` or `Dynamsoft.DWT.Host="local.dynamsoft.com"` out. No need to worry about the expiry date of the certificate anymore.
-- **[Highly Recommend] High Level Security Requirement**
+- **High Level Security Requirement**
1. Set back to "127.0.0.1" by comment the line `Dynamsoft.WebTwainEnv.Host = "local.dynamsoft.com"` or `Dynamsoft.DWT.Host="local.dynamsoft.com"` out.
2. Replace the certificate of "127.0.0.1" with your own domain certificate and build Service MSI yourself. More information refer to [How can I change the certificate of the Dynamsoft Service?](https://www.dynamsoft.com/web-twain/docs/faq/change-dynamsoft-service-certificate.html)
@@ -45,7 +45,7 @@ By default, “127.0.0.1” is used for service connection. "127.0.0.1" uses a s
> Note: the new certificate from Dynamsoft will expire on December 8th, 2023. This means you must update the certificate again after this certificate expires.
- Method 3. Contact Dynamsoft for a new MSI for client-side. -->
-- For v17.2 or higher versions, you can use the new API UpdateCert to automatically update client side certificate before it expires. **Please go to dynamsoft.webtwain.install.js file in the Resource Folder and search the keyword "OnSSLCertInfo"**, add the following lines of code:
+