Update Style Guide with note about not using inline-errata RFC

Author: RebeccaTamachiro

src/content/docs/style-guide/formatting/external-references.mdx

@@ -13,7 +13,7 @@ For general websites, consider the following recommendations about the link text
 * Authoritative sources for documents such as RFCs can have their own specific format for references, such as the RFC number.
 
 :::note
-When linking to a Cloudflare blog post, sometimes we use only "blog post" for the link text. 
+When linking to a Cloudflare blog post, sometimes we use only "blog post" for the link text.
 :::
 
 ## Referencing RFCs
@@ -37,8 +37,8 @@ When linking to an RFC (or RFC section), consider using a link to the following
 To get the link:
 
 1. Go to [RFC Editor](https://www.rfc-editor.org/rfc-index.html) and search for the RFC number.
-2. Select HTML to open the HTML version.
-3. (optional) Navigate to a specific section, if necessary.
+2. Select **HTML** to open the HTML version. If available, do **not** use **HTML with inline errata** as this version should not be used as reference.
+3. (Optional) Go to a specific section, if necessary.
 4. Use the current URL as the link target in Developer Documentation.
 
 URL example: