[css-2015] Clean up issues

Author: fantasai

css-2015/Overview.bs

@@ -16,33 +16,12 @@ Abstract: This document collects together into one definition all the specs that
 	includes modules by specification stability, not Web browser adoption rate.
 </pre>
 
-<style>
-	.feedback {
-		background: #FFEECC;
-		padding: .5em;
-		border: .5em;
-		border-left-style: solid;
-		border-color: orange;
-		page-break-inside: avoid;
-	}
-	.feedback:before {
-		content: "Review Needed: ";
-		color: #FF8800;
-	}
-</style>
-
 <div boilerplate=status>
 	This document represents the state of CSS as of 2015.
 	The CSS Working Group does not expect any further changes to this document:
 	new snapshots will be published at <a href="http://www.w3.org/TR/CSS/">http://www.w3.org/TR/CSS/</a> as CSS advances.
 </div>
 
-
-<div class="issue">
-	* Plan to incorporate intro material from CSS2.1 in next update
-	* Plan to incorporate property indices/glossaries/etc. once we can generate them for an entire snapshot
-</div>
-
 Introduction {#intro}
 =====================
 
@@ -409,8 +388,6 @@ Requirements for Responsible Implementation of CSS</h2>
 <h4 id="experimental">
 Experimentation and Unstable Features</h4>
 
-	<p class="feedback">Rewritten per gregwhitworth's feedback.
-
 	Implementations of <a>unstable</a> features
 	that are described in W3C specifications
 	but are not interoperable
@@ -447,11 +424,9 @@ Experimentation and Unstable Features</h4>
 <h4 id="proprietary">
 Proprietary and Non-standardized Features</h4>
 
-	<p class="feedback">Rewritten as open vs. closed systems instead of Web vs. non-Web, per szilles' request.
-
 	To avoid clashes with future CSS features,
 	the CSS2.1 specification reserves a
-	<dfn lt="vendor prefix | vendor-prefixed | prefixed | unprefixed"><a href="http://www.w3.org/TR/CSS21/syndata.html#vendor-keywords">prefixed syntax</a></dfn>
+	<dfn lt="vendor prefix | vendor-prefixed | prefixed | unprefixed"><a href="http://www.w3.org/TR/CSS21/syndata.html#vendor-keywords">prefixed syntax</a></dfn> [[!CSS21]]
 	for proprietary and experimental extensions to CSS.
 	A CSS feature is a <dfn>proprietary extension</dfn> if it is meant for use
 	in a closed environment accessible only to a single vendor's user agent(s).
@@ -544,9 +519,6 @@ Vendor-prefixing Unstable Features</h5>
 		due to content depending on that syntax.
 	</details>
 
-	<p class="feedback">Added "should not" against advocating prefixed syntax,
-	per <a href="https://lists.w3.org/Archives/Public/www-style/2015Sep/0165.html">Florian's clarification of dual-syntax usage</a>.
-
 	Anyone promoting <a>unstable</a> features to authors
 	should document them using their standard unprefixed syntax,
 	and avoid encouraging the use of the <a>vendor-prefixed</a> syntax
@@ -555,8 +527,6 @@ Vendor-prefixing Unstable Features</h5>
 <h5 id="open-technology" class="no-toc">
 Preserving the Openness of CSS</h5>
 
-	<p class="feedback">Added "should not" against encumbered features, per dbaron's request.
-
 	In order to preserve the open nature of CSS as a technology,
 	vendors should make it possible for other implementors
 	to freely implement any features that they do ship.
@@ -926,9 +896,6 @@ At-Rule Index</h3>
 <h3 id="properties">Property Index</h3>
 
 ISSUE: Bikeshed should be amended shortly to allow auto-genning the propdef index.
-If this isn't done by the time we publish this spec,
-remove this section until it is.
-
 
 <h3 id="values">Values Index</h3>