Number Security, Privacy, Changes (#215)

Overview.bs

@@ -2353,7 +2353,7 @@ when using integer ids, but may be unevenly distributed or even constant for str
 d1 through d4 should take care to make the ends of the id strings vary.  It is valid to mix d1 through d4 with a base64url-encoded
 id.
 
-<h2 class=no-num id=priv>Privacy Considerations</h2>
+<h2 id=priv>Privacy Considerations</h2>
 
 
 <h3  id="content-inference-from-character-set">Content inference from character set</h3>
@@ -2397,7 +2397,7 @@ found in the CSS Fonts 4 specification:
   outside of the documents that reference it would constitute a security leak since the contents of one page would be able to
   affect other pages, something an attacker could use as an attack vector." - [[css-fonts-4#font-palette-values]]
 
-<h2 class=no-num id=sec>Security Considerations</h2>
+<h2 id=sec>Security Considerations</h2>
 
 One security concern is that IFT fonts could potentially generate a large number of network requests for patches. This could cause
 problems on the client or the service hosting the patches. The IFT specification contains a couple of mitigations to limit excessive
@@ -2410,7 +2410,7 @@ number of requests:
      font load. As a result cross-origin requests for patch files are disallowed unless the hosting service opts in via the appropriate
      access control headers.
 
-<h2 class=no-num id=changes>Changes</h2>
+<h2 id=changes>Changes</h2>
 
 Since the <a href="https://www.w3.org/TR/2023/WD-IFT-20230530/">Working 
   Draft of 30 May 2023</a> (see