[css-scoping-1][editorial] Split into separate Security and Privacy considerations, as now required for horizontal review. See w3c#7494

Author: svgeesus

css-scoping-1/Overview.bs

@@ -818,13 +818,23 @@ Changes</h2>
 	* Make featureless elements match nothing.
 	* Define <a>in the context of a shadow tree</a>.
 
-Privacy and Security Considerations {#priv-sec}
+Privacy Considerations {#privacy}
 ===============================================
 
 This specification introduces Shadow DOM and some shadow-piercing capabilities,
-but this does not introduce any privacy or security issues--
-shadow DOM, as currently specified, is intentionally not a privacy/security boundary
-(and the parts of the UA that use shadow DOM and <em>do</em> have a privacy/security boundary
+but this does not introduce any privacy issues--
+shadow DOM, as currently specified, is intentionally not a privacy boundary
+(and the parts of the UA that use shadow DOM and <em>do</em> have a privacy boundary
+implicitly rely on protections not yet specified,
+which protect them from the things defined in this specification).
+
+Security Considerations {#security}
+===============================================
+
+This specification introduces Shadow DOM and some shadow-piercing capabilities,
+but this does not introduce any security issues--
+shadow DOM, as currently specified, is intentionally not a security boundary
+(and the parts of the UA that use shadow DOM and <em>do</em> have a security boundary
 implicitly rely on protections not yet specified,
 which protect them from the things defined in this specification).