[css-easing][editorial] Separate security and privacy sections are now required w3c#10688

Author: svgeesus

css-easing-1/Overview.bs

@@ -463,13 +463,17 @@ defined in [[CSSOM]] with the following additional requirements:
   timing-functions-syntax-computed.html
 </wpt>
 
-Privacy and Security Considerations {#priv-sec}
-===================================
+<h2 class=no-num id=privacy>Privacy Considerations</h2>
+
+<!-- Horizontal review wants Security and Privacy sections to be separate. -->
+
+No new privacy considerations have been reported on this specification.
 
 This specification does not directly introduce any new capabilities to the
 Web platform but rather provides common definitions that may be referenced by
 other specifications.
-As a result, it does not introduce any new privacy and security concerns.
+
+<h2 class=no-num id=security>Security Considerations</h2>
 
 Specifications referencing the features defined in this specification
 should consider that while easing functions most commonly

css-easing-2/Overview.bs

@@ -790,13 +790,17 @@ defined in [[CSSOM]] with the following additional requirements:
   timing-functions-syntax-computed.html
 </wpt>
 
-Privacy and Security Considerations {#priv-sec}
-===================================
+<h2 class=no-num id=privacy>Privacy Considerations</h2>
+
+<!-- Horizontal review wants Security and Privacy sections to be separate. -->
+
+No new privacy considerations have been reported on this specification.
 
 This specification does not directly introduce any new capabilities to the
 Web platform but rather provides common definitions that may be referenced by
 other specifications.
-As a result, it does not introduce any new privacy and security concerns.
+
+<h2 class=no-num id=security>Security Considerations</h2>
 
 Specifications referencing the features defined in this specification
 should consider that while easing functions most commonly