From 0dcbb71e09d1e867dbe26c449e6d8cc4cc037a7c Mon Sep 17 00:00:00 2001
From: Mike Taylor <miketaylr@chromium.org>
Date: Mon, 30 Oct 2023 15:20:47 -0400
Subject: [PATCH] Editorial: link to Fetch's destinations for Sec-Fetch-Dest

---
 index.bs | 6 ++----
 1 file changed, 2 insertions(+), 4 deletions(-)

diff --git a/index.bs b/index.bs
index 27271e1..eb37b90 100644
--- a/index.bs
+++ b/index.bs
@@ -123,10 +123,8 @@ The <dfn http-header export>`Sec-Fetch-Dest`</dfn> HTTP request header exposes a
 Sec-Fetch-Dest = sh-token
 ```
 
-Valid `Sec-Fetch-Dest` values include "`audio`", "`audioworklet`", "`document`", "`embed`",
-"`empty`", "`font`", "`frame`", "`iframe`", "`image`", "`manifest`", "`object`", "`paintworklet`",
-"`report`", "`script`", "`serviceworker`", "`sharedworker`", "`style`", "`track`", "`video`",
-"`worker`", "`xslt`".
+Valid `Sec-Fetch-Dest` values include the set of valid [=request=] [=request/destinations=]
+defined by [[!Fetch]].
 
 In order to support forward-compatibility with as-yet-unknown request types, servers SHOULD ignore
 this header if it contains an invalid value.