From d6f9087d7fb9126f7354c13f47fe82e37599aedd Mon Sep 17 00:00:00 2001
From: Ahson Khan <ahson_ahmedk@yahoo.com>
Date: Wed, 22 Jul 2020 13:58:11 -0700
Subject: [PATCH] Highlight that the link to unsafe-escaping shows why it is
 unsafe.

---
 xml/System.Text.Encodings.Web/JavaScriptEncoder.xml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/xml/System.Text.Encodings.Web/JavaScriptEncoder.xml b/xml/System.Text.Encodings.Web/JavaScriptEncoder.xml
index 7a9fae08106..83b88b465ce 100644
--- a/xml/System.Text.Encodings.Web/JavaScriptEncoder.xml
+++ b/xml/System.Text.Encodings.Web/JavaScriptEncoder.xml
@@ -192,7 +192,7 @@ Unlike the <xref:System.Text.Encodings.Web.JavaScriptEncoder.Default> encoding (
 
 Unlike the <xref:System.Text.Encodings.Web.JavaScriptEncoder.Default> encoder, this encoder instance allows some other characters (such as '+') to go through unescaped and therefore must be used cautiously.
 
-For more information, see [Serialize all characters](/dotnet/standard/serialization/system-text-json-how-to#serialize-all-characters).
+For more information about why this could be **unsafe**, see [Serialize all characters](/dotnet/standard/serialization/system-text-json-how-to#serialize-all-characters).
 
           ]]></format>
         </remarks>