Editorial: remove conformance text around limits

Infra handles that as per whatwg/infra#520.

source

@@ -2134,12 +2134,6 @@ a.setAttribute('href', 'https://example.com/'); // change the content attribute
    </dd>
   </dl>
 
-  <p id="hardwareLimitations">
-  <!--INSERT TRACKING-->
-  User agents may impose implementation-specific limits on otherwise unconstrained inputs, e.g., to
-  prevent denial of service attacks, to guard against running out of memory, or to work around
-  platform-specific limitations.</p>
-
   <p>For compatibility with existing content and prior specifications, this specification describes
   two authoring formats: one based on <span data-x="the XML syntax">XML</span>, and one using a <a
   href="#writing">custom format</a> inspired by SGML (referred to as <span>the HTML syntax</span>).
@@ -30303,10 +30297,8 @@ was an English &lt;a href="/wiki/Music_hall">music hall&lt;/a> singer, ...</code
         If the result is less than zero, let <var>error</var> be <i>yes</i>.
         Otherwise, let <var>density</var> be the result.</p>
 
-        <p class="note">If <var>density</var> is zero,
-        the <span>intrinsic dimensions</span> will be infinite.
-        User agents are expected to have limits in how big images can be rendered,
-        which is allowed by the <a href="#hardwareLimitations">hardware limitations</a> clause.</p>
+        <p class="note">If <var>density</var> is zero, the <span>intrinsic dimensions</span> will be
+        infinite. User agents are expected to have limits in how big images can be rendered.</p>
        </li>
       </ol>
      </dd>
@@ -115508,9 +115500,8 @@ dictionary <dfn dictionary>StorageEventInit</dfn> : <span>EventInit</span> {
 
   <p class="note">The algorithm described below places no limit on the depth of the DOM tree
   generated, or on the length of tag names, attribute names, attribute values, <code>Text</code>
-  nodes, etc. While implementers are encouraged to avoid arbitrary limits, it is recognized that <a
-  href="#hardwareLimitations">practical concerns</a> will likely force user agents to impose nesting
-  depth constraints.</p>
+  nodes, etc. While implementers are encouraged to avoid arbitrary limits, it is recognized that
+  practical concerns will likely force user agents to impose nesting depth constraints.</p>
 
 
   <h5>Creating and inserting nodes</h5>