Switched to implementation-defined

Author: pmeenan

fetch.bs

@@ -1740,7 +1740,7 @@ not always relevant and might require different behavior.
 
 <p>A <a for=/>request</a> has an associated
 <dfn export for=request id=concept-request-internal-priority>internal priority</dfn> (null or a
-user-agent-defined object). Unless otherwise stated it is null.
+<a>implementation-defined</a> object). Unless otherwise stated it is null.
 
 <p>A <a for=/>request</a> has an associated
 <dfn export for=request id=concept-request-origin>origin</dfn>, which is
@@ -4142,10 +4142,12 @@ the request.
   <p>If <var>request</var>'s <a for=request>internal priority</a> is null, then use
   <var>request</var>'s <a for=request>priority</a>, <a for=request>initiator</a>,
   <a for=request>destination</a>, and <a for=request>render-blocking</a> appropriately in setting
-  <var>request</var>'s <a for=request>internal priority</a> to a user-agent-defined object.
+  <var>request</var>'s <a for=request>internal priority</a> to an <a>implementation-defined</a>
+  object.
 
-  <p class=note>The user-agent-defined 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>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.
 
  <li>
   <p>If <var>request</var> is a <a>subresource request</a>, then: