From 210f0ea97fad0b8a5cc485b1772c1cbdc175acc8 Mon Sep 17 00:00:00 2001
From: Barry Pollard <barrypollard@google.com>
Date: Mon, 4 Sep 2023 09:30:17 +0100
Subject: [PATCH] Editorial: further clarify the early hints HTTP/2 note

---
 source | 6 ++----
 1 file changed, 2 insertions(+), 4 deletions(-)

diff --git a/source b/source
index a96c2fea339..ec9157348bb 100644
--- a/source
+++ b/source
@@ -15861,10 +15861,8 @@ interface <dfn interface>HTMLLinkElement</dfn> : <span>HTMLElement</span> {
   <span data-x="concept-response">response</span>.<ref>RFC8297</ref></p>
 
   <p class="note">For compatibility reasons <a
-  href="https://httpwg.org/specs/rfc8297.html#security-considerations">it is recommended</a> to
-  only send early hints responses over HTTP/2 or later, unless the client is known to handle
-  informational responses correctly. Despite this, the examples below use HTTP/1.1-style notation
-  as per usual convention.</p>
+  href="https://httpwg.org/specs/rfc8297.html#security-considerations">early hints are typically
+  delivered over HTTP/2 or above</a>, but for readability we use HTTP/1.1-style notation below.</p>
 
   <div class="example">
    <p>For example, given the following sequence of responses:</p>