From 180d5df28549dc3fe58bb3190c47c1aceb4f020c Mon Sep 17 00:00:00 2001
From: Christian Liebel <christian.liebel@thinktecture.com>
Date: Wed, 15 Nov 2023 04:47:14 +0100
Subject: [PATCH] =?UTF-8?q?Editorial:=20remove=20=E2=80=9Ccommonly?=
 =?UTF-8?q?=E2=80=9D=20to=20reflect=20actual=20JSON=20encoding=20(#1100)?=
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

Co-authored-by: Marcos Cáceres <marcos@marcosc.com>
---
 index.html | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/index.html b/index.html
index 04d53c3a9..ce03227b5 100644
--- a/index.html
+++ b/index.html
@@ -2647,8 +2647,8 @@ <h2>
         as "high value" (particularly from a privacy perspective).
       </p>
       <p>
-        As the manifest format is JSON and will commonly be encoded using
-        [[UNICODE]], the security considerations described in [[JSON]] and
+        As the manifest format is JSON and will be encoded using [[UNICODE]],
+        the security considerations described in [[JSON]] and
         [[UNICODE-SECURITY]] apply. In addition, because there is no way to
         prevent developers from including custom/unrestrained data in a
         <a>manifest</a>, implementors need to impose their own