diff --git a/src/content/docs/speed/optimization/content/troubleshooting/content-encoding-issues.mdx b/src/content/docs/speed/optimization/content/troubleshooting/content-encoding-issues.mdx
index a0ecb7401b1534..9ba441eb29f2e2 100644
--- a/src/content/docs/speed/optimization/content/troubleshooting/content-encoding-issues.mdx
+++ b/src/content/docs/speed/optimization/content/troubleshooting/content-encoding-issues.mdx
@@ -3,7 +3,7 @@ pcx_content_type: troubleshooting
 title: Content encoding issues
 ---
 
-If you are noticing any encoding errors with your HTML pages, we recommend verifying that the impacted pages are explicitly setting the correct charset in the `Content-Type` header from your origin for all text/html pages, for example `Content-Type: text/html; charset=utf-8`. This is particularly important if you are not using UTF-8 encoding. Alternatively you can set the correct charset within the HTML.
+If you are noticing any encoding errors with your HTML pages, we recommend verifying that the impacted pages are explicitly setting the correct charset in the `Content-Type` header from your origin for all text/html pages, for example `Content-Type: text/html; charset=utf-8`. This is particularly important if you are not using [UTF-8 encoding standard](https://en.wikipedia.org/wiki/UTF-8) for characters. Alternatively you can set the correct charset within the HTML.
 
 If you believe these settings are correct, please inform us. You can find more information in [setting the HTTP charset parameter](https://www.w3.org/International/articles/http-charset/index) and in [HTML charset attribute](https://www.w3schools.com/tags/att_meta_charset.asp).