Incorporate changes for priority-hints

These changes when combined with similar changes to HTML in
whatwg/html#8470 obsolete the existing
Priority Hints specification https://wicg.github.io/priority-hints/

fetch.bs

@@ -4145,9 +4145,10 @@ the request.
   <var>request</var>'s <a for=request>internal priority</a> to an <a>implementation-defined</a>
   object.
 
-  <p class=note>The <a>implementation-defined</a> object could encompass stream weight and
-  dependency for HTTP/2, and equivalent information used to prioritize dispatch and processing
-  of HTTP/1 fetches.
+  <p class=note>The <a for=request>internal priority</a> <a>implementation-defined</a> object
+  could encompass stream weight and dependency for HTTP/2, priorities used in
+  <a href=https://datatracker.ietf.org/doc/rfc9218/>HTTP extensible priorities</a>, and equivalent
+  information used to prioritize dispatch and processing of HTTP/1 fetches.
 
  <li>
   <p>If <var>request</var> is a <a>subresource request</a>, then:
@@ -7084,9 +7085,9 @@ object), initially null.
  <span class=note>See <a href="https://github.com/whatwg/fetch/issues/1254">issue #1254</a> for
  defining "<code>full</code>".</span>
 
-<dt><code><var>request</var> . <a attribute for=Request>priority</a></code>
+ <dt><code><var>request</var> . <a attribute for=Request>priority</a></code>
  <dd>Returns the <a>priority</a> of the <var>request</var>, e.g., "<code>high</code>",
- "<code>low</code>" or "<code>auto</code>".
+ "<code>low</code>", or "<code>auto</code>".
 
  <dt><code><var>request</var> . <a method for=Request>clone</a>()</code>
  <dd><p>Returns a clone of <var>request</var>.