[css-overflow-4] Bikshed fixes

Author: frivoal

css-overflow-4/Overview.bs

@@ -193,7 +193,7 @@ Managing Overflow: the 'overflow-x', 'overflow-y', and 'overflow' properties</h3
 
 	On [=replaced elements=],
 	the [=used values=]
-	of all computed values other than ''visible''
+	of all computed values other than ''overflow/visible''
 	is ''overflow/clip''.
 	Host languages should define [=UA style sheet=] rules
 	that apply a default value of ''overflow/clip'' to such elements
@@ -1777,67 +1777,16 @@ showing in which case space is reserved for the <a>scrollbar gutter</a>.
 
 </div>
 
-<h2 id=priv-sec class=nonum>
-Appendix B: Privacy and Security Considerations</h2>
+<h2 id=privclass=nonum>
+Appendix B: Privacy Considerations</h2>
 
-This specification introduces no new security considerations.
-
-The <a href="http://www.w3.org/2001/tag/">TAG</a> has developed a <a href="https://www.w3.org/TR/security-privacy-questionnaire/">self-review questionnaire</a>
-to help editors and Working Groups evaluate the risks introduced by their specifications.
-Answers are provided below.
-
-<dl>
-<dt>Does this specification deal with personally-identifiable information?
-<dd>No.
-
-<dt>Does this specification deal with high-value data?
-<dd>No.
-
-<dt>Does this specification introduce new state for an origin that persists across browsing sessions?
-<dd>No.
-
-<dt>Does this specification expose persistent, cross-origin state to the web?
-<dd>No.
-
-<dt>Does this specification expose any other data to an origin that it doesn’t currently have access to?
-<dd>No.
-
-<dt>Does this specification enable new script execution/loading mechanisms?
-<dd>No.
-
-<dt>Does this specification allow an origin access to a user’s location?
-<dd>No.
+This specification introduces no new privacy considerations.
 
-<dt>Does this specification allow an origin access to sensors on a user’s device?
-<dd>No.
+<h2 id=sec class=nonum>
+Appendix B: Security Considerations</h2>
 
-<dt>Does this specification allow an origin access to aspects of a user’s local computing environment?
-<dd>No.
-
-<dt>Does this specification allow an origin access to other devices?
-<dd>No.
-
-<dt>Does this specification allow an origin some measure of control over a user agent’s native UI?
-<dd>No
-
-<dt>Does this specification expose temporary identifiers to the web?
-<dd>No.
-
-<dt>Does this specification distinguish between behavior in first-party and third-party contexts?
-<dd>No.
-
-<dt>How should this specification work in the context of a user agent’s "incognito" mode?
-<dd>No difference in behavior is needed.
-
-<dt>Does this specification persist data to a user’s local device?
-<dd>No.
-
-<dt>Does this specification have a "Security Considerations" and "Privacy Considerations" section?
-<dd>Yes, this is the section you are currently reading.
+This specification introduces no new security considerations.
 
-<dt>Does this specification allow downgrading default security characteristics?
-<dd>No.
-</dl>
 
 <h2 id="changes" class="no-num">
 Changes</h2>